You can configure HSRP to act either way, ie if pri 1 fails, don't fail HSRP over to the other 3640 (so pri2 users are uninterrupted/work normally) or you can have it fail over (pri1 and pri2 users now on second 3640). The way you do this is with priority and track commands. You can track both pri lines and assign a value to decrement the priority by so that if one or both dies it can force the failover to the other 3640.
Once the failover occurs, users pointing to the HSRP address (and they may be users of the dead pri1 and active pri2) will now point to the second 3640.
Users on the pri2 won't be stay on that line, they will be forced over to the second 3640.
You have to create two HSRP groups one for each PRI on each 36XX rtr.
36xx--1 rtr wil be active for pri1 and will track it priority decrement . and will switch over all activities reated to that pri ti 36xx--2 only . all other traffic for pri2 wil still fo through 36xx--1 and vice versa....
Lemme know if you need comfig as well.... I can send you a config lemme know ur Ips and setup ...
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 ...