Confirming the Client Connection to Lightbits

AI Tools

To confirm the client connection to Lightbits, perform the following command:

nvme list-subsys

Sample Output

root@rack07-server56:~ nvme list-subsys nvme-subsys0 - NQN=nqn.2016-01.com.lightbitslabs:uuid:66ee2ad7-8602-49ed-9b82-0c85af8da36d \+ - nvme0 tcp traddr=172.16.231.70 trsvcid=4420 live +- nvme1 tcp traddr=172.16.231.71 trsvcid=4420 live +- nvme2 tcp traddr=172.16.231.72 trsvcid=4420 live

Next, review your connected block devices to see the newly connected NVMe/TCP block device, using the Linux lsblk command:

lsblk

Sample Output

root@rack07-server56:~ lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT nvme0n1 259:1 0 25G 0 disk /snapshot/tmp nvme0n2 259:3 0 25G 0 disk sda 8:0 0 223.6G 0 disk |-sda2 8:2 0 1G 0 part /boot |-sda3 8:3 0 222.6G 0 part | |-inaugurator--v2-osmosis--cache 253:1 0 30G 0 lvm | |-inaugurator--v2-root 253:2 0 147.7G 0 lvm / | `-inaugurator--v2-swap 253:0 0 8G 0 lvm [SWAP] `-sda1

A new nvme0n1 block device with 200GB of storage is identified and available.

To determine which node in the cluster is the primary and which is secondary for this block device, enter the nvme list-subsys command with the block device name.

nvme list-subsys $DEVICE_PATH

Sample Output

root@rack07-server56:~ nvme list-subsys /dev/nvme0n1 nvme-subsys0 - NQN=nqn.2016-01.com.lightbitslabs:uuid:66ee2ad7-8602-49ed-9b82-0c85af8da36d \+ - nvme0 tcp traddr=172.16.231.70 trsvcid=4420 live optimized +- nvme1 tcp traddr=172.16.231.71 trsvcid=4420 live +- nvme2 tcp traddr=172.16.231.72 trsvcid=4420 live