MIB Viewer

vmwNsxTNodeAgentsHealthNodeAgentsDown

NOTIFICATION-TYPE
1.3.6.1.4.1.6876.120.1.0.12.0.3
Status
current
Sub-identifiers
0
The agents running inside the Node VM appear to be down. Action required: For ESX: 1. If Vmk50 is missing, refer to this Knowledge Base article https://kb.vmware.com/s/article/67432. 2. If Hyperbus 4094 is missing, restarting nsx-cfgagent or restarting the container host VM may help. 3. If container host VIF is blocked, check the connection to the Controller to make sure all configurations are sent down. 4. If nsx-cfg-agent has stopped, restart nsx-cfgagent. For KVM: 1. If Hyperbus namespace is missing, restarting the nsx-opsagent may help recreate the namespace. 2. If Hyperbus interface is missing inside the hyperbus namespace, restarting the nsx-opsagent may help. 3. If nsx-agent has stopped, restart nsx-agent. For Both ESX and KVM: 1. If the node-agent package is missing, check whether node-agent package has been successfully installed in the container host vm. 2. If the interface for node-agent in container host vm is down, check the eth1 interface status inside the container host vm.