Hi all
Thanks in advance
I´m trying to remove update manager v4.1 and I have this error:
Error 25061. Setup failed to remove the DSN used to access the local VMware vCenter Update Manafer database
Then click OK
and it rolling back
I review DSN and every think is OK
Have you got any suggestions?
VCenter 4.1
VUM 4.1
VCenter and VUM in the same Virtual Machine.
Regards.
Hi all,
I am using vCenter 6.0u3h on Windows server + Update Manager installed with the embedded MS SQL Express database option. Now Windows Update service sees it and recommends to apply patches and SP3 upgrade. Should I patch/upgrade the embedded database via Windows Update or should it be handled by future VUM upgrades instead?
Thanks in advance,
David
I have just installed update manager 5.1
I am trying to get the download settings working and download patch definitions
in the download settings section, the download source for virtual appliances shows as not connected
when I try and download, my status gets to 50% and then fails with error
Cannot download patch definitions.
the problem is this
http://vapp-updates.vmware.com/vai-catalog/index.html is not a valid virtual appliance download URL
anyone know how to resolve?
the status for the hostupdate esx components says connected
Al instalar el update 1 en VMWARE ESXi 6 sobre un servidore IBM es necesario reinstalar algun driver de red o en su caso la actualizacion lo incluye?
Hello,
I'm going nuts. I can't find the Scan Now function in the 6.7 U1 HTML5 Gui. I Select a host, select "Host updates", I can attach, detach, stage and remediate but the Scan button? Where is it?
On my 6.7 U1 hosts, there are currently 2 patches waiting for them. I have not scanned any hosts yet.
Now, the HTML5 Gui says 47 patches are waiting??? and the compliance status of both "Critical" and "Non Critical" Host patches is "unknown".
When I scan Now via the Flash GUI (because I can't find it in the HTML5 Gui) and then refresh the HTML5 Gui again, it will say "not compliant" and when selecting Stage or Remediate, will show the same 2 patches as the Flash GUI (instead of those silly 47).
What am I missing here?
Hello Everyone, of VM's
Can we schedule for Bulk VM's Hardware version upgrade at particular time ? I know we cn schedule the Hardware compatibility of a VM's but in host there might be multiple VM's running and we cant downtime for all VM's. Is there any option in VUM for scheduling the bulks VM's HW upgrade ? Any help is much appreciated.
Thanks
Vmk
Hi,
I have the following configuration :-
• Dell PowerEdge R630 Server
o Hypervisor: VMware ESXi 6.5 U2
o Guest OS : FreeBSD v8.4
o CPU : Intel Xeon E5-2680 v4 2.4 GHz
I'm using Intel provided RDRAND/RDSEED instructions for getting random numbers..
I wanted to know if the instruction are used in freebsd , whether hypervisor wil
override those Intel instruction RDRAND/RDSEED with its own information,
or the instruction will be directly processed by Intel CPU and data will be relayed back
to the guest os. (Hypervisor doesn't override).
I have some internet sources which says that to support lockstep mode, hypervisor may override
Intel RDRAND/RDSEED with its own implementation.
Can some one please clarify the behavior wrt VMware ESXi 6.5 U2 ?
Thanks.
Versions:
vCenter 5.5
Update Manager 5.5
Esxi 5.5
We have a client that has vCenter 5.5 installed using VUM (Yes I understand unsupported). I have seen in another question but no definitive answer hence my question as to the issue relating to the fact that version 4 of Microsoft's XML Parser engine (DLL) is no longer supported and needs to be removed / unregistered.
The vCenter server has both msxml3.dll and msxml6.dll installed with the CLSID pointing to msxml3.dll. On the post which I found referenced here: https://kb.vmware.com/s/article/2113837 it states that there were issues with upgrading to version 6 which and the download process for VUM.
My question is this: Is the vSphere vCenter client and COM written application (C++) or is it .NET written in C# and therefore uses different .NET assemblies and not COM?
I want to disable the version 4 by doing an unregister of the DLL via: regsvr32 /u msxml4.dll and also rename the file but I do not want to break the functionality of VUM. If version 6 msxml6.dll is already installed on the server will version 5.5 VUM work with this or does it require msxml4.dll specifically?
Thanks
Hi, when I access vCenter via vSphere client (html5), I can access vSphere update manager as the server and client are
automatically installed. However, when I access the same vCenter via vSphere web client (flex), I cannot acess vSphere
update manager. The service is running, but the client plug in is not installed. I clicked "check for new client plug-ins",
and nothing happened. Is there anything I am missing or configuration that I need to enable? Thanks!
According to vsphere 6.7 document, "The Update Manager client plug-ins for the vSphere Client and the vSphere Web Client require no installation. "
So how to access vSphere update manager in flex client? Thanks!
vCenter 5 / vUM 5
ESXi 5
Error msg in vCenter console when trying to Stage patches or Patch a server:
"Cannot download software packages from patch source. Check the events and the Update Manager log for download details"
This is a new setup, so this is the first time trying.
I have 3 baselines:
Critical Host
Non-Critical Host
HP Baseline
I DO NOT get the error when I stage or patch Just the Critical Host baseline.
I get the error when trying to stage the Non-Critical or HP patches.
And I can remediate the non-critical (maybe this is an order of execution issue .. remediate critical first...?)
But I get the same error if I try to stage or remediate the HP patches.
VUM did successfully connect and download the patches from the websites. I can see the files and metadata on the vUM server.
It seems the error refers to moving the patches from vUM server to the host.
I looked at the logs, but I don't see anything apparent.
Any ideas?
Thanks
when i patch hosts from the lcuster level and enable parallel remediation, why doest vcenter take into account how overloaded the hosts are? I have 9 hosts and it tries to put all the hosts into matiintenance mode. and other hosts now is maxes to 99% memory utilization because of this.
Hi,
I imported driver vib for ixgben driver version 1.7.15 (VMware Compatibility Guide - I/O Device Search) into 6.5 VUM patch repository (VCSA). Then I added this vib to a custom baseline, I did the same a while ago for version 1.7.10, but can't remember if I had same problems back then.
But I'm unable to install this vib,
vmware-vum-server-log4cpp.log:
[2019-05-28 12:24:48:693 'HostUpdateDepotManager' 140273770456832 INFO] [scanHost20, 1436] One or more VIBs mapping to Bulletin VMW-ESX-6.0.0-ixgben-1.7.15 have dependencies not installed on the host: xxxxxxxx (entity: host-39) and not part of the bulletin, marking as 'UNKNOWN' for DVS scan
I'm able to install the vib with cli without problems, only VUM is not liking it. Any idea why and how to resolve this? Using cli to rollout his vib to a larger number of hosts is not the most efficient way.
# esxcli software vib install -v /tmp/ixgben-1.7.15-1OEM.600.0.0.2768847.x86_64.vib
Installation Result
Message: The update completed successfully, but the system needs to be rebooted for the changes to be effective.
Reboot Required: true
VIBs Installed: INT_bootbank_ixgben_1.7.15-1OEM.600.0.0.2768847
VIBs Removed: INT_bootbank_ixgben_1.7.10-1OEM.600.0.0.2768847
VIBs Skipped:
# esxcli software vib get -n ixgben
INT_bootbank_ixgben_1.7.15-1OEM.600.0.0.2768847
Name: ixgben
Version: 1.7.15-1OEM.600.0.0.2768847
Type: bootbank
Vendor: INT
Acceptance Level: VMwareCertified
Summary: Network driver for Intel(R) 10 Gigabit NIC
Description: Native ixgben network driver for VMware ESXi
ReferenceURLs:
Creation Date: 2019-03-29
Depends: vmkapi_2_3_0_0
Conflicts:
Replaces:
Provides:
Maintenance Mode Required: False
Hardware Platforms Required:
Live Install Allowed: False
Live Remove Allowed: False
Stateless Ready: True
Overlay: False
Tags: module, driver
Payloads: ixgben
esxcli software vib get -n ixgben
INT_bootbank_ixgben_1.7.10-1OEM.600.0.0.2768847
Name: ixgben
Version: 1.7.10-1OEM.600.0.0.2768847
Type: bootbank
Vendor: INT
Acceptance Level: VMwareCertified
Summary: Network driver for Intel(R) 10 Gigabit NIC
Description: Native ixgben network driver for VMware ESXi
ReferenceURLs:
Creation Date: 2018-09-06
Depends: vmkapi_2_3_0_0
Conflicts:
Replaces:
Provides:
Maintenance Mode Required: False
Hardware Platforms Required:
Live Install Allowed: False
Live Remove Allowed: False
Stateless Ready: True
Overlay: False
Tags: module, driver
Payloads: ixgben
I'm trying to sort through the logging/UI to see why one specific host is incompatible.
The goal is to upgrade to vSphere 6.7. 1 of 5 hosts in the cluster shows incompatible with the upgrade, but I'm a little fuzzy as to why.
I've uploaded the most recent ESXi 6.7 to Update Manager, created and applied the baseline, then did a compliance check. This is what I see:
From the vib list, the only package on the incompatible host that's not on the rest is:
lsu-lsi-mptsas-plugin
Vice versa, there is one on the compatible hosts that isn't on the in compatible:
vmware-perccli-007.0127.0000.0000
The mptsas plugin wasn't actually be used, removing it didn't resolve the incompatible host flag when checking compliance.
Is there any one log that would clearly state why a host isn't compatible?
The 5 hosts above are all the same vendor and spec (CPU & Memory), and are config consistent as far as I can tell aside from this vib mentioned above.
Dear All,
earlier times it was possible to select single patches from a baseline to remediate or stage. I think since VCSA 6.x it's no more possible or I did not yet find how to do that.
Is there any way to select / deselect single patches from a baseline to stage / remediate to an host?
Thanks Wolfgang
Hello everyone,
I got a question about the update manager.
One of my customers got multiple clusters some with single host some with multiple hosts and wants to perform an update sheduled at 3:00 am
Is there any way to shedule an VM power off for the single host clusters?
With best regards
Robert Schneider
I can't seem to find anywhere how to do this anymore. If I go to the depreciated flash client, its still there. For the moment the workaround has been to maintenance mode the hosts and then do the remediation against each separately.. Hardly fast when you have many to do..
My Update Manager server is not internet facing. I downloaded VMware-vCenter-Server-Appliance-6.7.0.40000-14367737-updaterepo.zip. I believe this is the latest and greatest of patches and updates need for vSphere 6.7 please let me know if it is not and where I should pick the correct one at. I have turned off it to be able to download from https://hostupdate.mware.com yet it still shows trying to download at (Oct 21 2918) even though I have disabled this feature under patch setup. Instead, I uploaded it last night around 5:00.
Am I doing Offline Updates wrong all together?
Have some questions about VUM. We are upgrading several hosts from 6.5 to 6.7 using Dell Customized Images. We are noticing some of the NIC and HBA VIBs do not get upgraded, yet the lsi-msgpt3 does.
Can someone explain to me how and why this works?
Hi,
I am trying to update the esxi patch through update manager but i am getting the below error.
Esxi version - 6.5
vcenter version - 6.5
In esxupdate.log when checking compliance in VUM:
ValueError: VIBs ELX_bootbank_elx-esx-libelxima.so_12.0.1108.0-03 and ELX_bootbank_elx-esx-libelxima.so_12.0.1108.0-03 have unequal values of the 'payloads' attribute: '[elx-esx-libelxi: 1602.936 KB]' != '[elx-esx-libelxi: 1493.833 KB]
This is from a host that was installed with the 6.7U2 HPE Custom ISO then patched with the "critical" VUM baseline. It seems the baseline installs a conflicting vib which breaks VUM compliance checks from that point forward.
If I remove the vib with esxcli software vib remove -n elx-esx-libelxima.so, it allows VUM compliance scanning to resume but then the host reports as non-compliant against the critical patch baseline.
Is there a definitive fix for this? Can I somehow blacklist this vib within VUM? We don't even need it -- we don't have this hardware!