NSX Alarm "The number of objects defined in the system for vSphere Clusters Prepared for NSX has reached 5 and is at or below the maximum supported count of 5."
search cancel

NSX Alarm "The number of objects defined in the system for vSphere Clusters Prepared for NSX has reached 5 and is at or below the maximum supported count of 5."

book

Article ID: 395928

calendar_today

Updated On:

Products

VMware NSX VMware vSphere ESXi

Issue/Introduction

  • The vSphere cluster count in the NSX Capacity Dashboard UI shows an alarm with the message:
    "The number of objects defined in the system for vSphere Clusters Prepared for NSX has reached 5 and is at or below the maximum supported count of 5."

  • The environment has legitimately expanded beyond the 5-cluster limit supported by the Medium NSX Manager form factor. 

  • Or The user only has 5 clusters configured and User configured 6th vSphere cluster with a host that is in an orphaned state, meaning the host is still a Transport Node (has NSX on it).
    But the cluster does not have any transport node profiles.

  • NSX Manager /var/log/syslog shows similar output to the following.
    Host configuration: Failed to send the HostConfig message. [TN=TransportNode/######-####-####-##########]. Reason: Failed to send HostConfig RPC to MPA node:######-####-####-##########. Error: Unable to reach client ######-####-####-##########, application SwitchingVertical.

Environment

VMware NSX

Cause

This alarm is triggered when the count of vSphere clusters prepared for NSX approaches or exceeds the supported limit for the NSX Manager's current form factor. This typically occurs in two scenarios:

  • Scenario A (Capacity): The environment has legitimately expanded beyond the 5-cluster limit supported by the Medium NSX Manager form factor.
  • Scenario B (Stale/Orphaned Nodes): A cluster was removed or un-prepared, but a host remains in an "orphaned" state (still identified as a Transport Node in the NSX database).

Resolution

Verify Actual Usage

Use the NSX API to identify exactly how many clusters NSX "sees" as prepared:

GET https://{{nsx-manager}}/api/v1/capacity/usage


Look for the usage_type: NUMBER_OF_VCENTER_CLUSTERS.

  • If current_usage_count matches your expected count but exceeds the limit, proceed to Scenario A.
    • Starting with NSX 3.2.0, the Medium form factor is limited to 5 vSphere clusters [1]. If you legitimately require more than 5 clusters:

      1. Check Configuration Maximums: Verify your version's limits at configmax.broadcom.com.
      2. Resize Appliances: Increase the NSX Manager form factor to Large.
      3. Resolve Alarm: Once resized, the alarm should clear automatically. If it persists, manually select Resolve in the Alarms UI.

  • If current_usage_count is higher than your expected count, proceed to Scenario B.
    • If the count is higher than expected, a stale entry is likely present.

      1. Identify Orphaned Hosts: Check /var/log/syslog for errors such as: 
        Host configuration: Failed to send the HostConfig message. [TN=TransportNode/######-####-####-##########]. Reason: Failed to send HostConfig RPC to MPA node:######-####-####-##########. Error: Unable to reach client ######-####-####-##########, application SwitchingVertical.
      2. Cleanup Stale Entries: Use the following API to attempt a cleanup of stale transport node entries:
        POST https://{{nsx-manager}}/api/v1/transport-nodes?action=clean_stale_entries
      3. Manual Removal: If the API does not resolve the alarm, navigate to System > Fabric > Nodes > Host Transport Nodes. Ensure no hosts from deleted clusters are still listed. 

Additional Information