VMware Cloud Community
dennisv
Contributor
Contributor

ESXi400-201003401-BG conflict

Hi All,

I'm having an issue with an update for ESXi 4

ESXi400-201003401-BG

http://kb.vmware.com/kb/1019497

The selected Update conflicts with following Updates in VMware vCenter Update Manager patch repository:

VEM400-200904001-BG, VEM400-200906002-BG, VEM400-200907001-BG, VEM400-200909001-BG, VEM400-200911014-BG, VEM400-200912001-BG, VEM400-200912016-BG, VEM400-201002001-BG, VEM400-201002011-BG.

All these updates are related to Cisco 1000 Nexus switch, which is not beeing used.

This update dates from 01-April-2010.

I have 1 machine with ESX4 and 1 machine with ESX4i, this problem only occurs on the ESXi machine.

We are professional partner, but somehow I am unable to file a support request. Thus I'm trying to put this on the commuties page hoping

someone notices Smiley Happy

Reply
0 Kudos
2 Replies
Saju_C
Enthusiast
Enthusiast

Is it from update manager? Have you added Cisco download link to the update manager?

If your patch repository contains cisco patches ( ie if you have downloaded cisco patches) then your vmware patch baseline will conflict with cisco patches. If your baseline doesnt contain cisco patches then you can proceed by remediating the patches and you can ignore this message.

Please refer KB http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=101306...

Thanks

CS

dennisv
Contributor
Contributor

(while writing this post the staging worked.... please read on)

Yes this update is using update manager to remediate the host.

I do not have any Cisco downloads or patches in my repository :

I do not use or have any Cisco switches (neither physical or virtual).

I can't ignore this warning, the remediate will simply fail.

( I was going to put a screenshot here , but I was unable to reproduce the error...read on)

While I was trying to stage the host I got another warning saying the host contains the vCenter VM.

I moved this VM to the other host and remediated the host.

This time it worked as expected. The host was remediated.

I can't recall the vCenter VM warning and I am unable to find the logs for the conflict. Very strange...

Anyway, seems to be working now.

Thanks and regards.

Reply
0 Kudos