vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* Ensure that the service mesh and extended networks between the on-premises source site and the IBM Cloud target sites are deleted. To remove the service mesh and extended networks, use the HCX user interface in the on-premises VMware vSphere Web Client.
* Ensure that the site pairings between the on-premises source site and the IBM Cloud target sites are removed. To remove the site pairings, use the HCX user interface in the on-premises VMware vSphere Web Client.
* If you delete a workload cluster and that cluster is the service mesh cluster, the HCX service is automatically deleted.
* The deletion of HCX is automated. The following procedures are completed for the successful deletion of this service:



* The HCX license that is ordered for the cloud-side HCX Manager is deactivated.
* HCX Manager is deleted.
* The vMotion IP addresses that were reserved for HCX are released.
* The HCX management edge appliances are deleted.





Only the VMs that were deployed during the initial installation of the HCX instances are deleted. Any node that is deployed after the installation is not cleaned up.





 Related links 



* [Ordering HCX](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-hcx_ordering)
* [Managing HCX](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-managinghcx)
* [Glossary of HCX terms](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-hcx_glossary)
* [Contacting IBM Support](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-trbl_support)
* [VMware Hybrid Cloud Extension overview](https://cloud.vmware.com/vmware-hcx)
* UI
* CLI
* API







 Deleting an endpoint gateway 

You can delete an endpoint gateway by using the UI, the CLI, or the API.



 Deleting an endpoint gateway in the UI 

To delete an endpoint gateway, follow these steps:



1. Navigate to the list of endpoint gateways for VPC. From the [IBM Cloud® console](https://cloud.ibm.com/login), select the Menu icon ![Menu icon](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/vpc//images/menu_icon.png), then click VPC Infrastructure > Virtual private endpoint gateways in the Network section.

The Virtual private endpoint gateways for VPC page shows all endpoint gateways for all VPCs in the region.
2. Click the Actions menu ![Actions menu](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/vpc/images/overflow.png) next to the endpoint gateway you want to delete, then click Delete. Click Delete again to confirm the deletion.



If you previously selected the auto-delete option for attached IP addresses, any attached reserved IPs are also deleted.





 Deleting an endpoint gateway from the CLI 

Before you begin, make sure to [set up your CLI environment](https://cloud.ibm.com/docs/vpc?topic=vpc-infrastructure-cli-plugin-vpc-reference).

To delete an endpoint gateway by using the CLI, run the following command:

ibmcloud is endpoint-gateway-delete ENDPOINT_GATEWAY [-f, --force]

Where:



* ENDPOINT_GATEWAY is the ID of the endpoint gateway.
If not set, the context instance specified by ibmcloud cis instance-set INSTANCE is used.--output: Specify output format, only JSON is supported.<-- </section "id="section-update-range-app-options" "> --><-- <section "id="section-update-range-app-examples" "> --> Examples Update range app ea95132c15732412d22c1476fa83f27a. ibmcloud cis range-app-update 31984fea73a15b45779fa0df4ef62f9b ea95132c15732412d22c1476fa83f27a --json '{"protocol":"tcp/22", "dns":{"type":"CNAME","name":"ssh.example.com"}, "origin_direct":"tcp://1.2.3.4:22"] ! ! ! , "proxy_protocol":"off", "ip_firewall":true, "tls":"full", "edge_ips":{"type":"dynamic", "connectivity":"all"}, "traffic_type":"direct"}' -i "cis-demo"
<-- </section "id="section-update-range-app-examples" "> --><-- </section "id="section-update-range-app" "> --><-- <section "id="section-delete-range-app" "> --> ibmcloud cis range-app-delete Delete a previously existing application (Enterprise plan only). ibmcloud cis range-app-delete DNS_DOMAIN_ID APP_ID --instance INSTANCE] ! ! ! ! ! !
<-- <section "id="section-delete-range-app-options" "> --> Command options DNS_DOMAIN_ID: The ID of DNS domain.
Show more
<-- </section "id="section-command-example-origin-certificate-create" "> --><-- </section "id="section-origin-certificate-create" "> --><-- <section "id="section-origin-certificate" "> --> ibmcloud cis origin-certificate Get details of a given origin certificate. ibmcloud cis origin-certificate DNS_DOMAIN_ID CERT_ID --instance INSTANCE_NAME] --output FORMAT] ! ! ! ! ! !
<-- <section "id="section-command-options-origin-certificate" "> --> Command options DNS_DOMAIN_ID: The ID of DNS domain. Required.CERT_ID: The ID of Origin Certificate. Required.-i, --instance: Instance name or ID. If not set, the context instance specified by ibmcloud cis instance-set INSTANCE is used.--output: Specify output format, only JSON is supported.<-- </section "id="section-command-options-origin-certificate" "> --><-- <section "id="section-command-example-origin-certificate" "> --> Examples Get details of origin certificate a5836c2a7ea72d2e225890caea70ae32. ibmcloud cis origin-certificate 31984fea73a15b45779fa0df4ef62f9b a5836c2a7ea72d2e225890caea70ae32 -i cis-demo --output JSON
<-- </section "id="section-command-example-origin-certificate" "> --><-- </section "id="section-origin-certificate" "> --><-- <section "id="section-origin-certificate-delete" "> --> ibmcloud cis origin-certificate-delete Delete an origin certificate. ibmcloud cis origin-certificate-delete DNS_DOMAIN_ID CERT_ID --instance INSTANCE_NAME] ! ! !
[Delete icon](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/icons/delete.svg) to delete the cluster.



