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

NSX-v Controller(s) rejecting the requests from hosts to join VNI(s) (66739)

Last Updated: 5/16/2021Categories: TroubleshootingTotal Views: 8819Language:
English

3 like this article

Subscribe to get an email
newsletter with new updates

3 people found this helpful Please provide article feedback:

Symptoms

NSX Data Center for vSphere version is 6.3.x or pre 6.4.4

ESXi host logs (netcpa.log) may display message(s) similar to:

#grep -hE "notification from controller for invalid|notification from controller error" /var/run/log/netcpa.log
2019-12-07T11:43:03.643Z error netcpa[2104030] [Originator@6876 sub=Default] Vxlan: notification from controller error/sub:4/1
2019-12-07T11:43:03.643Z error netcpa[2104030] [Originator@6876 sub=Default] Vxlan: notification from controller for invalid VNI 15212, switchID 0
2019-12-07T11:43:08.645Z error netcpa[2104030] [Originator@6876 sub=Default] Vxlan: notification from controller error/sub:4/1
2019-12-07T11:43:08.645Z error netcpa[2104030] [Originator@6876 sub=Default] Vxlan: notification from controller for invalid VNI 15211, switchID 0
2019-12-07T11:43:08.645Z error netcpa[2104030] [Originator@6876 sub=Default] Vxlan: notification from controller error/sub:4/1
2019-12-07T11:43:08.645Z error netcpa[2104030] [Originator@6876 sub=Default] Vxlan: notification from controller for invalid VNI 15212, switchID 0

NSX Controller logs (syslog) display message(s) similar to:

#show log syslog filtered-by “Try to join VNI.* not assigned to this node by TransportSwitch”
2018-12-12T11:15:18.226817+00:00 2018-12-12 11: 15:18,226 2513561004 [vxlan worker 3] WARN com.vmware.controller.apps.vxlan.VxlanService  - Try to join VNI 5008 not assigned to this node by TransportSwitch [Connection [ip=11.12.13.11:21641, cnnId=46], swId=0]
2018-12-12T11:15:18.227796+00:00 2018-12-12 11: 15:18,227 2513561005 [vxlan worker 2] WARN com.vmware.controller.apps.vxlan.VxlanService  - Try to join VNI 5021 not assigned to this node by TransportSwitch [Connection [ip=11.12.13.11:21641, cnnId=46], swId=0]
2018-12-12T11:15:18.755600+00:00 2018-12-12 11: 15:18,755 2513561533 [vxlan worker 2] WARN com.vmware.controller.apps.vxlan.VxlanService  - Try to join VNI 5000 not assigned to this node by TransportSwitch [Connection [ip=10.139.211.138:42621, cnnId=50], swId=0]
2018-12-12T11:15:18.756518+00:00 2018-12-12 11: 15:18,756 2513561534 [vxlan worker 1] WARN com.vmware.controller.apps.vxlan.VxlanService  - Try to join VNI 5018 not assigned to this node by TransportSwitch [Connection [ip=11.12.13.14.138:42621, cnnId=50], swId=0]

ESXi host shows the NSX Controller responsible for the impacted VXLAN as "down"

#net-vdl2 -l

Example of output:
(...) output omitted
VXLAN network:  15212
Multicast IP:   N/A (headend replication)
Control plane:  Enabled ()
Controller:     10.10.10.10 (down) <<--------------
Controller Disconnected Mode: no
Multicast Routing Domain ID: -N/A-
MAC entry count:        26
ARP entry count:        0
Port count:     1
VXLAN network:  15211
Multicast IP:   N/A (headend replication)
Control plane:  Enabled ()
Controller:     10.10.10.10 (down) <<--------------
Controller Disconnected Mode: no
Multicast Routing Domain ID: -N/A-
MAC entry count:        1
ARP entry count:        0
(...) output omitted

ESXi host has a TCP socket opened on port TCP 1234 to the NSX Controller marked as "down":

#esxcli network ip connection list | grep “1234 “
Example of output:
tcp         0       0  10.200.19.27:20306   10.10.10.10:1234     ESTABLISHED   2103863  newreno  netcpa-worker
tcp         0       0  10.200.19.27:20305   10.10.10.9:1234      ESTABLISHED   2103839  newreno  netcpa-worker
tcp         0       0  10.200.19.27:20304   10.10.10.8:1234      ESTABLISHED   2103842  newreno  netcpa-worker

Cause

Sometimes there is a race condition between two cluster events (Cluster down and Sharding Update) in the Controller functionality. When this error is observed Controller may reject VNI join request from ESXi hosts.

Impact / Risks

This will lead to network outages for VMs on that ESXi host connected to that Logical Switch.
This is a known issue affecting:

VMware NSX for vSphere 6.3.3 to NSX for vSphere 6.3.7

VMware NSX for vSphere 6.4.0 to NSX for vSphere 6.4.4.

Resolution

This issue is resolved in VMware NSX for vSphere 6.4.5, available at VMware Downloads.

Workaround

To workaround the issue, restart the impacted NSX Controller. To identify the impacted NSX controller follow the steps below:

1.  Verify the NSX controller(s) marked as “down”
# net-vdl2 -l

Example of output:
(...) output omitted
VXLAN network:  15212
Multicast IP:   N/A (headend replication)
Control plane:  Enabled ()
Controller:     10.10.10.10 (down) <<--------------
Controller Disconnected Mode: no
Multicast Routing Domain ID: -N/A-
MAC entry count:        26
ARP entry count:        0
Port count:     1
VXLAN network:  15211
Multicast IP:   N/A (headend replication)
Control plane:  Enabled ()
Controller:     10.10.10.10 (down) <<--------------
Controller Disconnected Mode: no
Multicast Routing Domain ID: -N/A-
MAC entry count:        1
ARP entry count:        0
(...) output omitted

2.  Confirm the ESXi host have a TCP socket open on port 1234 for the NSX controller(s) marked as “down”
#esxcli network ip connection list | grep “1234 “

Example of output:
tcp         0       0  10.200.19.27:20306   10.10.10.10:1234     ESTABLISHED   2103863  newreno  netcpa-worker
tcp         0       0  10.200.19.27:20305   10.10.10.9:1234      ESTABLISHED   2103839  newreno  netcpa-worker
tcp         0       0  10.200.19.27:20304   10.10.10.8:1234      ESTABLISHED   2103842  newreno  netcpa-worker

3.  Review the NSX Controller logs and confirm you can see the error “Try to join VNI XXX not assigned to this node by TransportSwitch”
#show log syslog filtered-by “Try to join VNI.* not assigned to this node by TransportSwitch”

Example of output:
2018-12-12T11:15:18.226817+00:00 2018-12-12 11: 15:18,226 2513561004 [vxlan worker 3] WARN com.vmware.controller.apps.vxlan.VxlanService  - Try to join VNI 5008 not assigned to this node by TransportSwitch [Connection [ip=11.12.13.11:21641, cnnId=46], swId=0]
2018-12-12T11:15:18.227796+00:00 2018-12-12 11: 15:18,227 2513561005 [vxlan worker 2] WARN com.vmware.controller.apps.vxlan.VxlanService  - Try to join VNI 5021 not assigned to this node by TransportSwitch [Connection [ip=11.12.13.11:21641, cnnId=46], swId=0]

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
•
Instalar y actualizar VMware Tools en vSphere (2004754)

KB
•
[ハードウェア ステータス] タブで警告とエラーをクリアする方法 (2011531)

KB
•
调整 ESX 主机时区 (1436)

Results 1-4 of 4

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

VMware NSX for vSphere 6.3.x

Take Our Survey

Support Assistant