vania-janet/multiturn-rag-retrieval-data huggingface dataset:
2021/05/24 05:03:42 Terraform apply | Error: timeout - last error: ssh: rejected: connect failed (Connection timed out)
2. Paste the errors into the case details.



3. Provide the architecture name, source URL, and version from the log:



1. In the log file, find the architecture information. In the following example, you see the Related Workspace, sourcerelease, and sourceurl:

2023/04/06 18:11:43 Related Workspace: name=deploy-arch-ibm-slz-ocp-04-06-2023, sourcerelease=(not specified), sourceurl=https modules/terraform-ibm-landing-zone/archive/v3.1.2.tar.gz, folder=terraform-ibm-landing-zone-3.1.2/patterns/roks
2. Copy the architecture information and paste it into the case details.









 Routing your support case 

To route your support case correctly to speed up resolution, select the applicable product when you open the case.



 Routing when you can't deploy successfully 

If you can't deploy your deployable architecture, open a support case with the most likely cause of the issue:



* If you identified the service that you think is causing the error from the Schematics log, use the name of that service as the product name in the case.
* If you can't identify the error from the Schematics log, use the name of the deployable architecture as it is listed in the IBM Cloud catalog.







 Routing when you deployed successfully 

If you successfully deployed, yet have an issue with a service in the deployable architecture, open a support case and use the name of that service.
* [Invoke a smart contract from the SDK](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-appibp-console-app-invoke).
* Learn about application development by deploying the [commercial paper tutorial](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-appibp-console-app-commercial-paper) to the nodes managed from your console.







 Low-Level Fabric SDK APIs** 

If you want to continue to use your existing smart contract and application code, or use the other Fabric SDK languages that are provided by the Hyperledger community, you can use the [low-level Fabric SDK APIs](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-appibp-console-app-low-level-api) to connect to your network.







 Application connectivity and availability 

