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

I have Vcenter installed as an appliance and the update manager installed on a windows 2012 server.

When I go to the web client for VCenter I cannot see the Web plugin for the Update Manager, how do I get it installed?

John.

vCenter Server 6.0  disk space is growing automatically on daily basis in GBs. On which disk, vCneter Update Manager is installed. Size of this particular Drive is 50 GB in which only 4 GB data is reside however its space has been consumed 43 GB.

When all space has been occupied of this Drive  ( Drive D) then vCenter Server Services goes stop. I have no idea where is the problem and could not find out the root cause. Secondly, other-than vCenter Update Manager Server Services, all vCenter Server 6.0 related services are installed on Drive C. 

Internet Services are enabled on vCenter Server but i have disabled the option on Update Manager configuration Tab for auto downloading VMware patches. Please help out.......

Hi,

i moved my vcenter 5.5 to a different server (2003 -> 2008r2) while upgrading from 5.1 caused by os incompatibility.

everything works fine but the vcenter shows an com.vmware.vcintegrity alert.

Error Message is that i cant receive systemstate of https://vcsernameOLD:9084/vci/downloads/health.xml.

By the fact that i do not use the update manager i did not move the update manager to the new server i just deleted the old server after i reinstalled the vcenter on my new server with the old database.

Can anyone tell me how can i let the vcenter forget that their was a update manager and fix the alert?

i tried to access the https://venterip/mob website but the plugin is not registered, so might be a config xml entry or a database entry which is still wrong.

Or am i just wrong in my opinion, that the error tell me he cant contact the no longer existing update manager??

Thanks for your help

Hello community!

I have a VMware vSphere Update Manager 6  installed in my vSphere6 env.

Update manager is working fine and updates hosts, but in WebClient in "System configuration" tab in services health status I observe "VMware vSphere Update Manager extension" in critical status.

When I open it I see following:

I checked the update manager and vpxd logs and found nothing suspicious.

Any idea what might it be?

Hello,

I imported a bnx2 driver into my Update Manager and now I want to remove it, but cannot figure out how.

Any ideas?

Hi,

I've imported a few offline bundles into update manager, but i would like to remove one of them, anyone knows how to do it?

I need to upgrade vcenter 5.5 to vcenter 6 and point that to my new vcenter 6

do I do the upgrade on it first or what is the procedure to do this?

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 ?

Hi all,

Another unusual problem. The update manager plugin on vsphere 5.5 keeps disabling itself as "not installed on the (vcenter) server" - however if I log on to the update manager server and test the odbc settings, everything works again for a few days. Then the whole cycle is repeated.

Any ideas?

Morning All,

Hoping someone can help with an issue I am experiencing with VUM 6.0 (Installed from the VMware-VIMSetup-all-6.0.0-3040890.iso image) - The problem in a nutshell is that for some reason it is completely ignoring the proxy settings and attempting to access the internet directly.

I have tried setting the proxy using both FQDN & the IP Address, neither seem to have any affect.

The log file shows:

[2015-10-22 09:43:57:738 'DownloadMgr' 2400 INFO]  [downloadMgr, 593] Executing download job {30749632}, url=https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml

[2015-10-22 09:43:57:738 'httpDownload' 2400 INFO]  [httpDownload, 571] Downloading https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml via proxy <OURPROXYCHANGED>:9090

[2015-10-22 09:43:57:816 'httpDownload' 2400 ERROR]  [httpDownload, 732] Error 12175 from WinHttpSendRequest for url https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml

[2015-10-22 09:43:57:816 'httpDownload' 2400 INFO]  [httpDownload, 926] Retrying https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml with proxy off

[2015-10-22 09:43:57:816 'httpDownload' 2400 INFO]  [httpDownload, 556] Downloading https://hostupdate.vmware.com/software/VUM/PRODUCTION/main/vmw-depot-index.xml

[2015-10-22 09:43:58:082 'Activation' 1784 INFO]  [activationValidator, 367] Leave Validate. Succeeded for integrity.option.OptionManager.GetUpdateURLs on target: Integrity.OptionManager

[2015-10-22 09:43:58:082 'ConfigurationMgr' 1784 INFO]  [configurationMgr, 1137] Getting software update URLs.

[2015-10-22 09:43:58:097 'Activation' 1784 INFO]  [activationValidator, 367] Leave Validate. Succeeded for integrity.option.OptionManager.queryView on target: Integrity.OptionManager

However monitoring both the proxy & the firewall this never actually tries the proxy server it actually tries to get out to the web directly. I have confirmed that the VUM server can resolve the name correctly (however this wont matter when using the IP address), I have changed the service to use a domain admin account (even though it's a anonymous proxy - figured it might be worth trying).

Any advice or pointers would be great

Thank

MadAsToast.

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'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

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 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 )

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.