Hi,

I have a cluster I patched with a consiatent build #. I added a new host and patched the critical & non-critical patches, then is was at a higher 6.7 build #.

How can I build a baseline and go back to the older build number I had before? I'm having a little trouble figuring this out in Update Manager.

Thank you.

Hello,

i can't install one driver update on my host.

In this Log: vmware-vum-server-log4cpp.log

i found:

[2020-05-28 14:54:24:127 'HostUpdateDepotManager' 140415677196032 INFO]  [vibDownloaderImpl, 382] Now downloading https://hostupdate.vmware.com/software/VUM/PRODUCTION/addon-main/addon/HPE/vib20/qlnativefc/Marvell_bootbank_qlnativefc_4.1.9.0-1OEM.700.1.0.15525992.vib

[2020-05-28 14:54:24:127 'DownloadMgr' 140415677196032 DEBUG]  [downloadMgr, 586] Url: https://hostupdate.vmware.com/software/VUM/PRODUCTION/addon-main/addon/HPE/vib20/qlnativefc/Marvell_bootbank_qlnativefc_4.1.9.0-1OEM.700.1.0.15525992.vib, Download destination: /storage/updatemgr/patch-store/hostupdate/HPE/vib20/qlnativefc/Marvell_bootbank_qlnativefc_4.1.9.0-1OEM.700.1.0.15525992.vib

[2020-05-28 14:54:24:127 'DownloadMgr' 140415677196032 DEBUG]  [downloadMgr, 437] Inserted download job {140415501480432} to queue

[2020-05-28 14:54:24:127 'DownloadMgr' 140415677196032 DEBUG]  [downloadMgr, 457] Current download count: 0

[2020-05-28 14:54:24:127 'DownloadMgr' 140415677196032 DEBUG]  [downloadMgr, 473] Current download count: 1

[2020-05-28 14:54:24:127 'DownloadMgr' 140415677196032 DEBUG]  [downloadMgr, 479] Adding download job {140415501480432} to scheduler

[2020-05-28 14:54:24:127 'DownloadMgr' 140415678793472 INFO]  [downloadMgr, 640] Executing download job {140415501480432}, url=https://hostupdate.vmware.com/software/VUM/PRODUCTION/addon-main/addon/HPE/vib20/qlnativefc/Marvell_bootbank_qlnativefc_4.1.9.0-1OEM.700.1.0.15525992.vib

[2020-05-28 14:54:24:128 'DownloadMgr' 140415677196032 DEBUG]  [downloadMgr, 499] Waiting for download job {140415501480432} to finish...

[2020-05-28 14:54:24:783 'httpDownload' 140415678793472 INFO]  [httpDownloadPosix, 658] curl_easy_perform() succeeded - url: https://hostupdate.vmware.com/software/VUM/PRODUCTION/addon-main/addon/HPE/vib20/qlnativefc/Marvell_bootbank_qlnativefc_4.1.9.0-1OEM.700.1.0.15525992.vib

[2020-05-28 14:54:24:787 'HostUpdateDepotManager' 140415678793472 ERROR]  [vibDownloaderImpl, 222] Computed checksum of file /storage/updatemgr/patch-store/hostupdate/HPE/vib20/qlnativefc/Marvell_bootbank_qlnativefc_4.1.9.0-1OEM.700.1.0.15525992.vib.part differs from the expected checksum

[2020-05-28 14:54:24:787 'DownloadMgr' 140415678793472 ERROR]  [downloadMgr, 693] Validation failed for file downloaded from: https://hostupdate.vmware.com/software/VUM/PRODUCTION/addon-main/addon/HPE/vib20/qlnativefc/Marvell_bootbank_qlnativefc_4.1.9.0-1OEM.700.1.0.15525992.vib

[2020-05-28 14:54:24:787 'DownloadMgr' 140415678793472 INFO]  [downloadMgr, 614] Download job {140415501480432} finished, bytes downloaded = 0

[2020-05-28 14:54:24:787 'DownloadMgr' 140415677196032 DEBUG]  [downloadMgr, 505] Download job {140415501480432} finished

[2020-05-28 14:54:24:787 'DownloadMgr' 140415677196032 DEBUG]  [downloadMgr, 518] Removing download job {140415501480432} in queue

[2020-05-28 14:54:24:787 'DownloadMgr' 140415677196032 DEBUG]  [downloadMgr, 537] Current download count: 0

