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

In container environments NSX-T host upgrades fail at 10% or get stuck trying to put host in maintenance mode (70865)

Last Updated: 12/24/2019Categories: InformationalTotal Views: 5229Language:
Chinese (Simplified)JapaneseEnglish

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

The following conditions are met:

NSX-T ESXi host upgrade fails with this exception

Install of offline bundle failed on host <UUID> with error

Exception('VSIP Filters not cleared') Exception: VSIP Filters not cleared

The ESXi host contains stale dvfilter entries identified by "bad vnic uuid"

#vsipioctl getfilters

Filter Name : nic-79253-eth47-vmware-sfw.1
VM UUID :
VNIC Index : 0
VNIC UUID : bad vnic uuid
VIF ID : bfcf0811-dbe8-492c-8fed-e15e05687601
Service Profile : --NOT SET--
Filter Hash : 8497

Containers are deployed in the environment

Note, in some cases this issue may manifest itself as a failure to enter maintenance mode at the start of the upgrade process

The ESXi host gets stuck while entering Maintenance Mode as some of the VMs/Worker nodes fail to get migrated to other ESXi hosts.

VM tasks reports an error similar to:

Failed waiting for data. Error 195887105. Failure.

Cause

This issue occurs because in some cases when VMs running containers are vmotioned from a host, the dvfilter is not destroyed as part of the cleanup process. This results in stale dvfilters left behind on the ESXi host.

As part of an NSX-T upgrade dvfilters on a host must be deleted, it is not possible to remove these stale dvfilters and so the host upgrade fails.

Resolution

This issue is resolved in VMware ESXi 6.5 P04 and VMware ESXi 6.7 Update 3, available at VMware Downloads.

Before performing an NSX-T upgrade, ESXi hosts should be upgraded to the fixed version.

Workaround

To work around this issue if you do not want to upgrade, the ESXi host must be rebooted to clear the stale dvfilters.

There are 2 options

Automatic reboot all hosts during upgrade:

Change the group upgrade mode to reboot hosts by default as follows:

Find the group id for the cluster using GET api/v1/upgrade/upgrade-unit-groups?component_type=HOST or from UI

GET api/v1/upgrade/upgrade-unit-groups/<group id>

In the above response, change extended_configuration value by updating {"key" : "rebootless_upgrade", "value" : "false"}.

PUT the modified payload to api/v1/upgrade/upgrade-unit-groups/<group uuid>

or

Manual reboot of hosts
Post reboot, the NSX-T upgrade must be performed before exiting maintenance mode as moving VMs onto and off the host again may reintroduce the problem.

Select to Pause the upgrade when an upgrade unit fails to upgrade.

Start host upgrade.

Once a host upgrade fails due to the issue described in this article:

a) Confirm the host is in vSphere maintenance mode and reboot it to clear the stale dvfilters.
b) Post reboot, the ESXi host should continue to remain in vSphere maintenance mode.
c) To retry the NSX-T upgrade, the host must be taken out of NSX maintenance mode.
Select System > Fabric > Nodes > Host Transport Nodes.
Select the ESXi host and from Actions and click "Exit Maintenance Mode".
If "Exit Maintenance mode" is not available, via the UI, use the API.
POST https://manager/api/v1/transport-nodes/{node_id}?action=exit_maintenance_mode.
d) On the Upgrade Coordinator, click Reset to clear the error.
e) Restart the host upgrade. It will now retry the problem host and allow the upgrade to proceed.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
Chinese (Simplified)JapaneseEnglish

Attachments

Additional Resources

KB
•
使用 DRS 高级设置 - IsClusterManaged (70864)

KB
•
适用于 VMware Cloud on AWS 的 Dell EMC Avamar 19.1 (70846)

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

KB
•
vCenter Server 6.0 のインストール/デプロイの方法 (70795)

Results 1-4 of 4

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