You are on page 1of 258

UTRAN

Outputs
Node B
OML:Node B
A50016-G5000-F226-prelim3-7619
ND-57314-705(E)-prelim03

OML:Node B

Outputs
Node B

Important Notice on Product Safety


DANGER - RISK OF ELECTRICAL SHOCK OR DEATH - FOLLOW ALL INSTALLATION INSTRUCTIONS.
The system complies with the standard EN 60950 / IEC 60950. All equipment connected to the system must
comply with the applicable safety standards.
Hazardous voltages are present at the AC power supply lines in this electrical equipment. Some components may
also have high operating temperatures.
Failure to observe and follow all installation and safety instructions can result in serious personal injury
or property damage.
Therefore, only trained and qualified personnel may install and maintain the system.

The same text in German:


Wichtiger Hinweis zur Produktsicherheit
LEBENSGEFAHR - BEACHTEN SIE ALLE INSTALLATIONSHINWEISE.
Das System entspricht den Anforderungen der EN 60950 / IEC 60950. Alle an das System angeschlossenen
Gerte mssen die zutreffenden Sicherheitsbestimmungen erfllen.
In diesen Anlagen stehen die Netzversorgungsleitungen unter gefhrlicher Spannung. Einige Komponenten
knnen auch eine hohe Betriebstemperatur aufweisen.
Nichtbeachtung der Installations- und Sicherheitshinweise kann zu schweren Krperverletzungen oder
Sachschden fhren.
Deshalb darf nur geschultes und qualifiziertes Personal das System installieren und warten.

Caution:
This equipment has been tested and found to comply with EN 301489. Its class of conformity is defined in table
A30808-X3247-X910-*-7618, which is shipped with each product. This class also corresponds to the limits for a
Class A digital device, pursuant to part 15 of the FCC Rules.
These limits are designed to provide reasonable protection against harmful interference when the equipment is
operated in a commercial environment.
This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the relevant standards referenced in the manual Guide to Documentation, may cause harmful interference to radio communications.
For system installations it is strictly required to choose all installation sites according to national and local requirements concerning construction rules and static load capacities of buildings and roofs.
For all sites, in particular in residential areas it is mandatory to observe all respectively applicable electromagnetic
field / force (EMF) limits. Otherwise harmful personal interference is possible.

Trademarks:
All designations used in this document can be trademarks, the use of which by third parties for their own purposes
could violate the rights of their owners.

Copyright (C) Siemens AG / NEC Corporation 2005.


Issued by:
Siemens AG, Communications, Hofmannstrae 51, 81359 Mnchen, Germany and
NEC Corporation, 7-1, Shiba 5-chome, Minato-ku, Tokyo, Japan
Technical modifications possible.
Technical specifications and features are binding only insofar as they are specifically and expressly agreed upon in a written contract.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

Reason for Update


Summary:
Addition of two new alarms (Error-IDs 200658 and 200659). Improved error descriptions
and troubleshootings.
Details:
Chapter/Section

Reason for Update

200658 - Transmit bandwidth


limit for NBAP reached
200659 - Core Controller
overload protection activated

New

All

Improved error descriptions and troubleshootings.


Editorial changes.

Issue History
Issue

Date of issue

Reason for Update

05/2005

First issue for new release.

07/2005

Addition of three new alarms (Error-IDs 201038,


201039, and 201040). Deletion of two alarms
(Error-IDs 200930 and 200978). Modification of the
error description for MEF alarms.
Generally, improved descriptions and editorial
changes.

prelim3

10/2005

Addition of two new alarms (Error-IDs 200658 and


200659). Improved error descriptions and troubleshootings.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

OML:Node B

Outputs
Node B

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

This document consists of 258 pages. All pages are issue prelim3.

Contents
Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Title
..........................................................
Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Managed Object Class / Hardware Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Event Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

11
11
11
11
11
12
12
13
14

Errors in Numerical Order (error-ID). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15


200506 - Node B system start-up malfunction due to software/hardware problem . . 16
200507 - System halt due to software watchdog detected problem. . . . . . . . . . . . . . 17
200508 - System halt due to detected application process error . . . . . . . . . . . . . . . . 18
200509 - System halt due to detected hardware exception . . . . . . . . . . . . . . . . . . . . 19
200510 - System halt due to detected software loading malfunction . . . . . . . . . . . . . 20
200656 - Iub link broke down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
200657 - SSCOP sent overrun. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
200658 - Transmit bandwidth limit for NBAP reached . . . . . . . . . . . . . . . . . . . . . . . . 24
200659 - Core Controller overload protection activated. . . . . . . . . . . . . . . . . . . . . . . 25
200706 - An error occurred in the nbDatabase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
200707 - A warning occurred in the nbDatabase . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
200756 - System call unsuccessful . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28
200757 - Unexpected software error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
200758 - Not enough memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
200759 - A fatal error has occurred that may affect OAM command processing. . . . 31
200905 - VSWR alarm Low . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
200906 - VSWR alarm High . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
200907 - RX alarm Low . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
200908 - RX alarm High. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
200909 - TMA switched off, but not defective . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
200910 - TMA feeder alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
200911 - TMA DC alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41
200914 - Fan unit failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
200915 - Site input alarm detected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
200916 - Rack Door open . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
200918 - PA combiner interface fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
200919 - Failure in the DC supply of PA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
200920 - High temperature of PA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49
200921 - Over temperature of PA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
200922 - RF performance not being met due to bad linearization . . . . . . . . . . . . . . . 53
200923 - Internal failure of PA detected. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
200924 - Input power level of LPA too high but LPA can still hold its RF specification .
55
200925 - Input power level of PA too high . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

OML:Node B

Outputs
Node B

200926 - CPU failure of baseband card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57


200927 - Volatile memory failure of baseband card . . . . . . . . . . . . . . . . . . . . . . . . . . 58
200928 - Non-volatile memory failure of baseband card. . . . . . . . . . . . . . . . . . . . . . . 59
200929 - DSP failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
200931 - FPGA failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
200932 - Control FPGA failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
200933 - External timing signal failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
200934 - Failure of the RF part of the TRX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
200935 - LVDS Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
200936 - Local bus failure around the CPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
200937 - FTP connection failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
200938 - SWI CRC check failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68
200939 - Static configuration file CRC check failed . . . . . . . . . . . . . . . . . . . . . . . . . . 69
200940 - SW activation failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
200941 - Internal clock failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
200942 - Configuration file inconsistent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
200943 - IOR file inconsistent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
200944 - FTP put failed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
200945 - FTP manage failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
200946 - Still alive supervision failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
200947 - Failure in the DC supply of DUAMCO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
200948 - CORBA communication failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78
200949 - Internal CORBA call failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
200950 - Timeout for request or modification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
200951 - Status notification undefined . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
200952 - Maximum number of resets exceeded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
200953 - CAN bus off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
200954 - No message response on CAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
200955 - Mount supervision failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
200956 - Watch dog timer expired . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
200957 - Internal CAN processing failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
200958 - Timer for the reset supervision expired . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
200959 - Missing response from baseband card . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
200960 - Invalid response from baseband card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
200961 - Firmware download failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
200980 - Invalid MO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
200981 - MO not mounted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
200982 - Invalid command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
200983 - Invalid parameter in command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
200984 - FW download access file error. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
200985 - CAN transaction error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97
200986 - Temperature out of range in upper direction . . . . . . . . . . . . . . . . . . . . . . . . 98
200987 - Hardware parameter invalid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
200988 - Response unknown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
200989 - No CORBA proxy available for LRU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
200990 - No still alive response from LRU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102
200991 - Duplex error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

200992 - Software Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104


200993 - Unexpected Alarm Status Bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105
200994 - HW Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
200995 - High Temperature Limit (Ht3) reached . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
200996 - Critical Temperature Limit (Ht4) reached . . . . . . . . . . . . . . . . . . . . . . . . . 109
200997 - Lower Temperature Limit (Ht0) reached . . . . . . . . . . . . . . . . . . . . . . . . . . 111
200998 - Temperature out of range in lower direction . . . . . . . . . . . . . . . . . . . . . . . 112
200999 - Unexpected loss of unlocked card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113
201001 - RET power off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
201002 - RET feeder alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116
201003 - RET hardware alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
201004 - RET communication error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
201005 - RET isnt calibrated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119
201006 - RET isnt scaled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120
201007 - RET lost position . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
201008 - RET received wrong configuration data . . . . . . . . . . . . . . . . . . . . . . . . . . 122
201009 - A mounted card is not used to its full capacity . . . . . . . . . . . . . . . . . . . . . 123
201010 - An incompatible card is mounted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
201011 - Alignment of standby CC failed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
201012 - Timeout for connection to standby CC . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
201013 - Connection failure to standby CC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127
201014 - Standby CC forced to become active due to unreachable active CC . . . . 128
201015 - Preparation of data to be aligned has failed . . . . . . . . . . . . . . . . . . . . . . . 129
201016 - Non-fatal internal LVDS failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130
201017 - Digital input power level too high, but gain reduced . . . . . . . . . . . . . . . . . 131
201018 - The LRU could not process a message from CC . . . . . . . . . . . . . . . . . . . 132
201019 - Gain below threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
201020 - Loss of single DRIF interface detected . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
201022 - Alignment of file data has failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
201023 - Bad signal quality of single DRIF interface detected. . . . . . . . . . . . . . . . . 136
201024 - Bad signal quality of all DRIF interfaces detected. . . . . . . . . . . . . . . . . . . 137
201025 - PID could not be read or is corrupted . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138
201026 - LRU sent illegal parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139
201027 - LRU could not process a message from CC containing data from DB . . . 140
201028 - HW-failure clock processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141
201029 - MEF blocked . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142
201030 - Invalid hardware capacity licensing value . . . . . . . . . . . . . . . . . . . . . . . . . 143
201031 - Wrong combination of licensed cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144
201032 - Not all cells are licensed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145
201033 - PID could not be read or is corrupted - non-fatal . . . . . . . . . . . . . . . . . . . 146
201034 - Boosters Fan unit failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147
201035 - MEF completely blocked . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148
201036 - RRHs unable to establish communication links with the expected number of
PSRs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149
201037 - RET unspecified error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150
201038 - Resource conflict between CP and OAM . . . . . . . . . . . . . . . . . . . . . . . . . 151
201039 - Inconsistency between hardware license and configuration . . . . . . . . . . . 152

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

OML:Node B

Outputs
Node B

201040 - Wrong cabling of LRU detected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153


201916 - Toggling condition detected for alarm AIS, SP ID 202059 . . . . . . . . . . . 154
201917 - Toggling condition detected for alarm RAI, SP ID 202060 . . . . . . . . . . . 155
201918 - Toggling condition detected for alarm lineAIS, SP ID 202062. . . . . . . . . 156
201919 - Toggling condition detected for alarm lineRDI, SP ID 202063 . . . . . . . . 157
201920 - Toggling condition detected for alarm pathAIS, SP ID . . . . . . . . . . . . . . 158
201921 - Toggling condition detected for alarm pathRDI, SP ID 202066 . . . . . . . . 159
201922 - Toggling condition detected for alarm vcAIS, SP ID 202072. . . . . . . . . . 160
201923 - Toggling condition detected for alarm vcRDI, SP ID 202073 . . . . . . . . . 161
201924 - Toggling condition detected for alarm vpAIS, SP ID 202075. . . . . . . . . . 162
201925 - Toggling condition detected for alarm vpRDI, SP ID 202076 . . . . . . . . . 163
201926 - Toggling condition detected for alarm LOC, SP ID 202097. . . . . . . . . . . 164
202006 - A bbUsageRatio Quality of Service alarm has occurred . . . . . . . . . . . . . . 165
202007 - A scanner could not be initialized. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166
202008 - The temporary measurement results could not be stored . . . . . . . . . . . . . 167
202009 - Unable to request measurement results . . . . . . . . . . . . . . . . . . . . . . . . . . 168
202010 - The ScanCo could not be initialized. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169
202011 - The final results files could not be generated. . . . . . . . . . . . . . . . . . . . . . . 170
202012 - The first bbUsageRatio Quality of Service alarm has occurred . . . . . . . . . 171
202013 - The second bbUsageRatio Quality of Service alarm has occurred . . . . . . 172
202014 - The first sccpchUsageRatio Quality of Service alarm has occurred . . . . . 173
202015 - The second sccpchUsageRatio Quality of Service alarm has occurred . . 174
202016 - The first prachUsageRatio Quality of Service alarm has occurred . . . . . . 175
202017 - The second prachUsageRatio Quality of Service alarm has occurred. . . . 176
202018 - The first cpUsageRatio Quality of Service alarm has occurred . . . . . . . . . 177
202019 - The second cpUsageRatio Quality of Service alarm has occurred . . . . . . 178
202020 - The first prachCrciFailures Quality of Service alarm has occurred . . . . . . 179
202021 - The second prachCrciFailures Quality of Service alarm has occurred . . . 180
202056 - Loss Of Signal on Physical Link. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181
202057 - Loss Of Frame on Physical Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183
202058 - Loss Of Cell Delineation on Physical Link . . . . . . . . . . . . . . . . . . . . . . . . . 185
202059 - Alarm Indication Signal on Physical Link . . . . . . . . . . . . . . . . . . . . . . . . . . 187
202060 - Remote Alarm Indication on Physical Link. . . . . . . . . . . . . . . . . . . . . . . . . 188
202061 - Loss of Multi Frame Alarm Indication on E1 Physical Link . . . . . . . . . . . . 189
202062 - Line Alarm Indication Signal Indication on STM1 Physical Link. . . . . . . . . 191
202063 - Line Remote Defect Indication on STM1 Physical Link . . . . . . . . . . . . . . . 192
202064 - Path Loss of Pointer Indication on STM1 Physical Link. . . . . . . . . . . . . . . 194
202065 - Path Alarm Indication Signal on STM1 Physical Link . . . . . . . . . . . . . . . . 197
202066 - Path Remote Defect Indication on STM1 Physical Link. . . . . . . . . . . . . . . 199
202068 - Signal Label Mismatch Indication on STM1 Physical Link . . . . . . . . . . . . . 200
202070 - Signal Degrade Indication on STM1 Physical Link . . . . . . . . . . . . . . . . . . 201
202071 - Excessive Bit Error Rate Indication on STM1 Physical Link . . . . . . . . . . . 202
202072 - Alarm Indication Signal on an ATM VC . . . . . . . . . . . . . . . . . . . . . . . . . . . 204
202073 - Remote Defect Indication on an ATM VC . . . . . . . . . . . . . . . . . . . . . . . . . 205
202074 - SSCOP Failure Indication on an ATM VC used by ALCAP or NBAP . . . . 206
202075 - Alarm Indication Signal on an ATM VP . . . . . . . . . . . . . . . . . . . . . . . . . . . 208
202076 - Remote Defect Indication on an ATM VP . . . . . . . . . . . . . . . . . . . . . . . . . 209

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

202077 - ALCAP PVC Out Of Service Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . 210


202078 - Loss Of Delay Synchronization on IMA Link . . . . . . . . . . . . . . . . . . . . . . . 211
202079 - Loss Of IMA Frame on IMA Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212
202080 - Remote Failure Indicator on IMA Link. . . . . . . . . . . . . . . . . . . . . . . . . . . . 213
202081 - IMA Tx link is detected as mis-connected. . . . . . . . . . . . . . . . . . . . . . . . . 214
202082 - IMA Rx link is detected as mis-connected . . . . . . . . . . . . . . . . . . . . . . . . 215
202083 - Tx fault declared at the NE on IMA Link . . . . . . . . . . . . . . . . . . . . . . . . . . 216
202084 - Rx fault declared at the NE on IMA Link . . . . . . . . . . . . . . . . . . . . . . . . . . 217
202085 - FE has reported Tx-Unusable on IMA Link . . . . . . . . . . . . . . . . . . . . . . . . 218
202086 - FE has reported Rx-Unusable on IMA Link. . . . . . . . . . . . . . . . . . . . . . . . 219
202087 - Startup FE reported on IMA Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220
202088 - Config Abort reported on IMA Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221
202089 - Config Abort FE reported on IMA Group. . . . . . . . . . . . . . . . . . . . . . . . . . 222
202090 - Insufficient Links reported at NE on IMA Group . . . . . . . . . . . . . . . . . . . . 223
202091 - Insufficient Links at FE reported on IMA Group . . . . . . . . . . . . . . . . . . . . 224
202092 - Group Blocked at FE reported on IMA Group . . . . . . . . . . . . . . . . . . . . . . 225
202093 - Timing Synch error reported on IMA Group . . . . . . . . . . . . . . . . . . . . . . . 226
202095 - The Near End IMA has detected an invalid version set by the Far End . . 227
202097 - Loss of Continuity detected on an ATM VP . . . . . . . . . . . . . . . . . . . . . . . 228
202098 - CRC4 not used by FE reported on E1TTP . . . . . . . . . . . . . . . . . . . . . . . . 229
202106 - Software activation failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230
202107 - Database activation failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231
202108 - Reliable software started without prior explicit activation . . . . . . . . . . . . . 232
202109 - Reliable database started without prior explicit activation. . . . . . . . . . . . . 233
202156 - Cannot acquire mutex for logging of FER . . . . . . . . . . . . . . . . . . . . . . . . . 234
202157 - Cannot release mutex after logging of FER . . . . . . . . . . . . . . . . . . . . . . . 235
202158 - Reset safe RAM for logging of FERs unavailable . . . . . . . . . . . . . . . . . . . 236
202357 - CAN opcode not valid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237
202358 - CAN received an unexpected message . . . . . . . . . . . . . . . . . . . . . . . . . . 238
202359 - CAN received a message with an invalid parameter . . . . . . . . . . . . . . . . 239
202360 - A necessary resource is missed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240
202406 - ALCAP Protocol Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241
202431 - ITR initiated action from CPA to RNC timed out . . . . . . . . . . . . . . . . . . . . 242
202432 - CPN initiated action from CPA to RNC timed out . . . . . . . . . . . . . . . . . . . 243
202433 - Configuration misalignment between RNC and CPA . . . . . . . . . . . . . . . . 244
202434 - RNC Establish Request message received which is invalid or cannot be handled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245
202435 - CPA to RNC communication (socket) problems . . . . . . . . . . . . . . . . . . . . 246
202456 - CC Clock Warm Up Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247
202457 - CC Card HW Test Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248
202506 - Node B System Clock in Holdover Mode . . . . . . . . . . . . . . . . . . . . . . . . . 249
202507 - Node B System Clock in Medium Accuracy . . . . . . . . . . . . . . . . . . . . . . . 251
262041 - System call unsuccessful . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252
262042 - Unexpected software error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253
262043 - Error from Device Driver received. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254
262044 - Not enough memory to initialize software . . . . . . . . . . . . . . . . . . . . . . . . . 255
262045 - Memory allocation failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

OML:Node B

Outputs
Node B

262046 - Unexpected exception handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257


262047 - Uncaught exception handling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258

10

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

Introduction
i

This document is prepared as a standard edition that may include descriptions not applying to your system.
The goal of this manual is to describe all alarms and system information which can be
generated by the Node B. The OML:Node B provides information on handling these
alarms via the LMT.
A description of the general UTRAN maintenance concept and an example of how to
solve an alarm are provided in the Guide to Documentation.
The software attempts to provide a precise error description for each alarm containing
all information for the operator and manufacturer in order to rapidly localize, investigate
and eliminate the fault. There is no relation between the number of described faults and
their frequency of occurrence in the system.
Error ceased messages clear all alarms for a specific probable cause of one object.
Whenever a diagnosis of a faulty object fails, the operator has to replace the faulty module (specified in the test report) following the procedure described in the according maintenance manual.
This manual is organized according to the error-IDs where each one forms a chapter
with:
Title
Failure Event Report
Error Description
Troubleshooting

Title
Composed of error-ID and error string

Failure Event Report


Contains the following details:
Managed Object Class / Hardware Type
Event Type
Probable Cause
Severity

Managed Object Class / Hardware Type


The managed object class / hardware type identifies the managed object class of the
fault or error.
In the OML:Node B, an asterisk (*) symbol in the related field of the failure event report
means that potentially any managed object class / hardware type can report this alarm.

Event Type
The Event Type may have these possible values:
communicationAlarm
environmentalAlarm
equipmentAlarm
Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

11

OML:Node B

Outputs
Node B

qualityOfServiceAlarm
processingErrorAlarm

Probable Cause
Identifies the probable cause of the fault or error. The probable cause is taken out of a
predefined set of values defined for each alarm type.

Severity
According to the CCITT Rec. X.733 all alarm notifications produced in switching systems have to be classified concerning the severity of their impact on the NEs (Network
Element) functionality.
The severity assigned to a specific alarm has one of the following values:
critical
major
minor
warning
Fault Escalation Strategy
Some specific problems are handled according to the Fault Escalation Strategy. The
Fault Escalation Strategy consists of the following rules:
If the object raises the corresponding alarm for the first time, the alarms severity is
WARNING.
Upon each occurrence of this alarm, a dedicated escalation counter is incremented
and a corresponding dedicated escalation timer is (re-)started.
If the object operates normally for a specific period of time (the expiration period of
the escalation timer), i.e. if the object does not raise the same alarm again until the
escalation timer expires, the escalation counter is reset.
If the object raises the same alarm after expiry of the escalation timer, the alarms
severity will be WARNING again.
If the object raises the same alarm a predefined number of times without having operated normally for the escalation counters expiration period or longer, i.e. if the escalation counter crosses a predefined threshold, the severity will change from
WARNING to a predefined final alarm severity.
The alarms final severity is then set in the Failure Event Report. The OML:Node B
describes the alarms final severity in the failure event report of the relevant alarm.
Configuration of alarm severities
The operator can configure the severities of some alarms to either minor, major, or critical, thus achieving a satisfying adaptation to actual needs. To adapt the alarm severity,
the Node Bs database (DB) has to be changed. The FaultMng MOC in the Node Bs
DB contains the severities parameter which is a list of all modified alarm severities.
Several instances within this list can be created at the LMT. Each instance provides the
following operator-configurable attributes:
Error ID of the alarm to be modified
ID of the MOC related to the alarm for which the severity is to be changed
Severity

12

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

Each instance within the severities parameter is evaluated by the Node Bs software
(SW). Instances with MOC IDs or error IDs incompatible to the current Node B SW load
are ignored.
To change the severity of an alarm, the following procedure has to be applied:
1. Upload the DB to the LMT.
Use the TREE View window of the LMT or apply the uploadDataInitiate command to
the relevant OSU managed object.
2. Modify the DB with the help of an XML editor or using scripts.
Proceed according to the OGL:Node B DB Editing Guide.
The following possibilities exist at the LMT:
Adding or removing an instance to or from, respectively, the severities list.
Modifying an existing instance within the list.
3. Download the modified DB.
Use the TREE View window of the LMT or apply the downloadDataInitiate command
to the relevant OSU managed object.
4. Activate the downloaded DB.
Use the TREE View window or the activate nodeBDatabaseVersionType command.
For more information about DB parameters, refer to the OGL:Node B DB Description.
The severity assignment for a specific alarm is determined by the following sources,
listed in descending priority:
1. Severity setting for a particular managed object class (MOC), such as ExtEquipIn or
Scanner.
2. Severity setting in the severities list of the Node Bs FaultMng MOI.
3. Default built-in severity.

NOTE
The severities attribute will be considered only for alarms that represent a condition
for which a corresponding clearance event exists. In contrast, alarms that represent only
one single event, will always be sent with severity warning.

Error Description
Describes the probable cause of the error concisely.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

13

OML:Node B

Outputs
Node B

Troubleshooting
Describes the actions the operator must perform to attempt to solve the problem.
Collect Info for Assistance
In some cases it is necessary to get support from customer services in order to isolate
the fault. Prior to contacting the Technical Assistance Center (TAC) pay attention to the
following questions and tasks:
Description of malfunction.
What is the suspected origin of the error?
What are the functional and hardware states of the affected system?
What are the issues of the affected boards? Check HW and FW states.
Observed system activities?
External influences (power supply, environment)?
What has been done (customer, local service staff)?
Exact time of error: synchronize the time stamp of all log files, if possible.
Save the database of the affected NE.
Save the IDF (Inventory Data File) of the affected NE.
Upload the log file of the affected NE.
The LMT provides a feature to upload diagnosis data from the Node B. The result of the
diagnosis data upload is a zip file which should be attached to any fault report. The zip
file contains information on the exact time of occurrence of the error, the database and
the inventory data file (IDF) of the affected network element and the log file. For details
about the diagnosis data upload, refer to the Operator Guideline OGL:LMT NB.

14

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

Errors in Numerical Order (error-ID)


In this chapter all failure event reports related with the Node B 2nd platform are listed in
numerical order. Each title is composed of the error-ID concatenated with the error string
and followed by the failure event report.
An error description gives a general understanding of the alarm at systems level and
points out what impacts could be expected. Hints of other symptoms or alarms that
might be associated are also given.
Checks, detailed actions or data collection procedures for troubleshooting tasks are described subsequently.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

15

OML:Node B

Outputs
Node B

200506 - Node B system start-up malfunction due to software/hardware problem


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Osu
processingErrorAlarm
ApplicationSubsystemFailure
critical

Error Description
The Node B system start-up is maintained by a dedicated software subsystem (MasterServiceTask: MST). Any error encountered during initialization of this subsystem will
generate this fault report. The affected Node B Core Controller is not available. Probable
reasons for these conditions are problems related either to hardware (e.g.: memory
problem, input/output malfunction) or operating system environment. This condition
leads to a recovery reset of the whole Node B.
If the fault report relates to a HW problem, troubleshooting might require detailed knowledge of the Node B hardware structure (memory, boot system, ...). If the fault report relates to a SW problem, troubleshooting might require direct access to the Node B's
operating system console.
Troubleshooting
Due to the imponderable system behavior in such cases there is no statement about further system operations. Contact the technical assistance center (TAC) to get support in
isolating the fault. For suitable preparation save the error symptoms as described in
"Collect Info for Assistance". Log files need to be analyzed and specific measures must
be taken which are out of the operators scope.

16

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

200507 - System halt due to software watchdog detected


problem
Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Osu
processingErrorAlarm
WatchDogTimerExpired
critical

Error Description
This problem reports a situation, where the software health observation system has detected a missing health indication from any Node B software subsystem. The affected
subsystem malfunction might (dependent of subsystem and error cause) be already noticeable by generated fault reports from it's own scope. This condition leads to a recovery reset of the whole Node B. The affected Node B Core Controller is temporary not
available. This information has to be analyzed to find the malfunction originator. Due to
the recovery reset, only the system log files could be used for 'post' analysis.
The probable reason for this alarm is a software problem.
Troubleshooting
Contact the technical assistance center (TAC) to get support in isolating the fault. For
suitable preparation save the error symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are
out of the operators scope.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

17

OML:Node B

Outputs
Node B

200508 - System halt due to detected application process


error
Failure Event Report
Managed Object Class / Hardware Type: Osu
Event Type:
processingErrorAlarm
Probable Cause:
SoftwareProgramAbnormallyTerminated
Severity:
critical
Error Description
This problem reports a situation, where the software health observation system has detected a 'dead' Node B software subsystem. The affected subsystem (generally) could
not be indicated by generated fault reports from it's own scope, but this problem report
contains information about the originator of the error. This condition leads to a recovery
reset of the whole Node B. The affected Node B Core Controller is temporarily not available. Due to the recovery reset, only the system log files could be used for 'post' analysis.
The probable reason for this alarm is a software problem.
Troubleshooting
Contact the technical assistance center (TAC) to get support in isolating the fault. For
suitable preparation save the error symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are
out of the operators scope.

18

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

200509 - System halt due to detected hardware exception


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Osu
communicationAlarm
VendorSpecific
critical

Error Description
This problem reports a situation, where the software health observation system has detected an 'unexpected' signal by the Node B hardware. This will be just logged by the
observation system. This problem report contains information about the signal originator. This condition leads to a recovery reset of the whole Node B. The affected Node B
Core Controller is temporarily not available. Due to the recovery reset, only the system
log files could be used for 'post' analysis.
Troubleshooting
Contact the technical assistance center (TAC) to get support in isolating the fault. For
suitable preparation save the error symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are
out of the operators scope.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

19

OML:Node B

Outputs
Node B

200510 - System halt due to detected software loading


malfunction
Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Osu
communicationAlarm
VendorSpecific
critical

Error Description
This problem reports a situation, where the system loader detects a failure during software loading. This problem report contains information about the name of the failed software component. If the malfunction relates to a HW problem, it might be necessary to
replace the addressed card. If the malfunction relates to a software problem, it might be
solved by the recovery mechanisms of the software management subsystem (ISW).
This condition leads to a recovery reset of the whole Node B. The affected Node B
Core Controller is temporarily not available. Due to the recovery reset, only the system
log files could be used for 'post' analysis.
Troubleshooting
1. Try to reset the addressed card.
2. If there is a hardware failure, replace the addressed card. Replacement must be
done according to the Maintenance Manual MMN:Node B.
3. It there is a software failure, contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save the error symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific
measures must be taken which are out of the operators scope.

20

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

200656 - Iub link broke down


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Cc
equipmentAlarm
LinkFailure
critical

Error Description
An existing ATM connection between CRNC (controlling RNC) and Node B (Iub link) is
broken because the CRNC is down, the cable has been plugged off or is broken. Therefore the Node B performs a reset.
The following subsequent alarms may also be initiated depending on the used interface
type (E1/J1/T1, STM-1/OC-3):
202056 - Loss Of Signal on Physical Link
202057 - Loss Of Frame on Physical Link
202058 - Loss Of Cell Delineation on Physical Link
202059 - Alarm Indication Signal on Physical Link
202060 - Remote Alarm Indication on Physical Link
202061 - Loss of Multi Frame Alarm Indication on E1 Physical Link
202062 - Line Alarm Indication Signal Indication on STM1 Physical Link
202063 - Line Remote Defect Indication on STM1 Physical Link
202064 - Path Loss of Pointer Indication on STM1 Physical Link
202068 - Signal Label Mismatch Indication on STM1 Physical Link
202070 - Signal Degrade Indication on STM1 Physical Link
202071 - Excessive Bit Error Rate Indication on STM1 Physical Link
202072 - Alarm Indication Signal on an ATM VC
202073 - Remote Defect Indication on an ATM VC
202074 - SSCOP Failure Indication on an ATM VC used by ALCAP or NBAP
202075 - Alarm Indication Signal on an ATM VP
202076 - Remote Defect Indication on an ATM VP
202077 - ALCAP PVC Out Of Service Indication
The Iub link broke down alarm may be caused by:
1. A failure in the RNC. In this case alarms from the RNC are additionally active.
2. A failure of the link equipment or in the cable connection between Node B and link
equipment (LE). Usually the Node B is connected to the RNC or each other (Iub interface) via link equipment (LE) and in some rare cases by direct lines. If LE is involved the operation and maintenance system of this network has to be used for
getting information about the state and status of the relevant network element (NE).
3. A failure within the OVPT or the IUBCON in case an E1/J1/T1 interface is used.
4. A failure in the CC (refer to 200994 - HW Failure). In this case, other CC initiated
alarms are additionally active.
The affected Node B is not working. All services will be interrupted. All cells will be lost.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

21

OML:Node B

Outputs
Node B

Troubleshooting
If RNC alarms for the Iub link to the affected Node B are reported to the RC concentrate the fault clearance actions on these alarms first.
Is the LE, which is connected to the relevant port, reporting an equipment alarm?
if an equipment alarm at the LE is present try to fix this fault first which probably
also eliminates the Iub link broke down alarm.
Check the cable connections:
1. In case of E1/J1/T1 lines check the OVPT or IUBCON
Electrical Iub lines (E1/J1/T1) are connected to the Node B using an OVPT (overvoltage protection and tracer module) equipped with surge arresters or an IUBCON
(Iub connector). Both are available for coax and symmetrical cables.
check surge arresters at OVPT and replace a defective one if necessary
replace OVPT or IUBCON if no other reason was found
2. In case of optical STM-1/OC-3 lines

WARNING
To avoid damage to health, you must observe the regulations regarding protection
against radiation from laser devices (EN 60825 / IEC 60825). You must always use dedicated laser-protective goggles. Never look into open fiber-optic cable ends, as this may
damage your eyes.

check for:
proper connection at the LE (good contact, clean optical connector)
proper connection at the Node B (good contact, clean optical connector)
undamaged cable between Node B and LE respectively other Node B or RNC
Is there also an equipment alarm of the Core Controller (CC) in the reporting Node B
present?
Using the ALARM View window of the LMT:
click on the Alarm View button or use the shortcut key Ctrl-A
use the filter and sort function to concentrate on CC alarms
If an equipment alarm of the CC is present try to fix this fault first which probably also
eliminates the Iub link broke down alarm.

