Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


  • 1 EC2 instance mayascale1
  • 1.9 TB NVMe SSD (ephemeral)
  • Default network with private  IP (
    Permit  port 4420 which is the default port for NVMeoF TCP traffic
    Image Removed

  1. Connect to the MayaScale Cloud Data Platform instance using SSH  to secure the Web console GUI access by changing the default password to something random by running

    Code Block
    # /opt/mayastor/web/

    Or to set your own password

    Code Block
    # /opt/mayastor/web/
    Login name (default admin): 
    Login password: 
    Password again: 

    And then restart the web server for password changes to take effect

    No Format
    # /opt/mayastor/web/stop
    # /opt/mayastor/web/start

  2. Now you can proceed with provisioning NVMe storage using the  Administration Web console available on http://<mayanas<mayascale1-ip>:2020

  3. Based on the number of NVMe SSD that is available on the instance you will be able to view them on the GUI from View Disks

    For provisioning NVMe storage to clients you can create volume group from the physical NVMe and then slice them as logical volumes for flexible provisioning.  But for this guide we will be provisioning the whole NVMe resource to client.

    Using Mayascale Server Wizards → Create Mayastor Volume. Then Select Simple Volume and click Next

  4. Select the device for provisioning and click Next. In this example nvme0n1 is chosen.

  5. The next screen is to specify a name for the provisioned volume with brief description.

  6. Confirm the new volume settings.

  7.  Once the volume mynvme  was created successfully the next step is to make them available to clients using the NVMe TCP protocol. For this use the wizard Map a volume . Here select the newly create volume mynvme and choose nvmet-tcp  as the controller.  For iSCSI provisioning the controller will be iscsi. Then click Next

  8. Here the LUN refers the NVMe namespace id and it starts from 1.  For iSCSI the LUN starts from 0.

  9. Confirm mapping settings.

  10. Once mapping was created successfully it can be viewed by clicking Add or remove Mappings from the sidebar. Here you would notice the default NQN for the new volume.

  11. The next step is to activate the newly created mapping so that it is discoverable from NVMe hosts in the network. To activate click on the checkbox associated with mynvme
    and click Bind

  12. To discover this NVMe target from another client with  NVMe over fabrics support.

    Code Block
    [root@ip-172-31-20-45 ~]# modprobe nvme-tcp
    [root@ip-172-31-20-45 ~]# /opt/zettalane/bin/nvme  discover -a -s 4420 -t tcp
    Discovery Log Number of Records 1, Generation counter 1
    =====Discovery Log Entry 0======
    trtype:  tcp
    adrfam:  ipv4
    subtype: nvme subsystem
    treq:    not specified
    portid:  0
    trsvcid: 4420
    [root@ip-172-31-20-45 ~]# 

  13. For the client to perform IO on the discovered NVMe target, it has to be connected and configured with the host as follows.

    Code Block
    [root@ip-172-31-20-45 ~]# /opt/zettalane/bin/nvme  connect -a   -s 4420  -t tcp -n 
    [root@ip-172-31-20-45 ~]# /opt/zettalane/bin/nvme list
    [root@ip-172-31-20-45 ~]# /opt/zettalane/bin/nvme list
    Node             SN                   Model                                    Namespace Usage                      Format           FW Rev  
    ---------------- -------------------- ---------------------------------------- --------- -------------------------- ---------------- --------
    /dev/nvme0n1     vol047c5ca2e5ca231b8 Amazon Elastic Block Store               1           0.00   B /   8.59  GB    512   B +  0 B   1.0     
    /dev/nvme1n1     7e2888517b895b8      Linux                                    1           1.90  TB /   1.90  TB    512   B +  0 B   3.10.0-6

  14. Congratulations you have created NVMe target with MayasScale and mapped over NVMeof-TCP successfully to be discovered by clients.