VsanNetworkConfigPortgroupWithNoRedundancyIssue

VsanNetworkConfigPortgroupWithNoRedundancyIssue

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.

This structure may be used only with operations rendered under /vsan.

AllOf

This class requires all of the following:

VsanNetworkConfigBaseIssue

JSON Example

{
    "_typeName": "string",
    "host": {
        "_typeName": "string",
        "type": "string",
        "value": "string"
    },
    "portgroupName": "string",
    "vds": {
        "_typeName": "string",
        "type": "string",
        "value": "string"
    },
    "pg": {
        "_typeName": "string",
        "type": "string",
        "value": "string"
    },
    "numPnics": 0
}

host

Required

The Host on which the vmknic exists

string

portgroupName

Optional

Portgroup name, in case of VMware Standard Switch (VSS).

vds

Optional

The Virtual Distributed Switch, if in-use.

pg

Optional

Portgroup, either VSS or VDS.

integer As int64 As int64

numPnics

Required

Number of configured physical NICs.

Property Of

ArrayOfVsanNetworkConfigPortgroupWithNoRedundancyIssue