A Cisco SD-WAN edge router successfully establishes DTLS control connections but fails to form OMP adjacencies. Which issue is the most likely cause?

A Cisco SD-WAN edge router successfully establishes DTLS control connections but fails to form OMP adjacencies. Which issue is the most likely cause?

• A. Invalid site ID or system IP mismatch
• B. STP root election failure
• C. CAPWAP tunnel instability
• D. EtherChannel hashing inconsistency

Answer: (A)

OMP adjacencies require the peers to have matching identity information. Even when the DTLS control channel is up, the overlay won’t form neighbors if the device’s site ID or system IP isn’t correct or doesn’t match what the orchestrator expects. The site ID identifies the device’s location in the SD-WAN fabric, and the system IP is the address used by OMP to recognize the neighbor. If these values are invalid or misaligned between peers, OMP will not establish adjacency. STP root election, CAPWAP tunnel behavior, or EtherChannel hashing affect other layers or transport issues, not the specific identity information needed for OMP neighbor formation. So the most likely cause is an invalid site ID or system IP mismatch. Check that the edge’s site ID and system IP align with the vManage/vBond configuration and that there are no duplicates or mismatches across the fabric.

OMP adjacencies require the peers to have matching identity information. Even when the DTLS control channel is up, the overlay won’t form neighbors if the device’s site ID or system IP isn’t correct or doesn’t match what the orchestrator expects. The site ID identifies the device’s location in the SD-WAN fabric, and the system IP is the address used by OMP to recognize the neighbor. If these values are invalid or misaligned between peers, OMP will not establish adjacency.

STP root election, CAPWAP tunnel behavior, or EtherChannel hashing affect other layers or transport issues, not the specific identity information needed for OMP neighbor formation. So the most likely cause is an invalid site ID or system IP mismatch. Check that the edge’s site ID and system IP align with the vManage/vBond configuration and that there are no duplicates or mismatches across the fabric.