How to bring your own ASN with IP prefix to Cherry Servers

Learn to integrate your own ASN and IP prefixes into Cherry Servers network infrastructure for seamless BGP routing.

Key points to consider

• You must specify the Cherry Servers location where your ASN will be announced. Each Cherry Servers data center operates under a distinct ASN, and selecting the correct one ensures proper routing.
• For proper routing, import and export remarks must be added to your ASN object.  This step allows your IP prefixes to be accepted and announced correctly within the Cherry Servers network.
• All IP prefixes must have valid ROA records, and LOA documentation is recommended. This guarantees route authenticity, preventing prefix hijacking or misconfiguration issues.
• Ensure that your prefixes are not blocked to avoid connectivity issues. Blocked prefixes may be filtered by ISPs, leading to reachability problems.
• Cherry Servers will verify your ASN and IP prefix validity, which may take up to 24 hours. This review ensures compliance with security policies and network integrity.

Step-by-step instructions

Step 1: Select a Cherry Servers location

First, decide which Cherry Servers data center your ASN and IP prefixes will be used for. Each Cherry Server location has a different Autonomous System Number (ASN):

Step 2: Update your ASN object

To establish routing with Cherry Servers, update your ASN object with the correct import/export remarks. For example, if you are using Cherry Servers in Lithuania (LT), add the following lines:

import:         from AS16125 accept ANY

export:         to AS16125 announce <your ASN>

Make sure to replace AS16125 with the correct Cherry Servers ASN for your selected location.

Step 3: Submit your ASN and IP prefix for validation

Once you have updated your ASN object, provide Cherry Servers with:

• Your ASN
• The IP prefixes you wish to bring
• ROA records (required)
• LOA documentation (recommended)

Important: Before submitting, ensure that your IP prefixes are not blocked in public IP databases for botnets or spamming!

Cherry Servers will verify your request, which typically takes less than 24 hours but may take up to a full day.

Step 4: Configure BGP on your Cherry Servers project

Once validation is complete, your Cherry Servers project will be assigned your ASN.

1. Log into your Cherry Servers Client Portal.
2. Navigate to Network > Local BGP under each ordered server.
3. Copy the provided BGP configuration from the Local BGP section and paste it into your server terminal to apply it.

Note: your BGP configuration must be adjusted based on the IP prefix you bring.

For detailed instructions on managing Local BGP configurations within Cherry Servers, refer to the Local BGP service guide.

Step 5: Apply BGP configuration on your server

Your server must establish a BGP session with Cherry Servers to announce the IP prefix. This configuration depends on your server's OS and routing software. Most Linux-based servers use BIRD, while Windows-based systems may require a third-party BGP client.

For BIRD v1.6, add the following BGP configuration for your prefix:

protocol static stat_my_pfx {
        table master;
        route <your prefix> via <your server main IP>;
}

Replace <your prefix> with your actual IP prefix and <your server main IP> with the primary IP assigned to your server.

Step 6: Wait for global propagation

After announcing your IP prefix, it may take up to 24 hours for ISPs worldwide to recognize the new subnet.

While most ISPs recognize new prefix announcements within a few hours, some networks may take the full 24-hour period before fully accepting the route. You can monitor the propagation of your announced prefix using tools such as:

• Hurricane Electric's BGP Toolkit – Provides visibility into your BGP routes across the internet.
• RIPEstat – Analyzes routing and ASN details for your prefix.
• BGPView – Monitors real-time prefix propagation and peer announcements.

Once propagation is complete, your IP prefix will be fully operational and available for use under the server announcing it.

Summary

Bringing your ASN and IP prefix to Cherry Servers allows you to manage your routing more effectively. The process involves selecting a data center, updating your ASN object, submitting your ASN and prefixes for validation, and configuring BGP on your server. Once your prefix is announced, allow up to 24 hours for ISPs worldwide to recognize the new subnet. Proper validation, including ROA records and blocklist checks, is essential for a seamless setup.