From: John Galt Kupec (jkupec2@xxxxxxxxxx)
Date: Thu Nov 11 1999 - 11:57:12 GMT-3
This might be a problem that somebody in CCIE lab mode has or will
hit so I'll pose my question here:
I'm essentially copying the "multicast stub" examples in "Configuring IP
Multicast Routing" (CCO) and Parkhurst's Multicast book. I'm using
dense-mode PIM and IOS 11.3. Although "debug ip pim" shows that the
incoming PIM message is blocked by the access list, the neighbor
relationship is still eventually formed and the HELLO's are still
accepted by the core router. Is this a bug or am I missing something?
I'm assuming that the access list should prevent the neighbor
relationship and that "show ip pim neighbor" on the core router should
_not_ be showing the neighbor on Serial1. There are no devices on the
stub router's Ethernet interface. I didn't see any bugs relevant
to this on CCO.
core_router:
interface Serial1
ip address 192.168.12.1 255.255.255.0
ip pim neighbor-filter 1
ip pim dense-mode
clockrate 64000
access-list 1 deny 192.168.12.2
stub_router:
interface Ethernet0
ip address 192.168.2.2 255.255.255.0
ip pim dense-mode
ip igmp helper-address 192.168.12.1
!
interface Serial0
ip address 192.168.12.2 255.255.255.0
ip pim dense-mode
core(config)#int s 1
core(config-if)#no shut
core(config-if)#^Z
debug ip pim on core_router:
01:05:27: PIM: Send Router-Query on Serial1 (dual PIMv1v2)
01:05:30: PIM: PIM neighbor 192.168.12.2 explicitly denied on Serial1
core#sho ip pim neigh
PIM Neighbor Table
Neighbor Address Interface Uptime Expires Ver Mode
192.168.13.3 Serial0 00:42:26 00:01:22 v2
192.168.12.2 Serial1 00:00:07 00:01:37 v2
So, to my eye the neighbor relationship is still being formed.
Anybody with experience along these lines?
Thanks
John
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 08:21:55 GMT-3