1SMCSS(8) Linux Programmer's Manual SMCSS(8)
3
7 smcss - print information about the AF_SMC sockets and link groups
8
11 smcss [--debug|-d] [--smcd|-D] [--wide|-W]
12 smcss {--all|-a} [--debug|-d] [--smcd|-D] [--wide|-W]
14 smcss [--debug|-d] [--smcr|-R] [--wide|-W]
16 smcss {--all|-a} [--debug|-d] [--smcr|-R] [--wide|-W]
18 smcss {--listening|-l} [--wide|-W]
20 smcss {--version|-v}
22 smcss {--help|-h}
24
27 smcss prints information about the Linux AF_SMC sockets and link
28 groups. The type of information printed is controlled by the first ar‐
29 gument, as follows:
30 (none)
32 displays a list of connecting, closing, or connected SMC sockets
33 with basic information.
34 -a, --all
37 displays all types of SMC sockets: listening, opening, closing,
38 and connected.
39 -l, --listening
42 shows listening sockets only. These are omitted by default.
43
46 -d, --debug
47 displays additional debug information, such as shutdown state.
48 -D, --smcd
51 displays additional SMC-D specific information. Shows SMC-D
52 sockets only.
53 -h, --help
56 displays usage information.
57 -R, --smcr
60 displays additional SMC-R specific information. Shows SMC-R
61 sockets only.
62 -v, --version
65 displays program version.
66 -W, --wide
69 do not truncate IP addresses.
70
73 State
74 The state of the socket. The state can be one of these values:
75 INIT The SMC socket is being initialized. It is not connected nor
77 listening yet.
78 CLOSED The SMC socket is closed. It is not connected nor listening any‐
80 more.
81 LISTEN The SMC socket is a listening socket, waiting for incoming con‐
83 nection requests.
84 ACTIVE The SMC socket has an established connection. In this state,
86 the TCP connection is fully established, rendezvous processing
87 has been completed, and SMC peers can exchange data via RDMA.
88 PEERCLW1
90 No further data will be sent to the peer.
91 PEERCLW2
93 No further data will be sent to or received from the peer.
94 APPLCLW1
96 No further data will be received from the peer.
97 APPLCLW2
99 No further data will be received from or sent to the peer.
100 APPLFINCLW
102 The peer has closed the socket.
103 PEERFINCLW
105 The socket is closed locally.
106 PEERABORTW
108 The socket was abnormally closed locally.
109 PROCESSABORT
111 The peer has closed the socket abnormally.
112 UID
114 User ID of the SMC socket.
115 Inode
117 Inode attribute of the socket.
118 Local Address
120 Address and port number of the local end of the SMC socket. The dis‐
121 played address is truncated when it ends with '..'. -W, --wide can be
122 used to display addresses untruncated.
123 Peer Address
125 Address and port number of the remote end of the socket. Analogous to
126 "Local Address".
127 Intf
129 When the socket is explicitly bound with setsockopt option SO_BINDTODE‐
130 VICE then Intf shows the interface number of the Ethernet device to
131 which the socket is bound.
132 Mode
134 SMCD The SMC socket uses SMC-D for data exchange.
135 SMCR The SMC socket uses SMC-R for data exchange.
137 TCP The SMC socket uses the TCP protocol for data exchange, because
139 an SMC connection could not be established.
140 In case of an error during connection setup, respective error codes
142 will be displayed in the format <local>/<remote>.
143 Linux error codes:
145 0x01010000 Out of memory
147 0x02010000 Timeout while waiting for confirm link message over RDMA
149 device
150 0x02020000 Timeout while waiting for RDMA device to be added
152 0x03000000 Configuration error
154 0x03010000 Peer does not support SMC
156 0x03020000 Connection uses IPsec
158 0x03030000 No SMC devices found (R and D)
160 0x03030001 No ISM device for SMC-D found
162 0x03030002 No RDMA device for SMC-R found
164 0x03030003 Hardware has no ISMv2 support
166 0x03030004 Peer sent no SMCv2 extension
168 0x03030005 Peer sent no SMC-Dv2 extension
170 0x03030006 Peer sent no ISMv2 SEID
172 0x03030007 No SMC-Dv2 device found, but required
174 0x03030008 Peer sent no UEID
176 0x03040000 SMC modes mismatch (R or D)
178 0x03050000 Peer has eyecatcher in RMBE
180 0x03060000 Fastopen sockopt not supported
182 0x03070000 IP prefix / subnet mismatch
184 0x03080000 Error retrieving VLAN ID of IP device
186 0x03090000 Error while registering VLAN ID on ISM device
188 0x030a0000 No active SMC-R link in link group
190 0x030b0000 SMC-R link from server not found
192 0x030c0000 SMC version mismatch
194 0x030d0000 SMC-D connection limit reached
196 0x030e0000
199 SMC-Rv2 connection found no route to peer
200 0x030f0000 SMC-Rv2 connection mismatch direct/indirect with peer
202 0x04000000 Synchronization error
203 0x05000000 Peer declined during handshake
205 0x09990000 Internal error
207 0x09990001 rtoken handling failed
209 0x09990002 RDMA link failed
211 0x09990003 RMB registration failed
213 ShutD
216 <-> The SMC socket has not been shut down.
217 R-> The SMC socket is shut down one-way and cannot receive data.
219 <-W The SMC socket is shut down one-way and cannot send data.
221 R-W The SMC socket is shut down in both ways and cannot receive or
223 send data.
224 Token
226 Unique ID of the SMC socket connection.
227 Sndbuf
229 Size of the to-be-sent window of the SMC socket connection.
230 Rcvbuf
232 Size of the receiving window of the SMC socket connection (filled by
233 peer).
234 Peerbuf
236 Size of the peer receiving window of the SMC socket connection (to fill
237 during RDMA-transfer).
238 rxprod-Cursor
240 Describes the current cursor location of the "Rcvbuf" for data to be
241 received from the peer.
242 rxcons-Cursor
244 Describes the current cursor location of the "Peerbuf" for data sent to
245 peer and confirmed by the peer.
246 rxFlags
248 SMC socket connection flags set by and received from the peer.
249 txprod-Cursor
251 Describes the current cursor location of the "Peerbuf" for data sent to
252 peer.
253 txcons-Cursor
255 Describes the current cursor location of the "Rcvbuf" for data received
256 from the peer and confirmed to the peer.
257 txFlags
259 SMC socket connection flags set locally and sent to the peer.
260 txprep-Cursor
262 Describes the current cursor location of the "Sndbuf" for data to be
263 sent. The data is to be moved to the "Peerbuf".
264 txsent-Cursor
266 Describes the current cursor location of the "Sndbuf" for data sent.
267 The data was moved to the "Peerbuf".
268 txfin-Cursor
270 Describes the current cursor location of the "Sndbuf" for data sent and
271 send completion confirmed. The data was moved to the "Peerbuf" and
272 completion was confirmed.
273 Role
275 CLNT The link group of the SMC socket is used for client connections.
276 SERV The link group of the SMC socket is used for server connections.
278 IB-Device
280 Name of the RoCE device used by the link group to which the SMC socket
281 belongs.
282 Port
284 Port of the RoCE device used by the link group to which the SMC socket
285 belongs.
286 Linkid
288 Unique link ID of the link within the link group to which the SMC
289 socket belongs.
290 GID
292 Gid of the RoCE port used by the link group to which the SMC socket be‐
293 longs.
294 Peer-GID
296 Gid of the Foreign RoCE port used by the link group to which the SMC
297 socket belongs.
298 VLAN
300 tbd.
301
303 Successful smcss commands return 0 and display the requested socket
304 state table or link group information. If an error occurs, smcss
305 writes a message to stderr and completes with a return code other than
306 0.
307
309 af_smc(7), smc_chk(8) smc_rnics(8), smc_run(8), smc_pnet(8), smcd(8),
310 smcr(8)
311smc-tools June 2018 SMCSS(8)