vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Viewing VMware as a Service instances 

View the summary and detailed information of the IBM Cloud® for VMware as a Service instances that are provisioned in your account.



 Procedure to view a summary of VMware as a Service instances 



1. In the VMware Solutions console, click Resources > VMware as a Service from the left navigation pane.
2. In the VMware as a Service table, click either the Virtual data centers tab or the Cloud director sites tab to view the list of instances that are provisioned.
3. Review the name, location, and status of the provisioned instances.







 Procedure to view details for VMware as a Service instances 



1. In the VMware as a Service table, click either the Virtual data centers tab or the Cloud director sites tab. Then, click an instance name.
2. On the Summary tab, review the virtual data center or Cloud Director site details.
3. For virtual data centers, the following options are available.



* On the Summary tab, toggle fast provisioning off or on.
* On the Add-on services tab, you can:



* Enable or delete Veeam® Backup and Replication.
* Click Veeam backups to open the Self-Service Backup Portal.





4. For Cloud Director sites, the following options are available.



* On the Summary tab, you can:



* Click Set IAM integration to enable IAM (Identity Access Management) for existing sites. For more information, see [Managing resource groups](https://cloud.ibm.com/docs/account?topic=account-rgs).
* Click Enable Veeam to provision Veeam Backup and Replication for your instance.



* On the Infrastructure tab, you can:



* Click the Clusters tab, view all clusters that are deployed into the instance. Click a cluster name to review information such as total cores and RAM, host units, storage type, and cluster status.
* Click the Virtual data centers tab to view all VDCs deployed into the instance. Click a VDC to review information such as public IP addresses.
* Click the Network edges tab to view the edges deployed into the instance.
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)
* VMware vSphere ESXi 6.7 P06 (build 18828794)
* VMware vCenter Server Appliance 6.7.0 Update 3q (build 19300125)
* VMware NSX-T 3.2.0.1.0 (build 19232400)
* VMware NSX-V 6.4.13 (build 19307994)



VMware ESXi firewall configuration for NFS
: (Updated on 7 June 2022) IBM Cloud® identified a problem with the following feature, which might cause some firewall rules to be lost during the update. This problem is now fixed.

VMware ESXi attempts to manage the outbound firewall for NFS traffic for you automatically. Under some circumstances, VMware ESXi might not discover all IP addresses for an NFS data store, sometimes resulting in loss of connectivity if the IBM Cloud Endurance servers are undergoing maintenance. VMware Solutions corrects the ESXi firewall configuration whenever adding hosts, clusters, or storage to your vCenter Server instance. For more information about ESXi firewall rules, see [NFS client firewall behavior](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.vsphere.storage.doc/GUID-70686ADB-961A-46BD-B814-48DCF6C5E34B.html).

Loss of connectivity to NFS storage
: (Updated on 7 June 2022) See Why did my host lose connection to my NFS datastore?
Firewalls 

With IBM Cloud® Virtual Servers, you have several firewall options that provide an essential security layer. The firewall options are provisioned on demand, without service interruptions. The firewall services prevent unwanted traffic from reaching your servers, reducing the likelihood of an attack, and by allowing your server resources to be dedicated for their intended use.

Firewalls are available as an add-on feature for all servers on the infrastructure public network.

As part of the ordering process, you can select device-specific hardware or a software firewall to provide protection. Alternatively, you can deploy dedicated firewall appliances to the environment and deploy the virtual server to a protected VLAN.

You can't protect a virtual server with two firewall appliances on the same interface.

For more information, see the following security topic collections.



