Re: AutoRP filter-list

From: Derek Pocoroba (dpocoroba@gmail.com)
Date: Wed Aug 15 2007 - 19:59:43 ART


I dont think you can get this granular when it comes to filtering the
announcements with auto-rp. Basically the RP will announce itself for
224.0.0.0/4. I have seen other tasks asking to use the minimal amount of
lines needed on the ACL. In those cases though you they were usually
sequential groups. however in this case you cant use the ODD / EVEN ACL's.

-Derek
CCIE #18559

On 8/15/07, Joseph Brunner <joe@affirmedsystems.com> wrote:
>
> Are 150.1.1.1, and 150.1.2.2 known via the routing table on R3?
>
> Do all loopback interfaces have "ip pim sparse-mode" configured?
>
> Do a debug ip mpacket detail on R3, keep it running for a bit and post it.
>
> thanks
>
> Joe
>
>
> -----Original Message-----
> From: Prasad Shemrudkar (pshemrud) [mailto:pshemrud@cisco.com]
> Sent: Wednesday, August 15, 2007 6:19 PM
> To: Joseph Brunner; Cisco certification
> Subject: RE: AutoRP filter-list
>
> Hey Joseph,
>
> Sorry, my fault I should have given the whole picture at the first
> instance itself, but thought I was messing it up in some very basic ACL
> config, hence limited myself. Any case, below the full picture:
>
> Running sparse mode, with autorp-listner on all the 3 routers.
>
> R3:
>
> !
> ip pim autorp listener
> ip pim send-rp-discovery Loopback0 scope 32
> ip pim rp-announce-filter rp-list R1 group-list EVEN
> ip pim rp-announce-filter rp-list R2 group-list ODD
> !
> !
> ip access-list standard EVEN
> permit 0.0.0.0 254.255.255.255
> ip access-list standard ODD
> permit 1.0.0.0 254.255.255.255
> ip access-list standard R1
> permit 150.1.1.1
> ip access-list standard R2
> permit 150.1.2.2
> !
> !
>
> R2:
>
> !
> ip pim autorp listener
> ip pim send-rp-announce Loopback0 scope 16 group-list ODD
> !
> !
> ip access-list standard ODD
> permit 1.0.0.0 254.255.255.255
> !
>
> R1:
>
> !
> ip pim autorp listener
> ip pim send-rp-announce Loopback0 scope 16 group-list EVEN
> !
> !
> ip access-list standard EVEN
> permit 0.0.0.0 254.255.255.255
> !
> !
>
> Below a few debug and show commands output:
>
> Rack1R3(config-std-nacl)#
> 05:14:09: Auto-RP(0): Received RP-announce, from 150.1.1.1, RP_cnt 1, ht
> 181
> 05:14:09: Auto-RP(0): Received RP-announce, from 150.1.1.1, RP_cnt 1, ht
> 181
> Rack1R3(config-std-nacl)#
> 05:14:23: Auto-RP(0): Build RP-Discovery packet
> Rack1R3(config-std-nacl)#
> 05:14:39: Auto-RP(0): Received RP-announce, from 150.1.2.2, RP_cnt 1, ht
> 181
> 05:14:39: Auto-RP(0): Filtered 224.0.0.0/4 for RP 150.1.2.2
> 05:14:39: Auto-RP(0): Received RP-announce, from 150.1.2.2, RP_cnt 1, ht
> 181
> 05:14:39: Auto-RP(0): Filtered 224.0.0.0/4 for RP 150.1.2.2
>
> Rack1R3(config-std-nacl)#do sh ip pim rp ma
> PIM Group-to-RP Mappings
> This system is an RP-mapping agent (Loopback0)
>
> Rack1R3(config-std-nacl)#
>
> TIA,
> Prasad
> -----Original Message-----
> From: Joseph Brunner [mailto:joe@affirmedsystems.com]
> Sent: Thursday, August 16, 2007 3:37 AM
> To: Prasad Shemrudkar (pshemrud); 'Cisco certification'
> Subject: RE: AutoRP filter-list
>
> Please post the rest of the config... we'll hammer it out and see what's
> wrong... those are first octet odd/evens...
>
> Are you running sparse mode, dense mode, or sparse-dense mode on the
> interfaces?
>
> If you are running sparse-mode did you remember to add
> "ip pim auto-rp listener"?
>
> How are you seeing failure?
>
> Did you do "show ip pim rp" from the MA?
>
> -Joe
>
> -----Original Message-----
> From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
> Prasad Shemrudkar (pshemrud)
> Sent: Wednesday, August 15, 2007 5:39 PM
> To: Cisco certification
> Subject: AutoRP filter-list
>
> Hi,
>
> R1, R2 and R3 are running auto-rp. R3 is the MA with R1 and R2 being the
> candidate RPs. Task requires you to configure R3 to map first octet odd
> to R2 and first octet even to R1.
>
> I am using the following group-list on all 3:
>
> ip access-list standard EVEN
> permit 0.0.0.0 254.255.255.255
> ip access-list standard ODD
> permit 1.0.0.0 254.255.255.255
>
> but the MA fails to map the discovery packets. I do not understand
> what's wrong with the ACL?
>
> Prasad
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html
>
> _______________________________________________________________________
> Subscription information may be found at:
> http://www.groupstudy.com/list/CCIELab.html



This archive was generated by hypermail 2.1.4 : Sat Sep 01 2007 - 11:32:11 ART