Link products and services via a global router

General instructions for setting up a global router network for all Servercore products. For examples of configuration for individual products (dedicated servers, Managed Databases, Managed Kubernetes), see the Linking Products and Services via a Global Router section.

For your information

Some dedicated server configurations cannot be added to a global router network because they lack a port for connecting to a private network. You can check for a private network port in the control panel on the server page on the Ports **** tab.

1. Create a global router.
2. Connect networks and subnets to the global router for each VLAN and cloud platform project that you want to connect.
3. Assign IP addresses from the subnets to the servers.
4. Optional: specify routes on the servers.
5. Optional: set up routing on the global router.

1. Create a global router

1. In the Control panel, in the top menu, click Products and select Global Router.
2. Click Create router. A limit of five global routers is set for each account.
3. Enter the router name.
4. Click Create.
5. If the router was created with the status ERROR or is stuck in one of the statuses, create a ticket.

2. Connect networks and subnets to the global router

Dedicated server

Use for a dedicated or hosted server.

You can connect a new or existing network to the router if it is not already connected to any of the account's global routers.

1. In the control panel, on the top menu, click Products and select Global Router.

2. Go to the router page → Networks tab.

3. Click Create network.

4. Enter a network name. It will only be used in the control panel.

5. Select the Servers and Equipment service.

6. Select a location for the network.

7. Select or enter a VLAN.

8. If you want to create a network up to an internal segment (Q-in-Q), specify its tag—a number from 2 to 4094. If a network already exists for the VLAN, you must specify the Q-in-Q segment of this VLAN.

9. Enter a subnet name. It will only be used in the control panel.

10. Enter the CIDR—the IP address and mask of the private subnet. You can enter a new subnet or an existing private server subnet if it has not yet been added to any of the global routers in the account. The subnet must meet the following conditions:

    • belong to the RFC 1918 private address range: 10.0.0.0/8, 172.16.0.0/12 or 192.168.0.0/16;
    • have a size of at least /29, as three addresses will be occupied by Servercore network equipment;
    • do not overlap with other subnets added to this router—IP addresses must not repeat across subnets on the same router;
    • if a Managed Kubernetes cluster on cloud servers is included in the global router network, the subnet must not overlap with the ranges 10.10.0.0/16, 10.96.0.0/12, 10.250.0.0/16 and 10.251.0.0/24. If a cluster on dedicated servers is included in the network — with ranges 10.10.0.0/16, 10.222.0.0/16, 10.250.0.0/16, 10.251.0.0/24 and 172.250.0.0/14. These subnets are used for Managed Kubernetes internal addressing, and their use may lead to conflicts in the global router network.

11. Enter the gateway IP or leave the first address from the subnet that is assigned by default. Do not assign this address to your devices to avoid network disruption.

12. Enter the service IPs or leave the last addresses from the subnet that are assigned by default. Do not assign these addresses to your devices to avoid network disruption.

13. Click Create network.

14. Optional: check the network topology on the global router. In the Control panel, in the top menu, click Products → Global Router → router page → Network map.

15. If you specified a Q-in-Q tag in step 8, you need to enable Q-in-Q technology on the switch port and configure the private network interface that you specified in step 10. Learn more in the Configure Q-in-Q section of the Q-in-Q guide.

Cloud platform

Use for a cloud server, Managed Kubernetes cluster nodes, or a Managed Database cluster.

You can connect a new or existing network to the router if it is not already connected to any of the account's global routers.

Connect a new network

1. In the Control panel, on the top menu, click Products and select Global Router.

2. Open the router page → Networks tab.

3. Click Create network.

4. Enter a network name. It will only be used in the control panel.

5. Select the Cloud Platform service.

6. Select a location for the network.

7. Select a project.

8. Enter a subnet name. It will only be used in the control panel.

