[c-nsp] Customer getting its own AS

[redscorpion69]

Okay. This part is clear:

1) Set up BGP session, without deleting static routes. There are still
prefered and advertised upstream (so our AS is route origin).
2) When BGP is all set up, delete static routes, now customer originated
routes (with his AS) is advertised upstream.
3) This part is a problem because we can't aggregate more assigned prefixes
which are all given to our customer. Their prefix is outside of bigger
aggregation.

This is why I asked, what if upstream providers filter based on AS+prefix.
Could we ask them to accept same prefix from two different origin ASs for a
short time ?

What are your suggestions ?

Regards!

On Tue, Oct 7, 2014 at 2:45 PM, Mikael Abrahamsson <swmike at swm.pp.se> wrote:

> On Tue, 7 Oct 2014, redscorpion69 wrote:
>
>  One of our customers just got AS number. He is going to keep our
>> addressing
>> scheme (so Provider Assigned address space).
>>
>> What is the best strategy to change static routing to now new BGP sessions
>> on few of POPs. Where does deleting ripe object and creating new ones come
>> into play?
>>
>> So in other words what would be the best order of operation to migrate
>> customer with least amount of downtime?
>>
>
> There should be no downtime if you do it right.
>
> Set up BGP sessions.
> Make sure prefixes and default route are being propagated.
> Delete static route(s). Traffic now flows according to BGP routing.
> Change route object.
> In case someone has a problem with the route object, your encompassing
> larger prefix is going to make sure you get the traffic anyway.
>
> --
> Mikael Abrahamsson    email: swmike at swm.pp.se
>