In this step in the workflow of onboarding a Horizon pod to first-gen Horizon Control Plane services, you run the precheck.sh diagnostic tool to validate that the pod and Horizon Cloud Connector are both ready for the pairing process. By first running the diagnostics and remediating any blocking issues found in system components and configurations, you can maximize your chances of success with the pairing process.
Note: The precheck.sh diagnostic tool is only available for Horizon Cloud Connector 1.6 or later. If you have downloaded and deployed Horizon Cloud Connector 1.5 or earlier, disregard the following procedure and proceed directly to First-Gen Tenants - Complete Pairing the Horizon Pod with First-Gen Horizon Cloud Using the Horizon Cloud Connector Configuration Portal.
The precheck.sh diagnostic tool validates the health of the services and components that are required to pair the control plane with your Horizon pod successfully. In addition, the tool checks whether:
- The configurations related to certificates and proxy settings are correct.
- Connectivity of Horizon Cloud Connector with the control plane and with Horizon Connection Server can be established.
- Any SSL-related issues exist for Horizon Cloud Connector.
Prerequisites
Verify the following:
- You have completed the steps in First-Gen Tenants - Download and Deploy the Horizon Cloud Connector into Your Pod's Environment, including the steps to Enable SSH Access to the Horizon Cloud Connector Using a Command Line Interface and if you want to activate any of the cloud-hosted services, the steps to manually activate those services.
- The Horizon Cloud Connector virtual appliance is powered on.
Procedure
-
Open an SSH session to your deployed Horizon Cloud Connector virtual appliance.
-
Run the diagnostic tool using
sudoand theprecheck.shscript. Replace CS-FQDN with the fully qualified domain name (FQDN) of the pod's Connection Server.
Follow the steps based on your Horizon Cloud Connector version:
- For Horizon Cloud Connector version 2.5 and later, run
sudo /opt/horizon/bin/precheck.sh CS-FQDN - For Horizon Cloud Connector 1.6 through 2.4, locate the
precheck.shscript within the appliance's/opt/directory structure. Change directories to that location and run:sudo precheck.sh CS-FQDN
If the diagnostic tool discovers an issue that will prevent a successful pairing process, it reports the following information:
- Name of the problem component or service
- Status of the problem component or service
- Associated error message and details
- Suggested remediation steps, if any, to restore the component or service to a healthy and ready state.
Note: The diagnostic tool always reports one or both of the following expected conditions as part of its output. Both conditions are normal and expected at this stage of the onboarding workflow, and neither one blocks the pairing process.
Reported condition:
Component/Service Name: "Cloud Broker Client Service"
Status: "NOT_INITIALIZED"
Message: Service is not initialized.
This condition pertains to the control plane's Universal Broker service, which remains in the NOT_INITIALIZED state until it is enabled as described in Setting Up Horizon Universal Broker for Multi-Cloud Assignments. You can still successfully pair the Horizon pod with the when Universal Broker is in the NOT_INITIALIZED state. Therefore, this condition does not represent a blocking issue and you can disregard it.
Reported condition
Component/Service Name: "Connector Client Service"
Status: "FAIL"
Message: Connector service is initialized post on-boarding.
The Horizon Cloud Connector client service is initialized after you complete the pairing process, because the initialization process requires connectivity to the control plane. Therefore, the FAIL condition is expected at this stage of the onboarding workflow. In a successful pairing process, the Horizon Cloud Connector client service is initialized and the FAIL condition clears.
-
If the diagnostic tool reports an issue that interferes with the pairing process, investigate the affected component or service and perform the suggested remediation steps. As previously noted, you can disregard error conditions for "Cloud Broker Client Service" and "Connector Client Service" because they are not blocking issues.
As needed, repeat steps 2 and 3 to run the diagnostic tool again and troubleshoot problems until the tool does not report any blocking issues that prevent the pairing process. The Horizon pod and Horizon Cloud Connector are now ready for the pairing process.
Note: If you attempt the pairing process without first clearing any blocking issues reported by the diagnostic tool, the pairing process might fail.
-
Continue with the pod onboarding workflow by following the steps in First-Gen Tenants - Complete Pairing the Horizon Pod with First-Gen Horizon Cloud Using the Horizon Cloud Connector Configuration Portal.
Previous topic:When Keeping the CSMS Service is Deactivated in the Horizon Cloud Connector, How to Prevent the Sync Failed Message
Cette page vous a-t-elle été utile ?