I was told PR/677087 but its currently marked as internal so not public
On 02/11/2012, at 11:24 PM, "Billy Sneed" wrote:
> On 11/02/2012 02:21 AM, Luca Salvatore wrote:
>> Confirmed as a bug. AE interfaces flap when master switch in VC reboots.
>> Fixed in 11.4r6 (not released yet) or 12.1
>>
On 11/02/2012 02:21 AM, Luca Salvatore wrote:
Confirmed as a bug. AE interfaces flap when master switch in VC reboots.
Fixed in 11.4r6 (not released yet) or 12.1
Luca
Do you have the PR# by chance, or any info I can read up on at juniper.net?
___
ju
atore
Sent: Thursday, 1 November 2012 7:32 AM
To: Morgan McLean
Cc: juniper-nsp@puck.nether.net
Subject: Re: [j-nsp] How reliable is EX multichassis? 3300 and 8200 switches
I see the 60 sec delay when crashing master. It seems the backup switch takes a
while to notice the master is gone. But my main de
31.10.2012 10:38, joel jaeggli wrote:
> On 10/30/12 5:49 PM, Pavel Lunin wrote:
>> When it comes to ethernet switching, "routing protocols" means what? :)
> spanning-tree/trill/l2vpn/NVO and so on.
Right, but if we get back to the particular case of DC/enterprise core,
consisting of two EX boxes, t
c: juniper-nsp@puck.nether.net
Subject: Re: [j-nsp] How reliable is EX multichassis? 3300 and 8200 switches
I see the 60 sec delay when crashing master. It seems the backup switch takes a
while to notice the master is gone. But my main delay is the fact that my OSPF
neighbours are lost when mast
I see the 60 sec delay when crashing master. It seems the backup switch takes a
while to notice the master is gone. But my main delay is the fact that my OSPF
neighbours are lost when master crashes.
@Doug, nonstop bridging is also configured.
Luca
On 01/11/2012, at 7:25 AM, "Morgan McLean"
m
Did you see the failover times I mentioned? Is that expected timing?
8 seconds using VC-LAG w/ LACP to a third switch when pulling masters power
over 60 seconds when crashing master
Morgan
On Wed, Oct 31, 2012 at 1:20 PM, Doug Hanks wrote:
> Don't forget to configure NSB to help with LACP and
Don't forget to configure NSB to help with LACP and other L2 stuffs.
set ethernet-switching-options nonstop-bridging
On 10/31/12 1:05 PM, "Luca Salvatore" wrote:
>Yes so GRES and NSR is configured am correctly then?
>
>The AE is a VC-lag with one member on each switch.
>
>Luca
>
>On 01/11/2012
Yes so GRES and NSR is configured am correctly then?
The AE is a VC-lag with one member on each switch.
Luca
On 01/11/2012, at 3:56 AM, "Stefan Fouant"
wrote:
> On Oct 31, 2012, at 10:01 AM, Luca Salvatore wrote:
>
>> Yep my mistake.
>> However I do have 'set chassis redundancy graceful-sw
On Oct 31, 2012, at 10:01 AM, Luca Salvatore wrote:
> Yep my mistake.
> However I do have 'set chassis redundancy graceful-switchover' configured as
> well as 'set protocols nonestop-routing'
>
> On 31/10/2012, at 11:24 PM, "Stefan Fouant"
> mailto:sfou...@shortestpathfirst.net>> wrote:
>
> I
ober 2012 4:27 PM
To: Luca Salvatore; Morgan McLean; EXT -
bd...@comlinx.com.au<mailto:bd...@comlinx.com.au>
Cc: juniper-nsp@puck.nether.net<mailto:juniper-nsp@puck.nether.net>
Subject: Re: [j-nsp] How reliable is EX multichassis? 3300 and 8200 switches
Make sure the platform + software
t; To: Luca Salvatore; Morgan McLean; EXT - bd...@comlinx.com.au
> Cc: juniper-nsp@puck.nether.net
> Subject: Re: [j-nsp] How reliable is EX multichassis? 3300 and 8200 switches
>
> Make sure the platform + software + configuration supports GRES + NSR + NSB
> and you're good to go.
>
&
How many vmembers do you have configured on this set?
I've seen serious issues with having trunk ports and a lot of vlans
configured in terms of reconvergence time.
Tim
On 31-10-12 00:06, Morgan McLean wrote:
Can anybody give me an idea regarding typical failover times if the master
in a two s
On 10/30/12 5:49 PM, Pavel Lunin wrote:
"Richard A Steenbergen" wrote:
IMHO multi-chassis boxes are for
people who can't figure out routing protocols
When it comes to ethernet switching, "routing protocols" means what? :)
spanning-tree/trill/l2vpn/NVO and so on.
And the same observation ap
a better config than non-stop routing?
> >>
> >>Luca
> >>
> >>
> >>-Original Message-
> >>From: juniper-nsp-boun...@puck.nether.net
> >>[mailto:juniper-nsp-boun...@puck.nether.net] On Behalf Of Morgan McLean
> &
cLean; EXT - bd...@comlinx.com.au
Cc: juniper-nsp@puck.nether.net
Subject: Re: [j-nsp] How reliable is EX multichassis? 3300 and 8200 switches
Make sure the platform + software + configuration supports GRES + NSR + NSB and
you're good to go.
On 10/30/12 8:58 PM, "Luca Salvatore" wr
--Original Message-
>From: Doug Hanks [mailto:dha...@juniper.net]
>Sent: Wednesday, 31 October 2012 2:42 PM
>To: Luca Salvatore; Morgan McLean; EXT - bd...@comlinx.com.au
>Cc: juniper-nsp@puck.nether.net
>Subject: Re: [j-nsp] How reliable is EX multichassis? 3300 and 8200
>switches
>
r.net
Subject: Re: [j-nsp] How reliable is EX multichassis? 3300 and 8200 switches
GR is mutually exclusive with NSR.
You want NSR.
On 10/30/12 5:44 PM, "Luca Salvatore" wrote:
>I'm just playing around with this now since I have a few new EX
>switches not in product
essage-
>From: juniper-nsp-boun...@puck.nether.net
>[mailto:juniper-nsp-boun...@puck.nether.net] On Behalf Of Morgan McLean
>Sent: Wednesday, 31 October 2012 11:00 AM
>To: Ben Dale
>Cc: juniper-nsp@puck.nether.net
>Subject: Re: [j-nsp] How reliable is EX multichassis? 3300
Seriously, routing protocol ain't my problem here.
Sent from my iPhone
On Oct 30, 2012, at 5:49 PM, Pavel Lunin wrote:
> "Richard A Steenbergen" wrote:
>
>> IMHO multi-chassis boxes are for
>> people who can't figure out routing protocols
>
> When it comes to ethernet switching, "routing pr
"Richard A Steenbergen" wrote:
>IMHO multi-chassis boxes are for
> people who can't figure out routing protocols
When it comes to ethernet switching, "routing protocols" means what? :)
___
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://pu
c: juniper-nsp@puck.nether.net
Subject: Re: [j-nsp] How reliable is EX multichassis? 3300 and 8200 switches
Neither of these two options show up as a configurable flag:
set routing-options nonstop-routing
set ethernet-switching-options nonstop-bridging
I'm running 11.4R2.14 on the ex33
Neither of these two options show up as a configurable flag:
set routing-options nonstop-routing
set ethernet-switching-options nonstop-bridging
I'm running 11.4R2.14 on the ex3300-48t switches.
Granted, right now the VC is broken so maybe it doesn't allow me to
configure it? I can head to the d
ber 2012 10:31 AM
To: Morgan McLean
Cc: juniper-nsp@puck.nether.net
Subject: Re: [j-nsp] How reliable is EX multichassis? 3300 and 8200 switches
Hi Morgan,
On 31/10/2012, at 9:06 AM, Morgan McLean wrote:
> Can anybody give me an idea regarding typical failover times if the
> master in a two sw
Hi Morgan,
On 31/10/2012, at 9:06 AM, Morgan McLean wrote:
> Can anybody give me an idea regarding typical failover times if the master
> in a two switch pair were to die? The quickest I've seen in my testing with
> EX3300's is 45 seconds, just for L2 forwarding to continue working, no
> routing
Have no split detection, I'll try for the GRES and NSR.
Thanks,
Morgan
On Tue, Oct 30, 2012 at 4:24 PM, Doug Hanks wrote:
> Should be hitless. You need to configure GRES + NSR + no-split-detection.
>
>
> On 10/30/12 4:06 PM, "Morgan McLean" wrote:
>
> >Can anybody give me an idea regarding typ
Should be hitless. You need to configure GRES + NSR + no-split-detection.
On 10/30/12 4:06 PM, "Morgan McLean" wrote:
>Can anybody give me an idea regarding typical failover times if the master
>in a two switch pair were to die? The quickest I've seen in my testing
>with
>EX3300's is 45 seconds
Can anybody give me an idea regarding typical failover times if the master
in a two switch pair were to die? The quickest I've seen in my testing with
EX3300's is 45 seconds, just for L2 forwarding to continue working, no
routing. All the ports drop link as well on the secondary switch while
things
Robert,
It was released by juniper one or two weeks ago I think.
Take a look:
https://www.juniper.net/us/en/products-services/routing/mx-series/mx2000/
MX2010
MX2020
https://www.juniper.net/us/en/products-services/routing/mx-series/mx2000/#specifications
But I really don't know if it will sup
Any idea where i could test out the EX8200 VC in a lab somewhere? Think our
vendor insight would have some I could fly out and mess with? Unfortunately
the only two we have are for production, and they're a bit expensive to buy
as lab toys.
Morgan
On Sun, Oct 28, 2012 at 10:47 AM, Robert Hass wr
On Fri, Oct 26, 2012 at 11:44 PM, Giuliano Medalha
wrote:
> Considering the MX family (240, 480 and 960 with TRIO 3D) and the new MX-L
Hi
What is new MX-L - can you write a little mort ? MX80 successor ?
Rob
___
juniper-nsp mailing list juniper-nsp@puc
On 27/10/2012, at 12:15 PM, Craig Askings wrote:
> On Saturday, October 27, 2012, Richard A Steenbergen wrote:
>>
>>
>>
>> I'm still sad that I couldn't get Juniper to bless the XRE200 as an
>> external route reflector, since it's an infinitely more useful form
>> factor than a JCS, but alas
On Saturday, October 27, 2012, Richard A Steenbergen wrote:
>
>
>
> I'm still sad that I couldn't get Juniper to bless the XRE200 as an
> external route reflector, since it's an infinitely more useful form
> factor than a JCS, but alas lack of common sense knows no bounds. :)
>
>
>
I'm glad I'm not
Obviously the external RE has its benefits, but I still need two RE per chassis
to make use of it?
Morgan
Sent from my iPhone
On Oct 26, 2012, at 3:03 PM, Richard A Steenbergen wrote:
> On Fri, Oct 26, 2012 at 07:44:27PM -0200, Giuliano Medalha wrote:
>> Morgan,
>>
>> I really dont know why
On Fri, Oct 26, 2012 at 07:44:27PM -0200, Giuliano Medalha wrote:
> Morgan,
>
> I really dont know why JUNIPER did this kind of crazy environment with
> EX8200.
>
> Considering the MX family (240, 480 and 960 with TRIO 3D) and the new
> MX-L I think you do not need the external routing engines
Morgan,
I really dont know why JUNIPER did this kind of crazy environment with
EX8200.
Considering the MX family (240, 480 and 960 with TRIO 3D) and the new MX-L
I think you do not need the external routing engines for virtual chassis.
About the line card ... the information I have is that you n
On Fri, Oct 26, 2012 at 2:46 PM, Morgan McLean wrote:
> fault tolerance. How reliable is VC? I've really done my best to avoid it
I can't speak to EX3300 specifically, but on EX4200 the VC works very
well. I have many stacks running for many years, and have had no
stacking-related problems since
I know I need the XRE200, but my question would be why? Why is this the
only EX product requiring external RE's? And also, it looks like you need
two local RE's to be able to connect to two external RE's? Seems
unnecessarily expensive.
Also, are the 8XS required for inter connects? Right now I onl
Morgan,
We have some cases running EX8200 as a Virtual Chassis, but you will need
the XRE200 External Routing Engines:
http://www.juniper.net/in/en/products-services/switching/ex-series/options/xre200/
Don't forget that you will need the 8 ports (10 gig) for chassis inter x
connections - EX8200
Hey guys,
So I run SRX as my core firewalls, with EX8200's doing core switching and
EX3300's doing access switching. I have two SRX's, two 8208's, and two
3300's at every cabinet. Spanning tree is a pain in my ass, especially
since I have other environments setup the same way, just with smaller
sw
40 matches
Mail list logo
