Configure IPTV at the access level

During a 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.

We’ll look at the settings of one of them in the networks of the Ethernet provider.

The theory of multicast traffic, and IPTV is nothing more than a multicast, was well told by the user lena_sakhno in the Multicast routing topic for IPTV , there was talk mainly about the core of the network and PIM routing. But how can a user provide television as a service, additional to the Internet and a local network?
The provider with all its soul wants to distribute all its services on various IP subnets, vlan and other, so that it is convenient to charge, manage services, change the quality of service, in the end. Those. submit all services in one VLAN to the user; we do not have a moral plan. Issue a trunk connection to the user? Yes, for such an eggthey won’t pat on the head, especially since we can rake the duplicated 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: at Cisco it is called MVR , at D-Link - ISM vlan .

It so happened that at the access level, mainly D-Link (universally) and Edge-Core switches (at least with us :) are used), and we’ll take a look at their settings as an example.

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 kind of connection scheme), inside which local traffic will run (as an option, DC ++, eMule, Shareman, etc.). Internet access will be via PPTP \ L2TP, everything is as usual. A separate vlan has been established for IPTV traffic, through which the switch will accumulate all IGMP messages about joining the group on it and send reports on its behalf to the IGMP polling device. 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 VLANs.

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

OK, as for the configuration itself, an 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

Ports 1.2 of the switch go to users, ports 25-26, respectively, are uplink. Using the create igmp_snooping multicast_vlan IPTV 601
command, we create an ISM vlan named IPTV located in VLAN 601. The config igmp_snooping multicast_vlan IPTV member_port 1-2 command configures streams 1.2 as service recipients, source_port 25-26 - source ports, replace_source_ip 10.21.255.2 - Substitute IP addresses of users in IGMP requests for this address. The following example is for the Edge-core ES3528. It has a slightly truncated version of MVR, as I understand it, and it 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 vlan in the vlan database , turn on mvr , use the mvr type receiver
command on the user port to say that this is the recipient port, use the mvr type source
command on the uplink port to configure the source port.

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