vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Keep in mind that the [service](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_limitationstech_limits) limitations also apply.



Classic cluster compute limitations

 Category Description 

 Reserved instances [Reserved capacity and reserved instances](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-provisioning-reserved-capacity-and-instances) are not supported. 
 Worker node flavors Worker nodes are available in [select flavors](https://cloud.ibm.com/docs/openshift?topic=openshift-planning_worker_nodesshared_dedicated_node) of compute resources. 
 Worker node host access For security, you can't SSH into the worker node compute host. 







 Networking 

Keep in mind that the [service](https://cloud.ibm.com/docs/openshift?topic=openshift-openshift_limitationstech_limits) limitations also apply.



Classic cluster networking limitations

 Category Description 

 Ingress ALBs <br><br> * The Ingress application load balancer (ALB) can process 32,768 connections per second. If your Ingress traffic exceeds this number, [scale up the number of ALB replicas](https://cloud.ibm.com/docs/containers?topic=containers-ingress-alb-managescale_albs) in your cluster to handle the increased workload.<br> * ALBs that run the [Red Hat OpenShift on IBM Cloud custom Ingress image](https://cloud.ibm.com/docs/containers?topic=containers-managed-ingress-about) only: HTTP/2 is not supported.<br> * ALBs that run the [Red Hat OpenShift on IBM Cloud custom Ingress image] (/docs/containers?topic=containers-managed-ingress-about) only: The names of the ClusterIP services that expose your apps must be unique across all namespaces in your cluster.<br><br><br>
For more information about the number of interfaces that a virtual server supports, see [Bandwidth allocation with multiple network interfaces](https://cloud.ibm.com/docs/vpc?topic=vpc-profiles&interface=uibandwidth-multi-vnic). To utilize the increased limit for network interfaces, you can create secondary network interfaces by specifying network_interfaces when you [create an instance](https://cloud.ibm.com/apidocs/vpc/latestcreate-instance). You also can add secondary network interfaces to an existing instance by [creating a network interface on an instance](https://cloud.ibm.com/apidocs/vpc/latestcreate-instance-network-interface).

For an existing, running instance with 17 or more vCPUs to take advantage of the new network interface limits, it must be stopped and then started again. A reboot action on the running virtual server does not activate the increased network interface limit.

IBM® LinuxONE Bare Metal Servers. Accounts with access to the profiles for s390x bare metal servers can now [create](https://cloud.ibm.com/apidocs/vpc/latestcreate-bare-metal-server) LinuxONE Bare Metal Servers. These profiles have a cpu_architecture of s390x and must be used with Red Hat Enterprise Linux for s390x and SUSE Linux Enterprise Server (SLES) for s390x. For more information, see [Creating bare metal servers on VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-bare-metal-servers&interface=api).

In support of s390x bare metal servers, the following enumerations have been expanded:
No. The network load balancer does not support layer 7 switching.





 What's the maximum number of front-end listeners I can define with my load balancer? 

You can define a maximum of ten front-end listeners for an NLB.





 What's the maximum number of virtual server instances I can attach to my back-end pool? 

You can attach a maximum of 50 virtual server instances to your back-end pool for a network load balancer.





 Is an NLB horizontally scalable? 

No. A network load balancer is not horizontally scalable.





 What should I do if I'm using ACLs on the subnets that are used to deploy an NLB? 

Make sure that the proper ACL rules are in place to allow incoming traffic for configured listener ports and traffic between a network load balancer and back-end instances should also be allowed.





 What are the default settings and allowed values for health check parameters? 

The following default settings apply to network load balancer health check parameters:



* Health check interval: Five seconds, and the range is 2 - 60 seconds.
* Health check response timeout: Two seconds, and the range is 1 - 59 seconds.
* Maximum retry attempts: Two retry attempts, and the range is 1-10 retries.



The health check response timeout value must be less than the health check interval value.





 Is the network load balancer IP address fixed? 

The IP address is fixed for both public and private network load balancers. However, route mode NLBs toggle between primary and standby appliance IPs throughput their lifetime.





 Does IBM complete quarterly ASV scans of data-plane LBaaS appliances? 

Approved Scanning Vendor (ASV) quarterly scanning is a requirement of the Payment Card Industry (PCI) Security Standards Council. ASV scanning of LBaaS data-plane appliances is solely a customer responsibility. IBM does not use ASVs to scan data-plane appliances because these scans can negatively impact customer workload functions and performance.
Known limitations 

This section details some of the known limitations of DNS Services.



*  Resolvers cache permitted network details for a zone. The TTL for these cached details is typically 1 hour.
*  In custom resolvers, disabling both custom resolver locations at the same time may be possible, but is not recommended when the custom resolver is enabled.
*  DNS Services custom resolver platform metrics do not track secondary zone usage. This means that DNS queries made to a configured custom resolver for a secondary zone will not be counted in the reported metrics.
There is a [limit](https://cloud.ibm.com/docs/account?topic=account-known-issuesiam_limits) on the total number of policies that are allowed in an account. You can use a few strategies to ensure that you don't reach the limit and to reduce the amount of time that you spend managing access for the identities in your account (users, service IDs, or trusted profiles):



* Use the principle of least privilege and assign only the access that is necessary. This can help you ensure that the identities in your account are limited to only the actions that you want to allow. For example, rather than the account owner sharing their credentials, which by default give them Administrator and Manager access over all resources under their account, create new policies for users who need access to the account and to each service instance (and its associated keys).
* Add resources to a resource group to further minimize the number of necessary policies. For example, you might have a team working on a project that uses specific resources in your account. Add the team members to an access group or trusted profile with a policy that assigns access to only the resources that are in a specific resource group. This way, you don't need to assign a policy to each resource for each team member. For more information about assigning fine-grained access, check out [assign fine-grained access to a single key](https://cloud.ibm.com/docs/key-protect?topic=key-protect-grant-access-keysgrant-access-key-level).
* Use access groups to streamline managing access for identities that require the same level of access. You can set up an access group with a specific policy defined, and then add those identities to the group. If the group members need more access later on, you simply define a new policy for the access group.
* Use access management tags to control access to the resources in your account at scale. By assigning access only to resources that have specific tags that are attached to them, you can avoid multiple updates to your defined policies. For more information, see [Controlling access to resources by using tags](https://cloud.ibm.com/docs/account?topic=account-access-tags-tutorial).
Range No No Yes<br><br><br><br> * 10 unique FQDNs<br> * Overage fees incurred past 5 TB of traffic<br><br><br> Yes<br><br><br><br> * 10 unique FQDNs<br> * Overage fees incurred past 5 TB of traffic<br><br><br> Yes<br><br><br><br> * 10 unique FQDNs<br><br><br> 
 Edge functions 1 action <br>(must be named after domain) <br>1M Edge function requests Unlimited actions Unlimited actions Unlimited actions Unlimited actions 
 Protected traffic <br>(does not include traffic that is related to an attack) <br>Overage charges can occur 0.5 TB 5 TB 5 TB 5 TB 5 TB 
 Firewall rules <br><br> * 100 active rules<br> * Does not support Log action<br> * Does not support matches operator<br><br><br> <br><br> * 1000 active rules<br> * Supports all actions<br> * Supports all operators<br><br><br> <br><br> * 1000 active rules<br> * Supports all actions<br> * Supports all operators<br><br><br> <br><br> * 1000 active rules<br> * Supports all actions<br> * Supports all operators<br> * Supports bot management<br><br><br> <br><br> * 1000 active rules<br> * Supports all actions<br> * Supports all operators<br><br><br> 
 Smart routing No Yes Yes Yes Yes 
 Alerts No Yes Yes Yes Yes 
 Advanced rate limiting No No Yes Yes Yes 
 Bot management No No No Yes No 





 Deprecated plans 

The following plans are scheduled for deprecation or deprecated.



* The Standard plan reached the end of marketing on 30 April 2023. End of support is not yet determined.
* Enterprise Package, Enterprise GLB, and Enterprise Security plans will reach the end of marketing on 31 August, 2023. End of support is not yet determined.
Known limitations 

Known limitations are as follows:



* VPC networking doesn't consider the AS path length when selecting the best route for network traffic and therefore, AS prepends configured on direct links have no effect when VPCs are directly connected. However, you can use a transit gateway between the direct link and VPC in some topologies to achieve the desired effect. For more information, see [Planning considerations when using AS prepends with VPC connections](https://cloud.ibm.com/docs/dl?topic=dl-as-prepends-routes).
* Each IBM Cloud Direct Link connection requires a unique order. If you require multiple connections, open an IBM Cloud Direct Link order for each connection.
* IBM Cloud Direct Link requires BGP to establish the routes to a customer's remote network.
* Each IBM Cloud Direct Link service is not redundant. Diversity can be supplied by IBM for multiple direct links. However, customers must build redundancy in their own BGP schemes.
* If you want to connect to the classic infrastructure, be aware that IP subnet overlaps might exist and require exception approval. For more information, see [Configuring BGP](https://cloud.ibm.com/docs/direct-link?topic=direct-link-configure-ibm-cloud-direct-linkconfiguring-bgp).
* The IBM Cloud services network isn't accessible directly from your remote networks.
* IBM Cloud doesn't permit customers to back haul traffic between their remote sites across the IBM Cloud backbone. Use IBM Cloud Direct Link to let your remote networks communicate privately with your IBM Cloud infrastructure.
* IBM Cloud Direct Link requires you to use a VRF (Virtual Routing and Forwarding) instance.
* VRF isn't fully compatible with the IBM Cloud SSL and IPsec VPN services.
* The IBM Cloud fees for Direct Link Dedicated cover the cost of port termination on the IBM Cloud infrastructure. Customers are responsible for any fees that are associated with reaching the PoP from a remote network and any cross-connects needed within the PoP facility. IBM Cloud does not order a cross-connect on any customer's behalf.
For example, a single NLB cannot have a listener with a port range of 20001 - 20005 and a second listener with a port range of 20004 - 20006.
4. The member ID and member port must be unique and cannot overlap. For example, a single NLB cannot have the following configuration:



* Listener A, with a port range of 20001 - 20005
* Pool B, associated to listener A, that includes member C with a port range of 20001 - 20005
* Listener D, with a single port of 20006
* Pool E, associated to listener D, that includes member C with a single port of 20004



Note that, member C uses port 20004 in two different listeners. This is not allowed.

To help illustrate this limitation, refer to the following diagram.

Zoom

![Port range configuration](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/vpc/images/port_range_customer_doc.jpg)

Port range configuration
5. When you enable a port range for the listener, the data traffic of its members flows through all the ports in that range as well. If the pool health check port is not configured, the member port is used only as a health check port.
Via: SIP/2.0/UDP agenta.atlanta.example.com;branch=z9hG4bK2293940223
To: <sip:b@atlanta.example.com>
From: <sip:a@atlanta.example.com>;tag=193402342
Call-ID: 898234234@agenta.atlanta.example.com
CSeq: 93809823 REFER
Max-Forwards: 70
Refer-To: sip:user@domain.com?User-to-User=637573746f6d2d757365722d746f2d75736572%3Bencoding%3Dhe&X-Watson-Assistant-Session-History-Key=dev::latest::893499::dff9c274-adc4-4f63-93de-781166760bf8::978f1fd7-4e24-47d8-adb0-24a8a6eff69e::b5ffd6c2-902f-4658-b586-e3fc170a6cf3::7ad616a350cc48078f17e3ee3df551de
Contact: sip:a@atlanta.example.com
Content-Length: 0







 Playing hold music or a voice recording 

To play hold music or to play a recorded message, use the audio response type. This response type can be specified in a dialog node or action step using the JSON editor.

You cannot play hold music during a call transfer. However, you might want to play hold music if your assistant needs time to perform processing of some kind, such as calling a client-side action or making a call to a webhook.

The phone integration supports the following properties for the audio response type:



 Property Description 

 source The URL of a publicly-accessible .wav audio file. The audio file must be single channel (mono) and PCM-encoded, and must have an 8,000 Hz sampling rate with 16 bits per sample.
--limit (int64)
: The number of locks to retrieve. By default, list operations return the first 25 items. To retrieve a different set of items, use limit with offset to page through your available resources.

Usage: If you have 20 locks associated with your secret, and you want to retrieve only the first 5 locks, use ..?limit=5.

The maximum value is 100. The minimum value is 1.

--offset (int64)
: The number of locks to skip. By specifying offset, you retrieve a subset of items that starts with the offset value. Use offset with limit to page through your available resources.

Usage: If you have 100 locks on your secret, and you want to retrieve locks 26 through 50, use ..?offset=25&limit=25.

The minimum value is 0.

--search (string)
: Filter locks that contain the specified string in the field "name".

Usage: If you want to list only the locks that contain the string "text" in the field "name", use ..?search=text.

The maximum length is 64 characters.





 Examples 

ibmcloud secrets-manager locks --secret-type=arbitrary --id=exampleString --limit=1 --offset=0 --search=exampleString





 Example output 

Example response for listing the locks that are assosiated with a specified secret.

{
"metadata" : {
"collection_type" : "application/vnd.ibm.secrets-manager.secret.lock+json",
"collection_total" : 2
},
"resources" : [ {
"name" : "lock-1",
"description" : "lock for consumer-1",
"creation_date" : "2020-08-27T14:28:54Z",
"created_by" : "IBM-id-1",
"attributes" : {
"key" : "value"
},
Worker node host access For security, you can't SSH into the worker node compute host. 







 Networking 

Keep in mind that the [service](https://cloud.ibm.com/docs/containers?topic=containers-limitationstech_limits) limitations also apply.



Classic cluster networking limitations

 Category Description 

 Ingress ALBs <br><br> * The Ingress application load balancer (ALB) can process 32,768 connections per second. If your Ingress traffic exceeds this number, [scale up the number of ALB replicas](https://cloud.ibm.com/docs/containers?topic=containers-ingress-alb-managescale_albs) in your cluster to handle the increased workload.<br> * ALBs that run the [IBM Cloud Kubernetes Service custom Ingress image](https://cloud.ibm.com/docs/containers?topic=containers-managed-ingress-about) only: HTTP/2 is not supported.<br> * ALBs that run the [IBM Cloud Kubernetes Service custom Ingress image] (/docs/containers?topic=containers-managed-ingress-about) only: The names of the ClusterIP services that expose your apps must be unique across all namespaces in your cluster.<br><br><br> 
 Istio managed add-on See [Istio add-on limitations](https://cloud.ibm.com/docs/containers?topic=containers-istio-aboutistio_limitations). 
 Network load balancers (NLB) <br><br> * You can't update an existing NLB from version 1.0 to 2.0. You must create a new NLB 2.0.<br> * You can't create subdomains for private NLBs.<br> * You can register up to 128 subdomains. This limit can be lifted on request by opening a [support case](https://cloud.ibm.com/docs/get-support?topic=get-support-using-avatar).<br><br><br>
Setting the number of allowed concurrent sessions 

You can choose the maximum number of concurrent sessions that are allowed for your account users. Concurrent sessions are active sessions that the user is signed into at one time. Users can have multiple sessions open by using different browsers or several logins with the IBM Cloud CLI. Multiple concurrent sessions are more beneficial for parallel workloads.



1. In the IBM Cloud console, click Manage > Access (IAM), and select Settings.
2. From the Concurrent sessions tile, click the Edit icon ![Edit icon](https://cloud.ibm.com/docs-content/v1/content/4d8c6eec891cff72b666dc24bd3211810c77fb42/icons/icon_write.svg), click the Unlimited dropdown > Limit sessions.
3. Enter the limit. Users can have an unlimited number of concurrent sessions.
4. Click Save.







 Setting the number of allowed concurrent sessions by using Terraform 

You can choose the maximum number of concurrent sessions that are allowed for your account users. Concurrent sessions are active sessions that the user is signed into at one time. Users can have multiple sessions open by using different browsers or several logins with the IBM Cloud CLI. Multiple concurrent sessions are more beneficial for parallel workloads.

To update your user's allowed number of concurrent sessions by using terraform, complete the following steps:



1. Create an argument in your main.tf file. The following example sets the number of allowed concurrent sessions by using the ibm_iam_account_settings and iam_account_settings_instance resources.
2. Enter the period of time in seconds in which you want a session to invalidate due to inactivity. Supported valid values are



* Any whole number greater than '0'.
* Use NOT_SET to unset account setting and use service default.



resource "ibm_iam_account_settings" "iam_account_settings_instance" {
max_sessions_per_identity = "3"
}
3.
If the assistant is unable to send an SMS message to the caller, a new turn is initiated with the text input vgwSMSFailed. This input indicates that an SMS message could not be sent the caller. You can design your dialog or actions to handle such a failure by creating intents or actions that are triggered by the input text vgwSMSFailed.

{
"input": {
"message_type": "text",
"text": "vgwSMSMessage"
},
"context": {
"skills": {
"main skill": {
"user_defined": {
"vgwSMSMessage": "1545 Lexington Ave."
}
}
}
}





 Defining a sequence of phone commands 

If you want to run more than one command in succession, include multiple responses in the output.generic array. These commands are processed in the order in which they are specified in the array.

This example shows two responses: first a text response, followed by an end_session response to end the call.

{
"output": {
"generic": [
{
"values":
{
"text": "Goodbye."
}
],
"response_type": "text",
"selection_policy": "sequential"
},
{
"response_type": "end_session"
}
]
}
}
Show more
A valid number format follows the [E.164 international numbering format](https://en.wikipedia.org/wiki/E.164). For example, a US number takes the form +19998887777. You must specify both the country code, starting with a + symbol and the national subscriber number. In some countries, Vonage supports alpha-numeric sender IDs. App ID uses the value that you enter as Vonage's sender ID. So, if they are supported by Vonage, you can use the IDs with App ID.









 With the APIs 

Before you get started with the API, be sure that you have the following prerequisites:



* Your App ID instance's tenant ID. This ID can be found in the Service Credentials section of the dashboard.
* Your Identity and Access Management (IAM) token. For help with obtaining an IAM token, check out the [IAM docs](https://cloud.ibm.com/docs/account?topic=account-iamtoken_from_apikey).





1. Enable MFA by making a PUT request to the /config/cloud_directory/mfa endpoint with your MFA configuration to set isActive to true.

curl -X PUT https://<region>.appid.cloud.ibm.com/management/v4/<tenantID>/config/cloud_directory/mfa --header 'Content-Type: application/json' --header 'Accept: application/json' --header 'Authorization: Bearer <IAMToken>' -d '{"isActive": true}'
2. Enable your MFA channel by making a PUT request to the /mfa/channels/<channel> endpoint with your MFA configuration. When isActive is set to true, your MFA channel is enabled. The config takes in the Nexmo API key and secret as well as the from number.
Performance limitations for security groups 

Some performance limitations exist for security groups and their associated rules.



Table 1. Performance limitations for specific resources

 Resource                               Limit 

 Security groups per network interface  5     
 Security groups per account            500   
 Rules per security group               50    
 Remote rules per security group        5     
 Network interfaces per security group  100   



A remote rule is one that specifies a security group as the source or destination.
In the following example output, the last line displays the total number of rules:

% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 3422 100 3422 0 0 7830 0 --:--:-- --:--:-- --:--:-- 7830
4





 Viewing the total number of rules per account by using the CLI 

To get the total number of rules per account, use the Context-based restrictions CLI:

ic cbr rules --output json | jq '.rules | length'

The following example output displays the total number of rules:

4







 Requesting a policy and rule shared limit increase 

You can request a limit increase for the total number of policies and rules that are allowed in the account only if the following criteria is met:



* You must be the account owner or an administrator on all account management services.
* Access groups are currently used to limit the overall number of policies in the account.
* Use policies for resources grouped by resource group.
* You have taken efforts to clean up and reduce the number of policies in the account.
* You have taken efforts to clean up and reduce the number of rules in the account.



IAM policies and context-based restrictions rules share a combined limit.

If you meet all of the listed criteria, you can request a policy limit increase by submitting a support case in the [console](https://cloud.ibm.com/unifiedsupport/cases/add). In the case, provide all of the following information. Each piece of information is required for processing and approval of your request.



* Case title of Request to increase account policy limit
* The use case for the extra policies
* Information on all efforts taken to follow the [Best practices for organizing resources and assigning access](https://cloud.ibm.com/docs/account?topic=account-account_setuphow_access) to reduce the number of policies on the account
* Account ID
* Note how many extra policies in the account are required
* If you are requesting an increase per subject, note how many extra policies per subject are required