1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
|
nvme-connect(1)
===============
NAME
----
nvme-connect - Connect to a Fabrics controller.
SYNOPSIS
--------
[verse]
'nvme connect'
[--transport=<trtype> | -t <trtype>]
[--nqn=<subnqn> | -n <subnqn>]
[--traddr=<traddr> | -a <traddr>]
[--trsvcid=<trsvcid> | -s <trsvcid>]
[--host-traddr=<traddr> | -w <traddr>]
[--host-iface=<iface> | -f <iface>]
[--hostnqn=<hostnqn> | -q <hostnqn>]
[--hostid=<hostid> | -I <hostid>]
[--config-file=<cfg> | -J <cfg> ]
[--dhchap-secret=<secret> | -S <secret>]
[--dhchap-ctrl-secret=<secret> | -C <secret>]
[--nr-io-queues=<#> | -i <#>]
[--nr-write-queues=<#> | -W <#>]
[--nr-poll-queues=<#> | -P <#>]
[--queue-size=<#> | -Q <#>]
[--keep-alive-tmo=<#> | -k <#>]
[--reconnect-delay=<#> | -c <#>]
[--ctrl-loss-tmo=<#> | -l <#>]
[--tos=<#> | -T <#>]
[--keyring=<#> ]
[--tls_key=<#> ]
[--duplicate-connect | -D]
[--disable-sqflow | -d]
[--hdr-digest | -g]
[--data-digest | -G]
[--tls ]
[--dump-config | -O]
[--output-format=<fmt> | -o <fmt>]
DESCRIPTION
-----------
Create a transport connection to a remote system (specified by --traddr and
--trsvcid) and create a NVMe over Fabrics controller for the NVMe subsystem
specified by the --nqn option.
OPTIONS
-------
-t <trtype>::
--transport=<trtype>::
This field specifies the network fabric being used for
a NVMe-over-Fabrics network. Current string values include:
+
[]
|=================
|Value|Definition
|rdma|The network fabric is an rdma network (RoCE, iWARP, Infiniband, basic rdma, etc)
|fc |*WIP* The network fabric is a Fibre Channel network.
|tcp |The network fabric is a TCP/IP network.
|loop|Connect to a NVMe over Fabrics target on the local host
|=================
-n <subnqn>::
--nqn <subnqn>::
This field specifies the name for the NVMe subsystem to connect to.
-a <traddr>::
--traddr=<traddr>::
This field specifies the network address of the Controller.
For transports using IP addressing (e.g. rdma) this should be an
IP-based address (ex. IPv4).
-s <trsvcid>::
--trsvcid=<trsvcid>::
This field specifies the transport service id. For transports using IP
addressing (e.g. rdma) this field is the port number. By default, the IP
port number for the RDMA transport is 4420.
-w <traddr>::
--host-traddr=<traddr>::
This field specifies the network address used on the host to connect
to the Controller. For TCP, this sets the source address on the socket.
-f <iface>::
--host-iface=<iface>::
This field specifies the network interface used on the host to connect
to the Controller (e.g. IP eth1, enp2s0, enx78e7d1ea46da). This forces
the connection to be made on a specific interface instead of letting
the system decide.
-q <hostnqn>::
--hostnqn=<hostnqn>::
Overrides the default Host NQN that identifies the NVMe Host.
If this option is not specified, the default is read from
@SYSCONFDIR@/nvme/hostnqn first. If that does not exist, the autogenerated
NQN value from the NVMe Host kernel module is used next.
The Host NQN uniquely identifies the NVMe Host.
-I <hostid>::
--hostid=<hostid>::
UUID(Universally Unique Identifier) to be discovered which should be
formatted.
-J <cfg>::
--config-file=<cfg>::
Use the specified JSON configuration file instead of the
default @SYSCONFDIR@/nvme/config.json file or 'none' to not read in
an existing configuration file. The JSON configuration file
format is documented in
https://github.com/linux-nvme/libnvme/doc/config-schema.json
-S <secret>::
--dhchap-secret=<secret>::
NVMe In-band authentication secret; needs to be in ASCII format as
specified in NVMe 2.0 section 8.13.5.8 'Secret representation'.
If this option is not specified, the default is read from
@SYSCONFDIR@/nvme/hostkey. If that does not exist no in-band authentication
is attempted.
-C <secret>::
--dhchap-ctrl-secret=<secret>::
NVMe In-band authentication controller secret for bi-directional
authentication; needs to be in ASCII format as
specified in NVMe 2.0 section 8.13.5.8 'Secret representation'.
If not present bi-directional authentication is not attempted.
-i <#>::
--nr-io-queues=<#>::
Overrides the default number of I/O queues create by the driver.
-W <#>::
--nr-write-queues=<#>::
Adds additional queues that will be used for write I/O.
-P <#>::
--nr-poll-queues=<#>::
Adds additional queues that will be used for polling latency sensitive I/O.
-Q <#>::
--queue-size=<#>::
Overrides the default number of elements in the I/O queues created
by the driver.
-k <#>::
--keep-alive-tmo=<#>::
Overrides the default keep alive timeout (in seconds).
-c <#>::
--reconnect-delay=<#>::
Overrides the default delay (in seconds) before reconnect is attempted
after a connect loss.
-l <#>::
--ctrl-loss-tmo=<#>::
Overrides the default controller loss timeout period (in seconds).
-T <#>::
--tos=<#>::
Type of service for the connection (TCP)
--keyring=<#>::
Keyring for TLS key lookup.
--tls_key=<#>::
TLS key for the connection (TCP).
-D::
--duplicate-connect::
Allows duplicated connections between same transport host and subsystem
port.
-d::
--disable-sqflow::
Disables SQ flow control to omit head doorbell update for submission
queues when sending nvme completions.
-g::
--hdr-digest::
Generates/verifies header digest (TCP).
-G::
--data-digest::
Generates/verifies data digest (TCP).
--tls::
Enable TLS encryption (TCP).
-O::
--dump-config::
Print out resulting JSON configuration file to stdout.
-o <format>::
--output-format=<format>::
Set the reporting format to 'normal' or 'json'. Only one output format can
be used at a time. When this option is specified, the device associated with
the connection will be printed. Nothing is printed otherwise.
EXAMPLES
--------
* Connect to a subsystem named nqn.2014-08.com.example:nvme:nvm-subsystem-sn-d78432
on the IP4 address 192.168.1.3. Port 4420 is used by default:
+
------------
# nvme connect --transport=rdma --traddr=192.168.1.3 \
--nqn=nqn.2014-08.com.example:nvme:nvm-subsystem-sn-d78432
------------
SEE ALSO
--------
nvme-discover(1)
nvme-connect-all(1)
AUTHORS
-------
This was co-written by mailto:james.p.freyensee@intel.com[Jay Freyensee]
and mailto:hch@lst.de[Christoph Hellwig]
NVME
----
Part of the nvme-user suite
|
