Hi, Have a Cisco SGE2010p small business switch. I am trying to get multicast IGMP working with it, but the switch insists on flooding traffic to every single port.
* ticked the box Enable IGMP snooping
* ticked the box Enable Bridge multicast filtering (dont really know exactly what this does)
* set ports to Filtering on Unregistered Multicast - this fixed the port flood and allowed existing multicast to finish, but didn't allow new multicast sessions to start. Not sure if should be filtered or forwarded. (forwarding is for another switch connection????)
* have (i hope) enabled igmp querier on the switch as there is no mcast router
Any ideas or suggestions on what else needs to be done (or exactly what the above options do) very greatly appreciated.
sw1# sh ip igmp snooping int 1
IGMP Snooping is globaly enabled
IGMP Snooping is enabled on VLAN 1
IGMP Snooping admin: enabled
Routers IGMP version: 3
Groups that are in IGMP version 2 compatibility mode:
Groups that are in IGMP version 1 compatibility mode:
IGMP snooping querier admin: enabled
IGMP snooping querier oper: disabled
IGMP snooping querier address admin:
IGMP snooping querier address oper: 192.168.10.9
IGMP snooping querier admin version: 3
IGMP host timeout is 260 sec
IGMP Immediate leave is disabled. IGMP leave timeout is 10 sec
IGMP mrouter timeout is 300 sec
Automatic learning of multicast router ports is enabled
The problem was that Windows deployment services was using multicast address 239.0.0.x which conflicts from a layer 2 perspective mac-ethernet multicast address of 224.0.0.x. Therefore the switch had no alternative but to send to all ports. Changed the multicast address to something a bit higher (239.45.33.x) fixed the problem working nicely. Seems a strange default to have for a multicasting program, perhaps the really expensive switches that microsoft can afford can process multicast based on the l3 address and not do mac table groups.
You could tell it was flooding because all lights flashed together and counters for ports went up that werent part of the session.
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...