Connecting the Client to Lightbits

To connect the client to Lightbits, make sure to do the following:

Ping to data_ip from the client to the target.
To use NVMe/TCP, load the NVMe host modules.

Bash
    
 
modprobe nvme_tcp; lsmod | grep nvme
Copy

The output is similar to the following example:

Bash
    
 
root@rack07-server56:~ modprobe nvme_tcp; lsmod | grep nvmenvme_tcp 36864 0nvme_fabrics 24576 1 nvme_tcpnvme_core 118784 3 nvme_tcp ,nvme_fabricst10_pi 16384 2 sd_mod ,nvme_core
Copy

On the target node, enter the lbcli get cluster command on the Lightbits storage server to identify the subsytem NQN.

Bash
    
 
lbcli get cluster
Copy

Sample Output

Bash
    
root@rack03-server72:~ lbcli get clusterUUID Subsystem NQNCurrent Max Replicas Supported Max Replicas MinVersionInCluster MinAllowedVersion MaxAllowedVersiond63110c9-f6f3-4ab3-ba86-1e6fd6afc66a nqn.2016-01.com.lightbitslabs:uuid:66ee2ad7-8602-49ed-9b82-0c85af8da36d 3 3 2.3.12~b793 2.3.X 2.4.X
Copy

Enter the lbcli list nodes command to identify the NIC IP address and TCP port. With the IP, port, subsystem NQN, and ACL values for the volume, you can execute the nvme connect command to connect to all of the nodes in the cluster.

Bash
    
 
lbcli list nodes
Copy

Sample Output

Bash
    
 
root@rack03-server72:~ lbcli list nodesName UUID State NVMe endpoint Failure domains Locaserver02-0 3b7a262a-ba3f-5447-9c21-e3c8ed699f0f Active 172.16.231.72:4420 [server02] Noneserver00-0 8b980170-f941-5473-9162-36a17e866a36 Active 172.16.231.70:4420 [server00] Noneserver01-0 cfbfdc90-43b3-5ce6-be99-1ab4171785b0 Active 172.16.231.71:4420 [server01] None
Copy

Connect To Each Controller One By One

Connect To All Controllers

Use NVMe Connect

This command connects to a single controller in the Lightbits cluster. You will have to connect to every controller in the cluster.

Bash
    
xxxxxxxxxx
 
nvme connect -t tcp -a $CONTROLLER_DATA_IP --ctrl-loss-tmo -1 -n $LIGHTBITS_CLUSTER_NQN -s 4420 -q $VOLUME_ACL
Copy

Sample NVMe Connect Commands

Bash
    
xxxxxxxxxx
 
# server00-0nvme connect -t tcp -a 172.16.231.70 --ctrl-loss-tmo -1 -n nqn.2016-01.com.lightbitslabs:uuid:66ee2ad7-8602-49ed-9b82-0c85af8da36d -s 4420 -q acl3# server01-0nvme connect -t tcp -a 172.16.231.71 --ctrl-loss-tmo -1 -n nqn.2016-01.com.lightbitslabs:uuid:66ee2ad7-8602-49ed-9b82-0c85af8da36d -s 4420 -q acl3# server02-0nvme connect -t tcp -a 172.16.231.72 --ctrl-loss-tmo -1 -n nqn.2016-01.com.lightbitslabs:uuid:66ee2ad7-8602-49ed-9b82-0c85af8da36d -s 4420 -q acl3
Copy

For persisting the NVMe connections across client reboots, use the Lightbits open source discovery-client tool.

Check Connection

To check which clients are connected to the Lightbits cluster, run:

Bash
    
 
lbcli list connected-hosts
Copy

Sample Output

Bash
    
 
root@rack03-server72:~ lbcli list connected-hostsHost NQN IP Address Hostnameacl3 172.16.231.78
Copy

Last updated on

Was this page helpful?