RNC Maintenance and Fault Management in RNC

Alarms Handling

1 © Nokia Siemens Networks RN33153EN20GLA0

RN33153EN20GLA0 1
RNC Maintenance and Fault Management in RNC

Nokia Siemens Networks

Academy
Legal notice

Intellectual Property Rights

All copyrights and intellectual property rights for Nokia Siemens Networks training
documentation, product documentation and slide presentation material, all of which are forthwith
known as Nokia Siemens Networks training material, are the exclusive property of Nokia
Siemens Networks. Nokia Siemens Networks owns the rights to copying, modification,
translation, adaptation or derivatives including any improvements or developments. Nokia
Siemens Networks has the sole right to copy, distribute, amend, modify, develop, license,
sublicense, sell, transfer and assign the Nokia Siemens Networks training material. Individuals
can use the Nokia Siemens Networks training material for their own personal self-development
only, those same individuals cannot subsequently pass on that same Intellectual Property to
others without the prior written agreement of Nokia Siemens Networks. The Nokia Siemens
Networks training material cannot be used outside of an agreed Nokia Siemens Networks
training session for development of groups without the prior written agreement of Nokia
Siemens Networks.

2 © Nokia Siemens Networks RN33153EN20GLA0

RN33153EN20GLA0 2
RNC Maintenance and Fault Management in RNC

Document change history

Date Version Name Change comment

22.02.2010 1.0 Kittipong Thamapa

3 © Nokia Siemens Networks RN33153EN20GLA0

RN33153EN20GLA0 3
RNC Maintenance and Fault Management in RNC

Objectives

After completing this module, the student should be able to

• Explain maintenance system and maintenance routine tasks
for DX200 and IPA2800
• Understand Hardware Management System (HMS)
• Understand Alarms Structures
• Handling Alarms Administration: alarms history, active alarm,
block alarm

4 © Nokia Siemens Networks RN33153EN20GLA0

RN33153EN20GLA0 4
RNC Maintenance and Fault Management in RNC

Reference Reading Material

PDF Reference Reading material can be found from NED

-Preventive Maintenance: DN02143189

-Alarm Administration in RNC:DN02142969
-System Maintenance: DN981849

5 © Nokia Siemens Networks RN33153EN20GLA0

Reference Reading Material can be found from NED by

1. Select ‘Content’ tab then PDF and browse related topics
2. Use ‘Search box’ then ‘PDF’ indicate in front of search result

RN33153EN20GLA0 5
RNC Maintenance and Fault Management in RNC

Preventive Maintenance Strategy

• Create disaster recovery and escalation plans to enable the fast and
correct handling of problems.
• Create a plan for preventive maintenance, for example by using daily,
weekly and bi-annual routines as a basis.
• Define maintenance entities suitable for your network structure.
• Plan all maintenance activities well beforehand.

6 © Nokia Siemens Networks RN33153EN20GLA0

The successful operation and maintenance of analogue, digital or mixed networks

requires that a network operator sets up an appropriate maintenance organisation and
defines a strategy as well as the responsibilities and procedures for the maintenance
organisation.
Here are some things to consider when planning the maintenance strategy:
•Create disaster recovery and escalation plans to enable the fast and correct
handling of problems. See Troubleshooting recommendations.
•Create a plan for preventive maintenance, for example by using daily, weekly
and six monthly routines as a basis.
•Define maintenance entities suitable for your network structure.
•Plan all maintenance activities well beforehand.

For more information on developing a maintenance strategy and organization, you can
refer to the following ITU-T recommendations for example:
Recommendation M.10 (10/92) - Scope and application of Recommendations
for maintenance of telecommunication networks and services
Recommendation M.20 (10/92) - Maintenance philosophy for telecommunication
networks
Recommendation M.21 (10/92) - Maintenance philosophy for telecommunication
services

RN33153EN20GLA0 6
RNC Maintenance and Fault Management in RNC

Network Element Maintenance

• Modular structure ensures fault tolerance and ease of maintenance

• Redundancies ensure NE remains operational in fault situations

• Maintenance consists of:

– Automatic functions built into NE
– Functions carried out by O&M personnel including preventive
maintenance

7 © Nokia Siemens Networks RN33153EN20GLA0

The modular structure of network elements ensures not only fault tolerance but also ease
of maintenance. If a plug-in unit becomes faulty, you can replace it with a new plug-in
unit; the redundancy schemes ensure that the network element remains operational even
in fault situations.
Maintenance system consists of automatic functions that are integrated into the network
element and functions that are carried out by the operation and maintenance personnel.
Preventive maintenance applies to the computer units and peripheral devices of network
elements. In a digital network element, the need for preventive maintenance actions is
limited and mainly associated with peripherals.
The purpose of preventive maintenance is to prevent equipment from malfunctioning and
wearing out.
The alarm and diagnostic reports generated by the system provide you with information
on the network element's state.

RN33153EN20GLA0 7
RNC Maintenance and Fault Management in RNC

Maintenance of Network Element

Fault / disturbance Activation of Activation of

observation recovery fault location

Failure

Supervision Alarm Recovery Diagnostics

System System System System

•Fault • Alarm • Fault • Fault

detection printouts elimination location

• Processing of
alarms events

8 © Nokia Siemens Networks RN33153EN20GLA0

Preventive maintenance applies to the computer units and peripheral devices of network
elements. In a digital network element, the need for preventive maintenance actions is
limited and mainly associated with peripherals. The purpose of preventive maintenance
is to prevent equipment from malfunctioning and wearing out.
The alarm and diagnostic reports generated by the system provide you with information
on the network element's state.

