From: Sally Crawford (crawford0982003@yahoo.com)
Date: Sun Mar 28 2004 - 22:58:56 GMT-3
Hi All
Does anyone know why when redistributing eigrp into rip, the isis and connected rip interfaces are blocked ? ie
!
router rip
version 2
redistribute isis level-2 metric 1 route-map isis-any
redistribute eigrp 100 metric 2 route-map eigrp-rip
!
router eigrp 100
redistribute isis level-2 metric 10000 100 255 1 1500 route-map isis-any
redistribute rip metric 10000 100 255 1 1500 route-map rip-eigrp
!
router isis
redistribute eigrp 100 metric 1 route-map any-isis
redistribute rip metric 1 route-map any-isis
!
ip access-list standard eigrp-p
permit 6.6.0.0
permit 172.16.10.128
permit 172.16.200.4
permit 172.16.200.12
permit 172.16.200.8
permit 172.16.35.0
permit 172.16.16.0
permit 172.16.10.0
ip access-list standard isis-p
permit 172.16.200.16
permit 172.16.30.0
ip access-list standard rip-r3r4-p
permit 172.16.34.0
permit 172.16.35.0
permit 172.16.30.0
!
route-map rip-eigrp deny 10
match ip address eigrp-p
!
route-map rip-eigrp permit 20
!
route-map eirgp-rip deny 10 <--
match ip address isis-p
!
route-map eigrp-rip deny 20 <--
match ip address rip-r3r4-p
!
route-map eigrp-rip permit 30
!
route-map isis-any permit 10
match ip address isis-p
!
route-map any-isis deny 10
match ip address isis-p
!
route-map any-isis permit 20
!
I understand that rip covers the interfaces that are connected, but why explicity block the routes in eigrp ?
Its a bit hard to explain without posting the whole lab, but for those who have completed it may understand the question.
Thanks in advance
Sally
---------------------------------
Do you Yahoo!?
Yahoo! Finance Tax Center - File online. File on time.
This archive was generated by hypermail 2.1.4 : Thu Apr 01 2004 - 08:15:49 GMT-3