Downloading Firmware From A Usb Device - IBM System Storage SAN384B-2 Installation, Service And User Manual

6. Log back in to the standby CP blade and run firmwareDownloadStatus on the
7. If you are upgrading through several levels of the Fabric OS, repeat step 2
8. Log out of the standby CP blade and log in to the active CP blade.
9. Proceed to "Completing the CP8 blade replacement" on page 81

Downloading firmware from a USB device

For this task, refer to Table 14 on page 78 for the correct sequence of upgrading
firmware versions to reach your target version.
Complete the steps to download the firmware from a USB device.
This section assumes that the new firmware has already been copied onto the USB
device. The folder structure on the USB device must be as follows in order to allow
the device to be enabled:
brocade>
The firmware folder contains the folder for the specific release you are installing.
80
SAN384B-2 Installation, Service, and User Guide
standby CP blade to validate a successful commit. This may take up to 10
minutes.
through step 7 as often as necessary based on the path outlined in the table
above. Otherwise, proceed to step 9.
config
firmware
firmwareKey
support
1. Insert the USB drive into the USB port of the active CP blade.
2. Attach a serial cable from the PC to the active CP blade.
3. Log in to the active CP blade as admin if you are not still logged in and then
enter usbStorage -e to enable the USB device.
4. Remove the serial cable from the active CP blade and attach it to the standby
CP blade and log in as admin.
5. 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).
6. 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 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.
7. Ensure that you are still logged in to the standby CP blade (the blade for
which you just changed the firmware level) and type 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...