Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

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 (76607)

Last Updated: 12/19/2019Categories: TroubleshootingTotal Views: 5606Language:
Chinese (Simplified)JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

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.

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 (https://kb.vmware.com/s/article/70865)

Resolution

The issue reported in KB https://kb.vmware.com/s/article/70865 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

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
特定の状況で、NSX-T 2.5.0 から NSX-T 2.5.1 へのホストのライブ アップグレードが失敗する場合がある (76606)

KB
•
Edge Gateway が South（ダウンリンク）インターフェイスからのトラフィックで DNAT をサポートしない (76562)

KB
•
从环境故障恢复 vCenter Server Appliance、工作负载控制层面和 NSX (76585)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware NSX-T Data Center 2.5.x

VMware NSX-T Data Center

Take Our Survey

Support Assistant