Manually assigning a public IP address to a BareMetal server

1. In the management console, select the folder where you are going to create your infrastructure.
2. Navigate to BareMetal.
3. In the left-hand panel, select  Public addresses and subnets.
4. At the top right, click Order a public subnet.
5. In the Availability zone field, select the availability zone where the subnet will be available.
6. In the Pool field, select the ru-central1-m3 server pool.
7. In the subnet size field, select /29.
8. In the Name field, enter the subnet name: my-public-subnet.
9. Click Order.

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

2. Navigate to BareMetal.

3. Click Lease server and, in the window that opens, select Stock configurations and a suitable BareMetal server configuration in the ru-central1-m3 server pool.

   Do it by selecting the ru-central1-m3 server pool in the filter on the right side of the window, under Pool.

   To select the suitable server configuration, click the section with its name in the central part of the screen.

   Tip

   You can reduce the cost of renting a server in some configurations by ordering server assembly.

   To use the discount, hover over Cheaper with assembly under the configuration at hand and click Go to assembly in the pop-up window.

   When ordering a server with assembly, follow the steps below to configure the server properties. In this case, the server will not be available immediately, but only after the assembly is completed (within four calendar days), and at a lower price.

4. In the server configuration window that opens:

   1. In the Lease duration field, select the 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.

   2. Under Image, select the image of the operating system you will be configuring the network interface in (Ubuntu 24.04, AlmaLinux 9, or Windows Server 2022).

   3. Optionally, under Disk, configure disk partitioning:

      1. Click Configure disk layout.

      2. Specify partition settings. To create a new partition, click Add partition.

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

      3. Click Save.

   4. Under Network interfaces:

      1. In the Public address field, select From a dedicated subnet.
      2. In the public subnet selection field that appears, specify the previously created my-public-subnet.

   5. 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 there are no SSH keys in your profile or you want to add a new key:

         1. Click Add key.

         2. Enter a name for the SSH key.

         3. Select one of the following:

            • Enter manually: Paste the contents of the public SSH key. You need to create an SSH key pair on your own.

            • Load from file: Upload the public part of the SSH key. You need to create an SSH key pair on your own.

            • Generate key: Automatically create an SSH key pair.

              When adding a new SSH key, an archive containing the key pair will be created and downloaded. In Linux or macOS-based operating systems, unpack the archive to the /home/<user_name>/.ssh directory. In Windows, unpack the archive to the C:\Users\<user_name>/.ssh directory. You do not need additionally enter the public key in the management console.

         4. Click Add.

         The system will add the SSH key to your organization user profile. If the organization has disabled the ability for users to add SSH keys to their profiles, the added public SSH key will only be saved in the user profile inside the newly created resource.

   6. Under Server information, in the Name field, enter the server name: my-server.

   7. Click Lease server.

In the KVM console terminal, run this command:

ip a

Result:

...
2: etx1: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 00:25:90:c8:03:f8 brd ff:ff:ff:ff:ff:ff
    altname enp2s0f0
    inet6 fe80::225:90ff:fec8:3f8/64 scope link
        valid_lft forever preferred_lft forever
3: etx2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 00:25:90:c8:03:f9 brd ff:ff:ff:ff:ff:ff
    altname enp2s0f1
    inet6 fe80::225:90ff:fec8:3f9/64 scope link
        valid_lft forever preferred_lft forever
...

In this example, the public MAC address from the management console is 00:25:90:c8:03:f9, so the server's public network interface is eth2.

1. In the KVM console terminal, learn the name of the Netplan configuration file:

   ls /etc/netplan/
   

   Result:

   50-cloud-init.yaml
   

2. Open the configuration file:

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

3. Update the public network interface settings:

   network:
     version: 2
     ethernets:
       ... # This example shows only the public interface configuration.
       etx2:
         match:
           macaddress: "00:25:90:c8:03:f9"
         dhcp4: false # Disable DHCP on the interface
         set-name: "etx2"
         addresses: # Set a static public IP address and subnet mask
           - 198.51.100.106/29
         routes: # Set the default route through the public subnet gateway
           - to: default
             via: 198.51.100.105
         nameservers: # Set DNS servers
           addresses: [77.88.8.8, 77.88.8.1]
   

   Where:

   • match.macaddress: MAC address of the public network interface.
   • dhcp4: false disables DHCP on the interface.
   • addresses: Public IP address from the range of available subnet addresses, with the subnet mask in CIDR format.
   • routes.to: default and via: Default route through the public subnet gateway address.
   • nameservers.addresses: DNS server addresses.

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

4. Make sure the configuration is correct:

   netplan try
   

   If the configuration is free of errors, the utility will temporarily apply it and prompt you to confirm the changes. Confirm the changes by pressing ENTER.

5. Apply the new configuration:

   netplan apply
   

1. Check that the specified IP address has been assigned to the network interface:

   ip a | grep etx2
   

   Result:

   3: etx2: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
       inet 198.51.100.106/29 brd 198.51.100.111 scope global etx2
   

2. Check the route table:

   ip r
   

   Result:

   default via 198.51.100.105 dev etx2 proto static
   198.51.100.104/29 dev etx2 proto kernel scope link src 198.51.100.106
   

3. Check the DNS settings:

   resolvectl status
   

4. Check internet connectivity:

   ping ya.ru -c 5
   

   Result:

   PING ya.ru (77.88.55.88) 56(84) bytes of data.
   64 bytes from ya.ru (77.88.55.88): icmp_seq=1 ttl=55 time=3.45 ms
   64 bytes from ya.ru (77.88.55.88): icmp_seq=2 ttl=55 time=3.22 ms
   ...
   
   --- ya.ru ping statistics ---
   5 packets transmitted, 5 received, 0% packet loss, time 4006ms
   rtt min/avg/max/mdev = 3.215/3.337/3.452/0.085 ms