vania-janet/multiturn-rag-retrieval-data huggingface dataset:
For more information about these features, see [Choose enrichments](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-domain).

For more information about migrating your solutions, see [Migrating Knowledge Studio solutions](https://cloud.ibm.com/docs/discovery-data?topic=discovery-data-migrate-wks).





 4.7.0 release, 28 June 2023 

IBM Watson® Discovery Cartridge for IBM Cloud Pak® for Data 4.7.0 is available.

For a list of new features and bug fixes, see [What's new and changed in Watson Discovery](https://www.ibm.com/docs/SSQNUZ_4.7.x/fixlist/discovery-fixlist.html)

Features that are not available in this release
: The following features are generally available from managed IBM Cloud deployments at the time of this release, but not from installed deployments:



* Answer finding
* Optical Character Recognition v2







 4.6.6 release, 18 May 2023 

IBM Watson® Discovery Cartridge for IBM Cloud Pak® for Data was not refreshed as part of 4.6.6. You can use Discovery 4.6.5 with IBM Cloud Pak for Data 4.6.6.





 4.6.5 release, 2 May 2023 

IBM Watson® Discovery Cartridge for IBM Cloud Pak® for Data 4.6.5 is available.

For a list of new features and bug fixes, see [What's new and changed in Watson Discovery](https://www.ibm.com/docs/SSQNUZ_4.6.x/fixlist/discovery-fixlist.html)

Manage the data in a collection from the new Manage data page
: You can now access a Manage data page for a collection. From the new page, you can see a list of the documents in your collection and get a quick view of information about the documents. You can also delete documents from a collection with just a few clicks.
[IBM Cloud for VMware Solutions forest with parent-child trust diagram](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/vmwaresolutions/images/adds-forestwithparentchildtrust.svg)

Figure 1. IBM Cloud for VMware Solutions forest with parent-child trust diagram





 IBM Cloud for VMware Solutions forest with tree-root trust 

This model creates a single forest by using the existing IBM Cloud for VMware Solutions infrastructure domain as the parent and configuring a new IBM Cloud for VMware Solutions workload parent domain. The tree-root trust is a two-way transitive trust between the two parent domains. The vSphere SSO connected to the IBM Cloud for VMware Solutions infrastructure domain can access the users from the other parent domain.

If the other parent domain has a child domain, due to the two-way trust, those users are also accessible. The following diagram shows the Active Directory Domain Services topology for this IBM Cloud for VMware Solutions forest with tree-root trust model.

Zoom

![IBM Cloud for VMware Solutions forest with tree-root trust diagram](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/vmwaresolutions/images/adds-forestwithtreeroottrust.svg)

Figure 2. IBM Cloud for VMware Solutions forest with tree-root trust diagram





 Two-way forest trust 

VMware always recommends two-way trusts for forest trusts. For more information, see [Microsoft Active Directory Trusts supported by VMware vCenter Single Sign-On](https://kb.vmware.com/s/article/2064250).
You can also add the provisioned resources to the IBM Cloud estimate tool, by clicking Add to estimate. This option 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 to purchase.





 Results after you add ESXi servers 



1. You might experience a slight delay on the console while the instance status changes from Available to Modifying. Allow the operation to complete before you make more changes to the instance.
2. You're notified by email that your request to add ESXi servers is being processed. On the console, the status of the cluster that is associated with the ESXi servers is changed to Modifying.
3. If you don't see the new ESXi servers added to the list in the cluster, check your email or console notifications for more details.



If you are adding ESXi servers during maintenance mode, virtual machines (VMs) are not migrated to the new servers until you remove the cluster from maintenance mode.







 Deleting ESXi servers from vCenter Server with Hybridity Bundle instances 



 Before you delete ESXi servers 



* Whenever possible, remove ESXi servers by using the IBM Cloud® for VMware Solutions console because changes that you make on the VMware vSphere® Web Client are not synchronized with the IBM Cloud for VMware Solutions console. Therefore, remove ESXi servers from vCenter Server only for on-premises ESXi servers or ESXi servers that you don't manage in the IBM Cloud for VMware Solutions console.
* vSAN storage requires at least 4 ESXi servers.
* Before you delete ESXi servers on which F5® or FortiGate® Virtual Appliance is installed, you must migrate the F5 BIG-IP® and FortiGate VMs to a different ESXi server than the one that is hosting the VMs.
* When you delete ESXi servers, the servers are placed in maintenance mode. After that, all the virtual machines (VMs) running on the servers are migrated before they are deleted from vCenter Server. For maximum of control over the relocation of VMs, it is recommended that you place the ESXi serversin maintenance mode.
After the workloads are migrated, you can remove the ESXi hosts from vCenter and decommission the old servers from the IBM Cloud portal.







 I have VMware Solutions - vCenter Server with NSX-V, IBM Cloud Bare Metal Servers with vSphere 6.5 or 6.7, and the support is ending. What do I need to do to keep the environment supported, and what options do I have? 

General support for vSphere 6.x ended on 15 October 2022. For more information, see [End of general support for vSphere 6.5 and vSAN 6.5 or 6.6](https://kb.vmware.com/s/article/83223) and [VMware product lifecycle matrix](https://lifecycle.vmware.com//).

In addition, the vCenter Server instances with vSphere 6.5 or 6.7 typically run NSX-V 6.4. NSX-V 6.4 was End of General Support on 16 January 2022 and End of Technical Guidance on 16 January 2023. See more on VMware Official Product Lifecycle Matrix. An exclusive support agreement between VMware and IBM to support NSX-V until 31 December 2023 exists.

IBM Cloud recommends an upgrade to vSphere 7.x and NSX-T™ 3.x.

To migrate from NSX-V to NSX-T (also called a V2T migration), IBM Cloud uses a migration approach that is called lift-and-shift. In the lift-and-shift approach, the IBM Cloud automation is used to deploy a new vCenter Server instance. You need to migrate network configurations from NSX-V to NSX-T and migrate workloads between instances. IBM Cloud provides extensive documentation for a validated approach and guidance for existing IBM Cloud for VMware Solutions customers with vCenter Server instances.





 How do I know whether my IBM Cloud bare metal server hardware is suitable for in-place vSphere 7.x upgrade? 

You can check whether your server and its hardware options are compatible with vSphere 7.x.
One bare metal server with the configuration presented in [Technical specifications for vCenter Server with Hybridity Bundle instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_hybrid_overviewvc_hybrid_overview-specs).





 Licenses and fees for expansion nodes 



* One VMware vSphere Enterprise Plus 6.73
* One VMware NSX Service Providers Edition (Advanced or Enterprise) 6.4
* One Support and Services fee
* VMware vSAN (Advanced or Enterprise) 6.6



You must manage the IBM Cloud for VMware Solutions components that are created in your IBM Cloud account only from the IBM Cloud for VMware Solutions console, not the IBM Cloud infrastructure customer portal, or any other means outside of the console. If you change these components outside of the IBM Cloud for VMware Solutions console, the changes are not synchronized with the console.

CAUTION Managing any IBM Cloud for VMware Solutions components (which were installed into your IBM Cloud account when you ordered the instance) from outside the VMware Solutions console can make your environment unstable. The following activities are considered management activities:



* Adding, modifying, returning, or removing components
* Expanding or contracting instance capacity through adding or removing ESXi servers
* Powering off components
* Restarting services

Exceptions to these activities include managing the shared storage file shares from the IBM Cloud infrastructure customer portal. Such activities include: ordering, deleting (which might impact data stores if mounted), authorizing, and mounting shared storage file shares.









 Related links 



* [vCenter Server BOM](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_bom)
* [HCX overview](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-hcx_considerationshcx_considerations)
* [Contacting IBM Support](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-trbl_support)
Why aren't Zerto VRAs displaying for newly created ESXi servers? 

  What’s happening 

Virtual Replication Appliances (VRAs) are not displayed on the Zerto Virtual Replication console after you add VMware ESXi™ servers to a VMware vCenter Server® instance with Zerto disaster recovery installed.

  Why it’s happening 

The Zerto disaster recovery service is installed only on the ESXi server from the default cluster (cluster1 for instances that are deployed in V3.1 or earlier). If new clusters are created in the same vCenter Server environment or if ESXi servers are added to new clusters, Zerto disaster recovery is not installed on them. On those clusters, you must install Zerto disaster recovery separately.

  How to fix it 

Open an IBM Cloud® Support ticket and work with IBM Support to obtain available IP addresses for you to install the VRAs from the Zerto console, instead of the IBM Cloud for VMware Solutions console.

To access the Zerto console, click the Zerto card from the Services tab of the instance and click View details. Then, click View Zerto console.

For more information about contacting IBM Support, see [Contacting IBM Support](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-trbl_supporttrbl_support).
Landscapes have several possible configurations, such as server (CPU, RAM) size and storage size, for all SAP solutions in the market. These solutions include SAP NetWeaver-based products. SAP NetWeaver-based products range from older solutions, such as SAP ECC and SAP BW (that use "AnyDB" vendors that are approved by SAP), to the new range of SAP solutions, such as SAP S/4HANA and SAP BW/4HANA (that use SAP HANA database). Beyond the enterprise resource planning (ERP) and enterprise data warehouse (EDW) examples, there are many available SAP products or add-ons for different industries and business types or operating geographies.

SAP NetWeaver-based products are designed to run on SAP NetWeaver-certified hosts, and SAP HANA-based products are designed to run on SAP HANA-certified hosts. The certified operating systems and supported database systems for IBM Cloud are listed in [SAP Note 2927211](https://launchpad.support.sap.com//notes/2927211).

More solutions are available from SAP that are not SAP NetWeaver-based and many third-party software options that might integrate with SAP can affect the planning of your system landscape. For example, SAP HANA can run as a database for an SAP NetWeaver stack-based solution or as a standalone entity depending on your usage scenario.

Contact [SAP Support](https://support.sap.com/en/index.html) if you plan to deploy and integrate non-SAP NetWeaver-based or third-party software into your SAP landscape on IBM Cloud.

You want to be as detailed as possible when you determine the size of your server based on the applications that you plan to run, potential growth, and performance. Additionally, keep in mind your storage and memory requirements for your applications. SAP systems in a landscape have specific requirements for connectivity, either among each other or to external systems.

Questions during your determination of the SAP landscape:



* How do you intend to use the applications? Is the intended use for development and testing, or production?
* How do you intend to connect your SAP workloads in Cloud to your existing network and systems?
* How will the database be used?
Dizzion on IBM Cloud overview 

Organizations with high-performing, remote, and hybrid workforces choose Dizzion digital workspaces, Desktop as a Service (DaaS), and virtual applications to protect sensitive data and create a seamless, work-from-anywhere platform. Dizzion on IBM Cloud outperforms legacy virtual desktop infrastructure (VDI) and commodity Desktop as a Service (DaaS) for a superior user experience. At the same time, it provides more service-level choices, multicloud integration, compliance, protection, and simplified management for the teams that are in charge with environment optimization. Dizzion on IBM Cloud is a non-IBM product that is offered under terms and conditions from Dizzion, not IBM.



  Technical specifications for Dizzion 

You can expect the following benefits when you request Dizzion for IBM Cloud®:



*  More choices and control. Over 40 global IBM Cloud locations, hybrid cloud integration, and DIY-to-turnkey support levels.
*  Simplified digital workspaces. Dizzion’s proprietary C3 platform makes a complex IT service easier and automated.
*  Empowered digital transformation. IT asset unification with integrated multicloud and in-house environments.
*  Unrivaled experience. Avoid slow-downs and dropped calls with the market’s top-performing digital workspace.
*  Maximum productivity. Optimize work environments for productivity with 99.99% availability, backup, and Disaster Recovery.
*  Digital workspaces for any user. Exceed expectations of your most intense workspace users with performance add-ons.
*  Always protected and compliant. Stay compliant (HIPAA, PCI, GDPR) with change, remote work, and personal devices.
*  Transparent workforce. Remove employee and contractor risks with real-time insights into workforce activity.
*  Secure and control-sensitive data. Solve difficult information governance and sovereignty challenges.







  Procedure to request Dizzion 



1.  In the IBM Cloud for VMware Solutions console, scroll down to the services section and click Dizzion in the Featured workload solutions category.
2.  On the Dizzion page, in the Dizzion box, click the arrow icon to access the Dizzion DaaS service in the IBM Cloud catalog.







  Related links 



*  [Dizzion product documentation](https://help.dizzion.com/en_US/product-documentation)
HCX is not supported on vSphere 6.7 for vCenter Server with NSX-T 3.1 instances.
* The 12-month commitment for HCX is removed.
* The private interconnect option is removed. The network connection options are either public or private.
* You can choose the target cluster for service mesh (NSX-T only).
* The HCX service is removed if the service mesh target cluster is removed on NSX-T.
* If the management cluster or HCX service mesh target cluster is private only, the only connection type would be private connection. If the connection type is private, a proxy is required.



VMware vRealize Operations - vSAN storage requirements
: If you install VMware vRealize Operations and select vSAN storage, you must have an estimated 750 GB of vSAN storage to successfully install vRealize Operations. This storage requirement does not apply to NFS.

REST APIs
: REST API support for the VMware HCX service is now available.

New and updated documentation
: The following documentation updates are available.



* (Updated on 24 February 2021) The Veeam on bare metal reference architecture document is now available in the Reference section of the user documentation.
* A new topic, Managing security and compliance, is now available. The topic provides information about monitoring security and compliance posture with VMware Solutions by using Caveonix RiskForesight.



User interface updates and enhancements
: The user interface is updated and provides the following enhancements.

The following enhancements are made to the landing page of IBM Cloud for VMware Solutions console to better assist you in learning and selecting the appropriate offering and services according to your needs:



* The previous Start provisioning section is renamed to IaaS platforms.
* A new VMware Regulated Workloads section is added.
* The previous Services section is renamed to Add-on services.









 2020 



 26 October 2020 

VMware Solutions Shared - support for Dallas 12 and Dallas 13 IBM Cloud data centers
: Starting with release 3.9, Dallas 12 and Dallas 13 IBM Cloud data centers are now available for deployment on VMware Solutions Shared instances.

VMware Solutions Shared - Integration with IBM Cloud Monitoring
If you're planning to use user accounts from your on-premises AD forest to resources that are running as VMs hosted on your vCenter Server instance in the VMware Solutions workload forest-domain, you must establish at least a one-way trust to your AD forest-domain running in IBM Cloud. In this deployment model, your IBM Cloud for VMware Solutions workload forest-domain becomes the resource domain where resource objects are located, and on-premises domain becomes the user account domain. You must have AD connectivity between on-premises and IBM Cloud. Typically, a two-way trust is not commonly deployed in this model as an alternative deployment pattern is used to extend Active Directory. The IBM Cloud for VMware Solutions infrastructure domain is used for the user credentials and service accounts of your system administrators and the resource objects for the underlay-connected infrastructure components only. The following diagram shows the Active Directory Domain Services topology for this new forest with trusts model.

Zoom

![New AD forest with trusts to existing forest diagram](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/vmwaresolutions/images/adds-newforest.svg)

Figure 2. New AD forest with trusts to existing forest diagram





 Extend forest and create a new domain model 

In this deployment model, you extend your existing AD forest from on-premises to IBM Cloud and create a new child domain. More domain controllers are now running as VMs hosted on your vCenter Server instance. This deployment is simple, flexible, and provides the following advantages:



* You are not required to set up more trusts.
* Domain controllers in IBM Cloud are handling both accounts and resources.
* More resilient to network connectivity issues.



In this model, the customer provisions a minimum of two domain controllers as VMs hosted in each vCenter Server instance. These VMs would be connected to an overlay network and the new domain controllers would have the primary domain controller role for the child domain. All user credentials, service accounts, and resource objects are on in this IBM Cloud for VMware Solutions workload child domain that is hosted on these domain controllers.
: Dizzion is now available as a featured service from the VMware Solutions console.

Name change for HyTrust add-on services
: The company Entrust acquired the HyTrust company. The names of the following services are updated.



* Entrust CloudControl™
* Entrust DataControl
* Entrust KeyControl™, which is deprecated



Veeam VSI, Veeam bare metal, and Zerto configuration changes
: Beginning with the 4.7 release, the Veeam VSI, Veeam bare metal, and Zerto services are not configured with an IBM Cloud Infrastructure portable IP address or with a NAT connection to the public network, even if you have public interfaces in your instance. This update helps to avoid the possibility of asymmetric routing when using a network gateway appliance.

New architecture documentation
: The following technical documents are now available or updated:



* VMware Solutions architecture patterns
* VMware NSX-V to NSX-T migration



User interface updates and enhancements
: The VMware Solutions documentation now has a [landing page](https://cloud.ibm.com/docs/vmwaresolutions) where you can get oriented with the content available for the offering.





 21 February 2022 

VMware Cloud Director upgrade for VMware Solutions Shared
: (Updated on 15 March 2022) VMware Solutions provides an upgrade to the VMware Shared infrastructure to VMware Cloud Director (vCD) v10.3.2.

VMware vCenter Server instances
: The 4.6 release applies the following upgrades and improvements for newly deployed instances, clusters, and hosts.



* VMware vCenter Server Appliance 7.0 Update 3c (build 19234570)
* VMware NSX-T 3.1.3.5.0 (build 19068434)
* VMware NSX-V 6.4.12 (build 19066632)
* VMware vSAN 7.0 Update 2c (build 18426014)



VMware vSAN 7.68 TB SSD disk support for 10 Gb uplink speed
Using NSX with your virtual machines 

During vCenter Server instance deployment, VMware NSX® is ordered, installed, licensed, and configured in your instance. Also, NSX Manager, VMware NSX Controllers™, and NSX Transport Zone are set up, and each VMware ESXi™ server is configured with the NSX components.

An VMware NSX Edge™ Services Gateway is also deployed to be used by your workload VM or VMs. For more information, see [Configuring your network to use the customer-managed NSX ESG with your VMs](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_esg_config).





 Considerations when you change passwords for NSX components 

Review the following considerations before you attempt to change the passwords for the NSX Manager, NSX Controllers, and NSX Edges.



 Considerations when you change passwords for NSX-T components 



* Do not change the NSX Manager admin password for NSX-T.
* You can change the NSX Manager root password. This password is not displayed in the VMware Solutions console. However, the password is the same as the one for the root user for NSX Controllers, which is displayed in the console.
* You can change the passwords for the root user for NSX Controllers. The root credentials are displayed in the VMware Solutions console.
* You can change the passwords for the admin user and the root user for the customer-managed VMware NSX Edge Services Gateway (ESG). The admin credentials are displayed in the VMware Solutions console, but the root credentials are not displayed. The passwords for the root user and the admin user are the same.
* You can change the passwords for admin user and root user for management services NSX ESG. The admin credentials are displayed in the VMware Solutions console, but the root credentials are not displayed. The passwords for the root user and the admin user are the same.







 Considerations when you change passwords for NSX-V components 



* You can change the NSX Manager password.