Detecting / Controlling Power in the Complex

GSP

The following procedure uses the GSP command menu to check power status for Superdome cabinets, cells, and core I/O.

1. Log in to the Superdome complex's GSP and access the GSP command menu.From the GSP main menu, enter CM to access the command menu.

2. Issue the PS command from the GSP command menu.

   The PS command allows you to list detailed information about components within the Superdome complex.

   The PS command initially reports all cabinets, cells, and core I/O cards it locates, and prompts you to specify what hardware you want information about.

3. Specify the cabinet whose components' status you want to check.

   For each cabinet, the PS command reports detailed information that includes the power status for all components within the cabinet.

   The information that the PS command reports for each cabinet includes the following details:

   • Cabinet Power—Whether the 48-volt cabinet power switch is on or off, whether cabinet power is enabled, and details about the backplane power boards ("BP Power Boards") and cabinet bulk power supplies ("BPS" 0-5).

   • Cell Power—Whether power is enabled and on for all cells within the cabinet.

   • Core I/O Card Power—Whether power is enabled and on for all core I/O cards within the cabinet.

   For Superdome complexes that have multiple cabinets, you must check details for each cabinet separately.

   The following example shows cabinet power details for cabinet 0 of an SD64000 model Superdome server.

HP-UX Commands

The frupower, parstatus, and rad commands enable you to check Superdome power status from HP-UX.

This procedure describes how to use these HP-UX commands to check cabinet, cell, and I/O chassis, and PCI card slot power details.

1. Log in to HP-UX running on one of the Superdome complex's partitions.

   You can check the power status for cabinets, cells, and I/O chassis from any partition.

   To check the power status for PCI card slots, you must log in to the local partition where the corresponding PCI card cage resides.

