NSX Minimum capacity above threshold of 70%.

Products

• VMware NSX

Issue/Introduction

NSX alarms indicating the number of objects defined in the system for Tier-1 Gateways with NAT Enabled has reached XXX which is above the minimum capacity threshold of 70.0%.

Even after acknowledging the above alarm, the alarm eventually is generated again. 

On an NSX Manager var/log/syslog, the following log messages report two different values continuously flapping:

2024-07-15T16:25:15.777Z MONITORING [nsx@6876 comp="nsx-manager" entId=#### eventFeatureName="capacity" eventSev="warning" eventState="On" eventType="minimum_capacity_threshold" level="WARNING" subcomp="manager"] The number of objects defined in the system for Tier-1 Logical Routers with NAT Enabled has reached 1395 which is above the minimum capacity threshold of 70.0%.

2024-07-15T16:29:15.776Z MONITORING [nsx@6876 comp="nsx-manager" entId=#### eventFeatureName="capacity" eventSev="warning" eventState="Off" eventType="minimum_capacity_threshold" level="WARNING" subcomp="manager"] The number of objects defined in the system for Tier-1 Logical Routers with NAT Enabled has reached 170 and is at or below the minimum capacity threshold of 70.0%.

Environment

VMware NSX-T Data Center

VMware NSX

Cause

This is caused by Policy and Proton reporting two different values, resulting in the alarm continuously flapping. 

Resolution

The value mismatch between Policy and Proton is resolved in NSX Version 4.2.0.