Automatic maintenance functions

System maintenance handles all the fault situations and user-initiated configuration
management tasks within the hardware and software of the system. System Maintenance
is responsible for availability performance on the network element level. It is
designed to perform its task as automatically and autonomously as possible.
Usually all activities can be performed remotely unless the required action involves the
hardware. Depending on the structure of your network, you may need to change some
of the logical file outputs, for example diagnostic and observation outputs, to be able to
receive all the information that is needed to perform maintenance activities remotely.

RN33153EN20GLA0 8
RNC Maintenance and Fault Management in RNC

Supervision System

Fault / disturbance
observation
Supervision is responsible for fault detection
Failure and uses both hardware and software for
this purpose.
Supervision Alarm
System System
• Hardware supervision
• Software supervision
•Fault • Time supervision
detection • Supervision of semipermanent connections

9 © Nokia Siemens Networks RN33153EN20GLA0

Supervision functions

Supervision is responsible for fault detection and uses both hardware and software forthis
purpose.

Detailed supervision functions have been dedicated to certain supervised objects:

• hardware supervision
• software supervision
• time supervision
• supervision of semipermanent connections
These functions generate alarm events when faults are detected. Hardware supervision
relies on hardware configuration data stored in the configuration database.A
nonconformity
between the database and the actual hardware generates an alarm event.

RN33153EN20GLA0 9
RNC Maintenance and Fault Management in RNC

Maintenance of Network Element

Activation of
recovery

Alarm functions
The system has the following
Alarm alarm functions:
System
• Collection of alarm data
• Storage of alarms
• Alarm • Output of alarms
printouts • Control of alarm outputs
• Activation of recovery functions
when a unit fails
• Processing of
• Informing about alarms
alarms events

10 © Nokia Siemens Networks RN33153EN20GLA0

Alarm functions

The system has the following alarm functions:

• Collection of alarm data
• Storage of alarms
• Output of alarms
• Control of alarm outputs
• Activation of recovery functions when a unit fails
• Informing about alarms

Alarm functions have a user interface with which you can set alarm parameters,
examine the alarm situation and alarm history, and define handling rules for new events.

RN33153EN20GLA0 10
RNC Maintenance and Fault Management in RNC

Maintenance of Network Element

Activation of
Recovery includes the following fault location
functions:

• Restarting program blocks, computers, Recovery

preprocessors, and the whole system
System
• Automatic recovery from faults
• A user interface, for example, for
manual recovery
• Fault
elimination

11 © Nokia Siemens Networks RN33153EN20GLA0

Recovery functions

Recovery is responsible for eliminating the effects of faults on the operation of the
system. For this purpose, it uses unit switchovers and different kinds of restarts.
Individual program blocks can be restarted by a local unit state administration function
(part of the recovery) when the program blocks do not respond to supervision messages.

The recovery or the hardware watchdog timer can restart any computer unit,
without restarting the whole system.
Recovery includes the following functions:
• Restarting program blocks, computers, preprocessors, and the whole system
• Automatic recovery from faults
• A user interface, for example, for manual recovery

RN33153EN20GLA0 11
RNC Maintenance and Fault Management in RNC

Maintenance of Network Element

Activation of
fault location
•Recovery starts diagnostic programs
automatically.

Diagnostics
•Diagnostic programs are executed on System
functional units which are in the test
state (TE-EX).

• Fault
location

12 © Nokia Siemens Networks RN33153EN20GLA0

Diagnostic functions

Diagnostic programs are able to localise faults in the system to an accuracy of one plugin
unit in 70% of all cases, and four plug-in units in 95% of the cases.
The system complies with the ITU-T requirement on the average active repair time of 30
minutes.
Recovery starts diagnostic programs automatically.
Diagnostic programs are executed on functional units which are in the test state (TE-EX).
The same programs can be activated with the commands of the UD MML command
group.

Plug-in units can normally be removed from and inserted in functional units which are in
the separated (SE-OU or SE-NH) state, without disconnecting the power.
The fault diagnosis relies on the hardware configuration data which is stored in the
configuration database, and nonconformity between the database. The actual hardware
situation usually leads to a diagnosis report. In this case, the fault localisation function
may not be able to complete its actual task properly.

RN33153EN20GLA0 12
RNC Maintenance and Fault Management in RNC

Daily Maintenance Routines

• Alarms
– Display active alarms
– Display and store alarm history
• Performance Indicators
• Working states
– Check the working states of computer units
– Check the working states of I/O devices
– Check Radio Network states
– Signalling links
– Circuit groups
• Safe copy
– Make fallback copies of SW in NE
– Check safe-copying information
– Make backup copies of the fallback copy
• OMS
– Make an OMS backup
– Save the OMS logs

13 © Nokia Siemens Networks RN33153EN20GLA0

Performing daily maintenance routines

Steps
1 Monitor the alarms daily as described in Monitoring alarms daily
2 Check the working states of computer units
For further information, see Working state change
3 Make fallback copies as described in Fallback copying the software build
4 Verify the fallback build as described in Verifying fallback build
5 Make backup copies of the fallback copy as described in Backup copying FB buildto
optical disk

RN33153EN20GLA0 13
RNC Maintenance and Fault Management in RNC

Weekly Maintenance Routines

• Monitor the signalling network
– Amount of traffic, traffic distribution, failure situation
• Performance indicators
• Check system time
• Print and save the working states
• Display blocked alarms
• Monitor the use of memory
• Monitor load share of IP routers
• Check computers unit logs

