02-03-2022 11:27 PM
Hi All,
I have been experiencing frequent VS_TMO flaps on a daily basics at multiple locations which usually recovers by itself within 10mins. As such, I am trying to pin point the causes for these flap and mitigate them as much as I can.
Cisco Control Connection Troubleshooting guide have suggested the following:
"What has been observed is that if the packets are rate-limited to below 1Mbps, control connection(s) mayn't be formed and you will see "VM_TMO" errors. Make sure to look into the underlay, for any potential BW / throughput issues"
At the moment I am able to obtain the packet capture remotely via vManage but was not able to identify any obvious issues. So am in the blind how I can identify and resolve this..
I am wondering if anyone have experienced this and could point me at the right direction on ways I could identify potential BW / throughput issues in the underlay that is restricting the packet below 1Mbps.
Simplified network diagram for references:
Solved! Go to Solution.
02-07-2022 06:45 PM
02-07-2022 06:45 PM
04-28-2024 07:24 PM
Old post but relevant, so here is what I found. I am using version 20.9.5 (manager/controller/vbond) and c8000v for edges.
After activate the chassis you will find its serial number:
cEdge_1#request platform software sdwan vedge_cloud activate chassis-number C8K-aaaaaaaa-0CBE-aaa-7074-2aaaa50A token c8blablalalaal. (*****)
cEdge_1#show sdwan control local-properties | in chassis
chassis-num/unique-id C8K-aaaaaaaa-0CBE-aaa-7074-2aaaa50A
Now, on vbond, check if the serial exist:
vbond# show orchestrator valid-ved | begin C8K-4E0560CC-0CBE-7A1E-7074-2CD6D173550A
orchestrator valid-vedges C8K-aaaaaaaa-0CBE-aaa-7074-2aaaa50A
serial-number 1B7B7ADD ---->>>
Now on cEdge, activate the chassis once again, but this time, use SERIAL number as token:
cEdge_1#request platform software sdwan vedge_cloud activate chassis-number C8K-aaaaaaaa-0CBE-aaa-7074-2aaaa50A token 1B7B7ADD
cEdge_1#show sdwan control connection-h
cEdge_1#show sdwan control connections
PEER PEER CONTROLLER
PEER PEER PEER SITE DOMAIN PEER PRIV PEER PUB GROUP
TYPE PROT SYSTEM IP ID ID PRIVATE IP PORT PUBLIC IP PORT ORGANIZATION LOCAL COLOR PROXY STATE UPTIME ID
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
vbond dtls 0.0.0.0 0 0 10.10.0.3 12346 10.10.0.3 12346 blalbalas biz-internet - up 0:00:36:20 0
vmanage dtls 10.200.1.10 700 0 10.10.0.5 12346 10.10.0.5 12346 blablala biz-internet No up 0:00:36:19 0
Hope this help somebody.
-Francisco
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide