EIGRP and Stub connected

[TRACY HARTMANN]

We have two sites both with Managed MPLS routers.  Then we have a local T1 line between them.   We want to use that local T1 line for backup if the MPLS circuit fails at either site.  I have tested that backup and the route from the failed router never seems to get advertised out.

On the routers with the T1 lines I do have 

Router eigrp 400

Network 10.0.0.0

no auto-summary

eigrp stub connected

I was thinking that I need to take the eigrp stub connected off however that causes and issue at other sites because this router tends to want to advertise other routes out of it.

Both subnets fall within the network 10.0.0.0 so I wasn't sure if I needed to have the more specific network or if that even mattered.

[Mark Malone]

Hey

without seeing your eigrp tables an route table its hard to tell what happens during failover but from your scenario if you don't want to remove your stub due to other known issues and still advertise certain routes out you could use something like eigrp stub leak-map and just advertise what you leak basically

eigrp stub connected leak-map leak

[TRACY HARTMANN]

I am going to give this a try tonight.  I am assuming the statement is just an access list with the subnet permitted that we want to advertise?

[Mark Malone]

yes exactly just a route-map matching an acl thata allows it to be leaked out

[TRACY HARTMANN]

eigrp stub connected leak-map leak

ip access-list extended leak permit eigrp ?

[Mark Malone]

Match the acl in a route-map leak

route-map Leak permit 10

match ip address xxxx

[TRACY HARTMANN]

Ok but the match ip address refers to a IP access-list

So on the access-list do I permit eigrp with any or just add the subnet that I want?

[Mark Malone]

sorry i missed that was on the road by then , heres a full example of what im talking about that you can try with config screenshots

http://hackingcisco.blogspot.ie/2011/03/lab-53-eigrp-filtering-with-stub.html