9. Enter the CIDR — IP address and subnet mask. The subnet must meet the following conditions:

   • belong to the RFC 1918 private address range: 10.0.0.0/8, 172.16.0.0/12 or 192.168.0.0/16;
   • have a size of at least /29, as three addresses will be occupied by Servercore network equipment;
   • it does not overlap with other subnets added to this router — there must be no identical IP addresses within the subnets of one router;
   • if a Managed Kubernetes cluster on cloud servers is to be connected to the global router network, the subnet must not overlap with the 10.10.0.0/16, 10.96.0.0/12, 10.250.0.0/16 and 10.251.0.0/24. If a cluster on dedicated servers is connected to the network, it must not overlap with the 10.10.0.0/16, 10.222.0.0/16, 10.250.0.0/16, 10.251.0.0/24 and 172.250.0.0/14. These subnets are used for Managed Kubernetes internal addressing, and their use may cause conflicts in the global router network.

10. Enter the gateway IP or leave the first address from the subnet, which is assigned by default. Do not assign this address to your devices to avoid disrupting network operation.

11. Enter the service IPs or leave the last addresses from the subnet, which are assigned by default. Do not assign these addresses to your devices to avoid disrupting network operation.

12. Click Create network.

13. Optional: check the network topology on the global router. In the Control panel, on the top menu, click Products → Global Router → router page → Network Map.

Connect an existing network

1. Ensure the network is not already added to any global router in your account. In the Control panel, on the top menu, click Products → Cloud Servers → Network → tab Private networks → check that the network card does not have the tag Global Router.

2. Verify that the subnet meets the following conditions:

   • belongs to the RFC 1918 private address range: 10.0.0.0/8, 172.16.0.0/12 or 192.168.0.0/16;
   • is at least /29, as three addresses will be occupied by Servercore network equipment;
   • it does not overlap with other subnets added to this router: the IP addresses of each subnet on the router must not match the IP addresses of other subnets on it;
   • if a Managed Kubernetes cluster on cloud servers is to be connected to the global router network, the subnet must not overlap with the 10.10.0.0/16, 10.96.0.0/12, 10.250.0.0/16 and 10.251.0.0/24. If a cluster on dedicated servers is connected to the network, it must not overlap with the 10.10.0.0/16, 10.222.0.0/16, 10.250.0.0/16, 10.251.0.0/24 and 172.250.0.0/14. These subnets are used for Managed Kubernetes internal addressing, and their use may cause conflicts in the global router network.

3. In the Control panel, on the top menu, click Products and select Cloud Servers.

4. Go to Network → tab Private networks.

5. From the network menu, select Connect to Global Router.

6. Select a global router.

7. For each subnet in the network, enter the IP address to be assigned to the router or leave the first available address from the subnet, which is assigned by default. Do not assign this address to your devices to avoid disrupting network operation. The last two available subnet addresses will be reserved as service addresses.

8. Click Connect. Do not close the window until a message appears confirming the network has been connected. After that, in the control panel:

   • the network will appear in the section Servercore Global Router on the router page to which you connected it;
   • in the section Cloud Servers → Network → on the tab Private networks, the network will have the tag Global Router.

3. Assign IP addresses to the servers

On each server included in the global router network, configure a local port to work with the subnet created on the router. Assign an IP address from the private subnet that you connected to the global router for the corresponding VLAN or project.

Dedicated server

Ubuntu

1. Connect to the server via SSH or via KVM console.

2. Open the netplan utility configuration file with the vi:

   vi /etc/netplan/01-netcfg.yaml

3. Add or change the values of the private network interface settings:

       <eth_name>:
               addresses: [<ip_address>]

   Specify:

   • <eth_name> — the name of the private network interface;
   • <ip_address> — the private IP address of the server with a subnet mask, for example 192.168.0.2/24.

4. Press ESC.

5. Exit the vi text editor with your changes saved:

   :wq

6. Apply the configuration:

   netplan apply

7. Optional: reboot the server.

8. Optional: assign a private IP address to the server in the control panel.

