vSAN Management API
| Local Properties | ||
Managed Object Types | Data Object Types | All Properties | All Methods |
Data Object - VsanNetworkConfigPortgroupWithNoRedundancyIssue(vim.vsan.VsanNetworkConfigPortgroupWithNoRedundancyIssue)
- Extends
- VsanNetworkConfigBaseIssue
- See also
- DistributedVirtualSwitch, HostSystem, Network
- Since
- 6.6
Data Object Description
Configuration issue: vSAN is using a vmknic on a portgroup which doesn't have any physical NIC redundancy. This means in case of a physical NIC failure vSAN would not be able to use the vmknic any more to communicate with the remaining cluster. There are two possible causes for this issue: a) The virtual switch itself may lack physical NIC redundancy (also tracked as a separated health issue) or b) the NIC teaming policy of the portgroup is not configured for redundancy. Note that physical NIC redundancy is a best practice, not a functional/support requirement.Properties
Name | Type | Description |
---|---|---|
host | ManagedObjectReference
to a HostSystem |
The Host on which the vmknic exists
|
numPnics | xsd:long |
Number of configured physical NICs.
|
pg* | ManagedObjectReference
to a Network |
Portgroup, either VSS or VDS.
|
portgroupName* | xsd:string |
Portgroup name, in case of VMware Standard Switch (VSS).
|
vds* | ManagedObjectReference
to a DistributedVirtualSwitch |
The Virtual Distributed Switch, if in-use.
|
Properties inherited from VsanNetworkConfigBaseIssue | ||
None | ||
Properties inherited from DynamicData | ||
None |
Show WSDL type definition
Top of page | Local Properties | ||
Managed Object Types | Data Object Types | All Properties | All Methods |