- 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
Remote VMware vSAN data store option
For primary storage with dynamic clusters, you can use an existing VMware vSphere or VxRail cluster with a local VMware vSAN data store in your data center.
The VMs running on the dynamic cluster use the free storage resource on the VMware vSAN data store, and the compute resources on the local nodes.
Ensure that the following guidelines are understood:
- Verify the cluster being targeted to supply storage resources to the dynamic cluster is at a support VxRail version. See the VxRail Support Matrix to verify if an upgrade is needed on this cluster.
- The cluster that is sharing its VMware vSAN data store and any dynamic cluster that is connected to this remote VMware vSAN data store must be configured on the same VMware vCenter instance under a common data center object.
- If you already have a cluster that is sharing its VMware vSAN data store to other clusters, ensure that you have not reached the maximum of five clusters that are already mounted to this VMware vSAN data store.
- The physical Ethernet network in your data center must support connectivity between the cluster nodes of both clusters.
- If Layer 3 connectivity is required, routing settings such as static routes or BGP must be configured.
- The RTT latency between the cluster sharing the vSAN data store and the dynamic cluster nodes must be less than 5 milliseconds.
- Routable IP addresses must be used on the VMkernel adapters supporting VMware vSAN on both the cluster nodes sharing the VMware vSAN data store and dynamic cluster nodes.
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: <>()\