This section demonstrates the deployment of the VLC-Holo-Site-1 nested lab using VLC.
There are two different methods for performing the deployment:
- Method 1 demonstrates how to perform the deployment using the VLC GUI
- Method 2 demonstrates how to perform the deployment using VLC from the command line
Perform only one of the methods to deploy the environment.
The previous procedures were completed successfully.
Obtain the IP address of the ESXi server used to host the environment. Until DNS services can be established, communication will have to be performed with the IP address.
Note that these tasks are performed from the Holo-Console VM deployed earlier. They can be carried out by directly accessing the Holo-Console via the ESXi console option, or via RDP to the Holo-Router IP address.
Method 2: Deploy VCF using VLC command line (Option 2)
The second method to deploy VCF with VLC is by using the command line.
This task is not needed to be performed if VCF was already deployed using Method 1 above.
[Step 1] Configure VLC configuration file
This step configures the VLC INI file used for command line (headless) mode. This example assumes deploying a pod named “Holo-A” which runs on port group VLC-A-PG.
- On the Holo-Console, use the Windows File Manager to navigate to C:\VLC\VLC-Holo-Site-1
- Open Holo-A1-v45.ini for editing
- Change the values for the following attributes as needed:
- ds: Datastore for this pod
- esxhost: IP of ESXi host
- labDNS: Provide IP of DNS server if 184.108.40.206 is not accessible.
- nestedVMPrefix: This defines the prefix to be used for all the VMs deployed by VLC.
- netName: This specifies the name of the port group to be used
- password: This specifies the password for the ESXi host to deploy to
- Note the configuration specifies the use of the add_3_hosts.json file which provides the information for VLC to deploy an additional three hosts into the nested VCF environment
- Save the file with a name representing the pod configuration. The name used in this example is Holo-A1-v45.ini
[Step 2] Deploy using VLC command line mode
- From within the Holo-Console, click on Windows Start Menu->Windows PowerShell->Windows PowerShell
- Type the following command at the prompt:
- Enter the following command:
.\VLCGui.ps1 -iniConfigFile .\Holo-A1-v45.ini -isCLI $true
- This starts the VCF deployment with VLC in headless mode. The VCF deployment takes approximately three hours to complete
- Wait until the process successfully completes and the message for accessing the SDDC Manager is displayed
[Step 3] Test VLC Deployment
- From the Holo-Console, open Chrome and click on the Managed bookmarks and select the SDDC Manager
- Acknowledge the security warning by clicking on Advanced followed by Proceed to sddc-manager.vcf.sddc.lab (unsafe)
- Acknowledge the second security warning by clicking on Advanced followed by Proceed to vcenter-mgmt.vcf.sddc.lab (unsafe)
- Login as the user firstname.lastname@example.org with the password VMware123!
- Uncheck the VMware CEIP box
- Verify the page displayed resembles the following
- Click on hosts
- Close the Tasks pane
- Notice the four host VCF Management domain and the three additional unassigned hosts
[Step 4] Set FTT=0 on Nested VSAN datastore. (Optional)
The following step is recommended to reduce out of space issues on the nested environment. As this is a lab environment, and running on underlying SSD, it is typically acceptable to reduce redundancy in the nested environment
- Using the vSphere Web Client, click to expand the menu, then click Policies and Profiles
- Select VM Storage Policies -> vSAN Default Storage Policy -> Edit
- Leave Name and Description as is and click Next
- On the vSAN Availability tab, set Failures to Tolerate to No Data Redundancy then click Next
- Click next on Storage Compatibility
- Review setting and click Finish
- Select Now when prompted on Reapply to VM’s, then Yes
[Step 5] Reboot Holo-Console VM
- Using the vSphere Web Client, select the Holo-A-Console and click Restart to reboot the VM. NOTE: This step is required to clear temporary Holo-Console network routing. After reboot Holo-Console receives routing, DNS, NTP, etc from Cloud Builder within the pod.