Getting information about a server
-
In the management console, select the folder the server belongs to.
-
Go to BareMetal and, in the list of servers that opens, select the one you need.
The page offers the following information:
- Under Overview, general information about the server, including its name, ID, status, availability zone, and server pool.
- Under Resources, information about the server's hardware configuration.
- Under Marketplace application, information about the operating system installed on the server.
- Under Public network, information about the server's public network, including the ID, type, and CIDR of the public subnet, default gateway address, and MAC address of the network interface in the public network.
- Under Private network, information about the server's private network, including the private subnet, as well as the private IP and MAC address of the network interface in the private network.
- Under Lease conditions, information about the terms of server lease, including lease period/duration and auto-renewal.
- Under Backup and Accesses, information about the server's connection to Yandex Cloud Backup and public SSH key of the root user, respectively.
If you do not have the Yandex Cloud CLI installed yet, install and initialize it.
By default, the CLI uses the folder specified when creating the profile. To change the default folder, use the yc config set folder-id <folder_ID> command. You can also set a different folder for any specific command using the --folder-name or --folder-id options.
-
View the description of the command for getting information about a server:
yc baremetal server get --help -
Get information about the server:
yc baremetal server get <server_name_or_ID>
To get information about a server, use the get REST API method for the Server resource or the ServerService/Get gRPC API call.
Example
Get information about the server:
yc baremetal server get demo-baremetal-server
Result:
done (22m45s)
id: ly52dtzdi55r********
cloud_id: b1gia87mbaom********
folder_id: b1g0ijbfaqsn********
name: demo-baremetal-server
description: My first BareMetal server
zone_id: ru-central1-m
hardware_pool_id: ru-central1-m4
status: PROVISIONING
os_settings:
image_id: ly5vhn4lapev********
ssh_public_key: ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIGcM4tRfRHJGrlLMT+YJFr+aOdSQYnYYjAoj********
storages:
- partitions:
- type: EXT3
size_gib: "999"
mount_point: /
- type: EXT4
size_gib: "499"
mount_point: /root
raid:
type: RAID0
disks:
- id: ly5ual3jbnhr********
type: HDD
size_gib: "1862"
- id: ly54qfjw55d4********
type: HDD
size_gib: "1862"
- partitions:
- type: EXT3
size_gib: "999"
mount_point: /boot
- type: SWAP
size_gib: "9"
disk:
id: ly5ojffpngul********
type: HDD
size_gib: "1862"
network_interfaces:
- id: ly5wbsiklrtd********
mac_address: 00:25:90:92:fa:48
private_subnet:
private_subnet_id: ly5ztavbezrf********
- id: ly5ygl4loyy6********
mac_address: 00:25:90:92:fa:49
public_subnet:
public_subnet_id: ly5o6l7pxmk2********
configuration_id: ly5lymxdltk3xitpkrmi
created_at: "2025-07-06T21:53:46.186130Z"
labels:
env: test
curl -X GET \
-H "Content-Type: application/json" \
-H "Authorization: Bearer <IAM_token>" \
-d '{}' \
"https://baremetal.api.cloud.yandex.net/baremetal/v1alpha/servers/<server_ID>"
Where:
<IAM_token>: IAM token used for authentication.<server_ID>: Server ID.
Result:
{
"osSettings": {
"storages": [
{
"partitions": [
{
"type": "EXT3",
"sizeGib": "9",
"mountPoint": "/boot"
},
{
"type": "SWAP",
"sizeGib": "4"
},
{
"type": "EXT4",
"mountPoint": "/"
}
],
"raid": {
"disks": [
{
"id": "ly536lgz5cdo********",
"type": "HDD",
"sizeGib": "1862"
},
{
"id": "ly55nr77qcgq********",
"type": "HDD",
"sizeGib": "1862"
},
{
"id": "ly57e5ouat4r********",
"type": "HDD",
"sizeGib": "1862"
},
{
"id": "ly5g77vbnavh********",
"type": "HDD",
"sizeGib": "1862"
}
],
"type": "RAID10"
}
}
],
"imageId": "ly5vyzcggvci********",
"sshPublicKey": "ssh-ed25519 AAAAC3NzaC1lZDI1NTE5AAAAIMYMj0PbB7ObhwL0z3y+vN0BfNKwLm0u7DWw4D********"
},
"networkInterfaces": [
{
"privateSubnet": {
"privateSubnetId": "ly55shvlzvy4********"
},
"id": "ly5j33j44gtc********",
"macAddress": "00:25:90:e9:49:98"
},
{
"publicSubnet": {
"publicSubnetId": "ly5bss2zvuae********"
},
"id": "ly5rmqqchyep********",
"macAddress": "00:25:90:e9:49:99"
}
],
"id": "ly56xpblirh4********",
"cloudId": "b1gia87mbaom********",
"folderId": "b1g07hj5r6i4********",
"name": "bm-server-test",
"zoneId": "ru-central1-m",
"hardwarePoolId": "ru-central1-m4",
"status": "PROVISIONING",
"configurationId": "ly5fcdnlzp7j********",
"createdAt": "2025-12-07T19:09:42.520760Z"
}
Where:
-
id: Server ID. -
cloudId: Cloud ID. -
folderId: Folder ID. -
name: Server name.- Length: between 3 and 63 characters.
- It can only contain lowercase Latin letters, numbers, and hyphens.
- It must start with a letter and cannot end with a hyphen.
-
zoneId: Availability zone ID. -
hardwarePoolId: Server pool ID. -
status: Server status. The possible values are:PROVISIONING: Server is waiting to be allocated from the hardware pool.RUNNING: Server is running normally.STOPPED: Server is stopped.ERROR: Server encountered an issue and is unavailable.DELETING: Server deletion is in progress.REINSTALLING: Reinstalling server OS.
-
configurationId: Server configuration ID. -
osSettings: Server OS settings. This is an optional field. It will be empty if the server is created without an OS. -
networkInterfaces: Network interfaces connected to the server. -
disks: Disks connected to the server. -
createdAt: Creation time in RFC3339 format.