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

Log spew in the vmkernel.log file on the error: "Lif Update: Bridge operation Failed" (52825)

Last Updated: 3/30/2018Categories: TroubleshootingTotal Views: 4186Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

​Log spew in the /var/log/vmkernel.log file on the affected ESXi host.

You see entries similar to:

"Lif Update: Bridge operation Failed".

In the /var/log/vmkernel.log file on the affected ESXi host, you see entries that shows when the full sync occurs (by default 10 min) similar to:

2018-02-08T15:14:49.735Z cpu6:66548)vdrb: VdrRtFlushTimeOut:1225: INST:[I:0x139b] Flush route triggered by defer flush time (timer refereshed 0 times)
2018-02-08T15:14:54.646Z cpu5:72696)WARNING: vdrb: VdrProcessLifUpdateMessageAddLifs:1094: CP:[I:0x138c] Lif Update: Bridge operation Failed, status: Failure
2018-02-08T15:14:54.646Z cpu5:72696)vdrb: VdrRtCreateFlushTimer:1268: INST:[I:0x138c] Route defer flush timer is set to 300 Secs (status = 0)

The VDR instance is stuck in the “I”(init) state.

For example:

VDR Instance default+edge-2 Control Plane Sync State:

Sync Status Legend: [I:Init], [G:Gen number error], [U:Update error], [N:Num of TLV mismatch]

Time Stamp                      223712        223177        222577        221977        221377
Status                               I                    I                   I                    I                   I
…...
……

NSX Controllers show VDR instance is not in-sync.

For example:

nsx-controller # show control-cluster logical-routers instance 0x1514
LR-Id      LR-Name                                            Universal Service-Controller Egress-Locale      In-Sync Sync-Category
0x1514     default+edge-3                                     false     10.146.96.224      local                       No         NORMAL

One or more connections is in ‘synching’ or ‘error state’.

For example:

nsx-controller # show control-cluster logical-routers connections 0x1514
Id     IP                      Version         Locale-Id                                              Sync-State
16     10.146.101.57    6.2     00000000-0000-0000-0000-000000000000 SYNCHING
18     10.146.105.64    6.2     00000000-0000-0000-0000-000000000000 SYNCHING
19     10.146.103.117   6.2     00000000-0000-0000-0000-000000000000 SYNCHING
15     10.146.106.51    6.2     00000000-0000-0000-0000-000000000000 SYNCHING

In the vnet-controller logs cloudnet_java-vnet-controller*.log file, you see entries similar to:

[vdr worker 2] ERROR com.vmware.controller.apps.vdr.handler.VdrStatusResponseHandler  - Status response from conn Connection [ip=10.146.101.57:62228, cnnId=11] for Vdr 5394. Seq Num: -11736, Expected seq num: -11736, Status: SYNCHING
[vdr worker 2] INFO com.vmware.controller.apps.vdr.VdrService  - Initiating full state sync for vdr 0x1512 and connection Connection [ip=10.146.101.57:62228, cnnId=11]

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Cause

The issue occurs when the NSX Distributed Logical Router (DLR) are used and no static or dynamic routes are configured (only connected routes exist on the instance).

Impact / Risks

Log spamming no other impact.

Resolution

This issue is resolved in:

VMware NSX for vSphere 6.3.6, available at VMware Downloads.

VMware NSX for vSphere 6.4.0, available at VMware Downloads.

Workaround

To work around this issue if you do not want to upgrade:

Option 1: Configure a (dummy) route on the DLR.

Find a subnet which is not useful in the network.

From the NSX User Interface ( UI), set the route in DLR configuration.

For example: 123.1.1.0/24 192.168.1.2

Option 2:
Disable the defer route flush timer by setting it to 0 by running this command:

net-vdr --instance -o setTunables -n rtDeferFlushTimer -v 0 default+edge-2

Note: Option 1 is recommended as Option 2 changes are not persistent if the ESXi host is rebooted and will be applied per ESXi host and not globally.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

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

KB
•
ESXi 5 VMware Tools の完全インストールの後に Windows ネットワーク ファイル コピーのパフォーマンスが低下する (2034490)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware NSX for vSphere

Related Versions:

VMware NSX for vSphere 6.3.x

Take Our Survey

Support Assistant