vania-janet/multiturn-rag-retrieval-data huggingface dataset:
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. <br> <br>For on-prem destination, there is error during the requesting app connecting to the SG Server, or a timeout error when receiving data from the on-prem resource. <br> <br>For cloud destination, it could be anything from TLS handshake failure, to errors in the cloud resource For on-prem destination, please ensure the requesting app using the appropriate protocols to establish the connection with SG Server, if the error occurs when receiving data from on-prem resource, please try to extend/disable the timeout. If the timeout is disabled but still getting this error 3600 seconds after the last data transmitted/received, please implement the keep-alive logic when sending the request on cloud side. <br> <br>For cloud destination, the logs of the cloud resource should be checked to confirm no error has caused the connection to be interrupted. If nothing is found in the cloud resource 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. 



Many applications experience "hangs" after an ECONNRESET occurring on the other end of the tunnel. This is expected. Secure Gateway can not replay the RST packet on the other end of the tunnel since the TCP packets have already been ACKed for that side of the tunnel. Define the timeouts on the application, which never receives an acknowledging response, are the only method to end the hang.







 Configure your Docker client to restart when your server restarts 



 What is happening 

When you restart the server where your Secure Gateway client runs, you must manually restart the Secure Gateway Docker client.
If you navigate to your channel by using the console, you are able to see that another block was added by the transaction.