The Hyperledger Fabric [Transaction Flow](https://hyperledger-fabric.readthedocs.io/en/release-2.2/txflow.html) spans multiple components, with the client applications playing a unique role. The SDK submits transaction proposals to the peers for endorsement. It then collects the endorsed proposals to be sent to the ordering service, which then sends blocks of transactions to the peers to be added to channel ledgers. Developers of production applications need to be prepared to manage their interactions between the SDK and their networks for efficiency and availability.





 Network considerations 

Regardless of whether you choose to use the high-Level Fabric contract APIs, or the low-Level Fabric SDK APIs, both require network access to the following components:



* The CA for your organization. (You should never need to access the CA for another organization).
* All organizations peers (where all organizations are the organizations that are required for endorsing transactions).
* All ordering service nodes for all channels that you are transacting on.
For example, dynamic routing protocols and firewalls.
* Run an HCX unstretch network workflow in the UI and select the appropriate routing NSX device to take control of the default gateway of the unstretched network.
* Run any external routing changes, which can include inserting changed routing for networks that were migrated, removing routes to source site from the migrated network, and ensuring that routing to the migrated subnet across the WAN still works for the applications that were not migrated.
* The application owner tests the migrated applications from all possible access points: the Internet, the intranet, and the VPN.



For example, you want to network swing an application that has all VMs migrated to the cloud:



* You are using a vyatta on the private network side to insert routes into your MPLS cloud and to tunnel to the edge routing devices on the MPLS so you can avoid the IBM Cloud IP space.
* You have your account set with an IBM Cloud VRF.
* Some applications are behind a network load balanced virtual IP (vIP). Those vIPs are on your owned subnet that's located on a virtual F5 behind the vyatta.



Adding more specific routing into the MPLS for networks that are swung over to IBM Cloud through HCX works fine for other networks. However, it does not work for the individual vIPs because a /32 route is being added.

The common solution for WAN providers is to filter out /32 routes that are added. Work with the WAN vendor to allow.

The following are considerations and implications:



* Applications that share subnet, vLAN, and VXLAN need to move together.
* Applications behind a load balancer that uses an internal routable IP can require routing changes if they cannot be moved together or it is not desirable to do so. For example, involving too many applications in one swing can be perceived too much of a risk.
* VMware admins, network admins (including customers and WAN vendors), and application owners need to be involved, even if there's no planned impact on a particular system or network equipment.







 Related links
Because clientAuthRequired is set to false and also mutual TLS is enabled, when you access the REST server, you need to pass the TLS identities to be able to authenticate. This setting ensures that only users with the appropriate keys can see the corresponding logs.
* Only the metrics pulling model that is based on [Prometheus](https://hyperledger-fabric.readthedocs.io/en/release-2.2/operations_service.htmlprometheus) is supported for now.







 Before you begin 

You need to gather the following information from your peer and orderer.



* peer-endpoint or orderer-endpoint

You can find the operations endpoint URL of the peer or orderer in the peer or orderer JSON file that you export from the console.



1. Click the peer or orderer in the Node tab.
2. On the peer or orderer page, click the Settings icon besides the peer or orderer name.
3. In the side panel, click Export to save the peer or orderer JSON file.
4. Find the operations endpoint URL that is the value of the operations_url parameter in the JSON file. This value is referred to as the peer-endpoint or orderer-endpoint in the commands later in this topic. For example:

{
"short_name": "Peer1Org1_0",
"name": "Peer1 Org1",
"url": "https://169.46.208.93:32739",
"type": "fabric-peer",
"msp_id": "org1msp",
"operations_url": "https://169.46.208.93:32101"
}

{
"short_name": "Orderer_0",
"name": "Orderer",
"url": "https://169.46.208.93:31612",
"type": "fabric-orderer",
"msp_id": "orderermsp",
To inquire about the status of your ticket, follow the steps in [Contacting IBM Support](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-trbl_support).







 What to do next 

Manage your instances from the IBM Cloud for VMware Solutions console or the VMware vSphere Web Client.

Before you click vCenter console on the instance summary page to go to the vSphere Web Client and start managing your VMware ESXi™ servers, you must log in to the VPN portal of the IBM Cloud data center. Hover over vCenter console and follow the instructions to ensure that you meet all requirements and you completed the necessary steps before you access the vSphere Web Client.

Review the following topics for information to help you complete the login instructions:



* For the requirements and necessary steps before you access the vSphere Web Client, see [Timeout reached while connecting to the vSphere Web Client](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-trbl_timeout_vc_console).
* For a list of access points to log in to the IBM Cloud infrastructure Private Network by using VPN, see [VPN access](https://www.ibm.com/cloud/vpn-access).
* If you have problems when you deploy an OVF (Open Virtualization Format) file by using the vSphere Web Client, see [Deploying an OVF file using the vSphere Web Client](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-trbl_deploy_ovf).







 Related links 



* [Ordering vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_orderinginstance-req)
* [Adding clusters for vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_addingclusters)
Approving failed validations 

As an administrator on the IBM Cloud® projects service, if the validation pipeline didn't complete or succeed, you can override the failure and approve it.

Before you override a failed validation, ensure that the pipeline failed due to a Code Risk Analyzer scan and not because of a validation or plan failure. If you override a failure because of a validation or plan failure, approving isn't recommended because the configuration won't deploy successfully.



  When to approve a failed validation 

There might be a couple scenarios where you'd want to override a failed validation. If a major customer-impacting event requires you to make updates quickly, you might want to deploy your changes even at the risk of introducing compliance errors, which can be fixed later.

Sometimes, compliance errors are introduced that aren't applicable to your configuration or business needs. For example, if your Object Storage bucket resiliency is not set to cross region, the corresponding compliance goal will fail. However, this compliance issue might not impact your business if you don't need maximum availability and want to deploy your configuration to only one region.

To approve a failed validation, complete the following steps:



1.  From the projects list, select a project.
2.  Go to the Configurations tab, select a deployable architecture configuration, and click Edit.
3.  Select View details from the menu.
4.  Review the issues that caused the validation to fail.
5.  If you want to approve the changes, select Override and approve.
6.  Add a comment that explains why you're approving the changes.
7.  Click Override and approve.
Be sure to insert your application choice in place of aaaaaaaa (IBM Cloud® Virtual Router Appliance, Juniper vSRX, or Fortigate Security Appliance (FSA) 10G), and your specific account number in place of xxxxxx in your subject line.
* Wanclouds, our partner in this conversion configuration process, has completed several hundred successful migration engagements. They transform your existing Vyatta 5400 to create similar functionality on the Vyatta 5600 Platform. They provide their services in two tiers:

![Tiers](https://cloud.ibm.com/images/tiers.png)

Service tiers



See [Migrating Vyatta 5400](https://cloud.ibm.com/docs/virtual-router-appliance?topic=virtual-router-appliance-migration-overview) to get started.
* Are there any additional paid migration services available from IBM Business Partners for migrating off the Vyatta 5400?

We have several business partners who provide paid support for Vyatta 5400 migrations. For more information, see the [End of Support Announcement](https://cloud.ibm.com/docs/virtual-router-appliance?topic=virtual-router-appliance-vyatta-5400-end-of-support-announcement).
* Is there a Vyatta 5400 Offering Management support contact in IBM where I can ask questions related to my Vyatta 5400 migration?

Contact IBM Vyatta 5400 and VRA Network Offering Management with questions at nwom@us.ibm.com. You can also contact them using slack with the IBM Watson Cloud Platform workspace: vyatta-migration
* What additional resources are available to help me with this migration?

Review the following IBM Cloud® Virtual Router Appliance documentation resources for more information:



* [Getting Started with IBM Cloud® Virtual Router Appliance](https://cloud.ibm.com/docs/virtual-router-appliance?topic=virtual-router-appliance-getting-started)
(https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-v2-troubleshootingibp-v2-troubleshooting-update-channel)
* [When I log in to my console, why am I getting a 401 unauthorized error?](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-v2-troubleshootingibp-v2-troubleshooting-console-401)
* [Why am I getting a Cluster linking is taking too long error when I try to link my Kubernetes cluster in IBM Cloud to my IBM Blockchain Platform service instance?](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-v2-troubleshootingibp-v2-troubleshooting-console-helm-reset)
* [Why am I getting an error “all SubConns are in TransientFailure” on the console?](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-v2-troubleshootingibp-console-transientfailure)



Issues with your Nodes



* [Why is my first start of a smart contract returns the following error: no suitable peers available to initialize from?](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-v2-troubleshootingibp-v2-troubleshooting-smart-contract-anchor-peers)
* [Why are my node operations fail to operate after I create my peer or ordering service?](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-v2-troubleshootingibp-console-build-network-troubleshoot-entry1)
* [Why does my peer or ordering node fail to start?](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-v2-troubleshootingibp-console-build-network-troubleshoot-entry2)
Common use cases: Best for working with hybrid workloads, cross-provider workloads, large or frequent data transfers, private workloads, and environment administration. This option is usually selected: (1) when the wanted PoP does not have the wanted carrier or network service provider, (2) for high-performance workloads requiring high throughput, or (3) for compliance requirements that cannot be satisfied by either the Exchange on Classic or Connect on Classic implementation model.



 Use Case 1: Customer facility to IBM Cloud 

Zoom

![Customer facility to IBM Cloud](https://cloud.ibm.com/docs-content/v1/content/d7287ec7418d843dbd7caf286d842c439df6979e/direct-link//images/Direct-link-Dedicated.png)

Figure 2. Customer facility to IBM Cloud





 Use Case 2: Customer colocation to IBM Cloud 

Zoom

![Customer colocation to IBM Cloud](https://cloud.ibm.com/docs-content/v1/content/d7287ec7418d843dbd7caf286d842c439df6979e/direct-link//images/dedicated-model-colo.png)

Figure 3. Customer colocation to IBM Cloud

Termination location: IBM Cloud point of presence (PoP) or Data Center (DC).

Typical deployment time: 10 - 15 business days after the new circuit reaches the PoP. Deployment time can possibly be 30 - 60 days overall, depending on your location and requirements when you order a circuit from an NSP or carrier.

Cross-connect details: IBM Cloud provides a Letter of Authorization (LOA) that a customer uses to order fiber Ethernet (single-mode fiber only, either 1Gig-LX or 10Gig-LR optics) that runs from a customer cage or provider cage to the IBM Cloud CFA termination point, which will be tied down to the cross-connect router (XCR) infrastructure. The media must be a 1310 nm wavelength optic.

Port speed options: Select 1 Gbps, 2 Gbps, 5 Gbps, or 10 Gbps.
* Cancelling <environment> upcharges...
* VMware license cancellation in progress...
* VMware license cancellation is complete.
* The IBM Cloud infrastructure order failed or timed out.







 Instance error messages 

IBM Cloud for VMware Solutions issues the following instance history error messages.



* Error ordering VMware licenses. Open a service ticket for assistance.
* Error ordering subnets. Open a service ticket for assistance.
* Error: The IBM Cloud infrastructure API key is not valid. Open a service ticket for assistance.
* Error: The IBM Cloud infrastructure data center is not valid. Open a service ticket for assistance.
* Error using a shared image in the provided IBM Cloud infrastructure account. Open a service ticket for assistance.
* Error ordering service entries. Open a service ticket for assistance.
* Error ordering subnets. Open a service ticket for assistance.
* Error ordering licenses. Open a service ticket for assistance.
* Error ordering services. Open a service ticket for assistance.







 Cluster history messages 

IBM Cloud for VMware Solutions issues the following messages for VMware vCenter Server® clusters.



* Starting the cluster configuration...
* Starting the cluster configuration for <cluster_name>...
* The cluster configuration is complete.
* The <cluster_name> cluster is ready to use.
* Adding the new cluster into vCenter...
* The new cluster is added to vCenter.
* Starting the cluster deletion for <cluster_name>...
* Deleting the <cluster_name> cluster from vCenter...
* The <cluster_name> cluster is deleted from vCenter.
* The <cluster_name> cluster is deleted.







 ESXi server history messages 

IBM Cloud for VMware Solutions issues the following messages for VMware ESXi™ servers.



* Starting the order for <quantity> ESXi servers...
* Verifying the ESXi server order...
* The ESXi servers with the <ip_addresses> Private IP address are ready.
* All ESXi servers are reclaimed.
"DeliverTraceDir": null
},
"Metrics": {
"Provider": "disabled",
"Statsd": {
"Network": "udp",
"Address": "127.0.0.1:8125",
"WriteInterval": "30s",
"Prefix": null
}
}
}
Show more

Paste the modified JSON that contains only the parameters that you want to update into the Configuration JSON box. For example, if you only needed to update the value for the ServerTimeout field you would paste this JSON into the Configuration JSON box:

{
"General": {
"Keepalive": {
"ServerTimeout": "20s"
}
}
}

The ability to update an ordering node configuration is not available for ordering nodes that have been imported into the console.









 Using certificates from an external CA with your peer or ordering service 

Instead of using an IBM Blockchain Platform Certificate Authority as your peer or ordering service's CA, you can use certificates from an external CA, one that is not hosted by IBM. To use an external CA, the CA needs to issue certificates in [X.509](https://hyperledger-fabric.readthedocs.io/en/release-2.2/identity/identity.htmldigital-certificates) format. You need to generate your private keys using the PKCS 8 standard. For a quick tutorial, see [Using certificates from an external Certificate Authority](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-tutorial-extca).



 Before you begin 



1. You need to gather the following certificate information and save it to individual files that can be uploaded to the console.
Note: The certificates inside the files can be in either PEM format or base64 encoded format.



* Peer or ordering node identity certificate This is the signing certificate from your external CA that the peer or ordering node will use.
Archive failures Reports unsuccessful requests uploading objects to a bucket. Reports all reason codes except 200. 



To use these views, you must customize them by entering the Activity Tracker hosted event search instance CRN, the bucket name, and the service ID that is used to authenticate and work with the bucket.

The information on these views include the following information for each record:



* Action that you can use to identify the type of request.
* Region where the bucket is located.
* Bucket name.
* Reason code (RC).
* Account ID that indicates the account where the bucket is available.
* Instance ID that indicates the Cloud Object Storage instance where the bucket is provisioned.



The following table outlines the predefined views that you can use to monitor when archiving fails due to invalid credentials uploading objects to the bucket:



Table 4. Archiving enablement predefined views to report failures

 View name Description 

 COS credentials deleted Reports when the COS serviceId credentials are deleted. 
 COS API key deleted Reports when the API key associated with the COS service ID is deleted. 
 Internal error (RC 500) Reports when there is a SocketTimeoutException and archiving fails. 
 IP invalid Reports when the request is originating from an IP address that is not in the IP allowed list. 
 Unable to access bucket Reports when there is a ReplicationConfigurationNotFoundError and archiving fails. 
 Unauthorized access Reports unauthorized attempts to access your archives and manage 1 bucket. Checks reason codes 403 and 401. 







 Predefined dashboards 

The following table outlines the predefined dashboards that you can use to monitor Activity Tracker instances and Log Analysis instances that have the archiving feature configured to an IBM Cloud Object Storage bucket:



Table 5. Predefined dashboard

 Dashboard name Description 

 Archiving bucket Monitor archiving for 1 Activity Tracker hosted event search instance in an account. 
 Archiving overview Monitor archiving across the account. 
 Failures to archive Monitors scenarios where archiving fails. 



To use these dashboards, you must customize them by entering the bucket name and the service ID that is used to authenticate and work with the bucket.
Enabling or adding failover crypto units after you provision a service instance 

Failover crypto units back up the operational crypto units and keystores in another region. If a regional disaster occurs, you can use failover crypto units to automatically restore your data, which can reduce the downtime and data loss. You can either enable failover crypto unit [when you provision a service instance](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-provision) or after you provision a service instance. This topic guides you through enabling or adding failover crypto units after you provision a service instance.

If you have a service instance in the us-south or us-east region, you can enable failover crypto units for your instance with the IBM Cloud Trusted Key Entry (TKE) CLI plug-in or the Management Utilities. If failover crypto units are already assigned to your service instance, you can still add extra ones.

You can specify a total number of failover crypto units that are equal to or less than the number of operational crypto units. However, to meet high availability, at least two failover crypto units need to be assigned. Failover crypto units are also charged. For the detailed pricing information, see [FAQs: Pricing](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-faq-pricing).



 Using the IBM Cloud CLI 

To enable or add failover crypto units by using the IBM Cloud CLI, follow these steps:



1. Check and make sure that you install the [IBM Cloud CLI](https://cloud.ibm.com/docs/cli?topic=cli-install-ibmcloud-cli) and the latest TKE CLI plug-in with the following command:

ibmcloud plugin install tke

If you have installed the TKE CLI plug-in, make sure to update your plug-in to the latest version with the following command:

ibmcloud plugin update tke
2.