Exit Print View

Sun Datacenter InfiniBand Switch 72 Topic Set

Get PDF Book Print View
 

Document Information

Using This Documentation

Related Documentation

Documentation, Support, and Training

Documentation Feedback

User Guide

Installing the Switch

Administering the Switch

Troubleshooting the Switch

Switch Hardware Problems

InfiniBand Fabric Problems

Understanding the LEDs

Front Status LEDs

Rear Status LEDs

Check Chassis Status LEDs

Check Network Management Port Status LEDs

Check Link Status LEDs

Check Power Supply Status LEDs

Check Fan Status LEDs

Understanding Routing Through the Switch

CXP Connectors and Link LEDs to Switch Chip Port Routes

Switch Chip Port to Switch Chip Port Routes

Switch Chip Port to CXP Connectors and Link LED Routes

Signal Route Through the Switch

Switch GUIDs Overview

Administrative Command Overview

Hardware Command Overview

InfiniBand Command Overview

Monitoring the Hardware

Display Switch General Health

Display Power Supply Status

Check Board-Level Voltages

Display Internal Temperatures

Display Fan Status

Display Switch Environmental and Operational Data

Display Switch Firmware Versions

Locate a Switch Chip or Connector From the GUID

Display Switch Chip Boot Status

Display Link Status

Display Switch Chip Port Status

Monitoring the InfiniBand Fabric

Identify All Switches in the Fabric

Identify All HCAs in the Fabric

Display the InfiniBand Fabric Topology

Display a Route Through the Fabric

Display the Link Status of a Node

Display Counters for a Node

Display Data Counters for a Node

Display Low-Level Detailed Information About a Node

Display Low-Level Detailed Information About a Port

Map LIDs to GUIDs

Display Subnet Manager Status

Controlling the Hardware

Restart the Management Controller

Restart the Entire Switch

Reset the Switch Chip

Recover Ports After Switch Chip Reset

Set Link Speed

Disable a Switch Chip Port

Enable a Switch Chip Port

Change the Administrator Password

Controlling the InfiniBand Fabric

Perform Comprehensive Diagnostics for the Entire Fabric

Perform Comprehensive Diagnostics for a Route

Determine Changes to the InfiniBand Fabric Topology

Find 1x or SDR or DDR Links in the Fabric

Determine Which Links Are Experiencing Significant Errors

Clear Error Counters

Clear Data Counters

Check All Ports

Reset a Port

Set Port Speed

Disable a Port

Enable a Port

Controlling the Subnet Manager

Create the guid.txt File

Create the opensm.conf File

Enable the Subnet Manager

Disable the Subnet Manager

Set the Subnet Manager Priority

Start the Subnet Manager With the opensmd Daemon

Stop the Subnet Manager With the opensmd Daemon

Servicing the Switch

Reference

Understanding the Commands

Index

Determine Changes to the InfiniBand Fabric Topology

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 any time.


  1. Initiate the Subnet Manager.

  2. Take a “snapshot” of the fabric topology.

    # osmtest -f c
    Command Line Arguments
    Done with args
     Flow = Create Inventory
    Aug 13 19:44:53 601222 [B7D466C0] 0x7f -> Setting log level to: 0x03
    Aug 13 19:44:53 601969 [B7D466C0] 0x02 -> osm_vendor_init: 1000 pending umads specified
    using default guid 0x21283a8620b0f0
    Aug 13 19:44:53 612312 [B7D466C0] 0x02 -> osm_vendor_bind: Binding to port 0x21283a8620b0f0
    Aug 13 19:44:53 636876 [B7D466C0] 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
    #
  3. 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
    Aug 13 19:45:02 342143 [B7EF96C0] 0x7f -> Setting log level to: 0x03
    Aug 13 19:45:02 342857 [B7EF96C0] 0x02 -> osm_vendor_init: 1000 pending umads specified
    using default guid 0x21283a8620b0f0
    Aug 13 19:45:02 351555 [B7EF96C0] 0x02 -> osm_vendor_bind: Binding to port 0x21283a8620b0f0
    Aug 13 19:45:02 375997 [B7EF96C0] 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
    -----------------------------
    Aug 13 19:45:02 378991 [B7EF96C0] 0x01 -> osmtest_validate_node_data: Checking node 0x0021283a8620b0a0, LID 0x14
    Aug 13 19:45:02 379172 [B7EF96C0] 0x01 -> osmtest_validate_node_data: Checking node 0x0021283a8620b0b0, LID 0x15
    .
    .
    .
    Aug 13 19:45:02 480201 [B7EF96C0] 0x01 -> osmtest_validate_single_path_rec_guid_pair: 
         Checking src 0x0021283a8620b0f0 to dest 0x0021283a8620b0f0
    Aug 13 19:45:02 480588 [B7EF96C0] 0x01 -> osmtest_validate_path_data: Checking path SLID 0x19 to DLID 0x19
    Aug 13 19:45:02 480989 [B7EF96C0] 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.


Related Information