Hulp nodig? Inloggen

Article

Migration to new core network: FAQ

Migration to advanced new core network

signetbreedband has developed a new core netwok called the ‘Connectivity Core’. This pivotal hub underpins our entire technical framework. With enhanced bandwidth capacity and advanced redundancy features, it’s primed to handle the escalating frequency of DDoS attacks. For a deeper dive into this transformation, check out this article (only in Dutch).

What’s on the horizon?

Starting from 2023, we initiated a gradual shift of all our connections to the new core network. This full transition is set to conclude by the end of the year 2024. We've meticulously planned the migrations to occur during scheduled maintenance windows, ensuring minimal disruption for you, our valued customer.

For clarity on the move, we’ve compiled a frequently asked questions (FAQ) section detailing the migration steps. As the transition unfolds, we’ll continuously update this section with fresh insights and responses to queries from our customers. Should you not find the answer to your specific concern, please reach out to us via our service page. We’re here to assist. 

Technical changes

While the core functionality of our connections will remain consistent, there are distinct technical changes to be aware of. This is especially crucial for those who rely on self-monitoring.

IPv4
For (keepalive) monitoring, you can now use the following IP addresses. These can already be configured on your router. We advise implementing this adjustment as soon as possible. After migration, the old gateway IP address will no longer be reachable via ping (ICMP). Please note that pinging these IP addresses is only possible from a signetbreedband connection.

IP addresses for (keepalive) monitoring: 

91.216.162.78          ping1.signetbreedband.nl
91.216.162.79          ping2.signetbreedband.nl

Do you have a Sophos firewall? Then extra attention is required. Sophos firewalls have a keepalive set to the gateway in the default configuration. Sophos also calls this 'Uplink monitoring'. This can cause your connection to drop after migrating to our new core network. Therefore, before the migration, configure the keepalive settings on your Sophos firewall with one of the (ping) IP addresses as mentioned above to prevent issues.

IPv6
If you are using IPv6 and/or BGP, specific changes will be required on the connected equipment. We assess each connection to determine whether IPv6 and/or BGP are applied. We will contact each customer individually via email and also by phone, if applicable, to discuss what is needed and to coordinate the migration timing. For IPv6, after migration, the following (link-local) gateway address can be set: fe80::6aab:9ff:fe15:a401.

MAC address of our gateway
When migrating your connection, the MAC address of our gateway will also change. Please take this into account if you have static filtering or routing applied to it. 

Practical insights on the migration process

  • When is my connection set to migrate?

    Given the vast number of connections, it’s unfeasible to transition all at once. Thus, the migration is phased, and we’re addressing them batch-wise based on network partners. As soon as we finalise the schedule for your specific connection, we’ll keep you informed. For further details, please refer to the subsequent question.

  • Will I receive a notification when my connection’s migration is scheduled?

    Absolutely! We prioritize transparent communication. Once your connection is slated for migration, you’ll receive an email detailing the specific technical modifications and key considerations. Furthermore, every customer will get a personalised email, clearly stating the precise migration timing. Rest assured; you’ll be well-informed ahead of time. 

  • Who will be informed about the migration maintenance schedule?

    Prior to the actual migration process, we’ll disseminate a maintenance announcement specifying the exact timing of the migration. This notice will be forwarded to the designated technical contact we have on file for maintenance notifications. If you’re uncertain about receiving these communications, please reach out to us. We’ll verify the information and make any essential updates as needed.

  • How will the migration affect me?

    Our primary aim is to ensure a seamless transition for our customers. Thus, we’ve arranged for the migration to occur during evening hours or other suitable times to minimise any disruptions. Before the shift, you’ll be provided with a maintenance notification, giving you a clear picture of when your specific connection(s) will be migrated. Additionally, this communication will also cover any pertinent technical details to keep you abreast of the changes.

  • What steps should I take in anticipation of the migration?

    We've got the migration covered. There's no additional action needed from your end.

  • How was the Connectivity Core conceived?

    signetbreedband took the reins in conceptualising and constructing the Connectivity Core, collaborating closely with Nokia as a trusted partner, and also drawing support from team.blue and other providers. Within the team.blue framework, there’s a reservoir of architectural insight. Our network architects and engineers have harnessed this knowledge and expertise to its maximum potential. Opting for Nokia, a European vendor, allows us to maintain independence from both American and Chinese entities, reinforcing our commitment to operational reliability. For a deeper understanding of our core network’s evolution, click here (only in Dutch available).

  • Do you have additional questions?

    Should you wish to delve deeper into the specifics of the new core network or if there’s a query not addressed in this FAQ, please don’t hesitate to reach out. We’re here to assist and provide clarity! Contact us at: info@signetbreedband.nl

Contact us