vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Under Sites, select the existing site you want to use this trunk with. To create a new site, specify a name and location and click Create.
12. Click Number plans. Create a new number plan and specify the following information:



* In the Number Plan Name field, type a descriptive name (for example, Watson).
* For Match type, select E. 164 Number List.
* In the Numbers field, type a number in the Start and End fields. This does not need to be a real number; you can make up any number to use as an identifier to assign to Watson. Specify the same number in both fields.

To create a PSTN number you can give to your clients, you must create a Direct Inward Dialing (DID) or Bring Your Own Carrier (BYOC) number. For more information about how to do this, see the Genesys documentation.
* In the Classification field, type a classification name (for example, Watson).



Click Save Number Plans.

![Genesys number plan](https://cloud.ibm.com/docs-content/v1/content/417db917d18067d9dcc4cf2612564a9a87c3ddc8/assistant/images/phone-genesys-number-plan.png)
13. Click Outbound Routes. You can either edit the default outbound route or create a new one. Specify the following information:



* In the External Trunks field, click Select External Trunks. Select the trunk you created for Watson Assistant.
* In the Classifications field, add the applicable classifications. This should at least include National and the classification you created for Watson Assistant earlier. (The National route is used only to simulate the call in order to make sure the trunk is operational.)
* Toggle the State switch to Enabled.



!
* [Trigger rate limits](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-limitslimits_triggers)
* [Increasing fixed limits](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-limitslimits_fixed)
* [Cloud Functions entities](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-limitslimits_entities_ov)



* [Namespaces and packages](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-limitslimits_namespaces)
* [Fully qualified names in Cloud Functions](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-limitslimits_fullnames)



* [Action semantics](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-limitslimits_semantics)



* [Statelessness](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-limitslimits_stateless)
* [Invocation input and output](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-limitslimits_invocationio)
* [Invocation ordering of actions](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-limitslimits_ordering)
* [Action executions](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-limitslimits_exec)



* [Activation record](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-limitslimits_activation)







 Error handing for Cloud Functions 

[Error handing for Cloud Functions](https://cloud.ibm.com/docs/openwhisk?topic=openwhisk-error-handing-functionserror-handing-functions)
Private VLANs only Private network load balancers (NLBs) can't be registered with the domain name server (DNS), so the cluster can't be created with only a private network interface. Worker nodes must be connected to both public and private VLANs. You can still create a private service to expose your apps on only the private network. 
 Service endpoints When you create a cluster, you can enable the public and private cloud service endpoint or the public cloud service endpoint only, but you can't enable the private cloud service endpoint only. After cluster creation, you can't later change the service endpoints. 
 strongSwan VPN service See [strongSwan VPN service considerations](https://cloud.ibm.com/docs/openshift?topic=openshift-vpnstrongswan_limitations). 
 Service IP addresses You can have 65,000 IP addresses per cluster in the 172.21.0.0/16 range that you can assign to Kubernetes services within the cluster. 
 Subnets per VLAN Each VLAN has a limit of 40 subnets. 







 Storage 

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



Classic cluster storage limitations

 Category Description 

 Volume instances You can have a total of 250 IBM Cloud infrastructure file and block storage volumes per account. If you mount more than this amount, you might see an "out of capacity" message when you provision persistent volumes. For more FAQs, see the [file](https://cloud.ibm.com/docs/FileStorage?topic=FileStorage-file-storage-faqsprovision) and [block](https://cloud.ibm.com/docs/BlockStorage?topic=BlockStorage-block-storage-faqsauthlimit) storage docs. If you want to mount more volumes, [contact IBM Support](https://cloud.ibm.com/docs/get-support?topic=get-support-using-avatar).
An application contains one or more revisions. Each update of an application configuration property creates a new revision of the application. Code Engine has a quota for the number of apps and app revisions in a project. For more information about limits for projects, see [Project quotas](https://cloud.ibm.com/docs/codeengine?topic=codeengine-limitsproject_quotas).



Table 9: Number of revisions per application

 Metadata Description 

 Metric Name ibm_codeengine_application_revision_count 
 Metric Type gauge 
 Value Type none 
 Segment By Service instance, name of the namespace, project name, application name 







 ibm_codeengine_application_service_count 

Number of applications per project.

Use this metric to observe how many applications are in your project.

Code Engine has a quota for the number of apps and app revisions in a project. For more information about limits for projects, see [Project quotas](https://cloud.ibm.com/docs/codeengine?topic=codeengine-limitsproject_quotas).



Table 10: Number of applications per project

 Metadata Description 

 Metric Name ibm_codeengine_application_service_count 
 Metric Type gauge 
 Value Type none 
 Segment By Service instance, name of the namespace, project name, application name 







 ibm_codeengine_application_route_count 

Number of routes per application.

Code Engine supports only 1 route per application.



Table 11: Number of routes per application

 Metadata Description 

 Metric Name ibm_codeengine_application_route_count 
 Metric Type gauge 
 Value Type none 
 Segment By Service instance, name of the namespace, project name, application name 







 ibm_codeengine_application_target_concurrency_per_pod 

The number of concurrent requests that you want for each pod.

Use this metric to observe the target concurrency value that is set for your application.

Target concurrency for application scaling is configurable. See [Configuring application scaling](https://cloud.ibm.com/docs/codeengine?topic=codeengine-app-scale).
Customers can achieve 99.99% effectively with two or more Direct Links that are properly configured for failover by using BGP, but IBM cannot control that or provide an SLA on it.





 Where can I get help setting up a Direct Link? 

For connecting to Direct Link, see [Configuring IBM Cloud Direct Link](https://cloud.ibm.com/docs/direct-link?topic=direct-link-configure-ibm-cloud-direct-link). If you need more help, you can request engineering support in the case that was opened for the new service. Even if it is an API service with Equinix, opening a case enables an engineer to look at it. Or you can contact your IBM Sales representative.





 On Direct Link Exchange, does IBM set a BGP password? 

BGP passwords for Direct Link Exchange aren't set up, by default. There is an option to specify BGP ASN and we assign BGP IP addresses. Also, it's possible to set up a BGP password for authentication purposes, we just need to let the engineers know.
Port speed options: Select 1 Gbps, 2 Gbps, 5 Gbps, or 10 Gbps.

Approximate latency: Latency is approximately 0.5 ms within the local data center.

IBM colocation services: Yes.

Redundancy: IBM Cloud provides connections to two diverse cross-connect routers (XCRs) as part of the product. To establish redundant connectivity, customers must configure BGP on each Direct Link on Classic connection as they prefer. Examples include options such as these: prefer Lowest MED, prefer highest local-preference, or prefer shorter AS paths.

Local and global routing options: The default routing option is Local routing. It provides access to data centers within the same Market as the Direct Link PoP (denoted, for example, as DAL, AMS, or MEL). The Global routing option is required as an add-on to connect your IBM Cloud resources to other IBM Cloud resources in data centers outside the local market. It is used to share workloads between IBM Cloud resources (for example Dallas to Ashburn, or Dallas to Frankfurt).

Third-party, cross-connect add-on:



* Customer can order an additional third-party, cross connect for carrier connections.
* Customer is responsible for ordering the circuit directly from the carrier and for providing the LOA/CFA (Letter of Authorization – Carrier Facility Assignment) to the colocation provider.
* Carrier availability might vary by location.



Zoom

![Cross-Connect Router (XCR)](https://cloud.ibm.com/docs-content/v1/content/d7287ec7418d843dbd7caf286d842c439df6979e/direct-link/images/dedicated_hosting.png)

Figure 5. Cross-Connect Router (XCR)

Use cases:



* Additional cross connects are requested to the MMR to service ISP/Telco links, connect to other CSPs, or colocation tenants.
* DLDH customer procures services and LOA/CFA from third party.
* DLDH customer supplies third party LOA/CFA to colocation provider for cross-connect order.







 The Direct Link Exchange on Classic solution
If you require redundancy through the Direct Link service, you can purchase two separate Direct link connections in a single IBM Cloud network PoP on two separate routers, or you can order two single connections into two geographically diverse Direct Link PoP locations. It is your responsibility to configure the routing protocols to ensure resiliency between the two links.
5. IBM Cloud will not allow customers to backhaul traffic between their remote sites across the IBM Cloud backbone.

The Direct Link product is meant for your remote networks to be able to privately communicate with your IBM Cloud infrastructure.
6. Be aware if you use Classic IaaS, that infrastructure uses the 10.x.x.x network and you cannot overlap your on-premises hosts within IBM Cloud or with the IBM Cloud services network (10.0.0.0/14, 10.198.0.0/15, and 10.200.0.0/14).
7. Virtual Routing and Forwarding (VRF) is not compatible with IBM Cloud SSL and IPsec VPN services. An alternative is to use the Direct Link itself for management of your servers, or run your own VPN solution (such as a Vyatta) that can be configured with different types of VPNs.

After migrating to a VRF, SSL VPN typically works when a VPN connection is made to the same data center location as the compute that's being accessed, but does not allow access globally.
8. Direct Link Cloud requires Border Gateway Protocol (BGP) to implement routes to a customer's remote network.
9. If you choose to use auto-assign IP addressing, IBM will assign two IP addresses from this network, 169.254.0.0/16 for the BGP point-to-point addresses.

IBM will use the first IP address in the /30 subnet. The customer can use the second IP address from this subnet.
The ports that end with 1-1 and 1-2 belong to one port group, and the ports ending with 2-1 and 2-2 belong to another port group. If you select a port from the first port group, you must select a port from the second port group for the redundant Direct Link Connect instance. That is, if you select -1-1 for the first Direct Link Connect instance, you must select -2-1 or -2-2 for the second Direct Link Connect instance.

Zoom

![BGP and connections](https://cloud.ibm.com/docs-content/v1/content/1d36273917990fbf48078805e201d2e85e2fcb27/power-iaas/images/bgp-connections.png)

Figure 1. BGP and connections

Border Gateway Protocol (BGP) sessions are configured for the Direct Link Connect service in such a way that when a fault is detected on a Direct Link Connect instance, the BGP routes traffic to an alternate Direct Link Connect instance. For 10 Gbps connections, use the new ports that are not GRE capable. Ports that are GRE capable can use only up to a 5 Gbps speed.

Refer to the following table to identify the ports and port groups that you must select for the redundant Direct Link Connect instance:



Table 2. Port and Port groups for redundant Direct Link instances

 Data center Network provider Port group 1 Port group 2 for redundancy 

 LON04 IBM Power VS IBM POWER VS-CLOUD EXCHANGE SL-LON04-1-1 <br>IBM POWER VS-CLOUD EXCHANGE SL-LON04-1-2 IBM POWER VS-CLOUD EXCHANGE SL-LON04-2-1 <br>IBM POWER VS-CLOUD EXCHANGE SL-LON04-2-2
If you encounter this phenomenon, check the [IBM Cloud® status page](https://cloud.ibm.com/status?component=block-storage&selected=status) to see whether a current event might impact your host's ability to access the storage. If no events are reported, perform the discovery scan again to ensure that all paths are properly discovered. If an event is in progress, the storage can be attached with a single path. However, it's essential that paths are rescanned after the event is completed. If both paths are not discovered after the rescan, [create a support case](https://cloud.ibm.com/unifiedsupport/cases/add) so it can be properly investigated.
<br>Ensuring that there are no IP address conflicts between on-premises subnets, and subnets on IBM Cloud for both VPC and classic infrastructure connections. 
 Fulfillment IBM fulfills requests for Direct Link connections and additional capacity based on use. The Customer is responsible for monitoring service notifications for communications regarding maintenance operations. The Customer is also responsible for uploading the Completion notice from their service provider when Cross Connect is completed by the chosen service provider. 
 Partnership IBM provides partner relationships with physical locations for Direct Link interconnects. The Customer is responsible for ordering connectivity services from appropriate partner. 
 Performance IBM does not have a Service Level Agreement (SLA) today. A Customer can achieve 99.99% effectively with two or more direct links that are properly configured for failover by using BGP, but IBM cannot control that, or provide an SLA on it. The Customer is responsible for opening tickets in the event of an outage to track performance. 
 IP addressing IBM assigns the subnets to VPCs specified by the Customer. The Customer is responsible for ensuring no IP overlap on their on-premises subnet. 







 Change management 

Change management includes tasks, such as deployment, configuration, upgrades, patching, configuration changes, and deletion.



Table 2. Responsibilities for change management

 Task IBM Responsibilities Your Responsibilities 

 Major version upgrades IBM is responsible for providing availability and tooling for major version updates. The Customer is responsible for migrating to a supported version before end-of-support for an old version. 
 API version changes IBM is responsible for versioning the REST APIs. The Customer is responsible for integrating with the desired version of REST APIs. 
 Scaling IBM is responsible for scaling infrastructure as requested and to meet the capacity that you selected. The Customer is responsible for ordering the appropriate Direct Link port speed in the IBM Cloud console. 
 Updates, fixes, and new features IBM is responsible for providing regular updates, bug fixes, and new features, following a continuous delivery model in a way that is transparent to you. Notifications are posted for changes that impact you. The Customer is responsible for reading system-generated notifications and taking appropriate action. 







 Traffic management 

Traffic management includes tasks, such as bandwidth monitoring, packet inspection, forwarding detection, and traffic routing.



Table 3.
With an Exchange service, customers can enable multi-cloud connectivity to their colocation rapidly because the underlying circuits are provisioned already (these other cloud providers must already have a physical interconnection present within the facility).

Direct Link Exchange can allow for a multi-cloud, shared-use environment through a single cloud exchange port, created by an NNI connection at Layer 2 between IBM Cloud and the Cloud Exchange Service Provider. Port speeds are available up to 5 Gb.

Direct Link Connect is for customers who prefer to use their existing network between their own on-premises deployment and IBM Cloud. With a Direct Link Connect service, customers can use new and existing Telco networks (such as MPLS) to enable IBM Cloud rapidly, by using pre-provisioned underlying circuits.

With Direct Link Connect, customers can connect to IBM Cloud through the Connect provider, over a Network-to-Network Interface (NNI) connection, operated by IBM partners in facilities worldwide. Port speeds are available up to 5 Gb.
* How do Direct Link Connect and Direct Link Exchange providers compare?

Connect providers are Telcos who have network reach beyond the data center. Exchange providers are limited to their data centers. Both can enable the multi-cloud experience for customers. Exchange providers usually require colocation in their data centers, while Connect providers can reach a customer's on-premises site and data centers.
* Can IBM Support IPv6 over Direct Link?

Not for the BGP Session. We must assign our /30 from IPv4, and we need the same in return from the customer.
* Can IBM do IPV6 on the private network?

No. IPv6 is public only.
* Are there any special Direct Link requirements for Verizon SCI? Prefix / ASN / VLAN BGP / and so forth?

Verizon SCI is one of several MPLS based, Layer-3 (IP VPN) services. It requires that IBM establish BGP with Verizon instead of directly with the customer. Verizon then establishes BGP with the customer and advertises routes accordingly. Several other Layer-3 based service providers participate in the Direct Link Connect program. Customers need to be aware of what they are ordering and how their account will behave when connecting to IBM Cloud.
(https://cloud.ibm.com/docs/openshift?topic=openshift-cs_vpn_failscs_vpn_fails)

[Why can't I install a new strongSwan Helm chart release?](https://cloud.ibm.com/docs/openshift?topic=openshift-cs_strongswan_releasecs_strongswan_release)

[Why does strongSwan VPN connectivity fail after I add or delete worker nodes?](https://cloud.ibm.com/docs/openshift?topic=openshift-cs_vpn_fails_worker_addcs_vpn_fails_worker_add)

[Why do OpenSSL connections to Let's Encrypt fail after 30 September 2021?](https://cloud.ibm.com/docs/openshift?topic=openshift-ts-letsencryptts-letsencrypt)

[Debugging Calico components](https://cloud.ibm.com/docs/openshift?topic=openshift-calico_log_levelcalico_log_level)



* [Increasing the log level for the calico-typha components](https://cloud.ibm.com/docs/openshift?topic=openshift-calico_log_levelcalico-increase-logging-typha)
* [Increasing the log level for the calico-cni components](https://cloud.ibm.com/docs/openshift?topic=openshift-calico_log_levelcalico-increase-logging-cni)
* [Increasing the log level for the calico-node components](https://cloud.ibm.com/docs/openshift?topic=openshift-calico_log_levelcalico-increase-logging-node)
* [Increasing the log level for the calico-kube-controllers components](https://cloud.ibm.com/docs/openshift?topic=openshift-calico_log_levelcalico-increase-logging-kube-controllers)
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.
* IBM Cloud does not colocate any customer equipment in our network PoPs. Customers must work with their provider to determine whether they need to colocate any equipment in the facility where the IBM Cloud network PoP exists.







 Direct Link Dedicated Hosting on Classic limitations 



* Direct Link Dedicated Hosting requires a specific contract between IBM Cloud and the customer. This contract outlines the terms and conditions for the product, the pricing for the colocation environment, and the term commitment for the services. A 6-, 9-, or 12-month contract is required.
* Provider connectivity is limited to the On-Net providers of the selected data center.







 Direct Link Exchange on Classic limitations 



* Customers are responsible for any fees that are associated with reaching the PoP from a remote network and any fees that are incurred with the Cloud Exchange provider.
* IBM Cloud does not colocate any customer equipment in our network PoPs. Customers must work with their provider to determine whether they need to colocate any equipment in the facility where the IBM Cloud network PoP exists.
* Direct Link Exchange availability varies between locations. Customers can contact their IBM Cloud account manager to confirm current or future availability.
Alternatives for your Direct Link on Classic deployment 

Here are alternatives that customers sometimes choose as use cases for their Direct Link on Classic deployments.



 Diverse deployments for Connect and Exchange on Classic 

The default deployments of Direct Link Connect and Direct Link Exchange on Classic do not include redundant configuration, although they can be deployed diversely on discrete routers.

Many customers choose to create redundant deployments by setting up an additional Direct Link connection. This document presents some schematic representations of alternative Direct Link on Classic deployments.

Zoom

![Diverse Exchange](https://cloud.ibm.com/docs-content/v1/content/d7287ec7418d843dbd7caf286d842c439df6979e/direct-link//images/Direct-Link-Exchange-Diverse.png)

Figure 1. A diverse IBM Cloud Direct Link Exchange deployment

IBM Cloud Direct Link also makes it easy to establish diverse Connect deployments, as shown in the following figure.

Zoom

![Diverse Connect](https://cloud.ibm.com/docs-content/v1/content/d7287ec7418d843dbd7caf286d842c439df6979e/direct-link//images/Direct-Link-Connect-Diverse.png)

Figure 2. A redundant and diverse IBM Cloud Direct Link Connect on Classic deployment





 Using Connect and Exchange on Classic along with other clouds 

Some customers want to use Direct Link Connect on Classic along with other cloud providers, such as AWS, Azure, or Google Cloud. The following schematic shows an overview of how to establish this type of connection with a Telco (NSP).

Zoom

![Other Clouds Connect](https://cloud.ibm.com/docs-content/v1/content/d7287ec7418d843dbd7caf286d842c439df6979e/direct-link//images/Direct-Link-Connect-other-clouds.png)

Figure 4. Using Direct Link Connect in conjunction with other clouds