Control Channel To Transport Node Down Alarm

Products

• VMware NSX

Issue/Introduction

Title: Alarm for Control channel to transport node down
Event ID: control_channel_to_transport_node_down

Alarm Description

• Purpose: Controller service to Transport node's connection is down for at least three minutes.
• Impact: In this scenario, no new configuration can be pushed down to the Transport node from the Control plane and features like vMotion will not be available.

Environment

VMware NSX

Resolution

Steps to Resolve
For 4.2.0 and higher

Recommended Action: 

Using ODS runbooks

1. Invoke CcpTNConnection runbook. Run following commands on any of the NSX Managers to invoke the runbook.
   /opt/vmware/nsx-netopa/bin/sha-appctl -c set_ods_level --level internal
   Retrieve the transport node name from System->Fabric->Hosts screen and replace the token '<TN_NAME>' in following command with it.
   /opt/vmware/nsx-netopa/bin/sha-appctl -c start_invocation --runbook CcpTNConnection --transport_node_name <TN_NAME>
   Above command will output an INVOCATION_UUID. Note this down and run the next command to get the status of the execution.
   /opt/vmware/nsx-netopa/bin/sha-appctl -c get_invocation_result --invocation <INVOCATION_UUID> -j
   
   Once the runbook execution is complete, follow the instructions from the output. If no issue is detected, proceed to the next step.
   
   
2. Invoke nsx_proxy runbook on the Transport Node. Run following commands to invoke the runbook. Once the runbook execution is complete, follow the instructions from the output.

• • On ESX Node

/usr/lib/vmware/netopa/bin/sha-appctl -c set_ods_level --level internal
/usr/lib/vmware/netopa/bin/sha-appctl -c start_invocation --runbook nsx_proxy
Above command will output an INVOCATION_UUID. Note this down and run the next command to get the status of the execution.
/usr/lib/vmware/netopa/bin/sha-appctl -c get_invocation_result --invocation <INVOCATION_UUID> -j

• • On Edge Node

/opt/vmware/nsx-netopa/bin/sha-appctl -c set_ods_level --level internal
/opt/vmware/nsx-netopa/bin/sha-appctl -c start_invocation --runbook nsx_proxy
Above command will output an INVOCATION_UUID. Note this down and run the next command to get the status of the execution.
/opt/vmware/nsx-netopa/bin/sha-appctl -c get_invocation_result --invocation <INVOCATION_UUID> -j

Once the runbook execution is complete, follow the instructions from the output.

Maintenance window required for remediation? No