[187181] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

RE: Is it normal for your provider to withhold BGP peering info

daemon@ATHENA.MIT.EDU (Ian Mock)
Thu Jan 21 18:13:32 2016

X-Original-To: nanog@nanog.org
From: Ian Mock <ianm@fairwaymc.com>
To: c b <bz_siege_01@hotmail.com>, "nanog@nanog.org" <nanog@nanog.org>
Date: Thu, 21 Jan 2016 23:13:22 +0000
In-Reply-To: <BLU171-W1333A8EB3D4757546EF8243ABC30@phx.gbl>
Errors-To: nanog-bounces@nanog.org

Sounds like you need a little posturing with your sales team and account ma=
nager on the phone. Threaten to cancel the contract and site their lack of =
support and willingness to help you be successful. Say they're interfering =
with your company's ability to do business. If their sales team is worth an=
ything they'll jump all over trying to fix the problem. If not, cancel the =
contract and move on. Do you and your company's mgmt want to deal with some=
one that unhelpful? Imagine what happens when you have a problem..

Ian Mock

-----Original Message-----
From: NANOG [mailto:nanog-bounces@nanog.org] On Behalf Of c b
Sent: Thursday, January 21, 2016 3:27 PM
To: nanog@nanog.org
Subject: Is it normal for your provider to withhold BGP peering info until =
the night of the cut?

We have 4 full-peering providers between two data centers. Our accounting p=
eople 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 expens=
ive 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 ask=
ed 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 t=
his 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 presta=
ge 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 jus=
t provide it ahead of time?
Thanks in advance.
CWB =09=09 =09   =09=09 =20


home help back first fref pref prev next nref lref last post