It's an EX4500-VC running Junos 11.4r2.14
You can't configure GRES + NSR - they are mutually exclusive.... right?
Config is attached.
Luca
-----Original Message-----
From: Doug Hanks [mailto:dha...@juniper.net]
Sent: Wednesday, 31 October 2012 4:27 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
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" <l...@ninefold.com> wrote:
>Yep I'm aware, but why are my OSPF neighbours going down when one
>switch reboots?
>
>Luca
>
>
>-----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
>
>GR is mutually exclusive with NSR.
>
>
>You want NSR.
>
>On 10/30/12 5:44 PM, "Luca Salvatore" <l...@ninefold.com> wrote:
>
>>I'm just playing around with this now since I have a few new EX
>>switches not in production just yet Have a pretty simple setup with
>>two
>>EX4500 in VC connected to another two
>>EX4500 in VC mode. I'm running OSPF between them.
>>
>>I rebooted the master member while running a ping an it took around 40
>>seconds to come back up. I noticed that my OSPF adjacency went down
>>and the delay was waiting for the OSPF neighbours to come back up.
>>
>>I have:
>>nonstop-routing configured under routing options graceful-switchover
>>configured under chassis redundancy nonstop-bridging configured under
>>ethernet-switching-options
>>
>>Would graceful-restart be 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
>>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 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 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 <bd...@comlinx.com.au> wrote:
>>
>>> Hi Morgan,
>>>
>>> On 31/10/2012, at 9:06 AM, 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?
>>> >
>>>
>>> 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 <
>>> 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/mx
>>> 2
>>> 0
>>> 00/
>>> >>
>>> >> MX2010
>>> >> MX2020
>>> >>
>>> >>
>>> >>
>>> https://www.juniper.net/us/en/products-services/routing/mx-series/mx
>>> 2
>>> 0
>>> 00/#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
>>
>>_______________________________________________
>>juniper-nsp mailing list juniper-nsp@puck.nether.net
>>https://puck.nether.net/mailman/listinfo/juniper-nsp
>>
>
>
>
{master:0}
root@switch1> show configuration | no-more
## Last commit: 2012-04-09 19:18:40 UTC by root
version 11.4R2.14;
system {
host-name ic2z1prccsw001;
root-authentication {
encrypted-password xxxxxx; ## SECRET-DATA
}
syslog {
user * {
any emergency;
}
file messages {
any notice;
authorization info;
}
file interactive-commands {
interactive-commands any;
}
}
commit synchronize;
}
chassis {
redundancy {
graceful-switchover;
}
aggregated-devices {
ethernet {
device-count 20;
}
}
}
interfaces {
ge-0/0/0 {
unit 0 {
family ethernet-switching;
}
}
xe-0/0/0 {
unit 0 {
family ethernet-switching {
port-mode trunk;
vlan {
members ProdDirty-69;
}
}
}
}
ge-0/0/1 {
unit 0 {
family ethernet-switching;
}
}
xe-0/0/1 {
ether-options {
802.3ad ae1;
}
}
ge-0/0/2 {
unit 0 {
family ethernet-switching;
}
}
xe-0/0/2 {
ether-options {
802.3ad ae2;
}
}
ge-0/0/3 {
unit 0 {
family ethernet-switching;
}
}
xe-0/0/3 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/4 {
unit 0 {
family ethernet-switching;
}
}
xe-0/0/4 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/5 {
unit 0 {
family ethernet-switching;
}
}
xe-0/0/5 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/6 {
unit 0 {
family ethernet-switching;
}
}
xe-0/0/6 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/7 {
unit 0 {
family ethernet-switching;
}
}
xe-0/0/7 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/8 {
unit 0 {
family ethernet-switching;
}
}
xe-0/0/8 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/9 {
unit 0 {
family ethernet-switching;
}
}
xe-0/0/9 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/10 {
unit 0 {
family ethernet-switching;
}
}
xe-0/0/10 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/11 {
unit 0 {
family ethernet-switching;
}
}
xe-0/0/11 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/12 {
unit 0 {
family ethernet-switching;
}
}
xe-0/0/12 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/13 {
unit 0 {
family ethernet-switching;
}
}
xe-0/0/13 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/14 {
unit 0 {
family ethernet-switching;
}
}
xe-0/0/14 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/15 {
unit 0 {
family ethernet-switching;
}
}
xe-0/0/15 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/16 {
unit 0 {
family ethernet-switching;
}
}
xe-0/0/16 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/17 {
unit 0 {
family ethernet-switching;
}
}
xe-0/0/17 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/18 {
unit 0 {
family ethernet-switching;
}
}
xe-0/0/18 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/19 {
unit 0 {
family ethernet-switching;
}
}
xe-0/0/19 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/20 {
unit 0 {
family ethernet-switching;
}
}
xe-0/0/20 {
ether-options {
802.3ad ae0;
}
}
ge-0/0/21 {
unit 0 {
family ethernet-switching;
}
}
xe-0/0/21 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/22 {
unit 0 {
family ethernet-switching;
}
}
xe-0/0/22 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/23 {
unit 0 {
family ethernet-switching;
}
}
xe-0/0/23 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/24 {
unit 0 {
family ethernet-switching;
}
}
xe-0/0/24 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/25 {
unit 0 {
family ethernet-switching;
}
}
xe-0/0/25 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/26 {
unit 0 {
family ethernet-switching;
}
}
xe-0/0/26 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/27 {
unit 0 {
family ethernet-switching;
}
}
xe-0/0/27 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/28 {
unit 0 {
family ethernet-switching;
}
}
xe-0/0/28 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/29 {
unit 0 {
family ethernet-switching;
}
}
xe-0/0/29 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/30 {
unit 0 {
family ethernet-switching;
}
}
xe-0/0/30 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/31 {
unit 0 {
family ethernet-switching;
}
}
xe-0/0/31 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/32 {
unit 0 {
family inet {
address 10.255.255.86/30;
}
}
}
xe-0/0/32 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/33 {
unit 0 {
family ethernet-switching;
}
}
xe-0/0/33 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/34 {
unit 0 {
family ethernet-switching;
}
}
xe-0/0/34 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/35 {
unit 0 {
family ethernet-switching;
}
}
xe-0/0/35 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/36 {
unit 0 {
family ethernet-switching;
}
}
xe-0/0/36 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/37 {
unit 0 {
family ethernet-switching;
}
}
xe-0/0/37 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/38 {
unit 0 {
family ethernet-switching;
}
}
xe-0/0/38 {
unit 0 {
family ethernet-switching;
}
}
ge-0/0/39 {
unit 0 {
family ethernet-switching;
}
}
xe-0/0/39 {
unit 0 {
family ethernet-switching;
}
}
ge-0/1/0 {
unit 0 {
family ethernet-switching;
}
}
xe-0/1/0 {
unit 0 {
family ethernet-switching;
}
}
ge-0/1/1 {
unit 0 {
family ethernet-switching;
}
}
xe-0/1/1 {
unit 0 {
family ethernet-switching;
}
}
ge-0/1/2 {
unit 0 {
family ethernet-switching;
}
}
xe-0/1/2 {
unit 0 {
family ethernet-switching;
}
}
ge-0/1/3 {
unit 0 {
family ethernet-switching;
}
}
xe-0/1/3 {
unit 0 {
family ethernet-switching;
}
}
ge-0/2/0 {
unit 0 {
family ethernet-switching;
}
}
xe-0/2/0 {
unit 0 {
family ethernet-switching;
}
}
ge-0/2/1 {
unit 0 {
family ethernet-switching;
}
}
xe-0/2/1 {
unit 0 {
family ethernet-switching;
}
}
ge-0/2/2 {
unit 0 {
family ethernet-switching;
}
}
xe-0/2/2 {
unit 0 {
family ethernet-switching;
}
}
ge-0/2/3 {
unit 0 {
family ethernet-switching;
}
}
xe-0/2/3 {
unit 0 {
family ethernet-switching;
}
}
xe-1/0/0 {
unit 0 {
family ethernet-switching {
port-mode trunk;
vlan {
members ProdDirty-69;
}
}
}
}
xe-1/0/1 {
ether-options {
802.3ad ae1;
}
}
xe-1/0/2 {
ether-options {
802.3ad ae2;
}
}
xe-1/0/20 {
ether-options {
802.3ad ae0;
}
}
ge-1/0/32 {
unit 0 {
family inet {
address 10.255.255.90/30;
}
}
}
ae0 {
aggregated-ether-options {
link-speed 10g;
lacp {
active;
}
}
unit 0 {
family ethernet-switching {
port-mode trunk;
vlan {
members ProdRack3Routing;
}
}
}
}
ae1 {
aggregated-ether-options {
link-speed 10g;
lacp {
active;
}
}
unit 0 {
family ethernet-switching {
port-mode trunk;
vlan {
members ProdRack1Routing;
}
}
}
}
ae2 {
aggregated-ether-options {
link-speed 10g;
lacp {
active;
}
}
unit 0 {
family ethernet-switching {
port-mode trunk;
vlan {
members ProdRack2Routing;
}
}
}
}
lo0 {
unit 0 {
family inet {
address 10.255.0.4/32;
}
}
}
me0 {
unit 0 {
family inet {
address 1.1.1.1/24;
}
}
}
vlan {
unit 81 {
family inet {
address 10.255.255.1/30;
}
family inet6 {
address fc00:2:1:12::1/64;
}
}
unit 82 {
family inet {
address 10.255.255.5/30;
}
}
unit 83 {
family inet {
address 10.255.255.9/30;
}
}
}
}
routing-options {
nonstop-routing;
}
protocols {
ospf {
area 0.0.0.0 {
interface ge-0/0/32.0;
interface ge-1/0/32.0;
interface lo0.0;
}
area 0.0.0.1 {
interface vlan.81;
interface vlan.82;
interface vlan.83;
}
}
ospf3 {
area 0.0.0.1 {
interface vlan.81;
}
}
mstp {
configuration-name mstp;
revision-level 1;
bridge-priority 60k;
msti 1 {
bridge-priority 16k;
vlan 69;
}
msti 2 {
bridge-priority 0;
vlan 1000-3999;
}
}
lldp {
interface all;
}
lldp-med {
interface all;
}
}
ethernet-switching-options {
nonstop-bridging;
storm-control {
interface all;
}
}
vlans {
ProdDirty-69 {
vlan-id 69;
}
ProdRack1Routing {
vlan-id 81;
l3-interface vlan.81;
}
ProdRack2Routing {
vlan-id 82;
l3-interface vlan.82;
}
ProdRack3Routing {
vlan-id 83;
l3-interface vlan.83;
}
}
virtual-chassis {
no-split-detection;
member 0 {
mastership-priority 255;
}
member 1 {
mastership-priority 255;
}
}
{master:0}
root@switch1>
_______________________________________________
juniper-nsp mailing list juniper-nsp@puck.nether.net
https://puck.nether.net/mailman/listinfo/juniper-nsp
