Interface Considerations For Vm Platforms; Software Adaptations For Physical Interfaces; Cots Interfaces - Oracle Netra Server X5-2 Installation Manual

10

Interface Considerations for VM Platforms

Oracle Communications Session Border Controller management and media traffic use
separate network interfaces to connect to networks. The user configures these interfaces'
properties, and then adapts other configuration elements to those interfaces. This
configuration requires an understanding of the platform's mechanisms for using interfaces as
well as the properties they can configure, as presented in this section.

Software Adaptations for Physical Interfaces

Having been installed on a virtual machine, Oracle Communications Session Border
Controller (OCSBC) physical interface configuration elements provide for the applicable
properties and same statistics measurements as are available for Acme Packet platform
interfaces. With the exception of the MACTAB file, the abstraction of these elements from
those physical ports is transparent to the user.
The user must independently understand the bus or virtual network paths used by their
hardware to access physical ports. Refer to your hardware or virtual machine documentation
for information about proper configuration and operation related to, for example, physical port
location and speed. The user must consider these system and physical details when
configuring OCSBC phy-interface elements, which is documented in the ACLI Configuration
Guide.
Media Interface Consideration
The template Oracle provides for VM deployment selects the correct interface detail for both
management and media interfaces during deployment. If you are using a manual deployment
approach or you wish to change interface selection after deployment, Use either Paravirtual,
PCI-pt or SR-IOV I/O mode for media interfaces.
Note:
Prior to version S-Cz8.3.0m1p10, the OCSBC required emulated NICs for
management interfaces

COTS Interfaces

Physical interfaces on COTS platforms are defined by the platform, with bussing and driver
access fully independent of the Oracle Communications Session Border Controller. Utilization
of COTS interfaces by the Oracle Communications Session Border Controller is the same as
with VM interfaces. The Oracle Communications Session Border Controller extracts physical
interface MAC addressing from the platform and maps it to Oracle Communications Session
Border Controller configuration naming syntax to direct network traffic to physical interfaces
based on the type of service they support.
10-1