2. Issue the HP-UX commands to check the power status for the Superdome complex components of interest to you.

   You can check power status details by using the HP-UX commands shown in the following list.

   For more details on these HP-UX commands, see the manpage for parstatus(1), frupower(1M), and rad(1M).

   This list covers cabinet, cell, I/O chassis, and PCI card slot power.

   • Cabinet Power—Use the parstatus command for Superdome cabinet power information.

     Specify both the verbose (-V) and cabinet number (-b#) options.

     For example, parstatus -V -b0 prints a detailed status for cabinet number 0.

     The parstatus command can give details about each cabinet's bulk power supplies (BPS 0-5, if installed) and backplane power boards, in addition to other details about cabinet fans and blowers.

   • Cell Power—Use the frupower command for cell power status.

     For status on all cells' power, use the frupower -d -C command.

     For status on a specific cell's power, use frupower -d -c# and specify the cell ID.

   • I/O Chassis Power—Use the frupower command for I/O chassis power status.

     For status on all I/O chassis' power, use the frupower -d -I command.

     For status on a specific I/O chassis' power, use frupower -d -i#/#/# and specify the I/O chassis (cabinet/bay/chassis).

   • PCI Card Slot Power—Use the rad -q command and option to list details including PCI card slot power for all PCI card slots within the local partition.

     The rad command provides information for the local partition only.

GSP

Use this procedure to power on or power off cells, I/O chassis, and cabinets through the Superdome complex's GSP.

From the GSP command menu, you can manage the power for all components within the Superdome complex, regardless of the components' partition assignments (if any).

	CAUTION: Be certain to correctly specify the cell, I/O chassis, or cabinet when using the GSP command menu's PE command to power on or off hardware. The PE command does not check whether the hardware is actively being used.

1. Log in to the Superdome complex's GSP and access the GSP command menu.

   From the GSP main menu, enter CM to access the command menu.

2. Issue the PE command and specify the type of hardware whose power you want to turn on or turn off.

   You can manage power to cells, I/O chassis, and cabinets (including all components in the cabinet).

3. Specify the hardware device to power on or power off.

   For cells, specify both the cabinet and cell slot in which the cell resides.

   For I/O chassis, specify the cabinet, bay, and chassis where it resides.

   Note the following issues when using the GSP command menu to manage Superdome hardware power.

   • When you power off an I/O chassis from the GSP command menu, the system firmware resets the cell attached to the I/O chassis.

   • When you power off a cell, the firmware also powers off any I/O chassis attached to the cell.

   • When you power off a cabinet, the firmware also powers off all cells and I/O chassis in the cabinet.

   The GSP does not check whether the specified component is being used; this means you can power cycle hardware that a partition is actively using.

   In the following example the GSP powers off cell 2 in cabinet 0.

HP-UX Commands

Use this procedure to power on or power off cells (and their associated I/O chassis) using HP-UX commands.

When using HP-UX commands to manage power, you are restricted to powering on or off inactive cells that are either assigned to the local partition or are not assigned to a partition.

You cannot use HP-UX commands to manage the power of active cells or cells assigned to a remote partition. To power on or off an I/O chassis using frupower, do so by power cycling the cell to which it is connected.

1. Log in to HP-UX running on one of the Superdome complex's partitions.

   To manage a cell's power you must log in to the partition to which the cell is assigned.

   If the cell is not assigned to a partition, you can manage its power from any partition.

2. Use the frupower command to turn on or turn off the cell's power.

   Specify the frupower -f option to power off a cell. This also powers off any I/O chassis connected to the cell.

   Specify the frupower -o option to power on a cell. This also powers on any I/O chassis connected to the cell.

   The example that follows shows several sample frupower commands and their results.

   In the above example, cell 0 is active and thus cannot be powered off using frupower. Cell 2 is inactive and is powered off (frupower -f -c2) and then powered back on (frupower -o -c2). Cell 6 is assigned to a remote partition (partition number 1) and thus cannot be powered off. I/O chassis 0/1/1 is attached to cell 4, so to power it off cell 4 must be powered off.

Partition Manager

Powering cells on and off can be done through the Partition Manager, though the Partition Manager limits what you can do based on whether the cell you are trying to control is in an active state, and whether it is in the local partition or a remote partition. If you attempt to power off a cell in a remote partition the Partition Manager will report an error message. The Partition Manager will also not allow you to power off an active cell by not making available the menu item to do so when an active cell is selected. Also, cell boards must be configured into a partition before you can power them on.

To power on a cell board or to power off an inactive cell board in the local partition:

1. On the left-hand side of the Partition Manager's primary display window, highlight the entry for the partition that contains the cell that you want to power on/off. This will display a list of cells and I/O chassis for the partition on the right-hand side of the window.

2. On the right-hand side of the window, highlight the entry for the cell that you want to control power to.

3. From the Cell menu, select Power On Cell (or Power Off Cell)

   If an I/O chassis is attached to the cell board that you are powering on or off, the I/O chassis will also be powered on or off, respectively.

HP-UX Commands

Use this procedure to turn on and turn off service indicator lights using the fruled command.

1. Log in to HP-UX running on one of the Superdome complex's partitions.

   You can turn on or off any of the service and cabinet LEDs in a Superdome complex from HP-UX running on any of the complex's partitions.

2. Use the fruled command to turn on or off cabinet number LEDs or the service LEDs for cells and I/O chassis.

   Use the fruled -f option to turn off an LED and use fruled -o to turn on an LED.

   When issuing the fruled command, specify cells and I/O chassis using the notation described in the fruled(1) manpage.

   The following example turns off and turns on various cell, I/O chassis, and cabinet LEDs.

   For complete details refer to the fruled(1) manpage.

3. If you want to check the status of cell and I/O chassis LEDs, use the GSP command menu's PS command.

   Log in to the Superdome complex's GSP and access the command menu.

   In the following example, the service LEDs for cells 0, 2, and 4 are turned on, as are the service LEDs for I/O chassis 0/0/1 and 0/0/3.

Partition Manager

The Partition Manager can be used to temporarily turn on service indicator lights for cells and I/O chassis.

1. Use the Partition Manager's tree structure locate and select the cell board, or I/O Chassis associated with the LED that you want to light.

2. Cell board indicator LEDs: Select Light Cell LED from the Cell menu. In addition to lighting the LED on the cell board, the two-digit cabinet number for the cabinet containing the cell board will flash.

   I/O chassis indicator LEDs: Select Light I/O Chassis LED from the I/O menu. In addition to lighting the LED on the I/O chassis, and the two-digit cabinet number for the cabinet containing the I/O chassis will flash.

3. A requestor will appear, regardless of the type of indicator you chose to light. When you are finished locating the indicated hardware, you can extinguish the indicators by clicking on the OK button in the requestor.