Check the status of the transport node.

Procedure

Make the following API call to get the state of the transport node.
GET https://<nsx-mgr>/api/v1/transport-nodes/<transport-node-ID>/state

If the call returns the error RPC timeout, perform the following troubleshooting steps:

  • Run /etc/init.d/nsx-opsAgent status to see if opsAgent is running.

  • Run /etc/init.d/nsx-mpa status to see if nsx-mpa is running.

  • To see if nsx-mpa is connected to the NSX Manager, check the nsx-mpa heartbeat logs.

  • To see if opsAgent is connected to the NSX Manager, check the nsx-opsAgent log. You will see the following message if opsAgent is connected to the NSX Manager.

    Connected to mpa, cookie: ...
  • To see if opsAgent is stuck processing HostConfigMsg, check the nsx-opsAgent log. If so, you will see an RMQ request message but the reply is not sent or sent after a long delay.

  • Check to see if opsAgent crashed while executing HostConfigMsg.

  • To see if the RMQ messages are taking a long time to be delivered to the host, compare the timestamps of log messages on the NSX Manager and the host.

If the call returns the error partial_success, there are many possible causes. Start by looking at the nsx-opsAgent logs. On the ESXi host, check hostd.log and vmkernel.log. On KVM, syslog holds all the logs.