vania-janet/multiturn-rag-retrieval-data huggingface dataset:
Blogs and other links 

These resources for gateway appliances were created by IBM and some of our partners and customers.



*  [Product Brief: AT&T Vyatta vRouter: Agile Networking and High Performance](https://public.dhe.ibm.com/cloud/bluemix/network/vra/final_vyatta_product_brief_june_2018_2.pdf)

As the first virtual router for carrier-class networks, the AT&T Vyatta vRouter is the highest-performing software router in the industry. Achieving 10+ Gbps performance per physical core, the AT&T Vyatta vRouter delivers advanced routing, stateful firewall, NAT, and VPN capabilities in software without sacrificing the reliability and carrier class performance of hardware networking solutions.
*  [Blog Post: Keep your cloud safe with IBM network security services](https://www.ibm.com/blogs/cloud-archive/2017/09/keep-cloud-safe-ibm-network-security-services/)

When it comes to securing your network, there’s no such thing as a one-size-fits-all approach. As organizations increasingly leverage critical data and applications in the cloud, you might stop and wonder which security option best suits your needs of your network.
*  [Blog Post: Meet the Virtual Router Appliance](https://www.ibm.com/blogs/cloud-archive/2017/07/virtual-router-appliance/)

With the Virtual Router Appliance, you can turn your high-performance bare metal servers into enterprise-grade virtual routers, firewalls, and VPNs to fit your unique application requirements—all from a standalone appliance or a pair of high availability (HA) appliances.
4. On the Select name and folder page, edit the name if necessary and select the location for the Hybrid Cloud Services. Click Next.
5. On the Select a resource page, select the installation location.
6. On the Select storage page, select the storage for the Hybrid Cloud Services and click Next. From the Select virtual disk format list, you can select either thin provisioning or thick provisioning.
7. On the Setup networks page, map the Hybrid Cloud Services adapter to a host network chosen from the Destination list.



7. On the Customized template page, enter the values specific to the environment:



* For the passwords, the default username for both the command-line interface (CLI) and the web user interface is admin. The admin user and password to log in to the web user interface is required as is also a root user account that has a password that can be set.
* Enter and reenter the CLI admin user password.
* Enter and reenter the root user password. In the future, if help is needed from VMware Global Support Services (GSS), this password might have to be shared so they can troubleshoot the system.
* For the network properties, enter the hostname for the HCX Manager VM. Enter the network IPv4 address, the IPv4 prefix (the CIDR), and the default gateway. The following table shows sample values:





Table 2. Sample values for network properties

 Field Value 

 Hostname HCM_1 
 Network 1 IPv4 address 192.168.200.101 
 Network 1 IPv4 prefix 24 
 Default IPv4 gateway 192.168.200.1 
 Network 1 IPv6 address 
 Network 1 IPv6 prefix 



8. Review the vService bindings page. Click Next to continue.
9. On the Ready to complete page, follow these steps:



* Check the Power on after deployment box.
* Review the Hybrid Cloud Services settings, and click Finish. It might take several minutes for the Hybrid Cloud Services appliance to power on.
For more information about these systems and how they're used inside the IBM Power Systems Virtual Server service, see the following data sheets:

Data sheets:



* [IBM Power System S922 (9009-22A)](https://www.ibm.com/downloads/cas/KQ4BOJ3N)
* [IBM Power System E980 (9080-M9S)](https://www.ibm.com/downloads/cas/VX0AM0EP)



For further information, see [hardware specifications for IBM Power Systems Virtual Servers](https://cloud.ibm.com/docs/power-iaas?topic=power-iaas-about-virtual-serverhardware-specifications).







 VMware Software-Defined Data Center 

IBM Cloud and VMware partner to bring the capabilities of VMware for SAP into Cloud by using VMware vSphere installed to IBM Cloud® Bare Metal Servers.

This enables secure single-tenant compute with full root control to the hypervisor, providing optimized performance with high agility, resiliency, and elastic compute costs. Since Dec-2007, when VMware first announced support for SAP, there has been continuous improvement to VMware-SAP capabilities, which provide flexible delivery of SAP project implementations and easier maintenance of SAP Systems; all these capabilities are available with VMware and IBM Cloud.

In short, IBM Cloud provides two levels of VMware, which are both SAP-certified:



* Intel Bare Metal and VMware vSphere (ESXi OS), requires manual VMware setup and configuration
* IBM Cloud for VMware Solutions Dedicated, fully automated VMware SDDC setup and configuration



* includes optional BYOL and access to advanced VMware capabilities, such as VMware HCX for seamless bidirectional network extension and connection to existing VMware clusters on-premises





For more information about IBM Cloud for VMware on Classic Infrastructure, see [IBM Cloud for VMware](https://www.ibm.com/cloud/vmware). Additional information is available on:
Dedicated private cloud for instances on Amazon Web Services 

IBM® Db2® Warehouse on Cloud can now be deployed on an Amazon Web Services instance in a dedicated virtual network managed by IBM.

One quantity of this part supports up to ten Db2 Warehouse on Cloud service instances. When a dedicated virtual network is in place, only specific AWS VPC's can access the database.

If you'd like to request this option, open a support case with IBM Cloud support to make the request. You will need to provide your IBM Cloud account ID in the ticket.

The lead time required is approximately 3-4 weeks. After your dedicated private cloud environment has been pre-built, you can deploy one or more instances into the private cloud environment by setting "Dedicated Private Cloud Configuration" to Yes when you order the instance from the IBM Cloud catalog page.
Network 1 IPv6 address 
 Network 1 IPv6 prefix 



8. Review the vService bindings page. Click Next to continue.
9. On the Ready to complete page, follow these steps:



* Check the Power on after deployment box.
* Review the Hybrid Cloud Services settings, and click Finish. It might take several minutes for the Hybrid Cloud Services appliance to power on.
* To check the status, go to the vSphere Web Client home page, and on the Home tab, go to Inventories and click Hosts and Clusters. Expand the data center hierarchy, and click the Hybrid Cloud Services service VM to display a summary in the center pane.
* View the Summary tab, the console reads Powered On and the Play icon is green.



10. The HCX Manager is powered on and ready to be registered with the on-premises vCenter.









 Initial configuration of the HCX Manager Appliance 



1. Ensure that the Hybrid Cloud Service virtual appliance has outbound access to https://connect.hcx.vmware.com and https://hybridity-depot.vmware.com.
2. Log in to Hybrid Cloud Services virtual appliance admin interface https://<IP>:9443 with admin.
3. Provide the license key collected in Client-Side Prerequisites.
4. For HCX Cloud Datacenter Location, enter the city nearest to the data center where the HCX Cloud Instance resides. If the city is not present, select the nearest major city.
5. Provide the system name.







 Import vSphere Server certificate 



1. Log in to HCX Manager Admin Interface https://<IP>:9443.
2. Select the Administration tab, under Certificate -> Trusted CA Certificate.
3. Import vSphere Server website.







 Procedure to register HCX Manager with vCenter/SSO/NSX 



1. Log in to Hybrid Cloud Services service virtual appliance.
2. On the Dashboard pane, complete the following steps:



1.
For more information about resource requirements and capacity checking for some services, see [Resource requirements for services](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_addingservicesvc_addingservices-resource-requirements).

The following components are ordered and included in the Zerto service.

Zerto Virtual Replication Appliance (VRA) components are deployed only into the default cluster.



 Virtual Service Instances 



* One Virtual Service Instance (VSI) - Zerto Virtual Manager
* 2 x 2.0 GHz cores
* 4 GB RAM
* Windows® Server 2019 Standard Edition (64-bit)







 Storage 

100 GB (SAN) disk





 Zerto Networking 



* VSI



* One primary private IP address
* 1 Gbps private network uplink



* Virtual replication appliances (VRAs)



* One private portable subnet for VRA deployment





The Zerto service is not configured with an IBM Cloud Infrastructure portable IP address or with a NAT connection to the public network, even if you have public interfaces in your instance. This implementation helps to avoid the possibility of asymmetric routing when it uses a network gateway appliance.

When you deploy Zerto, you must configure your own proxy or NAT connection to the public network. If you do not complete the configuration, Zerto blocks management activities in 15 days. For more information about the Call Home feature for Zerto, see [Considerations for ordering Zerto](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-zerto_orderingzerto_ordering-private-only).





 Licenses and fees 

Zerto Replication version 9.7u3 license.







 Related links 



* [Ordering Zerto](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-zerto_ordering)
* [Managing Zerto](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-managingzertodr)
: To migrate the Veeam service from VMware NSX-V to VMware NSX-T, open an IBM Support ticket by following the steps in Contacting IBM Support.

REST API
: For VMware Shared, the V1 API support ended on 31 December 2022. Use the [V2 API](https://cloud.ibm.com/apidocs/vmware-solutions-shared/vmware-solutions-shared-v2.0.0).

User interface updates and enhancements
: The left navigation menu in the instance detail page is now changed to tabs. Also, a new tab Access information is added, where you can see information such as AD/DNS IP and remote desktop credentials for your instance.







 2022 



 31 October 2022 

Cyber Recovery
: The V5.0 release offers a new Cyber Recovery instance. The instance can help you protect your systems and data from cyberthreats and attacks. It can assist you with handling ransomware and help you with other problems and threats.

The Cyber Recovery instance includes Veeam Backup and Replication 12, a Linux® hardened repository (LHR), and an edge gateway. For more information, see Cyber Recovery overview.

Private network endpoint enhancements
: You can now edit the private network endpoints allowlisted IP addresses and subnets for your VMware Solutions Shared instance. For more information, see Modifying a private network endpoint for a virtual data center.

Veeam self-service portal for VMware Shared
: The Veeam self-service portal is now automatically enabled for existing and new VMware Cloud Director organizations. For more information, see Managing Veeam for VMware Shared.

MEX01 data center no longer available
: (Updated on 14 November 2022) The Mexico 01 IBM Cloud data center is closing on 31 January 2023. This data center is no longer available for deployments.

VMware vSphere 7.0u2 - deprecated
: (Updated on 14 November 2022) The vSphere 7.0u2 option is no longer available for adding hosts to vCenter Server instances and scaling existing vSphere clusters.
* The classic infrastructure filters the following networks from the BGP advertisements coming from the Power Systems Virtual Server router because these IP addresses are used by the services networks: 10.0.0.0/14, 10.198.0.0/15, 10.200.0.0/14, 169.254.0.0/16, 224.0.0.0/4 and any IP ranges that are assigned to your IBM Cloud classic private subnets.

You can use the 10.x.x.x range if there is no conflict with an IBM Cloud back-end 10.x.x.x service. You must contact IBM Support if you want to use NAT'ing or IP aliasing to resolve the IP conflict. However, IBM does not recommend using the 10.x.x.x range when you create a network.





3. Identify the IBM Cloud classic private subnets and the IP address schema that is assigned to you when you ordered bare metal or virtual server instances that are hosted on your IBM Cloud classic private subnets. Connect to the required resources and services.

All the routers in all classic infrastructure data centers and PoPs across the global IBM Cloud backbone are connected to the Power Systems Virtual Server router by using the Direct Link Connect VRF-enabled connection.

Each IBM Cloud Direct Link workspace is not redundant. However, diversity can be engineered using multiple Direct Links and BGP. For more information, see [Models for diversity and redundancy in Direct Link (2.0)](https://cloud.ibm.com/docs/dl?topic=dl-models-for-diversity-and-redundancy-in-direct-link).







 Connecting to VPC by using Direct Link Connect 

In this deployment topology, a Direct Link (2.0) is used to connect your Power Systems Virtual Server networks to resources that are hosted in the IBM Cloud VPC infrastructure.

Zoom

![Connect to VPC](https://cloud.ibm.com/docs-content/v1/content/1d36273917990fbf48078805e201d2e85e2fcb27/power-iaas/images/network-connect-to-vpc.svg)

Figure 2.
[DNS Services](https://cloud.ibm.com/docs/dns-svcs/getting-started) Provides private DNS to Virtual Private Cloud (VPC) users. 
 [Transit Gateway](https://cloud.ibm.com/docs/transit-gateway?topic=transit-gateway-getting-started) Interconnect IBM Cloud Classic and Virtual Private Cloud (VPC) infrastructures worldwide, keeping traffic within the IBM Cloud network. 
 [Direct Link 2.0](https://cloud.ibm.com/docs/dl/getting-started) Seamlessly connect your on-premises resources to your cloud resources. 







 Classic infrastructure 



Table 2. Networking options - Classic

 Option Description 

 [Content Delivery Network](https://cloud.ibm.com/docs/CDN?topic=CDN-getting-started) Used for various industry solutions, including media, entertainment, software, gaming, banking, and e-commerce, to meet the needs of your businesses. 
 [Domain Name Service](https://cloud.ibm.com/docs/dns?topic=dns-getting-started) Provides a central location to view and manage your domains through the basic DNS management interface, and also gives you the option to manage reverse and secondary DNS in the same location for free of charge. 
 [Global IP addresses](https://cloud.ibm.com/docs/subnets?topic=subnets-about-subnets-and-ipsglobal-ip-addresses) Provide flexibility to shift workloads between servers, even across geographically disparate data centers. 
 [Load balancing](https://cloud.ibm.com/docs/loadbalancer-service?topic=loadbalancer-service-getting-started) Distributes processing and communications evenly across multiple servers within a data center so that a single device does not carry an entire load.
Required permissions for the IBM Cloud infrastructure account

 Permission Details 

 Add Server This permission is required for the following operations: to order IBM Cloud bare metal servers on which VMware ESXi™ runs and to provision hourly virtual servers that are used, for instance, configuration, maintenance, and support operations. 
 Cancel Server This permission is required to release and reclaim bare metal servers on which VMware ESXi runs. If you delete your instance, the ordered components are automatically released in the correct dependency sequence. 
 View Virtual Server Details This permission is required to retrieve the server provisioning details, which are required for order validation and automated configuration. 
 Add Storage This permission is required to order backup storage and shared storage for the instance. 
 Manage Storage This permission is required to manage backup storage and shared storage for the instance. 
 Hardware Firewall This permission is required to edit or view firewall log files and settings for the Fortinet service, if it is installed on your instance. 
 Add Compute with Public Network Port This permission is required to order hardware and VSIs (Virtual Server Instances) with public network ports. 
 Add IP Addresses This permission is required to order portable private subnet ranges on your behalf, which is needed to manage the virtual machines that run in a VMware vSphere® cluster. When more services are added to your instance, the portable private IP addresses are assigned to VMware ESXi servers to isolate and allocate bandwidth. 
 Add Tickets This permission is required to open service tickets on your behalf. Tickets might be created for the following operations: to initiate restore operations and to initiate problem resolution processes automatically when issues are found. 
 Edit Tickets This permission is required to edit the service tickets that are created on your behalf. 
 View Tickets This permission is required to monitor the service tickets that are related to the components in your instance for IBM Cloud infrastructure provisioning delays and problems. 
 View Hardware Details This permission is required to retrieve the hardware details, which are needed for order validation and automated configuration. 
 Reboot / Control This permission is required to power off the hardware during the hardware cancellation process when you delete an instance. 
 View Licenses This permission is required to retrieve and validate the licenses that are used by your instance. 
 View Passwords This permission is required to be able to administer the ordered VSIs.
An example of a successful configuration is also provided.







 Using Network High Availability 

Use Network High Availability to anchor your VMware Cloud Director network in two data centers.

You must access data center groups to use the Network High Availability feature. A data center group acts as a cross-virtual data center router that provides the following.



* Centralized networking administration
* Configuration for multiple egress points in multiple virtual data centers
* East-west traffic between all networks within the group



For more information, see [Managing cross-virtual data center networking](https://docs.vmware.com/en/VMware-Cloud-Director/10.1/VMware-Cloud-Director-Tenant-Portal-Guide/GUID-086DD0B6-C01C-43EB-BFDE-DED999980B2A.html).

The data center groups do not require physical separation. However, for optimal redundancy, the recommended implementation of a data center group has the egress points in two different physical data centers, for example, Dallas 10 and Dallas 12.



 Procedure to create a local data center group 



1. From the main navigation bar of the IBM Cloud for VMware Solutions console, select Data Centers > Data Center Groups, then click New Data Center Group.
2. Complete the configuration of the new data center group.



1. On the Name tab, enter the name of the data center group and select Create Local Group. Click NEXT.
2. On the Network Pool tab, select the network pool. Click NEXT.
3. On the Data Centers tab, select the virtual data centers to include in the data center group. Click NEXT.
4. On the Review tab, confirm your configuration and click FINISH.





The data center group is created and an NSX Distributed Logical Router (DLR) is associated to the group.





 Procedure to add an EGress point 

The NSX Edge Service Gateways (ESG) must have a free interface (vNIC) that is used to attach to the DLR.
* (NSX-V only) One VXLAN (Virtual eXtensible LAN) with DLR (Distributed Logical Router) for potential east-west communication between local workloads that are connected to layer 2 (L2) networks. The VXLAN is deployed as a sample routing topology, which you can modify, build on it, or remove it. You can also add security zones by attaching extra VXLANs to new logical interfaces on the DLR.
* VMware NSX Edge Services Gateways (four for NSX-T and two for NSX-V):



* One secure management services VMware NSX Edge Services Gateway (ESG) for outbound HTTPS management traffic, which is deployed by IBM as part of the management networking typology. This ESG is used by the IBM management VMs to communicate with specific external IBM management components that are related to automation. For more information, see [Configuring your network to use the customer-managed ESG](https://cloud.ibm.com/docs/vmwaresolutions?topic=vmwaresolutions-vc_esg_config).

This ESG is named mgmt-nsx-edge, it's not accessible to you and you can't use it. If you modify it, you might not be able to manage the vCenter Server instance from the IBM Cloud for VMware Solutions console. In addition, by using a firewall or disabling the ESG communications to the external IBM management components might cause VMware Solutions to become unusable.
* Secure customer-managed ESG for outbound and inbound HTTPS workload traffic. The ESG is deployed by IBM as a template that can be modified by you to provide VPN access or public access. For NSX-V, one ESG is deployed. For NSX-T, two ESGs are deployed on the datastore with the highest IOPS.



For more information, see [Does the customer-managed NSX Edge pose a security risk?]
: Optional: Do not show the message of the day or update reminders.



 Example cluster subnet add command 

ibmcloud oc cluster subnet add --cluster my_cluster --subnet-id 1643389







 ibmcloud oc cluster subnet create 

Classic infrastructure

Create a portable classic subnet in an IBM Cloud infrastructure account on your public or private VLAN and make it available to a cluster.

Portable public IP addresses are charged monthly. If you remove portable public IP addresses after your cluster is provisioned, you still must pay the monthly charge, even if you used them only for a short amount of time. When you make a subnet available to a cluster, IP addresses of this subnet are used for cluster networking purposes. To avoid IP address conflicts, make sure that you use a subnet with one cluster only. Do not use a subnet for multiple clusters or for other purposes outside of IBM Cloud Kubernetes Service at the same time. If you use the same subnet across multiple clusters, your default Ingress TLS certificate might become invalidated. In classic clusters, if you have multiple VLANs for your cluster, multiple subnets on the same VLAN, or a multizone classic cluster, you must enable a [Virtual Router Function (VRF)](https://cloud.ibm.com/docs/account?topic=account-vrf-service-endpointvrf) for your IBM Cloud infrastructure account so your worker nodes can communicate with each other on the private network. To enable VRF, see [Enabling VRF](https://cloud.ibm.com/docs/account?topic=account-vrf-service-endpointvrf). To check whether a VRF is already enabled, use the ibmcloud account show command. If you can't or don't want to enable VRF, enable [VLAN spanning](https://cloud.ibm.com/docs/vlans?topic=vlans-vlan-spanningvlan-spanning).