[2020-05-28 14:54:24:788 'HostUpdateDepotManager' 140415677196032 ERROR]  [vibDownloaderImpl, 407] Error downloading vib file from https://hostupdate.vmware.com/software/VUM/PRODUCTION/addon-main/addon/HPE/vib20/qlnativefc/Marvell_bootbank_qlnativefc_4.1.9.0-1OEM.700.1.0.15525992.vib Error:downloading file: https://hostupdate.vmware.com/software/VUM/PRODUCTION/addon-main/addon/HPE/vib20/qlnativefc/Marvell_bootbank_qlnativefc_4.1.9.0-1OEM.700.1.0.15525992.vib failed, 0 bytes downloaded.

What can be the problem?

Kind regards

Stefan

Hi,

I'm using an Essentials license.  Here's what I've got:

(2) esxi 6.0u2 hosts

(1) Windows server 2016 running vCenter server.

I'm using the same ISO I used to install vCenter to try and install Update manager on the vCenter server.  During the installation it installed, SQL 2012 express, starts to install Update manager and at about half way through, it rolls back the changes and ends with a message, "The wizard was interrupted before VMware vSphere Update manager could be completely installed."

If I watch the status during the installation, I can see it first install Java, then install Jetty web server.  As soon as it starts to install "Virtual storage volume driver" it's interrupted and rolls back the install.

I've already rebooted and disabled the A/V.  Anyone know what's happening and how to get past this?

We need to update the qlogic drivers for our HP ESXi hosts (ESXi 6.7).  I've uploaded the patch to a new baseline to deploy, but for some reason this patch is also showing for the Non-Critical Host Patches baseline.  When I scan our Cisco UCS hosts for updates, the Non-Critical baseline now shows as non-compliant with one patch to install, which is the qlogic patch for the updated drivers.  The UCS blades do not have any qlogic devices.  I haven't tried remediating one of the UCS hosts yet.  I would like to be able to remove the qlogic patch from the Non-Critical baseline to avoid any possible issues.  When I check in Update Manager, I only have the option to remove it from the custom baseline I created.

Hi all,

I logged took a VM snapshot of my VCSA 6.7 U3c, logged in to my VCSA Appliance console using https://vctr67rs.xxxx.com:5480, took an NFS backup, staged and installed the last of 3 updates available, since in the screen it says they are cumulative and you can install the latest.

Well, the upgrade completed successfully and vCenter rebooted, the build was updated to 16243230, but the Update tab on the ESXi servers are gone.

I clicked on Menu > Shortcuts and I don't see the VMware Update Manager icon there anymore, how is that possible?

Any of you run into this issue?

Thanks

Mark

Why does the Update Manager of vCenter 6.7 list this Host as Incompatible for this upgrade: VMware-ESXi-6.7.0-Update3-15160138-HPE-Gen9plus-670.U3.10.5.5.25-Mar2020.iso which is HPE own Custom ESXi Image?

Same issue on the other ProLiant DL380 Gen10 we have but on the 6 ProLiant DL360 Gen10 we the Host are listed as Non-Compliant which is as expected.

Best regards

Peter Rasch Lageri

UCL

Hello,

we have currently an issue with our single Dell Server. currently we installed ESXI Version 6.7.0 Build 16075168 and Vcenter 6.7.0.32000 Build Number 14070457, but we are always getting the message:

Vmware Vcenter server is installed on the virtual machine and DRS is disabled on the cluster

there is no cluster installed and we went through the following link:

https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.update_manager.doc/GUID-8ECDD0CC-8426-44F9-A283-301F957D88A2.html

and

https://communities.vmware.com/thread/615825

but the issue is not solved. what can we do to solve this issue?

where can we verify, if there is a cluster enabled or was a Cluster enabled somewhere? Currently there is not cluster configured on the single Host.

Hello,

I imported one vib in the VMware Update Manager (VUM). This vib was a newer version of one driver. However, after many tests we realized we don't need the updated driver. So, I would like to remove this vib/baseline I imported directly in VUM. However, I don't find any method to remove an imported vib/baseline in VUM. Any idea?

Thanks in advance,

Christian

After installing U3 on our VCSA 6.7 we're having issues upgrading the ESXi hosts to U3.  The "Update Manager" is asking for an ISO file, but all of the downloads from VMware's Update website only downloads a ZIP file.

https://my.vmware.com/group/vmware/patch#search

VMware is asking me to download from the full package area of the website, but those files are dated back to 8/2019 and doesn't have the current updates.  The problem is the update website only downloads ZIP files and the main website has both available, but they are older updates.

