vania-janet/multiturn-rag-retrieval-data huggingface dataset:
IBM Cloud infrastructure Service - Provision Windows VSI IBM Cloud infrastructure services network 10.0.0.0/14 Veeam Private primary subnet 8051 TCP EMC2 (Legato) Networker or Sun Solstice Backup 
 IBM Cloud infrastructure Service - Provision Windows VSI IBM Cloud infrastructure services network 10.200.0.0/14 Veeam Private primary subnet ICMP ICMP Ping 







 Ports for VMware Aria Operations and VMware Aria Operations for Logs 

The following table provides information about the VMware Aria Operations ports for vCenter Server with NSX-T instances.



Table 9. VMware Aria Operations ports for NSX-T instances

 Source Subnet, IP range Target Subnet, IP range Port Protocol Purpose Service 

 ESXi host Private primary subnet VMware Aria Operations New subnet ordered in private VLAN 514 UDP Remote syslog Syslog 
 vCenter Server Infrastructure VMs VMware Aria Operations New subnet ordered in private VLAN 514 UDP Remote syslog Syslog 
 VMware Aria Operations New subnet ordered in private VLAN Windows Active Directory Private primary subnet <br>Infrastructure VMs 53 TCP and UDP Use Windows DNS service DNS 
 VMware Aria Operations New subnet ordered in private VLAN vCenter Server Infrastructure VMs 443 TCP VMware Aria Operations configuration HTTPS 
 VMware Aria Operations New subnet ordered in private VLAN NSX-T Manager and NSX-T controllers Infrastructure VMs 443 TCP VMware Aria Operations configuration HTTPS 
 VMware Aria Operations New subnet ordered in private VLAN NSX-T Manager and NSX-T controllers Infrastructure VMs 1234 TCP NSX messaging 
 VMware Aria Operations New subnet ordered in private VLAN NSX-T Manager and NSX-T controllers Infrastructure VMs 1235 TCP NSX messaging 
 VMware Aria Operations New subnet ordered in private VLAN NSX-T virtual IP Infrastructure VMs 443 TCP VMware Aria Operations configuration HTTPS 
 NSX-T Manager and NSX-T controllers Infrastructure VMs VMware Aria Operations New subnet ordered in private VLAN 514 UDP Remote syslog Syslog
* NSX-T network super admin - responsible for deployment and operation of necessary shared network objects, such as T0 routers or edge gateways for the workloads.
* NSX-T network security admin - dedicated security admin that has responsibility that is limited to the firewall and security aspects of NSX-T.
* Tenant NSX-T admin - where wanted, scope that is limited to a function/application/business unit as applicable to manage resources with such limited scope. Would include deployment of T1 routers for example.







 Management cluster 

The vSphere administrator is responsible for the proper configuration, operation, and maintenance of the entire virtualized compute and storage infrastructure. The platform security administrator and network administrator share responsibility for the protection and operation of the network and security aspects of the management infrastructure. The network administrator role scope includes the configuration, operation, and maintenance of the software-defined network (NSX-T) which delivers network and security services to the SaaS consumer workloads.

The use of NSX-T as the software-defined networking provider eliminates reliance on the vCenter appliance for control of the SDN. Therefore, it enables a clear separation of duties and responsibilities for the networking and computes resources, and the storage between the platform network administrator and the vSphere administrator.

Both the vSphere administrator and network administrator create roles with the necessary and appropriate privilege levels to enable the SaaS application administrators to fulfill their required duties. The use of a zero trust model improves the security of the entire IBM Cloud for VMware Regulated Workloads implementation.





 Gateway cluster 

While the vSphere administrator holds responsibility for proper operation of the underlying ESXi hosts that form the gateway cluster, the VMware administrator has no access rights to the vSRX appliance nodes that run on them. There is no software-defined network applicable to the gateway cluster, so the NSX-T administrator has no access to the vSRX appliance nodes.

