vania-janet/multiturn-rag-retrieval-data huggingface dataset:
ibmcloud is instance-reboot INSTANCE [--no-wait] [-f, --force] [--output JSON] [-q, --quiet]



 Command options 



* INSTANCE: ID or name of the instance.
* --no-wait: Execute the action immediately and drop all queued actions.
* --force, -f: Force the operation without confirmation.
* --output: Specify output format, only JSON is supported. One of: JSON.
* -q, --quiet: Suppress verbose output.



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







 ibmcloud is instance-start 

Start a virtual server instance.

ibmcloud is instance-start INSTANCE [--output JSON] [-q, --quiet]



 Command options 



* INSTANCE: ID or name of the instance.
* --output: Specify output format, only JSON is supported. One of: JSON.
* -q, --quiet: Suppress verbose output.



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







 ibmcloud is instance-stop 

Stop a virtual server instance.



* When you stop an instance and restart it, a new private IP address is assigned if the instance wasn't created with a static IP address or the primary_ipv4_address attribute wasn't set when the instance was created by using the CLI or API. For more information about setting a static IP address, see primary_network_interface in the [API reference](https://cloud.ibm.com/apidocs/vpccreate-an-instance). -



ibmcloud is instance-stop INSTANCE [--no-wait] [-f, --force] [--output JSON] [-q, --quiet]



 Command options 



* INSTANCE: ID or name of the instance.
* --no-wait: Execute the action immediately and drop all queued actions.
* --force, -f: Force the operation without confirmation.
* --output: Specify output format, only JSON is supported.
This is possible only when the volume pool of existing volume supports replication.





 How can I check whether volume is already replication enabled? 

You need to check the replicationEnabled attribute of the volume. A volume is replicationEnabled when it is true.





 How can I check whether volume is master or auxiliary volume? 

Volume is auxiliary when isAuxiliary field of volume is true. When replicationEnabled is true and isAuxiliary is false then volume is a master volume.





 How can I check the serial number of my virtual server instance? 

The serial number is available after you deploy your virtual server instance and you can choose to display the serial number system value.

You must pin the IBM i virtual server instances that use the IBM i licenses. If you do not pin the virtual server instances and request a migration to a different host, the serial numbers changes, and the IBM i license will not work.





 What should I do If I do not see the latest information in the UI? 

Consider the following if you do not see an update in the User Interface(UI):



1. Power System Virtual Server utilizes a new caching mechanism for some resources to ensure that UI refresh operations complete in a timely manner.
2. In some scenarios out-dated information may be shown while the cache is updated, for approximately four minutes.
3. You can refresh the page to trigger an update to the cached data, eventually leading to the updated information's display.
4. When the DC has a heavy amount of traffic, and the cache has not been refreshed within the last four minutes, Power System Virtual Server UI may display an error message. A subsequent page refresh will retrieve and display the updated information.







 Why I cannot see the storage pool and tier of my boot images? 

IBM improved the performance of copying a stock image into customers' accounts. As a result of this new feature, the newly copied stock image acts like an image reference, where volumes are not accessible to the user. The improved process now offers:



1. Faster copy of stock image to your private project.
2. The stock image cannot be exported. One can do VM capture and export on a deployed VM that uses the stock image.
3.
archive: H4sIADXNg2IAA+3W326CMBQGcK59it555XbanraMq70KlOLIJhjqzPb2q6g3S9xiIi7T75eQlj+hDYcP6vvVuo/hMZsQJc6YsU2+t2NfsmKyyhHLjKRUSmbCTDmpo/e4KQchsqHvNz9d99v5f8of6l/3/jUMi8Puw+fq7XJj7ApsmU/WX2m7r7/j9Abs6s/W2kzQ5aZw2p3XfxuG2PZdIeZ6Poth2LY+xGImRLdsu49dR4h2VS5DsT/yHF9KZWxRSU02NCGkxJJ0FQVSoSlrn8Jba5eyrEsOT55dlduq9sY55sbrhlJpda7HG6/7YRP3YyxETkVOhz6zLtI2++unc/tO5b+84AfgrPyn4JM0pDXyfw3I/32bMvdH5+SfOK0TpdZWIv/XgPzftynX/Udn/f/NmH+l8P+/CuQfAAAAAAAAAAAAAOD2fAEPQbuiACgAAA==
Show more







 Next steps 



* [Creating an instance by using the UI](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-virtual-servers)
* [Creating an instance by using the CLI](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-virtual-servers&interface=cli)
The servers are dedicated for your use, or your customer's, and not shared in any part, including server resources, with other IBM Cloud customers.

These servers are managed by the account holder, either you, your customer, or your services partner, depending on your business operations.

These servers are provisioned with your choice of operating system (OS) image that is directly installed to bare metal.

Because customization is controlled on bare metal servers, fast provisioning times of in the range 1 - 4 hours are obtainable with worldwide availability. For larger systems (greater 3 TB DRAM), there is a longer validation period for checking the hardware components (particularly RAM), but the machines are usually available within 24 hours.

For more information about Bare Metal servers on VPC Infrastructure, see [Deploy IBM Cloud Bare Metal Servers on VPC Infrastructure](https://www.ibm.com/cloud/bare-metal-servers/vpc) on ibm.com and [About Bare Metal Servers for VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-about-bare-metal-servers) on IBM Cloud Docs.





 IBM Power Virtual Server 

This is a complementary offering from IBM Power Systems, with low latency access to IBM Cloud services

IBM Power Virtual Servers are virtual machine servers with enterprise-grade performance and extensive customization capabilities. These IBM Power Virtual Servers are also known as an IBM Power Logical Partitions (LPARs).

The servers run on IBM PowerVM (Type 1 hypervisor) managed by IBM Power Systems and facilitated by IBM Cloud are a form of Infrastructure-as-a-Service (IaaS) provisioned with your choice of operating system (IBM AIX or Linux®) image that is installed and infrastructure customization (such as dedicated CPU performance or shared CPU for optimized costs). By using the IBM PowerVM underneath, the customization of the Virtual Servers is flexible, with fast self-service provisioning available in worldwide locations - all with pay-as-you-use billing that makes it easier for you to scale up and out.

IBM Power Virtual Servers are colocated in the same IBM Cloud data centers that are used by both IBM Cloud Classic Infrastructure and VPC Infrastructure, but are separated from the rest of the IBM Cloud servers with separate networks and storage.
Provisioning transient instances 

You can provision your transient virtual server instances through the IBM Cloud® console.

For the IBM Cloud console, you must have an upgraded account to order virtual servers. For more information about upgrading your account, see [Pay-As-You-Go account](https://cloud.ibm.com/docs/account?topic=account-accountspaygo).



 Before you begin 

Before you begin, review the following prerequisites.



1. Review the deployment options that are available to you. For more information, see [Transient virtual servers](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-about-vs-transient).
2. Review virtual server instance capacity considerations. For more information, see [Resource considerations for virtual server instances](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-capacity-considerationscapacity-considerations).
3. Open the [virtual server instance](https://cloud.ibm.com/gen1/infrastructure/provision/vs?guestType=transient&cm_sp=Cloud-Product-_-OnPageNav-IBMCloudPlatform_IBMVirtualMachines-_-VSI_Prod_Midpage) page from the IBM Cloud console.







 Provisioning a transient virtual server instance 

To provision a transient virtual server instance, you need to consider the following information.

You must be logged in to see all available options.



 Transient instance 



Table 1. Transient instance options

 Field Details 

 Billing Transient instances are only available as hourly instances. If you cancel your hourly instance after 10 days, you pay for only the hours for those 10 days. 
 Hostname Can contain labels that are made of alphanumeric characters and dashes, which are separated by periods. Labels cannot be numeric only, begin or end with a dash, nor have consecutive dashes or periods. 
 Domain Must have two or more labels that can be made of alphanumeric characters and dashes, which are separated by periods. Labels can't begin or end with a dash, or have consecutive dashes or periods.
2. Click Order devices
3. In the Compute category, click Bare Metal Servers.
4. In the Bare Metal Server section, click Monthly.
5. Select the servers. See VMware Support publications for minimum requirements:



* The following servers were selected for the example. Keep in mind that having dual unbonded public and private uplinks is a requirement for redundancy. Confirm that the data center where you created your VLANs contain unbonded uplinks.
* Capacity Cluster (Quantity 2)



* Server configuration - Select an Intel® Xeon v3 server from the 'Dual processor multi-core Servers' section
* Software is OS = VMware
* OS Storage is 2 x 1 TB SATA (configured as a RAID 1)
* Data Storage - Recommend ordering 2 TB SATA or 1.2 TB SSD or Endurance or Performance NFS SAN Storage



* If you are interested in other storage types, see [Storage to use with VMware Systems](https://cloud.ibm.com/docs/vmware?topic=vmware-vmware-storagevmware-storage)
* Uplink Port Speeds: 1 Gbps Dual Public and Private Networks (Unbonded)



* 10 Gbps Uplinks are recommended for VMware vSAN solutions









6. If you are creating a new deployment in a new IBM Cloud® data center, proceed to step 6. If this deployment is an expansion or a deployment into an existing Data Center, select the preferred back-end BCR VLAN + front-end FCR VLAN. For the example, the back-end BCR VLAN is 1101 and the front-end FCR VLAN is 2200. Note: If this deployment is new or a new deployment into a new DC the back-end BCR and front-end FCR VLANs are created when you order the server.
7. Enter a Hostname and Domain.
8. Review the order and click Finalize Your Order to start the provisioning process.







 Ordering vCenter Server 

vCenter is an add-on to a Windows Server. This configuration scales up to 20 vSphere hosts.
In the [IBM Cloud console ![External link icon](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/icons/launch-glyph.svg)](https://cloud.ibm.com/login), go to Menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/icons/icon_hamburger.svg) > VPC Infrastructure > Compute > Bare metal servers.
2. From the Bare metal servers for VPC page, click Create.
3. On the New bare metal server for VPC page, you can view and select profiles under Profile.







 Using the CLI to view profiles 

Use the following command to list all the bare metal server profiles that are available in a region:

ibmcloud is bare-metal-server-profiles [--output JSON] [-q, --quiet]





 Using the API to view profiles 

List all bare metal server profiles that are available in a region by running the following API request:

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





 Next Steps 

After you choose a profile, you can [create bare metal servers on VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-bare-metal-servers).
Ordering VMware as a Service instances 

You can order an IBM Cloud® for VMware as a Service instance from the VMware Solutions user interface after you review the minimum requirements.



 Minimum requirements for VMware as a Service instances 

Minimum 2 servers (6 servers for vSAN profiles)



* 2 hosts (2-socket 32 cores, 192 GB RAM)
* 24 TB of shared storage
* Minimum of 1 virtual data center (VDC) with a medium performance edge



You can start with just one virtual data center (VDC) and a performance network edge of medium size.





 Procedure to order VMware as a Service instances 



1. In the VMware Solutions console, click Create on the VMware as a Service card.
2. On the VMware as a Service page, click the VMwaaS single-tenant Cloud Director site card.
3. Specify the Cloud Director site name and select a resource group.

If No resource group available is displayed, you currently do not have the permission to add VDCs to any resource group in this account. Contact the account owner to be assigned the Editor or Administrator role on a resource group in the account. For more information, see [IAM roles](https://cloud.ibm.com/docs/account?topic=account-userroles).
4. Select the Cloud Director geography and location.
5. Specify the provider virtual data center (PVDC) name and select PVDC location.
6. Specify the settings for the cluster.



1. Specify the cluster name.
2. Select the profile storage type.
3. Select the host profile.
4. Select the host quantity.



* For NFS only storage, select a minimum of 2.
* For vSAN™ storage, select a minimum of 6.



5. For vSAN, optionally select the Enable vSAN de-duplication & compression checkbox to save storage space.
6. Select the sizings for one or more IOPS/GB performance tiers for attached NFS storage.



7.
Network interface configuration for bare metal server profiles. When you [retrieve a bare metal server profile](https://cloud.ibm.com/apidocs/vpc/latestget-bare-metal-server-profile) or [list all bare metal server profiles](https://cloud.ibm.com/apidocs/vpc/latestlist-bare-metal-server-profiles), the response now provides a network_interface_count property. When the type is range, the new property provides max and min sub-properties that denote the maximum and minimum number of network interfaces that are supported for a bare metal server with the specified profile. The values for max and min include both the primary network interface and secondary network interfaces. When the type is dependent, the network interface count depends on another value that is specified when the server is created. For more information about network interfaces, see [Overview of bare metal server network interfaces](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-nic-for-bare-metal-serversoverview-bare-metal-network-interfaces), and [Managing network interfaces for bare metal servers on VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-nic-for-bare-metal-servers&interface).







 28 March 2023 



 For all version dates 

VCPU manufacturer support for instances and dedicated hosts. When [provisioning](https://cloud.ibm.com/apidocs/vpc/latestcreate-instance) an instance or dedicated host, you can now use the new vcpu_manufacturer property in the [instance](https://cloud.ibm.com/apidocs/vpc/latestlist-instance-profiles) or [dedicated host](https://cloud.ibm.com/apidocs/vpc/latestlist-dedicated-host-profiles) profile to choose between profiles from different processor manufacturers. You can also view the virtual server instance VCPU configuration through the vcpu sub-property manufacturer.
Enabling Auto scale for better capacity and resiliency 

This tutorial shows you how to set up compute (virtual server instance) Auto scale for horizontal scaling. You create an Auto scale instance template that defines the details of the virtual server instances that are created. After you define the template, you define instance groups to set the scaling policies that determine when and how many virtual server instances are added or removed. The instance group setup includes enabling the backend orchestration to add the newly created virtual server instances to the backend server pool for the cloud load balancer.



 Objectives 



* Learn how to create an Auto scale template and group for the virtual server instance
* Learn how to enable the backend orchestration to add newly created virtual server instances to the backend server pool for the cloud load balancer







 Architecture 

Zoom

![Autoscale.](https://cloud.ibm.com/docs-content/v1/content/df269b100c3499f1efcbb7d030dce8dec25c539b/ha-infrastructure/images/ha-pools-origins-1zone-tut.svg)

Figure 1. Deploying server pools and origins in single MZR





 Before you begin 

This tutorial builds on the [Deploying server pools and origins in a single MZR](https://cloud.ibm.com/docs/ha-infrastructure?topic=ha-infrastructure-ha-pools-origins) solution tutorial. If you don’t have an environment or need to rebuild your environment, use that tutorial to set it up.

You must remove any virtual server instances from the back-end server pool before you start this task. Auto scale requires an empty back-end server pool; an empty back-end pool has no servers that are attached to it.





 Step 1: Create Instance templates for virtual server instances 

To create an Auto scale instance template for the virtual server instance, complete the following steps:



1. From the VPC overview page, scroll down to Auto scale and click Instance templates.
2. Click Create +.
3. In the New instance template:

a.
* ibmcloud is bare-metal-server-update 7d317c32-71f8-4060-9bdc-6c971b0317d4 --name my-server --enable-secure-boot true --tpm-mode tpm_2
* ibmcloud is bare-metal-server-update 7d317c32-71f8-4060-9bdc-6c971b0317d4 --name my-server --output JSON
* ibmcloud is bare-metal-server-update my-baremetal-1 --name my-bm-server --output JSON







 Command options 



* SERVER: ID or name of the server.
* --name: New name of the bare metal server.
* --enable-secure-boot: Indicates whether secure boot is enabled. If enabled, the image must support secure boot or the server fails to boot. The status of the bare metal server must be stopped before you change this configuration. One of: false, true.
* --tpm-mode: The mode for the trusted platform module (TPM). One of: tpm_2, disabled.
* --output: Specify output format, only JSON is supported. One of: JSON.
* -q, --quiet: Suppress verbose output.



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







 ibmcloud is bare-metal-servers 

List all bare metal servers.

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.
Location Locations are composed of regions (specific geographic areas) and zones (fault tolerant data centers within a region). Select the location where you want your bare metal server. 
 Name A name is required for your bare metal server. 
 Resource group Select a resource group for the server. 
 Tags You can assign labels to your server so that you can easily filter resources in your resource list. 
 Access management tags Access management tags help you apply flexible access policies on specific resources. 
 Operating system Select the operating system and version from an image.<br><br><br><br> * For x86 architecture, ibm-esxi-7-amd64-1 installs a licensed ESXi 7.x hypervisor.<br> * For s390x architecture, sles-15-sp3-metal-s390x installs a licensed SUSE Linux Enterprise Server 15 SP3 (s390x). red-8-metal-s390x installs Red Hat Enterprise Linux 8.x - Minimal Install (s390x) for your bare metal server.<br><br><br> 
 Profile Select from popular profiles or from all available vCPU and RAM combinations. The profile families are Balanced, Compute, and Memory. For more information, see [Bare metal servers profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-bare-metal-servers-profile) or [s390x bare metal server profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-s390x-bare-metal-servers-profile). 
 SSH key Select an existing public SSH key or click Create an SSH key to create a new one. For more information about creating an SSH key, see [Creating your SSH key by using the UI](https://cloud.ibm.com/docs/vpc?topic=vpc-ssh-keys&interface=uigenerate-ssh-keys-ui).
No hpcc-symp731-scale5151-rhel86-v1-4 
 login_node_instance_type Specifies the virtual server instance profile type to be used to create the login node for the IBM Spectrum Symphony cluster. For choices on profile types, see [Instance profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-profiles). No bx2-2x8 
 management_node_count Number of management nodes. This is the total number of primary, secondary, and management nodes. There is one primary, one secondary, and the rest of the nodes are management nodes. Enter a value in the range 1 - 10. No 3 
 management_node_instance_type Specify the virtual server instance profile type to be used to create the management nodes for the IBM Spectrum Symphony cluster. For choices on profile types, see [Instance profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-profiles). No bx2-4x16 
 remote_allowed_ips Comma-separated list of IP addresses that can access the Spectrum Symphony instance through an SSH or RDP interface. For security purposes, provide the public IP addresses assigned to the devices that are authorized to establish an SSH or RDP connection (for example, ["169.45.117.34"]). To fetch the IP address of the device, use [https://ipv4.icanhazip.com/](https://ipv4.icanhazip.com/). Yes None 
 resource_group Resource group name from your IBM Cloud account where the VPC resources should be deployed. Note: Do not modify the "Default" value if you would like to use the auto-scaling capability. For additional information on resource groups, see [Managing resource groups](https://cloud.ibm.com/docs/account?topic=account-rgs). No Default 
 scale_compute_cluster_filesystem_mountpoint Compute cluster (accessingCluster) file system mount point.
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](https://my.vmware.com). Do not place this VM on the vCenter Server instance that is being upgraded.



Complete the following steps to download 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.1-17327517.iso.
* For ESXi 7, VMware-ESXi-7.0U1c-17325551-depot.zip.