vSphere Web Services API
|
| Local Properties | ||
| Managed Object Types | Data Object Types | All Properties | All Methods |
Data Object - HostNvmeDiscoveryLogEntry(vim.host.NvmeDiscoveryLog.Entry)
- Property of
- HostNvmeDiscoveryLog
- Extends
- DynamicData
- See also
- HostNvmeTransportParameters
- Since
- vSphere API Release 7.0
Data Object Description
This data object represents a single entry in the Discovery Log returned by a Discovery controller.Properties
| Name | Type | Description |
|---|---|---|
| adminQueueMaxSize | xsd:int |
The maximum size of the Admin Submission Queue.
Corresponds to the ASQSZ field in the Discovery Log
Page Entry as specified by the NVME over Fabrics spec.
This applies to all controllers within the NVM Subsystem.
When establishing a connection, the value of
adminQueueSize may not exceed
this value.
|
| connected | xsd:boolean |
Indicates whether the controller represented
by this Discovery Log Page Entry is already connected
to the adapter through which the discovery is initiated.
|
| controllerId | xsd:int |
NVME Controller ID within the NVM subsystem.
Corresponds to the CNTLID field in the Discovery Log
Page Entry as specified by the NVME over Fabrics spec.
In the static controller model, this field may be set
to a specific controller ID which can be used to connect
to that particular controller. It could also be set
to 0xFFFE (65534 in decimal), in which case the controller
ID will be allocated when a connection is established.
In the dynamic controller model, this field shall be set
to 0xFFFF (65535 in decimal).
Note that this is different from the controllerNumber
controllerNumber,
which is the unique identifier of the NVMe controller
within the entire host and is allocated only after a
connection is established.
|
| subnqn | xsd:string |
NVME Qualified name of the discovered subsystem.
Corresponds to the SUBNQN field in the Discovery Log
Page Entry as specified by the NVME over Fabrics spec.
|
| subsystemPortId | xsd:int |
NVM subsystem port ID.
Corresponds to the PORTID field in the Discovery Log Page Entry as specified by the NVME over Fabrics spec. For an overview, see:
|
| subsystemType | xsd:string |
NVM Subsystem type.
Corresponds to the SUBTYPE field in the Discovery Log
Page Entry as specified by the NVME over Fabrics spec.
The set of supported values is described in
SubsystemType.
|
| transportParameters | HostNvmeTransportParameters |
Transport specific parameters necessary to establish
a connection.
Different types of fabrics transports and different
means to specify a connection target may be supported.
The transport specific parameters object is constructed
based on the data in the Transport Type (TRTYPE),
Address Family (ADRFAM), Transport Service Identifier
(TRSVCID), Transport Address (TRADDR) and Transport
Specific Address Subtype (TSAS) fields in the Discovery
Log Page Entry as specified by the NVME over Fabrics spec.
When connecting to the controller represented by this
Discovery Log Page Entry, the transport specific
parameters can be passed directly as
NvmeConnectSpec#transportParameters.
|
| transportRequirements | xsd:string |
The requirements for NVME Transport.
Corresponds to the TREQ field in the Discovery Log
Page Entry as specified by the NVME over Fabrics spec
The set of possible values is described in
TransportRequirements
|
| Properties inherited from DynamicData | ||
| None | ||
Show WSDL type definition
| Top of page | Local Properties | ||
| Managed Object Types | Data Object Types | All Properties | All Methods |