Re: ARIN?

[Phillip Vandry <vandry () Mlink NET>]

> Well, like others have mentioned, there are ways around this, even if they
> are a bit sub-optimal.  As long as you have at least a /19 total, and you
> use the same upstream provider(s) in all of the POPs that this /19 is used
> in, you can announce the specifics for each pop along with the /19 in each
> of those POPs.  This will accomplish several things for you.  First of
> all, like you said, if you lose all internal connectivity from any of
> those POPs, but you still have at least 1 upstream, all of your traffic
> will still get to you by following the more specific route.  Since the /19
> is still being announced, those backbones that filter longer masks will
> still send the traffic to your upstream(s) who will have the more specific
> routes in their tables and send the traffic in the right direction.
>
> This method, of course, is a bit unfriendly since you're making more
> announcements than you would be otherwise.

But you can remove the unfriendliness (again, in the case that you are
using the same upstream in each location) by announcing the specifics
with community no-export.

Although I once tried this and it failed utterly for lack of clue in the
upstream.

-Phil