E5MS SNMP Trap Identification by Network Management System

Asset ID:	1-71-2289171.1
Update Date:	2017-07-28
Keywords:

Solution Type Technical Instruction Sure

Solution 2289171.1 : E5MS SNMP Trap Identification by Network Management System

Applies to:

Oracle Communications EAGLE (Hardware) - Version E5-MS 45.0 and later
Tekelec

Goal

NMS team has implemented the SNMP trap E5MS alarm clearing logic upon "no multiple alarms for same sub resource" rule.
It seems there are multiple alarms for same sub resource and hence facing an issue with clear those alarms. The Solution part explains the behavior of the alarms trapsforwarded by SNMP to another platform.

Solution

Refer to the alarm balancing matrix for Eagle.
For Eagle Software version is 46.3, Refer to Unsolicited Alarm and Information Messages Reference - E72180 Revision 2 - Appendix A - UAM Balancing Matrix
http://docs.oracle.com/cd/E76234_01/docs.463/E72180_rev_2.pdf

Suppose minor alarm for Resource A and Subresource B is created. Then if for same resource A and Subresource B, a major alarm is created that will supersede the earlier minor alarm and now a major alarm should show.
So in alarm window there should be one alarm from resource and subresource but count changing based upon whether it is a new alarm or a continuation of an old event.
In the db (or in a network events page if available) there will be both the instances present.

Taking example of DPC System Alarms
UAM 0325 can be changed to: 0312, 0319, 0326, 0332 or can be cleared by any of following: 0324,0327, 0333
This is not a one-on-one relationship but is complex in some instances. The complete details for each UAM balancing are in the above mentioned document.

Similarly 0316-Route is Prohibited has been termed as a Resolution
If it appears after 0315 (Route is Restricted); then its a clearance event.
If it appears at first; then its a Problem
So in some cases; its not one on one linkage.
The reason is obvious:
If a Point Code is prohibited; it may cause a related route towards that point code to go prohibited as well.
So assumption that you will have only one alarm for an entity at a time is not entirely correct.
Usually the NMS teams follow the alarm balancing matrix (already shared with you) to get the perfect match between Eagle alarms and their clearance events.

UAM 0316 can be a first occurrence or can be an intermediate alarm of 0315.

If 0315 came first; it can be changed into transient stages 0316 or 0319. Clearance events of these can be 0314 or 0402
If 0316 came first; it can be changed into transient stages 0315 or 0319. Clearance events of these can be 0314 or 0402

Note: Usually confusion arises due to below mentioned two UAM codes 0316 and 0313

0313-DPC is prohibited

0316-Route is Prohibited

These are two different types of alarms. In case of a network event when a connectivity is lost these alarms can appear at same time.

The system should be able to recognize the fact that a route prohibition and a point code prohibition are not mutually exclusive events and can occur simultaneously.

However the catch is in the alarm level:
0313 is "Critical"
0316 is "No alarm condition. The message is informational only."

A typical network event would be like this on Eagle:
   3395.0313 *C DPC POINTCODE1            DPC is prohibited
   ****16-07-28 00:33:33****
   3394.0316    DPC POINTCODE1              Route is prohibited
   ****16-07-28 00:33:32****

Check that both UAMs appear together but one is Critical while other is for information only.
So customer can decide to keep the CRITICAL alarm on alarm window while keep the INFORMATION alarm suppressed.

Please download the relevant document to your Eagle Release from this link: http://docs.oracle.com/en/industries/communications/eagle/index.html

Attachments

This solution has no attachment