Connect file storage to a dedicated server

File storage and a dedicated server are always located in different pools, so to connect file storage to a dedicated server, you need to set up private L3 network connectivity via a global router.

note

Some Chipcore Line dedicated server configurations cannot be added to a global router network because they do not have a port for connecting to a private network. You can check if a private network port is available in the control panel: in the top menu, click Products and select Dedicated Servers → Servers → server page → Ports tab.

1. Create a global router.

2. Connect the network and subnet to the dedicated server VLAN to the global router.

3. Connect the network and subnet for file storage to the global router.

4. Assign an IP address to the dedicated server.

5. Configure a route on the dedicated server.

6. Configure a route in the file storage subnet.

7. Create file storage.

8. Mount the file storage to the dedicated server.

See the example of connecting file storage to a dedicated server.

Example of connecting file storage to a dedicated server

For example, you want to connect file storage in pool ru-2 to a dedicated server in pool SPB-2.

1. Create a global router.

2. Connect two private subnets to the global router: 192.168.0.0/29 with gateway 192.168.0.1 for pool SPB-2 and 172.16.0.0/29 with gateway 172.16.0.1 for pool ru-2.

3. Assign an address from the subnet 192.168.0.0/29 to the dedicated server, for example 192.168.0.2.

4. Configure a route on the dedicated server in the SPB-2 pool to subnet 172.16.0.0/29 via gateway 192.168.0.1.

5. Create file storage in subnet 172.16.0.0/29.

6. Mount the file storage to the dedicated server.

1. Create a global router

1. In the control panel, in 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 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 the network and subnet to the router up to the dedicated server VLAN

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, from 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 Servers and hardware service.

6. Select the location of the network.

7. Select or enter a VLAN.

8. If you want to create a network 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, because three addresses will be occupied by Servercore network equipment;
    • do not overlap with other subnets added to this router — there must be no identical IP addresses within subnets on the same router;
    • if a Managed Kubernetes cluster on cloud servers is connected to 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 connected to the network — with the 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 in 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, which 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, which 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, from the top menu, click Products → Global Router → router page → Network map.

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

3. Connect the network and subnet for the file storage to the router

You need to connect the network and subnet to the global router for the project and pool where the file storage will be created in the future.

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

1. In the control panel, in 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 the location where the file storage will be created.

7. Select the project where the file storage will be created.

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

9. Enter the CIDR — the IP address and the 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;
   • be at least /29 in size, since three addresses will be occupied by Servercore network equipment;
   • it must not overlap with other subnets added to this router — there must be no identical IP addresses within the subnets of a single router;
   • if a Managed Kubernetes cluster on cloud servers is connected to 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 connected to the network, with the 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 internal Managed Kubernetes addressing, and using them may cause conflicts in the global router network.

10. Enter a 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 network disruption.

11. Enter 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 network disruption.

12. Click Create network.

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

Connect an existing network

1. 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 → Cloud Servers → Network → Private networks tab → check that the network card does not have the Global Router tag.

2. Ensure 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 in size, since 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 overlap with the IP addresses of other subnets on it;
   • if a Managed Kubernetes cluster on cloud servers is connected to 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 connected to the network, with the 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 internal Managed Kubernetes addressing, and using them may cause conflicts in the global router network.

3. In the control panel, in the top menu, click Products and select Cloud Servers.

4. Go to the Network section → Private networks tab.

5. In the network menu, select Connect to global router.

6. Select a global router.

7. 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, which is assigned by default. Do not assign this address to your devices to avoid network disruption. The two last available subnet addresses will be reserved as service addresses.

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

   • the network will appear in the Servercore Global Router section on the page of the router to which you connected it. You can check it in the control panel: in the top menu, click Products → Global Router → router page;
   • the network will have the Global Router tag. You can check it in the control panel: in the top menu, click Products → Cloud Servers → cloud server page → Network section → network card.

4. Assign an IP address to the dedicated server

