HSRP & Routing-Need to prevent load balancing from Distribution Layer
I am planning a HSRP implementation on two 1700 series routers. The two routers provide Internet access. My first requirement is to track the serial interface on the primary router and fail over to the secondary router in the event of failure on the secondary router. The second requirement is to only allow 1.5 Mbs of traffic to flow into and out of the customers network.
In lab, I have successfully configured HSRP to track the Serial Interfaces and fail over when the primary interfaces fails. The only hitch is the distribution router sees two routes to both routers. We use static routes at the distribution layer. Here an example of the distribution layer:
ip address 192.168.10.1 255.255.255.252
ip address 192.168.11.1 255.255.255.252
ip route 172.16.0.0 255.255.248.0 Serial1/0/0:1
ip route 172.16.0.0 255.255.248.0 Serial2/0/0:1
The config on the distribution router load balances the routes to the /21 over both serial interfaces. The customer would actually get 3.0 Mbs worth of Internet access into their network and 1.5 Mbs out of their network. The dilema is they are only paying for 1.5 Mbs worth of Internet access. Having the site purchase 3.0 Mbs of transit is not a option. Therefore, it seems that my only recourse is to rate-limit the output of both T1s on the distribution side to 768K. I particularly do not want to apply a rate-limit because if one of the T1s fail, they will only receive half the purchased bandwidth.
Re: HSRP & Routing-Need to prevent load balancing from Distribut
I suggest you try making the destinations for your static routes be the addresses on the 1700s. Then, to favor one of these statics over the other, add a higher admin distance to the second static route. Your static route statements will look like:
ip route 172.16.0.0 255.255.248.0 192.168.10.2
ip route 172.16.0.0 255.255.248.0 192.168.11.2 100
This will result in only the first static route being active, unless there is a line failure, in which case the second will be the only one active.
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...