For Sponsored Posts & Articles, please email us on 📧 networks.baseline@gmail.com

Cisco Viptela SDWAN : Troubleshooting commands for Control Plane, OMP and BFD

Today I am going to talk about the troubleshooting commands for Cisco Viptela SDWAN. In order to troubleshoot Bidirectional Forwarding Detection(BFD) and Data Plane Connections Issues below are the basic commands used.

1. Control Plane troubleshooting
2. Overlay Management Protocol (OMP) troubleshooting
3. Bidirectional Forwarding Detection(BFD) troubleshooting

Control Plane troubleshooting 
Control Plane troubleshooting will help you to check about the WAN TLOC information and status. below are the various commands 

NDNA_vEdge1# show control local-properties wan-interface-list 


NDNA_vEdge1# show control connections



if the interface that does not form data tunnels tries to connect, you can solve it by achieving successful bring-up of the control connections via that color.

Make sure you check the setting of max-control-connections as it should not be 0 in the selected interface under the tunnel interface section.


Overlay Management Protocol (OMP) troubleshooting
OMP TLOCs cannot be sent because the interface tries to form control connections via that color and is not able to reach the controllers. So, check if the color that the data tunnels do not work or come up sends the TLOC for that particular color to the vSmarts.

NDNA_vEdge1# show omp tlocs advertised 


NDNA_vEdge1# show omp tlocs received  



Bidirectional Forwarding Detection

NDNA_vEdge1# show bfd sessions 


  • System IP: Peers system-ip
  • Source and Remote TLOC color: This is useful to know what TLOC you are expecting to receive and send.
  • Source IP: It is the private source IP. If you are behind a NAT, this information won't be displayed here (it can be seen with the use of show control local-properties <wan-interface-list> that is explained at the start of the document).
  • DST Public IP: It is the destination that the NDNA_vEdge is using to form the Data Plane tunnel, regardless if it is behind NAT or not. (Example: NDNA_vEdges directly attached to the Internet, or Multi-Protocol Label Switching (MPLS) links)
  • DST Public Port: Public NAT-ed port that the NDNA_vEdge uses in order to form the Data Plane tunnel to the remote NDNA_vEdge.
  • Transitions: Number of times the BFD session has changed its status, from NA to UP and vice versa.

NDNA_vEdge1# show tunnel statistics 


NDNA_vEdge1# show tunnel statistics bfd



No comments

Note: Only a member of this blog may post a comment.