Cluster I/O Protocols (CIP) Configuration and Management Manual (H06.16+, J06.05+)

g. Wait for the updated CLIMs to return to the STARTED state, determined by using the SCF
STATUS CLIM $ZZCIP.* command to find the current status
h. Update down-rev firmware of the remaining CLIM SAS cards that are in slot 5.
i. Choose the Firmware Update action.
ii. Select the SAS cards of Storage CLIMs that show the Firmware Compare State attribute
as Down-rev, that are in slot 5 (that is, whose Resource Name ends with
‘$ZZCIP.Clim-Name.5), and whose CLIMs belong to the second group of Storage
CLIMs to be updated (determined previously by looking at the primary and backup
paths of disks). Add these SAS cards to the bottom pane.
iii. Select the SAS cards of the second group of networking CLIMs that show the Firmware
Compare State attribute as Down-rev, and are in slot 5 (that is, whose Resource
Name ends with $ZZCIP.Clim-Name.5). (Include the CLIM implementing $ZTCP1
in this group.) Add these SAS cards to the bottom pane.
iv. Click Perform Action.
NOTE: During a SAS update of the slot-5 HBA, the CLIM may be rebooted
automatically.
v. Check the estimated time in Table 11 (page 154) and wait for the updates to complete.
(See the figures in step 1.h.)
i. Step 12.h may result in some CLIMs being rebooted automatically which will result in
CLIMs being transitioned to the STARTING state as shown by the SCF STATUS CLIM
$ZZCIP.* command. If any CLIM has changed to the STARTING state, wait until the
recovery is completed and the CLIM changes back to STARTED state.
j. Wait for the updated CLIMs to return to the STARTED state by using the SCF STATUS
CLIM $ZZCIP.* command to find the current status.
Once all the CLIMs and their components are updated, the CLIMs must be rebooted.
Verify if any CLIM was automatically rebooted as a result of the firmware update in step 12.d or
12.h. If so, do NOT reboot it again by using the CLIM reboot procedure in “Rebooting CLIMs
When the System is Up” (page 159).
Rebooting CLIMs When the System is Up
This procedure reboots CLIMs in parallel while avoiding losing access to the OSM Service
Connection, $SYSTEM, or any disk revives.
1. Switch away the paths of the first group of Storage CLIMs:
a. Open the OSM Service Connection Multi-Resource Actions window by using the OSM
Service Connection window and clicking Display→Multi-Resource Actions.
b. Select the resource type CLIM.
c. Choose the Switch Storage Paths Away action.
d. Select the first group of Storage CLIMs to be updated (determined previously by looking
at the primary and backup paths of disks) and add them to the bottom pane.
NOTE: Do not select any Storage CLIM that already was rebooted at the end of firmware
update procedure.
e. Click Perform Action.
f. Wait for the updates to complete. See the figures in step 1.h of “Upgrading CLIM Firmware
with the System Running” (page 150).
2. Add the first group of networking CLIMs:
Select half of the networking CLIMs (include the CLIM implementing $ZTCP0 in this half, but
not the CLIM implementing $ZTCP1), and add them to the bottom pane. Do not select any
networking CLIM that already was rebooted at the end of the firmware-update procedure.
Upgrading CLIM Software and Firmware While Maintaining Network or Storage Traffic 159