And here is a thread discussion IGMP snooping - which is not IGMP routing on 6024 but rather how L2 switches help with IGMP operation. You may also need to be aware of this if you need to setup IGMP snooping on your L2 switches:
Thanks for the reply and I apologies for the random question. After looking through the documentations I still can route multicast traffic from one VLAN to another
Hi LesFrampton, I created your topology in the lab and tested multicast across both Vlans and it worked fine. Please have a look at the configs and compare them to your own.
Multicast Server is attached to 3424A Eth1 on Vlan 100. Eth24 is a Trunk to 6024 on both 3424 switches. On 3424B Client on Eth1 Vlan 100 and Client on Eth2 Vlan 101 both receiving multicast transmisson.
Hi Toeside, I've applied you config to my setup and noticed that you have spanned Vlan 100 (video Server LAN) across all switch which tells me it working a Layer 2 and not actually routing across the 6024F. When I patch the client into E1 VLAN 100 on 3424B it works but then patch the client into E2 VLAN 101 on 3424B it fails.
I want the 6024F to route all multicast traffic when it leaves VLAN 100 using the DVMRP to VLAN 101. The 3424b switch should only have Vlan 101 configured and trunked to the 6024F
What I'm trying to do.
client connect to vlan101 on switch 3424b
Start VLC player and point to 224.1.1.150
Join the multicast group using IGMP on 6024F
6024F then routes the Multicast traffice to group 224.1.1.150 on the 3424A
The source is in vlan 100 on the 3424A, streaming a DVD to Multicast group 224.1.1.150
Yes I applied the stream across both Vlans but the routing does occur in the 6024. I had a client connected to both E1 and E2 on the 3424B, with E2 being in Vlan 101 (separate subnet), where both clients received the multicast traffic.
This morning I removed Vlan 100 from the Trunk on 3424B (E24) to 6024 and multicast traffic still streamed from server which is located in Vlan 100.
I know this is stating the obvious but could you check the gateways on your clients and server, they should be the same as the Vlan Ip addresses on the 6024, also the client should be able to ping the server. I'm using Microsoft Media Services to stream the video but will try VLC.....
Hi Toeside, I really appreciate your help - config's attached. I checked the IP connectivity end to end server is 172.16.100.100, Client 172.16.101.100, the gateways are .254 respectively
I've also just experienced some problems with getting VLC to work in both Vlans with the Multicast setting. It does however work if you select the HTTP option for transmitting within VLC and on the client VLC side input http://192.168.1.10:8080 (server ip).
It will be next week before I can investigate this fully (Public Holiday on Monday:), hopefully the above is also an option for you?
Hi, I'm in the UK so public holiday for me as well :smileyhappy:. When I show IP IGMP groups on the 6024F it see the client request for multicast address but does not see the Source registering with the IGMP...should that happen?
Could you recomend a multicast program that I use to test the config...you mentioned Windows Media Services?
DELL-Cuong N.
1K Posts
0
April 25th, 2006 11:00
lesframpton
7 Posts
0
April 26th, 2006 10:00
Thanks for the reply and I apologies for the random question. After looking through the documentations I still can route multicast traffic from one VLAN to another
Setup
Receiver edge switch router core switch source 224.1.1.10
Client vlan 101 3424 6024F 3424 VideoServer vlan 100
Enabled on both the core and edge switches
Layer 2 links to the 6024
Enable on 6024F
I can’t access the Video server on the core switch when connect to the Edge switch.
lesframpton
7 Posts
0
April 26th, 2006 10:00
Message Edited by lesframpton on 04-26-200606:38 AM
ToeSide
1 Rookie
•
63 Posts
0
April 27th, 2006 14:00
no spanning-tree
bridge multicast filtering
interface ethernet e24
switchport mode trunk
exit
vlan database
vlan 100-101
exit
interface ethernet e1
switchport access vlan 100
exit
interface ethernet e24
switchport trunk allowed vlan add 100
exit
interface ethernet e24
switchport trunk allowed vlan add 101
exit
ip igmp snooping
interface vlan 100
ip igmp snooping
exit
interface vlan 101
ip igmp snooping
exit
interface vlan 100
ip address 192.168.1.200 255.255.255.0
exit
bridge multicast filtering
interface ethernet e24
switchport mode trunk
exit
vlan database
vlan 100-101
exit
interface ethernet e1
switchport access vlan 100
exit
interface ethernet e24
switchport trunk allowed vlan add 100
exit
interface ethernet e2
switchport access vlan 101
exit
interface ethernet e24
switchport trunk allowed vlan add 101
exit
ip igmp snooping
interface vlan 100
ip igmp snooping
exit
interface vlan 101
ip igmp snooping
exit
interface vlan 100
ip address 192.168.1.201 255.255.255.0
exit
bridge multicast filtering
interface range ethernet g(23-24)
switchport mode trunk
exit
vlan database
vlan 100-101
exit
interface range ethernet g(23-24)
switchport trunk allowed vlan add 100
exit
interface range ethernet g(23-24)
switchport trunk allowed vlan add 101
exit
ip igmp snooping
interface vlan 100
ip igmp snooping
exit
interface vlan 101
ip igmp snooping
exit
interface vlan 100
ip address 192.168.1.254 255.255.255.0
exit
interface vlan 101
ip address 10.1.1.254 255.255.255.0
exit
ip multicast-routing
interface vlan 100
ip dvmrp
exit
interface vlan 101
ip dvmrp
exit
interface vlan 100
ip igmp
exit
interface vlan 101
ip igmp
exit
lesframpton
7 Posts
0
April 28th, 2006 07:00
Hi Toeside, I've applied you config to my setup and noticed that you have spanned Vlan 100 (video Server LAN) across all switch which tells me it working a Layer 2 and not actually routing across the 6024F. When I patch the client into E1 VLAN 100 on 3424B it works but then patch the client into E2 VLAN 101 on 3424B it fails.
I want the 6024F to route all multicast traffic when it leaves VLAN 100 using the DVMRP to VLAN 101. The 3424b switch should only have Vlan 101 configured and trunked to the 6024F
What I'm trying to do.
ToeSide
1 Rookie
•
63 Posts
0
April 28th, 2006 07:00
lesframpton
7 Posts
0
April 28th, 2006 08:00
bridge multicast filtering
interface ethernet e24
switchport mode trunk
exit
vlan database
vlan 100-101
exit
interface ethernet e1
switchport access vlan 100
exit
interface ethernet e24
switchport trunk allowed vlan add 100
exit
interface ethernet e24
switchport trunk allowed vlan add 101
exit
ip igmp snooping
interface vlan 100
ip igmp snooping
exit
interface vlan 101
ip igmp snooping
exit
interface vlan 100
ip address 172.16.100.200 255.255.255.0
exit
no spanning-tree
bridge multicast filtering
interface ethernet e24
switchport mode trunk
exit
vlan database
vlan 100-101
exit
interface ethernet e1
switchport access vlan 100
exit
interface ethernet e24
switchport trunk allowed vlan add 100
exit
interface ethernet e2
switchport access vlan 101
exit
interface ethernet e24
switchport trunk allowed vlan add 101
exit
ip igmp snooping
interface vlan 100
ip igmp snooping
exit
interface vlan 101
ip igmp snooping
exit
interface vlan 100
ip address 172.16.100.200 255.255.255.0
exit
Router Configuration
-----------------------------
bridge multicast filtering
interface range ethernet g(23-24)
switchport mode trunk
exit
vlan database
vlan 100-101
exit
interface range ethernet g(23-24)
switchport trunk allowed vlan add 100
exit
interface range ethernet g(23-24)
switchport trunk allowed vlan add 101
exit
ip igmp snooping
interface vlan 100
ip igmp snooping
exit
interface vlan 101
ip igmp snooping
exit
interface vlan 100
ip address 172.16.100.254 255.255.255.0
exit
interface vlan 101
ip address 172.16.101.254 255.255.255.0
exit
ip multicast-routing
interface vlan 100
ip dvmrp
exit
interface vlan 101
ip dvmrp
ToeSide
1 Rookie
•
63 Posts
0
April 28th, 2006 08:00
Hi Les,
I've also just experienced some problems with getting VLC to work in both Vlans with the Multicast setting. It does however work if you select the HTTP option for transmitting within VLC and on the client VLC side input http://192.168.1.10:8080 (server ip).
It will be next week before I can investigate this fully (Public Holiday on Monday:), hopefully the above is also an option for you?
lesframpton
7 Posts
0
April 28th, 2006 09:00