Network
Public network
A network with internet access to which all servers are physically connected. On some TCP and UDP ports, network traffic between the private network and the internet is limited. Some BareMetal server configurations support reserving MC-LAG public network channels.
When working with a public network and internet access, make sure to comply with the terms of use.
Ephemeral public subnet
An ephemeral public subnet is a public subnet of the /31 size that is randomly assigned to a BareMetal server from the range of public IPv4 addresses reserved for Yandex BareMetal.
Ephemeral public subnets are assigned to servers with Public address set to From ephemeral subnet in their network parameters.
When leasing a BareMetal server, you can enable the DHCP server in an ephemeral public subnet. To do this, enable Assign via DHCP. Otherwise, the DHCP server in this subnet will be disabled. You will not be able to change the DHCP server settings in such subnet later.
The lifecycle of an ephemeral public subnet depends on the lifecycle of the server this subnet is assigned to. When a server lease is cancelled, the ephemeral public subnet assigned to it will be automatically deleted and the server’s public IPv4 address will be released back to the BareMetal address pool.
You can convert an ephemeral public subnet to a dedicated public subnet of size /31.
Dedicated public subnet
A dedicated public subnet is a public subnet made up of an IP address range that will be available to your servers in the selected pools. The IP address range is assigned to the dedicated public subnet automatically.
You can order a dedicated public subnet in the following sizes:
| Subnet size | Total number of IP addresses | Available IP addresses |
|---|---|---|
/311 |
2 | 1 |
/29 |
8 | 6 |
/28 |
16 | 14 |
/272 |
32 | 30 |
/262 |
64 | 62 |
/252 |
128 | 126 |
/242 |
256 | 254 |
1 You can order a public subnet of size /31 only by converting an ephemeral public subnet.
2 To order public subnets with sizes /27, /26, /25, and /24, contact support.
The dedicated public subnet does not have a DHCP server; therefore, on the network interface of the server connected to such subnet, you should manually configure a static IP address from the subnet’s range of available public IP addresses and specify the default gateway address.
The information about the range of IP addresses available in a public subnet and default gateway is provided in the Public network section on the server information page and on the public subnet information page.
When you cancel the lease of a server which has a dedicated public subnet assigned to it, its public IPv4 address is released back to the dedicated public subnet’s address pool so you can later use it for another server.
In Yandex BareMetal, dedicated public subnets are billable. The minimum lease period for a dedicated public subnet is one month, so you cannot delete such a subnet during the first month after the order date.
Private network
A local network to which all servers are connected. Logically joins servers into isolated user networks. Some BareMetal server configurations support reserving MC-LAG private network channels.
Private subnet
A network physically bounded by the network equipment of a single pool, isolated both from the internet and from other users' networks.
Within a single pool, L2 connectivity (VLAN) and L3 connectivity (VRF) are possible between leased servers. Between servers physically hosted in different pools, only L3 connectivity is available.
To configure networking between servers from different pools, select the same VRF for the appropriate subnets under Routing settings.
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.
Virtual network segment (VRF)
To provide L3 routing, private subnets with configured routing are aggregated into virtual network segments (VRFs).
Servers from the same or different pools connected to different private subnets aggregated into a VRF segment will be able to maintain L3 networking between them.
Private connection to cloud networks
To set up network connectivity between BareMetal servers, Yandex Virtual Private Cloud private subnets, and private subnets in the on-premise infrastructure, use Yandex Cloud Interconnect.
MAC addresses of network interfaces
You can look up the MAC addresses of the BareMetal server network interfaces on the server information page under Public network and Private network.
Yandex BareMetal network traffic billing when communicating with other Yandex Cloud services
Yandex Virtual Private Cloud
Traffic sent from Yandex Virtual Private Cloud to Yandex BareMetal public addresses is classified as outgoing traffic subject to the VPC pricing policy.
Note
To transfer large data volumes between Yandex Virtual Private Cloud and Yandex BareMetal, use Yandex Cloud Interconnect.
Traffic transmitted via Yandex Cloud Interconnect between private Yandex BareMetal and Yandex Virtual Private Cloud addresses in either direction is not billable.
Yandex Object Storage
Traffic between Yandex BareMetal and Yandex Object Storage is free of charge regardless of direction according to the Object Storage pricing policy.
Yandex Cloud Backup
Traffic transmitted between Yandex BareMetal and Yandex Cloud Backup is free of charge.