20-OnW310660 IManager M2000 V200R013 Alarm Management ISSUE1.00

Internal use only!
This is a customer training slide from LS Dept. Without permission

of LS, please do not send or present this slide to customer!
Copyright © 2013 Huawei Technologies Co., Ltd. All rights reserved.

M2000 V200R013
Alarm Management
www.huawei.com

References
 M2000 Online Help
 M2000 Administrator Guide
Copyright © 2013 Huawei Technologies Co., Ltd. All rights reserved. Page2
Objectives
Upon completion of this course, you will be able to:
 Understand alarm categories, severities, and statuses.
 Know how to report and store alarms.
 Be familiar with basic operations on alarms.
 Monitor the network running status.
Contents
1. Alarm Management Overview
2. Basic Concept
3. Basic Operations on Alarms
4. M2000 Alarm Settings
5. NE Alarm Settings
Alarm Management Overview
 A new display style of
M2000 client is added
from R13 version, that
is, application style.
The difference between
the two styles is only
about the organization
of the menus. You can
choose the style you
prefer in Preferences
window under file menu
.
 In this course, we will

continue use the
traditional style and you
can try the new style if
you are interested in it.
Alarm Management
 Fault management involves

 Displaying and collecting
alarm statistics
 Notifying alarms in an
audible and visual manner
 Acknowledging and
synchronizing alarms.
Contents
1. Alarm Management Overview
2. Basic Concept
Alarm and Event
 Alarm
 An alarm refers to the notification reported when a fault is detected by the system.
 A fault refers to a physical or logical factor, such as excessively high CPU usage,
hardware fault, or network cable disconnection, which causes a system failure.
 Both generation time and clear time can be obtained.
 Event
 An event refers to the notification reported when an event is detected by the
system.
 An event is anything that takes place on the managed object. For example,
operation logs are periodically exported.
 Only generation time but not recovery time can be obtained.
 Alarms of all NEs are actively reported to M2000.
Alarm Severity
 Critical
If a critical alarm is generated, devices or resources may not work at all. Emergent recovery
is required.
 Major
If a major alarm is generated, the service quality of devices or resources has been seriously
deteriorated. Quick measures are required.
 Minor
If a minor alarm is generated, the service quality of devices or resources has been slightly
deteriorated. Proper handling or further observation is required in case that a serious fault
occurs.
 Warning
If a warning alarm is generated, the service quality of devices or resources is potentially
affected. Different measures are taken for different errors.
Alarm Status
 Four alarm statuses are provided as follows: unacknowledged and
uncleared, acknowledged and uncleared, unacknowledged and
cleared, and acknowledged and cleared.
 Alarm status change
Alarm Storing
 History Alarm: Acknowledged and cleared alarms.
 Current Alarm: All alarms exceps history alarms.
 Alarm log: refers to received alarms that are logged by the fault subsystem.
Each alarm record is an alarm log.
 Event log: refers to received events that are logged by the fault subsystem.
Each event record is an event log.
Alarm Reporting Process
1. An NE reports alarms to M2000.
2. Filter alarms.
3. Redefine alarm severities.
4. Perform alarm correlation analysis.
5. Save alarm information.
6. Send alarm notifications.
Alarm Audible and Visual Display
Alarm sound box

Alarm panel
Topology view
 The following can only receive
fault alarms: Alarm
information
 Alarm panel
Alarm box
 Alarm sound box
 Topology view
 The alarm box can receive both fault alarms and event alarms
simultaneously.
Questions
 1. What status are the alarms classified into?
 2. How many days can the acknowledged and cleared alarms
store in the alarm list?
Contents
1. Basic Concept
Contents
2.1 Browsing Current Alarms
2.2 Performing Alarm Operations
2.3 Querying Alarm or Event Logs
2.4 Querying Alarm or Event Log Statistics
2.5 Displaying the Alarm Panel
2.6 Querying Historical Alarms
Browsing Current Alarms
Name of an
alarm to be
queried
Duration =
Clear
Time -
Generatio
n Time
Display
correlative
alarms displays
correlative
alarms set by
an NE or
M2000.
Browsing Current Alarms (Cont.)
Select an
alarm or event
source.
Browse Current Alarm[1]
Setting Column Headers on the
Browse Current Alarm[1]
 After you set column headers, information only on the set columns is displayed
