Re: EIGRP stub leak-map

ahh classic hub and spoke..

thanks Narbik clear & concise many thanks

On 11 July 2012 22:58, Narbik Kocharians <narbikk_at_gmail.com> wrote:

> Have a look at this lab, sorry for the long post.
>
> *Topology:*
> R1 is the hub and it's configured with three P2P sub-interfaces:
> S0/0.12 (connecting R1 to R2)
> S0/0.13 (Connecting R1 to R3)
> S0/0.14 (Connecting R1 to R4)
> R4 and R5 are connected via a Frame-relay P2P connection.
> *IP Addressing:*
> *R1's IP addressing:*
> connection to R2 10.1.12.1/24
> connection to R3 10.1.13.1/24
> connection to R4 10.1.14.1/24
> Loopback 0 1.1.1.1/24
> *R2's IP addressing:*
> connection to R1 10.1.12.2/24
> *R3's IP addressing:*
> connection to R1 10.1.13.3/24
> *R4's IP addressing:*
> connection to R1 10.1.14.4/24
> connection to R5 10.1.45.4/24
> *R5's IP addressing:*
> connection to R4 10.1.45.5/24
> Loopback 2 2.2.2.2/24
> Loopback 3 3.3.3.3/24
>
>
> *Task 1*
>
> * *
>
> Configure OSPF area 0 on the following routers/interfaces; ensure
>
> that the loopback interfaces are advertised with their correct mask:
>
>
>
> *Router*
>
> *Interface*
>
> R4
>
> S0/0.45
>
> *R5*
>
> *S0/0.54*
>
> *Loopback 2*
>
> *Loopback 3*
>
>
>
>
>
>
>
> *On R4*
>
>
>
> R4(config)#*router ospf 1*
>
> R4(config-router)#*netw 10.1.45.4 0.0.0.0 area 0*
>
>
>
> *On R5*
>
>
>
> R5(config)#*int lo2*
>
> R5(config-if)#*ip ospf netw point-to-point*
>
>
>
> R5(config-if)#*int lo3*
>
> R5(config-if)#*ip ospf netw point-to-point*
>
>
>
> R5(config)#*router ospf 1*
>
> R5(config-router)#*netw 10.1.45.5 0.0.0.0 area 0*
>
>
>
> R5(config-router)#*netw 2.2.2.2 0.0.0.0 area 0*
>
> R5(config-router)#*netw 3.3.3.3 0.0.0.0 area 0*
>
>
>
> *To verify the configuration:*
>
> * *
>
> *On R4*
>
>
>
> R4#*show ip route ospf*
>
>
>
> 2.0.0.0/24 is subnetted, 1 subnets
>
> O 2.2.2.0 [110/65] via 10.1.45.5, 00:01:18, Serial0/0.45
>
> 3.0.0.0/24 is subnetted, 1 subnets
>
> O 3.3.3.0 [110/65] via 10.1.45.5, 00:01:18, Serial0/0.45
>
>
>
>
>
>
>
> *Task 2*
>
>
>
> Configure Eigrp 100 on the following routers/interfaces; disable
>
> auto summarization.
>
>
>
> *Router*
>
> *Interface*
>
> R1
>
> S0/0.12
>
> S0/0.13
>
> S0/0.14
>
> Loopback 0
>
> R2
>
> S0/0.21
>
> R3
>
> S0/0.31
>
> R4
>
> S0/0.41
>
>
>
>
>
>
>
> *On R1*
>
>
>
> R1(config)#*router eigrp 100*
>
> R1(config-router)#*NO au*
>
> R1(config-router)#*netw 10.1.12.1 0.0.0.0*
>
> R1(config-router)#*netw 10.1.13.1 0.0.0.0*
>
> R1(config-router)#*netw 10.1.14.1 0.0.0.0*
>
> R1(config-router)#*netw 1.1.1.1 0.0.0.0*
>
>
>
> *On R2*
>
>
>
> R2(config)#*router eigrp 100*
>
> R2(config-router)#*NO au*
>
> R2(config-router)#*netw 10.1.12.2 0.0.0.0*
>
>
>
> *On R3*
>
>
>
> R3(config)#*router eigrp 100*
>
> R3(config-router)#*NO au*
>
> R3(config-router)#*netw 10.1.13.3 0.0.0.0*
>
>
>
> *On R4*
>
>
>
> R4(config)#*router eigrp 100*
>
> R4(config-router)#*NO au*
>
> R4(config-router)#*netw 10.1.14.4 0.0.0.0*
>
>
>
> *To verify the configuration:*
>
> * *
>
> *On R4*
>
>
>
> R4#*show ip route eigrp *
>
>
>
> 1.0.0.0/24 is subnetted, 1 subnets
>
> D 1.1.1.0 [90/2297856] via 10.1.14.1, 00:04:29, Serial0/0.41
>
> 10.0.0.0/24 is subnetted, 4 subnets
>
> D 10.1.13.0 [90/2681856] via 10.1.14.1, 00:14:24, Serial0/0.41
>
> D 10.1.12.0 [90/2681856] via 10.1.14.1, 00:14:24, Serial0/0.41
>
>
>
> *On R3*
>
>
>
> R3#*show ip route eigrp *
>
>
>
> 1.0.0.0/24 is subnetted, 1 subnets
>
> D 1.1.1.0 [90/2297856] via 10.1.13.1, 00:03:58, Serial0/0.31
>
> 10.0.0.0/24 is subnetted, 3 subnets
>
> D 10.1.14.0 [90/2681856] via 10.1.13.1, 00:14:48, Serial0/0.31
>
> D 10.1.12.0 [90/2681856] via 10.1.13.1, 00:14:48, Serial0/0.31
>
>
>
> *On R2*
>
>
>
> R2#*show ip route eigrp*
>
>
>
> 1.0.0.0/24 is subnetted, 1 subnets
>
> D 1.1.1.0 [90/2297856] via 10.1.12.1, 00:03:08, Serial0/0.21
>
> 10.0.0.0/24 is subnetted, 3 subnets
>
> D 10.1.14.0 [90/2681856] via 10.1.12.1, 00:15:16, Serial0/0.21
>
> D 10.1.13.0 [90/2681856] via 10.1.12.1, 00:15:16, Serial0/0.21
>
>
>
>
>
>
>
> *Task 3*
>
>
>
> Configure mutual redistribution between OSPF and EIGRP on R4; use a
>
> metric of your choice.
>
>
>
>
>
> *On R4*
>
>
>
> R4(config)#*router ospf 1*
>
> R4(config-router)#*redistribute eigrp 100 subnets*
>
>
>
> R4(config)#*router eigrp 100*
>
> R4(config-router)#*redistribute ospf 1 metric 1 1 1 1 1*
>
>
>
> *To verify the configuration:*
>
> * *
>
> *On R5*
>
> * *
>
> R5#*show ip route ospf | inc O*
>
>
>
> O E2 1.1.1.0 [110/20] via 10.1.45.4, 00:06:00, Serial0/0.54
>
> O E2 10.1.14.0 [110/20] via 10.1.45.4, 00:07:39, Serial0/0.54
>
> O E2 10.1.13.0 [110/20] via 10.1.45.4, 00:07:39, Serial0/0.54
>
> O E2 10.1.12.0 [110/20] via 10.1.45.4, 00:07:39, Serial0/0.54
>
>
>
> *On R1*
>
>
>
> R1#*show ip route eigrp*
>
>
>
> 2.0.0.0/24 is subnetted, 1 subnets
>
> D EX 2.2.2.0 [170/2560512256] via 10.1.14.4, 00:01:00, Serial0/0.14
>
> 3.0.0.0/24 is subnetted, 1 subnets
>
> D EX 3.3.3.0 [170/2560512256] via 10.1.14.4, 00:01:00, Serial0/0.14
>
> 10.0.0.0/24 is subnetted, 4 subnets
>
> D EX 10.1.45.0 [170/2560512256] via 10.1.14.4, 00:01:00, Serial0/0.14
>
> * *
>
> *On R2*
>
>
>
> R2#*show ip route eigrp*
>
> * *
>
> 1.0.0.0/24 is subnetted, 1 subnets
>
> D 1.1.1.0 [90/2297856] via 10.1.12.1, 00:07:33, Serial0/0.21
>
> * 2.0.0.0/24 is subnetted, 1 subnets*
>
> *D EX 2.2.2.0 [170/2561024256] via 10.1.12.1, 00:01:51, Serial0/0.21*
>
>
> * 3.0.0.0/24 is subnetted, 1 subnets*
>
> *D EX 3.3.3.0 [170/2561024256] via 10.1.12.1, 00:01:51, Serial0/0.21
> *
>
> 10.0.0.0/24 is subnetted, 4 subnets
>
> D 10.1.14.0 [90/2681856] via 10.1.12.1, 00:19:41, Serial0/0.21
>
> D 10.1.13.0 [90/2681856] via 10.1.12.1, 00:19:41, Serial0/0.21
>
> D EX 10.1.45.0 [170/2561024256] via 10.1.12.1, 00:01:51, Serial0/0.21
>
>
>
> *On R3*
>
>
>
> R3#*show ip route eigrp*
>
>
>
> 1.0.0.0/24 is subnetted, 1 subnets
>
> D 1.1.1.0 [90/2297856] via 10.1.13.1, 00:10:45, Serial0/0.31
>
> *2.0.0.0/24 is subnetted, 1 subnets*
>
> *D EX 2.2.2.0 [170/2561024256] via 10.1.13.1, 00:05:02, Serial0/0.31*
>
> * 3.0.0.0/24 is subnetted, 1 subnets*
>
> *D EX 3.3.3.0 [170/2561024256] via 10.1.13.1, 00:05:02, Serial0/0.31*
>
> 10.0.0.0/24 is subnetted, 4 subnets
>
> D 10.1.14.0 [90/2681856] via 10.1.13.1, 00:21:34, Serial0/0.31
>
> D 10.1.12.0 [90/2681856] via 10.1.13.1, 00:21:34, Serial0/0.31
>
> D EX 10.1.45.0 [170/2561024256] via 10.1.13.1, 00:05:02, Serial0/0.31
>
>
>
> *NOTE: R2 and R3 have networks 2.2.2.0/24 and 3.3.3.0/24.*
>
>
>
>
>
>
>
> *Task 4*
>
>
>
> Configure Eigrp stub on R1 such that it ONLY advertises its
>
> directly connected interfaces that are advertised with a network command
>
> to its Eigrp neighbors.
>
>
>
>
>
> *On R1*
>
>
>
> R1(config)#*router eigrp 100*
>
> R1(config-router)#*eigrp stub connected*
>
>
>
> *To verify the configuration:*
>
> * *
>
> *On R2*
>
>
>
> R2#*show ip route eigrp *
>
>
>
> 1.0.0.0/24 is subnetted, 1 subnets
>
> D 1.1.1.0 [90/2297856] via 10.1.12.1, 00:02:01, Serial0/0.21
>
> 10.0.0.0/24 is subnetted, 3 subnets
>
> D 10.1.14.0 [90/2681856] via 10.1.12.1, 00:02:01, Serial0/0.21
>
> D 10.1.13.0 [90/2681856] via 10.1.12.1, 00:02:01, Serial0/0.21
>
>
>
> *On R3*
>
> * *
>
> R3#*show ip route eigrp*
>
>
>
> 1.0.0.0/24 is subnetted, 1 subnets
>
> D 1.1.1.0 [90/2297856] via 10.1.13.1, 00:02:41, Serial0/0.31
>
> 10.0.0.0/24 is subnetted, 3 subnets
>
> D 10.1.14.0 [90/2681856] via 10.1.13.1, 00:02:41, Serial0/0.31
>
> D 10.1.12.0 [90/2681856] via 10.1.13.1, 00:02:41, Serial0/0.31
>
>
>
> *On R1*
>
>
>
> R1#*show ip route eigrp*
>
>
>
> 2.0.0.0/24 is subnetted, 1 subnets
>
> D EX 2.2.2.0 [170/2560512256] via 10.1.14.4, 00:03:25, Serial0/0.14
>
> 3.0.0.0/24 is subnetted, 1 subnets
>
> D EX 3.3.3.0 [170/2560512256] via 10.1.14.4, 00:03:25, Serial0/0.14
>
> 10.0.0.0/24 is subnetted, 4 subnets
>
> D EX 10.1.45.0 [170/2560512256] via 10.1.14.4, 00:03:25, Serial0/0.14
>
>
>
> *Note R2 and R3 DO NOT have the redistributed routes; this is because of
> R1s stub connected configuration.*
>
> * *
>
>
>
>
>
> *Task 5*
>
>
>
> Configure R1 such that routers R2 and R3 have networks 2.2.2.0 /24 and
>
> 3.3.3.0 /24 in their routing table. DO NOT remove the Eigrp stub
> connected
>
> configuration from R1 to accomplish this task.
>
>
>
>
>
> *To accomplish this task a leak-map is referenced in the Eigrp stub
> connected command. *
>
> *The leak-map references a route-map called TST, the route-map
> references an access-list. *
>
> *Any IP address/es that are permitted in the access-list is leaked along
> the connected networks.*
>
>
>
> *On R1*
>
>
>
> R1(config)#*access-list* *1* *permit 2.2.2.0 0.0.0.255*
>
> R1(config)#*access-list* *1* *permit 3.3.3.0 0.0.0.255*
>
>
>
> R1(config)#*route-map* *TST* *permit 10*
>
> R1(config-route-map)#*match ip addr 1*
>
>
>
> R1(config)#*router eigrp 100*
>
> R1(config-router)#*eigrp stub connected leak-map* *TST*
>
>
>
> *To verify the configuration:*
>
> * *
>
> *On R2*
>
> * *
>
> *R2#show ip route eigrp | inc ex*
>
>
>
> *D EX 2.2.2.0* [170/2561024256] via 10.1.12.1, 00:04:29, Serial0/0.21
>
> *D EX 3.3.3.0* [170/2561024256] via 10.1.12.1, 00:04:29, Serial0/0.21
>
> * *
>
> *On R3*
>
> * *
>
> *R3#show ip route eigrp | inc ex*
>
>
>
> *D EX 2.2.2.0* [170/2561024256] via 10.1.13.1, 00:00:13, Serial0/0.31
>
> *D EX 3.3.3.0* [170/2561024256] via 10.1.13.1, 00:00:13, Serial0/0.31
>
>
>
> *Note both R2 and R3 have both networks (2.2.2.0 /24 and 3.3.3.0 /24) in
> their routing table.*
>
>
>
>
>
> * *
>
> *Task 6*
>
>
>
> Re-configure R1 such that R2 gets network 2.2.2.0 /24 and R3 gets
>
> network 3.3.3.0 /24. DO NOT remove the Eigrp stub connected
> configuration
>
> from R1 to accomplish this task.
>
>
>
>
>
> *The access-list and the route-map TST should be removed before
> proceeding further: *
>
> * *
>
> *On R1*
>
>
>
> R1(config)#*NO* *access-list 1*
>
> R1(config)#*NO* *route-map TST*
>
>
>
>
>
> *We should identify the two networks using two different access-lists, in
> this *
>
> *case access-list 2 identifies network 2.2.2.0 /24 and access-list 3
> identifies *
>
> *network 3.3.3.0 /24:*
>
>
>
> R1(config)#*access-list* *2* *permit 2.2.2.0 0.0.0.255*
>
> R1(config)#*access-list* *3* *permit 3.3.3.0 0.0.0.255*
>
>
>
> *The next step is to configure a new route-map as follows:*
>
>
>
> R1(config)#*route-map* *TST* *permit 10*
>
> R1(config-route-map)#*match ip addr* *2*
>
> R1(config-route-map)#*match inter S0/0.12*
>
>
>
> R1(config-route-map)#*route-map* *TST* *permit 20*
>
> R1(config-route-map)#*match ip addr* *3*
>
> R1(config-route-map)#*match inter S0/0.13*
>
> * *
>
> *To verify the configuration:*
>
> * *
>
> *On R2*
>
>
>
> *R2#show ip route eigrp | inc ex*
>
>
>
> *D EX 2.2.2.0* [170/2561024256] via 10.1.12.1, 00:03:16, Serial0/0.21
>
>
>
> *On R3*
>
> * *
>
> *R3#show ip route eigrp | inc ex*
>
>
>
> *D EX 3.3.3.0* [170/2561024256] via 10.1.13.1, 00:03:43, Serial0/0.31
>
>
>
>
>
>
>
> *Task 7*
>
>
>
> Erase the startup configuration and reload the routers before proceeding
> to the next lab.
>
>
> I hope this helped.
>
> On Wed, Jul 11, 2012 at 2:34 PM, Tony Singh <mothafungla_at_gmail.com> wrote:
>
>>
>> ok got this feature working with....
>>
>> topology (r3 & r4 stubs) r3 having neighbourships with r1 & r3
>> r1 ---> r3 ---> r4
>>
>> on r3 learnt 1.1.1.1 from r1 then created a leak map referencing
>> access-list to permit the leak of 1.1.1.1 which was duly learned on r4
>> after this.
>>
>> used in situations where we have 2 distribution devices on remote sites &
>> for 2nd router to route around a failed link?
>>
>> correct me please....
>>
>>
>>
>> On 11 July 2012 09:45, Tony Singh <mothafungla_at_gmail.com> wrote:
>>
>>> Narbik
>>>
>>> That would be great please. I haven't fully had a chance to test various
>>> options or go through doc cd before posting this (shooting from the hip)
>>>
>>>
>>> --
>>> BR
>>>
>>> Sent from my iPhone on 3
>>>
>>> On 11 Jul 2012, at 07:36, Narbik Kocharians <narbikk_at_gmail.com> wrote:
>>>
>>> Do you guys want a lab on that? Would that help?
>>>
>>> On Tue, Jul 10, 2012 at 10:24 PM, Tony Singh
<mothafungla_at_gmail.com>wrote:
>>>
>>>> Thanks Leigh, could not find a config guide under 12.4 mainline will
>>>> check it out, prior under a non stub router got it working perfect after
>>>> interface summary.
>>>>
>>>> --
>>>> BR
>>>>
>>>> Sent from my iPhone on 3
>>>>
>>>> On 11 Jul 2012, at 02:05, "Leigh Finch" <leigh_at_leighfinch.net> wrote:
>>>>
>>>> > Hi Tony,
>>>> > As far as I can tell from the DOC-CD and my own testing, the leak-map
>>>> only
>>>> > applies to routes learned via EIGRP. As soon as you apply a leak-map
>>>> to an
>>>> > EIGRP stub you need to explicitly allow connected, static,
>>>> redistributed
>>>> > routes if you want those.
>>>> >
>>>> > I think you are looking for something more like.
>>>> >
>>>> > eigrp 500
>>>> > redistribute connected route-map LEAK metric 1 1 1 1 1
>>>> > network 70.1.1.0 0.0.0.3
>>>> > no auto-summary
>>>> > eigrp stub redistributed
>>>> >
>>>> > leigh
>>>> >
>>>> >> Any secret to using these maps on a stub area to leak two routes out?
>>>> >>
>>>> >> Here's my config..
>>>> >>
>>>> >> R1>R2 10mbps fe 70.1.1.0/30
>>>> >>
>>>> >>
>>>> >> R2
>>>> >>
>>>> >> Loopbacks
>>>> >> 80.1.2.1
>>>> >> 80.1.3.1
>>>> >>
>>>> >> access-list 7 permit 80.1.0.0 0.0.3.255
>>>> >> route-map LEAK
>>>> >> match ip address 7
>>>> >>
>>>> >> eigrp 500
>>>> >> network 70.1.1.0 0.0.0.3
>>>> >> no auto-summary
>>>> >> eigrp stub leak-map LEAK
>>>> >>
>>>> >> I'm not seeing the routes on R1- go on point it out..
>>>> >>
>>>> >> --
>>>> >> BR
>>>> >>
>>>> >> Tony
>>>> >>
>>>> >> Sent from my iPad
>>>> >>
>>>> >>
>>>> >> Blogs and organic groups at http://www.ccie.net
>>>> >>
>>>> >>
>>>> _______________________________________________________________________
>>>> >> Subscription information may be found at:
>>>> >> http://www.groupstudy.com/list/CCIELab.html
>>>>
>>>>
>>>> Blogs and organic groups at http://www.ccie.net
>>>>
>>>> _______________________________________________________________________
>>>> Subscription information may be found at:
>>>> http://www.groupstudy.com/list/CCIELab.html
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>> --
>>> *Narbik Kocharians
>>> *CCSI#30832, CCIE# 12410 (R&S, SP, Security)
>>> *www.MicronicsTraining.com* <http://www.micronicstraining.com/>
>>> Sr. Technical Instructor
>>> YES! We take Cisco Learning Credits!
>>> A Cisco Learning Partner
>>>
>>>
>>
>
>
> --
> *Narbik Kocharians
> *CCSI#30832, CCIE# 12410 (R&S, SP, Security)
> *www.MicronicsTraining.com* <http://www.micronicstraining.com/>
> Sr. Technical Instructor
> YES! We take Cisco Learning Credits!
> A Cisco Learning Partner

Blogs and organic groups at http://www.ccie.net
Received on Thu Jul 12 2012 - 07:12:12 ART