COM Overview
Introduction
What is COM?
COM is the Common Object Model. It is an authoritative, language-neutral format written in JSON that allows us to document, report, and define rules for our application. COM has inherent security, is declarative (future), and supports processors (like Elasticsearch). Today’s COM only supports SNMP (either traps or polling), but the goal is to enhance this capability to support protocols like tier 1, webhooks and APIs.
How Does COM Work?
The COM applications in our SDK convert your MIBs into Oracle Communications COM definition files. These definitions are in a JSON format that defines the SNMP OIDs needed to satisfy basic polling functionality like CPU, Memory, Disk, Temp, Fan, Interfaces, etc. The Oracle Communications COM definition file names are FCOM for fault and PCOM for performance metrics.
Oracle Communications Unified Assurance COM SDK has the following applications:
-
MIB2FCOM – Run this with a Management Information Base (MIB) file to generate a pre-certified FCOM file that then goes through curation to create a certified FCOM file.
-
FCOM2Rules – Run this with the certified FCOM file to generate the foundation rules.
-
FCOM2Test – Run this to generate a set of synthetic test traps to test the workflow of the curated FCOM file.
-
PCOM2Rules – Run this with a certified PCOM to generate the foundation rules. You must use a file that has already been manually curated and certified—Oracle Communications does not provide a MIB2PCOM app in the SDK.
The following diagram shows the overall process for converting your MIBS to Federos FCOM files.
Description of illustration mib2fcom.png
The following diagram shows the overall process for creating foundation rules with a certified FCOM file.
Description of illustration fcom-to-foundation-rules.png
Getting Started
To run all the Oracle Communications COM applications, you will need a system with Unified Assurance already installed as well as several additional packages. Follow these steps before you run the COM applications.
-
Download all of the required packages and create the local MIB repository on the system.
-
Log in to the command line for the server that will be used.
-
Run the following command to install the sdk-lib package:
$A1BASEDIR/bin/Package install sdk-lib -
Wait for the package installation process to complete.
-
Put the MIBs you want to convert into a subdirectory of the local MIBs repository.
Note:
The default location is
$A1BASEDIR/distrib/mibs/. -
Proceed to Fault for the next steps.