[j-nsp] juniper-nsp Digest, Vol 152, Issue 5

[Charmaine Low]

On 7 Jul 2015 12:00 am, <juniper-nsp-request at puck.nether.net> wrote:
>
> Send juniper-nsp mailing list submissions to
>         juniper-nsp at puck.nether.net
>
> To subscribe or unsubscribe via the World Wide Web, visit
>         https://puck.nether.net/mailman/listinfo/juniper-nsp
> or, via email, send a message with subject or body 'help' to
>         juniper-nsp-request at puck.nether.net
>
> You can reach the person managing the list at
>         juniper-nsp-owner at puck.nether.net
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of juniper-nsp digest..."
>
>
> Today's Topics:
>
>    1. Re: eBGP Failover (Adam Vitkovsky)
>    2. Re: eBGP Failover (Mark Tinka)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 6 Jul 2015 12:11:30 +0000
> From: Adam Vitkovsky <Adam.Vitkovsky at gamma.co.uk>
> To: Mark Tinka <mark.tinka at seacom.mu>, Peter Ehiwe
>         <peterehiwe at gmail.com>, Mohammad Khalil <eng.mssk at gmail.com>
> Cc: "juniper-nsp at puck.nether.net" <juniper-nsp at puck.nether.net>
> Subject: Re: [j-nsp] eBGP Failover
> Message-ID:
>         <
627266B72B856946BCD625D4B34B19163165AFDE at INF-EXCH-MB-02.gammatelecom.com>
>
> Content-Type: text/plain; charset=WINDOWS-1252
>
> Hi Mark,
>
> It comes with unpredictable up to several second failover/restoration
times.
> It looks like some HW to SW or vice versa signalling failure.
>
> adam
> > -----Original Message-----
> > From: Mark Tinka [mailto:mark.tinka at seacom.mu]
> > Sent: 01 July 2015 13:47
> > To: Adam Vitkovsky; Peter Ehiwe; Mohammad Khalil
> > Cc: juniper-nsp at puck.nether.net
> > Subject: Re: [j-nsp] eBGP Failover
> >
> >
> >
> > On 1/Jul/15 10:38, Adam Vitkovsky wrote:
> > > With LACP you are reliant on the mercy of the service provider.
> > > And besides that LACP is tricky so you might not get the failover
times you
> > are after.
> >
> > How is LACP tricky?
> >
> > Mark.
>
>
>
> ------------------------------
>
> Message: 2
> Date: Mon, 6 Jul 2015 16:31:13 +0200
> From: Mark Tinka <mark.tinka at seacom.mu>
> To: Adam Vitkovsky <Adam.Vitkovsky at gamma.co.uk>, Peter Ehiwe
>         <peterehiwe at gmail.com>, Mohammad Khalil <eng.mssk at gmail.com>
> Cc: "juniper-nsp at puck.nether.net" <juniper-nsp at puck.nether.net>
> Subject: Re: [j-nsp] eBGP Failover
> Message-ID: <559A9131.80302 at seacom.mu>
> Content-Type: text/plain; charset=windows-1252
>
>
>
> On 6/Jul/15 14:11, Adam Vitkovsky wrote:
> > Hi Mark,
> >
> > It comes with unpredictable up to several second failover/restoration
times.
> > It looks like some HW to SW or vice versa signalling failure.
>
> We have LACP running with an upstream on an ASR9001. No issues.
>
> I recall running LACP with a peer on an M10i (they had an MX960) at
> previous job. No issues.
>
> We run LACP on about 80% of the routers/switches in our network
> (Cisco-Cisco, Cisco-Juniper and Juniper-Juniper). No issues.
>
> Mark.
>
>
> ------------------------------
>
> Subject: Digest Footer
>
> _______________________________________________
> juniper-nsp mailing list
> juniper-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/juniper-nsp
>
> ------------------------------
>
> End of juniper-nsp Digest, Vol 152, Issue 5
> *******************************************