1. Platform Preparation and Installation Guide
  2. Session Delivery Products as Virtual Machines

6 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.

Support for the OCSBC and OCSR as VMs is the same. This document refers to the OCSBC, but applies equally to the OCSR.

VM deployment types include:

  • A standalone (not orchestrated) instance Oracle Communications Session Border Controller operating as a virtual machine running on a hypervisor
  • Virtual Machine(s) deployed within an Orchestrated Network Functions Virtualization (NFV) environment
  • Virtual Machine(s) deployed within private or public Cloud environments

Standalone SBC VM deployment instances supported for all platforms. Support within an orchestrated environment is dependent on orchestrator and SBC version. High Availability configurations are supported by both deployment types.

You can enable the SBC to utilize CPU hyperthreading, also called SMT. Considerations include your environment's support of the feature and its impact on your implementation. A key consideration beyond support is the ability of your platform to provide information on sibling CPUs to the SBC . You configure hyperthreading after installation.

VLAN Support

Oracle recommends that you evaluate the VLAN support of your deployment's hypervisor and interface I/O mode before implementation to ensure secure support for the transmission and receiving of VLAN-tagged traffic. Please consult your hypervisor’s vendor documentation for details.

Refer to the ACLI Configuration Guide for instructions on configuring VLANs on the SBC. Note that when you configure a VLAN, the SBC requires VLAN tags to be included in the packets delivered to and from the VM.

Hypervisor and cloud platform and resource requirements are version-specific. Refer to your Release Notes for applicable requirements, recommendations and caveats for qualified platforms.