Hi, I tried your route-map and it worked. But I wonder why mine does not work, it is the same logic behind, or?
I had matches on the ACL! -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of [email protected] Sent: Tuesday, May 18, 2010 4:24 PM To: [email protected] Subject: CCIE_SP Digest, Vol 38, Issue 13 Send CCIE_SP mailing list submissions to [email protected] To subscribe or unsubscribe via the World Wide Web, visit http://onlinestudylist.com/mailman/listinfo/ccie_sp or, via email, send a message with subject or body 'help' to [email protected] You can reach the person managing the list at [email protected] When replying, please edit your Subject line so it is more specific than "Re: Contents of CCIE_SP digest..." Today's Topics: 1. Vol. 1 Task 6.7 & 6.8 (Smail) 2. Re: Vol. 1 Task 6.7 & 6.8 (Tyson Scott) ---------------------------------------------------------------------- Message: 1 Date: Mon, 17 May 2010 21:02:51 +0200 From: "Smail" <[email protected]> Subject: [OSL | CCIE_SP] Vol. 1 Task 6.7 & 6.8 To: <[email protected]> Message-ID: <[email protected]> Content-Type: text/plain; charset="us-ascii" Hi, I just finished Lab 6 (ISIS) and found a few differences in the DSG and I would like to hear your opinions. Task 6.7 Create two Loopback interfaces on R9. Interface Loopback1 (10.6.0.6/24) and Interface Loopback2 (10.6.1.6/24). Summarize these two IP subnets into one and advertise it through IS-IS level 1 and level 2 routers. Make sure that the advertisements of the Loopbacks do not waste CPU cycles by trying to form unnecessary adjacencies. After configuring the loopbacks on R9, they need to be redistributed into ISIS before a summary will be advertised. For the summary, the first two octets are the same, and the third differs only on the last bit, so a 23 bit summary will cover both networks. When redistributing into a routing protocol, creating a route-map allows you to be granular regarding which networks you want to bring to that protocol. R9(config)#int loop1 R9(config-if)#ip address 10.6.0.6 255.255.255.0 R9(config-if)#int loop2 R9(config-if)#ip address 10.6.1.6 255.255.255.0 R9(config)#access-list 77 permit 10.6.0.0 0.0.1.0 R9(config)#route-map CONN R9(config-route-map)#match ip address 77 R9(config-route-map)#router isis R9(config-router)#redist conn route-map CONN level-1-2 R9(config-router)#summary-address 10.6.0.0 255.255.254.0 level-1-2 I have not used the route-map and still got the summary address in the routing table of other routers This is all what I did: summary-address 10.6.0.0 255.255.254.0 level-1-2 Task 6.8 Create 2 static routes on R9: 192.6.6.0 255.255.255.0 to null0 and 192.7.7.0 255.255.255.0 to null0. Redistribute both static routes into the IS-IS process, but do not advertise the 192.7.7.0/24 subnet to any other routers. Here, we have 2 static routes to redistribute into ISIS on R9. Here, we need to redistribute both routes into ISIS, but only advertise one to the other routers. By setting the metric for the second route to the maximum value, it will not appear on the other routers. R9(config)#ip route 192.6.6.0 255.255.255.0 null0 R9(config)#ip route 192.7.7.0 255.255.255.0 null0 R9(config)#access-list 86 permit 192.6.6.0 R9(config)#access-list 87 permit 192.7.7.0 R9(config)#route-map 192s permit 10 R9(config-route-map)#match ip address 86 R9(config-route-map)#route-map 192s permit 20 R9(config-route-map)#match ip address 87 R9(config-route-map)#set metric 4294967295 R9(config)#router isis R9(config-router)#redist static ip route-map 192s I tried with a route-map too but I did not worked (no idea why), this was my route-map: standard IP access list REDIS 10 permit 192.7.7.0, wildcard bits 0.0.0.255 (6 matches) 30 deny any (6 matches) route-map REDIS deny 10 match ip address REDIS router isis redistribute static ip route-map REDIS --------- Then I tried this and it worked but I think that this solution is not scalable: router isis redistribute maximum-prefix 1 redistribute static ip The other routers have only the 192.6.6.0 subnet in their routing table (cleared ISIS process, too) I get this message but it is not a problem: IPRT-4-REDIST_MAX_PFX: Redistribution prefix limit has been reached "isis L2" - 1 prefixes -------------- next part -------------- An HTML attachment was scrubbed... URL: http://onlinestudylist.com/pipermail/ccie_sp/attachments/20100517/d44558e0/a ttachment-0001.htm ------------------------------ Message: 2 Date: Tue, 18 May 2010 10:23:38 -0400 From: "Tyson Scott" <[email protected]> Subject: Re: [OSL | CCIE_SP] Vol. 1 Task 6.7 & 6.8 To: "'Smail'" <[email protected]>, <[email protected]> Message-ID: <00a301caf695$b63902b0$22ab08...@com> Content-Type: text/plain; charset="us-ascii" The first one the route-map is just to make sure only the two networks get redistributed. If you had additional connected networks that shouldn't be in IS-IS they would also be redistributed without the route-map For the second one change your ACL to ip access-list standard REDIS-DENY permit 192.7.7.0 0.0.0.255 ip access-list standard REDIS-PERMIT permit 192.6.6.0 0.0.0.255 route-map REDIS deny 10 match ip address REDIS-DENY route-map REDIS permit 20 match ip address REDIS-PERMIT Regards, Tyson Scott - CCIE #13513 R&S, Security, and SP Technical Instructor - IPexpert, Inc. Mailto: <mailto:[email protected]> [email protected] Telephone: +1.810.326.1444, ext. 208 Live Assistance, Please visit: <http://www.ipexpert.com/chat> www.ipexpert.com/chat eFax: +1.810.454.0130 IPexpert is a premier provider of Self-Study Workbooks, Video on Demand, Audio Tools, Online Hardware Rental and Classroom Training for the Cisco CCIE (R&S, Voice, Security & Service Provider) certification(s) with training locations throughout the United States, Europe, South Asia and Australia. Be sure to visit our online communities at <http://www.ipexpert.com/communities> www.ipexpert.com/communities and our public website at <http://www.ipexpert.com/> www.ipexpert.com From: [email protected] [mailto:[email protected]] On Behalf Of Smail Sent: Monday, May 17, 2010 3:03 PM To: [email protected] Subject: [OSL | CCIE_SP] Vol. 1 Task 6.7 & 6.8 Hi, I just finished Lab 6 (ISIS) and found a few differences in the DSG and I would like to hear your opinions. Task 6.7 Create two Loopback interfaces on R9. Interface Loopback1 (10.6.0.6/24) and Interface Loopback2 (10.6.1.6/24). Summarize these two IP subnets into one and advertise it through IS-IS level 1 and level 2 routers. Make sure that the advertisements of the Loopbacks do not waste CPU cycles by trying to form unnecessary adjacencies. After configuring the loopbacks on R9, they need to be redistributed into ISIS before a summary will be advertised. For the summary, the first two octets are the same, and the third differs only on the last bit, so a 23 bit summary will cover both networks. When redistributing into a routing protocol, creating a route-map allows you to be granular regarding which networks you want to bring to that protocol. R9(config)#int loop1 R9(config-if)#ip address 10.6.0.6 255.255.255.0 R9(config-if)#int loop2 R9(config-if)#ip address 10.6.1.6 255.255.255.0 R9(config)#access-list 77 permit 10.6.0.0 0.0.1.0 R9(config)#route-map CONN R9(config-route-map)#match ip address 77 R9(config-route-map)#router isis R9(config-router)#redist conn route-map CONN level-1-2 R9(config-router)#summary-address 10.6.0.0 255.255.254.0 level-1-2 I have not used the route-map and still got the summary address in the routing table of other routers This is all what I did: summary-address 10.6.0.0 255.255.254.0 level-1-2 Task 6.8 Create 2 static routes on R9: 192.6.6.0 255.255.255.0 to null0 and 192.7.7.0 255.255.255.0 to null0. Redistribute both static routes into the IS-IS process, but do not advertise the 192.7.7.0/24 subnet to any other routers. Here, we have 2 static routes to redistribute into ISIS on R9. Here, we need to redistribute both routes into ISIS, but only advertise one to the other routers. By setting the metric for the second route to the maximum value, it will not appear on the other routers. R9(config)#ip route 192.6.6.0 255.255.255.0 null0 R9(config)#ip route 192.7.7.0 255.255.255.0 null0 R9(config)#access-list 86 permit 192.6.6.0 R9(config)#access-list 87 permit 192.7.7.0 R9(config)#route-map 192s permit 10 R9(config-route-map)#match ip address 86 R9(config-route-map)#route-map 192s permit 20 R9(config-route-map)#match ip address 87 R9(config-route-map)#set metric 4294967295 R9(config)#router isis R9(config-router)#redist static ip route-map 192s I tried with a route-map too but I did not worked (no idea why), this was my route-map: standard IP access list REDIS 10 permit 192.7.7.0, wildcard bits 0.0.0.255 (6 matches) 30 deny any (6 matches) route-map REDIS deny 10 match ip address REDIS router isis redistribute static ip route-map REDIS --------- Then I tried this and it worked but I think that this solution is not scalable: router isis redistribute maximum-prefix 1 redistribute static ip The other routers have only the 192.6.6.0 subnet in their routing table (cleared ISIS process, too) I get this message but it is not a problem: IPRT-4-REDIST_MAX_PFX: Redistribution prefix limit has been reached "isis L2" - 1 prefixes -------------- next part -------------- An HTML attachment was scrubbed... URL: http://onlinestudylist.com/pipermail/ccie_sp/attachments/20100518/6cea4b03/a ttachment.htm End of CCIE_SP Digest, Vol 38, Issue 13 *************************************** _______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
