Connect file storage to a dedicated server

Connect file storage to a dedicated server

The file storage and the dedicated server are always in different pools, so to connect the file storage to the dedicated server you need to configure private network connectivity at L3 level via global router.

For your information

Some dedicated server configurations Chipcore Line cannot be added to the global router network because they do not have a port to connect to the private network. The availability of the private network port can be checked in Control Panel under Servers and Hardware → Servers → Server page → Ports tab.

1. Create global router.
2. Connect the network and subnet to the global router to the dedicated server VLAN.
3. Connect the network and subnet to the global router for file storage.
4. Assign IP address to dedicated server.
5. #write-routes-on-dedicated-server.
6. Create file storage.
7. Mount file storage to a dedicated server.

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

1. Create a global router.
2. Connect two private subnets to the global router — 192.168.0.0.0/29 with a gateway of 192.168.0.1 for the SPB-1 pool and 172.16.0.0.0/29 with a gateway of 172.16.0.1 for the 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 a route on the dedicated server in the SPB-1 pool — to the 172.16.0.0.0/29 subnet via the 192.168.0.1 gateway.
5. Create a file store on the 172.16.0.0.0/29 subnet.
6. Mount the file storage to a dedicated server.

Create a global router⁠

1. In Control Panel, go to Network Services → Servercore Global Router.
2. Click Create Router. Each account has a limit of five global routers.
3. Enter the name of the router.
4. Press Create.
5. If the router was created with status ERROR or hung in one of the statuses, create a ticket.

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 Control Panel, go to Network Services → Servercore 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 the Dedicated Servers service.

6. Select pool.

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

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 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, or 192.168.0.0.0/16;
   • have a size of at least /29, as three addresses will be occupied by Servercore 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, and 10.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.

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

13. Click Create Network.

14. Optional: check the network topology on the global router. In Control Panel, go to Network Services → Servercore Global Router. Open the page of the desired router and click Network Map.

Connect a network and subnet to the router for file storage⁠

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 need to connect the network and subnet to the global router up to the project and cloud platform 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.

Подключить новую сеть

1. In Control Panel, go to Network Services → Servercore 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 the Cloud Platform service.

6. Select pool where the file storage will be created.

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

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

9. 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, or 192.168.0.0.0/16;
   • have a size of at least /29, as three addresses will be occupied by Servercore 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, and 10.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.

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

12. Click Create Network.

13. Optional: check the network topology on the global router. In Control Panel, go to Network Services → Servercore Global Router. Open the page of the desired router and click Network Map.

Подключить существующую сеть

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

2. 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, or 192.168.0.0.0/16;
   • is at least /29, as three addresses will be occupied by Servercore 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, and 10.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.

3. In Control Panel, go to Cloud Platform → Network.

4. Open the Private Networks tab.

5. From the menu ( ) of the network, select Connect to Global Router.

6. Select the global router.

7. For each of the network subnets, enter the IP address to 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.

8. Press Connect. Do not close the window until you see the message that the network is connected. After that, in the control panel:

   • The network will appear in section Network Services → Servercore Global Router on the page of the router you connected it to;
   • in section Cloud Platform → Network → on the Private Networks tab, the network will have the Global Router tag.

Assign an IP address to a dedicated server⁠

Configure a local port on a 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

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

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.

Debian

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

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

   vi /etc/network/interfaces

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

4. Press the ESC key.

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

   :wq

6. Restart the network:

   service networking restart

7. Optional: reboot the server.

CentOS

1. Connect to the server via SSH or via 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> as the name of the network interface of the private network.

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

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

   Specify:

   • <eth_name> is the name of the network interface of the private network;
   • <ip_address> is the private IP address of the server, for example, 192.168.0.2/29;

5. Press the ESC key.

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

   :wq

7. Restart the network:

   systemctl restart network

8. Optional: reboot the server.

Windows

1. Connect to the server via RDP or via KVM-console.

2. Open the Network and Sharing Center.

3. Open the network interface of the private network.

4. Press Properties.

5. From the list, select IPv4.

6. Press Properties.

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

8. Press OK.

Write routes on a dedicated server⁠

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 a global router network, it must have static routes to all subnets with which you want connectivity.

Ubuntu

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

2. Open the network configuration file:

   vi /etc/netplan/01-netcfg.yaml

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

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

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

6. Save the file.

7. Check the settings:

   sudo netplan try

8. Apply the changes:

   netplan apply

Debian

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

2. Open the network configuration file:

   vi /etc/network/interfaces

3. Locate the data block of the corresponding network interface.

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

5. If you need to write multiple routes, add them sequentially in the same block.

6. Save the file.

7. Restart the network:

   sudo /etc/init.d/networking restart

CentOS

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

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

3. Restart the network:

   systemctl restart network

Windows

1. Connect to the server via RDP or via KVM-console.

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

Create file storage⁠

1. In Control Panel, go to Cloud Platform → File Storage.

2. Click Create Storage.

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

4. Select the pool where the storage will be located.

   If you plan to use storage to store backups, we recommend pooling storage and a dedicated server from different availability zones or regions to improve fault tolerance.

5. Select the subnet of the Servercore Global Router private network that you connected to the router for file storage.

6. Select file storage type. Storages differ in read/write speeds and bandwidth values:

   • HDD Basic;

   • SSD Universal;

   • SSD Fast.

     Once created, the storage type cannot be changed.

7. Specify the storage size: from 50 GB to 50 TB. Once created, you can increase file-storage, but you can't decrease it.

8. Select a protocol:

   • NFSv4 — for connecting storage to servers running Linux and other Unix systems;

   • CIFS SMBv3 — for connecting the storage to Windows servers.

     Once created, the protocol cannot be changed.

9. Check out the cost of file storage.

10. Press Create.

Mount the file storage to a dedicated server⁠

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

Mount storage using NFSv4 protocol⁠

Linux

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

2. Install the NFS protocol package:

   sudo apt install nfs-common

3. Create a folder to mount the repository:

   sudo mkdir -p /mnt/nfs

4. 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 look in control panel under Cloud Platform → File Storage → Storage page → Settings tab → IP field;
   • <mountpoint_uuid> — mount point ID. You can look in Control Panel under Cloud Platform → File Storage → Storage page → Connectivity block → GNU/Linux tab.

Windows

File storage works only with NFS client version NFSv4. By default, Windows supports NFS clients of versions below: NFSv2 and NFSv3. Learn more about NFS versions in the NFS Overview article of Microsoft's documentation.

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

Mount storage using CIFS SMBv3 protocol⁠

Linux

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

2. Install the CIFS protocol package:

   sudo apt install cifs-utils

3. Create a folder to mount the repository:

   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 look in control panel under Cloud Platform → File Storage → Storage page → Settings tab → IP field;
   • <mountpoint_uuid> — mount point ID. You can look in Control Panel under Cloud Platform → File Storage → Storage page → Connectivity block → GNU/Linux tab.

Windows

1. Connect to the server via RDP or via KVM-console.

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 look in control panel under Cloud Platform → File Storage → Storage page → Settings tab → IP field;
   • <mountpoint_uuid> — mount point ID. You can look in Control Panel under Cloud Platform → File Storage → File Storage → Storage page → Connect block → Windows tab.