Debian

1. Connect to the server via SSH or via KVM console.

2. Open the network interfaces configuration file with the vi:

   vi /etc/network/interfaces.d/50-cloud-init

3. Add or change the values of the private network interface settings:

   auto <eth_name>
   iface <eth_name> inet static
       address <ip_address>/<mask>

   Specify:

   • <eth_name> — the name of the private network interface;
   • <ip_address> — the private IP address of the server, for example 192.168.0.2;
   • <mask> — the subnet mask, for example /24.

4. Press ESC.

5. Exit the vi text editor with your changes saved:

   :wq

6. Restart the network:

   service networking restart

7. Optional: reboot the server.

8. Optional: assign a private IP address to the server in the control panel.

CentOS

1. Connect to the server via SSH or via KVM console.

2. Output information about the network interfaces:

   ip address

3. Create or open the private network interface configuration file with the vi:

   vi /etc/sysconfig/network-scripts/ifcfg-<eth_name>

   Specify <eth_name> — the name of the private network interface.

4. Add or change the values of the network interface settings:

   NAME="<eth_name>"
   ONBOOT=yes
   BOOTPROTO=none
   IPADDR="<ip_address>"

   Specify:

   • <eth_name> — the name of the private network interface;
   • <ip_address> — the private IP address of the server with a subnet mask, for example 192.168.0.2/24;

5. Press ESC.

6. Exit the vi text editor with your changes saved:

   :wq

7. Restart the network:

   systemctl restart network

8. Optional: reboot the server.

9. Optional: assign a private IP address to the server in the control panel.

Windows

1. Connect to the server via RDP or via KVM console.

2. Open the Network and Sharing Center.

3. Open the private network interface.

4. Click Properties.

5. From the list, select IPv4.

6. Click Properties.

7. Specify the network interface parameters:

   • IP-address — the private IP address of the server with a subnet mask, for example 192.168.0.2;
   • Subnet mask — the subnet mask.

8. Click OK.

9. Optional: assign a private IP address to the server in the control panel.

Cloud platform

1. Add a cloud server or Managed Kubernetes cluster node to the created global router subnet. If you do not have a server or node yet, create one. When creating it, select the global router subnet as the subnet.

2. Apply changes depending on the Apply changes port parameter. You can view the parameter value in the control panel: in the top menu, click Products → Cloud Servers → server page → Ports tab → Port settings:

   • When rebooting the server — programmatically reboot the cloud server or manually make changes to the network configuration file on the server;
   • Manually in the network configuration file on the server — manually make changes to the network configuration file on the server.

4. Specify routes on devices

Example of static route organization

You need to configure private communication between two dedicated servers in the SPB-2 pool and a cloud server in the ru-2 pool. To do this, you need to:

1. Create a global router with two private subnets — 192.168.0.0/28 to the VLAN that contains the dedicated servers in the SPB-2 pool, and 172.16.0.0/28 to the cloud platform project in the ru-2 pool.

2. Assign addresses from the subnets to the servers.

3. Specify routes:

   • for each server in the SPB-2 pool — to the 172.16.0.0/28 subnet via the 192.168.0.1 gateway;
   • for the server in the ru-2 pool — to the 192.168.0.0/28 subnet via the 172.16.0.1 gateway.

Specify static routes

Dedicated server, Cloud powered by VMware

Ubuntu

1. Connect to the server.

2. Open the network configuration file:

   vi /etc/netplan/01-netcfg.yaml

3. At the end of the data block for the required network interface, add the route:

   routes:
     - to: <ip_address>/<mask>
       via: <gateway>

   Specify:

   • <ip_address>/<mask> — the subnet to which you need to add a route, specifying the mask, for example 192.168.0.0/28;
   • <gateway> — the gateway for the current server's subnet, which is specified on the global router.