14 © Nokia Siemens Networks RN33153EN20GLA0

Performing weekly maintenance routines

Steps
1 Monitor the signalling network
For more information, see Activating and deactivating SS7 signalling measurement
reporting, Activating SS7 signalling interval log reporting, Configuring MTP's traffic
measurement
matrix, Interrogating SS7 signalling measurements with MML commands
2 Print and save the working states
For further information, see Working state change fails
3 Display blocked alarms as described in Displaying alarm blocking data weekly
4 Monitor the use of memory as described in Measuring long-period memory usage

RN33153EN20GLA0 14
RNC Maintenance and Fault Management in RNC

Six-Monthly Maintenance Routines

• Operating system
– Set daylight saving time
▪ OMU
▪ OMS

• Site support system

– Antenna light
– Door alarm system, fire sensor, wired alarm connection
– Battery and power back up
– Visual inspection
– Test external equipment

• Diagnostics
– Run fault diagnostics

15 © Nokia Siemens Networks RN33153EN20GLA0

Performing six-monthly maintenance routines

Steps
1 Set daylight saving time as described in Setting summer time on or off
2 Run fault diagnostics as described in Inspecting unit diagnostics and working
states
Further information
Clean the magneto optical disks periodically to ensure satisfactory operation. Do this
according to the magneto disk manufacturer's recommendatio

RN33153EN20GLA0 15
RNC Maintenance and Fault Management in RNC

Proactive Maintenance
• Monitor Radio Network
– Configuration, counter, alarm data
– Critical resource, mobility action, connection quality

• Produce KPI Trends

– KPI level, KPI class

• Analyze KPI Trends

• Analyze and escalate suspected problems

• Perform a visual inspection whenever visiting the site for preventive

maintenance

16 © Nokia Siemens Networks RN33153EN20GLA0

RN33153EN20GLA0 16
RNC Maintenance and Fault Management in RNC

Supervision System by
Hardware Management System (HMS) IPA 2800

Hardware Management Master Nodes

HMMNs  OMS

Hardware Management System Bridge Nodes

HMSBs TSS/TBU

Hardware Management System nodes

HMSSs  Other unitห

17 © Nokia Siemens Networks RN33153EN20GLA0

The Hardware Management System (HMS) provides a duplicated serial bus between the
master node (located in the OMU) and every plug-in unit in the system. The bus provides fault
tolerant message transfer facility between plug-in units and HMS master node.
The HMS is used in supporting auto-configuration, collecting fault data from plug-in units and
auxiliary equipment, collecting condition data external to network element and setting hardware
control signals like restart and state control in plug-in units.
The hardware management system is robust. For example, it is independent of system timing and
it can read hardware alarms even from a plug-in unit without power. Thus it allows power alarms
and remote power on/off switching function.
The hardware management system forms a hierarchical network (see above). The duplicated
master network connects the master node with the bridge node of each subrack. The subrack
level networks connect the bridge node with each plug-in unit in the subrack.

HMS supports following functions:

In system set-up: Collecting data of existing racks and subracks and their indexes. Collecting
equipping data of every subrack, plug-in unit types, their variants and versions.

In normal use: Collecting fault data from plug-in units and auxiliary equipment and condition data
external to network element. Setting hardware control signals like restart and state control in plug-
in units. Reading and writing of any configuration data stored in non volatile memory of unit
computer or control computer to check hardware configuration and to set communication
channels between computers for ATM based message passing via the ATM switch fabric.
Offering protected message link between HMS master node and an unit having no connectivity via
the ATM switch fabric. Controlling auxiliary equipment like fan trays and AC/DC power supplies.
Controlling equipment and space external to network element like door locking, temperature and
other states, alarms and conditions of street side cabinets, wall mounting cabinets and
telecommunication sites or other installation space.

In maintenance operations: Detecting extracting and inserting a plug-in unit. Identifying inserted
plug-in unit. Setting automatically configuration data of an inserted plug-in unit.
Under severe fault conditions: HMS is able to read hardware alarms from a plug-in unit without
power feed. HMS performs all its tasks even when system timing is missing.

RN33153EN20GLA0 17
RNC Maintenance and Fault Management in RNC

RNC Alarm System

NetAct
Alarm Monitor
• RNC NE Alarm includes WBTS
Nwi3
through an alarm mediation
RNC OMS
OMS FS Platform
Apps Apps
• RNC OMS Alarm includes
UI – Alarm generated by EM
Alarm System (OBRO and
FM) applications
– FlexiServer alarms,
RNC NE – WBTS Alarm
Alarm System MMI

• All alarms are transferred to

Alarm Alarm Alarm NetAct through alarm mediation
on RNC OMS
System System System

FTM AXC

UI UI UI

NB/RSxxx WBTS Flexi WBTS UltraSite WBTS

18 © Nokia Siemens Networks RN33153EN20GLA0

Platform alarm system

The platform alarm system consists of distributed and centralised parts.
The distributed part handles, on the unit level, the fault observations and disturbance
observations set by the application program blocks, and the cancellations of fault
observations. The distributed part sends the hypotheses that have become certain on the
unit level, and their cancellations, to the alarm system's centralised part located in the
maintenance computer of the system. The distributed part also transmits the notices set
by the application program blocks to the centralised part.
On the system level, the centralised part processed the hypotheses, cancellations of
hypotheses, and notices received from the distributed part. It then sends the hypotheses
that have become set on the system level, as well as their cancellations, to the Network
element level alarm system (NELAS). If necessary, it also informs the recovery of starting
the recovery actions.

RN33153EN20GLA0 18
RNC Maintenance and Fault Management in RNC