22

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

200657 - SSCOP sent overrun


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Cc
equipmentAlarm
LinkFailure
critical

Error Description
Node Bs SSCOP is not able to transmit the messages to the CRNC (controlling RNC)
using the requested data rate. Therefore, the Node B performs an automatic reset.
Troubleshooting
Contact the technical assistance center (TAC) to get support in isolating the fault. For
suitable preparation save the error symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are
out of the operators scope.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

23

OML:Node B

Outputs
Node B

200658 - Transmit bandwidth limit for NBAP reached


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

NodeBFddE
qualityOfServiceAlarm
System ResourcesOverload
minor

Error Description
Under conditions with high traffic, the NBAP bandwidth set at the reporting Node Bs Iub
interface may not be sufficient. If the high-traffic condition persists, the Node B will start
dropping messages.
This alarm therefore indicates a general lack of bandwidth to send messages at the
Node Bs Iub interface. In other words, the Node Bs transmit bandwidth for NBAP connections toward the RNC has reached its limit and the message buffers are exhausted.
The Node B then started overload defence actions. This may affect service quality because dedicated measurement reports will be dropped and RL setup or reconfiguration
attempts will be rejected.
The reporting Node B continues operation. Service quality, however, is decreased. The
increased traffic thus requires appropriate settings for the transmit bandwidth at the
Node Bs Iub interface. In other words, the Node Bs database (DB) settings have to be
revised and the transmit bandwith at the Iub interface has to be increased.
Troubleshooting
Take the following measures to clear this alarm and to prevent this overload condition
in the future:
1. Revise the reporting Node Bs DB settings in such a way that the NBAP transmit
bandwidth is increased.
Increase both the ingress and the egress peak cell rate to an identical value, using
the following commands:
Set peakCellRateIngress TrafficDescriptor
Set peakCellRateEgress TrafficDescriptor
2. If the first action did not clear the cause for this alarm, contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save
the error symptoms as described in "Collect Info for Assistance". Log files need to
be analyzed and specific measures must be taken which are out of the operators
scope.

24

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

200659 - Core Controller overload protection activated


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

NodeBFddE
qualityOfServiceAlarm
System ResourcesOverload
minor

Error Description
A situation with peak load has occurred in the reporting Node B. Due to this situation,
the Node B may activate an overload protection. Overload protection is a defence action
of the Node B to maintain stable operation.
In fact, the reporting Node Bs core controller (CC) CPU capacity has reached its limit.
As a consequence, RL setup or reconfiguration attempts will be rejected. Service quality
is decreased.
The causes for the Node Bs high CPU load needs to be investigated.
Troubleshooting
First, investigate the causes for the high CC load.
Contact the technical assistance center (TAC) to get support in isolating the fault. For
suitable preparation save the error symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are
out of the operators scope.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

25

OML:Node B

Outputs
Node B

200706 - An error occurred in the nbDatabase


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Osu
processingErrorAlarm
SoftwareError
critical

Error Description
Node B startup failed because of an error in the nbDatabase.
This may be caused by the following:
A new database was installed but does not match release and version of the software load.
A new database was installed but does not match the hardware configuration.
A new hardware equipment was installed but was not configured in the database.
A software error has occurred.
Troubleshooting
Depending on the cause due to which the Node B startup failed, perform one of the following tasks:
If the new database does not match release and version of the software load:
Check the Node B database with the mibCheck tool delivered with Node B software. Proceed according to the OGL:Node B DB Editing Guide.
Adapt the database according to the results of this check. Proceed according to
the OGL:Node B DB Editing Guide.
If the new database does not match the hardware configuration:
Check that the current database version is used (from the RC or on site). Proceed
according to the OGL:Node B DB Editing Guide.
Upgrade the database if necessary. Use the mibUpgrader tool. Proceed according to the OGL:Node B DB Editing Guide.
Check the Node B database to generate a new database that matches the hardware configuration. Use the mibCheck or mibCheckWin tool. Proceed according
to the OGL:Node B DB Editing Guide.
If only little changes are necessary, enter new hardware equipment in database.
To edit the Node Bs database, proceed according to the OGL:Node B DB Editing
Guide.
If new hardware equipment is not configured in the database:
Check the hardware configuration (on site). Use the mibCheck or mibCheckWin
tool. Proceed according to the OGL:Node B DB Editing Guide.
Enter new hardware equipment in database. To edit the Node Bs database, proceed according to the OGL:Node B DB Editing Guide.
If the error is not caused by an invalid DB or an unsuitable hardware configuration:
Contact the technical assistance center (TAC) to get support in isolating the fault. For
suitable preparation save the error symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which
are out of the operators scope.

26

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

200707 - A warning occurred in the nbDatabase


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Osu
processingErrorAlarm
SoftwareError
warning

Error Description
There may be an error in the nbDatabase. This warning only occurs during a version upgrade of the database.
There may be the following causes:
1. During version upgrade: There are missing attributes because of using a database
from an older version.
2. No version upgrade: The database is defective or a new database was installed but
does not match the software version.
Troubleshooting
1. There is no action necessary because default values will be used.
2. If the new database does not match the software load:
Check the Node B database with the mibCheck tool delivered with Node B software. Proceed according to the OGL:Node B DB Editing Guide.
Adapt the database according to the results of this check. Proceed according to
the OGL:Node B DB Editing Guide.

NOTE
Software load and database must base on the same InfoModel which is
also the basis for the Command Manual CML:Node B.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

27

OML:Node B

Outputs
Node B

200756 - System call unsuccessful


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

*
processingErrorAlarm
SystemCallUnsuccesful
critical

Error Description
A fatal software error has occurred. This is a recoverable error situation caused by a potentially serious software fault, which should be reported to customer services!
A call to the operating system or the operating system wrapper layer has failed. After an
unsuccessful system call, the Node B resets automatically. Due to the reset, all services
will be interrupted.
This may cause the following:
All cells will be lost.
The connection between the Node B and the RNC will be lost.
Uplink or downlink errors will be reported by other Node Bs if they are connected to
the resetting Node B.
Once the reset is completed, normal operational service should be resumed i.e. the cells
are build up again, connection with the RNC will be re-established and any cross connections will be built up again.
This error is caused by a corrupted software image.
Troubleshooting
1. If a reset does not fix the problem, use a previous, working version of the software.
2. Contact the technical assistance center (TAC) to get support in isolating the fault.
For suitable preparation save the error symptoms as described in "Collect Info for
Assistance". Log files need to be analyzed and specific measures must be taken
which are out of the operators scope.

28

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

200757 - Unexpected software error


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

*
processingErrorAlarm
SoftwareError
critical

Error Description
A fatal software error has occurred. This is a recoverable error situation caused by a potentially serious software fault, which should be reported to customer services!
A call to the operating system or the operating system wrapper layer has failed. After an
unexpected software error, the Node B resets automatically. Due to the reset, all services will be interrupted.
This may cause the following:
All cells will be lost.
The connection between the Node B and the RNC will be lost.
Uplink or downlink errors will be reported by other Node Bs if they are connected to
the resetting Node B.
Once the reset is completed, normal operational service should be resumed i.e. the cells
are build up again, connection with the RNC will be re-established and any cross connections will be built up again.
This error is caused by a corrupted software image.
Troubleshooting
1. If a reset does not fix the problem, use a previous, working version of the software.
2. Contact the technical assistance center (TAC) to get support in isolating the fault.
For suitable preparation save the error symptoms as described in "Collect Info for
Assistance". Log files need to be analyzed and specific measures must be taken
which are out of the operators scope.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

29

OML:Node B

Outputs
Node B

200758 - Not enough memory


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

*
processingErrorAlarm
OutOfMemory
critical

Error Description
A fatal software error has occurred. This is a recoverable error situation caused by a potentially serious software fault, which should be reported to customer services. The recovery will result in a complete reset of the Node B. Due to the reset, all services will be
interrupted.
This may cause the following:
All cells will be lost.
The connection between the Node B and the RNC will be lost.
Uplink or downlink errors will be reported by other Node Bs if they are connected to
the resetting Node B.
All connections to the management system will also be interrupted during this reset period. Once the reset is completed, normal operational service should be resumed i.e. the
cells are built up again, connection with the RNC will be re-established and any cross
connections will be built up again. Any calls that were in operation before the reset are
lost.
Troubleshooting
Contact the technical assistance center (TAC) to get support in isolating the fault. For
suitable preparation save the error symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are
out of the operators scope.

30

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

200759 - A fatal error has occurred that may affect OAM


command processing
Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

*
processingErrorAlarm
SystemCallUnsuccessful
critical

Error Description
A fatal software error has occurred! This is a recoverable error situation caused by a potentially serious software fault, which should be reported to customer services. The recovery will result in a complete reset of the Node B. Due to the reset, all services will be
interrupted.
This may cause the following:
All cells will be lost.
The connection between the Node B and the RNC will be lost.
Uplink or downlink errors will be reported by other Node Bs if they are connected to
the resetting Node B.
All connections to the management system will also be interrupted during this reset period. Once the reset is completed, normal operational service should be resumed i.e. the
cells are built up again, connection with the RNC will be re-established and any cross
connections will be built up again. Any calls that were in operation before the reset are
lost.
Troubleshooting
Contact the technical assistance center (TAC) to get support in isolating the fault. For
suitable preparation save the error symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are
out of the operators scope.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

31

OML:Node B

Outputs
Node B

200905 - VSWR alarm Low


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Duamco, Rrh
equipmentAlarm
TransmitterAntennaNotAdjusted
minor

Error Description
Each antenna port of the DUAMCO/RRH is monitored for the Voltage Standing Wave
Ratio (VSWR) of the connected antenna system. Two levels for the antenna return loss
can be defined for which an alarm of the appropriate severity will be generated as soon
as the relevant threshold is exceeded. The VSWR alarm Low is the minor one - which
is under consideration here - related with the lower threshold and may be received before alarm 200906 - VSWR alarm High. The most likely reason for the VSWR alarms is
a defective antenna feeder cable or a damaged antenna.
Troubleshooting
To isolate the origin of the high return loss it is necessary to know whether the antenna
system is equipped with a TMA / DTMA or not. This is known from the site specific documentation or can be verified by checking the availability via LMT.
Probable causes:
A destroyed antenna due to a stroke of lightning or thunderstorms can trigger this
alarm
Water inleakage or an otherwise damaged feeder cable is the most likely reason
Other alarms related with the TMA e. g. 200910 - TMA feeder alarm or 200911 TMA DC alarm may also be received previously indicating a broken/short-circuit
feeder cable or a faulty TMA itself

WARNING
When replacing antenna cables, antennas, TMAs or DUAMCOs switch off the relevant
breakers which supply the LPAs/CATs involved in the affected antenna branch in order
to prevent an uncontrolled emission of microwave radiation. For RRHs, switch off the
power supply to prevent uncontrolled emission of microwave radiation.
For an effective trouble-shooting the actions in the following order should be performed
with reference to the relevant manuals:
1. Inspect the antenna, the feeder cable and the TMA - if mounted - visually for any
damage caused by lightnings, thunderstorms or other impacts (e.g. bullets).
Replace the defective cable or antenna according to the OEM manual
Replace the defective TMA. Replacement must be done according to the Maintenance Manual MMN:Node B.
2. Check all connectors of the antenna system for correct and tight fit and if loose for
not being corroded.
Tighten loose connectors after removing corrosion or replacing destroyed ones.
3. Measure the antenna feeder cable parameters according to the OEM specification.
Replace the defective cable if minimum requirements are not met according to the
OEM manual.

32

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

4. If none of the causes above can be identified for the alarm the DUAMCO or RRH is
assumed to be defective.
Replace the DUAMCO or RRH. Replacement must be done according to the
Maintenance Manual MMN:Node B

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

33

OML:Node B

Outputs
Node B

200906 - VSWR alarm High


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Duamco, Rrh
equipmentAlarm
TransmissionAntennaFailure
major

Error Description
Each antenna port of the DUAMCO/RRH is monitored for the Voltage Standing Wave
Ratio (VSWR) of the connected antenna system. Two levels for the antenna return loss
can be defined for which an alarm of the appropriate severity will be generated as soon
as the releveant threshold is exceeded. The 200905 - VSWR alarm Low is the minor one
related with the lower threshold and may be received before the VSWR alarm High
which is under consideration here. The most likely reason for the VSWR alarms is a defective antenna feeder cable or a damaged antenna.
As a consequence, cells or calls could potenitally be lost. Furthermore, the states of all
affected managed objects is changed accordingly.
Troubleshooting
To isolate the origin of the high return loss it is necessary to know whether the antenna
system is equipped with a TMA / DTMA or not. This is known from the site specific documentation or can be verified by checking the availability via LMT.
Probable causes:
A destroyed antenna due to a stroke of lightning or thunderstorms can trigger this
alarm
Water inleakage or an otherwise damaged feeder cable is the most likely reason
Other alarms related with the TMA e. g. 200910 - TMA feeder alarm or 200911 TMA DC alarm may also be received previously indicating a broken/short-circuit
feeder cable or a faulty TMA itself

WARNING
When replacing antenna cables, antennas, TMAs or DUAMCOs switch off the relevant
breakers which supply the LPAs/CATs involved in the affected antenna branch in order
to prevent an uncontrolled emission of microwave radiation. For RRHs, switch off the
power supply to prevent uncontrolled emission of microwave radiation.
For an effective trouble-shooting the actions in the following order should be performed
with reference to the relevant manuals:
1. Inspect the antenna, the feeder cable and the TMA - if mounted - visually for any
damage caused by lightnings, thunderstorms or other impacts (e.g. bullets).
Replace the defective cable or antenna according to the OEM manual
Replace the defective TMA. Replacement must be done according to the Maintenance Manual MMN:Node B.
2. Check all connectors of the antenna system for correct and tight fit and if loose for
not being corroded.
Tighten loose connectors after removing corrosion or replacing destroyed ones.

34

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

3. Measure the antenna feeder cable parameters according to the OEM specification.
Replace the defective cable if minimum requirements are not met according to the
OEM manual.
4. If none of the causes above can be identified for the alarm the DUAMCO or RRH is
assumed to be defective.
Replace the DUAMCO or RRH. Replacement must be done according to the
Maintenance Manual MMN:Node B

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

35

OML:Node B

Outputs
Node B

200907 - RX alarm Low


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Duamco, Tma, Rrh


equipmentAlarm
ReceiverFailure
minor

Error Description
This alarm occurred because one branch of an RX amplifier of the reporting LRU has
failed. The RX amplifier is still working but degraded in its performance.
If both branches become out of order, the 200908 - RX alarm High will be sent.
Troubleshooting
An immediate action is not necessary, but it is recommended to replace the DUAMCO
or the TMA or the RRH as soon as possible. Perform the following tasks in the order
described:
First, before replacing the equipment, try to reset the reporting MOC. Use the TREE
View window of the LMT or apply the rst command to the relevant managed object.

NOTE
During the reset and the repair action the cell is not available.
If the alarm persists after the reset, replace the DUAMCO or the TMA or the RRH. Replacement must be done according to the Maintenance Manual MMN:Node B.

36

DANGER
To avoid the danger of an uncontrolled emission of microwave radiation, switch off the
breakers for the related LPAs/CATs before replacing the TMA or DUAMCO. For RRHs,
switch off the power supply to prevent uncontrolled emission of microwave radiation.

NOTE
Before replacing the DUAMCO, set the DIP-switches on the front side of the DUAMCO
in the same configuration as it was on the replaced DUAMCO.

NOTE
After replacing the TMA, reset the DUAMCO via LMT or reset button. When resetting
the DUAMCO via reset button. press the button for at least eight seconds. Otherwise,
the reset will not become effective.
Then reset the TMA (via LMT). Use the TREE View window or the rst command.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

200908 - RX alarm High


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Duamco, Tma, Rrh


equipmentAlarm
ReceiverFailure
major

Error Description
This alarm occurred because both branches of an RX amplifier of the reporting LRU
have failed.
If the alarm message is sent by the TMA, the MUCO mode in the DUAMCO will switch
back to AMCO mode. After the reset, the DUAMCO will be in its original mode according
to the DIP-switches on the front.
There might have been an alarm 200907 - RX alarm Low before.
As a consequence, cells or calls could potentially be lost. Furthermore, the states of all
affected managed objects change accordingly.
Troubleshooting
Reset the reporting MOC. Use the TREE View window of the LMT or apply the rst command to the relevant MOC.

NOTE
During the reset and the repair action the cell is not available.
If the alarm persists after the reset, replace the DUAMCO or the TMA. Replacement
must be done according to the Maintenance Manual MMN:Node B.

DANGER
To avoid the danger of an uncontrolled emission of microwave radiation, switch off the
breakers for the related LPAs/CATs before replacing the TMA or DUAMCO. For RRHs,
switch off the power supply to prevent uncontrolled emission of microwave radiation.

NOTE
Before replacing the DUAMCO, set the DIP-switches on the front side of the DUAMCO
in the same configuration as it was on the replaced DUAMCO.

NOTE
After replacing the TMA, reset the DUAMCO via LMT or reset button. When resetting
the DUAMCO via reset button, press the button for at least eight seconds. Otherwise,
the reset will not become effective. Then reset the TMA (via LMT). Use the TREE View
window or the rst command.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

37

OML:Node B

Outputs
Node B

200909 - TMA switched off, but not defective


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Tma
equipmentAlarm
PowerSupplyFailure
minor

Error Description
The TMA is switched off, but not defective and the DUAMCO works in AMCO mode.
This mode is indicated by the TMA LED which is off. The receiver is degraded in its performance. The failure occurs in one of the following situations:
Most likely this alarm is raised during normal Node B operation if the DIP switch 1
of the corresponding DIP switch group of the DUAMCO is set to OFF position (AMCO mode/TMA off) by accident. The TMA is switched off, but not defective.
In rare cases, the alarm can also be raised together with another more critical alarm
like 200908 - RX alarm High.
Troubleshooting
Check the power supply for the TMA at the associated DUAMCO. Furthermore, verify
that the TMA is connected to the DUAMCO and check if the DIP switch 1 of the DUAMCO (TMA ON/OFF) is switched ON.
If the DIP switch 1 was set to the OFF position by accident do the following:
1. Switch the DUAMCO DIP switch 1 to the ON position. The TMA LED should now be
on (green), but the alarm still exists at the LMT/RC.
2. Reset the TMA managed object in the TREE View window of the LMT. Alternatively,
apply the rst command to the TMA managed object.
If other critical alarms like 200908 - RX alarm High are also raised, please refer to the
corresponding alarm description. Please note that the DIP switch 1 may be in the ON
position in this case.

38

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

200910 - TMA feeder alarm


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Tma
equipmentAlarm
ReceiverFailure
minor

Error Description
The DUAMCO monitors the 2.176 MHz signaling carrier coming from the TMA. A breakdown of this carrier initiates the TMA Feeder Alarm. The amplifier is degraded in its performance. The combination of OST/AVS for the addressed TMA and the related
localCellE managed object instance changes to disabled/failed and enabled/degraded, respectively.
The TMA Feeder Alarm may be caused by:
A failure in the antenna feeder cable. In this case, the 200905 - VSWR alarm Low /
200906 - VSWR alarm High and uplink/downlink alarms may be additionally active.
A failure in the TMA.
A failure in the power supply, indicated by the 200911 - TMA DC alarm.
If a RET module is installed in the current configuration, the alarm 201004 - RET communication error will be output as a consequence of this alarm.
For TMA recovery, a reset of the related DUAMCO is required in order to re-establish
the communication between the DUAMCO and the TMA. A reset of the TMA managed
object is not possible while this failure persists.
Troubleshooting

DANGER
To avoid the danger of an uncontrolled emission of microwave radiation, switch off the
breakers for the related LPAs/CATs before replacing the TMA or DUAMCO.
1. First, reset the related DUAMCO to re-establish the communication between the
DUAMCO and the TMA.
Use the TREE View window or the rst command.
2. The further procedure depens on the actual problem. Refer to the following list:
If only the TMA Feeder Alarm exists, replace the TMA. Replacement must be
done according to the Maintenance Manual MMN:Node B
If an additional DC alarm (200911 - TMA DC alarm) is active in the ALARM View
window, check the DC/DC converter of the DUAMCO: Unplug the antenna feeder
cable and measure the voltage at the antenna port of the DUAMCO. If the voltage
is below the defined threshold, the DC/DC converter of the DUAMCO is defective.
Replace the DUAMCO. Replacement must be done according to the Maintenance Manual MMN:Node B
If an additional VSWR alarm (200905 - VSWR alarm Low or 200906 - VSWR
alarm High) is active in the ALARM View window, check the antenna feeder cable:
If the alarm message is canceled after unplugging the antenna feeder cable, the
fault is caused by a short circuit in the antenna feeder cable or an overcharged
TMA. Check the antenna feeder cable.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

39

OML:Node B

Outputs
Node B

3. If none of the above reasons could be verified, replace the TMA. Replacement must
be done according to the Maintenance Manual MMN:Node B

40

NOTE
Before replacing the DUAMCO, set the DIP-switches on the front side of the DUAMCO
in the same configuration as it was on the replaced DUAMCO.

NOTE
After replacing the TMA, reset the DUAMCO via LMT or reset button. When resetting
the DUAMCO via reset button, press the button for at least eight seconds. Otherwise
the reset will not become effective. Then reset the TMA (via LMT). Use the TREE View
window or the rst command.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

200911 - TMA DC alarm


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Duamco
equipmentAlarm
EquipmentFailure
minor

Error Description
The power supply for the TMA is fed via the antenna feeder cable from the DUAMCO to
the TMA. If the supply voltage for the TMA at the antenna port of the DUAMCO is below
the defined threshold (11,3 V), the TMA DC Alarm is initiated.
The TMA DC Alarm may be caused by:
A failure in the DC/DC converter of the DUAMCO.
A short circuit in the antenna feeder cable. In this case the alarms 200906 - VSWR
alarm High or 200905 - VSWR alarm Low and uplink/ downlink alarms are additionally active.
The TMA is overcharged. The current consumption of the TMA is too high.
The amplifier is degraded in its performance.
Troubleshooting

DANGER
To avoid the danger of an uncontrolled emission of microwave radiation, switch off the
breakers for the related LPAs/CATs before replacing the TMA or DUAMCO.
1. Unplug the antenna feeder cable and measure the voltage at the antenna port of the
DUAMCO. If the voltage is below the defined threshold, the DC/DC converter of the
DUAMCO is defective. Replace the DUAMCO. Replacement must be done according to the Maintenance Manual MMN:Node B
2. If the alarm message is cleared after unplugging the antenna feeder cable, the fault
is caused by a short circuit in the antenna feeder cable or an overcharged TMA.
Check the antenna feeder cable.
3. If none of the above reasons could be verified, replace the TMA. Replacement must
be done according to the Maintenance Manual MMN:Node B

NOTE
Before replacing the DUAMCO, set the DIP-switches on the front side of the DUAMCO
in the same configuration as it was on the replaced DUAMCO.

NOTE
After replacing the TMA, reset the DUAMCO via LMT or reset button. When resetting
the DUAMCO via reset button, press the button for at least eight seconds. Otherwise,
the reset will not become effective. Then reset the TMA (via LMT). Use the TREE View
window or the rst command.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

41

OML:Node B

Outputs
Node B

200914 - Fan unit failed


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Fan
environmentalAlarm
FanFailure
major

Error Description
One of the fan units in the Node B is defective. There might be a failure of components
sensitive to heat. Caused by the lack of air circulation, there might occur temperature
alarms, reported by the rack/ shelter or the cards.
This alarm message may occur in conjunction with temperature alarms:
200920 - High temperature of PA
200921 - Over temperature of PA
200995 - High Temperature Limit (Ht3) reached
200996 - Critical Temperature Limit (Ht4) reached

42

NOTE
If the reporting Node B is of type NB-441/NB-881, the lack of air circulation may be
caused by a polluted membrane filter (MEF). Therefore, if the Node B site is located in
heavily air-polluted environments combined with special temperature conditions, a
maintenance of the MEF filters in the outdoor NB-441/NB-881 might be necessary.
If the MEFs are polluted, the 201029 - MEF blocked or 201035 - MEF completely
blocked alarm is output. Refer to the relevant alarms error description and follow the
troubleshooting.

NOTE
To avoid toggling of this alarm from the same managed object, i.e. the alarm is raised
and ceased alternately, the alarm will only be ceased if the following applies:
After having cleared the cause of this fault, the addressed LRU has not reported the
same alarm again for at least 100 seconds.
Otherwise, this alarm will not be ceased but remains active. Troubleshooting tasks must
be taken.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

Troubleshooting

i
!

NOTE
If all fan units of the B-shelf are defective, self-disabling of B-shelf cards can occur as a
consequence. The Node B handles self-disabled cards as if a fatal board failure, such
as an on-board power supply failure, has occurred. In other words, the combination of
OST/AVS changes to disabled/not installed and the LED of the self-disabled card is
off.

NOTE
The defective fan unit(s) are recommended to be exchanged within the next 24 hours!

CAUTION
When pulling out the fan module, the rotor may still rotate for a few seconds. Watch your
fingers.
1. Identify the defective fan unit. Use either the TREE View window or the ALARM View
window of the LMT.
2. Replace the fan unit. Replacement must be done according to the Maintenance
Manual MMN:Node B

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

43

OML:Node B

Outputs
Node B

200915 - Site input alarm detected


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

ExtEquipIn
environmentalAlarm
ExternalEquipmentFailure
minor, major, critical

Error Description

NOTE
Changing the ExtEquipIn managed objects alarm severity, alarm value, associated
string, and probable cause attributes does not affect an existing 200915 - Site input
alarm detected alarm. The modified attributes will take effect for the next occurrence of
this alarm.
When modifying the attributes mentioned above, however, only one attribute can be
changed simultaneously. In other words, when using the relevant command for setting
these attributes, only one single attribute of one single managed object can be set.
A site input alarm was detected.
This alarm is raised if one of the connected site input sensors is active, e.g. water detector, site door open switch, window broken, air condition system defect, etc.
The reported Probable Cause and Severity in the Failure Event Report depend on
the configuration of the related ExtEquipIn managed object in the nbDatabase.
For the severity the value of the attribute label alarmSeverity of each object class
ExtEquipIn can be set to minor, major, or critical in the nbDatabase by an equivalent
string.
The ExtEquipIn instances ExtEquipIn.4 to ExtEquipIn.12 at the RRH are reserved
for reporting alarms related to the power supply units for RRHs (PSRs). These ExtEquipIn instances have to exist in the database in configurations with RRHs.
Whereas the value of the probableCause attribute label is represented by a number which is related to a string defined in the Infomodel, e. g.:
4 = Battery Breakdown
22 = Power Supply Failure
147 = Smoke Detected
149 = Fuse Failure
With the new AD panel HW, the alarm properties (Probable Cause: PowerSupplyFailure) listed in the following table may be displayed.
Source

Additional Text

ExtEquipIn.7

AC/DC Converter - Mains Break Down Alarm

ExtEquipIn.8

AC/DC Converter - Battery Breakdown Alarm

ExtEquipIn.9

AC/DC Converter - Battery Charger Fault

ExtEquipIn10

AC/DC Converter - DC Output Voltage out of Tolerance

For explanations of customizing a nbDatabase please refer to the relevant chapter of


the OGL:Node B DB Description.

44

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

External equipment input identifier (extEquipInId) and pinning relations to the ACTM
(Alarm Collection Terminal Master) can be found in the HWMN:Node B Cards/Modules.
Troubleshooting

If the following alarm properties are displayed after the system was in battery backup
operation there is no need for further actions:
- Source: ExtEquipIn.10 (of Service.Rack.0)
- Probable Cause: PowerSupplyFailure
- Additional Text: AC/DC Converter - DC Output Voltage out of Tolerance
Before re-charging is finished and battery is full again, it may happen that the alarm oszillates sometimes. When battery is fully charged the alarm is ceased durable.
1. Inspect the supervised object for being in false condition and get rid of the alarm
causing conditions, e. g. window broken or air condition system defect.
2. If the alarm is active even though no unusual conditions are identifiable, the supervision contacts and the cabling should be checked.
3. A wrong configuration of the database could also be the reason for an alarm:
upload the database via LMT
find the alarmValue attribute of the extEquipInId of the alarm in question and
verify the setting: 0 = low active = closed contact; 1 = high active = open contact
correct the setting if necessary and download the database
activate the downloaded database
4. If the above measures did not help to cease this alarm, contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save
the error symptoms as described in "Collect Info for Assistance". Log files need to
be analyzed and specific measures must be taken which are out of the operators
scope.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

45

OML:Node B

Outputs
Node B

200916 - Rack Door open


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

BaseRack, ServiceRack, Booster


environmentalAlarm
EnclosureDoorOpen
minor

Error Description
The door condition is controlled by a reed switch together with a permanent magnet.
This alarm occurs if one of the following doors is open:
The door of a rack
The door of a single shelter
One or both doors of a double shelter
A damaged or misaligned supervision contact (reed switch - magnet) or a door that is
not firmly closed (gap more than 10mm) should also be taken into consideration.
For outdoor shelters it has to be noted that the filter system (MEF = membrane filter)
may be by-passed allowing dust to contaminate the equipment in the shelter, resulting
in the malfunction.
Troubleshooting
1. Inspect the doors for perfect closing and locking.
2. Damaged doors (vandalism) have to be replaced. Shelters must be air tight to ensure effective air filtering and circulation as well as electromagnetic shielding requirements conformance.
3. If the alarm is active even though all doors are perfectly closed, the supervision contacts (reed switch - magnet) and the cabling should be checked:
Is the door supervision contact connected to the ACT board? For double shelters
the left door contact is connected to the ACTCM at the EMI-Panel, the right door
contact is connected to the ACTCB at the DC-Panel. The door contact of single
shelters is connected to the ACTCS at the EMI-Panel whereas the door contact
of a rack to the ACTCB at the DC-Panel connected is.
Is the permanent magnet at the top edge of the doors in place? If not, adjust the
magnet or fit a new one.
With the door open place a permanent magnet close to the reed switch at the top
edge of the rack/shelters opening. Drawing the magnet far and near should activate/deactivate the alarm. If not, the reed switch has to be replaced.

46

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

200918 - PA combiner interface fault


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Lpa, Booster, Cat


equipmentAlarm
TransmitterFailure
major

Error Description
An excessive level of Radio Frequency (RF) reflected power occurred. The cable between the Power Amplifier (PA) and the DUAMCO may be damaged or not connected.
As a consequence, the PA is switched off.
The PA was put out of service. This leads to a scenario in which cells or calls could potentially be lost. The states of all affected managed objects are then changed accordingly.
Troubleshooting
Check the cable connection between the PA and the DUAMCO:
For correct attached and tightened connectors (N-type) at PA and DUAMCO
Undamaged cable (visual inspection)
Two different lengths of the RG142 cables are used, depending on wether the PA is located left (80 mm) or right (250 mm) of the DUAMCO.

WARNING
When replacing cables connected to the output of a PA, the relevant breaker which supplies this PA has to be switched off in order to prevent an uncontrolled emission of microwave radiation.
1. A damaged cable has to be replaced by the right type and length.
2. If the error has not ceased yet, the related card has to be replaced. Replacement
must be done according to the Maintenance Manual MMN:Node B.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

47

OML:Node B

Outputs
Node B

200919 - Failure in the DC supply of PA


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Lpa, Booster, Cat, Rrh


equipmentAlarm
PowerSupplyFailure
major

Error Description
A failure in the internal DC supply of the Power Amplifier (PA) occurred. As a consequence, the PA is switched off.
The PA was put out of service. This leads to a scenario in which cells or calls could potentially be lost. The states of all affected managed objects change accordingly.
Troubleshooting
At the front of the PA the state of the DC supply is shown by an LED marked POWER.
This LED can either be ON or OFF, depending on the failure cause inside the LPA.
Please replace the relevant PA. Replacement must be done according to the Maintenance Manual MMN:Node B.

48

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

200920 - High temperature of PA


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Lpa, Booster, Cat, Rrh


environmentalAlarm
HighTemperature
minor

