vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* For more information about support tickets, see [IBM Support Guide](https://www-01.ibm.com/support/docview.wss?uid=ibm10733923) and follow the steps in [Contacting IBM Support](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-trbl_support).









 Client responsibilities 



* While we commend clients taking steps to make their environments more secure, it should be noted that some practices might have adverse effects on the effectiveness of VMware Solutions.
* Clients are accountable for the firewalls they create and the resulting limitations that are imposed on communications between the VMware Solutions components. These firewalls might also hinder the ability of IBM Support to access client instances and resolve issues. For more information about minimum recommended firewall configuration, see [Ports that are used by VMware Solutions](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vmwaresol_ports-vmwareuses).
* Clients are fully responsible for encrypting the data in their system.
* Upon initial deployment, the offering’s automation and client’s account are separate. The client is allowed and encouraged to change all passwords that IBM provides in the console.
* vCenter access and credentials are created during initial deployments and provided to the client. As part of the requirement of our offering, IBM Support must retain full access to the management layer to provide life–cycle management and support to our clients.
* For more information about the credentials that are used by IBM automation and IBM Support, see [IBM user IDs](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-audit_user_ids). By leaving these credentials active, you are granting IBM permission to access the environment for satisfying provisioning requests or providing support as outlined here. You can revoke these credentials to prevent IBM access to the environment. If IBM later needs to satisfy a provisioning request or provide support, you are required to provide updated credentials to IBM Support.
You can move an account by calling the Enterprise Management API as shown in the following sample request. Replace the IAM token and ID variables with the values from your enterprise.



* Curl
* Java
* Python
* Go
* Node



curl -X PATCH "https://enterprise.cloud.ibm.com/v1/accounts/$ACCOUNT_ID"
-H "Authorization: Bearer <IAM_Token>"
-H 'Content-Type: application/json'
-d '{
"parent": crn:v1:bluemix:public:enterprise::a/$ENTERPRISE_ACCOUNT_ID::account-group:$NEW_PARENT_ACCOUNT_GROUP"",
}'

UpdateAccountOptions updateAccountOptions = new UpdateAccountOptions.Builder()
.accountId(accountId)
.parent(newParentCRN)
.build();

Response<Void> response = service.updateAccount(updateAccountOptions).execute();

response = enterprise_management_service.update_account(
account_id=account_id,
parent=new_parent_crn,
)

updateAccountOptions := enterpriseManagementService.NewUpdateAccountOptions(
accountID,
newParentCRN,
)

response, err := enterpriseManagementService.UpdateAccount(updateAccountOptions)
if err != nil {
panic(err)
}

const params = {
accountId: accountId,
parent: newParentCrn,
};

enterpriseManagementService.updateAccount(params)
.then(res => {
done();
})
.catch(err => {
console.warn(err)
});

