cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
14716
Views
0
Helpful
32
Replies

vSphere Host patch update fails with 1000v installed

Robert Burns
Cisco Employee
Cisco Employee

Greetings all,

Wanted to give a heads up as people are rolling out the VMware Update 2 patch.

Problem:

When trying to install the offline bundle for ESX Update 2 it fails with an error similar to:

DependencyError: Requested VIB rpm_vmware-esx-vmkernel64_4.0.0-2.17.261974@i386 conflicts with the host

Reason:

This is because the VEM software currently installed is not compatible with the new kernel update.

Resolution:

You must to install the new VEM version for Update 2 & the Vmware Update 2 offline bundle together.

[From ESX CLI]

esxupdate --bundle=[Updated 1000v VEM offline bundle] --bundle=[VMware Offline Update Bundle] update

Ex. esxupdate --bundle VEM-4.0.0-update02-v120.zip --bundle upgrade-from-esx4.0-4.0_update02.zip update


[Using VI Host Update utility]

./vihostupdate --install --bundle[Path to VMware Update offline bundle] ",”[Path to Updated 1000v VEM Offline bundle]” --server [vSphere Host IP Address]

Ex. ./vihostupdate --install --bundle “/../upgrade-from-esx4.0-4.0_update02.zip ",”/../ VEM-4.0.0-update02-v120.zip” --server 192.168.1.101

Nexus 1000v Compatability Matrix:

http://www.ciscosystems.com/en/US/docs/switches/datacenter/nexus1000/sw/4_0_4_s_v_1_3/compatibility/information/n1000v_compatibility.html

http://www.ciscosystems.com/en/US/docs/switches/datacenter/nexus1000/sw/4_0_4_s_v_1_2/compatibility/information/n1000v_compatibility.html

http://www.ciscosystems.com/en/US/docs/switches/datacenter/nexus1000/sw/4_0/compatibility/information/n1000v_compatibility.html

Obtain Latest VEM Software:

http://tools.cisco.com/support/downloads/go/ImageList.x?relVer=4.0%284%29SV1%283%29&mdfid=282646785&sftType=NX-OS+System+Software&optPlat=&nodecount=2&edesignator=null&modelName=Cisco+Nexus+1000V+Switch&treeMdfId=&treeName=&modifmdfid=null&imname=&hy...

Regards,

Robert

32 Replies 32

born.jason
Level 1
Level 1

Tried to update with the following CLI command with no success:

esxupdate --bundle VEM400-201006011.zip --bundle upgrade-from-esx4.0-4.0_update02.zip update

