Multicast Over Vlans - Not Working - Page 3

abdelkader amghar · ‎08-02-2017

Hello All,

I've multicast issue, when i use different vlan.

The group adress is 239.192.1.1

On 3850 :

I've enable IP PIM sparse mode enable on INT VLAN 7 ET VLAN 3

RP adresse10.1.8.254

On SG500 L2 :

Ip igmp snooping only enable

here is the config on the 3850 and some multicast command in order to debug:

CORE#sh ip int brief

Interface IP-Address OK? Method Status Protocol

Vlan1 unassigned YES NVRAM up up

Vlan2 10.1.1.254 YES NVRAM up up

Vlan3 10.1.2.254 YES NVRAM up up

Vlan4 10.1.5.254 YES NVRAM up up

Vlan5 10.1.6.254 YES NVRAM up up

Vlan6 10.1.7.254 YES NVRAM up up

Vlan7 10.1.8.254 YES NVRAM up up

Vlan8 10.1.9.254 YES NVRAM up up

Vlan9 10.1.10.254 YES NVRAM up up

Vlan10 10.1.11.254 YES NVRAM up up

GigabitEthernet0/0 unassigned YES unset down down

GigabitEthernet1/0/1 unassigned YES unset down down

GigabitEthernet1/0/2 unassigned YES unset administratively down down

GigabitEthernet1/0/3 unassigned YES unset administratively down down

GigabitEthernet1/0/4 unassigned YES unset administratively down down

GigabitEthernet1/0/5 unassigned YES unset administratively down down

GigabitEthernet1/0/6 unassigned YES unset administratively down down

GigabitEthernet1/0/7 unassigned YES unset administratively down down

GigabitEthernet1/0/8 unassigned YES unset administratively down down

GigabitEthernet1/0/9 unassigned YES unset administratively down down

GigabitEthernet1/0/10 unassigned YES unset up up

Te1/1/1 10.92.255.22 YES NVRAM up up

Te1/1/2 unassigned YES unset up up

Te1/1/3 unassigned YES unset up up

Te1/1/4 unassigned YES unset administratively down down

Tunnel0 10.1.8.254 YES unset up up

Tunnel1 10.1.8.254 YES unset up up

CORE#sh ip route

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

+ - replicated route, % - next hop override

Gateway of last resort is 10.92.255.21 to network 0.0.0.0

S* 0.0.0.0/0 [1/0] via 10.92.255.21

10.0.0.0/8 is variably subnetted, 20 subnets, 4 masks

C 10.1.1.0/24 is directly connected, Vlan2

L 10.1.1.254/32 is directly connected, Vlan2

C 10.1.2.0/24 is directly connected, Vlan3

L 10.1.2.254/32 is directly connected, Vlan3

C 10.1.4.0/23 is directly connected, Vlan4

L 10.1.5.254/32 is directly connected, Vlan4

C 10.1.6.0/24 is directly connected, Vlan5

L 10.1.6.254/32 is directly connected, Vlan5

C 10.1.7.0/24 is directly connected, Vlan6

L 10.1.7.254/32 is directly connected, Vlan6

C 10.1.8.0/24 is directly connected, Vlan7

L 10.1.8.254/32 is directly connected, Vlan7

C 10.1.9.0/24 is directly connected, Vlan8

L 10.1.9.254/32 is directly connected, Vlan8

C 10.1.10.0/24 is directly connected, Vlan9

L 10.1.10.254/32 is directly connected, Vlan9

C 10.1.11.0/24 is directly connected, Vlan10

L 10.1.11.254/32 is directly connected, Vlan10

C 10.92.255.20/30 is directly connected, TenGigabitEthernet1/1/1

L 10.92.255.22/32 is directly connected, TenGigabitEthernet1/1/1

CORE#sh int vlan 7

Vlan7 is up, line protocol is up

Hardware is Ethernet SVI, address is cc5a.5383.1067 (bia cc5a.5383.1067)

