How to configure PIM-DM on Omada L3 Switch via Omada Controller
2401 Contents
- Omada Controller (Software Controller / Hardware Controller / Cloud Based Controller, v5.9 and above)
- Omada L3 switches
This article focuses on how to configure the PIM-DM function on the Omada L3 switches via Omada Controller.
The Protocol Independent Multicast (PIM) provides routing for IP multicast using unicast static routing or unicast routing tables generated by any unicast routing protocol. Independent of the unicast routing protocol used, multicast routing serves to generate corresponding multicast routing table entries through unicast routing protocol.
PIM-DM, a dense-mode multicast routing protocol that uses the Push mode to transmit multicast data, is suitable for small networks with dense multicast group members.
Typical scenario for PIM-DM application:
The Source sends 16 channels of multicast data streams (235.0.0.51~235.0.0.66). Now Host A wants to join the group 235.0.0.51, and Host C wants to join the group 235.0.0.52.
|
Device |
Interface |
IP Address |
VLAN |
|
Switch A
|
GE 1/0/1 |
10.110.1.1/24 |
100 |
|
GE 1/0/2 |
192.168.11.1/24 |
101 |
|
|
Switch B
|
GE 1/0/1 |
10.110.2.1/24 |
200 |
|
GE 1/0/2 |
192.168.12.1/24 |
102 |
|
|
Switch C
|
GE 1/0/1 |
10.110.2.2/24 |
200 |
|
GE 1/0/2 |
192.168.13.1/24 |
103 |
|
|
Switch D
|
GE 1/0/1 |
10.110.5.1/24 |
300 |
|
GE 1/0/2 |
192.168.11.2/24 |
101 |
|
|
GE 1/0/3 |
192.168.12.2/24 |
102 |
|
|
GE 1/0/4 |
192.168.13.2/24 |
103 |
Video-on-demand streams are sent to receiver hosts in multicast. Receiver groups from different organizations form the stub networks, in each of which there is at least one receiver. The entire PIM domain uses the DM mode.
Host A and Host C are multicast receivers on two stub networks; Switch D is connected to the network where the multicast source (Source) is located through GE 1/0/1; Switch A is connected to the stub network N1 through GE 1/0/1 and to Switch D through the GE 1/0/2; Switch B and Switch C are connected to the stub network N2 through their respective GE 1/0/1 interfaces, and are connected to Switch D through their respective GE 1/0/2 interfaces.
IGMP runs between Switch A and stub network N1; it also runs between Switch B/C and stub network N2.
Before proceeding with the following configurations, configure the IP address and subnet mask of each interface and ensure that the routing is reachable between devices within the PIM-DM domain.
Then configure the unicast routing protocol within the domain to ensure reachability of each subnet. For more information, please refer to the RIP/OSPF configuration guide.
Step 1. Configure the unicast routing protocol within the domain to ensure reachability of each subnet. For more information, please refer to the RIP/OSPF configuration guide.
Step 2. Log in to the Controller and go to Setting > CLI configuration > Device CLI > Create New Device CLI profile.
Step 3. Send the following commands separately to Switch A, Switch B, and Switch C:
Switch A:
ip multicast-routing
ip igmp
ip pim dense-mode
interface vlan 101
ip pim
interface vlan 100
ip pim
ip igmp
Switch B:
ip multicast-routing
ip igmp
ip pim dense-mode
interface vlan 102
ip pim
interface vlan 200
ip pim
ip igmp
Switch C:
ip multicast-routing
ip igmp
ip pim dense-mode
interface vlan 103
ip pim
interface vlan 200
ip pim
ip igmp
Note: IGMP Querier Election: The switch with the smaller IP address will become the IGMP querier. When multiple PIM upstream routers exist within a subnet, an Assert Winner election will occur. If the route priority and cost are the same, the switch with the larger IP address will elected as the Assert Winner. The multicast data stream will be forwarded downstream to clients by the Assert Winner.
In the topology, there is an IGMP Querier and PIM Assert Winner election between Switch B and Switch C. According to the configuration in the sample topology, Switch B becomes the IGMP Querier, and Switch C becomes the Assert Winner that forwards the multicast stream to the group members in Network 2.
After configuring the switches connected to the stub networks, you need to enable PIM on other switches within the PIM domain (only Switch D in the sample topology). We take Switch D as an example to demonstrate the configuration.
Step 4. Go to Setting > CLI configuration > Device CLI > Create New Device CLI profile.
Step 5. Send the following commands to Switch D:
ip multicast-routing
ip pim dense-mode
interface vlan 101
ip pim
interface vlan 102
ip pim
interface vlan 103
ip pim
interface vlan 300
ip pim
Step 1. Log in to Controller, Go to Tools>Terminal, select Switch as Device Type, and choose Switch A/B/C/D as Sources. Then click Open Terminal to connect to Switches via SSH. You could switch SSH terminals of different switches by Device List.
Step 2. Checking Mroute table and PIM DM neighbors on Switch D:
There are a total of 16 channels in the Mroute table.
There are 3 PIM DM neighbors.
Step 3. Checking multicast flow forwarding on Switch A:
Switch A forwards the data stream of channel 235.0.0.51 to the VLAN100 where Host A is located.
Step 4. Checking Querier election result and IGMP group formation on Switch B:
Result: Switch B is elected as the Querier.
IGMP group formation on Switch B:
Step 5. Checking multicast flow forwarding on Switch C:
Switch C, the PIM Assert Winner, forwards the data stream of channel 235.0.0.52 to Host C.
You have finish all the configuration of PIM-DM via Omada Controller, it should work properly now.
Get to know more details of each function and configuration please go to Download Center to download the manual of your product.
Is this faq useful?
Your feedback helps improve this site.
TP-Link Community
Still need help? Search for answers, ask questions, and get help from TP-Link experts and other users around the world.