I85PREP
⌘ K
Dell VxRail Deploy study materials
Dell VxRail Deploy study resources

Dell VxRail Deploy: VxRail Cluster Deployment and Network Configuration

Dell VxRail Deploy · Work through your exam, one topic at a time.

All guide sections

VxRail Cluster Deployment and Network Configuration

What this domain covers

This domain tests the VxRail deployment workflow: the Deploy wizard, vCenter choice, VLAN/IP pool entry, vSAN and vMotion VMkernel setup, witness configuration, and validation failures.

Core rules

  • Open VxRail Manager and run Deploy > New Cluster. Select VxRail-managed vCenter or customer-managed vCenter; the choice changes which credentials and version checks apply.
  • Enter the vCenter FQDN, SSO credentials, VxRail Manager IP, DNS servers, and NTP servers. For customer-managed vCenter, confirm the existing vCenter is supported and reachable.
  • Configure management, vSAN, vMotion, VM, and internal VLANs. Supply IP pools, gateways, and MTU values. VxRail creates a distributed switch and places the appropriate VMkernel adapters on each host.
  • If vSAN uses MTU 9000, every switch port and uplink in the path must support jumbo frames. If any link is 1500, use 1500 consistently end to end.
  • For a two-node cluster, deploy the witness at the third site and configure witness traffic so quorum survives the loss of either data site.
  • Run validation before deployment. It checks IP conflicts, DNS, NTP, VLAN reachability, MTU, and credentials. Resolve every failure rather than forcing the deployment.
  • During deployment VxRail configures ESXi, creates the distributed switch, deploys or joins vCenter, configures vSAN, and registers the VxRail plugin.

Worked example

A cluster uses VLAN 110 for vSAN with MTU 9000. The ToR trunk allows VLAN 110, but one uplink between ToR A and ToR B is left at 1500. Validation reports an MTU mismatch on one host. Reasoning: the vSAN VMkernel MTU must match across the entire path; a single 1500 link causes vSAN health alerts and possible packet drops. Fix the uplink MTU, re-run validation, and only then deploy.

Traps

  • Selecting customer-managed vCenter without SSO admin credentials or a supported vCenter version.
  • Placing vSAN and vMotion on the same VMkernel adapter.
  • Forgetting the witness for a two-node cluster or placing it at a data site.
  • Missing PTR records, causing vCenter registration to fail.
  • Deploying a VxRail-managed vCenter into a VLAN with no VM network or gateway.
  • Mixing jumbo and standard MTU across the vSAN path.