From: Chuck Larrieu (chuck@xxxxxxxxxxxxx)
Date: Fri Feb 09 2001 - 01:46:13 GMT-3
Chuck, I am glad you asked. I set up a quick and dirty lab to test.
The answer, according to my experiment, is yes - you can add distribute list
commands under the routing protocols in question and it works as expected,
even though you do not explicitly redistribute.
Eigrp-----router6-----eigrp------router4----igrp-----router5---igrp
RELEVANT PARTS OF THE ROUTER 4 CONFIGURATION:
router eigrp 500
network 192.168.2.0
distribute-list 2 out
no auto-summary
!
router igrp 500
network 192.168.1.0
network 197.197.1.0
network 197.197.2.0
network 197.197.3.0
distribute-list 1 out
!
ip classless
access-list 1 deny 192.100.1.0 0.0.0.255
access-list 1 deny 192.100.3.0 0.0.0.255
access-list 1 permit any
access-list 2 deny 201.201.0.0 0.0.255.255
access-list 2 permit any
!
ROUTER 4 ROUTING TABLE - AL ROUTES FROM ALL ROUTERS - ALL IN THE ORIGINAL
PROTOCOL
Router_4#sh ip route
Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, * - candidate
default
U - per-user static route, o - ODR
Gateway of last resort is not set
I 201.201.1.0/24 [100/8726] via 192.168.1.5, 00:00:50, Serial1
C 197.197.1.0/24 is directly connected, TokenRing0
I 201.201.2.0/24 [100/8976] via 192.168.1.5, 00:00:51, Serial1
C 197.197.2.0/24 is directly connected, Loopback1
I 201.201.3.0/24 [100/8976] via 192.168.1.5, 00:00:51, Serial1
C 197.197.3.0/24 is directly connected, Loopback2
C 192.168.1.0/24 is directly connected, Serial1
C 192.168.2.0/24 is directly connected, Serial0
D 192.100.1.0/24 [90/2233856] via 192.168.2.6, 00:07:41, Serial0
D 192.100.2.0/24 [90/2297856] via 192.168.2.6, 00:07:41, Serial0
D 192.100.3.0/24 [90/2297856] via 192.168.2.6, 00:07:42, Serial0
200.200.200.0/32 is subnetted, 1 subnets
C 200.200.200.4 is directly connected, Loopback0
Router_4#
ROUTER 6 ROUTING TABLE - NOTE THE FILTERED ROUTES DO NOT APPEAR:
Router_6#sh ip route
Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, * - candidate
default
U - per-user static route, o - ODR
Gateway of last resort is not set
D EX 197.197.1.0/24 [170/2169856] via 192.168.2.4, 00:07:03, Serial0
D EX 197.197.2.0/24 [170/2169856] via 192.168.2.4, 00:07:04, Serial0
D EX 197.197.3.0/24 [170/2169856] via 192.168.2.4, 00:07:04, Serial0
D EX 192.168.1.0/24 [170/2169856] via 192.168.2.4, 00:07:04, Serial0
C 192.168.2.0/24 is directly connected, Serial0
C 192.100.1.0/24 is directly connected, TokenRing0
C 192.100.2.0/24 is directly connected, Loopback1
C 192.100.3.0/24 is directly connected, Loopback2
200.200.200.0/32 is subnetted, 1 subnets
C 200.200.200.6 is directly connected, Loopback0
Router_6#
ROUTER 5 ROUTING TABLE - NOTE THE FILTERED ROUTES DO NOT APPEAR.
Router_5#sh ip route
Codes: C - connected, S - static, I - IGRP, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2, E - EGP
i - IS-IS, L1 - IS-IS level-1, L2 - IS-IS level-2, * - candidate
default
U - per-user static route, o - ODR
Gateway of last resort is not set
I 197.197.1.0/24 [100/8726] via 192.168.1.4, 00:00:02, Serial1
C 201.201.1.0/24 is directly connected, TokenRing0
I 197.197.2.0/24 [100/8976] via 192.168.1.4, 00:00:03, Serial1
C 201.201.2.0/24 is directly connected, Loopback1
I 197.197.3.0/24 [100/8976] via 192.168.1.4, 00:00:03, Serial1
C 201.201.3.0/24 is directly connected, Loopback2
C 192.168.1.0/24 is directly connected, Serial1
I 192.168.2.0/24 [100/10476] via 192.168.1.4, 00:00:03, Serial1
I 192.100.2.0/24 [100/10976] via 192.168.1.4, 00:00:03, Serial1
200.200.200.0/32 is subnetted, 1 subnets
C 200.200.200.5 is directly connected, Loopback0
Router_5#
Add just one more bit of obscure expertise to the pile :->
Chuck
59 days - :-O
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Chuck Church
Sent: Thursday, February 08, 2001 11:14 AM
To: 'Chuck Larrieu'; CCIE_Lab Groupstudy List
Subject: RE: Experiments - Distribute List out
Chuck, anyone,
I noticed you're explicitly redistributing between IGRP and EIGRP.
Remember that if the AS numbers are the same, the redistribution occurs
automatically. Now, my question is can you still use distribute lists if
the redistribution is automatic? I'm not at my lab to try it right now.
Also, I remember IPX rip and EIGRP will also automatically redistribute.
Same distribute lists rules apply?
Thanks,
Chuck Church
CCNP, CCDP, MCNE, MCSE
Sr. Network Engineer
Magnacom Technologies
140 N. Rt. 303
Valley Cottage, NY 10989
845-267-4000 x218
-----Original Message-----
From: Chuck Larrieu [mailto:chuck@cl.cncdsl.com]
Sent: Monday, January 29, 2001 2:34 AM
To: CCIE_Lab Groupstudy List
Subject: Experiments - Distribute List out
This has been fun. Several practice labs have left me realizing I didn't
understand the distribute-list function all that well. Thanks to some of you
here for your posts on the subject. And let me follow up with a report on my
own experiments.
Igrp_domain-----redistribution_router---------rip_domain
Pretty simple lab. Played around with access-lists and redistribution and
distribute-list out. It is indeed as someone here pointed out. A better
command might have been "redistribute-list" It would appear that the
distribute-list works in conjunction with the redistribute command under the
routing protocol configuration. So now I believe I understand. The routing
protocol is redistributing routes from a different routing protocol, and the
distribute-list out command further determines which of those other routing
protocol 's routes get redistributed. Makes sense now.
OK. I'm a bright boy. So what is the purpose of the distribute-list out
options?
A not quite so quick and dirty lab helps clarify things.
Standard hub and spoke setup, with router_1 being the hub, and routers 2,3,
and 4 being the spokes. Router_2 is IGRP, router_3 is EIGRP ( different AS
number so we have to redistribute ), and router_4 is RIP. Router_1 has all
three protocols enabled, and redistributes among them.
Using loopbacks to simulate 6 subnets on each router, and configuring the
redistribution router appropriately, I can see all routes from all domains
in the routing tables of each domain. Life is good
Next, I want to verify that what I believe about the distribute-list out
options is true. I.e. in the situation I have created on the redistribution
router, distribute-list out options are the means of accomplishing complex
redistribution when several routing protocols are involved on the same
router.
So, in my case, I create several access-lists, each one permitting half of
the subnets for each routing protocol. And I tailor my distribute-list out
commands under each routing protocol configuration to accomplish my goal of
permitting only selected halves of a protocol's subnets to be redistributed
into other protocols.
I know this isn't making much sense, and unfortunately I am too tired to set
things up so that folks can visit my lab and see exactly what I am talking
about. I have included the relevant parts of the redistribution router's
configuration to help clarify things.
Let me just say that I did correctly predict which routes would show up
where prior to applying the distribute lists. So I am taking that as a sign
that this small thing is now making sense to me.
!
router eigrp 500
redistribute rip metric 5000 1000 255 1 1500
redistribute igrp 100 metric 10000 100 255 1 1500
network 192.168.30.0
distribute-list 44 out rip
distribute-list 22 out igrp 100
!
router rip
redistribute igrp 100 metric 10
redistribute eigrp 500 metric 5
network 192.168.40.0
distribute-list 2 out igrp 100
distribute-list 3 out eigrp 500
!
router igrp 100
redistribute rip metric 5000 1000 255 1 1500
redistribute eigrp 500 metric 10000 100 255 1 1500
network 192.168.20.0
distribute-list 4 out rip
distribute-list 33 out eigrp 500
!
access-list 2 permit 192.168.21.0 0.0.0.255
access-list 2 permit 192.168.22.0 0.0.0.255
access-list 2 permit 192.168.23.0 0.0.0.255
access-list 3 permit 192.168.31.0 0.0.0.255
access-list 3 permit 192.168.32.0 0.0.0.255
access-list 3 permit 192.168.33.0 0.0.0.255
access-list 4 permit 192.168.41.0 0.0.0.255
access-list 4 permit 192.168.42.0 0.0.0.255
access-list 4 permit 192.168.43.0 0.0.0.255
access-list 22 permit 192.168.24.0 0.0.0.255
access-list 22 permit 192.168.25.0 0.0.0.255
access-list 22 permit 192.168.26.0 0.0.0.255
access-list 33 permit 192.168.34.0 0.0.0.255
access-list 33 permit 192.168.35.0 0.0.0.255
access-list 33 permit 192.168.36.0 0.0.0.255
access-list 44 permit 192.168.44.0 0.0.0.255
access-list 44 permit 192.168.45.0 0.0.0.255
access-list 44 permit 192.168.46.0 0.0.0.255
!
Got a long day with bootcamp planned for tomorrow. See you all another time.
Chuck
A long shot at passing is better than no shot.
Right now that's all I got to get me through,
So I gotta believe!
( paraphrased from Kathy Baille / Baille and the Boys
a song from several years ago )
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:28:42 GMT-3