User Manual
Table Of Contents
- Mellanox WinOF VPI User Manual
- Table of Contents
- List of Tables
- Document Revision History
- About this Manual
- 1 Introduction
- 2 Firmware Upgrade
- 3 Driver Features
- 3.1 Hyper-V with VMQ
- 3.2 Header Data Split
- 3.3 Receive Side Scaling (RSS)
- 3.4 Port Configuration
- 3.5 Load Balancing, Fail-Over (LBFO) and VLAN
- 3.6 Ports TX Arbitration
- 3.7 RDMA over Converged Ethernet (RoCE)
- 3.8 Network Virtualization using Generic Routing Encapsulation
- 3.9 Differentiated Services Code Point (DSCP)
- 4 Deploying Windows Server 2012 and Above with SMB Direct
- 5 Driver Configuration
- 6 Performance Tuning
- 7 OpenSM - Subnet Manager
- 8 InfiniBand Fabric
- 8.1 Network Direct Interface
- 8.2 part_man - Virtual IPoIB Port Creation Utility
- 8.3 InfiniBand Fabric Diagnostic Utilities
- 8.3.1 Utilities Usage
- 8.3.2 ibdiagnet
- 8.3.3 ibportstate
- 8.3.4 ibroute
- 8.3.5 ibdump
- 8.3.6 smpquery
- 8.3.7 perfquery
- 8.3.8 ibping
- 8.3.9 ibnetdiscover
- 8.3.10 ibtracert
- 8.3.11 sminfo
- 8.3.12 ibclearerrors
- 8.3.13 ibstat
- 8.3.14 vstat
- 8.3.15 osmtest
- 8.3.16 ibaddr
- 8.3.17 ibcacheedit
- 8.3.18 iblinkinfo
- 8.3.19 ibqueryerrors
- 8.3.20 ibsysstat
- 8.3.21 saquery
- 8.3.22 smpdump
- 8.4 InfiniBand Fabric Performance Utilities
- 8.4.1 ib_read_bw
- 8.4.2 ib_read_lat
- 8.4.3 ib_send_bw
- 8.4.4 ib_send_lat
- 8.4.5 ib_write_bw
- 8.4.6 ib_write_lat
- 8.4.7 ibv_read_bw
- 8.4.8 ibv_read_lat
- 8.4.9 ibv_send_bw
- 8.4.10 ibv_send_lat
- 8.4.11 ibv_write_bw
- 8.4.12 ibv_write_lat
- 8.4.13 nd_write_bw
- 8.4.14 nd_write_lat
- 8.4.15 nd_read_bw
- 8.4.16 nd_read_lat
- 8.4.17 nd_send_bw
- 8.4.18 nd_send_lat
- 8.4.19 NTttcp
- 9 Software Development Kit
- 10 Troubleshooting
- 11 Documentation
- Appendix A: Windows MPI (MS-MPI)
- Appendix B: NVGRE Configuration Scrips Examples
Rev 4.60
Mellanox Technologies
64
8.3.2.2 ibdiagnet Output Files
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
Table 11 - ibdiagnet Output Files
Output File Description
ibdiagnet.log A dump of all the application reports generate according to the provided flags
ibdiagnet.lst List of all the nodes, ports and links in the fabric
ibdiagnet.fdbs A dump of the unicast forwarding tables of the fabric switches
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 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.