on the Browse Current Alarm[1] tab page.
Viewing Detailed Alarm Information
Browsing Current Alarms by Statuses
Browsing Current Alarms by
Severities
Contents
Locating Alarms in the Topology View
Physical Topo
Manually Acknowledging Alarms
 Acknowledge an
alarm to identify that
it has been handled
and no more concern
is required.
Manually Clearing Alarms
 You can manually clear
an alarm when it cannot
be automatically cleared
or it does not exist on the
NE.
Synchronizing Alarms
 Alarms can be automatically or manually synchronized.
 Automatic synchronization
 When an NE connects to M2000, all alarms on the NE can be
automatically synchronized to M2000.
 All alarms are automatically synchronized to M2000 after you create a
GSM or UMTS NE on M2000; all current alarms are automatically
synchronized after you create a CDMA NE.
 Manual synchronization
 The uncleared active alarms can be manually synchronized.
Manually Synchronizing NE Alarms
Contents
Querying Alarm Logs
Select the
default duration.
Querying Alarm Logs (Cont.)
Querying Event Logs
No clear time can

be obtained for
events.
Querying Event Logs (Cont.)
Contents
Collecting Statistics on Alarm Logs
(Cont.)
(Cont.)
(Cont.)
Contents
Displaying the Alarm Panel
Displaying the Alarm Panel (Cont.)
Querying Alarm Bar Charts
Contents
Querying Historical Alarms
Name of an
alarm to be
queried
Duration =
Clear Time -
Generation
Time
Display correlative
alarms displays
correlative alarms set by
an NE or M2000.
Querying Historical Alarms (Cont.)
Select an
alarm or event
source.
Querying Historical Alarms (Cont.)
Questions
 1. What types are the alarm synchronization classified into? What
kind of NE are supported by each type?
 2. Can all the alarms be obtained by one browse operation?
