This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/
[address-policy-wg] Migration Datacenter
- Previous message (by thread): [address-policy-wg] Migration Datacenter
- Next message (by thread): [address-policy-wg] 2016-05 New Policy Proposal (Synchronising the Initial and Subsequent IPv6 Allocation Policies)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Erik Bais
ebais at a2b-internet.com
Thu Nov 24 13:43:07 CET 2016
Hi Angel, Typically the route objects are being used to create daily filters at certain upstream / backbone providers.. As long as you delete the old RIPE Route object (let's say 12 hrs before the migration ) and create a new one for the new transit provider to allow them to notify their transit provider to update their filters and announce the new route.. you should be ok. You could also ... ( during the migration ) ask the new transit provider to announce in /24's, so that if the old provider hasn't stopped their announcement yet, you can still use the IP's in your new location. As a more specific route has preference above a larger announcement. And once the old provider stopped the announcement of the /22, you can start to announce the /22 on the new location and stop with the /24's to be announced. ( Aggregation back to a /22 is nice to do.. ) Good luck on the migration. Kind regards, Erik Bais A2B Internet -----Oorspronkelijk bericht----- Van: address-policy-wg [mailto:address-policy-wg-bounces at ripe.net] Namens ANGEL MARTINEZ SANCHEZ Verzonden: donderdag 24 november 2016 1:07 Aan: address-policy-wg at ripe.net Onderwerp: [address-policy-wg] Migration Datacenter Hello, We are going to migrate from our actually datacenter to another one. We have /22 IPs block and not have AS number, our datacenter announce them. Our plan is as follows: - We already add new route objects before migration and will remove old after migration. - At dawn on Sunday, November 27 about 3:00 AM, we will shut down all our servers from the current data center. - At that point we will delete the current route ASXXXX in RIPE DB from inetnum XXX.XXX.XX.0/22 and only the route object corresponding to new datacenter will remain. - We will contact new datacenter to activate our IP block on their router and configure the requested gateway. - We will dismantle the entire rack from old datacenter and move it to the new datacenter where we will start up all our servers again. We need to know if the procedure is correct and very important, the time it takes to propagate the new route of our IP block since we delete the current ASXXXXX and the new ASXXXX is activated by new datacenter. We also need to know if we depend on any action by the current data center to complete this procedure. For example, if they have to remove our block from their AS or their router and that would happen in case they refused to do so on the date indicated for the migration. Thanks and regards. Angel Sent via RIPE Forum -- https://www.ripe.net/participate/mail/forum
- Previous message (by thread): [address-policy-wg] Migration Datacenter
- Next message (by thread): [address-policy-wg] 2016-05 New Policy Proposal (Synchronising the Initial and Subsequent IPv6 Allocation Policies)
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]