Your transaction might fail if you did not configure an anchor peer on your channel. Unless you manually updated your connection profile, your application needs to use the [Service Discovery](https://hyperledger-fabric.readthedocs.io/en/release-2.2/discovery-overview.html) feature to learn about the peers it needs to submit the transaction to. For more information, see [Configuring anchor peers](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-governibp-console-govern-channels-anchor-peers).





 Running the Commercial Paper sample 

The [commercial paper tutorial](https://hyperledger-fabric.readthedocs.io/en/release-2.2/tutorial/commercial_paper.html) in the Hyperledger Fabric documentation takes developers through a use case in which multiple parties buy, sell, and redeem commercial paper. It extends the [Developing applications topic](https://hyperledger-fabric.readthedocs.io/en/release-2.2/developapps/developing_applications.html) by providing sample smart contract and application code that allows you to create and trade assets on a local instance of Fabric.

You can also deploy the commercial paper tutorial sample code onto an IBM Blockchain Platform network. This allows you to quickly get started interacting with your network and use the sample to download the necessary dependencies. The sample code also includes examples of how you can import certificates into a [wallet](https://hyperledger-fabric.readthedocs.io/en/release-2.2/developapps/wallet.html) and use your connection profile to build a [Fabric gateway](https://hyperledger-fabric.readthedocs.io/en/release-2.2/developapps/gateway.html). The tutorial can be used by two different organizations to complete different transactions with a single asset.
For short-term emergencies where the original site is unavailable for a period of time, but servers and storage remain intact, a delta-resynch might fit the need to bring the operation back to on premises.

For other emergencies, that have forced a change to the site, server, or storage in the original on premises, it might require a full resynchronization of data, so the fallback will happen tidily at the most convenient time after the sync point has been achieved.





 Cloud networking (LAN) 

Having a DR on cloud might also imply that you need to rebuild your network structures to adapt to the network structures and constraints on the cloud provider. In some cases, you are be forced to use Software Defined Network (SDN) and Network Functions Virtualization (NFV) to reproduce your complex enterprise network layout. A careful planning and evaluation of performance and scalability limitation is essential to assure your reprovisioned compute can work properly.





 Cloud networking (WAN) 

All the external networks connected to your primary (failed) site must be rerouted to the alternative cloud site. Different options are available, and you need to evaluate what options best fit your requirements. Consider the charges associated with the use of the network, such as download and upload charges, when using the cloud provider resources, as they might add a substantial cost to your DR total cost of ownership (TCO).

When implementing a DR on cloud, the solution is simplified by leveraging the same technology in the primary and secondary sites.





 Full versus partial failover 

Partial failover is used to potentially increase the availability of the services by allowing to run and recover some of the services in DR while all the others are still running production on the customer data center.

Partial failover carries a lot more complexity in the network design that is associated with the solution, as it requires an extension of production site networks to the DR site that can happen on Layer 2 (such as L2TPv3, Cisco Overlay Transport Virtualization), Layer 3 (such as Cisco Locator/ID Separation protocol (LISP), Virtual Private LAN Services (VPLS), or Software Defined Network technique.
How do I troubleshoot a Direct Link Dedicated connection during activation? 

I'm experiencing issues with the activation of my Dedicated connection. What should I do?

 What’s happening 

The Direct Link Dedicated connection cannot establish end-to-end connectivity because the physical link is down.

 Why it’s happening 

Possible causes include:



* The single-mode fiber cable between the patch panel and edge device (router or switch) was not installed.
* An incorrect optic was used.
* There is a faulty cable, optic, or port along the path.
* The Site Provider installed the cross-connect in the wrong patch panel or ports.
* The port on the edge device is not up.
* The fiber's (RX/TX) strands are not aligned.



 How to fix it 

Follow these steps to troubleshoot Layer 1 (physical) issues:



1. Compare the IBM Connecting Facility Assignment (CFA) details in the Letter of Authorization (LOA) to the cross-connect completion notice provided by the facility. Verify that the CFA details matches the cross-connect completion notice.

Contact the facility owner if the cross-connect completion notice does not match up with the LOA/CFA.

For an example of a cross-connect completion notice, see [Completion notice example](https://cloud.ibm.com/docs/dl?topic=dl-completion-notice-example).
2. Verify that your router, or the network provider's router, is powered on and that the ports are up.
3. Ensure that device patching is complete. The single-mode fiber cable must be installed between the device to the patch panel.
4. Ensure that the device is using the correct optic.

For 1G connections, use 1G optic; for connections greater than 1G, use a 10G optic. (1310nm optic - 1G=1000BASE-LX / 10G=10GBASE-LR)
5. Check the light levels from the Meet Me Room (MMR) to make sure that you're sending light to IBM and receiving light from IBM.
6. Try rolling the fiber by flipping TX/RX strands.
A failure to receive a response from one of the zones being health-checked can be used to either provide notification of a failure to trigger a manual failover, or it can be used to automate removal of the failed zone from the route list.





 Failover 

The SIP trunking provider plays an important role in detecting and managing a failover, especially if an automatic failover is expected between regions. In most cases, SIP trunking providers should be configured to treat each zone within a region as active/active and two regions where an assistant is configured as active/passive. SIP trunking providers should always be configured to load balance and fail over between zones within a single region. The remainder of this section focuses on handling a failover between regions.





 Full service outage 

Phone integration failures have two types. The first type is a full outage where the session border controllers in all 3 regional zones become unreachable. This is the easier of the two types to detect and handle because the SIP trunking provider is immediately notified via SIP timeouts that the call fails and can be configured to either automatically fail over or the call routing can be manually reconfigured at the SIP trunking provider to direct traffic away from the failed region towards the passive backup region. If a failover is automated and a regional backup is enabled, it is always best to try a different zone first and only redirect traffic to the passive backup region if a preconfigured number of failures occur within a short period of time. This prevents an unnecessary failover between regions if only a short outage occurs.

Note that Watson Assistant provides a round-robin fully qualified domain name (FQDN) that includes the IPs for each zone in the region. Many SIP trunking providers automatically retry each IP in the FQDN when failures occur. To support disaster recovery, the service provider may need to configure two separate SIP trunks, one for each region, and only when all the zones in a single region fail should the call be switched to the backup region. It's important to set the SIP INVITE failure timeouts at the SIP trunking provider low enough to avoid long call setup latencies when a failover is occurring.





 Partial service outage 

The second type of failure is a partial service outage within the region.
For more information, see [Personal use availability](https://cloud.ibm.com/docs/account?topic=account-account-getting-startedsignup-personalaccts).
4. Verify that you are creating the correct account type: personal or business.







 Why was there an error in the payment process? 

 What’s happening 

An issue occurred that caused the payment process to fail. This error might prompt the following message:

> There was an error in the payment process: We're afraid this transaction has been rejected. General decline of the card. No other information provided by the issuing bank.

 Why it’s happening 

Your credit card issuer has declined the transaction.

 How to fix it 

Contact your credit card issuer for more information.





 Why is the transaction already processed? 

 What’s happening 

An issue occurred that caused the payment process to fail. This error might prompt the following message:

> Transaction already processed.

 Why it’s happening 

Our payment system has detected multiple similar payments within a short period of time. IBM Cloud is attempting to avoid unintentional duplicate payments.

 How to fix it 

Wait 3-4 hours for the manual payment to be processed and posted to your IBM Cloud} account. Verify your account balance on the [Payments page](https://cloud.ibm.com/billing/payments).





 Why can't I upgrade my account? 

 What’s happening 

An issue occurred that caused the payment process to fail. This error might prompt the following message:

> Your account couldn't be upgraded. Click Upgrade account to try again.

 Why it’s happening 

IBM Cloud} was unable to process your transaction.

 How to fix it 

Submit your account upgrade information again. If the error continues to occur, you can contact [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 Why can't I save my credit card to the account? 

 What’s happening 

An issue occurred that caused the payment process to fail. This error might prompt the following message:

> Your card could not be saved.
"start_timestamp": "2021-10-12T20:54:06.321Z",
"stop_timestamp": "2021-10-12T20:54:14.338Z",
"response_milliseconds": 535
}
},
{
"type": "enable_speech_barge_in"
},
{
"type": "text_to_speech",
"barge_in_occurred": true,
"streaming_statistics": {
"transaction_id": "eafdd846-2829-4e1a-8068-b1035510b1e1",
"start_timestamp": "2021-10-12T20:54:14.795Z",
"stop_timestamp": "2021-10-12T20:54:20.388Z",
"response_milliseconds": 447
}
}
]
},
{
"assistant": {
"log_id": "07d74b35-0205-43e4-923c-1e43e1cb429c",
"response_milliseconds": 0,
"start_timestamp": "2021-10-12T20:54:20.377Z"
},
"request": {
"type": "hangup"
},
"response": ]
}
]
}
]
}

