Hi Michele,
So STP didn't protect you and you faced the loop.
okay, but how is this a loop from the perspective of the switches in the
higher levels? The Procurve sees packets coming in from the same port
where they were sent out. Isn't that by definition not a loop?
When the loop
Hi David,
Once you draw your diagram correctly you'll see what you're up against
(and it ain't pretty).
Juniper MX480 no RSTP
||
ae0
||
Juniper EX4550 VC RSTP bridge id 0
||
ae0
||
Juniper EX4200 VC RSTP
Hello,
I think we are missing some important details here.
AFAIK, in order to detect MAC moves, the port must be in a
bridge-domain/VPLS instance.
So Your MX480 ae0 must be a L2/bridged port, not a L3/routed one.
So the question would be - are there any other ports on this MX480 in
same
On 8-Nov-2014 14:56:27 (+0200), Jeff Meyers wrote:
alright, but why would the ProCurve and everything above care? Isn't the
loop only inside the Windows Host since from the perspective of the
ProCurve, packets come in the same interface where they were sent out?
Furthermore, what is required
:( I thought Juniper was trying to get more business...
--Original Message--
From: Skeeve Stevens
Sender: juniper-nsp
To: Tim Jackson
Cc: juniper-nsp@puck.nether.net
Subject: Re: [j-nsp] EX3300/4300 Switch MPLS CCC Support
Sent: Nov 7, 2014 23:44
I was referring to OSPF, IPv6, etc..
On 9-Nov-2014 00:59:34 (+0200), Patrick Okui wrote:
so ...
conf t
fault-finder broadcast-storm
sorry should be fault-finder broadcast-storm sensitivity high
--
patrick
signature.asc
Description: OpenPGP digital signature
___
6 matches
Mail list logo