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

Edge deployment fails with the error: "greater than MAX fds Supported 1000" (55748)

Last Updated: 2/27/2024Categories: TroubleshootingTotal Views: 6495Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

Edge deployment fails where timeout is seen while waiting for the Edge initialization and NSX Manager log reports.

2018-05-09 13:27:25.990 IDT ERROR TaskFrameworkExecutor-4 AbstractEdgeApplianceManager:203 - Timed out waiting for Edge vm {}. Vm took too long to boot and respond
com.vmware.vshield.edge.exception.VshieldEdgeException: vShield Edge:10078:Timeout while waiting for Edge initialization. It may happen if edge vm failed to boot because of resource constraint or failed to communicate with edge vm. Please refer log for details.

In the ESXi host logs, vsfwd.log file, you see entries similar to:

vsfwd.0.gz:2018-05-11T09:51:17Z vsfwd: [ERROR] Closing Client FD : 1017 as greater than MAX fds Supported 1000
vsfwd.2.gz:2018-05-11T09:29:42Z vsfwd: [ERROR] Queuing as Unable to Write 197 Bytes for VMCI Client For Client Type VMCI error ret -1 errno 107

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

Cause

This issue occurs because there is a host limit encountered when the number of Edges per host cross the 250 count.

Resolution

This is a known limitation on VMware NSX for vSphere 6.2.x, 6.3.x and 6.4.x.

Clearer error messaging was added to the UI VMware NSX for vSphere 6.4.2.

Workaround

To work around this issue, either do one of the following:

Reduce the number of Edges on the failing host.

Try deploying the Edge on a different host with less than 250 Edges.

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

Related Versions:

VMware NSX for vSphere 6.4.x

VMware NSX for vSphere 6.3.x

VMware NSX for vSphere 6.2.x

Take Our Survey

Support Assistant