1
2SMCSS(8) Linux Programmer's Manual SMCSS(8)
3
4
5
7 smcss - print information about the AF_SMC sockets and link groups
8
9
11 smcss [--debug|-d] [--smcd|-D] [--wide|-W]
12
13 smcss {--all|-a} [--debug|-d] [--smcd|-D] [--wide|-W]
14
15 smcss [--debug|-d] [--smcr|-R] [--wide|-W]
16
17 smcss {--all|-a} [--debug|-d] [--smcr|-R] [--wide|-W]
18
19 smcss {--listening|-l} [--wide|-W]
20
21 smcss {--version|-v}
22
23 smcss {--help|-h}
24
25
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
31 (none)
32 displays a list of connecting, closing, or connected SMC sockets
33 with basic information.
34
35
36 -a, --all
37 displays all types of SMC sockets: listening, opening, closing,
38 and connected.
39
40
41 -l, --listening
42 shows listening sockets only. These are omitted by default.
43
44
46 -d, --debug
47 displays additional debug information, such as shutdown state.
48
49
50 -D, --smcd
51 displays additional SMC-D specific information. Shows SMC-D
52 sockets only.
53
54
55 -h, --help
56 displays usage information.
57
58
59 -R, --smcr
60 displays additional SMC-R specific information. Shows SMC-R
61 sockets only.
62
63
64 -v, --version
65 displays program version.
66
67
68 -W, --wide
69 do not truncate IP addresses.
70
71
73 State
74 The state of the socket. The state can be one of these values:
75
76 INIT The SMC socket is being initialized. It is not connected nor
77 listening yet.
78
79 CLOSED The SMC socket is closed. It is not connected nor listening any‐
80 more.
81
82 LISTEN The SMC socket is a listening socket, waiting for incoming con‐
83 nection requests.
84
85 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
89 PEERCLW1
90 No further data will be sent to the peer.
91
92 PEERCLW2
93 No further data will be sent to or received from the peer.
94
95 APPLCLW1
96 No further data will be received from the peer.
97
98 APPLCLW2
99 No further data will be received from or sent to the peer.
100
101 APPLFINCLW
102 The peer has closed the socket.
103
104 PEERFINCLW
105 The socket is closed locally.
106
107 PEERABORTW
108 The socket was abnormally closed locally.
109
110 PROCESSABORT
111 The peer has closed the socket abnormally.
112
113 UID
114 User ID of the SMC socket.
115
116 Inode
117 Inode attribute of the socket.
118
119 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
124 Peer Address
125 Address and port number of the remote end of the socket. Analogous to
126 "Local Address".
127
128 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
133 Mode
134 SMCD The SMC socket uses SMC-D for data exchange.
135
136 SMCR The SMC socket uses SMC-R for data exchange.
137
138 TCP The SMC socket uses the TCP protocol for data exchange, because
139 an SMC connection could not be established.
140
141 In case of an error during connection setup, respective error codes
142 will be displayed in the format <local>/<remote>.
143
144 Linux error codes:
145
146 0x01010000 Out of memory
147
148 0x02010000 Timeout while waiting for confirm link message over RDMA
149 device
150
151 0x02020000 Timeout while waiting for RDMA device to be added
152
153 0x03000000 Configuration error
154
155 0x03010000 Peer does not support SMC
156
157 0x03020000 Connection uses IPsec
158
159 0x03030000 No SMC devices found (R and D)
160
161 0x03030001 No ISM device for SMC-D found
162
163 0x03030002 No RDMA device for SMC-R found
164
165 0x03030003 Hardware has no ISMv2 support
166
167 0x03030004 Peer sent no SMCv2 extension
168
169 0x03030005 Peer sent no SMC-Dv2 extension
170
171 0x03030006 Peer sent no ISMv2 SEID
172
173 0x03030007 No SMC-Dv2 device found, but required
174
175 0x03040000 SMC modes mismatch (R or D)
176
177 0x03050000 Peer has eyecatcher in RMBE
178
179 0x03060000 Fastopen sockopt not supported
180
181 0x03070000 IP prefix / subnet mismatch
182
183 0x03080000 Error retrieving VLAN ID of IP device
184
185 0x03090000 Error while registering VLAN ID on ISM device
186
187 0x030a0000 No active SMC-R link in link group
188
189 0x030b0000 SMC-R link from server not found
190
191 0x030c0000 SMC version mismatch
192
193 0x030d0000 SMC-D connection limit reached
194
195 0x04000000 Synchronization error
196
197 0x05000000 Peer declined during handshake
198
199 0x09990000 Internal error
200
201 0x09990001 rtoken handling failed
202
203 0x09990002 RDMA link failed
204
205 0x09990003 RMB registration failed
206
207
208 ShutD
209 <-> The SMC socket has not been shut down.
210
211 R-> The SMC socket is shut down one-way and cannot receive data.
212
213 <-W The SMC socket is shut down one-way and cannot send data.
214
215 R-W The SMC socket is shut down in both ways and cannot receive or
216 send data.
217
218 Token
219 Unique ID of the SMC socket connection.
220
221 Sndbuf
222 Size of the to-be-sent window of the SMC socket connection.
223
224 Rcvbuf
225 Size of the receiving window of the SMC socket connection (filled by
226 peer).
227
228 Peerbuf
229 Size of the peer receiving window of the SMC socket connection (to fill
230 during RDMA-transfer).
231
232 rxprod-Cursor
233 Describes the current cursor location of the "Rcvbuf" for data to be
234 received from the peer.
235
236 rxcons-Cursor
237 Describes the current cursor location of the "Peerbuf" for data sent to
238 peer and confirmed by the peer.
239
240 rxFlags
241 SMC socket connection flags set by and received from the peer.
242
243 txprod-Cursor
244 Describes the current cursor location of the "Peerbuf" for data sent to
245 peer.
246
247 txcons-Cursor
248 Describes the current cursor location of the "Rcvbuf" for data received
249 from the peer and confirmed to the peer.
250
251 txFlags
252 SMC socket connection flags set locally and sent to the peer.
253
254 txprep-Cursor
255 Describes the current cursor location of the "Sndbuf" for data to be
256 sent. The data is to be moved to the "Peerbuf".
257
258 txsent-Cursor
259 Describes the current cursor location of the "Sndbuf" for data sent.
260 The data was moved to the "Peerbuf".
261
262 txfin-Cursor
263 Describes the current cursor location of the "Sndbuf" for data sent and
264 send completion confirmed. The data was moved to the "Peerbuf" and
265 completion was confirmed.
266
267 Role
268 CLNT The link group of the SMC socket is used for client connections.
269
270 SERV The link group of the SMC socket is used for server connections.
271
272 IB-Device
273 Name of the RoCE device used by the link group to which the SMC socket
274 belongs.
275
276 Port
277 Port of the RoCE device used by the link group to which the SMC socket
278 belongs.
279
280 Linkid
281 Unique link ID of the link within the link group to which the SMC
282 socket belongs.
283
284 GID
285 Gid of the RoCE port used by the link group to which the SMC socket be‐
286 longs.
287
288 Peer-GID
289 Gid of the Foreign RoCE port used by the link group to which the SMC
290 socket belongs.
291
292 VLAN
293 tbd.
294
296 Successful smcss commands return 0 and display the requested socket
297 state table or link group information. If an error occurs, smcss
298 writes a message to stderr and completes with a return code other than
299 0.
300
302 af_smc(7), smc_chk(8) smc_rnics(8), smc_run(8), smc_pnet(8), smcd(8),
303 smcr(8)
304
305
306
307
308smc-tools June 2018 SMCSS(8)