[187197] in North American Network Operators' Group
Re: Is it normal for your provider to withhold BGP peering info until
daemon@ATHENA.MIT.EDU (Owen DeLong)
Fri Jan 22 05:34:16 2016
X-Original-To: nanog@nanog.org
From: Owen DeLong <owen@delong.com>
In-Reply-To: <BLU171-W1333A8EB3D4757546EF8243ABC30@phx.gbl>
Date: Fri, 22 Jan 2016 02:31:58 -0800
To: c b <bz_siege_01@hotmail.com>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
> On Jan 21, 2016, at 1:26 PM, c b <bz_siege_01@hotmail.com> wrote:
>=20
> 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 substantially lower this year and leadership =
decided to swap our most expensive 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 peering 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 over the years with all of our other carriers and this is =
the first one to ever do this. We even escalated to our account manager =
and they still won't provide it.
> I know it's not a huge deal, but life is so much easier when you can =
prestage 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 just provide it ahead of time?
> Thanks in advance.
> CWB =20
They probably make it up as they go along during the turn-up.
Owen
