Powering off an expansion unit

Before beginning, read this entire procedure. If there are procedural steps that cannot be performed at this time, the procedure must be delayed until a later time.

1. The system will not allow the expansion unit to be powered off if there are failed or inactive links in the HSL loop that the expansion unit is on, other than the links adjacent to the expansion unit. Verify the existing RIO/HSL loops by completing the following steps:
   
   1. In the navigation area of the HMC, expand Systems Management.
   2. Expand the Servers folder.
   3. Select the server you are working with. A list of server-related tasks will display in the Tasks pane.
   4. Expand the Information folder in the Tasks pane.
   5. Under the Information folder, click the RIO Topology task.
   6. Verify that all of the entries of type External (ignore Internal links) have a LinkStatus of Operational. If the LinkStatus for all of the external entries is operational, continue to the next step. If the LinkStatus is not operational for any of the external entries, the links must be repaired before continuing. If you need assistance, contact your service provider.


2. Verify that the SPCN loop is complete. A 10009135 reference code in the error log indicates an incomplete SPCN loop. A complete SPCN loop is not required, but is highly recommended.



3. The system will not allow the expansion unit to be powered off if the expansion unit is configured as switchable and the system that owns the HSL I/O bridge is not the system that provides power to the expansion unit (the system whose SPCN the expansion unit resides in, or SPCN system).

   Is the expansion unit configured as switchable?
   

   1. No: The expansion unit is configured as private to this system. Go to step 6.
   2. Yes: Continue with the next step.


4. Is the logical owner of the expansion unit also the SPCN system?
   
   1. No: You must switch logical ownership of the HSL I/O bridge in the expansion unit to the SPCN system. This should be done using the iSeries OptiConnect user interface. If the switch cannot be performed, contact your service provider for assistance. When you have switched logical ownership to the SPCN system, continue with the next step.
   2. Yes: Continue with the next step.


5. Does the expansion unit contain resources included in an active Cluster Resource Group (CRG)?
   
   1. No: Continue with the next step.
   2. Yes: End each active CRG that contains resources in the expansion unit, and then continue with the next step.


6. Are any of the I/O resources in the expansion unit owned by partitions running Linux?
   
   1. No: Continue with the next step.
   2. Yes: Power off the partitions running Linux and continue with the next step.


7. Are any of the I/O resources in the expansion unit owned by partitions running AIX?
   
   1. No: Continue with step 8.
   2. Yes: Do the partitions have a code level that supports the powering off and on of an expansion unit with the partition running? The required level for AIX 5.2 is 5.2.0.61 or later and the required level for AIX 5.3 is 5.3.0.22 or later. You can determine the level of AIX by invoking the command lslpp -l devices.chrp.base.rte from the AIX command line.
      • Yes: Continue with the next step.
      • No: Power off the partitions that are running AIX and that own I/O resources in the expansion unit, then continue with the next step.


8. You must ensure that all I/O activity to the expansion unit has been ended. If all partitions that own I/O resources in the expansion unit have been powered off, skip this step and continue with the next step.
   
   
   
   1. In i5/OS partitions:
      • Vary off all configuration descriptions (for example, ctl, device, line, network server, etc.) that use resources in the expansion unit. This can be done using the vrycfg command.
      • If the expansion unit contains disk unit IOPs and/or IOAs, and the disk units are not mirrored to disk units in other expansion towers, end all communications activities to these disk units by ending all subsystems.
   2. In AIX partitions:
      • Unconfigure all logical device resources that use resources in the expansion unit. This can be done using the rmdev command.
      • If logical device resources that use resources in the expansion unit cannot be unconfigured, the procedure must be delayed, or the partitions that have such resources must be powered off.
      • Following is an example of the type of message that is displayed if there are logical AIX resources that must be unconfigured. It shows two messages. The first indicates that logical device resource pci11 with physical name U5294.001.23B2424-CB1-C01 must be unconfigured. To unconfigure this resource invoke the AIX command rmdev -R -l pci11. The second indicates that logical device resources pci6 and ent0 with physical name U0595.001.435DF30-CB1-C02 must be unconfigured. To unconfigure these resources invoke the AIX command rmdev -R -l pci6.

        Reporting partition type: RPA

        Return code type: Failure (hard stop or user intervention required).

        Message:

        com.ibm.hsc.client.rmc.HSCRMCException: Query operation for slot resource has failed on partition 2.

        The partition command is:

        drmgr -Q -c slot -s U5294.001.23B2424-CB1-C01 -w 0 -d 3

        The partition standard output is:

        drslot_chrp_slot: slot_type=1 all slots=0x20042d68

        The partition standard error is:

        0931-029 The specified slot contains a device or devices that are currently configured. Unconfigure the following device or devices and try again.

        pci11

        The RMC return code is 0. The AIX return code is 1.

        Reporting partition type: RPA

        Return code type: Failure (hard stop or user intervention required).

        Message:

        com.ibm.hsc.client.rmc.HSCRMCException:

        Query operation for slot resource has failed on partition 2.

        The partition command is:

        drmgr -Q -c slot -s U0595.001.435DF30-CB1-C02 -w 0 -d 3

        The partition standard output is:

        drslot_chrp_slot: slot_type=1 all slots=0x20042ca8

        The partition standard error is:

        0931-029 The specified slot contains a device or devices that are currently configured. Unconfigure the following device or devices and try again.

        ent0 pci6

        The RMC return code is 0. The AIX return code is 1.

      • The following AIX commands are helpful in determining which logical device resources use an expansion unit. In the following examples, U0595.001.435DF30 is the location code of the expansion unit being powered off.

        Displays information about logical device resource pci5:

        lscfg -l pci5

        Displays all logical resources in U0595.001.435DF30:

        lscfg | grep U0595.001.435DF30

        * pci5 U0595.001.435DF30-CB1 PCI Bus

        + sisioa0 U0595.001.435DF30-CB1-C01 PCI-X Dual Channel U320 SCSI RAID Adapter

        + scsi0 U0595.001.435DF30-CB1-C01-T1 PCI-X U320 SCSI RAID Adapter Physical bus

        + hdisk0 U0595.001.435DF30-CB1-C01-T1-L6-L0 16 Bit LVD SCSI Disk Drive (36400 MB)

        * ses0 U0595.001.435DF30-CB1-C01-T1-L15-L0 SCSI Enclosure Services Device

        + scsi1 U0595.001.435DF30-CB1-C01-T2 PCI-X U320 SCSI RAID Adapter Physical bus

        + sisraid0 U0595.001.435DF30-CB1-C01-C1-T1 PCI-X U320 SCSI RAID Adapter Logical bus

        Displays the rootvg hdisk(s):

        lsvg - o

      • The resources representing the partition's LAN connection to the HMC, such as ent0 and en0, must not be unconfigured or the procedure will not work. If these resources use the expansion unit, the partition must be powered off to continue with the procedure.
        Note: If resources in the expansion unit are assigned to I/O server partitions and are being used by I/O server partitions, you must determine whether powering off the expansion unit will negatively impact the client partitions. If so, the client partitions should be powered off before continuing.


9. Power off all external DVD-RAM storage devices (containing their own power supplies) connected to resources in the expansion unit.



10. Wait for the expansion unit to power off. This might take up to 15 minutes depending on the configuration. If the expansion unit does not power off after more than 15 minutes, contact your service provider for assistance.
    • When the utility gives notification that the power off has completed, ensure that the expansion unit is actually powered off by verifying that one of the two air moving devices (AMDs) in the expansion tower has stopped and that the power LED/indicator on the expansion unit control panel is off.