Futher to my message below, uh, it seems there were some uh.. problems with the config after some BGP changes some time ago. I believe this has now been fixed, and we&#39;re now advertising approximately 2000 prefixes learned through APE towards Akamai&#39;s quagga box.<br>
<br>I guess this should put an end to the discussion about setting up an APE-connected Akamai cluster.<br><br><br><br><div class="gmail_quote">On 15 July 2010 10:23, Ian Batterbee <span dir="ltr">&lt;<a href="mailto:ibatterb@gmail.com">ibatterb@gmail.com</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br><div class="gmail_quote"><div class="im">On 14 July 2010 15:31, Lincoln Reid <span dir="ltr">&lt;<a href="mailto:lincoln@acsdata.co.nz" target="_blank">lincoln@acsdata.co.nz</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div>
<br>
</div>Ideally someone from Callplus could chirp in here and clarify if they<br>
are feeding all the prefixes they learn at APE on to Akamai, or if there<br>
is a static list that will become out of date etc.<br></blockquote></div><div><br>We set a community on anything we learn from APE, and send everything that has that community to Akamai. If someone can identify a particular route that isn&#39;t working as expected, let me know and I&#39;ll have a look.<br>

<br><br></div></div>
</blockquote></div><br>