Configure a local port on the dedicated server that is connected to the global router network. Assign an IP address from the subnet that you connected to the global router in step 2 to the port.

Ubuntu

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

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

   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> – private network interface name;
   • <ip_address> – 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, saving the changes:

   :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 the KVM console.

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

   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> — private network interface name;
   • <ip_address> — private IP address of the server, for example, 192.168.0.2;
   • <mask> — subnet mask, for example, /24.

4. Press ESC.

5. Exit the vi text editor, saving the changes:

   :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 the KVM console.

2. Output information about the network interfaces:

   ip address

3. 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> — the private network interface name.

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

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

   Specify:

   • <eth_name> — private network interface name;
   • <ip_address> — 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, saving the changes:

   :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 the KVM console.

2. Open Network and Sharing Center.

3. Open the private network interface.

4. Click Properties.

5. Select IPv4 in the list.

6. Click Properties.

7. Specify the network interface parameters:

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

8. Click OK.

9. Optional: assign a private IP address to the server in the Control Panel.

5. Specify a route on the dedicated server

On the server, you need to configure a static route to the file storage subnet that you connected to the global router in step 3.

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> — subnet to which the route is needed, specifying the mask, for example 192.168.0.0/28;
   • <gateway> — gateway for the subnet of the current server 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> — subnet to which the route is needed, for example 192.168.0.0;
   • <mask> — mask of the subnet to which the route is needed, for example 255.255.255.0;
   • <gateway> — gateway for the subnet of the current server 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> — subnet to which the route is needed, specifying the mask, for example 192.168.1.0/28;
   • <gateway> — gateway for the subnet of the current server specified on the global router;
   • <eth_name> — 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 the KVM console.

2. Add the required routes one by one:

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

   Specify:

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

6. Specify a route in the file storage subnet

In the file storage subnet that you connected to the global router in step 3, you need to configure a static route to the dedicated server subnet that you connected to the global router in step 2.

Use the Configure static routes on subnet section of the Static routes instructions.

7. Create file storage

Control panel

1. In the Control panel, in the top menu, click Products and select File Storage.

2. Click Create storage.

3. Enter a storage name or leave the name that is automatically created.

4. Select the location where the storage will be created.

   If you need to increase the disk space of a cloud server or Managed Kubernetes cluster using file storage, select the location where the server or cluster is located. To increase the disk space of dedicated servers, file storage can be created in any location.

   If you plan to use storage for backups, we recommend choosing a location different from the main infrastructure location to improve fault tolerance.

5. Fill in the blocks:

   • Subnet
   • Settings
   • Access rules

6. Check the price of the file storage.

7. Click Create.

Subnet

1. Select the private subnet of the file storage that you connected to the global router in step 3. Once the storage is created, the subnet cannot be changed.

2. Enter a private IP address for the storage or leave the first available address from the subnet, which is assigned by default. You will not be able to change the IP address after the storage is created.

Settings

1. Select the file storage type:

   • HDD Basic,
   • SSD Universal,
   • SSD Fast.

   Once created, the storage type cannot be changed.

2. Specify the storage size: from 50 GB to 50 TB. After creation, you can increase the file storage, but cannot decrease it.

3. Select a protocol:

   • NFSv4 — for connecting storage to servers running Linux and other Unix systems;
   • CIFS SMBv3 — for connecting storage to Windows servers.

   Once created, the protocol cannot be changed.

Access rules

NFSv4

1. Configure access rules for the file storage:

   • accessible by everyone — the storage will be accessible from any IP address in the private subnet where it is created;
   • access restricted — the storage will be accessible only to specific IP addresses or private subnets. If you create file storage without rules, access will be restricted for all IP addresses.

2. If you selected the Restricted access option, click Add rule.

3. Enter the IP address or CIDR of the private subnet and select the access level.

   After creating the storage, you can configure new access rules.

CIFS SMBv3

