vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* ibmcloud is vpn-gateway-connection-create my-connection fee82deba12e4c0fb69c3b09d1f12345 169.21.50.5 lkj14b1oi0alcniejkso --local-cidr 10.240.0.0/24 --peer-cidr 192.168.1.0/24 --ike-policy 72251a2e-d6c5-42b4-97b0-b5f8e8d1f479
* ibmcloud is vpn-gateway-connection-create my-connection fee82deba12e4c0fb69c3b09d1f12345 169.21.50.5 lkj14b1oi0alcniejkso --local-cidr 10.240.0.0/24 --local-cidr 10.240.1.0/24 --peer-cidr 192.168.1.0/24 --peer-cidr 192.168.2.0/24 --output JSON







 Command options 



* CONNECTION_NAME: Name of the connection.
* VPN_GATEWAY: ID or name of the VPN gateway.
* PEER_ADDRESS: The IP address of the peer VPN gateway.
* PRESHARED_KEY: The preshared key.
* --vpc: ID or name of the VPC. It is only required to specify the unique resource by name inside this VPC.
* --admin-state-up: If set to false, the VPN gateway connection is shut down. One of: true, false. (default: true).
* --dead-peer-detection-action: Dead Peer Detection actions. One of: restart, clear, hold, none. (default: restart).
* --dead-peer-detection-interval: Dead Peer Detection interval in seconds (default: 2).
* --dead-peer-detection-timeout: Dead Peer Detection timeout in seconds (default: 10).
* --ike-policy: ID or name of the IKE policy.
Why is my IBMid not associated with any IBM Cloud accounts? 

Your IBMid must be associated with an IBM Cloud® account.

  What’s happening 

When you log in to IBM Cloud, the following message is displayed:

> You have reached this page because your authentication was successful, however, this IBMid is not associated with any IBM Cloud accounts.

  Why it’s happening 

