Note: Be sure that the captive screws are tightened. If they are not tightened, high pressure from fan
operation may unseat blade from chassis connectors.
4. Observe the blade power and status LEDs and verify the following:
a) The amber status LED on the blade illuminates until POST completes for the blade. The LED
remains amber until the blade has gained sync with the active CP. This can take a few minutes to
complete depending on the configuration. If the status LED remains amber for an extended period,
the board may not be properly seated in the backplane or the board may be faulty.
b) The power LED on the port blade should displays a steady green. If it does not turn on, ensure that
the blade is firmly seated and blade ejector screws are tightened.
5. Connect the cables to the new CP blade.
6. Remain logged in to the active CP and continue to "Verifying and synchronizing firmware on blades" on
page 138.
Verifying and synchronizing firmware on blades
About this task
At this point, the active blade is up and running. The replacement blade is the standby blade. Next, you
must ensure that boot and POST are complete on the newly installed CP blade, that the CP blade has
achieved failover redundancy, and that firmware levels are synchronized on the installed blades.
Perform the following steps.
Procedure
1. Enter slotShow. The command output shows the new CP blade as "enabled."
If the standby CP is unresponsive, you can try unplugging the new CP blade, running haDisable on
the active CP blade, and plugging the new CP blade back in. At that point, you can repeat Step 1 to
begin the verification process again.
2. Log on to each CP blade and enter the haShow command to display the CP status. Verify the CP state,
status, health, and that the HA state is synchronized. Remedy any issues before proceeding. For more
information on haShow output, refer to the Fabric OS Command Reference Manual.
3. Determine the firmware version of installed CP blades by entering firmwareShow. If the serial
console on the replacement CP blade is connected, issue the firmwareShow command there. More
information is available through the console.
4. If the firmware versions for both CP blades are the same, skip to "Completing the replacement" on
page 143.
If the firmware version on the replacement (standby) and active CP blades do not match, a warning
message appears with the results of the firmwareshow command.
WARNING: The local CP and remote CP have different versions
of firmware, please
5. Bring the replacement blade firmware to the same firmware level as the active blade using one of the
following procedures:
• Run the firmwaresync command on the active CP blade to copy all firmware from the active CP
blade to the standby CP blade.
Note: To use this command, you must restart the existing telnet, secure telnet, or SSH sessions to
the standby CP blade.
• 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:
• If you are using an FTP server to download the firmware, skip to the procedure for downloading
firmware from an FTP server.
138 IBM Storage Networking SAN256B-7: SAN256B-7 Installation, Service, and User Guide
Need help?
Do you have a question about the Storage Networking SAN256B-7 and is the answer not in the manual?
Questions and answers