1 Oracle SDM Cloud Deployment Overview

The Oracle® Session Delivery Management Cloud (Oracle SDM Cloud) consists of two components that interact with one another to provide the service. These components are the Oracle SDM Cloud services and the Management Cloud Engine (MCE). The Oracle SDM Cloud service resides in the Oracle Cloud, while the MCE resides on premises. You can install the MCE, a Podman image, on a Virtual Machine.
  • MCE: The MCE provides the protocol conversion from legacy Network Function (NF) to cloud centric REST-based APIs. MCE is deployed in its own container and you can deploy multiple instances of MCE. MCE is completely stateless. When it registers with Oracle SDM Cloud, the Unified Management Service (UMS) provide each MCE with instructions for load balancing of polling events, processing traps, and managing NFs.

The following image shows an example Oracle SDM Cloud setup interacting with the MCE component.This diagram depicts an example of the Oracle SDM Cloud and the MCE interacting.

On-Premises Software Compatibility

For up to date information regarding on-premises software compatibility between Oracle® Session Delivery Management Cloud (Oracle SDM Cloud) and Management Cloud Engine (MCE), see the Oracle SDM Cloud What's New guide.

Version Requirements for External Components

The Oracle® Session Delivery Management Cloud (Oracle SDM Cloud) requires the following versions, at minimum, for components external to the Oracle Cloud.

Management Cloud Engine

The following values reflect the minimum value for one MCE. For additional instances, you will need the appropriate resources.
  • CPUs—4
  • Memory—8GB
  • Disk—24GB
  • Interfaces—2
    • Throughput—1Gbps NIC capacity
  • Podman v4.4.1 or higher
  • Oracle Linux 8.8 or higher or Red Hat Compatible Kernel

    Note:

    The latest version of Oracle SDM Cloud is not tested on Red Hat Enterprise Linux (RHEL) and Oracle recommends using the base version of Linux on the 8.x release.
  • Perl v5.26.3 or higher

MCE Deployment, Management, and Work Flow

When you deploy the Management Cloud Engine (MCE), you must run the supplied scripts to install, configure, activate, decativate, and uninstall the service. Oracle provides a unique set of scripts for MCE, and packs them all in the archive.tgz file that you download from either Oracle Software Delivery Cloud or My Oracle Support. The download creates the following directory tree on the host.

Directory tree:
mce-<version>.<build>
mce-<version>.<build>/mce/
mce-<version>.<build>/mce/perl/ 
mce-<version>.<build>/mce/perl/activate.pl
mce-<version>.<build>/mce/perl/config.pl 
mce-<version>.<build>/mce/perl/deactivate.pl 
mce-<version>.<build>/mce/perl/uninstall.pl
mce-<version>.<build>/mce/cfg/ 
mce-<version>.<build>/mce/ssl/
mce-<version>.<build>/mce/log/
mce-<version>.<build>/mce/img/
mce-<version>.<build>/mce/img/mce.tar 
mce-<version>.<build>/mce/.version 
mce-<version>.<build>/mce/.build 
mce-<version>.<build>/install.pl
The initial installation process for the MCE includes running the scripts in the following order:
  1. Install
  2. Configure
  3. Activate
    After the initial installation you can use the various scripts to manage the MCE, as follows:
    • Reconfigure and reactivate the installed version of the MCE.
    • Deactivate and reactivate the existing configuration.
    • Uninstall the MCE.

Enable Communication Between the Oracle SDM Cloud and SBCs

When adding an SBC to the Oracle® Session Delivery Management Cloud (Oracle SDM Cloud) as a device, the SBC must use the Management Cloud Engine (MCE) to communicate with the Oracle SDM Cloud. In order to enable this communication, you must add the MCE to the SBC's SNMP community and as a trap receiver target.

Note:

For each MCE configured, you must configure a corresponding entry in the SBC's snmp-community and trap-receiver configurations. This includes redundancy pairs.

For more information on adding the SBC as a device, see https://docs.oracle.com/en/industries/communications/session-delivery-management-cloud/userguide/device-manager.html#GUID-9472A394-416E-4C48-9AAB-0FA8FFF144FE.

The following is a sample configuration of a device running ECZ810m1, which supports both SNMP v1 and v2. Enter the IP address of the MCE that is current registered with the Oracle SDM Cloud and the community name you use when adding the device to the Oracle SDM Cloud. 
ecz25# configure terminal
ecz25(configure)# system
ecz25(system)# snmp-community
ecz25(snmp-community)# ip-addresses 15.122.0.00
ecz25(snmp-community)# community-name mce
ecz25(snmp-community)# done
snmp-community
        community-name               mce
        access-mode                  READ-ONLY
        ip-addresses                 15.122.0.00
        last-modified-by             admin@15.122.0.00
        last-modified-date           2021-01-20 22:28:31
The following sample configuration shows the user adding the MCE's IP address to the SBC's trap-receiver configuration. During MCE installation, you are prompted to enter the trap reciever port for the MCE. This value must be the same on both the device and the MCE. The default value is 162.
ecz235# configure terminal
ecz235(configure)# system
ecz235(system)# trap-receiver
ecz235(trap-receiver)# ip-address 15.122.0.00
ecz235(trap-receiver)# filter-level Major
ecz235(trap-receiver)# community-name mce
ecz235(trap-receiver)# done
trap-receiver
        ip-address                15.122.0.00:162
        filter-level              Major
        community-name            mce
        last-modified-by          admin@15.122.0.00
        last-modified-date        2021-01-20 22:40:31