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
29 argument, 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 -R, --smcr
56 displays additional SMC-R specific information. Shows SMC-R
57 sockets only.
58
59
60 -W, --wide
61 do not truncate IP addresses.
62
63
65 State
66 The state of the socket. The state can be one of these values:
67
68 INIT The SMC socket is being initialized. It is not connected nor
69 listening yet.
70
71 CLOSED The SMC socket is closed. It is not connected nor listening any‐
72 more.
73
74 LISTEN The SMC socket is a listening socket, waiting for incoming con‐
75 nection requests.
76
77 ACTIVE The SMC socket has an established connection. In this state,
78 the TCP connection is fully established, rendezvous processing
79 has been completed, and SMC peers can exchange data via RDMA.
80
81 PEERCLW1
82 No further data will be sent to the peer.
83
84 PEERCLW2
85 No further data will be sent to or received from the peer.
86
87 APPLCLW1
88 No further data will be received from the peer.
89
90 APPLCLW2
91 No further data will be received from or sent to the peer.
92
93 APPLFINCLW
94 The peer has closed the socket.
95
96 PEERFINCLW
97 The socket is closed locally.
98
99 PEERABORTW
100 The socket was abnormally closed locally.
101
102 PROCESSABORT
103 The peer has closed the socket abnormally.
104
105 UID
106 User ID of the SMC socket.
107
108 Inode
109 Inode attribute of the socket.
110
111 Local Address
112 Address and port number of the local end of the SMC socket. The dis‐
113 played address is truncated when it ends with '..'. -W, --wide can be
114 used to display addresses untruncated.
115
116 Peer Address
117 Address and port number of the remote end of the socket. Analogous to
118 "Local Address".
119
120 Intf
121 When the socket is explicitly bound with setsockopt option SO_BINDTODE‐
122 VICE then Intf shows the interface number of the Ethernet device to
123 which the socket is bound.
124
125 Mode
126 SMCD The SMC socket uses SMC-D for data exchange.
127
128 SMCR The SMC socket uses SMC-R for data exchange.
129
130 TCP The SMC socket uses the TCP protocol for data exchange, because
131 an SMC connection could not be established.
132
133 In case of an error during connection setup, respective error codes
134 will be displayed in the format <local>/<remote>.
135
136 Linux error codes:
137
138 0x01010000 Out of memory
139
140 0x02010000 Timeout while waiting for confirm link message over RDMA
141 device
142
143 0x02020000 Timeout while waiting for RDMA device to be added
144
145 0x03000000 Configuration error
146
147 0x03010000 Peer does not support SMC
148
149 0x03020000 Connection uses IPsec
150
151 0x03030000 No SMC devices found (R and D)
152
153 0x03030001 No ISM device for SMC-D found
154
155 0x03030002 No RDMA device for SMC-R found
156
157 0x03030003 Peer not reachable through ISM device
158
159 0x03040000 SMC modes mismatch (R or D)
160
161 0x03050000 Peer has eyecatcher in RMBE
162
163 0x03060000 Fastopen sockopt not supported
164
165 0x03070000 IP prefix / subnet mismatch
166
167 0x03080000 Error retrieving VLAN ID of IP device
168
169 0x03090000 Error while registering VLAN ID on ISM device
170
171 0x030a0000 No active SMC-R link in link group
172
173 0x030b0000 SMC-R link from server not found
174
175 0x030c0000 SMC version mismatch
176
177 0x030d0000 SMC-D connection limit reached
178
179 0x04000000 Synchronization error
180
181 0x05000000 Peer declined during handshake
182
183 0x09990000 Internal error
184
185 0x09990001 rtoken handling failed
186
187 0x09990002 RDMA link failed
188
189 0x09990003 RMB registration failed
190
191
192 ShutD
193 <-> The SMC socket has not been shut down.
194
195 R-> The SMC socket is shut down one-way and cannot receive data.
196
197 <-W The SMC socket is shut down one-way and cannot send data.
198
199 R-W The SMC socket is shut down in both ways and cannot receive or
200 send data.
201
202 Token
203 Unique ID of the SMC socket connection.
204
205 Sndbuf
206 Size of the to-be-sent window of the SMC socket connection.
207
208 Rcvbuf
209 Size of the receiving window of the SMC socket connection (filled by
210 peer).
211
212 Peerbuf
213 Size of the peer receiving window of the SMC socket connection (to fill
214 during RDMA-transfer).
215
216 rxprod-Cursor
217 Describes the current cursor location of the "Rcvbuf" for data to be
218 received from the peer.
219
220 rxcons-Cursor
221 Describes the current cursor location of the "Peerbuf" for data sent to
222 peer and confirmed by the peer.
223
224 rxFlags
225 SMC socket connection flags set by and received from the peer.
226
227 txprod-Cursor
228 Describes the current cursor location of the "Peerbuf" for data sent to
229 peer.
230
231 txcons-Cursor
232 Describes the current cursor location of the "Rcvbuf" for data received
233 from the peer and confirmed to the peer.
234
235 txFlags
236 SMC socket connection flags set locally and sent to the peer.
237
238 txprep-Cursor
239 Describes the current cursor location of the "Sndbuf" for data to be
240 sent. The data is to be moved to the "Peerbuf".
241
242 txsent-Cursor
243 Describes the current cursor location of the "Sndbuf" for data sent.
244 The data was moved to the "Peerbuf".
245
246 txfin-Cursor
247 Describes the current cursor location of the "Sndbuf" for data sent and
248 send completion confirmed. The data was moved to the "Peerbuf" and
249 completion was confirmed.
250
251 Role
252 CLNT The link group of the SMC socket is used for client connections.
253
254 SERV The link group of the SMC socket is used for server connections.
255
256 IB-Device
257 Name of the RoCE device used by the link group to which the SMC socket
258 belongs.
259
260 Port
261 Port of the RoCE device used by the link group to which the SMC socket
262 belongs.
263
264 Linkid
265 Unique link ID of the link within the link group to which the SMC
266 socket belongs.
267
268 GID
269 Gid of the RoCE port used by the link group to which the SMC socket
270 belongs.
271
272 Peer-GID
273 Gid of the Foreign RoCE port used by the link group to which the SMC
274 socket belongs.
275
276 VLAN
277 tbd.
278
280 Successful smcss commands return 0 and display the requested socket
281 state table or link group information. If an error occurs, smcss
282 writes a message to stderr and completes with a return code other than
283 0.
284
286 af_smc(7), smc_rnics(8), smc_run(8), smc_pnet(8)
287
288
289
290smc-tools June 2018 SMCSS(8)