vania-janet/multiturn-rag-retrieval-data huggingface dataset:
With IBM Cloud for VMware Solutions, you can quickly and seamlessly integrate or migrate your on-premises VMware workloads to the IBM Cloud by using the scalable, secure, and high-performance IBM Cloud infrastructure and the industry-leading VMware hybrid virtualization technology. You can easily deploy your VMware virtual environments and manage the infrastructure resources on IBM Cloud. At the same time, you can still use your familiar native VMware product console to manage the VMware workloads. [Learn more](https://www.ibm.com/cloud/vmware).

The following table lists VMware solution services that send auditing events:



Table 15. List of VMware solution services

 Service CRN service name Activity Tracker hosted event search offering Events 

 [IBM Cloud for VMware Solutions](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_vcenterserveroverview) vmware-solutions ![Checkmark](https://cloud.ibm.com/docs-content/v1/content/6f3c07c34058f637b1c86044ca4f9b24214330a7/activity-tracker//images/checkmark-icon.svg) [Global events](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-at-eventsat-events) 
 [IBM Cloud® for VMware® Solutions Shared](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-shared_overview) vmware-solutions !
Viewing gateway appliance details 

Network gateways are used to control network traffic on a VLAN that is regularly controlled by a router. Within the Gateway Appliance Details page on the IBM Cloud console, you can associate, disassociate, route and bypass VLANs associated with a network gateway.

Perform the following procedure to reach the Gateway Appliance Details page.



1.  From your browser, open the [IBM Cloud catalog](https://cloud.ibm.com) and log in to your account.
2.  Select the Menu icon from the top left, then click Classic Infrastructure.
3.  Choose Network > Gateway Appliances.
4.  Click the name of the network gateway you want to view to access the Gateway Appliance Details page.



Use the Bulk Actions feature to take action on multiple VLANs at the same time.
* Regional-level High Availability through creating VMware Cloud Director provider virtual data centers (PVDCs) and vCenter clusters in multiple data centers in the same region.
* Full compatibility to run existing VMware workloads. Migration of existing IBM Cloud, on-premises or other workloads are fully supported.
* Each VMware as a Service instance contains the following VMware components:



* Dedicated VMware ESXi™ hosts
* Dedicated VMware vCenter
* Dedicated VMware NSX-T™ with dedicated networking
* Dedicated VMware Cloud Director



* Right-size and scale the VMware environment



* Add and remove hosts per VMware vCenter cluster
* Add and remove storage per VMware vCenter cluster
* Add and remove VMware vCenter clusters
* Add and remove VMware Cloud Director PVDCs



* Create and delete virtual data centers to deploy VMware workload vApps and virtual machines in VMware Cloud Director







 Billing specifications for VMware as a Service 

VMware as a Service instances incur charges for the following components:



* NFS size and performance tiers used
* Host type and counts used
* Egress public networking
* Networking edge types and counts
* Optional Veeam Backup and Replication service







 Related links 



* [Ordering VMware as a Service instances](https://cloud.ibm.com/docs/vmware-service?topic=vmware-service-tenant-ordering)
* [Viewing VMware as a Service instances](https://cloud.ibm.com/docs/vmware-service?topic=vmware-service-tenant-viewing)
* [Visualizing your site with IBM Cloud Monitoring](https://cloud.ibm.com/docs/vmware-service?topic=vmware-service-single-tenant-monitoring)
* [Deleting VMware as a Service instances](https://cloud.ibm.com/docs/vmware-service?topic=vmware-service-tenant-deleting)
Along with the internet access methods, you can use IBM Cloud service endpoints to access your virtual data centers from other IBM Cloud accounts. This way, you can use DirectLink or other on-premises environments to access your IBM Cloud account network options. Then, from your cloud account, you can connect into your virtual data centers by using the Cloud Service Endpoint method.
* How are my VMware virtual platform consumptions billed?

All costs for the physical and virtual infrastructure and the licenses that result from the instance are charged to your IBM Cloud account. When you order an instance, you must have an IBM Cloud account and provide the SoftLayer API key that is associated with the account.
* How do I choose the data centers for my instances?

The instance deployments have strict physical infrastructure requirements, which vary among IBM Cloud data centers. When you place your instance order, the available data centers are listed within regions and you can select the one that you want from the list.

For more information, see [IBM Cloud data center availability](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-shared_planningshared_planning-dc-availability).
* How long does it take for my instance to be deployed?

You can check the status of the instance deployment by viewing the deployment history on the instance details page from the IBM Cloud for VMware Solutions console.
* How can I view a list of all notifications?

To view the complete notification history, click Notifications from the left navigation pane.
* What if I have issues with VMware Shared?

If you need assistance with IBM Cloud for VMware Solutions, open an IBM Support ticket by following the steps in [Contacting IBM Support](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-trbl_support).
* Can I bring my own firewall?

Yes. Each customer virtual data center comes with an edge firewall in the ESG and a distributed firewall that protects the internal virtual data center environment.
* For the [VMware Solutions API](https://cloud.ibm.com/apidocs/vmware-solutions), support is provided for VMware vSphere cluster new deployments and for the KMIP for VMware stand-alone service.



User interface updates and enhancements
: Various error messages and tooltip enhancements are available to assist you in selecting the appropriate setting on the user interface.



* You can now view site and virtual data center details from the Resources page for VMware Shared.
* The following enhancements are made to the ordering page for IBM Cloud for VMware Solutions offerings.



* A vertical progress indicator bar is now available that maps each section on the ordering page and helps to quickly browse to different areas of the page. You can directly jump onto any specific section of the page by clicking the heading in the progress bar. When you scroll through the page, the progress bar also keeps a check on whether the data is entered or not.
* The CPU model selection tile group is now changed to a list of items in a table. You can select the CPU model of your choice from the table.









 25 April 2022 

VMware Cloud Director upgrade for VMware Solutions Shared
: (Updated on 8 May 2022) VMware Solutions provides an upgrade to the VMware Shared infrastructure to VMware Cloud Director (vCD) v10.3.3.

Compute policy support for VMware Solutions Shared virtual data centers
: You can now choose to enable a compute policy for a VMware Solutions Shared virtual data center. This feature provides a convenient option to choose a compute policy for your virtual machine (VM) from the list of policies that are available for that virtual data center.

vSAN support for VMware Solutions Shared virtual data centers
: vSAN™ support is now available for Dallas 10 and Dallas 12 VMware Solutions Shared virtual data centers.

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



* VMware vSphere ESXi 7.0 Update 2e (build 19290878)
* ibmcloud dl vcc fb0df64a-ef8d-4b3c-b473-dc0230593529 --type vpc --network-id crn:v1:staging:public:is:us-south:a/28e4d90ac7504be694471ee66e70d0d5::vpc:r134-b8b62f60-f152-471f-971a-376da52721e0 --name newVC --output json









 ibmcloud dl virtual-connection-delete 

Delete a virtual connection.

ibmcloud dl virtual-connection-delete|vcd GATEWAY_ID VIRTUAL_CONNECTION_ID [--help|-h] [--force|-f]



 Command options 

GATEWAY_ID
: Specify the ID of the gateway.

VIRTUAL_CONNECTION_ID
: Specify the ID of the virtual connection.

--help|-h
: Get help on this command. Optional.

--force|-f
: Force the delete operation without confirmation. Optional.





 Examples 



* ibmcloud dl virtual-connection-delete fb0df64a-ef8d-4b3c-b473-dc0230593529 0b1e165c-a89c-4682-9771-dbe062e3acf7
* ibmcloud dl vcd fb0df64a-ef8d-4b3c-b473-dc0230593529 26284b6e-78a9-416c-ba5e-2b6ec085f18b -f









 ibmcloud dl virtual-connection-update 

Update a virtual connection.

ibmcloud dl virtual-connection-update|vcu [--name NAME] [--status STATUS] [--help|-h] [--output format]



 Command options 

--name NAME
: Specify the name of the virtual connection.

--status STATUS
: Specify the virtual connection status.
: You can improve network performance on your virtual server instance by configuring jumbo frames in your virtual server settings. You can configure jumbo frames for the following operating systems.



* Linux: Debian, Ubuntu, CentOS, Red Hat Enterprise Linux
* Windows









 May 2019 



 07 May 2019 

Autoscale now available for virtual servers
: Auto scale for IBM Cloud® Virtual Servers provides you with the ability to automate the manual scaling process that's associated with adding or removing instances to support your business applications. This automation sets up new instances automatically as more resources are needed and then those instances are shut down and removed when the extra load subsides. Auto scale uses groups to contain the policies that change how your environment expands or shrinks. These policies use actions to add or remove virtual server based on your business and application needs. For more information, see [Auto scale](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-about-auto-scale).







 April 2019 



 15 April 2019 

View and update device details for virtual servers
: You can now view the existing usernames and passwords for a device or update those values from the device details page. For more information, see [Viewing and managing device usernames and passwords](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-view-update-user-name-password-for-device).





 24 April 2019 

New profile families for virtual server
: When you provision IBM Cloud® Virtual Servers, you can select from supported families of profiles. A profile is a combination of vCPU and RAM that can be instantiated quickly to start a virtual server instance. In the IBM Cloud console, you can choose from popular profile configurations or select from a list of profiles that best fit your needs. For more information, see [Profiles](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-about-virtual-server-profiles).







 October 2018 



 03 October 2018 

Provision virtual server by using 3rd-party images
VPC networking overview 

Properly setting up and managing your networking components is critical to building a solution that meets the [best practices and requirements](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-best-practices) of the IBM Cloud Framework for Financial Services. This is the starting point for learning how to perform those tasks for the [VPC reference architecture](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-about).



  Next steps 

Walk through the topics for how to build out your networking solution:



*  [Creating and connecting the management and workload VPCs](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-connectivity-create-vpcs)
*  [Connecting application provider to the management VPC](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-connectivity-management)
*  [Running operator actions through bastion host](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-connectivity-bastion)
*  [Consumer connectivity to workload VPC](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-connectivity-workload)
*  [Connectivity to IBM Cloud services with private endpoints](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-connectivity-to-services)
*  [Accessing the public internet](https://cloud.ibm.com/docs/framework-financial-services?topic=framework-financial-services-vpc-architecture-connectivity-to-internet)
* Integrates with DNS Services.

When creating an endpoint gateway, a DNS zone and records are created. The VPE service automatically upgrades your virtual server instances to use the private DNS as the default DNS resolver. For more information, see [DNS Services](https://cloud.ibm.com/docs/dns-svcs?topic=dns-svcs-getting-started).







 Supported services 

For supported IBM Cloud services, see [VPE supported services](https://cloud.ibm.com/docs/vpc?topic=vpc-vpe-supported-services).





 VPE connectivity patterns 

VPE for VPC IP addresses use a multi-zone-region, logical endpoint gateway to connect to a service endpoint on the IBM Cloud private backbone. The endpoint gateway is designed to support the best practice of binding a single IP from each zone of the VPC. You can create an endpoint gateway with zero IP addresses and bind IPs as each zone is brought online.

As more IBM Cloud services are enabled for VPE for VPC, each service instance will require you to configure its endpoint gateway, but will leverage the same topologies and best practices. For additional provisioning and best practices guidelines, refer to the documentation provided by the individual service.



 Single-zone topology 

Zoom

![VPE single-zone topology](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/vpc//images/vpe-single-zone.png)

Figure 1. VPE single-zone topology





 Multi-zone topology 

Zoom

![VPE multi-zone topology](https://cloud.ibm.com/docs-content/v1/content/f02b9c9adcbb7328d95a45e105cec371d50f15eb/vpc//images/vpe-multi-zone.png)

Figure 2. VPE multi-zone topology
ibmcloud dl virtual-connections 

List virtual connections.

ibmcloud dl virtual-connections|vcs [--help|-h] [--output format]



 Command options 

--help|-h
: Get help on this command. Optional.

--output value
: Specify whether you want the output displayed in JSON format. Currently, json is the only supported format. Optional.





 Examples 



* ibmcloud dl virtual-connections a771366f-2c8c-49f6-a23b-9d49fad035a3
* ibmcloud dl vcs a771366f-2c8c-49f6-a23b-9d49fad035a3 --output json
The data that you store in Hyper Protect Virtual Servers is encrypted securely at rest by using a randomly generated key, which the underlying [IBM Secure Service Container technology](https://www.ibm.com/us-en/marketplace/secure-service-container) manages. Use the Linux command-line tools to delete data in a virtual server.





 Data in flight 

The IBM LinuxONE infrastructure components for the Hyper Protect Virtual Servers service are situated in colocation with the data centers. This means that these components are placed in the same data centers as the IBM Cloud infrastructure but have their own network setup, which affects the network connection.

Zoom

![Hyper Protect Virtual Servers** architecture network isolation](https://cloud.ibm.com/docs-content/v1/content/29e0ddc9fd7149f916889ba6a4d131cc3528c9bc/hp-virtual-servers/image/hpvs_architecture-vs_network_overview.svg)

Figure 1. Hyper Protect Virtual Servers Architecture network isolation

It is your responsibility to protect the connection for any application that runs in your IBM Cloud and it is recommended that you follow these guidelines:



* You can either use the public route or a private route through [IBM Cloud Service Endpoints](https://cloud.ibm.com/docs/account?topic=account-service-endpoints-overview) if you want to connect any other service to a Hyper Protect Virtual Servers instance. You can find a list of all IBM Cloud services, which support IBM Cloud Service Endpoints [here](https://cloud.ibm.com/docs/account?topic=account-vrf-service-endpointuse-service-endpoint). It is recommended that you use a protected connection if you use the public route, for example, a VPN.
* Public IP addresses are mapped to internal IP addresses on all ports. Make sure you open only the ports on your virtual server that you want to be exposed to the public network.
* Use the internal IP address to connect from one virtual server to another in the same region via the internal network. Your traffic on the internal network is automatically isolated from other tenants.
* If you are using VMware NSX-V, familiarize yourself with VMware product lifecycle for NSX-V and make appropriate plans to migrate your workloads to NSX-T.
* vCenter Server is designed to allow for a “rolling” upgrade. That is, virtual machine (VM) workloads that are currently functioning continue to function without an outage if you complete the following procedure. Enterprises must engage their change management policies to enable a structured and communicated upgrade and plan for contingencies. However, during the upgrade process of certain management functions, such as vCenter Server and NSX Manager, temporary outages of management functions, configuration changes, powering off and on VMs, might be impacted.







 Before you begin 

The time to complete the upgrade is unknown. It is possible that it might take several maintenance windows to completely upgrade an environment. Running up-leveled and down-leveled versions of the SDDC software is supported by VMware during the upgrade process. However, some functions such as vMotion, maybe limited during this process.

Complete the following requirements before you begin the upgrade:



* Upgrade any extensions or snap-ins within the vCenter Server environment. Review the following documentation before you plan your upgrade:



* [VMware vSphere 7.0 release notes](https://docs.vmware.com/en/VMware-vSphere/7.0/rn/vsphere-esxi-vcenter-server-70-release-notes.html)
* [About VMware ESXi upgrade](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.esxi.upgrade.doc/GUID-65B5B313-3DBB-4490-82D2-A225446F4C99.html)



* Set up vSphere Update Manager (VUM) within your vCenter Server instance to download updates from VMware vSphere.
Installing VMware Tools - Linux 

VMware Tools is a suite of utilities that enhances the performance of the virtual machine’s guest operating system and improves management of the virtual machine. Installing VMware Tools in the guest operating system is vital. Although the guest operating system can run without VMware Tools, you lose important functionality and convenience.

The service is named vmware-guestd on Linux, FreeBSD, and Solaris guests. The vmware-guestd service performs the following duties within the guest operating system:



*  Passes messages from the host operating system to the guest operating system.
*  Executes commands in the operating system to cleanly shut down or restart a Linux, FreeBSD, or Solaris system when you select power operations in Workstation.
*  Synchronizes the time in the guest operating system with the time in the host operating system.
*  Runs scripts that help automate guest operating system operations. The scripts run when the virtual machine’s power state changes.



The service starts when the guest operating system starts.

To install VMware tools on a Linux server, right-click the appropriate server in your vSphere client, hover over Guest, and click Install/Upgrade VMware Tools.

This link mounts a virtual CD-ROM drive that contains the VMware tools rpm. To install the tools after you mount the virtual CD-ROM drive, follow these steps:



1.  Mount the CD-ROM drive by using the command: mount /dev/cdrom /mnt
2.  Verify that the file exists and is mounted correctly by using the ls /mnt command on the mounted directory. You see the file VMWareTools-4.0.0-208167.i386.rpm.
3.  Run the command rpm –ivh /mnt/VMWareTools-4.0.0-208167.i386.rpm.
4.  Run the following command to configure VMware Tools for the running kernel: /usr/bin/vmware-config-tools.pl. Note: You are asked to press ENTER once midway during the configuration updates. Note: It is not necessary to restart the VM after you install the VMware tools however, it is recommended.



If the VMware tools installed correctly, “OK” is displayed within your vSphere Client interface.
When you manage user accounts, instances, clusters, and services in IBM Cloud for VMware Solutions, an event is generated.

The following table provides the actions that generate and send management events to Activity Tracker.



Table 2. Description of actions that generate management events

 Action Description 

 vmware-solutions.account-apikey.update The infrastructure API key for an account is updated. 
 vmware-solutions.account-notification.update The notification setting for an account is updated. 
 vmware-solutions.instance-secure-data.wipe The instance-secure data is wiped. 
 vmware-solutions.instance-bss-account.migrate An instance is migrated to a BSS account. 
 vmware-solutions.vcs.create A VMware vCenter Server® instance is created. 
 vmware-solutions.vcs.delete A vCenter Server instance is deleted. 
 vmware-solutions.vcs-host.add A host is added to a vCenter Server instance. 
 vmware-solutions.vcs-host.remove A host is removed from a vCenter Server instance. 
 vmware-solutions.vcs.update A vCenter Server instance is updated. 
 vmware-solutions.vcs-cluster.create A cluster is created for a vCenter Server instance. 
 vmware-solutions.vcs-cluster.delete A cluster is deleted for a vCenter Server instance. 
 vmware-solutions.vcs-nsx-license.update The VMware NSX® license is updated for a vCenter Server instance. 
 vmware-solutions.vcs-nfs-storage.add NFS storage is added to a vCenter Server instance. 
 vmware-solutions.vcs-nfs-storage.remove NFS storage is removed from a vCenter Server instance. 
 vmware-solutions.vcs-plan.update A vCenter Server instance's plan is updated. 
 vmware-solutions.vss.create A vSphere instance is created. 
 vmware-solutions.vss.update A vSphere instance is updated. 
 vmware-solutions.vss-template.remove A vSphere template is removed.
Supported vCenter of 5.5U3 or vCenter 6.0U2 and higher, with ESXi 5.5 or higher is required for Hybrid Cloud Services.
* If NSX is used, version 6.2.2 or higher. NSX is required for policy migration.
* If cross-cloud vMotion is intended, the same affinity restrictions apply across clouds as they do on-premises.
* The source environment must have a method to connect to cloud environments, which includes public internet access or private connections by using IBM Cloud Direct link.
* The source environment VM’s and networks to be migrated or stretched must be on portgroups within a Virtual Distributed Switch.
* The IBM Cloud must contain at least one instance of VMware vCenter Server®.
* Sufficient resources for the virtual appliances.
* The networks must allow the appliances to communicate with both local and remote virtual appliances, and other VMs.
* The port access requirements topic lists ports that must be opened so that Hybrid Cloud Services virtual appliances can be installed successfully.
* A vSphere service account exists and the Administrator vCenter Server system role is assigned to it.
* Enough disk space for installing Hybrid Cloud Services and the associated service appliances.
* Sufficient IP addresses for the on-premises VMs provisioned during the installation.
* If the SSO server is remote, the URL of the vCenter, external SSO Server, or Platform Services Controller (PSC) that runs the external lookup service must be identified. When the HCX service is registered with the vCenter, this URL must be supplied.







 Related links 



* [VMware HCX introduction](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-hcx-archi-intro)