Error Description
The temperature of the PA has exceeded the maximum operating temperature specified. This could be caused by an internal problem of the PA or by insufficient cooling of
the rack/shelter.
If this alarm is reported by a booster, the 201034 - Boosters Fan unit failed alarm may
be the root cause for the failure reported by this alarm.
An additional rack/shelter temperature alarm (200995 or 200996) or fan alarms
(200914) may indicate that the air circulation is decreased. A fan unit could be defective
or especially for outdoor shelters obstructed air in- or outlets could also reduce the cooling capability.
This alarm message may occur in conjunction with temperature alarms:
200914 - Fan unit failed
200995 - High Temperature Limit (Ht3) reached
200996 - Critical Temperature Limit (Ht4) reached

NOTE
If the reporting Node B is of type NB-441/NB-881, the lack of air circulation may be
caused by a polluted membrane filter (MEF). Therefore, if the Node B site is located in
heavily air-polluted environments combined with special temperature conditions, a
maintenance of the MEF filters in the outdoor NB-441/NB-881 might be necessary.
If the MEFs are polluted, the 201029 - MEF blocked or 201035 - MEF completely
blocked alarm is output. Refer to the relevant alarms error description and follow the
troubleshooting.
Troubleshooting
Depending on the actual problem, perform one of the following tasks:
In the event that the following preconditions are met, i.e.
The 200920 - High temperature of PA alarm is reported by a booster and
The 201034 - Boosters Fan unit failed alarm has been output before,
refer to the error description of the 201034 - Boosters Fan unit failed alarm and follow the troubleshooting accordingly.
The 201034 - Boosters Fan unit failed alarm may indicate the root cause for the failure reported by this alarm.
If this alarm is raised for one single PA only, it is most likely that the PA itself has got
a problem. Replace the relevant PA. Replacement must be done according to the
Maintenance Manual MMN:Node B.
In case of one or more fan alarms or a rack/shelter temperature alarm is reported
the addressed fan unit should be checked and possibly replaced. Replacement must
be done according to the Maintenance Manual MMN:Node B.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

49

OML:Node B

Outputs
Node B

50

A rack/shelter temperature alarm lead one to assume that the air circulation is decreased by obstructed air in- or outlets. Check and clean the air in- and outlets according to the section Cleaning of Air In- and Outlets in the Maintenance Manual
MMN:Node B.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

200921 - Over temperature of PA


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Lpa, Booster, Cat, Rrh


equipmentAlarm
ExcessiveTransmitterTemperature
major

Error Description
The PA is overheated and a high temperature alarm (200920 - High temperature of PA)
may be preceded. Because the temperature has reached a level that would cause damage, the PA is switched off. This could be caused by an internal problem of the PA or by
insufficient cooling capacity of the rack/shelter.
If this alarm is reported by a booster, the 201034 - Boosters Fan unit failed alarm may
be the root cause for the failure reported by this alarm.
An additional rack/shelter temperature alarm (200995 or 200996) or fan alarms
(200914) may indicate that the air circulation is decreased. A fan unit could be defective
or especially for outdoor shelters obstructed air in- or outlets could also reduce the cooling capability.
As a consequence, the PA was put out of service. Cells and/or calls could potentially be
lost. The states of all affected managed objects change accordingly.
This alarm message may occur in conjunction with temperature alarms:
200914 - Fan unit failed
200995 - High Temperature Limit (Ht3) reached
200996 - Critical Temperature Limit (Ht4) reached

NOTE
If the reporting Node B is of type NB-441/NB-881, the lack of air circulation may be
caused by a polluted membrane filter (MEF). Therefore, if the Node B site is located in
heavily air-polluted environments combined with special temperature conditions, a
maintenance of the MEF filters in the outdoor NB-441/NB-881 might be necessary.
If the MEFs are polluted, the 201029 - MEF blocked or 201035 - MEF completely
blocked alarm is output. Refer to the relevant alarms error description and follow the
troubleshooting.
Troubleshooting
Depending on the actual problem, perform one of the following tasks:
In the event that the following preconditions are met, i.e.
The 200921 - Over temperature of PA alarm is reported by a booster and
The 201034 - Boosters Fan unit failed alarm has been output before,
refer to the error description of the 201034 - Boosters Fan unit failed alarm and follow the troubleshooting accordingly.
The 201034 - Boosters Fan unit failed alarm may indicate the root cause for the failure reported by this alarm.
If this alarm is raised for one single PA only, it is most likely that the PA itself has got
a problem. Replace the relevant PA. Replacement must be done according to the
Maintenance Manual MMN:Node B.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

51

OML:Node B

Outputs
Node B

52

In case of one or more fan alarms or a rack/shelter temperature alarm is reported


the addressed fan unit should be checked and possibly replaced. Replacement must
be done according to the Maintenance Manual MMN:Node B.
A rack/shelter temperature alarm lead one to assume that the air circulation is decreased by obstructed air in- or outlets. Check and clean the air in- and outlets according to the section Cleaning of Air In- and Outlets in the Maintenance Manual
MMN:Node B.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

200922 - RF performance not being met due to bad linearization


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Lpa, Booster, Cat, Rrh


equipmentAlarm
SignalQualityEvaluationFault
major

Error Description
The PA linearization technics does not work correctly and could result in signal quality
not being met. The PA is switched off. The PA was, furthermore, put out of service.
As a consequence, cells or calls could potentially be lost. The states of all affected managed objects change accordingly.
Troubleshooting
The addressed card has to be replaced. Replacement must be done according to the
Maintenance Manual MMN:Node B.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

53

OML:Node B

Outputs
Node B

200923 - Internal failure of PA detected


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Lpa, Booster, Cat, Rrh


equipmentAlarm
EquipmentFailure
major

Error Description
A fatal vendor specific hardware or software failure inside the PA was detected and the
PA was switched off. Furthermore, the PA was put out of service.
The card should be replaced.
Cells or calls could potentially be lost. The states of all affected managed objects
change accordingly.
Troubleshooting
1. First, reset the addressed card. Use the TREE View window of the LMT or, alternatively, apply the rst command to the addressed card.
2. If the fault cannot be cleared by reset, the addressed card has to be replaced. Replacement must be done according to the Maintenance Manual MMN:Node B.

54

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

200924 - Input power level of LPA too high but LPA can still
hold its RF specification
Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Lpa
equipmentAlarm
ExcessiveTransmitterOutputPower
minor

Error Description
The LPA detected an input power level from a TRX card that is above the nominal value.
However, the specifications relating to the RF output are still met. There is no imminent
danger for the LPA to be damaged.
A further power level increase will result in the error report 200925 - Input power level of
PA too high with the higher severity level major and a shutdown of the LPA is inevitable.
Troubleshooting
First, check the cables connections.
The connected TRX card should be monitored for a high output level and if the output
power increases further, the error 200925 - Input power level of PA too high will occur
and the LPA will be switched off.
Precautionary the TRX card should be replaced. Replacement must be done according
to the Maintenance Manual MMN:Node B.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

55

OML:Node B

Outputs
Node B

200925 - Input power level of PA too high


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Lpa, Booster, Cat, Rrh


equipmentAlarm
ExcessiveTransmitterOutputPower
major

Error Description
The PA detected an input power level that would cause the PA to fail specifications relating to the RF output or damaging the PA. According to the following cases, the input
power level may be either analog or digital:
Case 1: This alarm occurred in an LPA, receiving its input power from a TRX card.
Thus, the analog input power level is too high.
Case 2: This alarm occurred in a CAT/RRH, receiving its input power from DRIC.
The following causes may be the root for this failure:
The digital input power level has been too high for a certain period of time. In this
case, an autonomous gain correction was not possible.
Too rapid digital input signal variations could not be processed adequately.
The CAT/RRH itself produces too much power.
To avoid this the PA is switched off. As a consequence, cells or calls could potentially
be lost. The states of all affected managed objects change accordingly.
It may be that the error reports 200924 - Input power level of LPA too high but LPA can
still hold its RF specification if LPA is concerned, or 201018 - The LRU could not process
a message from CC if CAT/RRH is concerned, were emitted before, being a sign of increasing power level input at the PA.
Troubleshooting
1. First, check the cables connections.
2. The related card has to be replaced. Replacement must be done according to the
Maintenance Manual MMN:Node B.

56

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

200926 - CPU failure of baseband card


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Ch, Rep, Trx, Dric


equipmentAlarm
ProcessorProblem
major (final), handled according to the
Fault Escalation Strategy

Error Description
A fatal software or hardware error arose: a boot or watchdog error of a CPU occurred.
After an unsuccessful automatic recovery by means of a reset, the reporting BB card
was put out of service.
As a consequence, cells or calls could potentially be lost. The states of all affected managed objects change accordingly.
Troubleshooting
1. First, reset the addressed card again. Use the TREE View window of the LMT or,
alternatively, apply the rst command to the addressed card.
2. If the fault cannot be cleared by reset, the addressed card has to be replaced. Replacement must be done according to the Maintenance Manual MMN:Node B.
3. Furthermore, contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save the error symptoms as described
in "Collect Info for Assistance". Log files need to be analyzed and specific measures
must be taken which are out of the operators scope.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

57

OML:Node B

Outputs
Node B

200927 - Volatile memory failure of baseband card


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Ch, Rep, Trx, Dric


equipmentAlarm
EquipmentMalfunction
major (final), handled according to the
Fault Escalation Strategy

Error Description
A failure of an SDRAM (synchronous dynamic random access memory) was detected.
After an unsuccessful automatic recovery by means of a reset, the reporting BB card
was put out of service.
As a consequence, cells or calls could potentially be lost. The states of all affected managed objects change accordingly.
Troubleshooting
1. First, reset the addressed card. Use the TREE View window of the LMT or, alternatively, apply the rst command to the addressed card.
2. If the fault cannot be cleared by reset, the addressed card has to be replaced. Replacement must be done according to the Maintenance Manual MMN:Node B.

58

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

200928 - Non-volatile memory failure of baseband card


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Ch, Rep, Trx, Dric


processingErrorAlarm
CorruptData
major (final), handled according to the
Fault Escalation Strategy

Error Description
A checksum error was found for a ROM (read only memory).
After an unsuccessful automatic recovery by means of a reset, the reporting BB card
was put of service.
As a consequence, cells or calls could potentially be lost. The states of all affected managed objects change accordingly.
Troubleshooting
1. First, reset the addressed card. Use the TREE View window of the LMT or, alternatively, apply the rst command to the addressed card.
2. If the fault cannot be cleared by reset, the addressed card has to be replaced. Replacement must be done according to the Maintenance Manual MMN:Node B.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

59

OML:Node B

Outputs
Node B

200929 - DSP failure


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Ch, Rep, Trx, Dric


equipmentAlarm
ProcessorProblem
major (final), handled according to the
Fault Escalation Strategy

Error Description
A boot or watchdog error of a UTOPIA relevant DSP (digital signal processor) occurred.
After an unsuccessful automatic recovery by means of a reset, the reporting BB card
was put out of service.
As a consequence, cells or calls could potentially be lost. The states of all affected managed objects change accordingly.
Troubleshooting
1. First, reset the addressed card. Use the TREE View window of the LMT or, alternatively, apply the rst command to the addressed card.
2. If the fault cannot be cleared by reset, the addressed card has to be replaced. Replacement must be done according to the Maintenance Manual MMN:Node B.

60

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

200931 - FPGA failure


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Ch, Rep, Trx, Dric


equipmentAlarm
EquipmentMalfunction
major (final), handled according to the
Fault Escalation Strategy

Error Description
A configuration failure of an FPGA (field programmable gate array) was detected.
After an unsuccessful automatic recovery by means of a reset, the reporting BB card
was put out of service.
As a consequence, cells or calls could potentially be lost. The states of all affected managed objects change accordingly.
Troubleshooting
1. First, reset the addressed card. Use the TREE View window of the LMT or, alternatively, apply the rst command to the addressed card.
2. If the fault cannot be cleared by reset, the addressed card has to be replaced. Replacement must be done according to the Maintenance Manual MMN:Node B.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

61

OML:Node B

Outputs
Node B

200932 - Control FPGA failure


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Ch, Rep, Trx, Dric


equipmentAlarm
EquipmentMalfunction
major (final), handled according to the
Fault Escalation Strategy

Error Description
A control FPGA (field programmable gate array) failure occurred.
After an unsuccessful automatic recovery by means of a reset, the reporting BB card
was put out of service.
As a consequence, cells or calls could potentially be lost. The states of all affected managed objects change accordingly.
Troubleshooting
1. First, reset the addressed card. Use the TREE View window of the LMT or, alternatively, apply the rst command to the addressed card.
2. If the fault cannot be cleared by reset, the addressed card has to be replaced. Replacement must be done according to the Maintenance Manual MMN:Node B.

62

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

200933 - External timing signal failure


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Ch, Rep, Trx, Dric


equipmentAlarm
EquipmentMalfunction
major (final), handled according to the
Fault Escalation Strategy

Error Description
For synchronizing the baseband cards (CH, REP, TRX, DRIC) the Core Controller (CC)
sends timing signals via the UTOPIA bus and clock busses. These timing signals derive
from the master clock generator of the Core Controller.
If only one baseband card sends the alarm message: There is a hardware failure in
the baseband card. The Node B is degraded in its performance.
If several baseband cards send the alarm message: There is a failure in the Core
Controller. The uplink and downlink connections of the Node B are affected. All affected cells are lost.
After an unsuccessful automatic recovery by means of a reset, the reporting BB card
was put out of service.
As a consequence, cells or calls could potentially be lost. The states of all affected managed objects change accordingly.
Troubleshooting
1. Contact the technical assistance center (TAC) to get support in isolating the fault.
For suitable preparation save the error symptoms as described in "Collect Info for
Assistance". Log files need to be analyzed and specific measures must be taken
which are out of the operators scope.
2. Reset the addressed card. Use the TREE View window of the LMT or, alternatively,
apply the rst command to the addressed card.
3. If only one baseband card sends the alarm message and the fault cannot be cleared
by reset, replace this baseband card. Replacement must be done according to the
Maintenance Manual MMN:Node B.
4. If several baseband cards send the alarm message and the fault cannot be cleared
by reset, replace the CC. Replacement must be done according to the Maintenance
Manual MMN:Node B.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

63

OML:Node B

Outputs
Node B

200934 - Failure of the RF part of the TRX


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Trx
equipmentAlarm
EquipmentMalfunction
major (final), handled according to the
Fault Escalation Strategy

Error Description
There is a hardware failure in the TRX card. Within the TRX card, the radio frequency
block (RF) handles the downlink signals. If there is a failure in the RF part, the TRX card
does not transmit downlink signals any longer.
After an unsuccessful automatic recovery by means of a reset, the reporting TRX card
was put out of service.
As a consequence, cells or calls could potentially be lost. The states of all affected managed objects change accordingly.
Troubleshooting
1. First, reset the addressed TRX card. Use the TREE View window of the LMT or, alternatively, apply the rst command to it.
2. The TRX card can be blocked locally. The card or carrier can also be blocked from
the LMT. Make sure that the card is not blocked, i.e., confirm that the administrative
state of the relevant TRX card is set to unlocked. Use either the TREE View window
or the RACK View window of the LMT. Alternatively, apply the Set AdministrativeState Unlocked command to the reporting TRX.
3. If the fault cannot be cleared by reset, the addressed card has to be replaced. Replacement must be done according to the Maintenance Manual MMN:Node B.

64

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

200935 - LVDS Failure


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Ch, Rep, Trx, Dric


communicationAlarm
RemoteNodeTransmissionError
major (final), handled according to the
Fault Escalation Strategy

Error Description
The LVDS (low voltage differential signal) is an internal connection between the baseband cards. This alarm message occurs if the communication between the baseband
cards is disconnected. The card which sends the alarm message is probably not the defective card.
After an unsuccessful automatic recovery by means of a reset, the reporting BB card
was put out of service.
As a consequence, cells or calls could potentially be lost. The states of all affected managed objects change accordingly.
This alarm message may occur in conjunction with the 200933 - External timing signal
failure.
Troubleshooting
1. First, reset the addressed card. Use the TREE View window of the LMT or, alternatively, apply the rst command to the addressed card.
2. Check the function of CH, TRX and REP cards. The addressed card is probably not
the defective card. So check accurately which card is defective.
3. Replace the defective card. Replacement must be done according to the Maintenance Manual MMN:Node B.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

65

OML:Node B

Outputs
Node B

200936 - Local bus failure around the CPU


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Ch, Rep, Trx, Dric


communicationAlarm
RemoteNodeTransmissionError
major (final), handled according to the
Fault Escalation Strategy

Error Description
Local bus failure around the CPU.
After an unsuccessful automatic recovery by means of a reset, the reporting BB card
was put out of service.
As a consequence, cells or calls could potentially be lost. The states of all affected managed objects change accordingly.
Troubleshooting
1. First, reset the addressed card. Use the TREE View window of the LMT or, alternatively, apply the rst command to the addressed card.
2. If the fault cannot be cleared by reset, the addressed card has to be replaced. Replacement must be done according to the Maintenance Manual MMN:Node B.

66

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

200937 - FTP connection failure


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Ch, Rep, Trx, Dric, Cat, Rrh


communicationAlarm
TransmissionError
major (final), handled according to the
Fault Escalation Strategy

Error Description
FTP (file transfer protocol) connection between CC card (Core Controller) and BB card
(baseband) or CAT (combined amplifier and transceiver) or RRH (remote radio head)
could not be established.
After an unsuccessful automatic recovery by means of a reset, the reporting LRU was
put out of service.
As a consequence, cells or calls could potentially be lost. The states of all affected managed objects change accordingly.
The error should be reported to customer services. The root of the problem may be a
hardware or software error.
Troubleshooting
1. First, reset the addressed card. Use the TREE View window of the LMT or, alternatively, apply the rst command to the addressed card.
2. If the fault cannot be cleared by reset, the addressed card has to be replaced. Replacement must be done according to the Maintenance Manual MMN:Node B.
3. Furthermore, contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save the error symptoms as described
in "Collect Info for Assistance". Log files need to be analyzed and specific measures
must be taken which are out of the operators scope.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

67

OML:Node B

Outputs
Node B

200938 - SWI CRC check failed


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Ch, Rep, Trx, Dric


processingErrorAlarm
FileError
major (final), handled according to the
Fault Escalation Strategy

Error Description
A CRC (cyclic redundancy check) error has been detected while checking the SWI (software image). This alarm message may occur if a new SW load is activated, which, however, is defective. If no new SW load has been activated, there is an error in the
software.
After an unsuccessful automatic recovery by means of a reset, the reporting BB card
was put out of service. As a consequence, cells and/or calls could potentially be lost.
The states of all affected managed objects change accordingly.
Troubleshooting
Contact the technical assistance center (TAC) to get support in isolating the fault. For
suitable preparation save the error symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are
out of the operators scope.

68

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

200939 - Static configuration file CRC check failed


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Ch, Rep, Trx, Dric


processingErrorAlarm
FileError
major (final), handled according to the
Fault Escalation Strategy

Error Description
A CRC (cyclic redundancy check) error has been detected while checking the static configuration file. This alarm message may occur if a new SW load is activated, which, however, is defective. If no new SW load has been activated, there is an error in the
software.
After an unsuccessful automatic recovery by means of a reset, the reporting BB card
was put out of service. As a consequence, cells or calls could potentially be lost. The
states of all affected managed objects change accordingly.
Troubleshooting
Contact the technical assistance center (TAC) to get support in isolating the fault. For
suitable preparation save the error symptoms as described in "Collect Info for Assistance". Special actions must be taken and log files need to be analyzed which are out
of the operators scope.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

69

OML:Node B

Outputs
Node B

200940 - SW activation failed


Failure Event Report
Managed Object Class / Hardware Type: Ch, Rep, Trx, Dric
Event Type:
processingErrorAlarm
Probable Cause:
SoftwareProgramAbnormallyTerminated
Severity:
major (final), handled according to the
Fault Escalation Strategy
Error Description
The SW version specified in the SW activation command could not be activated.
After an unsuccessful automatic recovery by means of a reset, the reporting BB card
was put out of service.
As a consequence, cells or calls could potentially be lost. The states of all affected managed objects change accordingly.
Troubleshooting
1. Report this error to the technical assistance center (TAC). For suitable preparation
save the error symptoms as described in "Collect Info for Assistance". Special actions must be taken and log files need to be analyzed which are out of the operators
scope.
2. Reset the addressed card. Use the TREE View window of the LMT or, alternatively,
apply the rst command to the addressed card.
3. If the fault cannot be cleared by reset, the addressed card has to be replaced. Replacement must be done according to the Maintenance Manual MMN:Node B.

70

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

200941 - Internal clock failure


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Ch, Rep, Trx, Dric


equipmentAlarm
TimingProblem
major (final), handled according to the
Fault Escalation Strategy

Error Description
A failure of the internal clock occurred.
After an unsuccessful automatic recovery by means of a reset, the reporting BB card
was put out of service.
As a consequence, cells or calls could potentially be lost. The states of all affected managed objects change accordingly.
Troubleshooting
1. First, reset the addressed card. Use the TREE View window of the LMT or, alternatively, apply the rst command to the addressed card.
2. If the fault cannot be cleared by reset, the addressed card has to be replaced. Replacement must be done according to the Maintenance Manual MMN:Node B.
3. Furthermore, contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save the error symptoms as described
in "Collect Info for Assistance". Log files need to be analyzed and specific measures
must be taken which are out of the operators scope.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

71

OML:Node B

Outputs
Node B

200942 - Configuration file inconsistent


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Ch, Rep, Trx, Dric, Cat, Rrh


processingErrorAlarm
FileError
major (final), handled according to the
Fault Escalation Strategy

Error Description
A configuration file contains inconsistent data.
After an unsuccessful automatic recovery by means of a reset, the reporting LRU was
put out of service.
As a consequence, cells or calls could potentially be lost. The states of all affected managed objects change accordingly.
Troubleshooting
1. Report this error to the technical assistance center (TAC). For suitable preparation
save the error symptoms as described in "Collect Info for Assistance". Special actions must be taken and log files need to be analyzed which are out of the operators
scope.
2. First, reset the addressed card. Use the TREE View window of the LMT or, alternatively, apply the rst command to the addressed card.
3. If the fault cannot be cleared by reset, the addressed card has to be replaced. Replacement must be done according to the Maintenance Manual MMN:Node B.

72

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

200943 - IOR file inconsistent


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Ch, Rep, Trx, Dric, Cat, Rrh


processingErrorAlarm
FileError
major (final), handled according to the
Fault Escalation Strategy

Error Description
A fatal software error has occurred. The IOR (interoperable object reference) configuration file contains inconsistent data.
After an unsuccessful automatic recovery by means of a reset, the reporting LRU was
put out of service.
As a consequence, cells or calls could potentially be lost. The states of all affected managed objects change accordingly.
Troubleshooting
1. First, reset the addressed card. Use the TREE View window of the LMT or, alternatively, apply the rst command to the addressed card.
2. If the fault cannot be cleared by reset, the addressed card has to be replaced. Replacement must be done according to the Maintenance Manual MMN:Node B.
3. Report this error to the technical assistance center (TAC). For suitable preparation
save the error symptoms as described in "Collect Info for Assistance". Special actions must be taken and log files need to be analyzed which are out of the operators
scope.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

73

OML:Node B

Outputs
Node B

200944 - FTP put failed


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Ch, Rep, Trx, Dric


communicationAlarm
TransmissionError
warning (final), handled according to
the Fault Escalation Strategy

Error Description
A failure occurred while trying to put an FTP (file transfer protocol) file to the CC card
(Core Controller). The addressed LRU is reset.
The error should be reported to customer services.
As a consequence of this failure, cells or calls could potentially be lost. The states of all
affected managed objects furthermore change accordingly.
Troubleshooting
1. First, reset the addressed card. Use the TREE View window of the LMT or, alternatively, apply the rst command to the addressed card.
2. If the fault cannot be cleared by reset, the addressed card has to be replaced. Replacement must be done according to the Maintenance Manual MMN:Node B.
3. Report this error to the technical assistance center (TAC). For suitable preparation
save the error symptoms as described in "Collect Info for Assistance". Special actions must be taken and log files need to be analyzed which are out of the operators
scope.

74

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

200945 - FTP manage failure


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Ch, Rep, Trx, Dric


processingErrorAlarm
CorruptData
warning (final), handled according to
the Fault Escalation Strategy

Error Description
A failure occurred in managing the RAM (random access memory) disc via FTP. The
addressed LRU is reset.
The error should be reported to customer services.
As a consequence of this failure, cells or calls could potentially be lost. The states of all
affected managed objects change accordingly.
Troubleshooting
1. First, reset the addressed card. Use the TREE View window of the LMT or, alternatively, apply the rst command to the addressed card.
2. If the fault cannot be cleared by reset, the addressed card has to be replaced. Replacement must be done according to the Maintenance Manual MMN:Node B.
3. Report this error to the technical assistance center (TAC). For suitable preparation
save the error symptoms as described in "Collect Info for Assistance". Special actions must be taken and log files need to be analyzed which are out of the operators
scope.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

75

OML:Node B

Outputs
Node B

200946 - Still alive supervision failure


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Ch, Rep, Trx, Dric, Cat, Rrh


equipmentAlarm
EquipmentMalfunction
major (final), handled according to the
Fault Escalation Strategy

Error Description
A still alive supervision failure occurred. It is possible that a hardware or software error
is the root of the problem.
After an unsuccessful automatic recovery by means of a reset, the reporting LRU was
put out of service.
As a consequence, cells or calls could potentially be lost. The states of all affected managed objects change accordingly.
Troubleshooting
1. First, reset the addressed card. Use the TREE View window of the LMT or, alternatively, apply the rst command to the addressed card.
2. If the fault cannot be cleared by reset, the addressed card has to be replaced. Replacement must be done according to the Maintenance Manual MMN:Node B.
3. Report this error to the technical assistance center (TAC). For suitable preparation
save the error symptoms as described in "Collect Info for Assistance". Special actions must be taken and log files need to be analyzed which are out of the operators
scope.

76

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

200947 - Failure in the DC supply of DUAMCO


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Duamco
equipmentAlarm
PowerSupplyFailure
major

Error Description
The DUAMCO is switched off. As a consequence, the DUAMCO was put out of service.
Furthermore, cells or calls could potentially be lost. The states of all affected managed
objects change accordingly.
Troubleshooting
1. First, reset the addressed card. Use the TREE View window of the LMT or, alternatively, apply the rst command to the addressed card.
2. If the fault cannot be cleared by reset, the addressed card has to be replaced. Replacement must be done according to the Maintenance Manual MMN:Node B.

WARNING
When replacing antenna cables, antennas, TMAs or DUAMCOs switch off the relevant
breakers which supply the LPAs involved in the affected antenna branch in order to prevent an uncontrolled emission of microwave radiation.

NOTE
Before replacing the DUAMCO, set the DIP-switches on the front side of the DUAMCO
in the same configuration as it was on the replaced DUAMCO.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

77

OML:Node B

Outputs
Node B

200948 - CORBA communication failed


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Ch, Rep, Trx, Dric, Cat, Rrh


communicationAlarm
TransmissionError
major (final), handled according to the
Fault Escalation Strategy

Error Description
This alarm message is output due to the following fatal error: a CORBA (common object
request broker architecture) communication failure between CC and the reporting LRU
occurred. It is possible that a hardware or a software error is the root of the problem.
After an unsuccessful automatic recovery by means of a reset, the reporting LRU was
put out of service.
As a consequence, cells or calls could potentially be lost. The states of all affected managed objects change accordingly.
Troubleshooting
1. First, reset the addressed card. Use the TREE View window of the LMT or, alternatively, apply the rst command to the addressed card.
2. If the fault cannot be cleared by reset, the addressed card has to be replaced. Replacement must be done according to the Maintenance Manual MMN:Node B.
3. If the fault cannot be cleared by reset, contact the technical assistance center (TAC)
to get support in isolating the fault. For suitable preparation save the error symptoms
as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are out of the operators scope.

78

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

200949 - Internal CORBA call failed


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Cc
communicationAlarm
TransmissionError
warning

Error Description
A fatal software error has occurred! This is a recoverable error situation caused by a potentially serious software fault which should be reported to customer services! The recovery will result in a complete reset of the Node B. Due to the reset, all services will be
interrupted.
This means:
All cells will be lost.
The connection between the Node B and the RNC will be lost.
Uplink or downlink errors will be reported by other Node Bs if they are connected to
the resetting Node B.
All connections to the management system will also be interrupted during this reset period. Once the reset is completed, normal operational service should be resumed i.e. the
cells are built up again, connection with the RNC will be re-established, and any cross
connections will be built up again. Any calls that were in operation before the reset are
lost.
Troubleshooting
Contact the technical assistance center (TAC) to get support in isolating the fault. For
suitable preparation save the error symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are
out of the operators scope.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

79

OML:Node B

Outputs
Node B

200950 - Timeout for request or modification


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

*
processingErrorAlarm
TimeoutExpired
major (final), handled according to the
Fault Escalation Strategy

Error Description
A fatal hardware error has occurred. The card did not send an expected response or notification.
After an unsuccessful automatic recovery by means of a reset, the reporting LRU was
put out of service.
As a consequence, cells or calls could potentially be lost. The states of all affected managed objects change accordingly.
Troubleshooting
1. First, reset the addressed card.
2. If the fault cannot be cleared by reset, the addressed card has to be replaced. Replacement must be done according to the Maintenance Manual MMN:Node B.
3. Contact the technical assistance center (TAC) to get support in isolating the fault.
For suitable preparation save the error symptoms as described in "Collect Info for
Assistance". Log files need to be analyzed and specific measures must be taken
which are out of the operators scope.

80

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

200951 - Status notification undefined


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

*
processingErrorAlarm
CorruptData
major (final), handled according to the
Fault Escalation Strategy

Error Description
A fatal hardware error has occurred. The card sends an unknown status notification.
After an unsuccessful automatic recovery by means of a reset, the reporting LRU was
put out of service.
As a consequence, cells or calls could potentially be lost. The states of all affected managed objects change accordingly.
Troubleshooting
1. First, reset the addressed card.
2. If the fault cannot be cleared by reset, contact the technical assistance center (TAC)
to get support in isolating the fault. For suitable preparation save the error symptoms
as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are out of the operators scope.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

81

OML:Node B

Outputs
Node B

200952 - Maximum number of resets exceeded


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

*
equipmentAlarm
EquipmentMalfunction
major

Error Description
A fatal hardware error or software error occurred. The card was not able to start up completely even after performing several numbers of resets.
The reporting LRU was put out of service.
As a consequence, cells or calls could potentially be lost. The states of all affected managed objects change accordingly.
Troubleshooting
1. First, reset the addressed card.
2. If the fault cannot be cleared by reset, the addressed card has to be replaced. Replacement must be done according to the Maintenance Manual MMN:Node B.
3. If the fault cannot be cleared by card replacement, contact the technical assistance
center (TAC) to get support in isolating the fault. For suitable preparation save the
error symptoms as described in "Collect Info for Assistance". Log files need to be
analyzed and specific measures must be taken which are out of the operators
scope.

82

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

200953 - CAN bus off


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

*
equipmentAlarm
ProcessorProblem
warning

Error Description
There is an error detected in the physical CAN communication layer. Service may thus
be affected.
This alarm message may occur in conjunction with other CAN-related alarms:
200954 - No message response on CAN
200955 - Mount supervision failure
200956 - Watch dog timer expired
200957 - Internal CAN processing failure
Troubleshooting
1. First, reset the addressed card.
2. If the fault cannot be cleared by reset, the addressed card has to be replaced. Replacement must be done according to the Maintenance Manual MMN:Node B.
3. If the card replacement did not clear the fault, contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save the error
symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are out of the operators scope.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

83

OML:Node B

Outputs
Node B

200954 - No message response on CAN


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

*
processingErrorAlarm
TimeoutExpired
major (final), handled according to the
Fault Escalation Strategy

Error Description
The watchdog timer on the CAN bus is expired. An object on the affected CAN bus
therefore performed a reset.
After an unsuccessful automatic recovery by means of a reset, the reporting LRU was
put out of service.
As a consequence, cells or calls could potentially be lost. The states of all affected managed objects change accordingly.
This alarm message may occur in conjunction with other CAN-related alarms:
200953 - CAN bus off
200955 - Mount supervision failure
200956 - Watch dog timer expired
200957 - Internal CAN processing failure
Troubleshooting
1. First, reset the addressed card.
2. If the fault cannot be cleared by reset, the addressed card has to be replaced. Replacement must be done according to the Maintenance Manual MMN:Node B.
3. If the card replacement did not clear the fault, contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save the error
symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are out of the operators scope.

84

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

200955 - Mount supervision failure


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

*
processingErrorAlarm
TimeoutExpired
major (final), handled according to the
Fault Escalation Strategy

