vania-janet/multiturn-rag-retrieval-data huggingface dataset:
All IBM Cloud data centers and PoPs are connected by the private network backbone. This private network is separate from the public network, and it enables connectivity to services in IBM Cloud data centers around the world. Moving data between IBM Cloud data centers is done through multiple 10 Gbps or 40 Gbps connections to the private network.

Similar to the public network, the private network is multitiered in that servers and other infrastructure components are connected to aggregated back-end customer switches (BCS). These aggregated switches are attached to a pair of separate back-end customer routers (BCR) for L3 networking. The private network also supports the ability to use jumbo frames (MTU 9000) for physical host connections.





 Management network 

In addition to the public and private networks, each IBM Cloud server is connected for management to the private primary network subnet. This connection allows Intelligent Platform Management Interface (IPMI) access to the server independently of its CPU, firmware, and operating system, for maintenance and administration purposes.





 Primary and portable IP blocks 

IBM Cloud allocates two types of IP addresses to be used within the IBM Cloud infrastructure:



* Primary IP addresses are assigned to devices, bare metal, and virtual servers that are provisioned by IBM Cloud. Do not manually assign any IP addresses in these blocks.
* Portable IP addresses are provided for you to assign and manage as needed. The IBM Cloud for VMware Regulated Workloads automation provisions several portable IP ranges for its use. Use only the portable IP address ranges that are assigned to specific NSX-T components and specified for SaaS provider use.



Primary or portable IP addresses can be made routable to any VLAN within your account when the account is configured as a Virtual Routing and Forwarding (VRF) account.





 Virtual routing and forwarding 

The IBM Cloud infrastructure account must be configured as a Virtual Routing and Forwarding (VRF) account, which enables automatic global routing between subnet IP blocks. All accounts with Direct-Link connections must be converted to, or created as, a VRF account.

As various connectivity options and network routing options require that the IBM Cloud account is in VRF mode, it is recommended that the account is in VRF mode before you provision the IBM Cloud for VMware Regulated Workloads.
As the successor to the core product SAP ECC, SAP S/4HANA was presented as the intelligent ERP system of the new generation. Thanks to modern technologies, the Software as Service (SaaS) version is designed to help companies standardize processes and make the leap to digitalization.

While previous SAP ERP solutions support the most common databases, SAP S/4HANA uses exclusively the SAP HANA in-memory database developed by SAP. This in-memory database offers users the greatest technical benefit and they benefit from increased performance. The "S" in S/4HANA stands for "simple", while the "4" refers to the generation sequence. Compared to the SAP core product SAP ECC, which is still used in most companies, SAP S/4HANA offers many innovative functions that revolutionize the system landscape from the ground up. As SAP plans to discontinue the mainstream maintenance of its existing ERP solutions by 2027, many SAP ECC users are already considering a migration to SAP S/4HANA





 What is created 

