All Collections
Knowledge Base
Other useful information
Aqaba Jordan Route Server Migration Overview
Aqaba Jordan Route Server Migration Overview
Antoinette van der Stouwe avatar
Written by Antoinette van der Stouwe
Updated over a week ago

Customer Announcement Route Server Migration

Dear Peers and Customers, 
Aqaba IX is going to introduce two new route servers. We would like to ask you to carry out a configuration change on your equipment to reconfigure your BGP sessions for the Aqaba IX route servers between 2023-09-07 and 2023-09-14.
Please find all required info below:
rs1.aqabaix.com (new machine):
IPv4: 84.252.106.252
IPv6: 2a10:1100::3:2a9b:a:1
rs2.aqabaix.com (new machine):
IPv4: 84.252.106.253
IPv6: 2a10:1100::3:2a9b:a:2
You can configure both IPv4 and IPv6 BGP sessions beforehand, but please note that the new machines will not be made available/accept sessions before 2023-09-07. Important: Please configure these as additional sessions for now, and do not remove your old sessions yet!
We will shut down the old route servers on 2023-09-14.
Please also note that with the introduction of the new route servers we offer BGP communities to control your announcements, please see the following page for an overview: https://intercom.help/de-cix/en/articles/8272442-aqaba-jordan-route-server-migration-overview You can deconfigure old sessions at your convenience after the corresponding route server goes out of operation. This concludes the migration of your BGP sessions to the new Aqaba IX route servers.
Regards,
DE-CIX Customer Service

Peering LAN

IPv4: 84.252.106.0/24
IPv6: 2a10:1100::/64

RS Peering

RS

ASN

Old IPs

New IPs

207515

IPv4: 84.252.106.1
IPv6: 2a10:1100::1

IPv4: 84.252.106.252
IPv6: 2a10:1100::3:2a9b:a:1

207515

IPv4: 84.252.106.254
IPv6: 2a10:1100::254

IPv4: 84.252.106.253
IPv6: 2a10:1100::3:2a9b:a:2

BGP Action Communities Overview

Action

New BGP Community

Do not announce to any client

0:65534 or 207515:0:0

Announce to peer, even if tagged with the previous community

65534 :peer_as or 207515:1:peer_as

Do not announce to peer

0:peer_as or 207515:0:peer_as

Prepend the announcing ASN once to peer

65001:peer_as or 207515:101:peer_as

Prepend the announcing ASN twice to peer

65002:peer_as or 207515:102:peer_as

Prepend the announcing ASN thrice to peer

65003:peer_as or 207515:103:peer_as

Prepend the announcing ASN once to any

65001:0 or 207515:101:0

Prepend the announcing ASN twice to any

65002:0 or 207515:102:0

Prepend the announcing ASN thrice to any

65003:0 or 207515:103:0

Add NO_EXPORT to peer

207515:901:peer_as

Add NO_ADVERTISE to peer

207515:901:peer_as

Blackholing (RTBH)

65535:666

Required Customer Interaction

  • Customers will keep their current IPv4 and IPv6 addresses (but new customers will get DE-CIX addressing scheme IPv6 addresses assigned, but this not relevant for the migration)

  • Customers will need to reconfigure RS peerings

Timeline


Did this answer your question?