[c-nsp] Sprint & AT&T BGP multihoming

[Stephen Kratzer]

Deleted the original post, so I'll reply to this leaf...

ATT is fine. Make sure that Sprint, at that particular location, has multiple 
transit providers. We are multihomed at one location with Embarq and Level3. 
As it turns out, Embarq's sole transit provider at that location IS Level3 
making the Embarq connection all but useless as far as diverse, load-balanced 
routing is concerned.

Stephen Kratzer
Network Engineer
CTI Networks, Inc.

On Wednesday 11 February 2009 08:58:30 Adam Greene wrote:
> Had a good experience multihoming to AT&T, including fixing an issue with
> balancing traffic between the two providers, which we solved through
> advertisement of community strings. The engineer I spoke with was extremely
> knowledgable.
>
> This was already a few years ago, though ...
>
> ----- Original Message -----
> From: "ChrisSerafin" <chris at chrisserafin.com>
> To: <cisco-nsp at puck.nether.net>
> Sent: Tuesday, February 10, 2009 5:44 PM
> Subject: [c-nsp] Sprint & AT&T BGP multihoming
>
> >I am planning on multi-homing a client's Internet connection for
> >redundancy, and wanted to know if anyone is doing this with Sprint and/or
> >AT&T and has any pointers or 'gotchas' they have run into.
> >
> > I'm still months out from doing this and will most likely want to KEEP
> > the existing subnets that they gave us (a /23 and /24), without the need
> > for rebuilding a bunch or VPNs, re-IP'ing externally facing devices, and
> > DNS changes for externally available web presence.
> >
> > Ideas? Comments? Concerns? Flames?
> >
> > Thanks,
> >
> > Chris Serafin
> > chris at chrisserafin.com