From: Johnny Dedon (johnny.dedon@xxxxxxxxxx)
Date: Tue Apr 17 2001 - 18:53:17 GMT-3
John,
I assume that your access-list 1 only permits 22.22.22.22.
You don't need the group-list 2 option unless you only want it to be the RP
for the restricted list of multicast addresses inlcuded in the ACL.
I am not sure if order of operations has any effect here.
ie, is your announce statement before your filter statement.
I am also not sure how R3 will handle this filter. I would assume that it
would not care that it is a local address and still apply the filter.
HTH
Johnny
----- Original Message -----
From: "Elias, John, NLSOP" <johnelias@att.com>
To: <ccielab@groupstudy.com>
Sent: Tuesday, April 17, 2001 4:39 PM
Subject: IP Multicast filtering
> Hi Guys,
> I am new in the group and some quick info on the filtering process
> of the candidates using a dynamic RPs. I configure r2 (loopback ip
address
> 22.22.22.22) and r3 (loopback ip address 33.33.33.33) as poosible RP
> candidates with the 'ip pim send-rp-announce loopback 0 scope 16 ' also
> configured r1, r2 and r3 with as Map Agents (for the RP election purposes)
> with the 'ip pim send-rp-discovery scope 16' command. The election works
> fine and r3 becomes the RP because he has the higest loopback address, but
> when I use the 'ip pim rp-announce-filter rp-list 1 group-list 2', trying
to
> filter out r3 from becoming the RP, r3 still becomes RP anyway. Was
> wondering if anyone any suggestions.
>
>
> (s0) r1(s1)
> / \
> / \
> (s0) r2-----------r3 (s0)
>
>
>
> R1
> !
> ip multicast-routing
> ip dvmrp route-limit 2000
> !
> interface loopback 0
> ip address 111.111.111.111 255.255.255.0
> !
> interface ether 0/0
> ip address 1.1.1.1 255.255.255.0
> ip igmp join-group 224.1.1.1
> ip pim sparse-dense-mode
> !
> interface ser0
> ip address 10.10.10.1 255.255.255.0
> ip pim sparse-dense-mode
> !
> interface ser1
> ip address 11.11.11.1 255.255.255.0
> ip pim sparse-dense-mode
> !
> ip pim send-rp-discovery scope 16
> ip pim rp-announce-filter rp-list 1 group-list 2
> !
> access-list 1 deny host 33.33.33.33
> access-list 1 permit host 22.22.22.22
> access-list 2 deny 225.1.1.1
> access-list 2 permit 226.1.1.1
> access-list 2 permit 224.1.1.1
> access-list 2 permit 229.1.1.1
> !
> end
>
>
>
> R2
> !
> ip multicast-routing
> ip dvmrp route-limit 2000
> !
> interface loopback 0
> ip address 22.22.22.22 255.255.255.0
> !
> interface ether 0/0
> ip address 2.2.2.2 255.255.255.0
> ip igmp join-group 224.1.1.1
> ip igmp join-group 225.1.1.1
> ip pim sparse-dense-mode
> !
> interface ser0
> ip address 10.10.10.2 255.255.255.0
> ip pim sparse-dense-mode
> !
> interface ser1
> ip address 13.13.13.2 255.255.255.0
> ip pim sparse-dense-mode
> !
> ip pim send-rp-announce loopback 0 scope 16
> ip pim send-rp-discovery scope 16
> ip pim rp-announce-filter rp-list 1 group-list 2
> !
> access-list 1 deny host 33.33.33.33
> access-list 1 permit host 22.22.22.22
> access-list 2 deny 225.1.1.1
> access-list 2 permit 226.1.1.1
> access-list 2 permit 224.1.1.1
> access-list 2 permit 229.1.1.1
> !
> end
>
>
>
>
> R3
> !
> ip multicast-routing
> ip dvmrp route-limit 2000
> !
> interface loopback 0
> ip address 33.33.33.33 255.255.255.0
> !
> interface ether 0/0
> ip address 3.3.3.3 255.255.255.0
> ip igmp join-group 226.1.1.1
> ip pim sparse-dense-mode
> !
> interface ser0
> ip address 11.11.11.3 255.255.255.0
> ip pim sparse-dense-mode
> !
> interface ser1
> ip address 13.13.13.3 255.255.255.0
> ip pim sparse-dense-mode
> !
> ip pim send-rp-announce loopback 0 scope 16
> ip pim send-rp-discovery scope 16
> ip pim rp-announce-filter rp-list 1 group-list 2
> !
> access-list 1 deny host 33.33.33.33
> access-list 1 permit host 22.22.22.22
> access-list 2 deny 225.1.1.1
> access-list 2 permit 226.1.1.1
> access-list 2 permit 224.1.1.1
> access-list 2 permit 229.1.1.1
> !
> end
>
> John
> **Please read:http://www.groupstudy.com/list/posting.html
**Please read:http://www.groupstudy.com/list/posting.html
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:29:48 GMT-3