User Manual

Rev 2.2-1.0.1
Mellanox Technologies
225
9.4.2 ibdiagnet (of ibutils) - IB Net Diagnostic
Please note that ibdiagnet is an obsolete package. We recommend using ibdiagnet from
ibutils2.
This version of ibdiagnet is included in the ibutils package, and it is not run by default
after installing Mellanox OFED.
To use this ibdiagnet version and not that of the ibutils package, you need to specify
the full path: /opt/ibutils/bin
9.4.3 ibdiagpath - IB Diagnostic Path
ibdiagpath is located at: /opt/ibutisl/bin.
ibdiagpath traces a path between two end-points and provides information regarding the nodes
and ports traversed along the path. It utilizes device specific health queries for the different
devices along the path.
The way
ibdiagpath operates depends on the addressing mode used on the command line. If
directed route addressing is used (-d flag), the local node is the source node and the route to the
destination port is known apriori. On the other hand, if LID-route (or by-name) addressing is
employed, then the source and destination ports of a route are specified by their LIDs (or by the
names defined in the topology file). In this case, 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 that path. Therefore, the path cannot
be predicted as it may change.
ibdiagpath should not be supplied with contradicting local ports by the -p and -d flags (see
synopsis descriptions below). In other words, when ibdiagpath is provided with the options -p
and -d together, the first port in the direct route must be equal to the one specified in the “-p”
option. Otherwise, an error is reported.
When ibdiagpath queries for the performance counters along the path between the
source and destination ports, it always traverses the LID route, even if a directed route
is specified. If along the LID route one or more links are not in the ACTIVE state, ibdi-
agpath reports an error.
Moreover, the tool allows omitting the source node in LID-route addressing, in which case the
local port on the machine running the tool is assumed to be the source.
Synopsis
ibdiagpath {-n <[src-name,]dst-name>|-l <[src-lid,]dst-lid>|-d <p1,p2,p3,...>} [-c <count>]
[-v] [-t <topo-file>] [-s <sys-name>] [-ic<dev-index>]c[-p <port-num>] [-o <out-dir>]
[-lw <1x|4x|12x>] [-ls <2.5|5|10>][-pm] [-pc] [-P <<PM counter>=<Trash Limit>>]