7.
Verify the installation. See
8.
Replace the chassis door. See
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 HA is not enabled, 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
---------------------------------
1
UNKNOWN
2
SW BLADE
3
CORE BLADE
4
CP BLADE
5
CP BLADE
6
CORE BLADE
7
UNKNOWN
8
SW BLADE
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
Remote CP (Slot 6, CP0): Standby
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.
180
Replacing DC04 SAN Director field-replaceable units (FRUs)
"Verifying operation of the new CP
"Installing the chassis
ID
Status
VACANT
55
ENABLED
52
ENABLED
50
ENABLED
50
ENABLED
52
ENABLED
VACANT
55
ENABLED
Primary partition:
Secondary Partition:
Primary partition:
Secondary Partition:
blade" on page 180.
door" on page 170.
v6.2.0
v6.2.0
v6.2.0
v6.2.0