A Virtual Network Function (VNF) requires the CPU core, memory, disk size, and network interfaces specified for operation. The Oracle® Enterprise Session Border Controller (E-SBC) uses the Intel Data Plane Development Kit (DPDK) for datapath design, which imposes specific VNF resource requirements for CPU cores. Deployment details, such as the use of distributed DoS protection, dictate resource utilization beyond the defaults.
You configure CPU core utilization from the ACLI based on your deployment. You can also define memory and hard disk utilization based on your deployment. You must configure the hypervisor with the appropriate settings prior to startup, if you need settings other than the machine defaults set by the machine template (OVA).
Default VM Resources
VM resource configuration defaults to the following:
- 4 CPU Cores
- 16 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
Interface Host Mode
The E-SBC E-CZ8.1.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.
- XEN (OVM) - The user must configure HVM+PV mode.
Note:When deploying the E-SBC over VMware and using PV interface mode, the number of forwarding cores you may configure is limited to 2, 4, or 8 cores.
CPU Core Resources
The E-SBC E-CZ8.1.0 VNF requires an Intel Core2 processor or higher, or a fully emulated equivalent including 64-bit SSSE3 and TSC support.
If the hypervisor uses CPU emulation (qemu etc), Oracle recommends that you set the deployment to pass the full set of host CPU features to the VM.