Hi,
I have a newly installed vCenter 6.5 appliance but I can't find VUM anywhere.
The "VMware vSphere Update Manager" service is running and in good health.
I can't find anything with Update Manager in the Client Plug-Ins och vCenter Server Extensions.
Thanks.
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.
Hi all, I have a vCenter 5.5 Update Manager which does not have internet access. We have open up firewall rules for it to reach vmware.com
On the firewall we have allow the traffic to the below on port 80 & 443. So far we don't see any traffic blocked, except the connection attempt is incomplete
204.51.149.4
208.91.0.132
On telnet, we are able to successfully telnet most except vmware.com port 443.
Currently the Update Manager is still unable to reach vmware.com, is there any missing ports or IP ?
I have log 3 cases with VMware and looking at the alternative to build a patch repository server which have internet access.
Would anyone be able to advise what ports is required between the VC & this patch repository server ?
I am getting database temporarily unavailable when enabling the update manager plugin
any idea?
I change the service account from local system to a domain service account and same issue
Hi,
I have VUM 5.1 u3 and I can't update one ESXi with it. ESXi version is 5.1 u2. When I run remediate task it fails after some time with an error that VUM was not able to put host into maintenance mode. If I put this host into maintenance mode manualy, VUM is able to install required updates. So how can I fix this situation? Thanks.
Hi,
VCSA Appliance (6.0) External PSC
VCSA Appliance (6.0) vCenter
VUM 6.0 (1 x Windows 2012 R2 running SQL 2014 and 1 x Windows 2012 R2 with VUM installed)
Open SSL Root and Subordinate CA
I've replaced the SSL certs for the PSC with no issues, the VC and hosts are all looking good:-)
In order to replace the SSL certs for VUM I've followed KB 1023011 and replaced the self signed certs with certs signed by an OpenSSL Subordinate CA. When I open the VI client and enable the VUM plugin I get a certificate error. If I open the PFX and import it into my personal cert store the full chain, subordinate and root is there and all are trusted. If I browse via https to another server where I've replaced the SSL cert with one that has been signed by the same CA the browser doesn't moan.
Questions:
1. Does the error indicate that my PC doesn't trust the cert or that the vCenter doesn't support the cert?
2. If it's likely to be that the vCenter isn't trusting the cert how do I install the Root CA certificate into the keystore on the vCenter? The PSC already has it and is trusting it, otherwise it would not be handing nicely signed certs to the esxi hosts.
3. The cert that has been issued for VUM has the dns name of the VUM server in the SAN part of the cert but not in the issued to. Is that likely to be a problem?
4. The CSR that was generated for VUM was not generated from the VUM server, instead it was done from the workstation where he has OpenSSL installed. Is that likely to be an issue?
As a side note KB 1023011 has no mention of being the right process for 5.5, let alone 6.0!
Many thanks,
Gerg
I have a test environment in which I recently installed VUM 6.0, as well as VCenter 6. VUM is not showing up in either client, and I'm at a loss a to how to fix it at this point. The plug in is showing as registered in the web client.
Recently we have upgraded our vCenter to 5.5 from 5.1.
After up gradation we are not able to remediate multiple esxi host in one cluster.
We also tried multiple remediation option.
I've built a new vCenter 6.0/Update Manager setup.
I'm trying to upload my first ESXi image (ESX 5.5 Update 3a) But it errors after uploading saying:
"Failed to import data"
Google points me to KB 2097168 which says to make sure update manager is as new as the image you're uploading. Well, in this case, it is!
Suggestions?
GTG
I have just installed VMware Replication appliance a few days ago on my virtual environment.
Now every time Update manager starts a scan. The Discover virtual appliance task failed with an unknown error.
Looking at the log4cpp.log file i found this entry
'VADiscovery' 6204 ERROR] [vaDiscovery, 479] Error during discover VA: Crypto Exception: error:02001002:system library:fopen:No such file or directory:unable to load ssl\vm-10973\cert.pem
'SingleVADiscoveryTask.SingleVADiscoveryTask{302}' 6204 ERROR] [singleVADiscoveryTask, 174] Discover callback received an exception: Crypto Exception: error:02001002:system library:fopen:No such file or directory:unable to load ssl\vm-10973\cert.pem
'SingleVADiscoveryTask.SingleVADiscoveryTask{302}' 6204 ERROR] [singleVADiscoveryTask, 232] SingleVADiscoveryTask{302} encountered error: Crypto Exception: error:02001002:system library:fopen:No such file or directory:unable to load ssl\vm-10973\cert.pem
does someone knows what this error means ?
I am at a lost on how to resolve this.
Hello,
I have a problem with installing
Device Drivers for HP Custom ESXi 6.0.0 Image v600.9.1
Device Drivers for HP Custom ESXi 6.0.0 Image v600.9.2
Device Drivers for HP Custom ESXi 6.0.0 Image v600.9.3
Device Drivers for HP Custom ESXi 6.0.0 Image v600.9.30
When staging this packages I get an error message with the info to look into the Log Files.
Device Drivers for HP Custom ESXi 6.0.0 Image v600.9.4 are installed.
ESXi Version is from Custom HP Image VMware-ESXi-6.0.0-Update1-3073146-HP-600.9.4.34-Nov2015.
I did some checking with the log and found out the following vibs are missing.
QLogic_bootbank_ima-qla4xxx_500.2.01.31-1vmw.0.3.100400.vib
QLogic_bootbank_scsi-qla4xxx_644.55.34.0-1OEM.550.0.0.1331820.vib
Should I manual install the missing vibs?
Thanks for your help in advance.
Regards,
Dieter
The Log show the following entries:
[2015-12-09 13:33:15:813 'HostUpdateDepotManager' 13716 INFO] [scanHost20, 1261] Bulletin: hpq-driver-bundle-600.9.1.39 Release Type: extension Status: Missing ( vib: Broadcom_bootbank_misc-cnic-register_1.710.30.v55.1-1OEM.550.0.0.1331820: obsoleted by Host vib: Broadcom_bootbank_net-bnx2_2.2.5f.v55.6-1OEM.550.0.0.1331820: obsoleted by Host vib: Broadcom_bootbank_net-bnx2x_2.710.39.v55.2-1OEM.550.0.0.1331820: obsoleted by Host vib: Broadcom_bootbank_net-cnic_2.710.35.v55.5-1OEM.550.0.0.1331820: obsoleted by Host vib: Broadcom_bootbank_net-tg3_3.136h.v55.1-1OEM.550.0.0.1331820: obsoleted by Host vib: Broadcom_bootbank_scsi-bnx2fc_1.710.35.v55.7-1OEM.550.0.0.1331820: obsoleted by Host vib: Broadcom_bootbank_scsi-bnx2i_2.710.30.v55.4-1OEM.550.0.0.1331820: obsoleted by Host vib: Brocade_bootbank_scsi-bfa_3.2.3.0-1OEM.550.0.0.1198610: obsoleted by Host vib: Emulex_bootbank_elxnet_10.2.298.5-1OEM.550.0.0.1331820: obsoleted by Host vib: Emulex_bootbank_ima-be2iscsi_10.2.250.1-1OEM.550.0.0.1331820: obsoleted by Host vib: Emulex_bootbank_lpfc_10.2.340.18-1OEM.550.0.0.1331820: obsoleted by Host vib: Emulex_bootbank_scsi-be2iscsi_10.2.250.1-1OEM.550.0.0.1331820: obsoleted by Host vib: Hewlett-Packard_bootbank_scsi-hpdsa_5.5.0.12-1OEM.550.0.0.1331820: obsoleted by Host vib: Hewlett-Packard_bootbank_scsi-hpsa_5.5.0.74-1OEM.550.0.0.1331820: obsoleted by Host vib: Hewlett-Packard_bootbank_scsi-hpvsa_5.5.0-90OEM.550.0.0.1331820: obsoleted by Host vib: Intel_bootbank_net-igb_5.0.5.1-1OEM.550.0.0.1198611: obsoleted by Host vib: Intel_bootbank_net-ixgbe_3.15.1.8-1OEM.550.0.0.1198611: obsoleted by Host vib: LSI_bootbank_scsi-mpt2sas_15.10.06.00.1vmw-1OEM.550.0.0.1198610: obsoleted by Host vib: QLogic_bootbank_ima-qla4xxx_500.2.01.31-1vmw.0.3.100400: Missing vib: QLogic_bootbank_ima-qla4xxx_500.2.01.31-1vmw.0.3.100400: Obsoletes Host vib: QLogic_bootbank_net-nx-nic_5.5.639-1OEM.550.0.0.1331820: obsoleted by Host vib: QLogic_bootbank_net-qlcnic_5.5.190-1OEM.550.0.0.1331820: obsoleted by Host vib: QLogic_bootbank_qlnativefc_1.1.29.0-1OEM.550.0.0.1331820: obsoleted by Host vib: QLogic_bootbank_scsi-qla4xxx_644.55.34.0-1OEM.550.0.0.1331820: Missing vib: QLogic_bootbank_scsi-qla4xxx_644.55.34.0-1OEM.550.0.0.1331820: Obsoletes Host )
[2015-12-09 13:33:15:814 'HostUpdateDepotManager' 13716 INFO] [scanHost20, 1261] Bulletin: hpq-driver-bundle-600.9.2.38 Release Type: extension Status: Missing ( vib: Broadcom_bootbank_misc-cnic-register_1.710.70.v55.1-1OEM.550.0.0.1331820: obsoleted by Host vib: Broadcom_bootbank_net-bnx2_2.2.5f.v55.16-1OEM.550.0.0.1331820: obsoleted by Host vib: Broadcom_bootbank_net-bnx2x_2.710.70.v55.7-1OEM.550.0.0.1331820: obsoleted by Host vib: Broadcom_bootbank_net-cnic_2.710.70.v55.5-1OEM.550.0.0.1331820: obsoleted by Host vib: Broadcom_bootbank_net-tg3_3.137d.v55.1-1OEM.550.0.0.1331820: obsoleted by Host vib: Broadcom_bootbank_scsi-bnx2fc_1.710.70.v55.3-1OEM.550.0.0.1331820: obsoleted by Host vib: Broadcom_bootbank_scsi-bnx2i_2.710.70.v55.6-1OEM.550.0.0.1331820: obsoleted by Host vib: Emulex_bootbank_elxnet_10.2.445.0-1OEM.550.0.0.1331820: obsoleted by Host vib: Emulex_bootbank_ima-be2iscsi_10.2.250.1-1OEM.550.0.0.1331820: obsoleted by Host vib: Emulex_bootbank_lpfc_10.2.455.0-1OEM.550.0.0.1331820: obsoleted by Host vib: Emulex_bootbank_scsi-be2iscsi_10.2.250.1-1OEM.550.0.0.1331820: obsoleted by Host vib: Hewlett-Packard_bootbank_scsi-hpdsa_5.5.0.26-1OEM.550.0.0.1331820: obsoleted by Host vib: Hewlett-Packard_bootbank_scsi-hpsa_5.5.0.84-1OEM.550.0.0.1331820: obsoleted by Host vib: Hewlett-Packard_bootbank_scsi-hpvsa_5.5.0-92OEM.550.0.0.1331820: obsoleted by Host vib: Intel_bootbank_net-igb_5.2.7-1OEM.550.0.0.1331820: obsoleted by Host vib: Intel_bootbank_net-ixgbe_3.21.4-1OEM.550.0.0.1331820: obsoleted by Host vib: LSI_bootbank_scsi-mpt2sas_15.10.06.00.1vmw-1OEM.550.0.0.1198610: obsoleted by Host vib: QLogic_bootbank_ima-qla4xxx_500.2.01.31-1vmw.0.3.100400: Missing vib: QLogic_bootbank_ima-qla4xxx_500.2.01.31-1vmw.0.3.100400: Obsoletes Host vib: QLogic_bootbank_net-nx-nic_5.5.641-1OEM.550.0.0.1331820: obsoleted by Host vib: QLogic_bootbank_net-qlcnic_5.5.190-1OEM.550.0.0.1331820: obsoleted by Host vib: QLogic_bootbank_qlnativefc_1.1.39.0-1OEM.550.0.0.1331820: obsoleted by Host vib: QLogic_bootbank_scsi-bfa_3.2.5.0-1OEM.550.0.0.1331820: installed vib: QLogic_bootbank_scsi-qla4xxx_644.55.35.0-1OEM.550.0.0.1331820: Missing vib: QLogic_bootbank_scsi-qla4xxx_644.55.35.0-1OEM.550.0.0.1331820: Obsoletes Host )
[2015-12-09 13:33:15:814 'HostUpdateDepotManager' 13716 INFO] [scanHost20, 1261] Bulletin: hpq-driver-bundle-600.9.3 Release Type: extension Status: Missing ( vib: Broadcom_bootbank_misc-cnic-register_1.710.70.v55.1-1OEM.550.0.0.1331820: obsoleted by Host vib: Broadcom_bootbank_net-bnx2_2.2.5f.v55.16-1OEM.550.0.0.1331820: obsoleted by Host vib: Broadcom_bootbank_net-bnx2x_2.710.70.v55.7-1OEM.550.0.0.1331820: obsoleted by Host vib: Broadcom_bootbank_net-cnic_2.710.70.v55.5-1OEM.550.0.0.1331820: obsoleted by Host vib: Broadcom_bootbank_net-tg3_3.137h.v55.1-1OEM.550.0.0.1331820: obsoleted by Host vib: Broadcom_bootbank_scsi-bnx2fc_1.710.70.v55.3-1OEM.550.0.0.1331820: obsoleted by Host vib: Broadcom_bootbank_scsi-bnx2i_2.710.70.v55.6-1OEM.550.0.0.1331820: obsoleted by Host vib: EMU_bootbank_lpfc_10.4.236.0-1OEM.600.0.0.2159203: obsoleted by Host vib: Emulex_bootbank_elxnet_10.5.65.4-1OEM.550.0.0.1331820: obsoleted by Host vib: Emulex_bootbank_ima-be2iscsi_10.5.65.7-1OEM.550.0.0.1331820: obsoleted by Host vib: Emulex_bootbank_scsi-be2iscsi_10.5.65.7-1OEM.550.0.0.1331820: obsoleted by Host vib: Hewlett-Packard_bootbank_scsi-hpdsa_5.5.0.36-1OEM.550.0.0.1331820: obsoleted by Host vib: Hewlett-Packard_bootbank_scsi-hpsa_5.5.0.106-1OEM.550.0.0.1331820: obsoleted by Host vib: Hewlett-Packard_bootbank_scsi-hpvsa_5.5.0.98-1OEM.550.0.0.1331820: obsoleted by Host vib: Intel_bootbank_net-igb_5.2.10-1OEM.550.0.0.1331820: installed vib: Intel_bootbank_net-ixgbe_3.21.4.3-1OEM.550.0.0.1331820: installed vib: LSI_bootbank_scsi-mpt2sas_15.10.06.00.1vmw-1OEM.550.0.0.1198610: obsoleted by Host vib: QLogic_bootbank_ima-qla4xxx_500.2.01.31-1vmw.0.3.100400: Missing vib: QLogic_bootbank_ima-qla4xxx_500.2.01.31-1vmw.0.3.100400: Obsoletes Host vib: QLogic_bootbank_net-nx-nic_5.5.641-1OEM.550.0.0.1331820: obsoleted by Host vib: QLogic_bootbank_net-qlcnic_5.5.190-1OEM.550.0.0.1331820: obsoleted by Host vib: QLogic_bootbank_qlnativefc_2.1.20.0-1OEM.600.0.0.2159203: obsoleted by Host vib: QLogic_bootbank_scsi-bfa_3.2.5.0-1OEM.550.0.0.1331820: installed vib: QLogic_bootbank_scsi-qla4xxx_644.55.36.0-1OEM.550.0.0.1331820: Missing vib: QLogic_bootbank_scsi-qla4xxx_644.55.36.0-1OEM.550.0.0.1331820: Obsoletes Host )
[2015-12-09 13:33:15:815 'HostUpdateDepotManager' 13716 INFO] [scanHost20, 1261] Bulletin: hpq-driver-bundle-600.9.3.30 Release Type: extension Status: Missing ( vib: Broadcom_bootbank_misc-cnic-register_1.710.70.v55.1-1OEM.550.0.0.1331820: obsoleted by Host vib: Broadcom_bootbank_net-bnx2_2.2.5f.v55.16-1OEM.550.0.0.1331820: obsoleted by Host vib: Broadcom_bootbank_net-bnx2x_2.710.70.v55.7-1OEM.550.0.0.1331820: obsoleted by Host vib: Broadcom_bootbank_net-cnic_2.710.70.v55.5-1OEM.550.0.0.1331820: obsoleted by Host vib: Broadcom_bootbank_net-tg3_3.137h.v55.1-1OEM.550.0.0.1331820: obsoleted by Host vib: Broadcom_bootbank_scsi-bnx2fc_1.710.70.v55.3-1OEM.550.0.0.1331820: obsoleted by Host vib: Broadcom_bootbank_scsi-bnx2i_2.710.70.v55.6-1OEM.550.0.0.1331820: obsoleted by Host vib: EMU_bootbank_lpfc_10.4.236.0-1OEM.600.0.0.2159203: obsoleted by Host vib: Emulex_bootbank_elxnet_10.5.65.4-1OEM.550.0.0.1331820: obsoleted by Host vib: Emulex_bootbank_ima-be2iscsi_10.5.65.7-1OEM.550.0.0.1331820: obsoleted by Host vib: Emulex_bootbank_scsi-be2iscsi_10.5.65.7-1OEM.550.0.0.1331820: obsoleted by Host vib: Hewlett-Packard_bootbank_scsi-hpdsa_5.5.0.36-1OEM.550.0.0.1331820: obsoleted by Host vib: Hewlett-Packard_bootbank_scsi-hpsa_5.5.0.106-1OEM.550.0.0.1331820: obsoleted by Host vib: Hewlett-Packard_bootbank_scsi-hpvsa_5.5.0.100-1OEM.550.0.0.1331820: installed vib: Intel_bootbank_net-igb_5.2.10-1OEM.550.0.0.1331820: installed vib: Intel_bootbank_net-ixgbe_3.21.4.3-1OEM.550.0.0.1331820: installed vib: LSI_bootbank_scsi-mpt2sas_15.10.06.00.1vmw-1OEM.550.0.0.1198610: obsoleted by Host vib: QLogic_bootbank_ima-qla4xxx_500.2.01.31-1vmw.0.3.100400: Missing vib: QLogic_bootbank_ima-qla4xxx_500.2.01.31-1vmw.0.3.100400: Obsoletes Host vib: QLogic_bootbank_net-nx-nic_5.5.641-1OEM.550.0.0.1331820: obsoleted by Host vib: QLogic_bootbank_net-qlcnic_5.5.190-1OEM.550.0.0.1331820: obsoleted by Host vib: QLogic_bootbank_qlnativefc_2.1.20.0-1OEM.600.0.0.2159203: obsoleted by Host vib: QLogic_bootbank_scsi-bfa_3.2.5.0-1OEM.550.0.0.1331820: installed vib: QLogic_bootbank_scsi-qla4xxx_644.55.36.0-1OEM.550.0.0.1331820: Missing vib: QLogic_bootbank_scsi-qla4xxx_644.55.36.0-1OEM.550.0.0.1331820: Obsoletes Host )
[2015-12-09 13:33:15:815 'HostUpdateDepotManager' 13716 INFO] [scanHost20, 1292] Bulletin: hpq-driver-bundle-600.9.4 Release Type: extension Status: Installed ( vib: BRCM_bootbank_net-tg3_3.137l.v60.1-1OEM.600.0.0.2494585: installed vib: EMU_bootbank_elxnet_10.5.121.7-1OEM.600.0.0.2159203: installed vib: EMU_bootbank_ima-be2iscsi_10.5.101.0-1OEM.600.0.0.2159203: installed vib: EMU_bootbank_lpfc_10.5.70.0-1OEM.600.0.0.2159203: installed vib: EMU_bootbank_scsi-be2iscsi_10.5.101.0-1OEM.600.0.0.2159203: installed vib: Hewlett-Packard_bootbank_scsi-hpdsa_5.5.0.46-1OEM.550.0.0.1331820: installed vib: Hewlett-Packard_bootbank_scsi-hpsa_6.0.0.114-1OEM.600.0.0.2494585: installed vib: Hewlett-Packard_bootbank_scsi-hpvsa_5.5.0.100-1OEM.550.0.0.1331820: installed vib: Intel_bootbank_intelcim-provider_0.5-1.4: installed vib: Intel_bootbank_net-i40e_1.2.48-1OEM.550.0.0.1331820: installed vib: Intel_bootbank_net-igb_5.2.10-1OEM.550.0.0.1331820: installed vib: Intel_bootbank_net-ixgbe_3.21.4.3-1OEM.550.0.0.1331820: installed vib: LSI_bootbank_scsi-mpt2sas_15.10.06.00.1vmw-1OEM.550.0.0.1198610: obsoleted by Host vib: MEL_bootbank_nmlx4-core_3.1.0.0-1OEM.600.0.0.2348722: installed vib: MEL_bootbank_nmlx4-en_3.1.0.0-1OEM.600.0.0.2348722: installed vib: MEL_bootbank_nmst_4.0.0.20-1OEM.600.0.0.2295424: installed vib: QLogic_bootbank_misc-cnic-register_1.712.50.v60.1-1OEM.600.0.0.2494585: installed vib: QLogic_bootbank_net-bnx2_2.2.5j.v60.3-1OEM.600.0.0.2494585: installed vib: QLogic_bootbank_net-bnx2x_2.712.50.v60.6-1OEM.600.0.0.2494585: installed vib: QLogic_bootbank_net-cnic_2.712.50.v60.6-1OEM.600.0.0.2494585: installed vib: QLogic_bootbank_net-nx-nic_6.0.643-1OEM.600.0.0.2494585: installed vib: QLogic_bootbank_net-qlcnic_6.1.191-1OEM.600.0.0.2494585: installed vib: QLogic_bootbank_qlnativefc_2.1.27.0-1OEM.600.0.0.2768847: installed vib: QLogic_bootbank_scsi-bfa_3.2.5.0-1OEM.550.0.0.1331820: installed vib: QLogic_bootbank_scsi-bnx2fc_1.712.50.v60.7-1OEM.600.0.0.2494585: installed vib: QLogic_bootbank_scsi-bnx2i_2.712.50.v60.4-1OEM.600.0.0.2494585: installed vib: QLogic_bootbank_scsi-qla4xxx_644.6.04.0-1OEM.600.0.0.2159203: installed )
Hi all,
I recently tried up patch my ESXi 5.1 with the latest patches using Update Manager. Everything was working well until one of my hosts fails with the updates and I cant patch it. I noticed that the Image Profile is now at "<Unknown - no profile defined>
How can I correct this? I patched 10 other hosts in this cluster and this one does not want to be patched.
What can I do?
Any help will be appreciated.
Thanks,
Mike
Hello All,
I am facing this error during vSphere Update Manager installation although I did tried some resolutions posted on VMware KB, like:
VMware KB: Installing VMware Update Manager fails with the error: Error 25085
and this:
I input the user administrator@vsphere.local in the Update Manager installation to connect to vCenter Server. Therefore, this user already has administrator role with 'Register Extention' permission included.
However, after doing all the above, the error still remains. Is there anyone have another resolution to solve this error?
Thanks in advance.
Hello,
I just inherited three Essentials installations. Is there anyway to get the ESXi hosts updated automatically like it is possible with the Update Manager and the other vSphere versions?
Cheers
AWo
Hi,
I'm receiving the below error when I remediate few of my hosts in the cluster.
fault.com.vmware.vcIntegrity.VcIntegrityFault.summary
All the hosts are identical in configuration.
Please help.
I have used Fujitsu Image for setting up a new server.
Fujitsu has removed lsi-mr3 package from their customized image. (readme is telling: Otherwise new LSI RAID controllers with SAS3.0 support like PRAID CP400i or EP400i are not supported by ServerView Raid.)
what is the proper way to keep update manager to reinstall any update/component which puts the driver back into the system ?
i found this problem after installing all esx patches on to of the fujitsu image and then serverview raid-monitoring broke because of this.
i know i could exclude patches by name in update manager, but how should i know that "Vmware ESXi 5.5 complete update 3" contains this driver?
I dont want to exclude patches which i need on other servers and i don`t like to manage different patch baselilnes for different servers, i just want to avoid this driver to be reinstalled
I am running only ESX 6.0 in my environment and I noticed that Update Manager downloads patches for multiple versions of ESX.
I am wondering if there is a way to exclude patches for older versions. I found this in the vci-integrity.xml file:
-<contentSettings>
<hostInclude id="0001">embeddedEsx-5.0.0-INTL</hostInclude>
<hostInclude id="0002">embeddedEsx-5.1.0-INTL</hostInclude>
<hostInclude id="0003">embeddedEsx-5.5.0-INTL</hostInclude>
<hostInclude id="0004">embeddedEsx-6.0.0-INTL</hostInclude>
<hostUpdateEnabled>true</hostUpdateEnabled>
<vaUpgradeEnabled>true</vaUpgradeEnabled>
</contentSettings>
If I remove the lines for the first three versions, will it download only the patches for esx 6.0 or will I break something?
Being the incredibly impatient person that I am, I went ahead and changed the vci-integrity.html file located in "<DriveLetter>:\Program Files (x86)\VMware\Infrastructure\Update Manager" to the following:
-<contentSettings>
<hostInclude id="0001">embeddedEsx-6.0.0-INTL</hostInclude>
<hostUpdateEnabled>true</hostUpdateEnabled>
<vaUpgradeEnabled>true</vaUpgradeEnabled>
</contentSettings>
After editing the file, I restarted the VMware vSphere Update Manager Service and initiated a download of patches through the client. This seems to have successfully limited the downloads to only version 6.0.
Hi,
Just starting out using VUM, and having trouble understanding a few things.
Currently running vmware 5.1 hosts on build 5.1.0, 2583090, with vcenter 1235233, I need to upgrade the hosts to 5.1 Update 3 to support another tool we use.
Vmware suggests the build number 5.1.0, 2583090 is ESXI 5.1 Patch 7, but the build number seems to be released after update 3.
Question 1 - Whats the difference between a patch and an update?
Question 2 - if patch 7 is installed do I need update 3?
Question 3 - Does it matter which way I patch? Should I use update manager, should I download the patch to an ISO?
Help would be much appreciated
Hi,
How do I install UM so it works with the VCenter Server Appliance? I haven't found any details for this. Using Essentials Plus 6.0 bundle...
regards
Tor
Hi All
I upgraded my Lab environment to 6 u1 yesterday and have been trying to get the web client working with VUM. When I click a Host and go to the Update Manager tab I get the error below:-
and I get these errors in the C:\ProgramData\VMware\VMware Update Manager\Logs\vmware-vum-server-x.log:-
[#3] 2015-09-17T09:16:37.866+01:00 info vmware-vum-server[01536] [Originator@6876 sub=VcIntegrity] Session: [sessionId masked]; user DOMAIN\username
[#3] 2015-09-17T09:16:37.944+01:00 info vmware-vum-server[01536] [Originator@6876 sub=VcIntegrity] Active? true
2015-09-17T09:16:37.959+01:00 info vmware-vum-server[01660] [Originator@6876 sub=VcIntegrity] Connecting to host lab-vc1.DOMAIN on port 80 using protocol http
-->
2015-09-17T09:16:38.006+01:00 info vmware-vum-server[01660] [Originator@6876 sub=VcIntegrity] Authenticating extension by SSL certificate
2015-09-17T09:16:38.022+01:00 info vmware-vum-server[01660] [Originator@6876 sub=VcIntegrity] Logged in!
2015-09-17T09:16:38.022+01:00 info vmware-vum-server[01660] [Originator@6876 sub=VcIntegrity] ImpersonateUser user DOMAIN\username
2015-09-17T09:16:38.069+01:00 info vmware-vum-server[01660] [Originator@6876 sub=VcIntegrity] Impersonated user!
[#3] 2015-09-17T09:16:38.147+01:00 info vmware-vum-server[01312] [Originator@6876 sub=VcIntegrity] Session: [sessionId masked]; user DOMAIN\username
[#3] 2015-09-17T09:16:38.147+01:00 info vmware-vum-server[01312] [Originator@6876 sub=VcIntegrity] Active? true
2015-09-17T09:16:38.178+01:00 info vmware-vum-server[01280] [Originator@6876 sub=VcIntegrity] Connecting to host lab-vc1.DOMAIN on port 80 using protocol http
-->
2015-09-17T09:16:38.225+01:00 info vmware-vum-server[01280] [Originator@6876 sub=VcIntegrity] Authenticating extension by SSL certificate
2015-09-17T09:16:38.240+01:00 info vmware-vum-server[01280] [Originator@6876 sub=VcIntegrity] Logged in!
2015-09-17T09:16:38.240+01:00 info vmware-vum-server[01280] [Originator@6876 sub=VcIntegrity] ImpersonateUser user DOMAIN\username
2015-09-17T09:16:38.256+01:00 info vmware-vum-server[01280] [Originator@6876 sub=VcIntegrity] Impersonated user!
2015-09-17T09:17:23.029+01:00 error vmware-vum-server[01536] [Originator@6876 sub=Ufa.HTTPService] Failed to read request; stream: <SSL(<io_obj p:0x01498200, h:-1, <TCP '0.0.0.0:0'>, <TCP '0.0.0.0:0'>>)>, error: class Vmacore::TimeoutException(Operation timed out)
If i go to the Update Manager item itself i get this error about "Class not found 'com.vmware.vum.views.events.VumEventConsoleView' in module /vsphere-client/updatemanager-ui/UpdateManager.swf":-
I tried re-registering VUM to vCSA via the VMwareUpdateManagerUtility.exe as detailed here vSphere 6.0 Documentation Center but it made no difference. Even the good old universal fix (rebooting everything) didn't help.
Any ideas folks?
Thanks
Danny