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 Manager fails and disconnects from the vCenter Server after a CPU spike (52343)

Last Updated: 2/15/2018Categories: TroubleshootingTotal Views: 4381Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

NSX Manager fails and disconnects from the vCenter Server after a CPU spike.

NSX Manager User Interface (UI) indicates High CPU alerts with Firewall among top consumers.

NSX Manager restarts automatically during which it is disconnected from the vCenter Server temporarily.

When NSX Manager gets disconnected from the vCenter Server, the NGC UI displays the error similar to:

No NSX Manager available

In the vsm.log file, you see entries similar to:

SimpleTaskManager:171 - Error during publish Task AppNotificationHandler.
java.lang.OutOfMemoryError: GC overhead limit exceeded
at
org.hibernate.type.descriptor.sql.DecimalTypeDescriptor.getExtractor(DecimalTypeDescriptor.java:60)
at
org.hibernate.type.AbstractStandardBasicType.nullSafeGet(AbstractStandardBasicType.java:260)
at
org.hibernate.type.AbstractStandardBasicType.nullSafeGet(AbstractStandardBasicType.java:256)
at
org.hibernate.type.AbstractStandardBasicType.nullSafeGet(AbstractStandardBasicType.java:246)
at
org.hibernate.loader.hql.QueryLoader.getResultRow(QueryLoader.java:453)
at
org.hibernate.loader.hql.QueryLoader.getResultColumnOrRow(QueryLoader.java:436)
at org.hibernate.loader.Loader.getRowFromResultSet(Loader.java:769)
at org.hibernate.loader.Loader.processResultSet(Loader.java:985)
at org.hibernate.loader.Loader.doQuery(Loader.java:943)
at
org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:349)
at org.hibernate.loader.Loader.doList(Loader.java:2615)
at org.hibernate.loader.Loader.doList(Loader.java:2598)
at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2430)
at org.hibernate.loader.Loader.list(Loader.java:2425)
at org.hibernate.loader.hql.QueryLoader.list(QueryLoader.java:502)
at
org.hibernate.hql.internal.ast.QueryTranslatorImpl.list(QueryTranslatorImpl.java:379)
at
org.hibernate.engine.query.spi.HQLQueryPlan.performList(HQLQueryPlan.java:216)
at org.hibernate.internal.SessionImpl.list(SessionImpl.java:1488)
at
org.hibernate.query.internal.AbstractProducedQuery.doList(AbstractProducedQuery.java:1445)
at
org.hibernate.query.internal.AbstractProducedQuery.list(AbstractProducedQuery.java:1414)
at org.hibernate.query.Query.getResultList(Query.java:146)
at
com.vmware.vshield.vsm.dao.AbstractTranslationDao.getTargetNodesByDynamicCriteria_aroundBody8(AbstractTranslationDao.java:147)
at
com.vmware.vshield.vsm.dao.AbstractTranslationDao$AjcClosure9.run(AbstractTranslationDao.java:1)
at
org.aspectj.runtime.reflect.JoinPointImpl.proceed(JoinPointImpl.java:149)
at
com.vmware.vshield.vsm.aspects.elapsedtime.ElapsedTimeAspect.doPerformance(ElapsedTimeAspect.java:61)
at
com.vmware.vshield.vsm.aspects.elapsedtime.ElapsedTimeAspect.ajc$inlineAccessMethod$com_vmware_vshield_vsm_aspects_elapsedtime_ElapsedTimeAspect$com_vmware_vshield_vsm_aspects_elapsedtime_ElapsedTimeAspect$doPerformance(ElapsedTimeAspect.java:1)
at
com.vmware.vshield.vsm.aspects.elapsedtime.ElapsedTimeAspect.annotatedMethod(ElapsedTimeAspect.java:56)
at
com.vmware.vshield.vsm.dao.AbstractTranslationDao.getTargetNodesByDynamicCriteria(AbstractTranslationDao.java:139)
at
com.vmware.vshield.vsm.dynamicmembership.service.translate.DynamicSetTranslator.translateCriteria(DynamicSetTranslator.java:151)
at
com.vmware.vshield.vsm.dynamicmembership.service.translate.DynamicSetTranslator.translateInternal(DynamicSetTranslator.java:131)
at
com.vmware.vshield.vsm.securitygroup.service.translate.AbstractTranslator.translate(AbstractTranslator.java:83)
at
com.vmware.vshield.vsm.securitygroup.service.translate.TranslationServiceVersion2.translate(TranslationServiceVersion2.java:63)...

