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.
You have an extra week of fun! Capture the Flag has been extended through July 17. Register using the links below.
As a part of Cisco Live US auxiliary programs, we invite you to learn new technologies and obtain hands-on experience in a...
Hi,I'm trying to setup a cellular connection on my Cisco 1111 router.The interface is UP and it gets a private IPv4 and a public IPv6 address.If I try to send something on IPv4 through the cellular interface it works fine.But there seems to be an issue wi...
For an offline or printed copy of this document, simply choose ⋮ Options > Printer Friendly Page. You may then Print, Print to PDF or copy and paste to any other document format you like.
Is your WAN ready for a multicloud transformation?
Network Insider Live Webinar
Tuesday, July 21, 2020 10:00 am Pacific Time (San Francisco, GMT-08:00)
This webinar will show how convergence between SD-WAN and Security is emerging as important new SASE a...