Broadcom / Vmware VCSA and Lifecycle Manager Updates cannot be downloaded (due to missing download token)

 

(Important Update: Changes to How You Download VMware Software Binaries - VMware Cloud Foundation (VCF) Blog)

It is necessary, to generate a download token in Broadcom Support Portal to get updates for VCSA or ESXi.

 

Generate Donwload Token:

1. Login to Broadcom Portal
2. Go to Quick Links „Generate Download Token)
3. Select Site ID and klick “Generate Token”

 

 

 

vCenter Update: VCSA-Settings

 

1. Login to VCSA (https://vcenter_server_fqdn/IP:5480)
2. Change to Update
3. Settings
4. Copy the yellow part of the Download URL
1. https://vapp-updates.vmware.com/vai-catalog/valm/vmw/XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXX/<current_version>.latest
5. Change to „Specified“ and create a new Download URL using the token and the part you have copied:
1. https://dl.broadcom.com/<downloadToken>/PROD/COMP/VCENTER/vmw/XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXX/<current_version>.latest

 

Now, the Update should work.

 

ℹ️ Extended Info from Broadcom:

• Further patches automatically update this URL. For example, if you patch 8.0.3.00400 to 8.0.3.00500, the default URL will change to end in 8.0.3.00500.

 

So, no further changes should be necessary.

 

 

See also:

Error: "The vCenter Server is not able to reach the specified URL" vCenter Server patching via VAMI fails to download the updates from online repositories

 

 

 

 

ESXi Update: Lifecycle Manager-Settings

 

1. Login to vCenter Client and navigate to Lifecycle Manger
2. Go to „Settings“ - „Administration“ - „Patch Setup”
3. Deactivate all VMware Download Sources
4. Add the following new Download Sources:
1. https://dl.broadcom.com/<DownloadToken>/PROD/COMP/ESX_HOST/main/vmw-depot-index.xml
2. https://dl.broadcom.com/<DownloadToken>/PROD/COMP/ESX_HOST/addon-main/vmw-depot-index.xml
3. https://dl.broadcom.com/<DownloadToken>/PROD/COMP/ESX_HOST/iovp-main/vmw-depot-index.xml
4. https://dl.broadcom.com/<DownloadToken>/PROD/COMP/ESX_HOST/vmtools-main/vmw-depot-index.xml
5. Restart Update Manager Service in VCSA (ssh VCSA service-control --restart vmware-updatemgr) | alternatively via VCSA GUI
6. Download Updates „Lifecycle Manger“ - „ACTIONS“ -  „Sync Updates“

 

See also:

"A general system error occurred: Failed to download VIB(s): Error: HTTP Error Code: 403", vLCM fails to download the ESXi patches and images from online repositories

 

 

Problems using LCM for SPP Updates after changing Hosts to UEFI/Secure Boot on HPE HW prior Gen11

After changing Boot Settings to UEFI/Secure Boot on HPE HW prior to Gen11, phoenix is unable to boot due to missing SecureBoot Keys, so FW Upgrades via LCM are not possible.

To fix this, get the Key:

https://download.nutanix.com/kbattachments/Nutanix_Secure_Boot_v3.cer

put it on a USB Stick. Insert the Stick in a Server USB Port (not ILO USB)

enter RBSU on the affected Server:

Enter Maintenance Mode, Reboot the Server

press F9

Enter System Configuration

BIOS/Plattform Configuration (RBSU)

Server Security

Secure Boot Settings

Advanced Secure Boot Options

KEK - Key Exhange Key

Enroll KEK Entry

Enroll KEK using File

File Systems on attached Media

Choose your USB Device

Locate the File

Commit Changes and Exit

After enrolling, you can view KEK Entrys:

You should see the Nutanix Entry now.

Leave RBSU (F12 Save and exit) and continue normal Boot

You are able to Update FW through LCM now.

Change Cluster an Storagecontainer from RF2 to RF3

 You can change your FT Level from 1N/1D to 2N/2D (if you have 5 or more Hosts) in the Prism GUI:

Then you have to change the RF at Storagecontainerlevel as well:

show all Container:

nutanix@NTNX-x:~$ ncli
<ncli> ctr list

Change RF to 3:

nutanix@NTNX-x:~$ ncli

<ncli> ctr edit name=CONTAINERNAME rf=3

for the Nutanix Management Share you have to login as admin:

nutanix@NTNX-x:~$ ncli -h true

<ncli> ctr update name=NutanixManagementShare rf=3 force=true