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

Dell VxRail Deploy: VxRail Deployment Planning

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

All guide sections

VxRail Deployment Planning

What this domain covers

This domain tests whether you can turn a customer workload and site constraint into a valid VxRail bill of materials and a deployable network plan. Expect questions on cluster topology, vCenter ownership, IP/DNS/NTP sizing, model selection, and supported limits.

Core rules

  • Start with the VxRail Support Matrix, not a data sheet. It defines which models, drives, NICs, ESXi/vCenter versions, and expansion combinations are supported for the release you will deploy.
  • A standard cluster needs at least three nodes. A two-node cluster is a supported ROBO topology only with a witness; the witness belongs in a third fault domain, not on one of the two data-site nodes.
  • Choose the vCenter model early: VxRail-managed vCenter (VxRail deploys a dedicated VCSA) or customer-managed vCenter (VxRail joins an existing supported vCenter). The latter needs SSO credentials, a supported version, and network access from every node and VxRail Manager.
  • Reserve separate VLANs/subnets for management, vSAN, vMotion, VM traffic, and the VxRail internal network. Each node needs a management IP, a vSAN VMkernel IP, and a vMotion VMkernel IP; add VxRail Manager, vCenter, and witness addresses.
  • DNS must resolve forward and reverse (PTR) for vCenter, VxRail Manager, and every ESXi host. NTP must be external and consistent; time skew breaks SSO and certificates.
  • Size for failure and growth: vSAN policy (FTT=1 vs FTT=2), N+1 power, ToR uplinks, and spare capacity for rebuilds. Model series (E/P/V/S/D) map to general, performance, VDI, storage, and dense use cases; confirm exact model support in the matrix.
  • Licensing: VxRail bundles vSphere/vSAN entitlements, but customer-managed vCenter and add-on services still need valid keys.

Worked example

A four-node cluster, no witness, with management, vSAN, and vMotion on separate VLANs. IP count: 4 nodes x 3 VMkernel addresses = 12, plus VxRail Manager = 13, plus vCenter = 14. Do not request 12; the appliance and vCenter addresses are easy to forget. If the design later becomes a two-node ROBO cluster, add witness addresses and a third-site network path.

Traps

  • Planning vSAN and management on the same subnet "to save VLANs"; validation and support may reject it.
  • Forgetting PTR records, then failing vCenter registration.
  • Using a vCenter version outside the VxRail release matrix.
  • Assuming a two-node cluster works without a witness.
  • Sizing only for current VMs, with no rebuild headroom.