Establishing network connectivity in a Yandex BareMetal private subnet

In the management console, select the folder where you are deploying your infrastructure.

In the list of services, select BareMetal and click Lease server.

Under Configuration, click the Pool filter and select the ru-central1-m3 server pool.

Under Configuration, select the appropriate server configuration.

(Optional) Under Disk, configure disk partitioning:

1. Click Configure disk layout.

2. Specify the partitioning parameters. To create a new partition, click Add partition.

   To build RAID arrays and configure disk partitions yourself, click Remove RAID.

3. Click Save.

Under Image, select the Ubuntu 24.04 image.

In the Lease duration field, select a lease period: 1 day, 1 month, 3 months, 6 months, or 1 year.

When this period expires, server lease will automatically be renewed for the same period. You cannot terminate the lease during the specified lease period, but you can refuse to extend the server lease further.

Under Private network, in the Private subnet field, select the subnet-m3 subnet you created earlier.

Under Public network, select No address in the Public address field.

Under Access:

1. In the Password field, select one of the following options to create a root password:

   • To generate a new root password, select New password and click Generate.

     Warning

     This option requires you to maintain password security. Save the password you generated in a secure location. Yandex Cloud does not store it, and you will not be able to retrieve it once the server is deployed.

   • To use the root password saved in a Yandex Lockbox secret, select Lockbox secret.

     In the Name, Version, and Key fields, select the secret containing your password, its version, and its key, respectively.

     If you do not have a Yandex Lockbox secret, click Create to create it.

     Choose the Custom secret type to specify a custom password or Generated to generate password automatically.

2. In the Public SSH key field, select the SSH key saved in your organization user profile.

   If your profile has no SSH keys or you need to add a new one:

   • Click Add key.
   • Specify the SSH key name.
   • Upload your public key file or paste its contents in the field below. You will need to create your own SSH key pair to establish a secure server connection.
   • Click Add.

   The SSH key will be added to your organization user profile.

   If adding SSH keys by users to their profiles is disabled in the organization, the public SSH key you add will be saved only to the OS user profile of the new BareMetal server.

Under Server information, in the Name field, enter the server name: server-m3-1.

Click Lease server.

Similarly, lease one more server named server-m3-2 in the ru-central1-m3 server pool.

In the management console, select the folder where you are deploying your infrastructure.

In the list of services, select BareMetal.

Next to server-m3-1, click and select KVM console.

The KVM console terminal window will open, showing a login prompt:

server-m3-1 login:

If you do not see this prompt, try restarting the server.

Perform all further actions described in this step in the KVM console terminal:

1. Specify root for the username and press ENTER.

2. Paste the password received when leasing the server in the password input line and press ENTER. Note that when typing or pasting a password in Linux, the characters you enter will not appear on the screen.

   Tip

   To paste clipboard text to the KVM console, use the Paste text here field in the upper right corner.

   Result:

   Welcome to Ubuntu 24.04.2 LTS (GNU/Linux 6.8.0-53-generic x86_64)
   ...
   root@server-m3-1:~# _
   

   If you did not save the server administrator password, you can create a new password following this guide or reinstall the server OS.

3. View a list of the server’s network interfaces and find the interface connected to the private subnet:

   ip a
   

   Result:

   ...
   5: etx2: <BROADCAST, MULTICAST,UP,LOWER_UP> mtu 1500 qdisc ma state UP group default qlen 1000
       link/ether 00:02:09:35:fd:31 brd ff:ff:ff:ff:ff:ff
       altname enp6s0d1
       inet6 fe80::202:c9ff:fe35:fd31/64 scope link
           valid_lft forever preferred_lft forever
   ...
   

   Since the server has no public IP address, its only active network interface (with the state UP status) is the one connected to the private subnet. In the example above, this interface has the etx2 ID. In the next step, you will assign a static IP address to this interface.

   Tip

   To make sure the correct network interface is selected, use its MAC address. You can view the MAC address of your BareMetal server’s network interface on the server information page under Private network.

4. Open the server network interface configuration file:

   nano /etc/netplan/50-cloud-init.yaml
   

5. In the file, edit the network interface settings:

   network:
     version: 2
     ethernets:
       ... # This example shows only the configuration of the interface you need to set up.
       etx2:
         match:
           macaddress: "00:02:09:35:fd:31"
         dhcp4: false # Here, opt out of using DHCP.
         addresses: # Set the interface static IP address in this section.
           - 192.168.1.101/24
         set-name: "etx2"
   

   For the etx2 interface, configure the following settings:

   • Change the dhcp4 value to false to opt out of using DHCP and set the interface IP address statically.

   • Add the addresses section with the internal static IP address assigned to the server. Each server's address must be unique within the subnet.

     Note

     For subnet addressing purposes, you can use any CIDR in the ranges reserved for private networks: 10.0.0.0/8, 172.16.0.0/12, or 192.168.0.0/16. The subnet must include at least 8 host addresses, requiring a CIDR prefix length is /29.

   To save the changes and exit the text editor, press Ctrl + X and confirm saving changes to the 50-cloud-init.yaml file.

6. Apply your changes:

   netplan apply
   

