From: Brian McGahan (bmcgahan@internetworkexpert.com)
Date: Fri Jul 29 2005 - 12:56:54 GMT-3
Andy,
I see your logic but you are overcomplicating the issue. Yes
"permit 224.0.0.0 14.255.255.255" is technically more specific, but how
can the RP announce itself for groups not in the multicast address
range? In the CCIE lab exam the simplest answer is always the best
answer.
HTH,
Brian McGahan, CCIE #8593
bmcgahan@internetworkexpert.com
Internetwork Expert, Inc.
http://www.InternetworkExpert.com
Toll Free: 877-224-8987 x 705
Outside US: 775-826-4344 x 705
24/7 Support: http://forum.internetworkexpert.com
Live Chat: http://www.internetworkexpert.com/chat/
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf
Of
> Andy
> Sent: Friday, July 29, 2005 4:23 AM
> To: Cisco certification
> Subject: Multicast / the multicast group (IEWB lab8)
>
> Hi,
> i'm doing task 7.3 -7.6 lab 8 in IEWB.
> This states that R1 should anounce its loopback as a candidate RP via
> Auto-rp
> and R3 should map all multicast groups with event numbered first octet
to
> R1.
>
> Ok, the question is clear enough and this is my answer:
>
> R1:
> !
> interface Loopback0
> ip pim sparse-dense-mode
> !
> ip pim send-rp-announce Loopback0 scope 16
>
>
> R3:
> interface Loopback0
> ip pim sparse-dense-mode
> !
> ip pim send-rp-discovery Loopback0 scope 16
> !
> ip pim rp-announce-filter rp-list R1_RP group-list R1_GROUPS
> !
> ip access-list standard R1_GROUPS
> permit 224.0.0.0 14.255.255.255
> !
> ip access-list standard R1_RP
> permit 150.1.1.1
> !
>
>
> And when looking at solution guide, i see this:
>
>
>
> R3
>
> !
>
> interface Loopback0
> ip pim sparse-dense-mode
> !
> ip pim send-rp-announce Loopback0 scope 16 group-list 1 interval 5
> !
> access-list 1 permit 0.0.0.0 254.255.255.255
>
>
>
> R3:
> interface Loopback0
> ip pim sparse-dense-mode
> !
> ip pim send-rp-discovery Loopback0 scope 16
> !
> ip pim rp-announce-filter rp-list R1_RP group-list R1_GROUPS
> !
> ip access-list standard R1_GROUPS
> permit 0.0.0.0 254.255.255.255
> ip access-list standard R1_RP
> permit 150.1.1.1
>
>
> Ok, two things i want to clarify here are:
>
> 1- The access list that match multicast group.
>
> permit 0.0.0.0 254.255.255.255 from SG
> vs
>
> permit 224.0.0.0 14.255.255.255 is mine.
>
>
>
> I don't have a rack to test at the moment but i believe the two of
them
> will
> work fine. However, which one do you think will be prefered ? The acl
that
> match exactly the multicast score is "better", isn't it ?
>
>
>
> 2- Do we have to apply R1_Group to both RP in send-rp-annouce and MA
in
> rp-annouce-filter command ? or it's only needed to configure
rp-annouce-
> filter
> on the mapping agent ? And there's no word about changing annouce
> interval,
> why put interval 5 in there ?
>
>
>
> Comments are welcome.
>
>
>
> Andy
>
>
This archive was generated by hypermail 2.1.4 : Sun Sep 04 2005 - 17:00:32 GMT-3