Summary: New node can not be detected after loudmouth restarted on VxRail Manager


Article Content

Issue


When doing the node replacement or single node addition, if the loudmouth service is restarted, VxRail Manager will not be able to detect the new node.
Cause
Marvin service will register itself in Loudmouth when it starts, but once Loudmouth is restarted, the record of Marvin service will disappear in Loudmouth. That makes new host can't add itself to the VxRail Manager.
Resolution
Workaround
Restart the Marvin service again with the following command:
service vmware-marvin restart