Alarm Rnc Alarm Structure

8/10/2019 Alarm Rnc Alarm Structure

http://slidepdf.com/reader/full/alarm-rnc-alarm-structure 1/12

WCDMA RAN, Rel. RU40,

Operating Documentation,

Issue 02

Alarm Structure for IPA-RNC

DN00158394

Issue 04

Approval Date 2013-01-16

Confidential



2 DN00158394

Issue 04


Id:0900d805809987e4

Confidential

The information in this document is subject to change without notice and describes only the

product defined in the introduction of this documentation. This documentation is intended for the

use of Nokia Siemens Networks customers only for the purposes of the agreement under whichthe document is submitted, and no part of it may be used, reproduced, modified or transmitted

in any form or means without the prior written permission of Nokia Siemens Networks. The

documentation has been prepared to be used by professional and properly trained personnel,

and the customer assumes full responsibility when using it. Nokia Siemens Networks welcomes

customer comments as part of the process of continuous development and improvement of the

documentation.

The information or statements given in this documentation concerning the suitability, capacity,

or performance of the mentioned hardware or software products are given "as is" and all liability

arising in connection with such hardware or software products shall be defined conclusively and

finally in a separate agreement between Nokia Siemens Networks and the customer. However,

Nokia Siemens Networks has made all reasonable efforts to ensure that the instructions

contained in the document are adequate and free of material errors and omissions. Nokia

Siemens Networks will, if deemed necessary by Nokia Siemens Networks, explain issues which

may not be covered by the document.

Nokia Siemens Networks will correct errors in this documentation as soon as possible. IN NO

EVENT WILL Nokia Siemens Networks BE LIABLE FOR ERRORS IN THIS DOCUMENTA-

TION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL, DIRECT, INDI-

RECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUT NOT LIMITED

TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESS OPPORTUNITY

OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT OR THE INFORMATION

IN IT.

This documentation and the product it describes are considered protected by copyrights and

other intellectual property rights according to the applicable laws.

The wave logo is a trademark of Nokia Siemens Networks Oy. Nokia is a registered trademark

of Nokia Corporation. Siemens is a registered trademark of Siemens AG.

Other product names mentioned in this document may be trademarks of their respectiveowners, and they are mentioned for identification purposes only.

Copyright © Nokia Siemens Networks 2013. All rights reserved

f Important Notice on Product SafetyThis product may present safety risks due to laser, electricity, heat, and other sources

of danger.

Only trained and qualified personnel may install, operate, maintain or otherwise handle

this product and only after having carefully read the safety information applicable to this

product.

The safety information is provided in the Safety Information section in the “Legal, Safety

and Environmental Information” part of this document or documentation set.

The same text in German:

f Wichtiger Hinweis zur ProduktsicherheitVon diesem Produkt können Gefahren durch Laser, Elektrizität, Hitzeentwicklung oder

andere Gefahrenquellen ausgehen.

Installation, Betrieb, Wartung und sonstige Handhabung des Produktes darf nur durch

geschultes und qualifiziertes Personal unter Beachtung der anwendbaren Sicherheits-

anforderungen erfolgen.

Die Sicherheitsanforderungen finden Sie unter „Sicherheitshinweise“ im Teil „Legal,

Safety and Environmental Information“ dieses Dokuments oder dieses Dokumentations-

satzes.



DN00158394 3


Id:0900d805809987e4

Confidential

Table of contentsThis document has 12 pages.

Summary of changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

1 Alarm Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

1.1 Alarm descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

1.2 Structure of the alarm description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

1.3 Structure of the long alarm printout . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

1.4 Structure of the short alarm printout . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

1.5 Example of an alarm printout. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11



4 DN00158394


Id:0900d805809987e4

Confidential

List of figuresFigure 1 Structure of the long alarm printout. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Figure 2 Structure of the short alarm printout . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10



DN00158394 5

Alarm Structure for IPA-RNC Summary of changes

Id:0900d8058099843f

Confidential

Summary of changesChanges between document issues are cumulative. Therefore, the latest document

issue contains all changes made to previous issues.

Changes between issues 3-2 (2009-09-17, RU20) and 04 (2013-01-16, RU40)

The product name IPA-RNC is added in the document title.

MX622-A information is replaced with MX1G6-A in the example printout.

Changes made between issues 3–2 and 3–1

Editorial corrections have been made, no changes in the technical content.


Structure of the alarm description

Added information on External Alarms numbers.

Structure of the long alarm printout

Added that the supplementary text field (25) might not be identical between the setting

and cancellation printouts of an alarm.

Added that the left margin of the line is shifted left if the text in fields 25 and 26 is longer

than 76 characters.


Structure of the alarm description

Chapter updated.


Added information about the second line reserved for supplementary information fields.

Updated the explanation of the field “Supplementary information fields”.



The description of the alarm printout field 'Trial information' has been updated.

Example of an alarm printout

The example of an alarm reference manual page has been updated.



6 DN00158394


Id:0900d80580998440

Confidential

Alarm Structure

1 Alarm Structure

1.1 Alarm descriptionsThe Alarm Reference Manual is intended for the operating personnel. It describes the

alarms and diagnosis reports printed out on an alarm output device and contains, when

necessary, instructions for corrective maintenance actions.

The manual contains the alarms of all applications, and therefore it is possible that it also

contains alarms that do not belong to the configuration of a particular customer.

