Aruba & ProVision-based
Showing results for 
Search instead for 
Did you mean: 

IGMP configuration and VLAN tagging

Occasional Contributor

IGMP configuration and VLAN tagging

Currently, there is a "feed" server that initiates an IGMP Multicast stream that a number of "broadcast" servers listen to. They are all curently on the same ProCurve 5406zl recently upgraded to firmware version K.15.07.008. The feed and broadcast servers are on the same VLAN. Their interfaces are untagged on that VLAN. Everything is working properly.


I have recently implemented a blade chassis with servers running VMware connected through a couple of Cisco switches. There is a trunk port between the ProCurve and each of the Cisco switches. The interface is untagged on VLAN 1. (Yes, all the regular network traffic uses VLAN 1 - something that I will redesign later). I need the feed server (Multicast Server) to deliver the IGMP broadcast to a server on VMware. When I add a broadcast server to VMware, it sees the traffic for about 3 minutes and then stops. My initial questions are about VLAN tagging.


Should the interface that the feed servre connects to be taged on VLAN 10 instead of untagged on VLAN 10?


The trunk connections to the Cisco traffic need to cary VLAN 10 traffic. Can I add "tagged VLAN 10" without interupting the function of the "untagged VLAN 1" traffic?


I'm attaching a Visio diagram.


Any help would be greatly appreciated!


Esteemed Contributor

Re: IGMP configuration and VLAN tagging

I'm not an expert in multicast, but i'll try to answer some of your questions.

  • Unless you have specifically configured the feed server for tagged VLANs, it should definitely not be tagged.  The switch will ensure that all tagged and untagged ports are in the same layer 2 broadcast domain.
  • According to your Visio diagram, Trk1 & Trk2 are already tagged on VLAN 10.  You can add and removed tagged VLANs at any without affecting the untagged VLAN.
  • It's always a good idea to select an appropriately-placed switch as the IGMP querier.  You don't need an IP address configured in order to do this.

Keep in mind that if your VMware server has a VM that needs to receive multicast traffic in VLAN 10, then you will need to have VLAN 10 tagged on the server uplink, and also create a port group for VLAN 10 to which you connect the client VM.


Hope that helps you towards the solution.