"Currently connected network interface" "Network Adapter 1" uses network 'DVSwitch[50 29 dd 1a c9 58 df 20-a6 c1 XX XX XX XX XX XX} NSX Port Group {dvportgroup-2003}(lcp.ccpSession down)'. Which is not accessible[root@esxi-host:~] net-dvs -l | grep -i down com.vmware.common.opaqueDvs.status.component.lcp.ccpSession = down , propType = RUNTIME2025-03-24T09:12:00.287Z Wa(180) nsx-proxy[2827682]: NSX 2827682 - [nsx@6876 comp="nsx-esx" subcomp="nsx-proxy" s2comp="nsx-rpc" tid="2827699" level="WARNING"] RpcConnection[3599 Connecting to ssl://#.#.#.19:1235 0] Couldn't connect to ssl://#.#.#.19:1235 (error: 110-Connection timed out) The above log indicates Host Transport Node is not able to connect to Control Plane (CCP).
[root@esxi-host:~] nsxcli -c get controllers
Controller IP Port SSL Status Is Physical Master Session State Controller FQDN Failure Reason
#.#.#.18 1235 enabled not used false null NA NA #.#.#.17 1235 enabled not used false null NA NA #.#.#.19 1235 enabled disconnected true down NA CONNECTION_TIMED_OUT
VMware NSX
NSX Controller is needed during vMotion to provide the destination host with overlay network and new switchport for the VM.
NSX manager uses port 1235 for communication between the Central Control Plane (CCP) and transport node.
Please ensure Controller connectivity to the Host Transport Node is up.
Check the connectivity between Host Transport node and Control Plane (CCP) using the below command.[root@esxi-host:~] nsxcli -c get controllers
During the time when Controller connectivity to the Host Transport Node is down, no new configuration can be pushed down to the Transport node from the Control plane and features like vMotion will not be available.