The vSAN witness can be VxRail-managed or customer-managed.
- For a VxRail stretched cluster, a customer-managed vSAN witness is the only option.
- Configuring connectivity between the VxRail cluster networks and the vSAN witness networks occurs after VxRail Manager completes the initial build of the cluster at the primary site.
- For a VxRail 2-node cluster, the vSAN witness can be VxRail-managed or customer-managed.
- For a VxRail-managed vSAN witness, VxRail Manager configures the vSAN witness with the network settings that are provided during the initial build process.
- For a customer-managed vSAN witness, VxRail Manager validates network connectivity as part of the validation process. Validation must pass before continuing to the initial build phase.
Record the two IP addresses for the vSAN witness virtual appliance. The Witness Management Network and the Witness vSAN Network cannot share the same subnet.
| Network configuration table | Action |
| Row 67 | Enter IP address for Witness Management Network. |
| Row 73 | Enter IP address for Witness vSAN Network. |
Decide whether to use the vSAN network or the Witness Traffic Separation (WTS) Network for monitoring.
- For a VxRail 2-node cluster, the WTS network is required.
- For a VxRail stretched cluster, a WTS network is recommended but not required.
Record the VLAN for the WTS network using the network configuration table: Row 74 and enter the VLAN for the WTS network.
For a 2-node cluster deployment, record the IP addresses for each node that is required for vSAN witness traffic.
| Network configuration table | Action |
| Row 75 | Enter the IP address for the first of the two nodes in the 2-node cluster. |
| Row 76 | Enter the IP address for the second of the two nodes in the 2-node cluster. |