"Disconnected depot: active" in Build > Software Depot after registering the Online Depot in VCF 9.1

Products

• VCF Operations

Issue/Introduction

• The Online Depot was registered without error in VCF Operations
• "Validation completed successfully. No errors found." was seen after clicking Validate in step 3. Submit the activation code
• Confirmed that the activation code from Business Services Console was used (not the download token used for previous version.)

Environment

• VMware Cloud Foundation (VCF) 9.1.0
• VCF Operations 9.1.0

Cause

The necessary URLs were not added to the allow list in the firewall protecting the environment resulting in the network traffic targeted to the Broadcom URLs being blocked.

Resolution

1. Work with the network security team in your environment to add the required URLs to the firewall allow list
   • Public URLs Required for Online Functionalities for VCF and vSphere Foundation
2. Restart the Software Depot service
   1. Log in to VCF Operations with an administrative account
   2. Navigate to Build > Lifecycle > VCF Management > Components and click Software depot
   3. Click the Actions menu and select Stop service
   4. Click View details... to monitor the shutdown task
   5. After the Task status: shows "Completed", click < Back (or navigate to Build > Lifecycle > VCF Management > Components and click Software depot)
   6. Click the Actions menu and select Start service
   7. Click View details... to monitor the startup task
   8. After the Task status: shows "Completed", navigate to Build > Software Depot and validate that "Online depot: active" is seen

 

To check connectivity to the required URLs for the Software Depot

1. Log in to the VCF Operations node as root via SSH or vSphere console
2. Test connectivity with curl to each URL

   1. curl -s -o /dev/null --cacert /etc/ssl/certs/a3418fda.pem -w "%{http_code}\n" https://dl.broadcom.com

      Expected response: 403

   2. curl -s -o /dev/null --cacert /etc/ssl/certs/3513523f.pem -w "%{http_code}\n" https://eapi.broadcom.com

      Expected response: 500

   3. curl -s -o /dev/null --cacert /etc/ssl/certs/5ad8a5d6.pem -w "%{http_code}\n" https://vvs.broadcom.com

      Expected response: 403

   4. curl -s -o /dev/null --cacert /etc/ssl/certs/3513523f.pem -w "%{http_code}\n" https://vsanhealth.vmware.com

      Expected response: 500

 

Additional Information

To check connectivity to the required URLs for other functions

1. Log in to the VCF Operations node as root via SSH or vSphere console
2. Test connectivity with curl to each URL

   1. curl -s -o /dev/null --cacert /etc/ssl/certs/dd8e9d41.pem -w "%{http_code}\n" https://projects.packages.broadcom.com

      Expected response: 302

   2. curl -s -o /dev/null --cacert /etc/ssl/certs/3513523f.pem -w "%{http_code}\n" https://vcsa.vmware.com

      Expected response: 404

   3. curl -s -o /dev/null --cacert /etc/ssl/certs/3513523f.pem -w "%{http_code}\n" https://auth.esp.vmware.com

      Expected result: 404