This is a little different than you set up but here is my version of Multicast stub routing in your situation. A few commands different.
no ip address
ip igmp version 3
interface Vlan200 (outgoing to WAN)
ip address 172.30.1.200 255.255.255.0
ip pim dense
interface Vlan300 (LAN)
ip pim dense
ip address 172.30.10.200 255.255.255.0
ip igmp helper-address 172.30.1.240
On the upstream router that should be the PIM neighbor (across you WAN) you would do the following
Dont know your interfaces for the other device but for example
int fa0/0 (WAN)
ip pim spase-mode
ip pim neighbor-filter 10
access-list 10 deny 172.30.1.200
access-list 10 permit any
You create the neighbor filter because you do not want to form a PIM neighborship between the device (This way multicast packets are no set out a non PIM enabled interface). The upstream router will build its multicast distribution tree on behalf of the stub router (in your case the switch) based off the IGMP proxy function.
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...