IPTV access level setup

During the protracted crisis, providers begin to fight for each user. This can be done in several ways: either to reduce the monthly fee, but there are certain limits, no one wants to work at a loss; or introduce new services.

On the settings of one of them in the networks of the Ethernet provider and see.

The theory of multicast traffic, and IPTV is nothing but multicast, was well described by the user lena_sakhno in the topic Multicast routing for IPTV , there was a conversation mainly about the network core and PIM routing. But how can the user provide television as a service, and moreover to the Internet and local network?
With all his heart, the provider wants to spread all its services across different IP subnets, vlans and so on, so that it is convenient to rate, manage services, change the quality of service, in the end. Those. we do not have a moral plan in one VLAN to the user. To give the user a trunk connection? Yes, such eggs will be torn on the head, they will not be stroked, especially since we can hit the duplicate stream of multicast traffic in one direction. At first glance, the situation is stalemate, but do not despair!

The manufacturers of communication equipment have a technology that allows us to live beautifully: Cisco has it called MVR , and D-Link has ISM vlan .
')
It so happened that at the access level, switches from D-Link (ubiquitous) and Edge-Core (at least, we have :)) are mainly used, using their example and consider the setting.

The essence of this technology is that we give the user a separate vlan with a local network (or an isolated vlan, who has some connection scheme), within which local traffic will run (alternatively, DC ++, eMule, Shareman, etc.). Internet access will be through PPTP \ L2TP, everything is as usual. For IPTV traffic, a separate VLAN has been established, by means of which the switch will accumulate all IGMP messages about joining a group on it and send reports to the IGMP polling device on its behalf. Thus, for each channel, only one copy of the multicast stream will be transmitted. Then the ISM VLAN will redirect the flow to the corresponding registered subscribers in the VLAN.

So, we have custom vlans 10, 20, and ISM vlan 601. Requests from subscribers come to the switch in user vlans, then the switch on its own behalf redirects the request to the upstream switch, which is a PIM router. From it the flow will come in 601 vlan, further the switch redirects this traffic to the corresponding user vlan.

OK, that concerns directly settings, example for D-Link 3526:

create vlan user1 tag 10
create vlan user2 tag 20
config vlan default delete 1-26
config vlan user1 add untagged 1
config vlan user1 add tagged 25,26
config vlan user2 add untagged 2
config vlan user2 add tagged 25,26
create igmp_snooping multicast_vlan IPTV 601
config igmp_snooping multicast_vlan IPTV member_port 1-2 source_port 25-26 replace_source_ip 10.21.255.2 state enable
enable igmp_snooping

Switch ports 1,2 go respectively to users, ports 25-26 - aplnik.
With the create igmp_snooping multicast_vlan IPTV 601 command, we create an ISM vlan with the name IPTV, located in VLAN 601.
Using the config igmp_snooping multicast_vlan IPTV member_port 1-2 command, we configure the system 1.2 as service recipients, source_port 25-26 - source ports, replace_source_ip 10.21.255.2 - replace IP addresses of users in IGMP requests to this address.

The following example is for Edge-core ES3528. He has a slightly trimmed version of MVR, as I understand it, and he only supports the scheme when both user 1 and user 2 are in the same vlan, for example, in vlan 10.

vlan database
vlan 10 media ethernet state active
vlan 20 media ethernet state active
vlan 601 name IPTV media ethernet state active
!
mvr
mvr vlan 601
mvr receiver-vlan 10
!
interface ethernet 1/1
ip source-guard sip-mac
ip source-guard max-binding 3
switchport allowed vlan add 10 untagged
switchport native vlan 10
switchport allowed vlan remove 1
spanning-tree root-guard
spanning-tree bpdu-guard
mvr type receiver
mvr immediate
!
interface ethernet 1/25
ip dhcp snooping trust
switchport allowed vlan add 601,10 tagged
mvr type source


Here we create a vlan in the vlan database , enable mvr , with the command mvr type receiver
on the user port we say that it is the port of the receiver, with the command mvr type source
on the uplink port, configure the source port.

With the help of simple protocols and settings, we can provide users with such a wonderful thing as television :)