I have a network scenario involving EIGRP routing between Cisco 6500 and two 3800 routers. The Internet T1s are connected on the 3800 with two T1s on Rt1 and one T1 on Rt2. I have setup EIGRP unequal load balancing on 6500 with variance 2 so that two connections go to Rt1 and one connection goes out to Rt2 and the routing works fine. PAT is running on both 3800s to get out to the internet. However, since the internet T1s have different public serial IP addresses, the connections going out to the internet servers might be taking any T1 path out to the internet and we have users complaining about some websites not fully loading pages with partial pages getting displayed. Is there a better way to define load balancing. CEF is turned on and default connection based load balancing is occuring. I have attached the diagram to be more clear.
Example; From a client PC behind the 6500, I go to ford.com and click on several links on the website. As supposed to work, I see NAT translations on both 3800 routers sourced from the client PC, going to same website ford.com. Is it causing problems because the Ford website sees two different public IP addresses (of the internet t1s) for the same connection ?
Although PBR is a valid option for this topology, but i found it not redundant for example if the Internet link connected to RT2 then the PBR will blackhole the traffic !!! unless you configure PBR with IP SLA in this case you can change the PBR path if the link goes down !!
i think one of the best option for this topology is the use of performance routing
you can configure one of routers as BR and MC and the other router as BR
you assign utilization percent to each link and you use static routing with a tag number all
internally you can keep the eigrp as the routing protocol and in the border routers you redistribute static with only for the taged route assigned
chose a long prefix for the automatically created routes like /29 or /32 in this case the routing will prefer the path based on logiest match and you will have lodbalncing over the links based on links utilization
bellow is a document will take through a simple example of configuring this technology
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...