Western Digital OpenFlex Data24 DCS0010 User Manual page 82

User Guide
Step 3 : Review the output to locate the subnqn number associated with the device that will be
connected. The following example shows two devices, the In-Band management device, as
well as the device intended for connection.
Discovery Log Number of Records 2, Generation counter 0
=====Discovery Log Entry 0======
trtype:
adrfam:
subtype: nvme subsystem
treq:
portid:
trsvcid: 4420
subnqn:
Management Device)
traddr:
rdma_prtype: roce-v2
rdma_qptype: connected
rdma_cms:
rdma_pkey: 0x0000
=====Discovery Log Entry 1======
trtype:
adrfam:
subtype: nvme subsystem
treq:
portid:
trsvcid: 4420
subnqn:
for NVMe device)
traddr:
rdma_prtype: roce-v2
rdma_qptype: connected
rdma_cms:
rdma_pkey: 0x0000
Step 4 : Connect to the device using the subnqn.
sudo nvme connect -t rdma -a 192.168.10.51 -n nqn.1992-05.com.wdc.openflex-
data24-usalp00000aa000a:nvme.1
Step 5 : Verify the connection using
root:~$ sudo nvme list -v
NVM Express Subsystems
Subsystem
----------------
-----------------------------------------------------------------------------------------
----------------
nvme-subsys0
NVM Express Controllers
Device
TxPort Address
-------- -------------------- ----------------------------------------
-------- ------ -------------- ------------ ----------------
rdma
ipv4
not specified
0
nqn.1992-05.com.wdc.openflex-data24-usalp00000bb000b:MI.AA (In-Band
192.168.10.51
rdma-cm
rdma
ipv4
not specified
0
nqn.1992-05.com.wdc.openflex-data24-usalp00000aa000a:nvme.1 (subnqn
192.168.10.51
rdma-cm
nvme list -v
Subsystem-NQN
nqn.1992-05.com.wdc.openflex-data24-usalp00000aa000a:nvme.1
SN MN
Subsystem
.
Controllers
nvme0
Namespaces
4. Management
4.3 NVMe-CLI
FR
75