Oracle Communications EAGLE (Software)
 

PLA-Support>Sun Systems>CommsGBU>Global Signaling Solutions>SN-SND: Tekelec EMS
 

In this Document

Goal

Solution

References

Created from <SR 3-17275905191>

Applies to:

Goal

In OCEEMS we have configured some servers to be sent SNMP traps. That works well except one field into every trap is not the same that we observe in E5-MS system; that field is ID, or in MIB terminology :
 TKLC-EAGLEEMS-COMMONOBJECTS::alertSequenceNumber (1.3.6.1.4.1.323.5.3.24.1.1.7)

We are able to observe all traps going to customer management systems by setting a tcpdump job in 162 port as follows:

In the OCEEMS DB, we can see following entry in the Event table:

We need your help for correcting this issue and that E5-MS sends correct ID, as customers needs to correlate alarms information.
 

Solution

The alertSequenceNumber is set by Set by OCEEMS northbound interface module. It is an incrementing sequence number allowing NMS to determine if an event has been missed.
The expectation to have this value to be same as the ID mentioned in the OCEEMS DB Table is wrong.

Your requirement is found In later OCEEMS release i.e. 46.5; where SNMP traps also include UAM sequence number to the trap.
This UAM sequence number can be used to correlate the alarms between Eagle, OCEEMS and the same goes to the far end NMS via SNMP.

Reference enhancement Bugs are:
ENH 19179579 - Add UAM sequence number and time zone to SNMP traps
BUG 25834696     - Add UAM sequence number and time zone to SNMP traps

Kindly note that this introduces a change in our MIB files as well.

In your release (i.e. 46.2) its not present.

References

This solution has no attachment