03-11-2025 02:12 AM
I need help to make a multicast network work. I have 2 IE5000 routers connected to each other on 2 ports (24 and 26) which are configured the same:
interface TenGigabitEthernet1/xx
switchport trunk allowed vlan 14,410-414,418
switchport mode trunk
channel-group 10 mode desirable
I also have a port-channel configured:
interface Port-channel10
switchport trunk allowed vlan 14,410-414,418
switchport mode trunk
On one port, I have a device connected that receives multicast traffic. This traffic is reaching me but I am not sending it. The VLAN where I receive the multicast is:
interface Vlan14
ip address 192.168.14.252 255.255.255.0
ip pim dense-mode
standby version 2
standby 19 ip 192.168.14.254
standby 19 priority 150
standby 19 preempt
And I send everything through a link via the VLANs:
interface Vlan418
ip address 10.211.8.252 255.255.255.0
ip pim dense-mode
standby version 2
standby 18 ip 10.211.8.254
standby 18 priority 150
standby 18 preempt
I have a route configured:
ip route 0.0.0.0 0.0.0.0 10.211.8.1
On the other router, I have the same configuration:
interface Vlan14
ip address 192.168.14.251 255.255.255.0
ip pim dense-mode
standby version 2
standby 19 ip 192.168.14.254
interface Vlan418
ip address 10.211.8.251 255.255.255.0
ip pim dense-mode
standby version 2
standby 18 ip 10.211.8.254
standby 18 preempt
ip route 0.0.0.0 0.0.0.0 10.211.8.1
All unicast traffic works without issues.
03-18-2025 10:28 AM
Hello @Fernandomunoz81 ,
you can check the state of multicast using commands like
show ip mroute
show ip mroute active
show ip pim neighbors
show ip igmp groups
You are trying to use IP dense mode have you enabled PIM under each SVI of interest ?
what is the source of the multicast stream ?
show ip rpf <source-address>
if the stream arrives on the wrong interface the packets are dropped
You have PIM enabled on at least two different SVIs this can be part of the issue.
Hope to help
Giuseppe
03-19-2025 03:46 AM
Hello @Giuseppe Larosa ,
Previously, I had configured in the VLAN 418 the IP address 10.211.8.250 on the main router and 10.211.8.251 on the other router. This didn't route the multicast, and the solution came when we changed the IP address on the main router's VLAN to 10.211.8.252 (a higher IP address than the other router; I wasn't entirely sure about these IP priorities).
Later, I made some changes to the network to run some tests, and when we returned to the situation I mentioned at the beginning, it worked fine. The solution was to perform a "clear IP mroute..." so some routes must have been saved in memory from when I was running the tests.
Thanks
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