Brocade Fabric Manager Administrator's Guide v6.1.0 (53-10000610-02, June 2008)
352 Fabric Manager Administrator’s Guide
53-10000610-02
Server issues
A
If the client has an incompatible version, a warning is issued.
Checking for no client/server interaction
1. Ensure that the server name is correct.
2. Ensure that the port number is correct.
3. Ensure there is IP connectivity (for example, using ping or trace route).
4. Check for the presence of firewalls.
5. Ensure that the proper ports are opened if a firewall is present.
See “Blocked port numbers” on page 11 for a complete list of ports and firewall requirements.
Installing a compatible client
1. Uninstall the incompatible client, see “Fabric Manager client uninstall” on page 37.
2. Automatically install a compatible version by opening a browser window and typing the Fabric
Manager server hostname or IP address in the Address field; for example:
http://FMserverhost1.companyname.com/
http://192.168.10.11/
Determining whether the problem is on the client or the server
1. Run another client.
If the other client displays correct data, the problem is probably client-related. If it displays
incorrect data, then the problem is probably associated with the server.
2. Check the server log for any errors.
If errors exist, it is probably a server problem if the client is operating incorrectly.
Firmware download failure with downgraded OS version
When SSL is enabled and firmware is downgraded from Fabric OS versions 5.3 or later to version
5.2 or earlier, the HTTP daemon does not restart automatically. This may cause Fabric Manager to
report an error in the firmware download window. If you encounter this issue, restart the HTTP
daemon on the switch (using the CLI) before continuing operations from Fabric Manager.
Server issues
If you suspect the problem is related to the server, check the following areas:
• “Checking switch access” on page 353
• “Checking server CPU usage” on page 353
• “Checking statistics collection” on page 353
• “Checking server IP interface configuration in a multihome server environment” on page 353