Heartbeat failure error of non-existing hosts in NSX Manager
Article ID: 336452
Updated On:
Products
VMware NSX Networking
Issue/Introduction
This article provides the work around to fix the heartbeat failed errors of non-existing hosts in the NSX Manager.
Symptoms:
Symptoms:
- NSX manager reports heartbeat failed error of decommissioned or removed hosts in the vCenter Inventory for every 3 mins, you see errors similar to:
EDT ERROR HeartbeatManagerHeartbeatTimer HeartbeatManager$HeartbeatTask:297 - Client has not responded to the heartbeat for longer than the alert threshold. Peer name = 'com.vmware.vshield.userworld', client token = 'host-587', client id = '1ab1e420-3b47-4776-9708-374a8a303593', last heartbeat response = '0', last published heartbeat = '5890'
- In the vsm.log file, you see error similar to:
2016-01-22 09:42:30.185 GMT ERROR HeartbeatManagerHeartbeatTimer HeartbeatManager$HeartbeatTask:297 - Client has not responded to the heartbeat for longer than the alert threshold. Peer name = 'com.vmware.vshield.userworld', client token = 'host-3842', client id = 'fc7549df-a459-4953-a35a-d6d540b455d7', last heartbeat response = '0', last published heartbeat = '11446'
Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.
Environment
VMware NSX for vSphere 6.1.x
Cause
This issue occurs when there is a stale entry in messaging-client table of NSX manager database, due to an incorrect un-installation of NSX VIB on ESXi hosts.
Resolution
There is currently no resolution.
Workaround:
To work around this issue if you do not want to upgrade,
- Remove the stale entry by using the REST API.
Method: DELETE
URL: https://nsxmgr-ip/api/1.0/messaging/clients/client
Where Client is the Client-ID of the messaging-client.
Additional Information
Feedback
Yes
No
Powered by
