[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Is it normal for your provider to withhold BGP peering info until the night of the cut?

I?d be concerned. IMHO, it?s not normal to withhold such information. Doing so suggests that they are disorganized at best.

When we sign a BGP customer, we collect their ASN and the networks they want 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?ve assigned, and port info. This is done weeks/months before turn-up.

On 1/21/16, 2:26 PM, "NANOG on behalf of c b" <nanog-bounces at nanog.org on behalf of bz_siege_01 at 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 substantially lower this year and leadership decided to swap our most expensive circuit to the new carrier. 
>(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.