Resolve Switching Alarm

T036-G
Nokia
S/W Revision : MS/!"R M#
$S S%
&M/NMS'000 T(0
!/W Revision : )*'00
&+,ective
To handle the switching alarm in systematical way and to understand the switching alarm behavior in each
fault group.
A+stract
This document describes the procedure of how to resolve switching alarms. Switching alarms are the alarms
which are generated within the switching system. These alarms can be caused either by software faults (for
example, program block failures, incompatible or wrong data in the system data files) or can be caused by
hardware faults (for example, plug in unit failure).
The surveillance engineer is responsible for repairing some of the faults. Faults like this involve, for instance,
replacing the faulty program block or data file when software fault occurs. n case of hardware alarms, he
need to identify the failing plug!in unit. f a site visit is needed to replace a faulty plug!in unit, he should then
inform the Field "aintenance personnel.
-rere./isite
The alarm system handles the fault and disturbance observations occurring in the exchange. The alarm
system is part of the exchange#s maintenance system. The supervision system detects the faults and reports
them to the alarm system. $larms can be caused by both the hardware and the software. The alarm system
tries to specify the functional unit in which the fault or disturbance has occurred, whereupon recovery actions
can be activated for it. The user is informed of the fault situation by alarm printouts and lamp panel controls.
The recovery system eliminates the effect of the fault by separating the faulty unit from the rest of the system
and, if possible, by replacing it with a back!up unit. %nce the fault has been eliminated, the fault diagnosis is
activated automatically. The fault diagnosis indicates the suspect plug!in unit.
&osition of alarm system in system maintenance of the exchange
$larm print!outs are divided into ' categories. These are notices ((%T)*), disturbance print!outs (+ST,-),
and failure print!outs ($.$-").
From the user#s point of view, the most important information produced about alarms is the urgency level. t is
output in connection with all alarms with the exception of notices. The urgency levels are/
+ocument (o/ %0"!&1S234!T5'6!7!(okia $S 0 (okia )onfidential -ev./$2 +ate/489529:: &age 49;
Resolve Switching Alarm
T036-G
Nokia
S/W Revision : MS/!"R M#
$S S%
&M/NMS'000 T(0
!/W Revision : )*'00
<<< immediate actions re=uired
<< actions re=uired during working hours
< no actions re=uired
$n alarm re=uiring immediate actions is given when the system has failed in such a way that its function has
totally terminated or threatens to terminate. The operation personnel must take immediate actions. $n attempt
is always made to print the alarm onto the alarm printer. n addition to controlling the alarm printer, this alarm
controls the alarm outputs indicating the alarm situation according to the unit type (switching, transmission,
%0", power, and external e=uipment).
$n alarm re=uiring actions during working hours is given when the failure does not threaten to terminate the
functioning of the entire system. Failures occurring during working hours should be repaired immediately. The
repair can, however, be done on the following day, if the failure occurs outside working hours. The alarm is
normally printed onto the alarm printer. n addition to controlling the alarm printer, all the alarms re=uiring
actions during working hours control a common alarm output.
$n alarm re=uiring no actions is typically given for a temporary failure. t does not necessitate any user
actions. The alarm is normally printed onto the alarm printer.
7eneration of software alarms/
The alarm system constantly monitors the functioning of the software modules in the switch (called >program
blocks?). The program blocks are software routines, which are running under the control of
the +@255 %perating System. The program blocks contain the software codes, which the
central processor of the different computer units has to execute. *ach program block is
assigned by the operating system to perform a given specific task (for example, $AB1FS@
program block controls the operation of the $!interface, $1B1@S@ program block controls
the $bis!interface, --"B1@S@ program block manages the allocation and release of -adio
-esources, etc.). There are hundreds of program blocks in a +@255 switch, each performing
its own uni=ue function. $ program block communicates with other program blocks by
exchanging data (called >messages?). This is so, because a program block normally re=uire
the services of other program blocks in order to perform its destined task (for example, the
C$SB1@S@ re=uires the services of --"B1@S@ in order to handle handover execution). So
the program blocks monitor each other through the exchange of messages and can detect
failures on the other program blocks (if the other program block does not respond or gives
the wrong response). The detecting program block then informs the alarm system about this
and gives the identity of the failing program block. $n alarm is then generated and reported
by the alarm system.
+ata files are the files which contain the information needed by the program blocks in order to carry out their
task. The program blocks operates on the data contained in these files (examples are subscriber data,
hardware configuration data, -adio (etwork data, etc.). The different logical files are also example of data
files. There are hundreds of data files in a +@255 switch. $ program block monitors the integrity of the data
contained in the data file it is operating on. The validity of the data is checked by comparing it against some
corresponding data contained in related data files to verify its consistency. f the program block had detected
the data to be erroneous or inconsistent (for example, attempting to perform read9write operations on a non!
+ocument (o/ %0"!&1S234!T5'6!7!(okia $S 0 (okia )onfidential -ev./$2 +ate/489529:: &age 29;
Resolve Switching Alarm
T036-G
Nokia
S/W Revision : MS/!"R M#
$S S%
&M/NMS'000 T(0
!/W Revision : )*'00
existent logical file, hardware configuration data not consistent with the actual physical hardware
configuration of the e=uipment, invalid &)" configuration), then the detecting program block informs the
alarm system about this and gives the identity of the failing data file. $n alarm is then generated and reported
by the alarm system.
7eneration of hardware alarms/
The alarm system also monitors the functioning of the hardware units in a +@255 switch. 3hen the alarm
system detects an hardware fault, it tries to specify the functional unit in which the fault or disturbance has
occurred, then informs the recovery system about the fault situation. The recovery system then automatically
activates the recovery actions on the failing unit. The user is informed of the fault situation by alarm printouts
and lamp panel controls. The recovery system eliminates the effect of the fault by separating the faulty unit
from the rest of the system and, if possible, by replacing it with a back!up unit. %nce the fault has been
eliminated, the fault diagnosis is activated automatically on the failing functional unit. The fault diagnosis
indicates the suspect plug!in unit within the functional unit.
Structure of alarm printout in +@255 systems/
+escription of the alarm printout fields/
4. Type of alarm printout
Standard alarm printout
D,&+TE $larm update printout
2. *xchange dentification
'. -emote subscriber stage (F characters)
&rinted only if the obGect of the alarm is in a remote subscriber stage.
The remote subscriber stage (-SS) is a system used in +@225 (Fixed .ine switch). t refers to a
functional unit that is considered as an extension part of the Fixed .ine switch. The -SS consist of
hardware units enclosed in its own cabinet frame and is located physically away from the Fixed
.ine switch. The -SS is controlled remotely by the Fixed (etwork Switch through an
interconnecting &)" link.
The -SS is used only in +@245 and +@225 Fixed .ine switches and is never used in +@255
7S"9+)S switches.
F. )omputer ,nit sending the alarm
H. $larm e=uipment type
+ocument (o/ %0"!&1S234!T5'6!7!(okia $S 0 (okia )onfidential -ev./$2 +ate/489529:: &age '9;
Resolve Switching Alarm
T036-G
Nokia
S/W Revision : MS/!"R M#
$S S%
&M/NMS'000 T(0
!/W Revision : )*'00
S3T)C switching e=uipment
%0" operation and maintenace e=uipment
T-$(S" transmission e=uipment
&%3*- power e=uipment
*@T*-( external e=uipment
,nknown e=uipment type is printed as IIIIII
6. +ate and time
Start time or termination time of the alarm Dyyyy!mm!ddE Dhh/mm/ssE
;. ,rgency level
<<< re=uires immediate actions
<< re=uires actions during normal
working hours
< no actions re=uired
,nknown urgency level is printed as a =uestion mark (I).
The urgency level is output in all alarm printouts except notices ((%T)*). The urgency levels of
terminated alarms are indicated by dots (.) instead of asterisks (<).
8. &rintout type
$.$-" fault situation
)$()*. fault terminated
+ST,- disturbance
(%T)* notice
:. $larm obGect
The functional unit which is the obGect of the alarm.
f the obGect of the alarm is not a functional unit, the field displays eight dots (.).
45. &osition coordinates of alarm obGects
&osition coordinates are expressed in the form -TJ!A, where/
- (4...6F) is the rack row
T ($...K) is the rack
J (554..2HH) is the vertical position of the subrack or cartridge in the rack
A (55...::) is the horiLontal position of the subrack or cartridge in the rack
f a rack is the obGect of an alarm, only -T is displayed. $n unknown position coordinate is printed
as IIIIII!II
44. $larm issuer
The program block issuing the alarm.
42. Trial information
f the exchange has been divided into a traffic transmitting part and a trial configuration, this field
displays the text T-$. if the alarm originated in the trial configuration.
4'. -ecovery information
3hen recovery is informed of the alarm in order to start the automatic recovery actions, this field
displays <-*)%A<.
+ocument (o/ %0"!&1S234!T5'6!7!(okia $S 0 (okia )onfidential -ev./$2 +ate/489529:: &age F9;
Resolve Switching Alarm
T036-G
Nokia
S/W Revision : MS/!"R M#
$S S%
&M/NMS'000 T(0
!/W Revision : )*'00
4F. Source information
f the alarm is set before the start!up of the distributed part of the alarm system, this field displays
.1.
4H. )onsecutive number
Failure printouts (<<<, <<, <) are numbered in ascending order. 3ith the help of the number the
user can follow the update and cancel printouts of the original failure printout.
46. $larm number
$larm number is a search index in the alarm reference manual.
4;.Text
The text is a short description of the alarm.
48. Supplementary information fields
$ maximum of 46 fields which are separated from one another by one or several spaces. The
following are possible values of the field/
! a hexadecimal number (e.g. 5425)
! a decimal number (e.g. 425d)
! a 1)+ coded number (e.g. 5425)
f the number is 1)+ coded, it is mentioned in the alarm reference manual in the
explanations of the field in =uestion
! a single character or characters (e.g. $.CST7@)
! a functional unit (e.g. %",)
! a plug!in unit (e.g. C3$T)
! a working state of a unit (e.g. 3%!*@)
! a date (e.g. 4::H!56!2;)
! a time (e.g. 45/24/F2.4:)
n addition, the value of a certain field (e.g. the index of functional unit or the index of plug!in unit)
can be displayed as two dots (..). This refers to a case where there is no single value to be given
to the field according to its meaning.
n fault situations there is a =uestion mark (I) printed at the end of the fields.
4:. Supplementary text
$ more detailed text printed out in some alarms.
25. $larm operating instructions
%perating instructions the user may have defined for an alarm.
-roce0/re
There are two types of alarms generated by the switch. These are/
4. Software alarms.
2. Cardware alarms.
These two types of alarms can be distinguished from each other by inspecting the supplementary information
fields of the alarm printout. The supplementary information fields of the alarm printout contain the
identification of the program block or data file in error (in case of software alarms) or the identity of the failing
+ocument (o/ %0"!&1S234!T5'6!7!(okia $S 0 (okia )onfidential -ev./$2 +ate/489529:: &age H9;
Resolve Switching Alarm
T036-G
Nokia
S/W Revision : MS/!"R M#
$S S%
&M/NMS'000 T(0
!/W Revision : )*'00
plug!in unit (in case of hardware alarms).
4. -esolving software alarms/
Software alarms are generated due to malfunctions in the execution of program block(s) or data file(s) in
a computer unit of the exchange. Software alarms can be identified by looking at the supplementary
information fields of a specific alarm number in =uestion. The supplementary information field gives the
identity of the malfunctioning program block or data file.
4.4. 3hen the alarm is due to a software fault, identify the failing program block or data file. This
information is contained in the supplementary information fields of the alarm printout. -efer to the
(SS
M4N
or 1S)
M2N
(*+ +ocumentation (section >$larm -eference "anual?) for the alarm description
and interpretation of the supplementary information fields. The alarm description can be referenced
from the (*+ +ocumentation by using the alarm number as the index to the >$larm -eference
"anual?.
4.2. f the alarm description (from the >$larm -eference "anual?) mentions that a program block had
failed, and that the failing program block is occuring on one of the winchester disk units, then replace
the faulty program block by copying from the other winchester disk unit. f the failing program block is
occuring on both winchester disk units, then replace the faulty program block by copying it from the
floppy diskettes. The floppy diskettes can be found from the respective Software -elease 1inders
delivered for each Software .evel ("S) "8 or 1S) S;)
M'NMFN
.
-efer to the (*+ +ocumentation
M4NM2N
(section >)ommand -eference "anual?) on how to copy files.
.ook for the description and syntax of the file copying commands ("". commands ZIWY and ZIBC).
4.'. f the alarm description (from the >$larm -eference "anual?) mentions that a data file had failed, and
that the failing data file is occuring to one of the winchester disk units, then replace the the faulty data
file by copying from the other winchester disk unit. f the failing data file is occuring on both
winchester disk units, then correct the erroneous data within the file (for example, if the erroneous
data is a base station data, then it can be corrected by deleting and re!creating the base stationO if
the erroneous data is hardware configuration data, it can be corrected by deleting non!existent
functional units or adding functional units in accordance with the actual physical hardware
configuration).
-efer to the (*+ +ocumentation
M4NM2N
(section >)ommand -eference "anual?) on how to copy files.
.ook for the description and syntax of the file copying commands ("". commands ZIWY and ZIBC).
4.F. $fter the replacement of the faulty program block or data file, verify whether the alarm previously
generated by the fault needs manual cancelling (see the cancelling instruction from the alarm
description in the >$larm -eference "anual?) and manually cancel the alarm if necessary.
2. -esolving hardware alarms/
Cardware alarms are generated due to occurences of failure in plug!in unit(s) in the exchange. Cardware
alarms can be identified by looking at the supplementary information fields of a specific alarm number in
=uestion. The supplementary information field gives the identity of the faulty plug!in unit.
2.4. 3hen the alarm is due to a hardware fault, identify the failing plug!in unit. This information is
contained in the supplementary information fields of the alarm printout. -efer to (SS
M4N
or 1S)
M2N

+ocument (o/ %0"!&1S234!T5'6!7!(okia $S 0 (okia )onfidential -ev./$2 +ate/489529:: &age 69;
Resolve Switching Alarm
T036-G
Nokia
S/W Revision : MS/!"R M#
$S S%
&M/NMS'000 T(0
!/W Revision : )*'00
(*+ +ocumentation (section >$larm -eference "anual?) for the alarm description and interpretation
of the supplementary information fields. The alarm description can be referenced from the (*+
+ocumentation by using the alarm number as the index to the >$larm -eference "anual?.
2.2. f the alarm description (from the >$larm -eference "anual?) cannot clearly specify the faulty plug!in
unit, then refer to the printout of the diagnostic results on the failing unit. The diagnostic routine is
automatically activated by the recovery system when a fault is detected on a functional unit. The
diagnostic printout identifies the faulty plug!in unit within the failing functional unit. $dvise the Field
"aintenance personnel to replace the faulty plug!in unit.
2.'. f the state of the functional unit is in T*!*@ or S*!%,, then try changing its state either to 3%!*@
or S&!*@ (if the functional unit is a spare unit). This will cause the unit to restart. $ny active alarm on
the unit will be temporarily cancelled during the restart. f the unit fails again after the restart, the
alarm is generated once more and the unit state goes to T*!*@ and then to S*!%,. The Field
"aintenance personnel then need to be informed to replace the faulty plug!in unit. The faulty plug!in
unit can be identified from the supplementary information of the alarm printout.
-efer to the (*+ +ocumentation
M4NM2N
(section >)ommand -eference "anual?) on how to change the
state of the functional unit. .ook for the unit state handling commands ("". commands ZUSC).
2.F. $fter the replacement of the faulty plug!in unit, the alarms previously generated by the unit will be
automatically cancelled. For related alarms which does not cancel, verify whether the alarm needs
manual cancelling (see the cancelling instruction from the alarm description in the >$larm -eference
"anual?) and manually cancel the alarm(s) if necessary.
Re1erence
M4N (*+ +ocumentation ! "S) 0 C.- (software version "8).
M2N (*+ +ocumentation P 1S) (software version S;).
M'N "S) 0 C.- Software -elease 1inders (software version "8).
MFN 1S) Software -elease 1inders (software version S;).
+ocument (o/ %0"!&1S234!T5'6!7!(okia $S 0 (okia )onfidential -ev./$2 +ate/489529:: &age ;9;
Resolve Switching Alarm
T036-G
Nokia
S/W Revision : MS/!"R M#
$S S%
&M/NMS'000 T(0
!/W Revision : )*'00
2n0e3
!
+ocument (o/ %0"!&1S234!T5'6!7!(okia $S 0 (okia )onfidential -ev./$2 +ate/489529:: &age 89;