During bring-up, the management domain is created on the ESXi hosts specified in the deployment configuration spreadsheet. The Cloud Foundation software components are automatically deployed, configured, and licensed using the information provided.
- Log in to the Cloud Foundation Builder VM with your admin credentials by navigating to https://Cloud_Builder_VM_IP
- Click Upload Config File. Select the completed parameter sheet and click Upload.
- After the file is uploaded, click Validate to validate the uploaded file.
The following audit tasks are performed and validation results are displayed on the UI.
- SDDC JSON validation
Validates JSON correctness, syntax, null values, and missing fields or components.
- License validation
Validates format, validity, and expiry for ESX, VSAN, vCenter Server, NSX, and Log Insight license keys.
- Password validation
Validates specified passwords. Checks for minimum length, invalid characters, and format.
- ESXi Host Version
Validates ESXi version installed on the hosts and compares against the VCF-EMS manifest located in /opt/evosddc/bundle/scripts/manifest.json on the Cloud Foundation Builder VM.
- vSAN Disk Availability
Validates that required disks for VSAN are available for use.
- Network IP Pools
Validates the following:
Pool defines enough IP addresses such that there is one IP address available for each host used for bring-up.
Start and end of IP inclusion pools are within the subnet specified for vSAN and vMotion.
IP addresses provided in inclusion pool are not in use.
- Cloud Builder Readiness
Validates that Cloud Builder has the correct NTP and DNS configuration.
- Network configuration
Validates CIDR to IP address validity, IP addresses in use, gateways, invalid or missing VLANs, invalid or missing MTU, IP pools, and network spec availability for all components.
- Host validation
Validates SSH access and policy, NTP configuration and policy, DNS configuration, VMNIC availability, vSwitch availability, VM network portgroup , and VLAN check on each host.
- DNS validation
Validates forward and reverse lookup for all hosts in bringup json.
- Network connectivity validation
Validates that the vSAN and vMotion VLANs, MTUs, and gateways specified in the parameter sheet are correctly configured.
- NTP configuration Validation
Validates NTP configuration for all ESX hosts.
To access the bring-up log file, SSH to the Cloud Foundation Builder VM as root and open the /opt/vmware/bringup/logs/vcf-bringup-debug.log file.
If there is an error during the validation and the Next button is grayed out, you can either make corrections to the environment or edit the JSON file and upload it again. Then click Re-Try to perform the validation again.
If any warnings are displayed and you want to proceed, click Acknowledge and then click Next.
- SDDC JSON validation
- Click Begin Bring-Up.
During the bring-up process, the following tasks are completed.
The status of the bring-up tasks is displayed in the UI. You can download the list of tasks by clicking Download.After bring-up is completed, a green bar is displayed indicating that bring-up was successful. A link to the SDDC Manager UI is also displayed.
- PSC, vCenter Server, vSAN, vRealize Log Insight, and NSX components are deployed.
- The management domain is created, which contains the management components - SDDC Manager, all vCenter Servers, and NSX Managers and Controllers.
If there are errors during bring-up, see Troubleshooting Cloud Foundation Deployment for guidance on how to proceed.
- Navigate to the SDDC Manager Dashboard by clicking the link displayed on the UI.
- Verify the following:
- View management domain details.
- Log in to vCenter Server and verify the management cluster, vSAN cluster, and deployed VMs.
- Power off the Cloud Foundation Builder VM.
The Cloud Foundation Builder VM includes the VMware Imaging Appliance, which you can use to install ESXi on additional servers after bring-up is complete. You can delete the Cloud Foundation Builder VM to reclaim its resources or keep it available for future server imaging. If you delete it now, you can always redeploy it when you need the VMware Imaging Appliance.Caution: Do not modify or delete any vDS or port groups, or modify the fefault configuration.