Renumbering at NetIX
What is 'renumbering'?
Due to our growth, we need to change to a new IPv4 network.
Currently we have IPv4 and IPv6 segments in use. Now, with the renumbering, we are moving to a new IPv4 scheme (193.218.0.0/24 -> 185.1.226.0/23). This means that all existing IPv4 customers must change their router's address and all IPv4 bgp peering sessions.
IPv6 customers are not affected by this and don't need to do anything.
Process: step-by-step
• Started Planning: November 2021
• Publicly announced: December 2021
Reminders from the NOC team will be weekly
• New peering block assigned: Renumbering plan created - first 3 octets - changed, the last octet/IP address stays the same.
• Migration (Parallel run) Period: from 15th Dec 2021 to 10th Feb 2022
• 1st Feb 2022: Final reminder (one week before the parallel run ends (10th Feb 2022))
• 11th Feb 2022: Contact all members not migrated to the new IPv4 network (185.1.226.0/23)
• 11th Feb 2022: Stop the old IPv4 network (193.218.0.0/24)
• Finalizing the process: decomissioning the old route servers
Example:
| First Octet | Second Octet | Third Octet | Fourth Octet | Prefix | |
|---|---|---|---|---|---|
| Existing IPv4 address | 193 | 218 | 0 | 205 | /24 |
| New IPv4 address | 185 | 1 | 226 | 205 | /23 |
* Figures in BOLD to become italic
* Fourth Octet won't change
What if I have a private peering session(s) with another member?
Just contact the member asking for establishing a BGP session with your new peer address.
What if my routing equipment cannot handle the extra IPv4 prefixes comming with the new BGP sessions ?
You can always activate the new BGP sessions with 185.1.226.X Route Servers but filter out the incoming prefixes. When ready to migrate to the new 185.1.226.0/23 segment - you can then shut down the old 193.218.0.0/24 sessions and start receiving announcements from the new BGP sessions.
What will happen if a member misses the deadline?
They cannot peer at NetIX until they have completed the change.
Who can I contact about this?
If you have any questions about this, please get in touch with the NOC team: [email protected]