Alarm Data Flow

Network element

IPA 2800 EMS

Platform Network
Alarm Element
System Level Alarm
Mediating NetAct
Alarm
System Function
(NELAS)

Appl Level
Alarm Sys

Alarm Output Devices

19 © Nokia Siemens Networks RN33153EN20GLA0

Application level alarm system

Application level alarm system is a lower level alarm handler which
collects alarm events from its own application area in the network element.
prehandles application specific alarm events before forwarding them to NELAS (network
element level alarm system)
can receive alarm events from external equipment that is under the supervision of the
application area.
The number of application level alarm systems and their connections outside the network
element depend on the network element type.
Network element level alarm system (NELAS)
The Network Element Level Alarm System (NELAS) does the final processing for all
alarm events concerning either the network element itself or remote objects controlled by
the network element. NELAS is situated on top of the centralised part of the platform
alarm system as well as on top of any application level alarm system that transmits
alarms of its application area to the NELAS. In addition to possible filtering of the alarm
events on the network element level, NELAS is responsible for collecting alarm history
and for sending alarms to be printed out by desired output devices and to NetAct.
Transmitting alarms to NetAct, in real time and by the alarm upload, is done via EMS.
Starting the transmission of the alarm events to NetAct is requested by the NetAct itself
and it needs no explicit configuring on the network element side.

Alarm Mediating Function

Alarm Mediating Function transmits the alarms between the Network Element (NE) and
NetAct. In this online alarm transfer, Alarm Mediating Function receives alarm events
from NELAS and sends them to NetAct. Alarms are sent to NetAct only when NetAct is
available and has ordered alarm events from EMS. During active alarm upload, Alarm
Mediating Function requests the currently active alarms from NELAS and passes them to
NetAct.

RN33153EN20GLA0 19
RNC Maintenance and Fault Management in RNC

OMS: Fault Management Application

OMS Fault Management (FM) application offer GUI interface for all
Fault Management function such as view active alarms and alarm history.
Therefore, no MML command required. i.e. RNC OMS can use for view alarms

20 © Nokia Siemens Networks RN33153EN20GLA0

Before you start

Make sure that Element Manager is installed on your workstation. For instructions on
how to install Element Manager, see .
Steps

1 Log in to Element Manager.

To start Element Manager and Application Launcher, enter your Element Manager user
ID and password, and the OMS IP address.

2 Start the Fault Management application.

In Application Launcher, double-click the icon for Fault Management. The Fault
Management
application starts and creates a connection to the OMS. After the connection
is successfully created, Fault Management automatically receives all active alarms.

RN33153EN20GLA0 20
RNC Maintenance and Fault Management in RNC

Display Active Alarm and Alarm History (FM)

in RNC OMS

21 © Nokia Siemens Networks RN33153EN20GLA0

Viewing Active Alarms

a) Start the Fault Management application.

b) Wait until the connection status in the status bar changes from disconnected to
connected.
Expected outcome
All active alarms are displayed in the Active Alarms view.
If you want, you can set filter rules by opening the Filter dialog from the Active menu or
by clicking the Filter button in the tool bar. See the Fault Management - Filter Active
Alarms dialog for more information.

RN33153EN20GLA0 21
RNC Maintenance and Fault Management in RNC

Display Active Alarm (Alarm Monitor) in NetAct

22 © Nokia Siemens Networks RN33153EN20GLA0

RN33153EN20GLA0 22
RNC Maintenance and Fault Management in RNC

Reducing alarm flow with History Analysis Graph

With the History Analysis Graph you can analyze alarm history data to find
and set optimum delay values for alarms.
The analysis of alarm history data allows you to forecast how much the
alarm count is reduced the next time a similar fault situation occurs.

RNC OMS

23 © Nokia Siemens Networks RN33153EN20GLA0

RNCs can generate large numbers of alarms. For alarms that are repeated or alarms
that follow certain patterns, you can reduce the number of alarms to a more manageable level
by adjusting the setting delay, cancelling delay, or alive time.
With the History Analysis Graph you can analyze alarm history data to find and set
optimum delay values for alarms. The analysis of alarm history data allows you to
forecast how much the alarm count is reduced the next time a similar fault situation
occurs. The history data is shown on the History Analysis Graph, and you can adjust the
setting delay, cancelling delay, or alive time to see how the forecast changes.
For more information about the setting delay, cancelling delay, and alive time alarm
parameters, see OMS alarm parameter values.

RN33153EN20GLA0 23
RNC Maintenance and Fault Management in RNC

Alarm Urgency Level

Alarm Class Description
Alarm which is not cancelled and which only informs about a fault
Notice event without printing out the urgency class

Disturbance is used for informing about temporary disturbance

Disturbance situations, which means informing about a short failure event that
does not have any permanent effect on service

* An alarm or transient disturbance marked with one asterisk

does not usually require user actions

An alarm marked with two asterisks does not threaten the operation of

** the system. However, if the fault occurs during working hours, it must
be corrected at once. If the fault occurs outside working hours, it can
be corrected the next day

Alarms marked with three asterisks require immediate action from the
user. An alarm like this is set when the system has become faulty to
*** the extent that some essential functionality of the system has
stopped, or is in danger of stopping. The maintenance personnel must
take immediate action

24 © Nokia Siemens Networks RN33153EN20GLA0

RN33153EN20GLA0 24
RNC Maintenance and Fault Management in RNC

External alarms and alarm outputs

• External alarms can be used for

