Tier-1 Gateway creation fails with "Insufficient resources to do auto allocation in edge cluster <EdgeCluster-UUID> <EdgeCluster-Name> of pool type LB_ALLOCATION_POOL"
search cancel

Tier-1 Gateway creation fails with "Insufficient resources to do auto allocation in edge cluster <EdgeCluster-UUID> <EdgeCluster-Name> of pool type LB_ALLOCATION_POOL"

book

Article ID: 425200

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

  • Attempting to create a new Tier-1 gateway results in a failed state.


  • Additionally, selecting the Errors tab on the screen above displays the following message.
    YYYY/MM/DD HH:MM:SS : [error_code=10087, module_name=ROUTING, error_message='[Routing] Insufficient resources to do auto allocation in edge cluster <EdgeCluster-UUID> <EdgeCluster-Name> of pool type LB_ALLOCATION_POOL because of below reason(s).', error_code=10149, module_name=ROUTING, error_message='[Routing] Node(s) [EdgeTransportNode/<EdgeTN-UUID>, ...(repeated for each node in the cluster)] don't have enough capacity to allocate.']
[Routing] Insufficient resources to do auto allocation in edge cluster <EdgeCluster-UUID> of pool type LB_ALLOCATION_POOL because of below reason(s).
[Routing] Node(s) [EdgeTransportNode/<EdgeTN-UUID>, ...(repeated for each node in the cluster)] don't have enough capacity to allocate.


  • The following message is recorded in the /var/log/proton/nsxapi.log file on the NSX Manager.
    YYYY-MM-DDTHH:MM:SS.NNNZ  WARN providerTaskExecutor-1-131 ECResourceAllocationServiceImpl ##### FABRIC [nsx@#### comp="nsx-manager" level="WARNING" subcomp="manager"] Node(s) [EdgeTransportNode/<EdgeTN-UUID>, ...(repeated for each node in the cluster)]  don't have enough capacity to allocate
YYYY-MM-DDTHH:MM:SS.NNNZ  INFO providerTaskExecutor-1-131 AlarmServiceImpl ##### POLICY [nsx@#### comp="nsx-manager" level="INFO" subcomp="manager"] Message returned [error_code=10087, module_name=ROUTING, error_message='[Routing] Insufficient resources to do auto allocation in edge cluster <EdgeCluster-UUID> path=[/infra/sites/default/enforcement-points/default/edge-clusters/<EdgeCluster-UUID>] of pool type LB_ALLOCATION_POOL because of below reason(s).', error_code=10149, module_name=ROUTING, error_message='[Routing] Node(s) [EdgeTransportNode/<EdgeTN-UUID>, ...(repeated for each node in the cluster)] don't have enough capacity to allocate.']
YYYY-MM-DDTHH:MM:SS.NNNZ  INFO providerTaskExecutor-1-131 AlarmServiceImpl ##### POLICY [nsx@#### comp="nsx-manager" level="INFO" subcomp="manager"] Message returned Found errors in the request. Please refer to the related errors for details.
YYYY-MM-DDTHH:MM:SS.NNNZ ERROR providerTaskExecutor-1-131 PolicyProviderUtil ##### POLICY [nsx@#### comp="nsx-manager" errorCode="PM0" level="ERROR" subcomp="manager"] Created alarm Alarm [policyPath=/infra/realized-state/enforcement-points/default/tier-1-logical-routers/<Tier1-Name>/alarms/<Tier1-UUID>, message=[error_code=10087, module_name=ROUTING, error_message='[Routing] Insufficient resources to do auto allocation in edge cluster <EdgeCluster-UUID> path=[/infra/sites/default/enforcement-points/default/edge-clusters/<EdgeCluster-UUID>] of pool type LB_ALLOCATION_POOL because of below reason(s).', error_code=10149, module_name=ROUTING, error_message='[Routing] Node(s) [EdgeTransportNode/<EdgeTN-UUID>, ...(repeated for each node in the cluster)] don't have enough capacity to allocate.'],errorId=PROVIDER_INVOCATION_FAILURE, path=null, apiError=error_code=10000, module_name=ROUTING, error_message='Found errors in the request. Please refer to the related errors for details.'
  related_errors=[
  error_code=10087, module_name=ROUTING, error_message='[Routing] Insufficient resources to do auto allocation in edge cluster <EdgeCluster-UUID> of pool type LB_ALLOCATION_POOL because of below reason(s).'
  error_code=10149, module_name=ROUTING, error_message='[Routing] Node(s) [EdgeTransportNode/<EdgeTN-UUID>, ...(repeated for each node in the cluster)] don't have enough capacity to allocate.'
  ], sourceSiteId=null].

