From: Geert Nijs (Geert.Nijs@simac.be)
Date: Fri Oct 05 2007 - 13:10:40 ART
Hello group,
In a PIM Sparse mode environment, how can i prevent certain ip ranges from sending multicast and allowing specific other regions ?
I was thinking about the command: ip pim accept-registerl list <acl>
But when i configure this is a lab environment to DROP ALL register messages, the multicast still comes through. Can the multicast be dropped by dropping the register messages ?
I see the RP point sending a REGISTER-STOP message, but some time later suddenly a JOIN appears and the multicast starts working ?????
Could this be a bug ? I am using version 12.2(37)SE1 on C3750 switches.
Config:
ALL INTERFACES ARE IN SPARSE-MODE !
topology: SERVER_SWITCH -------------- DISTRI_SWITCH --------------- ACCESS_SWITCH
distri_switch
ip pim rp-address 223.255.255.254 50 <<---- sink hole RP
no ip pim dm-fallback <<----------------------------- no dense mode fallback
ip pim spt-threshold infinity <<---------------------- no spt tree, only shared tree
ip pim autorp listener <<<-- use auto-rp to distribute RP information
ip pim send-rp-announce Loopback100 scope 32 group-list SITE-RP <-- send some specific ranges as RP with auto-rp (RP=1.1.1.1)
ip pim send-rp-discovery scope 15
ip pim accept-register list MC-DENYALL <<----------- DROP all register messages !!!
ip access-list extended MC-DENYALL
deny ip any any
ip access-list standard SITE-RP <<----- advertised groups
permit 239.192.0.0 0.0.255.255
permit 239.255.0.0 0.0.255.255
permit 239.1.0.0 0.0.255.255
SERVERFARM#
3w3d: PIM(0): Check RP 1.1.1.1 into the (*, 239.255.10.10) entry
3w3d: PIM(0): Send v2 Register to 1.1.1.1 for 10.102.68.1, group 239.255.10.10
3w3d: PIM(0): Received v2 Register-Stop on GigabitEthernet1/0/2 from 1.1.1.1
3w3d: PIM(0): for source 10.102.68.1, group 239.255.10.10
3w3d: PIM(0): Clear Registering flag to 1.1.1.1 for (10.102.68.1/32, 239.255.10.10)
3w3d: PIM(0): Building Graft message for 224.0.1.40, GigabitEthernet1/0/2: no entries
3w3d: PIM(0): Check RP 1.1.1.1 into the (*, 239.255.255.250) entry
3w3d: PIM(0): Building Triggered (*,G) Join / (S,G,RP-bit) Prune message for 239.255.255.250
3w3d: PIM(0): Insert (*,239.255.255.250) join in nbr 10.96.25.129's queue
3w3d: PIM(0): Building Join/Prune packet for nbr 10.96.25.129
3w3d: PIM(0): Adding v2 (1.1.1.1/32, 239.255.255.250), WC-bit, RPT-bit, S-bit Join
3w3d: PIM(0): Send v2 join/prune to 10.96.25.129 (GigabitEthernet1/0/2)
3w3d: PIM(0): Received v2 Join/Prune on GigabitEthernet1/0/2 from 10.96.25.129, to us
3w3d: PIM(0): Join-list: (10.102.68.1/32, 239.255.10.10), S-bit set
3w3d: PIM(0): Add GigabitEthernet1/0/2/10.96.25.129 to (10.102.68.1, 239.255.10.10), Forward state, by PIM SG Join
3w3d: PIM(0): Received RP-Reachable on GigabitEthernet1/0/2 from 1.1.1.1
3w3d: PIM(0): Received RP-Reachable on GigabitEthernet1/0/2 from 1.1.1.1
3w3d: for group 239.255.255.250
3w3d: PIM(0): Update RP expiration timer (270 sec) for 239.255.255.250
3w3d: PIM(0): Building Periodic (*,G) Join / (S,G,RP-bit) Prune message for 239.255.10.10
regards,
Geert
disclaimer : http://webservices.simac.be/disclaimer.htm
This archive was generated by hypermail 2.1.4 : Fri Nov 16 2007 - 13:11:12 ART