https://my.vmware.com/web/vmware/downloads/details?productId=742&downloadGroup=ESXI67U3

Is there a method in ESXi 6.7U2 hosts to update using the ZIP files?  Update Manager only allows ISO files, but there are no ISO files on the first link to the update page only the second link.

Right now I have another problem regarding the zip files.  When I try to burn them to CD/DVD the individual files within the ISO file are placed there instead of the ISO file Itself.

I want to update the hosts using the latest files up to April 2020.

Hi i'm getting an error when trying to check compliance on my hosts in vCenter Update Manager.

Any ideas?

I already checked the endpoint http://192.168.1.3:9084/vum/repository/hostupdate/vmw/vmw-ESXi-6.7.0-metadata.zip

I can access this file through the broweser.

This is the esxupdate.log output:

2020-07-02T06:26:22Z esxupdate: 2163364: downloader: INFO: Downloading http://192.168.1.3:9084/vum/repository/hostupdate/vmw/vmw-ESXi-6.7.0-metadata.zip to /tmp/tmpq4h1y7_q

2020-07-02T06:26:22Z esxupdate: 2163364: esxupdate: ERROR: An esxupdate error exception was caught:

2020-07-02T06:26:22Z esxupdate: 2163364: esxupdate: ERROR: Traceback (most recent call last):

2020-07-02T06:26:22Z esxupdate: 2163364: esxupdate: ERROR:   File "/build/mts/release/bora-16316930/bora/build/esx/release/vmvisor/esxupdate/lib64/python3.5/site-packages/vmware/esximage/Downloader.py", line 244, in _getfromurl

2020-07-02T06:26:22Z esxupdate: 2163364: esxupdate: ERROR:   File "/build/mts/release/bora-16316930/bora/build/esx/release/vmvisor/esxupdate/lib64/python3.5/site-packages/vmware/esximage/Downloader.py", line 188, in _retry

2020-07-02T06:26:22Z esxupdate: 2163364: esxupdate: ERROR:   File "/build/mts/release/bora-16316930/bora/build/esx/release/vmvisor/esxupdate/lib64/python3.5/site-packages/vmware/esximage/Downloader.py", line 208, in _download_to_file

2020-07-02T06:26:22Z esxupdate: 2163364: esxupdate: ERROR:   File "/build/mts/release/bora-16316930/bora/build/esx/release/vmvisor/esxupdate/lib64/python3.5/site-packages/vmware/esximage/Downloader.py", line 180, in _urlopen

2020-07-02T06:26:22Z esxupdate: 2163364: esxupdate: ERROR:   File "/build/mts/release/bora-16316930/bora/build/esx/release/vmvisor/sys-boot/lib64/python3.5/urllib/request.py", line 466, in open

2020-07-02T06:26:22Z esxupdate: 2163364: esxupdate: ERROR:   File "/build/mts/release/bora-16316930/bora/build/esx/release/vmvisor/sys-boot/lib64/python3.5/urllib/request.py", line 484, in _open

2020-07-02T06:26:22Z esxupdate: 2163364: esxupdate: ERROR:   File "/build/mts/release/bora-16316930/bora/build/esx/release/vmvisor/sys-boot/lib64/python3.5/urllib/request.py", line 444, in _call_chain

2020-07-02T06:26:22Z esxupdate: 2163364: esxupdate: ERROR:   File "/build/mts/release/bora-16316930/bora/build/esx/release/vmvisor/sys-boot/lib64/python3.5/urllib/request.py", line 1282, in http_open

2020-07-02T06:26:22Z esxupdate: 2163364: esxupdate: ERROR:   File "/build/mts/release/bora-16316930/bora/build/esx/release/vmvisor/sys-boot/lib64/python3.5/urllib/request.py", line 1257, in do_open

2020-07-02T06:26:22Z esxupdate: 2163364: esxupdate: ERROR:   File "/build/mts/release/bora-16316930/bora/build/esx/release/vmvisor/sys-boot/lib64/python3.5/http/client.py", line 1224, in getresponse

2020-07-02T06:26:22Z esxupdate: 2163364: esxupdate: ERROR:   File "/build/mts/release/bora-16316930/bora/build/esx/release/vmvisor/sys-boot/lib64/python3.5/http/client.py", line 307, in begin

2020-07-02T06:26:22Z esxupdate: 2163364: esxupdate: ERROR:   File "/build/mts/release/bora-16316930/bora/build/esx/release/vmvisor/sys-boot/lib64/python3.5/http/client.py", line 268, in _read_status

