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 58.
Use the vSphere Client to add the VxRail node as follows:
- Connect to the vCenter in a browser and launch the vSphere Client.
- In the vSphere Client, right-click the cluster and select VxRail > Add VxRail Hosts.
- After a brief scan, the fourth VxRail node is discovered, outlined in red as shown in the figure below.
- Click ADD HOST.
- In the Discovered Hosts window, check the box next to the service tag, as shown in the following figure.
- Click NEXT.
- In the User Credentials window, enter the vCenter and switch REST_USER credentials, as shown in the figure below.
- Click NEXT.
- In the NIC Configuration window, the default values are used, as shown.
- Click NEXT.
- In the Host Settings window, the hostname, IP address, and credentials for the new host are specified.
- Click NEXT.
- (Optional) In the Host Location window, the Rack Name and Rack Position may be entered. These fields are left blank in this example.
- Click NEXT.
- In the Network Settings window, provide the vSAN and vMotion IP addresses for the host, as shown in the following figure.
- Click NEXT.
- Review the settings in the Validate window. If no changes are needed, click VALIDATE. Validation may take 2 to 5 minutes.The Success message displays when the validation passes.
- An option to put the added host in maintenance mode is provided. In this example, this option is kept in the default No setting.
- Click FINISH.
On the Add VxRail Hosts page, 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 the figure below.
Note: The host expansion process may take 10 to 15 minutes to complete. - When complete, the Add VxRail Hosts page temporarily shows Host expansion complete.Note: This message may only appear on the screen for about one minute.
- The fourth VxRail node displays in the VxRail cluster as shown in the figure below.CAUTION: Review any warnings that may appear in the vSphere Client.
(Optional) Verify the interface connected to the new VxRail node has been automatically added to the VxRail networks on the leaf switches in Rack 2. 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.
The output below confirms the leaf switch interface connected to the new VxRail node, ethernet1/1/1, has been automatically placed in all VxRail virtual networks/VLANs.
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)