53-1001806-01 January 31, 2010 Control Processor Blade (CP8) Replacement Procedure Supporting Fabric OS v6.0.0 through v6.3.
Notes, Cautions, and Warnings NOTE A NOTE indicates important information that helps you make better use of your computer. CAUTION See the safety and regulatory information that shipped with your system. For additional regulatory information, see the Regulatory Compliance Homepage on www.dell.com at the following location: www.dell.com/regulatory_compliance. CAUTION A CAUTION indicates potential damage to hardware or loss of data if instructions are not followed.
In this guide • Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Time and items required . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Verifying the necessity of replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Recording critical backbone information . . . . . . . . . . . . . . . . . . . . . . . . . . . . • Removing a control processor blade (CP8) . . . . . . . . . . . . . . .
• • • • • • • • “Slot unknown” message relating to a CP slot CP blade errors or I2C timeouts FRU: FRU_FAULTY messages for a CP blade Configuration loader messages or “Sys PCI config” messages Generic system driver messages (“FABSYS”) Platform system driver messages (“Platform”) EM messages that indicate a problem with a CP blade Function fail messages for the CP master For more information about error messages, refer to the Fabric OS Message Reference.
This is an example of failing over a CP blade: Fabric OS (cp1) cp1 login: admin Password: swDir:admin> hashow Local CP (Slot 7, CP1): Active Remote CP (Slot 6, CP0): Standby, Healthy HA enabled, Heartbeat Up, HA State synchronized swDir:admin> hafailover Local CP (Slot 7, CP1): Active Remote CP (Slot 6, CP0): Standby, Healthy HA enabled, Heartbeat Up, HA State synchronized Warning: This command is being run on a redundant control processor(CP) system.
Removing a control processor blade (CP8) The PowerConnect B-DCX continues to operate while a CP blade is being replaced if the redundant CP blade is active and a failover does not occur. You can prevent failover by entering the haDisable command. ATTENTION The instructions below refer to the top and bottom of each blade in the vertical orientation as used in the PowerConnect B-DCX.
FIGURE 2 Control processor blade (CP8) in a DCX-4S chassis Replacing a control processor blade (CP8) ATTENTION The instructions below refer to the top and bottom of each blade in the vertical orientation as used in the PowerConnect B-DCX. For the PowerConnect B-DCX-4S, because the blades are horizontally oriented, top should be read as left and bottom should be read as right. ATTENTION Follow ESD precautions (see “ESD Precautions” in your chassis’ hardware reference manual).
7. Verify the installation (“Verifying operation of the new CP blade”). 8. Replace the chassis door (see the Chassis Door Replacement Procedure for your chassis). 9. Remain logged in to the active CP and continue to “Verifying operation of the new CP blade.” Verifying operation of the new CP blade ATTENTION The instructions below reference specific slot numbers. these numbers will be different between the PowerConnect B-DCX-4S and PowerConnect B-DCX.
10 FA4-18 FOS SAS 12 FR4-18i FOS v6.1.0 v6.1.0 v3.1.1 v3.1.1 v6.1.0 v6.1.0 rsl8-st03-dcx-1:admin> 3. If the firmware versions for both CP blades are the same, skip to step 11. 4. If the firmware version on the replacement blade does not match that on the active CP blade a warning message appears with the results of the firmwareshow command. You must bring the replacement blade to the same firmware level as the active blade using the firmwareDownload -s command to bring it up to the proper level.
7. Type firmwareDownloadStatus to verify that the firmware has been updated. 8. 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. 9. Log back in to standby CP blade and type firmwaredDownloadStatus on the standby CP blade to validate a successful commit. This may take 10 minutes. 10.