DS8000 Service Documentation Version 6.3.3

MAP4A00 HMC failure with CCL code update or code update utility still active

This procedure is called for when an error is detected but the management console (HMC) cannot communicate with the Storage Facility Image (SFI) to suspended CDA; or the HMC fails and becomes inaccessible while a code load is in process. CDA attributes are kept in the SFI. For the later condition, no open problems can be viewed.

About this task

This MAP is called for when an error is detected but the HMC cannot communicate with the SFI to suspended code update or the HMC fails and becomes inaccessible while a code load is in process. Code update status is kept in the SFI. For the later condition, no open problems can be viewed.

A single HMC can control a code update on more than one storage facility (DS8000®, DS8000, or both) at a time. Only one SFI on each storage facility is updated at a time.

If the HMC itself fails, then more than one code update might also fail. In that case, there should be a separate serviceable event for each code update process. They will be repaired individually.

Related tasks:
How to start the service information center

MAP4A00 Section-1

Procedure

  1. Can you log in to the HMC?
  2. Display the code update request status for the SFI. From the Updates navigation area, select the storage facility from the right work area and then click Request Management Utilities ....
    Note: If a code update is still active in the SFI, and the HMC is no longer aware of that status, using this option to display the status will create a new serviceable event. It will also suspend the code update process in the SFI. (You should not have been sent to this MAP, if this case does not apply.)
    Can the HMC display the status?
    • Yes, go to the next step.
    • No, display and repair serviceable events for the CEC enclosure and private network. After the repair is complete, return to the beginning of this MAP.
  3. Has one of the following occurred since the code update process was started?
    • HMC hard drive was replaced or the code image was reloaded during an HMC repair.
    • HMC was replaced with a different HMC.
    • Yes, ensure that the HMC is loaded with the code level for the update that was in progress. Then, go to the next step.
    • No, go to the next step.
  4. Wait a maximum of 2 minutes before proceeding. This allows the code update process enough time to create a serviceable event if needed. Was a new serviceable event created with an SRC of BE9Cxx40 / BE9Cxx41 (code update invoked by an HMC utility option) or BE9CxxC0 / BE9CxxC1 (code update process invoked by CCL process)?
    • Yes, close the serviceable event that sent you here and then exit this MAP. Continue the repair with the new serviceable event.
    • No, close the serviceable event that sent you here. Exit this MAP and start the code update process over again from the beginning. If it fails again in this MAP step, contact your next level of support.