indicating changes in the condition of
supervised external entities Alarm Output
• External Alarm are collected with the
help of the EHAT plug-in unit, from 0=***EQUIPM *** equipment alarms
which they are transferred to the alarm 1=***COMM *** communication alarms
system via the HMS bus
2=***PROCES ***processing error alarms

• Alarm outputs are used for indicating 3=***QUAL ***quality of service alarms
the overall alarm situation in the 4=***ENVIR ***environmental alarms
system
5=General All two star (**) alarms
• By default alarm outputs #0...#5 are
controlled according to the live alarm 15=Alarm output All *, ** and *** alarms
situation controlled on
• Alarm output #15 is by default alarm class basis
controlled on the basis of all alarms of
type ***ALARM, **ALARM, and
*ALARM

25 © Nokia Siemens Networks RN33153EN20GLA0

RN33153EN20GLA0 25
RNC Maintenance and Fault Management in RNC

Structure of Short Alarm Printout

Type of alarm printout: Recovery information:

none Normal alarm printout *RCY* recovery was informed of the alarm in
HST Alarm history printout order to start automatic recovery actions
UPD Alarm update printout for the object of the alarm
PLA Printout directly from *DIS* current operative state of the RNW object
platform alarm system is disabled
(Consecutive number) & *ENA* current operative state of the RNW object
Alarm object - index, probably faulty is enabled

HST (47546) MXU-0 *RCY* 2009-05-26 15:34:56.91

** 3050 NO RESPONSE FROM PLUG-IN UNIT

Alarm number & alarm text

Alarm class i.e. the urgency level of alarm
*** requires immediate actions
** requires actions during normal working hours
* normally no actions required

26 © Nokia Siemens Networks RN33153EN20GLA0

1. Type of alarm printout

HST Alarm history printout
UPD Alarm update printout (when printing out all live alarms at defined
time of the day)
PLA Alarm printout directly from the platform alarm system (indicating
problems in the functioning of the Network element level alarm system)

In case of normal alarm printout, the field is empty.

2. Consecutive number
Failure printouts (***, **, *) are numbered in ascending order. With the help of the number,
the operating personnel can follow the update and cancel printouts of the original failure
printout.
3. Alarm object
The object of the alarm, expressed either as a single object or in the form of an object
hierarchy.
The alarm object hierarchy consists of five levels at maximum. The first object (the
leftmost in the alarm printout) in the hierarchy identifies the alarm object at the most
general level. The next object in the hierarchy is always a subobject of the preceeding
one. Thus, it increases the accuracy of the object identification. Typically the alarm object
is a functional unit or an I/O device. If the alarm is not targeted to any particular object,
this field displays NONE.
If the object (or any of the objects in the object hierarchy) is unknown, its value is
displayed as such (as hexadecimal number) in the alarm printout.
If all of the object names in the object hierarchy do not fit to the field, a question mark (?)
is displayed as the last character in the field.

RN33153EN20GLA0 26
RNC Maintenance and Fault Management in RNC

4. Recovery information
This field displays *RCY*, when the alarm system informs the recovery of the alarm. After
this, the recovery starts automatic recovery actions for the object of the alarm.
5. Date
The setting or cancellation date of the alarm. Only month and day are displayed.
6. Time
The setting or cancellation time of the alarm.
7. Urgency level
Alarms are classified according to their criticality from the user's point of view:
*** requires immediate actions
** requires actions during normal working hours
* normally no actions required

The urgency level is output in all alarm printouts except notices (NOTICE). The urgency
levels in alarm cancellation printouts are indicated by dots (.) instead of asterisks (*).
8. Alarm number
An unambiguous identifier of an alarm. The alarm number is also a search index for the
alarm description.
9. Alarm text
A short description of the event that caused the alarm.

RN33153EN20GLA0 27
RNC Maintenance and Fault Management in RNC

Structure of Long Alarm Printout

Alarm Event Type (COMM, QUAL, PROC, ENVIR)
Network Element

Printout Type (CANCEL, DISTUR,NOTICE) Alarm Object Recovery Info

Consecutive Number Alarm Object location Info Date & Time

( 47546) IPA_HKI-LAB 1A2 - 0 - 9 EQUIPM *RCY* 2009-03-26 18:52:56.91

** ALARM MXU-0
3050 NO RESPONSE FROM PLUG-IN UNIT
HMALAR OMU-0
MX622- A 01 03 09
Alarm Text
Alarm Issuer

Alarm Number Computer Sending Alarm

Urgency Level Supplementary Info Fields (PIU type/Rack No/Subrack No/SlotNo.)

28 © Nokia Siemens Networks RN33153EN20GLA0

1. Type of alarm printout

HST Alarm history printout
UPD Alarm update printout (when printing out all live alarms at defined
time of the day)
PLA Alarm printout directly from the platform alarm system (indicating
problems in the functioning of the Network element level alarm system)

In case of a normal alarm printout, the field is empty.

2. Consecutive number
Failure printouts (***, **, *) are numbered in ascending order. With the help of the number,
the operating personnel can follow the update and cancel printouts of the original failure
printout.
3. Name of the network element
4. Name of the remote object (4 characters)
Printed only if the object of the alarm is located in a remote object that has been named
during the configuration of the system.

RN33153EN20GLA0 28
RNC Maintenance and Fault Management in RNC

5. Location information of the alarm object