1. Configure access rules for the file storage:

   • accessible by everyone — the storage will be accessible from any IP address in the private subnet where it is created;
   • access restricted — the storage will be accessible only to specific IP addresses or private subnets. If you create file storage without rules, access will be restricted for all IP addresses.

2. If you selected the Restricted access option, click Add rule.

3. Enter the IP address or CIDR of the private subnet.

   After creating the storage, you can configure new access rules.

OpenStack CLI

1. Open the OpenStack CLI.

2. Create a file storage network:

   openstack share network create \
     --name <share_network> \
     --neutron-net-id <net_uuid> \
     --neutron-subnet-id <subnet_uuid>

   Specify:

   • <share_network> — file storage network name;
   • <net_uuid> — ID of the private or public network to which the file storage will be connected. You can view the list of networks using the command openstack network list;
   • <subnet_uuid> — subnet ID. You can view the list of subnets using the command openstack subnet list.

3. Create the file storage:

   openstack share create <share_protocol> <share_size>\
     --name <share_name> \
     --share-network <share_network_id> \
     --share-type <share_type_name> 

   Specify:

   • <share_protocol> — file storage connection protocol NFSv4 or CIFS SMBv3;
   • <share_size> — file storage size in GB;
   • <share_name> — file storage name;
   • <share_network_id> — ID of the file storage network you created in step 2. You can view the list of file storage networks using the command openstack share network list;
   • <share_type_name> — file storage type. You can view the list of types using the command openstack share type list.

Terraform

Use the Create file storage instructions in the Terraform documentation.

8. Mount the file storage to the dedicated server

The mounting process depends on the operating system on the server and the file storage protocol: NFSv4 or CIFS SMBv3.

NFSv4

Linux

1. Connect to the dedicated server.

2. Open the CLI.

3. Install the package for working with the NFS protocol:

   sudo apt install nfs-common

4. Create a folder for mounting the storage:

   sudo mkdir -p /mnt/nfs

5. Mount the file storage:

   sudo mount -vt nfs "<filestorage_ip_address>:/shares/share-<mountpoint_uuid>" /mnt/nfs

   Specify:

   • <filestorage_ip_address> — IP address of the file storage. You can find it in the control panel: in the top menu, click Products → File Storage → storage page → Settings tab → IP field;
   • <mountpoint_uuid> — mount point ID. You can find it in the control panel: in the top menu, click Products → File Storage → storage page → Connection section → GNU/Linux tab.

Windows

To work with file storage from Windows, we recommend using file storage with the CIFS protocol. If you need to connect storage using the NFS protocol, install and use a client that supports the NFSv4 protocol.

File Storage only works with NFS client version NFSv4. By default, Windows OS supports NFS clients of versions NFSv2 and NFSv3. For more information about NFS versions, see the NFS overview article in Microsoft documentation.

CIFS SMBv3

Linux

1. Connect to the dedicated server.

2. Install the package for working with the CIFS protocol:

   sudo apt install cifs-utils

3. Create a folder for mounting the storage:

   sudo mkdir -p /mnt/cifs

4. Mount the file storage:

   sudo mount.cifs -o guest //<filestorage_ip_address>/share-<mountpoint_uuid> /mnt/cifs

   Specify:

   • <filestorage_ip_address> — IP address of the file storage. You can find it in the control panel: in the top menu, click Products → File Storage → storage page → Settings tab → IP field;
   • <mountpoint_uuid> — mount point ID. You can find it in the control panel: in the top menu, click Products → File Storage → storage page → Connection section → GNU/Linux tab.

Windows

1. Connect to the dedicated server.

2. Mount the file storage:

   net use X: \\\\<filestorage_ip_address>\share-<mountpoint_uuid>

   Specify:

   • <filestorage_ip_address> — IP address of the file storage. You can find it in the control panel: in the top menu, click Products → File Storage → storage page → Settings tab → IP field;
   • <mountpoint_uuid> — mount point ID. You can find it in the control panel: in the top menu, click Products → File Storage → storage page → Connection section → Windows tab.