vania-janet/multiturn-rag-retrieval-data huggingface dataset:
If either the service instance or bucket were deleted, [open a support case](https://cloud.ibm.com/docs/satellite?topic=satellite-get-help) and include your Satellite location ID.



3. If the control plane hosts can reach the Object Storage endpoint, and the Object Storage service instance and bucket exist, [open a support case](https://cloud.ibm.com/docs/satellite?topic=satellite-get-help) to investigate backup failures and include your Satellite location ID.







 R0049: Satellite Link IAM API key issue 

Location message
: The Link connector is experiencing authentication issues. Contact IBM Cloud Support and include your Satellite location ID.
: This error is reported because the IAM API key that is set for the region or resource group that the location is in does not have the required permissions in Satellite or Kubernetes Service, usually because the permissions of the API key owner changed or the API owner left the account.

Steps to resolve
: If you have a Red Hat OpenShift cluster in a Satellite location and you are the account owner or a user with Administrator permission for all Satellite components, you can resolve this issue by resetting the API key. Note that when you reset the API key, the old key is deleted. Be sure to check if other services are using this API key.
: 

1. Log in to IBM Cloud: ibmcloud login.
2. Target the region that the location is managed from: ibmcloud target -r <region>.
3. Target the resource group that the location is in: ibmcloud target -g <resource-group>.
4. Reset the IAM API key for that region or resource group: ibmcloud ks api-key reset --region <region>.
5. Review that the API key was set: ibmcloud ks api-key info --cluster <roks_cluster_in_location>.
6. [Open a support case](https://cloud.ibm.com/docs/satellite?topic=satellite-get-help) and ask that the location that contains the cluster to be refreshed.
Resources and support forums 

IBM Blockchain Service docs

[IBM Blockchain Service docs](https://cloud.ibm.com/docs/blockchain?topic=blockchain-get-started-ibpget-started-ibp), provides guidance on how to start with IBM Blockchain Platform. You can find corresponding topics from the table of contents or search any term from the search bar.

Hyperledger Fabric resources

[Hyperledger Fabric documentation](https://hyperledger-fabric.readthedocs.io/en/release-2.2/), the [Fabric community wiki](https://wiki.hyperledger.org/display/fabric), and the [Fabric Jira dashboard](https://jira.hyperledger.org/secure/Dashboard.jspa?selectPageId=10104) provide more details about the Fabric stack.

You can also post questions or check if your question was answered in [Stack Overflow](https://stackoverflow.com/questions/tagged/hyperledger-fabric).

Developer resources

[IBM Developer](https://developer.ibm.com/technologies/blockchain/) provides tutorials, code patterns, and videos for blockchain developers. Application developers can use the [Blockchain Design patterns](https://developer.ibm.com/technologies/blockchain/articles/getting-started-with-blockchain-design-patterns) to learn about common patterns and best practices for building applications that communicate with blockchain networks.

Because IBM does not support using Hyperledger Composer for production implementation, you are encouraged to engage with [Hyperledger Composer community](https://chat.hyperledger.org/channel/composer) and [Stack Overflow](https://stackoverflow.com/questions/tagged/hyperledger-composer) when you work on demos and proofs of concept.





 Submitting support cases 

For issues that are related to IBM Blockchain Platform for IBM Cloud, you can submit a support case in the [IBM Cloud Service Portal](https://cloud.ibm.com/unifiedsupport/supportcenter).
3. Click the log tab and review the log information.

![SSP-View-SR-Logs](https://cloud.ibm.com/docs-content/v1/content/bd177462727ef0a849ddcf8c842a6203b41f0625/mas-ms/images/SSP-View-SR-Logs.png)







 In the event of a failure 

Detailed log information surrounding the failure will be available in the log tab of the service request. In the event the failure is not due to a problem with the data submitted with the required, you should engage the operations team by opening a case. Use the following links for more information. Please include a request to complete the action required, as well documenting that this action was attempted via the self-service portal.

[Requesting Support for IBM Maximo Application Suite](https://cloud.ibm.com/docs/mas-ms?topic=mas-ms-getting-started-with-ibm-maximo-application-suite-dedicatedhow-to-register-for-mas-support)

[How To 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)

Requests will be handled per the Service Description for non-production environments. Issues with the portal are handled on the same service description.

[Service Descriptions and SLA](https://cloud.ibm.com/docs/mas-ms?topic=mas-ms-servicesservice-description)







 Access Management Tool 

The Access Management Tool is a self-service tool, located in the Saas Self-Service Portal, where users can manage access to their MAS-Dedicated environments.

Self-Service Portal URL:

[https://devops.maximo.com](https://devops.maximo.com)





 Access Management Tool Overview 



 User Roles 

The Access Management Tool supports two user roles - standard users and manager users. Manager users have elevated accesses to manage the tool for their customer.
RAID support case information 

If you have a question about using RAID on your bare metal server, you might find an answer in the [IBM Developer Answers](https://developer.ibm.com/answers/topics/ibm-cloud/) forum. You can also open a support case. For more information about support cases, see [Getting support](https://cloud.ibm.com/docs/get-support?topic=get-support-using-avatargetting-support).

When a support case is created, you need to provide RAID log files. The information in RAID log files is critical to the recovery of a lost RAID configuration. Providing your log files helps the support team identify drive order, array membership, array geometry, and cabling issues. Depending on the type of RAID controller that you are using, Adaptec or Broadcom, use the following commands to retrieve RAID log files.

Granting permission to restart or power down in the initial update or by asking for the drive to be hot-swapped, speeds up the support case process.



  Adaptec RAID cards 

Use the following command to obtain the log files for Adaptec RAID cards. Remember to include the full output of this log file in your support case.

arcconf getconfig 1/arcconf getlogs 1 device tabular





  Broadcom RAID cards 

Use the following commands to obtain the log files for Broadcom RAID cards. Remember to include full output of these log files in your support case.

/opt/MegaRAID/storcli/storcli64 /c0 show all
/opt/MegaRAID/storcli/storcli64 /c0 show TermLog
/opt/MegaRAID/storcli/storcli64 /c0 /eall /sall show all | grep -iE "det|cou|tem|SN|S.M|fir"
/opt/MegaRAID/storcli/storcli64 /c0 show TermLog

Make sure that you back up any work before troubleshooting begins.
Responsibilities for Day 2 operations 

Review the two key principles for Day 2 operations.



* Your VMware vCenter Server® instance is not actively monitored by IBM®. After deployment, use existing tools, use a managed service. Examples of a manged service include IBM Integrated Managed Infrastructure, a third-party managed service, or implement a self-managed monitoring solution as described in [Operations management introduction](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-opsmgmt-intro).
* IBM Support does not enter the VMware® management layer under normal operations without a client–written support ticket. You must raise a support ticket to engage support from IBM. For more information, see [Contacting IBM support](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-trbl_support). You must actively manage the ticket must be actively to ensure that you provide the requested information that is required by IBM in a timely manor. For more information, see [Managing your support cases](https://cloud.ibm.com/docs/get-support?topic=get-support-managing-support-cases) and [Escalating support cases](https://cloud.ibm.com/docs/get-support?topic=get-support-escalation).



For more information about IBM and customer responsibilities that concern compliance, see [Customer versus IBM responsibility for vCenter Server](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_compl_infovc_compl_info-responsibility).

Day 2 responsibilities include the following items:



* Service Support - IBM provides support for IBM Cloud® for VMware Solutions issues that you report. You must raise support tickets as directed in [Contacting IBM Support](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-trbl_support).
Why can't I create or edit support cases? 

You can't create or edit an IBM Cloud support case, and you receive an error message that you don't have the appropriate access.

  What’s happening 

When you try to create a case, the following error message is displayed:

> Looks like you don't have access to create cases for this account.

  Why it’s happening 

General problems with accessing and managing support cases might be caused by not having the Identity and Access Management (IAM) access policy for the Support Center account management service. You must be assigned the editor or administrator role on the support center account management service to create cases.

  How to fix it 

The account owner, an administrator on the support center service, or the administrator on all account management services can assign an IAM policy on support center to manage cases.

If you're the account owner or an administrator of the Support Center, complete the following steps to create an access policy for working with support cases:



1.  In the IBM Cloud console, go to Manage > Access (IAM) and select Users.
2.  Select a username, and click Access policies.
3.  Click Assign Access.
4.  From the Assign users additional access section, select Account management.
5.  For the type of access that you want to assign, select Support Center.
6.  Select a role to define the level of access for the user. The user needs the Editor or Administrator role to view, search, create, and update support cases.
Contact a Partner Center onboarding specialist, if you have questions about the following topics:



* General questions about the onboarding process
* Pricing models, for example, tiering model, monthly or yearly subscription, cancellation of subscription, or refund
* Metering and billing issues
* Broker functionality
* Tax and EFT (Electronic Funds Transfer) forms



To contact an onboarding specialist, complete the following steps:



1. In the IBM Cloud console, click the Navigation Menu icon ![Navigation Menu icon](https://cloud.ibm.com/docs-content/v1/content/ff5860bfede49db3197c4bbba7f7123769bdc068/icons/icon_hamburger.svg) > Partner Center > Sell > My products.
2. From the My products page, click the Help icon ![Help icon](https://cloud.ibm.com/docs-content/v1/content/ff5860bfede49db3197c4bbba7f7123769bdc068/icons/help.svg).
3. From the We're here to help tile, select Contact Us.
4. Describe your issue or question in the message field and click Send.







 Creating a Partner Center support case 

If you're experiencing issues with Partner Center, you can create a support case by using the [IBM Cloud Support Center](https://cloud.ibm.com/unifiedsupport/supportcenter).

To create a support case, you must have a Pay-As-You-Go or Subscription account. Also, ensure that you're assigned at least the editor role on the Support Center account management service to create, edit, or view support cases.
Latency Improvements 

For users facing latency issues when migrating from on-premise applications to on-cloud services please contact the Db2 on Cloud team and then complete the following steps to improve latency. To begin the latency improvement process, please open a support case.

For information about opening an IBM support case, or about support levels and case severities, see: [Working with support cases](https://cloud.ibm.com/docs/get-support?topic=get-support-open-caseopen-case)

The latency improvement process cannot be completed without contacting the Db2 on Cloud team at this time.



 Steps 



1. Set up client SSL (if not already set up)

For existing Db2 users, SSL would have been set up during the configuration process.

If SSL setup is required, follow the steps outlined in Db2 documentation:
[https://www.ibm.com/docs/en/db2/11.5?topic=ctsidc-configuring-tls-support-in-non-java-db2-clients](https://www.ibm.com/docs/en/db2/11.5?topic=ctsidc-configuring-tls-support-in-non-java-db2-clients)
2. Set up client connection



1. To enable client affinity, the Automatic Client Reroute (ACR) configuration is provided by the db2dsdriver.cfg on the db2 client machine



1. Obtain the sample db2dsdriver from /opt/ibm/db2/V11.5/cfg/db2dsdriver.cfg.sample
2. Copy into /home/db2inst1/sqllib/cfg/
3. Rename to db2dsdriver.cfg



2. The db2dsdriver.cfg is the last configuration method used to establish a connection to the db2 database. This means that db2dsdriver.cfg has the least precedence and will only be used for connecting when no other connection configurations are available.
3.
subnet_unknown_state 

Message: The subnet <subnet_id> is in an invalid state for the requested operation.

The subnet must be in available status before you can operate it. 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).





 target_in_use 

Message: The target already has floating IP attached.

There was a request to attach a floating IP address to a server’s network interface, but the network interface already has a floating IP attached to it.

To find the floating IP address currently attached to a network interface, run the API command GET /v1/floating_ips?version=$version&generation=1 and look for the network interface ID in the target.id field.

If you are using the CLI, run the command ibmcloud is floating-ips and look at the Target value. Be aware that the CLI truncates the network interface ID at the first dash (“-“) character. For example, a server’s primary network interface with an ID of abdfcb29-b3c5-4e4a-b7a0-cf0300154699 appears as primary(abdfcb29-.) in the CLI output.





 token_invalid 

Message: The service token was expired or invalid.

For further instructions to fix this problem, refer to the [API documentation](https://cloud.ibm.com/apidocs/vpc-on-classic). If this problem persists, [contact support](https://cloud.ibm.com/docs/vpc-on-classic?topic=vpc-on-classic-getting-help-and-support).





 token_missing 

Message: The service token was empty or did not exist in the request.

Recreate a token and try again.





 validation_enum 

Message: The value supplied was not a valid option.

One of the fields supplied has a value that must come from an enumeration of possible values.
Assigning user access for working with support cases 

By default, users in your account don't have access to create, update, search, or view cases. The account owner must provide users access by assigning an Identity and Access Management (IAM) access policy. Use the Support Center account management service to assign users access to work with support cases.

When you create a case, you can give other users full access to that case by adding their email to the Add another person to this case field. Any added users have access to view, edit, and update only that case in the account. They also receive notifications when the case is updated.

For classic infrastructure users, the permissions to assign support case access is now available in [migrated classic infrastructure permission access groups](https://cloud.ibm.com/docs/account?topic=account-migrated_permissions). The migrated permission access groups do include the IAM policy on the user management service with the viewer role assigned.

The following table shows the roles and actions that are required to work with cases:



Table 1. Roles and actions for the Support Center service

 Role Action 

 Viewer View and search cases 
 Editor View, search, create, and update cases 
 Administrator View, search, create, and update cases; manage support center roles for other users 



By default, users with a Support Center service role can access support cases that they are assigned to unless one of the following conditions is met:



* User list visibility is set to Unrestricted view by the account owner.
* The user is assigned a user management account management service role.





 Creating an access group for working with cases 

To streamline the access assignment process, you can take advantage of assigning a policy to users through access groups. Complete the following steps to create an access group with support center service access:



1. In the IBM Cloud console, go to Manage > Access (IAM), select Access groups, and click Create.
2. Enter an access group name and description, and click Create.
3. Click Actions... > Assign access.
4. Select Support Center from the list of services and click Next.
5.
http:
paths:
- backend:
service:
name: ibm-k8s-controller-health
port:
number: 80
path: /
pathType: ImplementationSpecific
tls:
- hosts:
- albhealth.<ingress-subdomain>
secretName: <ingress-secret>
Show more
3. Add the Ingress subdomain and Ingress secret that you retrieved in step 1 to the Ingress configuration file.
4. Create the Ingress resource in your cluster.

kubectl apply -f ingress.yaml
5. Wait 10-15 minutes, then retry the ibmcloud ks ingress status-report get command to see if the issue is resolved.
6. If the issue persists, contact support. Open a [support case](https://cloud.ibm.com/docs/get-support?topic=get-support-using-avatar). In the case details, be sure to include any relevant log files, error messages, or command outputs.
* If the case in which the incident occurred is closed, a new case should be opened by the customer specifically requesting an RCA. It should include the original case number of the incident.
* For example: "Request for RCA on TS00001111"



RCA lead times

An RCA can take between 5 to 10 business days to be completed. RCA detail will be provided in the applicable case.





 IBM Support Guides 

An IBM Support Guide for Maximo Application Suite is available. See link below. The guide contains information such as Contact Information, Hours of Operation, Severity Level Guidelines and Response Time Objectives and Issue Escalation:

[https://www.ibm.com/support/pages/node/733923](https://www.ibm.com/support/pages/node/733923)





 Project Implementation Guidelines 



 Planning 



 1.1 Implementation Types 

There are generally two types of implementation scenarios when working with IBM SRE on a large implementation of MAS:

New Implementation

In this scenario, MAS is implemented from an "out of the box" build. Data is usually migrated manually into "net new" MAS environment(s) by the customer or system implementor. Changes and customizations are made directly in the MAS environment itself or migrated manually from one or more standalone environment(s). This type of implementation typically does not require a statement of work with the customer or IBM internal DoU (Document of Understanding) with IBM SRE, as the level of effort on the SRE side usually falls under IBM's standard MAS support services.

Migration to IBM Cloud or AWS

In this scenario, an existing on-premise or non-IBM Cloud production Maximo v7 environment is migrated and upgraded to MAS on the IBM Cloud or AWS. This type of scenario requires a separate purchase of a migration part number as well as some analysis to ensure the correct level of IBM SRE effort is captured. It usually involves one or more test migrations and a live cutover. IBM SRE services related to a cloud migration effort are not included as part of IBM's standard MAS Dedicated or MAS-MS subscription. Please see Maximo Migration to Cloud Services for further details:
* Classic: If you see errors saying that no IPs are available, add new portable subnets to the cluster with the ibmcloud ks cluster subnet create[command](https://cloud.ibm.com/docs/containers?topic=containers-kubernetes-service-clics_cluster_subnet_create).
* VPC: If you see permission issues, review your IAM permissions. For more information, see [Setting up an Application Load Balancer for VPC](https://cloud.ibm.com/docs/containers?topic=containers-vpc-lbaassetup_vpc_ks_vpc_lb).
* VPC: Ensure that you did not reach your LBaaS instance quota. For more information, see [Quotas and service limits](https://cloud.ibm.com/docs/vpc?topic=vpc-quotasalb-quotas) and ibmcloud is load-balancers[command](https://cloud.ibm.com/docs/vpc?topic=vpc-vpc-referencelb-anchor).



6. Wait 10 to 15 minutes, then check if the load balancer got an address assigned. If not, check the events again.
7. If you see a different error, repeat the troubleshooting steps. If the issue persists, contact support. Open a [support case](https://cloud.ibm.com/docs/get-support?topic=get-support-using-avatar). In the case details, be sure to include any relevant log files, error messages, or command outputs.
Verify that it's enabled by checking the virtual routing and forwarding section, which is the preceding section in your account settings.
3. Review the impacts to your account, and click On.



It might take a few minutes for this change to take effect.





 Enabling service endpoints in the CLI 

To enable service endpoints from the [IBM Cloud CLI](https://cloud.ibm.com/docs/cli?topic=cli-getting-started), you need version 0.13 or later.



1. Check whether service endpoints are already enabled in your account.

ibmcloud account show

If Service Endpoint Enabled is false as shown in the following example, service endpoints are not enabled.

Retrieving account Mia Example's Account of m.example@example.com...
OK

Account ID: abc123d0bc2edefthyufffc9b5ca318
Currently Targeted Account: true
Linked Softlayer Account: 0123456
Service Endpoint Enabled: false
2. Enable service endpoints by running the following command.

ibmcloud account update --service-endpoint-enable true

It might take a few minutes for this change to take affect. After the command completes, you can run the ibmcloud account show command again to verify.

If VRF isn't enabled for your account, running this command prompts you to create a case to enable it. Enter y to create the support case. After VRF is enabled in the account, run the command again to enable service endpoint connectivity in your account.

Service Endpoint is not available in linked Softlayer Account 1008967.
Enable VRF(Virtual Routing and Forwarding) first to proceed.
Learn more about VRF here - https://cloud.ibm.com/docs/infrastructure/direct-link/vrf-on-ibm-cloud.html.

Do you want to open a ticket to enable it?[y/N]> y
Ticket 70729615 was opened successfully.