Skip to main content
A newer release of this product is available.

vserver nvme subsystem create

Contributors
Suggest changes
PDFs

Create an NVMe target subsystem

Availability: This command is available to cluster and Vserver administrators at the admin privilege level.

Description

The vserver nvme subsystem create command creates a new NVMe target subsystem.

When you create an NVMe subsystem on a Vserver, the Vserver must meet the following pre-conditions:

  • The Vserver must have an NVMe service created.

  • The Vserver must not already have an NVMe subsystem by the same name.

Note The NVMe subsystem identifiers are assigned by the system. The NQN is derived from the Vserver UUID and subsystem name and may not be specified or modified by the user.

Parameters

-vserver <Vserver Name> - Vserver Name

Specifies the Vserver.

-subsystem <text> - Subsystem

Specifies the NVMe target subsystem.

-ostype {windows|linux|vmware} - OS Type

Specifies the operating system type of the NVMe subsystem. The OS types are:

  • linux - the initiators belong to a Linux host.

  • vmware - the initiators belong to a VMware ESX host.

  • windows - the initiators belong to a Windows host.

[-comment <text>] - Comment

Contains a textual description of the NVMe subsystem.

[-delete-on-unmap {true|false}] - Delete on Unmap (privilege: advanced)

Specifies whether the subsystem should be deleted automatically when it is no longer mapped to a namespace.

[-vendor-uuids <UUID>,…​] - Vendor UUIDs (privilege: advanced)

Specifies vendor-specific identifiers (UUIDs) optionally assigned to an NVMe subsystem when the subsystem is created. The identifiers are used to enable vendor-specific NVMe protocol features. The identifiers are provided by a host application vendor and shared with NetApp prior to a joint product release. Creating an NVMe subsystem with an unknown or non-specific identifier will have no effect on the NVMe subsystem. Refer to the ONTAP SAN Administration Guide for a list of the supported vendor-specific identifiers. After a subsystem is created, the vendor-specific identifiers cannot be changed or removed.

Examples

cluster1::*> vserver nvme subsystem create -vserver vs_1 -subsystem sub_1 -ostype linux

Creates a subsystem named sub_1 on Vserver vs_1 .