Home > Networking Solutions > Converged and Hyperconverged Solutions > VxRail Networking Solutions > Guides > Dell EMC Networking SmartFabric Services Deployment with VxRail 7.0 > Validate and build VxRail cluster
Figure 56. Review and validate screen
Note: VxRail Manager must be able to reach the DNS server for validation to succeed. Expand Show history to view the validation status. Validation may take 5 to 10 minutes.
When validation is complete, a message indicating whether the configuration has passed or failed displays, as shown in Figure 57.
Note: If validation failed, address the items that failed and validate again.
Figure 57. Validation has passed
Note: Once validation passes, Dell Technologies recommends clicking the DOWNLOAD JSON button to save an offline copy of your VxRail settings.
Figure 58. New VxRail Manager IP address - start configuration
The switch port connected to the jump host has been 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.
Optionally, you can run the show virtual network command on the leaf switch that the jump host is connected to verify the change. In the output below, the jump host port 1/1/9:1 is now untagged in VLAN 1811.
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.
S5248F-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):
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.
Figure 59. VxRail deployment in progress
Deployment takes about 1 hour. When VxRail is successfully deployed, the Hooray! message displays, as shown in Figure 60.
Figure 60. VxRail deployment successful
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 succeed.
Note: If prompted, launch the vSphere Client (HTML5). The older Flash-based vSphere Web Client (Flex) is deprecated and is not used in this guide.
The Hosts and Clusters page of the vSphere Client appears, as shown in Figure 61.
Figure 61. Newly created VxRail cluster
Caution: Review any warnings that may appear in the vSphere Client.