The alarm threshold is set at 80%, so with the Edge node size and allowed load balancer size as per below table, the limit would always be breeched at 100% and generate the alarm:
Edge node size | Load balancer size |
Small | Small |
Medium | Medium |
Large | Large |
XLarge | XLarge |
The Edge nodes can only have a specific size load balancer, this depends on the size of the load balancer and the Edge node.
See configuration maxims page for details on number of load balancers allowed per Edge node and sizes allowed.
Maxims guide for NSX-T 3.1.2 Load BalancerUse the following API to check the load balancer usage per NSX-T Edge node:
GET https://<nsx-t-manager-ip>/api/v1/loadbalancer/usage-per-node/<edge-node-uuid>Sample result:
{
"form_factor": "MEDIUM_VIRTUAL_MACHINE",
"edge_cluster_id": "58d5a50a-512e-4342-9ca6-b73975cb0d9a",
"current_credit_number": 10, ----->>>>>
This is the number of load balancer credits for a medium NSX-T edge node "remaining_credit_number": 0, ----->>>>>>
This indicates remaining load balancer credits for this medium NSX-T edge node "usage_percentage": 100.0, ----->>>>>>
This indicates usage is at 100% "severity": "RED",
"current_pool_members": 0,
"current_virtual_servers": 1,
"current_pools": 0,
"current_small_load_balancer_services": 0,
"current_medium_load_balancer_services": 1,
"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": 2000,
"type": "LbEdgeNodeUsage",
"node_id": "ebfb8008-14ab-11ec-a8d6-0050568de760"
}
Note: These maxims may differ, depending on versions, please check for the maxims allowed per your version.