vania-janet/multiturn-rag-retrieval-data huggingface dataset:
My deployment failed, how do I proceed? 

Your deployment failed.

  What’s happening 

You attempted to deploy an instance of the Power Virtual Server for SAP HANA deployable architecture but it failed.

  Why it’s happening 

As part of the development of the deployable architecture we verify the workflows described in this guide continuously. In the stable IBM Cloud environment, no errors are expected. But because there are several infrastructure layers and components included in the deployment, there is a possibility for issues that aren't anticipated. For example, the maintenance activity in the particular data center, errors in the VPC, PowerVS or network services, or issues in OS software updates can cause deployment failures.

  How to fix it 

If the deployment process does not finish successfully, we recommend first looking at the IBM Cloud Schematics logs. These logs typically provide the information about the component that causes the issue.



*  Ensure that all prerequisites are applied according to the [planning guide](https://cloud.ibm.com/docs/sap-powervs?topic=sap-powervs-sap-powervs-automation-planning)
*  Verify that correct input parameters are provided as described in the [readme file](https://github.com/terraform-ibm-modules/terraform-ibm-powervs-sap/blob/main/examples/ibm-catalog/deployable-architectures/sap-ready-to-go/README.md)



If you still cannot solve your issue, open a case in the IBM Cloud support center.
Support on Connect and Exchange is theoretically possible, but it requires your Service Provider to work with IBM and ensure that the end-to-end connection supports Jumbo Frames, including the underlying Network-to Network-Interface (NNI).

Exchange and Connect support up to a 1500-byte Maximum Transmission Unit (MTU).





 With Direct Link Connect how does a customer ensure router diversity through the same carrier (for example, Verizon in DAL03)? 

We have diverse cross-connect routers (XCRs) creating diverse NNI links to the carrier. It is up to the carrier to maintain diversity from that point.





 For Direct Link Connect does a customer need to order two links for redundancy, or is the Direct Link Connect inherently redundant? 

Order two links for diversity. We do not offer redundancy between switches or routers. Customers create redundancy with their BGP configurations on each Direct Link.





 How easy is it to upgrade the bandwidth of my Direct Link connection, for example 1 - 5 GB? 

Typically, we install speeds of 1G and lower on 1G optics. For speeds of 2 - 10 GB, we install 10 GB optics. Thus, the upgrade 1 - 5 GB would require new optics to be assigned or inserted. It would be a service-affecting event. If you anticipate that type of growth, it's possible to request 10 GB optical fibers to be installed at the beginning of your Direct Link deployment, or to order 2 GB initially so that the 10 GB optics are in place.





 Is ECMP the way to go for redundant Direct Link connections? What alternatives exist? 

ECMP isn’t for redundant connections, but for balancing the load over the two links. With ECMP, both connections must terminate to the same IBM Cloud cross-connect router (XCR), which makes it a single point of failure. (In other words, ECMP can be provisioned only as two sessions on the same IBM Cloud XCR.)

IBM Cloud does NOT recommend the use of ECMP. ECMP balancing with IBM cloud only extends to the XCRs.
How do I address a failed deployment when using projects? 

You tried to deploy a configuration from a project, but the deployment failed, preventing a successful deployment to your target environment.

  What’s happening 

The project displays a Needs attention alert and a message displays on the Activity tab that states that the deployment failed.

  Why it’s happening 

The changes that you made to your resources failed to deploy. Go to the needs attention widget on the Overview tab and select Changes failed to deploy to view more information about the failure.

  How to fix it 



*  Lack of permissions: Ensure that the project has sufficient privileges in the target account.
*  Invalid input value: Check the logs for details.
*  Duplicate input values: Some input values, like an Object Storage bucket name or IP address, must be unique. Destroy the existing resource, or modify your input values to be unique.
*  Timeout: If the deployment runs too long, it might time out and cause a failure. Try deploying the configuration again.
*  A service was down during the deployment: Check the Schematics logs for 400 or 500 errors that indicate a problem with the service. Check the [Status page](https://cloud.ibm.com/status) for the service, and try to deploy again when the service is back up. For more information on the 500 errors in Schematics, see [Why am I getting 5xx errors in Schematics?](https://cloud.ibm.com/docs/secure-infrastructure-vpc?topic=secure-infrastructure-vpc-server-errors)
*  Reaching a quota limit: Ensure that sufficient quota space is available in the account. For example, you can have only one instance of a service that uses a Lite plan.
*  Manual changes were made to the account that conflict with the deployable architecture. We recommend avoiding manual changes to the account during a deployment.
Order the new device, following the instructions for either [Juniper vSRX](https://cloud.ibm.com/docs/vsrx?topic=vsrx-getting-started) or for [FSA -10G](https://cloud.ibm.com/docs/fortigate-10g?topic=fortigate-10g-getting-started).

It is a recommended best practice to order a High Availability solution.
3. Load the applicable configuration you onto your newly ordered device.
4. Schedule time to migrate your VLANs to your new device.

This step requires a brief downtime.
5. Test and confirm that your new device is functioning properly.
6. Open a support case to cancel your Vyatta 5400 device.







 Upgrading a Vyatta 5400 High Availability (HA) pair 

To upgrade two Vyatta 5400s in an HA pair, perform the following procedure:



1. Ensure that you have backed up your 5400 and stored the data in two different locations. This includes SSH keys, SSL certs, scripts and any other files necessary to recover your current Vyatta 5400 configuration, if necessary. To do so, follow [these instructions](https://cloud.ibm.com/docs/virtual-router-appliance?topic=virtual-router-appliance-backing-up-a-configuration).
2. Order the new device, following the instructions for either [Juniper vSRX](https://cloud.ibm.com/docs/vsrx?topic=vsrx-getting-started) or for [FSA-10G](https://cloud.ibm.com/docs/fortigate-10g?topic=fortigate-10g-getting-started).
3. Load the applicable configuration onto your newly ordered device.
4. Schedule time to migrate your VLANs to your new device.

This step requires a brief downtime.
5. Test and confirm that your new device is functioning properly.
6. Open a support case to cancel your Vyatta 5400 devices.
String endPoint = getEndpoint(COS_BUCKET_LOCATION, "public");
AmazonS3 s3client = createClient(COS_API_KEY_ID, COS_SERVICE_CRN, endPoint, COS_BUCKET_LOCATION);

TransferManager transferManager = TransferManagerBuilder.standard()
.withS3Client(s3client)
.withMinimumUploadPartSize(partSize)
.withMultipartCopyThreshold(thresholdSize)
.build();

try {
Upload lrgUpload = transferManager.upload(bucketName, itemName, uploadFile);

lrgUpload.waitForCompletion();

System.out.println("Large file upload complete!");
}
catch (SdkClientException e) {
System.out.printf("Upload error: %sn", e.getMessage());
}
finally {
transferManager.shutdownNow();
}
Show more

SDK References



* Classes



* [TransferManager](https://ibm.github.io/ibm-cos-sdk-java/com/ibm/cloud/objectstorage/services/s3/transfer/TransferManager.html)
* [TransferManagerBuilder](https://ibm.github.io/ibm-cos-sdk-java/com/ibm/cloud/objectstorage/services/s3/transfer/TransferManagerBuilder.html)
* [Upload](https://ibm.github.io/ibm-cos-sdk-java/com/ibm/cloud/objectstorage/services/s3/transfer/Upload.html)



* Methods



* [shutdownNow](https://ibm.github.io/ibm-cos-sdk-java/com/ibm/cloud/objectstorage/services/s3/transfer/TransferManager.htmlshutdownNow--)
My deployment failed, how do I proceed? 

Your deployment failed.

  What’s happening 

You attempted to deploy an instance of a landing zone deployable architecture, but it failed.

  Why it’s happening 

Several infrastructure layers and components are included in the deployment, and an issue in one of those pieces is causing the failure. For example, maintenance in a particular data center or errors in the VPC or network services can cause deployment failures.

If the deployment process does not finish successfully, look at the IBM Cloud Schematics logs. These logs typically provide the information about the component that causes the issue.

If you can't deploy successfully, follow these steps:



1.  Make sure that you comply with the prerequisites in the [planning](https://cloud.ibm.com/docs/secure-infrastructure-vpc?topic=secure-infrastructure-vpc-plan) topic.
2.  Check the values of the inputs.

For example, from the Configurations tab in your project, click the name of your deployable architecture > Edit.
3.  Rerun the Schematics apply action again in IBM Cloud Schematics by clicking Apply plan or by running the ibmcloud schematics apply command.



1.  In the IBM Cloud console, go to Schematics > Workspaces and select your instance of the deployable architecture.
2.  Click Apply plan.

This action resumes the job where it left off. In some cases, when the error was with provisioning a service, this second apply command is successful.





  How to fix it 

If the issue persists after the second apply, [open a case](https://cloud.ibm.com/docs/secure-infrastructure-vpc?topic=secure-infrastructure-vpc-help-supportsupport-case-details) in the IBM Cloud support center.
For additional information about the affected components, [set up Log Analysis](https://cloud.ibm.com/docs/satellite?topic=satellite-get-helpreview-logs) and review the [R0057 error logs](https://cloud.ibm.com/docs/satellite?topic=satellite-healthlogs-error).





 R0058: DNS registration is failing 

Location message
: A location with this name was recently deleted. If you want to reuse the location name of a recently deleted location, DNS registration might take a week to complete.

Steps to resolve
: If you don't need to reuse this location name, delete this location and create a location with a unique name. If the issue persists, [open a support case](https://cloud.ibm.com/docs/satellite?topic=satellite-get-help) and include your Satellite location ID.





 R0059: Outbound traffic to IBM Cloud Container Registry is failing. 

Location message
: Outbound traffic to IBM Cloud Container Registry is failing. To ensure that all host requirements are met, see the [Host system requirements](https://cloud.ibm.com/docs/satellite?topic=satellite-host-reqs). More information is available in the IBM Cloud Platform Logs. If the issue persists, contact IBM Cloud Support and include your Satellite location ID.

Steps to resolve
: Check the health status and ensure that the host system requirements are met.



1. Run the following command to check the health status.

curl https://iam.cloud.ibm.com/healthz
2. If the output from the previous step indicates a failure, check that your hosts meet all [system requirements](https://cloud.ibm.com/docs/satellite?topic=satellite-host-reqs).
3. If you have met all the system requirements and the issue persists, [open a support case](https://cloud.ibm.com/docs/satellite?topic=satellite-get-help) and include your Satellite location ID.
If you need to update your ECCN after you add it, you must contact IBM Cloud Support.

You must submit your tax and EFT documents and receive approval before you can provide the ECCN if you're using a usage-based pricing plan.



1. Go to Partner Center > Sell > My products.
2. Open the service that you want to edit and go to the Pricing tab.
3. Click Enter your ECCN and provide the ECCN for your service.
4. Click Save.







 Providing the UNSPSC 

You must provide your ECCN before the UNSPSC.

In addition to ECCN, you must provide the UNSPSC that applies to your product. The UNSPSC is required for both free and usage-based pricing plans. If you need help with selecting the UNSPSC for your service, see [How to select UNSPSC codes?](https://help.ungm.org/hc/en-us/articles/360013132940-How-to-select-UNSPSC-codes-). Providing your UNSPSC is a required step in the onboarding process.

To provide the UNSPSC code that applies to your product, complete the following steps:



1. Go to Partner Center > Sell > My products.
2. Open the service that you want to edit and go to the Pricing tab.
3. Click Add UNSPSC and select the UNSPSC code for your service.
4. Click Save.







 Accepting agreement terms and conditions 

Depending on the type of plans you are adding for your product, you must sign an agreement that outlines the terms and conditions of providing a product in the IBM Cloud. Or, you can upload a custom digital provider agreement in .pdf, .doc, or .docx file format.

Custom digital provider agreements must be reviewed and approved by IBM, which increases the time it takes for you to complete the onboarding process. The uploaded files are scanned for viruses, which might take a few minutes to complete. If a virus is detected, it is recommended to run another virus scan on your file, and then try uploading it again.



 Digital provider agreement
The redundant infrastructure can be used by the ordered VLANs.

For some network requirements, such as DR setup replication scenarios, you must check the location of the connected devices and any new network requirements specific to the software/application in question. In some cases, the IBM Cloud Classic Infrastructure's File or Block Storage with snapshot backups might fulfill your requirements. Check with IBM Cloud Support to determine which solution works best for your business needs.







 Configure high availability for IBM Power Infrastructure 

This is a complementary offering from IBM Power Systems, with low latency access to IBM Cloud services

The IBM Cloud® environment does not support any pre-configured high-availability (HA) scenarios for SAP. However, you can configure HA scenarios based on the HA extension for the operating system you choose.

You add the HA extension by adding the required hardware and the required software components to your landscapes. If you require more software licenses, access to different software repositories, or both, contact [IBM Cloud Support](https://cloud.ibm.com/docs/get-support?topic=get-support-using-avatargetting-support) to help you with setting up any additional requirements. In general, setup procedures do not differ from any setup procedures in an on-premises environment and require the same hardware and software configuration steps. For specific instructions on how to set up HA for IBM Power Systems Virtual Server, see [High Availability and Disaster Recover options in IBM Power Systems Virtual Server](https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-ha-dr).
The application provider and consumer might be the same when the organization providing the application also consumes it (for example, a financial institution deploys an application for internal use by others in their company). Or, they can be different when a third-party ISV provides an application for a financial institution to use.

Application providers who are within financial institutions are not beholden to the IBM Cloud Framework for Financial Services control requirements.
* What does it mean for a service to be IBM Cloud for Financial Services Validated?

IBM Cloud for Financial Services Validated designates that an IBM Cloud service or ecosystem partner service has evidenced compliance to the controls of the IBM Cloud Framework for Financial Services and can be used to build solutions that might themselves be validated.
* Should I only use IBM or third-party managed services that are IBM Cloud for Financial Services Validated?

Generally speaking, you should strive to use only services which are Financial Services Validated in your solutions. However, depending on your circumstance there may be exceptions. See the best practice [Use only services that are IBM Cloud for Financial Services Validated](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-best-practicesbest-practices-financial-services-validated-services) for more details and potential exceptions.
* What if I don't want to use managed services, but I want to install and manage my own software?

Self-installed (or "bring your own") software from third parties is permitted without special approval. Examples include databases, logging stacks, web application firewalls, and so on. But just like first-party software you might develop and deploy, self-installed third-party software must comply with all of the requirements of the IBM Cloud Framework for Financial Services. And, it is your responsibility to provide appropriate supporting evidence.

For more information, see [Ensure all usage of software meets IBM Cloud Framework for Financial Services controls](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-best-practicesbest-practices-self-installed-software).



Landing zone



* What is a deployable architecture?
[Deploying third-party router or firewall in converged or management clusters](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/vmwaresolutions/images/arch-pattern-nsx-t-3rd-party.svg)

Figure 2. Deploying third-party router or firewall in converged or management clusters

This architecture pattern deployment is summarized as follows:



1. Depending on the network preference selection, your vCenter Server instance is deployed with both public and private connectivity or private connectivity only.
2. You can optionally deploy a gateway cluster to host Juniper vSRX or your own routing or firewall device. In this case, you might put public and private VLANs behind the firewall.
3. You can deploy third-party network devices into vCenter Server clusters by bringing in your own license and following the hardware and software guidance as provided by the specific third-party vendor. Discuss the technical details with the vendor.
4. You can integrate the third-party network device or a router into using service insertion. With service insertion, you can apply third-party services to north-south traffic as well as east-west traffic that passes through a router. The services typically provide advanced security features, such as an intrusion detection system (IDS) or an intrusion prevention system (IPS).
5. When you use service insertion and after, deploy a service instance, you can configure the type of traffic that the router redirects to the service. Configuring traffic redirection is similar to configuring a firewall.
6. Alternatively, you can add the device into north-south traffic path and customize the NSX-T customer topology. Contact your third-party vendor to discuss the wanted network topology, for example, router mode versus transparent.



The following diagram presents the routing topology and routing for this pattern.

Zoom

!
* If the destination have enabled iptables rules, please ensure the IP of the cloud application is in the range of the iptables rules
* If the destination is set to use Mutual Auth, please ensure it is using associated certificate and key to connect



* If the client has generated error level logs from the request, then the issue is between the SG Client and the on-prem resource. For example:

[ERROR] Connection <connection ID> to destination <target host>:<target port> had error: '<Error Code>'

Below is a table containing common errors, the issues that typically cause them, and potential methods to troubleshoot them.





 Error Code Typical Cause Troubleshooting Methods 

 ETIMEDOUT The client is unable to find the hostname/ip to connect to due to network constraints. Attempt to ping the destination's hostname/ip from the host running the client to ensure network connectivity. If running the Docker version of the client, bridging the container with the host OS with --net=host may resolve the issue. 
 ECONNREFUSED The client has resolved the hostname/ip to connect to but is unable to begin the connection handshake This is typically caused by a mismatched protocol between the SG Client and the on-prem resource (e.g., the client is attempting a TCP connection to a host:port that is expecting a TLS connection). In some cases, a firewall rule may cause this error instead of ETIMEDOUT. 
 ECONNRESET The client has established a connection to the destination but something went wrong either during the handshake (a TLS handshake error might result in different errors, as well) or while the request was being handled by the on-prem resource. The logs of the on-prem resource should be checked to confirm no error has caused the connection to be interrupted. If nothing is found in the on-prem logs, then the destination configuration should be examined to ensure the appropriate protocols (and certificates, if necessary) are being provided to the client for the connection. 
 REMOTE_RST There is error occurred in SG Server side.
If the license was procured outside of IBM Cloud, please work with that procurement source for support. Otherwise, is is strongly recommended you contact [IBM Support](https://cloud.ibm.com/docs/vsrx?topic=gateway-appliance-getting-help) to migrate to a supported vSRX license.





 Correcting warning 1181 

The vSRX license and version on the Gateway are both unsupported. Refer to [Correcting warning 1179](https://cloud.ibm.com/docs/vsrx?topic=vsrx-correcting-readiness-errorscorrecting-1179) and [Correcting warning 1180](https://cloud.ibm.com/docs/vsrx?topic=vsrx-correcting-readiness-errorscorrecting-1180) for help in resolving these warnings.
* For the keystore, select either Hyper Protect Crypto Services or Key Protect.
* Select an authentication keystore instance.
* Select an authentication key.



* Detect network failures with Bidirectional Forwarding Detection (BFD) - Activate BFD to quickly detect faults in a network between two routers or switches that are connected by a link. BFD provides a single, standardized method for detecting link failures at any protocol layer, over any media. For more information, see [Setting up bidirectional forwarding detection](https://cloud.ibm.com/docs/dl?topic=dl-dl-bfd).

Activating and deactivating BFD after the BGP session is established causes BGP session downtime and network disruption until the BGP peer device is configured for the same change.

Complete the following information:



* Interval – The interval is the minimum time (in milliseconds) expected to occur between when the local routing device sends BFD hello packets and the reply from its neighbor. This value can range from 300 to 255,000 milliseconds.
* Multiplier – The multiplier is the number of times that a hello packet is missed before BFD declares the neighbor down. This value can range from 1 to 255. The default multiplier value is 3.



* Prioritize direct links with AS prepends - Adjust route preference by lengthening AS paths with multiples of the BGP Autonomous System Number (ASN). When the prefix is matched, the longer AS path becomes a lower priority for the BGP router. For more information, see [Prepending an AS path to influence route priority](https://cloud.ibm.com/docs/dl?topic=dl-prepend-as-paths).
* Filter your import routes - Select a default filter to either permit or deny all routes unmatched by active route filters. By default, all import routes are permitted. Next, click Configure filters to start creating import route filters. To prioritize filters, drag and drop the icon next to the Order number in the table. Click Save to save your configuration.