Critical capacity alarm for "Tier-1 Logical Routers with NAT Enabled" in VMware NSX Manager
search cancel

Critical capacity alarm for "Tier-1 Logical Routers with NAT Enabled" in VMware NSX Manager

book

Article ID: 423821

calendar_today

Updated On:

Products

VMware NSX VMware vSphere ESXi

Issue/Introduction

  • You observe a critical capacity alarm on the NSX Manager regarding the "Tier-1 Logical Routers with NAT Enabled" limit.
  • The system reports a usage significantly higher than the actual limit while the actual usage is validated to be within normal limits (e.g., ~200 objects).
  • This issue is a management plane reporting error and has no impact on production traffic or configuration limits.
  • You see log entries in /var/log/proton/nsxapi.log indicating the object count is oscillating or "flapping" between the correct and incorrect values:
    grep "CapacityUsageStreamListener" /var/log/proton/nsxapi.log | grep "NUMBER_OF_TIER1_WITH_NAT_RULE"
    2026-06-15T08:19:25.575Z  INFO CapacityUsageStreamListener-1-1 CapacityUsageStreamListener 86278 - [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] CapacityUsageStreamListener: deleted usage NUMBER_OF_TIER1_WITH_NAT_RULE: CapacityUsage [entity=NUMBER_OF_TIER1_WITH_NAT_RULE, count=0]
    2026-06-15T08:19:25.876Z  INFO CapacityUsageStreamListener-1-1 CapacityUsageStreamListener 86278 - [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] CapacityUsageStreamListener: updated usage NUMBER_OF_TIER1_WITH_NAT_RULE: CapacityUsage [entity=NUMBER_OF_TIER1_WITH_NAT_RULE, count=1221]
    2026-06-15T08:19:26.179Z  INFO CapacityUsageStreamListener-1-1 CapacityUsageStreamListener 86278 - [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] CapacityUsageStreamListener: updated usage NUMBER_OF_TIER1_WITH_NAT_RULE: CapacityUsage [entity=NUMBER_OF_TIER1_WITH_NAT_RULE, count=9]
     
  • In parallel, the value of "Current Usage Percentage for NUMBER_OF_TIER1_WITH_NAT_RULE" in the same log files remains static:
    2026-06-15T08:18:06.676Z  INFO pool-719-thread-1 L3CapacityProvider 86278 ROUTING [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] Current Usage Percentage for NUMBER_OF_TIER1_WITH_NAT_RULE : 2.25
     
  • Run the following script against the NSX Manager's /var/log/proton/nsxapi.log file to confirm the fluctuation. Only one value will correspond to the actual limit.

    Limits depend on the size of the Manager, please refer to VMware Configuration Maximums for details.
    awk '/Current Usage Percentage for NUMBER_OF_TIER1_WITH_NAT_RULE/ { p[$NF]=1 } /updated usage NUMBER_OF_TIER1_WITH_NAT_RULE:/ { c=$0; gsub(/.*count=|].*/, "", c); cnt[c]=1 } END { for (pct in p) for (count in cnt) if (pct > 0) printf "Current Usage Percentage: %s | Updated CapacityUsage Count: %-5s | Maximum capacity for number of Tier 1s with NAT rule = %.0f\n", pct, count, (100/pct)*count }' var/log/proton/nsxapi.log
     
    Sample output:
    Current Usage Percentage: 2.25 | Updated CapacityUsage Count: 9     | Maximum capacity for number of Tier 1s with NAT rule = 400
    Current Usage Percentage: 2.25 | Updated CapacityUsage Count: 1220  | Maximum capacity for number of Tier 1s with NAT rule = 54222
    Current Usage Percentage: 2.25 | Updated CapacityUsage Count: 1221  | Maximum capacity for number of Tier 1s with NAT rule = 54267
    In the sample above, the NSX Manager is in size "Medium", with a capacity of 400 Tier1 gateways with a NAT rule, hence the first line indicates the correct usage capacity.

Environment

VMware NSX

Resolution

To resolve this issue, clear the memory state on the affected NSX Manager node.

  1. SSH in to the CLI of the affected NSX Manager (the node reporting the false positive).
  2. Restart the manager service with the following command:
    restart service manager