In this section, the additional VxRail nodes are deployed as the second VxRail cluster.

1. In a browser on the jump host, go to https://192.168.10.200 to connect to the VxRail Manager Deployment Wizard. The Welcome to VxRail screen displays, as shown.
   Note: If you are doing a remote deployment without a jump host, use the IP address you have configured on the VxRail Manager for the second cluster. See the Remote Deployment of VxRail with SmartFabric Services Deployment Guide for more information.
   
   

   

2. Click GET STARTED on the welcome screen.
3. On the EULA page, review the terms provided, and if you agree, check the Accept box and click NEXT.
4. On the Cluster Type page, select Standard Cluster (3 or more hosts) and Standard vSAN, then click NEXT.

   

   Note: Other cluster types are not supported with SFS.
   
   
5. On the Resources page, wait for the VxRail hosts for the second cluster to be discovered.
6. Select the VxRail nodes to be included in the second cluster by checking the box next to the service tag. All four nodes are selected in this example.
7. Under Top-of-Rack (TOR) Switch, set Automated VxRail Switch Configuration to Disabled.

   After the selections are made, the screen appears as shown in the following figure.

   

   Note: Be sure Automated Switch Configuration is set to Disabled before proceeding.
   
   
   Note: If you do not see the option to disable Automated VxRail Switch Configuration outlined in red above, open the SFS UI and go to Global Settings > Fabric Settings. The setting named VxRail Manager Integration in the SFS UI must be set to its default value, enable. If it is set to disable, click EDIT, change the setting to enable, and click SUBMIT > OK. (This SFS UI setting will be renamed to mDNS in a future release). In the VxRail Deployment Wizard, under Top-of-Rack (TOR) Switch, click the refresh icon. Set Automated VxRail Switch Configuration to Disabled as shown in the figure above.
   
   
8. Click NEXT.
9. On the Network Confirmation page, check the two boxes. This confirms the network has been configured per the previous sections of this guide.
10. Click NEXT.
11. On the Configuration Method page, select your preferred configuration method, Step-by-step user input, or Upload a configuration file. Either configuration method may be used.
12. Click NEXT.
13. Step through screens 7–12 (Global Settings through Virtual Network Settings) of the deployment wizard. All configuration choices used for the second VxRail cluster in this example are listed in the VxRail deployment settings – second cluster section.
14. Click NEXT.
15. On screen 13, the Validate Configuration page displays, as shown.

    

16. 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 about 10 minutes for a four-node cluster.
    
    

    When validation is complete, a message indicating whether validation was successful or not is displayed, as shown.

    

    Note: If validation is not successful, address the items that failed and validate again. Once validation passes, Dell Technologies recommends clicking the DOWNLOAD CONFIGURATION FILE button to save a JSON file with your VxRail settings.
    
    
17. Click NEXT.
18. Click DEPLOY CONFIGURATION.

    

    The Deployment starts, as shown.

    

19. Expand Show Details to view the deployment status.
    Note: If you are doing a remote deployment without a jump host, skip to step 31.
    
    
20. When the deployment is about 25% complete, the following message is displayed:

    

    The VxRail manager has moved from its default IP address, 192.168.10.200, to its new IP address on the external management network, 172.18.11.73 in this example.
21. Move the jump host port from the Client Management VLAN, VLAN 4091, to the external management VLAN, 1811 in this example, as follows:
22. Keep the VxRail deployment browser tab open. In a new browser tab, connect to the SFS UI.
23. In the SFS UI, select the Switches tab.
24. Under Fabric Switches, expand the leaf switch the jump host is connected to and expand Breakout Ports & Jump Port.
25. Click X JUMP PORT.
26. When prompted to delete the jump port, click DELETE.
27. Click + JUMP PORT.
28. In the Add Jump Port window:
    1. Enter a Name, such as Jump Host 1.
    2. Next to Interface Name, select the interface that the jump host is connected to.
    3. Next to Untagged Network, select the external management Network, VLAN 1811 in this example, as shown in the following figure:

       

29. Click ADD.
    Note: Ensure the jump host NIC has an IP address on the external management 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.
    
    
30. Return to the VxRail deployment browser tab.

    You are redirected to the new VxRail Manager IP address in the browser.

31. Continue the VxRail deployment as shown in the following figure:
    Note: You may need to refresh the browser window.
    
    

    

32. Deployment may take about 1 hour for a four-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 succeed.
    
    
33. If prompted, click the LAUNCH VSPHERE CLIENT (HTML5) button.
34. Log in using your vCenter credentials. In this example, the username is administrator@vsphere.local.

    The vSphere Client Inventory page appears, as shown. The second VxRail cluster is outlined in red.

    

    CAUTION: Review any warnings that may appear in the vSphere Client.