Solved: Multicasting between vlan

kkpc · ‎11-20-2019

Hi,

I need help for configuration cisco catalist 4500x and catalyst 3750 protokol multicast.

swtitch 4500x is set to layer3:

ip multicast-routing

interface vlan 200

ip pim sparse-mode

interface vlan 203

ip pim sparse-mode

ip pim rp-address (ip 4500x)

swtitch 3750:

ip multicast-routing

interface vlan 200

ip pim sparse-mode

interface vlan 203

ip pim sparse-mode

ip pim rp-address (ip 4500x)

server is vlan 200

camers is vlan 203

Multicating between vlan200 and 203 not routing, why ?

Working multicasting inside vlan but between vlans is not working.

Thanks for help.

Jaderson Pessoa · ‎11-22-2019

@kkpc Hello

Could you share below configuration:

ON 4500X

show running-config

ON 3750

show running-config

?

Because in your topology you told to us that just 4500X is configured as L3 device, in this case, you wont neeed a interface vlan 200 and 203 on others switch and wont need "ip pim sparse-mode" under interface on them.

Jaderson Pessoa
*** Rate All Helpful Responses ***

View solution in original post

Sergey Lisitsin · ‎11-20-2019

Can you please show output of

show ip route, show ip mroute and show igmp group from both switches.

kkpc · ‎11-21-2019

@Sergey Lisitsin help me ?

balaji.bandi · ‎11-20-2019

can you post :

##show ip mroute

#sh ip igmp groups

#sh ip igmp snooping

PIM is also needed to perform multicast routing between Vlans.

https://www.cisco.com/c/en/us/td/docs/switches/lan/catalyst4500/12-2/54sg/configuration/guide/config/mcastmls.html

BB

***** Rate All Helpful Responses *****

How to Ask The Cisco Community for Help

kkpc · ‎11-20-2019

VSS1_B1#show ip mroute
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,
L - Local, P - Pruned, R - RP-bit set, F - Register flag,
T - SPT-bit set, J - Join SPT, M - MSDP created entry, E - Extranet,
X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,
U - URD, I - Received Source Specific Host Report,
Z - Multicast Tunnel, z - MDT-data group sender,
Y - Joined MDT-data group, y - Sending to MDT-data group,
G - Received BGP C-Mroute, g - Sent BGP C-Mroute,
N - Received BGP Shared-Tree Prune, n - BGP C-Mroute suppressed,
Q - Received BGP S-A Route, q - Sent BGP S-A Route,
V - RD & Vector, v - Vector, p - PIM Joins on route,
x - VxLAN group
Outgoing interface flags: H - Hardware switched, A - Assert winner, p - PIM Join
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode

(*, 239.168.1.32), 2d12h/00:02:56, RP 172.21.85.1, flags: SP
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list: Null

(*, 239.168.1.33), 4d06h/00:02:49, RP 172.21.85.1, flags: SP
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list: Null

(*, 239.168.1.34), 1w4d/00:02:58, RP 172.21.85.1, flags: SP
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list: Null

(*, 239.168.1.35), 4d06h/00:02:56, RP 172.21.85.1, flags: SP
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list: Null

(*, 239.168.1.36), 1w4d/00:02:55, RP 172.21.85.1, flags: SP
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list: Null

VSS1_B1#sh ip igmp groups
IGMP Connected Group Membership
Group Address Interface Uptime Expires Last Reporter Group Accounted
239.168.1.32 Vlan203 2d12h 00:02:49 172.20.26.2
239.168.1.33 Vlan203 4d06h 00:02:55 172.20.26.1
239.168.1.34 Vlan200 4d06h 00:02:50 172.20.26.6
239.168.1.35 Vlan200 4d06h 00:02:48 172.20.26.4
239.168.1.36 Vlan200 4d06h 00:02:56 172.20.26.3
239.168.1.37 Vlan200 4d06h 00:02:50 172.20.26.5
239.168.1.38 Vlan200 4d06h 00:02:50 172.20.26.7
239.20.16.1 Vlan200 4d07h 00:02:50 172.20.16.1
239.20.1.16 Vlan200 6d08h 00:02:50 172.20.1.17
239.20.16.3 Vlan200 4d07h 00:02:57 172.20.16.3
239.20.16.2 Vlan200 4d07h 00:02:49 172.20.16.2
239.20.1.5 Vlan200 4d09h 00:02:50 172.20.17.3
239.20.1.6 Vlan200 4d09h 00:02:48 172.20.17.4
239.20.1.1 Vlan200 6d01h 00:02:50 172.20.1.1

VSS1_B1#sh ip igmp snooping
Global IGMP Snooping configuration:
-------------------------------------------
IGMP snooping : Enabled
IGMPv3 snooping : Enabled
Report suppression : Enabled
TCN solicit query : Disabled
TCN flood query count : 2
Last member query interval : 1000

Vlan 200:
--------
IGMP snooping : Enabled
IGMPv2 immediate leave : Disabled
Explicit host tracking : Enabled
Multicast router learning mode : pim-dvmrp
CGMP interoperability mode : IGMP_ONLY
Last member query interval : 1000
Vlan 201:
--------
IGMP snooping : Enabled
IGMPv2 immediate leave : Disabled
Explicit host tracking : Enabled
Multicast router learning mode : pim-dvmrp
CGMP interoperability mode : IGMP_ONLY
Last member query interval : 1000
Vlan 202:
--------
IGMP snooping : Enabled
IGMPv2 immediate leave : Disabled
Explicit host tracking : Enabled
Multicast router learning mode : pim-dvmrp
CGMP interoperability mode : IGMP_ONLY
Last member query interval : 1000
Vlan 203:
--------
IGMP snooping : Enabled
IGMPv2 immediate leave : Disabled
Explicit host tracking : Enabled
Multicast router learning mode : pim-dvmrp
CGMP interoperability mode : IGMP_ONLY
Last member query interval : 1000

