[c-nsp] ip multicast boundary and IGMP?

[Jeff Bacon]

According to the documentation:

* IP multicast boundaries filter data and control plane traffic
including IGMP, PIM, and AutoRP messages. PIM Register messages are sent
using unicast and will not be filtered.


However, I have multiple multicast boundaries set up on various SVIs and
PIs, and IGMP appears to work just fine - "show ip igmp group vlan X"
reports state, multicast comes and goes, etc etc. 

In addition, I am running EIGRP across a link which has a multicast
boundary configured, which is using multicast of course, and it works
just fine. 

It does however block PIM and AutoRP, which I have to explicitly permit
in order for it to work. 


Is this just a flaw in the documentation? A flaw in the SX train? Am I
missing something?

This is on cat6500/sup720s, 12.2.33SXH4. 

Thanks,
-bacon


General traffic:

interface Vlan103
 ip address 10.201.64.34 255.255.255.224
 ip access-group mcast-subnets-in in
 ip access-group ISE-mcast-subnet-out out
 ip pim neighbor-filter deny-any
 ip pim sparse-dense-mode
 ip multicast boundary ISE-mcast-B-groups
 load-interval 60
 hold-queue 80 out
Standard IP access list ISE-mcast-B-groups
    10 permit 233.104.73.64, wildcard bits 0.0.0.63 (576170 matches)
    20 permit 233.104.73.128, wildcard bits 0.0.0.63 (13419 matches)

interface Vlan300
 description --- VLAN 300 -> nj-vendorsw00 main
 ip address 10.201.192.146 255.255.255.252
 ip pim sparse-dense-mode
 ip multicast boundary from-mcast-nj
 load-interval 60
 hold-queue 2000 in
Standard IP access list from-mcast-nj
    10 permit 233.54.12.119
    20 permit 233.54.12.120 (59448 matches)
    30 permit 224.0.1.39 (62277 matches)
    40 permit 224.0.1.40 (80379 matches)
    50 permit 233.54.12.10
    60 permit 224.0.0.13
    70 permit 224.0.58.0, wildcard bits 0.0.0.255
    80 permit 233.75.215.168, wildcard bits 0.0.0.1
    90 permit 233.75.215.40, wildcard bits 0.0.0.1
    100 permit 224.0.5.220, wildcard bits 0.0.0.3
    110 permit 224.0.5.224, wildcard bits 0.0.0.3