From: Mike Haddad (mike.haddad@hotmail.com)
Date: Sun Mar 30 2008 - 04:53:27 ART
The requirement is to exlude 225, 224 and 239.
Date: Sun, 30 Mar 2008 10:46:51 +0300From: ananth.sarma@gmail.comTo:
thekonqueror@gmail.comSubject: Re: Multicast GroupingCC:
mike.haddad@hotmail.com; ccielab@groupstudy.com
Mike / Rahul,
I think the requirement is to exclude only 227.0.0.1 and 237.0.0.1.
I may be wrong. Let me know.
Regards,
Ananth
On Sun, Mar 30, 2008 at 10:01 AM, theKonqueror <thekonqueror@gmail.com>
wrote:
Grouping the access lists as 226.0.0.0 12.255.255.255 will also allowfollowing
groups:227.0.0.1229.0.0.1231.0.0.1233.0.0.1234.0.0.1235.0.0.1237.0.0.1If the
task says, configure rp for ONLY given groups, then the 1 line aclcannot be
used. I'd ask proctor for clarification on this.Thanks,RahulOn Sun, Mar 30,
2008 at 12:24 PM, Mike Haddad <mike.haddad@hotmail.com>wrote:
> Hello,>> I still don't understand why the below ACL can't be grouped:>
interface Loopback0> ip pim sparse-dense-mode> !> ip pim send-rp-announce
Loopback0 scope 16 group-list 50> !> access-list 50 permit 226.0.0.0
1.255.255.255> access-list 50 permit 228.0.0.0 3.255.255.255> access-list 50
permit 232.0.0.0 3.255.255.255> access-list 50 permit 236.0.0.0 1.255.255.255>
access-list 50 permit 238.0.0.0 0.255.255.255>>> Why can't we group them as:>
access-list 50 permit 226.0.0.0 12.255.255.255>> Thanks for the
clarification,>>
This archive was generated by hypermail 2.1.4 : Tue Apr 01 2008 - 07:53:54 ART