Error Description
A CAN object performed a reset caused by expiration of the mount supervision timer.
After an unsuccessful automatic recovery by means of a reset, the reporting LRU was
put out of service.
As a consequence, cells or calls could potentially be lost. The states of all affected managed objects change accordingly.
This alarm message may occur in conjunction with other CAN-related alarms:
200953 - CAN bus off
200954 - No message response on CAN
200956 - Watch dog timer expired
200957 - Internal CAN processing failure
Troubleshooting
1. First, reset the addressed card.
2. If the fault cannot be cleared by reset, the addressed card has to be replaced. Replacement must be done according to the Maintenance Manual MMN:Node B.
3. If the card replacement did not clear the fault, contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save the error
symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are out of the operators scope.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

85

OML:Node B

Outputs
Node B

200956 - Watch dog timer expired


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

*
processingErrorAlarm
WatchDogTimerExpired
major (final), handled according to the
Fault Escalation Strategy

Error Description
The watch dog timer on CAN bus expired.
If the reporting managed object is a CAT (combined amplifier and transceiver) or a RRH
(remote radio head), the following applies: The CATs/RRHs CPU (central processing
unit) watchdog detected a CPU failure.
After an unsuccessful automatic recovery by means of a reset, the reporting LRU was
put out of service.
As a consequence, cells or calls could potentially be lost. The states of all affected managed objects change accordingly.
This alarm message may occur in conjunction with other CAN-related alarms:
200953 - CAN bus off
200954 - No message response on CAN
200955 - Mount supervision failure
200957 - Internal CAN processing failure
Troubleshooting
1. First, reset the addressed card.
2. If the fault cannot be cleared by reset, the addressed card has to be replaced. Replacement must be done according to the Maintenance Manual MMN:Node B.
3. If the card replacement did not clear the fault, contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save the error
symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are out of the operators scope.

86

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

200957 - Internal CAN processing failure


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

*
equipmentAlarm
EquipmentMalfunction
major (final), handled according to the
Fault Escalation Strategy

Error Description
A CAN object performed a reset caused by an internal processing failure.
After an unsuccessful automatic recovery by means of a reset, the reporting LRU was
put out of service.
As a consequence, cells or calls could potentially be lost. The states of all affected managed objects change accordingly.
This alarm message may occur in conjunction with other CAN-related alarms:
200953 - CAN bus off
200954 - No message response on CAN
200955 - Mount supervision failure
200956 - Watch dog timer expired
Troubleshooting
1. First, reset the addressed card.
2. If the fault cannot be cleared by reset, the addressed card has to be replaced. Replacement must be done according to the Maintenance Manual MMN:Node B.
3. If the card replacement did not clear the fault, contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save the error
symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are out of the operators scope.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

87

OML:Node B

Outputs
Node B

200958 - Timer for the reset supervision expired


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

*
equipmentAlarm
TimingProblem
major (final), handled according to the
Fault Escalation Strategy

Error Description
The timer for the reset supervision has been expired.
After an unsuccessful automatic recovery by means of a reset, the reporting LRU was
put out of service.
As a consequence, cells or calls could potentially be lost. The states of all affected managed objects change accordingly.
Troubleshooting
1. First, reset the addressed card.
2. If the fault cannot be cleared by reset, contact the technical assistance center (TAC)
to get support in isolating the fault. For suitable preparation save the error symptoms
as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are out of the operators scope.

88

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

200959 - Missing response from baseband card


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Ch, Rep, Trx, Dric


processingErrorAlarm
TimeoutExpired
major (final), handled according to the
Fault Escalation Strategy

Error Description
The following fatal error has occurred: NBAP (Node B application part) has detected a
missing response from a baseband card. It is possible that a hardware or software error
is the root of the problem.
After an unsuccessful automatic recovery by means of a reset, the reporting BB card
was put out of service.
As a consequence, cells or calls could potentially be lost. The states of all affected managed objects change accordingly.
The error should be reported to customer service.
Troubleshooting
1. First, reset the addressed card. Use the TREE View window of the LMT or, alternatively, apply the rst command to the addressed card.
2. If the fault cannot be cleared by reset, the addressed card has to be replaced. Replacement must be done according to the Maintenance Manual MMN:Node B.
3. If the card replacement did not clear the fault, contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save the error
symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are out of the operators scope.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

89

OML:Node B

Outputs
Node B

200960 - Invalid response from baseband card


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Ch, Rep, Trx, Dric


communicationAlarm
InvalidMessageReceived
major (final), handled according to the
Fault Escalation Strategy

Error Description
The following fatal software error has occurred: NBAP (Node B application part) has detected an invalid response from a baseband card. It is possible that a hardware or software error is the root of the problem.
After an unsuccessful automatic recovery by means of a reset, the reporting BB card
was put out of service.
As a consequence, cells or calls could potentially be lost. The states of all affected managed objects change accordingly.
The error should be reported to customer service.
Troubleshooting
1. First, reset the addressed card. Use the TREE View window of the LMT or, alternatively, apply the rst command to the addressed card.
2. If the fault cannot be cleared by reset, the addressed card has to be replaced. Replacement must be done according to the Maintenance Manual MMN:Node B.
3. If the card replacement did not clear the fault, contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save the error
symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are out of the operators scope.

90

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

200961 - Firmware download failure


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

*
processingErrorAlarm
SoftwareDownloadFailure
major

Error Description
A fatal hardware error was detected while downloading the FW (firmware) or no FW is
available at all at the card.
The reporting LRU was put out of service.
As a consequence, cells or calls could potentially be lost. The states of all affected managed objects change accordingly.
Troubleshooting
1. First, reset the addressed card.
2. If the fault cannot be cleared by reset, the addressed card has to be replaced. Replacement must be done according to the Maintenance Manual MMN:Node B.
3. If the card replacement did not clear the fault, contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save the error
symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are out of the operators scope.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

91

OML:Node B

Outputs
Node B

200980 - Invalid MO
Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Perceived severity:

*
processingErrorAlarm
DatabaseInconsistency
warning

Error Description
An object was accessed at the CAN bus which does not exist or which is not mounted.
There may be following causes:
The Node B database is defective. A new database was installed but does not match
the hardware configuration.
The hardware configuration is invalid. A new hardware equipment was installed but
does not match the database.
A software error has occurred.
Troubleshooting
Perform the following tasks in the given order to solve this alarm:
1. Check if the Node B works with the newest version of the database. Use the mibCheck or mibCheckWin tool delivered with the Node Bs software. Proceed according to the OGL:Node B DB Editing Guide.
2. If necessary, change the running database. Edit the database according to the
OGL:Node B DB Editing Guide.
3. Otherwise, if the database was not defective, check the hardware configuration.
Check the entry in the database and check the addressed MO on site. There might
have been a change of the MO type on site or in the configuration, which was not
edited in the database.
4. If the error is not caused by an invalid database or an unsuitable hardware configuration, contact the technical assistance center (TAC) to get support in isolating the
fault. For suitable preparation save the error symptoms as described in "Collect Info
for Assistance". Log files need to be analyzed and specific measures must be taken
which are out of the operators scope.

92

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

200981 - MO not mounted


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

*
communicationAlarm
Unavailable
warning

Error Description
The specified MO is not mounted.
Troubleshooting
Check if the addressed card is equipped. If not, insert a card of the required type, HW
and FW state. Proceed according to the Installation Manual of the reporting Node B
type:
For NB-440 or NB-880, refer to the IMN:NB-440/NB-880.
For NB-441 or NB-881, refer to the IMN:NB-441/NB-881.
For NB-420 or NB-860, refer to the IMN:NB-420/NB-860.
For NB-580, refer to the IMN:NB-580.
For NB-341, refer to the IMN:NB-341.
For Radio Server, refer to the IMN:RS.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

93

OML:Node B

Outputs
Node B

200982 - Invalid command


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

*
processingErrorAlarm
CorruptData
warning

Error Description
A CAN command is invalid.
This alarm may be caused by one of the following:
The Node B database is defective. A new database was installed but does not match
the hardware configuration.
The hardware configuration is invalid. A new hardware equipment was installed but
does not match the database.
A software error has occurred.
Troubleshooting
Perform the following tasks in the given order to solve this alarm:
1. Check the Node B database and software version. Use the mibCheck or mibCheckWin tool delivered with the Node Bs software. Proceed according to the
OGL:Node B DB Editing Guide.
2. If necessary, change the running database. Edit the database according to the
OGL:Node B DB Editing Guide.
3. Otherwise, if the database was not defective, check the hardware configuration.
Check the entry in the database and check the addressed MO on site. There might
have been a change of the MO type on site or in the configuration, which was not
edited in the database.
4. If the error is not caused by an invalid database or an unsuitable hardware configuration: Contact the technical assistance center (TAC) to get support in isolating the
fault. For suitable preparation save the error symptoms as described in "Collect Info
for Assistance". Log files need to be analyzed and specific measures must be taken
which are out of the operators scope.

94

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

200983 - Invalid parameter in command


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

*
processingErrorAlarm
InvalidParameter
warning

Error Description
A CAN command contains an invalid parameter.
This alarm may be caused by one of the following:
The Node B database is defective. A new database was installed but does not match
the hardware configuration.
The hardware configuration is invalid. A new hardware equipment was installed but
does not match the database.
A software error has occurred.
Troubleshooting
Perform the following tasks in the given order to solve this alarm:
1. Check the Node B database and software version. Use the mibCheck or mibCheckWin tool delivered with the Node Bs software. Proceed according to the
OGL:Node B DB Editing Guide.
2. If necessary, change the running database. Edit the database according to the
OGL:Node B DB Editing Guide.
3. Otherwise, if the database was not defective, check the hardware configuration.
Check the entry in the database and check the addressed MO on site. There might
have been a change of the MO type on site or in the configuration, which was not
edited in the database.
4. If the error is not caused by an invalid database or an unsuitable hardware configuration: Contact the technical assistance center (TAC) to get support in isolating the
fault. For suitable preparation save the error symptoms as described in "Collect Info
for Assistance". Log files need to be analyzed and specific measures must be taken
which are out of the operators scope.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

95

OML:Node B

Outputs
Node B

200984 - FW download access file error


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

*
processingErrorAlarm
SoftwareDownloadFailure
warning

Error Description
FW (firmware) download access file error. The access to the card firmware is not possible. Probably providing a wrong software causes the problem.
Troubleshooting
1. Contact the technical assistance center (TAC) to get support in isolating the fault.
For suitable preparation save the error symptoms as described in "Collect Info for
Assistance". Log files need to be analyzed and specific measures must be taken
which are out of the operators scope.
2. Choose the appropriate FW file for the selected card.
3. Download FW to card. The download has to be done separately for each card. (At a
particular time, FW download is only possible to one card).

96

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

200985 - CAN transaction error


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

*
equipmentAlarm
EquipmentMalfunction
warning

Error Description
A CAN transaction error occurred. The card will be reset after inconsistency of data during communication over CAN, e.g. message time-outs, unexpected responses or errors
while download of the firmware.
As a consequence, cells or calls could potentially be lost. The states of all affected managed objects change accordingly.
Troubleshooting
1. First, reset the addressed card.
2. If the fault cannot be cleared by reset, the addressed card has to be replaced. Replacement must be done according to the Maintenance Manual MMN:Node B.
3. If the card replacement did not clear the fault, contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save the error
symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are out of the operators scope.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

97

OML:Node B

Outputs
Node B

200986 - Temperature out of range in upper direction


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

BaseRack, ServiceRack
environmentalAlarm
HighTemperature
minor

Error Description
The temperature at the temperature sensor wired to the ACTC board is out of range in
upper direction. The temperature is above +87 C (188.6 F).
This error message occurs also, if the sensor is disconnected.

NOTE
If the reporting Node B is of type NB-441/NB-881, the lack of air circulation may be
caused by a polluted membrane filter (MEF). Therefore, if the Node B site is located in
heavily air-polluted environments combined with special temperature conditions, a
maintenance of the MEF filters in the outdoor NB-441/NB-881 might be necessary.
If the MEFs are polluted, the 201029 - MEF blocked or 201035 - MEF completely
blocked alarm is output. Refer to the relevant alarms error description and follow the
troubleshooting.
Troubleshooting
1. This error message may occur in conjunction with a fan failure, such as the 200914
- Fan unit failed alarm. Therefore, check the fan units:
First, use the LMTs TREE View window and apply the Get All Attributes command to all related fan units.
Perform a visual inspection and, if necessary, preventive maintenance tasks on
site (check the air filter, heat exchanger). Both tasks must be done according to
the Maintenance Manual MMN:Node B.
2. Check the sensor connections.

98

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

200987 - Hardware parameter invalid


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

*
processingErrorAlarm
InvalidParameter
warning

Error Description
This alarm indicates that an unknown hardware parameter has been received. The reporting card will be reset after it has delivered an unknown hardware parameter.
Normally, this alarm would have been caused by an incompatible hardware configuration, a defective database, etc.
In this case, however, the Node B software reports an invalid hardware parameter although neither the hardware configuration nor the Node B database are mismatched! In
fact, this is an error in the software which should be reported to customers service.
Due to the reason that this is a software error rather than an incompatibility in the database or hardware configuration, checking or changing the Node Bs database and hardware configuration would not help to solve this alarm.
As a consequence of this failure, cells or calls could potentially be lost. The states of all
affected managed objects change accordingly.
Troubleshooting
Contact the technical assistance center (TAC) to get support in isolating the fault. For
suitable preparation save the error symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are
out of the operators scope.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

99

OML:Node B

Outputs
Node B

200988 - Response unknown


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

*
processingErrorAlarm
MessageNotExpected
warning

Error Description
A non-fatal software error has occurred. An unknown response has been received.
Troubleshooting
1. First, reset the addressed card.
2. If the fault could not be cleared by the reset, replace the addressed card. Replacement must be done according to the Maintenance Manual MMN:Node B.
3. If the fault cannot be cleared by replacement of the card, contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation
save the error symptoms as described in "Collect Info for Assistance". Log files
need to be analyzed and specific measures must be taken which are out of the operators scope.

100

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

200989 - No CORBA proxy available for LRU


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Ch, Rep, Trx, Dric, Cat, Rrh


equipmentAlarm
EquipmentMalfunction
major (final), handled according to the
Fault Escalation Strategy

Error Description
This alarm is output due to the following fatal software error: there is no CORBA (common object request broker architecture) proxy available for the addressed LRU.
After an unsuccessful automatic recovery by means of a reset, the reporting LRU was
put out of service.
As a consequence, cells or calls could potentially be lost. The states of all affected managed objects change accordingly.
Troubleshooting
Perform the following tasks in the given order to solve this error:
1. First, reset the addressed card. Use the TREE View window of the LMT or, alternatively, apply the rst command to the addressed card.
2. If the fault cannot be cleared by reset, the addressed card has to be replaced. Replacement must be done according to the Maintenance Manual MMN:Node B.
3. If the card replacement did not clear the fault, either, contact the technical assistance
center (TAC) to get support in isolating the fault. For suitable preparation save the
error symptoms as described in "Collect Info for Assistance". Log files need to be
analyzed and specific measures must be taken which are out of the operators
scope.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

101

OML:Node B

Outputs
Node B

200990 - No still alive response from LRU


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Ch, Rep, Trx, Dric, Cat, Rrh


equipmentAlarm
EquipmentMalfunction
major (final), handled according to the
Fault Escalation Strategy

Error Description
This alarm message is output due to the following fatal software error: no still alive response from the addressed LRU has been received.
After an unsuccessful automatic recovery by means of a reset, the reporting LRU was
put out of service.
The error should be reported to the customers service.
As a consequence, cells or calls could potentially be lost. The states of all affected managed objects change accordingly.
Troubleshooting
Perform the following tasks in the given order:
1. First, reset the addressed card. Use the TREE View window of the LMT or, alternatively, apply the rst command to the addressed card.
2. If the fault cannot be cleared by reset, the addressed card has to be replaced. Replacement must be done according to the Maintenance Manual MMN:Node B.
3. If the card replacement did not clear the fault, contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save the error
symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are out of the operators scope.

102

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

200991 - Duplex error


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Cc
equipmentAlarm
EquipmentMalfunction
major (final), handled according to the
Fault Escalation Strategy

Error Description
The duplex error occurs in the event of:
Receive logical channel FIFO overrun on duplex.
Loss of signal alarm on duplex.
Loss of cell delineation.
HCS-error on RXD interface on duplex.
Cell delineation state out of sync.
Transmit logical channel FIFO overrun on duplex.
Unable to lock input reference clock on duplex.
Invalid start of cell sequence on utopia input port on duplex.
As a consequence of this failure, service may be affected. Thus, cells or calls could potentially be lost. The states of all affected managed objects change accordingly.
Troubleshooting
Perform the following tasks in the given order:
1. First, reset the addressed card. Use the TREE View window of the LMT or, alternatively, apply the rst command to the addressed card.
2. If the fault cannot be cleared by reset, the addressed card has to be replaced. Replacement must be done according to the Maintenance Manual MMN:Node B.
3. If the card replacement did not clear the fault, contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save the error
symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are out of the operators scope.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

103

OML:Node B

Outputs
Node B

200992 - Software Error


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Cc
processingErrorAlarm
SoftwareError
critical

Error Description
This error occurs in case of:
Flash error
CAN receive or transmit queue overflow
Interrupt queue overflow
As a consequence of this failure, service may be affected. Thus, cells or calls could potentially be lost. The states of all affected managed objects change accordingly.
Troubleshooting
Perform the following tasks in the given order to solve this error:
1. First, reset the addressed card. Use the TREE View window of the LMT or, alternatively, apply the rst command to the addressed card.
2. If the fault cannot be cleared by reset, the addressed card has to be replaced. Replacement must be done according to the Maintenance Manual MMN:Node B.
3. If the card replacement did not clear the fault, contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save the error
symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are out of the operators scope.

104

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

200993 - Unexpected Alarm Status Bit


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Cc
processingErrorAlarm
CorruptData
critical

Error Description
Unexpected CAN status notification occurs in case of:
CRC-8 error for the whole received cell (RXD) on duplex.
Remote defect indication (RDI) received on LVDS (low voltage differential signal) on
duplex.
SRAM, duplex, EEPROM or CAN voltage error.
As a consequence of this failure, service may be affected. Thus, cells or calls could potentially be lost. The states of all affected managed objects change accordingly.
Troubleshooting
Perform the following tasks in the given order to solve this error:
1. First, reset the addressed card. Use the TREE View window of the LMT or, alternatively, apply the rst command to the addressed card.
2. If the fault cannot be cleared by reset, the addressed card has to be replaced. Replacement must be done according to the Maintenance Manual MMN:Node B.
3. If the card replacement did not clear the fault, contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save the error
symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are out of the operators scope.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

105

OML:Node B

Outputs
Node B

200994 - HW Failure
Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Cc
equipmentAlarm
EquipmentFailure
warning

Error Description
This error occurs in case of:
PLL of DC/DC-unit unlocked
Voltage or current out of range
Insufficient or excess temperature on DC/DC-unit
Troubleshooting
Perform the following tasks in the given order to solve this error:
1. First, reset the addressed card. Use the TREE View window of the LMT or, alternatively, apply the rst command to the addressed card.
2. If the fault cannot be cleared by reset, the addressed card has to be replaced. Replacement must be done according to the Maintenance Manual MMN:Node B.
3. If the card replacement did not clear the fault, contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save the error
symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are out of the operators scope.

106

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

200995 - High Temperature Limit (Ht3) reached


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

BaseRack, ServiceRack
environmentalAlarm
HighTemperature
major

Error Description
The Node B rack/shelter internal temperature has reached a high level (Ht3). If the temperature increases further (by 2 C, which is equivalent to 3.6 F) the critical level (Ht4)
will be reached. See also 200996 - Critical Temperature Limit (Ht4) reached. The temperature level depends on the Node B type and is as follows:
NB-441/NB-881: Ht3 = 63 C (125.6 F)
NB-440/NB-880/NB-580: Ht3 = 59 C (138.2 F)
NB-420/NB-860: Ht3 = 61 C (141.8 F)
NB-341: Ht3 = 70 C (158 F)
This alarm message may occur in conjunction with 200920 - High temperature of PA and
200921 - Over temperature of PA.
This alarm is cleared if the temperature decreases to the Ht2 level, which depends also
on the Node B type:
NB-441/NB-881: Ht2 = 52 C (125.6 F)
NB-440/NB-880/NB-580: Ht2 = 47 C (116.6 F)
NB-420/NB-860: Ht2 = 47 C (116.6 F)
NB-341: Ht2 = 65 C (149 F)

NOTE
If the reporting Node B is of type NB-441/NB-881, this alarm may be caused by a polluted membrane filter (MEF). Therefore, if the Node B site is located in heavily air-polluted environments combined with special temperature conditions, a maintenance of the
MEF filters in the outdoor NB-441/NB-881 might be necessary.
If the MEFs are polluted, the 201029 - MEF blocked or 201035 - MEF completely
blocked alarm is output. Refer to the relevant alarms error description and follow the
troubleshooting.
Troubleshooting
First, contact the technical assistance center (TAC) to get support in isolating the fault.
For suitable preparation save the error symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are
out of the operators scope.
Additional fan alarms like 200914 - Fan unit failed may indicate the basic cause.
For indoor Node Bs:
1. Check the fan units.
2. Is the environmental temperature in the specified range?

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

107

OML:Node B

Outputs
Node B

For outdoor Node Bs:


1. Check the fan units.
2. Are the air in- and outlets free from air stream blocking material?
3. Make sure the heater units are not switched on undesignedly.

108

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

200996 - Critical Temperature Limit (Ht4) reached


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

BaseRack, ServiceRack
environmentalAlarm
HighTemperature
major

Error Description
The Node B rack/shelter internal temperature has reached a critical level (Ht4). An immediate operator action is required: Switch off the Node B! Otherwise a severe
hardware damage can occur.
The temperature level depends on the Node B type and is as follows:
NB-441/NB-881: Ht4 = 65 C (149 F)
NB-440/NB-880/NB-580: Ht4 = 61 C (141.8 F)
NB-420/NB-860: Ht4 = 63 C (145.4 F)
NB-341: Ht4 = 72 C (161.6 F)
This alarm message may occur in conjunction with 200920 - High temperature of PA and
200921 - Over temperature of PA.
This alarm is cleared if the temperature decreases to the Ht2 level, which depends also
on the Node B type:
NB-441/NB-881: Ht2 = 52 C (125.6 F)
NB-440/NB-880/NB-580: Ht2 = 47 C (116.6 F)
NB-420/NB-860: Ht2 = 47 C (116.6 F)
NB-341: Ht2 = 65 C (149 F)

NOTE
If the reporting Node B is of type NB-441/NB-881, this alarm may be caused by a polluted membrane filter (MEF). Therefore, if the Node B site is located in heavily air-polluted environments combined with special temperature conditions, a maintenance of the
MEF filters in the outdoor NB-441/NB-881 might be necessary.
If the MEFs are polluted, the 201029 - MEF blocked or 201035 - MEF completely
blocked alarm is output. Refer to the relevant alarms error description and follow the
troubleshooting.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

109

OML:Node B

Outputs
Node B

Troubleshooting

NOTE
An overtemperature scenario in the Node B can lead to a self-disabling of B-shelf cards.
The Node B handles self-disabled cards as if a fatal board failure, such as an on-board
power supply failure, has occurred. In other words, the combination of OST/AVS then
changes to disabled/not installed and the LED of the self-disabled card is off.
Switch off the Node B immediately! Otherwise, a severe hardware damage can occur.
Additional fan alarms like 200914 - Fan unit failed may indicate the basic cause.
For indoor Node Bs:
1. Check the fan units.
2. Is the environmental temperature in the specified range?
For outdoor Node Bs:
1. Check the fan units.
2. Are the air in- and outlets free from air stream blocking material?
3. Make sure the heater units are not switched on undesignedly.

110

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

200997 - Lower Temperature Limit (Ht0) reached


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

BaseRack, ServiceRack
environmentalAlarm
LowTemperature
minor

Error Description
The Node B rack/shelter internal temperature has reached the lower limit (Ht0). Below
this temperature electronic equipment does not work reliably.
The temperature level for all Node B types is:
Ht0 = -5 C (23 F)
This alarm is cleared, if the temperature increases to the Ht1 level, which is Node B dependent:
NB-441/NB-881: Ht1 = 5 C (41 F)
NB-440/NB-880/NB-580: Ht1 = 5 C (41 F)
NB-420/NB-860: Ht1 = 5 C (41 F)
NB-341: Ht1 = 0 C (32 F)
Troubleshooting
Even the Node Bs own power dissipation is not sufficient to keep the rack/shelter internal temperature above the lowest operating limit.
For indoor Node Bs:
Rooms with electronic equipment are usually temperatur- controlled by radiators
and/or air condition systems:
Check radiator for sufficient heating
Check windows, doors etc. for perfect closing (infiltration)
For outdoor Node Bs:
Are heater units installed for keeping the shelter internal temperature above -5C
(23 F) under worst environmental conditions?
Do the heater units work? Check the power supply, proper connection, and ohmic
resistance.
Replace the heater units if identified as defective. Replacement must be done according to the Maintenance Manual MMN:Node B.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

111

OML:Node B

Outputs
Node B

200998 - Temperature out of range in lower direction


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

BaseRack, ServiceRack
environmentalAlarm
LowTemperature
minor

Error Description
The temperature at the temperature sensor wired to the ACT is out of range in lower direction.
The temperature is below:
NB-441/NB-881: -8 C (17.6 F)
NB-440/NB-880/NB-580: -8 C (17.6 F)
NB-420/NB-860: -8 C (17.6 F)
NB-341: -10 C (14 F)
This error message occurs also, if there is a short-circuit in the sensor or in the wires
between sensor and ACT.
Troubleshooting
Even the Node Bs own power dissipation is not sufficient to keep the rack/shelter internal temperature above the lowest operating limit.
For indoor Node Bs:
Rooms with electronic equipment are usually temperature controlled by radiators
and/or air condition systems:
Check radiator for sufficient heating.
Check windows, doors etc. for perfect closing (infiltration).
For outdoor Node Bs:
Are heater units installed for keeping the shelter internal temperature above -5 C
(23 F) under worst environmental conditions?
Do the heater units work? Check the power supply, proper connection, and ohmic
resistance.
Replace the heater units if identified as defective. Replacement must be done according to the Maintenance Manual MMN:Node B.
Check the temperature sensor and the wires to the ACT for a short-circuit if none of
the above reasons were identified.

112

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

200999 - Unexpected loss of unlocked card


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

*
equipmentAlarm
EquipmentFailure
critical

Error Description
The mentioned card was unmounted without being locked before. The unexpected loss
of an unlocked card can be caused by one of the following:
Extracting the card without setting the administrative state (AST) to locked before
Occurrance of a fatal board failure
Self-disabling of the reporting card due to an overtemperature scenario
As a consequence of this scenario, cells or calls could potentially be lost. The states
of all affected managed objects thus change accordingly.
The Node B handles self-disabled cards as if a fatal board failure, such as an
on-board power supply failure, has occurred. In other words, the combination of
OST/AVS changes to disabled/not installed and the LED of the self-disabled card
is off.

NOTE
If the reporting Node B is of type NB-441/NB-881, the self-disabling of the reporting card may be caused by a polluted membrane filter (MEF). Therefore,
if the Node B site is located in heavily air-polluted environments combined
with special temperature conditions, a maintenance of the MEF filters in the
outdoor NB-441/NB-881 might be necessary.
If the MEFs are polluted, the 201029 - MEF blocked or 201035 - MEF completely blocked alarm is output. Refer to the relevant alarms error description
and follow the troubleshooting.

If this fatal board failure occurs, even a CAN communication is not possible anymore.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

113

OML:Node B

Outputs
Node B

Troubleshooting
Depending on the current situation due to which this fault occurred, perform one of the
following procedures to cease this alarm:
If this alarm occurs in combination with the 200914 - Fan unit failed alarm and/or the
200996 - Critical Temperature Limit (Ht4) reached alarm, the probability is very high
that the reporting card disabled itself due to an overtemperature scenario. Further
repair actions must be done according to the Maintenance Manual MMN:Node B.
If the card was plugged out by mistake, just install the card again.
If the card is not to be used anymore, perform a lock and unlock operation, using the
TREE View window of the LMT.

114

NOTE
If an LPA, a DUAMCO, or a TRX has to be locked and unlocked, the following procedure has to be applied:
1. Deactivate the related UTRAN cell using the LMT-RNC or the RC.
Proceed according to the OMN:RNC Cell Configuration.
2. Lock the LPA, DUAMCO, or TRX.
Use the TREE View window or the Set Administrative State Locked command.
3. Unlock the LPA, DUAMCO, or TRX.
Use the TREE View window or the Set Administrative State Unlocked
command.
4. Activate the related UTRAN cell using the LMT-RNC or the RC.
Proceed according to the OMN:RNC Cell Configuration.

If the card is still plugged in, a board failure occurred and the addressed card has to
be replaced. Replacement must be done according to the Maintenance Manual
MMN:Node B.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

201001 - RET power off


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Ret
environmentalAlarm
ExternalPowerSupplyFailure
minor

Error Description
The addressed RET module is switched off at the POWER ON/OFF switch, but not defective. This mode is indicated by the RET LED which is off. Most likely, this alarm is
raised during normal Node B operation if the DIP switch 6 of the corresponding DIP
switch group is set to OFF position by accident.
Please switch on the RET module.
This alarm will only be output if the power status of the RET module has changed from
ON to OFF during operation. However, if the RET module is already switched off at boot
time of the Node B, this alarm will not be raised.
For RET recovery, a reset of the related DUAMCO is required in order to re-establish
the communication between DUAMCO and RET. A reset of the RET managed object is
not possible while this failure exists.
Troubleshooting

DANGER
To avoid the danger of an uncontrolled emission of microwave radiation, switch off the
breakers for the related LPAs/CATs before replacing antenna cables, antennas, RET,
or DUAMCO.
If the DIP switch 6 was set to the OFF position by accident, perform the following steps
in the given order:
1. Confirm that the power is supplied to the relevant RET module from DUAMCO.
Check the cables, and switch the POWER ON/OFF DIP switch 6 in position ON.
2. Reset the relevant DUAMCO managed object.
Use the TREE View window of the LMT or, alternatively, apply the rst command to
the relevant managed object.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

115

OML:Node B

Outputs
Node B

201002 - RET feeder alarm


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Ret
equipmentAlarm
ReceiverFailure
minor

Error Description
RET operations of the reporting module are not possible because the 2.176 MHz carrier
between the DUAMCO and DTMARET or the cable between DTMARET and RET is defective.
In the current configuration of Node B, this alarm should not occur at all. This alarm is
designed for possible applications in the future when no TMA will be used. If the carrier
is defective in the current configuration, the alarms 200910 - TMA feeder alarm and
201004 - RET communication error are output.
For RET recovery a reset of the related DUAMCO is required in order to re-establish the
communication between DUAMCO and RET. A reset of the RET managed object is not
possible while this failure exists.
Troubleshooting

DANGER
To avoid the danger of an uncontrolled emission of microwave radiation, switch off the
breakers for the related LPAs/CATs before replacing antenna cables, antennas, RET,
or DUAMCO.
In order to solve this error, perform the following steps in the given order:
1. Confirm that the cables between RET and DUAMCO are connected properly.
2. Reset the relevant DUAMCO. Use the TREE View window of the LMT or, alternatively, apply the rst command to it.
3. If the alarm has not ceased yet, the defective RET module must be replaced. Since
both the RET module and the antenna are OEM products, replacement must be
done according to the OEM vendors description.

116

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

201003 - RET hardware alarm


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Ret
equipmentAlarm
EquipmentFailure
minor

Error Description
The addressed RET module reported a hardware error, such as a motor jam or an
EPROM error.
Troubleshooting

DANGER
To avoid the danger of an uncontrolled emission of microwave radiation, switch off the
breakers for the related LPAs/CATs before replacing antenna cables, antennas, RET,
or DUAMCO.
Perform the following steps in the given order to solve this error:
1. Replace the defective RET module. Since both the RET module and the antenna are
OEM products, replacement must be done according to the OEM vendors description.
2. If the card replacement did not clear the fault, contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save the error
symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are out of the operators scope.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

117

OML:Node B

Outputs
Node B

201004 - RET communication error


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Ret
communicationAlarm
CommunicationProtocolError
minor

