Dell VxRail Deploy key terms

A wizard-driven tool that runs before deployment to gather planning inputs such as host names, IP addresses, and credentials, producing a configuration file used by the VxRail deployer. It validates inputs so that later automated steps do not fail.

The temporary appliance or virtual machine that orchestrates imaging and configuration of VxRail nodes during initial build. It pushes the ESXi image and configuration to each node, then hands management to VxRail Manager once the cluster is formed.

The management virtual machine running inside the cluster that provides the VxRail plugin, health monitoring, lifecycle management, and upgrade orchestration. It integrates with vCenter Server and is the primary interface for day-two operations.

An extension registered in vCenter Server that surfaces VxRail-specific tasks such as cluster health, configuration, and upgrades within the vSphere Client. It communicates with VxRail Manager and requires a supported vCenter version.

A group of VxRail nodes managed as a single vSphere cluster with shared VxRail Manager and vCenter integration. Minimum and maximum node counts depend on the model and software version, and all nodes must be the same model family.

A single physical VxRail server in a cluster, containing compute, memory, storage, and network adapters. Each node is imaged with ESXi and joined to the cluster during deployment, and nodes are added or replaced individually.

The integrated Dell Remote Access Controller embedded in each VxRail node, providing out-of-band console, power control, and hardware inventory over a dedicated management IP. Deployment requires iDRAC connectivity and credentials for every node.

The dedicated network connecting iDRAC interfaces to a management switch, separate from data and vMotion traffic. It must be reachable from the deployer and sized with enough addresses for every node plus future expansion.

The network carrying ESXi management, VxRail Manager, and vCenter traffic. It requires static addresses, correct VLAN tagging, and DNS resolution so that components can register and communicate during and after deployment.

Forward and reverse DNS records plus reachable NTP sources that every VxRail component depends on. Missing or incorrect records cause deployment failures, certificate issues, and time-skew problems in vCenter and VxRail Manager.

The VMware management platform that VxRail integrates with for inventory, permissions, and clustering. It can be external or embedded depending on the VxRail version, and its version must match VxRail compatibility requirements.

The practice of assigning 802.1Q VLAN IDs to specific traffic types such as management, vMotion, vSAN, and VM networks. Correct tagging on both the physical switch ports and the VxRail configuration is required for traffic to pass.

The dedicated network carrying vSAN storage traffic between cluster nodes. It should be on its own VLAN with sufficient bandwidth, and it must be configured consistently across all nodes or the cluster will not form.

VMware's software-defined storage layer that pools local disks across cluster nodes into a shared datastore. VxRail uses vSAN as its primary storage architecture, and its health directly affects cluster availability and capacity planning.

A vSAN construct pairing one or more cache devices with capacity devices on a node. Disk group layout determines usable capacity and failure tolerance, and must be planned per node before deployment.

The flash devices in a vSAN disk group that absorb writes and hold recently read data. Cache sizing affects performance, and cache device failure can take an entire disk group offline.

The devices in a vSAN disk group that store persistent data. Capacity tier sizing determines usable datastore space after accounting for policy overhead and failure tolerance.

A vSAN rule set defining failure tolerance, stripe width, and other data placement characteristics applied to virtual machine objects. Policies determine how much raw capacity is consumed for a given amount of usable space.

The vSAN setting choosing between mirroring and erasure coding to protect data. Mirroring uses more capacity but performs better; erasure coding saves space but requires more CPU and specific cluster conditions.

The guided workflow in VxRail Manager or the deployer that steps an administrator through network, host, and cluster settings. It performs validation checks before applying configuration and reports errors that must be resolved to continue.

A documented set of prerequisites covering firmware, cabling, addressing, credentials, and compatibility that must be satisfied before starting a deployment. Skipping items typically causes failures mid-deployment that require a rebuild.

Dell's published list of supported hardware, firmware, ESXi, vCenter, and VxRail software combinations. Deployments outside the matrix are unsupported and may fail validation or behave unpredictably after upgrades.

A packaged set of BIOS, iDRAC, and device firmware versions validated together for a VxRail release. Applying the matching bundle keeps nodes consistent and is required before or during lifecycle operations.

The VxRail capability to plan, stage, and apply software and firmware updates across the cluster. It checks compatibility, performs pre-checks, and orchestrates rolling upgrades while maintaining cluster availability.

An automated assessment of cluster components covering hardware, vSAN, network, and software state. Running health checks before and after changes surfaces issues early and is a standard troubleshooting starting point.

A collected archive of VxRail Manager, ESXi, and hardware logs generated for support analysis. It is typically the first artifact requested when opening a case and should be captured soon after an issue appears.

A formal request filed with Dell technical support containing symptoms, timeline, and diagnostic evidence. Accurate descriptions and attached log bundles shorten resolution time and avoid repeated information requests.

The process of adding a new node to an existing cluster, which requires matching model, firmware, and software levels. The node is discovered, validated, imaged, and then joined, with vSAN rebalancing afterward.

Swapping a failed or degraded node for a spare while preserving cluster membership and data. The procedure involves putting the node into maintenance mode, removing it, and adding the replacement through the deployment workflow.

A vSphere state in which a host evacuates or migrates workloads so it can be serviced safely. Correct maintenance mode selection, including data evacuation options for vSAN, prevents unnecessary risk during repairs.

The access-layer switch connecting VxRail nodes to the network, providing the ports, VLANs, and link speeds required by the design. Its configuration must match the planned traffic separation and redundancy model.

Bonding multiple physical NICs into one logical link for bandwidth and redundancy. The switch configuration must match the host teaming policy, or traffic will fail or degrade unexpectedly.

A documented allocation of subnets, static addresses, and VLANs for management, vMotion, vSAN, and VM traffic. It must include spare addresses for expansion and be validated before deployment begins.

The passwords for ESXi root, iDRAC, and management components set during deployment. They must meet complexity rules, be recorded securely, and are required for later troubleshooting and lifecycle operations.

An external component used in two-node or stretched configurations to break ties and maintain quorum. Its placement and network reachability are critical, since losing it can make the cluster unavailable.

A configuration splitting nodes across two sites with a witness at a third location to survive a site failure. It requires low-latency links and careful policy design to meet availability goals.

A VxRail node managed by a central cluster but located at a remote site, extending management without a full local cluster. Networking and latency requirements differ from standard cluster nodes.

The specific ESXi build and driver set validated for a VxRail model and release. Using the correct profile ensures supported drivers and avoids validation errors during imaging.

A firmware feature verifying signed boot components before execution. VxRail supports it on qualified configurations, and enabling it incorrectly can prevent a node from booting after changes.