HP StorageWorks Fabric OS 6.x administrator guide (5697-7344, March 2008)

184 Installing and maintaining firmware
Troubleshooting firmwareDownload
Starting in Fabric OS 5.2.0 a network diagnostic script and preinstallation check was added as a part of
the firmwareDownload procedure. The script and preinstallation check performs troubleshooting and
automatically checks for any blocking conditions. However, you should follow these best practices for
firmware download before you start the procedure:
• Keep all session logs.
• Enter the supportSave or the supportShow command before and after entering the
firmwareDownload command.
• If a problem persists, package together all of the information (the Telnet session logs and serial console
logs, output from the supportSave command) for your switch support provider. Make sure you
identify what information was gathered before and after issuing the firmwareDownload command.
If the firmware download fails, see the Fabric OS Message Reference for details about error messages.
Also see, ”Considerations for downgrading firmware to Fabric OS 5.3.0 or earlier” on page 184.
If a firmware download fails in a Director, the firmwareDownload command synchronizes the firmware
on the two partitions of each CP by starting a firmware commit operation. Wait at least 10 minutes for this
commit operation to complete before attempting another firmware download.
If the firmware download fails in a Director, the CPs may end up with different versions of firmware and are
unable to achieve HA synchronization. In such cases, issue the firmwareDownload -s command on the
standby CP; the single mode (-s) option upgrades the firmware on the standby CP to match the firmware
version running on the active CP. Then re-issue the firmwareDownload command to download the desired
firmware version to both CPs. For example, if CP0 is running 5.2.0 on the primary and secondary
partitions, and CP1 is running 5.0.1 on the primary and secondary partition, then synchronize them by
issuing the firmwareDownload -s command.
See the Fabric OS Message Reference for detailed information about .plist-related error messages.
For more information on any of the commands in the Recommended Action section, see the Fabric OS
Command Reference.
NOTE: Some of the messages include error codes (as shown in the example below). These error codes
are for internal use only and you can disregard them.
Example:
Port configuration with EX ports enabled along with trunking for port(s) 63, use
the portcfgexport, portcfgvexport, and portcfgtrunkport commands to remedy this.
Verify blade is ENABLED. (error 3).
Considerations for downgrading firmware to Fabric OS 5.3.0 or earlier
To avoid failure of a firmware downgrade, verify your fabric does not have any of the following conditions:
• If an FC10-6 blade is powered on in the chassis, do not remove the blade until the
firmwareDownload command indicates that it can be removed. Removing the blades before some
related features are removed is not supported.
• If an FC8-16/32/48 blade is present, power-off and remove the blade prior to downgrading the
firmware.
• If there are any IP6 addresses configured, for example, switch IP address, syslog IP addresses, or
RADIUS server, remove the IP6 addresses. The firmwareDownload command will display any IP6
addresses.
• If more than 3000 LSAN zones are configured, reduce the number of LSAN zones.
• If default IP Filter policies are not active on the switch, make the default policies active before
downgrading.
• If the switch is configured with PEAP/MSCHAPv2 for RADIUS authentication, use aaaConfig to
remove the entry.
• If QOS or FIPS is enabled, disable these features prior to downgrading the firmware.