Summary:
Alarm correlation rules are compiled based on correlation information about root alarms and
correlative alarms of GSM, UMTS, and LTE NEs. The alarm correlation engine analyzes
alarms that comply with the rules and presents alarm correlations on the M2000. The
correlation information helps users identify faults and perform troubleshooting, improving
O&M efficiency.

Benefits:

Alarm correlation analysis significantly improves O&M efficiency from the following

aspects:

Reducing time required for fault identification
Improving accuracy of fault identification

Description:

By analyzing NE alarms, the M2000 identifies root alarms and correlative alarms based on
specified conditions, and displays the alarm associations. Based on alarm associations, users
can locate and rectify faults related to root alarms. This improves O&M efficiency. The
M2000 provides equivalent alarm association, parent-child alarm association identification,
and combination of alarms of the same types. The following provides some examples:
Example for equivalent alarm association rules
When a fault occurs on the transmission link between an RNC and a NodeB:
The RNC reports the alarm ALM-21581: Path Fault, and the NodeB reports the alarm
ALM-25838: AAL2 Path Fault. The two alarms are triggered by the same fault but are not in
parent-child relationship. After analyzing the alarm correlation, the M2000 sets up a
relationship between the two alarms. Based on user-specified settings, the M2000 can report
only one of the two alarms. This reduces the number of reported alarms.
Example for parent-child alarm association

When a fault occurs on an RNC and the RNC reports alarm ALM-21287: SDH/SONET

Tributary Alarm Indication Signal, the NodeB simultaneously reports alarm ALM-25802:
E1/T1 Remote Alarm Indication Signal. Among the two alarms, alarm ALM-21287 is the root
alarm, and users only need to handle this alarm. Based on the default alarm correlation rules,
the M2000 sets alarm 25802 on the NodeB side as the correlative alarm. Users can set rules so
that correlative alarms are not reported to the third-party system. This also reduces the number
of reported alarms.

Example for combining alarms of the same types

When multiple base stations are connected, if a fault occurs on one NE, other NEs also report
the same alarms. All these alarms can be combined as one alarm and handled one time.
For example, if a fault occurs on a base station, other base stations on the same chain
simultaneously report alarm ALM-25889: SCTP Link Congestion. The value of peer IP address in the location information about these alarms is the same, which is the IP address of the faulty base station. After analyzing the alarms, the M2000 combines the alarms ALM-25889: SCTP Link Congestion containing the same peer IP address and reported from base stations within a short time as one internal alarm, and reports this alarm instead of the
raw alarms to the third-party system. Users only need to handle the internal alarm that
contains key information about these alarms. This significantly reduces the number of alarms.

address in the location information about these alarms is the same, which is the IP address of
the faulty base station. After analyzing the alarms, the M2000 combines the alarms
ALM-25889: SCTP Link Congestion containing the same peer IP address and reported from
base stations within a short time as one internal alarm, and reports this alarm instead of the
raw alarms to the third-party system. Users only need to handle the internal alarm that
contains key information about these alarms. This significantly reduces the number of alarms.

Enhancement:
None

Dependency:
None

Alarm correlation analysis significantly improves O&M efficiency from the following aspects: Reducing time required for fault identification Improving accuracy of fault identification.

Excellent topic