Virtual Machine Platform Resources
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 VM Resources
VM resource configuration defaults to the following:
- 4 CPU Cores
- 8 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 for Private Virtual Infrastructures
The OCCSM 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 for Private Virtual Infrastructures
- Para-virtualized
- SR-IOV
- PCI Passthrough
- Emulated - Emulated is supported for management interfaces only.
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.
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 supported on VMware only.
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 |
|---|---|---|
| Emulated | e1000 | W |
| KVM (PV) | virtio | W/M |
| Hyper-V (PV) | NetVSC | M |
| VMware (PV) | VMXNET3 | W/M |
Emulated NICs do not provide sufficient bandwidth/QoS, and are suitable for use as management only.
- 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 or XEN when running on Private Virtual Infrastructures.CPU Core Resources
The OCCSM S-CZ9.1.5 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, for qemu for example, Oracle recommends that you set the deployment to pass the full set of host CPU features to the VM.
DPDK Reference
The OCCSM 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:
- 20.11.2