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 NSX Cross vCenter environment the BGP password is not replicated to newly promoted Primary manager (60367)

Last Updated: 6/10/2019Categories: TroubleshootingTotal Views: 3335Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

During failover or failback in an NSX Cross vCenter environment, the BGP relationship may not come up.

In the NSX Edge logs (show log follow):

2019-05-29T16:55:39+00:00 NSX-edge-1-0 kernel[]: [default]:  [kern.info] TCP: MD5 Hash failed for (192.168.119.1, 25307)->(192.168.119.254, 179)
2019-05-29T16:55:40+00:00 NSX-edge-1-0 kernel[]: [default]:  [kern.info] TCP: MD5 Hash failed for (192.168.119.1, 25307)->(192.168.119.254, 179)
2019-05-29T16:55:42+00:00 NSX-edge-1-0 kernel[]: [default]:  [kern.info] TCP: MD5 Hash failed for (192.168.119.1, 25307)->(192.168.119.254, 179)
2019-05-29T16:55:46+00:00 NSX-edge-1-0 kernel[]: [default]:  [kern.info] TCP: MD5 Hash failed for (192.168.119.1, 25307)->(192.168.119.254, 179)
2019-05-29T16:55:54+00:00 NSX-edge-1-0 kernel[]: [default]:  [kern.info] TCP: MD5 Hash failed for (192.168.119.1, 25307)->(192.168.119.254, 179)

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

Cause

There is an issue with NSX Cross vCenter 6.3.x and 6.4.x where the NSX manager fails to copy the password over from the primary NSX manager to the secondary NSX manager, which will now be the new primary NSX manager.
The means the BGP relationship cannot form and is stuck in connect/active state.
To validate if the BGP password was not sync'ed to the secondary NSX manager (now new primary NSX manager), the following API can be used to retrieve the BGP password. Be aware this returns the password in clear text.
GET /api/4.0/edges/<edge-id>?global_published_config

Impact / Risks

This issue can lead to a dataplane impact, as routes are not learned and published.

Resolution

This is resolved in NSX 6.4.4.

Workaround

If you are unable to upgrade, you can use the following workaround:

Manually re-entering the same BGP password and save, will allow the BGP relationships to form again.

Note: It is advised to include this step in any failover/failback procedures, just after the new UDLR control VM is deployed.

If BGP password is unknown, the following API can be used to retrieve the BGP password. Be aware this returns the password in cleartext:

Note: This API can only be run on the primary manager, so if the failover has already occurred and the new primary does not have the password, you will not see the BGP password.

GET /api/4.0/edges/<edge-id>?global_published_config

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:

VMware NSX for vSphere

VMware NSX Data Center for vSphere

Related Versions:

VMware NSX for vSphere 6.4.x

VMware NSX for vSphere 6.3.x

Take Our Survey

Support Assistant