I`ve downloaded the latest VEM for me here: http://www.vmware.com/patch/s3portal.portal?_nfpb=true&_windowLabel=SearchPatch&SearchPatch_actionOverride=%2Fportlets%2Fpatchupdate%2FfindPatchByProductVersion&_pageLabel=s3portal_pages_downloadPatch_page&type=vsphere&version=4.0.0&product=VEM

Here is the message which appear:

# esxupdate --bundle VEM400-201006011.zip --bundle upgrade-from-esx4.0-4.0_update02.zip update
VEM400-201006011.zip                                                              ##################################################################################################################### [100%]

Skipping bulletin ESX400-201006221-UG, it is installed or obsoleted
Skipping bulletin ESX400-201006212-UG, it is installed or obsoleted
Skipping bulletin ESX400-201006219-UG, it is installed or obsoleted
Skipping bulletin ESX400-201006217-UG, it is installed or obsoleted
Skipping bulletin ESX400-201006203-UG, it is installed or obsoleted
Skipping bulletin ESX400-201006215-UG, it is installed or obsoleted
Skipping bulletin ESX400-201006225-UG, it is installed or obsoleted
Skipping bulletin ESX400-201006202-UG, it is installed or obsoleted
Skipping bulletin ESX400-201006209-UG, it is installed or obsoleted
Skipping bulletin ESX400-201006214-UG, it is installed or obsoleted
Skipping bulletin ESX400-201006205-UG, it is installed or obsoleted
Skipping bulletin ESX400-201006222-UG, it is installed or obsoleted
Skipping bulletin ESX400-201006224-UG, it is installed or obsoleted
Skipping bulletin ESX400-201006204-UG, it is installed or obsoleted
Skipping bulletin ESX400-201006206-UG, it is installed or obsoleted
Skipping bulletin ESX400-201006218-UG, it is installed or obsoleted
Skipping bulletin ESX400-201006211-UG, it is installed or obsoleted
Skipping bulletin ESX400-201006220-UG, it is installed or obsoleted
Skipping bulletin ESX400-201006226-UG, it is installed or obsoleted
Skipping bulletin ESX400-201006208-UG, it is installed or obsoleted
Skipping bulletin ESX400-201006207-UG, it is installed or obsoleted
The following problems were encountered trying to resolve dependencies:
   Requested VIB rpm_vmware-esx-vmkernel64_4.0.0-2.17.261974@i386 conflicts with
   the host

Any suggestions?

I have the same trouble:

[root@node2 ~]# esxupdate --bundle /home/scotth/upgrade-from-esx4.0-4.0_update02.zip --bundle /home/scotth/VEM400-201006021.zip update
Skipping bulletin ESX400-201006221-UG, it is installed or obsoleted
Skipping bulletin ESX400-201006212-UG, it is installed or obsoleted
Skipping bulletin ESX400-201006219-UG, it is installed or obsoleted
Skipping bulletin ESX400-201006217-UG, it is installed or obsoleted
Skipping bulletin ESX400-201006203-UG, it is installed or obsoleted
Skipping bulletin ESX400-201006215-UG, it is installed or obsoleted
Skipping bulletin ESX400-201006225-UG, it is installed or obsoleted
Skipping bulletin ESX400-201006202-UG, it is installed or obsoleted
Skipping bulletin ESX400-201006209-UG, it is installed or obsoleted
Skipping bulletin ESX400-201006214-UG, it is installed or obsoleted
Skipping bulletin ESX400-201006205-UG, it is installed or obsoleted
Skipping bulletin ESX400-201006222-UG, it is installed or obsoleted
Skipping bulletin ESX400-201006224-UG, it is installed or obsoleted
Skipping bulletin ESX400-201006204-UG, it is installed or obsoleted
Skipping bulletin ESX400-201006206-UG, it is installed or obsoleted
Skipping bulletin ESX400-201006218-UG, it is installed or obsoleted
Skipping bulletin ESX400-201006211-UG, it is installed or obsoleted
Skipping bulletin ESX400-201006220-UG, it is installed or obsoleted
Skipping bulletin ESX400-201006226-UG, it is installed or obsoleted
Skipping bulletin ESX400-201006208-UG, it is installed or obsoleted
Skipping bulletin ESX400-201006207-UG, it is installed or obsoleted
The following problems were encountered trying to resolve dependencies:
   Requested VIB rpm_vmware-esx-vmkernel64_4.0.0-2.17.261974@i386 conflicts with
   the host

As you can tell you have a previously installed patch conflicting with the new VEM one you're trying to install.

Have you ensured you have the minimum kernel patches installed?


ESX  compatibility - The Cisco patch VEM400-201006021-BG should be used only  with the ESX vmkernel version released with ESX400-201006201-UG or later
ESXi  compatibility - The Cisco patch VEM400-20106021-BG should be used only  with the ESXi Firmware version released with ESXi400-201006201-UG or  later

Can you both paste the output of:

esxupdate query

rpm -qa | grep vmkernel | awk -F. '{print $5}'

Thanks,

Robert

The problem is actually the VEM RPMs (vib whatever) do no properly remove obsoleted versions.

Here's how I corrected my problem:

rpm -qa | grep vem

rpm -e <packagenames>.rpm

esxupdate --bundle upgrade4.0-4.0u2.zip --bundle VEM-201006021.zip

Then a reboot and the system came up properly.

I think Cisco may need to put some more lab time into the building of their vibs for vSphere, the nexus 1000v upgrade/install documentation is.... amature at best, it looks like some Cisco engineer just tried to copy and paste stuff but did it from different steps... it's pretty awful.

-SH

SH,

We appreciate the feedback - I've passed it on to our Docs team.  We're in the works on updating the current Upgrade/Compatibility docs posted on CCO (they're just be reviewed and should be posted this week).

FYI - As of vSphere 4.1 this process is greatly improved.  The VEM software has been de-coupled from the host kernel so it will not be required to update the VEM software bundle each time VMware releases an update/patch.  This should makes this much easier as of 4.1 and later.

As for the current process we'll see what we can do to improve the current documentation.

Regards,

Robert

For me its not working. See my below steps:

1.

[root@server01 ~]# rpm -qa | grep vem
cisco-vem-v100-esx-4.0.4.1.1.31-1.11.11
cisco-vem-v100-esx-4.0.4.1.1.28-0.7.3
cisco-vem-v110-esx-4.0.4.1.2.0.81-1.11.11

2.

[root@server01 ~]# rpm -e cisco-vem-v100-esx-4.0.4.1.1.28-0.7.3
Cannot remove VIB, host is part of DV switch DvsPortset-0
error: %preun(cisco-vem-v100-esx-4.0.4.1.1.28-0.7.3.x86_64) scriptlet failed, exit status 255
[root@server01 ~]# rpm -e cisco-vem-v100-esx-4.0.4.1.1.31-1.11.11
[root@server01 ~]# rpm -e cisco-vem-v110-esx-4.0.4.1.2.0.81-1.11.11
/usr/sbin/vmkmod-install.sh

[root@server01 ~]# rpm -qa | grep vem
cisco-vem-v100-esx-4.0.4.1.1.28-0.7.3

3.

C:\Program Files (x86)\VMware\VMware vSphere CLI\bin>vihostupdate.pl --install --bundle "C:\source\upgrade-from-esx4.0-4.0_update02.zip","C:\source\VEM400-201006011.zip" --server 10.10.10.101
Enter username: root
Enter password:
Please wait patch installation is in progress ...
There was an error resolving dependencies.
   Requested VIB rpm_vmware-esx-vmkernel64_4.0.0-2.17.261974@i386 conflicts with the host

@logininc1

do i first need to detach the esx host from the dvs?

If i put one host in maintanance mode, then disconnect the host from the DVS and connect the host back to the DVS. Which VEM version should then be installed on the host? The VSM is v1.2.

Do i have remove/erase some files from the host before add back to the DVS?

I'm sorry I left out a part.

Put the host in maintenance mode.

SSH in, go to /etc/init.d

Stop all the VEM services by doing

./vem-vnet100-dsspa-dpa stop

./vem-vnet100-dsspa-load stop

(please note I'm guessing on the above file names, do not copy and paste).

Then you can successfully remove the RPMs.

Note that if your management console is on the n1000v doing the above stops will disrupt your access, I recommend doing this via serial or directly on the console.

Then after you do the above do the esxupdate and a reboot and all should be well.

-SH

Assuming it is an esx host you want to stop and remove the VEM using vem-remove -s -r

This will stop the DPA agent and unload the modules from the kernel and then remove the VEM VIB.

For ESXi you have to find the VEM VIB version using vihostupdate query, then remove it using vihostupdate and then reboot the ESXi host to unload the VEM modules.

louis

it is an esx host.

Ok, steps to do.

1. esx host in maintenance mode

2. disconnect from DVS

3. vem-remove -s -r

4. install the complete update 2

5. add the host to the DVS and automaticaly VEM 1.2 should be installed, right?

if this not work well i have first remove the rpm`s like logininc1 described?

