Unable to add new Patch Token URL under lifecycle Manager in Vcenter Server

Products

• VMware vCenter Server
• VMware vCenter Server 8.0

Issue/Introduction

Adding Token URL (https://dl.broadcom.com/TokenID/PROD/COMP/ESX_HOST/main/vmw-depot-index.xml)  to the Lifecycle manager fails with error
"The Download Source https://dl.boradcom.com/TokenID/depot-index.xml is invalid or cannot be reached now"

Environment

VMware vCenter Server 7.x
VMware vCenter Server 8.x

Cause

The error typically occurs due to network connectivity issues between the Lifecycle Manager and the Broadcom download server. The specific causes could be one or more of the following:

1. Firewall Blockage: The firewall may be blocking the connection to the Broadcom URL, which prevents the Lifecycle Manager from accessing the necessary depot files.
   
   
2. Proxy Configuration: If a proxy server is used to manage network traffic, the proxy settings might be misconfigured or unable to handle secure connections (HTTPS). The default proxy settings in vSphere might be set to HTTPS, which could cause issues with retrieving the download source.

Resolution

• Ensure that the necessary Broadcom URLs are whitelisted in the firewall to allow uninterrupted communication between the Lifecycle Manager and the Broadcom server.
   Whitelist *.broadcom.com in the firewall
• If a proxy server is enabled, ensure that the proxy settings are correctly configured. On the vCenter Appliance Management Interface (VAMI), change the proxy protocol setting from HTTPS to HTTP
   

Additional Information

Token can be configured using the steps mentioned in ( https://knowledge.broadcom.com/external/article/390098 )