OCEEMS MIBs do not Compile if the TEKELEC-TOPLEVEL-REG file supplied with DSR or PIC Products is Used

Asset ID:	1-71-2357328.1
Update Date:	2018-02-12
Keywords:

Solution Type Technical Instruction Sure

Solution 2357328.1 : OCEEMS MIBs do not Compile if the TEKELEC-TOPLEVEL-REG file supplied with DSR or PIC Products is Used

Applies to:

Oracle Communications EAGLE (Software) - Version E5-MS 46.5 and later
Tekelec

Goal

While implementing the MIB files to Network Management System (NMS) by using TEKELEC-TOPLEVEL-REG with version 201412170000Z that is delivered with one of the MIB packages for either DSR or PIC, the EMS MIBs do not compile.

Solution

TEKELEC-TOPLEVEL-REG provided with PIC and DSR is different from the one provided with EAGLE/OCEEMS softwares in the software download centre.
This results in OCEEMS MIBs not compiling at customer's NMS when they are using the MIB provided with DSR or PIC.
TEKELEC-TOPLEVEL-REG delivered with Eagle MIBs contains the following entry for EMS:

tekelecEagleEMS OBJECT IDENTIFIER ::= { tekelecSwitchingGroup 24 }

TEKELEC-TOPLEVEL-REG with version 201412170000Z contains following entry for EMS:

tekelecEAGLEEMS OBJECT IDENTIFIER ::= { tekelecSwitchingGroup 24 }.

As the Oracle Communications Eagle Element Management System (OCEEMS) specific Management Information Database (MIB) files are using the tekelecEagleEMS obviously the MIBs are orphaned.
Ideally, the TEKELEC-TOPLEVEL-REG MIB file should be same across all of our products.

OCEEMS CoE Collab: 3-16420005031

Who suggested going to DSR field help

Field Support RT help ticket #17875

Who suggested going to Platform support

JIRA Ticket for platform support: CPE-1005Platform team confirmed that the relevant MIBs will be updated in next OCEEMS release documentation.

TKLC-EAGLEEMS-COMMONOBJECTS and TKLC-EAGLEEMS-NBI MIBs will be updated in OCEEMS 46.6

Attachments

This solution has no attachment