For detailed information about the API, see [Enterprise Management API](https://cloud.ibm.com/apidocs/enterprise-apis/enterprise).
Legacy account-based MFA was available to accounts with classic infrastructure prior to the release of ID-based MFA. This legacy offering continues to work for accounts with classic infrastructure and requires the user to provide a secondary authentication input when logging in or switching to accounts with classic infrastructure. Non-classic resources are not secured by this legacy offering. ID-based MFA is for customers that want to implement MFA to secure the full range of IBM Cloud offerings.



 ID-based MFA options 

As an Administrator on the IAM Identity Service or All IAM Account Management services, you can enable ID-based MFA for the account or a specific user, and it applies to all account resources.



* You can update the MFA setting for your account by going to Manage > Access (IAM) > Settings > Authentication in the IBM Cloud® console. For more information, see [Enabling MFA for an account](https://cloud.ibm.com/docs/account?topic=account-enablemfaenabling-account).
* You can update the MFA setting for a specific user in your account by going to Manage > Access (IAM) > Users and clicking the user whose MFA you want to update. If you are a new user, use the ID-based MFA option to ensure that your login is secure. For more information, see [Enabling MFA for an individual user](https://cloud.ibm.com/docs/account?topic=account-enablemfaenabling-user).





 None 

All users log in by using only a standard ID and password, which offers the lowest level of security. To increase the level of security for this option, you can disable logging in to the CLI with only a username and password. This way, you require an API key to log in to the CLI or users can log in with --sso.

Starting 3 May 2023, by default CLI logins with only a username and password are disabled for all users that have MFA set to None. This applies to users in new and existing accounts. Administrators can opt-out before that date in the IBM Cloud console.
IBM Cloud Framework for Financial Services 

IBM Cloud Framework for Financial Services is designed to build trust and enable a transparent public cloud ecosystem with the specific features for security, compliance, and resiliency that financial institutions require. The IBM Cloud Framework for Financial Services is a standard set of controls, controls guidance, and architectures informed by global regulatory requirements for cybersecurity, data security, and risk management, with ongoing governance by an industry council and promontory to ensure currency with new and changed regulations.

IBM Cloud Framework for Financial Services currently applies controls (US NIST 800-53 with IBM financial services guidance) to IBM Cloud services, IBM software, and third-party ISV and SaaS providers that provide a common control approach that can be mapped to regulatory guidelines worldwide. This solution platform and ecosystem program is built on an industry-informed framework of controls, architectures, and operations that mitigates systemic risk in using the IBM public cloud for mission-critical workloads with client-sensitive data. For more informations, see [What is IBM Cloud for Financial Services?](https://cloud.ibm.com/docs/overview?topic=overview-what-is-fscloud) and how to [enable your account to use Financial Services Validated products](https://cloud.ibm.com/docs/account?topic=account-enabling-fs-validated).





 EU support for your account 

You can add an extra layer of protection to your data in the European Union. Turning on EU support for your account ensures that any support ticket that you create is sent to IBM support teams in Europe. An EU supported account is useful if, for example, you use resources to process personal data for European citizens. For more information, see [Enabling EU support for your account](https://cloud.ibm.com/docs/account?topic=account-eu-supported).





 HIPAA support for your account 

The US Health Insurance Portability and Accountability Act (HIPAA) and the Health Information Technology for Economic and Clinical Health (HITECH) Act define standards for handling electronic healthcare transactions and information. If you or your company is a covered entity as defined by HIPAA, you must enable the HIPAA Supported setting if you run sensitive workloads that are regulated under HIPAA and the HITECH Act.
* grant_type: urn:ibm:params:oauth:grant-type:passcode
* response_type: cloud_iam uaa
* passcode: Your IBM Cloud passcode.
* uaa_client_ID: cf
* uaa_client_secret:
* bss_account: The IBM Cloud account ID that you retrieved in the previous step. Add the uaa_client_secret key with no value specified.

<-- </ul> -->

The following example shows output for the API request.

{
"access_token": "<iam_token>",
"refresh_token": "<iam_refresh_token>",
"token_type": "Bearer",
"expires_in": 3600,
"expiration": 1493747503
}

You can find the IBM Cloud IAM token in the access_token and the refresh token in the refresh_token field of your API output.
4. List all classic or VPC clusters in your account. Example request to list Classic clusters.
 {: codeblock}
GET https://containers.cloud.ibm.com/global/v2/classic/getClusters

Header
: Authorization: bearer <iam_token>

Example command to list VPC clusters.

 {: codeblock}
GET https://containers.cloud.ibm.com/global/v2/vpc/getClusters?provider=vpc-gen2

Header
: Authorization: Your IBM Cloud IAM access token (bearer <iam_token>).
5. Review the Red Hat OpenShift on IBM Cloud API documentation]https_containers.cloud.ibm.com_global_swagger-global-api] ! ! ! ! to find a list of supported APIs.<-- </ol> -->When you use the API for automation, be sure to rely on the responses from the API, not files within those responses.
For more information, see the IAM roles and actions for the [IBM Cloud Shell](https://cloud.ibm.com/docs/account?topic=account-account-servicesaccount-management-actions-roles) account management service.





 Enabling or disabling Cloud Shell for an account 

By default, Cloud Shell is enabled for an account. As an account owner or user with the correct access, you can enable or disable Cloud Shell for users in the account.

When the Cloud Shell availability setting is enabled, Cloud Shell is available to all users in the account. If the setting is disabled, no users in the account can access Cloud Shell. The IBM Cloud Shell icon ![IBM Cloud Shell icon](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/icons/terminal-cloud-shell.svg) is disabled in the IBM Cloud console.

To enable or disable Cloud Shell for the account, complete the following steps:



1. In the IBM Cloud console, go to Manage > Account, and select IBM Cloud Shell settings.
2. Select the Enabled or Disabled toggle, and then click Save changes.







 Enabling or disabling Cloud Shell locations for an account 

By default, all locations for the account are enabled, and the nearest available location is selected. Users are routed to the nearest available location, such as Dallas (us-south), Frankfurt (eu-de), or Tokyo (jp-tok).

As an account owner or user with the correct access, you can select whether Cloud Shell is enabled only in specific locations for the account. To select Cloud Shell locations for the account, complete the following steps:



1. In the IBM Cloud console, go to Manage > Account, and select IBM Cloud Shell settings.
2. Ensure that Cloud Shell Availability is enabled.
3. Select the toggle for each location that you want to enable or disable for the account.
4. Optional: Select Enable new locations by default to automatically enable new locations when they are available.
Enable [VRF](https://cloud.ibm.com/docs/account?topic=account-vrf-service-endpointvrf) in your IBM Cloud infrastructure account. To check whether a VRF is already enabled, use the ibmcloud account show command.
2. [Enable your IBM Cloud account to use service endpoints](https://cloud.ibm.com/docs/account?topic=account-vrf-service-endpointservice-endpoint).
3. Enable the private cloud service endpoint.

ibmcloud ks cluster master private-service-endpoint enable --cluster <cluster_name_or_ID>
4. Refresh the Kubernetes master API server to use the private cloud service endpoint by following the CLI prompt or by manually running the following command. It might take several minutes for the master to refresh.

ibmcloud ks cluster master refresh --cluster <cluster_name_or_ID>
5. [Create a ConfigMap](https://cloud.ibm.com/docs/containers?topic=containers-updateworker-up-configmap) to control the maximum number of worker nodes that can be unavailable at a time in your cluster. When you update your worker nodes, the ConfigMap helps prevent downtime for your apps as the apps are rescheduled orderly onto available worker nodes.
6. Update all the worker nodes in your cluster to pick up the private cloud service endpoint configuration.

By issuing the update command, the worker nodes are reloaded to pick up the service endpoint configuration. If no worker update is available, you must [reload the worker nodes manually](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-cli). If you reload, be sure to cordon, drain, and manage the order to control the maximum number of worker nodes that are unavailable at a time.

ibmcloud ks worker update --cluster <cluster_name_or_ID> --worker <worker1,worker2>
7. Optional: To use the private cloud service endpoint only,
After your support case is created, you can follow its progress on the [Manage cases](https://cloud.ibm.com/unifiedsupport/cases/manage) page. For more information about creating a case, see [Creating support cases](https://cloud.ibm.com/docs/get-support?topic=get-support-open-case).





 What are my options for contacting IBM Cloud Support? 

From the IBM Cloud console menu bar, click the Help icon ![Help icon](https://cloud.ibm.com/docs-content/v1/content/9147bc2ffd9bafd03e4559b378e714fac17a4977/icons/help.svg) > Support center. The options that are available to you depend on your support plan. For more information, see [Getting support](https://cloud.ibm.com/docs/get-support?topic=get-support-support-plans).

To contact support, you can use the following methods:



* If you have a valid Pay-As-You-Go or Subscription account, you can click Chat with IBM to connect with a support engineer.
* Pay-as-you-go or subscription accounts can also contact support by phone and can find the number in the [Support Center](https://cloud.ibm.com/unifiedsupport/supportcenter).
* Lite and Trial account support is limited to non-technical support issues that are related to account access and billing. Users with Lite or Trial accounts can view the [IBM Cloud documentation](https://cloud.ibm.com/docs/get-support?topic=get-support-using-avatar), Chat with Watson, and use [Stack Overflow](https://stackoverflow.com/questions/tagged/ibm-cloud).







 How do I escalate support cases? 

As an IBM Cloud customer, you can escalate support cases to surface critical issues. After a case is escalated, the IBM Cloud Support team reviews the information and responds with updates.
For more information, see the IAM roles and actions for the [IBM Cloud Shell](https://cloud.ibm.com/docs/account?topic=account-account-servicesaccount-management-actions-roles) account management service.





 Enabling or disabling Cloud Shell for an account 

By default, Cloud Shell is enabled for an account. As an account owner or user with the correct access, you can enable or disable Cloud Shell for users in the account.

When the Cloud Shell availability setting is enabled, Cloud Shell is available to all users in the account. If the setting is disabled, no users in the account can access Cloud Shell. The IBM Cloud Shell icon ![IBM Cloud Shell icon](https://cloud.ibm.com/docs-content/v1/content/6e73868222d2673c4d974c1cf0452448e1b38054/cloud-shell/includes/icons/terminal-cloud-shell.svg) is disabled in the IBM Cloud console.

To enable or disable Cloud Shell for the account, complete the following steps:



1. In the IBM Cloud console, go to Manage > Account, and select IBM Cloud Shell settings.
2. Select the Enabled or Disabled toggle, and then click Save changes.







 Enabling or disabling Cloud Shell locations for an account 

By default, all locations for the account are enabled, and the nearest available location is selected. Users are routed to the nearest available location, such as Dallas (us-south), Frankfurt (eu-de), or Tokyo (jp-tok).

As an account owner or user with the correct access, you can select whether Cloud Shell is enabled only in specific locations for the account. To select Cloud Shell locations for the account, complete the following steps:



1. In the IBM Cloud console, go to Manage > Account, and select IBM Cloud Shell settings.
2. Ensure that Cloud Shell Availability is enabled.
3. Select the toggle for each location that you want to enable or disable for the account.
4. Optional: Select Enable new locations by default to automatically enable new locations when they are available.
Getting help and support 

If you have problems or questions when you are using the IBM® Spectrum Scale offering on IBM Cloud®, you can use the following options:



*  You can call IBM Cloud Support. For a list of country-based numbers, see [https://www.ibm.com/planetwide](https://www.ibm.com/planetwide).
*  Open a support case by using the [Support Center](https://cloud.ibm.com/unifiedsupport/supportcenter).
* If some users in the account use a multifactor authentication (MFA) like [TOTP](https://cloud.ibm.com/docs/account?topic=account-totp), make sure that you [enable MFA](https://cloud.ibm.com/docs/account?topic=account-enablemfa) for all users in the IBM Cloud account.



Enabling MFA at the user level is not supported. If MFA is enabled for some users but is not enabled for all users at the account level, authentication errors might occur.





 Step 2: Check the public gateway 



* For VPC clusters with public and private cloud service endpoints enabled:

Check that a public gateway is enabled on each VPC subnet that your cluster is attached to. Public gateway are required for default components such as the web console and OperatorHub to use a secure, public connection to complete actions such as pulling images from remote, private registries.



1. Use the IBM Cloud console or CLI to [ensure that a public gateway is enabled on each subnet](https://cloud.ibm.com/docs/openshift?topic=openshift-vpc-subnetscreate_vpc_subnet) that your cluster is attached to.
2. Restart the components for the Developer catalog in the web console.



1. Edit the ConfigMap for the samples operator.

oc edit configs.samples.operator.openshift.io/cluster





2. Change the value of managementState from Removed to Managed. 3. Save and close the config map. Your changes are automatically applied.
* For Classic clusters with both public and private cloud service endpoints enabled:

Check that your cluster has public connectivity so that the networking components can talk to the master as they deploy.



1. Check the Master Status. If the Master Status is not Ready, [review its status](https://cloud.ibm.com/docs/openshift?topic=openshift-debug_master) and follow any troubleshooting information to resolve the issue.

ibmcloud oc cluster get -c <cluster_name_or_ID>
Enterprises offer significant advantages in your ability to scale your environment over time as described in [Enterprise account architecture](https://cloud.ibm.com/docs/enterprise-account-architecture?topic=enterprise-account-architecture-about).
4. Enable [multi-factor authentication (MFA)](https://cloud.ibm.com/docs/account?topic=account-enablemfa) by using the U2F MFA type for all users in your account. Users authenticate by using a physical hardware-based security key that generates a six-digit numerical code. Based on the FIDO U2F standard, this method offers the highest level of security. This security is needed because the IBM Cloud Framework for Financial Services requires a smart card or hardware token that is designed and operated to FIPS 140-2 level 2 or higher or equivalent (for example, ANSI X9.24 or ISO 13491-1:2007).

The following table shows the controls that are most related to this step.



Table 3. Related controls in IBM Cloud Framework for Financial Services for multi-factor authentication

 Family Control 

 Identification and Authentication (IA) [IA-2 (1) Identification and Authentication (Organizational Users) | Multi-factor Authentication To Privileged Accounts](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-ia-2.1) <br>[IA-2 (11) Identification and Authentication (Organizational Users) | Remote Access - Separate Device](https://cloud.ibm.com/docs/framework-financial-services-controls?topic=framework-financial-services-controls-ia-2.11) 



5. Restrict IP addresses from which a user can access the IBM Cloud account. For more information, see [Allowing specific IP addresses for an account](https://cloud.ibm.com/docs/account?topic=account-ipsips_account) for more information.

The following table shows the controls that are most related to this step.



Table 4. Related controls in IBM Cloud Framework for Financial Services for restricting IP addresses

 Family Control
You're given your API Key when you enable IAM. It is critical that you save the API Key. The value is not shown again. If you lose your API Key, you can delete the key and create a new one. For more information, see [Managing service ID API keys](https://cloud.ibm.com/docs/account?topic=account-serviceidapikeys).
* What is the Startup with IBM Program?

The [Startup with IBM Program](https://developer.ibm.com/startups/), formerly the IBM Global Entrepreneur Program (GEP), is an IBM corporate program helps you startup or scale up your business with or without funding. Acceptance decisions, length of participation, awarding of credits, and any possible extensions are made by the Startup with IBM Team and not IBM Cloud Support.

If your application to the program is approved, awarded credits are referred to as the Technology Incubator Program on an IBM Cloud Invoice. For more information about the program and its credits, see [Startup with IBM FAQs](https://developer.ibm.com/startups/faq).
* What is IBM PartnerWorld?

[IBM PartnerWorld Program](https://www.ibm.com/partnerworld/resources) is an IBM corporate program that provides access to the IBM product portfolio including the IBM Cloud Platform. Acceptance decisions, length of participation, awarding of credits, and any possible extensions are made by the IBM PartnerWorld Team and not IBM Cloud Support.

For more information about the program, contact the [IBM PartnerWorld Team](https://www.ibm.com/partnerworld/resources/support).
* What types of software can I add to the IBM Cloud catalog?

See the following list for the types of third-party software that you can currently add to the catalog:



* Helm charts on Kubernetes and Red Hat OpenShift on IBM Cloud clusters
* Terraform templates
* OVA images deployed on VMware Solutions Dedicated - vCenter Server
* Virtual server images with Terraform deployed on VPC infrastructure or Power Systems Virtual Server
* Operators with a TGZ file from GitHub or GitLab repositories