- Return to the Validate Configuration screen in the VxRail deployment wizard on the jump host.
- Click VALIDATE CONFIGURATION.Note: VxRail Manager must be able to reach the DNS server for validation to succeed. Expand Show Details to view the validation status. Validation may take 5 to 10 minutes for a 3-node cluster.When validation is complete, a message indicating whether the configuration has passed or failed displays, as shown in the figure below.Note: If validation failed, address the items that failed and validate again.Note: Once validation passes, Dell Technologies recommends clicking the DOWNLOAD CONFIGURATION FILE button to save a JSON file with your VxRail settings.
- Click NEXT.
- Click APPLY CONFIGURATION.The deployment begins.
- Expand the Show Details section to view the deployment details.
- When the deployment is about 30 percent complete, the Redirected to new address prompt displays.
The VxRail manager moves from its default IP address of 192.168.10.200, to its new IP address on the external management network, which is 172.18.11.72 in this example.Note: Ensure the jump host NIC has an IP address on the new network, 172.18.11.0/24 in this example, before proceeding with the next step. The jump host port on the leaf switch is untagged, so do not configure a VLAN ID on the jump host NIC.
- Click YES. You are automatically redirected to the new VxRail Manager IP address in the browser, and VxRail deployment continues, as shown in the figure below.Note: If the Redirected to new address prompt does not appear when deployment is about 30 percent complete, and the screen has not updated for at least 5 minutes, perform the following steps :
- At the CLI of the leaf switch that the jump host is connected to, run the show virtual-network command.
- Make sure the port that the jump host is connected to (Leaf1A, port 1/1/9:1 in this example) has automatically been moved from VLAN 4091 to the external management VLAN (1811 in this example).
- Once the jump host port has moved to the external management VLAN, manually change the IP address in the browser's address bar from 192.168.10.200 to the new VxRail Manager address, 172.18.11.72. The address is shown in the figure below. Leave the rest of the URL as-is. The browser connects to the new address and the deployment continues as shown in the figure below.
The switch port connected to the jump host is automatically moved from VLAN 4091 to the External Management VLAN, VLAN 1811, on the leaf switch to enable it to reach VxRail Manager on the new network.
(Optional) To verify the change, run the show virtual network command on the leaf switch that the jump host is connected to. In the output below, the jump host port 1/1/9:1 is now untagged in VLAN 1811 and is no longer in VLAN 4091.Note: Virtual networks 1812 through 1815 and 3939 have been removed from the output below for brevity. The output below is with an L3 uplink. If an L2 uplink is configured, the uplink port channel also appears as a member of VLAN 1811.
Leaf1A# show virtual-network Codes: DP - MAC-learn Dataplane, CP - MAC-learn Controlplane, UUD - Unknown-Unicast-Drop Un-tagged VLAN: 4080 Virtual Network: 1811 VLTi-VLAN: 1811 Members: Untagged: ethernet1/1/9:1 VLAN 1811: port-channel1000, ethernet1/1/1, ethernet1/1/2, ethernet1/1/3 VxLAN Virtual Network Identifier: 1811 Source Interface: loopback2(172.30.0.0) Remote-VTEPs (flood-list): Virtual Network: 4091 Description: Default untagged network for client onboarding VLTi-VLAN: 4091 Members: Untagged: ethernet1/1/1, ethernet1/1/2, ethernet1/1/3 VLAN 4091: port-channel1000 VxLAN Virtual Network Identifier: 4091 Source Interface: loopback2(172.30.0.0) Remote-VTEPs (flood-list):Deployment takes about one hour for a three-node cluster. When VxRail is successfully deployed, the VxRail Cluster Successfully Configured message displays, as shown.
- Click LAUNCH VCENTER to manage the cluster.Note: The jump host or workstation used must be able to reach the DNS server to resolve the hostname of the vCenter server for the connection to succeedNote: If prompted, click the LAUNCH VSPHERE CLIENT (HTML5) button.
- Log in using your vCenter credentials. In this example, the username is firstname.lastname@example.org.
The Hosts and Clusters page of the vSphere Client appears, as shown in the figure below.CAUTION: Review any warnings that may appear in the vSphere Client.