You logged in from the [IBM Cloud console](https://cloud.ibm.com/) with a valid IBMid, but you don't have an IBM Cloud account.

  How to fix it 

Create an IBM Cloud account by following the sign-up process.
* You will identify IBM Cloud as the sponsoring registrar upon inquiry from the customer.
* You agree to inform any customer of Yours, who may be acquiring a domain name through You using IBM Cloud’s registration services, that they are in fact registering their domain name through IBM Cloud and that IBM Cloud is an accredited registrar with ICANN.
* You will comply with any ICANN-adopted Specification or Policy that establishes a program for accreditation of individuals or entities who provide proxy and privacy registration services (a “Proxy Accreditation Program”).
* You will provide Your customers with a link to the ICANN webpage detailing registrant educational information, as follows: [https://www.icann.org/resources/pages/responsibilities-2014-03-14-en](https://www.icann.org/resources/pages/responsibilities-2014-03-14-en).
* That in the event IBM Cloud learns that You are causing IBM Cloud to be in breach of any of the provisions of the Registrar Accreditation Agreement, IBM Cloud will take reasonable steps to enforce this Agreement so as to cure and prevent further instances of non-compliance.
* You will provide Your customers access to the ICANN Registrant’s Benefits and Responsibilities Specification and will not take any actions inconsistent with them.







 Restriction of Services; Right of Refusal 

You agree not to use the Services, or to allow or enable others to use the Services, for the purposes of:



* The transmission of unsolicited email (Spam).
* Repetitive, high volume inquiries into any of the services provided by IBM Cloud (i.e. domain name availability, etc.).
* If You are hosting Your domain's name servers ("DNS") on IBM Cloud's servers, or are using IBM Cloud’s systems to forward a domain, URL, or otherwise to a system or site hosted elsewhere, or if You have Your domain name registered with IBM Cloud, You are responsible for ensuring that there is no excessive overloading on IBM Cloud's DNS systems.
* You may not use IBM Cloud's servers and/or Your domain as a source, intermediary, reply-to address, or destination address for mail bombs, Internet packet flooding, packet corruption, server hacking, security breaches or other abusive attacks.
Message: The provided CIDR does not fit in any of the address prefixes in the provided zone.

This error occurs if a user is trying to create a subnet with a CIDR that does not fall into any address prefixes for the given zone.

Run GET /vpcs/{vpc_id}/address_prefixes to get the list of address prefixes for the VPC. If using the CLI, you can run ibmcloud is vpc-address-prefixes to list all address prefixes for your VPC. Look at the cidr and zone values of the response and make sure the subnet's cidr is a subset of the cidr of the address prefix for the zone you are trying to create it.





 no_default_address_prefix 

Message: The zone must have a default address prefix to create a subnet using total_address_count.

This error occurs if a user is trying to create a subnet by address count and no default address prefix is available in the given zone.





 operating_system_restricted 

Message: You cannot use this operating system to create a custom image.

The referenced operating system is restricted for use with system images only. Select a different operating system and retry your request.





 over_quota 

Message: The request would exceed the quota for a resource type.

The quotas per resource are specified in [Quotas and limits for VPC](https://cloud.ibm.com/docs/vpc-on-classic?topic=vpc-on-classic-quotas).





 password_not_ready 

Message: None

Your instance must be running before you can retrieve the password. 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).





 pool_delete_conflict 

Message: Pool cannot be deleted because it is still associated with one or more listeners.

Ensure the pool is disassociated from any listeners and try again.





 pool_duplicate_name 

Message: Pool name <pool_name> is already used by another pool.
Error message: Can't start instance in the placement group

Your virtual server instance didn't start because the instance doesn't have enough available resource capacity in the instance group to start. To address this error, try the follow possible resolutions:



* Stop and restart the instance.
* Resize to a smaller instance profile.
* Delete the failed instance and create an instance in another availability zone.
* Remove the instance from the placement group and restart the instance.



If you still need help with the error, contact [support](https://cloud.ibm.com/docs/vpc?topic=vpc-getting-help).

For more information about managing your virtual server instance and placement groups, see the following topics:



* [Managing virtual server instances](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-virtual-server-instances)
* [Managing placement groups](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-placement-group)







 Error: cannot_start_compute 

Error message: Can't start instance because provisioning failed

Your virtual server instance did not start because of an unexpected failure. To address this error, try the follow possible resolutions:



* Stop and restart the instance.
* Delete the instance and try again.



If you still need help with the error, contact [support](https://cloud.ibm.com/docs/vpc?topic=vpc-getting-help).

For more information, see [Managing virtual server instances](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-virtual-server-instances)





 Error: cannot_start_network 

Error message: Can't start instance because network resources can't be provisioned

Your virtual server instance did not start because of a network resource failure. To address this error, try the follow possible resolutions:



* Stop and restart the instance.
* Delete the instance and try again.
Message: The value is not a valid IPv4 address.

Provide a valid IPv4 address.





 validation_invalid_ipv6_address 

Message: The value is not a valid IPv6 address.

Give a valid IPv6 address. Currently, IPv6 is not supported; use an IPv4 address.





 validation_invalid_field_type 

Message: The value type does not match the field type.

To fix this problem, be sure the content of your request conforms to the [API documentation](https://cloud.ibm.com/apidocs/vpc-on-classic) for the endpoint you are calling.





 validation_max_value 

Message: A value provided for a parameter is larger than allowed.

Provide a smaller value that meets the maximum as given by the [API documentation](https://cloud.ibm.com/apidocs/vpc-on-classic).





 validation_min_value 

Message: A value provided for a parameter is smaller than allowed.

You may get this error if you try to create a subnet with total_ipv4_address_count less than 8.

Provide a larger value that meets the minimum as given by the [API documentation](https://cloud.ibm.com/apidocs/vpc-on-classic).





 validation_not_null 

Message: The field supplied must be null.

Be sure the value is null. Refer to the [API documentation](https://cloud.ibm.com/apidocs/vpc-on-classic).

Here is an invalid example:

{
"name": null
}





 validation_only_one 

Message: The value must match one of the subschemas.

Make sure your request conforms to the [API documentation](https://cloud.ibm.com/apidocs/vpc-on-classic).





 validation_discriminator_forbidden 

Message: The discriminator field forbids this substructure.

For example, if you specify

{
protocol: icmp
port_min: 5
port_max: 100
}
Why is my origin status down? 

You checked the status of your origin, and it's down.

  What’s happening 

Your origin status is down. It might be for one or more of the following reasons.



  Initial health check might not be complete 

Your origin might be down because the initial health check has not finished yet.

  How to fix it 

Wait for the health check interval to pass before checking again.





  Security groups might not have been added yet 

Your origin might be down because the security group rules have not been added yet.

  How to fix it 

Be sure the [security group rules](https://cloud.ibm.com/docs/dns-svcs?topic=dns-svcs-global-load-balancerssecurity-groups-glb) have been added.





  Application error 

Your origin might be down because the application responsible for responding to the health check queries might not be running properly or on the correct port.

  How to fix it 

Verify that the application is running on the correct port, and is operating properly.





  Incorrect type selected for health check type 

Your origin might be down because you specified HTTPS as your type of health check.

  How to fix it 

Make sure that a valid certificate exists on the origin. For a self-signed certificate, you can use the Don't validate certificate option for the health check.





  Network interface limit 

Your origin might be down because your subnet might have reached the limit for the number of network interfaces allowed.

  How to fix it 

Try again with a subnet that has available space, or remove interfaces from the current subnet to give space for the health check virtual server instance.
Why isn't the DNS resolution request sent to the DNS server specified on the VPN server? 

I configured the DNS server IP addresses when I provisioned the VPN server; however, the DNS resolution request was not sent to the DNS server.

  What’s happening 

The DNS resolution request is sent to the original DNS server.

  Why it’s happening 

For Linux, the OpenVPN command-line client can receive the DNS option from the VPN server, but the OpenVPN command-line client expects an external command to act on this information. No such commands are configured by default. You must specify these commands with the up and down config options. For more information, see [OpenVPN DNS](https://wiki.archlinux.org/title/OpenVPNDNS).

  How to fix it 

Follow these steps to resolve this issue:



1.  Option 1: Use [OpenVPN Connect V2 or V3](https://openvpn.net/vpn-client/) instead of the OpenVPN command-line client.
2.  Option 2: Use a custom script recommended in [OpenVPN DNS](https://wiki.archlinux.org/title/OpenVPNDNS).
Why can't I establish a VPN connection? 

To establish a VPN connection, the right configurations must be in place.

  What’s happening 

Cannot establish a VPN connection.

  Why it’s happening 

One or more of your VPN for VPC configurations might be incorrect.

  How to fix it 

Follow these steps to verify your configurations:



1.  Verify that the IKE Phase 1 and Phase 2 configurations match on both sides.

One thing to watch out for is that VPN for VPC by default has Perfect Forward Secrecy (PFS) disabled in Phase 2. If PFS is enabled on its peer, then custom policy with PFS enabled is necessary.
2.  Make sure that ports UDP 4500 and UDP 500 are open on both sides.
3.  Make sure that NAT-Traversal is enabled on the peer, if it is a configurable option.
4.  Make sure that the peer device uses its public IP address as the IKE ID. This option is not a configurable option.
Why can't traffic get through my active connection? 

For application traffic to flow through a connection, the right configurations must be in place, including ACLs configured on both sides.

  What’s happening 

Your connection is active, but traffic is not getting through.

  Why it’s happening 

An interoperability issue might exist.

  How to fix it 

Follow these steps to resolve this issue:



1.  Make sure that NAT-Traversal is enabled on the peer, if it's a configurable option.
2.  Make sure that ACLs are configured properly on both sides to allow application traffic.
3.  If you're using a policy-based mode VPN with a static, route-based VPN peer and multiple CIDR subnets on either side, create multiple connections with one CIDR subnet pair per connection.
4.  If you're using a Cisco Adaptive Security Appliance (ASA) as the peer of VPN for VPC with multiple CIDRs and subnets that are configured on the Cisco side, try moving different subnets to separate connections.
5.  If you're using a route-based VPN on either side, configure the routes on each side properly so that traffic is routed to the VPN gateway correctly.
Why is traffic not reaching my back-end members? 

Use the information in this topic to help troubleshoot issue where traffic is not reaching your back-end member.

  What’s happening 

Incoming traffic fails to reach your back end members.

  Why it’s happening 

This could be caused by any of the following issues:



*  Your back-end pool health checks are failing.
*  Your back-end member application is not up and running.
*  Your load balancer security group rules do not allow outgoing traffic from load balancers on your back-end member port.
*  Your back-end member's security group rules, if any, do not allow all incoming traffic from the load balancer.



  How to fix it 

Check and resolve any of the previously listed issues that exist.
permission.

5) The Font Software, modified or unmodified, in part or in whole,
must be distributed entirely under this license, and must not be
distributed under any other license. The requirement for fonts to
remain under this license does not apply to any document created
using the Font Software.

TERMINATION
This license becomes null and void if any of the above conditions are
not met.

DISCLAIMER
THE FONT SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND,
EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTIES OF
MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT
OF COPYRIGHT, PATENT, TRADEMARK, OR OTHER RIGHT. IN NO EVENT SHALL THE
COPYRIGHT HOLDER BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY,
INCLUDING ANY GENERAL, SPECIAL, INDIRECT, INCIDENTAL, OR CONSEQUENTIAL
DAMAGES, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
FROM, OUT OF THE USE OR INABILITY TO USE THE FONT SOFTWARE OR FROM
OTHER DEALINGS IN THE FONT SOFTWARE.

END OF SIL OPEN FONT LICENSE 1.1 NON-IBM-LICENSE INFORMATION
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

END OF NON-IBM-LICENSE INFORMATION
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

END OF NON-IBM-LICENSE INFORMATION FILE
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
These features are listed in [Using the beta features](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-using_beta_features).





 Feature compatibility 

Some features that Liberty provides are not available in the Liberty for Java runtime because they are not applicable in the cloud environment.

Keep in mind that a server cannot load incompatible features, so be sure it is configured to enable only features that are compatible. See [Supported Java EE 6 and 7 feature combinations](https://www.ibm.com/support/knowledgecenter/SSEQTP_liberty/com.ibm.websphere.wlp.doc/ae/rwlp_prog_model_supported_combos.html) and [Supported Java EE 7 and 8 feature combinations](https://www.ibm.com/support/knowledgecenter/SSEQTP_liberty/com.ibm.websphere.wlp.doc/ae/rwlp_prog_model_supported_combos_7_8.html).

Apps that use remote EJBs can be deployed to IBM Cloud, but the remote EJBs are not remotely accessible with the CORBA/IIOP protocol because of port restrictions in the IBM Cloud environment.





 Liberty features index 

Skip to the section of the feature list by using the following index, or you can look through the [Liberty for Java features list](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-liberty_featureslibertyfeat_list).



 A-E 



* [A](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-liberty_featureslibertyfeat_A)
* [B](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-liberty_featureslibertyfeat_B)
* [C](https://cloud.ibm.com/docs/cloud-foundry-public?topic=cloud-foundry-public-liberty_featureslibertyfeat_C)
Building a high availability Certificate Authority (CA) 

Because redundancy is required to achieve high availability (HA) networks, you can use the IBM® Blockchain Platform console to configure a CA for high availability.

Target audience: This topic is designed for network operators who are responsible for creating, monitoring, and managing the blockchain network.

If you are using IBM Blockchain Platform for IBM Cloud, HA CA configuration is only available in paid Kubernetes clusters on IBM Cloud.



 Configuring CA replica sets 

When a Kubernetes pod becomes unavailable, Kubernetes immediately attempts to restart it. However, if your SLA requires zero downtime for your CA, you can configure replica sets for your CA. A replica set is a Kubernetes mechanism that is used to guarantee the availability of the pod. The use of replica sets ensures that multiple replicas of the pod are running at all times. If one of the CA replicas becomes unavailable, Kubernetes immediately switches to another CA replica, therefore there is no downtime while you wait for the pod to restart. The replica uses data from the same shared database so that the CA can continue to seamlessly process requests. If CA replica sets are required for your business, the IBM Blockchain Platform requires the CA to use an instance of a PostgreSQL database. Thus, before you can configure CA replica sets, you are responsible for configuring an instance of the PostgreSQL database.



 Deploying a PostgreSQL database 

PostgreSQL is a widely available open source relational database management system. The CA uses the database to store certificates (public keys only) and identities that are registered with the CA. Customers need to provision their own PostgreSQL database instance in IBM Cloud or from a third-party provider. When you deploy a new CA by using the blockchain console or APIs, you need to provide the connection information for the database. Each CA needs its own PostgreSQL database.







 Considerations 



* CA replica sets are only possible when the PostgreSQL database is selected for the CA. The SQLite database is not supported for use with CA replica sets.
And, in some ways it is extremely modular in that the replacement unit is usually an entire server. But there is one major difference between the redundancy that is provided in a mainframe and the redundancy that is provided in the cloud – in the cloud the redundancy must be managed by the user. This means that to design a system to run with high availability on the cloud the system designer needs to be familiar with various high availability issues, as well as the design issues associated with the system that they are trying to build.

There are decades of academic and practical writings on high availability, and much of the work requires a good understanding of probability mathematics. However, much like with the formula, many of the principles become obvious when properly explained. Redundancy, which can be complicated in some cases, such as the various levels of RAID disk subsystems, is simply a way of dealing with a widely known principle of system design: “Avoid single points of failure.” Admittedly, while the phrase is simple and obvious, implementation can be tricky.

Rather than go into the complexities of such implementations, we cover a high-level overview of the areas that need to be addressed by anyone looking to build or run a highly available cloud system.

Beyond the general principles of redundancy, fast repair, and single points of failure (SPOFs), probably the most important thing to understand is that improving availability requires spending effort on avoiding likely causes of outages, rather than trying to harden the system against all possible outages.

An example can help to make this clear. In astronomy, it is understood that our solar system will effectively end when the Sun goes nova. This will obviously cause all the computing systems on Earth to fail. Hence it is not something worth spending time and money on avoiding. Perhaps that particular example seems too extreme. So as a much simpler, business-oriented example, consider a city-wide fire, such as the one that burned down much of Chicago in the late 1800s. Fires on that scale are unusual, but not unique. As a business, should you spend time and money making sure that your computer systems could survive such a fire? The answer depends on various factors, but if for instance, your entire customer base is in Chicago, worrying about events that will wipe out the whole city is likely not useful.
For more information, see [Managing virtual server instances](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-virtual-server-instances)





 Error: cannot_start_network 

Error message: Can't start instance because network resources can't be provisioned

Your virtual server instance did not start because of a network resource failure. To address this error, try the follow possible resolutions:



* Stop and restart the instance.
* Delete the instance and try again.



If you still need help with the error, contact [support](https://cloud.ibm.com/docs/vpc?topic=vpc-getting-help).

For more information about managing network interfaces, see [Managing network interfaces](https://cloud.ibm.com/docs/vpc?topic=vpc-using-instance-vnics)





 Error: cannot_start_ip_address 

Error message: Can't start instance because the network interface IP address isn't available

Your virtual server instance did not start because of an unexpected network interface IP address failure. To address this error, try the follow possible resolutions:



* Stop and restart the instance.
* Delete the instance and try again.



If you still need help with the error, contact [support](https://cloud.ibm.com/docs/vpc?topic=vpc-getting-help).

For more information about managing your instance and IP addresses, see the following topics:



* [Managing virtual server instances](https://cloud.ibm.com/docs/vpc?topic=vpc-managing-virtual-server-instances)
* [Managing network interfaces](https://cloud.ibm.com/docs/vpc?topic=vpc-using-instance-vnics)







 Error: cannot_start_storage 

Error message: Can't start instance because storage wasn't provisioned

Your virtual server instance did not start because of a storage volume or storage disk provisioning error. To address this error, try the follow possible resolutions:



* Stop and restart the instance.
* Delete the instance and try again.