vania-janet/multiturn-rag-retrieval-data huggingface dataset:
See [User accounts](https://cloud.ibm.com/docs/vmware-service?topic=vmware-service-getting-startedgetting-started-user-accts).
* What if I have issues with VMware as a Service?

If you need assistance with VMware as a Service, contact IBM Support through one of the support channels. For more information, see [Contacting IBM Support](https://cloud.ibm.com/docs/vmware-service?topic=vmware-service-support).



VMware for Classic



* How is VMware licensed?

When you deploy ESX through the IBM Cloud® catalog, VMware Service Provider Program licensing (VSPP) automatically enables. On deployment, a default user 'ibmvmadmin' is added to the ESX server for data collection. Do not delete this default user. VSPP charges for RAM that is reserved and used for all “powered on” virtual machines (not “per socket” like a standard host license).
* How is VMware vSphere licensed?

When you deploy vSphere, VMware Service Provider Program licensing (VSPP) automatically enables. On deployment, a default user 'ibmvmadmin' is added to the Host for vSphere administration and integration services.
* What license level is enabled when you deploy vSphere from the IBM Cloud® catalog?

Enterprise Plus, the highest vSphere license level.
* Can I create an isolated private VMware cloud?

Yes, you can deploy bare metal systems and install any supported hypervisor (including VMware ESX) on these hosts. You can also deploy virtual machines by using the native management tools. By default, systems are deployed in VLANs for segmentation and networking components (such as gateways, routers, and firewalls) and are used to create almost any topology.
* Can I deploy VMware components directly from the IBM Cloud® catalog?

Yes, you have two options:



1. Select and deploy the ESX hypervisor automatically with a monthly bare metal system.
Services for VMware as a Service 

The Veeam® Backup and Replication service is preinstalled and included by default for your instance order. You can remove the service from your instance order. Service charges are incurred only if you choose to include the service in your order.





 Related links 



* [FAQ](https://cloud.ibm.com/docs/vmware-service?topic=vmware-service-faq-general)
* [Managing Veeam for VMware as a Service](https://cloud.ibm.com/docs/vmware-service?topic=vmware-service-tenant-veeam)
Make sure that ACL rules are in place to allow management traffic and VPN tunnel traffic. For more information, see [Configuring ACLs and security groups for use with VPN](https://cloud.ibm.com/docs/vpc?topic=vpc-acls-security-groups-vpn).





 What should I do if I am using ACLs on the subnets that must communicate with an on-premises private network? 

Make sure that ACL rules are in place to allow traffic between virtual server instances in your VPC and your on-premises private network. For more information, see [Configuring ACLs and security groups for use with VPN](https://cloud.ibm.com/docs/vpc?topic=vpc-acls-security-groups-vpn).





 Does VPN for VPC support high-availability configurations? 

Yes, VPN for VPC supports high availability in an Active-Standby configuration for policy-based VPNs, and Active-Active configuration for a static, route-based VPN.





 Are there plans to support SSL VPN? 

No, only IPsec site-to-site is supported.





 Are there any caps on throughput for site-to-site VPNaaS? 

Up to 650 Mbps of throughput is supported.





 Is Pre-Shared Key (PSK) and certificate-based IKE authentication supported for VPNaaS? 

Only PSK authentication is supported.





 Can you use VPN for VPC as a VPN gateway for your IBM Cloud classic infrastructure? 

No. To set up a VPN gateway in your classic environment, you must use an [IPsec VPN](https://cloud.ibm.com/catalog/infrastructure/ipsec-vpn).





 What does rekey collision cause? 

If you use IKEv1, rekey collision deletes the IKE/IPsec security association (SA). To re-create the IKE/IPsec SA, set the connection admin state to down and then up again. You can use IKEv2 to minimize rekey collisions.





 Is it possible to view logs from the VPN gateway for debugging purposes? 

Yes.
XRay), these preinstall libraries are then cached by the browser. Once cached the libraries are available for use in any new browser tab, even after browser restart or SAP Fiori logout; until browser cache cleared
* 20 KiB - 500 KiB (estimate) per each new Fiori app that is loaded within the session



* SAP HANA System Replication (HSR) Sync or Async, streaming Gigabyte's of data per month from primary to secondary (or tertiary) nodes



With increased traffic of new design SAP software, it is possible to heavily exceed the amount of network traffic seen in past SAP usage.

Designing your SAP applications to use the IBM Cloud private backbone for these data transfers is important, as there are no ingress/egress charges; whereas usage over public internet incurs egress charges.

You should estimate the amount of data that is transferred. During initial project implementation stages, this can be difficult. However at least by an order of magnitude estimate should be performed.





 Networking Throughput performance considerations 

SAP generally recommends 10 Gbps (redundant) network throughput for traffic between its application servers and SAP HANA databases, and for other SAP HANA clients, such as SAP Business Intelligence.

For deployments of SAP NetWeaver using SAP AnyDB with local storage, even for three-tier setups, 1 Gbps networks are usually sufficient.





 Networking Latency performance considerations 

For your business operations and non-SAP dependent systems, you may required certain latency key performance indicators (KPIs) to be met. This should consider the site location of your hosts, and testing the latency by using the IBM Cloud private backbone network.

The testing of latency by using the Round Trip Time (RTT) metric is necessary when designing High Availability (HA) and Disaster Recovery (DR) for SAP HANA.

If a HA failover is being designed within one site location, in almost all cases this will be achievable for SAP HANA System Replication requirements.

However, if designing High Availability for SAP HANA across multiple sites within a Region, or if designing Disaster Recovery across multiple Regions then the latency that uses the Round Trip Time (RTT) metric must be carefully tested and considered.
Upgrading NSX licenses for vCenter Server with Hybridity Bundle instances 

You can upgrade the VMware NSX® license for your instance to a later edition. Reverting the license to an earlier edition is not supported.



  Procedure to upgrade your NSX license 



1.  From the IBM Cloud® for VMware Solutions console, click Resources > vCenter Server from the left navigation pane.
2.  In the vCenter Server table, click the instance to upgrade the NSX license for.
3.  On the Summary page, verify that all instance details are displayed correctly. Then, click the Infrastructure tab to verify the details on the Infrastructure page.

If the details are not displayed, a connectivity problem might occur with the IBM® CloudDriver Virtual Server Instance (VSI), as a result of a firewall rule or a networking issue. Resolve the problem before you with the next step, otherwise the upgrade might fail.
4.  Click the Licensing tab and click Upgrade. In the Upgrade NSX license edition window, select the edition that you want to upgrade to and click Upgrade.

The license upgrade replaces all existing NSX licenses on the instance. Extra charges might be incurred from an overlap of old and new licenses if you upgrade in the middle of a billing cycle. To avoid extra charges, it is recommended to upgrade the license at the end of the billing cycle.







  Related links 



*  [vCenter Server with Hybridity Bundle overview](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_hybrid_overviewvc_hybrid_overview)
*  [Contacting IBM Support](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-trbl_support)
*  [FAQs](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-faq-vmwaresolutions)
Ordering Zerto 

You can include the Zerto service with a new VMware vCenter Server® instance or add the service to your existing instance.

Zerto v9.5u1 does not support vSphere 6.5 and 6.7. However, you can still order stand-alone licenses for existing vSphere 6.x instances.



 Billing for Zerto replication 

VMs that are replicated by using Zerto are metered by Zerto and IBM Cloud®. Your bill for this usage is charged through an IBM Cloud billable account instead of an IBM Cloud infrastructure account.

Before you order Zerto, ensure that your IBM Cloud account is a billable account, and that it is linked to the same IBM Cloud infrastructure account where your instance is deployed.



 Viewing Zerto charges 

To view your Zerto usage charges, follow these steps:



1. Go to the [IBM Cloud Billing and Usage](https://cloud.ibm.com/billing/usage) page.
2. From the Filter by group list, select VMware Solutions.









 Ordering Zerto for a new instance 



1. When you [order the instance](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_orderinginstance-procedure), scroll down to the Add-on services section. Zerto is in the Data resiliency and migration category.
2. Open the category, locate Zerto, and toggle its switch on.
3. Click Edit to review and specify the configuration information, then click Save.







 Ordering Zerto for an existing instance 



1. On the instance details page, click the Services tab.
2. Click Add to add the service.
3. On the Add services page, locate the Zerto service in the Data resiliency and migration section and toggle its switch on.
4. Click Edit to review and specify the configuration information, then click Save.
Technical interfaces are available for applications that are built on SAP NetWeaver AS ABAP and AS Java to run on SAP HANA. However, specific development enablement is normally required for each application to ensure it runs optimally on SAP HANA. SAP Business Suite applications (ERP, CRM, SCM, and other applications), SAP Business Warehouse (BW), and other SAP NetWeaver-based applications were modified to run on SAP HANA and use its many advantages. Additionally, various components and complimentary applications that are built on SAP NetWeaver can also run on SAP HANA by using the provided SAP NetWeaver DB interfaces.

The SAP HANA as primary persistence for SAP NetWeaver-based applications scenario has one restriction: SAP NetWeaver ABAP and Java application servers must run on separate hardware servers from the SAP HANA hardware.





 What is created 

The scripts automate the virtual infrastructure resources, provisioning processes for the SAP architecture in an existing VPC with a distributed environment. SAP NW 7.x (ABAP or Java) App server on a distinct virtual server instance VPC machine and SAP HANA DB on a dedicated server type virtual server instance VPC box machine are provisioned. The scripts work in two phases.

During the first phase ([Automate SAP bastion server – SAP media storage repository](https://cloud.ibm.com/docs/sap?topic=sap-sap-bastion-server)), the virtual infrastructure resources based on the components from the existing VPC created by the Bastion Server are:



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



* Allow inbound DNS traffic (port 53)
* Allow inbound SSH traffic (TCP port 22)
* Allow all outbound traffic from the virtual server instance
* Allow all traffic in the security group



* 1 subnet to enable networking in your VPC
* 2 virtual server instances with SAP certified storage and network configurations
* 2 floating IP address that you use to access your VPC virtual server instance over the public network



During the second phase, the Ansible Playbook is called and the SAP architecture is installed for both dedicated VSI’s SAP App VSI machine and dedicated SAP HANA VSI box.
* Example for using the custom storage class: The following .yaml file creates a claim that is named block-storage-pvc of the storage class ibmc-block-retain-custom, billed hourly, with a gigabyte size of 45Gi and IOPS of "300".

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: block-storage-pvc
labels:
billingType: "hourly"
region: us-south
zone: dal13
spec:
accessModes:
- ReadWriteOnce
resources:
requests:
storage: 45Gi
iops: "300"
storageClassName: ibmc-block-retain-custom
Show more

name
: Enter the name of the PVC.

billingType
: In the metadata labels section, specify the frequency for which your storage bill is calculated, "monthly" or "hourly". The default is "hourly".

region
: In the metadata labels section, specify the region where you want to provision your block storage. If you specify the region, you must also specify a zone. If you don't specify a region, or the specified region is not found, the storage is created in the same region as your cluster. This option is supported only with the IBM Cloud Block Storage plug-in version 1.0.1 or higher. For older plug-in versions, if you have a multizone cluster, the zone in which your storage is provisioned is selected on a round-robin basis to balance volume requests evenly across all zones. To specify the zone for your storage, you can create a [customized storage class](https://cloud.ibm.com/docs/openshift?topic=openshift-block_storageblock_multizone_yaml) first. Then, create a PVC with your customized storage class.

zone
: In the metadata labels section, specify the zone where you want to provision your block storage. If you specify the zone, you must also specify a region. If you don't specify a zone or the specified zone is not found in a multizone cluster, the zone is selected on a round-robin basis.
The continuous integration pipeline builds the executable .jar file for the sample Spring Java App.

Zoom

![VPC artifact storage Cloud Object Storage](https://cloud.ibm.com/docs-content/v1/content/562806c0b18119f4d21cb66f5ae6d051634b4a16/ContinuousDelivery/images/ds-vpc-setup-cos.png)

Figure 10. VPC artifact storage Cloud Object Storage

Alternatively, you can use Artifactory if you have an Artifactory instance of your own.







 Step 3: Add optional tool integrations 

You can add the IBM Cloud® DevOps Insights tool integration to your toolchain without any additional configuration.

[DevOps Insights](https://cloud.ibm.com/docs/ContinuousDelivery?topic=ContinuousDelivery-di_working) is included in the created toolchain. You do not need to provide any configuration steps for DevOps Insights. The continuous integration pipeline automatically uses the DevOps Insights instance that is included in the toolchain. DevOps Insights aggregates code, test, build, and deployment data to provide visibility into the velocity and quality of all of your teams and releases.

Click Continue.





 Step 4: Complete the toolchain setup 

On the Summary page, click Create. Several steps run automatically to set up your toolchain.

You can configure the individual toolchain integrations after the pipeline is created.

Zoom

![Kubernetes secure app toolchain summary](https://cloud.ibm.com/docs-content/v1/content/562806c0b18119f4d21cb66f5ae6d051634b4a16/ContinuousDelivery/images/ds-vpc-setup-summary.png)

Figure 11. VPC secure app toolchain summary





 Step 5: Explore your new toolchain 

After you create your toolchain, it shows each of the tool integrations that are part of the toolchain in a diagram.



 Explore the pipelines
* The service ID that you create for an IBM Cloud Object Storage instance is used by IBM Log Analysis to authenticate and access the IBM Cloud Object Storage instance.
* You can assign specific access policies to the service ID that restrict permissions on the IBM Cloud Object Storage instance. Restrict the service ID to only have writing permissions on the bucket where you plan to archive the logs.
* You can also restrict the IP addresses that are allowed to manage the bucket.



You are responsible for configuring and managing the bucket and the data stored in it.



* If you configure archiving in an EU-managed location, you must configure a bucket that complies with the EU-managed and GDPR regulations.



When you configure archiving, consider the following information:



* Logs are automatically archived in a compressed format (.json.gz). Each log preserves its metadata.
* After you enable and configure archiving, it can take between 24-48 hours before the first archive file is created. Data included in the first archive contains data for only the first hour.

To create an archive of older data to have available for search, you can [export the data](https://cloud.ibm.com/docs/log-analysis?topic=log-analysis-export) and uploaded the data to the archiving bucket.
* Archives can take 24 hours to be available, but can take as long as 72 hours for larger archive files.
* There is a minimum 6 hour delay from when data is archived.
* Logs are archived hourly. If a log line is received for an archive that was created 6 hours or more in the past, an archive file is created with the file name of the associated archive file appended with a sequence number (for example, 1).
* If there are no log entries for an hour, an archive file will not be written for that hour.
* In rare cases log lines can be duplicated in archive files. Duplicates can be determined by the log line ID.
* Automatic archiving is disabled for an instance when an the credentials that are used to archive data are invalid for over 24 hours.



The first time the archive process runs the number of days archived is dependent on the plan:
* UI
* CLI
* API
* Terraform







 Adjusting file share IOPS 

For File Storage for VPC file shares, you can increase or decrease IOPS to meet your performance needs. Adjust IOPS by specifying a different IOPS tier profile (IOPS are adjusted within the selected profile), custom profile, or dp2 profile. The process of adjusting the IOPS causes no outage or lack of access to the storage.

Billing for an updated share is automatically updated. The prorated difference of the new price is added to the current billing cycle. The new full amount is then billed in the next billing cycle.

IBM Cloud® File Storage for VPC is available for customers with special approval to preview this service in the Frankfurt, London, Madrid, Dallas, Toronto, Washington, Sao Paulo, Sydney, Osaka, and Tokyo regions. Contact your IBM Sales representative if you are interested in getting access.



 Adjustable IOPS concepts 

You can adjust IOPS for your file shares to tailor performance to meet your requirements.

For example, you might find that an application scaled such that a lower-tier storage profile is now a performance bottleneck. You can change the performance characteristics of the existing file share by increasing IOPS by selecting a higher IOPS tier (for example, 3 IOPS/GB tier to 5 IOPS/GB tier).

In another scenario, you might want to initially set your file storage at a higher 10 IOPS/GB performance level to expedite a data upload. After the upload completes, you can reset storage to 5 IOPS/GB for normal operations. Also, you might want to increase your file share's IOPS during peak times for your application and decrease IOPS during off-peak hours.

By using this feature, you can:



* Adjust IOPS up or down by selecting a different [IOPS tier](https://cloud.ibm.com/docs/vpc?topic=vpc-file-storage-profilesfs-tiers). IOPS is adjusted within the tier.
The field used to create the histogram must be of number (integer, float, double, or date) type. Non-number types such as string are not supported. For example, "price": 1.30 is a number value that works, and "price": "1.30" is a string, so it wouldn’t work. Use the interval argument to define the size of the sections the results are split into. Interval values must be whole, non-negative numbers, and are set to make sense for segmenting your possible field values. For example, if your data set includes the price of several items, like: “price”: 1.30, “price”: 1.99, and “price”: 2.99, you might use intervals of 1, so that you see everything grouped between 1 and 2, and 2 and 3. You would probably not use an interval of 100, because then all the data would end up in the same segment. Histograms can process decimal values, but intervals have to be whole numbers. The syntax is histogram(<field>,<interval>), as shown in the following example.

For example:

histogram(product.price,interval:1)





 timeslice 

A specialized histogram that uses dates to create interval segments. Valid date interval values are second/secondsminute/minutes, hour/hours, day/days, week/weeks, month/months, and year/years. The syntax is timeslice(<field>,<interval>,<time_zone>). To use timeslice, the time fields in your documents must be of the date data type and in [UNIX time](http://en.wikipedia.org/wiki/Unix_time) format. Unless both of these requirements are met, the timeslice parameter does not work correctly. You can create a timeslice if your documents contain date fields with values such as 1496228512. The value must be in a numeric format (for example, float or double) and not enclosed in quotation marks. The service treats dates in text and dates in ISO 8601 format as data type string, not as data type date.
The default is "hourly".

region
: In the metadata labels section, specify the region where you want to provision your block storage. If you specify the region, you must also specify a zone. If you don't specify a region, or the specified region is not found, the storage is created in the same region as your cluster. This option is supported only with the IBM Cloud Block Storage plug-in version 1.0.1 or higher. For older plug-in versions, if you have a multizone cluster, the zone in which your storage is provisioned is selected on a round-robin basis to balance volume requests evenly across all zones. To specify the zone for your storage, you can create a [customized storage class](https://cloud.ibm.com/docs/containers?topic=containers-block_storageblock_multizone_yaml) first. Then, create a PVC with your customized storage class.

zone
: In the metadata labels section, specify the zone where you want to provision your block storage. If you specify the zone, you must also specify a region. If you don't specify a zone or the specified zone is not found in a multizone cluster, the zone is selected on a round-robin basis. This option is supported only with the IBM Cloud Block Storage plug-in version 1.0.1 or higher. For older plug-in versions, if you have a multizone cluster, the zone in which your storage is provisioned is selected on a round-robin basis to balance volume requests evenly across all zones. To specify the zone for your storage, you can create a [customized storage class](https://cloud.ibm.com/docs/containers?topic=containers-block_storageblock_multizone_yaml) first. Then, create a PVC with your customized storage class.

storage
: In the spec resources requests section, enter the size of the block storage, in gigabytes (Gi). After your storage is provisioned, you can't change the size of your block storage. Make sure to specify a size that matches the amount of data that you want to store.

iops