Achieving Autofailover between Branches and HQ site using OSPF
I have a number of Branches and ATMs which connect to the HQ via GRE tunnels through L2MPLS of the service provdiers network.
Recently I commisioned a DR site that I would like all the branches and ATMs to point to incase of disaster.
Most importantly I am supposed to achieve an auto-failover solution between Branches and ATMs towards HQ, @ATM and branch has duo links from different providers for resiliency.
The standard I am supposed to use is OSPF between branches and HQ, where we have GRE tunnels running in between, is there anyone who can assist me on how to achieve auto-failover solution between the Branches and HQ using OSPF on the existing GRE tunnels.
What you are asking for here is a full blown network design. It is more than just a few configuration commands.
We can point you in the right direction but we cannot do the entire thing for you.
We would need to know things like is there a direct link between HQ and DR, how many branches, is OSPF already in use, if so what areas do you have, are you proposing to use the same IPs at the DR site etc etc.
But before all that have you thought about how the applications would work ?
Presumably you have applications that run on servers at HQ. How do you sync this information to the DR site servers ?
So a couple of scenarios -
1) the link at HQ fails and all sites automatically switch to DR. Then 10 minutes later the link comes back up so all sites switch back to HQ.
How are you going to make sure that any data written to servers in DR is now replicated to the HQ servers in real time.
2) a branch primary link fails. It switches to DR but all the other branches are still going to HQ.
Again how you are going to ensure the data remains consistent between the HQ and DR servers as you now have two active sites.
Routing protocols are very good at automatically providing failover but they don't understand the applications.
The hard part with DR is not the network, although that in itself can be challenging, but how the applications are going to work.
So if you only want to invoke DR if there is a major outage at your HQ sites which could last for days for example then using a dynamic routing protocol could create more problems than it would solve.
You may not have applications that need to be kept in sync so it may not be an issue for you.
But even then what you are asking for is not trivial, DR never is.
Perhaps you can clarify exactly how it is meant to work otherwise we cannot really point you in the right direction.
The following documents are reviewed on the Ask The Experts Session titled: Use Case Overview and Planning: Cisco DNA Center Project Planning.
Here you can find editable versions of the
Solution Requirements Document UCOP_CiscoDNACenterProjectPlann...
If so, we’d like to speak with you to understand you and your team’s process on how you monitor and troubleshoot network traffic.
We ask that you complete our brief survey: https://ciscoux.az1.qualtrics.com/jfe/form/SV_d4LYJ5oWqWj9CCy Based on your ...
Listen: https://smarturl.it/CCRS8E38 Follow us: twitter.com/CiscoChampionAdding learning capabilities to the internet will increase the overall network SLO and application experience. Real data driven experiments have shown that such an approach...
Listen: https://smarturl.it/CCRS8E37Follow us: twitter.com/ciscochampionSometimes, situations require temporary fixes. Sometimes, the network becomes an afterthought in overall office design and planning. In either situation, it may require netw...
In this special edition of the Insider Series, we hear from Cisco partners who have taken steps to be more eco-friendly and sustainable. We hear what inspires ASHRAE, Southwire, Igor, and NTT to create a workplace that is centered around people and how th...