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

tmpfs partition on DLR’s and Edges in NSX 6.3.6 and NSX 6.4.1, configured with HA can get full, preventing any configuration changes (57003)

Last Updated: 12/12/2019Categories: TroubleshootingTotal Views: 7564Language:
English

1 like this article

Subscribe to get an email
newsletter with new updates

1 people found this helpful Please provide article feedback:

Details

Symptoms:
Any addition / deletion / modification of configuration on the NSX Edge / DLR will fail.

NSX Manager logs begin reporting the following messages for the edge/DLR:

2018-07-16 08:03:34.361 AEST INFO messagingTaskExecutor-7 VseRpcResponseHandler:111 - Received empty response for request f3244e8c-918c-49d0-8df9-40b95aca4c88 from appliance: 501d5055-8dbd-2b7a-888b-d4845c55249c, vm vm-2879
2018-07-16 08:03:34.362 AEST ERROR http-nio-127.0.0.1-7441-exec-7976 BaseRestController:452 - REST API failed : 'null'
java.lang.NullPointerException

/run/vmware/vshield/cmdOut/ha.cid.debug file grows and fills up the temporary file system of DLRs and Edge VMs.

The issue affects only the Edges and DLRs configured in HA.
The ha.cid.debug file creation is triggered only after an HA event (like HA failover or split-brain), and it can take approximately four weeks for the ha.cid.debug file to fill up edge tmpfs on a DLR or compact edge. Thus, it could be weeks after the original HA event that the customer notices this issue.

No datapath impact is expected when the file system is full, only new configuration changes would fail for the affected edges.

Solution

This issue is resolved in:

VMware NSX for vSphere 6.3.7, available at VMware Downloads.
VMware NSX for vSphere 6.4.2, available at VMware Downloads.

Workaround: The Active Edge VM would need to be rebooted to get them back into a working state.

Related Information

The file ha.cid.debug does not exist until an HA event happens, i.e. a failover or split-brain recovery.
If you deploy a fresh Edge with HA enabled, the file will not exist until you trigger a failover.
/run/vmware/vshield/cmdOut/ha.cid.Out file filled with following logs on Edge appliances.

This rsync lacks old-style --compress due to its external zlib.  Try -zz. Continuing without compression.

This issue is seen in NSXv 6.3.6, 6.4.x.

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
•
VMware Tools の自動アップグレードが次のエラーで失敗する： vix エラー コード = 21009 (vix error code = 21009) (2129927)

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:

Take Our Survey

Support Assistant