vania-janet/multiturn-rag-retrieval-data huggingface dataset:
returned error: VSCC error: endorsement policy failure, err: signature set did not satisfy policy

 Why it’s happening 

If you have recently joined a channel and installed the smart contract, this error occurs if you have not added your organization to the endorsement policy. Because your organization is not on the list of organizations who can endorse a transaction from the smart contract, the endorsement from your peers is rejected by the channel. If you encounter this problem, you can change the endorsement policy by upgrading the smart contract. For more information, see [Specifying an endorsement policy](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-smart-contracts-v2ibp-console-smart-contracts-v2-install-propose) and [Versioning a smart contract](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-smart-contracts-v2ibp-console-smart-contracts-v2-versioning).





 Why are the transactions I submit from VS Code failing with a No endorsement plan available error? 

 What’s happening 

Transactions submitted from VS Code fail with an error similar to:

Error submitting transaction: No endorsement plan available for {"chaincodes":[{"name":"hello-world"}]}

 Why it’s happening 

This error occurs if you are using the Fabric Service Discovery feature but did not configure any anchor peers on your channel.

 How to fix it 

Follow step three of the [private data topic](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-smart-contracts-v2ibp-console-smart-contracts-v2-private-data) in the Deploy a smart contract tutorial to configure your anchor peers.





 Why are the transactions I submit from VS Code failing with an endorsement failure? 

 What’s happening
Connectivity is resumed, and access can be re-routed to Dallas when service is restored.



When sending requests to a tethered endpoint there is no automated failover if that region becomes unavailable.

For contrast, imagine another application using the normal US cross-region endpoint:



1. The application creates a client using the https://s3.us.cloud-object-storage.appdomain.cloud endpoint.
2. The Object Storage service in Dallas suffers an outage.
3. All Object Storage requests are automatically rerouted to San Jose or Washington until service is restored.





 Tethered endpoint reference 

Public

Private

Direct



Table 1. Cross Region Endpoints

 Region Type Endpoint 

 US: Dallas Public (Tethered) s3.dal.us.cloud-object-storage.appdomain.cloud 
 US: San Jose Public (Tethered) s3.sjc.us.cloud-object-storage.appdomain.cloud 
 US: Washington, D.C. Public (Tethered) s3.wdc.us.cloud-object-storage.appdomain.cloud 
 EU: Amsterdam Public (Tethered) s3.ams.eu.cloud-object-storage.appdomain.cloud 
 EU: Frankfurt Public (Tethered) s3.fra.eu.cloud-object-storage.appdomain.cloud 
 EU: Milan Public (Tethered) s3.mil.eu.cloud-object-storage.appdomain.cloud 
 AP: Tokyo Public (Tethered) s3.tok.ap.cloud-object-storage.appdomain.cloud 
 AP: Sydney Public (Tethered) s3.syd.ap.cloud-object-storage.appdomain.cloud 
 AP: Osaka Public (Tethered) s3.osa.ap.cloud-object-storage.appdomain.cloud 







 Tethered endpoint reference 

Public

Private

Direct



Table 2. Cross Region Static Web Endpoints

 Region Hosted Static Website Endpoint 

 US: Dallas s3-web.dal.us.cloud-object-storage.appdomain.cloud
