[c-nsp] Multicast on a 6500 running ios

[Tim Stevenson]

With IGMP snooping disabled, we will just flood to every port. Maybe 
that's fine w/you, depends on the application.

In any case, you can use snooping querier by configuring an SVI with 
the querier & an IP address, but leaving the interface in the "shut" 
state, preventing any L3 switching happening on that VLAN. The 
querier will still work in this case.

Tim

At 04:08 PM 1/29/2007 +0100, Jensen Geir (UmoeIKT) averred:
>Thanks Jeff,
>
>We switched off the igmp snooping, and now it works fine.
>
>Geir
>-----Original Message-----
>From: Jeff Tantsura [mailto:jeff.tantsura at sscplus.nl]
>Sent: 29. januar 2007 14:07
>To: Jensen Geir (UmoeIKT); cisco-nsp at puck.nether.net
>Subject: RE: [c-nsp] Multicast on a 6500 running ios
>
>Hi Geir,
>
>Yes, unfortunately it is.
>If you have got only 2 ports within multicast VLAN - disabling igmp
>snooping
>wouldn't really trouble you.
>If there are more ports and you'd like not to broadcast every multicast
>packet you could configure static CAM entry like:
>
>mac-address-table static 0100.5exx.xxxx vlan y interface
>gigabitethernet a/b gigabitethernet c/c
>
>When you configure a static entry, enter the disable-snooping keyword to
>prevent multicast traffic addressed to the statically configured
>multicast
>MAC address from also being sent to other ports in the same VLAN.
>
>Try to read RFC4541 :)
>
>Hope this helps,
>Jeff
>
> > -----Original Message-----
> > From: Jensen Geir (UmoeIKT) [mailto:Geir.Jensen at umoeikt.no]
> > Sent: maandag 29 januari 2007 13:46
> > To: Jeff Tantsura; cisco-nsp at puck.nether.net
> > Subject: RE: [c-nsp] Multicast on a 6500 running ios
> >
> > Thanks Jeff,
> >
> > I believe the "ip igmp snooping querier" requires a VLAN interface
>with
> > an ip address? For this particular vlan,  we want the 6500 to operate
>at
> > layer2.
> >
> > Does this imply that the 6500 (running ios) can't use igmp snooping
>when
> > it's being used as a layer2-switch?
> >
> > I'll try to disable igmp snooping.
> >
> > Geir
> >
> >
> > -----Original Message-----
> > From: Jeff Tantsura [mailto:jeff.tantsura at sscplus.nl]
> > Sent: 29. januar 2007 13:09
> > To: Jensen Geir (UmoeIKT); cisco-nsp at puck.nether.net
> > Subject: RE: [c-nsp] Multicast on a 6500 running ios
> >
> > Hi,
> >
> > You should either enable igmp snooping querier on this VLAN or disable
> > igmp
> > snooping.
> >
> >
> > To enable the IGMP querier in a VLAN, perform this task:
> > Step 1 Switch(config)# interface vlan vlan_ID
> > Step 2 Switch(config-if)#ip igmp snooping querier Enable the IGMP
> > querier.
> >
> > Jeff
> >
> > > -----Original Message-----
> > > From: cisco-nsp-bounces at puck.nether.net [mailto:cisco-nsp-
> > > bounces at puck.nether.net] On Behalf Of Jensen Geir (UmoeIKT)
> > > Sent: maandag 29 januari 2007 12:00
> > > To: cisco-nsp at puck.nether.net
> > > Subject: [c-nsp] Multicast on a 6500 running ios
> > >
> > > Hi there,
> > >
> > >
> > >
> > > What's required for a 6500 (running ios) to forward multicast
>traffic
> > > when the multicast sender and receivers are on the same vlan? (PIM
>is
> > > not configured because the multicast traffic does not need to be
> > routed.
> > > )
> > >
> > >
> > >
> > > Since IGMP is enabled by default,  I expected this to work out of
>the
> > > box. But it didn't..
> > >
> > >
> > >
> > > Thanks, appreciate any responses ;)
> > >
> > >
> > >
> > > Geir
> > >
> > >
> > >
> > >
> > > _______________________________________________
> > > cisco-nsp mailing list  cisco-nsp at puck.nether.net
> > > https://puck.nether.net/mailman/listinfo/cisco-nsp
> > > archive at http://puck.nether.net/pipermail/cisco-nsp/
> >
> >
> >
>
>
>
>
>_______________________________________________
>cisco-nsp mailing list  cisco-nsp at puck.nether.net
>https://puck.nether.net/mailman/listinfo/cisco-nsp
>archive at http://puck.nether.net/pipermail/cisco-nsp/



Tim Stevenson, tstevens at cisco.com
Routing & Switching CCIE #5561
Technical Marketing Engineer, Catalyst 6500
Cisco Systems, http://www.cisco.com
IP Phone: 408-526-6759
********************************************************
The contents of this message may be *Cisco Confidential*
and are intended for the specified recipients only.