Exit Print View

Sun Datacenter InfiniBand Switch 72 Command Reference

Get PDF Book Print View

Document Information

Using This Documentation

Related Documentation

Documentation, Support, and Training

Documentation Feedback

Understanding the Commands

Understanding Hardware Commands

Understanding InfiniBand Commands

ibaddr Command

ibcheckerrors Command

ibchecknet Command

ibchecknode Command

ibcheckport Command

ibcheckportstate Command

ibcheckportwidth Command

ibcheckstate Command

ibcheckwidth Command

ibclearcounters Command

ibclearerrors Command

ibdatacounters Command

ibdatacounts Command

ibdiagnet Command

ibdiagpath Command

ibhosts Command

ibnetdiscover Command

ibnodes Command

ibportstate Command

ibroute Command

ibstatus Command

ibswitches Command

ibsysstat Command

ibtracert Command

opensm Command

opensmd Daemon

osmtest Command

perfquery Command

saquery Command

sminfo Command

smpdump Command

smpquery Command


ibdiagpath Command

Traces the InfiniBand fabric diagnostic path.


ibdiagpath -n[src_name,]dst_name|-l[src_lid,]dst_lid|-d p1,p2,p3,...[-c count][-v][-o outputdir][-t topology][-s system][-i device][-p port][-wt topology][-pm][-pc][-P PM = value][-lw 1x|4x|12x][-ls 2.5|5|10][-h][-V]



This InfiniBand command traces a path between two end-points and provides information regarding the nodes and ports traversed along the path. The command uses device-specific health queries for the different devices encountered. The way the ibdiagpath command operates is determined from the addressing mode specified on the command line:

In LID route addressing, the actual path from the local port to the source port, and from the source port to the destination port, is defined by means of Subnet Management Linear Forwarding Table queries of the switch nodes along those paths.

Note - When the ibdiagpath command queries the performance counters along the path between the source and destination ports, it always traverses the LID route, regardless of whether a directed route is specified. If one or more links along the LID route are not in the Active state, the ibdiagpath command reports an error.

This command produces a set of files in the output directory. By default, the output directory is /tmp. The following table describes the files.

File Name
Dump of all the application reports generated according to the provided flags.
Dump of the Performance Manager counters values, for the fabric links.

The following table describes the options to the ibdiagpath command and their purposes:

Identifies the source and destination ports.
Identifies the source and destination LIDs.
Sets directed route from the local node to the destination node.
Sets the minimum number of packets sent across each link.
Provides verbose output.
Specifies the topology file name.
Specifies the local system name.
In the case of multiple devices on the local system, this option specifies the index of the device of the port used to connect to the InfiniBand fabric.
Specifies the local device port number used to connect to the InfiniBand fabric.
Specifies the output directory.
Specifies the expected link width.
Specifies the expected link speed.
Dumps all the fabric link Performance Manager counters into ibdiagpath.pm.
Resets all the fabric link Performance Manager counters.
Use the Performance Manager counter of PM set to the threshold of value.
Provides help.
Displays the version information.

The following example shows how to display the route from LID 1 to LID 44 with the ibdiagpath command.

# ibdiagpath -l 1,44
Loading IBDIAGPATH from: /usr/lib64/ibdiagpath1.2
-W- Topology file is not specified.
     Reports regarding cluster links will use direct routes.
Loading IBDM from: /usr/lib/ibdm1.2
-I- Using port 0 as the local port.
-I- Traversing the path from local to source
-I- From: lid=0x0010 guid=0x0021283a8620b0f0 dev=48438 Port=2
-I- To:   lid=0x0009 guid=0x0021283a8620b0a0 dev=48438 Port=8
-I- From: lid=0x0009 guid=0x0021283a8620b0a0 dev=48438 Port=26
-I- To:   lid=0x0005 guid=0x0021283a8189a000 dev=48438 Port=14
-I- From: lid=0x0005 guid=0x0021283a8189a000 dev=48438 Port=20
-I- To:   lid=0x0001 guid=0x00141213180211a2 dev=48438 Port=31
-I- Traversing the path from source to destination
-I- From: lid=0x0001 guid=0x00141213180211a2 dev=48438 Port=17
-I- To:   lid=0x000a guid=0x001412134402f2b2 dev=48438 Port=36
-I- From: lid=0x000a guid=0x001412134402f2b2 dev=48438 Port=26
-I- To:   lid=0x0003 guid=0x00141213180211c2 dev=48438 Port=18
-I- From: lid=0x0003 guid=0x00141213180211c2 dev=48438 Port=33
-I- To:   lid=0x0004 guid=0x00141213180211d2 dev=48438 Port=28
-I- From: lid=0x0004 guid=0x00141213180211d2 dev=48438 Port=19
-I- To:   lid=0x0021 guid=0x0003ba7aa1a3b0a0 dev=48438 Port=35
-I- From: lid=0x0021 guid=0x0003ba7aa1a3b0a0 dev=48438 Port=2
-I- To:   lid=0x002c guid=0x0003ba7aa1a3b0f0 dev=48438 Port=8
-I- PM Counters Info
-I- No illegal PM counters values were found
-I- Path Partitions Report
-I- Source Port=31 lid=0x0001 guid=0x00141213180211a2 dev=48438 Port 31
-I- Destination  lid=0x002c guid=0x0003ba7aa1a3b0f0 dev=48438
-I- Path shared PKeys: 0xffff
-I- IPoIB Path Check
-I- Subnet: IPv4 PKey:0x7fff QKey:0x00000b1b MTU:2048Byte rate:10Gbps SL:0x00
-I- QoS on Path Check
-I- The following SLs can be used:0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15
-I- Stages Status Report:
     STAGE                                    Errors Warnings
     LFT Traversal: local to source           0      0 
     LFT Traversal: source to destination     0      0 
     Performance Counters Report              0      0 
     Path Partitions Check                    0      0 
     Path IPoIB Check                         0      0 
     QoS on Path Check                        0      0 
Please see /tmp/ibdiagpath.log for complete log
-I- Done. Run time was 0 seconds.
Related Information