The security administrator is solely responsible for the configuration, operation, and maintenance of the vSRX gateway cluster. Only the security administrator has the right to implement configuration changes that impact the security stance of the IBM Cloud for VMware Regulated Workloads management layer.
Obtain HCX Connector virtual appliance OVA file.
2. From the vSphere Web Client, install the HCX Manager service virtual appliance in the on-premises vCenter that connects to IBM Cloud.
3. From the vSphere Web Client, register an IBM Cloud endpoint with the HCX plug-in. Registration establishes the one-to-one relationship between the on-premises HCX and the HCX instance on IBM Cloud.
4. Install and configure the service virtual appliances.
5. For each appliance installed on premises, the installer provisions a corresponding service virtual appliance in the target IBM Cloud.
6. After the installation, HCX Manager controls both local and remote service virtual appliances. In the IBM Cloud, HCX manages the provisioned Software-Defined WAN components as a service.





 Deployment component performance considerations 

Architecture planning includes the VMs to be migrated, the networks that are used for VM traffic, and the networks to be extended.

The following settings are the maximum and minimum values for the deployment components:



* vSphere vCenter. The HCX Manager appliance must be installed on the vCenter Server that requires hybrid services. You can have one HCX deployment per vCenter only. This restriction applies to linked mode. The HCX management appliance is only installed in the primary vCenter. HCX supports up to five registered vCenters in linked mode.
* Cloud registrations. The maximum number of cloud endpoints is ten. To find the number of endpoints, Hybrid Cloud Services tracks vCenter connections to the cloud.







 HCX virtual appliances 

The installation package is an OVA file that contains the Hybrid Cloud Services plug-in. This Hybrid Cloud Services management appliance is installed and configured and then used to configure the service appliance VMs:



* HCX Cloud and HCX Connector
* HCX-IX Interconnect Appliance (HCX-IX)
* HCX WAN Optimization Appliance (HCX-WO)
* HCX Network Extension Virtual Appliance (HCX-NE)







 HCX Connector
Red Hat activation key The activation key that you use to register the Red Hat virtual machine (VM). 





 Opening a support ticket for additional IP addresses or subnet 

To request five additional public IP addresses or an entire subnet for your virtual data center, open an IBM Support ticket by following the steps in [Contacting IBM Support](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-trbl_support).

Include the following details in your support ticket:



* Virtual data center region and location
* Organization ID
* Virtual data center name
* Number of additional IP addresses required
* Specify whether you plan to use the additional IP addresses by using Network Address Translate through the virtual data center Edge Services Gateway or by directly assigning the IP address to a VM.







 Viewing virtual data center resource reservation details 

Under Resource reservation, view the total reserved virtual CPU (vCPU) and RAM for the virtual data center.



Table 3. Virtual data center resource reservation details

 Resource Description 

 vCPU limit The limit or reserved amount of vCPU that can be used at any time by the virtual data center. 
 RAM limit The limit or reserved amount of memory that can be used at any time by the virtual data center. 









 Viewing virtual data center recommended services details 

Click the Services tab to view the virtual data center recommended services details.

For more information about recommended services details, see [Managing Veeam for VMware Shared virtual data centers](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-shared_veeam) and [Managing Zerto for VMware Shared virtual data centers](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-shared_zerto-portal).





 Related links 



* [Creating a private network endpoint](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-shared_creating-endpoints)
In this case, comment these lines out in your terraform.tfvars.

If you change the authentication method, the provider block in the code needs to changed to use a different authentication method. Currently only username and password method is supported in IBM Cloud® for VMware as a Service - single tenant instance.
2. Set a common name prefix to identify and separate your virtual data center networks, virtual machines and so on.

 Note. Use a common name prefix for each item.

item_name_prefix = "demo"
3. Define DNS servers for the virtual machines.

You can use IBM Cloud Public DNS server in your virtual machines, or you can use your own.

 Note. IBM Cloud DNS servers listed here.
 You may also use your own here.

dns_servers = ["161.26.1.10","161.26.1.11"]

