sub-interfaces does not work on vEdge-cloud. However, it does work on ISR4000 Series with sdwan image. It is limitation of vedge-cloud. i.e vpn 1 , int ge0/2.13 -- will use dot1.q encapsulation of vlan 13
Another grea8 video. Please could you explain more as to how vSmart is receiving 4 routes from the peer 10.3.0.1 and sending 6 and receiving 2 routes from the peer 10.4.0.1 and sending 8 (video time at 29:45).
For every TLOC created in VPN0, by default you will advertise all known connected/static routes by default via OMP to vSmart. If you have 4 routes to advertise, and 2 TLOCs to send those routes via, then the vSmart will learn in each route twice, so a total of 8 route advertisements, 4 routes out 2 TLOCs equals 8 total route advertisements.
Hi Rob, just a quick question, if I add connected/static route in VPN1 at vEdge1, the routes shows on vSmart as received but not sending, until I got another site's vEdgeX also got the same VPN1 build, is this because vSmart need to see the same VRF(VPNX) tunnel be established?
10mins in , regarding subinterfaces... I vaguely remember having to put the main interface (of the service VPN sub interfaces) into VPN 0 before it allowed the subinterfaces to actually work. Give it a go. Let me know if that works for you.
The Dark Knight Yeah, I discussed it a little further with Rob on twitter and my experience was with an ISR and not a vEdge, I assumed they would have been the same but it doesn’t sound like it. :)
Thanks Rob.. I have already joined the membership, but I have accessed only MPLS,INET and DC-SW config in the google drive. Where are other devices' initial configs ?? thanks.
Rob, can you provide initial configs of switches and routers? I use your topology, but I prepare initial config by myself after every lab. Please share with me init configs.
Hello Sir, How are you, I like you channel and recomend for every one its a very best channel for SDWAN learning, Sir if you don't mind could you shere this topology with me. thank you very much. CCIE # 47481 HCIE # 9339