[187175] in North American Network Operators' Group
Re: Is it normal for your provider to withhold BGP peering info until
daemon@ATHENA.MIT.EDU (Sean)
Thu Jan 21 16:57:08 2016
X-Original-To: nanog@nanog.org
Date: Thu, 21 Jan 2016 14:55:01 -0700
From: Sean <spedersen.lists@gmail.com>
To: "nanog@nanog.org" <nanog@nanog.org>
In-Reply-To: <BLU171-W1333A8EB3D4757546EF8243ABC30@phx.gbl>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
I=E2=80=99d be concerned. IMHO, it=E2=80=99s not normal to withhold such information. D=
oing so suggests that they are disorganized at best.
When we sign a BGP customer, we collect their ASN and the networks they wan=
t to advertise up front. With that information, we complete a network setup =
document that is forwarded to the customer. The document contains all of the=
information they provided, the transit network(s) we=E2=80=99ve assigned, and por=
t info. This is done weeks/months before turn-up.
On 1/21/16, 2:26 PM, "NANOG on behalf of c b" <nanog-bounces@nanog.org on b=
ehalf of bz_siege_01@hotmail.com> wrote:
>We have 4 full-peering providers between two data centers. Our accounting =
people did some shopping and found that there was a competitor who came in s=
ubstantially lower this year and leadership decided to swap our most expensi=
ve circuit to the new carrier.=20
>(I don't know what etiquette is, so I won't name the carrier... but it's a=
well-known name)
>Anyways, we were preparing for the circuit cutover and asked for the BGP p=
eering info up front like we normally do. This carrier said that they don't =
provide this until the night of the cut. Now, we've done this 5 or 6 times o=
ver the years with all of our other carriers and this is the first one to ev=
er do this. We even escalated to our account manager and they still won't pr=
ovide it.
>I know it's not a huge deal, but life is so much easier when you can prest=
age your cut and rollback commands. In fact, our internal Change Management =
process mandates peer review all proposed config changes and now we have to =
explain why some lines say TBD!
>Is this a common SOP nowadays? Anyone care to explain why they wouldn't ju=
st provide it ahead of time?
>Thanks in advance.
>CWB
