VMware Networking Community
horan193
Contributor
Contributor

Host preparation - Upgrade from vShield to NSX

After upgrading from vShield 5.5.4 to NSX 6.2.8, hosts are incorrectly prepared.

vShield-VXLAN-service agency performs the removal of the VIB esx-vxlan, vsip, and the second NSX agency performs the installation. This is an endless process of removing, installing, and rebooting a host.

How to prevent removal of the VIB with the old vShield and leave only the installation of the new NSX agency?

eam01.jpg

6 Replies
chrisgnoon
Enthusiast
Enthusiast

Wow still using vShield, haven't seen that in a while.

Try the below workflow and see how you get on:

- Identify 1 ESXi host having this issue.

- Place this host into maintenance mode.

- Drag this ESXi host out of the cluster, either to another cluster or to the top of the tree.  It's important where you drag the host to is not a cluster or area that is prepared for VXLAN.

- Wait 5 minutes for the VIB's/packages to be uninstalled.

- Reboot the ESXi host.

- Check the VIB's are all removed from the system.

- Drag the ESXi host back into the VXLAN prepared cluster.

- Check the VIB's/packages are correctly installed.

- Bring the ESXi host out of maintenance mode.

If it works, repeat for the hosts.

I assume you followed the recommended upgrade path?

Upgrade from vCloud Networking and Security 5.5.x to NSX 6.2.x

Chris Noon | CCDP | CCNP | VCDX 289
Don't forget to mark as solved if your questions are answered.
0 Kudos
Himadri
Contributor
Contributor

Try this:-

> Take one esx host

> Put the esx to maintenance mode.

> Remove and add on a temp cluster 

> Uninstall the 3 VIB's/packages

> Reboot the ESXi host.

> Check the VIB's are completely removed

> Put ESXi host back into the original cluster.

> Check the VIB's/packages are correctly installed.

> Check if issue resolved

horan193
Contributor
Contributor

Good job!

After rebooting the server to the cluster, the vibs are automatically removed (vShield-VXLAN) and installed (VMware Network Fabric). How to fix this?

0 Kudos
chrisgnoon
Enthusiast
Enthusiast

Is it fixed now?

Chris Noon | CCDP | CCNP | VCDX 289
Don't forget to mark as solved if your questions are answered.
0 Kudos
horan193
Contributor
Contributor

No..

My steps:

- place this host into maintenance mode

- drag this ESXi host out of the cluster in the same datacenter

- wait for the VIB's/packages to be uninstalled (

esxcli software vib remove -n esx-vxlan

esxcli software vib remove -n esx-vsip

esxcli software vib remove -n dvfilter-switch-security

esxcli software vib remove -n esx-vdpi)

- reboot the ESXi host

- drag the ESXi host back into the VXLAN prepared cluster

- bring the ESXi host out of maintenance mode

- resolve and wait for the VIB's uninstall (by VMware Network fabric) and them scan/install (vShield-VXLAN-Service)

Old vShield has 172.16.1.10 and same address has NSX.

0 Kudos
chrisgnoon
Enthusiast
Enthusiast

At the very end of the process, the vshield packages should be uninstalled and the NSX packages installed or queued for installation. The host may require another reboot, are you performing that final reboot?

Chris Noon | CCDP | CCNP | VCDX 289
Don't forget to mark as solved if your questions are answered.
0 Kudos