Platform and Public Cloud Support
The Oracle Communications Subscriber-Aware Load Balancer (Subscriber-Aware Load Balancer) can be run on the platforms listed in this section.
Note:
The Subscriber-Aware Load Balancer does not support automatic, dynamic disk resizing.Note:
Virtual Subscriber-Aware Load Balancers do not support media interfaces when media interfaces of different NIC models are attached. Media Interfaces are supported only when all media interfaces are of the same model, belong to the same Ethernet Controller, and have the same PCI Vendor ID and Device ID.Supported Hypervisors
The Subscriber-Aware Load Balancer supports the following hypervisors for version S-Cz10.0.0:
- KVM (the following versions or later)
- Linux kernel version: 3.10.0-1127
- Library: libvirt 4.5.0
- API: QEMU 4.5.0
- Hypervisor: QEMU 1.5.3
- VMware: vSphere ESXi (Version 6.5 or later)
Supported Public Cloud Platforms
You can run the S-Cz10.0.0 Subscriber-Aware Load Balancer over the following public cloud platforms.
- Oracle Cloud Infrastructure (OCI)
OCI Cloud Shapes and options supported by this release are listed below. After deployment, you can change the shape of your machine by, for example, adding disks and interfaces.
Shape OCPUs/VCPUs vNICs Tx/Rx Queues Max Forwarding Cores DoS Protection Memory VM.Optimized3.Flex-Small 4/8 4 8 6Foot 1 Y 16 VM.Optimized3.Flex-Medium 8/16 8 15 14Foot 2 Y 32 VM.Optimized3.Flex-Large 16/32 16 15 15 Y 64 Footnote 1 This maximum is 5 when using DoS Protection
Footnote 2 This maximum is 13 when using DoS Protection
Networking using image mode [SR-IOV mode - Native] is supported on OCI. PV and Emulated modes are not currently supported.
Note:
Although the VM.Optimized3.Flex OCI shape is flexible, allowing you to choose from 1-18 OCPUs and 1-256GB of memory, the vSBC requires a minimum of 4 OCPUs and 16GB of memory per instance on these Flex shapes. - Amazon Web Services (EC2)
This table lists the AWS instance sizes that apply to the Subscriber-Aware Load Balancer.
Instance Type Max NICs Memory (GB) vCPUs c5.xlarge* 4 8 4 c5.2xlarge 4 16 8 c5.4xlarge 8 32 16 c5n.xlarge 4 10.5 4 c5n.2xlarge 4 21 8 c5n.4xlarge 8 42 16 * — Hyperthreading must be enabled for this shape.
Note:
C5 instances use the Nitro hypervisor.Note:
ENA is supported on the C5/C5n family. - Google Cloud Platform
The following table lists the GCP instance sizes that you can use for the Subscriber-Aware Load Balancer.
Table 1-1 GCP Machine Types
Machine Type vCPUs Memory (GB) vNICs Egress Bandwidth (Gbps) Max Tx/Rx queues per VM n2-standard-4 4 16 4 10 4 n2-standard-8 8 32 8 16 8 n2-standard-16 16 64 8 32 16 Use the n2-standard-4 machine type if you're deploying an Subscriber-Aware Load Balancer that requires one management interface and only two or three media interfaces. Otherwise, use the n2-standard-8 or n2-standard-16 machine types for an Subscriber-Aware Load Balancer that requires one management interface and four media interfaces. Also use the n2-standard-8 or n2-standard-16 machine types if deploying the Subscriber-Aware Load Balancer in HA mode.
Before deploying your Subscriber-Aware Load Balancer, check the Available regions and zones to confirm that your region and zone support N2 shapes.
On GCP the Subscriber-Aware Load Balancer must use the virtio network interface card. The Subscriber-Aware Load Balancer will not work with the GVNIC
OpenStack Compatibility
Oracle distributes Heat templates for the Newton and Pike versions of OpenStack. Download the source, nnSCZ1000p1_HOT.tar.gz, and follow the OpenStack Heat Template instructions.
The nnSCZ1000p1_HOT.tar.gz file contains two files:
- nnSCZ1000p1_HOT_pike.tar
- nnSCZ1000p1_HOT_newton.tar
Use the Newton template when running either the Newton or Ocata versions of OpenStack. Use the Pike template when running Pike or a later version of OpenStack.
Platform Hyperthreading Support
Some platforms support SMT and enable it by default; others support SMT but don't enable it by default; others support SMT only for certain machine shapes; and others don't support SMT. Check your platform documentation to determine its level of SMT support.
DPDK Reference
The Subscriber-Aware Load Balancer relies on DPDK for packet processing and related functions. You may reference the Tested Platforms section of the DPDK release notes available at https://doc.dpdk.org. This information can be used in conjunction with this Release Notes document for you to set a baseline of:
- CPU
- Host OS and version
- NIC driver and version
- NIC firmware version
Note:
Oracle only qualifies a specific subset of platforms. Not all the hardware listed as supported by DPDK is enabled and supported in this software.The DPDK version used in this release is:
- 23.11