HPE Aruba Networking & ProVision-based
1821868 Members
3491 Online
109638 Solutions
New Discussion

Re: Otrum IPTV with Procurve Network

 
ibrahim_sms
Occasional Contributor

Otrum IPTV with Procurve Network

Hello,

 

I have two 8206 Cores, a bunch of 2920 edge switches.
The IPTV headends (Steams sources) are connected to one edge switch.
The TVs are connected to other edge switches.
I'm using vlan 50 as the IPTV VLAN, All TV's, Headends, DHCP are within the same VLAN(50).
I want to use multicasting to get the the TV's to work, without flooding the networking and using up my uplinks.
What should my config be on the cores and edge switches.
I really hope you guys can help me.

Thanks in advance

3 REPLIES 3
Vince-Whirlwind
Honored Contributor

Re: Otrum IPTV with Procurve Network

Because you have everything within the same VLAN, you do not need to enable ip multicast-routing on your core switch, all you need to do is disable querier on all your access switches, and make sure querier is enabled on the 2 cores.

ibrahim_sms
Occasional Contributor

Re: Otrum IPTV with Procurve Network

I have already enabled igmp-snooping on all devices. I disabled the igmp querier on all access switches and kept it on the Cores. I got the stream, but seems there is an issue when I'm toggling between channels, its not smooth, the stream freezes for a split second or gets messed up somtimes for a sec then goes back to normal. I'm thinking to give the IPTV VLAN some QoS.


I noticed in earlier firmwares, they used a command "igmp high-priority-forward"  but this is not available anymore in the newest firmware versions. They say in an HP article to replace that with QoS. I already have QoS under the IPTV VLAN context but never felt it did anything, seems something is missing. Any suggestion ?

Thanks,

Vince-Whirlwind
Honored Contributor

Re: Otrum IPTV with Procurve Network

QoS will only make a difference if you have congestion.

 

Congestion would be freezing/messed up at random intervals during normal operation.

 

Freezing/messed up after a channel change (only) can't be fixed with QoS, and probably has nothing to do with the network.