Create a network with a dedicated server
Some configurations of Chipcore Line dedicated servers cannot be added to the global router network because they do not have a port to connect to the private network. The availability of a private network port can be checked in the control panel on the server page under the Ports tab.
- Create a global router.
- Connect the network and subnet to the global router up to the VLAN of the dedicated server.
- Connect the network and subnet to the global router before the cloud platform project.
- Assign IP addresses from the created subnets to the dedicated server.
- Write routes on the dedicated server.
- Create a cloud database cluster: new or from a backup of an existing cloud database cluster.
See an example of creating network connectivity between a dedicated server and a cloud database.
Example of network organization between a cloud database and a dedicated server
If you need to configure private connectivity between a dedicated server in the SPB-2 pool and a new cloud database in the ru-2 pool:
- Create a global router.
- Connect two private subnets to the router —
192.168.0.0.0/29
with gateway192.168.0.1
for SPB-2 pool and172.16.0.0.0/29
with gateway172.16.0.1 for
ru-2 pool. - Assign an address from the
192.168.0.0.0/29
subnet to a dedicated server, such as192.168.0.2
. - Write routes on the dedicated server in the SPB-2 pool — to subnet
172.16.0.0.0/29
through gateway192.168.0.1
. - Create a new cloud database cluster on subnet
172.16.0.0.0/29
.


