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

With IP Discovery enabled, host VIB update may fail when upgrading from NSX-T 2.3.1 to NSX-T 2.4.0 (67445)

Last Updated: 3/14/2019Categories: TroubleshootingTotal Views: 6210Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Host running ESXi 6.7EP06 (build 11675023), VIB upgrade will fail during in-place upgrade with below error messages.

@ NSX Manager : /var/log/upgrade-coordinator/upgrade-coordinator.log

Unexpected error while upgrading upgrade unit: Install of offline bundle failed on host 6d1d1810-8884-4f4d-83bc-54ec5a86df3a with error : [LiveInstallationError] Error in running ['/etc/init.d/nsx-datapath', 'start', 'upgrade']: Return code: 1 Output: ERROR: ld.so: object '/lib/libMallocArenaFix.so' from LD_PRELOAD cannot be preloaded: ignored. ioctl failed: No such file or directory ERROR: ld.so: object '/lib/libMallocArenaFix.so' from LD_PRELOAD cannot be preloaded: ignored. ERROR: ld.so: object '/lib/libMallocArenaFix.so' from LD_PRELOAD cannot be preloaded: ignored. ERROR: ld.so: object '/lib/libMallocArenaFix.so' from LD_PRELOAD cannot be preloaded: ignored. start upgrade begin Exception: Traceback (most recent call last): File "/etc/init.d/nsx-datapath", line 1267, in <module> UnloadKernelModules() File "/etc/init.d/nsx-datapath", line 1083, in UnloadKernelModules unloadModule(modName, modName in ['nsxt-vsip']) File "/etc/init.d/nsx-datapath", line 1068, in unloadModule (moduleName, out.decode())) KernelModulesException: Failed to unload module nsxt-switch-security: vmkload_mod: Cannot remove module nsxt-switch-security: Consumed resource count of module is not zero It is not safe to continue. Please reboot the host immediately to discard the unfinished update. Please refer to the log file for more details..

@ESXi host : /var/log/vmkernel.log

2019-02-21T11:33:05.659Z cpu13:2399604)Mod: 5059: Unloading module <nsxt-switch-security> ...
2019-02-21T11:33:05.659Z cpu13:2399604)nsxt-switch-security: cleanup_module:386: [nsx@6876 comp="nsx-esx" subcomp="swsec"]Starting Cleanup
2019-02-21T11:33:05.659Z cpu13:2399604)nsxt-switch-security: SwSecRtmUnsubscribe:331: [nsx@6876 comp="nsx-esx" subcomp="swsec"]SwSec Unsubscribing to RTM Event
2019-02-21T11:33:05.659Z cpu13:2399604)nsxt-switch-security: SwSec_VMotionUnregister:210: [nsx@6876 comp="nsx-esx" subcomp="swsec"]SwSec Unegistering VMotion CBs
2019-02-21T11:33:05.659Z cpu13:2399604)nsxt-switch-security: SwSec_PropCleanup:384: [nsx@6876 comp="nsx-esx" subcomp="swsec"]Unregistered swsec property handler com.vmware.vswitch.port.swsec.security
2019-02-21T11:33:05.659Z cpu13:2399604)nsxt-switch-security: SwSec_PropCleanup:385: [nsx@6876 comp="nsx-esx" subcomp="swsec"]Unregistered swsec property handler com.vmware.vswitch.port.swsec.discovery
2019-02-21T11:33:05.659Z cpu13:2399604)nsxt-switch-security: SwSec_PropCleanup:386: [nsx@6876 comp="nsx-esx" subcomp="swsec"]Unregistered swsec property handler com.vmware.vswitch.port.swsec.enabled
2019-02-21T11:33:05.659Z cpu13:2399604)nsxt-switch-security: SwSecGenericCleanup:183: [nsx@6876 comp="nsx-esx" subcomp="swsec"]Starting SwSecGenericCleanup
2019-02-21T11:33:05.659Z cpu1:2116926)nsxt-switch-security: SwSecAgingWorldCheckExit:87: [nsx@6876 comp="nsx-esx" subcomp="swsec"]Exiting Aging World
2019-02-21T11:33:05.659Z cpu13:2399604)nsxt-switch-security: SwSecAgingWorldDestroy:411: [nsx@6876 comp="nsx-esx" subcomp="swsec"]Error destroying PriQ (0xbad0004): Busy
2019-02-21T11:33:05.659Z cpu13:2399604)nsxt-switch-security: SwSecGenericCleanup:187: [nsx@6876 comp="nsx-esx" subcomp="swsec"]Error destroying Aging World
2019-02-21T11:33:05.659Z cpu13:2399604)WARNING: Heap: 2734: Non-empty heap (nsxt-switch-security) being destroyed (avail is 110240, should be 192336).
2019-02-21T11:33:05.659Z cpu13:2399604)ALERT: Mod: 5212: Failed to unload module nsxt-switch-security, since its consumed resource count is 1. Waiting...
2019-02-21T11:33:10.677Z cpu13:2399604)ALERT: Mod: 5241: Failed to unload module nsxt-switch-security, since its consumed resource count is 1. Giving up.

Cause

The host VIB update fails since switch security module fails to unload. The issue occurs only if IP discovery feature is enabled in switching profile and performing an in-place upgrade from NSX-T 2.3.1 to NSX-T 2.4.0 with host running ESXi-6.7EP06 (build 11675023)

Resolution

This issue only occurs when upgrading from NSX-T 2.3.1 release to NSX-T 2.4.0. Future upgrades from NSX-T 2.4.0 to later releases will not experience the issue.

Workaround

Perform maintenance mode upgrade.
Put the host in maintenance mode, reboot the host, followed by NSX host component upgrade..

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

No results for undefined

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