Note 1: Even though Cisco fully supports VUM based upgrades we generally recommend the CLI for VEM upgrades as it provides more granular control on what gets upgraded when.
Note 2: If you plan on manually upgrading the VEM modules make sure you have disabled VMware Update Manager (VUM) service so that it does not automatically roll back changes we make. Once the vem upgrade is complete we can start it back up.
Step 0 Run a “show mod” to check the status of the modules
switch# show mod Mod Ports Module-Type Model Status --- ----- -------------------------------- ------------------ ------------ 1 0 Virtual Supervisor Module Nexus1000V active * 3 248 Virtual Ethernet Module NA ok 4 248 Virtual Ethernet Module NA ok 5 248 Virtual Ethernet Module NA ok 6 248 Virtual Ethernet Module NA ok Mod Sw Hw --- --------------- ------ 1 4.0(4)SV1(3b) 0.0 3 4.0(4)SV1(3b) 1.11 4 4.0(4)SV1(3b) 1.11 5 4.0(4)SV1(3b) 1.11 6 4.0(4)SV1(3b) 1.11 Mod MAC-Address(es) Serial-Num --- -------------------------------------- ---------- 1 00-19-07-6c-5a-a8 to 00-19-07-6c-62-a8 NA 3 02-00-0c-00-03-00 to 02-00-0c-00-03-80 NA 4 02-00-0c-00-04-00 to 02-00-0c-00-04-80 NA 5 02-00-0c-00-05-00 to 02-00-0c-00-05-80 NA 6 02-00-0c-00-06-00 to 02-00-0c-00-06-80 NA Mod Server-IP Server-UUID Server-Name --- --------------- ------------------------------------ -------------------- 1 172.16.165.55 NA NA 3 172.16.165.91 dcedbaac-1dc0-11df-0000-00000000000e 172.16.165.91 4 172.16.165.92 dcedbaac-1dc0-11df-0000-00000000000d 172.16.165.92 5 172.16.165.93 dcedbaac-1dc0-11df-0000-00000000000c 172.16.165.93 6 172.16.165.94 dcedbaac-1dc0-11df-0000-00000000000b 172.16.165.94 * this terminal session
This is looking good, with one active VSM and multiple VEM modules and all running the same version.