Refer to the exhibit. A vBond controller was added to the controller list with the same Enterprise Root CA certificate as vManage. The two controllers can reach each other via IP/PNO and share the…

For vManage to establish a control connection with vBond, it must be explicitly configured with the vBond controller's correct IP address. Even with basic IP reachability, vManage cannot initiate the control plane setup if it does not know where to find vBond.

Synchronizing the WAN Edge list is a subsequent step in the SD-WAN fabric bring-up process, not a prerequisite for the initial control connection between vBond and vManage.

While NTP synchronization is critical for certificate validation and control plane stability, the problem implies a more fundamental communication initiation issue, not a certificate or timing-related error.

A valid system IP is necessary for vBond's identity, but if it is already reachable via IP/PNO, it likely has a system IP; the issue lies with vManage knowing how to use that IP to connect to vBond.