Home > Networking Solutions > Converged and Hyperconverged Solutions > VxRail Networking Solutions > Guides > Dell EMC Networking SmartFabric Services Deployment with VxRail 7.0 > Add a VxRail node to the cluster
For this example, VxRail node 4 is connected to the fabric. It is in Rack 2 and connected to Leaf2A and Leaf2B, as shown in Figure 62.
Ensure forward and reverse lookup records have been added to the DNS server for each new node to be added to the cluster. In this example, the node FQDN is vxrail04.dell.lab, and its IP address is 172.18.11.104. Figure 68 shows validation commands run from a Microsoft Windows-based system with connectivity to the DNS server.
Figure 68. Forward and reverse lookup commands
Use the vSphere Client to add the VxRail node as follows:
Figure 69. VxRail node discovered
Figure 70. Discovered Hosts window
Figure 71. User Credentials window
Figure 72. Host IP Address window
Figure 73. ESXi Credentials window
Figure 74. Maintenance Mode window
Figure 75. Validate window
Figure 76. Validation successful
The Host expansion is in progress. Health monitoring is currently disabled during this task message displays and a progress bar displays under Status. Both are outlined in red in Figure 77.
Note: The host expansion process may take 10 to 15 minutes to complete.
Figure 77. Host expansion in progress
Figure 78. Fourth VxRail node added to the cluster
CAUTION: Review any warnings that may appear in the vSphere Client.
Optionally, verify the interface connected to the new VxRail node has been automatically added to the VxRail networks on the leaf switches. To verify the connection, run the show virtual network command. In this example, the new VxRail node is connected to interface 1/1/1 on Leaf2A and Leaf2B.
Note: The command output shown in the following command is for Leaf2A. The output for Leaf2B is the same.
The output below confirms the interface connected to the new VxRail node, ethernet1/1/1, has been automatically placed in all VxRail virtual networks/VLANs.
S5248F-Leaf2A# 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:
VLAN 1811: port-channel1000, ethernet1/1/1
VxLAN Virtual Network Identifier: 1811
Source Interface: loopback2(172.30.0.1)
Remote-VTEPs (flood-list): 172.30.0.0(CP)
Virtual Network: 1812
VLTi-VLAN: 1812
Members:
VLAN 1812: port-channel1000, ethernet1/1/1
VxLAN Virtual Network Identifier: 1812
Source Interface: loopback2(172.30.0.1)
Remote-VTEPs (flood-list): 172.30.0.0(CP)
Virtual Network: 1813
VLTi-VLAN: 1813
Members:
VLAN 1813: port-channel1000, ethernet1/1/1
VxLAN Virtual Network Identifier: 1813
Source Interface: loopback2(172.30.0.1)
Remote-VTEPs (flood-list): 172.30.0.0(CP)
Virtual Network: 1814
VLTi-VLAN: 1814
Members:
VLAN 1814: port-channel1000, ethernet1/1/1
VxLAN Virtual Network Identifier: 1814
Source Interface: loopback2(172.30.0.1)
Remote-VTEPs (flood-list): 172.30.0.0(CP)
Virtual Network: 1815
VLTi-VLAN: 1815
Members:
VLAN 1815: port-channel1000, ethernet1/1/1
VxLAN Virtual Network Identifier: 1815
Source Interface: loopback2(172.30.0.1)
Remote-VTEPs (flood-list): 172.30.0.0(CP)
Virtual Network: 3939
Description: In-band SmartFabric Services discovery network
VLTi-VLAN: 3939
Members:
VLAN 3939: port-channel1000, ethernet1/1/1
VxLAN Virtual Network Identifier: 3939
Source Interface: loopback2(172.30.0.1)
Remote-VTEPs (flood-list): 172.30.0.0(CP)
Virtual Network: 4091
Description: Default untagged network for client onboarding
VLTi-VLAN: 4091
Members:
Untagged: ethernet1/1/1
VLAN 4091: port-channel1000
VxLAN Virtual Network Identifier: 4091
Source Interface: loopback2(172.30.0.1)
Remote-VTEPs (flood-list): 172.30.0.0(CP)