Internet address is 10.1.8.254/24

MTU 1500 bytes, BW 1000000 Kbit/sec, DLY 10 usec,

reliability 255/255, txload 1/255, rxload 7/255

Encapsulation ARPA, loopback not set

Keepalive not supported

ARP type: ARPA, ARP Timeout 04:00:00

Last input 00:00:00, output never, output hang never

Last clearing of "show interface" counters never

Input queue: 0/75/20/0 (size/max/drops/flushes); Total output drops: 0

Queueing strategy: fifo

Output queue: 0/40 (size/max)

5 minute input rate 30277000 bits/sec, 2789 packets/sec

5 minute output rate 28000 bits/sec, 1 packets/sec

370430248 packets input, 503272111747 bytes, 0 no buffer

Received 0 broadcasts (10 IP multicasts)

0 runts, 0 giants, 0 throttles

0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored

416819 packets output, 95619968 bytes, 0 underruns

0 output errors, 2 interface resets

0 unknown protocol drops

0 output buffer failures, 0 output buffers swapped out

CORE#sh int vlan 3

Vlan3 is up, line protocol is up

Hardware is Ethernet SVI, address is cc5a.5383.1067 (bia cc5a.5383.1067)

Internet address is 10.1.2.254/24

MTU 1500 bytes, BW 1000000 Kbit/sec, DLY 10 usec,

reliability 255/255, txload 1/255, rxload 1/255

Encapsulation ARPA, loopback not set

Keepalive not supported

ARP type: ARPA, ARP Timeout 04:00:00

Last input 00:00:03, output never, output hang never

Last clearing of "show interface" counters never

Input queue: 0/75/0/0 (size/max/drops/flushes); Total output drops: 0

Queueing strategy: fifo

Output queue: 0/40 (size/max)

5 minute input rate 0 bits/sec, 0 packets/sec

5 minute output rate 57000 bits/sec, 4 packets/sec

3435540 packets input, 1945286581 bytes, 0 no buffer

Received 0 broadcasts (3 IP multicasts)

0 runts, 0 giants, 0 throttles

0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored

4778213 packets output, 6015209728 bytes, 0 underruns

0 output errors, 2 interface resets

0 unknown protocol drops

0 output buffer failures, 0 output buffers swapped out

CORE#

CORE#sh ip pim rp

Group: 239.192.1.1, RP: 10.1.8.254, next RP-reachable never

Group: 239.255.255.255, RP: 10.1.8.254, next RP-reachable never

Group: 239.255.255.254, RP: 10.1.8.254, next RP-reachable never

Group: 239.255.255.250, RP: 10.1.8.254, next RP-reachable never

Group: 239.192.0.1, RP: 10.1.8.254, next RP-reachable never

Group: 224.0.1.40, RP: 10.1.8.254, next RP-reachable never

CORE#

CORE#sh int trunk

Port Mode Encapsulation Status Native vlan

Gi1/0/47 on 802.1q trunking 1

Gi1/0/48 on 802.1q trunking 999

Te1/1/2 on 802.1q trunking 999

Te1/1/3 on 802.1q trunking 999

Port Vlans allowed on trunk

Gi1/0/47 1-10,30,999

Gi1/0/48 1-10,30,999

Te1/1/2 1-10,30,999

Te1/1/3 1-10,30,999

Port Vlans allowed and active in management domain

Gi1/0/47 1-10,30,999

Gi1/0/48 1-10,30,999

Te1/1/2 1-10,30,999

Te1/1/3 1-10,30,999

Port Vlans in spanning tree forwarding state and not pruned

Gi1/0/47 1-10,30,999

Gi1/0/48 1-10,30,999

Te1/1/2 1-10,30,999

Te1/1/3 1-10,30,999

CORE#

CORE#sh 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.192.1.1), 13:49:06/00:02:29, RP 10.1.8.254, flags: SJCL