4. If you need to define multiple routes, add them sequentially in the same block, for example:

   routes:
   - to: 192.168.0.0/28
       via: 172.16.0.1
   - to: 192.168.1.0/28
       via: 172.16.0.1

5. Save the file.

6. Check the settings:

   sudo netplan try

7. Apply the changes:

   netplan apply

Debian

1. Connect to the server.

2. Open the network configuration file:

   vi  /etc/network/interfaces

3. At the end of the data block for the corresponding network interface, add the required route:

   up route add -net <ip_address> netmask <mask> gw <gateway>
   down route del -net <ip_address> netmask <mask> gw <gateway>

   Specify:

   • <ip_address> — the subnet to which you need to add a route, for example 192.168.0.0;
   • <mask> — the subnet mask to which you need to add a route, for example 255.255.255.0;
   • <gateway> — the gateway for the current server's subnet, which is specified on the global router.

4. If you need to define multiple routes, add them sequentially in the same block.

5. Save the file.

6. Restart the network:

   sudo /etc/init.d/networking restart

CentOS

1. Connect to the server.

2. Create and fill out the file for configuring static routes:

   echo "<ip_address>/<mask> via <gateway>" >> /etc/sysconfig/network-scripts/route-<eth_name>

   Specify:

   • <ip_address>/<mask> — the subnet to which you need to add a route, specifying the mask, for example 192.168.1.0/28;
   • <gateway> — the gateway for the current server's subnet, which is specified on the global router;
   • <eth_name> — the name of the corresponding local network interface.

   If you need to add multiple routes, specify them in one command. List each route on a new line, for example:

   echo "192.168.0.0/28 via 172.16.0.1
   192.168.1.0/28 via 172.16.0.1" >> /etc/sysconfig/network-scripts/route-eno2

3. Restart the network:

   systemctl restart network

Windows

1. Connect to the server via RDP or via KVM console.

2. Add the required routes one by one:

   route -p ADD <ip_address> MASK <mask> <gateway> METRIC <x>

   Specify:

   • <ip_address> — the subnet to which you need to add a route, for example 192.168.0.0;
   • <mask> — the subnet mask to which you need to add a route, for example 255.255.255.0;
   • <gateway> — the gateway for the current server's subnet, which is specified on the global router;
   • <x> — a parameter determining the priority of the specified gateway, 1 being the highest priority.

Cloud platform

To specify static routes for a cloud server, Managed Database cluster, or Managed Kubernetes cluster, you must configure static routes on the private subnet where the server or cluster resides.

In the subnets, you must configure routes to all other global router subnets that will exchange traffic.

5. Configure routing on the global router

You need to configure routing on the global router if one of the devices in its network is used as a router to send traffic to the internet or a network outside the Servercore infrastructure.

You can specify static routes or configure dynamic BGP routing.

Specify static routes

1. In the control panel, in the top menu, click Products and select Global Router.
2. Open the router page → Static Routes tab.
3. Click Create route.
4. Enter a route name — any name; it will only be displayed in the control panel.
5. Enter the destination subnet CIDR — this is the private subnet where you need to direct traffic. The destination subnet must not overlap with the subnets on the global router. For internet traffic, specify 0.0.0.0/0.
6. Enter the Next hop IP address — the IP address of the server through which the traffic will be directed to the destination subnet. The IP address must belong to one of the subnets on the global router.
7. Click Create.

Configure dynamic BGP routing

1. In the control panel, in the top menu, click Products and select Global Router.
2. Open the router page → BGP tab.
3. Click Configure BGP.
4. Enter the BGP neighbor IP address (BGP neighbor) — for example, the address of the router to which traffic is sent from the global router. The IP address must belong to one of the subnets connected to the global router.
5. Enter the autonomous system (AS) number. You can specify a private AS from the 64512–65534 range, except for AS 64530, which is used for the global router.
6. Specify the tasks for which dynamic BGP routing is required.
7. Click Create ticket. We will clarify the details in the ticket and provide further instructions on establishing the connection.