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

Fabric Manager 5.x administrator guide 241
• Installation Wizard does not launch, page 241
• Installation Wizard locks up, page 241
• Incorrect performance monitoring port statistics, page 241
• Stopping the Fabric Manager server on Solaris, page 242
• Changing printers in Fabric Manager, page 242
• Changing the time in Fabric Manager, page 242
• Not enough system resources error, page 242
Installing Fabric Manager client on Solaris using BASH
When installing the Fabric Manager client on a Solaris 8 operating system with a BASH as the default
shell, you must run the following command from the command line before launching the Fabric Manager
client:
bash --login
If you do not run this command before you launch the client, Fabric Manager does not run properly.
Cannot locate Fabric Manager license key and serial number
Fabric Manager 4.1.0 and later stores the serial number and license key in a file each time a user
successfully registers Fabric Manager. The file name is fmlicense.txt and should be in the local Fabric
Manager user directory. The file contains the version of Fabric Manager installed, the serial number,
license key, license type, and licensing date.
You can also select Help > Register to view the license key and serial number.
If you still cannot find your license key and serial number, contact Technical Support.
Switches and hosts no longer recognize HBA after firmware download to the HBA
During the firmware download to HBA, if the switch that the HBA is attached to is rebooted, or the host that
the HBA is attached to is rebooted, the firmware in the HBA flash memory can become corrupted and HBA
cannot log in to the switch or respond to the query from the switch. Thus, from both the Fabric Manager
and the switch point of view, this HBA does not appear and drops out of the name server list.
To solve this problem, use HBAnyware on the attached host and reload the firmware on the HBA.
503 service unavailable/overloaded error
The 503 error indicates that Fabric Manager has discovered a switch whose web server is either
unavailable or overloaded. If you receive this error, try to poll the switch using only one Fabric Manager
server.
When a switch displays this error after Fabric Manager has already discovered the switch, the error is
displayed only in the error log.
Although switches can appear as unreachable in Fabric Manager when they receive this error, the error
occurs more frequently on switches that run firmware versions 2.x and 3.x.
Installation Wizard does not launch
Run the DOS command dxdiag and make sure that the graphics tests run without errors. If any version of
DirectX files or any diagnostic files are missing, visit the Microsoft web site and upgrade to the latest
version of DirectX.
Installation Wizard locks up
Press the Ctrl key until a DOS Java console is displayed. The console captures a log of the entire
installation process.
Incorrect performance monitoring port statistics
If you are running a 4.x version of Fabric OS on a switch that is 4.2.0b or earlier, the Advanced
Performance Monitoring port statistics for it are returned incorrectly. You must upgrade the firmware on the
4.x switch to Fabric OS 4.2.0c or later.