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" <l...@ninefold.com> 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, at 3:56 AM, "Stefan Fouant" ><sfou...@shortestpathfirst.net> wrote: > >> On Oct 31, 2012, at 10:01 AM, Luca Salvatore <l...@ninefold.com> 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" >>><sfou...@shortestpathfirst.net<mailto:sfou...@shortestpathfirst.net>> >>>wrote: >>> >>> I think you are confusing GRES w/ GR. NSR and GRES are NOT mutually >>>exclusive and in fact NSR requires it to function. >> >> 'set chassis redundancy graceful-switchover' is GRES, not GR. >> >>> What I actually see when the master switch robots is that the AE >>>interfaces between my devices flaps. I think this causes my OSPF >>>neighbours to go down. >>> >>> I see this in the logs: "rpd[2241]: RPD_OSPF_NBRDOWN: OSPF neighbor >>>10.255.255.9 (realm ospf-v2 vlan.83 area 0.0.0.1) state changed from >>>Full to Down due to KillNbr (event reason: interface went down" >> >> Which device is the ae interface tied to? Is it a VC-LAG with members >>tied to multiple physical devices, or is it comprised of only links >>belonging to a single device? >> >> Stefan Fouant >> JNCIE-SEC, JNCIE-SP, JNCIE-ENT, JNCI >> Systems Engineer, Juniper Networks > _______________________________________________ juniper-nsp mailing list juniper-nsp@puck.nether.net https://puck.nether.net/mailman/listinfo/juniper-nsp