nvmet.global.update =================== Update NVMe target global config. .. raw:: html
NVMetGlobalUpdateArgs parameters.
No Additional PropertiesNQN to be used as the prefix on the creation of a subsystem, if a subnqn is not supplied to nvmet.subsys.create.
Modifying this value will not change the subnqn of any existing subsystems.
Must be at least 11 characters long
Must be at most 223 characters long
Select the NVMe-oF backend.
Asymmetric Namespace Access (ANA) enabled.
RDMA is enabled for NVMe-oF.
Enabling is limited to TrueNAS Enterprise-licensed systems and requires the system and network environment have Remote Direct Memory Access (RDMA)-capable hardware.
Once enabled one or more ports may be configured with RDMA selected as the transport. See nvmet.port.create.
Controls whether cross-port referrals will be generated for ports on this TrueNAS.
If ANA is active then referrals will always be generated between the peer ports on each TrueNAS controller node.
The updated NVMe-oF global configuration.
No Additional PropertiesUnique identifier for the NVMe-oF global configuration.
NQN to be used as the prefix on the creation of a subsystem, if a subnqn is not supplied to nvmet.subsys.create.
Modifying this value will not change the subnqn of any existing subsystems.
Select the NVMe-oF backend.
Asymmetric Namespace Access (ANA) enabled.
RDMA is enabled for NVMe-oF.
Enabling is limited to TrueNAS Enterprise-licensed systems and requires the system and network environment have Remote Direct Memory Access (RDMA)-capable hardware.
Once enabled one or more ports may be configured with RDMA selected as the transport. See nvmet.port.create.
Controls whether cross-port referrals will be generated for ports on this TrueNAS.
If ANA is active then referrals will always be generated between the peer ports on each TrueNAS controller node.