vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Mounting an ISO on a bare metal server 

Although most IBM Cloud® customers use one of the standard operating systems that come with our servers, you can mount custom ISOs (disk images) on servers. You have two options for mounting custom ISOs.



 Overview 

For the two mounting methods to work, you need to connect to the private network through the SL VPN service, such as IBM Cloud SSL VPN - AMS01 or through another server that is connected to the network.

Lenovo hardware disk images larger than 50 MB must be mounted by using the IMM console and clicking Interface > Media tab.





 Option 1 (preferred): using IPMI (ISO on a CIFS share) 

If your infrastructure is already deployed on IBM Cloud, you can configure an existing server to offer a CIFS share to the internal network. You can then mount any ISO on the internal network to a bare metal server.

This option is the preferred method for installing a custom OS on a bare metal server. IPMI installs over the local network, which is fast and can keep an ISO mounted even if you log out or get disconnected from the management interface.

Follow these steps to install a custom OS from a CIFS Share:



1. Make sure that the ISO is on the CIFS Share.
2. Log in to the IPMI management console by pointing your web browser to the IP specified in cloud.ibm.com.
3. From the IBM Cloud console, go to Devices > Your server (device details) > Remote Mgmt. The username and password are also specified in the details.
4. Hover over Virtual Media and click CD-ROM image
5. Complete the appropriate details and click Save and Mount.



Not all users have permission to change the BIOS of the server. If necessary, you can open a support case and request the following items:



* Root user administrator privileges on IPMI (to be able to change the Virtual Media Attach mode).
* Change the boot sequence to ‘IPMI Virtual Disk’ as first boot option.





 What next 