* [Failure during step two: Migrating Fabric nodes](https://cloud.ibm.com/docs/blockchain?topic=blockchain-migrating-to-hlf-supportfailure-during-step-two-migrating-fabric-nodes)



* [Post-migration considerations](https://cloud.ibm.com/docs/blockchain?topic=blockchain-migrating-to-hlf-supportibp-post-migration-considerations)



* [Deleting the TLSCopy CronJob (Only For IBM Kubernetes Service)](https://cloud.ibm.com/docs/blockchain?topic=blockchain-migrating-to-hlf-supportdeleting-the-tlscopy-cronjob-only-for-ibm-kubernetes-service)
* [Checking the Ingresses](https://cloud.ibm.com/docs/blockchain?topic=blockchain-migrating-to-hlf-supportchecking-the-ingresses)
* [Deploying a new SaaS instance in same cluster as a migrated instance](https://cloud.ibm.com/docs/blockchain?topic=blockchain-migrating-to-hlf-supportdeploying-a-new-saas-instance-in-same-cluster-as-a-migrated-instance)





[Administering your console](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-manage-consoleibp-console-manage-console)



* [Refreshing your console](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-manage-consoleibp-console-refresh)
* [Adding and removing users from the console](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-manage-consoleibp-console-manage-console-add-remove)
Why do I get an R0043 error after setting up Direct Link? 

  What’s happening 

After you set up Direct Link, you see a message similar to one of the following messages.

R0043: The location does not meet the following requirement: Hosts must have TCP/UDP/ICMP Layer 3 connectivity for all ports across hosts. If you still have issues, contact IBM Cloud Support and include your Satellite location ID.

Oct 7 12:02:09 satellite-link-tunnel-74b648978b-jw4mr satellite-link-tunnel-container 50 flowlog: error when client 10.211.100.161:57124 connecting to a96ff1d0c68e3e5e087b3-6b64a6ccc9c596bf59a86625d8fa2202-ce00.us-east.satellite.appdomain.cloud:30000, conn_type: location, detail: connect ECONNREFUSED 10.0.2.80:30000

  Why it’s happening 

Your host doesn't meet the requirements or it needs to be rebooted.

  How to fix it 

Follow these steps to resolve your issue



1.  Verify that your host meets the requirements. For more information see [Host network requirements](https://cloud.ibm.com/docs/satellite?topic=satellite-reqs-host-network).
2.  If your host meets the requirements, perform an nslookup on your location subdomain to retrieve the IP address of the host that is registered with this subdomain.
3.  Find the host in your infrastructure provider and reboot the host.
4.  If the reboot does not resolve the issue, replace the host.
5.  If you are still unable to resolve the issue, [open a support case](https://cloud.ibm.com/docs/satellite?topic=satellite-get-helphelp-support). In the support case description, include all debugging steps that you followed and the output from these steps.
* The real interface addresses on the native vlans (e.g. dp0bond1: 169.110.20.28/29) are not always in the same subnet as their VIPs (169.110.21.26/29).







 Manual VRRP failover 

If you need to force a VRRP failover, it can be achieved by running the following on the device that currently is VRRP master:

vyatta@vrouter$ reset vrrp master interface dp0bond0 group 1

The group ID is the VRRP group ID of the native interfaces, and, as mentioned above, could be different in your pair.





 Connection synchronization 

When two VRA devices are in an HA pair, it might be useful to track stateful connections between the two devices so that if a failover happens, the current state of all connections that are on the failed device are replicated to the backup device. It isn't necessary for any current active sessions (like SSL connections) to be rebuilt from scratch, which can result in a disrupted user experience.

This is called connection tracking synchronization.

To configure it, you must declare what the failover method is, which interface you use to send the connection tracking information, and the IP of the remote peer:

set service connsync failover-mechanism vrrp sync-group SYNC1
set service connsync interface dp0bond0
set service connsync remote-peer 10.124.10.4

The other VRA has the same configuration, but a different remote-peer.

Note that this can saturate a link if there is a high number of connections coming in on other interfaces, and competes with other traffic on the declared link.





 VRRP Start Delay feature 

Vyatta OS version 1801p and greater includes a new vrrp command.

vrrp specifies an election protocol that dynamically assigns responsibility for a virtual router to one of the VRRP routers on a LAN. The VRRP router controlling the IPv4 or IPv6 addresses associated with a virtual router is called the Master, and it forwards packets that are sent to these IPv4 or IPv6 addresses.
Go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI2080E 

Message: The operation timed out while certificates and keys were being modified.

Go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI2081E 

Message: The certificates and keys weren't modified because an unknown error occurred: {0}.

Go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI2082E 

Message: The contents of the uploaded certificate wasn't read because a problem occurred: {0}.

Go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI2083E 

Message: The request to an extension of Business Support Systems could not be completed.

Go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI2084E 

Message: The list of countries that support payment could not be retrieved.

Go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI2085E 

Message: The pricing cost calculation cannot be parsed.

Go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI2086E 

Message: During an attempt to retrieve uploaded certificates, the organization could not be found.

Go to [IBM Cloud Support](https://cloud.ibm.com/unifiedsupport/supportcenter).





 BXNUI2087E 

Message: The app name is too long. This app name is limited to {0} characters.

Try again with a shorter name.





 BXNUI2088E 

Message: The action that you requested wasn't completed because the CSRF token is missing or invalid.
See [HCX troubleshooting](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-hcxclient-troubleshooting) and [VMware HCX troubleshooting](https://docs.vmware.com/en/VMware-HCX/services/user-guide/GUID-B6CF4054-9C8C-43DE-AC67-01AE0679B190.html). 
 HCX Cloud Database Upgrade Failed Not considered essential for notification as upgrades would be managed. See [HCX troubleshooting](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-hcxclient-troubleshooting) and [VMware HCX troubleshooting](https://docs.vmware.com/en/VMware-HCX/services/user-guide/GUID-B6CF4054-9C8C-43DE-AC67-01AE0679B190.html). 
 HCX Enterprise Database Upgrade Failed Not considered essential for notification as upgrades would be managed. See [HCX troubleshooting](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-hcxclient-troubleshooting) and [VMware HCX troubleshooting](https://docs.vmware.com/en/VMware-HCX/services/user-guide/GUID-B6CF4054-9C8C-43DE-AC67-01AE0679B190.html). 
 HCX Interconnect tunnel status Configure to send email one time for a critical tunnel status is down event. See [Network (WAN) connectivity](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-hcxclient-troubleshootinghcxclient-troubleshooting-wan-connect). 







 Events and alarms procedures
Refer to [Correcting error 1125](https://cloud.ibm.com/docs/vsrx?topic=vsrx-correcting-readiness-errorscorrecting-1125) for more information.





 Error 1126 

The gateway control link is down. Ensure vnet0 and vnet1 are configured on the Ubuntu host and retry.





 Error 1127 

The Ubuntu host is missing an ethernet interface in bond0. Ensure bond0 includes the 2 private ethernet interfaces.





 Error 1128 

The Ubuntu host is missing an ethernet interface in bond1. Ensure bond1 includes the 2 public ethernet interfaces.





 Error 1129 

The Ubuntu host has an extra ethernet interface in bond0. Ensure bond0 only includes the 2 private ethernet interfaces.





 Error 1130 

The Ubuntu host has an extra ethernet interface in bond1. Ensure bond1 only includes the 2 public ethernet interfaces.





 Error 1131 

The vSRX configuration is using a hidden cli command not compatible with the automation. Remove and replace the address-range command syntax and retry.





 Error 1132 

The Ubuntu host has a kvm xml configuration that is missing the default telnet configuration used for console access. Add this configuration back and retry.





 Error 1133 

The vSRX console connection via telnet timed out executing commands. Please rerun or contact support.





 Error 1134 

The node being OS reloaded cannot access the other node in the cluster. Ensure the other node is active and retry. If both nodes are unrecoverable contact support to run Rebuild Cluster.





 Error 1135 

The vSRX license file cannot be found. Please rerun or contact support.





 Error 1136 

The vSRX license file is found, but the contents are empty. Please rerun or contact support.





 Error 1137 

The vSRX license file cannot be read. Please rerun or contact support.





 Error 1138 

The vSRX license install has failed during the vSRX license configuration. Please rerun or contact support.





 Error 1139
Try again or contact [IBM Support](https://cloud.ibm.com/docs/vsrx?topic=gateway-appliance-getting-help).





 Error 1112 

The gateway experienced a precheck setup failure due to a cluster error. Ensure redundancy group 0 is online and has no monitor-failures.





 Error 1113 

The host experienced a precheck setup failure and is unable to determine the status of the host VM using virsh. Try again or contact [IBM Support](https://cloud.ibm.com/docs/vsrx?topic=gateway-appliance-getting-help).





 Error 1114 

The host has a precheck setup failure because insufficient memory is installed on the bare-metal server. A minimum of 32 GB is required. Contact [IBM Support](https://cloud.ibm.com/docs/vsrx?topic=gateway-appliance-getting-help) to install the required amount of memory.





 Error 1115 

The gateway has a precheck setup failure due to an incompatible SSH connection limit in the vSRX configuration. Remove the SSH connection limit from the vSRX configuration and retry.





 Error 1116 

The host has a precheck setup failure, Ubuntu is missing the telnet software package. Install telnet and retry.





 Error 1117 

The host's Ubuntu mirror server is not accessible. Retry the operation once the mirror is accessible.





 Error 1118 

The vSRX node is not started. Start the vSRX VM and retry the operation.





 Error 1119 

The vSRX node's VM is running but the node is not accessible via telnet. Exit from all console (telnet) sessions and retry the operation.





 Error 1120 

The vSRX node does not have a valid license. Remove any evaluation licenses and apply a valid license. Then retry the operation.
* [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)
* [Why is my first invoke 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)
* [Why does my blockchain node fail to restart?](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-v2-troubleshootingibp-v2-troubleshooting-restart)
* [What is the proper way to clean up a failed node deployment?](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-v2-troubleshootingibp-v2-troubleshooting-cleanup)
* [How can I view my smart contract container logs?](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-v2-troubleshootingibp-console-smart-contracts-troubleshoot-entry2)
* [Why is my CA, peer, or ordering node that is configured to use HSM not working?]
For more help, contact [support](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-gettinghelp) or open a support case.

Running a file system check might cause data loss, so make sure that your data is backed up.







 Why does my server have connectivity issues? 



 Why it's happening 

If your server has connectivity issues, the server might experience packet drops or packet loss and intermittent network connectivity.





 How to fix it 

When your server faces a connectivity issue, you need to gather the following information if you need to escalate the issue with IBM Cloud® support.



* Nongraphical MTR and traceroute from the server to user location.
* Nongraphical MTR and traceroute from user location to the server.
* Hundred ping count from the server to user location.
* Hundred ping count from user location to the server.





 Linux 

If your server uses Linux, run the following command to gather the nongraphical MTR information.

mtr -r -c 100 -n

To gather the Linux traceroute information, use the following Linux command.

traceroute





 Windows 

If your server uses Windows, you can use the [WinMTR tool](http://sourceforge.net/projects/winmtr/) to gather the nongraphical MTR and traceroute information.

To gather the Windows traceroute information, run the tracert command in the command prompt. Click Start > Run > cmd > click OK and type tracert.







 Next steps 

After the tests complete, paste the results into the support case. You can also attach the results as a file or image.

Make sure that you include the IP address that you are using to connect to the server.

Disable your firewall, or allow echo and ICMP requests so that server traffic isn't dropped.

For more help, contact [support](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-gettinghelp).
Create new peers, by using the CA you that imported from cluster one as the peer's CA. Use the peer organization MSP that you imported from cluster one as the peer organization MSP definition.
3. In cluster two and three, you can now repeat the steps that you ran to join the peers to the same channel as the peer in cluster one.
4. After you install the smart contract on these redundant peers, they are able to transact and query the ledger.
5. Again, if you plan to use service discovery, private data, and peer gossip, you need to make each redundant peer an anchor peer.



Your network is now configured such that a failure in any single region will not affect the peer workload.

To maximize your HA even further, consider the following additional options:



* Export the peers that you created in clusters two and three and import them into the console in cluster one. Then, everything can be managed from a single cluster.
* However, cluster one can fail. Therefore, to further account for a cluster failure, you can import all your peers into each of the three consoles. Then if a cluster containing any one console fails, everything can still be managed from the consoles in the other two clusters.
You might have extra charges from your exchange provider or network service provider. Refer to your providers for their fee information.
* How can I achieve redundancy with IBM Cloud Direct Link?

Direct Link does not provide an inherently Redundant service. Direct Link can provide Diverse connections that enable customers to create redundancy via BGP. You can achieve diversity with Direct Link by connecting to more than one IBM Cloud Direct Link Dedicated provider or Exchange provider for IBM Cloud. Alternatively, with Exchange and Connect you can use diverse network-to-networks (NNIs) with the IBM Cloud Direct Link providers.
* What is the difference between the default "local" routing and the global routing add-on for Direct Link?

The local routing option is the default routing option. If your Direct Link is connected at the local PoP, it provides access to all data centers within that same market. In some markets, local routing is applicable for stand-alone PoP locations and direct links that are terminated at the data center.

With our standard Direct Link offering, you can send traffic between the data centers in your selected region. If you need access to other data centers outside of the specified region, you must order the global routing add-on. For example, you might use global routing to share workloads between dispersed IBM Cloud resources (such as Dallas to Ashburn, or Dallas to Frankfurt).
* Why does a global routing add-on package exist for Direct Link?

The global routing add-on prevents our customers from experiencing unexpected data costs when traversing outside of their data center's local market. It keeps costs lower for most of our customers, and it provides the ability for customers with a global presence to reach all regions across the globe easily. However, usually a customer requires only a local bandwidth package.
* If I am connected to a Direct Link Dedicated, Direct Link Connect, or Direct Link Exchange in a region such as Dallas, do I have access to other regions in the US through Direct Link?

Yes, you are able to gain access to areas outside of your local market if you choose the global routing add-on. If this option is not selected, your Direct Link traffic is limited to the local market for the PoP or DC location you selected.
* Can I connect to any available region from a given Direct Link location?
Verizon SCI is one of several MPLS based, Layer-3 (IP VPN) services. It requires that IBM establish BGP with Verizon instead of directly with the customer. Verizon then establishes BGP with the customer and advertises routes accordingly. Several other Layer-3 based service providers participate in the Direct Link Connect program. Customers need to be aware of what they are ordering and how their account will behave when connecting to IBM Cloud.
* Does Direct Link support any type of QoS?

We are unable to support any QoS guarantees. QoS requires MPLS mapping between each of our service suppliers and IBM Cloud. Cloud Service providers generally cannot support QoS because it must reach from end-to-end and involve every device in between. No workaround is currently available by "tunneling" or any other method.
* Does Direct Link support Jumbo frames?

Jumbo frames (up to 9214 bytes) are supported on Dedicated and Dedicated Hosting. 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.