Unable to patch the vCenter via VAMI as it fails to download the updates from Broadcom public repositories
search cancel

Unable to patch the vCenter via VAMI as it fails to download the updates from Broadcom public repositories

book

Article ID: 390120

calendar_today

Updated On:

Products

VMware vCenter Server VMware vCenter Server 7.0 VMware vCenter Server 8.0

Issue/Introduction

  • vCenter Server patching via VAMI fails to download the updates from Broadcom public repositories.

  • VAMI Updates tab will show any of following error messages:
    The vCenter Server is not able to reach the specified URL. Ensure that the vCenter Server is connected to the internet, the specified URL is correct, and the latest version(s) is available on the VMware online repository. If the issue persists, please contact VMware Support.



  • Error seen on VAMI UI "Check the URL and try again."

    Steps: Login to VC VAMI UI (https://vcenter_server_fqdn/IP:5480) > Update .

         

  • Authentication failure. Enter a valid user name and password, and try again.


Validation:

  • Error seen from vCenter "Configured repository is not accessible due to network connectivity or incorrect URL. Verify the repository settings."

    Steps for vCenter 7.x: Select vCenter > Updates >  Update Planner.


  • Error seen from vCenter "Configured repository is not accessible due to network connectivity or incorrect URL."

    Steps for vCenter 8.x: select vCenter > Updates >  Prechecks > select target version "SELECT VERSION" .

 

Environment

VMware vCenter Server 7.x

VMware vCenter Server 8.x

VMware vCenter Server 9.x

Cause

  • As public facing repository URLs and authentication mechanisms are changing, download URLs are no longer common but unique to you. 
  • Download URLs need to be re-configured.

Resolution

  1. Download the Token from Broadcom Support Portal by following the steps in VCF Authenticated downloads Configuration Update Instructions. If the token has already been acquired, apply the same by following below instructions.

  2. Update the Token in Download URL

    Note: Scripted method to update the URLs are available in Authenticated Download Configuration Update Script.

    1. Login to VC VAMI UI (https://vcenter_server_fqdn/IP:5480)
    2. Navigate to Update tab
    3. Click on SETTINGS
    4. Use the Default URL to construct a new URL with the Downloaded Token as listed below.

      1. vCenter Server 7.x


        From:

        Default:
        https://vapp-updates.vmware.com/vai-catalog/valm/vmw/8d167796-34d5-4899-be0a-6daade4005a3/<current_version>.latest

        To:

        Specified:
        https://dl.broadcom.com/<downloadToken>/PROD/COMP/VCENTER/vmw/8d167796-34d5-4899-be0a-6daade4005a3/<current_version>/

        e.g.:

        From:

        Default        :
        https://vapp-updates.vmware.com/vai-catalog/valm/vmw/8d167796-34d5-4899-be0a-6daade4005a3/7.0.3.00800.latest/

        To:

        Specified:
        https://dl.broadcom.com/<downloadToken>/PROD/COMP/VCENTER/vmw/8d167796-34d5-4899-be0a-6daade4005a3/7.0.3.00800/

      2. vCenter Server 8.x

        From:

        Default:
        https://vapp-updates.vmware.com/vai-catalog/valm/vmw/8d167796-34d5-4899-be0a-6daade4005a3/<current_version>.latest

        To:

        Specified:
        https://dl.broadcom.com/<downloadToken>/PROD/COMP/VCENTER/vmw/8d167796-34d5-4899-be0a-6daade4005a3/<current_version>/

        e.g.:

        From:

        Default:
        https://vapp-updates.vmware.com/vai-catalog/valm/vmw/8d167796-34d5-4899-be0a-6daade4005a3/8.0.3.00400.latest/

        To:

        Specified:
        https://dl.broadcom.com/<downloadToken>/PROD/COMP/VCENTER/vmw/8d167796-34d5-4899-be0a-6daade4005a3/8.0.3.00400/

      3. vCenter Server 9.0

        From:

        Default:
        https://vapp-updates.vmware.com/vai-catalog/valm/vmw/8d167796-34d5-4899-be0a-6daade4005a3//<current_version>/

        To:

        Specified:
        https://dl.broadcom.com/<downloadToken>/PROD/COMP/VCENTER/vmw/8d167796-34d5-4899-be0a-6daade4005a3/<current_version>/

        e.g.:

        From:

        Default:
        https://vapp-updates.broadcom.com/vai-catalog/valm/vmw/8d167796-34d5-4899-be0a-6daade4005a3/9.0.0.0/

        To:

        Specified:
        https://dl.broadcom.com/<downloadToken>/PROD/COMP/VCENTER/vmw/8d167796-34d5-4899-be0a-6daade4005a3/9.0.0.0/

        Note: Replace <downloadToken> with the actual downloaded token id.

    5. Update the New URL in Specified, and click Save
    6. Releases should get listed from the new entitled URL

Notes:

    • The custom URL is not preserved post migration upgrade, FBBR restore and VCHA failover
    • If there is a proxy device configured between vCenter and the internet, ensure it is configured to allow communications to the new URL
    • Further patches automatically update this URL. For example, if 8.0.3.00400 is patched to 8.0.3.00500, the default URL will change to end in 8.0.3.00500.
    • When custom / specified URL is saved with token in VAMI. CLI patching will not pick this URL.

      Follow below steps to use the updated URL -

      set the current url from appliancesh

      #update.set --currentURL https://dl.broadcom.com/<downloadToken>/PROD/COMP/VCENTER/vmw/8d167796-34d5-4899-be0a-6daade4005a3/8.0.3.00000.latest
      then install patch.
      #software-packages install --url


      • On 70x VCSA

        Specified URL used:https://dl.broadcom.com/<downloadToken>/PROD/COMP/VCENTER/vmw/8d167796-34d5-4899-be0a-6daade4005a3/7.0.3.02200

        1. If you set Specified URL in VAMI UI, if it is not reflecting in the config file /etc/applmgmt/appliance/update.conf and when you run update.get it still points to vapp-updates Default URL,

        Set the Specified URL using update.set from appliancesh as a workaround.
        Without setting Specified URL, stage/installwill continue to use the Default URL


        2. Another observation is, if source vCenter server is 7.0 Update 2 or earlier, and if Specified URL is, https://dl.broadcom.com/<downloadToken>/PROD/COMP/VCENTER/vmw/8d167796-34d5-4899-be0a-6daade4005a3/7.0.3.02200

        vCenter Server is upgraded to 7.0.3.02200 instead of 7.0.3.02300.
        To work around this behaviour, set the Specified URL manually using update.set in appliancesh.

Additional Information

Powered by Wolken Software