Contents
1. Basic Concept
Contents
3.1 Automatically Acknowledging Alarms
3.2 Managing Object Groups
3.3 Managing Templates
3.4 Setting Alarm Masking Rules
3.5 Setting Alarm/Event Redefinition Rules
3.6 Setting Alarm/Event Remote Notifications
3.7 Setting ADMC Alarms
3.8 Setting Maintenance Mode Alarm
3.9 Setting Alarm Correlation Rules
3.10 Setting NE Alarm Log Synchronization Rules
Automatically Acknowledging Alarms
by Severities
Automatically Acknowledging Alarms
by Rules
Managing Object Groups
Managing Object Groups (Cont.)
Managing Alarm/Event Name Groups
Managing Alarm/Event Name Groups
(Cont.)
Managing Templates
Managing Templates(cont.)
Setting Alarm Masking Rules
Alarm masking rules
M2000
NEs
Discarded
alarms
Setting Alarm Masking Rules (Cont.)
Setting Alarm Redefinition Rules
Setting Alarm/Event Remote
Notifications
 By email
 Alarm information is sent by an SMTP server.
 In short messages
 Alarm information is sent by a wireless Modem (such as GSM Modem
or CDMA Modem) or short message gateway.
Email Short
message
Alarm
information
Notifications((Cont.)
Setting Communication Parameters
((Cont.)
((Cont.)
Notification Rules
Notification Rules (Cont.)
Notification Rules (Cont.)
Transforming Events to ADMC Alarms
Setting Alarm Lifecycles
Setting Maintenance Mode Alarms
Click the circled button to set Maintenance Mode alarms.
Setting Maintenance Mode Alarms
(Cont.)
Filtering Maintenance Mode Alarms
Filtering Maintenance Mode Alarms
(Cont.)
Querying Maintenance Mode Alarms
Alarm Correlation - Conception
 Alarms or events are correlated to each other, so you can set correlation rules.
After rules set, M2000 automatically processes alarms or events according to them
to redefine their levels, Discard them or set them to correlative alarms.
 For an example:
The high service memory usage
alarm leads to two alarms: high
memory usage alarm and high
CPU usage alarm which is the
root alarm leads to abnormal
M2000 service exit alarm.
Alarm Correlation - Default Correlation
 Correlation analysis involves two interfaces: Default Correlation and Correlation
Analysis. The Default Correlation interface displays the alarm correlation rules
defined by M2000. You can set whether to use these rules, but cannot modify them.
Alarm Correlation - Correlation Analysis
 You can add, delete or check the property of all the correlation displayed in the
window. The fields displayed in white can be changed, grey ones cannot be
changed, pink ones are already changed but not in use. Click Apply to take the
modifies into effect. The Apply button is available after a field is changed regardless
of selection of a record.
Alarm Correlation - Set Correlation Rule
Page87
Alarm Correlation - Set Correlation Rule
A
Page88
Alarm Correlation - Set Correlation
Rule((Cont.)
 If there is only one alarm in the

correlation rule, then Analysis
duration parameter is invalid.
Alarm Correlation - Alarm/Event
Frequency Analysis
 In alarm/event frequency analysis, if the number of the same alarms/events
generated during the preset time interval reaches the preset value, these
alarms/events are considered to be correlated to each other, then after alarm/event
frequency analysis rule set, M2000 processes the alarms/events according to the
preset actions.
Alarm Correlation - Set Alarm/Event
Frequency Rule
 If alarms/events meet the triggering
condition in the left picture, which
1 means:
 Their occurrence times within
the Time segment
 The number of them equal or
2
greater than the Alarm count.
 Then M2000 will process the
alarms/events according to the
policy preset in the left picture.
Alarm Correlation - Intermittent Alarm
and Repeat Event Analysis
 If the time interval of the current and last clearance time of the same alarms(or
occurrence time of the same events ) is shorter than or equal to the value in
interval, these alarms(events) are defined as intermittent alarms(repeat events).
 Multiple same alarms/events in a short period may be redundant and

inconvinient for the maintenance personnel.
Alarm Correlation - Set Intermittent
Alarm and Repeat Event Analysis
 Click select… to select

alarms or event. You can
select multiple
alarms/events. Each create
an analysis rule.
 If multiple the same alarms occur within the time interval and their number equal
to or more than the value in the Intermittence/Repeat Times will be abandoned.
 Memo can be added here to remind maintenance people the corresponding
important operations or just provide information.
Alarm Correlation - Acknowledged and
Uncleared Alarm Time Analysis
 If the acknowledged alarms
are not cleared in the time
segment, you can change the
alarm severities through
acknowledged and uncleared
alarm analysis, which helps
the maintenance personnel to
pay attention to the alarms and
handle them in time.
Alarm Correlation - Examples
 Examples
 The correlation configuration of the MSC is as follows:
 The fault alarm whose alarm level is Major is E1/T1 Loss of Signal
(ID=1101)
 The interval of the alarm is 10s.
 The times of high frequency alarm is 10.
 t1
The alarms meeting the correlation rules are abandoned. t2
1 2 3 4 5 6 7 8 9 10 11 12 13
0 t
T1 T2 T3 T4 T5 T6 T7 T8 T9 T10 T11 T12 T13
Setting NE Alarm Log Synchronization
Rules
Questions
 1. What types are the alarm shield classified into? What are the
differences?
 2. What is ADMC? Can they be cleared?
 3. What is the reason to set a alarm in maintenance mode?
 4. How will the alarms which accord with the correlation rules be
handled?
Contents
1. Basic Concept
NE Alarm Settings
Alarm Mask Rules
Alarm Mask Rules(Cont.)
Redefining NE Alarm Severities
User-defined Alarms
Binding User-defined Alarms
Questions
 1. what is the difference between the alarm severity redefining on
NE side and on OSS side?
 2. Can the masked alarms be seen on NE side once the NE alarm
mask rule set?
Thank you
www.huawei.com

20-OnW310660 IManager M2000 V200R013 Alarm Management ISSUE1.00

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

20-OnW310660 IManager M2000 V200R013 Alarm Management ISSUE1.00

Uploaded by

Copyright:

Available Formats

Internal use only!

This is a customer training slide from LS Dept. Without permission

Copyright © 2013 Huawei Technologies Co., Ltd. All rights reserved.

Copyright © 2013 Huawei Technologies Co., Ltd. All rights reserved.

 Understand alarm categories, severities, and statuses.

 Know how to report and store alarms.

 Be familiar with basic operations on alarms.

 Monitor the network running status.

 In this course, we will

 Fault management involves

Alarm sound box

No clear time can

Alarm masking rules

Click the circled button to set Maintenance Mode alarms.

 If there is only one alarm in the

 Multiple same alarms/events in a short period may be redundant and

 Click select… to select

You might also like