2 Oracle SDM Cloud Deployment Process and Procedures
- Oracle SDM Cloud Deployment Process
- Establish an Oracle SDM Cloud Service Subscription
- Login to Oracle SDM Cloud to obtain inputs for Management Cloud Engine (MCE)
- Establish a site with the Oracle SDM Cloud's Registration ID to which the Management Cloud Engine (MCE) can connect
- Install, Configure, and Activate the MCE
Oracle SDM Cloud Deployment Process
- Oracle Cloud—Contact your Oracle Cloud sales representative to establish a subscription for Oracle SDM Cloud and activate your Oracle Cloud and Oracle Identity Cloud Services accounts.
- Oracle Cloud—Login to Oracle SDM Cloud and obtain the Identity and Access Management (IAM) for inputs to Management Cloud Engine (MCE).
- Oracle Cloud—While logged into Oracle SDM Cloud, create a site. Once created, select the site to edit and obtain the generated site Registration ID to use for MCE inputs.
- On premises—Install the Management Cloud Engine (MCE) with the
install, activate, and configuration scripts provided in the software
download.
The following diagram illustrates the deployment process and shows the parameters you need to set in each Oracle SDM Cloud component to establish the service.
Supported Regions
Oracle® Session Delivery Management Cloud (Oracle SDM Cloud) supports deployment in two OCI Regions, Ashburn (IAD) and Frankfurt (FRA).
Within these two regions, users select a home region, which is where IAM resources are defined.
Oracle SDM Cloud supports the IAM domain home region to any of the following Ashburn deployment regions.
| Region Name | Region Location |
|---|---|
| Canada Southeast (Montreal) | Montreal, Canada |
| Canada Southeast (Toronto) | Toronto, Canada |
| US East (Ashburn) | Ashburn, VA |
| US West (Phoenix) | Phoenix, AZ |
| US West (San Jose) | San Jose, CA |
Oracle SDM Cloud supports the IAM domain home region to any of the following Frankfurt deployment regions.
| Region Name | Region Location |
|---|---|
| Germany Central (Frankfurt) | Frankfurt, Germany |
| Netherlands Northwest (Amsterdam) | Amsterdam, Netherlands |
| Switzerland North (Zurich) | Zurich, Switzerland |
Establish an Oracle SDM Cloud Service Subscription
To obtain the Oracle® Session Delivery Management Cloud (Oracle SDM Cloud) service, contact Oracle Cloud Sales to purchase a Cloud Services Agreement and the Oracle SDM Cloud service description.
- Go to https://docs.oracle.com/en/cloud/paas/identity-cloud/index.html for information about how to purchase a subscription to Oracle SDM Cloud.
- Go to https://docs.oracle.com/en/cloud/get-started/subscriptions-cloud/index.html for information about how to activate your Oracle Applications account order.
- Go to https://www.oracle.com/webfolder/technetwork/tutorials/obe/cloud/getting_started/create_cloud_account_admin_obe/create_cloud_acc_admin.html for information about how to manage your Oracle Cloud services.
Obtain the IAM Inputs for MCE
Create a Site and Retrieve Generated ID for MCE Inputs
MCE Host Installation
The host VM running the Management Cloud Engine (MCE) must use Oracle Linux 9.x as its operating system.
- Download the Oracle Linux 9 ISO.
- Log in to Oracle Software Delivery Cloud.
- Search for Oracle Linux.
- Select REL: Oracle Linux 9 (latest)
- Set Platform to x86 64 bit.
- Download the ISO.
- Upload the downloaded ISO to the ESXi datastore.
- In the ESXi host client, open Storage (or Datastore browser, depending on version).
- Upload the downloaded OL9 ISO to a location such as the datastore ISO folder.
- Create a new virtual machine.
- Log in to the VMware Host Client.
- Navigate to Virtual Machines, Create / Register VM (or Create a VM, depending on version).
- Select Create a new virtual machine and provide values in the following fields:
- Name—Enter a meaningful name for the VM.
- Guest OS Family—Enter Linux.
- Guest OS Version—Enter Oracle Linux 9 (64-bit)
- Storage type—Select Standard.
- Datastore—Select the datastore where you uploaded the ISO.
- Configure Virtual hardware as required for your deployment.
- Attach the ISO.
- Set CD/DVD Drive to Datastore ISO file.
- Browse to and select the uploaded Oracle Linux 9 ISO
- Ensure Connect at Power on is selected.
This opens the installation page.
- Install Oracle Linux 9.
- Power on the VM.
- In the console, select Install Oracle Linux 9.
- Follow the installer, using defaults unless otherwise required.
- Select your software.
- Open Software Selection.
- Under Base Environment, select Server.
- Under Additional Software, select Remote Management for Linux.
- Select Done.
- Configure installation destination and partitioning.
- Open Installation Destination.
- Select Custom storage configuration and select Done.
- Under Manual Partitioning, use the plus (+) icon to create the required mount points, and select Done.
- Confirm any partitioning changes when prompted.
- Perform network configuration (recommended before installation)
- Open Network & Host Name.
- Enter the Host Name.
- Set the network interface to On.
- Click Configure and set your required IPv4 details.
- Ensure connectivity by configuring the following fields:
- DNS Servers
- Search domains (under the IPv4 Settings tab)
- Select Save, then Done.
- Begin the installation.
- Click Begin Installation.
- Complete any required prompts (for example, set root password or create an admin user), if requested.
- After installation completes, reboot and log in.
Configure Two Network Interfaces
You can configure two NICs (LAN and WAN) either before installing Oracle Linux 9 (recommended) or after.
- In the ESXi Host Client, select the VM and click Edit (Edit settings).
- Click Add other device, Network Adapter (or Add network adapter).
- Configure the second adapter with the name Network Adapter 2 and enter any required details.
- Select Save.
- Assign the new IP to the interface using the following command:
sudo ifconfig <INTERFACE_NAME> 192.x.x.x netmask 255.x.x.x up - Use the ifconfig command to verify the new interface is added.
Using Base Environment: Server with Additional software: Remote Management for Linux installs key components that commonly include Podman, Perl, and SNMP utilities, along with other base and management packages.
| Purpose/Function | Key Packages (Examples) |
|---|---|
| Base system | glibc, coreutils, util-linux, bash, filesystem |
| Remote management | cockpit*, openssh*, sssd*, realmd, net-snmp* |
| Automation | ansible-core, dnf*, yum |
| Cloud/Container | podman*, buildah, open-vm-tools, virt-what |
| Device/storage/tools | lvm2*, xfsprogs, udisks2*, device-mapper* |
| Security/SELinux | selinux-policy*, firewalld, audit*, rsyslog* |
| Monitoring | sos, tuned, strace, procps-ng |
| Python & Perl | python3*, perl* |
| Compression/utility | tar, unzip, zip, rsync, wget |
| Internal libraries | libgcc, zlib, libstdc++, libxml2, openssl-libs |
Note:
Package names may vary slightly by update level and repository configuration.Install and Configure the MCE
The Management Cloud Engine (MCE) installation procedure requires the archive file containing the installation and configuration scripts that you downloaded from Oracle onto your host hardware. Oracle recommends running the two scripts consecutively in one session the first time you install the MCE. For that reason, this procedure includes the prerequisites and steps for running both scripts.
Do the following before performing the procedure.
- Ensure that the host meets Operation System and resource requirements.
- Operating System Oracle Linux 9 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 9.x release. - Install Perl V5.32.1 or higher on the host.
- Install Podman v5.4.0 or higher on the host.
- Download the archive file (mce-<version>.tgz) from My Oracle Support (MOS) to the host server. This .tgz file includes all necessary scripts.
Note:
MCE activation, configuration, and deactivation no longer require root privileges. Root access remains mandatory for the installation, uninstallation, and upgrades.
- Ensure that there is no MCE installation existing on the hardware. See the last step in this procedure for instructions.
- Ensure that you have root access.
- Note the MCE WAN IP, MCE LAN IP, and MCE name.
- Navigate to Oracle® Session Delivery Management Cloud (Oracle SDM Cloud) Security Manager, IAM page to configure IAM parameters.
Procedure
Note:
Before re-installing, you must first uninstall the existing MCE.Traffic Flow and Firewall Port Recommendations
The following table provides traffic flow and firewall port recommendations for communication between the Management Cloud Engine (MCE) and Network Functions (NFs).
| Port Number | Protocol | Service | Configurable | Purpose |
|---|---|---|---|---|
| 161 | UDP | SNMP | Y | SNMP traffic between the MCE and the NF. |
| 162 | UDP | SNMP | Y | SNMP trap reporting from the device to the MCE server. |
| 22 | TCP | SFTP/SSH | N | Used for secure file transfer (for example, software upgrades, Route Manager, and LRT updates) and SSH sessions between MCE and southbound NFs. |
| 3001/3000 | TCP | ACP/ACLI | N | Used by the MCE to communicate with all versions of a NF. |
| 443 | TCP | HTTPS | N | Usec by MCE to communicate with Media Engines (MEs). |
Upgrading the MCE
The Management Cloud Engine (MCE) upgrade procedure requires the archive file containing the installation and configuration scripts that you downloaded from Oracle onto your host hardware. For more information on the installation and configuration scripts and prerequisites, see "Install and Configure the MCE".
Use the following procedure to upgrade the MCE using the upgrade.pl.
- Log onto the server as a root user and ensure the user logging in has the proper Linux permissions.
- Shut down the existing version of MCE by running the
deactivate.pl
script.
/opt/oracle/mce/perl/deactivate.pl - Install the latest version of the MCE (provided by development) from MOS.
- Unpack the new mce-<version>.<build>.tgz
archive.
[root@cgbu-phx-604 perl]# tar -xvf mce<version>.<build>.tgz - Run the upgrade.pl script (under the new
mce-<version>.<build>/) to upgrade to the
latest version.
[root@cgbu-phx-604 perl]# ./upgrade.plThe upgrade.pl script displays a banner with information about the new MCE version.
The MCE performs the following validations to ensure the upgrade is supported and valid:- Validation that an existing version of MCE exists under
/opt/oracle/mce. - Validation that MCE is not currently activated.
- Validation that the upgrade path is supported.
- Validation that an existing version of MCE exists under
- Once validation is complete, the user is prompted to continue. Either continue or opt out to abort the upgrade.
- Run the activate.pl script under
/opt/oracle/mce/perl script to activate the new
version of MCE
.
[root@cgbu-phx-604 perl]# ./activate.pl
Persistent data files, including configuration properties and artifacts
generated when MCE registers with Oracle SDM Cloud, are copied from the old installation of MCE to the new installation. During
installation, the old installation of MCE gets moved from /opt/oracle/mce
to /opt/oracle/mce.bak and the new version is moved to
/opt/oracle/mce.
Use the following procedure to upgrade the MCE performing a fresh installation.
- Log onto the server as a root user and ensure the user logging in has the proper Linux permissions.
- Shut down the existing version of MCE by running the deactivate.pl
script.
/opt/oracle/mce/perl/deactivate.pl - Upgrade the operating system from Oracle Linux 7 to Oracle Linux
8.8.
From Oracle Linux 8:
- Log onto the server as a root user and ensure the user logging in has the proper Linux permissions.
- Unpack the new mce-<version>.<build>.tgz archive. The system installs the files in the /opt/oracle/mce directory.
- Run the install.pl script.
Upon installation, the system checks for an existing MCE instance in Podman and if one exists, the script execution stops and you must uninstall the MCE.[root@cgbu-phx-604 mce-25.2.0.0.0]# ./install.pl ------------------------------------------------------------------------------- Oracle Cloud Communications Service,(c) 2020 Oracle MCE v25.2.0.0.0 install.pl @ 2023-12-10 16:58:00 ------------------------------------------------------------------------------- Checking pre-conditions... Ok. Proceed with install (y/n) : y Installing mce to /opt/oracle ... Installation successful.This creates the /oracle/mce directory under /opt. If an Oracle directory already exists, the install creates a MCE directory only.
- Run the config.pl script from the
/opt/oracle/mce/perl directory and configure the attributes according to your
environment.
[root@cgbu-phx-604 perl]# ./config.pl ------------------------------------------------------------------------------- Oracle Cloud Communications Service, (c) 2020 Oracle MCE v25.2.0.0.0 @ 2023-12-10 16:58:35 ------------------------------------------------------------------------------- Checking pre-conditions... The following inputs are required for MCE to register with Oracle SDM Cloud: MCE Host Name : cgbu-phx-604 Host WAN IP Address : 100.77.50.195 Host LAN IP Address : 10.196.248.92 Oracle SDM Cloud FQDN : <From IAM page> Oracle SDM Cloud tenant ID : <From IAM page> IDCS tenant ID : <From IAM page> IDCS FQDN : <From IAM page> MCE IDCS client ID : <From IAM page> MCE IDCS client secret : <From IAM page> Oracle SDM Cloud Site ID : <From Device manager → Sites> Enable proxy (y/n) : y Proxy server address : 100.77.50.145 Proxy server port : 3128 -------------------------------------------------------------------- The following inputs are required for MCE KeyStore configuration: MCE TLS Key Store Password : MCE TLS Key Store Password confirm : -------------------------------------------------------------------- The following inputs are required for MCE operation: Trap Receiver Port : 162 -------------------------------------------------------------------- Ready to process inputs Proceed with configuration (y/n) : y Encrypting data ... Generating local mce.properties... Success.This creates a mce.properties file under /opt/oracle.mce/cfg, which contains all of the information entered in config.pl.
- Login to the Oracle SDM Cloud interface and delete the registered MCE from Device Manager. For more information, see "Device Manager" in the User Guide.
- Run the activate.pl script from /opt/oracle.mce/perl to activate the MCE.
[root@cgbu-phx-604 perl]# ./activate.pl ------------------------------------------------------------------------------- Oracle Cloud Communications Service, (c) 2020 Oracle MCE v25.2.0.0.0 @ 2023-12-10 17:01:15 ------------------------------------------------------------------------------- Checking pre-conditions... Ok. MCE tomcat port:7070, Trap receiver port:2000 Proceed with activate (y/n) : y Activating container mce... Start to run container mce, image id 1cb6109fc65a ... Container mce with image id 1cb6109fc65a started. Activation successful! - Optionally, you can check your work with Podman.
- List the MCE instances by typing podman images at
the prompt and pressing Enter. Under TAG, look
for <version> <build> to see the new installation. The following
code block shows an
example:
% podman images REPOSITORY CREATED SIZE TAG IMAGE ID cne-repos1.us.oracle.com:7744/apps/cgbu/ums/mce 1.0.0 fb90a2c4b930 4 days ago 434MB - List the running images by typing podman ps at
the prompt and pressing Enter. In the list, under
NAMES, look for mce. Under STATUS, look for the newest images. The
following code block shows an
example:
% podman ps CONTAINERID IMAGE COMMAND CREATED STATUS PORT NAMES % podman psIMAGECOMMANDCREATEDSTATUSPORTS ed6f90a7993dfb90a2c4b930"/bin/bash./start.sh" 3 days ago mce
- List the MCE instances by typing podman images at
the prompt and pressing Enter. Under TAG, look
for <version> <build> to see the new installation. The following
code block shows an
example:
Restore MCE Directory and Run Upgrade.pl
Oracle recommends upgrading the Management Cloud Engine (MCE) directory and running upgrade.pl to upgrade the MCE.
- Log onto the server as a root user and ensure the user logging in has the proper Linux permissions.
- Shut down the existing version of MCE by running the deactivate.pl script.
/opt/oracle/mce/perl/deactivate.pl - Create a backup of the MCE directory and save it in a safe location where it is easily accessible.
- Upgrade the operating system from Oracle Linux 8 to Oracle Linux 9 using the procedure detailed in MCE Host Installation.
- Log onto the server as a root user and ensure the user logging in has the proper Linux permissions.
- Install Podman version 5.4.0 or higher.
- Restore your backup of the MCE directory to
/opton Oracle Linux 9. This is the backup created above in step 3.tar -xvf <SAFE_LOCATION>/mce_ol8.tar -C /opt/ - Unpack the new mce-<version>.<build>.tgz archive.
This creates a directory with the name
mce-<version>, which contains the upgrade.pl script. - Run the upgrade.pl script. The following procedure uses release 26.1.0.0.0 as an example for upgrade.
The upgrade.pl script displays a banner with information about the new MCE version.[root@acme18 mce-26.1.0.0.0]# ./upgrade.pl ------------------------------------------------------------------------------- Oracle Cloud Communications Service, (c) 2020 Oracle MCE v26.1.0.0.0 upgrade.pl @ 2023-12-10 15:35:59 ------------------------------------------------------------------------------- Checking pre-conditions... Upgrade from 25.2.0.0.0 to 26.1.0.0.0 is supported. Ok. Proceed with upgrade (y/n) : y Backup... Installing... Importing... Upgrading configuration to 26.1.0.0.0 ... The following inputs are required for MCE to register with Oracle SDM Cloud: Host WAN IP Address : 100.77.18.47 Host LAN IP Address : 100.77.18.47 Success.The MCE performs the following upgrade validations:
- Validates that an existing version of MCE exists under
/opt/oracle/mce. - Validates that MCE is not currently activated.
- Validates that the upgrade path is supported.
- Validates that an existing version of MCE exists under
- Once validation is complete, you are prompted to continue. Either continue or opt out to cancel the upgrade.
- Run the activate.pl script under
/opt/oracle/mce/perlto activate the new version of MCE.The following upgrade procedure uses 26.1.0.0.0 as an example.
[root@cgbu-phx-604 perl]# ./activate.pl ------------------------------------------------------------------------------- Oracle Cloud Communications Service, (c) 2020 Oracle MCE v26.1.0.0.0 @ 2023-12-10 16:00:15 ------------------------------------------------------------------------------- Checking pre-conditions... Ok. MCE tomcat port:7070, Trap receiver port:2000 Proceed with activate (y/n) : y Activating container mce... Start to run container mce, image id 1cb6109fc65a ... Container mce with image id 1cb6109fc65a started. Activation successful!
Persistent data files, including configuration properties and artifacts generated when MCE registers with Oracle SDM Cloud, are copied from the old installation of MCE to the new installation. During installation, the old installation of MCE gets moved from /opt/oracle/mce to /opt/oracle/mce.bak and the new version is moved to /opt/oracle/mce.
Perform a Clean Installation
While Oracle recommends upgrading the Management Cloud Engine (MCE) directory and running upgrade.pl to upgrade the MCE, you can also perform a clean installation.
- Log onto the server as a root user and ensure the user logging in has the proper Linux permissions.
- Shut down the existing version of MCE by running the deactivate.pl script.
/opt/oracle/mce/perl/deactivate.pl - Upgrade the operating system from Oracle Linux 8 to Oracle Linux 9 using the procedure detailed in MCE Host Installation.
- Log onto the server as a root user and ensure the user logging in has the proper Linux permissions.
- Unpack the new
mce-<version>.<build>.tgzarchive.tar -xvzf mce-<version>.build.tgz - Run the install.pl script.
Upon installation, the system checks for an existing MCE instance in Podman and, if one exists, the script execution stops and you must uninstall the MCE.[root@cgbu-phx-604 mce-26.1.0.0.0]# ./install.pl ------------------------------------------------------------------- Oracle Cloud Communications Service,(c) 2020 Oracle MCE v26.1.0.0.0 install.pl @ 2023-12-10 16:58:00 ------------------------------------------------------------------- Checking pre-conditions... Ok. Proceed with install (y/n) : y Installing mce to /opt/oracle ... Installation successful.This creates the
/oracle/mcedirectory under/opt. If an Oracle directory already exists, the install creates a MCE directory only. - Run the config.pl script from the
/opt/oracle/mce/perldirectory and configure the attributes according to your environment.[root@cgbu-phx-604 perl]# ./config.pl ----------------------------------------------------------------- Oracle Cloud Communications Service, (c) 2020 Oracle MCE v26.1.0.0.0 @ 2023-12-10 16:58:35 ----------------------------------------------------------------- Checking pre-conditions... The following inputs are required for MCE to register with Oracle SDM Cloud: MCE Host Name : cgbu-phx-604 Host WAN IP Address : 100.77.50.195 Host LAN IP Address : 10.196.248.92 Oracle SDM Cloud FQDN : <From IAM page> Oracle SDM Cloud tenant ID : <From IAM page> IDCS tenant ID : <From IAM page> IDCS FQDN : <From IAM page> MCE IDCS client ID : <From IAM page> MCE IDCS client secret : <From IAM page> Oracle SDM Cloud Site ID : <From Device manager → Sites> Enable proxy (y/n) : y Proxy server address : 100.77.50.145 Proxy server port : 3128 ------------------------------------------------------------------ The following inputs are required for MCE KeyStore configuration: MCE TLS Key Store Password : MCE TLS Key Store Password confirm : ------------------------------------------------------------------ The following inputs are required for MCE operation: Trap Receiver Port : 162 -------------------------------------------------------------------- Ready to process inputs Proceed with configuration (y/n) : y Encrypting data ... Generating local mce.properties... Success.This creates a mce.properties file under
/opt/oracle/mce/cfg, which contains all of the information entered in config.pl. - Log in to the Oracle SDM Cloud interface and delete the registered MCE from Device Manager. For more information, see Device Manager in the User Guide.
- Run the activate.pl script from /opt/oracle/mce/perl to activate the MCE.
[root@cgbu-phx-604 perl]# ./activate.pl ----------------------------------------------------------------- Oracle Cloud Communications Service, (c) 2020 Oracle MCE v26.1.0.0.0 @ 2023-12-10 17:01:15 ------------------------------------------------------------------ Checking pre-conditions... Ok. MCE tomcat port:7070, Trap receiver port:2000 Proceed with activate (y/n) : y Activating container mce... Start to run container mce, image id 1cb6109fc65a ... Container mce with image id 1cb6109fc65a started. Activation successful! - Optionally, you can check your work with Podman.
- List the MCE instances by typing podman images at the prompt and pressing Enter. Under TAG, look for <version> <build> to see the new installation. The following code block shows an example:
% podman images REPOSITORY CREATED SIZE TAG IMAGE ID cne-repos1.us.oracle.com:7744/apps/cgbu/ums/mce 1.0.0 fb90a2c4b930 4 days ago 434MB - List the running images by typing podman ps at the prompt and pressing Enter. In the list, under NAMES, look for MCE. Under STATUS, look for the newest images. The following code block shows an example:
% podman ps CONTAINERID IMAGE COMMAND CREATED STATUS PORT NAMES % podman psIMAGECOMMANDCREATEDSTATUSPORTS ed6f90a7993dfb90a2c4b930"/bin/bash./start.sh" 3 days ago mce
- List the MCE instances by typing podman images at the prompt and pressing Enter. Under TAG, look for <version> <build> to see the new installation. The following code block shows an example:
Note:
If the host VM’s IP address changes after upgrading from Oracle Linux 8 to Oracle Linux 9:- For each upgraded MCE, update the corresponding entries in the SBC snmp-community and trap-receiver configurations.
- Reconfigure the HDR Push receiver for Reporting Manager.
Configure MCE Behind NAT or Firewall
Oracle® Session Delivery Management Cloud (Oracle SDM Cloud) allows you to configure the Management Cloud Engine (MCE) to operate behind a Network Address Translation (NAT) or a firewall. Oracle SDM Cloud contacts the MCE using the value for the mce.ip in mce.properties or wan-ip on setting up ./config.pl configuration.
mce.ip : 10.x.x.x Note:
The MCE does not have proxy support between itself and devices.Manage MCE Traps
Oracle® Session Delivery Management Cloud (Oracle SDM Cloud) provides trap filtering at the Management Cloud Engine (MCE) level. This allows administrators to prevent specific SNMP traps from being processed based on defined criteria, such as the source IP address or the trap name.
Trap filtering is configured through a trap-filter.json file located on the MCE.
When a trap is received, MCE evaluates it against the configured filters. If the trap matches any of the specified criteria, it is excluded from further processing.
The filter configuration supports multiple source IP addresses and trap names. Administrators can enable or disable filtering by modifying the trap-filter.json file and restarting the MCE for the changes to take effect.
| Filter Type | Description |
|---|---|
| trapName | Excludes traps matching the specified trap name. Note that trap names are case-sensitive. |
| sourceIp | Excludes all traps received from the specified source IP address. Note that only IPv4 is currently supported. |
Note:
Although both are referred to as filters, MCE-level trap filters and Fault Manager filters behave differently:- MCE-level filters block matching traps from being processed or forwarded.
- Fault Manager filters allow matching traps to be forwarded to configured receivers.
For information on adding and removing trap filters at the MCE level, see Add a Trap Filter At the MCE Level and Remove a Trap Filter at the MCE Level in Getting Started.
Add a Trap Filter At the MCE Level
- Navigate to the trap filter configuration directory.
cd /opt/oracle/mce/cfg/trapfilter - Open the trap filter configuration file.
vi trap-filter.json - In the trapfilterList array, add one or more filter objects. Each object must include:
- filterType—Specifies the filter criteria (trapName or sourceIp)
- value—The corresponding trap name or source IP address to filter
For example:
{ "trapFilterList": [ { "filterType": "trapName", "value": "linkDown" }, { "filterType": "sourceIp", "value": "100.77.41.61" } ] }
- Save the file.
- Restart the MCE for the changes to take effect.
./deactivate.pl ./activate.pl
Note:
In high availability (HA) deployments, include both the primary and secondary IP addresses when configuring filters to ensure traps from both nodes are handled consistently.For additional details, examples, and validation rules, see the README file located in /opt/oracle/mce/cfg/trapfilter.
Remove a Trap Filter At the MCE Level
- Navigate to the trap filter configuration directory.
cd /opt/oracle/mce/cfg/trapfilter - Open the trap filter configuration file.
vi trap-filter.json - Locate the filter entry you want to remove in the trapFilterList array, then do one of the following:
- Delete the filter object from the array, or
- Set the value field to null.
- Save the file.
- Restart the MCE for the changes to take effect.
./deactivate.pl ./activate.pl
For additional details, examples, and validation rules, see the README file located in /opt/oracle/mce/cfg/trapfilter.