[j-nsp] How reliable is EX multichassis? 3300 and 8200 switches

[Luca Salvatore]

Also will need the 'set commit sync' command under the 'edit system'
This is needed for nonstop-bridging

Luca

-----Original Message-----
From: juniper-nsp-bounces at puck.nether.net [mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of Ben Dale
Sent: Wednesday, 31 October 2012 10:31 AM
To: Morgan McLean
Cc: juniper-nsp at 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 <wrx230 at gmail.com> 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. All the ports drop link as well on the 
> secondary switch while things switch over. I can have my laptop 
> connected to the secondary switch, passing traffic up an uplink on the 
> secondary, and if the master dies it creates a 45 second interruption.
> 
> Normal?
> 

Yes, but add the following to your configuration:

set virtual-chassis no-split-detection    (you may already have this)
set routing-options nonstop-routing
set ethernet-switching-options nonstop-bridging

and try again.  In your testing, put a 3rd switch in place with LACP and one leg to each member.

My testing (45/42xx) has shown L2 should be pretty much hitless under most circumstances (except if your STP topology needs to re-converge), and L3 should around the 1-4 seconds mark (for violent failures of master RE).

The worst case scenario though is re-merging a split VC, which can take the best part of 45 seconds, so avoid split-brain scenarios whenever possible with redundant VCP/VCPe or schedule their repair during planned outage windows.

Cheers,

Ben




> Morgan
> 
> On Sun, Oct 28, 2012 at 2:24 PM, Giuliano Medalha <giuliano at wztech.com.br>wrote:
> 
>> 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/mx2
>> 000/
>> 
>> MX2010
>> MX2020
>> 
>> 
>> https://www.juniper.net/us/en/products-services/routing/mx-series/mx2
>> 000/#specifications
>> 
>> But I really don't know if it will support virtual chassis without JCS.
>> 
>> Att,
>> 
>> Giuliano
>> 
>> 
>> 
>> On Sun, Oct 28, 2012 at 3:47 PM, Robert Hass <robhass at gmail.com> wrote:
>> 
>>> On Fri, Oct 26, 2012 at 11:44 PM, Giuliano Medalha 
>>> <giuliano at wztech.com.br> 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 at puck.nether.net 
> https://puck.nether.net/mailman/listinfo/juniper-nsp
> 


_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp