doing 2 more times next month.
>
> From: Eric A Louie
>To: "nanog@nanog.org"
>Sent: Monday, November 25, 2013 5:21 PM
>Subject: Re: BGP neighbor/configuration testing
>
>
>No logged error with mismatched neighbor IP address - neither router had an
___
> From: Chuck Anderson
>To: nanog@nanog.org
>Sent: Monday, November 25, 2013 3:37 PM
>Subject: Re: BGP neighbor/configuration testing
>
>
>When you say "no logged error" with mismatched neighbor IP address,
>what do you mean? Did the session just not establish at
t;
>
>
> >________
> > From: Chuck Anderson
> >To: nanog@nanog.org
> >Sent: Monday, November 25, 2013 11:10 AM
> >Subject: Re: BGP neighbor/configuration testing
> >
> >
> >Authentication failure might mean (without knowing for sure which on
> >Cisco):
> >
> >- mismatch AS numbers
> >- mismatch neighbor IP addresses
> >- multihop/TTL issues
> >- MTU issues
t;
> >
> > From: Chuck Anderson
> >To: nanog@nanog.org
> >Sent: Monday, November 25, 2013 11:10 AM
> >Subject: Re: BGP neighbor/configuration testing
> >
> >
> >Authentication failure might mean (without knowing
ovember 25, 2013 11:10 AM
>Subject: Re: BGP neighbor/configuration testing
>
>
>Authentication failure might mean (without knowing for sure which on
>Cisco):
>
>- mismatch AS numbers
>- mismatch neighbor IP addresses
>- multihop/TTL issues
>- MTU issues
>
>On
uotecounterquote.com/2011/05/lucy-you-got-some-splainin-to-do.html
>
>
>
>
>
> >
> > From: Daniel Rohan
> >To: Eric A Louie
> >Cc: Joe Abley ; "nanog@nanog.org"
> >Sent: Monday, November 25, 2013 10:55 AM
> >Subject: Re: BGP nei
/05/lucy-you-got-some-splainin-to-do.html
>
> From: Daniel Rohan
>To: Eric A Louie
>Cc: Joe Abley ; "nanog@nanog.org"
>Sent: Monday, November 25, 2013 10:55 AM
>Subject: Re: BGP neighbor/configuration testing
>
>
>
/cri/index.html
-Original Message-
From: Daniel Rohan [mailto:dro...@gmail.com]
Sent: Monday, November 25, 2013 1:56 PM
To: Eric A Louie
Cc: nanog@nanog.org
Subject: Re: BGP neighbor/configuration testing
Seems like:
> Nov 25 06:28:34.837 pacific: %BGP-3-NOTIFICATION: received from
> neig
Seems like:
> Nov 25 06:28:34.837 pacific: %BGP-3-NOTIFICATION: received from neighbor
> xxx.118.92.149 2/5 (authentication failure) 0 bytes
>
should be a good starting place. I'm assuming you've already discussed auth
keys with your provider and if everyone is putting that in correctly, I'd
sug
nanog.org"
>Sent: Wednesday, November 20, 2013 12:01 PM
>Subject: Re: BGP neighbor/configuration testing
>
>
>
>On 2013-11-20, at 14:53, Eric A Louie wrote:
>
>> Scenario: a regional ISP preparing to cutover to a new upstream BGP provider
>> at one of my POPs.
On 11/20/13, 11:53 AM, Eric A Louie wrote:
> Scenario: a regional ISP preparing to cutover to a new upstream BGP provider
> at one of my POPs. Want minimal or no network disruption, and want to ensure
> everything is ready to go prior to the cutover.
>
> I'm planning to use the following order
On 2013-11-20, at 14:53, Eric A Louie wrote:
> Scenario: a regional ISP preparing to cutover to a new upstream BGP provider
> at one of my POPs. Want minimal or no network disruption, and want to ensure
> everything is ready to go prior to the cutover.
>
> I'm planning to use the following
12 matches
Mail list logo
