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 Edge HA (for load balancer) split-brain issues when grouping objects configuration (used in load balancer) is modified. (59549)

Last Updated: 1/2/2019Categories: TroubleshootingTotal Views: 14627Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

The High Availability (HA) channel between Edge VMs goes down as shown in [show service highavailability] command: show service highavailability

Highavailability Healthcheck Status:
This unit [0]: Up   Active: 1
Peer unit [1]: Up   Active: 0
Session via vNic_1: 1.1.1.1:1.1.1.2 Unreachable.

The Edge VM index -0 HA interface IP is not correct (switch to Edge VM index -1): show interface vNic_1 (Where vNic_1 is the Mgmt HA interface)

vNic_1    Link encap:Ethernet  HWaddr 00:50:56:AB:AB:BC
inet addr:1.1.1.2  Bcast:1.1.1.3  Mask:255.255.255.252
inet6 addr: fe80::250:56ff:feab:528b/64 Scope:Link
UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
RX packets:19223251 errors:0 dropped:261 overruns:0 frame:0
TX packets:17289853 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000
RX bytes:2223722150 (2120.7 Mb)  TX bytes:3620139033 (3452.4 Mb)

In the Edge log, we see the NSX Manager sending a configuration (json file) with the instruction to reload the configuration: show log follow

2018-10-17T10:07:31+00:00 EdgeLBHA-0 config[]: [default]:  [daemon.info] INFO :: VseCommandHandler :: command json file:
..
2018-10-17T10:07:34+00:00 EdgeLBHA-0  [user.notice]
2018-10-17T10:07:34+00:00 EdgeLBHA-0 config[]: [default]:  [daemon.debug] DEBUG :: C_ServiceControl :: Checking status, op: unmonitor, service: syslog-ng, status: Not monitored
2018-10-17T10:07:34+00:00 EdgeLBHA-0 config[]: [default]:  [daemon.info] INFO :: C_ServiceControl :: Action unmonitor for syslog-ng done
2018-10-17T10:07:34+00:00 EdgeLBHA-0 config[]: [default]:  [daemon.info] INFO :: C_ServiceControl :: serverid: 0, state: 0
2018-10-17T10:07:34+00:00 EdgeLBHA-0 config[]: [default]:  [daemon.debug] DEBUG :: C_ServiceControl :: Send signal to reload, server: syslog-ng, signal: HUP, pids: 833
2018-10-17T10:07:34+00:00 EdgeLBHA-1 syslog-ng[833]: [default]:  [syslog.notice] Configuration reload request received, reloading configuration;
2018-10-17T10:07:34+00:00 EdgeLBHA-1 syslog-ng[833]: [default]:  [syslog.notice] Configuration reload finished;

From the above log extract, we see the hostname of the VM moving from index -0 to index-1.

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

Purpose

In NSX 6.4.1 or above, when you have the following configurations, the edge HA (with load balancer) enters a split-brain situation when the grouping objects setting (for load balancer) is modified.

NSX Edge are configured in High Availability (HA) mode.

NSX Edge are also configured as Load balancer (LB).

NSX Edge Load balancer (LB) pool members are configured with grouping objects (Security groups, IP sets, etc...).

Cause

When the Grouping Objects configuration (Security groups, IP sets, etc.) used within load balancer Pool members is edited, the NSX manager pushes a faulty configuration to the Edge VMs. As a result, it will cause a split-brain scenario in the edge HA (of load balancer).

Impact / Risks

Split-brain scenario on the impacted Edges.

Possible data plane impact on the services running on the impacted Edges.

Resolution

This issue is resolved in VMware NSX Data Center for vSphere 6.4.4.

Workaround

To workaround this issue, you need to follow either one of the below:

Disable HA on the Edge.

Force sync or redeploying the impacted Edge fixes the issue temporarily until the Grouping Objects configuration is edited.

Force sync NSX Edge: https://docs.vmware.com/en/VMware-NSX-for-vSphere/6.4/com.vmware.nsx.admin.doc/GUID-21FF2937-4CDF-491C-933E-8F44E21ED55E.html?hWord=N4IghgNiBcIGYHsBOBjApgAgM4E8B2KIAvkA

Redeploy NSX Edge: https://docs.vmware.com/en/VMware-NSX-for-vSphere/6.4/com.vmware.nsx.admin.doc/GUID-23F6CC61-7A16-4CEB-887A-9D56035A7EF4.html

Editing the HA configuration of the Edge : "Enable/disable HA log level", fixes the issue temporarily until the Grouping Objects configuration is edited.

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
•
Download and Install VMware Fusion (2014097)

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

Take Our Survey

Support Assistant