Professional Documents
Culture Documents
Performence Alarms
Performence Alarms
! "
#
$%
$%
&
'
( (
)(*#
+|
,-
)
),
$ (
The Alarm Reference documentation consists of alarm printouts and diagnosis reports. The alarms have been divided into four groups, and each of
them is described in a dedicated piece of documentation.
The alarms are numbered in ascending order as follows:
Table: Alarm groups and numbers
Alarm number
in:
Notices
(NOTICE)
Disturbance
printouts
(DISTUR)
Failure
printouts
(ALARMS)
switching
equipment
0799
10001799
20002799
30003799
40004799
O&M equipment
800 - 899
18001899
28002899
38003899
48004899
transmission
equipment
900 - 999
19001999
29002999
39003999
49004999
diagnosis
report number
base station/
transmission
equipment
alarms
Diagnosis
reports
(DIAGN)
Base
station
alarms
Transmission
equipment
alarms
37003999
7000
7999
80008999
power
equipment
50005499
external
equipment
55005999
]
]
!
Unknown equipment type is printed as ??????
f.Date and time
Start or termination time of the alarm.
g.Urgency level
"""
""
!#
"!!$
Unknown urgency level is printed as a question mark (?).
The urgency level is output in all alarm printouts except notices (NOTICE). The urgency levels of terminated alarms are indicated by dots (.)
instead of asterisks (*).
h.Printout type
i.Alarm object
j.Position coordinates of the alarm object
k.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 hexadecimal form instead of the name.
If the alarm is set in a preprocessor plug-in unit, the plug-in unit name and index are output in this field (for example PCU_S-1). In this case, the
alarm concerns the functioning of the plug-in unit in question.
.((
f.Date
g.Time
h.Urgency level
"""
""
#
"
The urgency level is output in all alarm printouts except notices (NOTICE). The urgency levels of terminated alarms are indicated by dots (.) instead of asterisks (*).
i.Printout type
,')!+-
+! . ((
.
)],')!+-
+! . ((
.
0
Tramsmission Problem
1
1
1
1
1
0
0
0
0
0
0
0
0
0
0
Cable/Connector
Mux
M/W ODU/IDU
M/W fading/interference
Configuration problem
IP ftp
Path
,3+
4(# ((
++
5
5
5
6
6
,3+
4(!(#(7
)8+
5
5
5
6
6
,3|,
4(((
$ -|,
5
5
5
6
6
,
4(&(#(
,
5
5
5
6
6
((
0 2
!
(
0
"
(
0 ++9
:;-9:-:;-
:
2;(
0 <+
$%
(
-
Owner=3 ,]]-+
Rectification Responsibility:/
=3
>=3
,]]>9+=3
,]]-+ =3
]
=3
])]2=3
RR
R
R
R
R
R
R
R
R
R
R
&
'
(
(
'
'
'
)
*
'
*'
*'
+
+
(*''
(*'''
' , -.R/
/
&( 01
R
R
RR
R
R
R
R
R
R
R
R
R
R
R
R
R
!"#$""$%!
RR
!"#$""$%!
R
R
R
R
R
R
R
!"#$""$%!
!"#$""$%!
!"#$""$%!
!"#$""$%!
!"#$""$%!
!"#$""$%!
!"#$""$%!
!"#$""$%!
!"#$""$%!
!"#$""$%!
!"#$""$%!
!"#$""$%!
!"#$""$%!
7600 , >>?9/@=3
0 (
0 -
(
0 /
/A
(
0 /
,/] (
0 / /A
B
(
0 >%
$%= / ]<
,
(
7601 , >-;/%-2
<;)<;<
0
% 8
(
0 %
,/](
%
=
0
0 <
+,/] "
(
0 / /A ,(
0 -
(
0
0 (
0 2
(
0
(
0 /
(
0 >%
$%= / ]< ,
C< /]
-](
 ,/]-;/%-2
<;)<;<
0 #/A>?9/@&/A-;/%-2
<;)<;<
0 B
0 >%
$%= / ]<
< /]-](
7603 ,/]>?9/@
0 #/A>?9/@
0 >%
$%= / ]<
,
(
7606 /A>?9/@
0
0
0
0
0
0
0
0
0
7607 /A-;/%-2
<;)<;<
0
0
0
0
0
(
0 +
,] 5++%
5 %<</A(
0 >%
$%= / ]<
< /]-](
7616 -] %99/-<E?]/%2)
/;+-%9@%2/;?/;<
0 -
8
(
0 / "
(
8
(|
(/ 3
(
0 >%
$%= / ]< < /]
-](
0
7743 +;2-9<%2)/%+;
,;9-|<;>%2;</;]-9<
0 +
3
(/
(
0
0
/ 4
0 /
4
0
' 4
0 >%
$%= / ]< < /]
-](
7744 ;A ;]]%D;/
%2/;>;;2 ;
0 < /
B
"
3
(/
,/]
(
0 +
" (
0 /
!4F
0 B
0 /
4
0 >%
$%= / ]< < /]
-](
7745 22;9>%9?;/;
,-D;<;>%2;</;]-9<
0 /
(/
(
0
0 / 4F] >
0 ]< *4F
0 9 #4
0
]G
' 4
0 ]
4*344
0 ]
*344
0 >%
$%= / ]< < -](
2064 -?/;];/?2D%9,9;
0 /
(
]
(
0 >%
$%=
,]
44F (
2070 9%2$];/?2D%9,9;
0
(/
B
(
0 /
5
(
0 >%
$%=
,]
44F (
2072 >%9?;%2]%)299%2)9%2$
/%D/%-2-;]/-/%-2
0 /
(%
(]
(
0 >%
$%=
,]
(]< /
,]
(
2992 ,/]2</
?2]@2 -2%:/%-2 9; 99]
-2%2/;> ;
0
0
0
0
0
0
2993 ,/]2</
?2]@2 -2%:/%-2 9; 99]
-2,%]%2/;> ;
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
0
3020 2;/|-$];D% ;
D%/?9 -22; /%-2
?2D%9,9;
2 ]
D
(%
)
]
(
%>
2 ]
D
(
(
>
2
]
D
(
3
2 ]
D
]& ])]2I? ? ,] I, ]? (
2]3D %2];%
(
<9 %
(%
3 3
(%%
4B>>>>(
2 ]
D
(
(
>%
$%=
8099 ; ;%D;<,%/;-
/%-,;J;3
0 / B
(/
(
0 >%
$%=
>$%
(
8179 >3;2<9+
/
"
3
(/
(
0 >%
$%=
] (
7734 , %]2-//
;>;;<, /A
0 / ,/] /A
, /A ,
/A
,
%
% ; (
0 >%
$%= ;<);
(
0 7704 +>%9?;
-
0 7705 9<>%9?;/ ]<
0 7715 -2/%2?-?];]//]->, >5/A/
]<
C<
0 7725 />>% 22;9 /%D/%-2>%9?;/
< ,
0 7730 -2>%)?/%-2->, >>%9;<]<
/
0 7738 ,/]|%/2-/2] /%-2]
0 7!FAULT RATE MONITORING
,/]
The BTS alarm system receives alarm indications from the following sources in the radio network:
0BTS equipment alarms
0BTS software alarms
0external alarms from the BTS site
0alarms concerning PCM circuits in the radio network
0alarms from LAPD links in the radio network
0alarms from Abis interface equipment
0alarms from application programs of the BSC
0transmission equipment alarms.
This block diagram illustrates the structure of the BTS alarm system:
<
Alarms are written in a logical file. From the logical file, they can be directed to a local printer or to Nokia NetAct. The table below shows the logical files used
with alarms. For further information on the logical files used with alarms, refer to the Logical files directed to terminal devices section of :
Explanation
LOGICAL FILE
SWITCH1
TRANSM1
POWER1
EXTERN1
OPERMA1
SWITCH2
TRANSM2
POWER2
EXTERN2
OPERMA2
Operation and maintenance alarms whose type is notice, disturbance, or one-star alarm
BTSALARM1
BTSALARM2
BTSALARM3
BTSALARM4
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 command
group commands, you can display the history data concerning the system's alarm situation. For further information on displaying alarm history, refer to
( ) for DX 200 alarms, and
( ) for BTS alarms.
You can either display the alarm history, or merely the active alarms, on the selected output device.
The printout format is the same as in alarm printouts.
It is recommended that you print out the active alarms every day. Check if they require maintenance actions.
A DX 200 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.
You can print out active DX 200 alarms with the command , and active BTS alarms with the command .
You can display the DX 200 alarm history data with the command , and the BTS alarm history data with the command .