Refer to the exhibit. An engineer is troubleshooting an issue where vManage and vSmart nave a problem establishing a connection to vBond. Which action fixes the issue?

When configuring vBond, the command 'vbond <ip-address> local' is required on the vBond device itself to indicate it is the local orchestrator. Without the 'local' keyword, the device treats the address as a remote vBond to connect to rather than declaring itself as the vBond, causing vManage and vSmart to fail when attempting to establish control connections through it.

The transport color is used to categorize WAN interfaces for policy purposes and does not affect the control connection establishment between controllers and vBond.

Removing IPsec encapsulation from vBond would break secure control plane connections rather than fix them, as IPsec is required for DTLS/TLS control connections.

vManage and vSmart already use IPsec encapsulation for their tunnel interfaces by default - adding it would not resolve a vBond identification configuration issue.