Link products and services through a global router
General instructions for setting up a global router network for all Selectel products. For configuration examples for individual products (dedicated servers, cloud databases, Managed Kubernetes), see Link products and services via global router.
Some configurations of dedicated servers Chipcore Line cannot be added to a global router network because they do not have a port to connect to a private network. The availability of a private network port can be checked in control panel on the server page under the Ports tab.
- Create global router.
- Connect-networks-and-subnets-to-global-router to each VLAN and cloud platform project whose servers you want to merge. For VMware-based Cloud, you can add networks and subnets only through technical support.
- Assign IP addresses from created subnets to servers.
- Optional: write-routes-on-servers.
- Optional: configure-routing-on-global-router.
1. Create a global router
- In Control Panel, go to Network Services → Selectel Global Router.
- Click Create Router. Each account has a limit of five global routers.
- Enter the name of the router.
- Press Create.
- If the router was created with status ERROR or hung in one of the statuses, create a ticket.
2. Connect networks and subnets to a global router
- Выделенный сервер
- Облачная платформа
Use for a dedicated or hosted server.
You can connect a new network to the router or an existing network if it is not already connected to any of the account's global routers.
-
In Control Panel, go to Network Services → Selectel Global Router.
-
Open the router page → Networks tab.
-
Click Create Network.
-
Enter a network name, this will only be used in the control panel.
-
Select the Dedicated Servers service.
-
Select pool.
-
Select VLAN. If you want to network to an internal segment (Q-in-Q), specify its tag, a number between 2 and 4094. If there is already a network upstream of the VLAN, be sure to specify the Q-in-Q segment of that VLAN.
-
Enter the subnet name — this will only be used in the control panel.
-
Enter the CIDR — IP address and private subnet mask. You can enter a new subnet or an existing private server subnet, if it has not already been added to any of the global routers in the account. The subnetwork must meet the conditions:
- belong to the RFC 1918 private address range of
10.0.0.0.0/8
,172.16.0.0.0/12
, or192.168.0.0.0/16
; - have a size of at least /29, as three addresses will be occupied by Selectel network equipment;
- Do not overlap with other subnets added to this router: The IP addresses of each subnet on the router must not overlap with the IP addresses of other subnets on the router;
- if Managed Kubernetes nodes will be included in the global router network, the subnet must not overlap with the
10.250.0.0.0/16
,10.10.0.0.0/16
, and10.96.0.0.0/12
ranges. These subnets participate in the internal addressing of Managed Kubernetes, their use can cause conflicts in the global router network.
- belong to the RFC 1918 private address range of
-
If you specified the Q-in-Q tag, make sure to configure Q-in-Q. When configuring, use the subnet you specified in step 9.
-
Enter the gateway IP or leave the first address from the subnet assigned by default. Do not assign this address to your devices to avoid disrupting your network.
-
Enter service IPs or leave the last addresses from the subnet assigned by default. Do not assign these addresses to your devices to avoid disrupting your network.
-
Click Create Network.
-
Optional: check the network topology on the global router. In Control Panel, go to Network Services → Selectel Global Router. Open the page of the desired router and click Network Map.
If the cloud platform network is connected to a global router, you can only manage it on the global router page.
Use for a cloud server, Managed Kubernetes cluster node, or cloud database cluster.
You can connect a new network to the router or an existing network if it is not already connected to any of the account's global routers.
- Подключить новую сеть
- Подключить существующую сеть
-
In Control Panel, go to Network Services → Selectel Global Router.
-
Open the router page → Networks tab.
-
Click Create Network.
-
Enter a network name, this will only be used in the control panel.
-
Select the Cloud Platform service.
-
Select pool.
-
Select project.
-
Enter the subnet name — this will only be used in the control panel.
-
Enter the CIDR — IP address and subnet mask. The subnetwork must meet the conditions:
- belong to the RFC 1918 private address range of
10.0.0.0.0/8
,172.16.0.0.0/12
, or192.168.0.0.0/16
; - have a size of at least /29, as three addresses will be occupied by Selectel network equipment;
- Do not overlap with other subnets added to this router: The IP addresses of each subnet on the router must not overlap with the IP addresses of other subnets on the router;
- if Managed Kubernetes nodes will be included in the global router network, the subnet must not overlap with the
10.250.0.0.0/16
,10.10.0.0.0/16
, and10.96.0.0.0/12
ranges. These subnets participate in the internal addressing of Managed Kubernetes, their use can cause conflicts in the global router network.
- belong to the RFC 1918 private address range of
-
Enter the gateway IP or leave the first address from the subnet assigned by default. Do not assign this address to your devices to avoid disrupting your network.
-
Enter service IPs or leave the last addresses from the subnet assigned by default. Do not assign these addresses to your devices to avoid disrupting your network.
-
Click Create Network.
-
Optional: check the network topology on the global router. In Control Panel, go to Network Services → Selectel Global Router. Open the page of the desired router and click Network Map.
-
Check that the network has not yet been added to any of the account's global routers — in dashboard under Cloud Platform → Network → Private Networks tab it does not have the Global Router tag.
-
Verify that the subnet meets the conditions:
- belongs to the RFC 1918 private address range of
10.0.0.0.0/8
,172.16.0.0.0/12
, or192.168.0.0.0/16
; - is at least /29, as three addresses will be occupied by Selectel network equipment;
- does not overlap with other subnets added to this router: the IP addresses of each subnet on the router must not overlap with the IP addresses of other subnets on the router;
- if Managed Kubernetes nodes will be included in the global router network, the subnet must not overlap with the
10.250.0.0.0/16
,10.10.0.0.0/16
, and10.96.0.0.0/12
ranges. These subnets participate in the internal addressing of Managed Kubernetes, their use can cause conflicts in the global router network.
- belongs to the RFC 1918 private address range of
-
In Control Panel, go to Cloud Platform → Network.
-
Open the Private Networks tab.
-
From the network menu, select Connect to Global Router.
-
Select the global router.
-
For each of the network subnets, enter the IP address that will be assigned to the router, or leave the first available address from the subnet assigned by default. Do not assign this address to your devices to avoid disrupting your network. The last two free subnet addresses will be reserved as service addresses.
-
Press Connect. Do not close the window until you see a message that the network is connected. After that, in the control panel:
3. Assign IP addresses to the servers
On each server that is included in the global router network, configure a local port to work with the subnet created on the router. On the port, assign an IP address from the private subnet that you connected to the global router for the appropriate VLAN or project.
- Выделенный сервер
- Облачная платформа
- Облако на базе VMware
- Ubuntu
- Debian
- CentOS
- Windows
-
Open the
netplan
utility configuration file with the vi text editor:vi /etc/netplan/01-netcfg.yaml
-
Add or change values for the network interface settings of the private network:
<eth_name>:
addresses: [<ip_address>/<mask>]Specify:
<eth_name>
is the name of the network interface of the private network;<ip_address>/<mask>
— the private IP address of the server with a subnet mask, for example,192.168.0.2/29
.
-
Press the
ESC
key. -
Exit the
vi
text editor with the changes saved::wq
-
Apply the configuration:
netplan apply
-
Optional: reboot the server.
-
Open the network interfaces configuration file with the vi text editor:
vi /etc/network/interfaces
-
Add or change values for the network interface settings of the private network:
auto <eth_name>
iface <eth_name> inet static
address <ip_address>/<mask>Specify:
<eth_name>
is the name of the network interface of the private network;<ip_address>/<mask>
— the private IP address of the server with a subnet mask, for example,192.168.0.2/29
;
-
Press the
ESC
key. -
Exit the vi text editor with your changes saved:
:wq
-
Restart the network:
service networking restart
-
Optional: reboot the server.
-
Output information about the network interfaces:
ip address
-
Create or open the private network interface configuration file with the vi text editor:
vi /etc/sysconfig/network-scripts/ifcfg-<eth_name>
Specify
<eth_name>
as the name of the network interface of the private network. -
Add or change the values of the network interface settings:
NAME="<eth_name>"
ONBOOT=yes
BOOTPROTO=none
IPADDR="<ip_address>/<mask>"Specify:
<eth_name>
is the name of the network interface of the private network;<ip_address>/<mask>
— the private IP address of the server with a subnet mask, for example,192.168.0.2/29
;
-
Press the
ESC
key. -
Exit the vi text editor with your changes saved:
:wq
-
Restart the network:
systemctl restart network
-
Optional: reboot the server.
An example of changing network settings in CentOS is in the blog article Configuring Networking in CentOS 7.
-
Open the Network and Sharing Center.
-
Open the network interface of the private network.
-
Press Properties.
-
From the list, select IPv4.
-
Press Properties.
-
Specify the network interface parameters:
- IP-address is the private IP address of the server, for example,
192.168.0.2
; - Subnet mask — subnet mask.
- IP-address is the private IP address of the server, for example,
-
Press OK.
-
Add a cloud server or Managed Kubernetes cluster node to the created global router subnet. If you don't already have a server or node, create one. When creating, select the subnet of the global router as the subnet.
-
Apply the changes depending on the Apply Changes parameter in the Port Setup block. The value of the parameter can be viewed in Control Panel under Cloud Platform → Servers → Cloud Server page:
- 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.
- Open the Cloud Director panel.
- Click the Virtual Machines tab.
- In the block of the desired virtual machine, click the Details button.
- In the Hardware block, select the NICs block and click the Edit — New button.
- Select the global router network.
- Press the Save button.
4. write routes on the devices
If you have created a new server and added it to an existing global router network, you do not need to specify routes. In this case, the server will be immediately available to other devices on the network.
If you are adding an existing server to the global router network, you must #write-static-routes to all subnets with which you want connectivity.
Example of static route organization
You need to configure private communication between two dedicated servers in the SPB-1 pool and a cloud server in the ru-2 pool. To do this, you need:
-
Create a global router with two private subnets —
192.168.0.0.0/29
to the VLAN that contains the dedicated servers in pool SPB-1, and172.16.0.0.0/29
to the cloud platform project in pool ru-2. -
Assign addresses from subnets to servers.
-
write routes:
- on each server in the SPB-1 pool to the
172.16.0.0.0/29
subnet via the192.168.0.1
gateway; - on the server in pool ru-2 — to subnet
192.168.0.0.0/29
through gateway172.16.0.1
.
- on each server in the SPB-1 pool to the
write static routes
- Выделенный сервер, облако на базе VMware
- Ubuntu
- Выделенный сервер
-
Open the network configuration file:
vi /etc/netplan/01-netcfg.yaml
-
At the end of the data block of the desired network interface, add a route:
routes:
- to: <ip_address>/<mask>
via: <gateway>Specify:
<ip_address>/<mask>
— the subnet to which the route is needed, specifying the mask, for example,192.168.0.0.0/29
;<gateway>
is the gateway for the current server's subnet, which is specified on the global router.
-
If you need to write multiple routes, add them sequentially in the same block, for example:
routes:
- to: 192.168.0.0.0/29
via: 172.16.0.1
- to: 192.168.1.0.0/29
via: 172.16.0.1 -
Save the file.
-
Check the settings:
sudo netplan try
-
Apply the changes:
netplan apply
- Ubuntu
- Debian
- CentOS
- Windows
-
Open the network configuration file:
vi /etc/netplan/01-netcfg.yaml
-
At the end of the data block of the desired network interface, add a route:
routes:
- to: <ip_address>/<mask>
via: <gateway>Specify:
<ip_address>/<mask>
— the subnet to which the route is needed, specifying the mask, for example,192.168.0.0.0/29
;<gateway>
is the gateway for the current server's subnet, which is specified on the global router.
-
If you need to write multiple routes, add them sequentially in the same block, for example:
routes:
- to: 192.168.0.0.0/29
via: 172.16.0.1
- to: 192.168.1.0.0/29
via: 172.16.0.1 -
Save the file.
-
Check the settings:
sudo netplan try
-
Apply the changes:
netplan apply
-
Open the network configuration file:
vi /etc/network/interfaces
-
At the end of the data block of the corresponding network interface, add the desired route:
up route add -net <ip_address> netmask <mask> gw <gateway>
down route del -net <ip_address> netmask <mask> gw <gateway>Specify:
<ip_address>
is the subnet to which the route is needed, for example,192.168.0.0
;<mask>
is the subnet mask to which the route is needed, for example,255.255.255.0
;<gateway>
is the gateway for the current server's subnet, which is specified on the global router.
-
If you need to write multiple routes, add them sequentially in the same block.
-
Save the file.
-
Restart the network:
sudo /etc/init.d/networking restart
-
Create and complete a file to configure static routes:
echo "<ip_address>/<mask> via <gateway>" >> /etc/sysconfig/network-scripts/route-<eth_name>
Specify:
<ip_address>/<mask>
— the subnet to which the route is needed, specifying the mask, for example,192.168.1.0.0/29
;<gateway>
is the gateway for the current server's subnet, which is specified on the global router;<eth_name>
is the name of the corresponding LAN interface.
If you need to add multiple routes, specify them in one command. Specify each route on a new line, e.g.:
echo "192.168.0.0.0/29 via 172.16.0.1
192.168.1.0.0/29 via 172.16.0.1" >> /etc/sysconfig/network-scripts/route-eno2 -
Restart the network:
systemctl restart network
-
Add the required routes one at a time:
route -p ADD <ip_address> MASK <mask> <gateway> METRIC <x>
Specify:
<ip_address>
is the subnet to which the route is needed, for example,192.168.0.0
;<mask>
is the subnet mask to which the route is needed, for example,255.255.255.0
;<gateway>
is the gateway for the current server's subnet, which is specified on the global router;<x>
is a parameter that specifies the priority of the specified gateway, 1 being the highest priority.
5. Configure routing on a global router
You need to write static routes or configure dynamic BGP routing on the global router if you:
- organize Internet access on the global router network through one of the connected devices;
- or you plan to use a network larger than /29 and your server as a router.
- Прописать статические маршруты
- Настроить динамическую маршрутизацию по BGP
- In Control Panel, go to Network Services→ Selectel Global Router.
- Open the router page → Static Routes tab.
- Press Create Route.
- Enter a route name — any name, it will only appear in the control panel.
- Enter the CIDR of the destination subnet — this is the private subnet to which you want to direct traffic. The destination subnet must not overlap with subnets on the global router. To direct Internet traffic to one of the devices on the global router network, specify
0.0.0.0.0/0/0
. - Enter the IP address Next hop — the IP address of the server through which traffic will be routed to the destination subnet. The IP address must belong to one of the subnets on the global router.
- Press Create.
- In Control Panel, go to Network Services → Selectel Global Router.
- Open the router page → BGP tab.
- Click Customize BGP.
- Enter the IP address of the BGP neighbor — for example, the address of the router to which traffic from the global router is sent. The IP address must belong to one of the subnets connected to the global router.
- Enter the autonomous system (AS) number. You can specify a private AS from the range 64512-65534, except AS 64530, which is used for the global router.
- Specify the tasks that require dynamic routing over BGP.
- Click Create Ticket. In the ticket, we will clarify the data and provide further instructions on how to organize the connection.