/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.
VMware NSX
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:
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.
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:
If the count is higher than expected, a stale entry is likely present.
/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.
POST https://{{nsx-manager}}/api/v1/transport-nodes?action=clean_stale_entries