1IBDIAGPATH(1) IB DIAGNOSTIC PACKAGE IBDIAGPATH(1)
2
6 ibdiagpath - IB diagnostic path
7
9 ibdiagpath
10 {-n <[src-name,]dst-name>|-l <[src-lid,]dst-lid>|-d
11 <p1,p2,p3,...>}
12 [-c <count>] [-v] [-t <topo-file>] [-s <sys-name>] [-i
13 <dev-index>]
14 [-p <port-num>] [-o <out-dir>] [-lw <1x|4x|12x>] [-ls <2.5|5|10>]
15 [-pm]
16 [-pc] [-P <<PM counter>=<Trash Limit>>]
17
19 ibdiagpath traces a path between two end-points and provides
20 information regarding the nodes and ports traversed along the path. It
21 utilizes device specific health queries for the different devices along
22 the traversed path. The way ibdiagpath operates depends on the
23 addressing mode used on the command line. If directed route adressing
24 is used, the local node is the source node and the route to the
25 destination port is known apriori. On the other hand, if LID route (or
26 by-name) addressing is imployed, then the source and destination ports
27 of a route are specified by their LIDs (or by the names defined in the
28 topology file). In this case, the actual path from the local port to
29 the source port, and from the source port to the destination port, is
30 defined by means of Subnet Management Linear Forwarding Table queries
31 of the switch nodes along those paths. Therefore, the path cannot be
32 predicted as it may change. The tool allows omitting the source node,
33 in which case the local port on the machine running the tool is assumed
34 to be the source. Note: When ibdiagpath queries for the performance
35 counters along the path between the source and destination ports, it
36 always traverses the LID route, even if a directed route is specified.
37 If along the LID route one or more links are not in the ACTIVE state,
38 ibdiagpath reports an error. Checks for path validity from partitions,
39 IPoIB and QoS perspectives are also provided.
40 ibdiagpath.log -
42 A dump of all the application reports generate according to the
43 provided flags
44 ibdiagnet.pm -
46 A dump of the pm Counters values, of the fabric links
47
49 -n <[src-name,]dst-name> :
50 Names of the source and destination ports (as defined in the
51 topology file; source may be omitted -> local port is assumed to be
52 the source)
53 -l <[src-lid,]dst-lid> :
54 Source and destination LIDs (source may be omitted -> local port
55 is assumed to be the source)
56 -d <p1,p2,p3,...> :
57 directed route from the local node (which is the source) and the
58 destination node
59 -c <count> :
60 The minimal number of packets to be sent across each link (default
61 = 100)
62 -v :
63 Enable verbose mode
64 -t <topo-file> :
65 Specifies the topology file name
66 -s <sys-name> :
67 Specifies the local system name. Meaningful only if a topology
68 file is specified
69 -i <dev-index> :
70 Specifies the index of the device of the port used to connect to
71 the IB fabric (in case of multiple devices on the local system)
72 -p <port-num> :
73 Specifies the local device's port number used to connect to the IB
74 fabric
75 -o <out-dir> :
76 Specifies the directory where the output files will be placed
77 (default = /tmp)
78 -lw <1x|4x|12x> :
79 Specifies the expected link width
80 -ls <2.5|5|10> :
81 Specifies the expected link speed
82 -pm :
83 Dump all the fabric links, pm Counters into ibdiagnet.pm
84 -pc :
85 Reset all the fabric links pmCounters
86 -P <PM=<Trash>> :
87 If any of the provided pm is greater then its provided value,
88 print it to screen
89 -h|--help :
90 Prints the help page information
91 -V|--version :
92 Prints the version of the tool
93 --vars :
94 Prints the tool's environment variables and their values
95
97 1 - The path traced is un-healthy
98 2 - Failed to parse command line options
99 3 - More then 64 hops are required for traversing the local port to the
100 "Source" port and then to the "Destination" port.
101 4 - Unable to traverse the LFT data from source to destination
102 5 - Failed to use Topology File
103 6 - Failed to load required Package
104IBDIAG 1.0 2014-03-20 IBDIAGPATH(1)