Unsolved
This post is more than 5 years old
5 Posts
0
22882
September 10th, 2008 05:00
Multicast 6224 pim sm mode
Multicast in theory seems relatively easy. Why in practice then is it always complex?
We have a 6224 unit that connects to three Dell servers running CentOS.
A Dell server can send multicast traffic and the other two cann receive it, ut the 6224 switch doesn't show that there are any groups subscribed.
The real problem is that we need to subscribe to 4 data feeds, the source and the 3 Dell servers are connected via vlan 3. The traffic I need to listen to is as follows:-
239.142.2.1 port 17503
239.142.2.2 port 17513
239.142.2.3 port 17533
239.142.2.4 port 17543
We have been given a rendezvous point of 172.201.52.45. The upstream device is most likely a firewall. Others have removed the switch and verified the multicast traffic is being received (haven't found out what device or mechanism is being used yet).
As the switch is in a different continent to us we can't do any physical jobs to help determine the issue.
!Current Configuration:
!System Description "Dell 24 Port Gigabit Ethernet, 2.1.0.13, VxWorks5.5.1"
!System Software Version 2.1.0.13
!
configure
vlan database
vlan 2-3
exit
hostname "sw1"
stack
member 1 1
member 2 1
exit
ip address 172.19.128.241 255.255.255.0
ip default-gateway 172.19.128.254
ip domain-name xxx.com
ip name-server 172.19.128.251
ip name-server 172.19.128.252
logging 172.19.128.252
exit
ip routing
ip route 172.201.0.0 255.255.0.0 172.201.178.201
ip igmp
ip pimsm
ip pimsm staticrp 172.201.52.45 239.142.0.0 255.255.0.0
ip multicast staticroute 172.201.52.45 255.255.255.255 172.201.178.201 0 vlan 3
ip multicast staticroute 172.201.219.10 255.255.255.255 172.201.178.201 0 vlan 3
ip multicast
interface vlan 2
name "BCI"
exit
interface vlan 3
bridge multicast forward-all
bridge multicast address 0100.5E0E.0201
bridge multicast address 0100.5E0E.0202
bridge multicast address 0100.5E0E.0203
bridge multicast address 0100.5E0E.0204
name "BDJ"
routing
ip igmp
ip pimsm mode
ip mcast boundary 239.142.0.0 255.255.0.0
exit
ip ssh server
bridge multicast filtering
ip igmp snooping
But we never see any multicast traffic on the servers and the switch never it says it has subscribed to any mulitcast groups, as can be seen below.
sw1#show ip igmp groups vlan 3
IP Address..................................... 0.0.0.0
Subnet Mask.................................... 0.0.0.0
Interface Mode................................. Enable
sw1#show ip igmp groups ?
vlan Display IP VLAN Routing information.
sw1#show ip igmp interface vlan 3
Interface...................................... vlan3
IGMP Admin Mode................................ Enable
Interface Mode................................. Enable
IGMP Version................................... 3
Query Interval (secs).......................... 125
Query Max Response Time (1/10 of a second)..... 100
Robustness..................................... 2
Startup Query Interval (secs) ................. 31
Startup Query Count............................ 2
Last Member Query Interval (1/10 of a second).. 10
Last Member Query Count........................ 2
sw1#show ip igmp
IGMP Admin Mode................................ Enable
Router Alert Required.......................... False
IGMP INTERFACE STATUS
Interface Interface Mode Protocol State
--------- --------------- ---------------
vlan 3 Enable Non-Operational
So what is the definitive way to setup and diagnose mulitcast issues on these switches ?
sentinel-master
345 Posts
0
September 10th, 2008 21:00
Its strange that you are not seeing IGMP joins, because you should be at least seeing the clients or "recievers" trying to JOIn the group.
In your config you have entered "L3 unicast" addresses, instead of the Multicast group address......this would impact the Reverse Path Check (RPF)....and stream to fail.....but I would have expected a client/PC to join the group and then get no multicast data.
ip multicast staticroute 172.201.52.45 255.255.255.255 172.201.178.201 0 vlan 3
ip multicast staticroute 172.201.219.10 255.255.255.255 172.201.178.201 0 vlan 3
Should become
ip multicast staticroute 239.142.2.0 255.255.255.0 172.201.178.201 0 vlan 3
Let me know how you get on :
flare04
5 Posts
0
September 10th, 2008 23:00
Hi,
Thanks for your response. I've changed the static routers as you have suggested
ip routing
ip route 172.201.0.0 255.255.0.0 172.201.178.201
ip igmp
ip pimsm
ip pimsm staticrp 172.201.52.45 239.142.0.0 255.255.0.0
ip multicast staticroute 239.142.2.0 255.255.255.0 172.201.178.201 0 vlan 3
ip multicast
At the moment there is no change in that we still receive no mulitcast traffic and nothing indicates that a client has joined a group.
Thanks
cerbera_a84f2d
176 Posts
0
September 14th, 2008 22:00
Try enabling the MCast querier for the two VLANs
ip igmp snooping querier
flare04
5 Posts
0
September 15th, 2008 06:00
Hi,
I've applied the configuration that you suggested. Still no output.
I do have a copy of a partial working config from a cisco router. Would that help if I posted this ?
Thanks
sentinel-master
345 Posts
0
September 20th, 2008 13:00
You already have IGMP Snooping active, but as I said before couldn't see any Join stats...its almost like your Client VLAN PC's are not requesting to join the mulicast group.
Yes paste the Cisco config in case it highlights a difference in routes......one thing a Cisco router can do is statically join a group on behalf of the client PC's.....so it might prove/disprove that theory at least.