Hola,
Having unexpected results with a route-map statement applied to an EIGRP distribute-list
(http://i.imgur.com/JzKVJbK.png)
WTBsw1 is set to match subnets found on interface eth 0/0 and apply the EIGRP tag value of 100, then distribute that tag to its upstream EIGRP peers. We have a second entry within the route-map to match anything else and tag 200.
What we're seeing is tag value 200 shows up for the route on WTBsw1's Eth0/0, which indicates to me that the match interface eth0/0 isn't working correctly. When we strip out the route-map statement that matches anything else and tags 200, no routes are found on the upstream peers
There's a lot of good documentation online about using route-maps with EIGRP distribute-lists, but they never discuss matching on interfaces. The command is there, but is this matching feature supported?
"Match options allow EIGRP to filter internal and external routes based on source protocols, to match a metric against a range, and to match on an external protocol metric." - http://www.cisco.com/c/en/us/td/docs/ios-xml/ios/iproute_eigrp/configuration/xe-3s/asr1000/ire-xe-3s-asr1000-book/eigrp-route-map.html#GUID-8BA3E343-7488-4BF4-A4FB-16F96BC98DDD
route-map WTBsw1 permit 10
match interface Ethernet0/0
set tag 100
!
route-map WTBsw1 permit 20
match ip address ANY
set tag 200
router eigrp 100
distribute-list route-map WTBsw1 out
network 10.0.0.0
redistribute connected
redistribute static
WTBsw1#sh ip inter b | ex un
Interface IP-Address OK? Method Status Protocol
Ethernet0/0 10.7.5.1 YES NVRAM up up
Ethernet0/1 10.7.35.2 YES NVRAM up up
Ethernet0/2 10.7.45.2 YES NVRAM up up
WTBrt2#sh ip eigrp top 10.7.5.0/24
10.7.45.2 (Ethernet0/2), from 10.7.45.2, Send flag is 0x0
Internal tag is 200
WTBrt1#sh ip eigrp top 10.7.5.0/24
10.7.35.2 (Ethernet0/1), from 10.7.35.2, Send flag is 0x0
Internal tag is 200
>distribute-list route-map WTBsw1 out
If you want a distribute-list/route-map to apply to a specific interface, specify the interface at the end of the above line. Like this:
distribute-list route-map WTBsw1 out Ethernet0/0
I have never seen it done, in production, the way you've listed it in your post.
ditto to what javentre says, curious as well
Do you have the GNS3 topology handy for quick look-see?
Quote from: wintermute000 on January 14, 2015, 02:09:14 AM
Do you have the GNS3 topology handy for quick look-see?
yes, the GNS3 server is hosted by Google so you can just remote in and play around.
server 146.148.33.16
telnet ports 4001-4011 for network, 4501-4503 for vpcs
use my forums handle here for login, no password is required
(http://i.imgur.com/awz3PTK.png)
Quote from: javentre on January 13, 2015, 10:32:10 AM
>distribute-list route-map WTBsw1 out
If you want a distribute-list/route-map to apply to a specific interface, specify the interface at the end of the above line.
I agree that you can apply the route-map on a per-interface basis, but you can also apply it to all neighbors by not specifying the interfaces to apply it to. The fact that I'm seeing any tag value come in on the neighbors confirms that, but I'll try it out anyhow.
Quote from: wintermute000 on January 14, 2015, 02:09:14 AM
Do you have the GNS3 topology handy for quick look-see?
yes, the GNS3 server is hosted by Google so you can just remote in and play around.
server 146.148.33.1
telnet ports 4001-4011 for network, 4501-4503 for vpcs
use my forums handle here for login, no password is required
(http://i.imgur.com/awz3PTK.png)
awesome. WIll try to look on the weekend. Tied up on a combination of my JNCIS-SP labbing / stupid work faults rite now!