4. Click a cluster name to view the ESXi server, storage, and network interface details.



ESXi server details

Additional ESXi server details

Storage details



Table 1. ESXi server details

 Item Description 

 Name The name of the ESXi server is in the following format: <host_prefix><n>.<root_domain>, where n is the sequence of the ESXi server. 
 Hardware The hardware specification. 
 Credentials The username and password to access the ESXi server. 
 Private IP The private IP address of the ESXi server. 
 Status The status of the ESXi server, which can be one of the following values: <br>Available The ESXi server is ready to use. <br>Adding The ESXi server is being added. <br>Deleting The ESXi server is being deleted. 



Click View resource to access the VLAN details, including the subnet details and IP details.

Subnet details

IP details



Table 2. Network interface - Subnet details

 Item Description 

 Name The subnet name. Click the name to access the subnet details. 
 Type The type of subnet: primary or portable. 
 Description The description of the subnet. 







 Related links 



* [Viewing Cyber Recovery instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-cr_viewinginstances)
* [Adding ESXi servers to CR instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-cr_addingservers)
ibmcloud cis page-rule-update 31984fea73a15b45779fa0df4ef62f9b a5836c2a7ea72d2e225890caea70ae32 --json '{"targets":{"target":"url", "constraint":{"operator":"matches", "value":"example.com/images/"}}], "actions":{"id":"always_online", "value":"on"}] ! ! ! ,"priority":1, "status":"active"}' -i cis-demo --output JSON
<-- </section "id="section-command-examples-page-rule-update" "> --><-- </section "id="section-page-rule-update" "> --><-- <section "id="section-page-rule-delete" "> --> ibmcloud cis page-rule-delete Delete a page rule of the DNS domain. ibmcloud cis page-rule-delete DNS_DOMAIN_ID PAGE_RULE_ID -i, --instance INSTANCE] ! ! ! ! ! !
<-- <section "id="section-command-options-page-rule-delete" "> --> Command options DNS_DOMAIN_ID: The ID of DNS domain. Required.PAGE_RULE_ID: The ID of page rule. Required.-i, --instance: Instance name or ID. If not set, the context instance specified by ibmcloud cis instance-set INSTANCE is used.<-- </section "id="section-command-options-page-rule-delete" "> --><-- <section "id="section-command-examples-page-rule-delete" "> --> Examples Delete page rule a5836c2a7ea72d2e225890caea70ae32.
Follow any other directions in the enroll wizard and click submit.
6. If you browse back to the nodes page and select the Orderer Cluster tile, the TLS identity error should be gone.







 Removing an existing system channel 

The process of removing an existing system channel is to remove the system channel configuration from each ordering node. You should first place the system channel into maintenance mode (step 2 below) to prevent any application channels from being created while the system channel is being removed. You will then unjoin the system channel from each orderer node (step 3 below) using the Fabric Operations console, as follows:



1. Ensure that each ordering node in the Ordering Service is running Fabric v2.4.x or higher
2. Place the system channel into maintenance mode, using the Fabric Operations console UI, as follows:



