IP Multicast Group

[Learnercisco]

Hi Teck guy, 

I configured multicast in Core and access switch. The source and destnation are in the different vlan and in same access switch .The both VLANs mapped to same VRF name CCTV.

CCTV CAMS are preconfigured with Multicast Range (224.15.1.1 to 224.15.1.100).

Problem: CCTVServer (Destination)  is not getting the stream from CAM (Source) with Multicast-group address (e.g 224.15.1.10) for one Camera. if i see the Show ip mroute vrf CCTV command on Core , i see different multicast groups (e.g 232.x.x.x , 224.0.0.40 x)

IP Multicast mode is IP SSM

Core Switch Configuration

IP Multicast Routing

IP Multicast Routing vrf CCTV

ip vrf CCTV
rd 65100:101
oute-target export 65100:101
route-target import 65100:101

address-family ipv4
mdt default 224.15.0.0
mdt data 224.15.0.0 0.0.255.255 threshold 1 

ip access-list standard MDT-SSM permit 224.15.0.0 0.0.255.255
ip pim ssm range MDT-SSM

Int vlan10

Descrption CCTV Server

vrf forwarding CCTV

ip address 10.1.1.1 255.255.255.0

ip pim Sparse-mode

IP IGMP version 2

Int vlan11

Descrption CCTV Server

vrf forwarding CCTV

ip address 10.1.2.1 255.255.255.0

ip pim Sparse-mode

IP IGMP version 2

Access Switch Configuration:

 IP IGMP Snooping in enable globally and on host ports.

[balaji.bandi]

can you post below output.

1. sh ip mro vrf  CCTV

2. sh ip route vrf  CCTV

3. show mroute vrf CCV 224.15.x.x

as per the below comment, is only 1 camera having issues, others working?

Problem: CCTVServer (Destination)  is not getting the stream from CAM (Source) with Multicast-group address (e.g 224.15.1.10) for one Camera

[Learnercisco]

Thanks Balaji,

The Multicast Stream is not working for all. VLANs interfaces on Core are showing multicast traffic. 

from this command "sh ip mro vrf  CCTV" I can see the different cameras multicast ip address(start with 224.15.x.xx) and including two extra multicast groups e.g 232.255.255 & 224.0.0.40. 

IS there any debug command to check the multicast traffic on the Core. 

[balaji.bandi]

if you looking for us to help we need to have that output asked in the past to understand what is wrong. how you configured, since dont have complete visibility of your setup and what is not working. 

if you like to solve your own, below URL debug will help you :

https://www.cisco.com/c/en/us/support/docs/ip/ip-multicast/13726-57.html

https://www.cisco.com/c/en/us/support/docs/ip/ip-multicast/16450-mcastguide0.html

[Learnercisco]

Thanks Balaji for your Support,

i changed the following configuration on Core and it starts working. 

1) create RP on the Core..

1) i used PIM Dense mode instead of using Sparse mode

Secondly i add one more reciver down to Distribution-Acess Switch which is not working(Topology Attached).

do i configured Multicast VPN To extend the stream down to another Source. MPLS VPN is configured between Core/Distribution.

Thanks for your support

[Giuseppe Larosa]

Hello @Learnercisco ,

I have reviewed your thread.

My suggestion is to try to use PIM SM instead of PIM SSM for building the MDT trees.

the Core switch can be the RP for the multicast addresses in the global routing table used to carry VPN multicast traffic.

This is draft Rosen multicast VPN over GRE.

Try to use also PIM  SM in the multicast VPN as I'm not sure that PIM dense mode is supported in this scenario.

The Customer RP can be another loopback on core switch mapped to the VPN.

Hope to help

Giuseppe

[Learnercisco]

Thanks for you reply, i review your suggestion.below is my overall multicast configuration in core/distribution

Core Configuration

vrf definition PCCTV
rd 65001:10
route-target export 65001:110
route-target import 65001:110
!

address-family ipv4
mdt default 239.252.0.0

interface Loopback0
Descrption ### for BGP/MPLS/OSPF
ip address 172.16.0.1 255.255.255.255
ip pim sparse-dense-mode
end

ip multicast-routing
ip multicast-routing vrf PCCTV

ip pim vrf PCCTV rp-address 172.16.70.193 PCCTV-Multicast

ip access-list standard PCCTV-Multicast
10 remark map multicast address group for PCCTV
10 permit 239.252.0.0 0.0.255.255

interface Loopback100
### Description Lookpback for RP ###
vrf forwarding PCCTV
ip address 172.16.70.193 255.255.255.224
ip pim sparse-dense-mode
end

interface Vlan43
description PCCTV-Central-Equipment(Video Server,Multicast destination)
vrf forwarding PCCTV
ip address 172.16.70.1 255.255.255.224
ip pim sparse-dense-mode
end

interface Vlan44
description <<< PCCTV Field Equipment,CAMERAS, Multicast Source >>>)
vrf forwarding PCCTV
ip address 172.16.71.1 255.255.255.0
ip pim sparse-dense-mode

====================================================================
Distribution Switch configuration

vrf definition PCCTV
rd 65001:10
route-target export 65001:110
route-target import 65001:110
!
address-family ipv4
mdt default 239.252.0.0

interface Loopback0
Descrption ### for BGP/MPLS/OSPF
ip address 172.16.0.2 255.255.255.255
ip pim sparse-dense-mode
end

ip pim vrf PCCTV rp-address 172.16.70.193 PCCTV-Multicast

ip access-list standard PCCTV-Multicast
10 remark map multicast address group for PCCTV
10 permit 239.252.0.0 0.0.255.255

interface Vlan76
Descrption PCCTV Workstation (Multicast destination)
vrf forwarding PCCTV
ip address 172.16.38.1 255.255.255.192
ip pim sparse-dense-mode

Layer 2 Switch

cisco 9300 IGMP enabl by default.

[Giuseppe Larosa]

Hello @Learnercisco ,

on  L3 interface(s) between core and distribution you need to enable

mpls ip

ip pim sparse-dense mode

Because mpls ip is needed for unicast connectivity in VPN and ip pim is needed to be able to support multicast VPN traffic that is encapsulated in GRE packets with destination the MDT multicast group (s).

You still need to define the MDT default group and eventually MDT data groups for the VPN but these global multicast addresses have to be in PIM SM mode to use the global RP address.

Hope to help

Giuseppe