vania-janet/multiturn-rag-retrieval-data huggingface dataset:
You can [Provision an Intel® Optane-compatible bare metal server](https://cloud.ibm.com/docs/bare-metal?topic=bare-metal-bm-provision-optane-server) or one with an [Intel® SGX architecture](https://cloud.ibm.com/docs/bare-metal?topic=bare-metal-bm-server-provision-sgx). SAP-certified servers are certified to support SAP HANA and SAP NetWeaver landscapes.<br><br>Use the following links for provisioning information for that type of server. With SAP-certified servers, you need to select which type of landscape, SAP HANA, or SAP NetWeaver, you are provisioning.<br><br><br><br> * [Fast-provisioned bare metal servers](https://cloud.ibm.com/docs/bare-metal?topic=bare-metal-bm-select-popular-servers)<br> * [Custom bare metal servers](https://cloud.ibm.com/docs/bare-metal?topic=bare-metal-ordering-baremetal-server)<br> * [IBM Cloud SAP-Certified Infrastructure](https://cloud.ibm.com/docs/bare-metal?topic=bare-metal-sap-cert-infrastructure)<br><br><br> 
 7. Configure your bare metal server Your server is now ready to be configured. See the topics under Configuring.
Bulk provisioning instances with instance groups 

You can provision a large number of virtual server instances at the same time by using the IBM Cloud command-line interface to create an instance group.



 Before you begin 



1. Make sure that you completed set up for your [IBM Cloud® CLI environment](https://cloud.ibm.com/docs/vpc?topic=vpc-set-up-environmentcli-prerequisites-setup) and your [IBM Cloud VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-a-vpc-using-cli).
2. Make sure that you have the required IBM Cloud Identity and Access Management (IAM) permissions to create instance group resources. For more information, see [Required permissions for VPC resources](https://cloud.ibm.com/docs/vpc?topic=vpc-resource-authorizations-required-for-api-and-cli-calls).
3. Make sure that you have created an [instance template](https://cloud.ibm.com/docs/vpc?topic=vpc-create-instance-template) with the instance details that are used to provision like instances in your group.







 Creating an instance group 

When you have an instance template created, you can proceed with creating an instance group. When you create the instance group, you can specify 0-1000 for the membership count. The membership count determines how many instances are provisioned in the instance group.

If you want to include a load balancer for your instance group to balance incoming requests across instances, you must create the load balancer before you create the instance group. For more information, see [About application load balancers](https://cloud.ibm.com/docs/vpc?topic=vpc-load-balancers). If you attach a load balancer to your instance group, you are limited to a membership count of 50.

Gather the following information before running the ibmcloud is instance-group-create command.



Table 2. Required instance group details

 Instance group details Description 

 Instance template ID of the instance template that you want to use.
ibmcloud is bare-metal-servers [--resource-group-id RESOURCE_GROUP_ID | --resource-group-name RESOURCE_GROUP_NAME | --all-resource-groups] [--output JSON] [-q, --quiet]



 Command options 



* --resource-group-id: ID of the resource group. This ID is mutually exclusive with --resource-group-name.
* --resource-group-name: Name of the resource group. This name is mutually exclusive with --resource-group-id.
* --all-resource-groups: Query all resource groups.
* --output: Specify output format, only JSON is supported. One of: JSON.
* -q, --quiet: Suppress verbose output.



--------------------







 ibmcloud is bare-metal-server-network-interface-reserved-ips 

Lists all reserved IPs bound to a network interface of a bare metal server.

ibmcloud is bare-metal-server-network-interface-reserved-ips SERVER NIC [--output JSON] [-q, --quiet]



 Command options 



* SERVER: ID or name of the server.
* NIC: ID or name of the network interface.
* --output: Specify output format, only JSON is supported. One of: JSON.
* -q, --quiet: Suppress verbose output.



--------------------







 ibmcloud is bare-metal-server-network-interface-reserved-ip 

Retrieves the specified reserved IP address if it is bound to the network interface of a bare metal server.

ibmcloud is bare-metal-server-network-interface-reserved-ip SERVER NIC RESERVED_IP [--output JSON] [-q, --quiet]



 Command options 



* SERVER: ID or name of the server.
* NIC: ID or name of the network interface.
* RESERVED_IP: The ID or name of the reserved IP.
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](https://cloud.ibm.com/docs/vpc?topic=vpc-bare-metal-servers-network).





 How many NVMe drives does a bare metal server support? 

The number NVMe drives that are supported depends on the profile that you select. The 4-socket profile with drives supports 16 3.2 TB NVMe drives and the planned 2-socket profile with drives supports eight 3.2 TB NVMe drives. These NVMe drives are in addition to the 960 Gb boot drive.

No other drive configurations are supported and drive size, type, and quantity can't be changed.

For more information about profiles, see [Profiles for Bare Metal Servers for VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-bare-metal-servers-profile).





 Does Bare Metal Servers for VPC support RAID? 

The boot disk supports RAID 1 by using a hardware RAID controller. If you use a profile with NVMe drives, it is recommended that you use a software RAID option.

Secondary drives use a JBOD configuration and aren't supported by a hardware RAID controller.





 Can I enable dual uplinks (uplink redundancy)? 

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](https://cloud.ibm.com/docs/vpc?topic=vpc-bare-metal-servers-network).





 What storage replication is supported for Bare Metal Servers for VPC? 

Replication isn't supported.





 What is the size of the boot drive for Bare Metal Servers for VPC? 

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.





 How does billing work?
ibmcloud pi instances 



 List all server instances 

ibmcloud pi instances [--long] [--json]

Options



* --json: Format output in JSON.
* --long: Retrieve all instance details.



--------------------







 ibmcloud pi instance-operation 



 Perform an operation on an IBMi server instance 

ibmcloud pi instance-operation INSTANCE_ID --operation-type TYPE [--boot-mode MODE] [] [--boot-operating-mode MODE] [--job-task TASK]



* INSTANCE_ID: The unique identifier or name of instance.



Examples

ibmcloud pi instance-operation IBMi-TEST_VM --operation-type job --job-task dston

or

ibmcloud pi instance-operation IBMi-TEST_VM --operation-type boot --boot-mode a --boot-operating-mode normal

Options



* --operation: Operating system image identifier or name.
* --boot-mode: Name of the server boot mode. Allowed values are a, b, c, and d.
* --boot-operating-mode: Name of the server operating mode. Allowed values are normal and manual.
* --job-task: Name of the job task to execute. Allowed values are dston, retrydump, consoleservic, iopreset, remotedstof, remotedston, iopdump, and dumprestart.



--------------------







 ibmcloud pi instance-list-console-languages 



 List the available console languages for an instance 

ibmcloud pi instance-list-console-languages INSTANCE_ID [--json]



* INSTANCE_ID: The unique identifier or name of the instance.



Options



* --json: Format output in JSON.



--------------------







 ibmcloud pi instance-update-console-language
For this Bare Metal Server, this information is found in the Network details section on the Overview page. Record the CIDR and gateway information for the public and private interfaces for your system.
* Create or identify an IBM Cloud Object Storage bucket to store your ignition file.
* Create or identify a cluster within the Satellite location that runs a supported operating system; for example, this tutorial uses a Red Hat OpenShift cluster that is running 4.11.



In addition, the Bare Metal Servers used in this example required the following prerequisites.



* If you plan to have multiple VLANs for your cluster, multiple subnets on the same VLAN, or are planning for a multizone classic cluster, [enable VRF in your account](https://cloud.ibm.com/docs/account?topic=account-vrf-service-endpoint).
* [Create two VLAN pairs](https://cloud.ibm.com/docs/cli?topic=cli-manage-classic-vlanssl_vlan_create) (public and private) in the same IBM Cloud data center pod for each zone for your bare metal host.
* Later in this tutorial, you deploy [OpenShift Data Foundation for local disks](https://cloud.ibm.com/docs/satellite?topic=satellite-storage-odf-local&interface=ui). This solution requires additional storage devices on the worker nodes.







 Bare Metal Server requirements 

To set up virtualization, your Bare Metal Server must meet the following requirements.



* Must support virtualization technology.



* For Intel CPUs, support for virtualization is referred to as Intel VT or VT-x.
* For AMD CPUs, support for virtualization is referred to as AMD Virtualization or AMD-V.



* Must have a minimum of minimum of 8 cores and 32 GB RAM, plus any additional cores that you need for your vCPU overhead. For more information, see [CPU overhead](https://docs.openshift.com/container-platform/4.11/virt/install/preparing-cluster-for-virt.htmlCPU-overhead_preparing-cluster-for-virt) in the Red Hat OpenShift docs.
* UI
* CLI
* API







 Managing Bare Metal Servers for VPC 

You can manage your IBM Cloud® Bare Metal Servers for VPC by performing tasks such as start, stop, restart, and delete bare metal server.

You can perform the following actions by using the UI, API, or CLI:



Table 1. Actions available for bare metal servers

 Action Description 

 Stop Stop the server. 
 Start Start a stopped server. This action is not available if the the status is Running. 
 Reboot Immediately powers off a running server and then powers it back on. 
 Delete To delete a server, the server must be powered off. If the server has a floating IP address, the floating IP address must be unassociated or released before the server is deleted. The delete action permanently removes a server and its connected vNIC, boot volume, and data from your account. 





 Managing bare metal servers by using the UI 

You can view and manage your bare metal server from the Bare metal servers page in the IBM Cloud dashboard.

To manage your servers, complete the following steps.



1. In [IBM Cloud dashboard](https://cloud.ibm.com), go to Menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/icons/icon_hamburger.svg) > VPC Infrastructure > Compute > Bare metal servers.
2. On the Bare metal servers page, click the Actions icon ![More Actions icon](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/icons/action-menu-icon.svg) for the server that you want to manage. You can perform the following actions:





 Viewing your bare metal servers 

You can view the summary of all bare metal server on the bare metal server page, or you can click an individual server name to view details and make changes.
* Basic availability groups - A limited version of availability groups and are supported only on SQL Server Standard edition. The single secondary replica cannot be readable or backed up and each basic availability group can support only two replicas, but multiple basic availability groups can be configured per server. Basic availability groups allow for many of the same features of availability groups including synchronous or asynchronous replication, manual or automatic failovers.
* Distributed availability groups - This allows an availability group to treat another availability group to act as a secondary replica. The read-only secondary replicas can be globally dispersed, offloading workloads to regional read-only secondary replicas. The two availability groups, each with their own listener, do not need to be in same network or WSFC. This allows for geographically remote HA and DR across multi-site deployments. With distributed availability groups, a WSFC does not need to span across regions. There is no automatic failover between the primary availability group and the secondary availability group. The availability group that is not primary can only serve read-only queries, but does have a primary replica itself. The primary replica in the secondary availability group is charged with replicating transactions to the other secondary replicas in the secondary availability group. This architecture is useful for OS and SQL Server version upgrades as you can have different versions of Windows Server in each availability group. Although each availability group in a distributed scenario has its own listener, the distributed availability group as a whole does not. Applications, perhaps with the aid of DNS aliases, will connect to each availability group directly after a failover to take advantage of readable secondary replicas.









 Distributed Network Names 

This deployment uses Distributed Network Names (DNN), which is a name resource in WSFC and Always On availability groups, used for name resolution of the cluster resources. It differs from a standard network name resource because it does not require a separate IP address from the IP addresses of the nodes and does not require the use of Gratuitous Address Resolution Protocol (GARP) on the network when a failover occurs. In Windows Server 2019, the name of the WSFC, which is also the Cluster Name Object (CNO) in Active Directory Domain Services and the database listener can both be created with DNNs.
The trained model is saved back to IBM Cloud Object Storage, so that the data does not take up storage space in your edge environment.





 Step 2: Deploy Satellite with a serverless component to your edge environment 

As the edge environment system administrator, you enable a serverless tool to simplify model inferencing at the edge.



1. [Create a Satellite location](https://cloud.ibm.com/docs/satellite?topic=satellite-locations) on your edge computing infrastructure.
2. [Create a managed Red Hat OpenShift cluster](https://cloud.ibm.com/docs/satellite?topic=openshift-satellite-clusters) in the Satellite location.
3. [Access the Red Hat OpenShift web console](https://cloud.ibm.com/docs/openshift?topic=openshift-access_clusteraccess_cluster_sat).
4. Using the OperatorHub, [install the Red Hat OpenShift Serverless operator](https://www.redhat.com/en/topics/microservices/why-choose-openshift-serverless).
5. [Install the Knative Serving Operator](https://www.redhat.com/en/topics/microservices/why-choose-openshift-serverless).



You deployed Satellite with a serverless component.





 Step 3: Run model inferencing at the edge 

As the AI developer, run model inferencing on your edge data by using the serverless processing that the edge administrator set up.



1. Download the trained model from IBM Cloud Object Storage to your local development environment.
2. Create a [Knative-compliant container image](https://knative.dev/docs/serving/samples/hello-world/helloworld-python/index.html).
3. [Deploy the image](https://developers.redhat.com/blog/2020/04/30/serverless-applications-made-faster-and-simpler-with-openshift-serverless-ga) to your Red Hat OpenShift Serverless processor that runs in your Satellite cluster.
* ibmcloud is bare-metal-server-create --name my-server-name --zone us-east-1 --profile bmx2d-24x384 --image cfdaf1a0-5350-4350-fcbc-97173b510844 --keys 7ab1ee27-564c-4730-a1ad-9b9466589250,9727e31a-74d4-45cd-8f39-1ef7484b5f3e --pnic-subnet bdea9c01-ada2-46ba-a314-4b3240477a5f --pnic-rip 2302-74dd56cc-71c4-4461-95f0-4e5e3b57727d --network-interfaces '[{"name": "cli-snic", "allow_ip_spoofing": true, "enable_infrastructure_nat": true, "interface_type": "pci", "allowed_vlans": 1, 2, 3, 4], "subnet": {"id":"2302-531ad9fc-c86a-4504-b5cf-a46981fddb5f"}, "primary_ip":{"id": "2302-2b09dd0a-9cfb-4639-a2ac-cc6c154ab461"}}] Create a bare metal server with secondary network interface with pre-created reserved IP ID. Configurations of the two secondary interfaces are specified in JSON format. See help text for '--network-interfaces' option.
"mode": ""
},
"vpc": {
"crn": "crn:[...]",
"href": "https://us-south.iaas.cloud.ibm.com/v1/vpcs/r134-96cb322a-6a59-4ac4-8783-1f059f87e4a9",
"id": "r134-96cb322a-6a59-4ac4-8783-1f059f87e4a9",
"name": "my-vpc"
},
"zone": {
"href": "https://us-south.iaas.cloud.ibm.com/v1/regions/us-south/zones/us-south-1",
"name": "us-south-1"
}
}



The status displays "Pending" until the server is created.

For more information about the API request, see [Create a bare metal server](https://cloud.ibm.com/apidocs/vpccreate-bare-metal-server).





 Viewing your server 

When the server status changes to "Running", use the following request to view it.

curl -X GET "$vpc_api_endpoint/v1/bare_metal_servers/$bare_metal_server_id?version=2021-03-09&generation=2" -H "Authorization: $iam_token"







 Creating a bare metal server by using the CLI 

You can use the CLI to create a bare metal server. Use the following steps to create a bare metal server by using the IBM Cloud® CLI.



 Before you begin 



1. Make sure that you set up your [CLI environment](https://cloud.ibm.com/docs/vpc?topic=vpc-set-up-environmentcli-prerequisites-setup).
2. Make sure that you create a VPC and a subnet before you create a bare metal server.
[Provision Bare Metal Servers for VPC network interfaces for NSX-T ](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-vpc-bm-vmware-nsx-t-vlannics)Provision Bare Metal Servers for VPC network interfaces for NSX-T

In this tutorial, Bare Metal Servers for VPC VLAN network interfaces are created for NSX-T management and edge components. This phase is optional, if you plan to use NSX-T for your Virtual Machine networking.

Virtual Private Cloud (VPC) VMware Solutions



* 1 hour
* 2023-05-05



[Provision a Public Gateway and Floating IPs for VMware Virtual Machines](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-vpc-bm-vmware-pgwip)Provision a Public Gateway and Floating IPs for VMware Virtual Machines

If your VMware Virtual Machines require public Internet Access, you need to use either Public Gateway (outbound) or Floating IP (inbound). This tutorial provides an example for these use cases for a VMware VM's VLAN NIC.

VMware Solutions Virtual Private Cloud (VPC)



* 1 hour
* 2023-05-05



[Provision vCenter Appliance](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-vpc-bm-vmware-vcenter)Provision vCenter Appliance

In this tutorial, you will deploy a vCenter for a VMware Deployment in IBM Cloud VPC and a floating VLAN interface for it.

VMware Solutions Virtual Private Cloud (VPC)



* 2 hours
* 2023-05-05



[Provision IBM Cloud VPC for a VMware Deployment](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-vpc-bm-vmware-vpc)Provision IBM Cloud VPC for a VMware Deployment
Roll-your-own (classic bare metals servers) Preferred path <br>Consider provision vSphere bare metal server and deploy a new bare metal server or a bare metal server within [VPC Architecture](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vpc-ryo-overview).<br><br><br><br> * Provision a new bare metal server with VMware ESXi V7.<br> * Swap out the ESXi V6 servers.<br> * Reload OS image with ESXi V7. <br> Alternative path <br> Consider provision a new bare metal server within [VPC Architecture](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vpc-ryo-overview).<br><br><br> <br><br> * In-place upgrade from V6 to V7 is not supported.<br><br><br> 





 Preparing your jump server 

Because the IBM Cloud client access VPN is limited to 512 Kbps, take one of the following actions.



* Provision an IBM Cloud Windows® 2012-2016 server Virtual Server Instance (VSI).
* Set up a similar Windows® VM on a separate vCenter Server environment within the same IBM Cloud data center. The Windows VM is used as a jump server into the vCenter Server instance for the upgrade that downloads the binary files from https://my.vmware.com. Do not place this VM on the vCenter Server instance that is being upgraded.



Complete the following steps to download the most recent files to your jump server:



1. From the VMware portal, download the following product files onto your jump server:



* For VMware vCenter Server Appliance, VMware-VCSA-all-7.0.x-xxxx.iso
* For ESXi 7, VMware-ESXi-7.0Ux-xxxx-depot.zip
* For Hypervisor, VMware-VMvisor-Installer-7.0Ux-xxxx.x86_64.iso



2.
For more information, see [Bare metal server profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-bare-metal-servers-profile).

The first letter of the profile name indicates the profile family:



Table 2. IBM Cloud Bare Metal Servers for VPC Profile Families

 First letter Characteristics of the related profile family 

 c Compute Optimized family, CPU to Memory ratio 1:2 
 b Balanced family, CPU to Memory ratio 1:4 
 m Memory Optimized family, higher CPU to Memory ratio 1:8 



The Bare Metal Server profile names are contextual and sequential. See the following example:



 Profile name Naming convention component What it means 

 mx2d-metal-96x768 m Memory Optimized family 
 x Intel x86_64 CPU Architecture 
 2 The generation for the underlying hardware 
 d the optional 'd' in the name indicates that the server is equipped with one or more SSD storage devices 
 — spacer 
 96 96 vCPU 
 x spacer 
 768 768 GiB RAM 
 '-metal-' in the name indicates that this is a Bare Metal Server. 







 Profiles available on Hourly Consumption Billing 

All IBM Cloud Bare Metal Servers for VPC are available with Hourly Consumption Billing, which includes Suspend Discounts and Sustained Usage Discounts. With Suspend Discounts, storage charges occur only if the server is in Shutdown state. With Sustained Usage Discount, the more a server is used, the less the cost per hour.





 Storage specifications 

When the bare metal server profiles for SAP NetWeaver are initially provisioned, the servers all have one pre-configured disk (sda) attached with the following basic layout:



Table 4. Storage configuration of the default bare metal server deployment (boot volume)

 File system Partition Storage type Size 

 sda1 Pre-configured BIOS volume 1 MB 
 /boot/efi sda2 Pre-configured boot volume 100 MB 
 / sda3 Pre-configured root volume 9.9 GB 





 Internal Storage 

Your bare metal server on VPC comes with a number of internal NVMEs, depending on its size.