vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Support 

Support for MAS Dedicated can be obtained by submitting a support case through the [IBM support portal](https://www.ibm.com/mysupport). You must have an [IBMid](https://myibm.ibm.com) and be [registered for support](https://cloud.ibm.com/docs/mas-ms?topic=mas-ms-getting-started-with-ibm-maximo-application-suite-dedicatedhow-to-register-for-mas-support) before you can [create a case](https://cloud.ibm.com/docs/mas-ms?topic=mas-ms-getting-started-with-ibm-maximo-application-suite-dedicatedhow-to-create-a-case). Cases are reviewed based on the severity level assigned. Please see table below for further details.



Table 1. IBM Support Case Severity Levels and Response Time

 Case Severity Level Description Response Time Objective Response Time Coverage 

 1 Critical Business Impact/Service Down: Business critical functionality is inoperable or critical interface has failed. This should be used for Production environments only and indicates an inability to access services resulting in a critical impact on operations. Within 1 hour 24x7 
 2 Significant business impact: A service, business feature, or function of the service is severely restricted in its use, or you are in jeopardy of missing business deadlines. Within 2 business hours Monday – Friday business hours 
 3 Minor business impact: The service or functionality is usable and the issue does not represent a critical impact on operations. Within 4 business hours Monday – Friday business hours 
 4 Minimal business impact: An inquiry or non-technical request. Within 1 business day Monday – Friday business hours 



Response Time Objective describes IBM's goals only and do not represent a guarantee of performance.

Business Hours reflect normal country business hours in your time zone. For example, 8:00 AM to 5:00 PM in North America or 9:00 AM to 6:00 PM in some parts of Asia and Europe, Monday through Friday, excluding weekends and national or statutory holidays.
Message: The IKE policy <ike_policy_id> could not be created.

Try again in a few minutes. If this problem persists, [contact support](https://cloud.ibm.com/docs/vpc-on-classic?topic=vpc-on-classic-getting-help-and-support).





 ike_policy_not_deleted 

Message: The IKE policy <ike_policy_id> could not be deleted.

Try again in a few minutes. If this problem persists, [contact support](https://cloud.ibm.com/docs/vpc-on-classic?topic=vpc-on-classic-getting-help-and-support).





 ike_policy_not_found 

Message: The IKE policy <ike_policy_id> could not be found.

You referenced an IKE policy that does not exist. Review your request to ensure that you specified the proper IKE policy ID. Try again in a few minutes. If this problem persists, [contact support](https://cloud.ibm.com/docs/vpc-on-classic?topic=vpc-on-classic-getting-help-and-support).





 ike_policy_not_updated 

Message: The IKE policy <ike_policy_id> could not be updated.

Try again in a few minutes. If this problem persists, [contact support](https://cloud.ibm.com/docs/vpc-on-classic?topic=vpc-on-classic-getting-help-and-support).





 instance_delete_conflict 

Message: The instance cannot be deleted in the current status.

You cannot delete an instance when it is in deleting, pending, starting, stopping, or restarting status. The instance must be in running or stopped status. If the status does not change, [contact support](https://cloud.ibm.com/docs/vpc-on-classic?topic=vpc-on-classic-getting-help-and-support).





 instance_invalid_hostname 

Message: The instance cannot be created because the hostname is not valid.
* [Is the service highly available?](https://cloud.ibm.com/docs/openshift?topic=openshift-faqsha_sla)
* [What compliance standards does the service meet?](https://cloud.ibm.com/docs/openshift?topic=openshift-faqsstandards)
* [Can I use IBM Cloud and other services with my cluster?](https://cloud.ibm.com/docs/openshift?topic=openshift-faqsfaq_integrations)
* [Does IBM support third-party and open source tools that I use with my cluster?](https://cloud.ibm.com/docs/openshift?topic=openshift-faqsfaq_thirdparty_oss)
* [What am I charged for? Can I estimate and control costs in my cluster?](https://cloud.ibm.com/docs/openshift?topic=openshift-faqscharges)
* [Can I downgrade my cluster to a previous version?](https://cloud.ibm.com/docs/openshift?topic=openshift-faqsdowngrade)







 Troubleshooting 

[Getting help and support for Red Hat OpenShift on IBM Cloud](https://cloud.ibm.com/docs/openshift?topic=openshift-get-helpget-help)



* [General ways to resolve cluster issues](https://cloud.ibm.com/docs/openshift?topic=openshift-get-helphelp-general)
* [Reviewing issues and status](https://cloud.ibm.com/docs/openshift?topic=openshift-get-helphelp-cloud-status)
* [Feedback and questions](https://cloud.ibm.com/docs/openshift?topic=openshift-get-helpfeedback-qs)
You can access the Status page directly at [IBM Cloud - Status](https://cloud.ibm.com/status) to view the status of resources in all IBM Cloud locations. You can filter the list by selecting specific components and locations (for example, you can select Virtual Servers and view the network connectivity).





 How do I request a compliance report? 

For information about viewing or requesting compliance information and SOC reports, see [Understanding IBM Cloud compliance](https://cloud.ibm.com/docs/overview?topic=overview-compliance).





 How long does it take for maintenance to complete? 

The maintenance notification contains an estimated duration for the maintenance window. Keep in mind that the time frame is an estimate and maintenance tasks might take longer. Make sure that you allow an extra hour past the maintenance window for tasks to complete and for the server to return online. If the server remains offline longer than 2 hours past the estimate, contact [support](https://test.cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-gettinghelp).





 Why do I need to migrate my virtual server? 

Migrations happen for several reasons. The most common reasons are because of host failure and planned migrations due to maintenance.





 What happens if I don't perform a manual migrate for maintenance reasons? 

Sometimes you need to perform a public host migration for maintenance reasons. If you don't perform this manual migration within the allotted time, the migration happens automatically.





 Why can't I migrate my virtual server? 

You can migrate only private, dedicated hosts. For more information about migrating private, dedicated hosts, see [Migrating a dedicated host instance to another host](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-migrating-dedicated-host).





 What servers support suspend billing? 

Your virtual server instance must be configured with the following settings to support the suspend billing feature.



* Hourly SAN
* A public profile from one of the following families



* Balanced
* Compute
* Memory
* Variable compute









 How do I change the operating system on my virtual server?
* In the event that your issue requires non-EU expert assistance, it will be reviewed and approval given prior to any non-EU intervention.
* You can filter and identify the IBM Cloud Catalog services that are EU-Supported.







 Step 2. Provision IBM Log Analysis instances in Frankfurt 

You can provision IBM Log Analysis instances in multiple [locations](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-regions). However, only instances that are provisioned in the EU-DE (Frankfurt) location are EU-Supported.

For more information on how to provision an instance, see [Provisioning an instance](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-provision).





 Step 3. Configure 1 instance to manage service platform logs 

You can provision 1 or more instances in the Frankfurt location. However, only 1 of those instances can be configured to collect platform service logs for resources that run in the Frankfurt location. For more information on how to configure an instance to collect platform service logs, see [Configuring service logs](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-config_svc_logs).

Check out the list of IBM Cloud resources that automatically collect logs and forward them to your logging instance. See [platform service logs](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-cloud_services).





 Step 4. Configure your logging agents 

When you configure a logging agent for a resource such as a Kubernetes cluster, you specify to which instance that agent connects. You can only connect 1 agent per resource to a logging instance.

If you have agents that collect logs from resources, apps and services that run in the IBM Cloud or outside the IBM Cloud, and that must be EU-supported, you need to configure your agents to forward data to a logging instance in Frankfurt. Learn more:
* UI
* API







 Managing your support cases 

Each support case is assigned a unique number and severity level based on the details in the case description. You can use the case number to track the progress of your reported issue, leave feedback, or update the support case. Updates and feedback are recorded in the case notes, which you can find by selecting the specific support case. You can also add users in your account to a watchlist so they can receive alerts about a case. For more information, see [Updating your support case's watchlist](https://cloud.ibm.com/docs/get-support?topic=get-support-contact-watchlist).

To view and manage your support cases, go to the [Manage cases page](https://cloud.ibm.com/unifiedsupport/cases).

If you're a classic infrastructure user, and you don't see a listing of a previous case, click View classic infrastructure cases.



 Searching for support cases 

From the Manage cases page, you can filter by case status and search for all of your support cases by using query parameters in the search bar. All parameters can be used together and entered in any order. You can also filter cases by selecting All cases, My cases, and Watchlist cases.

See the following table for details about the search parameters:



Table 1. Search query parameters and options

 Parameter Option Rule 

 number target case number This parameter can't be used with other parameters. When the number parameter is used, all of the other parameters and options ignored. The number parameter doesn't autofill the search. You must use the whole case number to start the search. 
 sort number <br>subject <br>severity <br>updatedAt Only one of the sort options can be used at one time. You can use the prefix to reverse the sorting order. 
 status new <br>inProgress <br>waitingOnClient <br>resolutionProvided <br>resolved <br>closed Any number of options can be used. The available options can be entered as status:new,inProgress or as status:new status:inProgress.
The container might be temporarily out of service.

Try again later. If you see this message again, go to the [IBM Cloud status page](https://cloud.ibm.com/status?selected=status) to check whether a service or component has an issue. If the problem continues, go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI0089E 

Message: The '{0}' container can't be paused.

The container might be temporarily out of service.

Try again later. If you see this message again, go to the [IBM Cloud status page](https://cloud.ibm.com/status?selected=status) to check whether a service or component has an issue. If the problem continues, go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI0090E 

Message: The '{0}' container can't be unpaused.

The container might be temporarily out of service.

Try again later. If you see this message again, go to the [IBM Cloud status page](https://cloud.ibm.com/status?selected=status) to check whether a service or component has an issue. If the problem continues, go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI0091E 

Message: The '{0}' container wasn't deleted.

The container might be temporarily out of service.

Try again later. If you see this message again, go to the [IBM Cloud status page](https://cloud.ibm.com/status?selected=status) to check whether a service or component has an issue. If the problem continues, go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI0092E 

Message: The '{0}' VM group wasn't deleted because of a problem connecting to the VM resources.
For more information, see [Monitoring metrics using IBM Cloud Monitoring](https://cloud.ibm.com/docs/loadbalancer-service?topic=loadbalancer-service-monitoring-metricsmonitoring-metrics).





 What information do I need to file an IBM Support ticket? 

To file an IBM Support ticket, provide the product name ("IBM Cloud® Load Balancer"), the UUID of your load balancer (if possible) and your IBM Cloud account number. The UUID can be found in the URL after navigating to the overview page of the given load balancer.





 Where can I find pricing information for IBM Cloud Load Balancer? 

You can estimate the cost of a service using the cost estimator on the provisioning pages for IBM Cloud Load Balancer. Select IBM Cloud® Load Balancer from the Load Balancer page of the [IBM Cloud catalog](https://cloud.ibm.com/catalog/infrastructure/load-balancer-group), then click Create.
Notify customers of applicable impacts. Ascertain the impact of each notification that is reported. Engage IBM Support as required. 
 Workload monitoring Forward to customer any network intrusion notifications detected. Triage virtualization and backup-related errors to determine whether the customer issue needs assistance. Remediate all hardware failures, notification of potential workload impact. Monitor and respond to OS or software failures, backup, and replication jobs. Engage IBM Support as required. 
 Infrastructure management New features, updates, and bug fixes are continuously delivered as needed in a manner transparent to you. Maintenance activities that have customer impact are scheduled in advance, and notifications are posted to the IBM Cloud status page. Set preferences to receive emails notifications. Monitor the IBM Cloud status page for general announcements. 
 Incident management Unplanned incidents with customer impact are communicated through the CIE process. Impacted customers can obtain a report about the incident upon request. 







 Incident and operations management for VMware Solutions offerings (other than VMware Shared) 

The following table describes the responsibilities that are related to incident and operations management for all VMware Solutions offerings, other than VMware Shared.



Table 2. Responsibilities for incident and operations for VMware Solutions offerings (other than VMware Shared)
The rows are read from left to right. The first column describes the task that a customer or IBM might be responsible for. The second column describes IBM responsibilities for that task. The third column describes your responsibilities as the customer for that task.

 Task IBM responsibilities Your responsibilities 

 Availability Offer VMware® infrastructure in multiple locations, including<br><br>multizone regions (MZR)<br><br>. Plan and provision VMware infrastructure according to your availability requirements. 
 Infrastructure monitoring and notification Forward to the client all network intrusion notifications detected. Send notification upon hardware failures. Implement monitoring system and integrate with virtualization management. Determine the impact of each notification reported. Engage IBM support as required. 
 Workload monitoring Monitor and respond to OS or software failures. 
 Infrastructure management Implement monitoring and management system that is integrated with virtualization management. 
 Incident management Unplanned incidents with customer impact are communicated through the CIE process.
Click Notification preferences > Resource.
3. Select from the following options:



* Receive notifications about events that can cause an outage or restrict functionality. You can receive notifications for all incident severity levels (1, 2, 3, 4) or just a subset.
* Receive notifications about any important maintenance that keeps the platform operating at optimal status. You can receive notifications for all impact levels (high, medium, low), or just a subset.
* Receive notifications about security vulnerabilities and the required actions to take.
* Receive notifications about resource activity, such as status and service updates.
* By default, all IBM Cloud resource notifications are turned off.





To quickly turn off emails for the selected account or for all other accounts, click Actions, and select your preference.





 Setting user notifications for classic infrastructure resources 

Setting user notifications is available for classic infrastructure resources only. If you're an account owner, you can subscribe users in your account to notifications for a specific set of developer services like Auto-Scaling and Raid Alert Monitoring. When the user is subscribed to a service, they receive emails about that service. Changes that you make for a user take effect only for future notifications. A user is not notified about events that occurred before you set up notifications.

Users in your account receive notifications for the following types of important operational events:



* Unplanned infrastructure issues or outages: Issues that might cause an outage based on certain conditions for specific customers.
* Planned service or scheduled maintenance: Maintenance that is required to keep the infrastructure operating at optimal status.
* Security vulnerabilities: The affected area is isolated. A patch is created to close the vulnerability, and tests are performed on the patch to ensure that no collateral function is affected.



The timing of the notification varies depending on whether the event is unplanned, planned, or scheduled. The IBM Cloud infrastructure policy is to remedy problems as quickly as possible to remove or minimize the risk of further issues that might have a larger impact. Sometimes even planned maintenance is performed with only a short advanced notification.

To set up subscription notifications for your users, complete the following steps:



1.
Case severity and initial response times 

How quickly your support cases are addressed depends on the assigned severity. You assign the severity of the issue when you open the case. With your agreement, the support team adjusts the assigned severity if an incorrect severity level is selected. For more information about Support plans, see [Basic, Advanced, and Premium Support plans](https://cloud.ibm.com/docs/get-support?topic=get-support-support-plans).

The following table lists some common examples of support issues, suggested severity levels, and the initial response time objectives. The initial response time objectives are used to describe IBM goals only, and don't represent a performance guarantee.

Initial response Service Level Objectives (SLO) do not apply to any billing, invoice, or sales-related inquiry or cases.

Severity Level Definition

Initial Response Time Objectives



Table 1. Case severity definitions

 Severity  Business impact  Details                                                                                                                                                                                                                                                                                                                       

 4         Minimal          An inquiry or non-technical request.                                                                                                                                                                                                                                                                                          
 3         Some             The product, service, or functions are usable, and the issue doesn't represent a significant impact on operations.                                                                                                                                                                                                            
 2         Significant      A product, service, business feature, or function of the product or service is severely restricted in its use, or you are in jeopardy of missing business deadlines.                                                                                                                                                          
 1         Critical         System or Service Down  <br>Business-critical functions are inoperable or a critical interface has failed. This usually applies to a production environment and indicates an inability to access products or services that results in a critical impact on operations. This condition requires an immediate solution.         



We work with you 24 hours a day and seven days a week to resolve Severity 1 problems if you have a technical resource available to work during those hours. You must reasonably assist with any problem diagnosis and resolution.
If the output from the previous step indicates a failure, check that your hosts meet all [system requirements](https://cloud.ibm.com/docs/satellite?topic=satellite-host-reqs).
3. If you have met all the system requirements and the issue persists, [open a support case](https://cloud.ibm.com/docs/satellite?topic=satellite-get-help) and include your Satellite location ID. You can find your location ID by running the ibmcloud sat location ls command.



For additional information about the affected components, [set up Log Analysis](https://cloud.ibm.com/docs/satellite?topic=satellite-get-helpreview-logs) and review the [R0059 error logs](https://cloud.ibm.com/docs/satellite?topic=satellite-healthlogs-error).





 R0060: Outbound traffic to LaunchDarkly is failing. 

Location message
: Outbound traffic to LaunchDarkly is failing. To ensure that all host requirements are met, see the [Host system requirements](https://cloud.ibm.com/docs/satellite?topic=satellite-host-reqs).. More information is available in the IBM Cloud Platform Logs. If the issue persists, contact IBM Cloud Support and include your Satellite location ID.

Steps to resolve
: Check the health status and ensure that the host system requirements are met.



1. Run the following command to check the health status.

curl https://iam.cloud.ibm.com/healthz
2. If the output from the previous step indicates a failure, check that your hosts meet all [system requirements](https://cloud.ibm.com/docs/satellite?topic=satellite-host-reqs).
3. If you have met all the system requirements and the issue persists, [open a support case](https://cloud.ibm.com/docs/satellite?topic=satellite-get-help) and include your Satellite location ID. You can find your location ID by running the ibmcloud sat location ls command.