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

238 Troubleshooting
Checking fabric discovery problems
If you are having fabric discovery problems, identify the problem and try the solution recommended here:
• Switch does not exist or there is no Ethernet path to the switch: Attempt to ping the switch from both the
client and the server.
• IP address is not properly formed: Fix the IP address and/or URL.
• Domain name is unknown to the DNS: Check the DNS configuration.
• HTTP service on the switch is not running (or is running too slow): Attempt to use Advanced Web Tools
via the client.
• Fabric was reconfiguring or unstable at the time of the attempted launch: Use the fabricshow
command to see if the fabric is stable.
• Switch does not have Advanced Web Tools license: Attempt to use Advanced Web Tools from the client
host.
• Switch cannot deliver Fabricinfo.html: It is not an HP StorageWorks switch.
• Launch switch is already monitored in another fabric: Check all of the loaded fabrics on the client GUI.
• Client has lost connection to the server (or server is down)
For Windows: From the Start menu, select Settings > Control Panel > Administrative Tools > Services >
Fabric Manager Server (see Figure 166). Then use the Action menu to start or restart the server.
For Solaris: Run <fmdir>/server/bin/s99fabman start. This script checks whether the
database is running. If the database is not running, the script restarts it. It then stops and restarts the
Fabric Manager server process.
• Database is not running
CAUTION: Before stopping the database process, you must first stop the Fabric Manager server process
For Windows: From the Start menu, select Settings > Control Panel > Administrative Tools > Services >
Adaptive Server Anywhere- fabmandb (see Figure 167 on page 239). Then use the Action menu to
start or restart the database.
For Solaris: You need to stop and restart the Fabric Manager server process:
1. Run <fmdir>/server/bin/s99fabman stop.
2. Run <fmdir>/server/bin/stopDBServer.sh (to stop the database process).
3. Run <fmdir>/server/bin/startDBServer.sh (to restart the database process) or run
<fmdir>/server/bin/s99fabman start (to start the database and Fabric Manager server
process)