Skip to main content
Create a network with a dedicated server
Last update:

Create a network with a dedicated server

For your information

Some dedicated server configurations Chipcore Line cannot be added to the global router's network because they do not have a port to connect to the private network. You can check the availability of a port for the private network in the control panel on the server page under the tab Ports.

  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 a dedicated server.
  6. Create a cloud database cluster.

Check it out network organization example between the dedicated server and the 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/29 gateway 192.168.0.1 for the SPB-2 pool and 172.16.0.0/29 gateway 172.16.0.1for pool ru-2.
  3. Assign an address from a subnet 192.168.0.0/29 on a dedicated server, such as 192.168.0.2.
  4. Write routes on the dedicated server in the SPB-2 pool — to a subnet 172.16.0.0/29 through the gateway 192.168.0.1.
  5. Create a new cloud database cluster in a subnetwork 172.16.0.0/29.

Create a global router⁠

  1. In control panel go to Network services → Selectel Global Router.
  2. Click Create a router. Each account is set limit to five global routers.
  3. Enter the name of the router.
  4. Click Create.
  5. If the router was created with status ERROR or hovering in one of the statuses, file 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.

  1. In control panel go to Network services → Selectel Global Router.

  2. Open the router page → tab Networks.

  3. Click Create a network.

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

  5. Select a service Dedicated servers.

  6. Select 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/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 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 ranges 10.250.0.0/16, 10.10.0.0/16 and 10.96.0.0/12. These subnets participate in the internal addressing of Managed Kubernetes, their use may cause conflicts in the global router network.

  10. If you have specified a Q-in-Q tag, make sure to set up a 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 a network.

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

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 control panel go to Network services → Selectel Global Router.

  2. Open the router page → tab Networks.

  3. Click Create a network.

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

  5. Select a service Cloud platform.

  6. Select pool.

  7. Select 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/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 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 ranges 10.250.0.0/16, 10.10.0.0/16 and 10.96.0.0/12. These subnets participate in the internal addressing of Managed Kubernetes, their use may 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 a network.

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

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.

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

  2. Open the utility configuration file netplan 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> — 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.

  4. Press the key ESC.

  5. Exit the text editor vi with the changes intact:

    :wq

  6. Apply the configuration:

    netplan apply

  7. Optional: reboot the server.

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.

  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> — subnet to which you want to route, 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: 192.168.0.1
    - to: 192.168.1.0/29
        via: 192.168.0.1

  7. Save the file.

  8. Check the settings:

    sudo netplan try

  9. Apply the changes:

    netplan apply

Create a cloud database cluster⁠

  1. In control panel go to Cloud platform → Databases.

  2. Click Create a cluster.

  3. Enter the name of the cluster.

  4. Select region and pool.

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

  6. Select 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 configuration line:

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

  8. Select the type of subnet to which the cluster will be connected:

    • private subnet — a subnet without access from the Internet;

    • public subnet — all addresses on the public subnet are accessible from the Internet.

      A public IP address cannot be used.

      Addresses are assigned to each node in the cluster. Make sure that the number of addresses in the network is not less than the number of nodes in the cluster. Once a cluster is created, the network cannot be changed.

      You can address list from which access to the database cluster will be allowed.

  9. If you selected a private subnet, specify the subnet's CIDR.

  10. If you want to use DHCP for a private subnet, turn on the toggle switch DHCP. Read more about the DHCP protocol in Selectel's blog article How DHCP works.

  11. If you selected a public network, specify the subnet size.

  12. Optional: change DBMS settings To do this, press Modify. We recommend that you change the settings only when necessary — incorrect values can reduce cluster performance.

  13. Click Create a database cluster. The cluster will be ready for operation when it moves to status ACTIVE.