"The number of objects defined in the system for Compute Managers has reached # which is above the minimum capacity threshold of 70.0%. Maximum number of Compute Managers supported is #." on NSX 4.2.0 and later versions.

Products

• VMware NSX

Issue/Introduction

• You have recently deployed or recently upgraded to an NSX 4.2.x release.
• After upgrading or adding a new Compute Manager (vCenter), you observed a recent alarm: "Minimum Capacity Threshold" with the following description:
  The number of objects defined in the system for Compute Managers has reached 2 which is above the minimum capacity threshold of 70.0%. Maximum number of Compute Managers supported is 2.


  
  
• Following the Recommended Action: "Navigate to the capacity page under the NSX overview UI of respective feature ( i.e. Networking, Security, Inventory and System) and review current usage versus threshold limits. If the current usage is expected, consider increasing the minimum threshold values. If the current usage is unexpected, review the network policies configured to decrease usage at or below the minimum threshold.", and increasing the "Minimum Capacity Threshold" to 100% from NSX UI -> Plan & Troubleshoot -> Consolidated Capacity did not resolve the issue.
  
• Every time you manually "Resolve" the alarm, after a few minutes, the alarm trigger again.

Environment

VMware NSX 4.2 and later.

Cause

This alarm is expected to trigger in NSX 4.2 and later releases.
According to VMware Configuration Maximum, an NSX Manager Medium appliance supports a maximum of two Compute Managers. Therefore, adding a second Compute Manager will result in 100% utilization of its supported capacity. Since the Minimum Capacity Threshold ("min_threshold_percentage") is set at 70%, this scenario is expected to trigger the alarm.

When editing the "Consolidated Capacity" under "Plan & Troubleshooting" this action is performed exclusively from the Manager view, and the Policy view does not have the functionality to change it from the UI. Consequently, even after making this change in the NSX UI (Manager view), the alarm will still Open.

Resolution

This is an expected behavior, and you can ignore this alarm.

Workaround:

If you want to increase the min_threshold_percentage for the NSX Policy/Manager to resolve this alarm, you can follow these steps.

1. From the NSX Manager UI, under "Plan & Troubleshooting," change the Consolidated Capacity for the Compute Managers "Minimum Capacity Threshold" from 70% to 100%.
   Note: This change is only at the Manager level and requires the additional steps described below (PUT API).
2. Using the GET /policy/api/v1/infra/capacity/threshold API, take note of all the outputs.
3. Change the value from:
   

    {
       "threshold_type" : "NUMBER_OF_COMPUTE_MANAGER",
       "min_threshold_percentage" : 70.0,
       "max_threshold_percentage" : 100.0
     }

   
   to:
   

    {
     "threshold_type" : "NUMBER_OF_COMPUTE_MANAGER",
     "min_threshold_percentage" : 100.0,
     "max_threshold_percentage" : 100.0
   }

4. Using the PUT /policy/api/v1/infra/capacity/threshold API, copy all the content from the GET request (step 3), and only modify the part described above.
   Note: You need to copy and paste all the content, including for the other components, but only change the "min_threshold_percentage" for the NUMBER_OF_COMPUTE_MANAGER.
5. Wait a few minutes, and the alarm should be Resolved by the NSX.

Additional Information

VMware Configuration Maximum
NSX UI shows Compute Manager Capacity Threshold Alarm
False positive 'Compute Manager Minimum Capacity Threshold' Alarm for 'Medium' form-factor NSX-T Managers