The location of the alarm object is expressed either with the position co-ordinates of a
subrack and a plug-in unit position address (PPA), or with the HMS (Hardware
Management System) addressing. This depends on how the operator has given the
location information when configuring the alarm object to the system.
The position co-ordinates of the subrack and PPA are output in the form RIV-H-P, where:
R (1...64) is the number of the cabinet row
I (A...Z) is the cabinet identifier in the cabinet row
V (0...10) is the vertical deviation of the subrack in the cabinet
H (0...10) is the horizontal deviation of the subrack in the cabinet
P (1...38) is the PPA number of the plug-in unit in the subrack

HMS addressing is output in the form C-S-P, where:

C (1...15) is the HMS number of the cabinet
S (1...7) is the HMS number of the subrack
P (1...38) is the PPA number of the plug-in unit in the subrack

The location information displayed in the alarm printout does not necessarily contain all
the parts mentioned above. Its accuracy is determined on the basis of the hardware
component which contains the object of the alarm. For example, if the object of the alarm
consists of more than one plug-in unit, the PPA number is not displayed, or if an alarm
concerns the whole cabinet, only RI (or C) is displayed. An unknown location information
is printed as ?????-??-??
6. Alarm event type
Categorization of the alarm for the network management system (NMS). Five basic
categories are specified according to the CCITT Rec. X.733:
COMM communications alarm. Principally associated with the procedures
and/or processes required to convey information from point to point
QUAL quality of service alarm. Principally associated with a degradation
in the quality of service
PROCES processing error alarm. Principally associated with a software or
processing fault
EQUIPM equipment alarm. Principally associated with an equipment fault
ENVIR environmental alarm (= external alarm). Principally associated with
a condition relating to an enclosure in which the equipment resides

7. Recovery information
This field displays *RCY* when the alarm system informs the recovery of the alarm. After
this, the recovery starts automatic recovery actions for the object of the alarm.
8. Date
Setting or cancellation date of the alarm
9. Time
Setting or cancellation time of the alarm

RN33153EN20GLA0 29
RNC Maintenance and Fault Management in RNC

10. Urgency level

Alarms are classified according to their criticality from the user's point of view:
*** requires immediate actions
** requires actions during normal working hours
* normally no actions required

The urgency level is output in all alarm printouts except notices (NOTICE). The urgency levels in
alarm cancellation printouts are indicated by dots (.) instead of asterisks (*).
11. Printout type:
ALARM fault situation
CANCEL fault terminated
DISTUR disturbance
NOTICE notice

12. Alarm object

The object of the alarm, expressed either as a single object or in the form of an object hierarchy.
The alarm object hierarchy consists of five levels at maximum. The first object (the leftmost in the
alarm printout) in the hierarchy identifies the alarm object at the most general level. The next
object in the hierarchy is always a subobject of the preceeding one. Thus, it increases the
accuracy of the object identification. Typically the alarm object is a functional unit or an I/O
device. If the alarm is not targeted to any particular object, this field displays NONE.
If the object (or any of the objects in the object hierarchy) is unknown, its value is displayed as
such (as hexadecimal number) in the alarm printout.
If all of the object names in the object hierarchy do not fit to the field, a question mark (?) is
displayed as the last character in the field.
13. RNW object name
User defined name for the alarming Radio Network object.
Note that this field is possible only for alarms concerning radio network objects. If no name has
been defined for the object, the whole line is left out from the alarm printout.
14. Alarm number
An unambiguous identifier of an alarm. The alarm number is also a search index for the alarm
description.
15. Alarm text
A short description of the event that caused the alarm.
16. Alarm issuer
The program block issuing the alarm.
If the name of the program block issuing the alarm is not available, the family identifier of the
program block is output in a hexadecimal form.
17. Computer sending the alarm
The computer unit in which the alarm was issued.
18. Trial information
If the network element has been divided into a original slice and a trial slice (that is, a trial
configuration is in force), this field displays information on which slice the alarm object belongs
to. One of the texts ORIG or TRIAL is displayed.
If the alarm object is not a computer unit belonging to the HW configuration of the network
element itself, the trial information is displayed according to the computer unit in which the alarm
was issued.

RN33153EN20GLA0 30
RNC Maintenance and Fault Management in RNC

19. Processing information

If the alarm is set before the start-up of the distributed part of the platform alarm system, this
field displays LIB. The system cancels this kind of alarm immediately after its setting. Note that
in this case the cancellation does not indicate the termination of the fault that caused the alarm.
20. Flow control information (NMS)
If sending the alarm to network management system Nokia NetAct has been prevented, this
field displays NMS.
21. Flow control information (LPT)
If printing the alarm via logical files has been prevented, this field displays LPT.
22. Flow control information (OUT)
If the effect of the alarm on the state of an external alarm output has been prevented, this field
displays OUT.
23. Flow control information (RCY)
If the effect of the alarm on activating recovery actions has been prevented, this field displays
RCY.
24. Supplementary information fields
A maximum of 32 fields which are separated from one another by one or several spaces. If all
the fields do not fit into one line, they are printed out on two lines. The left margin of the line is
shifted left if printing the fields on two lines can be avoided by that. The following are the
possible values of the fields:
- a hexadecimal number (e.g. 0120)
- a decimal number (e.g. 288d)
- a BCD coded number (e.g. 0288)
If the number is BCD coded, it is mentioned in the alarm
reference manual in the explanation of the field in question
- a single character or characters (e.g. ULHISTGX)
- a functional unit (e.g. OMU)
- a plug-in unit (e.g. EHAT)
- a working state of a unit (e.g. WO-EX)
- a date (e.g. 2008-05-13)
- a time (e.g. 11:14:42.19)
- an IPv4 address (e.g. 131.255.0.12)
- an IPv6 address (e.g. 1080:0:FE:0:0:225:34:FFFF)

