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

Morgan McLean wrx230 at gmail.com
Tue Oct 30 20:00:17 EDT 2012


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 datacenter and upgrade these two devices to
recommended release and report back tomorrow as well.

Morgan

On Tue, Oct 30, 2012 at 4:30 PM, Ben Dale <bdale at comlinx.com.au> wrote:

> 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/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 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
> >
>
>


More information about the juniper-nsp mailing list