briansmith41 Posted June 27, 2022 Share Posted June 27, 2022 How is everyone creating the control policy/topologies for this route leaking? The way I see it, you could: #1 - create two topologies, one for branches to leak 198/200 into VPN 999, and apply it directly to the branch site-ids....and another topology for the DC to leak VPN 999 into 198/200, applied directly to the DC site-id OR #2 - create one topology, and make your entries more specific to reference a site-id for branches and a site-id for DC, relevant to what the task asks for...and then attach both branch and DC to the policy Both seem to work fine...just trying to figure out if one of them is the "wrong" way to do it based on the task. 3 Link to comment Share on other sites More sharing options...
Dunkle Posted August 4, 2022 Share Posted August 4, 2022 Don’t forget you also need to filter a prefix at the branch level. I would go with Option one because you need to filter based on the direction of the routes from the vSmarts perspective so you couldn’t filter one without filtering the other with a single policy. 2 Link to comment Share on other sites More sharing options...
morrmar Posted August 20, 2022 Share Posted August 20, 2022 Hi may i know how can i practice this as well? Link to comment Share on other sites More sharing options...
visasman Posted January 24, 2023 Share Posted January 24, 2023 Has anyone had problems getting b1/b2 to communicate with DMVPN sites? In VPN999 template, under OMP, I redistributed OSPF External routes. However, it does not reach vEdge40/51/52. I see that vEdge21/22 has O E2 10.6.0.0/15 installed, but I don't know why vSmart doesn't advertise to b1/b2. Would appreciate your comments. 1 Link to comment Share on other sites More sharing options...
Siscco Posted January 25, 2023 Share Posted January 25, 2023 18 hours ago, visasman said: Has anyone had problems getting b1/b2 to communicate with DMVPN sites? In VPN999 template, under OMP, I redistributed OSPF External routes. However, it does not reach vEdge40/51/52. I see that vEdge21/22 has O E2 10.6.0.0/15 installed, but I don't know why vSmart doesn't advertise to b1/b2. Would appreciate your comments. check for prefix suppression , try clear ospf in DC. Check if you're fully converged in VPNV4 - SP1 1 Link to comment Share on other sites More sharing options...
visasman Posted January 25, 2023 Share Posted January 25, 2023 12 hours ago, Siscco said: check for prefix suppression , try clear ospf in DC. Check if you're fully converged in VPNV4 - SP1 I will try to clear the OSPF process to all OSPF speakers running in DC Can you elaborate little more about checking VPNv4 convergence in SP#1? Link to comment Share on other sites More sharing options...
visasman Posted January 26, 2023 Share Posted January 26, 2023 19 hours ago, visasman said: I will try to clear the OSPF process to all OSPF speakers running in DC Can you elaborate little more about checking VPNv4 convergence in SP#1? Clearing the OSPF process in all DC OSPF devices solved the problem. 👍 1 Link to comment Share on other sites More sharing options...
mindset Posted January 31, 2023 Share Posted January 31, 2023 thx Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now