In addition, the value of a certain field (for example, the index of a functional unit or the index of
a plug-in unit) can be displayed as two dots (..).In this situation the field cannot be given a
single value according to its meaning.
If the amount of supplementary information data does not match with the formatting
information, a question mark (?) is printed at the end of the fields.
25. Supplementary text
A more detailed text printed out in some alarms. The left margin of the line is shifted left if the
text is longer than 76 characters.
Please note that this field may not be identical between the setting and cancellation printouts of
the alarm.
26. Alarm operating instructions
Operating instructions the user may have defined for an alarm. The left margin of the line is
shifted left if the text is longer than 76 characters

RN33153EN20GLA0 31
RNC Maintenance and Fault Management in RNC

Alarm Reference
• Alarm number
• Alarm manual is the main – Notices (0 – 999)
reference for alarm handling – Disturbances (1000 – 1999)
– Failure printout (2000 – 3999)
• It is available on
– NED, as part of WCDMA RAN – Diagnosis reports (3700 – 3999)
System documentation – Base Station alarms (7000 – 7999)
– FM Application – RNC OMS alarms (>70000)
– Alarm Monitor

(Alarm Monitor)
(FM)
32 © Nokia Siemens Networks RN33153EN20GLA0

According to the alarm type and the origin of the alarm, the numbering of the alarms
conforms with the following:

Alarm number
Notices 1 - 999
Disturbance Printouts 1000 - 1999
Failure Printouts 2000 - 3999
External Alarms 4000 — 5999
Base Station Alarms 7000 — 7999
Diagnosis Reports are numbered with the numbers 3700 – 3999.

RN33153EN20GLA0 32
RNC Maintenance and Fault Management in RNC

Alarm Reference
Alarm number
and text
Full description

Additional
information

Instruction in
handling the alarm

Cancelling
information
33 © Nokia Siemens Networks RN33153EN20GLA0

RN33153EN20GLA0 33
RNC Maintenance and Fault Management in RNC

RNC Alarm Handling

• Handle in various ways:
– MMI system
▪ Active Alarms Handling command group <AA_>
▪ Alarm History Handling command group <AH_>
– Element Manager
▪ Fault Management (FM) Application
– NetAct
▪ Alarm monitor
• Alarm Operation
– Display active alarm
– Display historical alarm
– Cancel alarm
– Block Alarm
– Display alarm statistics (with FM applications)

34 © Nokia Siemens Networks RN33153EN20GLA0

Each alarm event, alarm and its cancellation, not filtered by the alarm system, is saved in
a log file. This log data is called alarm history. Using the AH command group commands,
you can display the history data concerning the system's alarm situation.

You can either display the alarm history, or merely the active alarms, on the selected
output device.

An IPA 2800 alarm whose object unit is not in the normal working state is normally filtered
by the alarm system. When the alarm is filtered (by any means), it is neither printed out
nor stored in the alarm history. However, an alarm that is filtered purely on the basis of
the state of its object unit is printed out when displaying active alarms.
The alarm history can be useful in troubleshooting situations. By analyzing the alarm
history data you may be able to find trends or patterns on how and when the alarms
occur.

RN33153EN20GLA0 34
RNC Maintenance and Fault Management in RNC

Alarms Handling Commands

Command Description
Group
AA ACTIVE ALARM HANDLING
AE ERROR RATIO COUNTER HANDLING
AF ALARM FLOW HANDLING
AH ALARM HISTORY HANDLING

AL ALARM OUTPUT HANDLING

AO ALARM OPERATING INSTRUCTION HANDLING

AP ALARM PARAMETERS HANDLING
AQ EXTERNAL ALARM CONNECTIONS HANDLING
AR ALARM SYSTEM RULEBASE HANDLING
AT ALARM PRINTING HANDLING

35 © Nokia Siemens Networks RN33153EN20GLA0

AA - ACTIVE ALARM HANDLING

Commands in the command group are used for cancelling and displaying alarms
currently on.

AE - ERROR RATIO COUNTER HANDLING

You can use the commands of this command group to handle the parameters of an error
ratio counter.

AF - ALARM FLOW HANDLING

The commands in this command group are used for controlling the alarm flow in the
alarm system.

With the command group commands, you can block the alarm completely and
remove blocking prevent the alarm system from sending the alarm information to one
or more alarm indication instances, for example, the network management system
NetAct allow the alarm system to send the alarm information to one or more alarm
indication instances, if it has been prevented.cdisplay the blocking information of the
alarms and alarm indication instances.

AH - ALARM HISTORY HANDLING

Use the commands in this command group to display alarm history.

RN33153EN20GLA0 35
RNC Maintenance and Fault Management in RNC

AL - ALARM OUTPUT HANDLING

Use the commands in this command group to:
-Display the state and controlling information of the alarm outputs
-Set alarm outputs to the alarm state and remove alarm outputs from the alarm state
-Modify the controlling of the alarm outputs

AO - ALARM OPERATING INSTRUCTION HANDLING

The commands in this command group are used for handling alarm specific operating
instructions.

AP - ALARM PARAMETERS HANDLING

Use the commands in this command group for modifying and listing alarm parameters in
the alarm system.

AQ - EXTERNAL ALARM CONNECTIONS HANDLING

AR - ALARM SYSTEM RULEBASE HANDLING

Use the commands in this command group to add, delete, modify, output and restore the
rules in the alarm system rulebase.

AT - ALARM PRINTING HANDLING

The commands of the command group are used to
disable and enable the printing of alarms by alarm classes
display the printing states of alarm classes
set and display the times when active alarms are output on the local output device.