Show more

The payload JSON object for a call detail record event contains the following keys:



Keys for the payload object

 Key Type Description 

 primary_phone_number string The phone number that was called. 
 global_session_id string The unique session identifier. 
 failure_occurred Boolean Indicates whether a failure occurred during the call. 
 failure_details string Details about a failure. 
 transfer_occurred Boolean Indicates whether an attempt was made to transfer a call
My connection is down after scheduled Direct Link maintenance. What should I do? 

There is no connectivity after scheduled maintenance on my direct link.

  What’s happening 

My connection is down.

  Why it’s happening 

Possible causes:



1.  Address Resolution Protocol (ARP) cache issue
2.  Border Gateway Protocol (BGP) negotiation failure



  How to fix it 

Resolution:



1.  Clear ARP on your network gear.

Since IBM is moving the link to a different router, the MAC address associated with our IP address changes. If your router does not accept gratuitous ARP, connectivity might be down until the ARP cache is cleared on your router.
2.  Open a ticket to troubleshoot BGP sessions.

The new router is running a newer version of firmware that supports more BGP capabilities. If BGP was established before the move, but does not establish after the move, IBM opens a ticket on your account to troubleshoot the problem after the maintenance is completed.
Such provisioning delays are not subject to SLAs or credits. Ordered systems can be returned to inventory (after customer data is expunged) if the customer does not respond quickly.

Likewise, if a VRA or firewall is bypassed after an order is placed, it's still likely that the order will fail. There might be a narrow window during which automation retries are attempted. It is best that the entire provision process proceed without network interference.
* What firewall products does IBM offer?

