how many "s"s can you find in:
today we are going to talk about some of the troubleshooting steps when we got errors on the cisco viptela sdwan control connections. these are the basics of the types of issues we see normally on the control connections.
bidntvrfd indicates a missing serial number for vbond orchestrators.
crtrejser indicates a missing serial number for vedge routers and vsmart controllers.
serntpres on a vbond orchestrator indicates a serial number mismatch between vsmart controllers.
in the vedge list tab, select the device whose serial number is missing.
use organization-name command on the vedges/cedges as shown below for the vedges.
ndna_vedge(config)# system organization-name "ndna"
this is one of the most seen issue on the control connections. this error code shows that vedge router does not establish dtls connections to controllers in the overlay network.
verify that the default gateway is correctly mapping the ip address to the mac address correctly.
this is one of the rare issues but due to vedge/cedge router experiences transient control connection errors.
as discuss with cisco on this and reverted back that these issues are part of normal operation of the overlay network. they have no impact on production traffic, and they resolve by themselves, with no action required.
this is also a common issue we saw on tlocs which is represented as disabled tloc. a tloc identifies the physical interface where a vedge router connects to the wan transport network or to a nat gateway.
this error is also rare error when we deployed sdwan solution. this error indicates socket error messages.
check if overlay network contains duplicate ip addresses, especially duplicate transport addresses. once you removed duplicate ip, the issue may resolved.
check if packets have been corrupted, resolve the corrupted packets, the issue may resolved.
check if vedge router receives a reset request from the remote device. once the connection setup again, it will resolved.
check if vedge router and the vsmart controller are not both using dtls or tls ports.
check forwarding ports are open, if not we will face this issue.
this may be the simple error which shows that vedge router template not attached in vmanage nms and is when we are using ztp.
if the device is not attached with a template on the vmanage at the time of ztp and you will see no config. check and assign the template on the vmanage for the device which has issue.
this is also a rare case where you found this error message which describes as board id not initialized.
try to reset the board-id. it will take some time but will resolve your issue.
these are also very common errors and the issues is basically when the peer timeout occurs if the vedge router loses reachability to a controller in the overlay network.
increase the hello-interval and hello-tolerance values on the interface to prevent packet loss.
check if the underlay rate-limiting the tls/dtls packets may be the issue.
user
I counted 203 "s"s in that text.
assistant