On 10/12/2010 09:46 PM, Gert Doering wrote:
Hi,
On Tue, Oct 12, 2010 at 02:59:28PM -0500, christopher.mar...@usc-bt.com wrote:
The switch listens to the following messages in order to detect router ports
with IGMP snooping:
· IGMP Membership query send to 01?00?5e?00?00?01
· PIMv1 hello send
Hi,
On Wed, Oct 13, 2010 at 08:18:47AM +0100, Phil Mayers wrote:
On 10/12/2010 09:46 PM, Gert Doering wrote:
On Tue, Oct 12, 2010 at 02:59:28PM -0500, christopher.mar...@usc-bt.com
wrote:
The switch listens to the following messages in order to detect router
ports with IGMP snooping:
·
On 10/13/2010 08:37 AM, Gert Doering wrote:
Hi,
On Wed, Oct 13, 2010 at 08:18:47AM +0100, Phil Mayers wrote:
On 10/12/2010 09:46 PM, Gert Doering wrote:
On Tue, Oct 12, 2010 at 02:59:28PM -0500, christopher.mar...@usc-bt.com
wrote:
The switch listens to the following messages in order to
On 10/13/2010 3:41 AM, Phil Mayers wrote:
On 10/13/2010 08:37 AM, Gert Doering wrote:
Hi,
On Wed, Oct 13, 2010 at 08:18:47AM +0100, Phil Mayers wrote:
On 10/12/2010 09:46 PM, Gert Doering wrote:
On Tue, Oct 12, 2010 at 02:59:28PM -0500,
christopher.mar...@usc-bt.com
wrote:
The switch
On 13/10/10 13:32, Rob Taylor wrote:
Now I must admit: when I think about it, I don't know what model the
layer2 switch in question was; it may not even have been a Cisco (this
was some time back) in which case Christopher may also be right ;o)
Christopher is right here ... in this case,
There is a document on cisco#39;s site regarding how IGMP snooping breaks
multicast in typical LAN environments. I don#39;t have the link handy, but it
should be googleable. Effectively, the issue is that the switches do not have
a way to properly identify the mrouter port, and end up cutting
On Wed, 2010-10-13 at 06:08 -0700, David Barak wrote:
There is a document on cisco#39;s site regarding how IGMP snooping
breaks multicast in typical LAN environments. I don#39;t have the
link handy, but it should be googleable. Effectively, the issue is
that the switches do not have a way to
Peter said:
On Wed, 2010-10-13 at 06:08 -0700, David Barak wrote:
There is a document on cisco#39;s site regarding how IGMP snooping
breaks multicast in typical LAN environments. I don#39;t have the
link handy, but it should be googleable. Effectively, the issue is
that the switches do
It sounds like you might be describing a case where
- IGMP snooping is enabled on a switch
- There's no IGMP querier on the VLAN
If so, then we're in agreement. That doesn't work (though it may appear to
work at first).
There's a fourth option on some L2 switching platforms: enable an
Thanks again for everyone's help on this matter, and sorry about the quoting
problems from yesterday...
I think this is almost working. I was hoping to ask about one more point on
this. The 8540 that is part of this equation is set up for IRB. The vlan that
the servers are on is bridged
That makes sense... igmp snooping seems to be enabled, but it still isn't
working. Is there something else that needs to be done to the 2960?
Steve Pfister
Technical Coordinator,
The Office of Information Technology
Dayton Public Schools
115 S. Ludlow St.
Dayton, OH 45402
Office (937)
On Tue, Oct 12, 2010 at 8:50 AM, Steven Pfister spfis...@dps.k12.oh.us wrote:
That makes sense... igmp snooping seems to be enabled, but it still isn't
working. Is there something else that needs to be done to the 2960?
Do you know if this is source-specific multicast? If so, your
layer-two
Hi,
On Tue, Oct 12, 2010 at 10:50:09AM -0400, Steven Pfister wrote:
That makes sense... igmp snooping seems to be enabled, but it still isn't
working. Is there something else that needs to be done to the 2960?
Since there is no IGMP between routers, IGMP snooping can not be helpful
here.
On Tue, 2010-10-12 at 17:08 +0200, Gert Doering wrote:
On Tue, Oct 12, 2010 at 10:50:09AM -0400, Steven Pfister wrote:
That makes sense... igmp snooping seems to be enabled, but it still
isn't working. Is there something else that needs to be done to the
2960?
Since there is no IGMP
On Tue, Oct 12, 2010 at 11:45 AM, Peter Rathlev pe...@rathlev.dk wrote:
On Tue, 2010-10-12 at 17:08 +0200, Gert Doering wrote:
On Tue, Oct 12, 2010 at 10:50:09AM -0400, Steven Pfister wrote:
That makes sense... igmp snooping seems to be enabled, but it still
isn't working. Is there something
It's not really going router-switch-router... The video encoders are connected
to the 2960, which connects to the 4506 at the remote side. The vendor has
installed the video encoders but I haven't actually been to the remote end to
see them yet. I'm not sure yet if they're still trying to
Hi,
On Tue, Oct 12, 2010 at 07:45:10PM +0200, Peter Rathlev wrote:
I don't know much about multicast, but aren't routed multicast packets
sent as L2 unicast between multicast routers?
No.
I'm just guessing here,
but I don't see why routed multicast traffic would need to have the L2
group
Hi,
*please* fix your quoting. Your top posting makes it very hard to
see what you're referring to, and since you want something, it would
be prudent to make it easy for us to help.
On Tue, Oct 12, 2010 at 02:34:35PM -0400, Steven Pfister wrote:
It's not really going router-switch-router...
On Tue, 2010-10-12 at 21:07 +0200, Gert Doering wrote:
On Tue, Oct 12, 2010 at 07:45:10PM +0200, Peter Rathlev wrote:
but I don't see why routed multicast traffic would need to have the
L2 group bit set.
Well, if you only ever have two routers in a subnet, it doesn't need
to...
But
Hi,
On Tue, Oct 12, 2010 at 09:18:04PM +0200, Peter Rathlev wrote:
On Tue, 2010-10-12 at 21:07 +0200, Gert Doering wrote:
But what if you have 20 routers in a subnet and want the multicast
traffic to be heard by only those 5 that are interested in it?
Ah, of course. Does the switch (e.g.
Gert Doering said:
On Tue, Oct 12, 2010 at 07:45:10PM +0200, Peter Rathlev wrote:
I'm just guessing here,
but I don't see why routed multicast traffic would need to have the L2
group bit set.
Well, if you only ever have two routers in a subnet, it doesn't need to...
But what if you
Hi,
On Tue, Oct 12, 2010 at 02:59:28PM -0500, christopher.mar...@usc-bt.com wrote:
The switch listens to the following messages in order to detect router ports
with IGMP snooping:
· IGMP Membership query send to 01?00?5e?00?00?01
· PIMv1 hello send to 01?00?5e?00?00?02
· PIMv2 hello send to
22 matches
Mail list logo