2020-07-02T06:26:22Z esxupdate: 2163364: esxupdate: ERROR:   File "/build/mts/release/bora-16316930/bora/build/esx/release/vmvisor/sys-boot/lib64/python3.5/socket.py", line 576, in readinto

2020-07-02T06:26:22Z esxupdate: 2163364: esxupdate: ERROR: ConnectionResetError: [Errno 104] Connection reset by peer

2020-07-02T06:26:22Z esxupdate: 2163364: esxupdate: ERROR:

2020-07-02T06:26:22Z esxupdate: 2163364: esxupdate: ERROR: During handling of the above exception, another exception occurred:

2020-07-02T06:26:22Z esxupdate: 2163364: esxupdate: ERROR:

2020-07-02T06:26:22Z esxupdate: 2163364: esxupdate: ERROR: Traceback (most recent call last):

2020-07-02T06:26:22Z esxupdate: 2163364: esxupdate: ERROR:   File "/build/mts/release/bora-16316930/bora/build/esx/release/vmvisor/esxupdate/lib64/python3.5/site-packages/vmware/esximage/Transaction.py", line 83, in DownloadMetadatas

2020-07-02T06:26:22Z esxupdate: 2163364: esxupdate: ERROR:   File "/build/mts/release/bora-16316930/bora/build/esx/release/vmvisor/esxupdate/lib64/python3.5/site-packages/vmware/esximage/Downloader.py", line 335, in Get

2020-07-02T06:26:22Z esxupdate: 2163364: esxupdate: ERROR:   File "/build/mts/release/bora-16316930/bora/build/esx/release/vmvisor/esxupdate/lib64/python3.5/site-packages/vmware/esximage/Downloader.py", line 246, in _getfromurl

2020-07-02T06:26:22Z esxupdate: 2163364: esxupdate: ERROR: vmware.esximage.Downloader.DownloaderError: ('http://192.168.1.3:9084/vum/repository/hostupdate/vmw/vmw-ESXi-6.7.0-metadata.zip', '/tmp/tmpq4h1y7_q', '[Errno 104] Connection reset by peer')

2020-07-02T06:26:22Z esxupdate: 2163364: esxupdate: ERROR:

2020-07-02T06:26:22Z esxupdate: 2163364: esxupdate: ERROR: During handling of the above exception, another exception occurred:

2020-07-02T06:26:22Z esxupdate: 2163364: esxupdate: ERROR:

2020-07-02T06:26:22Z esxupdate: 2163364: esxupdate: ERROR: Traceback (most recent call last):

2020-07-02T06:26:22Z esxupdate: 2163364: esxupdate: ERROR:   File "/usr/sbin/esxupdate", line 239, in main

2020-07-02T06:26:22Z esxupdate: 2163364: esxupdate: ERROR:     cmd.Run()

2020-07-02T06:26:22Z esxupdate: 2163364: esxupdate: ERROR:   File "/build/mts/release/bora-16316930/bora/build/esx/release/vmvisor/esxupdate/lib64/python3.5/site-packages/vmware/esx5update/Cmdline.py", line 105, in Run

2020-07-02T06:26:22Z esxupdate: 2163364: esxupdate: ERROR:   File "/build/mts/release/bora-16316930/bora/build/esx/release/vmvisor/esxupdate/lib64/python3.5/site-packages/vmware/esximage/Transaction.py", line 85, in DownloadMetadatas

2020-07-02T06:26:22Z esxupdate: 2163364: esxupdate: ERROR: vmware.esximage.Errors.MetadataDownloadError: ('http://192.168.1.3:9084/vum/repository/hostupdate/vmw/vmw-ESXi-6.7.0-metadata.zip', None, "('http://192.168.1.3:9084/vum/repository/hostupdate/vmw/vmw-ESXi-6.7.0-metadata.zip', '/tmp/tmpq4h1y7_q', '[Errno 104] Connection reset by peer')")

2020-07-02T06:26:22Z esxupdate: 2163364: esxupdate: DEBUG: <<<

Hello,

Can someone share step by step guide/blog explaining how can we update the firmware and driver versions for storage controller using the VMware Update manager on a VSAN environments. (We are using HPE servers as HW)

Hello,

The VUM, when you attach it to an esxi host.

Migrate the vm with vmotion before mounting the server in maintenance?

Cluster with 2 esxi hosts, 6.7U3.

HA, without DRS

