[c-nsp] Route-Object creation

Daniel Holme dan.holme at gmail.com
Sun Mar 14 04:57:07 EDT 2010


Hi Andrew

If your ASN is public then you just need one route object with your
ASN in the 'origin' field.

You can check by doing a lookup with '-T route <prefix>'.

If your upstream is going to originate from their AS (ie. you had a
private AS or just statically routed) then they would need a route
object, maybe there's some confusion over what they think they are
providing you.

--Dan

On Sat, Mar 13, 2010 at 7:53 PM, Andrew Gabriel <mailandrewg at gmail.com> wrote:
>  Need a bit of advice from the folks who work at ISPs or are familiar with
> the ARIN setup.
>
> We already have our own ASN and public IP subnets registered to us, and we
> have had several sites running BGP with the ISP and also announcing our
> subnets out to the Internet, though with a single ISP at each site so far
> (this was done in preparation for multi-homing several years ago but we are
> only now adding the second ISP).
>
> Now, with the additional/backup ISP, but the same existing subnet that is
> already being announced and routed fine with the existing ISPs, do we still
> need to create a route-object? I was pretty sure that we didn't as the
> subnets already have route-objects done from when we started announcing them
> to the existing ISPs, and the route-object to my understanding is done by
> ARIN and is ISP-neutral.
>
> However the new ISP (a tier-1 provider, BTW) categorically stated in reply
> to my mailed query to them that we still needed to create a route-object. So
> I am confused. Would appreciate any advice.
>
> Thanks,
> -Andrew.
> _______________________________________________
> cisco-nsp mailing list  cisco-nsp at puck.nether.net
> https://puck.nether.net/mailman/listinfo/cisco-nsp
> archive at http://puck.nether.net/pipermail/cisco-nsp/
>



More information about the cisco-nsp mailing list