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

An ESXi host boots without the NSX vdrPort connected and logical routing does not function (52903)

Last Updated: 5/25/2018Categories: TroubleshootingTotal Views: 4535Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

After rebooting an ESXi host, East/West DLR routing does not function and VMs cannot communicate between Logical Switches.

Creation of the vdrPort fails.

In the /var/log/netcpa.log file of the ESXi host, you see entries similar to:

2018-02-08T23:44:19.431Z error netcpa[3FFEDA29700] [Originator@6876 sub=Default] Failed to add vdr port on dvs 96 ff 2c 50 0e 5d ed 4a-e0 15 b3 36 90 19 41 5d, Not found

Note: This happens because the locally cached configuration of the vSphere Distributed Switch can not be found on the host.

In the /var/log/hostd.log file of the ESXi host, you see the DVS registration occurs after the attempt to add the vdrPort with entries similar to:

2018-02-08T23:44:28.389Z info hostd[4F540B70] [Originator@6876 sub=Hostsvc.DvsTracker] Registered Dvs 96 ff 2c 50 0e 5d ed 4a-e0 15 b3 36 90 19 41 5d

Running the net-vdr -C -l command on the ESXi host fails to list any vdrPorts connected.

For example:

[root@ESXi00002:~] net-vdr -C -l
Host locale Id: 421b32a6-ef4b-acb4-ad50-abceaf4d3697
Connection Information:
-----------------------
DvsName VdrPort NumLifs VdrVmac
------- ------- ------- -------

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

Cause

This issue occurs due to a race condition where the Distributed Switch initialization activities occur after the host attempts to connect the vdrPort. The operation fails and is not retried. The registration of the ESXi host with the distributed switch can be delayed for a number of reasons including slow vCenter Server performance or the varying speed of the post-boot activities of host profiles on stateless auto-deploy ESXi hosts.

Impact / Risks

When the vdrPort does not exist on the ESXi host, all traffic destined to the DLR module on the host will be dropped. This will result in non-functional DLR routing. If an ESG exists on the host and a Logical Switch is used as a transit network between DLR and ESG, the North/South traffic flows may also be impacted.

Resolution

This issue is resolved in:

VMware NSX for vSphere 6.3.6, available at VMware Downloads.

VMware NSX for vSphere 6.4.1, available at VMware Downloads.

Workaround

To work around this issue if you do not want to upgrade, restart the control plane service (netcpa) on the ESXi host after the DVS is registered. This triggers the connection of the vdrPort.

This can be done using the /etc/init.d/netcpad restart command.

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)

Result 1 of 1

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