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

Products

• VMware NSX for vSphere

Issue/Introduction

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.

Environment

VMware NSX for vSphere 6.2.x
VMware NSX for vSphere 6.4.x
VMware NSX for vSphere 6.3.x

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.