ESXi hosts in a NSX-T prepared cluster running ESXi 6.5/6.7 versions may reboot during upgrade to NSX-T 2.5.1
Article ID: 336980
Updated On:
Products
Issue/Introduction
In a container based environment, hosts running 6.5-U2/U3 and/or 6.7-U1/U2, upgrading NSX-T VIBs to 2.5.1 may result in a reboot prior to upgrade without user intervention.
UI will display warning “VSIP Filters on the host have not been cleared. Rebooting the host to clear the filters” with specific host name.
Environment
VMware NSX-T Data Center 2.5.x
Cause
A known issue in ESXi releases 6.5-U2/U3 and/or 6.7-U1/U2 causes the VSIP filters on the host continue to show up even after the host is put in maintenance mode. As a result of the VSIP filters still present on the host, the VSIP module unload fails which leads to host upgrade failure.
User may not be able to determine if a host is experiencing the issue before upgrade. As part of upgrade, after the host is put in maintenance mode NSX-T upgrade co-ordinator will check if there stale DV filters present on the host and automatically reboot the host to clear the DV filters. The auto-reboot is triggered only if there is at least one stale DV Filters on the host after the host is put into maintenance mode refer to KB (In container environments NSX-T host upgrades fail at 10% or get stuck trying to put host in maintenance mode)
Resolution
The issue reported in KB "In container environments NSX-T host upgrades fail at 10% or get stuck trying to put host in maintenance mode" is addressed in ESXi 6.7 U3 and ESXi 6.5 EP16
The issue will not be seen If NSX-T host upgrade is attempted on ESXi 6.7 U3 and ESXi 6.5 EP16.
Workaround:
Upgrade to ESXi 6.7 U3 and ESXi 6.5 EP16 prior to upgrading NSX-T to 2.5.1
Feedback
