- 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
Decide on teaming and failover policies for VxRail networks
At the time of initial implementation, you can select and assign the teaming and failover policy on each port group for each required VxRail network.
The following load-balancing policies are supported for VxRail clusters:
- Route based on the originating virtual port: After the VMware VDS selects an uplink for a VM or VMkernel adapter, it always forwards traffic through the same uplink. This option makes a simple selection based on the available physical uplinks. This policy does not attempt to load balance based on network traffic.
- Route based on source MAC hash: The virtual switch selects an uplink for a VM based on the VM MAC address. This option requires more resources than the originating virtual port, but has more flexibility in uplink selection. This policy does not attempt to load balance based on network traffic analysis.
- Use explicit failover order: Always use the highest order uplink that passes failover detection criteria from the active adapters. No actual load-balancing is performed with this option.
- Route based on physical NIC load: The virtual switch monitors network traffic, and attempts to adjust overloaded uplinks by moving traffic to another uplink. This option does use additional resources to track network traffic.
VxRail does not support the route based on IP hash policy. This policy has a dependency on the logical link setting of the physical port adapters on the switch.
VxRail applies a default teaming and failover policy configuration based on the following teaming policy settings:
- Active/Active: The default load balance policy set by VxRail is Route based on physical NIC load.
- Active/Standby: The default load balance policy set by VxRail is Route based on originating virtual port.
If the Ethernet adapters targeted to support VMware vSAN support RDMA, the following teaming policies are supported:
- Route based on originating virtual port
- Route based on source MAC hash
- Use explicit failover order
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: <>()\