D-VXR-DY-01: VxRail Deploy V2

A read-only request for the current cluster configuration uses the HTTP GET method. GET retrieves resource information without creating, changing, or deleting configuration.

VxRail iDRAC management requires 1 GbE connectivity, but it can use open ports on the same ToR switches used for VxRail network traffic instead of a dedicated out-of-band management switch. LACP-based link aggregation can optimize demanding networks when selected, but it is not universally required before deployment.

Day 1 VxRail API operations cover initial cluster deployment: discovering the available hosts, configuring and initializing a new cluster, and checking the initialization request’s status. Cluster expansion and software upgrades are post-deployment lifecycle operations. Dell’s VxRail API documentation identifies initialization-host discovery and the system initialization API, while its release documentation treats lifecycle-management upgrades and cluster expansion as separate operations.

The -b option creates a VxRail Manager backup, and the -l option lists the backup copies. VxRail Manager logs are included only with --keeplog; listing existing services uses -d.

For a customer-managed VMware VDS using LAG, the LACP policy must be configured on the VDS in the customer-managed vCenter Server instance, and the appropriate port groups must have the required teaming and failover policy. Thus, the LAG uplink configuration must already exist in vCenter before implementation.