An administrator is attempting to troubleshoot why the vSAN witness node cannot form a stretched cluster with the vSAN data nodes. The administrator can successfully ping the vSAN data node from the…

Question

Options

• APort 12321 is not opened bidirectionally between all nodes.
• BPort 443 is not opened bidirectionally between all nodes.
• CThe customer does not have any virtual machines in the vSAN Cluster.
• DJumbo Frames have not been enabled on the Witness Network.

• A
  82% (32)
• B
  3% (1)
• C
  10% (4)
• D
  5% (2)

Explanation

In a vSAN Stretched Cluster, communication between the witness node and data nodes requires several specific TCP/UDP ports. The ability to successfully execute: vmkping -I <witness-vmk> <vsan-IP> -s 1472 -d L2/L3 connectivity is present MTU is correctly configured ICMP traffic flows without fragmentation However, vmkping alone does not verify vSAN control-plane communication. For the vSAN Witness to properly form a cluster, TCP port 12321 must be open bidirectionally Witness Data nodes Data nodes Witness Port 12321 is required for: vSAN cluster membership vSAN object health/state synchronization If this port is blocked by firewall policy or misconfigured network ACLs, the nodes can ping each other, but vSAN witness traffic will fail, preventing the stretched cluster from forming.

No community discussion yet for this question.