Unable to configure VMware Cloud Director after deployment

Products

• VMware Cloud Director

Issue/Introduction

• After deploying VMware Cloud Director (i.e. vcd), when connecting to https://<VMware Cloud Director IP>:5480 to proceed with configuration, the page fails to load with "<VMware Cloud Director IP> refused to connect" error. 
  
  
• When connecting to vcd console to check,  below messages can be found in /opt/vmware/var/log/firstboot:
  
  Checking for all required OVF parameters, for OS Configuration Phase
[Error] Not all required parameters for OS phase configuration were provided.
For more details, see: /opt/vmware/var/log/vcd/check-os-params.log


• Below messages can be found in /opt/vmware/var/log/vcd/check-os-params.log:
  
  Checking ovf parameters needed for proper OS and Network configuration
search_path ovf parameter not specified.
Number of missing parameters: 1
Not all required ovf parameters were specified, therefore skipping os configuration phase.

Environment

VMware Cloud Director 10.x

Cause

Domain search path parameter is not specified during vcd appliance deployment resulting in error during firstboot. 

Resolution

In this situation, the vcd appliance needs to be rebuilt and have domain search path parameter specified during re-deployment of vcd appliance. 

Normally the domain search path should be same as domain name.

Additional Information

For detailed steps to start up and configured vcd, please refer to:
Start Your VMware Cloud Director Appliance Deployment
Configure Your VMware Cloud Director Primary Appliance