kkpc · ‎11-20-2019

Somebody help ?.
How do you diagnose a problem?
Thx

mlund · ‎11-21-2019

Hi

On VSS1_B1 the igmp groups seems to be odd. The last reporter seems to be in different ip ranges, and also 172.20.26 is seeing on both vlan 200 and 203.

You can also see on the mroute that ther is no sender on any of the groups. There are only *.G entryn.

Can you please post the same outputs for the other switch.

/Mikael

kkpc · ‎11-21-2019

SW3_B2#show ip route
Extended Host Mode is enabled
Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route, H - NHRP, l - LISP
a - application route
+ - replicated route, % - next hop override, p - overrides from PfR

Gateway of last resort is not set

172.20.0.0/16 is variably subnetted, 2 subnets, 2 masks
C 172.20.0.0/16 is directly connected, Vlan200
L 172.20.80.3/32 is directly connected, Vlan200
172.21.0.0/16 is variably subnetted, 8 subnets, 2 masks
C 172.21.81.0/24 is directly connected, Vlan203
L 172.21.81.3/32 is directly connected, Vlan203
C 172.21.82.0/24 is directly connected, Vlan201
L 172.21.82.3/32 is directly connected, Vlan201
C 172.21.83.0/24 is directly connected, Vlan202
L 172.21.83.3/32 is directly connected, Vlan202
C 172.21.85.0/24 is directly connected, Vlan205
L 172.21.85.3/32 is directly connected, Vlan205
172.23.0.0/16 is variably subnetted, 2 subnets, 2 masks
C 172.23.0.0/23 is directly connected, Vlan2
L 172.23.0.3/32 is directly connected, Vlan2
SW3_B2#show ip mroute
IP Multicast Routing Table
Flags: D - Dense, S - Sparse, B - Bidir Group, s - SSM Group, C - Connected,
L - Local, P - Pruned, R - RP-bit set, F - Register flag,
T - SPT-bit set, J - Join SPT, M - MSDP created entry, E - Extranet,
X - Proxy Join Timer Running, A - Candidate for MSDP Advertisement,
U - URD, I - Received Source Specific Host Report,
Z - Multicast Tunnel, z - MDT-data group sender,
Y - Joined MDT-data group, y - Sending to MDT-data group,
G - Received BGP C-Mroute, g - Sent BGP C-Mroute,
N - Received BGP Shared-Tree Prune, n - BGP C-Mroute suppressed,
Q - Received BGP S-A Route, q - Sent BGP S-A Route,
V - RD & Vector, v - Vector, p - PIM Joins on route,
x - VxLAN group
Outgoing interface flags: H - Hardware switched, A - Assert winner, p - PIM Join
Timers: Uptime/Expires
Interface state: Interface, Next-Hop or VCD, State/Mode

(*, 239.255.255.250), 1w0d/00:02:28, RP 172.21.85.1, flags: SP
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list: Null

(*, 239.20.100.60), 02:53:37/00:02:42, RP 172.21.85.1, flags: SP
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list: Null

(*, 239.20.2.4), 4d20h/00:02:28, RP 172.21.85.1, flags: SP
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list: Null

(*, 239.20.2.2), 1w0d/00:02:32, RP 172.21.85.1, flags: SP
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list: Null

(*, 239.20.2.14), 1w0d/00:02:28, RP 172.21.85.1, flags: SP
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list: Null

(*, 239.20.2.26), 1w0d/00:02:33, RP 172.21.85.1, flags: SP
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list: Null

(*, 239.20.100.93), 6d06h/00:02:33, RP 172.21.85.1, flags: SP
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list: Null

kkpc · ‎11-21-2019

How can you diagnose the correctness routing multicast ?

By icmp: ping 239.x.x.x source vlan200 ?
ping 239.x.x.x source vlan203 ?

mlund · ‎11-20-2019

Hi

One common problem when mcast is not working, is that the sender is sending with ttl=1, thus the stream will be dropped by the router.

/Mikael

kkpc · ‎11-20-2019

@mlund
should I change this in the switch ?
if so how ?

command: ip multicast ttl-threshold 15 ?

balaji.bandi · ‎11-20-2019

you can do by config no ip mutlicast ttl-threshold, by default set to 1

or you can set on interface

interface vlan XXX 
 ip pim sparse-dense-mode 
 ip multicast ttl-threshold XX  ( XX is Hop)

BB

***** Rate All Helpful Responses *****

How to Ask The Cisco Community for Help

kkpc · ‎11-20-2019

not ttl:

(config-if)#ip multicast ?
boundary Boundary for administratively scoped multicast addresses
helper-map Broadcast to Multicast map OR Multicast to ip-address map
limit Limit multicast mroute state

mlund · ‎11-20-2019

Hi

No, You should check what the camera is setting. If they are setting ttl=1, then You have to change that setting in the cameras. If they already have ttl setting that is greater than 1, there is some other problem.

/Mikael

kkpc · ‎11-20-2019

In the cameras ttl=10