Incoming interface: Null, RPF nbr 0.0.0.0

Outgoing interface list:

Vlan3, Forward/Sparse, 01:36:32/00:02:29

Vlan7, Forward/Sparse, 13:20:02/00:02:08

(*, 239.255.255.255), 1d08h/stopped, RP 10.1.8.254, flags: SJC

Incoming interface: Null, RPF nbr 0.0.0.0

Outgoing interface list:

Vlan3, Forward/Sparse, 01:59:29/00:02:30

Vlan7, Forward/Sparse, 1d07h/00:02:10

(10.1.2.100, 239.255.255.255), 01:59:02/00:01:09, flags: T

Incoming interface: Vlan3, RPF nbr 0.0.0.0

Outgoing interface list:

Vlan7, Forward/Sparse, 01:59:02/00:02:10

(10.1.8.1, 239.255.255.255), 1d07h/00:02:45, flags: T

Incoming interface: Vlan7, RPF nbr 0.0.0.0

Outgoing interface list:

Vlan3, Forward/Sparse, 01:59:29/00:02:30

(10.1.8.100, 239.255.255.255), 1d07h/00:01:06, flags: JT

Incoming interface: Vlan7, RPF nbr 0.0.0.0

Outgoing interface list:

Vlan3, Forward/Sparse, 01:59:29/00:02:30

(*, 239.255.255.254), 01:59:30/00:02:35, RP 10.1.8.254, flags: SJC

Incoming interface: Null, RPF nbr 0.0.0.0

Outgoing interface list:

Vlan3, Forward/Sparse, 01:59:29/00:02:35

(*, 239.255.255.250), 1d08h/00:02:52, RP 10.1.8.254, flags: SJC

Incoming interface: Null, RPF nbr 0.0.0.0

Outgoing interface list:

Vlan3, Forward/Sparse, 01:59:29/00:02:33

Vlan6, Forward/Sparse, 1d08h/00:02:52

(*, 239.192.0.1), 01:59:27/00:02:36, RP 10.1.8.254, flags: SJCL

Incoming interface: Null, RPF nbr 0.0.0.0

Outgoing interface list:

Vlan3, Forward/Sparse, 01:59:27/00:02:36

(*, 224.0.1.40), 1d08h/00:02:51, RP 10.1.8.254, flags: SJCL

Incoming interface: Null, RPF nbr 0.0.0.0

Outgoing interface list:

Vlan6, Forward/Sparse, 1d08h/00:02:51

CORE#sh ip igmp membership

Flags: A - aggregate, T - tracked

L - Local, S - static, V - virtual, R - Reported through v3

I - v3lite, U - Urd, M - SSM (S,G) channel

1,2,3 - The version of IGMP, the group is in

Channel/Group-Flags:

/ - Filtering entry (Exclude mode (S,G), Include mode (G))

Reporter:

<mac-or-ip-address> - last reporter if group is not explicitly tracked

<n>/<m> - <n> reporter in include mode, <m> reporter in exclude

Channel/Group Reporter Uptime Exp. Flags Interface

*,239.192.1.1 10.1.2.254 01:37:06 02:56 2LA Vl3

*,239.192.1.1 10.1.8.100 13:20:36 02:39 2A Vl7

*,239.255.255.255 10.1.2.11 02:00:04 02:56 2A Vl3

*,239.255.255.255 10.1.8.100 1d07h 02:33 2A Vl7

*,239.255.255.254 10.1.2.20 02:00:04 02:56 2A Vl3

*,239.255.255.250 10.1.2.100 02:00:04 02:59 2A Vl3

*,239.255.255.250 10.1.7.2 1d08h 02:18 2A Vl6

*,239.192.0.1 10.1.2.254 02:00:01 02:03 2LA Vl3

*,224.0.1.40 10.1.7.254 1d08h 02:17 2LA Vl6