regards,

Hello Experts,

For the update of the esx through VUM, do you recommend to use the predefined template Critical Host Patches

Or is it too risky? and would it be better to use a custom one and slow down on the patches?

I don't want to break anything...

Hi,

Are the predefined Critical Host Patches and vSAN Cluster baselines applicable when using custom vendor ESXi images?

(They show as non compliant but are these really meant to work/tested with vendor custom ESXi?)

If not how should one check for updates when using custom vendor ESXi images and can these checks/downloads be integrated in VUM?

Dell/HP are typical examples where custom images are used so not sure if VUM is still applicable to patch such vendor ESXi images.

Thanks

I've been trying to figure this out for a little while now but I keep getting stuck. I've been trying to make a script that will update move vms then update the host but I can't get the host update part to work. I keep getting this error and I really don't know which logs to look in or what other things to try.

I did recently update from 6.7 to 7

Update-Entity : 7/16/2020 9:45:01 AM    Update-Entity           Remediate Inventory on entity 'esxi04' failed with following error: ''registry.proxy.' is invalid or exceeds the maximum number of characters permitted.'.

If anyone has any suggestions I'm all ears

Hello Team VMware,

today, I want to try the new vLCM in combination with HPe iLO Amplifier to firmware patching my ESXi hosts.

I successfully installed the HPe iLO Amplifier appliance and let it communicate with the vCenter.

I also uploaded the 3 latest HPe SPP firmware into the appliance but I can´t use it in the vCenter.

When I press "Add" for the Online Software Depot I get the following error:

Fetching of online depot URL failed. Depot URL not found in the SPP details.

Is somebody aware about that or got the HPe iLO Amplifier with VUM to fly?

vCenter 7: 16386335
ESXi 7: 16324942
Amplifier: 1.70

I really appreciate your help in advance.

Greetings

KKvss

VMware Update Manager (VUM) has an option to "Stage" patches to a Host.  This is supposed to copy patches to the Host ahead of time so that when you have your maintenance window you can install patches immediately without having to wait for them to be downloaded.

I have not had good luck with Staging patches. It seems like there are always some patches that do not get staged.  Worse, I think (but have not confirmed) that the Host re-downloads everything (even patches identified as "staged").

What causes patches to not get staged?  Maybe there are certain patches that cannot be staged -- if so is there a way for me to identify which patches cannot be staged ahead of time?

I am running vCSA 6.7.0.44100 (Build 16275304).

Can anyone explain how patching vSphere 7 LCM cluster image is done?

I understand how you set up the first image, add the addons etc..

But using baselines, you get patches regulary monthy or more often, while the ISO-updates used for images are released only when Vmware release a new minor update version, maybe every third month.

If you use a OEM ISO image from certain manufacturers that delay is even longer, maybe two-three months longer on top of that.

Basicly two questions comes out of that:

* How are the LCM cluster image "patched" when Vmware release the patches, similar to baselane updates?

* Should the base image be Vmware ESX image only, or OEM ESXi image (kind of defeating the Vendor Addon part of LCM)?

I am getting this error message for VCSA 7.0 - Update Planner "Unexpected error occurred while fetching the updates"

Also getting errors under "Interoperability" - Unexpected error occurred while fetching the interoperability details

I have tried:

"SSH into VCSA 7.0 and run the below command:

rm /etc/applmgmt/appliance/software_update_state.conf

After removing the file, VCSA patched successfully."

Also

Resetting VMware Update Manager Database on a vCenter Server Appliance:

VMware Knowledge Base

I am now stuck at why this update planner is no longer working.

Any help would be appreciated on this on.

Hello. We have recently upgraded vCenter to v6.5 and we are now upgrading our ESXi hosts from v6.0 to v6.5

Using VUM,  I can perform two remediations, the first to do the upgrade to v6.5 and the second to then install the Critical Host patches. This gets me to ESXi 6.5 P04 Build 15256549.

I believe it is possible to perform both an upgrade and updates in a single remediation operation. I have created a Baseline group containing my Custom ESXi ISO and the Critical Host patches baseline. But when I go through the remediate wizard, the patches shown are for v6.0 and not for v6.5. VUM has scanned the host and seen that some v6.0 patches are required but these cease to be required once the upgrade to v6.5 is performed. Allowing the remediation to run performs the upgrade only.

What I need VUM to do is to perform the upgrade and then scan for missing v6.5 patches and then install those.

Is this possible?

Thanks in advance for any assistance.

Mark Bell