When using your own DNS servers here, make sure you have network connectivity to reach these.
4. Define virtual data center networks.

When creating virtual data center networks, use the map variable vdc_networks to define these and their IP pools.

 Note. Create virtual data center networks of type routed or
 isolated. You can define one static_ip_pooland one
 dhcp_ip_pool for each.

vdc_networks = {
application-network-1 = {
description = "Application network 1"
type = "routed"
subnet = {
cidr = "172.26.1.0/24"
prefix_length = 24
gateway = "172.26.1.1"
static_ip_pool = {
start_address = "172.26.1.10"
end_address = "172.26.1.100"
}
dhcp_ip_pool = {
start_address = "172.26.1.101"
end_address = "172.26.1.199"
}
}
},
db-network-1 = {
description = "DB network 1"
type = "routed"
The HCX-IX Interconnect Appliance also incorporates vSphere replication technology to perform bidirectional migration.





 HCX WAN Optimization Appliance 

HCX also provides software-defined WAN Optimization. The HCX WAN Optimization appliance is a highly recommended component that performs WAN conditioning to reduce effects of latency. It also incorporates Forward Error Correction to negate packet loss scenarios, and deduplication of redundant traffic patterns. Altogether, these reduce bandwidth use and ensure the best use of available network capacity to expedite data transfer to and from IBM Cloud.

VM migration relies on the combination of HCX-IX Interconnect Appliance and HCX WAN Optimization appliance to achieve unparalleled mobility between vSphere on-premises and IBM Cloud.





 HCX Network Extension Virtual Appliance 

The Network Extension Service is provided by the HCX Network Extension Virtual Appliance. It extends a Layer 2 network from the on-premises vSphere data center to IBM Cloud and enables seamless migration between the data center and the cloud. The HCX Network Extension Virtual Appliance is required to stretch the on-premises network to IBM Cloud.

The HCX Network Extension Virtual Appliance has two interfaces:



* Internal trunk interface - Handles VM traffic on-premises for the extended networks by using a translational bridge mapping to a corresponding stretched network in IBM Cloud.
* Uplink interface - HCX uses this interface to send encapsulated overlay traffic to and from IBM Cloud. Application data travels through this interface.







 IP address requirements 

To deploy the HCX, the proper number of IP addresses must be available both on-premises and in the target IBM Cloud.



* vMotion address Maintaining a separate network for vMotion is a common practice in the on-premises data center. The Cloud Gateway must have access to the vMotion network. If it does not, an extra IP address is needed to communicate with the vMotion network.
* On-premises



* One IP address for the HCX Connector appliance.
* One for each HCX-IX Interconnect Appliance, add one for a separate vMotion network (if applicable).
See [platform as a service](https://cloud.ibm.com/docs/overview?topic=overview-glossaryx2029786).





 paravirtualized mode 

A lightweight virtualization technique. While in paravirtualized mode, a virtual machine does not require virtualization extensions from the host computer, thus allowing virtualization on hardware systems that do not support hardware-assisted virtualization.





 parent image 

An image that provides a base for another image. For example, Ubuntu Linux is the parent image of the IBM Liberty image. See also [image](https://cloud.ibm.com/docs/overview?topic=overview-glossaryx2024928), [base image](https://cloud.ibm.com/docs/overview?topic=overview-glossaryx5366487).





 part of speech (POS) 

A grammatical category, such as noun or verb, based on the syntactic function of a lexical item.





 path 

The route through which users access REST APIs. A path consists of one or more HTTP operations such as GET or POST.





 payload logging 

The capture of payload data and deployment output to monitor ongoing health of AI in business applications.





 payment method 

The method by which a client pays an invoice, such as credit card, check, or wire transfer.





 PEAR 

See [processing engine archive](https://cloud.ibm.com/docs/overview?topic=overview-glossaryx2959092).





 peer 

A blockchain network entity that maintains a ledger with an installed chaincode for performing read and write operations on the ledger. A peer is owned and maintained by an organization.





 performance 

The measurement of a Watson system in terms of accuracy, precision, and recall, for example, when answering questions, discovering relationships, or annotating text.





 plan 

The packaging construct by which APIs are made available to consumers. A plan makes available a collection of resources or operations from one or more APIs, and is published to communities of application developers.





 platform as a service (PaaS)
Creating a virtual data center in a VMware as a Service using the VMware Cloud Director Console 

This tutorial may incur costs. Use the [Cost Estimator](https://cloud.ibm.com/estimator/review) to generate a cost estimate based on your projected usage.

This tutorial is to demonstrate the basic steps to operationalize an IBM Cloud® for VMware as a Service – single tenant instance after initial instance provisioning. This tutorial should take about 30-60 minutes to complete and assumes that [IBM Cloud® for VMware as a Service – single tenant instance](https://cloud.ibm.com/docs/vmware-service?topic=vmware-service-tenant-ordering) and [a virtual data center (VDC)](https://cloud.ibm.com/docs/vmware-service?topic=vmware-service-vdc-adding) have already been provisioned.



 Objectives 

In this tutorial, you will learn:



* How to create virtual data center (VDC) networks inside your virtual data center,
* How to create virtual machines and attach them to your virtual data center network, and
* How to configure network address translation (NAT) and firewall (FW) rules on your virtual data center edge gateway.



The following diagram presents an overview of the solution to be deployed.

Zoom

![Architecture](https://cloud.ibm.com/docs-content/v1/content/f84e2238288b7f0355715a4c355609ce7ac48fb0/solution-tutorials/images/solution66-vmware-as-a-service/vmwaas-example-diagrams-ui-vmwaas-vdc-tutorial.svg)

Figure 1. Architecture diagram of the tutorial

This tutorial is divided into the following steps:



1.
Modifying a private network endpoint for a virtual data center 

You can add or remove allow listed IP addresses or subnets for a private network endpoint.



 Procedure to add an IP address or subnet for a private network endpoint 



1. From the IBM Cloud® for VMware Solutions console, click Resources > VMware Shared from the left navigation pane.
2. In the VMware Shared table, expand the site and click a virtual data center name.
3. Click the Services tab.
4. From the Private network endpoint details pane, click the Edit icon ![Edit icon](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/icons/edit-tagging.svg) next to Allow listed IPs and subnets.
5. Enter the IP address in the New IP field and click Add.
6. When all modifications are complete, click Update.







 Procedure to delete an IP address or subnet from a private network endpoint 



1. From the IBM Cloud for VMware Solutions console, click Resources > VMware Shared from the left navigation pane.
2. In the VMware Shared table, expand the site and click a virtual data center name.
3. Click the Services tab.
4. From the Private network endpoint details pane, click the Edit icon ![Edit icon](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/icons/edit-tagging.svg) next to Allow listed IPs and subnets.
5. Locate the IP address that you want to delete and click the Delete icon ![Delete icon](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/icons/delete.svg).
6. Select vApp Network Type.
7. Complete the Name and Gateway CIDR fields. For example, Web and 192.168.33.1/24.
8. (Optional) Provide the DNS information.
9. Leave the Static IP Pools section blank.
10. Set the slider to Connect to an organization VDC network.
11. Click Add.



For more information, see [Working with networks in a vApp](https://docs.vmware.com/en/VMware-Cloud-Director/10.1/VMware-Cloud-Director-Tenant-Portal-Guide/GUID-FCBC791B-3183-4CD9-A194-856E98CC32D3.html).









 Configuring a private network endpoint 

Every private network endpoint comes configured with one private network IP address that can be used to configure your virtual data center.



 Prerequisites for configuring a private network endpoint 



* Review [Getting Started with VMware Shared](https://cloud.ibm.com/docs/solution-tutorials?topic=solution-tutorials-vmware-solutions-shared-getting-started).
* You must have a running VM.
* The VM must be connected to a routed Organization virtual data center network. For more information, see [Creating a routed Organization virtual data center network](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-shared_vcd-ops-guideshared_vcd-ops-guide-routed-organization) and [Connect the VMs to the network](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-shared_vcd-ops-guideshared_vcd-ops-guide-connect-vm).
* You must have virtual routing and forwarding and service endpoints that are enabled on the account that the allow listed IP or subnet belong to.
On the VDC details page, click VMware Cloud Director Console to access the console.
5. Use the admin username and password to log in to the VMware Cloud Director Console for the first time.
6. After the admin is logged in to the VMware Cloud Director Console, you can create extra users who have roles that allow them to access the VMware Cloud Director Console.



Next, you will create the following virtual data center networks:



Virtual data center networks

 Network type Name IP subnet 

 routed network net-application 192.168.100.1/24 
 routed network net-db 192.168.101.1/24 
 isolated net-isolated-db 192.168.102.1/24 



Routed virtual data center networks are attached to the edge gateway while an isolated virtual data center network is a standalone network without any platform provided routing capabilities. You can create more networks based on your needs by following the same logic and steps.

The recommendation is to use RFC 1918 addresses, for example IP subnets from the 10.0.0.0/8, 172.16.0.0/12 or 192.168.0.0/16 ranges.

To create a virtual data center network:



1. In the top menu navigation, click on Networking. Then click on New to create a new virtual data center network. New Organization VDC Network wizard will appear.
2. Select the Organization Virtual Data Center (Default) and then select the VDC you want to deploy the new network to. In most cases there will be a single VDC. Click Next to continue.
3. Select network type as Routed (default) for routed networks net-application and net-db and select Isolated for the isolated network net-isolated-db. Click Next to continue.
4. For Edge Connection, select the edge that was provisioned for you and leave all other settings as default. Isolated networks do not have a gateway connection. Click Next to continue.
5. Provide a name and the gateway CIDR for the new network. CIDR includes the IP address of the gateway and the network mask length, e.g. 192.168.100.1/24.
Port access requirements for VMware HCX 

VMware® HCX™ must traverse the public internet and private lines, and connect to data center components, such as networks, switches, and port groups.

The following table lists ports that must be opened so that Hybrid Cloud Services virtual appliances can install successfully. Both the vSphere environment and the IBM Cloud® environment must allow Network Time Protocol (NTP) clock synchronization among vSphere on-premises devices and the IBM Cloud devices. UDP port 123 must be accessible to Hybrid Cloud Services virtual appliances and networks. Installed NTP Servers can be specified when the Hybrid Cloud Services Appliance is installed.



Table 1. Port access requirements

 Source Target Port Protocol Purpose Services 

 HCX Customer DNS 53 TCP/UDP Name resolution DNS 
 HCX NSX LB in IBM Cloud 443 TCP Registration service HTTPS 
 HCX vCenter in IBM Cloud 443 TCP HCX REST service HTTPS 
 HCX PSC in IBM Cloud 443 TCP HCX REST service HTTPS 
 HCX connect.hcx.vmware.com 443 TCP Registration service HTTPS 
 Web Browser HCX 9443 TCP HCX Virtual Appliance Management Interface for HCX system configuration HTTPS 
 Admin network HCX 22 SSH Administrator SSH access to Hybrid Cloud Services SSH 
 HCX ESXi Hosts 902 TCP Send management and provisioning instructions from HCX to ESXi Hosts in IBM Cloud. Internal 
 HCX vCenter SSO Server 7444 TCP vSphere Lookup Service 
 HCX NTP Servers 123 UDP Time synchronization 
 HCX Syslog User configured Connection between HCX (the client) and the Syslog server. Values for the Syslog port and protocol are specified in the vSphere Web Client. For example, port 514 for UDP protocol. 
 HCX HCX-IX 8123 TCP Send host-based replication service instructions to the HCX-IX. HTTP 
 HCX HCX-IX 9443 TCP Send management instructions to the local HCX-IX by using the REST API. HTTP <br>HTTPS