If you can't get the VMware Update 2 & New VEM bundle to install from the 2-in-1 esxupdate command, then yes you can remove the VEM software (thereby removing the conflicting package), apply the Vmware Update 2, and then re-add your host to the DVS (VUM will push the appropriate VIB) or manually install the new VEM bundle again.

Keep in mind with this process you have to evacuate all VMkernel Ports & VM connections from the before you can remove a host from the DVS.  An alternative (if you don't want to evacuate VMs to another host, or don't have that luxury), you can take a spare network adapter (or steal one from your DVS uplinks assuming you're not doing a port channel) and move it to a temporary vSwitch.  Then you can just migrate all the DVS Port Groups & VMKernel ports to the vSiwtch using the Network Migrate wizard in vCenter.  With all ports now off the DVS you can then safely remove the host from the DVS, remove the VEM software, and proceed with the update.  Take a little more work this way but at least you don't have to migrate VMs off the host.

BTW - You shouldn't need to remove the VEM software via RPM.  The method Louis detailed is the preferred method using the vem-remove command.

Robert

It worked, i`m now on VEM version 4.0(4)SV1(2). I have to detach the host from the DVS and then perform a "vem-remove -s -r", after that in VUM always a conflict were shown. Then i had to manualy remove the rpm because one vem package was in conflict. After this i was able to update the host with Complete Update 2 and after complete this patch i add the host back to the DVS and the new version installed automatically. I`ve raised the feature level and done.

See attached the screen, i thing it looks fine.

But see also attached the second screen. In vCenter i have in the networking tab a configuration issue. Seems that vCenter don`t recognized that the update is done. How can i manually complete this in vCenter?

Here is a "show vmware vem upgrade status"

# show vmware vem upgrade status

Upgrade Status:
Upgrade Notification Sent Time:
Upgrade Status Time(vCenter):
Upgrade Start Time:
Upgrade End Time(vCenter):
Upgrade Error:

Jason,

From your VSM issue the following command.


n1000v-AV(config)# vmware vem upgrade complete

If that doesn't work, assuming ALL your VEM hosts are upgrade, just restart the upgrade process from the VSM


n1000v-AV(config)# vmware vem upgrade notify

[Accept the upgrade notification in vCenter]

n1000v-AV(config)# vmware vem upgrade proceed

n1000v-AV(config)# vmware vem upgrade complete

As all your VEM hosts are already running the new version there should be no actions performed.

This should sync your VC with the correct VSM version.

Last step - raise your feature level on your VSM.

Regards,

Robert

If i process these commands:

n1000v-AV(config)# vmware vem upgrade notify

[Accept the upgrade notification in vCenter]

n1000v-AV(config)# vmware vem upgrade proceed

n1000v-AV(config)# vmware vem upgrade complete

you say normaly nothing should happen because the VEMs are already on version 1.2, right?

Because i want no downtime for the 2 hosts....

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: