2 Cities, 2 ASAs trying to route EIGRP between 4 routers

the_crooked_toe · ‎11-24-2008

Between 2 cities I have 2 connections, 4 routers, and 2 ASA5510s.

Louisville has a 2851 that talks to a 2821 in Lexington over a MPLS line.

Louisville has a 3662 that talks to a 3640 in Lexington over a Point-To-Point connection.

I want to use the MPLS as the primary connection and the Point-to-Point as the backup.

I am trying to add the ASA5510s into the EIGRP routing, but I am currently having trouble getting the routes through EIGRP and BGP to talk correctly. All the routes can be found, but they are defaulting to the Point-to-Point connection and not the MPLS. I would like to do this without setting a static route.

Here is a diagram

Louisville

Cisco 4507 is the core router. The 2851 and the 3662 are both connected to the core router. The ASA5510 is connected to the core router

If I try to add our DMZ addresses to EIGRP 101 (so Lexington can access the DMZ servers through our internal network), i get too many hops. If I trace the DMZ address from my desk it should go from my desk, to the core router, to the ASA. Instead, its going from my desk, to the Louisville MPLS router, to the Lexington MPLS router, to the Lexington Point-to-Point router, to the Louisville Point-toPoint router, then to the ASA.

I don't see where I'm going wrong. The MPLS routers use BGP and EIGRP, while the Point-to-Point routers use EIGRP only.

209.XXX.69.0 is the ip address range in Louisville that I want to broadcast. Notice it says connected to the MPLS router 192.168.187.252, but it should say connected to 192.168.187.99. It's like my core router doesn't want to talk with the ASA.

209.XXX.222.0 is the ip address range in Lexington that I want to broadcast. It should say it's coming from 192.168.187.252 (the mpls router), but its coming from the Point-to-Point (192.168.187.254).

the_crooked_toe · ‎11-24-2008

here is a sh ip route from the core router.

192.168.107.0/30 is subnetted, 1 subnets

D 192.168.107.0 [90/3178752] via 192.168.187.254, 01:49:38, Vlan1

D EX 192.168.28.0/24 [170/258816] via 192.168.187.252, 7w0d, Vlan1

D EX 192.168.13.0/24 [170/258816] via 192.168.187.252, 1w6d, Vlan1

C 192.168.15.0/24 is directly connected, Vlan15

64.0.0.0/30 is subnetted, 4 subnets

D EX 64.129.251.56 [170/1767168] via 192.168.187.254, 02:29:38, Vlan1

D EX 64.129.251.60 [170/258816] via 192.168.187.252, 7w0d, Vlan1

D EX 64.129.251.72 [170/258816] via 192.168.187.252, 7w0d, Vlan1

D EX 64.129.251.76 [170/258816] via 192.168.187.252, 1w6d, Vlan1

D 192.168.128.0/24 [90/1762048] via 192.168.187.254, 01:49:38, Vlan1

S 192.168.198.0/24 [1/0] via 192.168.187.99

S 192.168.199.0/24 [1/0] via 192.168.187.99

10.0.0.0/24 is subnetted, 9 subnets

C 10.110.115.0 is directly connected, Vlan115

C 10.110.2.0 is directly connected, Vlan2

C 10.110.232.0 is directly connected, Vlan232

C 10.110.233.0 is directly connected, Vlan233

C 10.110.215.0 is directly connected, Vlan215

C 10.10.201.0 is directly connected, Vlan201

D 10.20.201.0 [90/1764864] via 192.168.187.254, 01:49:41, Vlan1

C 10.110.132.0 is directly connected, Vlan132

C 10.110.133.0 is directly connected, Vlan133

D 192.168.113.0/24 [90/1762048] via 192.168.187.254, 01:49:41, Vlan1

C 192.168.36.0/24 is directly connected, Vlan36

C 192.168.53.0/24 is directly connected, Vlan53

D 192.168.7.0/24 [90/3181312] via 192.168.187.254, 03:37:48, Vlan1

C 192.168.52.0/24 is directly connected, Vlan52

C 192.168.187.0/24 is directly connected, Vlan1

C 192.168.34.0/24 is directly connected, Vlan34

C 192.168.50.0/24 is directly connected, Vlan50

C 192.168.35.0/24 is directly connected, Vlan35

D EX 209.XXX.69.0/24 [170/258816] via 192.168.187.252, 00:06:26, Vlan1

D 192.168.118.0/24 [90/1762048] via 192.168.187.254, 01:49:42, Vlan1

D EX 192.168.253.0/24 [170/258816] via 192.168.187.252, 04:37:57, Vlan1

C 192.168.32.0/24 is directly connected, Vlan32

D EX 192.168.18.0/24 [170/258816] via 192.168.187.252, 7w0d, Vlan1

C 192.168.33.0/24 is directly connected, Vlan33

D 209.XXX.222.0/24 [90/1767168] via 192.168.187.254, 00:39:17, Vlan1

S* 0.0.0.0/0 [1/0] via 192.168.187.99

Any help is greatly appreciated. It's weird because the MPLS is the default route for every network. I just can't understand why the ASAs in both cities are not being routed through it.

Thanks!