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-T MANAGER and HTTPS services goes down frequently due to incorrect NAT configuration (78298)

Last Updated: 2/23/2024Categories: TroubleshootingTotal Views: 9145Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Access to the NSX-T manager GUI fails or is intermittent.

REST API calls to the NSX-T manager may fail.

A new NAT (SNAT or DNAT) rule was added with address: 0.0.0.0/0.

The CPU of the NSX-T manager is high.

In the NSX-T manager CLI when you run the command 'get cluster status'

You will notice the HTTPS (reverse-proxy) and MANAGER (proton) service is down randomly on different managers, see example below:

Group Type: MANAGER

Group Status: DEGRADED

Members:

UUID FQDN IP STATUS

3a6c0842-1aa1-7f53-5669-14376f32b56f manager01 192.168.110.51 UP

6dd22d42--6a26-32f6-980a-fc7f7b685247 manager02 192.168.110.52 UP

0b172d42-19a0-b3fe--839a-320e8a494ebb manager03 192.168.110.53 DOWN

Group Type: HTTPS

Group Status: DEGRADED

Members:

UUID FQDN IP STATUS

3a6c0842-1aa1-7f53-5669-14376f32b56f manager01 192.168.110.51 UP

6dd22d42-6a26-32f6-980a-fc7f7b685247 manager02 192.168.110.52 UP

0b172d42-19a0-b3fe--839a-320e8a494ebb manager03 192.168.110.53 DOWN

Then a few minutes later it may flip to other managers:

Group Type: MANAGER

Group Status: DEGRADED

Members:

UUID FQDN IP STATUS

3a6c0842-1aa1-7f53-5669-14376f32b56f manager01 192.168.110.51 UP

6dd22d42--6a26-32f6-980a-fc7f7b685247 manager02 192.168.110.52 DOWN

0b172d42-19a0-b3fe--839a-320e8a494ebb manager03 192.168.110.53 UP

Group Type: HTTPS

Group Status: DEGRADED

Members:

UUID FQDN IP STATUS

3a6c0842-1aa1-7f53-5669-14376f32b56f manager01 192.168.110.51 UP

6dd22d42-6a26-32f6-980a-fc7f7b685247 manager02 192.168.110.52 DOWN

0b172d42-19a0-b3fe--839a-320e8a494ebb manager03 192.168.110.53 UP

You may see log entries in the log '/var/log/proton/proton-tomcat-wrapper.log' which indicate a Java Out of Memory issue:

STATUS | wrapper | 2020/02/03 13:31:31 | The JVM has run out of memory. Requesting thread dump.

STATUS | wrapper | 2020/02/03 13:31:31 | Dumping JVM state.

STATUS | wrapper | 2020/02/03 13:31:31 | The JVM has run out of memory. Restarting JVM.

INFO | jvm 1 | 2020/02/03 13:31:31 | Dumping heap to /image/core/proton_oom.hprof ...

ERROR | wrapper | 2020/02/03 13:32:06 | Shutdown failed: Timed out waiting for signal from JVM.

STATUS | wrapper | 2020/02/03 13:32:06 | Dumping JVM state..

STATUS | wrapper | 2020/02/03 13:44:34 | The JVM has run out of memory. Restarting JVM.

INFO | jvm 2 | 2020/02/03 13:44:34 | Dumping heap to /image/core/proton_oom.hprof ...

INFO | jvm 2 | 2020/02/03 13:44:34 | Unable to create /image/core/proton_oom.hprof: File exists

ERROR | wrapper | 2020/02/03 13:45:08 | Shutdown failed: Timed out waiting for signal from JVM.

STATUS | wrapper | 2020/02/03 13:45:08 | Dumping JVM state.

ERROR | wrapper | 2020/02/03 13:45:13 | JVM did not exit on request, termination requested.

STATUS | wrapper | 2020/02/03 13:45:13 | JVM received a signal SIGKILL (9).

STATUS | wrapper | 2020/02/03 13:45:13 | JVM process is gone.

Cause

This issue occur due to the process used to evaluate a NAT (SNAT or DNAT) rule which contains the 0.0.0.0/0 address range.

Note: this is the full IPv4 address range.

Currently the manager tries to implement each of these addresses on the loopback of the system.

This amount of processing causes java to run out of memory and the services HTTPS and MANAGER to continuously crash.

Resolution

This issue is resolved in VMware NSX-T Data Center 3.0, available at VMware Downloads.

Workaround

Do not use the range '0.0.0.0/0' when creating NAT rules, please use the word 'ANY' instead.

Once the '0.0.0.0/0' address is changed or removed, all 3 NSX-T managers need to be restarted at the same time.

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)

KB
•
Downloading and Installing the standalone VMware Remote Console (VMRC) in vSphere (2091284)

Results 1-3 of 3

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

Related Versions:

VMware NSX-T Data Center

Take Our Survey

Support Assistant