vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Juniper vSRX on IBM Cloud overview 

Juniper® vSRX on IBM Cloud is a virtual security appliance that provides security and networking services at the perimeter or edge in virtualized private or public cloud environments. Within a VMware® infrastructure, vSRX runs as a pair of virtual machines (VMs) within the VMware vSphere® environment. Juniper vSRX on IBM Cloud is a non-IBM product that is offered under terms and conditions from Juniper Network, not IBM.

IBM Cloud® for VMware Solutions offers promotions for some add-on services. Promotional pricing offers a number of months without charge for a service license, if the service has license charges. For more information, see [Promotions for VMware Solutions add-on services](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_addingservicesvc_addingservices-service-promotions).

The Juniper vSRX version available for deployment is 3.0 (23.1R1).

For more information about vSRX and the vSRX 3.0 architecture, see [vSRX Deployment Guide for Private and Public Cloud Platforms](https://www.juniper.net/documentation/us/en/software/vsrx/vsrx-consolidated-deployment-guide/index.html).

You can install Juniper vSRX as one of the following components:



* As a virtual appliance on the management cluster. In this case, Juniper vSRX protects the traffic in the management cluster. That is, the service protects only the traffic that you forward from your devices, for example, setting the default gateway to point to Juniper vSRX.
* As a security or gateway appliance on the gateway cluster. In this case, Juniper vSRX works like a gateway appliance, which you can set without having to configure any devices. Juniper vSRX protects all clusters in the same pod and data center. With this deployment, you route all traffic in the same pod and data center to protect a broader portion of the system.

You cannot install Juniper vSRX and FortiGate Virtual Appliance on the same gateway cluster.
For more information about rules regarding hostnames for SAP systems, see [SAP Note 611361 - Hostnames of SAP ABAP Platform servers](https://launchpad.support.sap.com//notes/%20611361). 



5. Initialize the Terraform CLI.

terraform init
6. Create a Terraform execution plan. The Terraform execution plan summarizes all the actions that are done to create the VPC instance in your account.

terraform init
7. Verify that the plan shows all of the resources that you want to create and that the names and values are correct. If the plan needs to be adjusted, edit the input.auto.tfvars file to correct resources and run terraform plan again.
8. Create the VPC for SAP instance and IAM access policy in IBM Cloud.

terraform apply

The VPC and components are created and you see output similar to the terraform plan output.



This automation is offered free of charge however, the provisioned infrastructure comes at cost.





 Next steps 

If you need to rename your resources after they are created, modify the input.auto.tfvars file to change the names and run terraform plan and terraform apply again. Do not use the IBM Cloud Dashboard and user interface to modify your VPC after it is created. The Terraform scripts create a complete solution and selectively modifying resources with the user interface might cause unexpected results.

If you need to remove your VPC, go to your project folder and run terraform destroy.
Review the following guidance for AD in a vCenter Server instance.



* For more information about supported AD trusts, see [Microsoft Active Directory trusts supported by VMware vCenter Single Sign-on](https://kb.vmware.com/s/article/2064250).
* Enable vCenter with an identity source for authentication of all vCenter services and system administrators. This configuration is made by the VMware Solutions automation ready for the customer to add their system administrator users. All systems administrators who are managing the VMware Server instance have user accounts that are members of this domain.
* Create a domain to serve as a single point of access control for systems administrators who support the VMware vSphere® and NSX infrastructure components. This configuration is made by the VMware Solutions automation.
* Deploy two domain controllers for resiliency. If you select the single VSI AD/DNS option, provision a second Microsoft® Windows® VSI and configure as a domain controller.
* Do not change the existing domain name.
* Do not change the existing ic4V-vCenter AD security group.
* Do not change the existing user automation or its group membership is altered.
* Do not change the existing add-on service accounts, or their groups membership is altered.
* When you deploy the IBM Cloud for VMware Solutions workload domain controllers, deploy them in subnets that don’t have a route to a NAT gateway or other device that would provide outbound internet access.
* Keep OS security patches up to date on all the domain controllers.
* Restrict ports and protocols that are allowed into the domain controllers by using NSX distributed firewall.
* Allow remote management access, like remote desktop protocol (RDP) only from trusted networks.
* Consider whether encryption of the VM is required.
* If you choose the option to deploy AD servers into the vSphere cluster, provide Microsoft Windows licensing and activation for the servers to ensure compliance and availability.
* Integrate NSX VPN, if applicable, with AD SSO.
* Integrate vSphere ESXi hosts with AD SSO.
* Consider extending the existing AD security group structure in the IBM Cloud for VMware Solutions infrastructure domain to provide more separation of duties.
* [About VMware ESXi upgrade](https://docs.vmware.com/en/VMware-vSphere/7.0/com.vmware.esxi.upgrade.doc/GUID-65B5B313-3DBB-4490-82D2-A225446F4C99.html)



* Set up vSphere Update Manager (VUM) within your vCenter Server instance to download updates from VMware vSphere. For more information, see [VMware Update Manager introduction](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vum-introvum-intro).
* Open a support ticket with the IBM Cloud for VMware Solutions team to notify them that an upgrade is being planned. The ticket remains open until the instance is registered at the upgraded level in the IBM Cloud for VMware Solutions console.
* Confirm whether the vCenter Server instance that you are upgrading is linked to another vCenter Server instance as primary or secondary in the IBM Cloud for VMware Solutions console. All linked instances must have their Platform Services Controllers (PSCs) upgraded first as part of a particular site upgrade.
* Confirm the following requirements for vSAN based instances:



* Ensure that the vSAN Health tool is enabled and reports no critical errors. If critical errors are present, contact the IBM Support team with the upgrade support ticket ID.
* Ensure that each node has space to handle rebuilding redundancy of vSAN objects in case an ESXi host fails to come back up during the upgrade. You might need to either reduce disk usage or add an ESXi host before the upgrade.
* Verify whether the overall vSAN volume usage is higher than 70%. You might need to either reduce disk usage or add an ESXi host before the upgrade.



* Verify that the PSC and vCenter Server root user ID with its credentials are visible on the console. If your vCenter Server instance was initially ordered in V2.5 or later, only the account with customerroot access is visible on the console. In this case, contact IBM Support for the root user ID password for PSC and vCenter Server.
VMware HCX introduction 

The VMware® HCX™ service enables creating a seamless connection between IBM Cloud® for VMware Solutions instances and an on-premises VMware virtualized data center.

The IBM Cloud for VMware Solutions includes fully automated, rapid deployments of VMware vCenter Server® in the IBM Cloud. These offerings complement the on-premises infrastructure and allow existing and future workloads to run in the IBM Cloud without conversion by using the same tools, skills, and processes they use on-premises.

The VMware HCX service takes this hybridity to the next step, blending instances of vCenter Server with existing on-premises virtualized data centers. It enables the creation of seamless network extensions and bidirectional migration of workloads.

The VMware HCX components are deployed as virtual machines (VMs) in the IBM Cloud VMware target site. They allow a connection with the VMware HCX components that are installed in the peer on-premises source site.

Zoom

![VMware vCenter Server – Hybrid Cloud services](https://cloud.ibm.com/docs-content/v1/content/5bdb37c0149145723c5437e8176651928565e722/vmwaresolutions/images/ibmcloud-hcx-overview.svg)

Figure 1. VMware vCenter Server - HCX overview

This connection creates a loosely coupled interconnectivity between on-premises and IBM Cloud and enables capabilities, such as:



* Simple interconnectivity – logical network connections are established easily over any physical connection such as public internet, private VPN, or direct link.
* Layer 2 extension – on-premises networks are extended into the cloud. These networks include on-premises subnets and IP addressing.
* Encryption – network traffic is securely encrypted between the two sides.
* Optimized network – selects the best connection and efficiently floods the connection so that network traffic is moved as fast as possible.
* Data deduplication – as much as 50% reduction in network traffic can be achieved
The domain controllers for your IBM Cloud for VMware Solutions workload domain are connected to these overlay networks.







 Preventing problems with Active Directory 

To prevent problems with your system in the future, you must keep your Active Directory (AD) up to date. A current AD is required for various functions, such as managing DNS records.





 Related links 



* [Overview of VMware Solutions](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-solution_overview)
* [Getting started with VMware Solutions](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-getting-started)
For more information about the VM routing process, see [Setting up a virtual machine network](https://cloud.ibm.com/docs/virtualization?topic=virtualization-setting-up-a-virtual-machine-network). Machines that are on the same VLAN can communicate after you set up the VM network. [Enable VLAN spanning](https://cloud.ibm.com/docs/vlans?topic=vlans-vlan-spanning) if machines that are on different VLANs must communicate.





 Access and securely store ISOs 

VMs on the IBM Cloud network can run pre-configured or custom ISOs. VMs on the IBM Cloud network can access the internal mirrors site, which is available exclusively to IBM Cloud users and provides popular configurations of the most commonly used operating systems. If you need a special version or configuration for a specific operating system, see the OS vendor's website.

If you run a custom ISO on your VM, upload your ISO to a secure location so it can be retrieved if a device fails. Many users choose to store custom ISOs on a device's local system by using SSH or RDP. Alternately, space is offered through storage services that have various features.
DNS FAQs 

Frequently asked questions for DNS and Domain Name Registration might include questions about server addresses, name server options, and other common inquiries. To find all FAQs for IBM Cloud®, see our [FAQ library](https://cloud.ibm.com/docs/faqs).



 What are the DNS servers? 

The DNS servers are 161.26.0.10 and 161.26.0.11.





 What are the local (or private) IBM Cloud DNS resolvers? 

The local resolving name servers on the IBM Cloud private network are:



* rs1.service.softlayer.com 10.0.80.11
* rs2.service.softlayer.com 10.0.80.12



These local resolving name servers are on our private network, so they don't use up public bandwidth.





 What are the IBM Cloud name server addresses? 

IBM has two addresses for authoritative name servers and two addresses for resolving name servers. These local resolving name servers are on the IBM private network, so they don't use up public bandwidth.



* Authoritative name servers



* ns1.softlayer.com 67.228.254.4
* ns2.softlayer.com 67.228.255.5



* Resolving name servers



* rs1.service.softlayer.com 10.0.80.11
* rs2.service.softlayer.com 10.0.80.12









 What IBM Cloud DNS servers will answer for my secondary domains? 

The IBM Cloud Anycast, IPv-enabled authoritative DNS Servers will answer for your secondary domains. These servers are found at the following addresses:



* ns1.softlayer.com
* ns2.softlayer.com







 Which IP addresses are used for my secondary domain zone transfers? 

Transfers for your secondary domains come from one of the following four IP addresses:



* 66.228.118.67
* 67.228.119.235
* 208.43.119.235
* 12.96.161.249







 What is the difference between the public and private name servers?
Quickly deploy an instance and use the streamlined console UI to [build a network](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-build-network), easily [deploy smart contracts](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-smart-contracts), [govern your components](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-govern-components), and [govern your channel](https://cloud.ibm.com/docs/blockchain?topic=blockchain-ibp-console-govern). Interested in APIs? See the [IBM Blockchain Platform API reference](https://cloud.ibm.com/apidocs/blockchain). With the IBM Blockchain Platform, it is easy to extend a basic network, work with multicloud solutions, and receive IBM worldwide support when needed. Finally, the IBM Blockchain Platform provides additional security benefits that are essential for running an enterprise-grade production network.





 What version of Hyperledger Fabric is being used with IBM Blockchain Platform? 

IBM Blockchain Platform for IBM Cloud uses Hyperledger Fabric v2.2.10.





 Can IBM Blockchain Platform components interoperate with Hyperledger Fabric components on the same network? And vice versa? And what is the support policy for networks that include both IBM Blockchain Platform components and open source components? 

Yes. Hyperledger Fabric networks consist of many distributed members owning one or more nodes. There are multiple deployment options:



* IBM Blockchain Platform for IBM Cloud with console
* IBM Blockchain Platform v2.x (Full Platform)
* IBM Blockchain Images
* Open source Hyperledger Fabric images or a non-IBM product



Containers deployed from any of the above sources can be connected on a single channel and transact. You can join IBM Blockchain Platform peers to any network running Hyperledger Fabric components.
* If you want to upgrade your existing vCenter Server with NSX-T instance, you must upgrade to NSX-T 3.0.2.



VMware Solutions Dedicated - new Cascade Lake server support
: The following IBM Cloud bare metal servers are available for deployment for vCenter Server instances and vSphere clusters with vSphere 6.7.



* Dual Intel Xeon Platinum 8260 / 48 Cores, 2.4 GHz
* Quad Intel Xeon Platinum 8260 / 96 Cores, 2.4 GHz



VMware Solutions Dedicated - support for Osaka IBM Cloud data centers
: The following IBM Cloud data centers are available for deployment on vCenter Server, VMware vSphere, and IBM Cloud for VMware Mission Critical Workloads instances: Osaka 21, Osaka 22, and Osaka 23.

VMware Solutions Dedicated - updates for the edge services cluster
: The CPU model for new deployments of vCenter Server instance edge services clusters is Dual Intel Xeon Silver 4210 (Cascade).

VMware Solutions Dedicated - increased local disk count
: For new vCenter Server instances and new clusters added to vCenter Server instances, the local disks option for storage now supports 10 and 12 disks.

Add-on services
: The 3.9 release provides the following service versions on newly deployed instances.



* BIG-IP VE v15.1.0.5
* HyTrust CloudControl v6.2 for vCenter Server with NSX-T



During the pre-configuration of HyTrust CloudControl v6.2, global PIP is enabled.



* Juniper vSRX and Juniper vSRX Gateway Appliance 3.0 (20.1R1.11)
* Red Hat OpenShift for VMware v4.4.23



You can now install the Red Hat OpenShift for VMware service on vCenter Server with NSX-T instances. For NSX-T, you must have a new vCenter Server instance with NSX-T that is provisioned with NSX-T 3.0.1.1 or you must upgrade from NSX-T 2.5.1 to NSX-T 3.0.2.
You can view or delete VMware vSphere® instances from the VMware Solutions console. You can also add or delete VMware ESXi™ servers, and add or delete licenses for vSphere instances from the VMware Solutions console.

22 June 2023 | Madrid data centers available

The data centers Madrid 02, Madrid 04, and Madrid 05 are now available for deployment.

8 March 2023 | VMware Cloud Director upgrade for VMware Shared

The VMware Shared infrastructure is updated to VMware Cloud Director (vCD) v10.4.1.
* The hostname prefix must end with a lowercase alphabetic or numeric character.
* The maximum length of the hostname prefix is 10 characters.







 Configure hostnames individually 

You can customize the hostnames prefix individually by toggling the switch on.

The hostname prefix must meet the following requirements:



* Only lowercase alphabetic, numeric, and dash (-) characters are allowed.
* No consecutive dash characters are allowed.
* The hostname prefix must start with a lowercase alphabetic character.
* The hostname prefix must end with a lowercase alphabetic or numeric character.







 Uplink speed 

The uplink speed of 10 Gb, which is selected by default.





 Networking type 

Select either Public and private network or Private network only for the gateway cluster.







 Summary 

Based on your selected configuration for the cluster, the estimated price is instantly generated and displayed in the Summary pane. Click Pricing details to generate a PDF document with the price summary for the IBM Cloud for VMware Solutions resources.

You can also add the provisioned resources to the IBM Cloud estimate tool, by clicking Add to estimate. The estimate tool is useful if you want to get an approximate price of the selected IBM Cloud for VMware Solutions resources together with other IBM Cloud resources that you might consider purchasing.





 Procedure to add clusters to Cyber Recovery instances 



1. From the VMware Solutions console, click Resources > Cyber Recovery from the left navigation pane.
2. In the Cyber Recovery table, click the instance that you want to add clusters to.

Ensure that the instance status is Available. Otherwise, you cannot add clusters to the instance.
3. Click the Infrastructure tab and click Create on the upper right of the Clusters table.
4. On the Create cluster page, select the cluster type.
5. For workload clusters, enter the cluster name and complete the following configuration.



1. Complete the licensing settings.



* For Business Partner users, the vSphere license (Enterprise Plus edition) is included and purchased on your behalf.
* For users who are not Business Partners, select Include with purchase for the new vSphere license to be purchased on your behalf.
Gateway Appliances docs 

IBM Cloud Gateway Appliances are devices that give you enhanced control over network traffic, accelerate your network’s performance, and improve your network security. You can manage your physical and virtual networks for routing multiple VLANs, for firewalls, VPN, traffic shaping, and more.

 Recommended content 

[Getting started with IBM Cloud Gateway Appliance Learn how to get started using a gateway appliance and what the next steps are so you can dive deeper.](https://cloud.ibm.com/docs/gateway-appliance?topic=gateway-appliance-getting-started)[Ordering an IBM Cloud Virtual Router Appliance The IBM Cloud™ Virtual Router Appliance (VRA) provides the latest Vyatta 5600 operating system for x86 bare metal servers. It is offered as a High Availability (HA) or standalone configuration, and lets you route private and public network traffic selectively, through a full-featured enterprise router that has firewall, traffic shaping, policy-based routing, VPN, and other features.](https://cloud.ibm.com/docs/virtual-router-appliance?topic=virtual-router-appliance-getting-startedorder-vra)[Ordering an IBM Cloud Junniper vSRX IBM Cloud™ Juniper vSRX allows you to route private and public network traffic selectively, through a full-featured, enterprise-level firewall that is powered by JunOS software features, such as full routing stacks, QoS and traffic sharing, policy-based routing, and VPN.](https://cloud.ibm.com/docs/vsrx?topic=vsrx-getting-startedordering-with-a-linked-account)

 Learn more 

[IBM Developer<br><br>Visit IBM Developer for technical articles, code patterns, tutorials, and more.<br><br>!
Use case 2 

IBM Cloud® for VMware® Regulated Workloads delivers high security for sensitive workloads such as those run by users in the healthcare or financial sectors.

The architecture of the IBM Cloud for VMware Regulated Workloads is designed for isolation of sensitive workloads.

Compute and storage resources are offered in a dedicated workload region where the deployment of multiple clusters allows isolation of workloads by business unit or other designation, such as PCI workloads, further enhancing the security of the IBM Cloud for VMware Regulated Workloads.

Network isolation is maintained between the workload region, the management plane, and the edge region by using a gateway appliance at the physical plant level. The workloads also benefit from the inclusion of an SDN overlay that is delivered with NSX-T™. NSX-T uses micro-segmentation to enforce traffic isolation. Micro-segmentation policies applied to workload VMs are configured by the user to meet business requirements.

The use of shared resources, such as VSIs or shared storage options, is prohibited to prevent any data leakage out of the IBM Cloud for VMware Regulated Workloads. All resources necessary to support the workloads are delivered from within the IBM Cloud for VMware Regulated Workloads dedicated instance.

Data and VM encryption options are included in the IBM Cloud for VMware Regulated Workloads. The preferred option is keep your own key (KYOK) by using IBM Hyper Protect Crypto Services (HPCS). Connecting HPCS to the IBM Cloud for VMware Regulated Workloads is either accomplished by through the IBM Cloud KMIP adapter that is required to integrate with the vCenter directly.

IBM Cloud for VMware Regulated Workloads is designed with high security throughout the platform, which makes it an option for user workloads that demand the highest level of protection.



  Related links 



*  [IBM Cloud compliance programs](https://www.ibm.com/cloud/compliance)