OK, seems like I jumped in a little prematurely here. The ACL is fine and the priority doesn¹t need swapping in your solution below, Carlos (but your question has a typo). Anyhow, the Solution Guide is being updated correctly and will be in the members section on our next update cycle.
Cheers, Jared Scrivener CCIE3 #16983 (R&S, Security, SP), CISSP Sr. Technical Instructor - IPexpert, Inc. URL: http://www.IPexpert.com Telephone: +1.810.326.1444 Fax: +1.810.454.0130 Mailto: [email protected] From: Jared Scrivener <[email protected]> Date: Fri, 10 Jul 2009 11:12:48 -0400 To: Carlos Valero <[email protected]>, <[email protected]>, Joe Astorino <[email protected]> Subject: Re: [OSL | CCIE_RS] Vol 3, Lab 2, Task 5.1 (Multicast) The ACL is fine. The priority value should be swapped so that it uses 10 on R2 and 20 on R7. This is just another lesson in how CCIE¹s can make typo¹s. I¹m fixing it up in our Proctor Guide now. Cheers, Jared Scrivener CCIE3 #16983 (R&S, Security, SP), CISSP Sr. Technical Instructor - IPexpert, Inc. URL: http://www.IPexpert.com Telephone: +1.810.326.1444 Fax: +1.810.454.0130 Mailto: [email protected] From: Carlos Valero <[email protected]> Date: Thu, 9 Jul 2009 17:19:29 -0700 (PDT) To: <[email protected]>, Joe Astorino <[email protected]> Subject: Re: [OSL | CCIE_RS] Vol 3, Lab 2, Task 5.1 (Multicast) Made a little mistake on the requirements section. The second part should be like this: Configure R7 to announce candidacy as an RP for Groups: - First octet = 225 or 227 - Second octet less than 128 - Priority = 20 Originally I wrote Priority = 10 But the solution it is being configured with Priority = 10 - ip pim rp-candidate l1 group-list 51 prio 10 That's exactly the source of my confusion. Why is R7 configuration based on R2's requirements and vice-versa? --- On Thu, 7/9/09, Carlos Valero <[email protected]> wrote: > > From: Carlos Valero <[email protected]> > Subject: Re: [OSL | CCIE_RS] Vol 3, Lab 2, Task 5.1 (Multicast) > To: [email protected], "Joe Astorino" <[email protected]> > Date: Thursday, July 9, 2009, 7:26 PM > > Hello, > > I think I need some help with this task. > It seems to be quite simple, but to me the solution seems to be backwards and > I'm very confused and stock! > > Requirements: > > Configure R2 to announce candidacy as an RP for Groups: > - First octet = 225 or 227 > - Priority = 10 > > Configure R7 to announce candidacy as an RP for Groups: > - First octet = 225 or 227 > - Second octet less than 128 > - Priority = 10 > > Solution: > > R2: > > access-list 51 permit 225.0.0.0 0.255.255.255 > access-list 51 permit 227.0.0.0 0.255.255.255 > > ip pim rp-candidate l1 group-list 51 prio 20 > ip pim bsr-candidate l1 > > R7: > > access-list 51 permit 225.0.0.0 0.127.255.255 > access-list 51 permit 227.0.0.0 0.127.255.255 > access-list 51 permit 225.0.0.0 0.127.255.255 > access-list 51 permit 227.0.0.0 0.127.255.255 > > ip pim rp-candidate l1 group-list 51 prio 10 > ip pim bsr-candidate l1 > > This seems to be backwards to me! > > That is, the requirements state that R2 should have a Priority = 10 and > R7 should have a Priority = 20 > > But it is configured backwards! R2 = 20 and R7 = 10! > > Needless to say, the ACL also seem to be backwards to me! > > Obviously, there is something that I'm missing here. > And frankly I don't know what it is. > > I hope somebody can help. > > Did I mention that Multicast is my less favorite topic? > Actually I should say that I almost hate it :-( > > > > > > > > > --- On Wed, 7/8/09, Joe Astorino <[email protected]> wrote: >> >> > > > > -----Inline Attachment Follows----- > > _______________________________________________ > For more information regarding industry leading CCIE Lab training, please > visit www.ipexpert.com _______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
_______________________________________________ For more information regarding industry leading CCIE Lab training, please visit www.ipexpert.com
