VPN Route leaking - Cisco SDWAN

[@SivakumarNetLabs]

kzbin.info

[@RishiRap]

vpn-id's are Locally Significant. Having same vpn-id at 2 different sites does not mean they belong to the same customer/vpn and are reachable from each other. You are missing some important clues here, imo. what logical topology are you using by default? Full-mesh is the default and therefore all sites can reach each other without any additional policy configuration. Perhaps route-leaking only applies to different vpn's on the same vEdge as mentioned by other users mentioned in comment section. Any ideas?

[@laithobeidat9462]

Thanks Siva I have one question please Ping from vpn 10 to vpn 20 in same vedge will not work Do you have any idea why ?

[@nidhikumari75]

Great explanation!! I have one question, i have tried the same thing and i am able to reach from vEdge-1 of VPN 10 to vEdge-2 VPN 20 but i am not able to reach VPN 10 subnet from VPN 20 on vEdge-2. Any idea or comment what i am missing here ?

[@SivakumarNetLabs]

@ Nidhi Kumari make sure all steps followed as i mentioned in the video, check whether the sequence rule allowing vpn 10 to 20 and vpn 20 to 10 rule created and added properly. Check the routing table whether the routes learned from proper vpn

[@vishwashsharma645]

Can't we perform this lab via out direction instead of in directions?? What's the benefits of using in indirection here ??