IBM System Storage SAN384B-2 Installation, Service And User Manual page 111

1. Log in to the standby CP blade as admin. If you need to know the IP address
of the standby blade, run ipaddrshow.
You should also remain logged in to the active CP blade in order to monitor it.
2. Run firmwareDownload -s to download the firmware to the standby CP blade.
The -s option also disables the autoreboot, so you will have to manually issue a
reboot after the download finishes to initiate firmwarecommit. Enter all
requested information (use default values).
3. To download firmware through the IBM site,
a. Go to the IBM Support Portal, www.ibm.com/supportportal
b. Search for your product machine type (2499) or product name
c. On the displayed page click Download in the Task section
d. From the displayed page, select the appropriate release notes link and read
the release notes prior to downloading and installing the firmware update
e. From the Release notes page, click the Release Firmware link and follow
the online prompts to navigate to the Brocade Downloads for IBM End
Users page.
f. Follow the instructions on the Brocade pages. Enter all requested
information (use default values).
4. When the download process finishes, run firmwareDownloadStatus to verify
that the firmware has been updated. The command displays a running account
of the progress of the firmwareDownload command (if it is still running) until
the command has completed. The final message is similar to the and will
appear with a date and time stamp:
Slot 4 (CP0, active): Firmwaredownload command has completed successfully.
Use firmwareshow to verify the firmware versions.
5. On the standby CP blade (the blade for which you just changed the firmware
level), run reboot. The reboot of the standby CP will initiate a firmwarecommit
to the secondary partition and log you out.
SAN384B-2_124:admin> reboot
Broadcast message from root (ttyS0) Fri Jun 18 14:49:45 2011...
The system is going down for reboot NOW !!
INIT: Switching to runlevel: 6
INIT: Sending processes the TERM signal SAN384B-2_124:admin> HAMu
Heartbeat down, stop FSS
Unmounting all f##exiting due to signal: 9, pending signals:
0x20000, 0x0 filesystems.
Please stand by while rebooting the system...
Restarting system.
The system is coming up, please wait...
.
.
.
Fri Jun 18 14:53:13 2011: Doing firmwarecommit now.
Please wait ...
Fri Jun 18 14:55:27 2011: Firmware commit completes successfully.
Validating the filesystem ...
Fri Jun 18 22:36:05 2011: Doing firmwarecommit now.
Please wait ...
Fri Jun 18 22:36:48 2011: Firmware commit completes successfully.
2011/06/18-14:56:50, [SULB-1004], 908, SLOT 4 | CHASSIS, INFO,
SAN384B-2, Firmwarecommit has completed.
2011/06/18-14:56:50, [SULB-1036], 909, SLOT 4 | CHASSIS, INFO,
SAN384B-2,The new Version: Fabric OS v7.0.1
2011/06/18-14:56:50, [SULB-1002], 910, SLOT 4 | CHASSIS, INFO,
SAN384B-2, Firmwaredownload command has completed successfully.
Note: The time stamp on the co-cpu may not be in sync with the main cpu on
the blade. This is not a cause for concern.
Chapter 5. Removing and installing components
79