I noticed that in the sh ip mroute i've (*,G) and not (S,G):

(*, 239.192.1.1), 13:49:06/00:02:29, RP 10.1.8.254, flags: SJCL

Incoming interface: Null, RPF nbr 0.0.0.0

Outgoing interface list:

Vlan3, Forward/Sparse, 01:36:32/00:02:29

Vlan7, Forward/Sparse, 13:20:02/00:02:08

BUT NOT

( IP player, 239.192.1.1) 13:49:06/00:02:29, RP 10.1.8.254, flags: SJCL

Incoming interface: VLAN 7, RPF nbr 0.0.0.0

Outgoing interface list:

Vlan3, Forward/Sparse, 01:36:32/00:02:29

Vlan7, Forward/Sparse, 13:20:02/00:02:08

Thanks for your help.

nsalgado · ‎08-03-2017

Hi Abdel,

can you please clarify exactly what do you mean with "work on VLAN 7 but not on others"?

This mean that when your receiver is in VLAN 7 you can see the announcement and actually get the stream?

Also please confirm that if I understood correctly: With receiver in VLAN 3 you see the Announcement but no stream. With receiver in VLAN 7 you see the Announcement and can get the stream.

Thank you.

abdelkader amghar · ‎08-03-2017

Hello,

Correct from vlan7 (same vlan used on server who send multicast) the player 10.1.7.100can see the announcement and get the stream.

From all other vlan i can get the announcment but the stream failed.

Thanks

nsalgado · ‎08-03-2017

Thanks.

If you ping 232.10.10.10 from the source server you've replys?

The problem seems registering the source. Can you get a capture from the Core to confirm that the traffic is hitting the box?

Also can you get do debug ip pim and do clear ip mroute * and try again?

abdelkader amghar · ‎08-03-2017

Hello,

I dont understand why you wanted to ping 232.10.10.10.

From the server :

admin@10.1.8.1's password:
AvediaStream g44xx

admin@0094F3:~$ ping 239.192.1.1
PING 239.192.1.1 (239.192.1.1): 56 data bytes
64 bytes from 10.1.8.1: seq=0 ttl=64 time=0.223 ms
64 bytes from 10.1.8.1: seq=1 ttl=64 time=0.130 ms

--- 239.192.1.1 ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 0.130/0.176/0.223 ms

admin@0094F3:~$ ping 232.10.10.10
PING 232.10.10.10 (232.10.10.10): 56 data bytes
^C
--- 232.10.10.10 ping statistics ---
4 packets transmitted, 0 packets received, 100% packet loss
admin@0094F3:~$

from the CORE:

