vania-janet/multiturn-rag-retrieval-data huggingface dataset:
* Zerto v9.7u3



Name change for VMware vRealize products
: VMware changed the vRealize® Suite Lifecycle Manager product name to VMware Aria® Suite Lifecycle. All vRealize products that are managed by vRealize Suite Lifecycle Manager are now referred as VMware Aria. The names are updated throughout the IBM Cloud for VMware Solutions documentation. The following products are rebranded:



* vRealize Operations and Log Insight is renamed to VMware Aria Operations and VMware Aria Operations for Logs.
* vRealize Automation is renamed to VMware Aria® Automation™.
* vRealize Operations (vROps) is renamed to VMware Aria Operations.
* vRealize Log Insight™ (vRLI) is renamed to VMware Aria Operations for Logs.
* vRealize Network Insight (vRNI) is renamed to VMware Aria Operations™ for Networks.



REST API
: The following updates are available:



* The [VMware Solutions API](https://cloud.ibm.com/apidocs/vmware-solutions) provides support for viewing and deleting VMware vSphere instances. You can also add or delete ESXi servers, and add or delete licenses for vSphere instances.
* Also for the VMware Solutions API, you can specify either quantity or host_names for the number of new hosts to be added in the hosts_order_data object.



User interface updates and enhancements
: The user interface is updated with various messages and tooltips, and provides the following enhancements:



* The Instance configuration name field is changed to a side panel. You can manage your configuration templates from a list of saved configurations in the side panel.
* The checkbox Select a different cluster location is changed to a switch, for consistency with other similar UI options.
* The SAP-certified Cascade Lake selections (NetWeaver and HANA) are merged into a single option for a more streamlined user experience when you choose the CPU model for your servers.
This default storage policy is automatic for new VMware Solutions Shared instances.

The 3.8 release introduces Standard storage policies and Encrypted storage policies. These new storage policies are available for new VMware Solutions Shared instances and added to existing VMware Solutions Shared instances with the VMware Cloud Director (vCD) v10.1.1 upgrade.



* A standard storage policy is now available for both decrypted and encrypted policies. The standard storage policy has no maximum throughput, but the number of IOPS/GB is not guaranteed.
* VMware Cloud Director v10.1.1 provides the capability to create encryption-enabled storage policies to all organization virtual data centers. Administrators can encrypt virtual machines (VMs) and disks by associating the VM or disk with a storage policy that has the VM encryption capability.



VMware Solutions Shared - off-site copy mode availability for Veeam Availability Suite
: Veeam Availability Suite off-site copy mode is now automatically enabled for new and existing VMware Solutions Shared instances.

VMware Solutions Dedicated - VMware vSphere 6.7u3 support
: You can order VMware vSphere 6.7u3 with your VMware vCenter Server instances and VMware vSphere clusters. vSphere Enterprise Plus 6.7u3 replaces the option to order vSphere Enterprise Plus 6.7u2 with new instances. Additionally, Single-node Trial for Migration and App Modernization and Single-node Trial for Data Protection and Disaster Recovery instances are now ordered with vSphere Enterprise Plus 6.7u3.

vSphere Enterprise Plus 6.7u3 is available for Skylake, Cascade Lake, and Cascade Lake SAP IBM Cloud bare metal servers.

If you have an existing instance with vSphere Enterprise Plus 6.7u2, you can add new ESXi servers with either vSphere Enterprise Plus 6.7u2 or vSphere Enterprise Plus 6.7u3.

VMware Solutions Dedicated - vSphere ESXi 6.7u2 for vSAN storage
: For vSAN storage, even though vSphere 6.7u3 is selected on the user interface, vSphere ESXi 6.7u2 is installed.
Managing Entrust KeyControl 

New installations of Entrust KeyControl™ are no longer supported for new or existing deployments of vCenter Server instances. You can still use or delete existing Entrust KeyControl installations on your existing instances.

To manage the Entrust KeyControl™ service, access the Entrust KeyControl web GUI from the IBM Cloud® for VMware Solutions console, or access the Entrust KeyControl console from the vSphere® Web Client.



 Accessing the Entrust KeyControl web GUI from the VMware Solutions console 

To log in to the web GUI of the primary or secondary Entrust KeyControl appliance, use the WebGUI credentials that are found on the Entrust KeyControl service details page.





 Accessing the Entrust KeyControl console from the vSphere Web Client 

To access the Entrust KeyControl console from the vSphere Web Client, use the following procedure:



1. In the vSphere Web Client, find the virtual machines (VMs) that start with the names KC1 and KC2 that have the matching IP address that is found on the Entrust KeyControl service details page.
2. Right-click KC1 or KC2, and then click Open Console.
3. Log in to the console by using the console credentials that you can find on the Entrust KeyControl service details page.



For more information, see [Ordering services for vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_addingservices).





 Enabling internet access for the Entrust KeyControl VMs 

For Entrust KeyControl 4.3.2 and later, IBM Cloud for VMware Solutions provides automatic renewal support for Entrust licenses with the Call Home feature enabled. For VMware vCenter Server® instances that are not private-only, Entrust KeyControl is deployed with firewall and SNAT (Source Network Address Translation) rules that are defined on the management services ESG mgmt-nsx-edge.

These rules enable internet access for the Entrust VMs.
When a third node is added to a two-node cluster, vCenter Server automatically rebalances the three NSX Controllers across the three nodes and creates a highly available environment.





 Can I set up VMware vCenter HA configuration? 

You can configure vCenter HA, but configuration support is not provided by IBM Cloud for VMware Solutions.





 Can clusters be renamed? 

For a new vCenter Server instance, you can set the name of the initial cluster that is created during deployment. When you add a cluster to a vCenter Server instance, you can specify the name that you want on the IBM Cloud for VMware Solutions console.





 How are patches managed? 

IBM provides ongoing updates to the IBM code by deploying the IBM CloudDriver virtual server instance (VSI) on demand. Updates and patches for the IBM management components are applied automatically, as needed.

When you review the summary details for each instance, the Properties section displays the Current version. The current version is the IBM code version that is set when the instance is initially ordered. Day 2 operations such as adding or removing hosts, storage, services, or clusters are automatically updated with the current IBM code. Customer upgrade to the current IBM code version is never required. The IBM code version is separate from the VMware and service software versions. When the IBM code version is updated, the VMware software and service versions that are already installed for the instance remain unchanged.

IBM does not provide ongoing updates to add-on services such as Zerto or Veeam®. Obtaining and installing these updates is your responsibility.

Newly deployed VMware ESXi™ servers and clusters are patched with recent, but not necessarily the most recent, VMware ESXi updates.

For all other VMware component updates, you must ensure that newly deployed ESXi servers and clusters have the most recent updates that you require. IBM Cloud for VMware Solutions does not offer support for applying updates and patches for VMware components. You must monitor and apply these updates yourself.

To download ESXi updates from VMware, you can configure VMware Update Manager (VUM), which is integrated into your vCenter Server.
Block deployments from vulnerable images or untrusted users Create an admission controller with custom policies so that you can verify container images before you deploy them. With the [open source Portieris project](https://github.com/IBM/portieris), you control where the images are deployed from and ensure that they meet content trust requirements. If a deployment does not meet the policies that you set, the admission controller blocks the deployment in your cluster. 



What options do I have to scan running containers for vulnerabilities?
: You can install third-party solutions in your cluster, such as [Twistlock](https://www.paloaltonetworks.com/prisma/cloud) or [StackRox](https://www.redhat.com/en/technologies/cloud-computing/openshift/advanced-cluster-security-kubernetes) to scan running containers and block malicious activities when they are detected.





 Container isolation and security 

When you run multiple apps in your cluster, you want to make sure that your workloads run isolated from each other and that you restrict the permissions of your pods within the cluster to avoid noisy neighbors or denial-of-service attacks.

What is a Kubernetes namespace and why should I use it?
: Kubernetes namespaces are a way to virtually partition a cluster and provide isolation for your deployments and the groups of users that want to move their workload onto the cluster. With namespaces, you can organize resources across worker nodes and also across zones in multizone clusters.
: Every cluster is set up with a set of default Kubernetes namespaces that include the deployments and services that are required for IBM Cloud Kubernetes Service to run properly and manage the cluster. For more information, see the [service architecture](https://cloud.ibm.com/docs/containers?topic=containers-service-arch).
: Cluster administrators automatically have access to these namespaces and can set up additional namespaces in the cluster.
Managing Entrust CloudControl 

To manage the Entrust CloudControl™ service, access the Entrust CloudControl WebGUI from the IBM Cloud® for VMware Solutions console, or access the Entrust CloudControl console from the VMware vSphere® Web Client.



 Accessing the Entrust CloudControl WebGUI from the VMware Solutions console 

To log in to the WebGUI of the primary or secondary Entrust CloudControl appliance, use the WebGUI credentials that are found on the Entrust CloudControl service details page.





 Accessing the Entrust CloudControl console from the vSphere Web Client 

To access the Entrust CloudControl console from the vSphere Web Client, use the following procedure:



1. In the vSphere Web Client, find the virtual machines (VMs) that are named CC1 and CC2.
2. Right-click CC1 or CC2, and then click Open Console.
3. Log in to the console by using the console credentials that you can find on the Entrust CloudControl service details page.



For more information, see [Ordering services for vCenter Server instances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_addingservices).





 Considerations when you add and remove hosts and clusters 

When you add and remove hosts and clusters to your instance, VMware Solutions do not manage your Entrust CloudControl inventory and credentials for you. IBM Cloud assumes that you take steps to lock IBM Cloud automation from having access to your Entrust CloudControl deployment.





 Procedure to find the firewall and SNAT rules defined (NSX-T only) 



1. Log in to the NSX-T Manager, and click Networking in the menu.
2. Click NAT from the left navigation pane.
3. Select the T0 consolidated gateway from the Gateway list.

The EntrustCC SNAT rules are displayed in the NAT rules table.







 Known issue about Network Time (Entrust CloudControl 5.x only)
* 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
: You can now use IBM Cloud Monitoring to view and customize dashboards to visualize performance, volume of usage, and to define alerts to monitor your environment.

VMware Solutions Dedicated - removed support for VMware vSphere 6.5u3
: VMware vSphere 6.5u3 is no longer supported for new VMware vCenter Server instances. Full support remains for existing instances, including support to add new hosts and clusters.

VMware vSphere 6.5u3 is no longer supported for new VMware vSphere clusters. Full support remains for existing clusters, including support to add new hosts.

VMware Solutions Dedicated - VMware NSX updates
: Review the following information about vCenter Server with NSX-T instances.



* New instances of vCenter Server with NSX-T are provisioned with NSX-T 3.0.1.1.
* Day 2 operations continue to be supported for vCenter Server with NSX-T 2.5.1 instances.
* If you want to upgrade your existing vCenter Server with NSX-T instance, you must upgrade to NSX-T 3.0.2.



VMware Solutions Dedicated - new Cascade Lake server support
: The following IBM Cloud bare metal servers are available for deployment for vCenter Server instances and vSphere clusters with vSphere 6.7.



* Dual Intel Xeon Platinum 8260 / 48 Cores, 2.4 GHz
* Quad Intel Xeon Platinum 8260 / 96 Cores, 2.4 GHz



VMware Solutions Dedicated - support for Osaka IBM Cloud data centers
For more information about NSX Edge certificate formats, see [Importing SSL Certificates](https://docs.vmware.com/en/VMware-NSX-Data-Center-for-vSphere/6.3/com.vmware.nsx.admin.doc/GUID-19D3A4FD-DF17-43A3-9343-25EE28273BC6.html).









 Deployment process for HCX 

The deployment of HCX is automated. Whether you order a vCenter Server instance with the service included or you deploy the service later into your instance, the following steps are completed by the IBM Cloud for VMware Solutions automation process:



1. Three subnets are ordered for HCX from the IBM Cloud infrastructure:



* One private portable subnet for HCX management.
* One private portable subnet for HCX interconnects. This subnet is used when the Private network option is selected for HCX connection type.
* One public portable subnet for HCX interconnects, if the Public network option is selected for HCX connection type. On NSX-V, this subnet is also used for activation and maintenance with VMware.



The IP addresses in the subnets that are ordered for HCX are intended to be managed by the VMware Solutions automation. These IP addresses cannot be assigned to VMware resources (such as VMs and NSX Edges) that are created by you. If you need more IP addresses for your VMware artifacts, you must order your own subnets from IBM Cloud.
2. If Private Network was selected for HCX Network Connection, a port group that is named SDDC-DPortGroup-HCX-Private is created on the private Distributed Virtual Switch (DVS).
3. An HCX activation key is ordered from VMware.
4. For vCenter Server with NSX-T instances, the firewall rules and network address translation (NAT) rules are configured to allow inbound and outbound HTTPS traffic to and from the HCX Manager.
5.
Veeam on IBM Cloud overview 

Veeam® on IBM Cloud seamlessly integrates directly with your VMware® hypervisors to help your enterprise achieve high availability. This service provides recovery points and time objectives for your applications and data. The recovery points and time objectives can be provided in less than 15 minutes after configuration is completed.

By using this service, you control both the backup and restore of all virtual machines (VMs) for your infrastructure directly from the Veeam console. Veeam on IBM Cloud is a non-IBM product that is offered under terms and conditions from Veeam, not IBM.

IBM Cloud® for VMware Solutions offers promotions for some services. Promotional pricing offers a number of months without charge for a service license, if the service has license charges. For more information, see [Promotions for VMware Solutions services](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_addingservicesvc_addingservices-service-promotions).

The Veeam service that is installed is Veeam Availability Suite™ 12 (known as Veeam 12).



 Veeam on a bare metal server 

You can install Veeam Backup and Replication 12 on a bare metal server. This installation is supported only for VMware vSphere® 7.0 with VMware NSX-T™.



* For VMware Regulated Workloads, the Veeam bare metal server is the only option. For Security and Compliance Readiness Bundle, the Veeam bare metal server is the default option with a choice of switching to Veeam VM.
* Veeam is always deployed on the management cluster.
* No migration path is available for existing Veeam users.



For more information about Veeam on bare metal server, see the following topics.



* [Veeam on bare metal server introduction](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-veeam-bms-archi-intro)
* 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. Also, migrate the VMs running on them manually using the VMware vSphere Web Client. After that, delete the ESXi servers by using the IBM Cloud for VMware Solutions console.









 Procedure to delete ESXi servers 



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 for which you want to contract capacity.
3. Click the Infrastructure tab.
4. In the CLUSTERS table, click the cluster from which you want to delete ESXi servers.
5. In the ESXi servers table, select the servers that you want to delete and click Delete.





 Results after you delete 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 are notified by email that your request to delete 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. The ESXi servers are fully reclaimed by IBM Cloud infrastructure at the end of the IBM Cloud infrastructure billing cycle, which is typically 30 days.

You are billed until the end of the IBM Cloud infrastructure billing cycle for the deleted ESXi servers.









 Related links 



* [vCenter Server BOM](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_bom)
How do I increase the max_connections on my IBM Cloud® Databases for PostgreSQL deployment? 

If you encounter an error when attempting to increase the max_connections on your IBM Cloud® Databases for PostgreSQL deployment, review these solutions.

  What’s happening 

You receive a superuser error message when attempting the increase the max_connections on your IBM Cloud® Databases for PostgreSQL deployment.

  How to fix it 

Review the following information to troubleshoot and resolve your max_connections issues:



*  The preferred method for this process is to use [Connection Pooling](https://cloud.ibm.com/docs/databases-for-postgresql?topic=databases-for-postgresql-managing-connectionsconnection-pooling). Connection pooling prevents you from exceeding the connection limit and ensures that connections from your applications are being handled efficiently.
*  Alternatively, see [Changing your IBM Cloud® Databases for PostgreSQL Configuration](https://cloud.ibm.com/docs/databases-for-postgresql?topic=databases-for-postgresql-changing-configuration).
Adding ESXi servers to Cyber Recovery instances 

You can expand the capacity of your Cyber Recovery instance according to your business needs by adding VMware ESXi™ servers.



 Before you add ESXi servers to Cyber Recovery instances 



* For the gateway cluster, you cannot add or remove ESXi servers.
* Whenever possible, add ESXi servers by using the VMware Solutions console because changes that you make on the VMware vSphere® Web Client are not synchronized with the VMware Solutions console. Therefore, add ESXi servers to Cyber Recovery only for on-premises ESXi servers or ESXi servers that you don't manage in the VMware Solutions console.
* For the consolidated cluster, you can order 1-51 servers in total, taking into account the existing number of hosts in the cluster.
* For the workload cluster, you can order 1-59 servers in total, taking into account the existing number of hosts in the cluster.
* If your initial cluster has vSAN storage, adding one or more ESXi servers after deployment can increase the cluster storage capacity.
* If your initial cluster has vSAN storage, SED SSD disks are not available. Non-SED SSD disks are ordered.







 Procedure to add ESXi servers to Cyber Recovery instances 



1. From the IBM Cloud® for VMware Solutions console, click Resources > Cyber Recovery from the left navigation pane.
2. In the Cyber Recovery table, click the instance for which you want to expand capacity.
3. Click the Infrastructure tab.
4. In the Clusters table, click the cluster to which you want to add ESXi servers.
5. In the ESXi servers section, click Add.
6. On the Add ESXi server side panel, enter the number of bare metal servers that you want to add. You can keep the Maintenance mode checkbox selected to add servers during maintenance mode.

When you provision new ESXi servers, virtual machines (VMs) are immediately migrated to the new servers if you do not select the Maintenance mode checkbox. You do not receive a confirmation message before the migration begins.
7. Complete the bare metal server configuration.
* Preparing the IBM CloudDriver...
* The IBM CloudDriver is ready.
* The <ip_address> IBM CloudDriver is ready to use.
* Checking the IBM CloudDriver status...
* Reusing the existing <ip_address> IBM CloudDriver...
* Reusing the existing IBM CloudDriver (In Provisioning)...
* Releasing the IBM CloudDriver...
* Releasing the <ip_address> IBM CloudDriver...
* Starting the IBM CloudDriver deletion...
* Completed the IBM CloudDriver deletion.







 Storage history messages 

IBM Cloud for VMware Solutions issues the following messages for storage settings.



* Ordering the vSAN license...
* Cancelling the vSAN license...
* The vSAN license cancellation is complete.
* Ordering <quantity> NFS storage(s) for the <cluster_name> cluster.
* The new NFS storage is added and ready to use.
* Cancelling Management NFS share storage...
* The selected NFS storage is deleted.
* Starting the order for Endurance Storage...
* Cancelling Endurance Storage...







 Service history messages 

IBM Cloud for VMware Solutions issues the following messages for services.



* Starting the management services setup...
* Ordering service entries...
* Completed the order for service entries.
* IBM operation services are running.
* Enabling the default services...
* The default services are successfully enabled.
* Service entry cancellation in progress...
* Service entry cancellation is complete.







 Related links 



* [Considerations about changing vCenter Server artifacts](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vcenter_chg_impactvcenter_chg_impact-automation-id)
* [Auditing events for VMware Solutions](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-at-eventsat-events)