Recommended Information Gathering for ISW (Identity Synchronization for Windows)
When contacting Sun Support to obtain assistance with an ISW issue it is necessary to provide a detailed problem description and a minimum set of required data. Directly below are some guidelines on these topics. It will also often be necessary to collect additional data which is more specific to the problem - recommendations for which will also follow.
Variables and Acronyms Used in This Technical Note
ISW Acronym for Identity Synchronization for Windows
MQ Acronym for Message Queue
admin-server-root This is the base file system location for the admin console install.
server-root This is the base file system location for the ISW (default /var/opt/SUNWisw)
isw-bin-path This is the path to the ISW binaries (default /opt/SUNWisw)
isw-configuration-root-suffix This is the directory server suffix which contains the ISW configuration defined at install of ISW core.
mq-install-path This is the base file system location for the Message Queue (default /var/imq)
Recommended basis for Data Collection for all ISW Server issues in a tar.gz file format:
- A clear current detailed problem description
- Current dateline of the ISW state, before and after the problem started, including actions already attempted.
- List of any changes that took place up to the current time, including changes that took place prior to the problem taking place.
- Complete network topology that includes host names, assigned IPs, OS versions, network hardware , software versions and location preferred in graphical format.
- Is this issue in a development, test or production environment?
- If production, is a development or test environment available?
- Is the problem continuous, or reproducible? If so please provide a complete step by step test case including sample data.
- Sun Explorer (SUNWexplo) output for the host where the issue took place.
- Provide the ISW configuration
To dump the ISW configuration data to an LDIF file, please do the following:
First you need to know where your ISW configuration data is stored. On install the very first item it asks for the configuration Root suffix. When using idsync the value for "-s" is the suffix in where it is stored. If you know where your "o=netscapeRoot" is stored you can search for the attribute "iplanetKeyValue", which will have a value that starts with configRoot=
$ ldapsearch -p port -h hostname -b "ou=services,isw-configuration-root-suffix" -D "cn=Directory manager" -w password objectclass=*
- Provide the ISW version & JRE version
To determine the version information please do the following.
$ /var/opt/SUNWisw/logs/sysmgr
$ egrep "Windows build" audit*
The result should look similar to this example below.
[24/Jul/2009:09:08:19.244 -0400] INFO 10 "Log opened. Identity Synchronization for Windows build 2009.047.1115. Java runtime version is 1.5.0_16."
- Provide ISW log files
The logs can be found in this location
$/var/opt/SUNW/isw/logs
tar.gz the whole directory
- Provide Sun Directory Server log files.
The logs can be found in this location
SunDS5: /server-root/slapd-instance_name/logs/error
/server-root/slapd-instance_name/logs/access
/server-root/slapd-instance_name/logs/audit (If Audit logging is enabled)
SunDS6: /instance-path/logs/access
/instance-path/logs/errors
/instance-path/logs/audit (If Audit logging is enabled)
If the logs do not exist in their default locations, examine the Directory Server configuration file, (SunDS6) instance-path/config/dse.ldif, (SunDS5) /server-root/slapd-instance_name/config/dse.ldif, to find the paths to the log files. The attributes that disclose the location to the files are nsslapd-accesslog, nsslapd-errorlog and nsslapd-auditlog (If enabled).
You can also use a script called Dirtracer from here to collect the SunDS data, which would cover all the requested data for the directory server.
You can find the script located at, "http://www.sun.com/bigadmin/scripts/indexSjs.html"
- Please provide the version of the directory server(s).
To find this data you can do the following.
SunDS5: cd /server-root/bin/slapd/server then ./ns-slapd -D /server-root/slapd-instance_name -V
SunDS6: /install-path/lib/ns-slapd -D instance-path _V
Windows 2000: Click Start - Settings - Control Panels - System, Upper right hand side shows the version information
Windows 2003: Click Start -RUN , type "winver" <enter>
- Please provide the MQ version
$ /usr/bin/imqbrokerd -v
For Further Information:
External documents for troubleshooting can be found at: http://docs.sun.com/app/docs/doc/820-2768/isw?l=en&a=view
Install :http://docs.sun.com/app/docs/doc/820-2761/isw-install?l=en&a=view
idsync command line interface: http://docs.sun.com/app/docs/doc/820-2761/gdaiw?l=en&a=view
Deployment Planning, http://docs.sun.com/app/docs/doc/820-0386?l=en
Sign up or Log in to add a comment or watch this page.