Environment

VMware NSX

Cause

  • This issue occurs when the Edge Nodes in the selected cluster do not have available Load Balancer Service slots matching the specific Edge Cluster Allocation Size configured on the Tier-1 Gateway.

  • When creating a Tier-1 Gateway for Load Balancing, an allocation size (LB Small , LB Medium etc) is defined. 
    If the Edge assigned to the logical router at this time lacks sufficient resources corresponding to the requested LB size, the realization will fail.

Resolution

To resolve this issue, identify whether there are edge nodes with available capacity or add resources to the environment.

Step 1: Verify Edge Node Usage
You can verify the current Load Balancer usage and capacity of specific Edge Nodes using the NSX API.

GET /api/v1/loadbalancer/usage-per-node/<EdgeTN-uuid>

Example Response (Resource Exhausted):

{
  "form_factor" : "XLARGE_VIRTUAL_MACHINE",
  "edge_cluster_id" : "<EdgeCluster-UUID>",
  "current_credit_number" : 80, 
  "remaining_credit_number" : 0,
  "usage_percentage" : 100.0, 
  "severity" : "RED", <<<<<<<<<<<
  "current_pool_members" : 77,
  "current_virtual_servers" : 44,
  "current_pools" : 38,
  "current_small_load_balancer_services" : 0,
  "current_medium_load_balancer_services" : 8,
  "current_large_load_balancer_services" : 0,
  "current_xlarge_load_balancer_services" : 0,
  "remaining_small_load_balancer_services" : 0,  <<<<<<<<<<<
  "remaining_medium_load_balancer_services" : 0,  <<<<<<<<<<<
  "remaining_large_load_balancer_services" : 0,  <<<<<<<<<<<
  "remaining_xlarge_load_balancer_services" : 0,  <<<<<<<<<<<
  "remaining_pool_members" : 9923,
  "type" : "LbEdgeNodeUsage",
  "node_id" : "<EdgeTN-UUID>"
}

Example Response (Available Capacity):

{
  "form_factor" : "XLARGE_VIRTUAL_MACHINE",
  "edge_cluster_id" : "<EdgeCluster-UUID>",
  "current_credit_number" : 40,
  "remaining_credit_number" : 40,
  "usage_percentage" : 50.0,  
  "severity" : "GREEN", <<<<<<<<<<<
  "current_pool_members" : 6,
  "current_virtual_servers" : 9,
  "current_pools" : 3,
  "current_small_load_balancer_services" : 0,
  "current_medium_load_balancer_services" : 4,
  "current_large_load_balancer_services" : 0,
  "current_xlarge_load_balancer_services" : 0,
  "remaining_small_load_balancer_services" : 40,  <<<<<<<<<<<
  "remaining_medium_load_balancer_services" : 4,  <<<<<<<<<<<
  "remaining_large_load_balancer_services" : 1,  <<<<<<<<<<<
  "remaining_xlarge_load_balancer_services" : 0,
  "remaining_pool_members" : 9994,
  "type" : "LbEdgeNodeUsage",
  "node_id" : "<EdgeTN-UUID>"
}



Step 2: Mitigation Strategies
Manual Allocation (Immediate Workaround) If the API check reveals that specific Edge Nodes still have capacity (Severity: GREEN) while others are full, the automatic placement algorithm may fail.

  1. Edit the failed Tier-1 Gateway.
  2. Disable Edge Cluster Auto Allocation.
  3. Manually select the Edge Node identified as having available capacity.
  4. Save the configuration.

If all nodes have reached their capacity limits, consider adding additional edge nodes to existing edge clusters or creating and assigning larger-sized Edge nodes.
Note: An Edge Cluster can have a maximum of 10 Edge Nodes.

Additional resource: VMware Configuration Maximums

Powered by Wolken Software