Virtual Machine Platform Requirements
A Virtual Network Function (VNF) requires the CPU core, memory, disk size, and network interfaces specified for operation. Deployment details, such as the use of distributed DoS protection, dictate resource utilization beyond the defaults. .
Default vSBC Resources
The default compute for the SLB image files is as follows:
- 8 vCPU Cores
- 32 GB RAM
- 40 GB hard disk (pre-formatted)
- 8 interfaces as follows:
- 1 for management (wancom0 )
- 2 for HA (wancom1 and 2)
- 1 spare
- 4 for media
Minimum VNF Resources
VM resource configuration defaults to the following:
- 4 vCPU Cores
- 8 GB RAM
- 20 GB hard disk (pre-formatted)
- 4 interfaces as follows:
- 1 for management (wancom0 )
- 1 for HA (wancom1)
- 2 for media
Interface Host Mode
The SLB S-Cz9.3.0 VNF supports interface architectures using Hardware Virtualization Mode - Paravirtualized (HVM-PV):
- ESXi - No manual configuration required.
- KVM - HVM mode is enabled by default. Specifying PV as the interface type results in HVM plus PV.
Supported Interface Input-Output Modes
- Para-virtualized
- SR-IOV
- PCI Passthrough
Supported Ethernet Controller, Driver, and Traffic Type based on Input-Output Modes
The following table lists supported Ethernet Controllers (chipset families) and their supported driver that Oracle supports for Virtual Machine deployments. Reference the host hardware specifications, where you run your hypervisor, to learn the Ethernet controller in use. The second table provides parallel information for virtual interface support. Refer to the separate platform benchmark report for example system-as-qualified performance data.
Note:
Virtual SBCs 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.For KVM and VMware, accelerated media/signaling using SR-IOV and PCI-pt modes are supported for the following card types.
| Ethernet Controller | Driver | SR-IOV | PCI Passthrough |
|---|---|---|---|
| Intel 82599 / X520 / X540 | ixgbe | M | M |
| Intel i210 / i350 | igb | M | M |
| Intel X710 / XL710 | i40e | M | M |
| Intel X710 / XL710 / XXC710 | i40enFoot 1 | M | M |
| Mellanox Connect X-4 | mlx5 | M | M |
Footnote 1 This driver is not supported on KVM.
For PV mode (default, all supported hypervisors), the following virtual network interface types are supported. You can use any make/model NIC card on the host as long as the hypervisor presents it to the VM as one of these vNIC types.
| Virtual Network Interface | Driver | W/M |
|---|---|---|
| KVM (PV) | virtio | W/M |
| VMware (PV) | VMXNET3 | W/M |
- W - wancom (management) interface
- M - media interface
Note:
Accelerated media/signaling using SR-IOV (VF) or PCI-pt (DDA) modes are not currently supported for Hyper-V when running on Private Virtual Infrastructures.CPU Core Resources
The SLB S-Cz9.3.0 VNF requires an Intel Core7 processor or higher, or a fully emulated equivalent including 64-bit SSSE3 and SSE4.2 support .
If the hypervisor uses CPU emulation (for example, qemu), Oracle recommends that you set the deployment to pass the full set of host CPU features to the VM.