Oracle netra X5-2, Руководство по установке

Страница: 50 / 152

5
Session Delivery Products as Virtual
Machines
You can deploy version S-Cz8.3.0 of Oracle's Session Delivery Products as Virtual Machine
(VM). This document refers to Session Delivery Products generically. See your software
version's Release Notes to verify your product's support for deployment as a virtual machine.
VM deployment types include:
• A standalone (not orchestrated) instance Oracle Communications Session Border
Controller operating as a virtual machine running on a hypervisor, and
• Virtual Machine(s) deployed within an Orchestrated Network Functions Virtualization
(NFV) environment.
Standalone OCSBC VM deployment instances are always supported. Support within an
orchestrated environment is dependent on orchestrator and OCSBC version. High Availability
configurations are supported by both deployment types.
Hypervisor platform and resource requirements are version-specific. Refer to your Release
Notes for applicable requirements, recommendations, caveats for qualified platforms.
Hyper-threading and CPU Affinity
Hyper-threading can provide increased workload efficiencies in specific configurations, but
poorly designed configurations can just as easily impact performance of the OCSBC.
Due to the polling operation of DPDK, using hyper-threaded cores can significantly degrade
the OCSBC's packet processing performance. Oracle recommends you disable hyper-
threading on the host system if possible, or configure CPU affinities on the hypervisor to
ensure mapping from only one virtual CPU to each physical CPU core. Learn how to
configure CPU affinity via your hypervisor documentation.
To use hyper-threading with OCSBC, it's important that the hypervisor passes a valid CPU
map to the VM, so that OSBC has sufficient information to avoid any potential contention from
using hyper-threaded sibling cores for realtime critical processes.
In summary:
1.
Configurations that have hyperthreading disabled on the host are supported in all cases -
same for both bare metal and virtual hosts.
2.
Configurations that have hyperthreading enabled on the host are supported if the
hypervisor provides correct CPU sibling maps to the guest.
3.
Configurations that have hyperthreading enabled on the host but do not report sibling
maps to the guest are unsupported unless CPU cores are manually pinned at the
hypervisor to avoid sibling contention.
You can verify and troubleshoot the OCSBC CPU assignments using, for example, the show
datapath-config command and understanding the following guidelines:
5-1