Thanks for the link and will go through it. MCAST is already enabled on one side of the link. Basically I'd like to know if the order side can be configured just query some groups. My understanding is that only requested groups will send across the link. Is that right?

The core switches have the following config (see attached).

We want the other side just be able to access:

239.255.46.11

239.255.46.12

239.255.46.13

239.255.46.14

239.255.46.15

And Multicast/unicast for 239.255.46.1

my intent was to only add ip pim sparse-dense-mode on the the serial interfaces and the VLAN where the servers belong

I don't recommend enabling dense on WAN links as it has a flooding behavior. Just enable ip pim sparse mode and configure a RP.

The RP will have the group-list that will contain the multicast groups that it should announce to other multicast routers.

Read the link I posted and everything will make sense. If you have additional questions, feel free to post back.

HTH,

__

Edison.

Ok, below is what I am planning to configure

core switches running auto-RP (RP address 10.33.63.1)<-->Remote switche <--->switchSite1

I was going to configure switchsite1 as below

ip multicast-routing

interface G0/1 (connecting to Remote switch at headquarter)

ip pim sparse-mode

ip pim rp-address 10.33.63.1 access-list 99 override

access-list 99 permit 239.255.46.1

access-list 99 permit 239.255.46.11

access-list 99 permit 239.255.46.12

access-list 99 permit 239.255.46.13

access-list 99 permit 239.255.46.14

access-list 99 permit 239.255.46.15

remote switch

int g0/2

ip pim sparse-mode

would this work?

Since you've decided to configure Static RP, not Auto-RP, you need to also enter the Static RP information in the remote switch.

ip pim rp-address 10.33.63.1

The remote switch already knows about the rp address. see below:

remoteswitch#sh ip pim rp mapping

PIM Group-to-RP Mappings

Group(s) 224.0.0.0/4

RP 10.33.63.1 (?), v2v1

Info source: 10.10.10.10 (?), elected via Auto-RP

Uptime: 1w1d, expires: 00:02:25

remoteswitch#sh ip pim rp

Group: 239.255.45.41, RP: 10.33.63.1, v2, uptime 1w1d, expires 00:02:33

Group: 239.255.255.250, RP: 10.33.63.1, v2, uptime 1w1d, expires 00:02:33

Group: 239.255.45.43, RP: 10.33.63.1, v2, uptime 1w1d, expires 00:02:33

Group: 239.255.45.32, RP: 10.33.63.1, v2, uptime 1w1d, expires 00:02:33

Group: 239.255.45.34, RP: 10.33.63.1, v2, uptime 1w1d, expires 00:02:33

Group: 239.255.45.24, RP: 10.33.63.1, v2, uptime 1w1d, expires 00:02:33

Group: 239.255.45.22, RP: 10.33.63.1, v2, uptime 1w1d, expires 00:02:33

Group: 239.255.46.14, RP: 10.33.63.1, v2, uptime 1w1d, expires 00:02:33

Group: 239.255.46.15, RP: 10.33.63.1, v2, uptime 1w1d, expires 00:02:33

Group: 239.255.46.12, RP: 10.33.63.1, v2, uptime 1w1d, expires 00:02:33

Group: 239.255.46.13, RP: 10.33.63.1, v2, uptime 1w1d, expires 00:02:33

Group: 239.255.46.11, RP: 10.33.63.1, v2, uptime 1w1d, expires 00:02:33

Group: 239.255.45.4, RP: 10.33.63.1, v2, uptime 1w1d, expires 00:02:33

Group: 239.255.46.5, RP: 10.33.63.1, v2, uptime 1w1d, expires 00:02:33

Group: 239.255.45.1, RP: 10.33.63.1, v2, uptime 1w1d, expires 00:02:33

Group: 239.255.45.2, RP: 10.33.63.1, v2, uptime 1w1d, expires 00:02:33

Group: 239.255.46.1, RP: 10.33.63.1, v2, uptime 1w1d, expires 00:02:33

Group: 239.255.45.103, RP: 10.33.63.1, v2, uptime 1w1d, expires 00:02:33

Group: 239.255.45.102, RP: 10.33.63.1, v2, uptime 1w1d, expires 00:02:33

Group: 239.255.140.2, RP: 10.33.63.1, v2, uptime 1w1d, expires 00:02:33

Group: 239.255.141.2, RP: 10.33.63.1, v2, uptime 1w1d, expires 00:02:33

Group: 239.255.45.132, RP: 10.33.63.1, v2, uptime 1w1d, expires 00:02:33

So you are using Auto-RP but you aren't filtering the Auto-RP group-list.

Per your output

Group(s) 224.0.0.0/4

covers all multicast groups.

The portion of the config you posted reflects a static RP configuration. You must have additional multicast information in your router for Auto-RP which you haven't posted.

We have two core switches configuring for Auto-RP. The switch called RemoteSwitch connect to those core switches internally. The RemoteSwitch is then connected to another switch that I called switchSite1 via a 20Mb Ethernet circuit. SwitchSite1 is the one requesting mcast information via RemoteSwitch.

CoreSwitch<->RemoteSwitch<20Mb>SwitchSite1.

Since I want to restrict the groups going from remoteswitch to switchsite1, can I just use ip multicast boundary on remoteswitch? This is an effect will deny any other groups from going across the 20Mbps circuit. Please advise.