Error Description
The addressed RET module reported a communication error, such as a signaling interrupt. This alarm may be caused by one of the following:
An error occurred on the serial communication line between TMA and RET (RS485).
This alarm is output as a consequence of 200910 - TMA feeder alarm, occurring
whenever the 2.176 MHz carrier between DUAMCO and DTMARET or the cable between DTMARET and RET is defective.
For RET recovery, a reset of the related DUAMCO and the addressed RET is required
in order to re-establish the communication between DUAMCO and RET. Only resetting
the RET managed object is not possible while this failure exists.
Troubleshooting

DANGER
To avoid the danger of an uncontrolled emission of microwave radiation, switch off the
breakers for the related LPAs/CATs before replacing antenna cables, antennas, RET,
or DUAMCO.
First, check whether alarm 200910 - TMA feeder alarm is output. If this alarm has occurred before, eliminate the cause of the fault. Proceed according to the troubleshooting
of 200910 - TMA feeder alarm. This may clear the RET communication error, as well.
If either the TMA feeder alarm did not occur or the measures taken above did not clear
this fault, perform the following steps in the given order:
1. Confirm that the cables between RET and DUAMCO are connected properly.
2. Reset the relevant DUAMCO managed object.
Use the TREE View window of the LMT or, alternatively, apply the rst command to
the relevant managed object.
3. Reset the addressed RET managed object.
Use the TREE View window of the LMT or, alternatively, apply the rst command to
the relevant managed object.
4. If the alarm is still active, replace the defective RET module. Since both the RET
module and the antenna are OEM products, replacement must be done according
to the OEM vendors description.
5. If the card replacement did not clear the fault, contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save the error
symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are out of the operators scope.

118

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

201005 - RET isnt calibrated


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Ret
equipmentAlarm
ExternalIFDeviceProblem
minor

Error Description
The reporting RET module is disabled because it is not calibrated. Both the RET module
and the antenna have to be calibrated after installation. The stepper motor drives to the
end position.
To solve this error, the addressed RET module has to be calibrated.
Troubleshooting
Perform the following tasks in the order described to solve this error:
1. First, calibrate the relevant RET module, using either the TREE View window of the
LMT or, alternatively, applying the clb command to this RET module.
2. Contact the technical assistance center (TAC) to get support in isolating the fault. For
suitable preparation save the error symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which
are out of the operators scope.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

119

OML:Node B

Outputs
Node B

201006 - RET isnt scaled


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Ret
equipmentAlarm
ExternalIFDeviceProblem
minor

Error Description
The reporting RET module is disabled because it is not scaled. In other words, the translation table has not been downloaded to the relevant RET module.
The spindle scale table of the relevant RET module must be re-programmed.
Troubleshooting
1. Upload the relevant configuration data.
As a precondition, the relevant RET module must be accessible to connect the
RS485 interface.
To upload (and update) the RET configuration data, use the TREE View window of
the LMT or, alternatively, apply the updTable command to the reporting RET.
2. Contact the technical assistance center (TAC) to get support in isolating the fault. For
suitable preparation save the error symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which
are out of the operators scope.

120

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

201007 - RET lost position


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Ret
equipmentAlarm
ExternalIFDeviceProblem
minor

Error Description
The reporting RET module lost position of the stepper motor and is therefore disabled.
The relevant RET module must be calibrated again.
Furthermore, while adjusting the antenna tilt, the power supply was interrupted.
Troubleshooting
Perform the following steps in the given order to solve this error:
1. First, calibrate the relevant RET module, using the TREE View window of the LMT
or, alternatively, applying the clb command to this RET module.
2. Contact the technical assistance center (TAC) to get support in isolating the fault. For
suitable preparation save the error symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which
are out of the operators scope.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

121

OML:Node B

Outputs
Node B

201008 - RET received wrong configuration data


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Ret
communicationAlarm
CommunicationProtocolError
minor

Error Description
The addressed RET module received wrong configuration data and is therefore disabled.
Setting the appropriate configuration data may be required after installation of any RET
module unless this task has already been performed by the vendor before delivery. It
loads vendor and antenna specific configuration data to establish the relationship between the movement of the drive system and the beam position of the antenna.
Troubleshooting

DANGER
To avoid the danger of an uncontrolled emission of microwave radiation, switch off the
breakers for the related LPAs/CATs before replacing antenna cables, antennas, RET,
or DUAMCO.
In order to solve this error, perform the following steps in the given order:
1. Check whether the correct configuration data (antenna type and antenna OEM vendor) is used.
If the configuration data is OK, go to step (2).
Otherwise, if the configuration data is NG, the correct configuration data must be
uploaded using the LMT. To upload and update the RET configuration data, use
the TREE View window of the LMT or, alternatively, apply the updTable command
to the reporting RET.
2. Confirm that the cables between the RET and DUAMCO modules are connected
properly.
3. If the alarm is still active, replace the defective RET module. Since both the RET
module and the antenna are OEM products, replacement must be done according
to the OEM vendors description.
4. If the card replacement did not clear the fault, contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save the error
symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are out of the operators scope.

122

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

201009 - A mounted card is not used to its full capacity


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

*
processingErrorAlarm
ConfigurationOrCustomizationError
warning

Error Description
The Node B's configuration does not use the mounted card's full capacity and/or features. This could be an unwanted waste of resources.
Troubleshooting
In order to solve this error, perform the following steps in the given order:
1. Check the hardware compatibility of the configuration.
2. Replace the incompatible card. Replacement must be done according to the Maintenance Manual MMN:Node B.
3. If the error has not ceased yet, contact the technical assistance center (TAC) to get
support in isolating the fault. For suitable preparation save the error symptoms as
described in "Collect Info for Assistance". Log files need to be analyzed and specific
measures must be taken which are out of the operators scope.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

123

OML:Node B

Outputs
Node B

201010 - An incompatible card is mounted


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

*
processingErrorAlarm
ConfigurationOrCustomizationError
critical

Error Description
The mounted card does not fulfill the Node B's configuration requirements.
Troubleshooting
In order to solve this error, perform the following steps in the given order:
1. Check the hardware compatibility of the configuration.
2. Replace the incompatible card. Replacement must be done according to the Maintenance Manual MMN:Node B.
3. If the error has not ceased yet, contact the technical assistance center (TAC) to get
support in isolating the fault. For suitable preparation save the error symptoms as
described in "Collect Info for Assistance". Log files need to be analyzed and specific
measures must be taken which are out of the operators scope.

124

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

201011 - Alignment of standby CC failed


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Cc
processingErrorAlarm
FileError
major (final), handled according to the
Fault Escalation Strategy

Error Description
The alignment of the standby CC failed. The error should be reported to customer services. It is possible that a hardware or software error is the root of the problem.
Troubleshooting
Take the following steps to solve this error:
1. First, reset the relevant card. Use the TREE View window of the LMT or, alternatively, apply the rst command to the addressed card.
2. If the manual reset did not clear the fault, contact the technical assistance center
(TAC) to get support in isolating the fault. For suitable preparation save the error
symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are out of the operators scope.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

125

OML:Node B

Outputs
Node B

201012 - Timeout for connection to standby CC


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Cc
processingErrorAlarm
TimeoutExpired
major

Error Description
An expected message from the standby CC did not come in time. The error should be
reported to customer services. It is possible that a hardware or software error is the root
of the problem.
Troubleshooting
In order to solve this error, perform the following steps in the given order:
1. Reset the relevant card. Use the TREE View window of the LMT or, alternatively, apply the rst command to the addressed card.
2. If the manual reset did not clear the fault, contact the technical assistance center
(TAC) to get support in isolating the fault. For suitable preparation save the error
symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are out of the operators scope.

126

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

201013 - Connection failure to standby CC


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Cc
equipmentAlarm
LinkFailure
major

Error Description
An attempt to connect to the standby CC failed. The error should be reported to customer services. It is possible that a hardware or software error is the root of the problem.
Troubleshooting
In order to solve this error, perform the following steps in the given order:
1. Reset the addressed standby CC. Use the TREE View window of the LMT or, alternatively, apply the rst command to the addressed card.
2. Confirm that the relevant standby CC card is properly plugged into its slot.
3. If the manual reset did not clear the fault, contact the technical assistance center
(TAC) to get support in isolating the fault. For suitable preparation save the error
symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are out of the operators scope.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

127

OML:Node B

Outputs
Node B

201014 - Standby CC forced to become active due to unreachable active CC


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Cc
processingErrorAlarm
CorruptData
warning

Error Description
The former standby CC was not able to connect with the expected active CC and now
became active. Please note that this CC became active due to a recovery action and
might not contain the expected configuration. The other CC was not able to become active, thus it should be replaced.
Troubleshooting
In order to solve this error, perform the following steps in the given order:
1. Replace that CC which is in standby mode now and used to be active before. Replacement must be done according to the Maintenance Manual MMN:Node B.
2. Confirm that the Node B is configured properly. Check the Node Bs versions of database and SW load.
Use the TREE View window of the LMT or apply the validateF command to the relevant OSU object.
3. Perform a switch-over of the standby CC. This CC will then become active.
Take the following steps in the order provided:
Reset the standby CC, using the TREE View window of the LMT or, alternatively,
applying the rst command to the standby CC.
Perform the actual switch-over. Use the TREE View window or apply the reduSwtch command to the CC reset before.
4. If the measures taken above did not clear the fault, contact the technical assistance
center (TAC) to get support in isolating the fault. For suitable preparation save the
error symptoms as described in "Collect Info for Assistance". Log files need to be
analyzed and specific measures must be taken which are out of the operators
scope.

128

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

201015 - Preparation of data to be aligned has failed


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Cc
processingErrorAlarm
FileError
warning

Error Description
Data which has to be aligned could not be prepared. As a consequence, the standby CC
will not be aligned correctly. The error should be reported to customer services. It is possible that a hardware or software error is the root of the problem.
Troubleshooting
Contact the technical assistance center (TAC) to get support in isolating the fault. For
suitable preparation save the error symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are
out of the operators scope.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

129

OML:Node B

Outputs
Node B

201016 - Non-fatal internal LVDS failure


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Dric
equipmentAlarm
EquipmentMalfunction
minor

Error Description
A non-fatal hardware error has occurred (internal LVDS failure) in the reporting DRIC.
The state of the card is changed accordingly (AVS is degraded). If the card is providing
service (SBS is Providing Service), parts of the service could be lost and some of the
cells get disabled.
The card is still working partly but should be replaced. If a redundant card is installed
which is enabled, an operator-triggered switchover can be initiated from LMT.
Troubleshooting
1. If a redundant card is installed, perform a switch-over to this card. Afterwards, this
card will be active.
To trigger a switch-over from the active to a redundant card installed, set the administrative state of the reporting DRIC to shuttingDown. Use the TREE View window
of the LMT or, alternatively, apply the Set AdministrativeState ShuttingDown command to it.

NOTE
A switch-over to a redundant DRIC can only be triggered by setting the active DRICs
AVS to shuttingDown. Setting the AVS to locked is not sufficient.
Applying the Set AdministrativeState ShuttingDown command is furthermore only allowed if no cells would go down due to this operation.
2. Replace the defective card which used to be active before. Replacement must be
done according to the Maintenance Manual MMN:Node B.

130

NOTE
Replacing the formerly active card will lead to a scenario in which all services will be lost
if there is not any redundant card installed.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

201017 - Digital input power level too high, but gain


reduced
Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Cat, Rrh
equipmentAlarm
ExcessiveTransmitterOutputPower
minor

Error Description
The CAT/RRH detected a digital input power level from the DRIC that has continuously
been too high. In fact, the digital input power level has been more than 5 dB above the
maximum output power of the CAT/RRH for more than 60 seconds.
A root cause for the occurrence of the 201017 - Digital input power level too high, but
gain reduced alarm may be the following: the congestion control parameters for the related cell are not configured sufficiently in the RNCs database.
Please refer to the
Command Manual CML:RNC for details about congestion control parameters
OMN:RNC Cell Configuration - Concepts for details about setting up congestion
control in a specific cell
Troubleshooting
In order to solve this error, perform the following steps in the given order:
1. Confirm that all relevant cables are connected properly.
2. Check the setting of the following parameters related to congestion control in the
RNC database. The relevant parameters for the related cell of this Node B must be
set to the following values:
Downlink congestion threshold: dl_cngt <= 0.9
Downlink congestion hysteresis: dl_cngh >= 0.15
Number of bearers that are switched/dropped in each step: k >= 1
Enable bearer dropping: ebd = ena
For details about the parameters, refer to the cell cctl command in the Command
Manual CML:RNC.
3. If the fault could not be cleared, the addressed card must be replaced. Replacement
must be done according to the Maintenance Manual MMN:Node B.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

131

OML:Node B

Outputs
Node B

201018 - The LRU could not process a message from CC


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Cc, Ch, Rep, Trx, Dric, Cat, Ret, Rrh


processingErrorAlarm
InvalidParameter
major (final), handled according to the
Fault Escalation Strategy

Error Description
A fatal software error has occurred: the addressed LRU indicates a messaging failure
towards the CC.
After an unsuccessful automatic recovery by means of a reset, the reporting LRU was
put out of service.
As a consequence, cells or calls could potentially be lost. The states of all affected managed objects change accordingly.
Troubleshooting
In order to solve this error, perform the following steps in the given order:
1. Check the hardware compatibility of the configuration.
If necessary, replace the relevant card. Replacement must be done according to the
Maintenance Manual MMN:Node B.
2. Reset the relevant card. Use the TREE View window of the LMT or, alternatively, apply the rst command to the addressed card.
3. Contact the technical assistance center (TAC) to get support in isolating the fault.
For suitable preparation save the error symptoms as described in "Collect Info for
Assistance". Log files need to be analyzed and specific measures must be taken
which are out of the operators scope.

132

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

201019 - Gain below threshold


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Cat, Rrh
equipmentAlarm
SignalQualityEvaluationFault
major

Error Description
The gain of the CAT/RRH falls below a certain threshold. The output power has been
3dB below the expected output power calculated from the digital input signal for more
than a specified period of time.
As a consequence, the reporting CAT/RRH was put out of service. Cells or calls could
potentially be lost. The states of all affected managed objects change accordingly.
Troubleshooting
Contact the technical assistance center (TAC) to get support in isolating the fault. For
suitable preparation save the error symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are
out of the operators scope.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

133

OML:Node B

Outputs
Node B

201020 - Loss of single DRIF interface detected


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Dric
equipmentAlarm
LinkFailure
minor

Error Description
The communiation to a specific CAT/RRH module over one CPRI-compliant DRIF interface was lost, whereas a second DRIF interface to this CAT/RRH exits and is still working.
The single DRIF loss may be caused by a missing cable connection, by hardware problems on the CAT/RRH-DRIF-interface side as well as on the DRIC side.
As a consequence, cells or calls could potentially be lost if the lost DRIF carried user
plane data. Furthermore, the states of all affected managed objects change accordingly.
Troubleshooting
In order to solve this error, perform the following steps in the given order:
1. Confirm that all relevant cables are connected properly.
2. If the fault could not be cleared, replace the defective card. Replacement must be
done according to the Maintenance Manual MMN:Node B.

134

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

201022 - Alignment of file data has failed


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Cc
processingErrorAlarm
FileError
minor, handled according to the Fault
Escalation Strategy

Error Description
Alignment of file data from the active to the standby CC failed.
The data to be aligned is not indispensable for redundancy in general. For example logging-, or PM-data can be affected.
The error should be reported to customer services. It is possible that a hardware or software error is the root of the problem.
Troubleshooting
Contact the technical assistance center (TAC) to get support in isolating the fault. For
suitable preparation save the error symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are
out of the operators scope.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

135

OML:Node B

Outputs
Node B

201023 - Bad signal quality of single DRIF interface


detected
Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Cat, Rrh
equipmentAlarm
LinkFailure
minor

Error Description
The addressed CAT/RRH module detected that the signal quality on one DRIF will not
ensure a reliable data transmission.
The following cases are possible:
Case 1: The DRIF to DRIC-N is affected and a second working DRIF connection to
DRIC-E exists. Therefore, CAT/RRH connects to DRIC-E. However, in this case cells
and calls could potentially be lost.
Case 2: The DRIF to DRIC-E is affected. This case has no direct impact for cells and
calls until a switch over to DRIC-E occurs.
This alarm message may occur in conjunction with 201020 - Loss of single DRIF interface detected on DRIC-N.
The failure can be caused by one of the following:
Failure to receive an expected response to a CORBA request within specified time
limits.
Indications of a connection failure from the communication stack, for example pointto-point protocol (PPP), internet protocol (IP), high level data link control protocol
(HDLC), etc.
Troubleshooting
In order to solve this error, perform the following steps in the given order:
1. Confirm that all relevant cables are connected properly.
2. If the fault could not be cleared, replace the defective card. Replacement must be
done according to the Maintenance Manual MMN:Node B.
3. If the replacement of the card could not clear the fault, contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save
the error symptoms as described in "Collect Info for Assistance". Log files need to
be analyzed and specific measures must be taken which are out of the operators
scope.

136

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

201024 - Bad signal quality of all DRIF interfaces detected


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Cat, Rrh
equipmentAlarm
LinkFailure
major (final), handled according to the
Fault Escalation Strategy

Error Description
The addressed CAT/RRH module detected that the signal quality on all DRIF will not ensure a reliable data transmission. After an unsuccessful automatic recovery (card reset),
the CAT/RRH was put out of service. The states of the CAT/RRH (operational state,
availability status, and alarm status) changed accordingly.
As a consequence, cells or calls could potentially be lost. The states of all affected managed objects change accordingly.
The failure can be caused by one of the following:
Failure to receive an expected response to a CORBA request within specified time
limits
Indications of a connection failure from the communication stack, for example pointto-point protocol (PPP), internet protocol (IP), high level data link control protocol
(HDLC), etc.
Troubleshooting
In order to solve this error, perform the following steps in the given order:
1. Confirm that all relevant cables are connected properly.
2. If the fault could not be cleared, replace the defective card. Replacement must be
done according to the Maintenance Manual MMN:Node B.
3. If the replacement of the card could not clear the fault, contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save
the error symptoms as described in "Collect Info for Assistance". Log files need to
be analyzed and specific measures must be taken which are out of the operators
scope.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

137

OML:Node B

Outputs
Node B

201025 - PID could not be read or is corrupted


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

*
equipmentAlarm
EquipmentFailure
major (final), handled according to the
Fault Escalation Strategy

Error Description
A hardware error has occurred! The PID of the addressed LRU could not be read or is
corrupted. Basic operation of the affected LRU is not possible.
The information contained in the PID is essential for the operation of the LRU. Therefore, the reporting LRU will fail.
As a consequence, cells or calls could potentially be lost. The states of all affected managed objects change accordingly.
Report this error to customer service. The PID of the failed LRU has to be updated.
Troubleshooting
Carrying out the following measures will help to solve this error:
1. Replace the addressed card. Replacement must be done according to the Maintenance Manual MMN:Node B.
However, if OEM parts are affected, proceed according to the OEM vendors description.
2. If the replacement of the card could not clear the fault, contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save
the error symptoms as described in "Collect Info for Assistance". Log files need to
be analyzed and specific measures must be taken which are out of the operators
scope.

138

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

201026 - LRU sent illegal parameter


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

*
processingErrorAlarm
InvalidParameter
major (final), handled according to the
Fault Escalation Strategy

Error Description
The following fatal software error has occurred: the addressed LRU sent an illegal parameter.
After an unsuccessful automatic recovery by means of a reset, the reporting LRU was
put of of service.
As a result of this failure, cells or calls could potentially be lost. Furthermore, the states
of all affected managed objects change accordingly.
As a matter of principle, this error should always be reported to customer service.
Manual recovery can be applied by an operator-triggered reset of the addressed card
from the LMT.
Troubleshooting
In order to solve this error, perform the following steps in the given order:
1. Reset the addressed card.
2. If the manual reset has not helped to cease the alarm, check the hardware compatibility of the configuration.
3. If the measures taken above have not been successful, contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save
the error symptoms as described in "Collect Info for Assistance". Log files need to
be analyzed and specific measures must be taken which are out of the operators
scope.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

139

OML:Node B

Outputs
Node B

201027 - LRU could not process a message from CC containing data from DB
Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Ch, Rep, Trx, Dric, Cat, Rrh


processingErrorAlarm
InvalidParameter
major

Error Description
A fatal error has occurred: the reporting LRU could not process a message from the core
controller (CC) containing data from the Node Bs database (DB).
This alarm may be caused by one of the following:
Wrong database
A database attribute which has been changed via Itf-B from the LMT.
As a consequence of this failure, service may be affected.
The database should be verified. Manual recovery could be applied by an operator-triggered reset of the reporting object from the LMT.
Troubleshooting
The following measures must be taken in the given order to solve this error:
1. Reset the reporting card by means of the following procedure:
Lock the card, using either the TREE View window or the Set AdministrativeState
Locked command.
Reset the card. Use the TREE View window of the LMT or, alternatively, apply the
rst command to the reporting MOI.
2. If the manual reset did not help to solve this error, check the Node Bs database. The
DB check must be performed according to the OGL:Node B DB Editing Guide.
3. Change the Node Bs DB. The DB change must be performed according to the
OGL:Node B DB Editing Guide.
4. If the measures taken above have not been successful, contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save
the error symptoms as described in "Collect Info for Assistance". Log files need to
be analyzed and specific measures must be taken which are out of the operators
scope.

140

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

201028 - HW-failure clock processing


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

NodeBFddE
equipmentAlarm
EquipmentMalfunction
major

Error Description
A fatal hardware (HW) error has occurred. This error is caused by a fatal HW failure of
the active core controllers (CC) clock processing unit. This failure may lead to impacts
on the air interfaces synchronization.
If the clock processing failure occurs simultaneously with the 202506 - Node B System
Clock in Holdover Mode alarm, stable Node B operation may not be possible any longer.
As a consequence, cells or calls could be lost. The states (operational state and availability status) of all affected managed objects change accordingly.
The card should be replaced. Furthermore, manual recovery could be applied by an operator-triggered reset of the CC from the LMT. If a standby CC is installed, a switch over
to this CC can be initiated, too.
Troubleshooting
Perform the following steps in the given order to solve this alarm:
1. Reset the defective core controller. Use the TREE View window of the LMT or, alternatively, apply the rst command to the reporting MOC.
2. If a standby CC is installed, perform a switch over from the defective active CC to the
standby CC. Use the TREE View window of the LMT or, alternatively, apply the reduSwtch command to the active CC.
3. Replace the defective CC. Replacement must be done according to the Maintenance Manual MMN:Node B.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

141

OML:Node B

Outputs
Node B

201029 - MEF blocked


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

BaseRack
equipmentAlarm
EquipmentMalfunction
minor

Error Description
The membrane filter (MEF) is polluted. Therefore, the MEFs lifetime will run out.
The 200920 - High temperature of PA alarm has been output before. This alarm indicates a high temperature scenario in at least one PA installed in the Node B.
The MEF has to be exchanged within the next 2 weeks.
A further increase of the MEFs pollution may lead to a severe defect. A heaviliy polluted
MEF can cause the following alarms:
200921 - Over temperature of PA
200986 - Temperature out of range in upper direction
200995 - High Temperature Limit (Ht3) reached
200996 - Critical Temperature Limit (Ht4) reached
201035 - MEF completely blocked
Troubleshooting
Replace the MEF during the next two (2) weeks after occurrence of this alarm. Replacement must be done according to the Maintenance Manual MMN:Node B.
Replacing the MEF will assure a sufficient air flow and therefore cooling of the Node B.

142

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

201030 - Invalid hardware capacity licensing value


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Cc, Ch, Dric


processingErrorAlarm
CorruptData
warning

Error Description
The hardware capacity licensing value read from the reporting card is invalid.
Troubleshooting
Perform the following steps in the given order to solve this error:
1. Replace the reporting card by a licensed card. Replacement must be done according to the Maintenance Manual MMN:Node B.
2. If the replacement of the card could not clear the fault, contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save
the error symptoms as described in "Collect Info for Assistance". Log files need to
be analyzed and specific measures must be taken which are out of the operators
scope.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

143

OML:Node B

Outputs
Node B

201031 - Wrong combination of licensed cards


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

NodeBFddE
processingErrorAlarm
ConfigurationOrCustomizationError
minor

Error Description
The combination of hardware capacity licensing values is invalid. This error might be
caused by using more cards that carry a restricted license than supported by the licensing terms and conditions.
Troubleshooting
Perform the following steps in the given order to solve this error:
1. Check the hardware compatibility of the configuration.
2. If the first step could not clear the fault, contact the technical assistance center (TAC)
to get support in isolating the fault. For suitable preparation save the error symptoms
as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are out of the operators scope.

144

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

201032 - Not all cells are licensed


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

NodeBFddE
processingErrorAlarm
ConfigurationOrCustomizationError
minor

Error Description
The contracted hardware capacity licenses for UTRAN cells do not cover all cells configured in the Node Bs database. Those cells which are not licensed remain disabled
after Node Bs start-up.
Troubleshooting
Carrying out the following steps in the given order will help to solve this alarm:
1. Check the compatibility of the current configuration.
2. Check the Node Bs database (DB), using the mibCheck or mibCheckWin tool delivered with the Node Bs software. The DB check must be performed according to the
OGL:Node B DB Editing Guide.
3. Change the Node Bs DB in such a way that only the licensed number of UTRAN
cells is configured. The DB change must be performed according to the
OGL:Node B DB Editing Guide.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

145

OML:Node B

Outputs
Node B

201033 - PID could not be read or is corrupted - non-fatal


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

*
equipmentAlarm
EquipmentFailure
minor

Error Description
A hardware error has occurred! The PID of the addressed LRU could not be read or is
corrupted. Basic operation of the affected LRU is possible without the information contained in the PID.
Service is not affected.
Report this error to customer service. The PID of the failed LRU has to be updated.
Troubleshooting
Carrying out the following measures will help to solve this error:
1. Replace the addressed card. Replacement must be done according to the Maintenance Manual MMN:Node B.
However, if OEM parts are affected, proceed according to the OEM vendors description.
2. If the replacement of the card could not clear the fault, contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save
the error symptoms as described in "Collect Info for Assistance". Log files need to
be analyzed and specific measures must be taken which are out of the operators
scope.

146

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

201034 - Boosters Fan unit failed


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Booster
environmentalAlarm
FanFailure
major

Error Description
The fan unit of the reporting booster is defective. This situation leads to a lack of air circulation in the affected Node B. A failure of components which are sensitive to heat may
exist.
Caused by the insufficient air circulation in the Node B, related temperature alarms may
be reported by the addressed booster. The following alarms may therefore occur in conjunction with the 201034 - Boosters Fan unit failed alarm:
200920 - High temperature of PA
200921 - Over temperature of PA
Troubleshooting

WARNING
When pulling out the fan module, the rotor may still rotate for a few seconds. Watch your
fingers.

NOTE
The defective fan unit(s) are recommended to be exchanged within the next 24 hours!
Replace the defective fan unit of the reporting booster within the next 24 hours. Replacement must be done according to the Maintenance Manual MMN:Node B.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

147

OML:Node B

Outputs
Node B

201035 - MEF completely blocked


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

BaseRack
equipmentAlarm
EquipmentMalfunction
critical

Error Description
The membrane filter (MEF) is heavily polluted. Therefore, the MEFs lifetime has run out.
The 200921 - Over temperature of PA alarm has been output before. This alarm indicates an over temperature scenario in at least one PA installed in the Node B.
Exchange the defective MEF immediately. Otherwise a severe hardware damage can
occur.
A defective MEF can cause the following alarms:
200986 - Temperature out of range in upper direction
200995 - High Temperature Limit (Ht3) reached
200996 - Critical Temperature Limit (Ht4) reached
Troubleshooting
Take the following measures to clear the fault which cause this alarm:
1. Replace the MEF immediately.
Replacement must be done according to the Maintenance Manual MMN:Node B.
Replacing the defective MEF will assure a sufficient air flow and therefore cooling of
the Node B.
2. As the 200921 - Over temperature of PA alarm is a fatal alarm (severity: major), all
PAs which report this alarm have to be reset manually via LMT.
Use the TREE View window of the LMT and apply the relevant rst commands to the
reporting PAs.

148

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

201036 - RRHs unable to establish communication links


with the expected number of PSRs.
Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

NodeBFddE
equipmentAlarm
EquipmentFailure
minor

Error Description
Remote radio heads (RRHs) of the reporting Node B cannot establish communication
links with the expected number of power supplies for the RRHs (PSRs).
The problem indicated by this alarm may occur in either of the following situations:
After Node B startup, not all configured PSRs managed to establish a communication link with a connected RRH within a specified period of time.
Besides RRH and PSR hardware defects and wrong cable connections, this alarm
can occur when the number of PSRs configured in the system is wrong.
After breakdown of a communication link, a PSR failed to reconnect itself to an RRH
within a specified period of time.
The breakdown of a communication link may be caused by the following:
RRH or PSR hardware defect
Broken cable connection
Preceding reset of the related RRH
If no communication link between RRH and PSR exists, no PSR alarms can be reported
by the Node B.
Troubleshooting
Take the following measures to clear the fault cause and, thus, the alarm:
1. Confirm that all cables are connected properly.
2. Replace the defective PSRs. Replacement must be done according to the Maintenance Manual MMN:Node B.
3. If the alarm has not ceased yet, check in the Node Bs database whether the number
of PSRs configured in the system is wrong.
Check the Node B database. Use the mibCheck or mibCheckWin tool delivered
with the Node Bs software. Proceed according to the OGL:Node B DB Editing
Guide.
If necessary, change the running database. Edit the database according to the
OGL:Node B DB Editing Guide.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

149

OML:Node B

Outputs
Node B

201037 - RET unspecified error


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Ret
equipmentAlarm
ExternalIFDeviceProblem
minor

Error Description
An unspecified error occurred in the reporting RET module. Due to this error, the addressed RET module is disabled.
Troubleshooting

DANGER
To avoid the danger of an uncontrolled emission of microwave radiation, switch off the
breakers for the related LPAs/CATs before replacing antenna cables, antennas, RET,
or DUAMCO.
Perform the following steps in the given order to solve this error:
1. Replace the defective RET module. Since both the RET module and the antenna are
OEM products, replacement must be done according to the OEM vendors description.
2. If the card replacement did not clear the fault, contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save the error
symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are out of the operators scope.

150

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

201038 - Resource conflict between CP and OAM


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

LocalCellE
processingErrorAlarm
UnderlyingResourceUnavailable
minor

Error Description
The CP rejected a request of the RNC, such as a radio link setup request, because the
necessary resources are currently allocated by OAM, for instance channels for orthogonal channel noise simulator (OCNS). These resources may be channelization codes or
code trees occupied by DLLG or OCNS, issued by the startModulatedSignalTransmission command.
The required resources have to be freed, releasing the OCNS channels, for example,
before the RNCs request can be processed.
This alarm is cleared as soon as all DLLG and OCNS channels are stopped on the affected cell.
Troubleshooting
To solve this problem, free the occupied resources of the reporting cell (LocalCellE
MOI) by completely stopping the DLLG or OCNS channels. Use the TREE View window
of the LMT or, alternatively, apply the endModulatedSignalTransmission command to
the CHC the occupied resources are assigned to.
This will clear the alarm and free the resources allocated by OAM. RNC requests can
now be serviced again.
To avoid such collisions in the future, an adjustment of the channelization codes used
for OCNS may be necessary.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

151

OML:Node B

Outputs
Node B

201039 - Inconsistency between hardware license and


configuration
Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Cat
processingErrorAlarm
ConfigurationOrCustomizationError
major

Error Description
The hardware capacity license of the reporting LRU is not consistent with the current
configuration. This error may be caused by using an LRU equipped with an insufficient
license.
As a result, the addressed LRU is put out of service. Additionally, all cells related to this
LRU remain disabled after startup.
Troubleshooting
To solve this error, perform the following steps in the order provided:
1. Check the hardware compatibility of the Node B.
2. Update the addressed LRUs hardware capacity to the required value.
Proceed according to the Operator Guideline OGL:LMT Node B.
3. If the first steps could not clear the fault, contact the technical assistance center
(TAC) to get support in isolating the fault. For suitable preparation save the error
symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are out of the operators scope.

152

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

201040 - Wrong cabling of LRU detected


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Cat
processingErrorAlarm
ConfigurationOrCustomizationError
major

