| IBDIAGPATH(1) | IB DIAGNOSTIC PACKAGE | IBDIAGPATH(1) |
ibdiagpath - IB diagnostic path
ibdiagpath
{-n <[src-name,]dst-name>|-l <[src-lid,]dst-lid>|-d
<p1,p2,p3,...>}
[-c <count>] [-v] [-t <topo-file>] [-s <sys-name>] [-i
<dev-index>]
[-p <port-num>] [-o <out-dir>] [-lw <1x|4x|12x>] [-ls
<2.5|5|10>] [-pm]
[-pc] [-P <<PM counter>=<Trash Limit>>]
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 traversed path. The way ibdiagpath operates depends on the addressing mode used on the command line. If directed route adressing is used, 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 imployed, 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 those paths. Therefore, the path cannot be predicted as it may change. The tool allows omitting the source node, in which case the local port on the machine running the tool is assumed to be the source. Note: 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, ibdiagpath reports an error. Checks for path validity from partitions, IPoIB and QoS perspectives are also provided.
| 2018-12-14 | IBDIAG 1.0 |