In VMware NSX environments, multiple "IP Pool Usage Very High" alarms appear in the NSX Manager dashboard. A distinguishing symptom is that these alarms lack an associated Entity Name (Object or Project) and persist even when the actual IP pool utilization is well below the threshold. This issue is typically encountered in environments utilizing VPC Subnet IP pools with high churn.
VMware NSX 9.1.x
During periods of high IP address churn, if specific ip-allocations paths are deleted, the alarm framework fails to reconcile or clear the existing "IP Pool Usage Very High" alarm state. This results in stale, orphaned alarms that lack entity metadata because the original object no longer exists to populate the alarm details.
This is a known issue affecting VMware NSX 9.1.x. There is currently no resolution.
To workaround this issue, acknowledge the offending alarms in the NSX UI.