vserver nvme subsystem controller show
- PDF of this doc site
Collection of separate PDF docs
Creating your file...
Display active NVMe controllers
Availability: This command is available to cluster and Vserver administrators at the admin privilege level.
Description
The vserver nvme subsystem controller show
command displays information for established NVMe controllers. An NVMe controller is established upon each host connection to a subsystem.
Parameters
- {
[-fields <fieldname>,…]
-
If you specify the
-fields <fieldname>, …
parameter, the command output also includes the specified field or fields. You can use '-fields ?' to display the fields to specify. - |
[-instance ]
} -
If you specify the
-instance
parameter, the command displays detailed information about all fields. [-vserver <Vserver Name>]
- Vserver Name-
Use this parameter to display the NVMe controllers that match the Vserver that you specify.
[-subsystem <text>]
- Subsystem-
Use this parameter to display the NVMe controllers that match the subsystem that you specify.
[-controller-id <Hex 16bit Integer>]
- Controller ID-
Use this parameter to display the NVMe controllers that match the controller ID that you specify. The controller ID is the identifier assigned by the NVMe subsystem upon host login and controller creation.
[-lif <text>]
- Logical Interface-
Use this parameter to display the NVMe controllers that match the LIF that you specify.
[-node <nodename>]
- Node-
Use this parameter to display the NVMe controllers that match the cluster node that you specify.
[-host-nqn <text>]
- Host NQN-
Use this parameter to display the NVMe controllers that match the host NQN that you specify. The host NQN is the NVMe identifier assigned to a specific host.
[-transport-protocol {fc-nvme|nvme-tcp}]
- Transport Protocol-
Use this parameter to display the NVMe controllers that match the transport protocol that you specify.
[-initiator-transport-address <text>]
- Initiator Transport Address-
Use this parameter to display the NVMe controllers that match the initiator transport address that you specify. The initiator transport address format depends on the transport protocol in use.
[-host-id <Hex String>]
- Host Identifier-
Use this parameter to display the NVMe controllers that match the host identifier that you specify. The host identifier is a 128-bit identifier assigned to a specific host.
[-io-queue-count <integer>]
- Number of I/O Queues-
Use this parameter to display the NVMe controllers that match the I/O queue count that you specify.
[-io-queue-depth <integer>,…]
- I/O Queue Depths-
Use this parameter to display the NVMe controllers that match the I/O queue depth that you specify.
[-admin-queue-depth <integer>]
- Admin Queue Depth-
Use this parameter to display the NVMe controllers that match the administrative queue depth that you specify.
[-subsystem-uuid <UUID>]
- Subsystem UUID-
Use this parameter to display the NVMe controllers that match the Subsystem UUID that you specify.
[-header-digest-enabled {true|false}]
- Header Digest Enabled-
Use this parameter to display the NVMe controllers that have header digest enabled.
[-data-digest-enabled {true|false}]
- Data Digest Enabled-
Use this parameter to display the NVMe controllers that have data digest enabled.
Examples
cluster1::*> vserver nvme subsystem controller show -vserver vs_1 -subsystem ss1 Vserver Subsystem ID LIF Host NQN ------- --------- ----- ------ ---------------------------------------------- vs_1 ss1 0003h lif1 nqn.2001-08.example.com:nvme:host1 0004h lif1 nqn.2001-08.example.com:nvme:host2 0009h lif2 nqn.2001-08.example.com:nvme:host1 000Ah lif2 nqn.2001-08.example.com:nvme:host2 4 entries were displayed.