eigrp route distribution issue

[lkadlik]

hi,

I am trying to advertise the following network to my other offices /eigrp peers

10.20.147.0/24

The network exists via  a static route on the router i need to advertise it from.  when i go under the eigrp config and say "redistribute static" it advertises the route.  The issue is there are other statics that I do not want advertised. This is the only static that I want to be advertised from this core.  When I tried the following the new network was not advertised.

route-map StaticVPN_to_EIGRP permit 10

match ip address 120

set metric 10000 100 255 1 1500

access-list 120 permit ip 10.20.147.0 0.0.0.255 any

router eigrp 7

redistribute static route-map StaticVPN_to_EIGRP

Thoughts?

Thank you.

Lynne

[cadet alain · Accepted solution]

Hi,

use a standard ACL or better a prefix-list to redistribute the static route.

ip prefix-list REDISTR_STATIC permit 10.20.147.0/24

route-map StaticVPN_to_EIGRP permit 10

match ip address prefix REDISTR_STATIC

set metric 10000 100 255 1 1500

Regards.

Alain

Don't forget to rate helpful posts.

[lkadlik]

Hi,

I am sorry.  This is probably a dumb questions but why is a pre-fix list better/correct compared to an acl?

thanks

Lynne

[cadet alain]

Hi,

only a prefix-list can match on both prefix and prefix-length.an ACL will only match on the prefix and not the prefix-length

so you may end up redistributing routes you don't wish to.

Regards.

Alain

Don't forget to rate helpful posts

[fb_webuser]

Use a standard ACL: ip access-list standard NAME and permit 10.20.147.0 0.0.0.255

OR

You can use a prefix-list: ip prefix-list NAME 5 permit 10.20.147.0/24

---

Posted by WebUser James Holley from Cisco Support Community App

[fb_webuser]

fb was having issues and did not see @cadetalain most excellent post that ties in the change in route-map syntax adding the "match ip address prefix" keyword.

---

Posted by WebUser James Holley from Cisco Support Community App

[fb_webuser]

To answer your question it is not better, just most tech professionals now use them in place of ACL. When using an ACL for route-map filtering you need to use a Standard ACL which has the command syntax: access-list access-list-number deny source .

With access-list 120, in your case your syntax is sor source and destination pair and protocols- too numerous to list here, but the bottom line is that you use standard ACL when using access-lists, because when using extended ACL it leads to tech issues. I think in your case you originally used access-list 120 permit ip 10.20.147.0 0.0.0.255 any

which means permit the ip protocol from source 10.20.147.0/24 (hosts 1-254 of that segment) to any destination. This would be used in a situation wher you were blocking/allowing traffic from a lan to a destination through the router (router as a filter)

---

Posted by WebUser James Holley from Cisco Support Community App

[jdholley]

Sorry, I was answering from fb app. Second sentence in the post should have been: 

When using an ACL for route-map filtering you need to use a Standard ACL which has the command syntax:

access-list access-list-number [deny|permit]  source [source-wildcard] [log]

[fb_webuser]

You can use distribute-list to filter routes.

router eigrp 7

redistribute static metric 10000 100 255 1 1500

distribute-list 120 out static

auto-summary

access-list 120 permit ip any 10.20.147.0 0.0.0.255

HTH,

Eduardo Campos

---

Posted by WebUser Eduardo Campos from Cisco Support Community App