Error Description
The reporting LRU was not cabled correctly according to the installation manual of the
Node B. As a result, the addressed LRU has been put out of service. All cells related to
this LRU remain disabled.
Troubleshooting
Perform the following steps in the order provided to solve this error:
For rack-mounted LRUs:
Check for the LRUs correct position in the Node Bs rack.
Otherwise, confirm that cables are connected correctly to the addressed LRU. In the
event of wrong cabling, connect the cables correctly to the LRU. Proceed according
to the Installation Manual (IMN) of the relevant Node B.
For NB-440 or NB-880, refer to the IMN:NB-440/NB-880.
For NB-441 or NB-881, refer to the IMN:NB-441/NB-881.
For NB-420 or NB-860, refer to the IMN:NB-420/NB-860.
For NB-580, refer to the IMN:NB-580.
For NB-341, refer to the IMN:NB-341.
For Radio Server, refer to the IMN:RS.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

153

OML:Node B

Outputs
Node B

201916 - Toggling condition detected for alarm AIS, SP


ID 202059
Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

E1TTP, J1TTP
communicationAlarm
VendorSpecific
minor

Error Description
An alarm toggling condition has been detected for the 202059 - Alarm Indication Signal
on Physical Link alarm.
Troubleshooting
No action is required to cease this alarm.

154

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

201917 - Toggling condition detected for alarm RAI, SP


ID 202060
Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

E1TTP, J1TTP
communicationAlarm
VendorSpecific
minor

Error Description
An alarm toggling condition has been detected for the 202060 - Remote Alarm Indication
on Physical Link alarm.
Troubleshooting
No action is required to cease this alarm.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

155

OML:Node B

Outputs
Node B

201918 - Toggling condition detected for alarm lineAIS,


SP ID 202062
Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Stm1TP
communicationAlarm
VendorSpecific
minor

Error Description
An alarm toggling condition has been detected for the 202062 - Line Alarm Indication
Signal Indication on STM1 Physical Link alarm.
Troubleshooting
No action is required to cease this alarm.

156

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

201919 - Toggling condition detected for alarm lineRDI,


SP ID 202063
Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Stm1TP
communicationAlarm
VendorSpecific
minor

Error Description
An alarm toggling condition has been detected for the 202063 - Line Remote Defect Indication on STM1 Physical Link alarm.
Troubleshooting
No action is required to cease this alarm.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

157

OML:Node B

Outputs
Node B

201920 - Toggling condition detected for alarm pathAIS,


SP ID
Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Stm1TP
communicationAlarm
VendorSpecific
minor

Error Description
An alarm toggling condition has been detected for the 202065 - Path Alarm Indication
Signal on STM1 Physical Link alarm.
Troubleshooting
No action is required to cease this alarm.

158

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

201921 - Toggling condition detected for alarm pathRDI,


SP ID 202066
Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Stm1TP
communicationAlarm
VendorSpecific
minor

Error Description
An alarm toggling condition has been detected for the 202066 - Path Remote Defect Indication on STM1 Physical Link alarm.
Troubleshooting
No action is required to cease this alarm.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

159

OML:Node B

Outputs
Node B

201922 - Toggling condition detected for alarm vcAIS,


SP ID 202072
Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

VcTTP
communicationAlarm
VendorSpecific
minor

Error Description
An alarm toggling condition has been detected for the 202072 - Alarm Indication Signal
on an ATM VC alarm.
Troubleshooting
No action is required to cease this alarm.

160

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

201923 - Toggling condition detected for alarm vcRDI,


SP ID 202073
Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

VcTTP
communicationAlarm
VendorSpecific
minor

Error Description
An alarm toggling condition has been detected for the 202073 - Remote Defect Indication on an ATM VC alarm.
Troubleshooting
No action is required to cease this alarm.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

161

OML:Node B

Outputs
Node B

201924 - Toggling condition detected for alarm vpAIS,


SP ID 202075
Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

VpTTP
communicationAlarm
VendorSpecific
minor

Error Description
An alarm toggling condition has been detected for the 202075 - Alarm Indication Signal
on an ATM VP alarm.
Troubleshooting
No action is required to cease this alarm.

162

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

201925 - Toggling condition detected for alarm vpRDI,


SP ID 202076
Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

VpTTP
communicationAlarm
VendorSpecific
minor

Error Description
An alarm toggling condition has been detected for the 202076 - Remote Defect Indication on an ATM VP alarm.
Troubleshooting
No action is required to cease this alarm.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

163

OML:Node B

Outputs
Node B

201926 - Toggling condition detected for alarm LOC, SP


ID 202097
Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

ContinuityMonitor
communicationAlarm
VendorSpecific
minor

Error Description
An alarm toggling condition has been detected for the 202097 - Loss of Continuity detected on an ATM VP alarm.
Troubleshooting
No action is required to cease this alarm.

164

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

202006 - A bbUsageRatio Quality of Service alarm has occurred


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

NodeBFddE
qualityOfServiceAlarm
ThresholdCrossed
indeterminate

Error Description
A bbUsageRatio threshold crossing alarm has been raised. (only used in UMR2.0
Drop 1)
Troubleshooting
Contact the technical assistance center (TAC) to get support in isolating the fault. For
suitable preparation save the error symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are
out of the operators scope.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

165

OML:Node B

Outputs
Node B

202007 - A scanner could not be initialized


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Scanner, ScannerHsdpa
processingErrorAlarm
ConfigurationOrCustomizationError
minor

Error Description
The addressed scanner could not be initialized. The additional text will give the reason
(e.g. too many scanners, invalid parameters). If the problem is a misconfiguration, the
scanner will be created but will be disabled. Lock the scanner, fix the configuration, then
unlock to clear the error.
Troubleshooting
1. Lock the relevant scanner. Use the TREE View window of the LMT in order to set
the administrative state of the relevant scanner to locked.
2. Fix the configuration.
3. Set the administrative state of the addressed scanner to unlocked in order to clear
the error. Use the TREE View window of the LMT.

166

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

202008 - The temporary measurement results could not be


stored
Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Scanner, ScannerHsdpa
processingErrorAlarm
FileError
minor

Error Description
The internal temporary measurement results could not be stored. The reporting scanner
will no longer perform any measurements and will be set to disabled. The Node B may
need to be reset before measurements can be restarted correctly.
Troubleshooting
Reset the Node B. Use the TREE View window of the LMT or, alternatively, apply the
rst command to the NODEBFDDE managed object.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

167

OML:Node B

Outputs
Node B

202009 - Unable to request measurement results


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Scanner, ScannerHsdpa
processingErrorAlarm
SystemCallUnsuccessful
minor

Error Description
One or more of the measurement results for the addressed scanner could not be requested. These measurements will be marked as suspect for the current granularity period. The scanner will try to request these measurements again at the end of the next
granularity period. If the next request for reports is successful, the fault will automatically
be cleared.
Troubleshooting
Contact the technical assistance center (TAC) to get support in isolating the fault. For
suitable preparation save the error symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are
out of the operators scope.

168

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

202010 - The ScanCo could not be initialized


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

ScanCo
processingErrorAlarm
ConfigurationOrCustomizationError
minor

Error Description
A ScanCo could not be created. The additional text will give the reason for the failure.
As a consequence, performance measurements will not be started on the relevant
Node B.
Troubleshooting
Contact the technical assistance center (TAC) to get support in isolating the fault. For
suitable preparation save the error symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are
out of the operators scope.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

169

OML:Node B

Outputs
Node B

202011 - The final results files could not be generated


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

ScanCo
processingErrorAlarm
FileError
minor

Error Description
The temporary measurement results of the reporting ScanCo could not be converted
into a final results files.
This failure will have the following impacts:
The upload in progress will be aborted.
Some measurement files will be lost.
A Node B reset may be required before further upload attempts will be successful.
Troubleshooting
Reset the associated Node B. Use the TREE View window of the LMT or, alternatively,
apply the rst command to the relevant NODEBFDDE managed object.

170

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

202012 - The first bbUsageRatio Quality of Service alarm


has occurred
Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

NodeBFddE
qualityOfServiceAlarm
ThresholdCrossed
indeterminate

Error Description
The first bbUsageRatio threshold-crossing alarm was raised (used from UMR2.0 Drop 2
onwards). This is a QoS alarm which was not generated by any HW or SW error.
The operator can set four thresholds of any percentage for bbUsageRatio: notify
high 1/2 and notify low 1/2 which raise and clear the related alarms (202012 - The first
bbUsageRatio Quality of Service alarm has occurred / 202013 - The second bbUsageRatio Quality of Service alarm has occurred), respectively, when crossed. Furthermore,
the operator can determine an alarm severity for each of the relevant QoS alarms. All
values are related to call-processing resources of the Node B.
If many subscribers within one UTRAN cell use their UEs at the same time, a shortage
of HW resources in this cell may occur as a consequence and this alarm will be output.
Troubleshooting
Re-consider the current network design. If possible, modify the configuration of the adjacent cells so that the same area of this cell is covered by several Node Bs. This may
help to solve the lack of resources without a system crash.
Furthermore, contact the technical assistance center (TAC) to get support in isolating
the fault. For suitable preparation save the error symptoms as described in "Collect Info
for Assistance". Log files need to be analyzed and specific measures must be taken
which are out of the operators scope.
As soon as this QoS alarm is ceased, relevant threshold information will be displayed.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

171

OML:Node B

Outputs
Node B

202013 - The second bbUsageRatio Quality of Service


alarm has occurred
Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

NodeBFddE
qualityOfServiceAlarm
ThresholdCrossed
indeterminate

Error Description
The second bbUsageRatio threshold-crossing alarm was raised (used from UMR 2.0
Drop 2 onwards). This is a QoS alarm which was not generated by any HW or SW error.
The operator can set four thresholds of any percentage for bbUsageRatio: notify
high 1/2 and notify low 1/2 which raise and clear the related alarms (202012 - The first
bbUsageRatio Quality of Service alarm has occurred / 202013 - The second bbUsageRatio Quality of Service alarm has occurred), respectively, when crossed. Furthermore,
the operator can determine an alarm severity for each of the relevant QoS alarms. All
values are related to call-processing resources of the Node B.
If many subscribers within one UTRAN cell use their UEs at the same time, a shortage
of HW resources in this cell may occur as a consequence and this alarm will be output.
Troubleshooting
Re-consider the current network design. If possible, modify the configuration of the adjacent cells so that the same area of this cell is covered by several Node Bs. This may
help to solve the lack of resources without a system crash.
Furthermore, contact the technical assistance center (TAC) to get support in isolating
the fault. For suitable preparation save the error symptoms as described in "Collect Info
for Assistance". Log files need to be analyzed and specific measures must be taken
which are out of the operators scope.
As soon as this QoS alarm is ceased, relevant threshold information will be displayed.

172

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

202014 - The first sccpchUsageRatio Quality of Service


alarm has occurred
Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

LocalCellE
qualityOfServiceAlarm
ThresholdCrossed
indeterminate

Error Description
The first sccpchUsageRatio threshold-crossing alarm was raised. This is a QoS alarm
which was not generated by any HW or SW error.
The operator can set four thresholds of any percentage for sccpchUsageRatio: notify
high 1/2 and notify low 1/2 which raise and clear the related alarms (202014 - The first
sccpchUsageRatio Quality of Service alarm has occurred / 202015 - The second sccpchUsageRatio Quality of Service alarm has occurred), respectively, when crossed. Furthermore, the operator can determine an alarm severity for each of the relevant QoS
alarms. All values are related to call-processing resources of the Node B.
If many subscribers within one UTRAN cell use their UEs at the same time, a shortage
of HW resources in this cell may occur as a consequence and this alarm will be output.
Troubleshooting
Re-consider the current network design. If possible, modify the configuration of the adjacent cells so that the same area of this cell is covered by several Node Bs. This may
help to solve the lack of resources without a system crash.
Furthermore, contact the technical assistance center (TAC) to get support in isolating
the fault. For suitable preparation save the error symptoms as described in "Collect Info
for Assistance". Log files need to be analyzed and specific measures must be taken
which are out of the operators scope.
As soon as this QoS alarm is ceased, relevant threshold information will be displayed.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

173

OML:Node B

Outputs
Node B

202015 - The second sccpchUsageRatio Quality of Service


alarm has occurred
Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

LocalCellE
qualityOfServiceAlarm
ThresholdCrossed
indeterminate

Error Description
The second sccpchUsageRatio threshold-crossing alarm was raised. This is a QoS
alarm which was not generated by any HW or SW error.
The operator can set four thresholds of any percentage for sccpchUsageRatio: notify
high 1/2 and notify low 1/2 which raise and clear the related alarms (202014 - The first
sccpchUsageRatio Quality of Service alarm has occurred / 202015 - The second sccpchUsageRatio Quality of Service alarm has occurred), respectively, when crossed. Furthermore, the operator can determine an alarm severity for each of the relevant QoS
alarms. All values are related to call-processing resources of the Node B.
If many subscribers within one UTRAN cell use their UEs at the same time, a shortage
of HW resources in this cell may occur as a consequence and this alarm will be output.
Troubleshooting
Re-consider the current network design. If possible, modify the configuration of the adjacent cells so that the same area of this cell is covered by several Node Bs. This may
help to solve the lack of resources without a system crash.
Furthermore, contact the technical assistance center (TAC) to get support in isolating
the fault. For suitable preparation save the error symptoms as described in "Collect Info
for Assistance". Log files need to be analyzed and specific measures must be taken
which are out of the operators scope.
As soon as this QoS alarm is ceased, relevant threshold information will be displayed.

174

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

202016 - The first prachUsageRatio Quality of Service


alarm has occurred
Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

LocalCellE
qualityOfServiceAlarm
ThresholdCrossed
indeterminate

Error Description
The first prachUsageRatio threshold-crossing alarm was raised. This is a QoS alarm
which was not generated by any HW or SW error.
The operator can set four thresholds of any percentage for prachUsageRatio: notify
high 1/2 and notify low 1/2 which raise and clear the related alarms (202016 - The first
prachUsageRatio Quality of Service alarm has occurred / 202017 - The second prachUsageRatio Quality of Service alarm has occurred), respectively, when crossed. Furthermore, the operator can determine an alarm severity for each of the relevant QoS
alarms. All values are related to call-processing resources of the Node B.
If many subscribers within one UTRAN cell use their UEs at the same time, a shortage
of HW resources in this cell may occur as a consequence and this alarm will be output.
Troubleshooting
Re-consider the current network design. If possible, modify the configuration of the adjacent cells so that the same area of this cell is covered by several Node Bs. This may
help to solve the lack of resources without a system crash.
Furthermore, contact the technical assistance center (TAC) to get support in isolating
the fault. For suitable preparation save the error symptoms as described in "Collect Info
for Assistance". Log files need to be analyzed and specific measures must be taken
which are out of the operators scope.
As soon as this QoS alarm is ceased, relevant threshold information will be displayed.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

175

OML:Node B

Outputs
Node B

202017 - The second prachUsageRatio Quality of Service


alarm has occurred
Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

LocalCellE
qualityOfServiceAlarm
ThresholdCrossed
indeterminate

Error Description
The second prachUsageRatio threshold-crossing alarm was raised. This is a QoS alarm
which was not generated by any HW or SW error.
The operator can set four thresholds of any percentage for prachUsageRatio: notify
high 1/2 and notify low 1/2 which raise and clear the related alarms (202016 - The first
prachUsageRatio Quality of Service alarm has occurred / 202017 - The second prachUsageRatio Quality of Service alarm has occurred), respectively, when crossed. Furthermore, the operator can determine an alarm severity for each of the relevant QoS
alarms. All values are related to call-processing resources of the Node B.
If many subscribers within one UTRAN cell use their UEs at the same time, a shortage
of HW resources in this cell may occur as a consequence and this alarm will be output.
Troubleshooting
Re-consider the current network design. If possible, modify the configuration of the adjacent cells so that the same area of this cell is covered by several Node Bs. This may
help to solve the lack of resources without a system crash.
Furthermore, contact the technical assistance center (TAC) to get support in isolating
the fault. For suitable preparation save the error symptoms as described in "Collect Info
for Assistance". Log files need to be analyzed and specific measures must be taken
which are out of the operators scope.
As soon as this QoS alarm is ceased, relevant threshold information will be displayed.

176

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

202018 - The first cpUsageRatio Quality of Service alarm


has occurred
Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

NodeBFddE
qualityOfServiceAlarm
ThresholdCrossed
indeterminate

Error Description
The first cpUsageRatio threshold-crossing alarm was raised. This is a QoS alarm which
was not generated by any HW or SW error.
The operator can set four thresholds of any percentage for cpUsageRatio: notify
high 1/2 and notify low 1/2 which raise and clear the related alarms (202018 - The first
cpUsageRatio Quality of Service alarm has occurred / 202019 - The second cpUsageRatio Quality of Service alarm has occurred), respectively, when crossed. Furthermore,
the operator can determine an alarm severity for each of the relevant QoS alarms. All
values are related to call-processing resources of the Node B.
If many subscribers within one UTRAN cell use their UEs at the same time, a shortage
of HW resources in this cell may occur as a consequence and this alarm will be output.
Troubleshooting
Re-consider the current network design. If possible, modify the configuration of the adjacent cells so that the same area of this cell is covered by several Node Bs. This may
help to solve the lack of resources without a system crash.
Furthermore, contact the technical assistance center (TAC) to get support in isolating
the fault. For suitable preparation save the error symptoms as described in "Collect Info
for Assistance". Log files need to be analyzed and specific measures must be taken
which are out of the operators scope.
As soon as this QoS alarm is ceased, relevant threshold information will be displayed.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

177

OML:Node B

Outputs
Node B

202019 - The second cpUsageRatio Quality of Service


alarm has occurred
Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

NodeBFddE
qualityOfServiceAlarm
ThresholdCrossed
indeterminate

Error Description
The second cpUsageRatio threshold-crossing alarm was raised. This is a QoS alarm
which was not generated by any HW or SW error.
The operator can set four thresholds of any percentage for cpUsageRatio: notify
high 1/2 and notify low 1/2 which raise and clear the related alarms (202018 - The first
cpUsageRatio Quality of Service alarm has occurred / 202019 - The second cpUsageRatio Quality of Service alarm has occurred), respectively, when crossed. Furthermore,
the operator can determine an alarm severity for each of the relevant QoS alarms. All
values are related to call-processing resources of the Node B.
If many subscribers within one UTRAN cell use their UEs at the same time, a shortage
of HW resources in this cell may occur as a consequence and this alarm will be output.
Troubleshooting
Re-consider the current network design. If possible, modify the configuration of the adjacent cells so that the same area of this cell is covered by several Node Bs. This may
help to solve the lack of resources without any system crash.
Furthermore, contact the technical assistance center (TAC) to get support in isolating
the fault. For suitable preparation save the error symptoms as described in "Collect Info
for Assistance". Log files need to be analyzed and specific measures must be taken
which are out of the operators scope.
As soon as this QoS alarm is ceased, relevant threshold information will be displayed.

178

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

202020 - The first prachCrciFailures Quality of Service


alarm has occurred
Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

LocalCellE
qualityOfServiceAlarm
ThresholdCrossed
indeterminate

Error Description
The first prachCrciFailures threshold-crossing alarm was raised. This is a QoS alarm
which was not generated by any HW or SW error.
The operator can set four thresholds of any percentage for cpUsageRatio: notify
high 1/2 and notify low 1/2 which raise and clear the related alarms (202020 - The first
prachCrciFailures Quality of Service alarm has occurred / 202021 - The second prachCrciFailures Quality of Service alarm has occurred), respectively, when crossed. Furthermore, the operator can determine an alarm severity for each of the relevant QoS
alarms. All values are related to call-processing resources of the Node B.
If many subscribers within one UTRAN cell use their UEs at the same time, a shortage
of HW resources in this cell may occur as a consequence and this alarm will be output.
Troubleshooting
Re-consider the current network design. If possible, modify the configuration of the adjacent cells so that the same area of this cell is covered by several Node Bs. This may
help to solve the lack of resources without a system crash.
Furthermore, contact the technical assistance center (TAC) to get support in isolating
the fault. For suitable preparation save the error symptoms as described in "Collect Info
for Assistance". Log files need to be analyzed and specific measures must be taken
which are out of the operators scope.
As soon as this QoS alarm is ceased, relevant threshold information will be displayed.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

179

OML:Node B

Outputs
Node B

202021 - The second prachCrciFailures Quality of Service


alarm has occurred
Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

LocalCellE
qualityOfServiceAlarm
ThresholdCrossed
indeterminate

Error Description
The second prachCrciFailures threshold-crossing alarm was raised. This is a QoS alarm
which was not generated by any HW or SW error.
The operator can set four thresholds of any percentage for cpUsageRatio: notify
high 1/2 and notify low 1/2 which raise and clear the related alarms (202020 - The first
prachCrciFailures Quality of Service alarm has occurred / 202021 - The second prachCrciFailures Quality of Service alarm has occurred), respectively, when crossed. Furthermore, the operator can determine an alarm severity for each of the relevant QoS
alarms. All values are related to call-processing resources of the Node B.
If many subscribers within one UTRAN cell use their UEs at the same time, a shortage
of HW resources in this cell may occur as a consequence and this alarm will be output.
Troubleshooting
Re-consider the current network design. If possible, modify the configuration of the adjacent cells so that the same area of this cell is covered by several Node Bs. This may
help to solve the lack of resources without any system crash.
Furthermore, contact the technical assistance center (TAC) to get support in isolating
the fault. For suitable preparation save the error symptoms as described in "Collect Info
for Assistance". Log files need to be analyzed and specific measures must be taken
which are out of the operators scope.
As soon as this QoS alarm is ceased, relevant threshold information will be displayed.

180

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

202056 - Loss Of Signal on Physical Link


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

E1TTP, J1TTP, Stm1TP


communicationAlarm
LossOfSignal
major

Error Description
Loss of signal (LOS) indication has been received on a physical link E1, J1, T1 or
STM-1/OC-3 (according to reported MOC in the failure event report). This indicates that
the signal from the next device upstream is not present. This may be due to misconfiguration of the hardware at either end, faulty hardware at either end or due to a break in
the transmission medium between the two ends.
The following subsequent alarms may also be initiated:
202057 - Loss Of Frame on Physical Link
202058 - Loss Of Cell Delineation on Physical Link
202059 - Alarm Indication Signal on Physical Link
202060 - Remote Alarm Indication on Physical Link
202062 - Line Alarm Indication Signal Indication on STM1 Physical Link
202063 - Line Remote Defect Indication on STM1 Physical Link
202065 - Path Alarm Indication Signal on STM1 Physical Link
202072 - Alarm Indication Signal on an ATM VC
202075 - Alarm Indication Signal on an ATM VP
Troubleshooting
Usually the Node B is connected to the RNC or each other (Iub interface) via Link Equipment (LE) and in some rare cases by direct lines. If LE is involved the operation and
maintenance system of this network has to be used for getting information about the
state and status of the relevant network element (NE).
Depending on the applied configuration of the Node Bs like star, hub, cascade or loop
not only the reported Node B of this error message is affected but also subordinated
Node Bs.
Star configuration
Only the reported Node B
Hub configuration
If the hub Node B is the reporting one for a connection to the RNC:
For E1/J1/T1: the supplied Node B of the relevant E1/J1/T1 link will report AIS
For STM-1/OC-3: all supplied Node Bs will report AIS
Cascade configuration
All Node Bs in the chain downstream the LOS reporting Node B will initial an AIS error message for the relevant E1/J1/T1 link respectively all if the first Node B is reporting and connected to the RNC via STM-1/OC-3.
Loop configuration
The redundant path in the loop configuration will take over the traffic
To isolate the fault check for other error messages in the following order:
1. Is there also an equipment alarm of the Core Controller (CC) in the reporting Node B
present?

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

181

OML:Node B

Outputs
Node B

Using the ALARM View window of the LMT:


Click on the Alarm View button or use the shortcut key Ctrl-A
Use the filter and sort function to concentrate on CC alarms
If an equipment alarm of the CC is present try to fix this fault first which probably also
eliminates the LOS alarm.
2. Is the LE, which is connected to the relevant port, reporting an equipment alarm?
If an equipment alarm at the LE is present try to fix this fault first which probably
also eliminates the LOS alarm.
3. Check the cable connection

WARNING
To avoid damage to health, you must observe the regulations regarding protection
against radiation from laser devices (EN 60825 / IEC 60825). You must always use dedicated laser-protective goggles. Never look into open fiber-optic cable ends, as this may
damage your eyes.
Take special care if an optical STM-1/OC-3 line is used (see warning above)
Proper connection at the LE (good contact, clean optical connector)
Proper connection at the Node B (good contact, clean optical connector)
Undamaged cable between Node B and LE respectively other Node B or RNC
4. Check the OVPT or IUBCON
Electrical Iub lines (E1/J1/T1) are connected to the Node B using an OVPT (overvoltage protection and tracer module) equipped with surge arresters or an IUBCON
(Iub connector). Both are available for coax and symmetrical cables.
Check surge arresters at OVPT and replace a defective one if necessary
Replace OVPT or IUBCON if any other reason could not be found. Replacement
must be done according to the Maintenance Manual MMN:Node B.
Configuration mismatch?
Is the configuration of the relevant ports at either end in accordance with each other?
For Node B use the LMT to upload the nbDatabase and analyze the settings for the
relevant port
For LE the appropriate local maintenance system has to be used
If the misconfiguration can be identified as probable cause for the error report the alignment of the settings should clear the fault.

182

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

202057 - Loss Of Frame on Physical Link


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

E1TTP, J1TTP, Stm1TP


communicationAlarm
LossOfFrame
major

Error Description
Loss of frame (LOF) indication has been received on a physical link E1, J1, T1 or
STM-1/OC-3 (according to reported MOC in the failure event report).
Independent of the mode of CRC operation, this alarm indicates one of the following:
Basic frame synchronization has been lost on the transport interface between the
Node B and the next device upstream.
This may be due to misconfiguration of the hardware at either end, faulty hardware
at either end or problems on the transmission medium between the two ends.
Although both frame alignment is active and the reporting line is running, a great
number of CRC-4 errors occurred.
The following subsequent alarms may also be initiated:
202058 - Loss Of Cell Delineation on Physical Link
202059 - Alarm Indication Signal on Physical Link
202060 - Remote Alarm Indication on Physical Link
202062 - Line Alarm Indication Signal Indication on STM1 Physical Link
202063 - Line Remote Defect Indication on STM1 Physical Link
202065 - Path Alarm Indication Signal on STM1 Physical Link
202072 - Alarm Indication Signal on an ATM VC
202075 - Alarm Indication Signal on an ATM VP
Troubleshooting
Usually the Node B is connected to the RNC or each other (Iub interface) via Link Equipment (LE) and in some rare cases by direct lines. If LE is involved the operation and
maintenance system of this network has to be used for getting information about the
state and status of the relevant network element (NE).
Depending on the applied configuration of the Node Bs like star, hub, cascade or loop
not only the reported Node B of this error message is affected but also subordinated
Node Bs.
Star configuration
only the reported Node B
Hub configuration
if the hub Node B is the reporting one for a connection to the RNC:
for E1/J1/T1: the supplied Node B of the relevant E1/J1/T1 link will report AIS
for STM-1/OC-3: all supplied Node Bs will report AIS
Cascade configuration
all Node Bs in the chain downstream the LOF reporting Node B will initial an AIS error message for the relevant E1/J1/T1 link respectively all if the first Node B is reporting and connected to the RNC via STM-1/OC-3.
Loop configuration
the redundant path in the loop configuration will take over the traffic

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

183

OML:Node B

Outputs
Node B

To isolate the fault check for other error messages in the following order:
1. Is there also an equipment alarm of the Core Controller (CC) in the reporting Node B
present?
Using the ALARM View window of the LMT:
Click on the Alarm View button or use the shortcut key Ctrl-A
Use the filter and sort function to concentrate on CC alarms
If an equipment alarm of the CC is present try to fix this fault first which probably also
eliminates the LOF alarm.
2. Is the LE, which is connected to the relevant port, reporting an equipment alarm?
If an equipment alarm at the LE is present try to fix this fault first which probably
also eliminates the LOF alarm.
3. Check the cable connection

WARNING
To avoid damage to health, you must observe the regulations regarding protection
against radiation from laser devices (EN 60825 / IEC 60825). You must always use dedicated laser-protective goggles. Never look into open fiber-optic cable ends, as this may
damage your eyes.
Take special care if an optical STM-1/OC-3 line is used (see warning above)
Proper connection at the LE (good contact, clean optical connector)
Proper connection at the Node B (good contact, clean optical connector)
Undamaged cable between Node B and LE respectively other Node B or RNC
4. Check the OVPT or IUBCON
Electrical Iub lines (E1/J1/T1) are connected to the Node B using an OVPT (overvoltage protection and tracer module) equipped with surge arresters or an IUBCON
(Iub connector). Both are available for coax and symmetrical cables.
Check surge arresters at OVPT and replace a defective one if necessary
Replace OVPT or IUBCON if any other reason could not be found. Replacement
must be done according to the Maintenance Manual MMN:Node B.
Configuration mismatch?
Is the configuration of the relevant ports at either end in accordance with each other?
For Node B use the LMT to upload the nbDatabase and analyze the settings for the
relevant port
For LE the appropriate local maintenance system has to be used
If the misconfiguration can be identified as probable cause for the error report the alignment of the settings should clear the fault.

184

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

202058 - Loss Of Cell Delineation on Physical Link


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

E1TTP, J1TTP, Stm1TP


communicationAlarm
LossOfCellDelineation
major

Error Description
Loss of cell delineation (LCD) indication has been received on a physical link E1, J1, T1
or STM-1/OC-3 (according to reported MOC in the failure event report). This indicates
that ATM cells are not being delineated correctly and so cannot be extracted from the
received signal. This may be due to faulty hardware at either end or problems on the
transmission medium between the two ends.
The following subsequent alarms may also be initiated:
202072 - Alarm Indication Signal on an ATM VC
202075 - Alarm Indication Signal on an ATM VP
Troubleshooting
1. Is there also an equipment alarm of the Core Controller (CC) in the reporting Node B
present?
Using the ALARM View window of the LMT:
Click on the Alarm View button or use the shortcut key Ctrl-A
Use the filter and sort function to concentrate on CC alarms
If an equipment alarm of the CC is present try to fix this fault first which probably also
eliminates the LCD alarm.
2. Is the LE, which is connected to the relevant port, reporting an equipment alarm?
If an equipment alarm at the LE is present try to fix this fault first which probably
also eliminates the LCD alarm.
3. Check the cable connection

WARNING
To avoid damage to health, you must observe the regulations regarding protection
against radiation from laser devices (EN 60825 / IEC 60825). You must always use dedicated laser-protective goggles. Never look into open fiber-optic cable ends, as this may
damage your eyes.
Take special care if an optical STM-1/OC-3 line is used (see warning above)
Proper connection at the LE (good contact, clean optical connector)
Proper connection at the Node B (good contact, clean optical connector)
Undamaged cable between Node B and LE respectively other Node B or RNC
4. Check the OVPT or IUBCON
Electrical Iub lines (E1/J1/T1) are connected to the Node B using an OVPT (overvoltage protection and tracer module) equipped with surge arresters or an IUBCON
(Iub connector). Both are available for coax and symmetrical cables.
Check surge arresters at OVPT and replace a defective one if necessary
Replace OVPT or IUBCON if any other reason could not be found. Replacement
must be done according to the Maintenance Manual MMN:Node B.
5. Configuration mismatch
Is the configuration of the relevant ports at either end in accordance with each other?

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

185

OML:Node B

Outputs
Node B

for Node B use the LMT to upload the nbDatabase and analyze the settings for
the relevant port
for LE the appropriate local maintenance system has to be used
If the misconfiguration can be identified as probable cause for the error report the
alignment of the settings should clear the fault.
6. In case none of the proposed actions results in a fault clearance contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save the error symptoms as described in "Collect Info for Assistance". Log
files need to be analyzed and specific measures must be taken which are out of the
operators scope.

186

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

202059 - Alarm Indication Signal on Physical Link


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

E1TTP, J1TTP
communicationAlarm
AlarmIndicationSignal
major