After you make these changes, go back to the IPMI management console and go to Configuration > Remote session. Change the attach mode to Attach.
* [Updating the IBM Cloud CLI](https://cloud.ibm.com/docs/satellite?topic=satellite-cli-updatecli-update-include-update-ibmcloud-cli)
* [Updating installed plug-ins](https://cloud.ibm.com/docs/satellite?topic=satellite-cli-updatecli-update-include-cli-update-plugin)



[Uninstalling the stand-alone IBM Cloud CLI](https://cloud.ibm.com/docs/satellite?topic=satellite-uninstall-ibmcloud-cliuninstall-ibmcloud-cli)



* [Uninstalling on Windows](https://cloud.ibm.com/docs/satellite?topic=satellite-uninstall-ibmcloud-cliuninstall-cli-windows)
* [Uninstalling on Linux and macOS](https://cloud.ibm.com/docs/satellite?topic=satellite-uninstall-ibmcloud-cliuninstall-cli-linux-macos)







 Planning your environment for Satellite 

[Planning your environment for Satellite](https://cloud.ibm.com/docs/satellite?topic=satellite-infrastructure-planinfrastructure-plan)



* [Planning your infrastructure](https://cloud.ibm.com/docs/satellite?topic=satellite-infrastructure-planinfra-plan-infra)



* [Plan your infrastructure provider](https://cloud.ibm.com/docs/satellite?topic=satellite-infrastructure-planinfra-plan-provider)
* [Plan for a multizone location](https://cloud.ibm.com/docs/satellite?topic=satellite-infrastructure-planinfra-plan-multizone)
* [Plan your host systems](https://cloud.ibm.com/docs/satellite?topic=satellite-infrastructure-planinfra-plan-compatible)
Download the latest version of following files from [GitHub](https://github.com/IBM-Cloud/hpcs-management-utilities/releases) to the same directory where you store the cloudtke.bin file:



* cloudtke.sig: The signed cryptographic hash of cloudtke.bin (SHA-256).
* digicert_cert.pem: An intermediate code signing certificate to prove the Management Utilities signing certificate.
* signing_cert.pem: The signing certificate of the Management Utilities.



2. Extract the public key from the signing certificate signing_cert.pem to the sigkey.pub file with the following command by using the OpenSSL command-line tool:

openssl x509 -pubkey -noout -in signing_cert.pem -out sigkey.pub
3. Verify the integrity of the cloudtke.bin file with the following command:

openssl dgst -sha256 -verify sigkey.pub -signature cloudtke.sig cloudtke.bin

When the verification is successful, Verified OK is displayed.
4. Verify the authenticity and validity of the signing certificate with the following command:

openssl ocsp -no_nonce -issuer digicert_cert.pem -cert signing_cert.pem -VAfile digicert_cert.pem -text -url http://ocsp.digicert.com -respout ocsptest

When the verification is successful, Response verify OK and signing_cert.pem: good are displayed in the output.
5. If the verification fails, cancel the installation and [contact IBM for support](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-getting-help). Otherwise, proceed with the following steps.



3. From the command line, enter the directory that the downloaded installation file is located, and perform the following steps to install the applications:



1. Add the execute permission to the installation file by running the following command:

chmod +x cloudtke.bin
For the no OS option to work properly, PXE setup needs to be in the same VLAN as the Bare Metal Servers, or DHCP forwarding needs to be used.

It might be necessary to open a support case to request that the switch ports be regrouped in basic mode for this option to work. This request is necessary because the PXE protocol doesn't require compatibility with link aggregation (LACP), which is now a standard capability to provide redundancy. Another option is to order the server with unbonded uplinks (no link aggregation) and then change them to redundant uplinks after the OS is installed.





 Option 2: IPMI device 

Install operating systems on Bare Metal Servers with no operating systems by booting from an ISO by using the included IPMI device. For more information about booting from an ISO, see [Mounting an ISO on a bare metal server](https://cloud.ibm.com/docs/bare-metal?topic=bare-metal-bm-mount-iso).
Manually deploying a VPC and configure a backup/restore on iCOS with a backint hana agent on a cloud platform can be time-consuming. The Terraform automation assures not only a much quicker implementation, but also a standardized and less prone to error deployment. Terraform and Ansible are used for automating the deployment processes.





 Ansible for SAP installation 

Ansible is an automation tool for the deployment of several IT tasks. Ansible is used for automating the installation of an Hana db backup to iCOS automation module. For more information about Ansible, see the [Ansible Documentation](https://docs.ansible.com/ansible/latest/index.html).

The deployment is done by using the Ansible core, which provides CLI tools for automation. More information about Ansible core can be found on the [Ansible core page](https://docs.ansible.com/ansible-core/devel/index.html). The Ansible playbook is called directly by the Terraform script. The script starts with Terraform specific steps for creating the VPC, and continues automatically with the Ansible specific steps to install the Hana db backup to iCOS automation module system.





 Where to run the scripts 

The recommended way to run the scripts is from your Deployment Server because the Deployment Server has Terraform and Ansible already installed. If you want to run the scripts from your local workstation, you need to install Terraform and Ansible locally. For both the Deployment Server and local workstation, you must download the SAP Kits to the temporary storage assigned to you on the Deployment Server. Ansible installs the kits for you. You specify the location of the Kits in the configuration files.





 Prerequisites, create a Bastion server to run the scripts 

Before you deploy any of the SAP automated solutions on IBM Cloud VPC, you create a Bastion server VPC in your chosen region. The Bastion server is used for downloading and storing specific SAP solution media that are needed for later automation deployment. The Bastion server is used for both CLI deployment scenarios, as well for Schematics UI deployments.
Installing Knowledge Studio 

To install IBM Watson™ Knowledge Studio for IBM Cloud Pak® for Data, see the [installation procedure](https://www.ibm.com/docs/SSQNUZ_4.5.x/svc-wks/knowledge-studio-install-overview.html) in the IBM Cloud Pak for Data documentation.



  Upgrading to the latest version 

You can do in-place upgrades starting with the IBM Cloud Pak for Data 4.x releases. For more information, see [Upgrading](https://www.ibm.com/docs/SSQNUZ_4.5.x/svc-wks/knowledge-studio-upgrade.html).

For releases earlier than 4.0.x, you must backup data, uninstall, install the new version, and then restore the data.

To upgrade the Knowledge Studio for IBM Cloud Pak for Data service in the same cluster, complete the following steps.

Only [Backing up and restoring data](https://cloud.ibm.com/docs/watson-knowledge-studio-data?topic=watson-knowledge-studio-data-backup-restore) is supported when upgrading. Note that [Backing up and restoring databases](https://cloud.ibm.com/docs/watson-knowledge-studio-data?topic=watson-knowledge-studio-data-backup-restore-databases) is not supported.



1.  [Backup the workspaces data](https://cloud.ibm.com/docs/watson-knowledge-studio-data?topic=watson-knowledge-studio-data-backup-restore).
2.  Deprovision the existing Knowledge Studio instance on the IBM Cloud Pak for Data console.
3.  Uninstall the existing installation.
4.  Install the latest version.
5.  Provision a new Knowledge Studio instance in the IBM Cloud Pak for Data console.
6.  [Restore the workspaces data](https://cloud.ibm.com/docs/watson-knowledge-studio-data?topic=watson-knowledge-studio-data-backup-restore) into the new instance.
* [Optional: Setting up encryption by using Hyper Protect Crypto Services](https://cloud.ibm.com/docs/openshift?topic=openshift-deploy-odf-classicodf-create-hscrypto-classic)
* [Preparing your cluster for an OpenShift Data Foundation installation](https://cloud.ibm.com/docs/openshift?topic=openshift-deploy-odf-classicodf-cluster-prepare-classic)
* [Getting your device details](https://cloud.ibm.com/docs/openshift?topic=openshift-deploy-odf-classicodf-classic-get-devices)



* [Installing the add-on from the CLI](https://cloud.ibm.com/docs/openshift?topic=openshift-deploy-odf-classicinstall-odf-cli-classic)
* [Installing the OpenShift Data Foundation add-on from the console](https://cloud.ibm.com/docs/openshift?topic=openshift-deploy-odf-classicinstall-odf-console-classic)
* [Creating your storage cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-deploy-odf-classicocs-classic-deploy-crd)
* [Parameter reference](https://cloud.ibm.com/docs/openshift?topic=openshift-deploy-odf-classicodf-classic-param-ref)



* [Version 4.13 parameters](https://cloud.ibm.com/docs/openshift?topic=openshift-deploy-odf-classicodf-classic-params-413)
* [Version 4.10, 4.11, and 4.12 parameters](https://cloud.ibm.com/docs/openshift?topic=openshift-deploy-odf-classicodf-classic-params-410)
The following components are installed in the selected cluster in the cloud data center.



* PrimaryIO On-cloud Manager
* PrimaryIO Cloud Cache (one per each VMware® ESXi™ node in cloud cluster)



After the cloud endpoint is successfully configured, a network connection between IBM Cloud and the on-premises cluster is established.

For more information, see the [HDM documentation](https://docs.primaryio.com).







 Troubleshooting PrimaryIO HDM 

For more information about troubleshooting installation-related issues, see the [HDM documentation](https://docs.primaryio.com).





 Uninstalling PrimaryIO HDM 

To uninstall HDM from the hybrid infrastructure, complete the installation steps in reverse order:



* Removing the IBM Cloud Endpoint
* Uninstalling on-premises components
* Uninstalling the HDM IO filter
* Unregistering the HDM vCenter Server plug-in
* Deleting the PrimaryIO appliance



For more information, see the [HDM documentation](https://docs.primaryio.com).





 Related links 



* [Contacting IBM Support](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-trbl_support)
Configure OIDC integration between IBM Cloud Pak for Multicloud Management and the Infrastructure management appliance.



* To install Infrastructure management as a virtual machine appliance, see [Getting started deploying Infrastructure management as a virtual machine appliance](https://cloud.ibm.com/docs/cloud-pak-multicloud-management?topic=cloud-pak-multicloud-management-getting-started-deploying-infrastructure-management-as-a-virtual-machine-appliance).



The Infrastructure management-related operators.

- ibm-management-im-install for Infrastructure management. For more information, see [Infrastructure management](https://www.ibm.com/support/knowledgecenter/SSFC4F_2.1.0/mcm/infrastructure/infra_mgmt_intro.html).

- ibm-management-infra-vm for provisioning virtual machines and instances. For more information, see [Provisioning Virtual Machines and Instances](https://www.ibm.com/support/knowledgecenter/SSFC4F_2.1.0/Infra_mgmt/provisioning_virtual_machines_and_hosts/index.html).

- ibm-management-infra-grc for Infrastructure management. For more information, see [Governance, risk, and compliance](https://www.ibm.com/support/knowledgecenter/SSFC4F_2.1.0/mcm/compliance/compliance_intro.html).
IBM Cloud Pak for Multicloud Management 2.0 Infrastructure management for Red Hat OpenStack Platform cp4mcm-im-rhos-2.0.x86_64.qcow2 CC732EN 
 Automation navigation for IBM Cloud Pak for Multicloud Management 2.0 automation-navigation-updates.sh CC734EN 







 Installing Infrastructure management - the options 

Two options are available to install and deploy operands for Infrastructure management.



 Option 1. Install Infrastructure management as a containerized deployment (podified). 



* Installing Infrastructure management (podified) in the hub cluster consists of these steps.



1. Configure OIDC integration between IBM Cloud Pak for Multicloud Management and Infrastructure management.
2. Deploy the ibm-management-im-install operand.
3. Create a connection for the functional operators.
4. Download and run the automation script to enable navigation to Infrastructure management with IBM Cloud Pak for Multicloud Management.



* To install Infrastructure management as a containerized deployment, see [Getting started deploying Infrastructure management as a containerized deployment (podified)](https://cloud.ibm.com/docs/cloud-pak-multicloud-management?topic=cloud-pak-multicloud-management-getting-started-deploying-infrastructure-management-as-a-containerized-deployment-podified-).







 Option 2. Install Infrastructure management as a virtual machine appliance. 



* Installing Infrastructure management as a virtual machine appliance consists of these steps.



1. Download the Infrastructure management appliance package for your environment.
2. Install and configure the Infrastructure management appliance.
3. Configure OIDC integration between IBM Cloud Pak for Multicloud Management and the Infrastructure management appliance.



* To install Infrastructure management as a virtual machine appliance, see [Getting started deploying Infrastructure management as a virtual machine appliance](https://cloud.ibm.com/docs/cloud-pak-multicloud-management?topic=cloud-pak-multicloud-management-getting-started-deploying-infrastructure-management-as-a-virtual-machine-appliance).
You can find the contact details on the [ESS support page](https://www.ibm.com/docs/en/entitled-systems-support?topic=information-ess-support).
3. After IBM has registered the customer number or server, click Software downloads under My entitled software in the navigation pane.
4. Select a category and group.
5. Check the box next to the installation image you would like to download and click Continue.
6. Next, select the language feature that you want and click Continue.
7. Agree to the terms and conditions.
8. Click the Click here to use HTTP link to download the ISO image by using HTTP. You can also click the Download now button.



AIX installation DVDs are delivered as ISO image files, while other installation images are delivered as compressed tar archives. In some cases, AIX ISO images are zipped and can be unzipped by using the [AIX Toolbox for Linux Application](https://www.ibm.com/support/pages/aix-toolbox-linux-applications-overview). After you download an ISO image, it is not necessary to burn a DVD to access the contents of the ISO image.





 Copying and installing your ISO image to an AIX virtual machine (VM) 

After you download an AIX installation DVD as an ISO image, you must copy the image to an existing AIX VM's file system. To copy the image, you must use Secure Copy Protocol (SCP). SCP is a protocol for securely transferring files between a local and a remote host or between two remote hosts.



1. Copy the ISO image to an existing AIX VM's file system by using the [scp](https://www.ibm.com/support/knowledgecenter/ST5Q4U_1.5.2/com.ibm.storwize.v7000.unified.152.doc/usgr_usng_scp.html) command.

The scp command does not work unless you are on a public network.

scp [Options]From_Host:]Source_File [User@]To_Host:]
2.
After you set up your single zone application:



* Configure snapshot backups for your application for SAZ. For more information, see [Taking snapshot backups for your 3-Tier applications for SAZ](https://cloud.ibm.com/docs/ha-infrastructure?topic=ha-infrastructure-snapshot-backups-3-tier-applications-saz).
* Install the software packages that you want on your virtual server instances. The packages vary based on your solution.
[Access your Red Hat OpenShift cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-access_cluster).
17. Run the following command to verify the ODF pods are running.

oc get pods -n openshift-storage



Next steps
: [Deploy an app that uses ODF](https://cloud.ibm.com/docs/openshift?topic=openshift-odf-deploy-app).





 Installing the add-on from the CLI 

You can install the add-on by using the [ibmcloud oc cluster addon enable command](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_cluster_addon_enable).



1. Review the [VPC parameter reference](https://cloud.ibm.com/docs/openshift?topic=openshift-deploy-odf-vpc&interface=uiodf-vpc-param-ref). When you enable the add-on, you can override the default values by specifying the --param "key=value" option for each parameter that you want to override.
2. [Access your Red Hat OpenShift cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-access_cluster).
3. List the openshift-data-foundation add-on versions. Make a note of the default version and determine the version that you want to install.

ibmcloud ks cluster addon versions
4. Before you enable the add-on, review the [change log](https://cloud.ibm.com/docs/openshift?topic=openshift-odf_addon_changelog) for the latest version information. Note that the add-on supports n+1 cluster versions. For example, you can deploy version 4.10.0 of the add-on to an OCP 4.9 or 4.11 cluster.
[Access your Red Hat OpenShift cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-access_cluster).
17. Run the following command to verify the ODF pods are running.

oc get pods -n openshift-storage



Next steps
: [Deploy an app that uses ODF](https://cloud.ibm.com/docs/openshift?topic=openshift-odf-deploy-app).





 Installing the add-on from the CLI 

You can install the add-on by using the [ibmcloud oc cluster addon enable command](https://cloud.ibm.com/docs/openshift?topic=openshift-kubernetes-service-clics_cluster_addon_enable).



1. Review the [VPC parameter reference](https://cloud.ibm.com/docs/openshift?topic=openshift-deploy-odf-vpcodf-vpc-param-ref). When you enable the add-on, you can override the default values by specifying the --param "key=value" option for each parameter that you want to override.
2. [Access your Red Hat OpenShift cluster](https://cloud.ibm.com/docs/openshift?topic=openshift-access_cluster).
3. List the openshift-data-foundation add-on versions. Make a note of the default version and determine the version that you want to install.

ibmcloud ks cluster addon versions
4. Before you enable the add-on, review the [change log](https://cloud.ibm.com/docs/openshift?topic=openshift-odf_addon_changelog) for the latest version information. Note that the add-on supports n+1 cluster versions. For example, you can deploy version 4.10.0 of the add-on to an OCP 4.9 or 4.11 cluster.
* [Deploying IBM WebSphere Application Server](https://cloud.ibm.com/docs/was-for-vsi?topic=was-for-vsi-getting-started) describes how to install a WebSphere Application Server traditional or Liberty environment on one or more virtual server instances (VSIs).
* [Migrating your workload](https://cloud.ibm.com/docs/was-for-vsi?topic=was-for-vsi-migrating) points to information that you can follow to migrate your existing WebSphere Application Server traditional or Liberty applications to VSIs.
* [Troubleshooting](https://cloud.ibm.com/docs/was-for-vsi?topic=was-for-vsi-troubleshoot) describes problems that you might encounter when you install and use the product and provides instructions for fixing the problems.
For more information, see the [Administration Guide for SAP Data Intelligence](https://help.sap.com/viewer/b13b5722c8ff4bf9bb097251310031d0/latest/en-US/884ffcd587784ed2a311b2c19feb8410.html).

For productive setups, we recommend preparing the required SSL certificates using the preferred tools. For non-productive setups, note that the SAP Data Intelligence installer can generate self-signed certificates.





 Red Hat OpenShift Cluster Storage 

SAP Data Intelligence requires access to persistent storage that is attached to the OpenShift cluster. For importing, exporting, and check-pointing SAP Vora database tables, SAP Data Intelligence requires access to a persistent shared file system or an object store. In the IBM Cloud environment, IBM Cloud Object Storage is utilized for that purpose.





 Prerequisites 

To be able to access the required installation binaries and authorizations to install SAP Data Intelligence



* You need an SAP S-user ID and Download Authorization for login to the [SAP ONE Support Launchpad](https://launchpad.support.sap.com).
* You need a Red Hat account for login to the [Red Hat Registry Service Accounts](https://access.redhat.com/terms-based-registry/).





 Next Step 



* Continue with [Deploying your OpenShift cluster and jump host](https://cloud.ibm.com/docs/sap?topic=sap-rhos-di-set-up-cluster).