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

Fabric Manager Administrator’s Guide 361
53-10000610-02
Additional problem areas
A
Relaunch the FC Router Configuration wizard by right-clicking on the edge fabric and selecting FC
Router Configuration; relaunch the Device Connectivity Troubleshooting wizard by clicking
Tasks>Device Management and Troubleshooting>Device Connectivity Troubleshooting (GDD).
Performance monitoring
The following problems might happen if you are using performance monitoring.
Incorrect performance monitoring port statistics
If you are running a 4.x version of Fabric OS on a switch that is v4.2.0b or earlier, the Advanced
Performance Monitoring port statistics for the switch are returned incorrectly. You must upgrade
the firmware on the 4.x switch to Fabric OS v4.2.0c or later.
Performance Monitoring Configuration window hangs
If you have manually stopped the Fabric Manager PM Server process and you then try to refresh
End-to-End monitors, the Performance Monitor configuration window hangs. If this happens, you
must manually restart the Fabric Manager PM Server process.
Fabric Manager database file is too large
Make sure that you periodically back up the Fabric Manager database so that the file does not get
too large. You can back up the database using the Server Management Console. See “Database
backup and restore” on page 329 for instructions.
Sequenced reboot does not show correct status
If you perform a sequenced reboot on all of the switches in a large fabric at the same time, the
Reboot window might not show the status of some of the switches correctly. The Reboot window
might show the status of switches as still performing the reboot when the reboot is actually done
and you can reach the switches using Telnet.
You can use the uptime command to verify how long the switch has been running. Refer to the
Fabric OS Command Reference for information.
Stopping Fabric Manager server on Solaris and Linux
Included in the Fabric Manager installation are scripts for starting and stopping the Fabric Manager
server. Normally you do not need to use these scripts, because the server starts automatically.
However, for troubleshooting you might need to stop and restart the server. To do this, change the
directory to <installdir>/server/bin and run ./fmsvcctl stop or ./fmsvcctl start.
Do not use the other scripts in this directory, such as stopFabricManagerServer.sh,
startFabricManagerServer.sh, and restartFabricManagerServer.sh, because they are intended for
internal use only.