Error Description
Alarm indication signal (AIS) indication has been received on a physical link E1, J1/, or
T1 (according to reported MOC in the failure event report). Indicates that a problem has
been detected upstream from the Node B on the physical link reporting the alarm and
transmission to the Node B from that direction has probably been interrupted on this link.
This alarm is triggered by one of the following preceded alarms from an upstream NE in
the supervision of the RC:
202056 - Loss Of Signal on Physical Link
202057 - Loss Of Frame on Physical Link
or from Link Equipment (LE) in upstream direction:
Loss Of Signal (LOS)
Loss Of Frame (LOF)
The following subsequent alarms may also be initiated:
202060 - Remote Alarm Indication on Physical Link
202072 - Alarm Indication Signal on an ATM VC
202075 - Alarm Indication Signal on an ATM VP
Troubleshooting
Because this error message is a consequence of a preceded alarm from an upstream
NE the troubleshooting has to start with investigation of the trigger alarm. Find the relevant alarm in the list of the ALARM View window of the LMT:
Click on the Alarm View button or use the shortcut key Ctrl-A
Use the filter and sort function to concentrate on the relevant alarms
For troubleshooting instructions refer to:
202056 - Loss Of Signal on Physical Link
202057 - Loss Of Frame on Physical Link
LE caused alarms are handled accordingly.
After solving the problem which initiated the trigger alarm this error message will also be
cleared.
If the fault cannot be cleared, contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save the error symptoms as described
in "Collect Info for Assistance". Log files need to be analyzed and specific measures
must be taken which are out of the operators scope.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

187

OML:Node B

Outputs
Node B

202060 - Remote Alarm Indication on Physical Link


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

E1TTP, J1TTP
communicationAlarm
RemoteAlarmIndication
major

Error Description
Remote alarm indication (RAI) indication has been received on a physical link E1, J1, or
T1 (according to reported MOC in the failure event report). Indicates that a problem has
been detected downstream from the Node B on the physical link reporting the alarm and
reception from the Node B in that direction has been probably interrupted on this link.
This may be due to faulty hardware at either end or problems on the transmission medium between the two ends.
This alarm is triggered by one of the following preceded alarms from an downstream NE
in the supervision of the RC:
202056 - Loss Of Signal on Physical Link
202057 - Loss Of Frame on Physical Link
or from Link Equipment (LE) in downstream direction:
Loss Of Signal (LOS)
Loss Of Frame (LOF)
The following subsequent alarms may also be initiated:
202059 - Alarm Indication Signal on Physical Link
202072 - Alarm Indication Signal on an ATM VC
202075 - Alarm Indication Signal on an ATM VP
Troubleshooting
Because this error message is a consequence of a preceded alarm from an upstream
NE the troubleshooting has to start with investigation of the trigger alarm. Find the relevant alarm in the list of the ALARM View window of the LMT:
Click on the Alarm View button or use the shortcut key Ctrl-A
Use the filter and sort function to concentrate on the relevant alarms
For troubleshooting instructions refer to:
202056 - Loss Of Signal on Physical Link
202057 - Loss Of Frame on Physical Link
LE caused alarms are handled accordingly.
After solving the problem which initiated the trigger alarm this error message will also be
cleared.
If the fault cannot be cleared, contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save the error symptoms as described
in "Collect Info for Assistance". Log files need to be analyzed and specific measures
must be taken which are out of the operators scope.

188

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

202061 - Loss of Multi Frame Alarm Indication on E1


Physical Link
Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

E1TTP
communicationAlarm
LossOfMultiFrame
major

Error Description
Loss of multi frame alarm indication (LOMF) indication has been received on an E1
physical link. This indicates that multiframe synchronization has been lost on the E1
transport interface between the Node B and the next device upstream. This may be due
to misconfiguration of the hardware at either end, faulty hardware at either end or problems on the transmission medium between the two ends.
The 202061 - Loss of Multi Frame Alarm Indication on E1 Physical Link alarm may be
caused by the following:
The Node Bs E1TTP managed objects attribute crcOperationMode, which indicates
the mode of CRC operation, is set to its default value crcForced whereas the frame format for the RNC is set to 0 meaning that the CRC is disabled. Therefore, the E1TTPs
OST/AVS combination changes to disabled/failed.
If the crcOperationMode is set to crcAutomatic, refer to the description of the 202098
- CRC4 not used by FE reported on E1TTP alarm and follow the alarms troubleshooting.
Troubleshooting
1. Is there also an equipment alarm of the Core Controller (CC) in the reporting Node B
present?
Using the ALARM View window of the LMT:
Click on the Alarm View button or use the shortcut key Ctrl-A
Use the filter and sort function to concentrate on CC alarms
If an equipment alarm of the CC is present try to fix this fault first which probably also
eliminates the LOMF alarm.
2. Is the LE, which is connected to the relevant port, reporting an equipment alarm?
If an equipment alarm at the LE is present try to fix this fault first which probably
also eliminates the LOMF alarm.
3. Check the cable connection

WARNING
To avoid damage to health, you must observe the regulations regarding protection
against radiation from laser devices (EN 60825 / IEC 60825). You must always use dedicated laser-protective goggles. Never look into open fiber-optic cable ends, as this may
damage your eyes.

Take special care if an optical STM-1/OC-3 line is used (see warning above)
Proper connection at the LE (good contact, clean optical connector)
Proper connection at the Node B (good contact, clean optical connector)
Undamaged cable between Node B and LE respectively other Node B or RNC

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

189

OML:Node B

Outputs
Node B

4. Check the OVPT or IUBCON


Electrical Iub lines (E1/J1/T1) are connected to the Node B using an OVPT (overvoltage protection and tracer module) equipped with surge arresters or an IUBCON
(Iub connector). Both are available for coax and symmetrical cables.
Check surge arresters at OVPT and replace a defective one if necessary
Replace OVPT or IUBCON if any other reason could not be found. Replacement
must be done according to the Maintenance Manual MMN:Node B.
5. Configuration mismatch
Is the configuration of the relevant ports at either end in accordance with each other?
For Node B use the LMT to upload the nbDatabase and analyze the settings for
the relevant port
For LE the appropriate local maintenance system has to be used
If the misconfiguration can be identified as probable cause for the error report the
alignment of the settings should clear the fault.
6. In case none of the proposed actions results in a fault clearance contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save the error symptoms as described in "Collect Info for Assistance". Log
files need to be analyzed and specific measures must be taken which are out of the
operators scope.

190

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

202062 - Line Alarm Indication Signal Indication on STM1


Physical Link
Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Stm1TP
communicationAlarm
AlarmIndicationSignal
major

Error Description
Line alarm indication signal (L-AIS) indication has been received on a STM-1/OC-3
physical link. Indicates that a problem (e.g. LOS, LOF, LOP) has been detected upstream from the Node B on the STM-1/OC-3 link reporting the alarm and transmission
to the Node B from that direction has probably been interrupted on this link.
This alarm is triggered by one of the following preceded alarms from an upstream NE in
the supervision of the RC:
202056 - Loss Of Signal on Physical Link
202057 - Loss Of Frame on Physical Link
202064 - Path Loss of Pointer Indication on STM1 Physical Link
or from Link Equipment (LE) in upstream direction:
Loss Of Signal (LOS)
Loss Of Frame (LOF)
Loss Of Pointer (LOP)
The following subsequent alarms may also be initiated:
202063 - Line Remote Defect Indication on STM1 Physical Link
202065 - Path Alarm Indication Signal on STM1 Physical Link
202072 - Alarm Indication Signal on an ATM VC
202075 - Alarm Indication Signal on an ATM VP
Troubleshooting
Because this error message is a consequence of a preceded alarm from an upstream
NE the troubleshooting has to start with investigation of the trigger alarm. Find the relevant alarm in the list of the ALARM View window of the LMT:
Click on the Alarm View button or use the shortcut key Ctrl-A
Use the filter and sort function to concentrate on the relevant alarms
For troubleshooting instructions refer to:
202056 - Loss Of Signal on Physical Link
202057 - Loss Of Frame on Physical Link
202064 - Path Loss of Pointer Indication on STM1 Physical Link
LE caused alarms are handled accordingly.
After solving the problem which initiated the trigger alarm this error message will also be
cleared.
If the fault cannot be cleared, contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save the error symptoms as described
in "Collect Info for Assistance". Log files need to be analyzed and specific measures
must be taken which are out of the operators scope.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

191

OML:Node B

Outputs
Node B

202063 - Line Remote Defect Indication on STM1 Physical


Link
Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Stm1TP
communicationAlarm
RemoteAlarmIndicator
major

Error Description
Line remote defect indication (L-RDI) indication has been received on an STM-1/OC-3
physical link. Indicates that a problem has been detected downstream from the Node B
on the STM-1/OC-3 link reporting the alarm and reception from the Node B in that direction has been probably interrupted on this link. This may be due to faulty hardware at
either end or problems on the transmission medium between the two ends.
This alarm is triggered by one of the following preceded alarms from an downstream NE
in the supervision of the RC:
202056 - Loss Of Signal on Physical Link
202057 - Loss Of Frame on Physical Link
202064 - Path Loss of Pointer Indication on STM1 Physical Link
202065 - Path Alarm Indication Signal on STM1 Physical Link
or from Link Equipment (LE) in downstream direction:
Loss Of Signal (LOS)
Loss Of Frame (LOF)
Loss Of Pointer (LOP)
The following subsequent alarms may also be initiated:
202062 - Line Alarm Indication Signal Indication on STM1 Physical Link
202072 - Alarm Indication Signal on an ATM VC
202075 - Alarm Indication Signal on an ATM VP
Troubleshooting
Because this error message is a consequence of a preceded alarm from an upstream
NE the troubleshooting has to start with investigation of the trigger alarm. Find the relevant alarm in the list of the ALARM View window of the LMT:
Click on the Alarm View button or use the shortcut key Ctrl-A
Use the filter and sort function to concentrate on the relevant alarms
For troubleshooting instructions refer to:
202056 - Loss Of Signal on Physical Link
202057 - Loss Of Frame on Physical Link
202064 - Path Loss of Pointer Indication on STM1 Physical Link
202065 - Path Alarm Indication Signal on STM1 Physical Link
LE caused alarms are handled accordingly.
After solving the problem which initiated the trigger alarm this error message will also be
cleared.
If the fault cannot be cleared, contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save the error symptoms as described

192

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

in "Collect Info for Assistance". Log files need to be analyzed and specific measures
must be taken which are out of the operators scope.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

193

OML:Node B

Outputs
Node B

202064 - Path Loss of Pointer Indication on STM1 Physical


Link
Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Stm1TP
communicationAlarm
LossOfPointer
major

Error Description
Path loss of pointer (P-LOP) indication has been received on an STM-1/OC-3 physical
link. The pointer enables the STM-1/OC-3 device on the Node B to locate the payload
within the signal. If the Node B STM-1/OC-3 interface has received an invalid path pointer, it will declare a loss of pointer condition. Because the STM-1/OC-3 interface cannot
determine where the payload starts, all downstream traffic will be lost as long as the condition persists. This may be due to faulty hardware at either end or problems on the
transmission medium between the two ends.
This alarm may trigger the following subsequent alarms:
202065 - Path Alarm Indication Signal on STM1 Physical Link
202066 - Path Remote Defect Indication on STM1 Physical Link
Troubleshooting
1. Is there also an equipment alarm of the Core Controller (CC) in the reporting Node B
present?
Using the ALARM View window of the LMT:
Click on the Alarm View button or use the shortcut key Ctrl-A
Use the filter and sort function to concentrate on CC alarms
If an equipment alarm of the CC is present try to fix this fault first which probably also
eliminates the P-LOP alarm.
2. Is the LE, which is connected to the relevant port, reporting an equipment alarm?
If an equipment alarm at the LE is present try to fix this fault first which probably
also eliminates the P-LOP alarm.
3. Check the cable connection

WARNING
To avoid damage to health, you must observe the regulations regarding protection
against radiation from laser devices (EN 60825 / IEC 60825). You must always use dedicated laser-protective goggles. Never look into open fiber-optic cable ends, as this may
damage your eyes.
Take special care if an optical STM-1/OC-3 line is used (see warning above)
Proper connection at the LE (good contact, clean optical connector)
Proper connection at the Node B (good contact, clean optical connector)
Undamaged cable between Node B and LE respectively other Node B or RNC
4. Check the OVPT or IUBCON
Electrical Iub lines (E1/J1/T1) are connected to the Node B using an OVPT (overvoltage protection and tracer module) equipped with surge arresters or an IUBCON
(Iub connector). Both are available for coax and symmetrical cables.
Check surge arresters at OVPT and replace a defective one if necessary

194

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

Replace OVPT or IUBCON if any other reason could not be found. Replacement
must be done according to the Maintenance Manual MMN:Node B.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

195

OML:Node B

Outputs
Node B

5. In case none of the proposed actions results in a fault clearance contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save the error symptoms as described in "Collect Info for Assistance". Log
files need to be analyzed and specific measures must be taken which are out of the
operators scope.

196

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

202065 - Path Alarm Indication Signal on STM1 Physical


Link
Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Stm1TP
communicationAlarm
AlarmIndicationSignal
major

Error Description
A Path Alarm Indication Signal (P-AIS) has been received on an STM-1/OC-3 physical
link.
The P-AIS indicates the following:
At least one of the following problems has been detected upstream from the Node B
on the STM-1/OC-3 link reporting this alarm:
Loss of Signal (LOS)
Loss of Frame (LOF)
Path Loss of Pointer (P-LOP)
Line Alarm Indication Signal (L-AIS)
Transmission from upstream direction to the Node B has probably been interrupted
on the reporting link.
The 202065 - Path Alarm Indication Signal on STM1 Physical Link alarm is triggered
by one of the following preceded alarms reported by an upstream NE:
202056 - Loss Of Signal on Physical Link
202057 - Loss Of Frame on Physical Link
202062 - Line Alarm Indication Signal Indication on STM1 Physical Link
202064 - Path Loss of Pointer Indication on STM1 Physical Link
Or by LOS, LOF, P-LOP, or L-AIS from link equipment (LE) in upstream direction.
Furthermore, as a consequence of this alarm, the following alarms may be triggered:
202063 - Line Remote Defect Indication on STM1 Physical Link
202066 - Path Remote Defect Indication on STM1 Physical Link
202072 - Alarm Indication Signal on an ATM VC
202075 - Alarm Indication Signal on an ATM VP
Troubleshooting
Due to the fact that this error message is a consequence of a preceded alarm from an
upstream NE, troubleshooting has to start with investigation of the trigger alarm(s). Find
the relevant trigger alarm in the ALARM View window of the LMT:
1. Click on the Alarm View button or use the shortkey Ctrl-A.
2. Use the filter and sort function to concentrate on the following relevant alarms:
202056 - Loss Of Signal on Physical Link
202057 - Loss Of Frame on Physical Link
202062 - Line Alarm Indication Signal Indication on STM1 Physical Link
202064 - Path Loss of Pointer Indication on STM1 Physical Link
3. Proceed according to the troubleshooting of the trigger alarm.
Alarms caused by LE are handled accordingly.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

197

OML:Node B

Outputs
Node B

After having solved the problem which initiated the trigger alarm, this error message will
also be cleared.
If the fault could not be cleared yet, contact the technical assistance center (TAC) to get
support in isolating the fault. For suitable preparation save the error symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are out of the operators scope.

198

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

202066 - Path Remote Defect Indication on STM1 Physical


Link
Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Stm1TP
communicationAlarm
RemoteAlarmIndication
major

Error Description
A Path Remote Defect Indication (P-RDI) indication has been received on an
STM-1/OC-3 physical link.
The P-RDI indicates the following:
At least one of the following problems has been detected upstream from the Node B
on the STM-1/OC-3 link reporting this alarm:
Path Loss of Pointer (P-LOP)
Path Alarm Indication Signal (P-AIS)
Transmission from upstream direction to the Node B has probably been interrupted
on the reporting link.
The 202066 - Path Remote Defect Indication on STM1 Physical Link alarm is triggered
by one of the following preceded alarms reported by an upstream NE:
202064 - Path Loss of Pointer Indication on STM1 Physical Link
202065 - Path Alarm Indication Signal on STM1 Physical Link
Or by P-LOP or P-AIS from link equipment (LE) in upstream direction.
Furthermore, as a consequence of this alarm, the following alarms may be triggered:
202072 - Alarm Indication Signal on an ATM VC
202075 - Alarm Indication Signal on an ATM VP
Troubleshooting
Due to the fact that this error message is a consequence of a preceded alarm from an
upstream NE, troubleshooting has to start with investigation of the trigger alarm(s). Find
the relevant trigger alarm in the ALARM View window of the LMT:
1. Click on the Alarm View button or use the shortkey Ctrl-A.
2. Use the filter and sort function to concentrate on the following relevant alarms:
202064 - Path Loss of Pointer Indication on STM1 Physical Link
202065 - Path Alarm Indication Signal on STM1 Physical Link
3. Proceed according to the troubleshooting of the trigger alarm.
Alarms caused by LE are handled accordingly.
After having solved the problem which initiated the trigger alarm, this error message will
also be cleared.
If the fault could not be cleared yet, contact the technical assistance center (TAC) to get
support in isolating the fault. For suitable preparation save the error symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are out of the operators scope.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

199

OML:Node B

Outputs
Node B

202068 - Signal Label Mismatch Indication on STM1 Physical Link


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Stm1TP
communicationAlarm
SignalLabelMismatch
minor

Error Description
Signal label mismatch (SLM) indication has been received on an STM-1/OC-3 physical
link. This may be because of corruptions on the STM-1/OC-3 line or incorrect configuration at the transmitting end.
Troubleshooting
Is the configuration of the relevant ports at either end in accordance with each other?
For Node B use the LMT to upload the nbDatabase and analyze the settings for the
relevant port
For LE the appropriate local maintenance system has to be used
If the misconfiguration can be identified as probable cause for the error report the alignment of the settings should clear the fault.
In case none of the proposed actions results in a fault clearance contact the technical
assistance center (TAC) to get support in isolating the fault. For suitable preparation
save the error symptoms as described in "Collect Info for Assistance". Log files need to
be analyzed and specific measures must be taken which are out of the operators scope.

200

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

202070 - Signal Degrade Indication on STM1 Physical Link


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Stm1TP
communicationAlarm
DegradedSignal
minor

Error Description
Signal degrade (SD) indication has been received on an STM-1/OC-3 physical link. This
indicates that the bit error rate on the received STM-1/OC-3 signal has exceeded the
threshold set in the signalDegradeThreshold configuration attribute. This may be due to
faulty hardware at either end or problems on the transmission medium between the two
ends.
Troubleshooting
1. Is there also an equipment alarm of the Core Controller (CC) in the reporting Node B
present?
Using the ALARM View window of the LMT:
Click on the Alarm View button or use the shortcut key Ctrl-A
Use the filter and sort function to concentrate on CC alarms
If an equipment alarm of the CC is present try to fix this fault first which probably also
eliminates the SD alarm.
2. Is the LE, which is connected to the relevant port, reporting an equipment alarm?
If an equipment alarm at the LE is present try to fix this fault first which probably
also eliminates the SD alarm.
3. Check the cable connection

WARNING
To avoid damage to health, you must observe the regulations regarding protection
against radiation from laser devices (EN 60825 / IEC 60825). You must always use dedicated laser-protective goggles. Never look into open fiber-optic cable ends, as this may
damage your eyes.
Take special care if an optical STM-1/OC-3 line is used (see warning above)
Proper connection at the LE (good contact, clean optical connector)
Proper connection at the Node B (good contact, clean optical connector)
Undamaged cable between Node B and LE respectively other Node B or RNC
4. Check the OVPT or IUBCON
Electrical Iub lines (E1/J1/T1) are connected to the Node B using an OVPT (overvoltage protection and tracer module) equipped with surge arresters or an IUBCON
(Iub connector). Both are available for coax and symmetrical cables.
Check surge arresters at OVPT and replace a defective one if necessary
Replace OVPT or IUBCON if any other reason could not be found. Replacement
must be done according to the Maintenance Manual MMN:Node B.
5. In case none of the proposed actions results in a fault clearance contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save the error symptoms as described in "Collect Info for Assistance". Log
files need to be analyzed and specific measures must be taken which are out of the
operators scope.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

201

OML:Node B

Outputs
Node B

202071 - Excessive Bit Error Rate Indication on STM1


Physical Link
Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Stm1TP
communicationAlarm
ExcessiveBER
major

Error Description
Excessive bit error rate (EBER) indication has been received on an STM-1/OC-3 physical link. This indicates that the bit error rate on the received STM-1/OC-3 signal has exceeded the threshold set in the signalFailThreshold configuration attribute. This may be
due to faulty hardware at either end or problems on the transmission medium between
the two ends.
Troubleshooting
1. Is there also an equipment alarm of the Core Controller (CC) in the reporting Node B
present?
Using the ALARM View window of the LMT:
Click on the Alarm View button or use the shortcut key Ctrl-A
Use the filter and sort function to concentrate on CC alarms
If an equipment alarm of the CC is present try to fix this fault first which probably also
eliminates the EBER alarm.
2. Is the LE, which is connected to the relevant port, reporting an equipment alarm?
If an equipment alarm at the LE is present try to fix this fault first which probably
also eliminates the EBER alarm.
3. Check the cable connection

WARNING
To avoid damage to health, you must observe the regulations regarding protection
against radiation from laser devices (EN 60825 / IEC 60825). You must always use dedicated laser-protective goggles. Never look into open fiber-optic cable ends, as this may
damage your eyes.
Take special care if an optical STM-1/OC-3 line is used (see warning above)
Proper connection at the LE (good contact, clean optical connector)
Proper connection at the Node B (good contact, clean optical connector)
Undamaged cable between Node B and LE respectively other Node B or RNC
4. Check the OVPT or IUBCON
Electrical Iub lines (E1/J1/T1) are connected to the Node B using an OVPT (overvoltage protection and tracer module) equipped with surge arresters or an IUBCON
(Iub connector). Both are available for coax and symmetrical cables.
Check surge arresters at OVPT and replace a defective one if necessary
Replace OVPT or IUBCON if any other reason could not be found. Replacement
must be done according to the Maintenance Manual MMN:Node B.

202

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

5. If none of the proposed actions results in a fault clearance contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation
save the error symptoms as described in "Collect Info for Assistance". Log files
need to be analyzed and specific measures must be taken which are out of the operators scope.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

203

OML:Node B

Outputs
Node B

202072 - Alarm Indication Signal on an ATM VC


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

VcTTP
communicationAlarm
AlarmIndicationSignal
minor

Error Description
An alarm indication signal (AIS) indication has been received on an ATM VC. This indicates that an alarm condition has been detected upstream from the Node B and the
equipment that has detected it is indicating a problem to equipment downstream of it.
The ATM cell stream on the affected VC will probably have been interrupted.
This alarm is triggered by one of the following preceded alarms from an upstream NE in
the supervision of the RC:
202056 - Loss Of Signal on Physical Link
202057 - Loss Of Frame on Physical Link
202058 - Loss Of Cell Delineation on Physical Link
202065 - Path Alarm Indication Signal on STM1 Physical Link
202066 - Path Remote Defect Indication on STM1 Physical Link
or from Link Equipment (LE) in upstream direction:
Loss Of Signal (LOS)
Loss Of Frame (LOF)
The following subsequent alarms may also be initiated:
202073 - Remote Defect Indication on an ATM VC
202075 - Alarm Indication Signal on an ATM VP
202076 - Remote Defect Indication on an ATM VP
Troubleshooting
Because this error message is a consequence of a preceded alarm from an upstream
NE the troubleshooting has to start with investigation of the trigger alarm. Find the relevant alarm in the list of the ALARM View window of the LMT:
Click on the Alarm View button or use the shortcut key Ctrl-A
Use the filter and sort function to concentrate on the relevant alarms
For troubleshooting instructions refer to:
202056 - Loss Of Signal on Physical Link
202057 - Loss Of Frame on Physical Link
202058 - Loss Of Cell Delineation on Physical Link
202065 - Path Alarm Indication Signal on STM1 Physical Link
202066 - Path Remote Defect Indication on STM1 Physical Link
LE caused alarms are handled accordingly.
After solving the problem which initiated the trigger alarm this error message will also be
cleared.
If the fault cannot be cleared, contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save the error symptoms as described
in "Collect Info for Assistance". Log files need to be analyzed and specific measures
must be taken which are out of the operators scope.

204

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

202073 - Remote Defect Indication on an ATM VC


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

VcTTP
communicationAlarm
RemoteAlarmIndication
minor

Error Description
A remote defect indication (RDI) indication has been received on an ATM VC. This indicates that an alarm condition has been detected downstream from the Node B and the
equipment that has detected it is indicating a problem to equipment upstream of it. The
ATM cell stream on the affected VC will probably have been interrupted.
This alarm is triggered by one of the following preceded alarms from an downstream NE
in the supervision of the RC:
202056 - Loss Of Signal on Physical Link
202057 - Loss Of Frame on Physical Link
202058 - Loss Of Cell Delineation on Physical Link
or from Link Equipment (LE) in downstream direction:
Loss Of Signal (LOS)
Loss Of Frame (LOF)
The following subsequent alarms may also be initiated:
202072 - Alarm Indication Signal on an ATM VC
202075 - Alarm Indication Signal on an ATM VP
202076 - Remote Defect Indication on an ATM VP
Troubleshooting
Because this error message is a consequence of a preceded alarm from an upstream
NE the troubleshooting has to start with investigation of the trigger alarm. Find the relevant alarm in the list of the ALARM View window of the LMT:
Click on the Alarm View button or use the shortcut key Ctrl-A
Use the filter and sort function to concentrate on the relevant alarms
For troubleshooting instructions refer to:
202056 - Loss Of Signal on Physical Link
202057 - Loss Of Frame on Physical Link
202058 - Loss Of Cell Delineation on Physical Link
LE caused alarms are handled accordingly.
After solving the problem which initiated the trigger alarm this error message will also be
cleared.
If the fault cannot be cleared, contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save the error symptoms as described
in "Collect Info for Assistance". Log files need to be analyzed and specific measures
must be taken which are out of the operators scope.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

205

OML:Node B

Outputs
Node B

202074 - SSCOP Failure Indication on an ATM VC used by


ALCAP or NBAP
Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

VcTTP
communicationAlarm
SscopFailure
warning

Error Description
A SAAL failure has been received on an ATM VC used for ALCAP or NBAP signaling.
This may be only a temporary failure from which the link will have recovered by itself
(e.g. by automatic retransmission). Persistent reports of this kind may be due to hardware or software failure at either end or problems on the transmission medium between
the two ends.
Troubleshooting
1. Is there also an equipment alarm of the Core Controller (CC) in the reporting Node B
present?
Using the ALARM View window of the LMT:
Click on the Alarm View button or use the shortcut key Ctrl-A
Use the filter and sort function to concentrate on CC alarms
If an equipment alarm of the CC is present try to fix this fault first which probably also
eliminates this alarm.
2. Is the LE, which is connected to the relevant port, reporting an equipment alarm?
If an equipment alarm at the LE is present try to fix this fault first which probably
also eliminates this alarm.
3. Check the cable connection

WARNING
To avoid damage to health, you must observe the regulations regarding protection
against radiation from laser devices (EN 60825 / IEC 60825). You must always use dedicated laser-protective goggles. Never look into open fiber-optic cable ends, as this may
damage your eyes.
Take special care if an optical STM-1/OC-3 line is used (see warning above)
Proper connection at the LE (good contact, clean optical connector)
Proper connection at the Node B (good contact, clean optical connector)
Undamaged cable between Node B and LE respectively other Node B or RNC
4. Check the OVPT or IUBCON
Electrical Iub lines (E1/J1/T1) are connected to the Node B using an OVPT (overvoltage protection and tracer module) equipped with surge arresters or an IUBCON
(Iub connector). Both are available for coax and symmetrical cables.
Check surge arresters at OVPT and replace a defective one if necessary
Replace OVPT or IUBCON if any other reason could not be found. Replacement
must be done according to the Maintenance Manual MMN:Node B.

206

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

5. In case none of the proposed actions results in a fault clearance contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save the error symptoms as described in "Collect Info for Assistance". Log
files need to be analyzed and specific measures must be taken which are out of the
operators scope.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

207

OML:Node B

Outputs
Node B

202075 - Alarm Indication Signal on an ATM VP


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

VpTTP
communicationAlarm
AlarmIndicationSignal
minor

Error Description
An alarm indication signal (AIS) indication has been received on an ATM VP. This indicates that an alarm condition has been detected upstream from the Node B and the
equipment that has detected it is indicating a problem to equipment downstream of it.
The ATM cell stream on the affected VP will probably have been interrupted.
This alarm is triggered by one of the following preceded alarms from an upstream NE in
the supervision of the RC:
202056 - Loss Of Signal on Physical Link
202057 - Loss Of Frame on Physical Link
202058 - Loss Of Cell Delineation on Physical Link
202065 - Path Alarm Indication Signal on STM1 Physical Link
202066 - Path Remote Defect Indication on STM1 Physical Link
or from Link Equipment (LE) in upstream direction:
Loss Of Signal (LOS)
Loss Of Frame (LOF)
The following subsequent alarms may also be initiated:
202072 - Alarm Indication Signal on an ATM VC
202073 - Remote Defect Indication on an ATM VC
202076 - Remote Defect Indication on an ATM VP
Troubleshooting
Because this error message is a consequence of a preceded alarm from an upstream
NE the troubleshooting has to start with investigation of the trigger alarm. Find the relevant alarm in the list of the ALARM View window of the LMT:
Click on the Alarm View button or use the shortcut key Ctrl-A
Use the filter and sort function to concentrate on the relevant alarms
For troubleshooting instructions refer to:
202056 - Loss Of Signal on Physical Link
202057 - Loss Of Frame on Physical Link
202058 - Loss Of Cell Delineation on Physical Link
202065 - Path Alarm Indication Signal on STM1 Physical Link
202066 - Path Remote Defect Indication on STM1 Physical Link
LE caused alarms are handled accordingly.
After solving the problem which initiated the trigger alarm this error message will also be
cleared.
If the fault cannot be cleared, contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save the error symptoms as described
in "Collect Info for Assistance". Log files need to be analyzed and specific measures
must be taken which are out of the operators scope.

208

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

202076 - Remote Defect Indication on an ATM VP


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

VpTTP
communicationAlarm
RemoteAlarmIndication
minor

Error Description
A remote defect indication (RDI) indication has been received on an ATM VP. This indicates that an alarm condition has been detected downstream from the Node B and the
equipment that has detected it is indicating a problem to equipment upstream of it. The
ATM cell stream on the affected VP will probably have been interrupted.
This alarm is triggered by one of the following preceded alarms from an downstream NE
in the supervision of the RC:
202056 - Loss Of Signal on Physical Link
202057 - Loss Of Frame on Physical Link
202058 - Loss Of Cell Delineation on Physical Link
or from Link Equipment (LE) in downstream direction:
Loss Of Signal (LOS)
Loss Of Frame (LOF)
The following subsequent alarms may also be initiated:
202072 - Alarm Indication Signal on an ATM VC
202073 - Remote Defect Indication on an ATM VC
202075 - Alarm Indication Signal on an ATM VP
Troubleshooting
Because this error message is a consequence of a preceded alarm from an upstream
NE the troubleshooting has to start with investigation of the trigger alarm. Find the relevant alarm in the list of the ALARM View window of the LMT:
Click on the Alarm View button or use the shortcut key Ctrl-A
Use the filter and sort function to concentrate on the relevant alarms
For troubleshooting instructions refer to:
202056 - Loss Of Signal on Physical Link
202057 - Loss Of Frame on Physical Link
202058 - Loss Of Cell Delineation on Physical Link
LE caused alarms are handled accordingly.
After solving the problem which initiated the trigger alarm this error message will also be
cleared.
If the fault cannot be cleared, contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save the error symptoms as described
in "Collect Info for Assistance". Log files need to be analyzed and specific measures
must be taken which are out of the operators scope.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

209

OML:Node B

Outputs
Node B

202077 - ALCAP PVC Out Of Service Indication


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

VcTTP
equipmentAlarm
LinkFailure
major

Error Description
The signaling protocol (STC) used by ALCAP has indicated that the connection is out of
service. This may be due to traffic congestion or a failure in the network or because the
far end is not configured. STC will repeatedly attempt to reconnect and will indicate
when the connection is in service.
Troubleshooting
Contact the technical assistance center (TAC) to get support in isolating the fault. For
suitable preparation save the error symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are
out of the operators scope.

210

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

202078 - Loss Of Delay Synchronization on IMA Link


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

ImaLink
communicationAlarm
VendorSpecific
minor

Error Description

NOTE
If an IMA group has been configured, however, not being operational during start-up,
the Node B possibly restarts some minutes after start-up.
A loss of delay synchronization (LODS) defect is reported when the link differential delay
between the link and the other links in the group is over the tolerable link differential delay (as defined by the configuration attribute imaGroupDiffDelayMax). If this alarm occurs then the ImaGroup will automatically cease transmitting on the link and (assuming
that there are sufficient good links for the Group to remain Operational) continue to operate using the remaining good links.
Troubleshooting
Contact the technical assistance center (TAC) to get support in isolating the fault. For
suitable preparation save the error symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are
out of the operators scope.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

