08-26-2019 01:57 PM
Hi Everyone,
My first time configuring mulitcast, and it is not working.. I'd like to understand why and how to fix it.
I have one host that get multicast traffic - 10.95108.142, and I was asked for two other hosts to get the same traffic so I used SSM, ver 3. The configuration before I changed was as follows:
Running config:
ip multicast-routing
ip multicast group-range Willis_Lab
!
!
ip pim rp-address 10.95.108.254 Wilis_Lab
ip pim snooping
!
!
Interface Config:
interface vlan 111
ip address 172.25.111.254 255.255.255.0 secondary
ip address 10.95.108.254 255.255.255.0
ip helper-address 10.95.102.139
ip helper-address 10.95.102.247
no ip redirects
ip flow ingress
ip pim sparse-mode
ip pim snooping
!
!
interface vlan 601
ip address 10.95.116.126 255.255.255.128
ip pim sparse-mode
ip igmp version 3
end
I need IP addresses 10.95.108.141 and 10.95.108.181 to display in the mrouting table OR to join the multicast group. IP address 10.95.108.142 currently shows under this config:
(10.95.108.142, 239.20.21.60), 03:17:25/00:02:52, flags: sTI
Incoming interface: Vlan111, RPF nbr 0.0.0.0, RPF-MFD
Outgoing interface list:
Vlan601, Forward/Sparse, 03:17:25/00:02:40, H
For all three IPs, I have configured the following only adding a few lines because of most config already done:
Running config:
ip pim ssm range Willis_Lab
!
!
interface Config:
interface vlan 111
ip address 172.25.111.254 255.255.255.0 secondary
ip address 10.95.108.254 255.255.255.0
ip helper-address 10.95.102.139
ip helper-address 10.95.102.247
no ip redirects
ip flow ingress
ip pim sparse-mode
ip pim snooping
ip igmp version 3
!
!
interface vlan 601
ip address 10.95.116.126 255.255.255.128
ip pim sparse-mode
ip igmp version 3
Ip address still shows under "sh ip mroute" after this added config, but it does not display .141 and .181:
(10.95.108.142, 239.20.21.60), 03:17:25/00:02:52, flags: sTI
Incoming interface: Vlan111, RPF nbr 0.0.0.0, RPF-MFD
Outgoing interface list:
Vlan601, Forward/Sparse, 03:17:25/00:02:40, H
Netstat is shown packets being sent to the multicast address from 10.95.108.141.
Regards and thank you for the help
Solved! Go to Solution.
08-27-2019 11:42 PM
Hello,
try to see if the ip igmp static-group command is supported. it is an alternative to the ip igmp join-group command
Hope to help
Giuseppe
08-27-2019 02:26 AM
Hello devdurha,
it is not clear to me if these two additional addresses are receivers or sources.
>> I need IP addresses 10.95.108.141 and 10.95.108.181 to display in the mrouting table OR to join the multicast group
if they are receivers it is normal they do not appear in mroute table.
>>
(10.95.108.142, 239.20.21.60), 03:17:25/00:02:52, flags: sTI
Incoming interface: Vlan111, RPF nbr 0.0.0.0, RPF-MFD
Outgoing interface list:
Vlan601, Forward/Sparse, 03:17:25/00:02:40, H
Netstat is shown packets being sent to the multicast address from 10.95.108.141.
Some end device must make an IGMPv3 report asking to receive traffic for multicast address 239.20.21.60 with Include section = 10.95.108.141.
By the way, remove ip pim snooping command because the SVI Vlan111 is running PIM.
Hope to help
Giuseppe
08-27-2019 10:23 AM
Hi Giuseppe Larosa,
.141 and.181 are sources.
Okay, I'll look into - "Some end device must make an IGMPv3 report asking to receive traffic for multicast address 239.20.21.60 with Include section = 10.95.108.141," as a solution and remove pim snooping. If this does the trick, I'll mark as the solution.
Regards,
08-27-2019 04:10 PM
It seems that after I looked into IGMv3 more to have more than one source; I will need to use ip join-group ***multicast address source x.x.x.141. for a host stack, But I don't currently have the right IOS feature.
Thanks,
08-27-2019 11:42 PM
Hello,
try to see if the ip igmp static-group command is supported. it is an alternative to the ip igmp join-group command
Hope to help
Giuseppe
08-28-2019 08:24 AM
Hi Giuseppe,
Ip igmp static-group worked! I now see .141, .181, .142 in mroute showing as source IPs. Thanks for sharing your knowledge!
Regards,
devdurha
08-28-2019 11:39 AM
I added .141, .142 and .181 with ip pim static-group x.x.x.x source .141, etc... and they are showing as source IPs now, but only .142 is working to the target which sits on vlan 601 - ip address 10.95.116.6. The other two are not working. I'm reading notes on static-group config - device 10.95.108.254 is the RP; I don't know the DR right now. currently config below:
Running config:
ip multicast-routing
ip multicast group-range Willis_Lab
ip pim rp-address 10.95.108.254 Willis_Lab
ip pim ssm range Willis_Lab
VLAN interfaces:
interface Vlan601
ip address 10.95.116.126 255.255.255.128 ***Target on this subnet 10.95.116.6***
ip pim dr-priority 100 ***I added to see if fix****
ip pim sparse-mode
ip igmp version 3
interface Vlan111
description Will_Liu's_Lab_C6509-01-10G_Switch
ip address 172.25.111.254 255.255.255.0 secondary
ip address 10.95.108.254 255.255.255.0
ip helper-address 10.95.102.139
ip helper-address 10.95.102.247
no ip redirects
ip flow ingress
ip pim sparse-mode
ip igmp static-group 239.20.21.60 source 10.95.108.141 **added** **Source IPS**
ip igmp static-group 239.20.21.60 source 10.95.108.181 ** added** **Source**
ip igmp static-group 239.20.21.60 source 10.95.108.142 ** added ** **Source**
ip igmp version 3
Show ip mroute:
(10.95.108.181, 239.20.21.60), 03:18:01/stopped, flags: sPTI
Incoming interface: Vlan111, RPF nbr 0.0.0.0, RPF-MFD
Outgoing interface list: Null
(10.95.108.141, 239.20.21.60), 03:18:12/stopped, flags: sPTI
Incoming interface: Vlan111, RPF nbr 0.0.0.0, RPF-MFD
Outgoing interface list: Null
(10.95.108.142, 239.20.21.60), 21:59:59/00:02:58, flags: sTI
Incoming interface: Vlan111, RPF nbr 0.0.0.0, RPF-MFD
Outgoing interface list:
Vlan601, Forward/Sparse, 01:24:09/00:02:16, H
(*, 224.0.1.40), 7w0d/00:02:02, RP 10.95.108.254, flags: SJCL
Incoming interface: Null, RPF nbr 0.0.0.0
Outgoing interface list:
Vlan111, Forward/Sparse, 18w0d/00:02:02
I checked with user, and .141 is forwarding packets.
Not sure if I need to map due to static group, but I'm looking into it.
Thoughts on get 141 and 181 to work?
Regards
08-28-2019 12:09 PM
Hello devdurha,
first of all in SSM there is no use of RP concept, so the RP settings are not relevant.
When we look at the ip mroute table we see the following:
(10.95.108.181, 239.20.21.60), 03:18:01/stopped, flags: sPTI
Incoming interface: Vlan111, RPF nbr 0.0.0.0, RPF-MFD
Outgoing interface list: Null
(10.95.108.141, 239.20.21.60), 03:18:12/stopped, flags: sPTI
Incoming interface: Vlan111, RPF nbr 0.0.0.0, RPF-MFD
Outgoing interface list: Null
(10.95.108.142, 239.20.21.60), 21:59:59/00:02:58, flags: sTI
Incoming interface: Vlan111, RPF nbr 0.0.0.0, RPF-MFD
Outgoing interface list:
Vlan601, Forward/Sparse, 01:24:09/00:02:16, H
The first two entries have the flags sPTI where s = SSM and P = Pruned ,
The third entry has flags sTI and the outgoing interface list is not Null :
>> Outgoing interface list:
Vlan601, Forward/Sparse, 01:24:09/00:02:16, H
There is a reicever in Vlan 601 that sends out IGMPv3 reports for group G=239.20.21.60 and include source S= 10.95.108.142.
As a result of this the stream is received on Vlan 111 and sent out Vlan 601 this entry is in forwarding state since 01:24:09 ago.
How to make the other two entries to become forwarding ?
The OIL must be not NULL ====>>>> move the ip igmp static-groups commands under SVI Vlan 601.
This should be enough to make the entries to become Forwarding and the P flag to be removed.
Now, you have the ip igmp static-group configured under SVI vlan 111 that is the same interface that connects to the multicast sources. This is the reason why OIL list is null.
Hope to help
Giuseppe
08-28-2019 12:49 PM
Hey,
So remove ip igmp static-group configured under SVI vlan 111 then configure under SVI Vlan 601?
Thanks!
08-29-2019 10:06 AM
Done! Thanks again Giuseppe!
Regards,
08-29-2019 10:10 AM
Hello,
yes the right change is to move the igmp static-group commands under SVI 601 to have non null OIL for all three sources.
Best Regards
Giuseppe
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide