Man page generated from reStructuredText.
. IBQUERYERRORS - query and report IB port counters . .nr rst2man-indent-level 0 . \\$1 \\n[an-margin] level \\n[rst2man-indent-level] level margin: \\n[rst2man-indent\\n[rst2man-indent-level]] - \\n[rst2man-indent0] \\n[rst2man-indent1] \\n[rst2man-indent2] .. .rstReportMargin pre:
. RS \\$1 . nr rst2man-indent\\n[rst2man-indent-level] \\n[an-margin] . nr rst2man-indent-level +1 .rstReportMargin post:
.. . RE indent \\n[an-margin]
old: \\n[rst2man-indent\\n[rst2man-indent-level]]
.nr rst2man-indent-level -1 new: \\n[rst2man-indent\\n[rst2man-indent-level]]
.. ibqueryerrors [options] The default behavior is to report the port error counters which exceed a threshold for each port in the fabric. The default threshold is zero (0). Error fields can also be suppressed entirely. In addition to reporting errors on every port. ibqueryerrors can report the port transmit and receive data as well as report full link information to the remote port if available. -s, --suppress <err1,err2,...> Suppress the errors listed in the comma separated list provided. -c, --suppress-common Suppress some of the common "side effect" counters. These counters usually do not indicate an error condition and can be usually be safely ignored. -r, --report-port Report the port information. This includes LID, port, external port (if applicable), link speed setting, remote GUID, remote port, remote external port (if applicable), and remote node description information. --data Include the optional transmit and receive data counters. --threshold-file <filename> Specify an alternate threshold file. The default is /etc/infiniband-diags/error_thresholds --switch print data for switch\(aqs only --ca print data for CA\(aqs only --skip-sl Use the default sl for queries. This is not recommended when using a QoS aware routing engine as it can cause a credit deadlock. --router print data for routers only --clear-errors -k Clear error counters after read. --clear-counts -K Clear data counters after read. CAUTION clearing data or error counters will occur regardless of if they are printed or not. See --counters and --data for details on controling which counters are printed. --details include receive error and transmit discard details --counters print data counters only The node to start a partial scan can be specified with the following addresses. Define the common option -G
. --port-guid, -G <port_guid> Specify a port_guid Define the common option -D for Directed routes
. -D, --Direct <dr_path> The address specified is a directed route NDENT 0.0 NDENT 3.5

Examples:
 -D "0" # self port
 -D "0,1,2,1,4" # out via port 1, then 2, ...

 (Note the second number in the path specified must match the port being
 used. This can be specified using the port selection flag \(aq-P\(aq or the
 port found through the automatic selection process.)

NINDENT NINDENT Note: For switches results are printed for all ports not just switch port 0. -S <port_guid> same as "-G". (provided only for backward compatibility) Define the common option load-cache
. --load-cache <filename> Load and use the cached ibnetdiscover data stored in the specified filename. May be useful for outputting and learning about other fabrics or a previous state of a fabric. Define the common option -C
. -C, --Ca <ca_name> use the specified ca_name. Define the common option -P
. -P, --Port <ca_port> use the specified ca_port. Explanation of local port selection
. Multiple port/Multiple CA support: when no IB device or port is specified (see the "local umad parameters" below), the libibumad library selects the port to use by the following criteria: NDENT 0.0 NDENT 3.5 NDENT 0.0 the first port that is ACTIVE. if not found, the first port that is UP (physical link up). NINDENT If a port and/or CA name is specified, the libibumad library attempts to fulfill the user request, and will fail if it is not possible. For example: NDENT 0.0 NDENT 3.5

ibaddr # use the first port (criteria #1 above)
ibaddr -C mthca1 # pick the best port from "mthca1" only.
ibaddr -P 2 # use the second (active/up) port from the first available IB device.
ibaddr -C mthca0 -P 2 # use the specified port only.

NINDENT NINDENT NINDENT NINDENT Define the common option -z
. --config, -z <config_file> Specify alternate config file. NDENT 0.0 NDENT 3.5 Default: /etc/infiniband-diags/ibdiag.conf NINDENT NINDENT Define the common option -z
. NDENT 0.0

--outstanding_smps, -o <val> Specify the number of outstanding SMP\(aqs which should be issued during the scan Default: 2 NINDENT Define the common option --node-name-map
. --node-name-map <node-name-map> Specify a node name map. NDENT 0.0 NDENT 3.5 This file maps GUIDs to more user friendly names. See FILES section. NINDENT NINDENT Define the common option -t
. -t, --timeout <timeout_ms> override the default timeout for the solicited mads. Define the common option -y
. NDENT 0.0

-y, --m_key <key> use the specified M_key for requests. If non-numeric value (like \(aqx\(aq) is specified then a value will be prompted for. NINDENT

Define the common option -d
. NDENT 0.0

-d raise the IB debugging level. May be used several times (-ddd or -d -d -d). NINDENT Define the common option -e
. NDENT 0.0

-e show send and receive errors (timeouts and others) NINDENT Define the common option -h
. -h, --help show the usage message Define the common option -v
. NDENT 0.0

-v, --verbose increase the application verbosity level. May be used several times (-vv or -v -v -v) NINDENT Define the common option -V
. -V, --version show the version info. -R (This option is obsolete and does nothing)

-1 if scan fails. 0 if scan succeeds without errors beyond thresholds 1 if errors are found beyond thresholds or inconsistencies are found in check mode. /etc/infiniband-diags/error_thresholds Define threshold values for errors. File format is simple "name=val". Comments begin with \(aq#\(aq Example: NDENT 0.0 NDENT 3.5

# Define thresholds for error counters
SymbolErrorCounter=10
LinkErrorRecoveryCounter=10
VL15Dropped=100

NINDENT NINDENT Common text for the config file
. /etc/infiniband-diags/ibdiag.conf A global config file is provided to set some of the common options for all tools. See supplied config file for details. Common text to describe the node name map file.
. The node name map is used to specify user friendly names for nodes in the output. GUIDs are used to perform the lookup. This functionality is provided by the opensm-libs package. See opensm(8) for the file location for your installation. Generically: NDENT 0.0 NDENT 3.5

# comment
<guid> "<name>"

NINDENT NINDENT Example: NDENT 0.0 NDENT 3.5

# IB1
# Line cards
0x0008f104003f125c "IB1 (Rack 11 slot 1 ) ISR9288/ISR9096 Voltaire sLB-24D"
0x0008f104003f125d "IB1 (Rack 11 slot 1 ) ISR9288/ISR9096 Voltaire sLB-24D"
0x0008f104003f10d2 "IB1 (Rack 11 slot 2 ) ISR9288/ISR9096 Voltaire sLB-24D"
0x0008f104003f10d3 "IB1 (Rack 11 slot 2 ) ISR9288/ISR9096 Voltaire sLB-24D"
0x0008f104003f10bf "IB1 (Rack 11 slot 12 ) ISR9288/ISR9096 Voltaire sLB-24D"

# Spines
0x0008f10400400e2d "IB1 (Rack 11 spine 1 ) ISR9288 Voltaire sFB-12D"
0x0008f10400400e2e "IB1 (Rack 11 spine 1 ) ISR9288 Voltaire sFB-12D"
0x0008f10400400e2f "IB1 (Rack 11 spine 1 ) ISR9288 Voltaire sFB-12D"
0x0008f10400400e31 "IB1 (Rack 11 spine 2 ) ISR9288 Voltaire sFB-12D"
0x0008f10400400e32 "IB1 (Rack 11 spine 2 ) ISR9288 Voltaire sFB-12D"

# GUID Node Name
0x0008f10400411a08 "SW1 (Rack 3) ISR9024 Voltaire 9024D"
0x0008f10400411a28 "SW2 (Rack 3) ISR9024 Voltaire 9024D"
0x0008f10400411a34 "SW3 (Rack 3) ISR9024 Voltaire 9024D"
0x0008f104004119d0 "SW4 (Rack 3) ISR9024 Voltaire 9024D"

NINDENT NINDENT NDENT 0.0

Ira Weiny < \%ira.weiny@intel.com > NINDENT Generated by docutils manpage writer.
.