vania-janet/multiturn-rag-retrieval-data huggingface dataset:
In some older IPMI consoles this option is not available so you can skip this step.
4. To return to the system information page, go to System > System information and click the console window icon. Accept all security warnings.
5. When the console connects, you see login prompt.
6. Click Virtual Media > Virtual Storage.
7. Go to the CDROM&ISO tab and select the ISO File under Logical Drive Type
8. Click Open image and select the ISO on your local computer.
9. Click Plug-in to insert the ISO into the virtual CD-ROM drive and click OK.
10. Restart the server and use the boot from the virtual CD-ROM drive option. You might need to use the virtual keyboard in the iKVM viewer to select a boot device.







 Troubleshooting 



* Not all users have default access to mount Virtual Media. If a permission error occurs, contact [Support](https://cloud.ibm.com/docs/bare-metal?topic=bare-metal-gettinghelp) for an update to the Root IPMI User permissions.
* If an ISO is already mounted, an error message appears with the text A disk is mounted. You must unmount the existing disk and replace it with the new ISO. Two ISOs cannot be mounted at the same time.
* You might need to contact support to change the boot order in the BIOS.
For more information about resource requirements and capacity checking for some services, see [Resource requirements for services](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_addingservicesvc_addingservices-resource-requirements).

The following components are ordered and included in the Caveonix RiskForesight service.



 vCenter Server resources 



* CPU - 8 CPUs
* RAM - 32 GB
* Disk - 100 GB







 Network 

A dedicated private subnet with 32 IP addresses is ordered.





 Licenses and fees 

A Caveonix RiskForesight license key is ordered for each instance of the service.

If you order Caveonix RiskForesight for a VMware Regulated Workloads or Security and Compliance Readiness Bundle instance, you are charged for a per-host license for every host on the instance. This way of charging for Caveonix RiskForesight is new in Version 4.1. However, you are not charged for per-VM licenses.

If you order Caveonix RiskForesight for a VMware vCenter Server® instance, you are charged for the number of per-VM licenses that you choose at installation. This method of charging for Caveonix RiskForesight is the same as in previous releases. You can select 10 - 25,000 VMs to license.

If you order Caveonix RiskForesight for a VMware Regulated Workloads or VMware Security and Compliance Readiness Bundle instance, the host-based licenses are hidden. Caveonix RiskForesight is deployed with a 25,000 VM key. You do not need to upgrade.

Caveonix RiskForesight licenses that are ordered separately from the Resources page are not per-host. Therefore, it is recommended that you do not order new Caveonix RiskForesight licenses and apply the key to your Caveonix RiskForesight service on Regulated Workloads or Security and Compliance Readiness Bundle instances. Ordering in this way will:



* Provide less coverage than when the license was initially deployed
* Result in you being charged twice for Caveonix RiskForesight licenses because your initial license cannot be canceled.
* Go to the Windows Installer, for example, managementagent64, and double-click to open the Citrix XenServer Windows Management Agent Setup wizard. Complete the installation wizard to install XenServer Tools.



Guest additions are important for reporting performance and health of virtual server instances. Without performance and health information, virtual server instances might be marked for offline migrations when a critical maintenance is needed.

Don't disable or remove the default guest additions that are installed on IBM Cloud supplied images.

If you want to make sure that the guest additions are working from the hypervisor point of view, you can [create a case](https://cloud.ibm.com/docs/get-support?topic=get-support-open-case) and ask for XenTools virtual server validation.
3. Make sure that your image is cloud-init enabled.



* For more information, see [cloudbase-init’s documentation](https://cloudbase-init.readthedocs.io/en/latest/index.html).
* For more information about data sources, see [Data sources](http://cloudinit.readthedocs.io/en/latest/topics/datasources.html). IBM Cloud cloud-init images are created for the environment by using the [Config Drive](http://cloudinit.readthedocs.io/en/latest/topics/datasources/configdrive.html) Version 2 data source to supply the metadata.



4. Windows images require the Cloudbase-init Metadata Service for public and private network support in IBM Cloud infrastructure. You can access the service [here](https://github.com/softlayer/bluemix-cloudbase-init).









 Preparing to import an encrypted image
The ISOs for the initial installation and the OS that you are currently running are featured here.

If you made more than one upgrade, those display here as well.

Next, change directories using the previously loaded OS as the next directory, and go to the VRA home directory:

vyatta@acs-jmat-vyatta01:cd 5.2R5S3.06301309/persistence/rw/home/vyatta/
vyatta@acs-jmat-vyatta01:/lib/live/mount/persistence/sda2/boot/5.2R5S3.06301309/persistence/rw/home/vyatta$ ls -la
total 343084
drwxr-x--- 3 vyatta users 4096 Jan 29 16:29 .
drwxr-xr-x 3 root root 4096 Nov 20 05:05 ..
-rw------- 1 vyatta users 10537 Feb 2 11:55 .bash_history
-rw-r--r-- 1 vyatta users 220 Nov 5 2016 .bash_logout
-rw-r--r-- 1 vyatta users 3515 Nov 5 2016 .bashrc
-rw------- 1 vyatta users 53 Dec 25 10:45 .lesshst
-rw-r--r-- 1 vyatta users 675 Nov 5 2016 .profile
drwxr-x--- 3 vyatta users 4096 Jan 9 10:34 .ssh
-rw-r----- 1 vyatta users 351272960 Jan 26 14:23 vyatta-vrouter-5.2_20180126T1706-amd64.iso

From this directory, you can see the dotfiles and copy them over:
Return to [Getting Started - Adding a Client](https://cloud.ibm.com/docs/services/SecureGateway?topic=SecureGateway-add-client).







 Mac OS X 



 Requirements for running on Mac OS X 

The following pre-requisites are required prior to running the client on Mac OS X.



1. Install Xcode development tools, it is required by some of the node modules on this platform.







 Mac OS X Installation Procedure 

You may require administrative privileges to perform this installation, depending on your system's security setup.



1. Mount the DMG image that was downloaded from the Secure Gateway UI, normally by 'double-clicking' it.
2. A new 'finder' window should appear. If not, 'double-click' the mounted volume. This window should contain an "ibm" folder icon and an Applications "shortcut" icon, drag and drop the "ibm" folder onto the shortcut.







 Starting an interactive client session 

To start the client, run the secgw.command file located in the default installation location: /Applications/ibm/.

Return to [Getting Started - Adding a Client](https://cloud.ibm.com/docs/services/SecureGateway?topic=SecureGateway-add-client).







 Linux 

The installation includes the IBM® Secure Gateway for IBM Cloud® client as well as a secure version of IBM's nodejs package. Both are installed under the /opt/ibm directory on the system. The installer will create or update the following:



 Directory Filename Description 

 /etc/ibm sgenvironment.conf configuration file for upstart 
 /etc/ibm passwd creates user: secgwadmin:x:501:501::/home/secgwadmin:/bin/bash 
 /etc/ibm group creates group: secgwadmin:x:501: 
 /etc/init securegateway_client.conf upstart file 
 /opt/ibm node-v -linux-x64 IBM's Node JS installation 
 /opt/ibm securegateway Secure Gateway client installation
Specify one mount configuration per --mount-secret option; for example, --mount-secret /etc/secret-a=secret--a --mount-secret /etc/secret-b=secret-b. This value is optional.

-n, --name
: The name of this job run. If you do not specify the --job value, then the --name and the --image values are required. Use a name that is unique within the project.



* The name must begin and end with a lowercase alphanumeric character.
* The name must be 53 characters or fewer and can contain lowercase letters, numbers, and hyphens (-).



This value is optional.

--no-wait, --nw
: Submit the job run and do not wait for the instances of this job run to complete. If you specify the --no-wait option, the job run submit begins and does not wait. Use the jobrun get command to check the job run status. This value is optional. The default value is true.

--output, -o
: Specifies the format of the command output. Valid values are json, yaml, jsonpath=JSONPATH_EXPRESSION, and jsonpath-as-json=JSONPATH_EXPRESSION. Use jsonpath to specify the path to an element of the JSON output. This value is optional.

--quiet, -q
: Specify this option to reduce the output of the command. This value is optional. The default value is false.

--registry-secret, --rs
: The name of the registry secret. The registry secret is used to authenticate with a private registry when you download the container image. This value is optional.

--retrylimit, -r
: The number of times to rerun an instance of this job run before the job run is marked as failed. An array index of a job run is rerun when it gives an exit code other than zero. This option can only be specified if mode is task. This value is optional. The default value is 3.
For more information about updating your registry to point to IBM Cloud WSUS servers, see [Updating instance to use local WSUS server](https://cloud.ibm.com/docs/bare-metal?topic=bare-metal-updating-an-instance-to-use-a-local-wsus-server).

For Microsoft Windows operating systems, servers are configured by default to download and install updates as soon as they become available. The server restarts automatically if a restart is required. Updates are completed to protect servers from crucial vulnerabilities. If you prefer to schedule your updates differently, you can change the update schedule through the Windows Updates feature in the control panel.
: Add the contents of a configmap to the file system of your application container by providing a mount directory and the name of a configmap, with the format MOUNT_DIRECTORY=CONFIGMAP_NAME. Each mounted configmap must use a unique mount directory. For each key-value pair in the configmap, a file is added to the specified mount directory where the filename is the key and the contents of the file is the value of the key-value pair. Specify one mount configuration per --mount-configmap option; for example, --mount-configmap /etc/config-a=config-a --mount-configmap /etc/config-b=config-b. This value is optional.

--mount-secret, --mount-sec
: Add the contents of a secret to the file system of your application container by providing a mount directory and the name of a secret, with the format MOUNT_DIRECTORY=SECRET_NAME. Each mounted secret must use a unique mount directory. For each key-value pair in the secret, a file is added to the specified mount directory where the filename is the key and the contents of the file is the value of the key-value pair. Specify one mount configuration per --mount-secret option; for example, --mount-secret /etc/secret-a=secret--a --mount-secret /etc/secret-b=secret-b. This value is optional.

--no-cluster-local, --ncl
: Deploy the application with a public endpoint. The application deploys such that it can receive requests from the public internet or from components within the Code Engine project. This value is optional. The default value is true.

--no-wait, --nw
: Create the application and do not wait for the application to be ready. If you specify the --no-wait option, the application create begins and does not wait. Use the app get command to check the application status. This value is optional. The default value is false.

--output, -o
: Specifies the format of the command output.
See [SAP Note 2414097)](https://launchpad.support.sap.com//notes/2414097) for version details.

Refer to [Installing VMware vSphere ESXi by using Remote Console and Virtual Media](https://cloud.ibm.com/docs/vmware?topic=vmware-installing-vsphere-esxiinstalling-vsphere-esxi) and other VMware.com documentation to install a Guest OS.







 Bring-your-own-OS (custom OS image and BYOL License) 

When you have your own operating system image and license, it can be used with IBM Cloud and the OS install based on the vendor's instructions.



 Infrastructure BYOS SAP workloads support 

 Intel Bare Metal Servers on Classic Infrastructure OS BYOL and custom image (BYOS) by using the ["no OS" option during provisioning](https://cloud.ibm.com/docs/bare-metal?topic=bare-metal-bm-no-osbm-no-os) SAP HANA by using TDI deployment <br>SAP NetWeaver AS 
 Intel Virtual Servers (Gen2) on VPC Infrastructure OS BYOL and Custom image (BYOS) by using [Importing and managing custom images](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-images) SAP HANA by using TDI deployment <br>SAP NetWeaver AS 
 IBM Power Systems Virtual Server in the IBM Power Infrastructure environment Linux OS BYOL and Custom Image (BYOS) by using [Linux within the Power Virtual Server - Capturing and importing a SLES image](https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-using-linuxpreparing-linux-image) Not supported for SAP HANA or SAP NetWeaver workloads, available for non-SAP workloads
Make sure the information on the form is accurate in order to prevent the possibility of re-work by IBM SRE after customer environments are provisioned. This can cause unnecessary project delays. Provisioning information to review:

Contacts

These are the contacts that will receive the Welcome Kit when the environments are first provisioned. Be sure all proper contacts have been identified, including any key members from the implementation team (IBM Expert Services, GBS or 3rd party)

Preferred Data Center Location

This is the IBM Cloud or AWS data center location where the environments will be provisioned and will serve as the primary data center. See the Architecture section for a list of currently supported locations. Be sure this location is correct and in line with the customer's expectations an nearest to the majority of their end users.

Environment URL names

These are the URL names that will be setup for each provisioned environment (PROD, DEV, TEST, etc). Customers can define a specific sub-domian level name for each environment URL. Be sure these are correct and in line with customer expectations and overall project plan.

IBM MAS example domain names for a company called ACME might be:

Production URL example : https://main.home.ACME.suite.maximo.com

Non-Production URL example: https://main.home.ACME-DEV.suite.maximo.com

Note: environment names, once specified, cannot be altered without re-provisioning. This will incurr additional costs. In addtion, no provisioning can take place until URLs have been specificed.

Languages

Be sure any languages that need to be installed in the environments (other than English) are identified.

Contact your IBM salesperson or the IBM CDS Project Office: SaaSIOTPPO/Dallas/IBM to obtain a current copy of the provisioning form for your customer.





 1.2.2 Component Verification 

It is important to check with your IBM salesperson to insure all necessary products and components have been included in the customer MAS order. This will help eliminate the need for re-work by the IBM SRE team after the initial environments have been provisioned and avoid unnecesssary delays.
However, you can also separately install the global directories on any host of your SAP system landscape.  You can also use the SAP transport host or the host with the global file system (SAP global host) as your primary application server instance host.  Optionally, you can install one or more additional application server instances.
* Database instance (DB) - To assist your project's planning phase, more design considerations are provided at SAP AnyDB – SAP HANA database with IBM Cloud for SAP. For more information, see [AnyDB - SAP HANA](https://cloud.ibm.com/docs/sap?topic=sap-anydb-hana-db) and [Infrastructure certified for SAP](https://cloud.ibm.com/docs/sap?topic=sap-iaas-offerings).
* Additional Application Server (AAS) - You can install one or more additional application server instances for an existing SAP system. Additional application server instances are optional and can be installed on separate hosts.
* SAP Dialog Instance (DI) / Additional Application Instance (AAS) - Dialog Instance (DI) is an additional application instance on top of the Central Instance (CI). Normally the DI is set up on a different host.

Dialog instance consists of Gateway (GW), Internet Communication Manager (ICM), and Dispatcher Process (Disp) only. The DI has no Message Server and Enqueue Work Process.

DI always starts after the CI starts because the DI depends on CI as the main instance where message server and enqueue server exist. DI is used to balance the load and handle more workload rather than use only the Central Instance. The new name for DI is Additional Application Server (AAS).

Structure:

DI/AAS = GW + ICM + Disp

For more information about configuring and adding a AAS instance in heterogeneous SAP environment, see [SAP Note - 680617 INST: Appl. Server in Heterogeneous SAP System Environment](https://launchpad.support.sap.com//notes/680617).
Installing a guest OS on a VM For more information about the process of installing a guest OS on to a VM, see [Installing a guest operating system](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.vm_admin.doc/GUID-4AB8C63C-61EA-4202-8158-D9903E04A0ED.html). 
 Creating a snapshot Snapshots capture the entire state of the VM at the time that you take the snapshot. You can take a snapshot when a VM is powered on, powered off, or suspended. For more information, see [Take a snapshot in the VMware host client](https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.html.hostclient.doc/GUID-A0D8E8E7-629B-466D-A50C-38705ACA7613.html). 
 Reverting a snapshot For more information about restoring the VM state to its previous state at the start of the snapshot, see [Restoring snapshots](https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.vm_admin.doc/GUID-E0080795-C2F0-4F05-907C-2F976433AC0D.html).
[Transient virtual server](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-about-vs-transient) IBM-managed, multi-tenancy virtual server deployments offered at a reduced cost and best suited for flexible workloads 
 [Reserved virtual server](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-about-reserved-virtual-servers) IBM-managed, multi-tenancy virtual server deployments with guaranteed capacity for a contract term 
 [Dedicated virtual server](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-dedicated-virtual-servers) IBM-managed, single-tenancy virtual server deployments 



IBM Cloud® Virtual Servers are powered by Citrix Hypervisor. As with most hypervisors, guest additions help maintain a properly working computing environment. IBM Cloud® uses the information from guest additions to make informed decisions about routine server maintenance. Without the required guest additions, your virtual servers might miss critical maintenance updates. So, don't disable or remove any default guest additions. If you are brining your own image to, you need to install the associated guest images. For more information about installing guest additions, see [Preparing and importing images](https://cloud.ibm.com/docs/image-templates?topic=image-templates-preparing-and-importing-images).





 Provisioning a virtual server 

After you decide upon a deployment option, begin the provisioning process.



Table 2. Provisioning information

 Provisioning instructions Description 

 [Provisioning public instances](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-ordering-vs-public) Provision public instances with various options 
 [Provisioning transient instances](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-ordering-vs-transient) Provision transient instances with various options 
 [Provisioning reserved capacity and instances](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-provisioning-reserved-capacity-and-instances) Provision reserved capacity and instances with various options
Why does the installation fail for HCX with BYOL NSX Data Center Enterprise Plus? 

  What’s happening 

When you install VMware HCX with a BYOL NSX Data Center Enterprise Plus license, you must ensure that you select the correct license for NSX-T. In the Licensing section, under the dropdown for NSX, select Enterprise Plus.

  Why it’s happening 

If you select the incorrect NSX-T license, the installation bypasses the HCX installation and it continues, but you get an error message.

  How to fix it 

You can correct the problem in one of the following ways:



*  To request that your BYOL NSX Data Center Enterprise Plus license key is updated, open an IBM Support ticket by following the steps in [Contacting IBM Support](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-trbl_support). After your key is updated, you can install HCX again.
*  Select an appropriate NSX license edition. After that, HCX is installed without using your BYOL key. An activation key is generated for you and the extra charge for the HCX service is added.
Click the tile for the deployable architecture to open the details.
5. Select the latest product version in the Architecture section.
6. Select a variation, if more than one is available.
7. Agree to the terms and conditions on the Overview page and click Review deployment options.
8. Select the Create from the CLI deployment type in Deployment options.
9. Copy and paste the ibmcloud catalog install command in the IBM Cloud CLI. For more information, see [ibmcloud catalog install](https://cloud.ibm.com/docs/cli?topic=cli-manage-catalogs-plugininstall-software-version).
10. Run ibmcloud catalog install to install your custom configuration. Choose one of the following options:



1. Change directory to the directory where values.json is located and then run ibmcloud catalog install. For example:

ibmcloud catalog install --vl 1082e7d2-5e2f-0a11-a3bc-f88a8e1931fc.3aa45988-c0db-4e28-b01d-d31ef406280e-global --override-values values.json
2. Specify the path to values.json and then run ibmcloud catalog install. For example:

ibmcloud catalog install --vl 1082e7d2-5e2f-0a11-a3bc-f88a8e1931fc.3aa45988-c0db-4e28-b01d-d31ef406280e-global --override-values /<mypath>/values.json
Portworx is installed by using a [Helm chart](https://cloud.ibm.com/docs/containers?topic=containers-storage_portworx_about). When you install the Helm chart, Portworx automatically analyzes the local persistent storage that is available in your cluster and adds the storage to the Portworx storage layer. To add storage from your Portworx storage layer to your apps, you must use [Kubernetes persistent volume claims](https://cloud.ibm.com/docs/containers?topic=containers-storage_portworx_deploy).

For more information about how to install and use Portworx with IBM Cloud Kubernetes Service, see [Setting up software-defined storage (SDS) with Portworx](https://cloud.ibm.com/docs/containers?topic=containers-storage_portworx_about).





 Billing and support 

Classic SDS worker node machines that come with local disks, and classic virtual machines that you use for Portworx are in your monthly IBM Cloud Kubernetes Service bill. For pricing information, see the [IBM Cloud catalog](https://cloud.ibm.com/kubernetes/catalog/about). The Portworx license is a separate cost and is not included in your monthly bill.

Contact Portworx support by using one of the following methods.



* Sending an e-mail to support@purestorage.com.
* Calling +1 (866) 244-7121 or +1 (650) 729-4088 in the United States or one of the [International numbers](https://support.purestorage.com/Pure_Storage_Technical_Services/Technical_Services_Information/Contact_Us).
* Opening an issue in the [Portworx Service Portal](https://support.purestorage.com/Pure_Storage_Technical_Services/Technical_Services_Information/Contact_Us). If you don't have an account, see [Request access](https://purestorage.force.com/customers/CustomerAccessRequest).