Loading

×Sorry to interrupt
This page has an error. You might just need to refresh it.
[NoErrorObjectAvailable] Uncaught ReferenceError: addCTracking is not defined
Failing descriptor: {markup://c:KM_ArticleThemeLayout}

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

NSX-T ESXi host upgrade fails when upgrading from 2.4.0/2.4.1 versions (77108)

Last Updated: 4/18/2020Categories: InformationalTotal Views: 4805Language:
Chinese (Simplified)JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

NSX-T ESXi host upgrade fails when upgrading from NSX-T Data Center 2.4.0 or 2.4.1

NSX-T DFW is configured with a rule of Service Type TCP/UDP/ALG for any of the following ports

TCP 21   - ALG FTP
TCP 1521 - ALG ORACLE_TNS
TCP 111  - ALG SUN_RPC_TCP
TCP 135  - ALG MS_RPC_TCP
UDP 69   - ALG TFTP

Upgrade Coordinator display a long error string which contains the following exception

"KernelModulesException: Failed to unload module nsxt-vsip: Cannot remove module nsxt-vsip: Consumed resource count of module is not zero"

The ESXi /var/log/vmkernel.log contains the following messaging

2020-01-25T12:22:27.020Z cpu28:98022942)Destroying solution lock.
2020-01-25T12:22:27.020Z cpu28:98022942)Unregistering char device
2020-01-25T12:22:27.024Z cpu28:98022942)WARNING: Heap: 2734: Non-empty heap (vsip-state) being destroyed (avail is 38203008, should be 38203216).
2020-01-25T12:22:27.106Z cpu28:98022942)ALERT: Mod: 5212: Failed to unload module nsxt-vsip, since its consumed resource count is 1. Waiting...
2020-01-25T12:22:32.124Z cpu28:98022942)ALERT: Mod: 5241: Failed to unload module nsxt-vsip, since its consumed resource count is 1. Giving up.

Cause

The upgrade fails because the 2.4.0/2.4.1 nsxt-vsip module cannot be unloaded and uninstalled from the host.
This occurs because of a memory heap issue caused by the ALG component of the DFW.

Resolution

This issue is resolved in:

VMware NSX-T Data Center 2.4.2, available at VMware Downloads.

VMware NSX-T Data Center 2.5, available at VMware Downloads.

VMware NSX-T Data Center 3.0, available at VMware Downloads.

Workaround

To workaround this issue after a host upgrade has failed

Reboot the ESXi host which will resolve the error condition on the host

On the NSX-T UI -> System -> Fabric -> Nodes -> Host Transport Node, ensure the host is not in maintenance mode

On the Upgrade Coordinator reset the host upgrade error and restart the host upgrade

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
End Of General Availability of the Free vSphere Hypervisor (ESXi 7.x and 8.x) (2107518)

Result 1 of 1

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.x

VMware NSX-T Data Center

Take Our Survey

Support Assistant