Adding the Token URLs (
https://dl.broadcom.com/<Token_ID>/PROD/COMP/ESX_HOST/main/<patch_source>.xml)
to the Lifecycle manager fails with the error message:
"The Download Source https://dl.broadcom.com/<Token_ID>/PROD/COMP/ESX_HOST/main/<patch_source>.xml is invalid or cannot be reached now"
VMware vCenter Server 7.x
VMware vCenter Server 8.x
The error typically occurs due to network connectivity issues between the Lifecycle Manager and the Broadcom download server.
Potential causes could be one or more of the following:
dl.broadcom.com
using the curl
command below:curl -v dl.broadcom.com:443
Note: The curl command would return a "400 Bad Request" error, which is expected in this case because a plain HTTP request was sent to an HTTPS port.
To verify the SSL certificate chain used by dl.broadcom.com, you can run the following command from the VCSA:
openssl s_client -connect dl.broadcom.com:443
Token can be configured using the steps mentioned in the KB article below:
VCF authenticated downloads configuration update instructions
The following article walks through various troubleshooting steps related to the VCF Authentication Download Token functionality:
VCF Authenticated Downloads Token Troubleshooting Guide