* From the Nodes tab, click the Ordering cluster tile
* Click the Ordering nodes tab
* Click the settings (gear) icon
* Click the Maintenance button
* Follow the prompts to turn maintenance mode on



3. Remove the system channel from all ordering nodes, using the Fabric Operations console UI, as follows:



* From the Nodes tab, click the Ordering cluster tile
* Remain on the Details tab
* Click the unjoin (trash can) icon on the system channel tile
* Follow the prompts to unjoin each ordering node from the system channel



4. Complete the process by upgrading the Node.js chaincode from Peer v1.4.x to v2.4.x







 Upgrading Node.js chaincode 

You may need to be cautious about upgrading peers and orderers to use the system channel removal features. Hyperledger Fabric v2.4 updated its chaincode version of Node.js to v16 and removed support for the earlier Node.js v12. If you are upgrading your peers and orderers to use the channel participation APIs, and are using Node.js v12 based chaincode, you must also incrementally upgrade the Node.js chaincode, as follows:



1.
* UI
* CLI
* API







 Deleting a workspace 

After you destroy all associated VPC resources, if you don't need the workspace anymore, you can also delete the Schematics workspace.

Make sure that you delete the resources in the workspace before you delete the workspace. If you delete the workspace without cleaning up the related resources, the resources would still be left behind and might have to be cleaned up individually.



 Deleting a workspace using the UI 



1. In the IBM Cloud console on the Schematics > Workspaces page, select Actions > Delete workspace to delete the schematics workspace.
2. Confirm the action by entering the workspace name in the text box and click Delete workspace.







 Deleting a workspace using the CLI 

Run the following command to delete your workspace:

ibmcloud schematics workspace delete --id <WORKSPACE_ID>

You can monitor the log files to view the deletion progress of your workspace.





 Deleting a workspace using the API 



1. To delete a workspace by using the IBM Cloud Schematics Python APIs, create a Python file and provide a name of your choice, for example, schematics_delete_workspace.py.
2. Copy and paste the [Delete a workspace using Schematics Python API](https://cloud.ibm.com/docs/ibm-spectrum-lsf?topic=ibm-spectrum-lsf-deleting-workspaceexample-request-delete-workspace) example request to your Python file.
3. Change the following parameters as part of the request:



* Replace your IBM Cloud key to the authenticator = IAMAuthenticator('<ibm-api-key>') variable.
[Delete icon](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/icons/delete.svg) to delete the cluster.



4. Click a cluster name to view the ESXi server, storage, and network interface details.



ESXi server details

Additional ESXi server details

Storage details



Table 1. ESXi server details

 Item Description 

 Name The name of the ESXi server is in the following format: <host_prefix><n>.<root_domain>, where n is the sequence of the ESXi server. 
 Hardware The hardware specification. 
 Credentials The user name and password to access the ESXi server. 
 Private IP The private IP address of the ESXi server. 
 Status The status of the ESXi server, which can be one of the following values: <br>Available The ESXi server is ready to use. <br>Adding The ESXi server is being added. <br>Deleting The ESXi server is being deleted. 



Click View resource to access the VLAN details, including the subnet details and IP details.

Subnet details

IP details



Table 2. Network interface - Subnet details

 Item Description 

 Name The subnet name. Click the name to access the subnet details. 
 Type The type of subnet: primary or portable. 
 Description The description of the subnet. 







 Related links 



* [Viewing vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_viewinginstances)
* [Expanding and contracting capacity for vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_addingservers)
If a boot volume created as part of provisioning a virtual server instance, the volume will be deleted by default when the instance is deleted. After you confirm the delete action, the process to delete the instance and its associated vNIC, boot volume, and data begins. The delete action can take up to 30 minutes, but when the process is complete, the instance no longer appears on the virtual server instances page.





 Delete a virtual server instance using the CLI 

You can delete the virtual server instance in your IBM Cloud VPC by using the command-line interface (CLI).

If the instance has a floating IP address, it must be unassociated or released before the instance is deleted. The account associated with the floating IP will continue to be charged if it is not released.

To delete the virtual server instance by using the CLI, use the ibmcloud is instance-delete command. Specify the ID or name of the virtual server instance that you want to delete by using the INSTANCE variable.

ibmcloud is instance-delete INSTANCE

For a full list of command options, see [ibmcloud is instance-delete](https://cloud.ibm.com/docs/vpc?topic=vpc-vpc-referenceinstance-delete).

The delete action permanently removes an instance and its connected vNIC, and data from your account. The instance boot volume is also deleted if the volume auto-delete setting is configured to be deleted when the attached instance is deleted. If an existing boot volume is attached as part of provisioning a virtual server instance, the volume is preserved by default when the instance is deleted. If a boot volume created as part of provisioning a virtual server instance, the volume will be deleted by default when the instance is deleted. After you confirm the delete action, the process to delete the instance and its associated vNIC, boot volume, and data begins. The delete action can take up to 30 minutes, but when the process is complete, the instance no longer appears on the virtual server instances page.





 Delete a virtual server instance using the API 

You can delete the virtual server instance in your IBM Cloud VPC by using the API.
In the KMIP for VMware table, find the instance to delete.
3. In the Actions column, click the Delete icon ![Delete icon](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/icons/delete.svg).
4. In the Delete instance window, click OK.

The status of the instance is changed to Removing. When the instance deletion is completed, the instance is no longer available in the KMIP for VMware table.







 Related links 



* [Ordering KMIP for VMware instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-kmip_standalone_ordering)
* [Adding, viewing, and deleting certificates for KMIP for VMware instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-kmip_standalone_addingdeletingcert)
* [Viewing KMIP for VMware instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-kmip_standalone_viewing)
* [KMIP for VMware solution architecture](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-kmip-overview)
* [Auditing events for VMware Solutions](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-at-events)
Managing your CIS deployment 

You'll begin by using the Overview screen as your working base of operations. It shows all of the current parameters for your deployment.

Once you've set up your DNS and configured it, you are ready to go!



 Using the Overview screen 

Using the Overview screen, you can see the status of all your selections. Each setting links to the section of the user interface where the setting is configured. To modify any selection, you can navigate by clicking the link for the setting. For example, to change the load balancer configuration or add a new load balancer, click the Load Balancer field.

On the Overview screen, you might see that your domain name configuration is in Pending status, or in Active status. Pending status indicates that your domain is not fully set up, yet. You have to update your DNS provider or registrar with the name servers that are provided as part of the setup process.

Enterprise only: The Service Details section of the Overview also allows you to add additional domains to your instance of CIS, and to switch between multiple domains.





 Changing the Service mode 

In the Service Mode section of the Overview page is a list menu to select one of two modes:



* Defense Mode helps protect against existing or predicted DNS attacks. This mode prevents all traffic from reaching your origin servers through your domain.
* Pause Service disables all security and performance benefits to your domain. DNS functions still resolve for your website, but traffic is sent directly to configured origins.





 Setting up Service mode 



1. Select the mode you want from the list menu.
2. Click Activate mode.
3. Confirm or cancel the selection in the confirmation pop-up.



A notification appears on all pages to show that either Pause Service or Defense Mode is active. To return to normal operation, click Deactivate mode in the notification banner.







 Configuring and managing your DNS 

Go to the Reliability section, click the DNS tab and add a record. Type in the information about your DNS record and then click Add record to implement your changes.

After creating your records, consider turning on the Proxy setting. Most of the features of CIS require that the internet traffic to your site flow through CIS infrastructure.
To remove crypto units from an existing service instance, you need to [raise a support ticket](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-add-remove-crypto-unitsstep1-support-ticket-change-number).

On the Create a case page, enter Remove crypto units as the subject, and include the number of crypto units that you want to remove in the case description.

You need to keep at least two crypto units in a service instance for high availability.





 What's next 

Now you can use the new set of crypto units to manage encryption keys and perform cryptographic operations.



* Use Hyper Protect Crypto Services as the root key provider for other IBM Cloud services. For more information about integrating Hyper Protect Crypto Services, check out [Integrating services](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-integrate-services).
* To learn more about performing cryptographic operations with the cloud HSM, see [Introducing cloud HSM](https://cloud.ibm.com/docs/hs-crypto?topic=hs-crypto-introduce-cloud-hsm).
Troubleshooting 1000 class errors 

The following error codes appear in the HTML body of 530 error messages. For more information, see [Error 530](https://cloud.ibm.com/docs/cis?topic=cis-html-5xx-errors530-error).



 Error 1000: DNS points to prohibited IP 

CIS halted the request for one of the following reasons:



* An A record within your CIS DNS points to a CIS IP address.
* Your CIS DNS A or CNAME record references another reverse proxy (such as an nginx web server that uses the proxy_pass function) that then proxies the request to CIS a second time.
* The request X-Forwarded-For header is longer than 100 characters.
* The request includes two X-Forwarded-For headers.





 Resolution 



* If an A record within your CIS DNS points to a CIS IP address, update the IP address to your origin web server IP address.
* There is a reverse-proxy at your origin that sends the request back through the CIS proxy. Instead of using a reverse-proxy, contact your hosting provider or site administrator to configure an HTTP redirect at your origin.









 Error 1001: DNS resolution error 

Common causes for 1001 errors are:



* A web request was sent to a CIS IP address for a non-existent CIS domain.
* An external domain that is not on using CIS has a CNAME record to a domain active on CIS
* The target of the DNS CNAME record does not resolve.
* A CNAME record in your CIS DNS requires resolution via a DNS provider that is currently offline.
* Serve Stale Content is enabled for a Custom Hostname (SSL for SaaS) domain.





 Resolution 

A non-CIS domain cannot CNAME to a CIS domain unless the non-CIS domain is added to a CIS account.

Attempting to directly access DNS records used for CIS CNAME setups also causes error 1001.

Disable Always Online if using Custom Hostnames (SSL for SaaS).







 Error 1002: DNS points to Prohibited IP 

Common causes for 1002 errors when a DNS points to a prohibited IP address are:
<-- <section "id="section-command-options-access-enable" "> --> Command options -i , --instance value: Instance name or ID. If not set, the context instance specified by ibmcloud cis instance-set INSTANCE is used.<-- </section "id="section-command-options-access-enable" "> --><-- <section "id="section-command-example-access-enable" "> --> Examples Enable Mutual TLS for instance cis-demo. ibmcloud cis access-enable -i cis-demo
<-- </section "id="section-command-example-access-enable" "> --><-- </section "id="section-access-enable" "> --><-- </section "id="section-mtls-enable-cli-ref" "> --><-- <section "id="section-origin-certificates-cli-ref" "> --> Origin certificates <-- <section "id="section-origin-certificates" "> --> ibmcloud cis origin-certificates List all origin certificates for a given DNS domain. ibmcloud cis origin-certificates DNS_DOMAIN_ID --instance INSTANCE_NAME] --output FORMAT] ! ! ! ! ! !
<-- <section "id="section-command-options-origin-certificates" "> --> Command options DNS_DOMAIN_ID: The ID of DNS domain. Required.-i, --instance: Instance name or ID. If not set, the context instance specified by ibmcloud cis instance-set INSTANCE is used.--output: Specify output format, only JSON is supported.<-- </section "id="section-command-options-origin-certificates" "> --><-- <section "id="section-command-example-origin-certificates" "> --> Examples List all origin certificates for domain 31984fea73a15b45779fa0df4ef62f9b.
ibmcloud cis certificate-priority-change 31984fea73a15b45779fa0df4ef62f9b --json '{"certificates": {"id":"5a7805061c76ada191ed06f989cc3dac", "priority":2},{"id":"9a7806061c88ada191ed06f989cc3dac","priority":1}] ! ! ! }' -i "cis-demo"
<-- </section "id="section-change-priority-custom-examples" "> --><-- </section "id="section-change-priority-custom-cert" "> --><-- <section "id="section-delete-cert" "> --> ibmcloud cis certificate-delete Delete a dedicated or custom certificate. ibmcloud cis certificate-delete DNS_DOMAIN_ID CERT_ID -i, --instance INSTANCE] ! ! ! ! ! ! ! !
<-- <section "id="section-delete-cert-options" "> --> Command options DNS_DOMAIN_ID: The ID of DNS domain. Required.CERT_ID: The ID of dedicated or custom certificate. Required.-i, --instance: Instance name or ID. If not set, the context instance specified by ibmcloud cis instance-set INSTANCE is used.<-- </section "id="section-delete-cert-options" "> --><-- <section "id="section-delete-cert-examples" "> --> Examples Delete custom certificate 5a7805061c76ada191ed06f989cc3dac.