infiniband-diags(8) - Linux man page

Synopsis

Description

infiniband-diags is a set of utilities designed to help configure, debug, and maintain infiniband fabrics. Many tools and utilities are provided. Some with similar functionality.

The base utilities use directed route MAD's to perform their operations. They may therefore work even in unconfigured subnets. Other, higher level utilities, require LID routed MAD's and to some extent SA/SM access.

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:

1. the first port that is ACTIVE.

2. if not found, the first port that is UP (physical link up).

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:

ibaddr # use the 'best port'

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.

Common Options

Most OpenIB diagnostics take the following common flags. The exact list of supported flags per utility can be found in the usage message and can be shown using "<util_name> -h".

# Addressing Flags

-D use the directed route specified.
Examples:

"0" # self port

"0,1,2,1,4" # out via port 1, then 2, ...

-G <guid> use the PortGuid specified.

-s <smlid> use 'smlid' as the target lid for SA queries.

# Local HCA/port flags:

-C <ca_name> use the specified ca_name.

-P <ca_port> use the specified ca_port.

# Debugging flags

-t <timeout_ms> override the default timeout for the solicited mads.

-d raise the IB debugging level. May be used several times (-ddd or -d -d -d).

-e show send and receive errors (timeouts and others)

-h show the usage message

-v increase the application verbosity level. May be used several times (-vv or -v -v -v)

-V show the version info.

Node Name Map File Format

Generically:

# comment
<guid> "<name>"

Example:

# 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"

Utilities list

Basic fabric conectivity

See: ibnetdiscover, iblinkinfo, ibidsverify

Node information

See: ibnodes, ibswitches, ibhosts, ibrouters

Port information

See: ibportstate, ibaddr

Switch Forwarding Table info

See: ibtracert, ibroute, dump_lfts, dump_mfts, check_lft_balance, ibfindnodesusing

Peformance counters

See: ibqueryerrors, perfquery

Local HCA info

See: ibstat, ibstatus,

Connectivity check

See: ibping, ibsysstat

Low level query tools

See: smpquery, smpdump, saquery, sminfo

Backwards compatibility scripts

The following scripts have been identified as redundant and/or lower performing as compared to the above scripts. They are provided as legacy scripts.

ibcheckerrors, ibclearcounters, ibclearerrors, ibdatacounters ibchecknet, ibchecknode, ibcheckport, ibcheckportstate, ibcheckportwidth, ibcheckstate, ibcheckwidth, ibswportwatch, ibprintca, ibprintrt, ibprintswitch

Authors

Ira Weiny

<weiny2@llnl.gov>