"Minimum Capacity Threshold" alarm is triggered even though the object count is below the Minimum Capacity Threshold

Products

• VMware NSX

Issue/Introduction

• The setup is in the policy mode, and the Minimum Capacity Threshold was changed from System > System Overview > Capacity. In the example below, it was changed from the default 70% to 85% for Edge Clusters.
  
  
  
• The "Minimum Capacity Threshold" alarm is triggered even though the Current Inventory percentage is below the Minimum Capacity Threshold. Even if the alarm is manually resolved, it triggers again immediately.
  
  
  
• When checking the result of the GET /policy/api/v1/infra/capacity/threshold API, the min_threshold_percentage reflects the specified value.
  

  {
      "threshold_type" : "NUMBER_OF_EDGE_CLUSTERS",
      "min_threshold_percentage" : 85.0,
      "max_threshold_percentage" : 100.0
  {

   

• However, when checking the result of the GET /api/v1/capacity/threshold API, the min_threshold_percentage remains at the default value.
  

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

Environment

VMware NSX 4.x

Cause

When the value is changed from System > System Overview > Capacity, it is updated in the Policy view, but the value in the Manager view is not updated, which causes the alarm to trigger.

Resolution

This alarm does not impact the system and can be safely ignored.

Workaround:

If you wish to prevent the alarm from triggering, perform the following steps:

1. Note down the complete output from the GET /api/v1/capacity/threshold API.

2. Modify the target values as shown below:

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

   Change to specified value on GUI:

   {
       "threshold_type" : "NUMBER_OF_EDGE_CLUSTERS",
       "min_threshold_percentage" : 85.0,
       "max_threshold_percentage" : 100.0
   }
   

3. Use PUT /api/v1/capacity/threshold to update the data using the content you noted in Step 1 (with the modifications made in Step 2) as the payload.

4. Wait a few minutes and verify that the alarm has been resolved.

Additional Information

If changed the threshold from Plan & Troubleshoot > Consolidated Capacity, the issue described in KB#413355 will occur.