[187204] in North American Network Operators' Group
RE: Is it normal for your provider to withhold BGP peering info
daemon@ATHENA.MIT.EDU (c b)
Fri Jan 22 14:20:12 2016
X-Original-To: nanog@nanog.org
From: c b <bz_siege_01@hotmail.com>
To: Daniel Corbe <dcorbe@hammerfiber.com>, Ian Mock <ianm@fairwaymc.com>
Date: Fri, 22 Jan 2016 12:20:09 -0700
In-Reply-To: <78BBA00C-DFB1-4790-B4A1-A3A6256E8F3B@hammerfiber.com>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Errors-To: nanog-bounces@nanog.org
Oh=2C we don't. Typically when we turn up a new circuit=2C the old is left =
in place for 2 weeks in case we need to roll back. This is simply a matter =
of them giving us their peering info ahead of time so that we can prestage =
the configs. Someone else responded that there are probably two teams invol=
ved on the carrier's side (and I'm guessing some automated systems?) which =
may explain some of this=2C but I can't understand why they couldn't just p=
unch in the info earlier than the night of the change. These guys are not a=
small carrier.
Anyways=2C it's just an inconvenience and it struck me as odd=2C so I thoug=
ht I'd ask if this is normal or not. Thanks for the feedback everyone.
> Subject: Re: Is it normal for your provider to withhold BGP peering info =
until the night of the cut?
> From: dcorbe@hammerfiber.com
> Date: Thu=2C 21 Jan 2016 18:35:05 -0500
> CC: bz_siege_01@hotmail.com=3B nanog@nanog.org
> To: ianm@fairwaymc.com
>=20
> > We have 4 full-peering providers between two data centers. Our accounti=
ng 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 ex=
pensive circuit to the new carrier.=20
> > (I don't know what etiquette is=2C so I won't name the carrier... but i=
t's a well-known name) Anyways=2C we were preparing for the circuit cutover=
and asked for the BGP peering info up front like we normally do. This carr=
ier said that they don't provide this until the night of the cut. Now=2C we=
've done this 5 or 6 times over the years with all of our other carriers an=
d this is the first one to ever do this. We even escalated to our account m=
anager and they still won't provide it.
> > I know it's not a huge deal=2C but life is so much easier when you can =
prestage your cut and rollback commands. In fact=2C our internal Change Man=
agement 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
> >=20
>=20
> My question to the OP would be why didn=92t you schedule the turndown of =
the old circuit to overlap with the turnup of the new circuit? That way yo=
u could perform your cut independently of turn-up testing with your new pro=
vider. Why is it that you MUST perform both activities on the same night? =
You can always turn up a circuit=2C make sure it works and then turn it ba=
ck down on your end until you=92re actually ready to use it. =20
>=20
>=20
=