CORE# debug ip pim
PIM debugging is on
CORE#clear ip mroute *
CORE#terminal monitor
CORE# debug ip pim
PIM debugging is on
CORE#
*Aug 3 14:23:13.372: PIM(0): Building Periodic (*,G) Join / (S,G,RP-bit) Prune message for 224.2.127.254
*Aug 3 14:23:14.172: PIM(0): Building Periodic (*,G) Join / (S,G,RP-bit) Prune message for 224.0.1.40
*Aug 3 14:23:30.074: PIM(0): Building Periodic (*,G) Join / (S,G,RP-bit) Prune message for 239.255.255.250
*Aug 3 14:23:31.273: PIM(0): Building Periodic (*,G) Join / (S,G,RP-bit) Prune message for 239.192.0.1
*Aug 3 14:23:31.572: PIM(0): Building Periodic (*,G) Join / (S,G,RP-bit) Prune message for 239.255.255.254
*Aug 3 14:23:35.372: PIM(0): Building Periodic (*,G) Join / (S,G,RP-bit) Prune message for 239.192.1.1
*Aug 3 14:24:11.774: PIM(0): Building Periodic (*,G) Join / (S,G,RP-bit) Prune message for 239.255.255.255
*Aug 3 14:24:12.971: PIM(0): Building Periodic (*,G) Join / (S,G,RP-bit) Prune message for 224.2.127.254
*Aug 3 14:24:13.174: PIM(0): Building Periodic (*,G) Join / (S,G,RP-bit) Prune message for 224.0.1.40
*Aug 3 14:24:29.473: PIM(0): Building Periodic (*,G) Join / (S,G,RP-bit) Prune message for 239.255.255.250
*Aug 3 14:24:29.673: PIM(0): Building Periodic (*,G) Join / (S,G,RP-bit) Prune message for 239.192.0.1
*Aug 3 14:24:29.973: PIM(0): Building Periodic (*,G) Join / (S,G,RP-bit) Prune message for 239.255.255.254
*Aug 3 14:24:35.072: PIM(0): Building Periodic (*,G) Join / (S,G,RP-bit) Prune message for 239.192.1.1
*Aug 3 14:25:11.072: PIM(0): Building Periodic (*,G) Join / (S,G,RP-bit) Prune message for 239.255.255.255
*Aug 3 14:25:12.473: PIM(0): Building Periodic (*,G) Join / (S,G,RP-bit) Prune message for 224.2.127.254
*Aug 3 14:25:13.073: PIM(0): Building Periodic (*,G) Join / (S,G,RP-bit) Prune message for 224.0.1.40
*Aug 3 14:25:28.373: PIM(0): Building Periodic (*,G) Join / (S,G,RP-bit) Prune message for 239.255.255.250
*Aug 3 14:25:28.671: PIM(0): Building Periodic (*,G) Join / (S,G,RP-bit) Prune message for 239.192.0.1
*Aug 3 14:25:29.175: PIM(0): Building Periodic (*,G) Join / (S,G,RP-bit) Prune message for 239.255.255.254
*Aug 3 14:25:33.271: PIM(0): Building Periodic (*,G) Join / (S,G,RP-bit) Prune message for 239.192.1.1
*Aug 3 14:26:09.672: PIM(0): Building Periodic (*,G) Join / (S,G,RP-bit) Prune message for 239.255.255.255
*Aug 3 14:26:11.272: PIM(0): Building Periodic (*,G) Join / (S,G,RP-bit) Prune message for 224.0.1.40
*Aug 3 14:26:12.272: PIM(0): Building Periodic (*,G) Join / (S,G,RP-bit) Prune message for 224.2.127.254
*Aug 3 14:26:26.972: PIM(0): Building Periodic (*,G) Join / (S,G,RP-bit) Prune message for 239.255.255.250
*Aug 3 14:26:27.975: PIM(0): Building Periodic (*,G) Join / (S,G,RP-bit) Prune message for 239.192.0.1
*Aug 3 14:26:28.071: PIM(0): Building Periodic (*,G) Join / (S,G,RP-bit) Prune message for 239.255.255.254
*Aug 3 14:26:31.774: PIM(0): Building Periodic (*,G) Join / (S,G,RP-bit) Prune message for 239.192.1.1
*Aug 3 14:27:08.471: PIM(0): Building Periodic (*,G) Join / (S,G,RP-bit) Prune message for 239.255.255.255
*Aug 3 14:27:10.173: PIM(0): Building Periodic (*,G) Join / (S,G,RP-bit) Prune message for 224.0.1.40
*Aug 3 14:27:11.071: PIM(0): Building Periodic (*,G) Join / (S,G,RP-bit) Prune message for 224.2.127.254
*Aug 3 14:27:25.671: PIM(0): Building Periodic (*,G) Join / (S,G,RP-bit) Prune message for 239.255.255.250
*Aug 3 14:27:26.274: PIM(0): Building Periodic (*,G) Join / (S,G,RP-bit) Prune message for 239.255.255.254
*Aug 3 14:27:26.274: PIM(0): Building Periodic (*,G) Join / (S,G,RP-bit) Prune message for 239.192.0.1
*Aug 3 14:27:31.071: PIM(0): Building Periodic (*,G) Join / (S,G,RP-bit) Prune message for 239.192.1.1
*Aug 3 14:28:07.272: PIM(0): Building Periodic (*,G) Join / (S,G,RP-bit) Prune message for 239.255.255.255
*Aug 3 14:28:09.173: PIM(0): Building Periodic (*,G) Join / (S,G,RP-bit) Prune message for 224.0.1.40
*Aug 3 14:28:09.871: PIM(0): Building Periodic (*,G) Join / (S,G,RP-bit) Prune message for 224.2.127.254
*Aug 3 14:28:24.071: PIM(0): Building Periodic (*,G) Join / (S,G,RP-bit) Prune message for 239.255.255.250
*Aug 3 14:28:25.072: PIM(0): Building Periodic (*,G) Join / (S,G,RP-bit) Prune message for 239.192.0.1
*Aug 3 14:28:25.574: PIM(0): Building Periodic (*,G) Join / (S,G,RP-bit) Prune message for 239.255.255.254
*Aug 3 14:28:30.372: PIM(0): Building Periodic (*,G) Join / (S,G,RP-bit) Prune message for 239.192.1.1
*Aug 3 14:29:06.171: PIM(0): Building Periodic (*,G) Join / (S,G,RP-bit) Prune message for 239.255.255.255
*Aug 3 14:29:08.371: PIM(0): Building Periodic (*,G) Join / (S,G,RP-bit) Prune message for 224.2.127.254
*Aug 3 14:29:08.371: PIM(0): Building Periodic (*,G) Join / (S,G,RP-bit) Prune message for 224.0.1.40
*Aug 3 14:29:23.373: PIM(0): Building Periodic (*,G) Join / (S,G,RP-bit) Prune message for 239.192.0.1

