I would say using a routing protocol would be the best option as it will allow you to load balance across the links and provide redundancy in the event of a link failure. Otherwise you can always use PBR.
Redudancy routing Protocol is best.. but this is DC-->DR site would be prefer static route.. Because data is transfering from one point other only.. Routing Protocol come in picture if packet have to transfer to more hops, thats y routing protocol was prefered.. We can do the Static routing failover with help of IPLA rechablity command.. But i expecting the different solution for above scenario.
If you are looking for something that would be a bit easier to configure and that can scale then routing is your best option regardless of the number of hops, in my humble opinion. It just seems like unnecessary overhead to be configuring static routes and IP SLA when a routing protocol can handle the load balancing and failover quite nicely.
Can I assume that primary & secondary core switches are connected to each other and are you running HSRP from server to reach core switches? If yes, then you can divide 10.x.x.x subnet into half and configure half of the subnet active on primary switch and other half active on secondary switch (this spilt would need to change gateway IP at server end). This way you can achieve load sharing between two core switches and the WAN links.
To achieve redundancy, you can configure track feature in HSRP. This will track the WAN link and switchover to other switch if WAN link fails.
However, I would also recommend to use a protocol for better control and less manageability.
The Author of this posting offers the information contained within this posting without consideration and with the reader's understanding that there's no implied or expressed suitability or fitness for any purpose. Information provided is for informational purposes only and should not be construed as rendering professional advice of any kind. Usage of this posting's information is solely at reader's own risk.
In no event shall Author be liable for any damages whatsoever (including, without limitation, damages for loss of use, data or profit) arising out of the use or inability to use the posting's information even if Author has been advised of the possibility of such damage.
If your hardware supports it, you may want to consider PfR. It does dynamic load balancing.
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...