I am looking for a High Availability solution for a WAN Core with 12 odd Chanelized and Frac T1 and a handful of odd 56k lines coming into it. Idealy I would like some sort of circuit failover for in the event of a system failure.
I can't seem to be able to find a solution for that meets this requirement. Any and all help is appretiated.
I am looking for a HA solution. In the IBM AIX world they call it HACMP. In the Microsoft world they call it a Fail Over Cluster.
I have a router with data circuits connected to it. I want a redundant router to 'take over' those data circuits when my primary router fails for whatever reason.
Think of it as a HOT SPARE solution. Instead of a hot spare power supply, a hot spare router. There used to be a technology available for cisco that did this. I find it hard to believe I am the only one looking for this?
There is a VRRP/Hot Standby Router Protocol supported by Cisco, but that's a LAN protocol. May be that's what you are looking for.
If there are two routers A and B, forming cluster e.g., and router A connects to a T1. If A goes down how will the T1 of downed router A be fed to router B? You are talking additional smart devices here to sense the router down and feed the T1 to other router. I am not aware of any such devices.
HSRP is the typical way to provide automatic failover for hosts on a LAN with Cisco routers. Other vendors use the open standard VRRP, which provides equivalent services (albeit in a different way with different strengths and weaknesses). WAN links usually are protected by standard routing protocols supporting redundant links and the issues are totally different from those on the LAN side of the routers. Both sides need to be addressed for real high availability.
Chapter six of my book "High Availability Networking with CIsco" is dedicated to the challenge of having one router on a LAN cover for the failure of an alternate router on the same LAN. I would recommend, however, reading the entire book, looking at the concepts in Chapter three (multihoming a host to multiple LANs), Eight (multihoming through multiple ISPs), Nine (redundant firewalls), Eleven (disaster recovery) and Twelve (management considerations).
I am assuming from your clarification that you have already taken care of the cluster and data considerations inherent in a useful HA solution. If you are not familiar with Marcus & Stern's "Blueprints for High Availability", you should pick up a copy and read that first. My book is a 600 page expansion of their one chapter on networking considerations.
For what it's worth, you'll find the data circuits far more prone to failure than the routers at either end. Consequently, while there are black boxes which will switch a data circuit from one router to another, the added availability is more often an illusion, as the black box also becomes yet another single point of failure. You would get more bang for your buck by focusing on physical diversity of your circuits.
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 ...