Verify the Gateway Status

You can use these commands on the management controller to check the status of the gateway.

1. Identify the prerequisite and subsequent installation tasks that you must perform in conjunction with this procedure.

   See Installation Sequence.

2. Check the overall health of the gateway:

   FabMan@gateway_name-> showunhealthy 
   OK - No unhealthy sensors
   FabMan@gateway_name-> 

   An unfavorable output from the showunhealthy command means a hardware fault with that particular component.

3. Check the status of the power supplies:

   FabMan@gateway_name-> checkpower
   PSU 0 present status: OK
   PSU 1 present status: OK
   FabMan@gateway_name->

   A power supply output that is not OK from the checkpower command means that there is a problem with that power supply. See Gateway Administration, checking power supply status LEDs, for assistance.

4. Check the status of the fans:

   FabMan@gateway_name-> getfanspeed
   Fan 0 not present
   Fan 1 running at rpm 11212
   Fan 2 running at rpm 11313
   Fan 3 running at rpm 11521
   Fan 4 not present
   #

   • A stopped or low speed in the output of the getfanspeed command means there is a problem with that particular fan.

   • If not present is in the output of the getfanspeed command, yet a fan is installed at that particular slot, there is a problem with that fan.

   For either condition, check the fan. See Gateway Service, servicing fans.

5. Check the status of the switch chip and BridgeX chips:

   FabMan@gateway_name-> checkboot
   Switch OK
   Bridge-0 OK
   Bridge-1 OK
   FabMan@gateway_name->

   If in the output of the checkboot command a component is not OK, there is a problem with that component. Try resetting the component. See Gateway Administration, resetting the switch chip and Gateway Administration, resetting the BridgeX chips.

6. Alternatively, you can use the env_test command to perform the preceding checks and more:

   FabMan@gateway_name-> env_test
   Environment test started:
   Starting Voltage test:
   Voltage ECB OK
   Measured 3.3V Main = 3.28 V
   Measured 3.3V Standby = 3.37 V
   Measured 12V = 12.06 V
   Measured 5V = 5.03 V
   Measured VBAT = 3.25 V
   Measured 1.0V = 1.01 V
   Measured I4 1.2V = 1.22 V
   Measured 2.5V = 2.52 V
   Measured V1P2 DIG = 1.17 V
   Measured V1P2 AND = 1.16 V
   Measured 1.2V BridgeX = 1.21 V
   Measured 1.8V = 1.80 V
   Measured 1.2V Standby = 1.20 V
   Voltage test returned OK
   Starting PSU test:
   PSU 0 present
   PSU 1 present
   PSU test returned OK
   Starting Temperature test:
   Back temperature 23.00
   Front temperature 32.62
   SP temperature 26.12
   Switch temperature 45, maxtemperature 45
   Bridge-0 temperature 41, maxtemperature 42
   Bridge-1 temperature 43, maxtemperature 44
   Temperature test returned OK
   Starting FAN test:
   Fan 0 not present
   Fan 1 running at rpm 11212
   Fan 2 running at rpm 11313
   Fan 3 running at rpm 11521
   Fan 4 not present
   FAN test returned OK
   Starting Connector test:
   Connector test returned OK
   Starting onboard ibdevice test:
   Switch OK
   Bridge-0 OK
   Bridge-1 OK
   All Internal ibdevices OK
   Onboard ibdevice test returned OK
   Environment test PASSED
   FabMan@gateway_name->

   ---

   Note - If in the output of the env_test command a voltage deviates more than 10% from the provided specification, there is a problem with the respective component.

   ---

7. (Optional) Set the gateway instance numbers.

   ---

   Note - If there is only one gateway in your InfiniBand fabric, you do not need to perform this step.

   ---

   If there is more than one gateway in your InfiniBand fabric, you must verify that each gateway’s instance number is unique.

   1. For each gateway, display its instance number:

      FabMan@gateway_name-> setgwinstance --list
      No BXM system name set, using 6 last bits of the ip-address, value: 34
      FabMan@gateway_name->

      The instance number for this example is 34.

   2. If the instance number is a duplicate, change it:

      FabMan@gateway_name-> setgwinstance number

      where number is the instance number, from 0 to 63. For example:

      FabMan@gateway_name-> setgwinstance 3
      Stopping Bridge Manager..                                  [  OK  ]
      Starting Bridge Manager.                                   [  OK  ]
      FabMan@gateway_name->

   3. Repeat from Step a for all remaining gateways in the InfiniBand subnet.
8. Once the gateway has an operational status, you can start the Subnet Manager.

   See Start the Subnet Manager.

Related Information

• Gateway Command Reference, showunhealthy command

• Gateway Command Reference, getfanspeed command

• Gateway Command Reference, checkboot command

• Gateway Command Reference, env_test command

• Attach the Management Cables

• Attach the Power Cords

• Accessing the Management Controller

• Start the Subnet Manager