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

236 Troubleshooting
5. Report the problem to technical support (using a zip or tar file).
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; server-related information is copied to the
server directory.
For example, in Figure 164 on page 233, 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 on page 234 for an example of fmsupportshow output.
Checking client/server interaction
If you suspect the problem is related to an interaction between the client and the server, check the following
areas:
• No client/server interaction, next
• Client/server version mismatch, page 236
• Determine client or server problem, page 236
No client/server interaction
If the client cannot talk to the server, follow these steps:
1. Ensure that the server name is correct.
2. Ensure that the port number is correct.
3. Ensure there is IP connectivity (ping, trace route, and the like)
4. Check for the presence of firewalls.
5. If a firewall is present, ensure that the proper ports are opened.
Fabric Manager takes the first six ports (numerically) starting with the port entered during installation.
For example, if you entered 24600 as the port during installation, ports 24600 through 24605 are
included. Ensure that ports 20, 21, and 23 are open. Also, for HTTP and API purposes, ports 80, 111,
600 through 1023, and 1024+ must also be open.
Client/server version mismatch
If the client has an incompatible version, a warning is issued. Upgrade the component (client or server)
with the earlier version.
Determine client or server problem
To determine whether the problem is related to the client or the server, follow these steps:
1. Run another client.
If the other client displays correct data, the problem is probably client-related. If it displays incorrect
data, the problem is probably associated with the server.
2. Check the server log for any errors.
If errors exist and the client is operating incorrectly, it is probably a server problem.
Checking the server-side
If you suspect the problem is related to the server side, check the following areas:
• Server cannot access switches, next
• Server-side CPU usage, page 237
• Statistics not collected, page 237