| copyright | lastupdated | subcollection | ||
|---|---|---|---|---|
|
2025-01-03 |
vpc |
{{site.data.keyword.attribute-definition-list}}
{: #bare-metal-server-faq}
You might encounter the following frequently asked questions when you use a Bare Metal Server for VPC.
What's the difference between Bare Metal Servers (Classic infrastructure) and Bare Metal Servers for VPC?
{: #faq-bare-metal-0} {: faq}
Compared to the classic bare metal infrastructure, Bare Metal Servers for VPC provides the following advantages:
- Security and performance of the private cloud with the flexibility and scalability that you expect of the public cloud.
- Integrates with other VPC services such as virtual server, security groups, networking, and more.
- Faster provisioning and deployment and simple hourly billing.
Keep in mind that Bare Metal Servers for VPC is less customizable than classic bare metal servers.
For more information about the differences between the Classic infrastructure and VPC, see Comparing IBM Cloud Classic and VPC infrastructure environments.
{: #faq-bare-metal-1} {: faq}
Currently, VMware ESXi, Windows, RHEL, RHELfor SAP, Debian GNU, SUSE Linux Enterprise, Ubuntu Linux, and custom images are supported.
{: #faq-bare-metal-2} {: faq}
One storage option is available that includes secondary local NVMe drives. All profiles include a pair of RAID1 boot drives.
- Profiles that are denoted with a
dlikebx2d-metal-96x384, provide mirrored 960 GB SATA M.2 drives as boot storage and 8 3.2 TB U.2 NVMe SSDs as secondary local storage to support vSAN, or user-managed RAID. Oppositely, a profile without theddenotation such asbx2-metal-96x384only provide mirrored 960 GB SATA M.2 drives for boot.
- {{site.data.keyword.block_storage_is_short}} is not supported.
- {{site.data.keyword.filestorage_vpc_short}} is supported.
- Encryption in transit is not supported between {{site.data.keyword.filestorage_vpc_short}} and {{site.data.keyword.bm_is_short}}.
For more information about file storage, see About {{site.data.keyword.filestorage_vpc_short}}.
{: #faq-bare-metal-3} {: faq}
When you are planning to create the bare metal servers, you can go through the configuration checklist on Planning for bare metal servers.
{: #faq-bare-metal-4} {: faq}
Bare metal servers are available in us-south, us-east, ca-tor, eu-de, eu-gb, eu-es, and jp-tok regions. See x86-64 bare metal server profiles.
Do I need to configure multiple network interfaces on a bare metal server to support the full 100 Gbps bandwidth?
{: #faq-bare-metal-5} {: faq}
No. You can add as many or as few vNICs as you need. Every interface can take advantage of the 100 Gbps bandwidth, but the total aggregate is 100 Gbps for each server. Meaning that the bandwidth is shared by all the vNICs. For more information about networking on bare metal, see Networking overview for bare metal servers.
{: #faq-bare-metal-6} {: faq}
Eight 3.2 TB NVMe drives are supported on specific profiles. These NVMe drives are in addition to the 960 Gb boot drive, see x86-64 bare metal server profiles.
No other drive configurations are supported and drive size, type, and quantity can't be changed. {: note}
For more information about profiles, see Profiles for Bare Metal Servers for VPC.
{: #faq-bare-metal-7} {: faq}
The boot disk supports RAID 1 by using a hardware RAID controller. If you use a profile with NVMe drives, use a software RAID option that is configured through your choice of Operating System.
Secondary drives use a JBOD configuration and aren't supported by a hardware RAID controller.
{: #faq-bare-metal-8} {: faq}
No. The uplinks (PCI network interfaces) are redundant by design. The VLAN network that you create are on that default, redundant uplink. You don’t need to manage uplink redundancy because redundancy is automatic.
For more information, see Networking overview for Bare Metal Servers on VPC.
{: #faq-bare-metal-9} {: faq}
Replication isn't supported.
{: #faq-bare-metal-10} {: faq}
The boot disk is 960 GB. You can configure each image differently for its partition sizes.
Bare Metal Servers for VPC supports only UEFI images. {: important}
{: #faq-bare-metal-11} {: faq}
You are billed for Bare Metal Servers for VPC based on the server profile that you selected. Billing stops only when you delete the bare metal server. Powering off the server doesn't change billing. For more information about billing and pricing, contact your IBM Sales representative.
You are also billed for other VPC services and resources that are attached to any bare metal servers. For the most up-to-date pricing information, you can create a cost estimate by clicking Add to estimate from the Create Bare metal server for VPC page in the {{site.data.keyword.cloud}} console.
{: #faq-bare-metal-12} {: faq}
The main difference between virtual server instances and the bare metal servers is that powering off a bare metal server has no effect on the billing cycle. Meaning that hourly billed servers still accrue at the normal rate whether the server is powered off or on. The billing stops only when the bare metal server is deleted.
{: #faq-bare-metal-13} {: faq}
To view your account invoices, follow these steps.
- Go to the {{site.data.keyword.cloud_notm}} console{: external},
- Then, click Manage > Billing and Usage.
Each account receives a single bill. If you need separate billing for different sets of resources, then you need to create multiple accounts.
For more information about invoices, see Viewing your invoices.