In the nsx-wrapper logs, you see entries similar to:

INFO | jvm 38 | 2018/01/04 10:41:34 | java.lang.OutOfMemoryError:
GC overhead limit exceeded
STATUS | wrapper | 2018/01/04 10:41:34 | The JVM has run out of memory.
Requesting thread dump.
STATUS | wrapper | 2018/01/04 10:41:34 | Dumping JVM state.
STATUS | wrapper | 2018/01/04 10:41:34 | The JVM has run out of memory.
Restarting JVM.

In the nsx-wrapper logs, you see a thread having stack traces with following lines in runnable state similar to:

Line 10060: INFO | jvm 38 | 2018/01/04 10:35:08 | at com.vmware.vshield.app.firewall.containers.IPListCollecter.getIpList(IPListCollecter.java:101)
Line 10061: INFO | jvm 38 | 2018/01/04 10:35:08 | at com.vmware.vshield.app.firewall.containers.IPListCollecter.getIpList(IPListCollecter.java:90)
Line 10062: INFO | jvm 38 | 2018/01/04 10:35:08 | at com.vmware.vshield.app.firewall.containers.IPListHandler.collectIpListForNode_aroundBody2(IPListHandler.java:77)
Line 10063: INFO | jvm 38 | 2018/01/04 10:35:08 | at com.vmware.vshield.app.firewall.containers.IPListHandler$AjcClosure3.run(IPListHandler.java:1)
Line 10068: INFO | jvm 38 | 2018/01/04 10:35:08 | at com.vmware.vshield.app.firewall.containers.IPListHandler.collectIpListForNode(IPListHandler.java:76)
Line 10069: INFO | jvm 38 | 2018/01/04 10:35:08 | at com.vmware.vshield.firewall.messaging.service.FirewallProtobufConverter.collectIpListForNode_aroundBody0(FirewallProtobufConverter.java:550)
Line 10070: INFO | jvm 38 | 2018/01/04 10:35:08 | at com.vmware.vshield.firewall.messaging.service.FirewallProtobufConverter$AjcClosure1.run(FirewallProtobufConverter.java:1)
Line 10075: INFO | jvm 38 | 2018/01/04 10:35:08 | at com.vmware.vshield.firewall.messaging.service.FirewallProtobufConverter.toContainerList(FirewallProtobufConverter.java:550)
Line 10076: INFO | jvm 38 | 2018/01/04 10:35:08 | at com.vmware.vshield.firewall.messaging.service.FirewallProtobufConverter.toRuleSet(FirewallProtobufConverter.java:635)
Line 10077: INFO | jvm 38 | 2018/01/04 10:35:08 | at com.vmware.vshield.firewall.messaging.service.FirewallMessagingManager.publishRuleSetToCluster(FirewallMessagingManager.java:116)
Line 10078: INFO | jvm 38 | 2018/01/04 10:35:08 | at com.vmware.vshield.firewall.service.impl.ConfigurationPublisher.readAndSendRules_aroundBody0(ConfigurationPublisher.java:135)
Line 10079: INFO | jvm 38 | 2018/01/04 10:35:08 | at com.vmware.vshield.firewall.service.impl.ConfigurationPublisher$AjcClosure1.run(Co...

Cause

This issue occurs when there are multiple virtual machines each configured with multiple IP addresses in the system, and are added to a Security Group through static / dynamic membership. When IP translations of such SGs are triggered, this issue will be hit.

Resolution

This is a known issue affecting VMware NSX for vSphere 6.4.x.

Currently, there is no resolution.

Workaround

To work around this issue:

Change the definition of the SGs containing all such VMs which are configured by multiple ip addresses, by splitting/segregating it into smaller SGs.

The firewall rules, in which the older SGs were consumed, need to be modified to consume the newly created smaller SGs.

To recover from this issue:

Once the system is restarted (automatically, after the issue is hit), delete the SGs containing all such VMs which are configured by multiple ip addresses and then follow the workaround steps.

Note: These virtual machines will not be secured at this time. When this issue is encountered, the security of these virtual machines are lost until a recovery is done.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
针对 VMware NSX-T Data Center 2.2.x 的产品服务 (52462)

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

Take Our Survey

Support Assistant