1IBLINKINFO(8) OpenIB Diagnostics IBLINKINFO(8)
2
6 IBLINKINFO - report link info for all links in the fabric
7
9 iblinkinfo <options>
10
12 iblinkinfo reports link info for each port in an IB fabric, node by
13 node. Optionally, iblinkinfo can do partial scans and limit its output
14 to parts of a fabric.
15
17 --down, -d Print only nodes which have a port in the "Down" state.
18 --line, -l Print all information for each link on one line. Default is
20 to print a header with the node information and then a list for each
21 port (useful for grep'ing output).
22 --additional, -p Print additional port settings (<Life‐
24 Time>,<HoqLife>,<VLStallCount>)
25 --switches-only Show only switches in output.
27 --cas-only Show only CAs in output.
29 Partial Scan flags
31 The node to start a partial scan can be specified with the following
32 addresses.
33 --port-guid, -G <port_guid> Specify a port_guid
35 -D, --Direct <dr_path> The address specified is a directed route
37 Examples:
39 -D "0" # self port
40 -D "0,1,2,1,4" # out via port 1, then 2, ...
41 (Note the second number in the path specified must match the port being
43 used. This can be specified using the port selection flag '-P' or the
44 port found through the automatic selection process.)
45 Note: For switches results are printed for all ports not just switch
47 port 0.
48 --switch, -S <port_guid> same as "-G". (provided only for backward com‐
50 patibility)
51 How much of the scan to be printed can be controlled with the follow‐
53 ing.
54 --all, -a Print all nodes found in a partial fabric scan. Normally a
56 partial fabric scan will return only the node specified. This option
57 will print the other nodes found as well.
58 --hops, -n <hops> Specify the number of hops away from a specified node
60 to scan. This is useful to expand a partial fabric scan beyond the
61 node specified.
62 Cache File flags
64 --load-cache <filename> Load and use the cached ibnetdiscover data
65 stored in the specified filename. May be useful for outputting and
66 learning about other fabrics or a previous state of a fabric.
67 --diff <filename> Load cached ibnetdiscover data and do a diff compari‐
69 son to the current network or another cache. A special diff output for
70 ibnetdiscover output will be displayed showing differences between the
71 old and current fabric. By default, the following are compared for
72 differences: switches, channel adapters, routers, and port connections.
73 --diffcheck <key(s)> Specify what diff checks should be done in the
75 --diff option above. Comma separate multiple diff check key(s). The
76 available diff checks are: port = port connections, state = port state,
77 lid = lids, nodedesc = node descriptions. Note that port, lid, and
78 nodedesc are checked only for the node types that are specified (e.g.
79 switches-only, cas-only). If port is specified alongside lid or nod‐
80 edesc, remote port lids and node descriptions will also be compared.
81 --filterdownports <filename> Filter downports indicated in a ibnetdis‐
83 cover cache. If a port was previously indicated as down in the speci‐
84 fied cache, and is still down, do not output it in the resulting out‐
85 put. This option may be particularly useful for environments where
86 switches are not fully populated, thus much of the default iblinkinfo
87 info is considered useless. See ibnetdiscover for information on
88 caching ibnetdiscover output.
89 Port Selection flags
91 -C, --Ca <ca_name> use the specified ca_name.
92 -P, --Port <ca_port> use the specified ca_port.
94 Local port Selection
96 Multiple port/Multiple CA support: when no IB device or port is speci‐
97 fied (see the "local umad parameters" below), the libibumad library
98 selects the port to use by the following criteria:
99 1. the first port that is ACTIVE.
101 2. if not found, the first port that is UP (physical link up).
103 If a port and/or CA name is specified, the libibumad library
105 attempts to fulfill the user request, and will fail if it is not
106 possible.
107 For example:
109 ibaddr # use the first port (criteria #1 above)
111 ibaddr -C mthca1 # pick the best port from "mthca1" only.
112 ibaddr -P 2 # use the second (active/up) port from the first available IB device.
113 ibaddr -C mthca0 -P 2 # use the specified port only.
114 Configuration flags
116 --config, -z <config_file> Specify alternate config file.
117 Default: /etc/infiniband-diags/ibdiag.conf
118 --outstanding_smps, -o <val>
120 Specify the number of outstanding SMP's which should be issued
121 during the scan
122 Default: 2
124 --node-name-map <node-name-map> Specify a node name map.
126 This file maps GUIDs to more user friendly names. See FILES sec‐
127 tion.
128 -t, --timeout <timeout_ms> override the default timeout for the
130 solicited mads.
131 -y, --m_key <key>
133 use the specified M_key for requests. If non-numeric value (like
134 'x') is specified then a value will be prompted for.
135 Debugging flags
137 -e show send and receive errors (timeouts and others)
138 -h, --help show the usage message
140 -v, --verbose
142 increase the application verbosity level. May be used several
143 times (-vv or -v -v -v)
144 -V, --version show the version info.
146
148 0 on success, -1 on failure to scan the fabric, 1 if check mode is used
149 and inconsistencies are found.
150
152 CONFIG FILE
153 /etc/infiniband-diags/ibdiag.conf
154 A global config file is provided to set some of the common options for
156 all tools. See supplied config file for details.
157 NODE NAME MAP FILE FORMAT
159 The node name map is used to specify user friendly names for nodes in
160 the output. GUIDs are used to perform the lookup.
161 This functionality is provided by the opensm-libs package. See
163 opensm(8) for the file location for your installation.
164 Generically:
166 # comment
168 <guid> "<name>"
169 Example:
171 # IB1
173 # Line cards
174 0x0008f104003f125c "IB1 (Rack 11 slot 1 ) ISR9288/ISR9096 Voltaire sLB-24D"
175 0x0008f104003f125d "IB1 (Rack 11 slot 1 ) ISR9288/ISR9096 Voltaire sLB-24D"
176 0x0008f104003f10d2 "IB1 (Rack 11 slot 2 ) ISR9288/ISR9096 Voltaire sLB-24D"
177 0x0008f104003f10d3 "IB1 (Rack 11 slot 2 ) ISR9288/ISR9096 Voltaire sLB-24D"
178 0x0008f104003f10bf "IB1 (Rack 11 slot 12 ) ISR9288/ISR9096 Voltaire sLB-24D"
179 # Spines
181 0x0008f10400400e2d "IB1 (Rack 11 spine 1 ) ISR9288 Voltaire sFB-12D"
182 0x0008f10400400e2e "IB1 (Rack 11 spine 1 ) ISR9288 Voltaire sFB-12D"
183 0x0008f10400400e2f "IB1 (Rack 11 spine 1 ) ISR9288 Voltaire sFB-12D"
184 0x0008f10400400e31 "IB1 (Rack 11 spine 2 ) ISR9288 Voltaire sFB-12D"
185 0x0008f10400400e32 "IB1 (Rack 11 spine 2 ) ISR9288 Voltaire sFB-12D"
186 # GUID Node Name
188 0x0008f10400411a08 "SW1 (Rack 3) ISR9024 Voltaire 9024D"
189 0x0008f10400411a28 "SW2 (Rack 3) ISR9024 Voltaire 9024D"
190 0x0008f10400411a34 "SW3 (Rack 3) ISR9024 Voltaire 9024D"
191 0x0008f104004119d0 "SW4 (Rack 3) ISR9024 Voltaire 9024D"
192
194 Ira Weiny
195 < ira.weiny@intel.com >
196 2018-07-09 IBLINKINFO(8)