vCenter Lifecycle Management (vLCM) fails on remediating host fails on cannot download patches.

search cancel

book

calendar_today

VMware vCenter Server

vCenter Lifecycle Management (vLCM) fails to remediate ESXi and following error message seen on vCenter server cluster tasks event :
```
File download error: Downloading file: https://dl.broadcom.com/<old-Token>/PROD/COMP/ESX_HOST/main/vmw-depot-index.xml
```
The token appear invalid after validating on Broadcom Portal .
The previous token URL where removed from vCenter LCM and added new token URL which is reflecting on Broadcom Portal.
Restarted the update manager service but no change
service-control --restart vmware-updatemgr
You can download patches , vSphere Client Home page → Lifecycle Manager and selecting "ACTIONS" → Updates → Sync updates.

But when remediating esxi host it still picks old token URL

https://dl.broadcom.com/<old-Token>/PROD/COMP/ESX_HOST/main/vmw-depot-index.xml

The invalid token URL still holding in vCenter VUM Database.

To resolve the issue reset the VUM DB, refer the following steps.

Note : Backup the new token URL information as these are custom URLs, they will need to be re-added after the resetting VUM DB.

SSH to the vCenter via root
If not in BASH shell, switch to the BASH Shell
```
shell
```
Stop the VMware Update Manager Service
```
service-control --stop vmware-updatemgr
```
Depending on the vCenter version, run one of the following commands to reset the VMware Update Manager Database:
- vCenter Server Appliance 6.7/7.0/8.0:
```
python /usr/lib/vmware-updatemgr/bin/updatemgr-utility.py reset-db
```
Delete the contents of the VMware Update Manager Patch Store
```
rm -rf /storage/updatemgr/patch-store/*
```

Start the VMware Update Manager Service

service-control --start vmware-updatemgr

Additional information considering vSAN and NSX-T installed in a vLCM-enabled cluster refer the article.

thumb_up Yes

thumb_down No