nerdexam
Broadcom-VMware

2V0-621D · Question #109

After deploying a vSphere Platform Services Controller (PSC), an administrator is unable to install vCenter Server. The error displayed is: Could not contact Lookup Service. Please check…

The correct answer is A. Verify that the clocks on the host machines running the PSC, vCenter Server, and the vSphere C. Ensure that there is no firewall blocking port 7444 between the PSC and vCenter Server. The "Could not contact Lookup Service" error during vCenter Server installation, following PSC deployment, often indicates a problem with time synchronization or network connectivity, specifically firewall blocking ports, between the components.

Section 5 – Administer and Protect vSphere 6.x Resources

Question

After deploying a vSphere Platform Services Controller (PSC), an administrator is unable to install vCenter Server. The error displayed is:

Could not contact Lookup Service. Please check VM_ssoreg.log. Which two actions can be taken to correct this problem? (Choose two.)

Options

  • AVerify that the clocks on the host machines running the PSC, vCenter Server, and the vSphere
  • BConfigure a valid Identity Source for the Platform Services Controller in the vSphere Web Client.
  • CEnsure that there is no firewall blocking port 7444 between the PSC and vCenter Server.
  • DUninstall and reinstall the Platform Services Controller software.

How the community answered

(42 responses)
  • A
    81% (34)
  • B
    7% (3)
  • D
    12% (5)

Why each option

The "Could not contact Lookup Service" error during vCenter Server installation, following PSC deployment, often indicates a problem with time synchronization or network connectivity, specifically firewall blocking ports, between the components.

AVerify that the clocks on the host machines running the PSC, vCenter Server, and the vSphereCorrect

Time synchronization is critical for vSphere components, especially for SSO and Lookup Service communication, as a significant clock skew between the PSC, vCenter Server, and host machines can cause certificate validation failures and prevent successful lookup service registration.

BConfigure a valid Identity Source for the Platform Services Controller in the vSphere Web Client.

Configuring an Identity Source is an administrative task performed after vCenter Server is successfully installed and connected to the PSC, and it is not a prerequisite for the vCenter Server installation process itself to contact the Lookup Service.

CEnsure that there is no firewall blocking port 7444 between the PSC and vCenter Server.Correct

The Lookup Service, a core component of the PSC, communicates over specific ports, and a firewall blocking port 7444 between the vCenter Server and the PSC would prevent the vCenter Server installer from establishing contact during initial setup.

DUninstall and reinstall the Platform Services Controller software.

Uninstalling and reinstalling the PSC is a drastic measure and typically unnecessary for a "Could not contact Lookup Service" error, which is more commonly resolved by checking basic networking and time synchronization issues.

Concept tested: vCenter/PSC Lookup Service connectivity troubleshooting (time sync, firewall)

Source: https://docs.vmware.com/en/VMware-vSphere/6.0/com.vmware.vsphere.install.doc/GUID-88C43073-C6BB-4EEB-9572-1E7E674640EC.html

Topics

#Platform Services Controller#PSC#vCenter Server Installation#Lookup Service#Troubleshooting

Community Discussion

No community discussion yet for this question.

Full 2V0-621D Practice