adel@baklawasecrets.com wrote:

Hi,

Thanks to everyone that replied to my post on failover configuration. This has lead me to this post. I'm at a point now where I'm looking at dual-homing with two BGP peers upstream. Now what I am looking at doing is as follows:

BGP Peer with Provider A who is multihomed to other providers. BGP Peer with Provider B who is not peered with provider A

I have an existing relationship with provider A, colo, cross connects etc. Provider A has offered to get the PI space, ASN number, purchase the transit for us with provider B and manage cross connects to provider B (they say they have a diverse "fibre backhaul network"). This is quite attractive from a support and billing perspective. Also suspect that provider A will be able to get more attractive pricing from Provider B than I would be able to.

Am I missing things that I need to consider?

Don't let them cross connect over their network. Bring it in to your site separate from A, otherwise there's no point in the multihoming exercise. ~Seth

On Mon, Nov 9, 2009 at 12:40 PM, <adel@baklawasecrets.com> wrote:

I have an existing relationship with provider A, colo, cross connects etc.  Provider A has offered to get the PI space, ASN number, purchase the transit for us with provider B and manage cross connects to provider B (they say they have a diverse "fibre backhaul network").  This is quite attractive from a support and billing perspective.  Also suspect that provider A will be able to get more attractive pricing from Provider B than I would be able to.

Am I missing things that I need to consider?

What happens when provider A is bought by provider C and you want to dump provider C but keep provider B? You'll have created a conflict of interest for provider B in any negotiation you have with them. Be aware that provider A's diverse network for provider A's service is the same diverse network they'll use to connect you to provider B. As a result, many or most of the outages which impact provider A will also impact your connectivity to provider B, defeating the central purpose of having a provider B. Regards, Bill Herrin -- William D. Herrin ................ herrin@dirtside.com bill@herrin.us 3005 Crane Dr. ...................... Web: <http://bill.herrin.us/> Falls Church, VA 22042-3004

adel@baklawasecrets.com wrote:

Hi,

Thanks to everyone that replied to my post on failover configuration. This has lead me to this post. I'm at a point now where I'm looking at dual-homing with two BGP peers upstream. Now what I am looking at doing is as follows:

BGP Peer with Provider A who is multihomed to other providers. BGP Peer with Provider B who is not peered with provider A

I have an existing relationship with provider A, colo, cross connects etc. Provider A has offered to get the PI space, ASN number, purchase the transit for us with provider B and manage cross connects to provider B

...I've likely missed something, but get the IP/ASN for yourself. *ensure* that A & B will peer and provide transit for you.

(they say they have a diverse "fibre backhaul network"). This is quite attractive from a support and billing perspective.

...until you find out that the backhaul network is owned by Provider B, or virtualized within an existing circuit to someplace else.

Also suspect that provider A will be able to get more attractive pricing from Provider B than I would be able to.

But at what cost?

Am I missing things that I need to consider?

I think so. Long-term survival for one. If you are budgeted for a diverse and redundant network, then I recommend that you ensure one. My current understanding is that you can negotiate terms with potential providers where there is competition. Don't allow any of your ISPs to manage/dictate the use of your address space. It will bite you, and cause undue frustration. Steve