User Manual

Rev 2.3-1.0.1
Mellanox Technologies
195
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 que
-
ries 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.
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.
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.
ibdiagpath is located at: /opt/ibutisl/bin.
For further information, please refer to the tool’s man page.
ibdump Dump InfiniBand traffic that flows to and from Mellanox Technologies Con-
nectX® family adapters InfiniBand ports. The dump file can be loaded by the
Wireshark tool for graphical traffic analysis.
The following describes a work flow for local HCA (adapter) sniffing:
1. Run ibdump with the desired options
2. Run the application that you wish its traffic to be analyzed
3. Stop ibdump (CTRL-C) or wait for the data buffer to fill (in --mem-mode)
4. Open Wireshark and load the generated file
To download Wireshark for a Linux or Windows environment go to www.wire-
shark.org.
Note: Although ibdump is a Linux application, the generated .pcap file may
be analyzed on either operating system.
In order for ibdump to function with RoCE, Flow Steering must be enabled.
To do so:
1. Add the following to /etc/modprobe.d/mlnx.conf file:
options mlx4_core log_num_mgm_entry_size=-1
2. Restart the drivers.
For further information, please refer to the tool’s man page.
Table 7 - Diagnostic Utilities (Sheet 3 of 6)
Utility Description