NOC Alarms
-
Upload
mohsin-akram -
Category
Documents
-
view
217 -
download
0
Transcript of NOC Alarms
![Page 1: NOC Alarms](https://reader030.fdocuments.in/reader030/viewer/2022021120/55cf966c550346d0338b5bcd/html5/thumbnails/1.jpg)
7/21/2019 NOC Alarms
http://slidepdf.com/reader/full/noc-alarms 1/6
Nokia Siemens Networks
Junaid Ur Rehman 26/04/2007
List of Alarms to be monitored by NOC
Version: 1.1
![Page 2: NOC Alarms](https://reader030.fdocuments.in/reader030/viewer/2022021120/55cf966c550346d0338b5bcd/html5/thumbnails/2.jpg)
7/21/2019 NOC Alarms
http://slidepdf.com/reader/full/noc-alarms 2/6
Nokia Siemens Networks
Junaid Ur Rehman 26/04/2007
TABLE OF CONTENTS
1. External/environmental alarms .....................................................................................................3 2. List of bts Alarms..........................................................................................................................4 3. Transmission alarms ....................................................................................................................5 4. List of BSC alarms .......................................................................................................................5 5. Oss alarms...................................................................................................................................6 6. Special note .................................................................................................................................6 7. New Network elements/ features..................................................................................................6
![Page 3: NOC Alarms](https://reader030.fdocuments.in/reader030/viewer/2022021120/55cf966c550346d0338b5bcd/html5/thumbnails/3.jpg)
7/21/2019 NOC Alarms
http://slidepdf.com/reader/full/noc-alarms 3/6
Nokia Siemens Networks
Junaid Ur Rehman 26/04/2007
1. EXTERNAL/ENVIRONMENTAL ALARMS
The following External/Environmental Alarms need to be monitored andescalated to respective teams by NOC.
!
"""" # $ % &
'''' () * + ,
---- $
! . ))&
/* &
)0 +&
$12&
2 32 32 32 3 456 456 456 456
(!((718!((7(!((718!((7(!((718!((7(!((718!((7
97 +
# 3 (
'''' #: 3 ( ;)
---- #: 3 ( : +
2 32 32 32 3
80 80 80 80####
#: 3 ( #
#: 3 (
#: 3 ( ;)
#: 3 ( : +Nokia PowerSystem(#2)Indoor BSC #: 3 ( #
9 :
0 $
/* ; : )
. : )
+ )"""" 9 :
/* ; : )
'''' . : )
)## 3)## 3)## 3)## 3
---- + )
....37373737 7%<
....37373737 <798:<
....37373737 8 $4000
....37373737.... #<7=
# #:# #:# #:# #:
4001 <><><><> !((7 ::<
![Page 4: NOC Alarms](https://reader030.fdocuments.in/reader030/viewer/2022021120/55cf966c550346d0338b5bcd/html5/thumbnails/4.jpg)
7/21/2019 NOC Alarms
http://slidepdf.com/reader/full/noc-alarms 4/6
Nokia Siemens Networks
Junaid Ur Rehman 26/04/2007
<><><><> /8%/ <3
<><><><> : $87<
<><><><> $87<1(?<
<><><><> 87!<7
<><><><> 97 $87<
4777 <><><><> <<(7 < 7
Salteq Eq Fail
Temp Alarm
Saltec AC Fail
High Tem
High V
AC Fail
@ @ @ @ 8240
Low V
:89< 7 3(8
7777 8000 Repeater 3(<7 33= $
, . + )
2. LIST OF BTS ALARMS
The following BTS/BCF alarms need to be monitored real time by NOC and
need to be escalated to concerned teams (Field+BO).
Service Affecting Alarms (related to BTS/BCF)
Alarm No. Description
7701 BCF Initialization
7704 PCM Failure
7706 BTS O&M Link Failure
7767 BCCH Missing
Quality Alarms
Alarm No. Description
7601 BCF Operation Degraded
7604 BTS Operation Degraded7606 TRX Faulty
7607 TRX Operation Degraded
7738 BTS with no Transactions
![Page 5: NOC Alarms](https://reader030.fdocuments.in/reader030/viewer/2022021120/55cf966c550346d0338b5bcd/html5/thumbnails/5.jpg)
7/21/2019 NOC Alarms
http://slidepdf.com/reader/full/noc-alarms 5/6
Nokia Siemens Networks
Junaid Ur Rehman 26/04/2007
3. TRANSMISSION ALARMS
The following Transmission alarms need to be monitored real time by NOCand need to be escalated to concerned teams (Field+BO).
Transmission Alarms
2925 SLIP FREQUENCY LIMIT EXCEEDED
8099 RECEIVED BIT ERROR RATIO (BER) > 1E-3
2923 CRC BIT ERROR RATIO OVER LIMIT
4. LIST OF BSC ALARMS
The following BSC alarms need to be monitored real time by NOC and needto be escalated to concerned teams (BSC+BO).
BSC AlarmsAlarm No. Description
2072 Failure in Signaling link Activation or Restoration
2250 Failure in D-Channel Activation or Restoration
2347 Power Supply Failure in CPU
2471 Radio Network Recovery Failed
2477 Global Reset Message Received
2478 Mobile Access Classes Abnormal
2632 Oscillator Failure
2692 Incorrect Working State
2756 Cartridge Power Supply failure
2757 Cartridge Non-Redundant Power Supply Failure
2758 Power Supply Adapter Failure
2759 Power supply Fuse Failure
2760 HWAT Failure
2764 CLS Failure
2801 O&M Network System Unreachable
2860 Disk Failure
2948 Radio Network Initialization
2992 BTS & TC Unsynchronized Clear Calls on A Interface
2993 BTS & TC Unsynchronized Clear Calls on Abis Interface
3019 Network Service Entity Unavailable
9108 Failure in OMC-NE Communication link
![Page 6: NOC Alarms](https://reader030.fdocuments.in/reader030/viewer/2022021120/55cf966c550346d0338b5bcd/html5/thumbnails/6.jpg)
7/21/2019 NOC Alarms
http://slidepdf.com/reader/full/noc-alarms 6/6
Nokia Siemens Networks
Junaid Ur Rehman 26/04/2007
5. OSS ALARMS
The following OSS alarms need to be monitored real time by NOC and needto be escalated to concerned teams (OSS+BO).
OSS Alarms
9304 File system is becoming Full
9041 Process recovery is needed repeatedly
9010 Process recovery Fails
6. SPECIAL NOTE
This list of alarms has been prepared on the basis of day to day Operationsexperience. This should not be taken as a final version. Extreme care has been taken toprepare this list but there may be alarms which have never appeared in the network to date
and they may be service effecting. To avoid such occurrences it is recommended to updatethis list on monthly basis or when needed.
It is also recommended to monitor the whole network without applying anyfilters by NOC personal at a regular interval of four hours and check for any abnormalalarm. Such alarm should be immediately escalated to vendor BO team for further analysis.
7. NEW NETWORK ELEMENTS/ FEATURES
Alarms of any new NE or any new feature should be communicated tosurveillance teams by concerned Network acceptance teams (TP rollout + TP acceptance)