The user of this manual is assumed to understand the operation and the maintenance

of the system. For more information on the alarm system, see About alarm system in

Alarm Administration.

1.2 Structure of the alarm description Alarms are divided into three groups according to the alarm type. The types are notice,

disturbance printout, and failure printout. Also alarm descriptions are divided according

to these three types.

Alarms of each alarm type are described in a separate document (Notices, Disturbance

Printouts, and Failure Printouts). Also diagnosis report descriptions have the same

structure as alarm descriptions, and they are also described in a separate document,

Diagnosis Reports.

According to the alarm type and the origin of the alarm, the numbering of the alarms

conforms with the following:

alarm numberNotices 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.

The description of an alarm in the Alarm Reference Manual always contains the follow-

ing parts:

Alarm number Decimal number on the upper corner of the page

Alarm text Text in the alarm printout

Meaning Verbal explanation of the reason for the alarm and of its impact

Supplementary information fields Interpretation of supplementary information fields, if

there are any. The supplementary information fields are indexed from 1

to 32 from left to right.

Instructions Operating instructions for all alarms with urgency level ** or ***. Instruc-

tions can also be given for alarms or disturbances with the urgency level

*, but normally they require no actions from the operating personnel.

The instructions are either in written form or in the form of an operating

sequence.



DN00158394 7

Alarm Structure for IPA-RNC Alarm Structure

Id:0900d80580998440

Confidential

Cancelling Information on whether the operating personnel should cancel the

alarm, or whether the system does it after the fault situation is over.

A diagnosis report description contains the same parts as the alarm description.

However, a diagnosis report is never cancelled.

1.3 Structure of the long alarm printout

Figure 1 Structure of the long alarm printout

g In the figure above, the fields marked with the text “optional field” contain user defined

data. If no such data has been defined and the optional field is the only field in the line,

the line is not printed so that there are no empty lines in the alarm printout. According to

the same principle, if the alarm in question does not have any supplementary informa-

tion fields, the line containing supplementary information fields is not printed. The

second line reserved for supplementary information fields is used only if the supplemen-

tary information fields of the alarm do not fit into one line.

1. Type of alarm printout

HST Alarm history printoutUPD 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 element4. 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.

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 rowI (A...Z) is the cabinet identifier in the cabinet row

21 3 4 5 6 8 9

10 11 12

13 (optional field)

14 15

16 17 18 1 9 20 21 22 23

24

(24)

25 (optional field)

7

26 (optional field)



8 DN00158394


Id:0900d80580998440

Confidential

Alarm Structure

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 typeCategorization 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 resides7. 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

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



DN00158394 9


Id:0900d80580998440

Confidential

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 preceed-

ing 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 print-

out.

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 iden-

tifier 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.

19. Processing information

If the alarm is set before the start-up of the distributed part of the platform alarmsystem, 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 termina-

tion of the fault that caused the alarm.

20. Flow control information (NMS)

If sending the alarm to network management system Nokia NetAct has been pre-

vented, 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.



10 DN00158394


Id:0900d80580998440

Confidential

Alarm Structure

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.

1.4 Structure of the short alarm printout

Figure 2 Structure of the short alarm printout

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.

31 4 5 62

8 97



DN00158394 11


Id:0900d80580998440

Confidential

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 preceed-

ing 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.

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.

1.5 Example of an alarm printout

An example of an alarm printout, both long and short format, and the description of the

alarm in the alarm reference manual are presented below.

Alarm printout in long format:

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

** ALARM MXU-0

3050 NO RESPONSE FROM PLUG-IN UNIT

HMALAR OMU-0



12 DN00158394


Id:0900d80580998440

Confidential

Alarm Structure

MX1G6–A 01 03 09

Alarm printout in short format:

(47546) MXU-0 *RCY* 03-26 18:52:56.91** 3050 NO RESPONSE FROM PLUG-IN UNIT

Page from the alarm reference manual:

3050

NO RESPONSE FROM PLUG-IN UNIT

MEANING The plug-in unit does not respond to the HMS messages sent to it.

The plug-in unit is damaged or the connection to the plug-in unit

is cut. When the alarm is on, the HMS communication is not working

to/from the plug-in unit. E.g. hw-alarms and restart notifications are not received from the plug-in unit, and the forced reset and

separation from use cannot be done to the plug-in unit.

SUPPLEMENTARY

INFORMATION

FIELDS 1 type of the plug-in unit detecting the fault

2 number of the rack in which the plug-in unit is located

3 number of the subrack in which the plug-in unit is located

4 location of the plug-in unit in the subrack (= slot number)

INSTRUCTIONS Check the cabling between the subracks and the wiring of the

backplate, see instructions on interconnection cables. If the

cabling is correct and this alarm concerning the other plug-in

units of the subrack is not on, the fault is obviously in the

plug-in unit. Change the faulty plug-in unit indicated in the

additional information of the alarm, see instructions on

replacing plug-in units.

If the alarm concerning the other plug-in units of the subrack is

on as well, the HMS-bridge might be damaged. Change the plug-in

unit of the subrack indicated in the additional information of

the alarm, the plug-in unit which has the HMS-bridge node of the

subrack.

CANCELLING Cancel the alarm with an MML command after correcting the fault

as presented in INSTRUCTIONS. See alarm administration instructions.

Alarm Rnc Alarm Structure

Documents

Transcript of Alarm Rnc Alarm Structure