If the CCP config session is not up, check the status of MPA and netcpa.

Procedure

  1. Make the following API call to see if MPA is connected to the NSX Manager.
    GET https://<nsx-mgr>/api/v1/logical-ports/<logical-port-uuid>
  2. On the hypervisor, run the command /bin/nsxcli to start NSX CLI.
  3. Run the following command to get the node-uuid.
    host1> get node-uuid
    0c123dd4-8199-11e5-95e2-73cc1cd9b614
  4. Run the following command to see if the NSX Manager pushed the CCP information to the host.
    cat /etc/vmware/nsx/config-by-vsm.xml
  5. If config-by-vsm.xml has CCP information, check if a transport node is configured on the hypervisor.

    The NSX Manager sends the host certificate for the hypervisor in the transport node creation step. The CCP must have the host certificate before it accepts connections from the host.

  6. Check the validity of the host certificate in /etc/vmware/nsx/host-cert.pem.

    The certificate must be the same as the one that the NSX Manager has for the host.

  7. Run the following command to check if the status of netcpa.

    On ESXi:

    /etc/init.d/netcpad status

    On KVM:

    /etc/init.d/nsx-agent status
  8. Start or restart netcpa.

    On ESXi, start netcpa if it is not running, or restart it if it is running.

    /etc/init.d/netcpad start
    /etc/init.d/netcpad restart

    On KVM, start netcpa if it is not running, or restart it if it is running.

    /etc/init.d/nsx-agent start
    /etc/init.d/nsx-agent restart
  9. If the config session is still not up, collect the technical support bundles and contact VMware support.