ibdiagpath Command - Sun Datacenter InfiniBand Switch 648 Topic Set

`ibdiagpath` Command

Traces the InfiniBand fabric diagnostic path. Issued on the Linux InfiniBand host.

Syntax

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]

where:

src_name is the source port.
dst_name is the destination port.
src_lid is the source LID.
dst_lid is the destination LID.
p1,p2,p3,... is the directed route.
count is the number of packets.
outputdir is the output directory.
topology is the topology file.
system is the local system name.
device is the index of the device connecting to the InfiniBand fabric.
port is the port of the device.
PM is the performance manager counter number.
value is the threshold of the performance manager counter.

Description

This InfiniBand software 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:

If directed route addressing is used, the local node is the source node and the route to the destination port is known.
If LID route addressing is used, the source and destination ports of a route are specified by their LIDs.

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	Description
`ibdiagpath.log`	Dump of all the application reports generated according to the provided flags.
`ibdiagpath.pm`	Dump of the Performance Manager counters values, for the fabric links.

Options

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

Option	Purpose
`-n`	Identifies the source and destination ports.
`-l`	Identifies the source and destination LIDs.
`-d`	Sets directed route from the local node to the destination node.
`-c`	Sets the minimum number of packets sent across each link.
`-v`	Provides verbose output.
`-t`	Specifies the topology file name.
`-s`	Specifies the local system name.
`-i`	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.
`-p`	Specifies the local device port number used to connect to the InfiniBand fabric.
`-o`	Specifies the output directory.
`-lw`	Specifies the expected link width.
`-ls`	Specifies the expected link speed.
`-pm`	Dumps all the fabric link Performance Manager counters into `ibdiagpath.pm`.
`-pc`	Resets all the fabric link Performance Manager counters.
`-P`	Use the Performance Manager counter of PM set to the threshold of value.
`-h`	Provides help.
`-V`	Displays the version information.

Example

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

# ibdiagpath -l 1,5
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/lib64/ibdm1.2
-I- Using port 2 as the local port.
-I---------------------------------------------------
-I- Traversing the path from local to source
-I---------------------------------------------------
-I- From: lid=0x003a guid=0x0003ba000100c70a dev=26428 nsn34-39/P2
-I- To:   lid=0x0001 guid=0x00bad0cc010016a2 dev=48438 Port=22
-I---------------------------------------------------
-I- Traversing the path from source to destination
-I---------------------------------------------------
-I- From: lid=0x0001 guid=0x00bad0cc010016a2 dev=48438 Port=1
-I- To:   lid=0x0039 guid=0x00bad0fc0100f8b2 dev=48438 Port=7
-I- From: lid=0x0039 guid=0x00bad0fc0100f8b2 dev=48438 Port=13
-I- To:   lid=0x0005 guid=0x0021283a841513a2 dev=48438 Port=1
-I---------------------------------------------------
-I- PM Counters Info
-I---------------------------------------------------
-I- No illegal PM counters values were found
-I---------------------------------------------------
-I- Path Partitions Report
-I---------------------------------------------------
-I- Source Port=22 lid=0x0001 guid=0x00bad0cc010016a2 dev=48438 Port 22
         PKeys:0xffff 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000
         0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000
         0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000 0x0000
-I- Destination  lid=0x0005 guid=0x0021283a841513a2 dev=48438 PKeys:Not-Enforced
-I- Path shared PKeys: 0xffff
-I---------------------------------------------------
-I- IPoIB Path Check
-I---------------------------------------------------
-I- Subnet: IPv4 PKey:0x7fff QKey:0x00000b1b MTU:2048Byte rate:10Gbps SL:0x00
-I---------------------------------------------------
-I- QoS on Path Check
-I---------------------------------------------------
-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

ibdiagpath man page
ibdiagnet Command

Exit Print View
Sun Datacenter InfiniBand Switch 648 Topic Set