Redistributing static routes on EIGRP stub routers

Ran into this little enigma while working with remote routers and distribution routers using EIGRP. At least, it’s always an enigma when you don’t know how it works, right?

The setup was fairly straightforward: two distribution routers talk to a remote router (configured as a stub in EIGRP), and the remote router has a static route to the subnet in question, 172.x.x.x/24 (see diagram below). How do you redistribute the 172 subnet back the core, through the distribution router?

Originally, I played with static routes. Static routes on Remote (to get a path through the firewall), and static routes on Dist 1 and a static route on the Core. Fine, it worked, but only provisionally. I could reach 172.x.x.x, but if Dist 1 failed, there was no automatic failover of the route. It had to be redistributed into EIGRP.

OK, that’s relatively simple – one one routing protocol, don’t have to work about weighting the metrics, no prob. Just to be sure I was only redistributing the route in question, and nothing else, I created a route map:

ip route 172.x.x.x 255.255.255.0 192.168.x.x (The original static route)

access-list 10 permit 172.x.x.x 0.0.0.255 (ACL identifying the 172.x.x.x subnet)

route-map 172.x.x.x_net permit 10 match ip address 10 (Route Map calling ACL 10)

So far so, good. Now, to redistribute the route into the EIRGP process:

router eigrp 1

redistribute static route-map 172.x.x.x_net

I looked at the eigrp topology table, and? Yes, 172.x.x.x does appear in the topology table:

P 172.19.39.0/25, 1 successors, FD is 28160 via Rstatic (28160/0)

All is well on the Remote router. Now, does the route appear in the Distribution Routers? I take a look at the EIGRP topology table there and? Nothing. Wait, what? Look again. Nothing.

Damn.

The route is making it into the EIGRP process on the remote, but isn’t being advertised to its peers. Why?

After some Googling, I run across this article:

http://www.cisco.com/en/US/docs/ios/12_0s/feature/guide/eigrpstb.html#wp1035883

It explains that in order to advertise redistributed static routes, you have to modify the stub configuration to allow the sending of redistributed static routes, thusly:

router eigrp 1

eigrp stub static

Now, when I check the Distribution Routers, there is the route, pretty as a sunrise on a morning in May.

Note to self: when redistributing static routes on EIGRP stub routers, redistribute first into EIGRP, and then be sure to modify the eigrp stub statement to allow advertisement of the route to EIGRP peers.


Advertisements

2 thoughts on “Redistributing static routes on EIGRP stub routers

  1. Timothy

    This is a very informative article. I was having the same issue. Your analysis provided me with a solution that I could work with. The only difference I was facing was that EIGRP was already configured as ‘eigrp stub connected’. By researching a couple of Cisco docs I found that I could declare ‘eigrp stub connected static’ which meant that I wouldn’t break the network and allow the single static route to be advertised by EIGRP without advertising all the other static routes that were configured on the router! Many thanks for your help.

    Reply
  2. Alam

    It’s a great article, quite helpful and this article has actually resolved one of my problem that i ran into after implementing a recent change in our network

    Reply

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s