No VUM in vCenter 6.5
Easy way to update host with vCenter on it?
Hi,
I have two ESXi 6.5 hosts.
Host-1 - Dell PowerEdge T620
Host-2 - Dell PowerEdge T440
vCenter 6.5 appliance is on Host-2 for the moment, but to be able to use VUM to upgrade the host, the host must be in maintenance mode and all VM's powered down and because of that I can't have vCenter on Host-2 when I should do the update on that host.
I don't have a license with vMotion but thinking of getting that if this method works so I did try the "Migrate" in vCenter anyway, but I got a lot of warnings with CPU incompatibility on Host-1 that I should move vCenter to.
The target host does not support the virtual machine's current hardware requirements.
To resolve CPU incompatibilities, use a cluster with Enhanced vMotion Compatibility (EVC) enabled. See KB article 1003212.
3DNow! PREFETCH and PREFETCHW are unsupported.
MOVBE is unsupported.
FMA3 is unsupported.
CPUID faulting is not supported.
Supervisor Mode Execution Protection (SMEP) is unsupported.
RDRAND is unsupported.
Instructions to read and write FS and GS base registers at any privilege level are unsupported.
Half-precision conversion instructions (F16C) are unsupported.
Fast string operations (Enhanced REP MOVSB/STOSB) are unsupported.
Is this even possible to fix? Will that EVC thing fix this?
I also tried the "Quick Migration" in Veeam and it did not complain about any incompatibility, maybe I should try that one instead.
Well, is there an easier method? I know I can download VIB's and install them from the ESXi shell, but it's a lot of updates and I don't wan't to install them all one by one.
Thanks.
Update Manager requirements
We recently migrated from a Vcenter 5.5 Windows server to the 6.0 VCSA. On the windows server Update Manager was using a local copy of full installation of MS SQL. I am preparing to install Update Manager 6 on separate Windows servers. We have 30 hosts and 800 vms at our site. Will SQL express suffice for the Update Manager database or will we need to use a full install of SQL server. I've opened a support call with VMware about this but days later I still haven't gotten an answer. Frustrating!
vCenter UI becomes unresponsive
Hi All,
On a newly installed vSAN 6.7 cluster, i'm experiencing intermittent response from the vCenter UI. It would return after ~30-45 seconds, during the UI being unavailable pings are still responsive, ruling out network connectivity. Both vCenter and hosts sit in the same subnet so they do not traverse the firewall for intercommunication.
It's a 3 node Hybrid cluster with the only existing VM deployed being vCenter. Things i've tried are:-
1. Rebooting the vCenter appliance.
2. Running thorough diagnostics at the vendor (Dell R830s) hardware layer on all components, all nodes passed successfully.
3. Migrate the Appliance off to different host servers within the cluster.
4. Have two hosts up at any one time, while shutting off the third (eliminate memory/disk issues). All produced the same issue, regardless of which node was hosting the VM.
Functionality wise, it works however, it is intermittent as described above. Anyone has any ideas/suggestions on this one?
Unable to modify Update Manager Proxy settings in vCenter 6.7
Just upgraded our development vCenters from VCSA 6.5 U1g to 6.7 and I'm running into issues with VUM. While trying to add the latest HPE vibsdepot URLs, I noticed there doesn't appear to be a way to modify VUM download sources and settings in the HTML5 Client yet. I then went into the Flash/FLEX client and noticed that the Proxy settings section shows a red error with text "A general system error occurred". If you click the "Edit..." button it gives you error message "An internal error has occurred - Error #1009". Restarting the VUM service and the Flex client service on the VCSA did not resolve the issue. Anyone run into this yet?
VCSA 6.5 U2 Update Manager UI glitch
Hi guys,
Basically I've upgraded our VCSA to 6.5 U2, and want to upgrade one of the hosts using Update Manager.
Uploaded ESXi 6.5 U2 iso image, then wanted to check if there any conflicting VIBs.
I know they are, because I updated same host in other datacenter yesterday, it just took me a while to mount an ESXi iso to virtual KVM console to update the server and during the upgrade one vib was in conflict.
I found that checking for conflicting VIBs can be done (as upgrade itself) using VUM.
But once I uploaded ESXi and then clicked on the host and then Update Manager tab, upper section is so collapsed (just under , os I can't see anything.
Does anyone expereince the same UI glich that I did?
Update Manager trying to install ESXI650-Update01 and ESXi650-Update02 when host already at 8294253
setting in vSphere 6.5u1 that allows to stop scanning of Virtual Appliances?
Recently we have migrated our vCenters to VCSA's 6.5u1 along with NSX 6.3.2 (vShield) after deploying the Guest Introspection getting a message in the tasks section is "cancel discovering virtual appliance" unable to cancel the same.
please provide your suggestions for resulotiion.
update manager with no vmotion and local disk
Hi
I have a 6.5 environment with 10 different hosts. All hosts use local storage and have only one VM on them, expect for one that has vcenter on it. If I use update manager to restart the host, will v center shutting down cause a problem. I'm thinking its may be better to just use the zip file and esxcli commands to update the host, but I like to avoid that if possible. Its a unique environment meant for one application.
Can Update Manager upgrade the ESXi host it's running in as a VM?
That's the question. Here's some background. We have been a completely virtualized environment for several years. 2 ESXi 5.5 hosts collocated at different data centers connected of course by a site-to-site VPN. The VPN itself is provided by VMs and vCenter runs in a VM at one of the sites as will Update Manager if we go ahead with installing it. If the vCenter and/or VPN VMs are down we have a very cool backup method of accessing and managing ESXi and its console. Some of you reading the rest of this will be tempted to suggest architecting our environment differently but we're very happy with the way it is thank you very much :-) Appreciate all responses but really just answered in this specific question.
The reason we want Update Manager is really just to be able to easily update ESXi in the future without getting into the console and running commands, etc. I realize from documentation and blogs on this subject that ESXi may need to go into maintenance mode and shut down VMs running on it (not a cluster so no migration) at which point ESXi will either lose connection to Update Manager (if the remote host) or shutdown Update Manager (if the local host). So the question is, is the upgrade process managed by Update Manager an atomic operation at this crucial point or a sequence of operations dependent on the continued connectivity and control of Update Manager. Ddoes ESXi then perform the upgrade and reboot independently - which would be great - or is it going to just sit there in maintenance mode waiting for more instructions from the now disconnected/shutdown Update Manager.
Your answers are much appreciated.
Roadmap/future for patching VMware appliances
VUM 6.7 deprecates VMWare appliance patches - what is the VMware preferred solution for automated appliance patching?
Baselines for 6.5U1
Hi,
Since 6.5U2 still is not supported by all vendors yet, is there any way to determine if a patch (Except the 6.5 Update 2 Complete patch) will update the ESXi to 6.5 U2?
I'm about to do an upgrade from 6.0U3 to 6.5U1, and would like to have it fully patched afterwards without upgrading to 6.5U2. Can anyone point me in the right direction? Is it just a matter of excluding patches that came out after 6.5 U2, or is there newer patches that we need to install as well?
Regards,
Andreas
VMware update manager - patches do not match ESXi Type
Hi,
i am willing to upgrade my ESXi hosts with the newest security patches available (Version 6.0 Builds 5251623 and 6856897).
i have a direct internet connection and i am trying to install the patches using the default internet repositories.
after successfully downloading the patches i see security patches available only for embedded ESXi's, while the ESXis installed in my environment are only installable (i also validated it with KB 2014558).
When i try to create a new baseline / edit an existing one and set it to dynamic or fixed i see zero patches available for esx 6.0.0.
What are the possible reasons?
i would be happy to get some assistance for solving this issue ASAP! Thanks!
UPdate manager embedded with VCSA 6.5 and UMDS
Hi,
We have upgraded vCenter from 6 to 6.5 version and after upgrade when trading to download patches from External UMDS getting below error.
Incompatible repository. Provide a repository from VMware vSphere Update Manager Download Service Incompatible repository. Provide a repository from VMware vSphere Update Manager Download Service
Please suggest.
odbc database user password
any idea how I can find the password to my odbc connection to the vum database? I lost it and dont want to reset or change the password
does DELL use HPE drivers ?
Hi,
the last 10 years I only had HPE hardware now I have my first Dell (M630) server. I just installed the VMware 6.7 image provided by Dell. Now I want to update the server to the newest versions.
First I did a 'check compliance' and then I wanted to remediate the needed updates. But there are two HPE software bundles automatically chosen - that confuses me. Is that normal that Dell get's HPE drivers? Or is there any problem with the Update Manager of vCenter 6.7?
It's the predefined non-critical Baseline.
Thanks Wolfgang
vCSA 6.5 - What are my options for running standalone update manager
Hi
Recently migrated from Windows / vCenter 6.0 to vCSA 6.5.
The installation is not connected to the Internet. With 6.0, we used standalone Update Manager Download Service (UMDS). Can we continue to use this and will it happily download 6.5 updates even though it's version 6.0?
Thanks
Vsphere - major and minor version
Hello.
I have a question about versions:
what are major and minor versions?
-ESXi 5.0, 6.0 are major versions?
-ESXi 5.1, 5.5, 6.5, 6.7 are minor versions?
I am confused about this.
VCSA 6.7 Update Manager fails to download patch definitions when behind proxy
VCSA 6.7.0.14000 Build 9451876
VMware Update Manager, Version = 6.7.0, Build = 9031744
When I test the proxy settings under 'Download Settings', it succeeds for www.microsoft.com, and fails for www.vmware.com (presumably because it gets a 301 Moved Permanently response), but both case use the proxy server successfully.
Clicking 'Download Now' generates no network traffic and shows this task result:
Web sites: https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml; hosting the patch definitions and patches cannot be accessed or have no patch data. Check the Internet connectivity.
Is there anything else I can do to get this working, or am I waiting on an update to fix this?
LOG /var/log/vmware/vmware-updatemgr/vum-server/vmware-vum-server-log4cpp.log:
['miscUtil' 139839201699584 INFO] [miscUtilPosix, 118] Value for registry.proxy.UseProxy is: 1
['miscUtil' 139839201699584 INFO] [miscUtilPosix, 118] Value for registry.proxy.ProxyServer is: http://proxy.my.example.domain
['miscUtil' 139839201699584 INFO] [miscUtilPosix, 118] Value for registry.proxy.ProxyPort is: 8080
['miscUtil' 139839201699584 INFO] [miscUtilPosix, 118] Value for registry.proxy.ProxyUserName is:
['miscUtil' 139839201699584 INFO] [miscUtilPosix, 116] Value for registry.proxy.ProxyPassword is: ********
['DownloadMgr' 139839201699584 DEBUG] [downloadMgr, 549] Url: https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml, Download destination: /tmp/vci6jGU8O
['DownloadMgr' 139839201699584 DEBUG] [downloadMgr, 400] Inserted download job {139838699463824} to queue
['DownloadMgr' 139839201699584 DEBUG] [downloadMgr, 420] Current download count: 0
['DownloadMgr' 139839201699584 DEBUG] [downloadMgr, 436] Current download count: 1
['DownloadMgr' 139839201699584 DEBUG] [downloadMgr, 442] Adding download job {139838699463824} to scheduler
['DownloadMgr' 139839201699584 DEBUG] [downloadMgr, 462] Waiting for download job {139838699463824} to finish...
['DownloadMgr' 139839201965824 INFO] [downloadMgr, 603] Executing download job {139838699463824}, url=https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml
['httpDownload' 139839201965824 ERROR] [httpDownloadPosix, 649] curl_easy_perform() failed: cURL Error: Couldn't connect to server, Unsupported proxy scheme for '[http://proxy.my.example.domain]:8080'
['DownloadMgr' 139839201965824 ERROR] [downloadMgr, 629] Executing download job {139838699463824} throws error: curl_easy_perform() failed: cURL Error: Couldn't connect to server, Unsupported proxy scheme for '[http://proxy.my.example.domain]:8080'
Update Manager could not download virtual appliance upgrade metadata using UMDS repository
Hello
We have an error trying to download patch definitions when using a UMDS exported repository. We have a vSphere 6.5 U1 install that does not have Internet access. It consists of several ESXi Hosts, vCSA with separate PSC and vROPs.
We use UMDS installed on a separate internet connected server to download HOST and Appliance upgrades.
vmware-umds.exe -v
VMware Update Manager Download Service 6.5.0.40982 Build = 8305924
vmware-umds.exe -G
[standard URLs]
Host patch content download: enabled
Host Versions for which patch content will be dowloaded:
embeddedEsx-6.5.0-INTL
Virtual appliance content download: enabled
So we refresh this on a scheduled task - approx 38GB. When we want to export the repository, we connect a USB disk (X:) and use the follwoing:
vmware-umds.exe -E --export-store x:\umds
This exports the repository as expected. The files are then copied to a local IIS server that the vSphere 6.5 cluster has access to. We have enabled directory browsing and can access the files using http://webserver:8000. We can see the files as expected.
In Update Manager, in the down Download Setting, we change to Use a shared repository and specify the URL above. Update Manager validates this. In the Download Sources pane, when we click Download Now, we can see the Download patch definitions task run but we get an error:
Cannot download patch definitions.
Related events:
Task: Download patch definitions.
Successfully downloded host patch definitions, New patches: 87
vaupgrade/__valm-consolidated-index__.xml
Could not download virtual appliance upgrade metadata for http://webserver:8000/
Could not download virtual appliance upgrade metadata.
So it looks like the host patch definitions are OK, but not the appliance definitions.
Does anyone know why this would be the case?
Many thanks