211

OML:Node B

Outputs
Node B

202079 - Loss Of IMA Frame on IMA Link


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

ImaLink
communicationAlarm
VendorSpecific
minor

Error Description

NOTE
If an IMA group has been configured, however, not being operational during start-up,
the Node B possibly restarts some minutes after start-up.
The LIF (Loss of IMA Frame) defect is the occurrence of persistent OIF (Out of IMA
Frame) anomalies for at least 2 IMA frames. This indicates that the IMA Frame synchronisation has been lost. If this alarm occurs then the ImaGroup will automatically cease
transmitting on the link and (assuming that there are sufficient good links for the Group
to remain Operational) continue to operate using the remaining good links.
Troubleshooting
Contact the technical assistance center (TAC) to get support in isolating the fault. For
suitable preparation save the error symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are
out of the operators scope.

212

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

202080 - Remote Failure Indicator on IMA Link


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

ImaLink
communicationAlarm
VendorSpecific
minor

Error Description
Persistence of an RDI-IMA defect at the NE. An RDI-IMA is when one of the available
remote defect indicators (including IMA link specific defect) is indicated in the link related
Link Information field. This indicates that the IMA Link at the far end has detected a defect and has reported it to the near end. If this alarm occurs then the ImaGroup will automatically cease transmitting on the link and (assuming that there are sufficient good
links for the Group to remain Operational) continue to operate using the remaining good
links.
Troubleshooting
Contact the technical assistance center (TAC) to get support in isolating the fault. For
suitable preparation save the error symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are
out of the operators scope.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

213

OML:Node B

Outputs
Node B

202081 - IMA Tx link is detected as mis-connected


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

ImaLink
communicationAlarm
VendorSpecific
minor

Error Description
TX link is detected as mis-connected. This is reported when the IMA unit has determined
that the Tx link is not connected to the same FE IMA unit as the other TX links in the
group. This condition will be detected by the Test Pattern Procedure.
Troubleshooting
Check the cable connections.

214

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

202082 - IMA Rx link is detected as mis-connected


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

ImaLink
communicationAlarm
VendorSpecific
minor

Error Description
RX link is detected as mis-connected. This is reported when the IMA unit has determined that the Rx link is not connected to the same FE IMA unit as the other Rx links in
the group. This condition will be detected by the Test Pattern Procedure.
Troubleshooting
Check the cable connections.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

215

OML:Node B

Outputs
Node B

202083 - Tx fault declared at the NE on IMA Link


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

ImaLink
communicationAlarm
VendorSpecific
minor

Error Description
Implementation specific TX fault declared at the NE. This alarm indication that a hardware specific defect has been detected in the Tx direction on one link of the IMAGroup.
If this alarm occurs then the ImaGroup will automatically cease transmitting on the link
and (assuming that there are sufficient good links for the Group to remain Operational)
continue to operate using the remaining good links. This alarm is likely to be due to faulty
hardware at the near end.
Troubleshooting
Contact the technical assistance center (TAC) to get support in isolating the fault. For
suitable preparation save the error symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are
out of the operators scope.

216

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

202084 - Rx fault declared at the NE on IMA Link


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

ImaLink
communicationAlarm
VendorSpecific
minor

Error Description
Implementation specific RX fault declared at the NE. This alarm indication that a hardware specific defect has been detected in the Rx direction on one link of the IMAGroup.
If this alarm occurs then the ImaGroup will automatically cease transmitting on the link
and (assuming that there are sufficient good links for the Group to remain operation)
continue to operate using the remaining good links. This alarm is likely to be due to faulty
hardware at either end.
Troubleshooting
Contact the technical assistance center (TAC) to get support in isolating the fault. For
suitable preparation save the error symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are
out of the operators scope.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

217

OML:Node B

Outputs
Node B

202085 - FE has reported Tx-Unusable on IMA Link


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

ImaLink
communicationAlarm
VendorSpecific
minor

Error Description
The far end has reported that the link is unusable in the TX direction. When the ImaGroup is starting up this is an indication that would be expected before the link gets to
its normal operating state and so does not necessarily indicate a problem. Thereafter
this alarm indication means that the link is no longer active for some reason that may be
indicated by other alarms. If this alarm occurs then the ImaGroup will automatically
cease transmitting on the link and (assuming that there are sufficient good links for the
Group to remain Operational) continue to operate using the remaining good links.
Troubleshooting
1. Check the cable connections.
2. If the cable connections were not indicated as basic cause, contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation
save the error symptoms as described in "Collect Info for Assistance". Log files
need to be analyzed and specific measures must be taken which are out of the operators scope.

218

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

202086 - FE has reported Rx-Unusable on IMA Link


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

ImaLink
communicationAlarm
VendorSpecific
minor

Error Description
The far end has reported that the link is unusable in the RX direction. When the ImaGroup is starting up this is an indication that would be expected before the link gets to
its normal operating state and so does not necessarily indicate a problem. Thereafter
this alarm indication means that the link is no longer active for some reason that may be
indicated by other alarms. If this alarm occurs then the ImaGroup will automatically
cease transmitting on the link and (assuming that there are sufficient good links for the
Group to remain Operational) continue to operate using the remaining good links.
Troubleshooting
1. Check the cable connections.
2. If the cable connections were not indicated as basic cause, contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation
save the error symptoms as described in "Collect Info for Assistance". Log files
need to be analyzed and specific measures must be taken which are out of the operators scope.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

219

OML:Node B

Outputs
Node B

202087 - Startup FE reported on IMA Group


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

ImaGroup
communicationAlarm
VendorSpecific
major

Error Description
The far end IMA Group is in the Startup state. This alarm indication should be seen as
part of the normal startup procedure of the Group and does not necessarily indicate a
problem. Thereafter it indicates that the Group has reset to its startup state for some reason that may be explained by other alarms.
Troubleshooting
Contact the technical assistance center (TAC) to get support in isolating the fault. For
suitable preparation save the error symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are
out of the operators scope.

220

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

202088 - Config Abort reported on IMA Group


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

ImaGroup
communicationAlarm
VendorSpecific
major

Error Description

NOTE
If an IMA group has been configured, however, not being operational during start-up,
the Node B possibly restarts some minutes after start-up.
This indication means that the IMA Group has aborted its attempted startup for some
reason. This may be because the IMA Group at the far end has been configured with
incompatible attributes to those that have been used at the near end. Possible incompatible attributes are: Frame Length, Group Symmetry or the IMA Version. These may
be fixable by modification to the configuration at one or both ends.
Troubleshooting
Check the hardware compatibility of the configuration.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

221

OML:Node B

Outputs
Node B

202089 - Config Abort FE reported on IMA Group


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

ImaGroup
communicationAlarm
VendorSpecific
major

Error Description

NOTE
If an IMA group has been configured, however, not being operational during start-up,
the Node B possibly restarts some minutes after start-up.
This indication is the same as the imaGroupConfigAbort (see: 202088 - Config Abort reported on IMA Group) but has been reported by the far end IMA to the near end. The
causes and possible fixes are the same as for the imaGroupConfigAbort.
Troubleshooting
Check the hardware compatibility of the configuration.

222

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

202090 - Insufficient Links reported at NE on IMA Group


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

ImaGroup
communicationAlarm
VendorSpecific
major

Error Description

NOTE
If an IMA group has been configured, however, not being operational during start-up,
the Node B possibly restarts some minutes after start-up.
The NE has reported that the number of active links (operational state = enabled) is less
than is required for the Group to be operational.
This may be caused by one of the following:
The configuration of the group requires more links than have been configured.
One or more links are non-operational for other reasons, such as fault conditions.
One or more links have not yet completed their startup procedure.
If enough links have been configured, the status of these links must be examined to determine why not sufficiently enough of these links are in the operational state enabled.
At startup of the group this alarm indication would normally be expected to be seen as
the group performs its startup procedure.
Troubleshooting
Perform the following tasks to solve this error:
1. Check Node B database.
Use the mibCheck or mibCheckWin tool which is supplied with the Node B software.
Refer to the OGL:Node B DB Editing Guide.
The number of links required for the group to be operational is configured by the attribute imaGroupMinNumLinks
2. Change Node B database.
Proceed according to the OGL:Node B DB Editing Guide.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

223

OML:Node B

Outputs
Node B

202091 - Insufficient Links at FE reported on IMA Group


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

ImaGroup
communicationAlarm
VendorSpecific
major

Error Description

NOTE
If an IMA group has been configured, however, not being operational during start-up,
the Node B possibly restarts some minutes after start-up.
The FE has reported that the number of active links (operational state = enabled) is less
than is required for the group to be operational.
The reasons and actions for this alarm are similar to those described for the Insufficient
Links indication at the near end (see: 202090 - Insufficient Links reported at NE on IMA
Group).
Troubleshooting
Perform the following tasks to solve this error:
1. Check Node B database.
Use the mibCheck or mibCheckWin tool which is supplied with the Node B software.
Refer to the OGL:Node B DB Editing Guide.
The number of links required for the group to be operational is configured by the attribute imaGroupMinNumLinks
2. Change Node B database.
Proceed according to the OGL:Node B DB Editing Guide.

224

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

202092 - Group Blocked at FE reported on IMA Group


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

ImaGroup
communicationAlarm
VendorSpecific
major

Error Description
The FE IMA group has been blocked (i.e. its adminstrative state has been set to locked
by the operator at the FE). As a consequence, the FE IMA group is not operating.
Troubleshooting
Perform the following tasks to solve this error:
1. Check the administrative state of the IMA group at the FE.
2. Change the administrative state to unlocked at the FE.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

225

OML:Node B

Outputs
Node B

202093 - Timing Synch error reported on IMA Group


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

ImaGroup
communicationAlarm
VendorSpecific
major

Error Description

NOTE
If an IMA group has been configured, however, not being operational during start-up,
the Node B possibly restarts some minutes after start-up.
FE transmit clock mode is different from the NE transmit clock mode due to different configuration of the group. The imaGroupNeTxClkMode at both ends should be set to CTC
(Common Transmit Clock).
Troubleshooting
Perform the following tasks to solve this error:
1. Check Node B database.
Use the mibCheck or mibCheckWin tool which is supplied with the Node B software.
Refer to the OGL:Node B DB Editing Guide.
The number of links required for the group to be operational is configured by the attribute imaGroupMinNumLinks
2. Change Node B database.
Proceed according to the OGL:Node B DB Editing Guide.

226

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

202095 - The Near End IMA has detected an invalid version


set by the Far End
Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

ImaGroup
communicationAlarm
VendorSpecific
major

Error Description
The Node B does only support IMA version 1.1. The far end IMA group, however, is using a different IMA version. This indicates that the far end hardware configuration is incompatible with the near end hardware.
Troubleshooting
Check the hardware compatibility of the configuration in the far end.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

227

OML:Node B

Outputs
Node B

202097 - Loss of Continuity detected on an ATM VP


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

ContinuityMonitor
communicationAlarm
VendorSpecific
minor

Error Description
The VpCTP or the VpTTP which contains the continuity monitor does not receive the expected continuity check cells from the source.
Troubleshooting
Troubleshooting has to start with investigation on other alarms: Check whether alarms
at upstream NEs are present in the ALARM View window of the LMT:
1. Click on the Alarm View button or use the shortkey Ctrl-A.
2. Proceed according to the troubleshooting of the trigger alarm.
If either no such alarm is present or if the actions taken above did not clear the condition
for this alarm, perform the following steps in the given order to cease this alarm:
1. Confirm that all relevant cables are connected properly.
2. If these actions did not help to solve this error, contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save the error
symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are out of the operators scope.

228

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

202098 - CRC4 not used by FE reported on E1TTP


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

E1TTP
communicationAlarm
VendorSpecific
warning

Error Description
The following indication has been received on the reporting E1 physical link: CRC4 not
used by FE.
The 202098 - CRC4 not used by FE reported on E1TTP alarm indicates that no multiframe synchronization could be found. This may be due to the follwing:
Misconfiguration of the hardware at either end
Faulty hardware at either end
Problems on the transmission medium between the two ends
The "202098 - CRC4 not used by FE Indication on E1 Physical Link" alarm may be
caused by the following:
The Node B's E1TTP managed object's attribute crcOperationMode, which indicates
the mode of CRC operation, is set to crcAutomatic whereas the frame format for the
RNC is set to 0 meaning that the CRC is disabled.
The "202098 - CRC4 not used by FE Indication on E1 Physical Link" does not cause any
change of the reporting E1TTP's OST/AVS.
Troubleshooting
Contact the technical assistance center (TAC) to get support in isolating the fault. For
suitable preparation save the error symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are
out of the operators scope.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

229

OML:Node B

Outputs
Node B

202106 - Software activation failed


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Osu
processingErrorAlarm
SoftwareError
warning

Error Description
The activation of a software load failed in the previous run.
As a consequence, the Node B now automatically switched back to the previously running software load.
Troubleshooting
Contact the technical assistance center (TAC) to get support in isolating the fault. For
suitable preparation save the error symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are
out of the operators scope.

230

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

202107 - Database activation failed


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Osu
processingErrorAlarm
ConfigurationOrCustomizationError
warning

Error Description
The activation of a database failed in the previous run.
As a consequence, the Node B now automatically switched back to the previously running database.
Troubleshooting
Contact the technical assistance center (TAC) to get support in isolating the fault. For
suitable preparation save the error symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are
out of the operators scope.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

231

OML:Node B

Outputs
Node B

202108 - Reliable software started without prior explicit


activation
Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Osu
processingErrorAlarm
SoftwareError
warning

Error Description
The reliable software was started without a prior explicit activation procedure (automatic
fallback).
This case occurs due to one of the following situations:
No activation is running and the start-up with the running software failed three times
in a row.
An error occurred in a very early boot phase.
Troubleshooting
Contact the technical assistance center (TAC) to get support in isolating the fault. For
suitable preparation save the error symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are
out of the operators scope.

232

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

202109 - Reliable database started without prior explicit


activation
Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Osu
processingErrorAlarm
SoftwareError
warning

Error Description
The reliable database was started without a prior explicit activation procedure (automatic fallback).
This case occurs due to one of the following situations:
No activation is running and the start-up with the reliable database failed three times
in a row.
An error occurred in a very early boot phase.
Troubleshooting
Contact the technical assistance center (TAC) to get support in isolating the fault. For
suitable preparation save the error symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are
out of the operators scope.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

233

OML:Node B

Outputs
Node B

202156 - Cannot acquire mutex for logging of FER


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Osu
processingErrorAlarm
SoftwareError
critical

Error Description
FER cannot be logged, because mutex to access reset safe RAM could not be acquired.
Troubleshooting
Contact the technical assistance center (TAC) to get support in isolating the fault. For
suitable preparation save the error symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are
out of the operators scope.

234

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

202157 - Cannot release mutex after logging of FER


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Osu
processingErrorAlarm
SoftwareError
critical

Error Description
Next FER can not be logged, because mutex for access to reset safe RAM could not be
released.
Troubleshooting
Contact the technical assistance center (TAC) to get support in isolating the fault. For
suitable preparation save the error symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are
out of the operators scope.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

235

OML:Node B

Outputs
Node B

202158 - Reset safe RAM for logging of FERs unavailable


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Osu
processingErrorAlarm
SoftwareError
critical

Error Description
Logging failure, because the reset safe RAM was not accessible. Logging of FERs is not
possible without accessing reset safe RAM.
Troubleshooting
Contact the technical assistance center (TAC) to get support in isolating the fault. For
suitable preparation save the error symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are
out of the operators scope.

236

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

202357 - CAN opcode not valid


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Cc
communicationAlarm
InvalidMessageReceived
warning

Error Description
The Node B CAN communicates with various devices via CAN bus. The Core Controller
software verifies messages from CAN participants for valid types. This fault report will
be generated, if the Core Controller software detects an invalid message type. The affected Node B may continue to operate in a degraded mode.
The probable cause for that condition could either be a hardware failure or a software
failure.
Troubleshooting
1. Any CAN bus participant may cause the problem. Check all CAN bus participants in
order to isolate the fault.
2. First, reset the addressed card. Use the TREE View window of the LMT or, alternatively, apply the rst command to the addressed card.
3. If the fault cannot be cleared by reset, the addressed card has to be replaced. Replacement must be done according to the Maintenance Manual MMN:Node B.
4. If the card replacement did not clear the fault, contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save the error
symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are out of the operators scope.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

237

OML:Node B

Outputs
Node B

202358 - CAN received an unexpected message


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Cc
communicationAlarm
InvalidMessageReceived
warning

Error Description
The Node B CAN communicates with various devices via CAN bus. The Core Controller
software verifies the communication scenarios. This fault report will be generated, if the
Core Controller software detects an unexpected message in the actual message scenario. The affected Node B may continue to operate in a degraded mode.
The probable cause for that condition could either be a hardware failure or a software
failure.
Troubleshooting
1. Any CAN bus participant may cause the problem. Check all CAN bus participants in
order to isolate the fault.
2. First, reset the addressed card. Use the TREE View window of the LMT or, alternatively, apply the rst command to the addressed card.
3. If the fault cannot be cleared by reset, the addressed card has to be replaced. Replacement must be done according to the Maintenance Manual MMN:Node B.
4. If the card replacement did not clear the fault, contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save the error
symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are out of the operators scope.

238

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

202359 - CAN received a message with an invalid parameter


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Cc
communicationAlarm
InvalidMessageReceived
warning

Error Description
The Node B CAN communicates with various devices via CAN bus. The Core Controller
software verifies some parameter values supplied by CAN participants. This fault report
will be generated, if the Core Controller software detects an invalid parameter from a
CAN participant. The affected Node B may continue to operate in a degraded mode.
The probable cause for that condition could either be a hardware failure or a software
failure.
Troubleshooting
1. Any CAN bus participant may cause the problem. Check all CAN bus participants in
order to isolate the fault.
2. First, reset the addressed card. Use the TREE View window of the LMT or, alternatively, apply the rst command to the addressed card.
3. If the fault cannot be cleared by reset, the addressed card has to be replaced. Replacement must be done according to the Maintenance Manual MMN:Node B.
4. If the card replacement did not clear the fault, contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save the error
symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are out of the operators scope.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

239

OML:Node B

Outputs
Node B

202360 - A necessary resource is missed


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Cc
processingErrorAlarm
UnderlyingRessourceUnavailable
warning

Error Description
The Node B communicates with various devices via a CAN bus. This fault report will be
generated, if the Core Controller cannot initialize its local resources. This condition leads
to a recovery reset. The affected Node B is therefore temporarily not operational.
The probable cause for that condition could either be a hardware failure or a software
failure.
Troubleshooting
1. Any CAN bus participant may cause the problem. Check all CAN bus participants in
order to isolate the fault.
2. First, reset the addressed card. Use the TREE View window of the LMT or, alternatively, apply the rst command to the addressed card.
3. If the fault cannot be cleared by reset, the addressed card has to be replaced. Replacement must be done according to the Maintenance Manual MMN:Node B.
4. If the card replacement did not clear the fault, contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save the error
symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are out of the operators scope.

240

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

202406 - ALCAP Protocol Error


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Cc
communicationAlarm
CommunicationProtocolError
warning

Error Description
ALCAP (access link control application part) protocol errors are an indication of one of
the following conditions:
Messages are being corrupted over the Iub interface.
Software implementation problems between RNC and Node B.
ALCAP protocol in the RNC has been upgraded to a later version of the specification
(ITU-T Q.2630.1).
Troubleshooting
Contact the technical assistance center (TAC) to get support in isolating the fault. For
suitable preparation save the error symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are
out of the operators scope.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

241

OML:Node B

Outputs
Node B

202431 - ITR initiated action from CPA to RNC timed out


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Cc
qualityOfServiceAlarm
Congestion
warning

Error Description
An ITR (transport management subsystem) initiated Iub request on ALCAP (access link
control application part) has timed out. This means that block request, unblock request
or reset request has been requested by ITR and has timed out before a reply has been
received from the RNC.
This condition is fairly serious as it can lead to a configuration misalignment between
RNC and Node B. This error could either be caused by congestion or a failure in the ALCAP socket between RNC and Node B.
Troubleshooting
Contact the technical assistance center (TAC) to get support in isolating the fault. For
suitable preparation save the error symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are
out of the operators scope.

242

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

202432 - CPN initiated action from CPA to RNC timed out


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Cc
qualityOfServiceAlarm
Congestion
warning

Error Description
A CPN (call processing NBAP) initiated Iub request on ALCAP (access link control application part) has timed out. This means that reset request or release request has been
requested by CPN and has timed out before a reply has been received from the RNC.
This condition is fairly serious as it can lead to a configuration misalignment between
RNC and Node B. This error could either be caused by congestion or a failure in the ALCAP socket between RNC and Node B.
Troubleshooting
Contact the technical assistance center (TAC) to get support in isolating the fault. For
suitable preparation save the error symptoms as described in "Collect Info for
Assistance". Log files need to be analyzed and specific measures must be taken which
are out of the operators scope.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

243

OML:Node B

Outputs
Node B

202433 - Configuration misalignment between RNC and


CPA
Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Cc
communicationAlarm
SscopFailure
warning

Error Description
This error occurs when RNC sends a message to CPA (call processing ALCAP) to perform an action which is not valid. Such actions include:
RNC attempts to block a path which is already blocked or does not exist.
RNC attempts to unblock a path which is already unblocked or does not exist.
RNC attempts to reset a path which does not exist.
RNC attempts to release a non-existent connection.
While not a serious problem in itself, these unexpected actions could point to either a
software error or a configuration misalignment between RNC and CPA which is serious.
Troubleshooting
Contact the technical assistance center (TAC) to get support in isolating the fault. For
suitable preparation save the error symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are
out of the operators scope.

244

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

202434 - RNC Establish Request message received which


is invalid or cannot be handled
Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Cc
communicationAlarm
CommunicationProtocolError
warning

Error Description
This error indicates that an ALCAP (access link control application part) establish request message has been received from the RNC which is either invalid or cannot be
handled.
Possible errors include:
Establish request for a connection which is destined to be routed to a BB (baseband)
card that is not in service (this is an NBAP/BB card problem).
Establish request which contains an invalid binding ID.
Establish request with an invalid NSEA (NSAP service endpoint address) address
for the Node B.
Establish request which contains unexpected parameters for this implementation.
Establish request for a path which does not exist
Establish request for a channel that is already in use.
Establish request with no TCI (test connection indication) for a path which is locally
blocked.
These either indicate a problem with the RNC or internal subsystems.
Troubleshooting
Contact the technical assistance center (TAC) to get support in isolating the fault. For
suitable preparation save the error symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are
out of the operators scope.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

245

OML:Node B

Outputs
Node B

202435 - CPA to RNC communication (socket) problems


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Cc
communicationAlarm
SscopFailure
warning

Error Description
This error occurs if data that is about to be sent is lost due to the TNP (transport network
protocol) socket between Node B and RNC either being out-of-service or returning error.
This is a serious problem as, if there is no retry mechanism (e.g. for release requests),
then configuration misalignment could result between RNC and Node B.
The following subsequent alarm may also be initiated:
200656 - Iub link broke down
Troubleshooting
Contact the technical assistance center (TAC) to get support in isolating the fault. For
suitable preparation save the error symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are
out of the operators scope.

246

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

202456 - CC Clock Warm Up Error


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Cc
environmentalAlarm
CoolingSystemFailure
critical

Error Description
In the reporting CC (Core Controller), a clock warm up error occurred.
BHS (basic hardware service) monitors the warming up of the clock. It waits 4 minutes
for the message from the LIU (line interface unit) board, where the oven quartz clock is
located, confirming the stable work of the clock. In the eventof any error, the CC must
be reset.
Troubleshooting
Perform the following tasks in the order provided:
1. First, reset the addressed card. Use the TREE View window of the LMT or, alternatively, apply the rst command to the addressed card.
2. If the fault cannot be cleared by reset, the addressed card has to be replaced. Replacement must be done according to the Maintenance Manual MMN:Node B.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

247

OML:Node B

Outputs
Node B

202457 - CC Card HW Test Error


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Cc
equipmentAlarm
EquipmentFailure
critical

Error Description
In the reporting CC (Core Controller) card, a hardware test error occurred.
BHS (basic hardware service) initiates and monitors the boards' device tests. In case of
any error board tests SW returns the short error description message (no more than 256
letters) which is forwarded to IFA (fault and alarm management). In fact, BHS tests the
CPU, LIU, ATM, and STM-1/OC-3 boards.
Troubleshooting
Perform the following steps to solve this error:
1. First, reset the addressed card. Use the TREE View window of the LMT or, alternatively, apply the rst command to the addressed card.
2. If the fault cannot be cleared by reset, the addressed card has to be replaced. Replacement must be done according to the Maintenance Manual MMN:Node B.

248

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

202506 - Node B System Clock in Holdover Mode


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

ClMng
equipmentAlarm
TimingProblem
minor

Error Description
The reference input for the Node B system clock is not available or not stable enough
for synchronization. System clock oscillator is running without external synchronization
(holdover mode). This may be due to incorrect configuration of the clock management
in the Node B database, or due to insufficient signal quality of the reference clock
source.
Troubleshooting
All clock signals in the Node B are derived from an internal high accuracy master clock
(OC-VCXO) which is synchronized to a reference clock signal by PLL. This reference
clock can be derived from the Iub interface (E1/J1/T1 or STM-1/OC-3) or from an external source connected to the external synchronization input.
With the MO clmng in the nbDatabase not only the source for the reference clock can
be defined but also the priority order of up to 4 possible sources can be selected. If the
reference clock is lost or is not of sufficient quality the internal clock (OC-VCXO) will still
work within 3GPP frequency stability limit of 0,05 ppm for at least 2 days. The working
state is hold over mode - high accuracy.
1. Reference clock lost
If the reference clock is derived from an E1/J1/T1 or STM-1/OC-3 line and the relevant incoming Iub signal is lost or degraded concentrate on fixing the Iub interface
alarm first as they are:
202056 - Loss Of Signal on Physical Link
202057 - Loss Of Frame on Physical Link
202070 - Signal Degrade Indication on STM1 Physical Link
202071 - Excessive Bit Error Rate Indication on STM1 Physical Link
2. Clock management configuration incorrect
The MO clmng in the nbDatabase defines the reference clock sources and their
priority. The attributes prio0Port and prio0LineType show the interface with the
highest priority whereas prio3Port and prio3LineType are assigned to the interface with the lowest priority.
upload the nbDatabase
check for right configuration of ports and line types of MO clmng as well as
stm1Port and lineCircuitAddress of the transport related MOCs stm1TP or
e1TTP/j1TTP respectively, refer to the OGL:Node B DB Description

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

249

OML:Node B

Outputs
Node B

3. Reference signal quality insufficient


For further investigation, contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save the error symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific
measures must be taken which are out of the operators scope.

250

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

202507 - Node B System Clock in Medium Accuracy


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

ClMng
equipmentAlarm
TimingProblem
minor

Error Description
The accuracy of the Node B system clock is in medium accuracy range. This may be
due to insufficient signal quality of the reference clock source.
The following preceded alarm should have been reported:
202506 - Node B System Clock in Holdover Mode
Troubleshooting
All clock signals in the Node B are derived from an internal high accuracy master clock
(OC-VCXO) which is synchronized to a reference clock signal by PLL. This reference
clock can be derived from the Iub interface (E1/J1/T1 or STM-1/OC-3) or from an external source connected to the external synchronization input.
With the MO clmng in the nbDatabase not only the source for the reference clock can
be defined but also the priority order of up to 4 possible sources can be selected. If the
reference clock is lost or is not of sufficient quality the internal clock (OC-VCXO) will first
change to the working state hold over mode - high accuracy. But if the bad synchronization remains for up to 2 days the Node B will go from hold over mode - high accuracy
to hold over mode - medium accuracy. In this case the frequency stability can only be
guaranteed for a few days and after this period there is a possibility that the Node B will
transmit outside 0,05 ppm.
1. Reference clock lost
If the reference clock is derived from an E1/J1/T1 or STM-1/OC-3 line and the relevant incoming Iub signal is lost or degraded concentrate on fixing the Iub interface
alarm first as they are:
202056 - Loss Of Signal on Physical Link
202057 - Loss Of Frame on Physical Link
202070 - Signal Degrade Indication on STM1 Physical Link
202071 - Excessive Bit Error Rate Indication on STM1 Physical Link
2. Clock management configuration incorrect
The MO clmng in the nbDatabase defines the reference clock sources and their
priority. The attributes prio0Port and prio0LineType show the interface with the
highest priority whereas prio3Port and prio3LineType are assigned to the interface with the lowest priority.
upload the nbDatabase
check for right configuration of ports and line types of MO clmng as well as
stm1Port and lineCircuitAddress of the transport related MOCs stm1TP or
e1TTP/j1TTP respectively. Refer to the OGL:Node B DB Description
3. Reference signal quality insufficient
For further investigation, contact the technical assistance center (TAC) to get support in isolating the fault. For suitable preparation save the error symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific
measures must be taken which are out of the operators scope.
Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

251

OML:Node B

Outputs
Node B

262041 - System call unsuccessful


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

*
processingErrorAlarm
SystemCallInsuccessful
critical

Error Description
A system call was not successful. As a consequence, the CC (Core Controller) will be
reset, because the software is not capable of working stable any longer. The problem
has to be analyzed by the customer service.
Troubleshooting
Contact the technical assistance center (TAC) to get support in isolating the fault. For
suitable preparation save the error symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are
out of the operators scope.

252

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

262042 - Unexpected software error


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

*
processingErrorAlarm
SoftwareError
critical

Error Description
An unexpected software error occurred. As a consequence, the CC (Core Controller)
will be reset, because the software is not capable of working stable any longer. The
problem has to be analyzed by the customer service.
Troubleshooting
Contact the technical assistance center (TAC) to get support in isolating the fault. For
suitable preparation save the error symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are
out of the operators scope.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

253

OML:Node B

Outputs
Node B

262043 - Error from Device Driver received


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

*
processingErrorAlarm
SoftwareError
critical

Error Description
A function call to a device driver returned an error. In most of the cases the CC (Core
Controller) will be reset as a consequence. The problem has to be analyzed by the customer service.
Troubleshooting
Contact the technical assistance center (TAC) to get support in isolating the fault. For
suitable preparation save the error symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are
out of the operators scope.

254

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

262044 - Not enough memory to initialize software


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

Cc
processingErrorAlarm
OutOfMemory
critical

Error Description
At start-up time the OS (operating system) could not allocate enough memory for task
stacks, message buffers and dynamic memory management etc.. The problem has to
be analyzed by the customer service.
Troubleshooting
Contact the technical assistance center (TAC) to get support in isolating the fault. For
suitable preparation save the error symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are
out of the operators scope.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

255

OML:Node B

Outputs
Node B

262045 - Memory allocation failure


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

*
processingErrorAlarm
OutOfMemory
critical

Error Description
The system did not have enough free memory to satisfy a memory allocation request.
As a consequence, the CC (Core Controller) will be reset. The problem has to be analyzed by the customer service.
Troubleshooting
Contact the technical assistance center (TAC) to get support in isolating the fault. For
suitable preparation save the error symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are
out of the operators scope.

256

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03

Outputs
Node B

OML:Node B

262046 - Unexpected exception handling


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

*
processingErrorAlarm
SoftwareError
critical

Error Description
An unexpected exception was thrown. As a consequence, the CC (Core Controller) will
be reset, because the software is not capable of working stable any longer. The problem
has to be analyzed by the customer service.
Troubleshooting
Contact the technical assistance center (TAC) to get support in isolating the fault. For
suitable preparation save the error symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are
out of the operators scope.

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:
ND-57314-705(E)-prelim03

257

OML:Node B

Outputs
Node B

262047 - Uncaught exception handling


Failure Event Report
Managed Object Class / Hardware Type:
Event Type:
Probable Cause:
Severity:

*
processingErrorAlarm
SoftwareError
critical

Error Description
A thrown exception was not caught. As a consequence, the CC (Core Controller) will be
reset, because the software is not capable of working stable any longer. The problem
has to be analyzed by the customer service.
Troubleshooting
Contact the technical assistance center (TAC) to get support in isolating the fault. For
suitable preparation save the error symptoms as described in "Collect Info for Assistance". Log files need to be analyzed and specific measures must be taken which are
out of the operators scope.

258

Siemens AG:A50016-G5000-F226-prelim3-7619
NEC Corporation:ND-57314-705(E)-prelim03