I am trying to accomplish some "Failover" routing via summary routes.
See attached "BASIC" picture.
Ethernet WAN is going to be OSPF Area 0
Datacenter 1 will be Area 1
Datacenter 2 will be Area 2
DC-1, RTR 1, has his WAN interface in Area 0
DC-2 RTR has his WAN interface in Area 0 as well as the point to point 250mbps link in Area 0
(a bunch of other irrelevant ones)
DC-2 has subnets:
(a couple other irrelevant ones heres)
With current setup, Routes from DC-1 -> DC-2 are going across the point to point link. That's typically what I want EXCEPT, my Ethernet WAN supports QoS while my Point to point does not. I'm trying to get traffic 10.10.116.0/22 <-> 10.10.241.0/24 to go across the 100mbps WAN connection instead of the PTP link. I still want 192.168.240.0/24 <-> DC-1 traffic to go across Point to Point. I need to build-in some failover.
On DC-2 router, I've created a summary route of this:
area 2 range 10.10.240.0 255.255.240.0
area 2 range 10.10.241.0 255.255.255.0
From there, I was going to try removing the /24 route when it comes into DC-1 RTR2. This way, my DC-1 RTR1 should learn both routes across the WAN, however, if the WAN goes down, I want it to use the summary route to go through DC-1 RTR2. I realize the first summary would "Hide" the /24 route, so I created the more specific /24 summary route. However, i'm not able to get both summary routes
in the tables. I dont even see the /21 in the OSPF database. Any hints? Am I going about this all wrong to accomplish what I am trying to do?
Right now I've recreated our network in GNS3 and using that for testing, the current live environment is a bit different.
Current Production environment:
DC-1 is Area 0
WAN is Area 2
DC-2 is Area 1
PTP link between DC-1 and DC-2 is in Area 1
This setup isn't really working well, especially for what i'm trying to do. I'm trying to get a different design that will work. Any thoughts?
Thanks both of you for your input. Right now i'm using static routes. One on DC-1 RTR-1 and one on DC-2. Has about the dynamic-ness of policy routing, but not a whole lot i can do right now haha. Thanks again.
How about sticking an interface on DC-1 RTR-2 onto the Ethernet WAN segment? I can have as many connections to it as i want really. Its one big L2 broadcast domain between my HQ , DR , and 18 branches. Because the point to point link to DC-2 is on RTR-2, i can weight the OSPF on that local router to prefer the Ethernet WAN route instead of the Point to point and if it fails, it'll go across the PTP thats attached to it.
adding DC1 RTR-2 to the Ethernet WAN is a good idea. But if you use OSPF weight to move your traffic over to the Ethernet WAN you have to keep in mind that this will affect every traffic, and not only 10.10.116.0/22 <-> 10.10.241.0/24.
And that means you won't be using your 250Mbit line (you would pay for a line with higher capacity that's only used in a fail-over case?).
Maybe you should have a closer look at PfR - it is easyer to configure as it looks like and it would be more efficent in the term of using both lines at the same time (not all the time but under certain conditions).
You would need to connect DC1 RTR-2 to the Ethernet-WAN (what you suggested) and then configure PfR to
route the traffic 10.10.116.0/22 <-> 10.10.241.0/24 over your Ethernet WAN as soon as the bandwidth utilization on your PtP link will be 50% (or what ever fits best in your environment).
In that scenario you would use both lines when you experience high traffic. And in case of a line outage routing will
This document gives several answers on frequently asked questions for PFRv3 channel state behavior.
Q1: What are all the channel operational states from a BR (border role) perspective and what are the rules/conditions to be in each st...
The need was to reach an host inside a LAN through a VPN connection managed by the LAN gateway (Cisco 1921).
The LAN gateway performs NAT and there was a dedicate nat rule for the host i wanted to reach through VPN.
I couldn't connect to the hos...
We have 3 identical switches configured by someone else and would like to claim some of the Gigabit ports(G1/G2/G3/G4) for use on servers. When we try to change the wiring and configuration, we run in to connectivity issues. Attached is a des...