User Manual

InfiniBand FabricRev 4.3
Mellanox Technologies
51
In addition to generating the files above, the discovery phase also checks for duplicate node/port
GUIDs in the IB fabric. If such an error is detected, it is displayed on the standard output. After
the discovery phase is completed, directed route packets are sent multiple times (according to the
-c option) to detect possible problematic paths on which packets may be lost. Such paths are
explored, and a report of the suspected bad links is displayed on the standard output.
After scanning the fabric, if the
-r option is provided, a full report of the fabric qualities is dis-
played. This report includes:
• SM report
• Number of nodes and systems
• Hop-count information: maximal hop-count, an example path, and a hop-count histo-
gram
• All CA-to-CA paths traced
• Credit loop report
• mgid-mlid-HCAs multicast group and report
• Partitions report
• IPoIB report
ibdiag-
net.mcfdbs
A dump of the multicast forwarding tables of the fabric switches
ibdiag-
net.masks
In case of duplicate port/node Guids, these file include the map between masked Guid
and real Guids
ibdiagnet.sm List of all the SM (state and priority) in the fabric
ibdiagnet.pm A dump of the pm Counters values, of the fabric links
ibdiagnet.pkey A dump of the the existing partitions and their member host ports
ibdiagnet.mcg A dump of the multicast groups, their properties and member host ports
ibdiagnet.db A dump of the internal subnet database. This file can be loaded in later runs using the -
load_db option
In case the IB fabric includes only one CA, then CA-to-CA paths are not
reported. Furthermore, if a topology file is provided, ibdiagnet uses the names
defined in it for the output reports.
Table 5 - ibdiagnet (of ibutils) Output Files
Output File Description