Purpose: Alarm is raised when messaging channel between Manager Node and Transport node is down for more than 15 minutes.
Impact: Possible functionality impacts include:
Config push from Manager node to Transport node will fail.
Monitoring status, stats and alarms would not be received by Manager node from the impacted Transport node.
Environment
VMware NSX
Resolution
Steps to Resolve
For 3.0.2 and higher
Resolution:
Ensure there is network connectivity between the impacted Manager node and Transport node and no firewalls are blocking traffic between the nodes.
On Windows Transport nodes, ensure the nsx-proxy service is running on the Transport node by invoking the command `C:\NSX\nsx-proxy\nsx-proxy.ps1 status` in the Windows PowerShell. If it is not running, restart it by invoking the command `C:\NSX\nsx-proxy\nsx-proxy.ps1 restart`.
On all other Transport nodes, ensure the nsx-proxy service is running on the Transport node by invoking the command `/etc/init.d/nsx-proxy status`. If it is not running, restart it by invoking the command `/etc/init.d/nsx-proxy restart`.
Maintenance window required for remediation? No
Additional Information
If incase restarting nsx-proxy doesn't helps to fix the issue, We request you to open a support request with Broadcom support to get assistance on the same.