Should be hitless. You need to configure GRES + NSR + no-split-detection.
On 10/30/12 4:06 PM, "Morgan McLean" <wrx...@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? > >Morgan > >On Sun, Oct 28, 2012 at 2:24 PM, Giuliano Medalha ><giuli...@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 <robh...@gmail.com> wrote: >> >>> On Fri, Oct 26, 2012 at 11:44 PM, Giuliano Medalha >>> <giuli...@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@puck.nether.net >https://puck.nether.net/mailman/listinfo/juniper-nsp > _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp