The number of objects defined in the system for vSphere Clusters Prepared for NSX has reached 7 which is above the minimum capacity threshold of 70.0%. Maximum number of vSphere Clusters Prepared for NSX supported is 5.

Products

• VMware NSX

Issue/Introduction

NSX reporting an Alarm: "The number of objects defined in the system for vSphere Clusters Prepared for NSX has reached 7 which is above the minimum capacity threshold of 70.0%. Maximum number of vSphere Clusters Prepared for NSX supported is 5."

• The environment had 7 clusters; however, it was reduced to 4.
• The API (GET https://{{nsx-manager}}/api/v1/capacity/usage) and Corfu table output(/opt/vmware/bin/corfu_tool_runner.py -n nsx -o showTable -t CapacityUsage) the cluster information is being updated correctly with the current cluster usage count.

Output of the API  /api/v1/capacity/usage:

   {
    "usage_type" : "NUMBER_OF_VCENTER_CLUSTERS",
    "display_name" : "vSphere Clusters Prepared for NSX",
    "current_usage_count" : 4,
    "max_supported_count" : 5,
    "min_threshold_percentage" : 70.0,
    "max_threshold_percentage" : 100.0,
    "current_usage_percentage" : 80.0,
    "severity" : "WARNING"
  },

Output of the Corfu DB CapacityUsage table:

Key:
{
  "stringId": "NUMBER_OF_VCENTER_CLUSTERS"
}

Payload:
{
  "entity": "DASHBOARD_ENTITY_NUMBER_OF_VCENTER_CLUSTERS",
  "count": "4"
}

Environment

VMware NSX

Cause

Based on the API (GET https://{{nsx-manager}}/api/v1/capacity/usage) and the Corfu Table output (/opt/vmware/bin/corfu_tool_runner.py -n nsx -o showTable -t CapacityUsage), the vSphere cluster usage information is updating correctly in the NSX.

The issue may stem from a realization problem or an alarm workflow stuck with stale information, resulting in incorrect vSphere cluster information in the minimum capacity threshold alert description.

Or

This problem may report due to configuration maximums limit, An example, Medium sized NSX manager has the limit 5. To verify refer to the Configuration_maximums.

Resolution

Manually resolve the alert within NSX. After a couple of hours, the alert description should then display the correct cluster information, provided the usage still reaches 70% of the minimum threshold.

To resolve the alert manually within NSX:

1.  In the NSX Manager UI, navigate to the Alarm section.
2.  Select the event Type.
3.  Under Action, select **Resolve**.

If in case configuration maximums has reached as per Configuration_maximums, Perform the resizing of NSX manager as per the required limits.

Additional Information

A similar issue has been reported here: https://knowledge.broadcom.com/external/article?articleNumber=395928