IBM SAN256B-6, Installation, Service And User Manual

Page: 171 / 292

v Run the firmwareDownload -s command or firmwaresync command (if versions are compatible) to
update firmware on the replacement blade to bring it up to the proper level.
6.
Perform one of the following tasks to download firmware:
v If you are using an FTP server to download the firmware, skip to the procedure for downloading
firmware from an FTP server.
v If you are using a USB device to download the firmware, skip to the procedure for downloading
firmware from a USB device. If the firmware on the standby CP blade is more than one level down
from the level on the active CP blade, you must have formatted USB devices for each of the
versions you will need to upgrade.
For details on supported upgrade paths and steps to upgrade through multiple versions of Fabric OS,
refer to theFabric OS Release Notes, and theFabric OS Upgrade Guide.
Downloading firmware from FTP server:
About this task
For this task, determine the correct sequence of upgrading firmware versions to reach your target version.
Complete the following steps to download the firmware from an FTP server to the replacement blade.
Procedure
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 remain logged in to the active CP blade in order to monitor it.
2. Run firmwareDownload -s to download the firmware to the replacement (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. 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
following and will appear with a date and time stamp.
Slot 1 (CP0, active): Firmwaredownload command has completed successfully.
Use firmwareshow to verify the firmware versions.
4. 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.
Chassis_1:admin> reboot
Broadcast message from root (ttyS0) Fri Jun 17 14:49:45 2016...
The system is going down for reboot NOW !!
INIT: Switching to runlevel: 6
INIT: Sending processes the TERM signal Chassis_1:admin> HAMu Heartbeat down, stop FSS
Unmounting all f##exiting due to signal: 9, pending signals: 0x20000, 0x0
ilesystems.
Please stand by while rebooting the system...
Restarting system.
The system is coming up, please wait...
.
.
.
Fri Jun 17 14:53:13 2016: Doing firmwarecommit now.
Please wait ...
Fri Jun 17 14:55:27 2016: Firmware commit completes successfully.
Validating the filesystem ...
Fri Jun 17 22:36:05 2016: Doing firmwarecommit now.
Please wait ...
Fri Jun 17 22:36:48 2016: Firmware commit completes successfully.
2016/06/17-14:56:50, [SULB-1004], 908, SLOT 2 | CHASSIS, INFO,
...Firmwarecommit has completed.
2016/06/17-14:56:50, [SULB-1036], 909, SLOT 2 | CHASSIS, INFO,
...The new Version: Fabric OS [version]
2016/06/17-14:56:50, [SULB-1002], 910, SLOT 2 | CHASSIS, INFO,
...Firmwaredownload command completed successfully.
Control Processor Blades
143