- Notes, cautions, and warnings
- Revision history
- Introduction
- VxRail network planning overview
- Plan the VxRail network
- VxRail cluster types
- VxRail hardware and switch selection decision points
- Prepare the data center to implement VxRail
- Decide on an IP address scheme
- Prepare external network connectivity for VxRail
- Prepare service connectivity for VxRail
- Prepare for VMware vSphere+ subscription licensing
- Prepare data center routing services
- Prepare for multirack VxRail cluster
- Prepare for VMware vSAN HCI mesh topology
- Prepare external FC storage for dynamic clusters
- Prepare for VxRail custom uplink assignments
- Prepare data center network MTU
- Prepare for LAG of VxRail networks
- Plan LAG on switch port pairs
- Prepare certificate authority server for VxRail
- Identify isolation IP addresses for VMware vSphere High Availability
- Plan the VxRail cluster implementation
- Decide on VxRail single point of management
- Decide on VxRail network traffic segmentation
- Decide on teaming and failover policies for VxRail networks
- Plan the VxRail logical network
- Plan network settings for VxRail management components
- Plan network settings for VMware vCenter Server management network
- Identify IP addresses for VxRail management components
- Select hostnames for VxRail management components
- Identify external applications and settings for VxRail
- Prepare the customer-managed VMware vCenter Server
- Prepare a customer-managed VMware VDS
- Reserve IP addresses for VxRail-managed VMware vSphere vMotion network
- Reserve IPv4/IPv6 addresses for VxRail vSAN network
- Decide on VxRail logging solution
- Assign passwords for VxRail management
- Plan VMware vSAN witness networking
- Plan networking for VxRail Satellite Nodes
- Configure the Network for VxRail
- Prepare to build the VxRail cluster
- VxRail network considerations after implementation
- Appendix A: VxRail Network Configuration Table
- Appendix B: VxRail Passwords
- Appendix C: VxRail cluster setup checklist
- Appendix D: VxRail Open Ports Requirements
- Appendix E: VMware VDS port group default settings
- Appendix F: Physical Network Switch Examples
- Pre-defined network profile: 2x10gb or 2x25gb from a single NDC/OCP
- Predefined network profile: 4x10gb or 4x25gb NDC/OCP
- Predefined network profile: 2 x 10/25 GB NDC/OCP and 2 x 10/25 GB PCIe
- Custom option: Any NDC/OCP ports paired with PCIe ports
- Custom option: Two NDC/OCP ports paired with PCIe ports other than the first slot
- Custom option: PCIe ports only
- Custom option: Six ports
- Custom option: Eight ports
- Custom option: Eight ports connected to four Ethernet switches
Dell VxRail Network Planning Guide
Reserve network settings for VMware vSAN witness networks
The VMware vSAN witness networks can be VxRail-managed or customer-managed.
- For a VxRail stretched cluster, a customer-managed VMware vSAN witness is the only option. Configuring connectivity between the VxRail cluster networks and the VMware 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 VMware vSAN witness can be either:
- VxRail-managed VMware vSAN witness where VxRail Manager configures the vSAN witness with the network settings that are provided during the initial build process.
- Customer-managed VMware vSAN witness where 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 VMware vSAN witness virtual appliance. The witness management network and the witness VMware vSAN network cannot share the same subnet.
| Network configuration table | Action |
|---|---|
| Row 96 | Enter the IP address for the witness management network. |
| Row 97 | Enter the IP address for witness VMware vSAN network. |
Decide whether to use the VMware 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.
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 98 | Enter the IP address for the first of the two nodes in the 2-node cluster. |
| Row 99 | Enter the IP address for the second of the two nodes in the 2-node cluster. |
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\