Cisco Support Community
Community Member

recent changes to upstream provider causing multicast issues

Recently our upstream provider changed from Cisco to Juniper, reasoning not to be discussed, anyway's until the change we have been receiving our multicast traffic from them with the interface connected set to sparse-dense-mode. Now they have changed to sparse only mode and setup RP's. We do not have RP's set up on our network due to most customer traffic is coming out dense-mode and some firewalls set to sparse mode, hence the use of sparse-dense-mode.

Now recently when trying to receive traffic from provider we were not seeing any multicast traffic coming in outside interface, due to the fact they hadn't told us of their change, we contacted them and they informed us of the change. So long story short we had to add on our tunnel interface (which points in to the local network) the following commands:

IP PIM dense-mode proxy-register 100

the following command had to be added to our outside interface (which points to our provider):

IP PIM sparse-dense-mode

IP igmp join-group 224.xx.xx.xx (for each multicast address being used for project)

We also had to add the following global commands:

IP  access-list 100 permit any any

IP PIM rp-address x.x.x.x

ip pim register-rate-limit 8000

Now this doesn't seem like much to have to add to get the multicast in but since their RP will never change but the multicast addresses will I was wondering if there were some different commands that I could add globally that would auto listen for their RP and automaticly pull all multicast addresses in and push them in the right direction. Anyone?

Community Member

recent changes to upstream provider causing multicast issues

they are running dense and you are running sparse-dense so you cannot use static RP address, you have to use dense mode or sparse dense, remove the rp-address and the rp register rate because you won't use an rp in dense any more.


CreatePlease to create content