vania-janet/multiturn-rag-retrieval-data huggingface dataset:
FAQs for Power Systems Virtual Server with VPC landing zone deployable architectures 

FAQs for the Power Systems Virtual Server for SAP HANA deployable architecture. To find all FAQs for IBM Cloud®, see our [FAQ library](https://cloud.ibm.com/docs/faqs).



  What does it mean for a deployable architecture to be SAP-certified? 

SAP-certified designates that the deployable architecture creates services that are certified by SAP to run SAP HANA based systems for production. For more information, see [IBM Cloud documentation for SAP](https://cloud.ibm.com/docs/sap).





  How long does the deployment take? 

Duration for the deployment depends on the daily IBM Cloud data center utilization and on the size and number of PowerVS instances. You can assume that a deployment of one SAP system as 'SAP ready PowerVS' takes about 1 to 2 hours. SAP software installation is additional time.





  Why certain IBM Cloud data centers might not be available? 

This deployable architecture ensures certain level of quality. Every data center is verified by our quality and assurance framework before we make it available. We extend the list of supported data centers regularly after all SAP-related verifications are completed.
Moving from IBM Cloud Pak for Data version 3.5 to version 4.0.3 continues to require use of migration utilities. For more information, see [Upgrading Watson Text to Speech](https://www.ibm.com/docs/en/cloud-paks/cp-data/4.0?topic=speech-upgrading-watson-text).

EDB PostgreSQL operator and license installation changes
: Installation, upgrade, and uninstallation for the Enterprise DB PostgreSQL operator and license have changed:



* Instructions for installing the EDB PostgreSQL operator and license are now included with the IBM Cloud Pak for Data foundational services. The instructions for installing the Speech services have been updated accordingly. For more information, see [Installing Watson Text to Speech](https://www.ibm.com/docs/en/cloud-paks/cp-data/4.0?topic=speech-installing-watson-text).
* Instructions for upgrading from Text to Speech version 4.0.0 to 4.0.3 include instructions for uninstalling the previous EDB PostgreSQL operator and license and reinstalling them with the IBM Cloud Pak for Data foundational services. For more information, see [Upgrading Watson Text to Speech](https://www.ibm.com/docs/en/cloud-paks/cp-data/4.0?topic=speech-upgrading-watson-text).
* Instructions for uninstalling the Speech services now include steps for removing the EDB PostgreSQL operator and license that were previously installed with Text to Speech. For more information, see [Uninstalling Watson Text to Speech](https://www.ibm.com/docs/en/cloud-paks/cp-data/4.0?topic=speech-uninstalling-watson-text).



New guidance for scaling up your installation
: The service now provides updated guidance about scaling up your installation. The information includes specifying the number of pods and the maximum number of concurrent sessions for enhanced neural or neural voices.
Why can't I install a Helm chart with updated configuration values? 

Virtual Private Cloud

Classic infrastructure

  What’s happening 

When you try to install an updated Helm chart by running helm install <release_name> <helm_repo>/<chart_name> -f config.yaml, you get the following error message.

Error: failed to download "<helm_repo>/<chart_name>"

  Why it’s happening 

You might need to update your Helm installation because of the following reasons:



*  The URL to the IBM Cloud Helm repository that is configured on your local machine might be incorrect.
*  The name of your local Helm repository might not match the Helm repository name or URL of the installation command that you copied from the Helm chart instructions.
*  The Helm chart that you want to install does not support the version of Helm that you installed on your local machine.
*  Your cluster network setup changed from public access to private-only access, but Helm was not updated.



  How to fix it 

To troubleshoot your Helm chart:



1.  List the IBM Cloud Helm repositories currently available in your Helm instance.

helm repo list
2.  Remove the IBM Cloud Helm repositories.

helm repo remove <helm_repo>
3.  Reinstall the Helm version that matches a supported version of the Helm chart that you want to install. As part of the installation, add and update the IBM Cloud Helm repositories. For more information, see [Installing Helm v3 in your cluster](https://cloud.ibm.com/docs/containers?topic=containers-helminstall_v3).



Now, you can follow the instructions in the Helm chart README to install the Helm chart in your cluster.
* [Enable and disable the built-in administrator account](https://learn.microsoft.com/en-us/windows-hardware/manufacture/desktop/enable-and-disable-the-built-in-administrator-account?view=windows-10).







 Initial steps for creating a Windows custom image 

Complete the following steps to start creating a Windows custom image.



1. Begin with a Windows ISO image file. For example, Windows.iso.
2. Create a VHD image where you can install Windows.

qemu-img create -f vpc Windows.vhd 100G

IBM Cloud® supports custom image import with VHD or qcow2. However, Virtual Box does not support the qcow2 format.
3. Use VirtualBox to create a virtual machine with the VHD image that you created in step 2. For more information, see [Oracle VM VirtualBox User Manual](https://www.virtualbox.org/manual/).



If you choose to use a method other than VirtualBox to create the custom image, such as VMware, you must remove all drivers that are specific to that hypervisor from the custom image.





 Customizing the virtual machine bvy using Virtual Box 

Complete the following steps to customize the virtual machine.



1. In Storage settings, add the Windows installation ISO and the virtio-win driver ISO as optical drives. For example, Windows.iso and virtio-win-1.9.15.iso.
2. Start the virtual machine and begin the Windows installation. When you see the page Where do you want to install Windows? you must load all of the virtio-win drivers. You might need to clear "Hide drivers that aren't compatible with this computer's hardware" to access all of the required drivers. Then, you can select Drive 0 and continue with the installation. When the installation is complete, shut down the virtual machine and remove the optical drives that you added: Windows installation ISO and virtio-win driver ISO. You can ignore any warnings about removing an optical drive.
3. Enable local administrator account and reset the local admin password.
* [Run the installation command](https://cloud.ibm.com/docs/openshift?topic=openshift-cli-installcli-install-include-step1-install-idt)
* [Verify the installation](https://cloud.ibm.com/docs/openshift?topic=openshift-cli-installcli-install-include-step2-verify-idt)
* [Install CLI plug-ins and tools](https://cloud.ibm.com/docs/openshift?topic=openshift-cli-installcli-install-include-step3-install-idt-manually)
* [Install the Red Hat OpenShift CLI](https://cloud.ibm.com/docs/openshift?topic=openshift-cli-installinstall-kubectl-cli)



[Updating the CLI](https://cloud.ibm.com/docs/openshift?topic=openshift-cli-updatecli-update)



* [Updating the IBM Cloud CLI](https://cloud.ibm.com/docs/openshift?topic=openshift-cli-updatecli-update-include-update-ibmcloud-cli)
* [Updating installed plug-ins](https://cloud.ibm.com/docs/openshift?topic=openshift-cli-updatecli-update-include-cli-update-plugin)



[Setting up the API](https://cloud.ibm.com/docs/openshift?topic=openshift-cs_api_installcs_api_install)



* [About the API](https://cloud.ibm.com/docs/openshift?topic=openshift-cs_api_installapi_about)
* [Automating cluster deployments with the API](https://cloud.ibm.com/docs/openshift?topic=openshift-cs_api_installcs_api)
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). A dedicated reference architecture about this AnyDB SAP HANA on IBM Cloud VPC cloud can be found on [AnyDB - SAP HANA Database](https://cloud.ibm.com/docs/sap?topic=sap-anydb-hana-db).

SAP HANA installation media that are used for this deployment is the default one for SAP HANA, platform edition 2.0 SPS05. The media is available at SAP Support Portal in the INSTALLATION AND UPGRADE area and it must be provided manually in the input parameter file.





 Terraform for infrastructure deployment 

Terraform on IBM Cloud enables predictable and consistent provisioning of IBM Cloud solutions. For more information about Terraform on IBM Cloud, see [Terraform on IBM Cloud getting started tutorial](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-getting-started).

Terraform is used to provision of the infrastructure components in IBM Cloud. For the automating this process, the current solution uses a Terraform script for deploying a VPC and a VSI with SAP certified storage and network configuration. The VPC contains one subnet and one security group that has three rules:



* Allow all outbound traffic from the VSI
* Allow inbound DNS traffic (UDP port 53)
* Allow inbound SSH traffic (TCP port 22)



After the successful deployment of the infrastructure, the Terraform script calls the Ansible Playbook, which automatically installs the SAP application. Access creating single-tier VPC for SAP by using Terraform to get the detailed steps about using Terraform only for the creation of a VPC for SAP.





 Ansible for SAP installation
: Known issue: The Swedish telephony (sv-SE_Telephony) and Italian multimedia (it-IT_Multimedia) models are not yet available. They will be made available with version 4.6.5.

Defect fix: You can now change the installed models and voices with the advanced installation options
: Defect fix: During installation, you can now specify different models or voices with the advanced installation options of the command-line interface. Previously, the service always installed the default models and voices. The limitation continues to apply for Watson Speech services versions 4.6.0, 4.6.2, and 4.6.3. For information about installing models and voices, see Specifying additional installation options in [Installing Watson Speech services](https://www.ibm.com/docs/en/cloud-paks/cp-data/4.6.x?topic=services-installing).

Setting load balancer timeouts
: Watson Speech services require that you change the load balancer timeout settings for both the server and client to 300 seconds. These settings ensure that long-running speech recognition requests, those with long or difficult audio, have sufficient time to complete. For more information, see Information you need to complete this task in [Installing Watson Speech services](https://www.ibm.com/docs/en/cloud-paks/cp-data/4.6.x?topic=services-installing).

Security vulnerabilities addressed
: The following security vulnerabilities have been fixed:



* [Security Bulletin: IBM Watson Speech Services Cartridge for IBM Cloud Pak for Data is vulnerable to cross-site scripting in GNOME libxml2 (CVE-2016-3709](https://www.ibm.com/support/pages/node/6967621)
* [Security Bulletin: IBM Watson Speech Services Cartridge for IBM Cloud Pak for Data is vulnerable to a denial of service in SQlite (CVE-2020-35525)](https://www.ibm.com/support/pages/node/6967623)
Management-nsx-edge public IP Public subnet for management edge BigIP license server 104.219.111.132/32 443 TCP License registration HTTPS 







 Ports for FortiGate Virtual Appliance 

The following table provides information about the FortiGate® virtual appliance ports.



Table 3. FortiGate Virtual Appliance ports

 Source Subnet, IP range Target Subnet, IP range Port Protocol Purpose Service 

 Management-nsx-edge public IP Public subnet for management edge Fortinet® servers 208.91.112.0/22 443 TCP FortiGate installation HTTPS 
 Management-nsx-edge public IP Public subnet for management edge Fortinet servers 96.45.33.0/24 443 TCP FortiGate installation HTTPS 
 Management-nsx-edge public IP Public subnet for management edge Fortinet servers 66.35.17.248 443 TCP FortiGate installation HTTPS 







 Ports for VMware HCX 

The following table provides information about the VMware HCX™ ports.



Table 4. VMware HCX ports

 Source Subnet, IP range Target Subnet, IP range Port Protocol Purpose Service 

 HCX New subnet ordered in private VLAN Windows Active Directory Private primary subnet <br>Infrastructure VMs 53 UDP Use Windows DNS service DNS 
 HCX New subnet ordered in private VLAN vCenter Server Infrastructure VMs 443 TCP Use vCenter Server REST service HTTPS 
 HCX New subnet ordered in private VLAN NSX Manager Infrastructure VMs 443 TCP Use NSX Manager registration service HTTPS 
 HCX public IP New subnet ordered in public VLAN connect.hcx. <br>vmware.com Public IP 45.60.63.140 443 TCP Registration service HTTPS 
 vCenter Server Infrastructure VMs HCX New subnet ordered in private VLAN 443 TCP Use HCX REST service HTTPS 
 IBM CloudDriver Private primary subnet <br>Infrastructure VMs HCX New subnet ordered in private VLAN 443 TCP Use HCX REST service HTTPS 
 IBM CloudDriver Private primary subnet <br>Infrastructure VMs HCX New subnet ordered in private VLAN 9443 TCP Use the HCX appliance management interface for HCX system configuration HTTPS
* Allow inbound DNS traffic (UDP port 53)
* Allow inbound SSH traffic (TCP port 22)



After the successful deployment of the infrastructure, the Terraform script calls the Ansible Playbook, which automatically installs the SAP application. Access creating single-tier VPC for SAP by using Terraform to get the detailed steps about using Terraform only for the creation of a VPC for SAP.





 Ansible for SAP installation 

Ansible is an automation tool for the deployment several IT tasks. This solution performs the automated deployment of SAP HANA 2.0 DB on Red Hat Enterprise Linux 7.6 for SAP HANA on stand-alone SAP HANA box VSI. For more information about Ansible, check out the documentation available on the Ansible page.

The deployment is done by 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 Terraform script is run in one run. During the run, the first steps are Terraform specific for creating the VPC, and it continues automatically with the second, Ansible, steps for the installation of the SAP system.

This automation is offered free of charge however, the provisioned infrastructure comes at cost.
Run the Agent installation package.
2. At the language screen, click OK.
3. At the welcome screen, click Next.
4. Select the Modify installation, and click Next.
5. Select the Leave Unchanged, and click Next.
6. At the custom setup screen, select each plug-in that you purchased, and select This feature will be installed on ..., then click Next.
7. Select Keep my current registration, and click Next.
8. Click Install.
9. When the installation is complete, check to ensure that both services are enabled and running.
10. If Cloud Backup Portal is able to access or view the database, then the installation was successful.







 Installing the plug-in for Linux 

The Oracle plug-in is an add-on to the Linux® Agent and is installed with the Agent on the database host. The Linux® Agent application must be installed before the plug-in installation occurs. The agent is available as a 32-bit application and a 64-bit application. For more information, see [Installing the IBM Cloud Backup for Classic Client in Linux®](https://cloud.ibm.com/docs/Backup?topic=Backup-InstallinLinux).

The Oracle plug-in installation kit is available in a tar.gz file.



1. On the host, download the installation package.

http://downloads.softlayer.com/evault/Oracle-Plugin-Linux-x64-8.10.5249.tar.gz
2. Extract the files from the package.

 cd /tmp
 tar xvf Oracle-Plugin-Linux-x64-8.10.5249.tar
3. Go to the folder.

 cd Oracle-Plugin-Linux-x64-8.10.5249.xxxx
4. Run the installation script.

 ./install.sh
5. Follow the installation instructions on the screen.



The Oracle plug-in performs an "inconsistent" whole database backup that requires that the database runs in ARCHIVELOG mode.
For more information about the IBM Cloud Provider plug-in for Terraform supported versions, see [Installing the Terraform CLI](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-setup_cli).

For example, you can download terraform_0.15.5_darwin_amd64.zip for a MacOS.
3. Extract the Terraform zip file and copy the files to your terraform directory.

unzip ./terraform_1.1.0_darwin_amd64.zip -d <terraform-directory>

For example,

unzip ./terraform_1.1.0_darwin_amd64.zip -d /usr/local/bin
4. Set the environment PATH variable to your Terraform files.

export PATH=$PATH:/usr/local/bin/terraform
5. Verify that the installation is successful by using a terraform command.

./terraform







 Step 2. Set up the IBM Cloud Provider plug-in 

After the Terraform CLI installation is complete, you must set up the IBM Cloud Provider plug-in for Terraform so that you can start working with resources and services in IBM Cloud. For a list of supported versions, see the [IBM Cloud Provider plug-in releases](https://github.com/IBM-Cloud/terraform-provider-ibm/releases).

The setup of the IBM Cloud Provider plug-in varies depending on the Terraform CLI version that you want to use. To run your Terraform configuration files with Terraform version 0.13.x or higher, installation of the IBM Cloud Provider plug-in for Terraform is not required. For more information, see [Terraform v0.13.x and higher](https://cloud.ibm.com/docs/ibm-cloud-provider-for-terraform?topic=ibm-cloud-provider-for-terraform-setup_cliinstall-provider-v13).
Installing the IBM Cloud HSM client 

You need to install the client software before you can configure your IBM Cloud® HSM.

Complete instructions about installing the client are available in the [SafeNet Luna Network HSM 7.2 Installation Guide](https://supportportal.gemalto.com/csm?id=kb_article_view&sys_kb_id=19a81c8bdb9a1fc8d298728dae96197d&sysparm_article=KB0017573) (page 32). Log in by using your Gemalto Support Portal Customer ID, which was supplied to you by IBM Cloud Support. If you didn't receive this ID, contact [IBM Cloud Support](https://cloud.ibm.com/docs/get-support?topic=get-support-using-avatar).

Use the following steps to access the installation guide after you log in to the Gemalto Support Portal.



1.  Click My Products.
2.  Select Luna SA/Luna Network HSM.
3.  Under Product Versions, select 7.x or 6.x.
4.  Download the applicable client and documentation for your operating system.
Mount the disk image by double-clicking the macos_dsdriver.dmg file.



A new Finder window opens with the contents of the disk image.

If the Finder window does not open, double-click the macos_dsdriver icon on your desktop. 2. In the Finder window, double-click the installDSDriver.sh file.

The driver package is installed in the default location: /Applications/dsdriver.
* For updates to your existing driver package installation



1. Back up current configuration files:



a. Go the Applications/dsdriver/cfg folder.

b. Copy the following files to a different folder:

db2cli.ini

db2dsdriver.cfg



2. Remove the currently installed driver package by right-clicking the dsdriver folder and selecting Move to Trash.
3. Install the new driver package as described in the preceding For a new installation section:



a. Mount the disk image by double-clicking the macos_dsdriver.dmg file. b. In the Finder window, double-click the installDSDriver.sh file. 4. Restore the configuration files:

Copy the db2cli.ini and db2dsdriver.cfg files that you saved from Step 1 to the /Applications/dsdriver/cfg folder.







 What's next? 

To be able to connect your local applications or client tools to your Db2 on Cloud database, [configure your local environment](https://cloud.ibm.com/docs/Db2onCloud/connecting?topic=Db2onCloud-drvr_pkgcfg_loc_env).







 Installing the driver package on Windows 

You can install the Db2 on Cloud driver package on Windows by using the installer.



 Prerequisites
SAP Content Server 

The SAP Content Server is a stand-alone component for storing large quantities of electronic documents in any format and with any content. This component can cache the content from several locations the business operates in which reduces network load. To use the SAP Content Server, your SAP applications must support its use.

The SAP Content Server uses the SAP MaxDB database and one of the following operating systems:



*  Windows Server
*  SUSE Linux®
*  Red Hat Linux



For more information about these supported operating systems releases, see the [SAP Product Availability Matrix (PAM)](https://support.sap.com/en/release-upgrade-maintenance.htmlsection_1969201630).

For more information about the SAP Content Server, see [SAP Help](https://help.sap.com/viewer/index) and documentation on the [SAP NetWeaver Knowledge Server components](https://help.sap.com/viewer/3ad3ba0715c5422eae08578d4c40328d/latest/en-US/4cff90895b605dc6e10000000a42189c.html).



  Usage considerations 

The SAP Content Server is not an alternative for optical storage and other storage media for long-term document archiving.

Follow the SAP Content Server Installation Guide, found on the [SAP Help Portal](https://help.sap.com/viewer/index) under "Installation of SAP Content Server". The guide is available for Windows or Linux.
For more information about installing the Mac OS X M1/ARM or Linux 64-bit ARM versions of the CLI, see the IBM Cloud CLI [release notes](https://github.com/IBM-Cloud/ibm-cloud-cli-release/releases/). These versions are provided as-is and are not fully supported.

For more installation methods, see [IBM Cloud CLI](https://cloud.ibm.com/docs/cli?topic=cli-getting-started).





 Step 2: Verify the installation 

To verify that the CLI was installed successfully, run the help command:

ibmcloud help

The output lists the usage instructions, the current version, and the supported commands.





 Step 3: Install CLI plug-ins and tools 

To manually install the CLI plug-ins and tools, see [Extending IBM Cloud CLI with plug-ins](https://cloud.ibm.com/docs/cli?topic=cli-plug-ins).

To install the container-service or ks plugin, which includes all ibmcloud sat commands, run the following command.

ibmcloud plugin install ks
* get the port number >PORT> that you will need later

oc get svc -n sap-slcbridge slcbridgebase-service -o jsonpath=$'{.spec.ports[0].nodePort}n'



This URL will be required later to launch the SDI installation - [https://HOSTNAME](https://HOSTNAME):PORT/docs/index.html.







 SAP Data Intelligence installation via running the SAP Maintenance Planner 

Review SAP documentation about the installation setup - [Install SAP Data Intelligence with SLC Bridge](https://help.sap.com/viewer/a8d90a56d61a49718ebcb5f65014bbe7/3.2.latest/en-US/7e4847e241c340b3a3c50a5db11b46e2.html).

Before installing SAP Data Intelligence you need to review the Red Hat article and do these steps:



* [(RHA) 5.3. Project setup](https://access.redhat.com/articles/5100521project-setup)



As described there execute all oc adm policy add-scc-to-* commands and then start the SAP Maintenance Planner.

Launch [SAP Maintenance Planner (MP)](https://apps.support.sap.com/sap/support/mp) in a browser and click Plan a New System.



1. Click Plan
2. Select CONTAINER BASED
3. Select SAP DATA INTELLIGENCE
4. Select SAP DATA INTELLIGENCE 3
5. Select 3.2 11/2021 from the drop-down box
6. Check DI - Platform full
7. Click Confirm Selection then Next
8. Select Linux on x86_64 64bit
9. Click Confirm Selection then Next
10. Click Execute Plan
11. Fill HOSTNAME that you found above into entry field Fully Qualified Domain Name
12. Fill PORT that you found above into entry field Port
13. Click Next