HP StorageWorks Fabric Manager 5.x Administrator Guide (AA-RUQSF-TE, September 2005)

234 Troubleshooting
The fmsupportshow utility provides the following information in the specified destination directory:
For Windows:
• ..\FabricManager\support\<date and time directory>\client
• ..\FabricManager\support\<date and time directory>\server
The fmsupportshow utility creates a directory using a combination of date and time stamp, and
copies all these files into this directory.
Client-related information is copied to the client directory, and server-related information is copied to
the server directory.
For example, in Figure 164, the files are located at:
• C:\FabricManager\support\09-28-2004-9-12-51\client
• C:\FabricManager\support\09-28-2004-9-12-51\server
For Solaris: See Figure 165 for an example of fmSupportShow output.
Figure 165 Example of fmSupportShow output for Solaris
Checking the client-side
If you suspect the problem is related to the client-side, check the following areas:
• Authentication issues (unable to log in), next
• Client access to switches, page 235
• Client-side CPU usage, page 235
If the problem persists or cannot be resolved, see ”Capturing and reporting client-side issues” on
page 235.
Authentication issues (unable to log in)
If the user is unable to log in to the Fabric Manager server, follow these steps:
1. Check the userid and password.
2. Check the Login Module and Domain settings in the server:
<installdir>/server/server/fmserver/deploy/fmauth-service.xml
Depending on the platform you have installed, there are three possible valid settings in the
fmauth-service.xml file:
• Fabric Manager server running under Windows when using Windows domain authentication:
<attribute name="LoginModule">Win</attribute>
<attribute name="DomainName">"your_domain"</attribute>
fmgr007006:/test/fm4.4/FabricManager/bin# ./fmsupportshow.sh
creating directory
/test/fm4.4/FabricManager/support/2004-09-28-09-28-12
Please include the following information along with the output of
fmclientsupportshow
1. Screenshot of client, if reporting UI issue
2. Fabric/switch activities (firmware downloads, reboots, seg/merge
etc)
3. Actions executed from FM (all of above and CM, PM etc)
creating directory
/test/fm4.4/FabricManager/support/2004-09-28-09-28-12/client
Fabric Manager Client data captured successfully to
/test/fm4.4/FabricManager/support/2004-09-28-09-28-12/client
creating directory
/test/fm4.4/FabricManager/support/2004-09-28-09-28-12/server
Fabric Manager Server data captured successfully to
/test/fm4.4/FabricManager/support/2004-09-28-09-28-12/server
fmgr007006:/test/fm4.4/FabricManager/bin#