vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Why am I not authorized when I start the Trusted Key Entry application? 

You receive an error message when you start the Trusted Key Entry application.

  What’s happening 

You might receive the following error message:

Zoom

![Unauthorized when you run TKE CLI plug-in commands](https://cloud.ibm.com/docs-content/v1/content/217f108cc44e2ce15fb692d4b57b4c628464e908/hs-crypto//images/tke_401.gif)

Figure 3. Unauthorized when you start the Trusted Key Entry application.

  Why it’s happening 

A valid authentication token is needed for the TKE application to send requests to IBM Cloud. You must log in to IBM Cloud with the IBM Cloud CLI to create a valid authentication token before you can run the TKE application, which might be the causes of this error:



*  You do not log in to IBM Cloud to create an authentication token.
*  Your authentication token is expired.



  How to fix it 

From the command line, log in to the IBM Cloud with the ibmcloud login command. Click Refresh Panel on the Crypto units tab to retry the query of your service instance.
The delta between those two variables specifies the maximum number of worker nodes that can either be created or destroyed by the LSF resource connector auto scaling feature. In configurations where that delta exceeds 250, it's recommended to take caution if the characteristics of the workload are expected to result in >250 cluster node join or remove operation requests at a single point in time. In those cases, it's recommended to pace the job start and stop requests, if possible. Otherwise, you might see noticeable delays in some subset of the nodes joining or being removed from the cluster.
* Why are there two different resource group parameters that can be specified in the IBM Cloud catalog tile?

The first resource group parameter entry in the Configure your workspace section in the IBM Cloud catalog applies to the resource group where the Schematics workspace is provisioned on your IBM Cloud account. The value for this parameter can be different than the one used for the second entry in the Parameters with default values section in the catalog. The second entry applies to the resource group where VPC resources are provisioned. As specified in the description for this second resource_group parameter, note that only the default resource group is supported for use of the LSF Resource Connector auto-scaling feature.
* Where are the Terraform files used by the IBM Spectrum LSF tile located?

The Terraform-based templates can be found in this [GitHub repository](https://github.com/IBM-Cloud/hpc-cluster-lsf).
* Where can I find the custom image name to image ID mappings for each cloud region?

The mappings can be found in the image-map.tf file in this [GitHub repository](https://github.com/IBM-Cloud/hpc-cluster-lsf).
* Which Spectrum LSF and Spectrum Scale versions are used in cluster nodes deployed with this offering?

Cluster nodes that are deployed with this offering include IBM Spectrum LSF 10.1 Standard Edition plus Data Manager plus License Scheduler.
In configurations where that delta exceeds 250, it's recommended to take caution if the characteristics of the workload are expected to result in >250 cluster node join or remove operation requests at a single point in time. In those cases, it's recommended to pace the job start and stop requests, if possible. Otherwise, you might see noticeable delays in some subset of the nodes joining or being removed from the cluster.





 Why are there two different resource group parameters that can be specified in the IBM Cloud catalog tile? 

The first resource group parameter entry in the Configure your workspace section in the IBM Cloud catalog applies to the resource group where the Schematics workspace is provisioned on your IBM Cloud account. The value for this parameter can be different than the one used for the second entry in the Parameters with default values section in the catalog. The second entry applies to the resource group where VPC resources are provisioned. As specified in the description for this second resource_group parameter, note that only the default resource group is supported for use of the LSF Resource Connector auto-scaling feature.





 Where are the Terraform files used by the IBM Spectrum LSF tile located? 

The Terraform-based templates can be found in this [GitHub repository](https://github.com/IBM-Cloud/hpc-cluster-lsf).





 Where can I find the custom image name to image ID mappings for each cloud region? 

The mappings can be found in the image-map.tf file in this [GitHub repository](https://github.com/IBM-Cloud/hpc-cluster-lsf).





 Which Spectrum LSF and Spectrum Scale versions are used in cluster nodes deployed with this offering? 

Cluster nodes that are deployed with this offering include IBM Spectrum LSF 10.1 Standard Edition plus Data Manager plus License Scheduler. See the following for a brief description of each of those programs: [IBM Spectrum LSF 10 family of products](https://www.ibm.com/common/ssi/ShowDoc.wss?docURL=/common/ssi/rep_ca/4/897/ENUS220-174/index.html&lang=en&request_locale=en)
* Virtual server image for VPC: Select an image from the list of available images, or import a new image to onboard it.



A virtual server image for VPC can only be added to one product within one private catalog at a time. If the virtual server image you want to import is already imported into another product, you must remove the image from that product or delete the product before you add the virtual server image to a new product.
5. If applicable, enter the version of the software in the format of major version, minor version, and revision. For example, enter version 1.1.2.
6. Select a catalog category for the product. Categories are used to organize products in the IBM Cloud catalog based on function, use, or common solutions.
7. Click Add product.







 Adding catalog entry details 

When you publish your product to the catalog for users with access to your private catalog, they see a tile with the product name and other details that add during onboarding. In addition to the category that you set when you import your software, you can add other filters that are related to industry, compliance, technologies it works with, and more. Each of these filters is used in the catalog for users to find software that fits their needs. In the catalog entry details section, you can also evaluate and make updates to the short descriptions, documentation URL, and even keywords to help user search and find your product quickly.



1. From the Catalog entry details section, click the Edit icon ![Edit icon](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/icons/edit-tagging.svg).
2. Review the information that was imported with your product, and make edits as needed.
3. Review the filters and industry options to select catalog filters that apply. You can select up to five industry filters.
4. Check your catalog entry preview to see how your catalog tile displays to users who are evaluating your software in the catalog.
5. Click Save when you're happy with your changes.
The value for this parameter can be different than the one used for the second entry in the Parameters with default values section in the catalog. The second entry applies to the resource group where VPC resources are provisioned. As specified in the description for this second resource_group parameter, note that only the default resource group is supported for use of the Symphony Host Factory auto-scaling feature.
* Can I use the Spectrum Symphony Host Factory feature for auto scaling on any cluster deployed with this offering?

No, the use of Host Factory to provision and delete compute nodes is not supported in the following cases:



* Provisioning and deleting compute nodes on dedicated hosts. Only static compute nodes can be deployed on dedicated hosts.
* When using Spectrum Scale for shared storage in the cluster.



* Where can I find the custom image name to image ID mappings for each cloud region?

The mappings can be found in the image-map.tf file and the scale-image-map.tf file in this public [GitHub repository](https://github.com/IBM-Cloud/hpc-cluster-symphony).
* Why does the egosh command not work if tried immediately after Schematics provisions the cluster?

This is expected behavior. Even after the Schematics web console shows that the cluster is successfully provisioned, there are still some tasks that run in the background for several minutes. Allow a few minutes (typically 2 minutes is sufficient) after the cluster gets provisioned for egosh to be available.
* Why does cluster creation using dedicated hosts fail sometimes with the error status of dedicated host is failed?

In some regions, dedicated hosts have a limitation on the number of virtual server instances that can be placed on them at one time. You can try to provision the cluster with a smaller number of virtual server instances to overcome this.
* Why does Spectrum Scale not allow use of the default value of 0.0.0.0/0 for security group creation?

For security reasons, Spectrum Scale does not allow you to provide a default value that would allow network traffice from any external device.
Why does my VPN client hang when I initiate a VPN session? 

The VPN server runs on the protocol and port that is specified when the server is provisioned. If a firewall is blocking traffic from your VPN client to the VPN server, your network administrator must open the protocol and port. For example, if your internet service provider (ISP) is blocking traffic, you can ask your VPN server administrator to change the protocol and port to an unblocked protocol and port. Typically, the TCP 443 port is not blocked by ISPs. Another root cause of a client not connecting to the VPN server is that the client certificate expired.

  What’s happening 

The VPN client logs the following error, TLS Error: TLS key negotiation failed to occur within 60 seconds (check your network connectivity).

  Why it’s happening 

The VPN server protocol traffic is blocked by a firewall, or your VPN client certificate expired.

  How to fix it 

Follow these steps to resolve this issue:



1.  Check that the security group that is attached to the VPN server allows VPN server protocol traffic.
2.  Check that the ACL on the subnet of the VPN server allows VPN server protocol traffic.
3.  Check with your ISP to allow VPN server protocol traffic.
4.  Check the client certificate expiration date. On Linux, you can run the following command to see the expiration date:

openssl x509 -enddate -noout -in client.crt
However, you must first create a service-to-service policy to globalcatalog-collection.instance.retrieve before you can create the instance group. For more information, see [Using a custom image in a private catalog with an instance group](https://cloud.ibm.com/docs/vpc?topic=vpc-private-catalog-image-instance-group&interface=ui).
* Can I change the boot volume associated with my resource group after creating the resource group?

No. The resource group of a volume is set at resource creation and cannot be changed. This behavior is shared by all VPC resources.
* Can I move my volume to another region or zone?

No, a volume is restricted to the zone it was created in. However, you can move the volume's data by creating a new snapshot from the volume, and creating a new volume from that snapshot in a different zone.
* Can I assign my instance to more than one placement group?

No, an instance can be assigned to only one placement group.
* What is the maximum number of instances that I can have per placement group?

If you are using the host spread placement strategy, you can have a maximum of 12 instances per placement group. If you are using the power spread placement strategy, you can have a maximum of four instances per placement group.

If more instances are needed, you can request a quota increase through IBM [customer support](https://cloud.ibm.com/docs/get-support?topic=get-support-using-avatar).
* Can I move an instance from one placement group to another?

No, the placement group strategy can't be modified after the placement group is created. Also, to remove an instance from a placement group, the instance must be deleted first.
* Can I use an instance that has placement group strategy within an instance group?

Yes, you can use instances that are provisioned with a placement group strategy within an instance group. The instance template includes the placement group attribute. Any instances that are started within an instance group that has a specified placement group is placed according to the placement group strategy. Placement groups allow instances from multiple zones to allow instance groups to support instances with subnets that span multiple zones.
Managing credentials 



  Generating credentials 



1.  Log in to your IBM Cloud account.
2.  Go to Resource list > Services and Software > Databases.
3.  Click on your Netezza Performance Server instance.
You are now on the Service instance details page where you can find information about endpoints for accessing the web console, the API server, and the database.
4.  Go to the Service Credentials tab.
5.  Click New Credentials.



1.  Type a name to assing to your credentials.
2.  Select the IAM role that was assigned to you to manage the instance.
3.  Click Add.





If your credentials were generated successfully, you can expand the newly created credential entry to view them.





  Viewing credentials 



1.  Log in to your IBM Cloud account.
2.  Go to Resource list > Services and Software > Databases.
3.  Click on your Netezza Performance Server instance.
You are now on the Service instance details page where you can find information about endpoints for accessing the web console, the API server, and the database.
4.  Go to the Service Credentials tab.
5.  Expand View credentials.
6.  Expand your credential entry. The following credentials are displayed:



*  username: admin - Specifies a local database admin user that was created for you to access the instance.
*  password: xxxx - Specifies the password that you must use when logging in to your instance as admin.
If the backup agent appears as unconfigured in the WebCC or Portal, confirm that you set up the backup job for your server as it is described in [Configuring simple file-level backups](https://cloud.ibm.com/docs/Backup?topic=Backup-configureFileBackup).
* I made a mistake in the agent installation process. How can I remove the Backup Agent from the server?

You can remove the backup agent either through the command line on a Linux server or through the Control Panel of a Windows® server. For more information, see the following topics.



* [Uninstalling the Backup Agent from a Windows® Server](https://cloud.ibm.com/docs/Backup?topic=Backup-cancelBackupuninstallbackupagentWin)
* [Uninstalling the Backup Agent from a Linux® Server](https://cloud.ibm.com/docs/Backup?topic=Backup-cancelBackupuninstallbackupagentLin)



* Can I back up NFS File Shares?

Yes. First, add the Linux® system in the Backup Portal. Then, you can create a backup job for files and folders that are saved on the NFS shares that are attached to this server. The backup job specifies which folders and files to back up, and where to save the data. For more information, see [Adding an NFS backup job](https://onlinehelp.evault.com/HelpFiles/LinuxAgent/10676.htm?TocPath=Server%2520Backup%2520User%2520Guide%257CAdd%2520and%2520edit%2520backup%2520jobs%257C_____10).

NFS Backups are not supported in Windows.
* Can I see what is backed up and sent to the vault when my agent is offline?

Yes. Backup job results can be obtained from the /opt/BUAgent/xlogcat utility.

First, go to the directory of the Backup Agent.

cd /opt/BUAgent
If the backup agent appears as unconfigured in the WebCC or Portal, confirm that you set up the backup job for your server as it is described in [Configuring simple file-level backups](https://cloud.ibm.com/docs/Backup?topic=Backup-configureFileBackup).





 I made a mistake in the agent installation process. How can I remove the Backup Agent from the server? 

You can remove the backup agent either through the command line on a Linux server or through the Control Panel of a Windows® server. For more information, see the following topics.



* [Uninstalling the Backup Agent from a Windows® Server](https://cloud.ibm.com/docs/Backup?topic=Backup-cancelBackupuninstallbackupagentWin)
* [Uninstalling the Backup Agent from a Linux® Server](https://cloud.ibm.com/docs/Backup?topic=Backup-cancelBackupuninstallbackupagentLin)







 Can I back up NFS File Shares? 

Yes. First, add the Linux® system in the Backup Portal. Then, you can create a backup job for files and folders that are saved on the NFS shares that are attached to this server. The backup job specifies which folders and files to back up, and where to save the data. For more information, see [Adding an NFS backup job](https://onlinehelp.evault.com/HelpFiles/LinuxAgent/10676.htm?TocPath=Server%2520Backup%2520User%2520Guide%257CAdd%2520and%2520edit%2520backup%2520jobs%257C_____10).

NFS Backups are not supported in Windows.





 Can I see what is backed up and sent to the vault when my agent is offline? 

Yes. Backup job results can be obtained from the /opt/BUAgent/xlogcat utility.

First, go to the directory of the Backup Agent.

cd /opt/BUAgent

Then, use the following syntax to show all backup job results.
The bootstrap.ign file needs to be copied to the document root of NGINX. The bootstrap ignition file must be hosted on the web server so the bootstrap node can reach it on the first start. The Ignition file is too large to fit in a vApp property.

Copy the bootstrap.ign file to the document root of NGINX.

cp bootstrap.ign /usr/share/nginx/html





 Terraform files 

You must update the following Terraform files.



* ignition.tf - This file needs to be updated so that the DNS entry matches the deployment.
* terraform.tfvars - This file needs to be created and holds the variables that are used by the main.tf file
* main.tf - This file needs to be updated to remove the DNS section.





 ignition.tf - Updating the DNS entry in the template 

The DNS IP details are hardcoded within the Terraform template. You must change this IP to be the vCenter Server instance AD DNS server.



Table 2. File parameters for ignition.tf

 Parameter Example Your deployment 

 DNS1 10.187.214.66 





1. In the SSH session to the bastion node, with root privileges, use the following command to open the file: vi /opt/ocpinstall/installer/upi/vsphere/machine/ignition.tf
2. Type i to enter insert mode, and then scroll down to the DNS1 entry.
3. Update the IP address from 8.8.8.8 to match the deployment.
4. Press Esc, then type :wq to save the file and exit the vi editor.



The file is similar to the following example:

locals {
mask = "${element(split("/", var.machine_cidr), 1)}"
gw = "${cidrhost(var.machine_cidr,1)}"

ignition_encoded = "data:text/plain;charset=utf-8;base64,${base64encode(var.ignition)}"
Troubleshooting AIX-related issues 

Learn how to troubleshoot Power® Systems Virtual Server AIX-related issues.



 What can I do if my AIX virtual machine (VM) does not initially boot? 

Symptoms: The AIX boot disk that you are using to provision an AIX VM is not successfully booting. As a result, the console displays a blank screen without standard debugging options.

Causes: The AIX boot disk might be corrupted.

Resolve: If the AIX VM does not boot, you must provision an additional AIX VM and use it as a Network Installation Management (NIM) server. Without a NIM server, you cannot debug the boot issue and must reimage your disk.



1. Determine the hostname and IP address of the system by using the following two commands, hostname and ifconfig -a.

Zoom

![Determining your hostname and IP address](https://cloud.ibm.com/docs-content/v1/content/1d36273917990fbf48078805e201d2e85e2fcb27/power-iaas/images/terminal-aix-hostname.png)

Figure 1. Determining your hostname and IP address
2. Using the information from the previous step, add an entry for your hostname and IP address into /etc/hosts. For example, echo "192.168.0.15 aix-7100-05-04" >> /etc/hosts.
3. Run the following command, nim_master_setup -a device=/usr/sys/inst.images -a mk_resource=no.

Zoom

![Creating a NIM master](https://cloud.ibm.com/docs-content/v1/content/1d36273917990fbf48078805e201d2e85e2fcb27/power-iaas/images/terminal-aix-nim.png)

Figure 2. Creating a NIM master
4. Once completed, the NIM master file set has been installed and the basic resource objects created.
The IBM Cloud command line interface can be used to list, create, or delete your Hyper Protect Virtual Servers instances.





 24 March 2020 

A virtual server now has a seven day reclamation period after you "delete" it from the resource list. During the reclamation period you can restore the virtual server or manually trigger a deletion via resource reclamations.





 27 February 2020 

A new pricing plan is available: Entry.





 30 January 2020 

Three new data centers are available for creating virtual servers: Frankfurt 02, Frankfurt 04, and Frankfurt 05.





 19 December 2019 

Instances of the "Free" plan can now be provisioned in Dallas 10 and Dallas 12.





 17 December 2019 

The provided Ubuntu operating system is now partwisely hardened according to CIS Ubuntu Linux 18.04 LTS Benchmark, Level 1 - Server profile. This operating system update will only be provided to new instances.





 12 December 2019 

The service offering moved from the Beta to the GA phase. Additionally, new pricing plans are available: Medium and Small.





 6 December 2019 

Three new data centers are available for creating virtual servers: Sydney 01, Sydney 04, and Sydney 05.





 12 November 2019 

You can now order virtual servers in different data centers: Dallas 10, Dallas 12, and Dallas 13.





 21 October 2019 

Your virtual server instances are now isolated in one virtual LAN (VLAN) per account and region.





 30 August 2019 

The service offering moved from the Experimental to the Beta phase.





 16 August 2019 

A new and extended version of the documentation is available.





 12 February 2019 

The Experimental version of Hyper Protect Virtual Servers is released. You can now access the Hyper Protect Virtual Servers service in the IBM Cloud Catalog under the Compute category.