To find a detailed comparison of all firewall products that are offered in IBM Cloud, see [Exploring firewalls](https://cloud.ibm.com/docs/fortigate-10g?topic=fortigate-10g-exploring-firewalls).
* Can a VRA confound customer support efforts?

Yes, for the preceding reasons. VRA is a black box: VLANs go in, VLANs come out, and IBM Support doesn't know what customers are doing with packets in-between.

IBM Support always does its best, but with VRA and dedicated firewall:



1. Customer privacy trumps connectivity.
2. Our standard support staff is not equipped to analyze poorly formed or highly complex VRA or firewall configurations.



As a first diagnostic step, IBM Support might require you to put your VRA or firewall VLANs in bypass mode. If, in this state, provisions that failed start going through, the issue is likely with your VRA or firewall configuration.
* What effect does VRA have on my network performance?

Keep in mind that even though they can't see you, a public cloud shares networks with other customers. True, best-case VRA throughput is determined by available network capacity at a point in time, plus the distance the data must travel.

These variables aside, VRA is capable of forwarding 80 Gbps of unmodified traffic across multiple interfaces, using the rough formula that every 10 Gbps of throughput requires one full processor core (not including hyperthread).
In the event of a catastrophic failure impacting an entire region, and the Direct Link physical link between on-premises and IBM Cloud was in that region, you would experience an outage. If you require a highly available connection to IBM Cloud, it is imperative that you have a redundant connection in a second region. If you decide to rely on a single connection, it is recommended that you back up all configuration elements in case you would ever have to recreate your Direct Link gateway and virtual connections. For information on how to design Diversity to achieve HA with Direct Link, see [Models for diversity and redundancy in Direct Link](https://cloud.ibm.com/docs/dl?topic=dl-models-for-diversity-and-redundancy-in-direct-link).



 Backing up Direct Link gateways for disaster recovery 

You must be prepared to recreate your Direct Link gateways and connections. This section helps you ensure that you have all the data needed.

Direct Link backups are cross-regionally durable. Backups are stored across multiple regions, and are restorable to other regions.

Preserve a list of all your direct links and their connections. To do so, perform the following procedure:

The following steps use the IBM Cloud CLI, but you can also use the IBM Cloud console or API.



1. Use the ibmcloud dl gateways command to list details about all your direct links. Save this output.
2. For each gateway, use the ibmcloud dl virtual-connections GATEWAY_ID command to list information about its connections. Save this output.



For more information, see the [Direct Link CLI reference](https://cloud.ibm.com/docs/dl?topic=dl-cli-plugin-dl-cli).

Saving the information returned from these commands helps you recover from a failure quickly. In the event of a failure, use the saved information and run the ibmcloud dl gateway-create and ibmcloud dl virtual-connection-create commands to recreate your direct links and their connections.
(https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-v2-troubleshootingibp-v2-troubleshooting-hsm-proxy)
* [Why are my transactions returning an endorsement policy error: signature set did not satisfy policy?](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-v2-troubleshootingibp-v2-troubleshooting-endorsement-sig-failure)
* [Why are the transactions I submit from VS Code failing with a No endorsement plan available error?](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-v2-troubleshootingibp-v2-troubleshooting-anchor-peer)
* [Why are the transactions I submit from VS Code failing with an endorsement failure?](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-v2-troubleshootingibp-v2-troubleshooting-endorsement)
* [Why is my peer unable to communicate with my ordering node?](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-v2-troubleshootingibp-v2-troubleshooting-peer-bad-connection)
* [When I hover over my node, the status is red, what does this mean?](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-v2-troubleshootingibp-v2-troubleshooting-status-error)
* [How do I disable the network policies in my namespace?](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-v2-troubleshootingibp-v2-troubleshooting-disable-network-policies)
* [How do I delete a peer pod?]
Body: streamToUpload
};
s3Client.upload(params, function(err, data) {
debug('S3 upload done');
if (err) {
debug(err);
reject(new Error('S3 upload failed'));
return;
}
debug('S3 upload succeeded');
debug(data);
resolve();
}).httpUploadProgress = (progress) => {
debug('S3 upload progress: ${progress}');
};

debug('Starting streaming data from ${sourceUrl}');
couchbackup.backup(
sourceUrl,
streamToUpload,
(err, obj) => {
if (err) {
debug(err);
reject(new Error('CouchBackup failed with an error'));
return;
}
debug('Download from ${sourceUrl} complete.');
streamToUpload.end(); // must call end() to complete S3 upload.
// resolve() is called by the S3 upload
}
);
});
}
Show more





 Other disaster recovery options 

Return to the [IBM Cloudant Disaster Recovery guide](https://cloud.ibm.com/docs/Cloudant?topic=Cloudant-disaster-recovery-and-backupdisaster-recovery-and-backup) to find out about the other features IBM Cloudant offers for a full disaster recovery setup.
BXNUI3065E 

Message: A problem occurred while contacting IBM Virtual Servers.

Try again later. If the problem continues, go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI3066E 

Message: The attempt to migrate your app failed because we couldn't contact Cloud Foundry to switch your app to Diego.

Try again. If you see this message again, contact [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI3067E 

Message: The attempt to roll your app back to DEA failed because we couldn't contact Cloud Foundry.

Try again. If you see this message again, contact [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).
Such provisioning delays are not subject to SLAs or credits. Ordered systems can be returned to inventory (after customer data is expunged) if the customer does not respond quickly.

Likewise, if a VRA or firewall is bypassed after an order is placed, it's still likely that the order will fail. There might be a narrow window during which automation retries are attempted. It is best that the entire provision process proceed without network interference.





 What firewall products does IBM offer? 

To find a detailed comparison of all firewall products that are offered in IBM Cloud, see [Exploring firewalls](https://cloud.ibm.com/docs/fortigate-10g?topic=fortigate-10g-exploring-firewalls).





 Can a VRA confound customer support efforts? 

Yes, for the preceding reasons. VRA is a black box: VLANs go in, VLANs come out, and IBM Support doesn't know what customers are doing with packets in-between.

IBM Support always does its best, but with VRA and dedicated firewall:



1. Customer privacy trumps connectivity.
2. Our standard support staff is not equipped to analyze poorly formed or highly complex VRA or firewall configurations.



As a first diagnostic step, IBM Support might require you to put your VRA or firewall VLANs in bypass mode. If, in this state, provisions that failed start going through, the issue is likely with your VRA or firewall configuration.





 What effect does VRA have on my network performance? 

Keep in mind that even though they can't see you, a public cloud shares networks with other customers. True, best-case VRA throughput is determined by available network capacity at a point in time, plus the distance the data must travel.

These variables aside, VRA is capable of forwarding 80 Gbps of unmodified traffic across multiple interfaces, using the rough formula that every 10 Gbps of throughput requires one full processor core (not including hyperthread).