*  [Hardware firewalls (Shared)](https://cloud.ibm.com/docs/hardware-firewall-shared?topic=hardware-firewall-shared-about-hardware-firewall-shared-)
*  [Hardware firewalls (Dedicated)](https://cloud.ibm.com/docs/hardware-firewall-dedicated?topic=hardware-firewall-dedicated-about-the-hardware-firewall-dedicated-)
* VMware vSphere ESXi™ 7.0 Update 3k (build 21313628)



Add-on services upgrades
: The following service versions are now available for deployment:



* Entrust CloudControl™ v6.6
* F5® BIG-IP® v17.0
* vRealize Operations and vRealize Log Insight v8.10
* Zerto v9.7u1



F5 BIG-IP migration from NSX-V to NSX-T
: To migrate the F5 BIG-IP service from VMware NSX-V to VMware NSX-T, open an IBM Support ticket by following the steps in [Contacting IBM Support](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-trbl_support).

New and updated documentation
: Documentation is available to assist with your custom cyber-recovery requirements. For more information, see [Cyber Recovery with Bring Your Own appliances](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-cr-byo-overview).

REST API updates
: The [VMware Solutions API](https://cloud.ibm.com/apidocs/vmware-solutions) provides support for getting and canceling billing item IDs for VMware vSphere clusters, deleting hosts from vSphere clusters, and deleting vSphere clusters.

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



* BYOL notification in the Licensing section for VMware vCenter Server instances, VMware vSphere clusters, add hosts and clusters, vRealize Operations and Log Insight, and VMware HCX™ services. Bring Your Own License (BYOL) is no longer supported, except for migrations or upgrades of existing BYOL clusters.
* The term edge services cluster is updated to edge gateway cluster throughout the UI, user documentation, and REST APIs.
After the previous configuration is completed, you can use the supported IBM Cloud services on the VMs in your virtual data center.

If your vApp or VM is deployed from the IBM templates that are provided in the public catalog, the services are already configured on the VM. To enable the connection, you must complete the previous steps in Adding the NAT rule and Adding the firewall rule.





 Adding the firewall rule for VMware as a Service 

Add a firewall rule to allow the traffic from the internal network to the service network.



1. Under the Services section, click the Firewall tab and click EDIT RULES. Then, click NEW ON TOP to add a firewall rule.
2. Add the IP addresses or range from your internal network to the Source field.
3. Add 52.117.132.1/24 in the Destination field.
4. Select Allow in the Action field.
5. Click Save.



After the previous configuration is completed, you can use the supported IBM Cloud services on the VMs in your virtual data center.

If your vApp or VM is deployed from the IBM templates that are provided in the public catalog, the services are already configured on the VM. To enable the connection, you must complete the previous steps in Adding the NAT rule and Adding the firewall rule.







 Creating a vApp Network for VMware Solutions Shared 

If not already completed, create a vApp containing at least two VMs. For more information, see [Working with vApps](https://docs.vmware.com/en/VMware-Cloud-Director/10.1/VMware-Cloud-Director-Tenant-Portal-Guide/GUID-AC48FB5E-4ADC-4835-AACE-B949B297A147.html).



1. From the tenant portal, click the Menu icon at the upper left of the page and select Data Centers.
2. From the main page under Virtual Data Center, click the virtual data center where you would like to create the vApp network.
3. In the left pane under Compute, click vApps.
4.
For more information, see [Understanding business continuity and disaster recovery](https://cloud.ibm.com/docs/vmware-service?topic=vmware-service-bc-dr). 
 Recovery of configuration Conduct recovery in the original data center after the infrastructure is available. 
 Recovery of workloads Restore capabilities are available in normal operations. For configuration restores, provide customer restore services after the infrastructure is available. If an offsite recovery is required, IBM works with the customer to help recover. Restore backups from your chosen backup provider. For more information, see [Understanding business continuity and disaster recovery](https://cloud.ibm.com/docs/vmware-service?topic=vmware-service-bc-dr). 







 Operating system licensing 

Operating system (OS) licensing refers to the operating system software and configuration that are deployed in virtual machines (VMs) or underlying bare metal servers.



Table 6. Responsibilities for OS licensing
The rows are read from left to right. The first column describes the task that a customer or IBM might be responsibility for. The second column describes IBM responsibilities for that task. The third column describes your responsibilities as the customer for that task.

 Item IBM responsibilities Your responsibilities 

 Workload OS licensing Provide OS licensing for infrastructure tools part of the service, such as VMware and add-on services solution components. Provide OS licensing for your workloads that are running inside your virtual data centers' VMs or vApps.
* Patching and Upgrading - vSphere Update Manager (VUM) provides centralized, automated patch and version management for VMware vSphere hosts and virtual machines (VMs) (not OS and apps).







 Operation management networking 

The following diagram shows the network overview.

Zoom

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

Figure 2. Operational tools networking



* A tooling private portable subnet is provisioned to provide IBM Cloud IP address space that is used for the initial provisioning of the tooling VMs. After provisioning, it becomes the responsibility of the client to manage the IP address space for scale-out of the tooling. VMs on this subnet require access to the components hosted on the Management and Internal Management subnets.
* Tooling VXLAN subnet is used to provide BYOIP IP address space that is used for the initial provisioning of the tooling VMs but then becomes the responsibility of the client to manage the IP address space for scale-out of the tooling. VMs on this subnet require access to the components hosted on the Overlay subnets. The ESG provides NAT between the IBM Cloud and BYOIP address spaces.
* The VMware Aria Operations Remote Collectors are deployed by the client if they would like to take advantage of the VMware Aria Operations to monitor their compute VMs.
* The VMware Aria Operations for Logs Forwarders relay log messages from overlay components to the VMware Aria Operations for Logs cluster. The client can also configure their compute VMs to uses these forwarders, if required.
* VMware Update Manager (VUM) provides updating of vSphere hosts and VM hardware and tools. VUM uses the Proxy to gain access to the internet repositories.



VMware Aria Operations collects data from objects in the environment. Each piece of data that is collected is called a metric observation or value.
FAQs: Virtual servers 



 What types of virtual servers are available for use? 

IBM Cloud® offers a couple types of virtual servers within its Classic Infrastructure. The standard offering is a public-based virtual server, which is a multi-tenant environment that is suitable for various needs. If you're looking for a single-tenant environment, consider the dedicated virtual server offering. The dedicated virtual server option is ideal for applications with more stringent resource requirements. For more information about the current virtual server offerings, see [Getting started with virtual servers](https://cloud.ibm.com/docs/virtual-servers?topic=virtual-servers-getting-started-tutorial).

IBM Cloud® Virtual Servers for Virtual Private Cloud (VPC) is the next generation of virtual servers. You create your own space in the IBM Cloud to run an isolated environment within the public cloud by using VPC. IBM Cloud VPC provides the security of a private cloud with the agility and ease of a public cloud. For more information, see [About virtual server instances for VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-about-advanced-virtual-servers).





 Where can I find pricing information for public instance types? 

For more information, see [Build your virtual server](https://www.ibm.com/cloud/virtual-servers).





 Where can I find pricing information for virtual public instances? 

Estimating your cost for an IBM Cloud server to support your workload begins in the [IBM Cloud catalog](https://cloud.ibm.com/catalog). From the catalog, select Compute and choose the server type - Bare Metal Server, Virtual Server, or Virtual Server for VPC (Virtual Private Cloud). For more information, see the [Virtual servers provisioning calculator](https://www.ibm.com/cloud/virtual-servers/calculator/).





 Can I change the configuration of a virtual server? 

After you provision a virtual server, you can upgrade or downgrade your server configuration at any time.
Network segmentation describes the approach to divide a network into multiple subnetworks. You can group apps and related data to be accessed by a specific group in your organization. Apps that run in one subnetwork can't see or access apps in another subnetwork. Network segmentation also limits the access that is provided to an insider or third-party software and can limit the range of malicious activities.

IBM Cloud Kubernetes Service provides IBM Cloud VLANs that ensure quality network performance and network isolation for worker nodes. A VLAN configures a group of worker nodes and pods as if they were attached to the same physical wire. VLANs are dedicated to your IBM Cloud account and not shared across IBM customers. In classic clusters, if you have multiple VLANs for your cluster, multiple subnets on the same VLAN, or a multizone classic cluster, you must enable a [Virtual Router Function (VRF)](https://cloud.ibm.com/docs/account?topic=account-vrf-service-endpointvrf) for your IBM Cloud infrastructure account so your worker nodes can communicate with each other on the private network. To enable VRF, see [Enabling VRF](https://cloud.ibm.com/docs/account?topic=account-vrf-service-endpointvrf). To check whether a VRF is already enabled, use the ibmcloud account show command. If you can't or don't want to enable VRF, enable [VLAN spanning](https://cloud.ibm.com/docs/vlans?topic=vlans-vlan-spanningvlan-spanning). To perform this action, you need the Network > Manage Network VLAN Spanning[infrastructure permission](https://cloud.ibm.com/docs/containers?topic=containers-access-credsinfra_access), or you can request the account owner to enable it.
* [Red Hat OpenShift for VMware](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-ocp_overview)
* [Veeam](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-veeamvm_overview)
* [VMware Aria Operations and VMware Aria Operations for Logs](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vrops_overview)
* [Zerto](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-addingzertodr)



Plan to migrate these services to new services on the VMware NSX-T™ environment.



 Understanding metadata 

Optional services can be decoupled from the vCenter Server® with NSX-V instance and reused with vCenter Server with NSX-V instance. However, it is important to understand the metadata that the service is using from vCenter Server.

Review the following information for Advanced Cross vCenter Server vMotion.



* MAC-Address stays the same.
* vCenter's MoRef ID for the VM changes. MoRef ID is a unique ID inside vCenter for every object. A MoRef ID is only unique within a vCenter Server.
* InstanceUUID stays the same. InstanceUUID is generated by the respective vCenter. However, it is preserved across vMotions that occur within the same SSO domain and across an SSO domain.







 Veeam 

It is possible to decouple your Veeam® instance from your vCenter Server with NSX-V instance for reuse with your vCenter Server with NSX-T instance. Configuration changes are required to the existing Veeam instance:



* Update instance point to the vCenter Server associated with the NSX-T environment
* Update the DNS setting on the Veeam Server, point to the AD/DNS servers.
[Troubleshooting networking](https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.networking.doc/GUID-217384C2-B361-471D-90C8-BC2676A0ECA6.html) 
 Network uplink redundancy degraded * Configure to send email one time when the Network Redundancy Degraded or Network Redundancy Degraded on DVPorts critical events occur. [Troubleshooting networking](https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.networking.doc/GUID-217384C2-B361-471D-90C8-BC2676A0ECA6.html) 
 VMKernel NIC not configured correctly * Configure to send email one time when the Invalid vmknic specified in /Migrate/VMknic critical event occurs. [Troubleshooting networking](https://docs.vmware.com/en/VMware-vSphere/6.7/com.vmware.vsphere.networking.doc/GUID-217384C2-B361-471D-90C8-BC2676A0ECA6.html) 
 Cannot connect to storage * Configure to send email one time when the Lost Storage Connectivity, Lost Storage Path Redundancy, Degraded Storage Path Redundancy, or Lost connection to NFS server critical events occur. [Identifying Fibre Channel, iSCSI, and NFS storage issues on ESX/ESXi hosts (1003659)g](https://kb.vmware.com/s/article/1003659) 
 Migration error * Configure to send email one time when the Cannot migrate VM, Migration error, Migration host error, Cannot relocate VM, or VM orphaned critical events occur.
The final step is to connect to the virtual machine through the Internet to validate the deployment and its network connectivity.

To connect to the virtual machine through the Internet:



1. You should be able to ping the public IP address public-ip-0 from your laptop or workstation, showing that the networking is complete and working.
2. You should be able to use RDP to connect to your Jump Server using the public IP address public-ip-0 and the username and password collected in the previous step.
3. You can then disable the FW rule dnat-to-jump created in the previous step by editing the rule and its State by sliding the State to Disabled (gray).







 Reference material 

Check the following VMware Cloud Director™ Tenant Portal Guides for more detailed information:



* [Managing Organization Virtual Data Center Networks](https://docs.vmware.com/en/VMware-Cloud-Director/10.4/VMware-Cloud-Director-Tenant-Portal-Guide/GUID-B208CDD2-5D46-4841-8F3C-BED9E4F27F07.html)
* [Managing NSX Edge Gateways](https://docs.vmware.com/en/VMware-Cloud-Director/10.4/VMware-Cloud-Director-Tenant-Portal-Guide/GUID-45C0FEDF-84F2-4487-8DB8-3BC281EB25CD.html)
* [Working with Virtual Machines](https://docs.vmware.com/en/VMware-Cloud-Director/10.4/VMware-Cloud-Director-Tenant-Portal-Guide/GUID-DF0C111D-B638-4EC3-B805-CC33994F8D53.html)
This service enables the collection, storage, and presentation of information about IP traffic flowing to and from network interfaces within a VPC. For more information, see [About IBM Cloud Flow Logs for VPC](https://cloud.ibm.com/docs/vpc?topic=vpc-flow-logs).





 16 July 2020 

New region
: The Tokyo region endpoint is now in service at https://jp-tok.iaas.cloud.ibm.com. For more information, see [Creating a VPC in a different region](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-a-vpc-in-a-different-region).

"Add to estimate" capability updates
: Added support for itemized virtual server pricing in the Add to estimate capability.





 03 July 2020 

Network load balancer (Beta)
: Network load balancers are available in a limited beta. Use network load balancers to distribute traffic among multiple server instances within the same region of your VPC. For more information, see [Load balancers overview](https://cloud.ibm.com/docs/vpc?topic=vpc-nlb-vs-elb) and [About network load balancers](https://cloud.ibm.com/docs/vpc?topic=vpc-network-load-balancers).

VPN for VPC update
: Access VPN monitoring metrics by using [Monitoring VPN for VPC metrics](https://cloud.ibm.com/docs/vpc?topic=vpc-sysdig-monitoring-metrics).







 June 2020 



 26 June 2020 

Dedicated hosts (Beta)
: In a limited beta, use dedicated hosts to carve out a single-tenant compute node. For more information, see [Creating dedicated hosts and groups (Beta)](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-dedicated-hosts-instances).





 19 June 2020 

Updated custom images information
Creating a private network endpoint 

VMware Shared now supports both public and private network endpoints. The public network endpoints that are provisioned by default are the five public IP addresses that are displayed in the VMware Shared virtual data center detail page. A private network endpoint allows a customer's IBM Cloud account devices or resources to connect to their virtual data centers by using the IBM Cloud private network. The Private network endpoint service is available and ready to use in all provisioned virtual data centers. After it is configured, the service allows your IBM Cloud account resources to connect to virtual machines (VMs) in your virtual data center over the IBM Cloud private network.

Connections to private network endpoints do not require public internet access. A private network endpoint provides a unique IP address that is accessible to you without a VPN connection. Private network endpoints support one-way traffic from IBM Cloud account resources to the VMs in your virtual data center.

Service charges are incurred only if you choose to use the service.



 Before you create a private network endpoint 



* If you have an IBM Cloud Direct Link on your account, you must establish a tunnel between the cross-connect router and the customer edge to have access to the virtual data center.
* You can order only one private network endpoint per single-zone virtual data centers.
* For multizone virtual data centers, two private network endpoints are ordered to correspond with each NSX Edge Service Gateway.
* If you want to change the device type of your private network endpoint, you must first delete the existing private network endpoint. Then, create a new private network endpoint with the new device type.
* You can simultaneously make resource updates to your virtual data center while you create or delete a private network endpoint.







 System settings 

When you create a private network endpoint, you must specify the following settings.



 Device type 

Select from the following device type options:



* Multitenant
* Dedicated with 1 Gbps uplinks
* Dedicated with 10 Gbps uplinks



You are not charged for the multitenant option.





 Allowlisted IP addresses and subnets 

Add the IP addresses or subnets that you want to have access to the private network endpoint.







 Monthly cost