vania-janet/multiturn-rag-retrieval-data huggingface dataset:
This problem can occur if a firewall prevents the provisioning framework from updating the password value.





 How to fix it 



* Option 1: Update the firewall to allow the IBM Cloud service IP ranges as described in the firewall [documentation](https://cloud.ibm.com/docs/vsrx?topic=hardware-firewall-shared-ibm-cloud-ip-ranges). These ranges allow for provisioning, monitoring, and management. Restart the server so the provisioning network to populate the password in the portal.
* Option 2: Bypass the VLAN of the server from the firewall. Then, restart the server to allow provisioning network to populate the password in the portal and then route the VLAN back in the firewall.









 Why is my virtual server read-only? 



 Why it's happening 

A virtual server might receive a read-only issue because of unplanned networking incidents or outages.





 How to fix it 

To bring back your server from a read-only status, you need to restart the server to rescue kernel, and you need to run a file system check on all your file systems.



1. From your device list, click the name of the server > Actions menu > Rescue kernel.
2. When your server restarts in rescue mode, log in to the server by using SSH with the root user credentials.
3. Run a file system check by using the following command: fsck -y -C /dev/xvda1
4. Run the same command if you have more files systems such as /dev/xvda2, /dev/xvda3, and so on.



For more help, contact [support](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-gettinghelp) or open a support case.

Running a file system check might cause data loss, so make sure that your data is backed up.







 Why does my server have connectivity issues? 



 Why it's happening 

If your server has connectivity issues, the server might experience packet drops or packet loss and intermittent network connectivity.





 How to fix it
Getting support 

ATTENTION!! IBM Blockchain Platform SaaS Edition is being replaced by IBM Support for Hyperledger Fabric!! IBM Blockchain Platform SaaS Edition will no longer be supported after July 31, 2023. Customers have been directed to migrate their networks by July 31, 2023. After this date, IBM Blockchain Platform SaaS networks that are not migrated to IBM Support for Hyperledger Fabric will be at risk for potential security vulnerabilities. A migration tool is provided from your console, and the disruption to your network is minimal. See [Migrating to IBM Support for Hyperledger Fabric](https://cloud.ibm.com/docs/blockchain?topic=blockchain-migrating-to-hlf-support) for details.

IBM® Blockchain Platform provides several avenues for troubleshooting problems and getting support, which depend on your IBM Blockchain Platform product, support plan and case severity.



 Security incidents 

IBM® Blockchain Platform provides the following methods for investigating and reporting security incidents:



* Search known IBM security issues on the [IBM Product Security Incident Response](https://www.ibm.com/blogs/psirt/) blog. You can filter the issues by severity.
* Report your security issue to the [IBM Product Security Incident Response Team (PSIRT)](https://www.ibm.com/trust/security-psirt). Reporting methods for third-parties and anonymous sources are also provided.
* IBM support subscribers can log in and open a case with the appropriate severity. Refer to details, including IBM response times, below in [Submitting support cases](https://cloud.ibm.com/docs/blockchain?topic=blockchain-blockchain-supportsubmitting-support-cases).







 General support 

For all IBM Blockchain Platform offerings, it is recommended to first use [free digital support resources](https://cloud.ibm.com/docs/blockchain?topic=blockchain-blockchain-supportblockchain-support-resources) to troubleshoot problems and get help from IBM and the Hyperledger Fabric Community.
If the issue persists when creating additional clusters, open an [IBM Cloud support case](https://cloud.ibm.com/docs/openshift?topic=openshift-get-help).





 Delete failed 

Review the following description of the Delete failed cluster state. To view the state of your cluster, run ibmcloud oc cluster get --cluster <cluster_name_or_ID>.

The Kubernetes master or at least one worker node can't be deleted. List worker nodes by running ibmcloud oc worker ls --cluster <cluster_name_or_ID>. If worker nodes are listed, see [Unable to create or delete worker nodes](https://cloud.ibm.com/docs/openshift?topic=openshift-cluster_infra_errors). If no workers are listed, open an [IBM Cloud support case](https://cloud.ibm.com/docs/openshift?topic=openshift-get-help).





 Deleted 

Review the following description of the Deleted cluster state. To view the state of your cluster, run ibmcloud oc cluster get --cluster <cluster_name_or_ID>.

The cluster is deleted but not yet removed from your dashboard. If your cluster is stuck in this state for a long time, open an [IBM Cloud support case](https://cloud.ibm.com/docs/openshift?topic=openshift-get-help).





 Deleting 

Review the following description of the Deleting cluster state. To view the state of your cluster, run ibmcloud oc cluster get --cluster <cluster_name_or_ID>.

The cluster is being deleted and cluster infrastructure is being dismantled. You can't access the cluster.





 Deploy failed 

Review the following description of the Deploy failed cluster state. To view the state of your cluster, run ibmcloud oc cluster get --cluster <cluster_name_or_ID>.

The deployment of the Kubernetes master can't be completed. You can't resolve this state.
(For information about the amount of time needed to create the service instance, see [Choosing your plan](https://cloud.ibm.com/docs/EventStreams?topic=EventStreams-choosing-your-planwhat-is-supported)).
2. Log in to the IBM Cloud CLI.

ibmcloud login
3. Get the resource name of your Event Streams service instance.

ibmcloud resource service-instances

(You can find the name of your instance in the Name column.)
4. View the current capacity configuration by using the Event Streams CLI.

To install and use the CLI plug-in, refer to [cli reference](https://cloud.ibm.com/docs/EventStreams?topic=EventStreams-cli_reference).

Use the following command to display the current capacity configuration:

ibmcloud es init  --instance-name  "Event Streams resource instance name"

Output is similar to the following output, which shows this service instance is configured with 150 MB/s of throughput capacity and 2 TB of storage capacity:

API Endpoint:        https://service-instance-adsf1234asdf1234asdf1234-0000.eu-south.containers.appdomain.cloud
Service endpoints:    public
Storage size:        2048 GB
Throughput:        150 MB/s
5. Scale up the service instance from 150 MB/s throughput capacity and 2 TB storage capacity to 300 MB/s throughput capacity and 8 TB storage capacity.

a. Run the following command from the CLI.

ibmcloud resource service-instance-update "Event Streams resource instance name" -p '{"throughput":"300","storage_size":"8192"}'

b. If you have an issue when you run the ibmcloud resource service-instance-update command and requires contacting IBM Support for assistance, run the following command and include the output when you contact support.

ibmcloud resource service-instance "Event Streams resource instance name" --output=json
6. Monitor the update of the service instance.
Directories are not supported.

Example:

save_file some_config ./config.yaml





 load_file 

 <key>: File name
load_file <key>

Prints the saved file to stdout.

Example:

load_file some_config > some_config.yaml





 save_repo 

 <key>: Key of the repository e.g. repository name
 <prop>: Type of the property, e.g. url, branch, commit etc.
 <value>: Value of the property
save_repo <key> [<prop>=<value> ...]

Registers a new repository with the pipeline or updates an existing one.

Supported properties:



* url: The URL that can be used to clone the repository.
* path: Location of the cloned repository relative to the workspace root.



Other property names can be used as well, but to avoid naming collisions, they must be prefixed with a service-specific identifier, for example instead of using foo, use my-service.foo.

Example:

save_repo app_ui "url=${REPO_URL}" "path=app_ui_repo"
save_repo app_ui "branch=${REPO_BRANCH}"
save_repo app_ui "commit=${REPO_SHA}"

 any additional property can be added
save_repo app_ui "commit=${REPO_SHA}"



 Using stdin as a value source 

Values can be provided from stdin, if the following conditions are true:



* The content is streamed for the command
* One property does not have a value and =



Example:

command_with_large_output | save_repo app_ui "issues"

 this also works with multiple properties,
 but stdin can provide value for only a single one
command_with_large_output | save_repo app_ui "issues" "result=success" "commit=${REPO_SHA}"
Why does the Ingress status show an ERRAHSNF error? 

Virtual Private Cloud

Classic infrastructure

You can use the the ibmcloud ks ingress status-report ignored-errors add command to add an error to the ignored-errors list. Ignored errors still appear in the output of the ibmcloud ks ingress status-report get command, but are ignored when calculating the overall Ingress Status.

  What’s happening 

When you check the status of your cluster's Ingress components by running the ibmcloud ks ingress status-report get command, you see an error similar to the following example.

The ALB health service is not found on the cluster (ERRAHSNF).

  Why it’s happening 

IBM Cloud Kubernetes Service deploys a managed health check service to every cluster. If the service is missing from your cluster, this might result in invalid health check results.

  How to fix it 

Manually create the health service.



1.  Copy the following service configuration and save it to a file called service.yaml.

apiVersion: v1
kind: Service
metadata:
name: ibm-k8s-controller-health
namespace: kube-system
spec:
ports:
- name: http
port: 80
protocol: TCP
targetPort: 8283
selector:
alb-image-type: community
type: ClusterIP
2.  Create the health check service in your cluster.

kubectl apply -f service.yaml
3.  Wait 10-15 minutes, then retry the ibmcloud ks ingress status-report get command to see if the issue is resolved.
4.  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 you're using the CLI or API to assign access, use streaming-analytics for the service name.

Service roles

Actions



Table 147. Service roles - streaming-analytics
Use the tab buttons to change the context of the table. This table has row and column headers. The row headers provide the service role name and the column headers identify the specific information available about each role.

 Role Description 

 null null 
 null null 







 Support Center 

Review the available platform and service roles and the actions mapped to each to help you assign access. If you're using the CLI or API to assign access, use support for the service name.

Platform roles

Actions



Table 148. Platform roles - Support Center
Use the tab buttons to change the context of the table. This table has row and column headers. The row headers provide the platform role name and the column headers identify the specific information available about each role.

 Role Description 

 Administrator View, search, create, and update support cases 
 Editor View, search, create, and update support cases 
 Viewer View and search support cases 







 IBM Cloud Monitoring with Sysdig 

Review the available platform and service roles and the actions mapped to each to help you assign access. If you're using the CLI or API to assign access, use sysdig-monitor for the service name.

Platform roles

Service roles

Actions



Table 149. Platform roles - IBM Cloud Monitoring with Sysdig
Use the tab buttons to change the context of the table. This table has row and column headers. The row headers provide the platform role name and the column headers identify the specific information available about each role.

 Role Description 

 Administrator As an administrator, you can perform all platform actions according to the resource for which this role is assigned, including assigning access policies to other users and managing Sysdig team membership. 







 IBM Cloud Security 

Review the available platform and service roles and the actions mapped to each to help you assign access. If you're using the CLI or API to assign access, use sysdig-secure for the service name.

Platform roles

Service roles

Actions



Table 150.
Administrator Create, delete, update a software instance<br><br>View the details page for the software instance<br><br>View the logs for the software instance<br><br>Assign IAM permissions crn:v1:bluemix:public:iam::::role:Administrator 







 Support center 

You can give users access to manage support cases.



Table 20. Roles and example actions for the Support Center service

 Roles Actions role_ID value 

 Viewer View cases<br><br>Search cases crn:v1:bluemix:public:iam::::role:Viewer 
 Operator Not applicable crn:v1:bluemix:public:iam::::role:Operator 
 Editor View cases<br><br>Search cases<br><br>Update cases<br><br>Create cases crn:v1:bluemix:public:iam::::role:Editor 
 Administrator View cases<br><br>Search cases<br><br>Update cases<br><br>Create cases crn:v1:bluemix:public:iam::::role:Administrator 



Assign users the viewer role on the user management service in addition to a support center access policy so the user can see all cases in the account regardless of user list visibility settings. If the user list visibility is set to be restricted, a user's ability to view, search, and manage support cases in an account that they didn't open themselves can be limited.





 User management 

You can give users access to view users in an account, invite and remove users, and view and update user profile settings.



Table 21. Roles and example actions for the User Management service

 Roles Actions role_ID value 

 Viewer View users in the account<br><br>View user profile settings crn:v1:bluemix:public:iam::::role:Viewer 
 Operator View users in the account<br><br>View user profile settings crn:v1:bluemix:public:iam::::role:Operator
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.
Why does the Ingress status show an ERRSEIPM error? 

Satellite

You can use the the ibmcloud oc ingress status-report ignored-errors add command to add an error to the ignored-errors list. Ignored errors still appear in the output of the ibmcloud oc ingress status-report get command, but are ignored when calculating the overall Ingress Status.

  What’s happening 

When you check the status of your cluster's Ingress components by running the ibmcloud oc ingress status-report get command, you see an error similar to the following example.

The service is missing one or more worker IPs (ERRSEIPM).

  Why it’s happening 

The service that exposes the default Ingress Controller does not have all the necessary worker IP addresses.

  How to fix it 

Add the worker IP addresses to the external Ingress service.



1.  Run the following command and make note of your worker IP addresses in the INTERNAL-IP column.

oc get nodes -o wide
2.  Run the following command to edit the service.

oc edit service -n openshift-ingress router-external-default
3.  Add the IP addresses that you retrieved in step 1 to the spec.externalIPs list.

If your cluster has many workers, you might not want to add all the IP addresses to the list. In this case, it is sufficient to add two IP addresses per zone. To see which worker belongs to which zone, look for the value of the topology.kubernetes.io/zone label in the output of the oc get nodes -o wide --show-labels command.
4.  Wait 10 to 15 minutes, then check if the warning is resolved by running the ibmcloud oc ingress status-report get command.
5.  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.
The overall amount of time can vary depending on the size (user license) of the environment(s), total number of environments needed (for example DEV, TEST, PROD), number and type of industry solutions within each environment, number & type of add-on components such as Maximo Anywhere, availability of resources in the target data center location, and amount of orders in the queue.





 Onboarding & Implementation 



 3.1 Onboarding Roles 

The following onboarding roles should be defined:



* Client Business Leader - provides formal sign off of completed phases
* Project Implementer - Top level contact of the Implementor (GBS, Partner, 3rd Party)
* Project Manager - usually provided by the Implementor
* IBM SRE - provides environment support via case tickets
* Client IT Team - obtains support for MAS environments by submitting case tickets







 3.2 Traps 

The following are common "traps" that can occur in MAS implementation projects.



* Not allocating time to test any potential product issues found
* Report Developer Access
* Planning & Organizing VPN configuration to support integration(s)
* Inability to submit case tickets (see IBM SRE Services Support)
* Not engaging the IBM SRE team early, esp regarding networking (see section 3.6 below 'Back End Access')
* Not planning or coordinating a detailed go live plan and schedule
* Not planning for post-go live maintenance
* Not allocating time or resources for performance load testing







 3.3 Welcome Kit 

When the MAS environments are provisioned and ready, the customer contacts on the order's Provisioning Form will receive a Welcome Kit from IBM with full details on accessing their environments. Customers will be provided a URL for each environment and will be able to login as the masadmin (Maximo) user. Customers are responsible for setting up additional users and security groups within each environment





 3.4 On Boarding Meeting 

IBM will schedule and provide an on-boarding meeting. This meeting serves as a brief introduction to IBM SRE services and covers the following details:



* Contacts, Support and Administration
* Client Environments (how to access)
* Support (How to get Help)
* Roles & Responsibilities
* Tools & Access Control
* Helpful Links
The best means of controlling how a specific string is pronounced is to use the <say-as> element of the SSML. The element allows you to specify exactly how a string is synthesized. You use the interpret-as attribute of the <say-as> element to indicate that a string of characters is to be pronounced as letters, digits, or in some other way. The available values differ by language.

If you use the letters or digits attributes, all letters and numbers of the string are pronounced individually. This is especially useful for spelling out the alphanumeric characters of a hexadecimal string or an identification or account number. For more information, including language-specific differences, see [The say-as element](https://cloud.ibm.com/docs/text-to-speech?topic=text-to-speech-elementssay-as_element).



 Specifying the pace at which strings are spelled out 

The spell_out_mode parameter is beta functionality that is supported only for German voices.

By default, the service reads characters that it spells out at the same rate at which it reads text for the language being synthesized. For German voices, however, you can use the optional spell_out_mode query parameter to indicate how the service is to spell out individual characters: one, two, or three at a time. The parameter applies globally to control the pace at which the service reads all strings that it spells out from a request. Use the spell_out_mode parameter only for longer strings. The parameter has no effect on a string that contains fewer than three characters.

Table 3 provides examples of how the service pronounces the following text with different values for the spell_out_mode parameter:

Die Nummer ist <say-as interpret-as=‘digits’>AB7234987FFA</say-as>.



Table 3. Using the spell_out_mode parameter for German

 Specification of the spell_out_mode parameter Audio sample 

 spell_out_mode=default <br>The service reads the characters in succession, typically with no pause between them, at the rate at which it synthesizes speech for the request. You can also omit the parameter to get the default behavior.
To send logs, creaate a file with the following content:

!/usr/bin/env python3
import os
import logging

from logdna import LogDNAHandler

apiKey = '<INGESTION-KEY>'

log = logging.getLogger('logdna')
log.setLevel(logging.INFO)

options = {
'hostname': '<HOSTNAME>',
'ip': '10.0.1.1',
'mac': 'C0:FF:EE:C0:FF:EE',
'env': 'Dallas',
'level': 'Info',
'index_meta': True,
'url': 'https://logs.us-south.logging.cloud.ibm.com/logs/ingest'
}

test = LogDNAHandler(apiKey, options)

log.addHandler(test)

log.warning("Sample message 1", {'app': 'sample-app'})
log.info("Sample message 2", {'app': 'sample-app'})
Show more

Where



* INGESTION_KEY is the key that you created in the previous step.
* The following table lists the options parameters:





Query parameters

 Query parameter Type Status Description 

 hostname string required Host name of the source. 
 mac string optional The network mac address of the host computer. 
 ip string optional The local IP address of the host computer. 
 now date-time optional The source UNIX timestamp in milliseconds at the time of the request. Used to calculate time drift. 
 tags string optional Tags that are used to dynamically group hosts. 
 url string required URL represents the entry point to the service. Each region has a different URL. To get the endpoint for a location, see [Ingestion endpoints](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-endpointsendpoints_ingestion).