[AusNOG] What Transit Providers Would You Pair Together

[Brent Paddon]

This is all well and good, but is nothing more than a snapshot-in-time view.

Commercial relationships and routing preferences/decisions change...

Brent


On Fri, Nov 1, 2013 at 8:51 AM, James Braunegg
<james.braunegg at micron21.com>wrote:

> Dear James****
>
> ** **
>
> I always start my research on http://bgp.he.net/  looking up each
> potential AS and then compare the common peers and make a list of few IP
> addresses which they are advertising (ie Prefixes)****
>
> ** **
>
> Once I have fined tuned a few providers I use http://www.lookinglass.org/ and pick a handful of looking glasses locally and from around the world.
> ****
>
> ** **
>
> ie local peering looking glasses and local transit providers in each state
> followed by looking glasses from a handful of each part of the world.****
>
> ** **
>
> I would then suggest doing a trace route from each looking glass (around
> the world)  to different IP’s within that providers prefix list from each
> potential  AS and compare the inbound trace towards that network between
> different IP ranges and different providers and your current provider. The
> above should give you a good idea of inbound paths, and how diverse or
> common they are. Finally once you have narrowed down your search I would
> then ask the provider for an outbound trace to certain networks. Without
> bound traffic this is slightly different again depending if your taking
> full routes / partial or a default route, you might let BGP do its thing,
> or you might create route maps for each provider or use software to
> optimize outbound routes.****
>
> ** **
>
> Hope this helps****
>
> ** **
>
> Kindest Regards****
>
> * *
>
> *James Braunegg
> **P:*  1300 769 972  |  *M:*  0488 997 207 |  *D:*  (03) 9751 7616****
>
> *E:*   james.braunegg at micron21.com  |  *ABN:*  12 109 977 666
> *W:*  www.micron21.com/ip-transit    *T:* @micron21****
>
> ** **
>
>
> [image: Description: Description: Description: Description: M21.jpg]
> This message is intended for the addressee named above. It may contain
> privileged or confidential information. If you are not the intended
> recipient of this message you must not use, copy, distribute or disclose it
> to anyone other than the addressee. If you have received this message in
> error please return the message to the sender by replying to it and then
> delete the message from your computer.****
>
> ** **
>
> -----Original Message-----
> From: AusNOG [mailto:ausnog-bounces at lists.ausnog.net] On Behalf Of James
> Mcintosh
> Sent: Friday, November 01, 2013 7:20 AM
> To: ausnog at ausnog.net
> Subject: [AusNOG] What Transit Providers Would You Pair Together
>
> ** **
>
> Hi Noggers,****
>
> ** **
>
> We're looking at adding a second transit provider for redundancy (and
> hopefully more-or-less even load balancing). I was wondering what transit
> providers people would recommend pairing together to get the most diverse
> set of routes. Obviously you don't want your two upstreams to have very
> similar routes and paths.****
>
> ** **
>
> As a start I was thinking perhaps a Gang of Four provider plus a non-Go4
> provider would make a good pairing but I'd really appreciate the comments
> of some of the more experienced BGP gurus on the list.****
>
> ** **
>
> ** **
>
> -James****
>
> _______________________________________________****
>
> AusNOG mailing list****
>
> AusNOG at lists.ausnog.net****
>
> http://lists.ausnog.net/mailman/listinfo/ausnog****
>
> _______________________________________________
> AusNOG mailing list
> AusNOG at lists.ausnog.net
> http://lists.ausnog.net/mailman/listinfo/ausnog
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.ausnog.net/pipermail/ausnog/attachments/20131101/66ce6624/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.jpg
Type: image/jpeg
Size: 2683 bytes
Desc: not available
URL: <http://lists.ausnog.net/pipermail/ausnog/attachments/20131101/66ce6624/attachment.jpg>