7. Make sure the network interface was assigned an IP address. To do this, run the following command and filter the output by the interface ID:

   ip a | grep etx2
   

   Result:

   5: etx2: <BROADCAST,MULTICAST, UP,LOWER_UP> mtu 1500 qdisc ma state UP group default qlen 1000
       inet 192.168.1.101/24 brd 192.168.1.255 scope global etx2
   

   The network interface is configured to use the 192.168.1.101 static IP address in subnet-m3.

Similarly, configure the server-m3-2 network interface by assigning it the 192.168.1.102/24 static IP address in the netplan settings.

In the management console, select the folder where you are deploying your infrastructure.

In the list of services, select BareMetal.

Next to server-m3-1, click and select KVM console.

Authenticate as the root user in the KVM console terminal with the password you saved when leasing the server.

In the KVM console terminal, run the ping command to make sure you can access server-m3-2 by its IP address, 192.168.1.102:

ping 192.168.1.102 -c 5

Result:

PING 192.168.1.102 (192.168.1.102) 56(84) bytes of data.
64 bytes from 192.168.1.102: icmp_seq=1 ttl=64 time=3.90 ms
64 bytes from 192.168.1.102: icmp_seq=2 ttl=64 time=0.235 ms
64 bytes from 192.168.1.102: icmp_seq=3 ttl=64 time=0.222 ms
64 bytes from 192.168.1.102: icmp_seq=4 ttl=64 time=0.231 ms
64 bytes from 192.168.1.102: icmp_seq=5 ttl=64 time=0.235 ms

--- 192.168.1.102 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4086ms
rtt min/avg/max/mdev = 0.222/0.964/3.899/1.467 ms

Network connectivity between the servers has been established with zero packet loss.

In the management console, select the folder where you are deploying your infrastructure.

In the list of services, select BareMetal.

In the left-hand panel, select Private subnets.

Next to subnet-m3, click and select Edit. In the window that opens:

1. Enable IP addressing and routing.
2. In the Virtual network segment (VRF) field, select the previously created segment, my-vrf.
3. In the CIDR field, specify 192.168.1.0/24.
4. In the Default gateway field, keep the default value, 192.168.1.1.
5. Enable the Assigning IP addresses via DHCP option and in the IP address range field that appears, leave the default values, 192.168.1.1 — 192.168.1.254.

Click Save changes.

In the management console, select the folder where you are deploying your infrastructure.

In the list of services, select BareMetal.

Next to server-m3-1, click and select KVM console.

Authenticate as the root user in the KVM console terminal with the password you saved when leasing the server. Perform all further actions described in this step in the KVM console terminal:

1. Open the server network interface configuration file:

   nano /etc/netplan/50-cloud-init.yaml
   

2. In the file, edit the settings of the network interface connected to the private subnet:

   network:
     version: 2
     ethernets:
       ... # This example shows only the configuration of the interface connected to the private subnet.
       etx2:
         match:
           macaddress: "00:02:09:35:fd:31"
         dhcp4: true # Here, enable DHCP.
         # Comment out or delete the addresses section.
         # addresses:
         #   - 192.168.1.101/24
         set-name: "etx2"
   

   Configure the following settings for the interface:

   • Change the dhcp4 value to true to enable DHCP for automatic IP address assignment on this interface.
   • Comment out or delete the addresses section with the internal static IP address assigned to the server.

   To save the changes and exit the text editor, press Ctrl + X and confirm saving changes to the 50-cloud-init.yaml file.

3. Apply your changes:

   netplan apply
   

4. Make sure the network interface was assigned an IP address. To do this, run the following command and filter the output by the interface ID:

   ip a | grep etx2
   

   Result:

   5: etx2: <BROADCAST,MULTICAST, UP,LOWER_UP> mtu 1500 qdisc ma state UP group default qlen 1000
       inet 192.168.1.2/24 metric 100 brd 192.168.1.255 scope global dynamic etx2
   

   The server-m3-1 network interface is assigned the 192.168.1.2 IP address in the private subnet named subnet-m3.

Similarly, configure the server-m3-2 network interface and save the IP address assigned to it in the private subnet. In our example, this is 192.168.1.3.

In the management console, select the folder where you are deploying your infrastructure.

In the list of services, select BareMetal.

Next to server-m3-1, click and select KVM console.

Authenticate as the root user in the KVM console terminal with the password you saved when leasing the server.

In the KVM console terminal, run the ping command to make sure you can access server-m3-2 by the IP address you saved in the previous step (192.168.1.3 in our example):

ping 192.168.1.3 -c 5

Result:

PING 192.168.1.3 (192.168.1.3) 56(84) bytes of data.
64 bytes from 192.168.1.3: icmp_seq=1 ttl=64 time=0.271 ms
64 bytes from 192.168.1.3: icmp_seq=2 ttl=64 time=0.215 ms
64 bytes from 192.168.1.3: icmp_seq=3 ttl=64 time=0.262 ms
64 bytes from 192.168.1.3: icmp_seq=4 ttl=64 time=0.223 ms
64 bytes from 192.168.1.3: icmp_seq=5 ttl=64 time=0.208 ms

--- 192.168.1.3 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4106ms
rtt min/avg/max/mdev = 0.208/0.235/0.271/0.025 ms

Network connectivity between the servers has been established with zero packet loss.