Thks

nsalgado · ‎08-03-2017

Sorry, I was thinking in other mcast group :)

So the ping from the server worked, and Im assuming that the S,G appeared in the Core, and that it wasnt other device in the same VLAN replying, right?

If true I think that we need the pkt cap at this point...

abdelkader amghar · ‎08-03-2017

Sorry maybe i don't understand what you asked me:

summary :

IPTV Server:10.1.8.1 and the player 10.1.8.100 on VLAN7

you asked me to ping from the server the ip of multicast channel 239.192.1.1 i've an answer but from the same equipement:

admin@10.1.8.1's password:
AvediaStream g44xx

admin@0094F3:~$ ping 239.192.1.1
PING 239.192.1.1 (239.192.1.1): 56 data bytes
64 bytes from 10.1.8.1: seq=0 ttl=64 time=0.223 ms
64 bytes from 10.1.8.1: seq=1 ttl=64 time=0.130 ms

is it normal situation?

what do you mean by "hat it wasnt other device in the same VLAN replying, right?"

about the pcap trace i take my laptop and take the IP 10.1.2.200 (VLAN3) same to the player doesnt works.

i've the SAP annoucement but not the stream.

you can see the pcap trace in my previous answer yesterday with the attachement pcapmulticast2.zip.

nsalgado · ‎08-03-2017

Could be normal.

Just do a ping from the Server and send show ip mroute from the Core.

You have a capture in VLAN3, we need a capture from the server side.

Tnks

abdelkader amghar · ‎09-11-2017

Hello Guys,

Hello Guys,

I'm back from the holidays.

I've done some test and i said a big mistake.

Sorry for this huge mistake!!!

here is the situation:

On the CORE, if i plug a VLC player on VLAN 7 it works but it doesntnt works in all other VLAN.

Therefore, we can focus the troubleshooting only on the core.

The settings i've done is the following:

Gateway IPTV-> 10.1.8.1

Enable multicast-routing
ip pim sparse mode in each SVI
define a RP -> 10.1.8.254 (Gateway of VLAN 7)

Do i need to add something in the settings in order to make multicast on different VLAN

Thanks for your help