The scripts work in two phases. The first phase automates creating the resources for the VPC provisioning process in an existing VPC created when you deployed the bastion VSI. The second phase creates the SAP architecture in a distributed environment SAP S/4HANA App server on a distinct VSI VPC machine and SAP HANA DB on a dedicated server type VSI VPC box machine. For more information about this architecture, see [SAP NetWeaver 7.x with SAP HANA IBM Cloud® VPC](https://cloud.ibm.com/docs/sap?topic=sap-sap-refarch-nw-hana&interface=ui).

During the first phase, the VPC is provisioned with these components:



* 1 VPC where the virtual server instances are provisioned
* 1 security group. The rules for this security group allow:



* Inbound DNS (port 53) and
* Inbound SSH (TCP port 22) connections to your virtual server instance
* All outbound traffic from the virtual server instance



* 1 subnet to enable networking in your VPC
* 2 X virtual server instances with SAP certified storage and network configurations
IBM Cloud is responsible for management of servers, network, storage, virtualization, middleware, and runtime, which ensures good performance and high availability. Customers are responsible for the management of data and applications, specifically encryption keys that are stored in Hyper Protect Crypto Services and user applications that use keys or cryptographic functions for cryptographic operations.
* How is this service different from IBM Cloud HSM?

IBM has an IaaS IBM Cloud HSM service, which is different from the Hyper Protect Crypto Services. IBM Cloud HSM is FIPS 140-2 Level 3 compliant. Hyper Protect Crypto Services provides a managed HSM service where no special skills are needed to manage the HSM other than loading of the keys. Hyper Protect Crypto Services is the only cloud service that provides HSMs that are built on FIPS 140-2 Level 4 certified hardware and that allow users to have control of the master key.
* How is Hyper Protect Crypto Services different from Key Protect?

IBM Key Protect for IBM Cloud is a shared multi-tenant key management service that supports the Bring Your Own Key (BYOK) capability. The service is built on FIPS 140-2 Level 3 certified HSMs, which are managed by IBM.

Hyper Protect Crypto Services is a single-tenant key management service and cloud HSM for you to fully manage your encryption keys and to perform cryptographic operations. This service is built on FIPS 140-2 Level 4 certified HSMs and supports the Keep Your Own Key (KYOK) capability. You can take the ownership to ensure your full control of the entire key hierarchy with no access even from IBM Cloud administrators. Hyper Protect Crypto Services also supports industry standards such as Public-Key Cryptography Standards #11 (PKCS #11) for cryptographic operations like digital signing and Secure Sockets Layer (SSL) offloading.
* How is Keep Your Own Key different from Bring Your Own Key?

Bring Your Own Key (BYOK) is a way for you to use your own keys to encrypt data. The key management services that provide BYOK are typically multi-tenant services. With these services, you can import your encryption keys from the on-premises hardware security modules (HSM) and then manage the keys.
* You must select On from the Shareable field when you create storage volumes for the virtual severs that are part of the PowerHA SystemMirror cluster.
* By using the Power Systems Virtual Server, you do not have access to the HMC, VIOS, and the host system. Therefore, any PowerHA SystemMirror functions that require access to these capabilities, such as Resource Optimized High Availability (ROHA) and Active Node Halt Policy (ANHP), are not available. However, PowerHA SystemMirror 7.2.6 SP1 or later versions support Resource Optimized High Availability (ROHA) functions. For more information on configuring and using ROHA with Power Systems Virtual Server, see [Resource Optimized High Availability in Cloud](https://www.ibm.com/docs/en/powerha-aix/7.2?topic=administering-resources-optimized-high-availability-in-cloud)



Licenses that are purchased outside a subscription model license are not eligible to be used in the Power Systems Virtual Server.





 Disaster recovery mechanisms 

You can implement disaster recovery mechanism between two AIX virtual server instances in separate IBM Cloud data centers by using GLVM replication. For a complete tutorial, see [AIX Disaster Recovery with IBM Power Systems Virtual Servers](https://cloud.ibm.com/media/docs/downloads/power-iaas-tutorials/PowerVS_AIX_DR_Tutorial_v1.pdf). For information about Transmission Control Protocol (TCP) tuning to improve wide area network (WAN) connection performance between AIX Virtual Machines, see [this support page](https://www.ibm.com/support/pages/node/6410510).

You can implement disaster recovery mechanisms between two IBM i virtual server instances by using PowerHA geographic mirroring. For a complete tutorial, see [IBM i Disaster Recovery with IBM Power Systems Virtual Servers](https://cloud.ibm.com/media/docs/downloads/power-iaas-tutorials/PowerVS_IBMi_DR_Tutorial_v1.pdf).





 Business Continuity through backup and restore 

Your Power Systems Virtual Server configuration and data are not backed up automatically.
* Subnet to assign to this network interface into



During virtual server provisioning, each virtual server requires a Primary network interface. If you are using a Floating IP, by default it is attached to the primary network interface.

By default during provisioning of a virtual server, the primary network interface is already added with the default Security Group. After a virtual server is created, the network interface is assigned its own Private IP from the selected Subnet range.



 Throughput of network interfaces 

Every virtual server profile has a maximum network bandwidth of 2 Gbps per vCPU, with a cap of 80 Gbps. Network bandwidth is distributed evenly across network interfaces. Each network interface has a cap of 16 Gbps that might limit the overall performance. You might need to attach multiple network interfaces to your virtual server instance to optimize network performance.

For example, if you choose a profile with 16 vCPU, the network cap for the profile is 32 Gbps. If you have just one network interface, the maximum network performance is 16 Gbps due to the network interface cap. You need to attach two network interfaces (16 Gbps each) to reach the profile cap of 32 Gbps.

For more information, see [VPC - Network performance notes for profiles](https://cloud.ibm.com/docs/vpc?topic=vpc-profilesnetwork-perf-notes-for-profiles).





 Multiple network interfaces 

You can add up to 5 network interfaces (vNIC) to your virtual server instance, each is assigned with a single unique IP address from the selected Subnet range, which provides multiple IP addresses for your virtual server instance.

Each of the multiple networks interfaces attached to the virtual server are able to use the same Subnet or different Subnets. However, these subnets must be within the same Zone of the VPC.

You can create a new network interface during provisioning or after the virtual server is running.

After a new network interface is created, it is immediately available to the OS shown by using ip link.

If your virtual server instance is running when you complete the following steps to add the network interface, then it remains in DOWN mode and you must configure the network interface for the instance.
The following information is a summary of [Configuring connectivity to Power Systems Virtual Server](https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-configuring-power) and [ Configuring and adding a private network subnet](https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-configuring-subnet).

The Virtual LAN (VLAN) on the IBM Power Systems Infrastructure network, provides an enterprise-grade private network with full isolation and security. Each VLAN is Public or Private, and is assigned to a specific data center for a specific IBM Cloud Account.

Each VLAN is associated with a single Subnet, for example:



* Public VLAN (only one per region)



* Public Subnet



* Private VLAN



* Private Subnet





A Public Subnet is the quickest and simplest way to connect to a IBM Power Systems Virtual Server instance. The public network is protected by a firewall and only the following network protocols are allowed:



* SSH (port 22)
* HTTPS (port 443)
* Ping (ICMP)
* IBM i 5250 console emulation with SSL (port 992)



For the public network, other ports are blocked and can be routed through SSH.

A Private Subnet is required for the connection of your virtual instances with systems outside of the IBM data centers and for communication between multiple instances in an SAP three-tier system. This subnet is an internal network that can be used to connect individual IBM Power Systems Virtual Servers with each other.

If you want to separate different types of network traffic in your landscape, you can order more subnets (and their respective VLANs).

Keep in mind that the additional VLANs and subnets lead to traffic segregation, not increased performance; the increased performance is gained when additional VLANs and Subnets are associated to a host. When multiple network interfaces are used, two performance increases are possible depending on the use case:



* Bonding of the network interfaces, creating a network path with the network throughput of both interfaces
[Connecting Power virtual server environments](https://cloud.ibm.com/docs-content/v1/content/1d36273917990fbf48078805e201d2e85e2fcb27/power-iaas/images/network-connect-to-pvs2pvs.svg)

Figure 4. Connecting Power virtual server environments

IBM Cloud Connect is a managed network service that uses Megaport services. This service is available only in the United States. You can also use Megaport to connect your on-premises network to Power Systems Virtual Server directly.

The key features of this Connect-to-classic topology are as follows:



1. Define the IP address schema of your Power Systems Virtual Server subnets in your Power Systems Virtual Server environment. Your Power Systems Virtual Server instances are hosted on these subnets. Ensure that you do not overlap these subnets with your IBM Cloud classic private subnets or the IP addressing schema that is used for the services network. For instructions, see [Configuring and adding a private network subnet](https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-configuring-subnet).
2. Procure the [Megaport](https://www.megaport.com/) VXC connections to connect your on-premises (remote) networks to the Megaport network.



* Open an IBM Support case against Power Systems Virtual Server to receive a service ID or a virtual cross-connect (VxC) identifier from IBM.
* Engage with Megaport to procure the connection (VxC) to Power Systems Virtual Server Port @ Megaport. When connecting a Power IaaS Location-1 to Power IaaS Location-2 by using Megaport, you might need a [Megaport Cloud Router (MCR)](https://docs.megaport.com/mcr/creating-mcr/) unless network connectivity is through a customer router. Consult a Direct Link Connect or Megaport representative for specific network requirements.



3.
IBM Power Virtual Server certified profiles for SAP HANA 

When you provision IBM Power Virtual Servers, you can select from the following families of profiles: [Small](https://cloud.ibm.com/docs/sap?topic=sap-hana-iaas-offerings-profiles-power-vssmall), [Balanced](https://cloud.ibm.com/docs/sap?topic=sap-hana-iaas-offerings-profiles-power-vsbalanced), [Compute Intensive](https://cloud.ibm.com/docs/sap?topic=sap-hana-iaas-offerings-profiles-power-vscomputeintensive), [Ultra Memory](https://cloud.ibm.com/docs/sap?topic=sap-hana-iaas-offerings-profiles-power-vsumemory), and [High Memory](https://cloud.ibm.com/docs/sap?topic=sap-hana-iaas-offerings-profiles-power-vshmemory).

Certified profiles for SAP HANA are a complementary offering from IBM Power Systems, with low latency access to IBM Cloud services

A profile is a combination of instance attributes, such as the number of vCPUs, amount of RAM, and network bandwidth. The attributes define the size and capabilities of the virtual server instance that is provisioned. You can select the most recently used profile or click View All Profiles to choose the profile that best fits your needs.



 Profile families 

The published names are subject to change.

The following section provides an overview of the SAP-certified profiles with IBM Power Virtual Servers and available profile families.



 Families Description 

 [Custom](https://cloud.ibm.com/docs/sap?topic=sap-hana-iaas-offerings-profiles-power-vscustom) Custom profiles are for nonproduct development for testing or development use only. These profiles are not intended for production deployments and are not supported or certified for SAP production. 
 [Small](https://cloud.ibm.com/docs/sap?topic=sap-hana-iaas-offerings-profiles-power-vssmall) Small profiles are best for balanced workloads that require less CPU and storage consumption.
Creating a virtual machine with VMware vSphere 



1.  Right-click your host node IP address in the Inventory pane of the vSphere Client.
2.  In the configuration window, select Custom.
3.  Give the virtual machine an appropriate name and click Next.
4.  Select the storage location for virtual machine files and click Next. The Virtual machine version menu gives you the option to use different cluster types.
5.  Select an Operating system.
6.  Set the number of virtual processors (on the CPUs page) and click Next. You can change the number of CPUs later if the resources are available.
7.  Set the amount of memory that you want for the virtual machine. Click Next. You can change the amount of memory later if the resources are available.
8.  In the network section, you need to connect the two NICs. NIC 1 is for the Private Network and NIC 2 is for the Public Network. The adapter type ID “Flexible”. Make sure that the “Connect at Power On” checkbox is selected.
9.  Leave the SCSI Controller screen to the default “LSI Logic Parallel”. On the Select a Disk screen, select Create a new virtual disk. Keep the default settings on the Advanced options screen and the Ready to complete screen. Your new virtual machine is now created. To begin loading your installation media, click the server name from the inventory list and click Edit virtual machine settings under Basic tasks.
10. With CD/DVD Drive 1 selected, select Connect at power under Device Status. To specify an ISO file that is located in your data store, click Browse.



*  The ISO files that are uploaded to the default Storage1 data store are selectable here. You also see folders that contain the configuration and log files (set up during Step 3 data store section of the Create a new virtual machine process) for all the server virtual machines.



11. After you select your ISO image, you are ready to install the respective OS.





*  After your Guest VM is running, if supported, install [VMWare® Tools](https://kb.vmware.com/s/article/1014294).
*  For more information about networking instructions, see [Setting up a virtual machine network](https://cloud.ibm.com/docs/virtualization?topic=virtualization-setting-up-a-virtual-machine-network).
* How does the application port function if I set a port range for the network load balancer listener instead of a single port?

If you set a port range for the network load balancer listener, then the instance group's application port will only be used for checking the health status of back-end members if you did not set a health check port for the pool.
* How do I know which load balancer offerings support auto scaling?

Not all network load balancer offerings support integration with instance groups. Load balancers support auto scaling if the instance_groups_supported property of the [load balancer detail](https://cloud.ibm.com/apidocs/vpcget-load-balancer) is true.
* What elements do I need to create a dedicated host?

Dedicated hosts in IBM Cloud VPC are created as part of a dedicated group. When you use IBM Cloud console to create a dedicated host, you create an initial dedicated group as part of the dedicated host provisioning process. If you are using the IBM Cloud CLI to create a dedicated host, you must first create a dedicated group. For more information, see [Creating dedicated hosts and groups](https://cloud.ibm.com/docs/vpc?topic=vpc-creating-dedicated-hosts-instances).
* How much am I charged for a dedicated host?

When you create a dedicated host, you are billed by the usage of the host on an hourly basis. You are not billed for the vCPU and RAM associated with instances that are running on the host.
* Why can I create only one dedicated host per region?

When you provision dedicated hosts, the vCPU associated with your dedicated hosts counts toward the total vCPU for virtual server instances per region. The standard quota for virtual servers vCPU is 200. The dedicated host profile uses 152 vCPUs. To increase your vCPU quota, [contact Support](https://cloud.ibm.com/docs/get-support?topic=get-support-using-avatar). For more information, see [Quotas](https://cloud.ibm.com/docs/vpc?topic=vpc-quotasvpcquotas).
Additional attributes 

These attributes are available to segment one or more attributes as described in the preceding table. See the individual metrics for segmentation options.



Table 22: Available attributes for segmenting one or more attributes

 Attribute Attribute name Attribute description 

 Disk name of the volume ibm_is_disk_name Disk name of the volume that is attached to the virtual server instance, corresponds to output of 'ls -l /dev/disk/by-id' 
 IBM IS Generation, 1 or 2 ibm_is_generation IBM IS Generation (1 for Gen. 1 (Classic) or 2 for Gen. 2 (VPC) ) 
 MAC address of the network interface ibm_is_mac_address MAC address of the corresponding network interface that is attached to the virtual server instance 
 Network interface index ibm_is_nic_index Index of the network interface that is attached to the virtual server, starting from 0 
 Resource name ibm_resource_name Resource name - for example, the virtual server instance name 
 ID of the volume ibm_is_volume_id UUID of storage volume that is attached to the virtual server instance 
 Virtual CPU index ibm_is_vcpu_index Index of the virtual CPU within the virtual server instance, starting from 0
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 

The HCX Connector plug-in is deployed on-premises only. It manages the service virtual appliances for the SD-WAN. The HCX Connector virtual appliance is an extension to the source vCenter and is deployed as a VM. This appliance’s file structure contains all the hybrid service virtual appliances. The HCX Connector oversees the deployment and configuration of the HCX-IX, the HCX-NE, and HCX-WO virtual appliance both on-premises and in the cloud.

The virtual appliance can be installed with either thin or thick provisioning for the hard disk drive. By default, hard disk drives for the service virtual appliances are thinly provisioned.

After the service, virtual appliance configuration, and deployment are done, log in to this VM to use the Hybrid Cloud Services management portal.





 HCX-IX Interconnect Appliance 

The HCX-IX Interconnect Appliance establishes and maintains a secure channel between vSphere and the IBM Cloud.

HCX uses strong encryption to bootstrap a site-to-site connection to IBM Cloud. The secure channel between vSphere and IBM Cloud achieves multitenancy for vSphere protocols that are not tenant aware, and to prevent networking "middle mile" security problems.

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.