RN33153EN20GLA0 36
RNC Maintenance and Fault Management in RNC

Active Alarm Handling

AA - ACTIVE ALARM HANDLING

The commands in this command group are:

AAN : CANCEL ALARM ACCORDING TO CONSECUTIVE NUMBER

AAE : CANCEL ALARM ACCORDING TO ALARM NUMBER OR OBJECT

AAP : DISPLAY ACTIVE ALARMS

AAO : DISPLAY ACTIVE ALARMS OF CERTAIN OBJECT

37 © Nokia Siemens Networks RN33153EN20GLA0

RN33153EN20GLA0 37
RNC Maintenance and Fault Management in RNC

Example of Active Alarms Handling

Display all active (***) stars alarms of object OMU

• AAP:OMU:CLS=AL3;

Display all active alarms of object OMU-0,DMCU-1

• AAP:OMU,0,DMCU,1;

Display all (**) stars active alarms

• AAP::CLS=AL2;

Display all active alarms. Use the short alarm format.

• AAP:::S;

38 © Nokia Siemens Networks RN33153EN20GLA0

RN33153EN20GLA0 38
RNC Maintenance and Fault Management in RNC

Example of Active Alarms Handling : ZAAP

AAP::CLS=AL2;

39 © Nokia Siemens Networks RN33153EN20GLA0

RN33153EN20GLA0 39
RNC Maintenance and Fault Management in RNC

Alarm History Handling

AH - ALARM HISTORY HANDLING

The commands in this command group are:

AHP : DISPLAY ALARM HISTORY

AHO : DISPLAY ALARM HISTORY OF CERTAIN OBJECT

AHR : RESIZE ALARM HISTORY

40 © Nokia Siemens Networks RN33153EN20GLA0

RN33153EN20GLA0 40
RNC Maintenance and Fault Management in RNC

Example of Alarm History

Display all alarms that occurred today, using the default
alarm format.
• AHP;

Display all alarms concerning object MXU-0 that require

immediate actions (***).
• AHP:MXU,0:CLS=AL3;

Display all alarms concerning object OMU-0, MXU-1 that

require immediate actions (***), beginning 15 Jan 2010 and
ending today.
• AHP:OMU,0,MXU,1:CLS=AL3:2010-01-15;

41 © Nokia Siemens Networks RN33153EN20GLA0

RN33153EN20GLA0 41
RNC Maintenance and Fault Management in RNC

Example Alarm History : ZAHO

AHO:OMU;

* More information in
“Alarm Handling” module

42 © Nokia Siemens Networks RN33153EN20GLA0

RN33153EN20GLA0 42
RNC Maintenance and Fault Management in RNC

Checking Blocked Alarms : Z AFP

AFP:::;
AFP:::;

RNC IPA2800
BLOCKED ALARMS

NBR ALARM TEXT

INH OBJECT
BLOCKING TYPE / PREVENTED INDICATION INSTANCES
START TIME END TIME
----------------------------------------------------------------------
7799 RNC RADIO NETWORK TEST ALARM
ALL
PREVENTED :NMS LPT

COMMAND EXECUTED

43 © Nokia Siemens Networks RN33153EN20GLA0

RN33153EN20GLA0 43
RNC Maintenance and Fault Management in RNC

Exercise : Alarm system

1. Display the Alarm System Administration menu.

_____________________________________________________

2. Display the Alarm Parameters Handling menu.

_____________________________________________________

3. Display the menu for Handling Active Alarms.

_____________________________________________________

44 © Nokia Siemens Networks RN33153EN20GLA0

RN33153EN20GLA0 44
RNC Maintenance and Fault Management in RNC

Exercise : Active alarms and Alarm History

Handling
1. By referring to the Alarm Reference Manual, find out which fault causes
the alarm with the alarm number 2692?

_____________________________________________________

2. Display all alarms currently in the ON state (= active alarms).

_____________________________________________________

3. Display all ** alarms and *** alarms for the OMU’s (active and history)

_____________________________________________________

_____________________________________________________

45 © Nokia Siemens Networks RN33153EN20GLA0

4. Display ** alarms which have occurred after date ___ ___ ___.

_____________________________________________________

5. Look for all working state change notices (alarm number 690)

of the OMU’s that have occurred since date ___ ___ ___.

_____________________________________________________

6. Show all the alarms that have appeared in the _______ today after 8 a.m.

_____________________________________________________

What is the difference between alarm history and active alarms?

(Hint: Check the listings!)

_____________________________________________________

_____________________________________________________

_____________________________________________________

RN33153EN20GLA0 45
RNC Maintenance and Fault Management in RNC

Exercise : Alarm Blocking and Alarm Cancelling

1. Select Alarm number ______ and block the Alarm

_____________________________________________________

2. Output blocked alarms

_____________________________________________________

3. Select Alarm number ______ and cancel the alarm

_____________________________________________________

4. Check the result of cancel alarm

_____________________________________________________

46 © Nokia Siemens Networks RN33153EN20GLA0

RN33153EN20GLA0 46
RNC Maintenance and Fault Management in RNC

How to use Nokia Siemens Networks

PPT template colours
Primary colours Supporting colours Example forms
R 255 R 153
G 204 G 153
B0 B 153

R 255 R 102
G 153 G 102
B0 B 102

R 102
G0
B 102

Delete this slide

1st Qtr
once slide set 2nd Qtr
3rd Qtr
preparation is 4th Qtr

complete
47 © Nokia Siemens Networks RN33153EN20GLA0

RN33153EN20GLA0 47