All things related to multicast

[Gordon Rogier <>]

I do not know if it is "learning" the router port.... it's current
behavior show would seem to indicate (i think) yes, as my recollection is
that only the "router" port is getting local source traffic.  however, the
3300 gives you absolutely _no_ diagnositic insights to mcast operation...
just the ability to turn it on or off... and no ability to hard configure
the router port.  again, 0x12 packets work just fine and get to the
router, it appears to be type 0x16 sensitive.

--*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*-*--
Gordon Rogier                        

            
Network Engineer                     785-864-0381wk 785-550-4468 cell
Great Plains Network                 785-864-9330 FAX

On Thu, 13 Jul 2000, Philip Pishioneri wrote:
> Doe it "learn" the port of the multicast router?  If so, is it correct
> and/or can you manually set it to see if that changes the behavior?
> 
> -Phil
> 
> Gordon Rogier wrote:
> > 
> > On Thu, 13 Jul 2000, Wallace, Steven S wrote:
> > > It's my understanding that all IGMP snooping Ethernet switches will not
> > > forward Host Reports to any segment other than to the querier.  This is 
> > > to
> > > insure all members are forced to send host reports, so that the switch 
> > > can
> > > identify all segment that contain members.  I'm not sure if our HP 
> > > switches
> > > send all host reports to the querier or just a period one.
> > 
> > I had considered this, but that is not the basic problem.  I have observed
> > that it is sending the 0x12 type memebership reports just fine.  It just
> > is not forwarding the 0x16 type reports.  Again, it appears to me that the
> > 3300 is "eating" all IGMP packets and when it gets a 0x16 type packet, it
> > just does not know how to handle it, so it drops it.
> > 
> > :grogier.
>