Brocade Fabric Manager Administrator's Guide v6.1.0 (53-10000610-02, June 2008)

Fabric Manager Administrator’s Guide 353
53-10000610-02
Server issues
A
If the problem persists or cannot be resolved, see “Capturing/reporting server-side issues” on
page 353.
Checking switch access
If the server cannot access any switches, follow these steps:
1. Ensure that there is IP connectivity to the switches.
2. If you are running secure Fabric OS, check http_policy.
3. If the Fabric Manager server has secured HTTP (HTTPS) enabled, verify that the switch also has
secured HTTP enabled and that the certificates are installed on both the switch and the Fabric
Manager server.
4. Ensure the version of the Fabric OS is supported.
NOTE
Fabric Manager displays inaccessible switches with a blue icon.
Checking server CPU usage
If the server-side CPU usage is too heavy and has an unusually sluggish or slow response, you
should check the recommended configuration.
Checking statistics collection
If your end-to-end or performance monitoring statistics are not collected, verify that the Fabric
Manager PM Server is running. If it is stopped, restart the service using the Server Management
Console. No alerts or errors are generated if this service is not running.
Capturing/reporting server-side issues
Generate supportshow output, as described in “Capturing Fabric Manager support information” on
page 348.
Checking server IP interface configuration in a multihome server
environment
In multihome servers, when the internal FTP server is used, the switch uses one of the IP interfaces
of the server to communicate to the FTP server during operations such as firmware download and
supportsave.
If one or more of the IP interfaces are not reachable from the network where the SAN is configured,
these operations may fail if one of the unreachable interfaces is used by the switch.
1. Open <FM Server Install folder>/server/conf fmservice.conf.
2. Uncomment the following entry and provide a reachable IP interface of the server: