vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Managing Veeam licenses 

You can view, edit notes, or delete the Veeam® licenses that you ordered for stand-alone use.



 Procedure to view Veeam licenses 



1. From the IBM Cloud® for VMware Solutions console, click Licenses from the left navigation pane.
2. Scroll down to the Veeam licenses table.
3. To view the details of a specific license, click the license.



A license key is not displayed. When licenses are ordered, the system does not generate a key, but it applies a primary key.

The following information is displayed for the Veeam license:



* License name
* License notes
* Number of virtual machines (VMs) licensed
* Creation date
* Status - the status can be one of the following items.



* Modifying - The license is being created.
* Installed - The license is ready to use.
* Removing - The license is being deleted.









 Procedure to edit notes for Veeam licenses 



1. From the IBM Cloud for VMware Solutions console, click Licenses from the left navigation pane.
2. Scroll down to the Veeam licenses table.
3. Click the license that you want to edit the notes for.
4. On the license details page, edit the license notes, and then click Confirm.







 Known issues about license date display 

If you are using Mozilla® Firefox® as your browser, the license start and end dates might be displayed with no values on the Veeam console. To resolve the issue, view the license information in another browser, such as Google Chrome™.

If you are experiencing this problem and the only browser you can use is Firefox, contact [Veeam support](https://www.veeam.com/support.html) for assistance.





 Procedure to delete Veeam licenses 

Deleting a Veeam license does not delete the Veeam service that is installed on a vCenter Server instance. To delete the service, you must do so in the IBM Cloud for VMware Solutions console.
Understanding how much time is needed to migrate and whether it needs to be done in stages can help you simplify the migration journey. 
 Migrate After you have spent time assessing your existing infrastructure and planning for your migration, you can migrate your resources and components with ease and confidence. Depending on your migration needs, there are tools available to help you with the migration process. 
 Validate After you migrate your resources and components into your target infrastructure, and before you make your infrastructure live, you will want to validate and test your environment to ensure it is ready for production. This might also entail updating your DNS and global load balancers, routes, or retiring old services. 







 Migration solutions 

Review the following table to identify the migration solution that best fits your migration needs.

Classic to classic infrastructure

Classic to VPC infrastructure

On-premises to VPC infrastructure



Table 2. Classic to classic infrastructure migration
This table has row and column headers. The row headers identify the migration solution. The column headers identify what can be migrated by using the migration solution. To understand what can be migrated by using a particular solution in the table, navigate to the row, and find the checkmark for the migration motion that you are interested in.

 Solution Bare metal to bare metal Bare metal to virtual server Virtual server to virtual server Block/File* storage Network 

 [VPC+ Cloud Migration](https://cloud.ibm.com/docs/cloud-infrastructure?topic=cloud-infrastructure-about-migration-infravpc-cloud-migration) 
 [RMM](https://cloud.ibm.com/docs/cloud-infrastructure?topic=cloud-infrastructure-about-migration-infrarackware-migration) ![Checkmark icon](https://cloud.ibm.com/docs-content/v1/content/8aa0853d34cf2349f1d2db8e5c61e6422a580169/icons/checkmark-icon.svg) !
* Size for vSAN capacity disks - Select an option for the capacity disks that you need.
* Number of vSAN capacity disks - Specify the number of capacity disks that you want to add.
* If you want to add more capacity disks, select the High performance with Intel Optane checkbox. This option provides two extra capacity disk bays that are useful for workloads that require less latency and higher IOPS throughput.

The High performance with Intel Optane option is available only for Skylake and Cascade Lake CPU models.
* Review the Disk Type for vSAN Cache Disks and Number of vSAN cache disks values. These values depend on whether you selected the High performance with Intel Optane checkbox.
* vSAN license - Select the VMware vSAN 6.6 license edition (Advanced or Enterprise).







 Licensing settings 

IBM-provided licenses for the following VMware components:



* vSphere Enterprise Plus 6.7u3
* VMware NSX® Service Providers 6.4 (Advanced or Enterprise edition)







 Network interface settings 

Network interface card (NIC) settings are based on your selection of either Public and private network or Private network only. The following add-on services require public NICs and aren't available with the private option:



* F5® BIG-IP®
* FortiGate® Virtual Appliance







 Summary 

Based on your selected configuration for the cluster, the estimated price is instantly generated and displayed in the Summary pane. Click Pricing details to generate a PDF document with the price summary for the IBM Cloud for VMware Solutions resources.

You can also add the provisioned resources to the IBM Cloud estimate tool, by clicking Add to estimate. The tool is useful if you want to estimate the price of the selected IBM Cloud for VMware Solutions resources together with other IBM Cloud resources that you might consider purchasing.







 Procedure to add clusters to vCenter Server with Hybridity Bundle instances 



1. From the IBM Cloud for VMware Solutions console, click Resources > vCenter Server from the left navigation pane.
2. In the vCenter Server table, click the instance to view the clusters in it.

Ensure that the instance status is Available. Otherwise, you can't add clusters to the instance.
= "test-subnet"
HOSTNAME		= "test-vsi"
PROFILE		 = "bx2-4x16"
IMAGE			= "ibm-redhat-7-6-amd64-sap-applications-1"
SSH_KEYS		= [ "<SSH Key ID 1>" , "<SSH Key ID 2>" ]
SWAP			= "16"
VOL1			= "10"
6. Initialize the Terraform CLI.

terraform init
7. Create a Terraform execution plan. The Terraform execution plan summarizes all the actions that are done to create the VPC instance in your account.

terraform plan
8. Verify that the plan shows all of the resources that you want to create and that the names and values are correct. If the plan needs to be adjusted, edit the input.auto.tfvars file to correct resources and run terraform plan again.
9. Create the VPC for SAP instance and IAM access policy in IBM Cloud.

terraform apply

The VPC and components are created and you see output similar to the terraform plan output.



This automation is offered free of charge however, the provisioned infrastructure comes at cost.





 Next steps 

If you need to rename your resources after they are created, modify the input.auto.tfvars file to change the names and run terraform plan and terraform apply again. Do not use the IBM Cloud Dashboard and user interface to modify your VPC after it is created. The Terraform scripts create a complete solution and selectively modifying resources with the user interface might cause unexpected results.

If you need to remove your VPC, go to your project folder and run terraform destroy.
Deployment dependencies 

The SAP solution end-to-end deployment by using deployable architectures is logically separated into the following steps:



1.  Deploying VPC landing zone infrastructure. This landing zone acts as network security and management landscape for SAP solutions that are logically isolated to another infrastructure deployed as next. There might exist only one VPC landing zone per region in one IBM Cloud account.
2.  Deploying Power Virtual Server with VPC landing zone. This deployed infrastructure hosts SAP solutions that are deployed as next. Provisioned IBM PowerVS workspace is connected to VPC landing zone. There might exist only one IBM PowerVS workspace per IBM PowerVS zone (data center) in one IBM Cloud account. Multiple PowerVS workspaces might be connected to the same VPC landing zone if the private CIDR network ranges of each IBM PowerVS infrastructure do not overlap. Multiple PowerVS workspaces in that case are connected to the same VPC landing zone and to each other.
3.  Deploying Power Virtual Server for SAP HANA on top of Power Virtual Server with VPC landing zone. Multiple SAP solutions (systems) might be deployed within one IBM PowerVS workspace that uses this deployable architecture if the private CIDR network range of each SAP solution does not overlap.



Each of these steps relies on the previous one. For instance, if you deploy Power Virtual Server for SAP HANA, you enter IBM Schematics workspace ID of the Power Virtual Server with VPC landing zone. The prerequisite dependency is constrained by type. Means, for Power Virtual Server for SAP HANA deployable architecture not every PowerVS workspace is accepted, but only the one created by Power Virtual Server with VPC landing zone.

Certain steps are combined together and provided as one deployment step to simplify provisioning. For instances, the Power Virtual Server with VPC landing zone offers a full-stack variation that deploys both VPC landing zone and PowerVS workspace in one step. In addition, you might deploy the Power Virtual Server with VPC landing zone as an extension that will create an additional PowerVS workspace and connect it with an existing VPC landing zone.
IBM Blockchain Platform is IBM's commercial distribution of Hyperledger Fabric. A key benefit of the platform is that IBM tests the open source code for security vulnerabilities daily and provides 24x7x365 support with SLAs appropriate for production environments. The platform is the commercial distribution of Hyperledger Fabric and includes integrated tools that provide end to end features for developers and network operators to develop, test, operate, monitor, and govern Fabric components by using an intuitive console UI. Quickly deploy an instance and use the streamlined console UI to [build a network](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-build-network), easily [deploy smart contracts](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-smart-contracts), [govern your components](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-govern-components), and [govern your channel](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-govern). Interested in APIs? See the [IBM Blockchain Platform API reference](https://cloud.ibm.com/apidocs/blockchain). With the IBM Blockchain Platform, it is easy to extend a basic network, work with multicloud solutions, and receive IBM worldwide support when needed. Finally, the IBM Blockchain Platform provides additional security benefits that are essential for running an enterprise-grade production network.
* What version of Hyperledger Fabric is being used with IBM Blockchain Platform?

IBM Blockchain Platform for IBM Cloud uses Hyperledger Fabric v2.2.10.
* Can IBM Blockchain Platform components interoperate with Hyperledger Fabric components on the same network? And vice versa? And what is the support policy for networks that include both IBM Blockchain Platform components and open source components?

Yes. Hyperledger Fabric networks consist of many distributed members owning one or more nodes. There are multiple deployment options:
* NSX-T multisite centralized - Management plane components centralized in one data center.
* NSX-T multisite distributed - Management plane components distributed across multiple data centers.



The automated offerings with manual tasks patterns are not validated by IBM Cloud. After the initial deployment, the Day 2 automation can be used to deploy vSphere clusters in different data centers by following the IBM Cloud documentation. A number of manual tasks can be initiated to create the required configuration. These VMware related tasks, such as redeploying NSX Managers are documented by VMware in their user guides, but are not specific to IBM Cloud. Therefore, additional considerations might apply when following these guides.

The following diagram can be used to compare and contrast the features that are offered by these offerings.

Zoom

![Automated offerings with manual customization tasks](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/vmwaresolutions/images/v2t-diagrams-platforms-manual.svg)

Figure 3 Automated offerings with manual customization tasks

In the previous diagram, the following terms require some additional comments:



* Single SSO and root domain - A single instance of Active Directory and Domain Name Services is deployed automatically. Additional Microsoft® domain controllers must be deployed manually at the other site and replication must be configured to enable this pattern.
* Single vCenter - vCenter is deployed automatically. A manual deployment of a backup server must be done to enable backups of this server to be made available at the other site to enable recovery. During failure of vCenter, some management functions are not available. However, workload VMs are still accessible.
* vCenter HA - vCenter High Availability (HA) protects vCenter against failures by using an active-passive architecture that uses a three-node cluster with active, passive, and witness nodes.
Operations management architecture overview 

The architecture of the products in the operations management layer provides centralized monitoring with logging data from IBM Cloud® for VMware Solutions. The operations management layer monitors in real time, the physical infrastructure, virtual infrastructure, and optionally the client’s compute workloads.

At a high level, the following information is collected:



* Topology data, such as physical and virtual compute, networking, and storage objects.
* Monitoring data, such as:



* Metrics - structured data such as performance and capacity
* Logs - unstructured data such as system events







 Operation management flows 

The following diagram shows the key interaction and integration of the operations management tools.

Zoom

![Management flows diagram](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/vmwaresolutions/images/opsmgmt-mgmtflows.svg)

Figure 1. Operational tools management flow

The IBM Cloud for VMware Solutions operations management consists of the following steps:



* Monitoring - VMware Aria® Operations™ Manager tracks and analyzes the operation of multiple objects in the IBM Cloud for VMware Solutions architecture by using analytic algorithms. These algorithms help VMware Aria Operations learn and predict the behavior of these objects. System administrators access this information by using views, reports, and dashboards.

When an issue occurs in the environment VMware Aria Operations generates alerts of three impact types:



* Health alerts - indicate issues that affect the health of the environment and require immediate attention.
* Risk alerts - indicate issues that are not immediate threats but need to be addressed soon.
* Efficiency alerts - information to improve performance or reclaim resources.



VMware Aria Operations Alerts are events that occur on the monitored objects when data analysis indicates deviations from normal metric values, or when an issue occurs with one of the monitored components. VMware Aria Operations alerts are assigned one of these categories:



* Critical - must be acted upon immediately.
* Immediate - must be acted on as soon as possible.
* Warning - must be checked when time allows.
For more information, see [VMware Update Manager introduction](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vum-introvum-intro).
* Open a support ticket with the IBM Cloud for VMware Solutions team to notify them that an upgrade is being planned. The ticket remains open until the instance is registered at the upgraded level in the IBM Cloud for VMware Solutions console.
* Confirm whether the vCenter Server instance that you are upgrading is linked to another vCenter Server instance as primary or secondary in the IBM Cloud for VMware Solutions console. All linked instances must have their Platform Services Controllers (PSCs) upgraded first as part of a particular site upgrade.
* Confirm the following requirements for vSAN based instances:



* Ensure that the vSAN Health tool is enabled and reports no critical errors. If critical errors are present, contact the IBM Support team with the upgrade support ticket ID.
* Ensure that each node has space to handle rebuilding redundancy of vSAN objects in case an ESXi host fails to come back up during the upgrade. You might need to either reduce disk usage or add an ESXi host before the upgrade.
* Verify whether the overall vSAN volume usage is higher than 70%. You might need to either reduce disk usage or add an ESXi host before the upgrade.



* Verify that the PSC and vCenter Server root user ID with its credentials are visible on the console. If your vCenter Server instance was initially ordered in V2.5 or later, only the account with customerroot access is visible on the console. In this case, contact IBM Support for the root user ID password for PSC and vCenter Server.
* Confirm that you have a [My VMware](https://my.vmware.com) user ID for which to download the required binary files to upgrade. If you don't, contact IBM Support with the upgrade support ticket ID.
* Confirm that VUM is configured to reach [https://www.vmware.com](https://www.vmware.com) to download patches.
IBM Blockchain Platform is IBM's commercial distribution of Hyperledger Fabric. A key benefit of the platform is that IBM tests the open source code for security vulnerabilities daily and provides 24x7x365 support with SLAs appropriate for production environments. The platform is the commercial distribution of Hyperledger Fabric and includes integrated tools that provide end to end features for developers and network operators to develop, test, operate, monitor, and govern Fabric components by using an intuitive console UI. Quickly deploy an instance and use the streamlined console UI to [build a network](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-build-network), easily [deploy smart contracts](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-smart-contracts), [govern your components](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-govern-components), and [govern your channel](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-govern). Interested in APIs? See the [IBM Blockchain Platform API reference](https://cloud.ibm.com/apidocs/blockchain). With the IBM Blockchain Platform, it is easy to extend a basic network, work with multicloud solutions, and receive IBM worldwide support when needed. Finally, the IBM Blockchain Platform provides additional security benefits that are essential for running an enterprise-grade production network.
* What version of Hyperledger Fabric is being used with IBM Blockchain Platform?

IBM Blockchain Platform for IBM Cloud uses Hyperledger Fabric v1.4.12 and v2.2.5.
* Can IBM Blockchain Platform components interoperate with Hyperledger Fabric components on the same network? And vice versa? And what is the support policy for networks that include both IBM Blockchain Platform components and open source components?

Yes. Hyperledger Fabric networks consist of many distributed members owning one or more nodes. There are multiple deployment options:
Release notes for Domain Name Registration 

Use these release notes to learn about the latest updates to Domain Name Registration that are grouped by date.



  1 November 2021 

Domain freeze
:   In the period between 2 November 2021 - 10 November 2021, for the purpose of migration, your domains will be in a frozen state.





  23 September 2021 

Add abuse policy
:   Added information about reporting violations of the Acceptable Use Policy.





  27 July 2021 

ResellOne end of service
:   Effective 1 November 2021, IBM Cloud no longer supports the ResellOne Domain Resale service, which was offered in partnership with Tucows Inc.





  24 March 2020 

Rename collection
:   Documentation collection name changed from "Domain Name Service" to "Domain Name Registration".
Deleting virtual data centers 

You can delete a virtual data center when it's in the Ready To Use state.

Before you delete your virtual data center, ensure that any items that you created within the are removed. Items might include the following artifacts.



* vApps, vApp templates, and virtual machines (VMs). You must remove these items even if they are stopped.
* Organization networks that are removed or unshared from the virtual data center.
* Organization catalogs.
* DHCP pools created within the Organization virtual data center edge gateway.
* Custom routes that are defined on the Organization virtual data center edge gateway distributed router.
* Load balancer custom configurations defined on the Organization virtual data center edge gateway.
* VPN custom configurations defined on the Organization virtual data center edge gateway.





 Considerations when you delete virtual data centers 

All of the virtual data center VM restore points in Veeam are automatically deleted when you delete a VMware Shared virtual data center.

Any job that includes instructions to back up the VM fails when the VM restore points in Veeam are deleted. However, the existing VMs in the job are still backed up, the job status is marked as failed. To remove the failed status, you must manually edit the job to remove the instruction to back up the now deleted VMs.





 Procedure to delete virtual data centers from the Resources page 



1. From the IBM Cloud for VMware Solutions console, click Resources > VMware Shared from the left navigation pane.
2. In the VMware Shared table, expand the site name and find the virtual data center to delete.
3. Click the vertical overflow menu next to the Status column, and then click Delete instance. The status of the virtual data center is changed to Deleting. When the virtual data center is deleted successfully, the components of the virtual data center are released, and the status is changed to Deleted.







 Procedure to delete virtual data centers from the virtual data center details page 



1. From the IBM Cloud for VMware Solutions console, click Resources > VMware Shared from the left navigation pane.
2.