Tier-1 Gateways with NAT Enabled false alarm

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 #% 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/nsxapi.log, the following log messages report two different values continuously flapping:

YYYY/MM/DDTHH:MM:SS  INFO CapacityUsageStreamListener-1-1 CapacityUsageStreamListener 4916 - [nsx@6876 comp="nsx-manager" level="INFO" subcomp="manager"] CapacityUsageStreamListener: updated usage policy_NUMBER_OF_TIER1_WITH_NAT_RULE: CapacityUsage [entity=NUMBER_OF_TIER1_WITH_NAT_RULE, count=######]
YYYY/MM/DDTHH:MM:SS  INFO CapacityUsageStreamListener-1-1 CapacityUsageStreamListener 4916 - [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=###]

• Running the following api call : "GET https://<nsx-mgr>/api/v1/capacity/usage" we will see similar output

usage_type": "NUMBER_OF_TIER1_WITH_NAT_RULE",

            "display_name": "Tier-1 Logical Routers with NAT Enabled",

            "current_usage_count": 69,

            "max_supported_count": 4000,

            "min_threshold_percentage": 70.0,

            "max_threshold_percentage": 100.0,

            "current_usage_percentage": 72.5,

            "severity": "INFO"

       

Environment

VMware NSX-T Data Center 3.x

VMware NSX 4.0.x/4.1.x

Cause

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

Resolution

This issue is resolved in NSX Version 4.2.0 and above.

Workaround:

Reboot the managers