An administrator discovers that a VMware Cloud Foundation (VCF) workload domain four-node vSAN cluster is experiencing a network partition. The workload domain vCenter displays a "vSAN duster…

Question

Options

• AIGMP snooping is disabled on the multicast group.
• BThe VLAN was changed on the physical switch port.
• CJumbo frames are configured on the vSphere distributed switch (VDS).
• DThe vSAN Witness service was added to the vMotion network.

• A
  3% (1)
• B
  74% (23)
• C
  10% (3)
• D
  13% (4)

Explanation

A vSAN cluster network partition occurs when vSAN nodes cannot communicate over the designated vSAN network. In VMware Cloud Foundation workload domains, the vSAN network relies on L2 adjacency, consistent VLAN configuration, and stable multicast/BUM behavior (in older versions). VCF 9.0 uses unicast-mode vSAN, so multicast-related issues (such as IGMP snooping configuration) are no longer relevant. A network partition can occur when the VLAN ID on the physical switch port differs from the VLAN configured on the vSphere Distributed Switch (VDS) for the vSAN VMkernel adapters. The documentation emphasizes that consistent VLAN configuration across the physical and virtual network is required for proper vSAN cluster communication. If a switch port is reconfigured-- intentionally or accidentally--to use a different VLAN, the node becomes isolated from the rest of the vSAN cluster, causing: "vSAN cluster partition" warnings in vCenter degraded performance objects marked as non-compliant resyncs that cannot complete

No community discussion yet for this question.