Hey Bauke, 1) Make sure that on R1 you are redistributing the connected interface for 172.29.10.0/26 into OSPF. At that point, R2 SHOULD see 172.29.10.0/26 as an E2 OSPF route. Now, additionall on R2 are you advertising the 172.29.12.0 network with either a network statement in OSPF or the command "ip ospf <process ID> area <area#>" ??? You would need to be if you have your adjacency between R1/R2 up in OSPF. If that is the case, and everything is working properly, you should see the 172.29.12.0 network in your OSPF domain at a bare mimimum without doing anything else. Now, on R2 going into RIP -- Make sure you are redistributing OSPF into RIP as well as your 172.29.12.0 connected interface specifically. Let me know that you have done all these things and how it goes and we will take it from there. 2) I think that the deny here for the R2/R5 serial link is just a way of not putting the same connected interface into both RIP and OSPF...that way it saves some confusion later on. By denying that network you ensure it only gets redistributed into 1 protocol and not 2 seperate ones. As for the Fa1/0 interface, it kind of works the other way. It is already participating in OSPF and is a directly connected interface...so you redistribute that connected interface into RIP. The route will already be in the OSPF domain by nature of it being advertised. Since you also want it in RIP so R4 has visibility you need to redistribute. My personal experience with redistribution: Don't sweat the proctor guide when doing this. At first yes, it can and will make your brain hurt. But once you get the hang of it, I encourage you to do your own thing and just "get it to work" as specified. As long as you don't break any rules, and you have full reachability, you are all good! Don't worry about doing redistribution EXACTLY as the solution guide says. It is one of those areas where there are likely many different right ways to do it.
Regards, Joe Astorino CCIE #24347 (R&S) Sr. Support Engineer - IPexpert, Inc. URL: http://www.IPexpert.com <http://www.ipexpert.com/> _____ From: [email protected] [mailto:[email protected]] On Behalf Of Bauke Dzavhale Sent: Friday, May 22, 2009 1:28 PM To: CCIE OSL Subject: Re: [OSL | CCIE_RS] LAB 7, vol 2, Task 5-4 - Redistribution Team, Few things I would appreciate help on... 1- There is no way to have connectivity end-to-end from and to R4. I am sure the problem is on redistributing "connected" and "Ospf to Rip" on R2. Did exactly as recommened in the PG , page 258, 259 but no success. Even after redistribution, R4 does NOT see the subnet 172.29.12.0 and 172.29.10.0 (both in R1) although I can (strange enough to me ...), ping the Lo1 of R1 (192.168.1.1). 2- I am uncomfortable with the reason behing denying the subnet 172.29.25.0 when injecting OSPF routes into RIP...i have no idea why they do so. I suspect has to do with the fact that subnet belongs to the connectyed interface s0/2/0 on R2 and also runs OSPF...but I am not sure. F1/0 in R2 (172.29.12.0) is a "connected" subnet and it also runs OSPF but is not denied when injecting OSPF into RIP. Any thoughts ? Thanks Bauke _____ <http://ca.promos.yahoo.com/newmail/overview2/> All new Yahoo! Mail - Get a sneak peak at messages with a handy reading pane. No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.5.339 / Virus Database: 270.12.31/2116 - Release Date: 05/22/09 06:03:00
