<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta http-equiv=Content-Type content="text/html; charset=us-ascii"><meta name=Generator content="Microsoft Word 14 (filtered medium)"><!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:Tahoma;
panose-1:2 11 6 4 3 5 4 4 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
{mso-style-priority:99;
mso-style-link:"Plain Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
p.MsoAcetate, li.MsoAcetate, div.MsoAcetate
{mso-style-priority:99;
mso-style-link:"Balloon Text Char";
margin:0cm;
margin-bottom:.0001pt;
font-size:8.0pt;
font-family:"Tahoma","sans-serif";
mso-fareast-language:EN-US;}
span.PlainTextChar
{mso-style-name:"Plain Text Char";
mso-style-priority:99;
mso-style-link:"Plain Text";
font-family:"Calibri","sans-serif";}
span.BalloonTextChar
{mso-style-name:"Balloon Text Char";
mso-style-priority:99;
mso-style-link:"Balloon Text";
font-family:"Tahoma","sans-serif";}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri","sans-serif";
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]--></head><body lang=EN-AU link=blue vlink=purple><div class=WordSection1><p class=MsoPlainText>Hi James, <o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Achieving near 50/50 load balancing will be very tough unfortunately!<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>[Balancing Problems]<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Let’s say that for example, you were to choose two different Go4 providers with very similar path costs to popular destinations (Australia and the USA for example). <o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>On the surface, it might seem like the ideal way to get the desired 50/50 balance but in practice if there are two identical cost paths than only one of those paths will be chosen, and the path that’s chosen will be the one that’s had the best uptime (least recent flapping event). <o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>So let’s say you started your prefix advertisements on provider [A], and then immediately turn on provider [B], the upstream routers will first choose the one with the shortest path, and if they see two equal cost paths they will chose provider [A] since it’s been up the longest. <o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>The end result is that most traffic ends up coming down provider [A], until such a time that this link goes down, and then the traffic will flick over to provider [B]. <o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>When provider [A] comes back online, the shortest path decision will happen of course, but where there’s equal cost paths the traffic will stay on [B]. So you end up finding that one provider gets the most traffic until it goes down, and then the other provider ends up with the most traffic, rinse and repeat. <o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>[Provider Choice]<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Obviously the key is choosing providers that utilize different domestic and international paths, as others have suggested to do some research by utilizing <a href="http://bgp.he.net">http://bgp.he.net</a>, etc, etc. <o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>But taking that another level, as far as domestic paths go, if you’re already with a Go4 provider than generally they don’t peer with other providers, so when it comes to choosing a non-Go4 just make sure you choose one that peers extensively (PipeIX, WAIX, etc) as this will help considerably with your balancing goals.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>As far as international paths go, try and make sure they use different logical international paths at a minimum, and preferably different physical paths as well (if it’s possible to ascertain). This will also help with the balancing goals. <o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>--<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Just my 2c, but I hope this all makes sense. <o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoNormal>Cheers,<o:p></o:p></p><p class=MsoNormal><span style='mso-fareast-language:EN-AU'><img border=0 width=498 height=120 id="Picture_x0020_1" src="cid:image001.png@01CED6F8.4309EB00" alt="email_signature"><o:p></o:p></span></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText><span lang=EN-US style='mso-fareast-language:EN-AU'>-----Original Message-----<br>From: AusNOG [mailto:ausnog-bounces@lists.ausnog.net] On Behalf Of James Mcintosh<br>Sent: Friday, 1 November 2013 6:20 AM<br>To: ausnog@ausnog.net<br>Subject: [AusNOG] What Transit Providers Would You Pair Together</span></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>Hi Noggers,<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>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.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>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.<o:p></o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText><o:p> </o:p></p><p class=MsoPlainText>-James<o:p></o:p></p><p class=MsoPlainText>_______________________________________________<o:p></o:p></p><p class=MsoPlainText>AusNOG mailing list<o:p></o:p></p><p class=MsoPlainText><a href="mailto:AusNOG@lists.ausnog.net"><span style='color:windowtext;text-decoration:none'>AusNOG@lists.ausnog.net</span></a><o:p></o:p></p><p class=MsoPlainText><a href="http://lists.ausnog.net/mailman/listinfo/ausnog"><span style='color:windowtext;text-decoration:none'>http://lists.ausnog.net/mailman/listinfo/ausnog</span></a><o:p></o:p></p></div></body></html>