Virtual IP for HSRP between the two routers, on the Ethernet interfaces is 192.168.1.3/24. Active router is RouterA. No HSRP is set on the serial interfaces, which are connected to different ISPs.
If line protocol or s0 physical interface goes down on s0 on RouterA, failover to RouterB will NOT occur, is that right? If I want a failover to be triggered under such scenario I would need to configure object tracking for this. Did I understand this right?
You are close but not quite right. In a simple HSRP configuration you are right that a failure of the serial interface would not cause a failover of the HSRP function. But you do not need Object Tracking to get the failover. In HSRP there is an ability to track interfaces and interface track can cause a failover of HSRP.
Here are some suggestions if you want to configure interface track in HSRP:
- specify priority to select which router is to be active (you do not want to negotiate this). And set the priority to 105 on the active router.
- specify interface track on one or both routers. (if the interface goes down the router will lower its priority by 10 points - resulting in priority of 95).
- configure preempt on both routers. You need preempt on the standby router so that it can take over if the active router lowers its priority. And you want preempt on the original lead router so that when its interface comes back up and its priority returns to 105 that it can take over being active router again.
Now imagine that I DO NOT implement the tracking feature. Then the interface s0 on Router1 fails. As we agreed, HSRP will not failover to the other node.
As long as I have BGP between RouterA and Router2 correctly configured, even without the tracking feature packets which cannot go out of the interface s0 (in case it goes down) will still bounce to RouterB and flow through the ISP2, right?
Yes. If you do not configure interface tracking and if the outbound serial on routerA fails then routerA remains the active HSRP router and when it receives packets to forward it will forward to router2 which will send to its ISP.
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...