Documentation, Support, and Training
Understanding Administrative Commands
Understanding the Component Addressing Scheme
Line Card CXP Connector Addressing
Switch-Specific Command Overview
InfiniBand Software Command Overview
Display the General Health of the Switch
Display Power Supplies Present
Check the Status of a Power Supply
Display the Firmware Version of a Power Supply
Check Internal Power and Temperature of a CMC
Check the Status LEDs of a CMC
Display the Firmware Version of a CMC
Display the Firmware Version of the Switch Chassis Manager
Check Fabric Card Power Faults
Check the Internal Power and Temperature of a Fabric Card
Check Fabric Card Internal Temperatures
Check Fabric Card Internal Voltages
Display the Base GUIDs of a Fabric Card
Check Fabric Card Link Status (Simple)
Check Fabric Card Link Status (Detailed)
Check Fabric Card Switch Chip Health
Check the IPMB State of a Fabric Card
Check the Status LEDs of a Fabric Card
Display the Firmware Versions of a Fabric Card
Check the Internal Power and Temperature of a Line Card
Check Line Card Internal Temperatures
Check Line Card Internal Voltages
Display the Base GUIDs of a Line Card
Check Line Card Link Status (Simple)
Check Line Card Link Status (Detailed)
Check Line Card Switch Chip Health
Check the IPMB State of a Line Card
Check the Status LEDs of a Line Card
Display the Firmware Versions of a Line Card
Checking Other Switch Characteristics
Display the Network Management Configuration
Locate a Switch Chip or Connector From the GUID
Monitoring the InfiniBand Fabric
Display Information About the Local HCA
Identify All HCAs in the Fabric
Identify All Switches in the Fabric
Display the InfiniBand Fabric Topology
Display a Route Through the Fabric
Display the Link Status of a Node
Display Data Counters for a Node
Display Low-Level Detailed Information About a Node
Display Low-Level Detailed Information About a Port
Determine the GUID and LID for a Node Within the Switch
Display OFED Software Version Information
Reconfigure the Network Management Parameters
Reconfigure the CMCs for Identical Addresses
Enable and Activate a Power Supply
Deactivate and Disable a Power Supply
Restart a Fabric Card or Filler
Enable a Fabric Card or Filler
Disable a Fabric Card or Filler
Enable Standby Power for a Fabric Card or Filler
Disable Standby Power for a Fabric Card or Filler
Enable a Fabric Card Slot for Hot-Insertion
Activate a Fabric Card or Filler
Deactivate a Fabric Card or Filler
Turn On a Fabric Card or Filler Locator LED
Turn Off a Fabric Card or Filler Locator LED
Enable Downed Fabric Card Links
Enable a Fabric Card Switch Chip Port
Disable a Fabric Card Switch Chip Port
Reset a Fabric Card Switch Chip
Enable Standby Power for a Line Card
Disable Standby Power for a Line Card
Enable a Line Card Slot for Hot-Insertion
Turn On a Line Card Locator LED
Turn Off a Line Card Locator LED
Enable a Line Card Switch Chip Port
Disable a Line Card Switch Chip Port
Controlling the InfiniBand Fabric
Perform Comprehensive Diagnostics for the Entire Fabric
Perform Comprehensive Diagnostics for a Route
Find 1x or SDR or DDR Links in the Fabric
Determine Which Links Are Experiencing Significant Errors
Controlling the Subnet Manager
Start the Subnet Manager With Min Hop Routing
Start the Subnet Manager With Fat Tree Routing
Start the Subnet Manager With the opensmd Daemon
Stop the Subnet Manager With the opensmd Daemon
Understanding ILOM on the Switch
If your fabric has a number of nodes that are suspect, the osmtest command enables you to take a “snapshot” (inventory file) of your fabric and at a later time compare that file to the present conditions.
Note - Though this procedure is most useful after initializing the Subnet Manager, it can be performed at anytime.
Initiate the Subnet Manager.
Take a “snapshot” of the fabric topology.
# osmtest -f c Command Line Arguments Done with args Flow = Create Inventory May 21 15:51:37 220542 [4CC45180] 0x7f -> Setting log level to: 0x03 May 21 15:51:37 220928 [4CC45180] 0x02 -> osm_vendor_init: 1000 pending umads specified May 21 15:51:37 248149 [4CC45180] 0x02 -> osm_vendor_bind: Binding to port 0x3ba000100c70a May 21 15:51:37 281955 [4CC45180] 0x02 -> osmtest_validate_sa_class_port_info: ----------------------------- SA Class Port Info: base_ver:1 class_ver:2 cap_mask:0x2602 cap_mask2:0x0 resp_time_val:0x10 ----------------------------- OSMTEST: TEST "Create Inventory" PASS #
After an event, compare the present topology to that saved in the inventory file:
# osmtest -f v Command Line Arguments Done with args Flow = Validate Inventory May 21 15:58:42 797761 [235DE180] 0x7f -> Setting log level to: 0x03 May 21 15:58:42 798204 [235DE180] 0x02 -> osm_vendor_init: 1000 pending umads specified May 21 15:58:42 825740 [235DE180] 0x02 -> osm_vendor_bind: Binding to port 0x3ba000100c70a May 21 15:58:42 860037 [235DE180] 0x02 -> osmtest_validate_sa_class_port_info: ----------------------------- SA Class Port Info: base_ver:1 class_ver:2 cap_mask:0x2602 cap_mask2:0x0 resp_time_val:0x10 ----------------------------- May 21 15:58:42 936899 [235DE180] 0x01 -> osmtest_validate_node_data: Checking node 0x00144f6c67be0000, LID 0x100 May 21 15:58:42 936956 [235DE180] 0x01 -> osmtest_validate_node_data: Checking node 0x0144f6c666b50100, LID 0x101 . . . May 21 15:55:45 306391 [22B6D180] 0x01 -> osmtest_validate_single_path_rec_guid_pair: Checking src 0x508002000082dc35 to dest 0x508002000082dc35 May 21 15:55:45 307222 [22B6D180] 0x01 -> osmtest_validate_path_data: Checking path SLID 0xFE to DLID 0xFE May 21 15:55:45 308458 [22B6D180] 0x02 -> osmtest_run: ***************** ALL TESTS PASS ***************** OSMTEST: TEST "Validate Inventory" PASS #
Note - Depending on the size of your InfiniBand fabric, the output from the osmtest command could be tens of thousands of lines long.
Switch Reference, osmtest command