Skip to main content
Link database and dedicated server
Last update:

Link database and dedicated server

For your information

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.

  1. Create a global router.
  2. Connect the network and subnet to the global router up to the VLAN of the dedicated server.
  3. Connect the network and subnet to the global router before the cloud platform project.
  4. Assign IP addresses from the created subnets to the dedicated server.
  5. Write routes on the dedicated server.
  6. Create a cloud database cluster: new or from a backup of an existing cloud database cluster.

See an example of networking 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:

  1. Create a global router.
  2. Connect two private subnets to the router — 192.168.0.0.0/29 with gateway 192.168.0.1 for SPB-2 pool and 172.16.0.0.0/29 with gateway 172.16.0.1 for ru-2 pool.
  3. Assign an address from the 192.168.0.0.0/29 subnet to a dedicated server, such as 192.168.0.2.
  4. Write routes on the dedicated server in the SPB-2 pool — to subnet 172.16.0.0.0/29 through gateway 192.168.0.1.
  5. Create a new cloud database cluster on subnet 172.16.0.0.0/29.

1. Create a global router⁠

  1. In the Control Panel, on the top menu, click Products and select Global Router.
  2. Click Create router. Each account has a limit of five global routers.
  3. Enter the name of the router.
  4. Click Create.
  5. If the router is created with the status ERROR or hangs in one of the statuses, create a ticket.

2. Connect the network and subnet to the router 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.

  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, this will only be used in the control panel.

  5. Select a Servers and Hardware service.

  6. Select a pool.

  7. 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.

  8. Enter the subnet name — this will only be used in the control panel.

  9. 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, or 192.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 and 10.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.

  10. 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.

  11. 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.

  12. 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.

  13. Click Create Network.

  14. Optional: Check the network topology on the global router. In the control panel, from the top menu, click Products → Global Router → Router Page → Network Map.

3. Connect the network and subnet to the router before the cloud platform project⁠

For your information

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.

  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, this will only be used in the control panel.

  5. Select a Cloud Platform service.

  6. Select a pool.

  7. Select a project.

  8. Enter the subnet name — this will only be used in the control panel.

  9. 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, or 192.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 and 10.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.

  10. 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.

  11. 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.

  12. Click Create Network.

  13. Optional: Check the network topology on the global router. In the control panel, from the top menu, click Products → Global Router → Router Page → Network Map.

4. Assign an IP address to the 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.

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

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

    vi /etc/netplan/01-netcfg.yaml

  3. 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 subnet mask, e.g. 192.168.0.2/29, 192.168.0.2/29.

  4. Press the ESC key.

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

    :wq

  6. Apply the configuration:

    netplan apply

  7. Optional: reboot the server.

5. Write routes on the 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.

  1. Connect to the server.

  2. Open the CLI.

  3. Open the network configuration file:

    vi /etc/netplan/01-netcfg.yaml

  4. Locate the data block for the desired network interface.

  5. At the end of this block, 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;
    • <gateway> — gateway for the current server subnet, which is specified on the global router.

  6. 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

  7. Save the file.

  8. Check the settings:

    sudo netplan try

  9. Apply the changes:

    netplan apply

6. Create a cloud database cluster⁠

  1. In the dashboard, on the top menu, click Products and select Cloud Databases.

  2. Click Create Cluster.

  3. Enter the name of the cluster.

  4. Select a pool.

  5. Select the PostgreSQL version. Once created, the version cannot be changed.

  6. Select the node configuration:

    • fixed — configurations with different ratio of vCPU, RAM and local disk;
    • arbitrary — free choice of the ratio of resources.

  7. For a fixed configuration, select a configuration ruler:

    • Standard;
    • CPU;
    • Memory;
    • HighFreq.

  8. Optional: check the Add replicas checkbox and specify the number of replicas. Replicas increase the fault tolerance of the cluster.

  9. 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.

  10. Select the connection pooler mode:

    • transaction — the connection is assigned to the client for the duration of the transaction;
    • session — the connection is assigned while the client is connected;
    • statement — transactions with multiple operators are prohibited.

  11. Optional: change the DBMS settings by clicking Change. We recommend changing the settings values only when necessary — incorrectly selected values may reduce cluster performance.

  12. Click Create Database Cluster. The cluster will be ready for operation when it enters the ACTIVE status.