7. Verify the installation. See “Verifying operation of the new CP blade” on page 84.
8. Replace the chassis door. See “Installing the chassis door” on page 74.
Verifying operation of the new CP blade
To verify that boot and POST are complete on the new CP blade and that the CP blade has achieved
failover redundancy:
1. Log into the active CP as admin.
2. Enable the redundancy feature using the haEnable command.
3. Verify that HA is enabled using the haShow command. The command output includes HA
Enabled Heartbeat Up and HA-state in sync.
If not, POST is not complete or the CP blades have not achieved redundancy. Wait one or two
minutes and re-enter the command until you can verify that redundancy has been achieved.
4. Type slotShow. The command output shows the new CP blade as “enabled”:
swDir:admin> slotShow
Slot Blade Type ID Status
---------------------------------
1 SW BLADE 16 ENABLED
2 SW BLADE 16 ENABLED
3 SW BLADE 16 ENABLED
4 SW BLADE 16 ENABLED
5 CR BLADE 17 ENABLED
6 CP BLADE 18 ENABLED
7 CP BLADE 18 ENABLED
8 CR BLADE 17 ENABLED
9 SW BLADE 16 ENABLED
10 SW BLADE 16 ENABLED
11 SW BLADE 16 ENABLED
12 SW BLADE 16 ENABLED
swDir:admin>
5. Type firmwareShow to determine the Fabric OS version.
This example shows sample output for the firmwareShow command:
swDir:admin> firmwareShow
Local CP (Slot 7, CP1): Active
Primary partition: v6.0.0
Secondary Partition: v6.0.0
Remote CP (Slot 6, CP0): Standby
Primary partition: v6.0.0
Secondary Partition: v6.0.0
Note: If Local CP and Remote CP have different versions
of firmware, please retry firmwaredownload command.
swDir:admin>
6. If the firmware version on the replacement blade does not match that on the active CP blade,
bring the replacement blade to the same firmware level as the active blade.
Replacing DC SAN Director field-replaceable units (FRUs)84
To Next Page
Loading...
