“Control Channel to Antrea Cluster Down” alarm received after Antrea-to-NSX Interworking integration

Products

• VMware vSphere with Tanzu

Issue/Introduction

After a success integration of Antrea to NSX interworking, the following symptoms can be seen:

• Control Channel to Antrea Cluster Down alarm in NSX UI
• DFW status shows Antrea Container Cluster Unkown

The following log entries can be seen in ccp-adapter.log
 StreamConnection[538 Closing to unix:///var/run/vmware/nestdb/nestdb-server.sock sid:538] Closing (reason: by peer)
 StreamConnection[538 Closed to unix:///var/run/vmware/nestdb/nestdb-server.sock sid:-1] Closed (reason: by peer, error: 2-End of file)
 RpcConnection[538 Connected to unix:///var/run/vmware/nestdb/nestdb-server.sock 0] Closing (network error)

Environment

VMware Container Networking with Antrea v1.7
Antrea interworking version below 0.11.2

Cause

The issue is caused by a known issue within interworking pod where connection to NSX CCP is not retried.

Resolution

Fixed in Interworking version above v0.11.2.

Either one of the the following options should work:

• Upgrade Tanzu Kubernetes Release to 1.27.x with embedded interworking pod
• Manually install interworking version above v0.11.2