Create a global router
- In the Control Panel, on the top menu, click Products and select Global Router.
- Click Create router. Each account has a limit of five global routers.
- Enter the name of the router.
- Click Create.
- If the router is created with the status
ERROR
or hangs in one of the statuses, create a ticket.
Connect the network and subnet to the router up to the VLAN of the dedicated 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 the Control Panel, on the top menu, click Products and select 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 a Servers and Hardware service.
-
Select a pool.
-
Select VLAN. If you want to create a network up to the internal segment (Q-in-Q), specify its tag, a number from 2 to 4094. If there is already a network up to the VLAN, be sure to specify the Q-in-Q segment of this 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 subnet of the server if it is not already added to any of the global routers in the account. The subnet must meet the conditions:
- belong to the RFC 1918 private address range:
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 are included in the global router network, the subnet must not overlap with the ranges
10.250.0.0.0/16
,10.10.0.0.0/16
and10.96.0.0.0/12
. These subnets participate in the internal addressing of Managed Kubernetes and their use can cause conflicts in the global router network.
- belong to the RFC 1918 private address range:
-
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 the 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 the network.
-
Click Create Network.
-
Optional: Check the network topology on the global router. In the control panel, in the top menu, click Products → Global Router → desired router page → Network Map.
Connect the network and subnet to the router before the cloud platform project
If the cloud platform network is connected to a global router, you can only manage it on the global router page.
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.
Connect a new network
Connect existing network
-
In the Control Panel, on the top menu, click Products and select 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 a Cloud Platform service.
-
Select a pool.
-
Select a project.
-
Enter the subnet name — this will only be used in the control panel.
-
Enter the CIDR — IP address and subnet mask. The subnet must meet the conditions:
- belong to the RFC 1918 private address range:
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 are included in the global router network, the subnet must not overlap with the ranges
10.250.0.0.0/16
,10.10.0.0.0/16
and10.96.0.0.0/12
. These subnets participate in the internal addressing of Managed Kubernetes and their use can cause conflicts in the global router network.
- belong to the RFC 1918 private address range:
-
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 the 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 the network.
-
Click Create Network.
-
Optional: Check the network topology on the global router. In the control panel, in the top menu, click Products → Global Router → desired router page → Network Map.
-
Check that the network has not yet been added to any of the account's global routers — in the Control Panel in the top menu, click Products and select Cloud Servers → Network section → 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:
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 are included in the global router network, the subnet must not overlap with the ranges
10.250.0.0.0/16
,10.10.0.0.0/16
and10.96.0.0.0/12
. These subnets participate in the internal addressing of Managed Kubernetes and their use can cause conflicts in the global router network.
- belongs to the RFC 1918 private address range:
-
In the dashboard, on the top menu, click Products and select Cloud Servers.
-
Open the Private Networks tab.
-
From the menu of the network, 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 the network. The last two free subnet addresses will be reserved as service addresses.
-
Click Connect. Do not close the window until you see a message that the network is connected. After that, in the Control Panel:
Assign an IP address to a dedicated server
To work with the subnet created on the router, configure a local port on the dedicated server that is included in the global router network. On the port, assign an IP address from the private subnet you created on the global router for the corresponding pool.
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>
— the name of the network interface of the private network;<ip_address>/<mask>
— private IP address of the server with a subnet mask, e.g.,192.168.0.2/29
.
-
Press the
ESC
key. -
Exit the
vi
text editor with your 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>
-name of the network interface of the private network;<ip_address>/<mask>
— private IP address of the server with a subnet mask, e.g,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>
is 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>"Specify:
<eth_name>
-name of the network interface of the private network;<ip_address>/<mask>
— private IP address of the server with a subnet mask, e.g,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 in the blog article Configuring Networking in CentOS 7.
-
Open the Network and Sharing Center.
-
Open the network interface of the private network.
-
Click Properties.
-
From the list, select IPv4.
-
Click Properties.
-
Specify the network interface parameters:
- IP-address — The private IP address of the server, e.g,
192.168.0.2
; - Subnet mask — subnet mask.
- IP-address — The private IP address of the server, e.g,
-
Press OK.
Specify routes on a dedicated server
If you create a new server and add 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 a global router network, it must have static routes to all subnets with which you want connectivity.
Ubuntu
Debian
CentOS
Windows
-
Open the CLI.
-
Open the network configuration file:
vi /etc/netplan/01-netcfg.yaml
-
Locate the data block for the desired network interface.
-
At the end of this block, add a route:
routes:
- to: <ip_address>/<mask>
via: <gateway>Specify:
<ip_address>/<mask>
— subnet to which the route is needed, specifying the mask, for example,192.168.0.0/29
;<gateway>
— gateway for the current server subnet, which is specified on the global router.
-
If you need to prescribe multiple routes, add them sequentially in the same block, for example,
routes:
- to: 192.168.0.0/29
via: 172.16.0.1
- to: 192.168.q.0/29
via: 172.16.0.1 -
Save the file.
-
Check the settings:
sudo netplan try
-
Apply the changes:
netplan apply
-
Open the CLI.
-
Open the network configuration file:
vi /etc/network/interfaces
-
Locate the data block of the corresponding network interface.
-
At the end of the block, 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>
— the subnet to which the route is needed, for example,192.168.0.0
;<mask>
— the mask of the subnet to which you want to route, for example,255.255.255.0
;<gateway>
— gateway for the current server subnet, which is specified on the global router.
-
If you need to prescribe multiple routes, add them sequentially in the same block.
-
Save the file.
-
Restart the network:
sudo /etc/init.d/networking restart
-
Open the CLI.
-
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>
— subnet to which the route is needed, specifying the mask, for example,192.168.0.0/29
;<gateway>
— gateway for the current server subnet, which is specified on the global router;<eth_name>
— 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, for example,
echo "192.168.0.0/29 via 172.16.0.1
192.168.1.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>
— the subnet to which the route is needed, for example,192.168.1.0
;<mask>
— the subnet mask of the subnet to which you want to route, for example,255.255.255.0
;<gateway>
— gateway for the current server subnet, which is specified on the global router;<x>
— parameter that determines the priority of the specified gateway, 1 being the highest priority.
Create a cloud database cluster
New
From the backup
-
In the Control panel, on the top menu, click Products and select Cloud Databases.
-
Click Create Cluster.
-
Enter the name of the cluster.
-
Select a region.
-
Select a pool. Once created, the pool cannot be changed.
-
Select RDBMS — Redis.
-
Select a version of Redis. Once created, the version cannot be changed.
-
Select a configuration line and a configuration.
-
Optional: to configure cluster fault tolerance, specify the number of nodes in the cluster in the Fault Tolerance block. The first node is the master node, the rest are replicas. SLA for a multi-node cluster — we guarantee 99.95% write availability and 99.99% read availability.
-
Choose a preemptive policy.
-
Enter the user password or click Generate. The password must contain:
- 32 to 64 characters;
- Latin letters of different cases;
- figures;
- special characters.
-
Copy and save the user password — you need it to connect to the cluster. The password cannot be viewed in the control panel, but can be changed.
-
Select the subnet that you connected to the global router before the cloud platform project.
You can restrict the list of addresses from which access to the database cluster will be allowed.
-
Check the price of the cluster.
-
Click Create Cluster. The cluster will be ready for operation when it enters
the ACTIVE
status.
-
In the Control panel, on the top menu, click Products and select Cloud Databases.
-
Click Create Cluster.
-
Select the pool that hosts your existing cloud database cluster.
-
Check the Restore cluster from backup checkbox.
-
Select an existing cloud database cluster.
-
Select how to restore the cluster — from the last available backup or to a specific point in time within the last 7 days.
-
Click Continue.
-
Select a configuration line and a configuration.
-
Optional: check the Add replicas checkbox and specify the number of replicas. Replicas increase the fault tolerance of the cluster.
-
Choose a preemptive policy.
-
Select the subnet that you connected to the global router before the cloud platform project.
You can restrict the list of addresses from which access to the database cluster will be allowed.
-
Click Create Cluster.
-
Once the cluster is rebuilt, the node addresses will change — change them in your application.