nodeboml

UTRAN

Outputs

Node B

OML:Node B

A50016-G5000-F226-prelim3-7619ND-57314-705(E)-prelim03

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

OML:Node B OutputsNode B

f Important Notice on Product SafetyDANGER - 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 mustcomply with the applicable safety standards.Hazardous voltages are present at the AC power supply lines in this electrical equipment. Some components mayalso have high operating temperatures.Failure to observe and follow all installation and safety instructions can result in serious personal injuryor 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 angeschlossenenGerte mssen die zutreffenden Sicherheitsbestimmungen erfllen.In diesen Anlagen stehen die Netzversorgungsleitungen unter gefhrlicher Spannung. Einige Komponentenknnen auch eine hohe Betriebstemperatur aufweisen.Nichtbeachtung der Installations- und Sicherheitshinweise kann zu schweren Krperverletzungen oderSachschden 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 tableA30808-X3247-X910-*-7618, which is shipped with each product. This class also corresponds to the limits for aClass 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 isoperated in a commercial environment.This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accor-dance with the relevant standards referenced in the manual Guide to Documentation, may cause harmful inter-ference to radio communications.For system installations it is strictly required to choose all installation sites according to national and local require-ments 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 electromagneticfield / 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 purposescould violate the rights of their owners.

Copyright (C) Siemens AG / NEC Corporation 2005.

Issued by:Siemens AG, Communications, Hofmannstrae 51, 81359 Mnchen, Germany andNEC 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.

OutputsNode B

OML:Node B

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

Reason for UpdateSummary: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 HistoryIssue Date of issue Reason for Update

1 05/2005 First issue for new release.

2 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 trouble-

shootings.

OutputsNode B

OML:Node B


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

Contents

Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Title . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Failure Event Report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Managed Object Class / Hardware Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Event Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Probable Cause . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Severity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12Error Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Errors in Numerical Order (error-ID). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15200506 - Node B system start-up malfunction due to software/hardware problem . . 16200507 - System halt due to software watchdog detected problem. . . . . . . . . . . . . . 17200508 - System halt due to detected application process error . . . . . . . . . . . . . . . . 18200509 - System halt due to detected hardware exception . . . . . . . . . . . . . . . . . . . . 19200510 - System halt due to detected software loading malfunction . . . . . . . . . . . . . 20200656 - Iub link broke down . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21200657 - SSCOP sent overrun. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23200658 - Transmit bandwidth limit for NBAP reached . . . . . . . . . . . . . . . . . . . . . . . . 24200659 - Core Controller overload protection activated. . . . . . . . . . . . . . . . . . . . . . . 25200706 - An error occurred in the nbDatabase . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26200707 - A warning occurred in the nbDatabase. . . . . . . . . . . . . . . . . . . . . . . . . . . . 27200756 - System call unsuccessful . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28200757 - Unexpected software error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29200758 - Not enough memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30200759 - A fatal error has occurred that may affect OAM command processing. . . . 31200905 - VSWR alarm Low . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32200906 - VSWR alarm High . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34200907 - RX alarm Low . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36200908 - RX alarm High. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37200909 - TMA switched off, but not defective . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38200910 - TMA feeder alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39200911 - TMA DC alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41200914 - Fan unit failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42200915 - Site input alarm detected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44200916 - Rack Door open . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46200918 - PA combiner interface fault . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47200919 - Failure in the DC supply of PA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48200920 - High temperature of PA. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49200921 - Over temperature of PA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51200922 - RF performance not being met due to bad linearization . . . . . . . . . . . . . . . 53200923 - Internal failure of PA detected. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54200924 - Input power level of LPA too high but LPA can still hold its RF specification .

55200925 - Input power level of PA too high . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56



200926 - CPU failure of baseband card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57200927 - Volatile memory failure of baseband card . . . . . . . . . . . . . . . . . . . . . . . . . . 58200928 - Non-volatile memory failure of baseband card. . . . . . . . . . . . . . . . . . . . . . . 59200929 - DSP failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60200931 - FPGA failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61200932 - Control FPGA failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62200933 - External timing signal failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63200934 - Failure of the RF part of the TRX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64200935 - LVDS Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65200936 - Local bus failure around the CPU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66200937 - FTP connection failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67200938 - SWI CRC check failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68200939 - Static configuration file CRC check failed . . . . . . . . . . . . . . . . . . . . . . . . . . 69200940 - SW activation failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70200941 - Internal clock failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71200942 - Configuration file inconsistent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72200943 - IOR file inconsistent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73200944 - FTP put failed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74200945 - FTP manage failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75200946 - Still alive supervision failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76200947 - Failure in the DC supply of DUAMCO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77200948 - CORBA communication failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78200949 - Internal CORBA call failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79200950 - Timeout for request or modification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80200951 - Status notification undefined . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81200952 - Maximum number of resets exceeded . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82200953 - CAN bus off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83200954 - No message response on CAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84200955 - Mount supervision failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85200956 - Watch dog timer expired . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86200957 - Internal CAN processing failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87200958 - Timer for the reset supervision expired . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88200959 - Missing response from baseband card . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89200960 - Invalid response from baseband card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90200961 - Firmware download failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91200980 - Invalid MO . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92200981 - MO not mounted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93200982 - Invalid command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94200983 - Invalid parameter in command. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95200984 - FW download access file error. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96200985 - CAN transaction error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97200986 - Temperature out of range in upper direction . . . . . . . . . . . . . . . . . . . . . . . . 98200987 - Hardware parameter invalid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99200988 - Response unknown . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100200989 - No CORBA proxy available for LRU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101200990 - No still alive response from LRU . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102200991 - Duplex error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103

OutputsNode B

OML:Node B


200992 - Software Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104200993 - Unexpected Alarm Status Bit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105200994 - HW Failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106200995 - High Temperature Limit (Ht3) reached . . . . . . . . . . . . . . . . . . . . . . . . . . . 107200996 - Critical Temperature Limit (Ht4) reached . . . . . . . . . . . . . . . . . . . . . . . . . 109200997 - Lower Temperature Limit (Ht0) reached . . . . . . . . . . . . . . . . . . . . . . . . . . 111200998 - Temperature out of range in lower direction . . . . . . . . . . . . . . . . . . . . . . . 112200999 - Unexpected loss of unlocked card . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113201001 - RET power off . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115201002 - RET feeder alarm . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116201003 - RET hardware alarm. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117201004 - RET communication error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118201005 - RET isnt calibrated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119201006 - RET isnt scaled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 120201007 - RET lost position . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121201008 - RET received wrong configuration data . . . . . . . . . . . . . . . . . . . . . . . . . . 122201009 - A mounted card is not used to its full capacity . . . . . . . . . . . . . . . . . . . . . 123201010 - An incompatible card is mounted . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124201011 - Alignment of standby CC failed. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125201012 - Timeout for connection to standby CC . . . . . . . . . . . . . . . . . . . . . . . . . . . 126201013 - Connection failure to standby CC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127201014 - Standby CC forced to become active due to unreachable active CC . . . . 128201015 - Preparation of data to be aligned has failed . . . . . . . . . . . . . . . . . . . . . . . 129201016 - Non-fatal internal LVDS failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 130201017 - Digital input power level too high, but gain reduced . . . . . . . . . . . . . . . . . 131201018 - The LRU could not process a message from CC . . . . . . . . . . . . . . . . . . . 132201019 - Gain below threshold . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133201020 - Loss of single DRIF interface detected . . . . . . . . . . . . . . . . . . . . . . . . . . . 134201022 - Alignment of file data has failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135201023 - Bad signal quality of single DRIF interface detected. . . . . . . . . . . . . . . . . 136201024 - Bad signal quality of all DRIF interfaces detected. . . . . . . . . . . . . . . . . . . 137201025 - PID could not be read or is corrupted . . . . . . . . . . . . . . . . . . . . . . . . . . . . 138201026 - LRU sent illegal parameter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139201027 - LRU could not process a message from CC containing data from DB . . . 140201028 - HW-failure clock processing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141201029 - MEF blocked . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142201030 - Invalid hardware capacity licensing value . . . . . . . . . . . . . . . . . . . . . . . . . 143201031 - Wrong combination of licensed cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . 144201032 - Not all cells are licensed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 145201033 - PID could not be read or is corrupted - non-fatal . . . . . . . . . . . . . . . . . . . 146201034 - Boosters Fan unit failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 147201035 - MEF completely blocked. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 148201036 - RRHs unable to establish communication links with the expected number of

PSRs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 149201037 - RET unspecified error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150201038 - Resource conflict between CP and OAM . . . . . . . . . . . . . . . . . . . . . . . . . 151201039 - Inconsistency between hardware license and configuration . . . . . . . . . . . 152



201040 - Wrong cabling of LRU detected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 153201916 - Toggling condition detected for alarm AIS, SP ID 202059 . . . . . . . . . . . 154201917 - Toggling condition detected for alarm RAI, SP ID 202060 . . . . . . . . . . . 155201918 - Toggling condition detected for alarm lineAIS, SP ID 202062. . . . . . . . . 156201919 - Toggling condition detected for alarm lineRDI, SP ID 202063 . . . . . . . . 157201920 - Toggling condition detected for alarm pathAIS, SP ID . . . . . . . . . . . . . . 158201921 - Toggling condition detected for alarm pathRDI, SP ID 202066 . . . . . . . . 159201922 - Toggling condition detected for alarm vcAIS, SP ID 202072. . . . . . . . . . 160201923 - Toggling condition detected for alarm vcRDI, SP ID 202073 . . . . . . . . . 161201924 - Toggling condition detected for alarm vpAIS, SP ID 202075. . . . . . . . . . 162201925 - Toggling condition detected for alarm vpRDI, SP ID 202076 . . . . . . . . . 163201926 - Toggling condition detected for alarm LOC, SP ID 202097. . . . . . . . . . . 164202006 - A bbUsageRatio Quality of Service alarm has occurred . . . . . . . . . . . . . . 165202007 - A scanner could not be initialized. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166202008 - The temporary measurement results could not be stored . . . . . . . . . . . . . 167202009 - Unable to request measurement results . . . . . . . . . . . . . . . . . . . . . . . . . . 168202010 - The ScanCo could not be initialized. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169202011 - The final results files could not be generated. . . . . . . . . . . . . . . . . . . . . . . 170202012 - The first bbUsageRatio Quality of Service alarm has occurred . . . . . . . . . 171202013 - The second bbUsageRatio Quality of Service alarm has occurred . . . . . . 172202014 - The first sccpchUsageRatio Quality of Service alarm has occurred . . . . . 173202015 - The second sccpchUsageRatio Quality of Service alarm has occurred . . 174202016 - The first prachUsageRatio Quality of Service alarm has occurred . . . . . . 175202017 - The second prachUsageRatio Quality of Service alarm has occurred. . . . 176202018 - The first cpUsageRatio Quality of Service alarm has occurred . . . . . . . . . 177202019 - The second cpUsageRatio Quality of Service alarm has occurred . . . . . . 178202020 - The first prachCrciFailures Quality of Service alarm has occurred . . . . . . 179202021 - The second prachCrciFailures Quality of Service alarm has occurred . . . 180202056 - Loss Of Signal on Physical Link. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181202057 - Loss Of Frame on Physical Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183202058 - Loss Of Cell Delineation on Physical Link . . . . . . . . . . . . . . . . . . . . . . . . . 185202059 - Alarm Indication Signal on Physical Link . . . . . . . . . . . . . . . . . . . . . . . . . . 187202060 - Remote Alarm Indication on Physical Link. . . . . . . . . . . . . . . . . . . . . . . . . 188202061 - Loss of Multi Frame Alarm Indication on E1 Physical Link . . . . . . . . . . . . 189202062 - Line Alarm Indication Signal Indication on STM1 Physical Link. . . . . . . . . 191202063 - Line Remote Defect Indication on STM1 Physical Link . . . . . . . . . . . . . . . 192202064 - Path Loss of Pointer Indication on STM1 Physical Link. . . . . . . . . . . . . . . 194202065 - Path Alarm Indication Signal on STM1 Physical Link . . . . . . . . . . . . . . . . 197202066 - Path Remote Defect Indication on STM1 Physical Link. . . . . . . . . . . . . . . 199202068 - Signal Label Mismatch Indication on STM1 Physical Link . . . . . . . . . . . . . 200202070 - Signal Degrade Indication on STM1 Physical Link . . . . . . . . . . . . . . . . . . 201202071 - Excessive Bit Error Rate Indication on STM1 Physical Link . . . . . . . . . . . 202202072 - Alarm Indication Signal on an ATM VC . . . . . . . . . . . . . . . . . . . . . . . . . . . 204202073 - Remote Defect Indication on an ATM VC . . . . . . . . . . . . . . . . . . . . . . . . . 205202074 - SSCOP Failure Indication on an ATM VC used by ALCAP or NBAP . . . . 206202075 - Alarm Indication Signal on an ATM VP . . . . . . . . . . . . . . . . . . . . . . . . . . . 208202076 - Remote Defect Indication on an ATM VP . . . . . . . . . . . . . . . . . . . . . . . . . 209

OutputsNode B

OML:Node B


202077 - ALCAP PVC Out Of Service Indication . . . . . . . . . . . . . . . . . . . . . . . . . . . 210202078 - Loss Of Delay Synchronization on IMA Link . . . . . . . . . . . . . . . . . . . . . . . 211202079 - Loss Of IMA Frame on IMA Link . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 212202080 - Remote Failure Indicator on IMA Link. . . . . . . . . . . . . . . . . . . . . . . . . . . . 213202081 - IMA Tx link is detected as mis-connected. . . . . . . . . . . . . . . . . . . . . . . . . 214202082 - IMA Rx link is detected as mis-connected . . . . . . . . . . . . . . . . . . . . . . . . 215202083 - Tx fault declared at the NE on IMA Link . . . . . . . . . . . . . . . . . . . . . . . . . . 216202084 - Rx fault declared at the NE on IMA Link . . . . . . . . . . . . . . . . . . . . . . . . . . 217202085 - FE has reported Tx-Unusable on IMA Link . . . . . . . . . . . . . . . . . . . . . . . . 218202086 - FE has reported Rx-Unusable on IMA Link. . . . . . . . . . . . . . . . . . . . . . . . 219202087 - Startup FE reported on IMA Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 220202088 - Config Abort reported on IMA Group . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221202089 - Config Abort FE reported on IMA Group. . . . . . . . . . . . . . . . . . . . . . . . . . 222202090 - Insufficient Links reported at NE on IMA Group . . . . . . . . . . . . . . . . . . . . 223202091 - Insufficient Links at FE reported on IMA Group . . . . . . . . . . . . . . . . . . . . 224202092 - Group Blocked at FE reported on IMA Group. . . . . . . . . . . . . . . . . . . . . . 225202093 - Timing Synch error reported on IMA Group . . . . . . . . . . . . . . . . . . . . . . . 226202095 - The Near End IMA has detected an invalid version set by the Far End . . 227202097 - Loss of Continuity detected on an ATM VP . . . . . . . . . . . . . . . . . . . . . . . 228202098 - CRC4 not used by FE reported on E1TTP . . . . . . . . . . . . . . . . . . . . . . . . 229202106 - Software activation failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 230202107 - Database activation failed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 231202108 - Reliable software started without prior explicit activation . . . . . . . . . . . . . 232202109 - Reliable database started without prior explicit activation. . . . . . . . . . . . . 233202156 - Cannot acquire mutex for logging of FER. . . . . . . . . . . . . . . . . . . . . . . . . 234202157 - Cannot release mutex after logging of FER . . . . . . . . . . . . . . . . . . . . . . . 235202158 - Reset safe RAM for logging of FERs unavailable . . . . . . . . . . . . . . . . . . . 236202357 - CAN opcode not valid . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 237202358 - CAN received an unexpected message . . . . . . . . . . . . . . . . . . . . . . . . . . 238202359 - CAN received a message with an invalid parameter . . . . . . . . . . . . . . . . 239202360 - A necessary resource is missed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 240202406 - ALCAP Protocol Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241202431 - ITR initiated action from CPA to RNC timed out . . . . . . . . . . . . . . . . . . . . 242202432 - CPN initiated action from CPA to RNC timed out . . . . . . . . . . . . . . . . . . . 243202433 - Configuration misalignment between RNC and CPA . . . . . . . . . . . . . . . . 244202434 - RNC Establish Request message received which is invalid or cannot be han-

dled . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 245202435 - CPA to RNC communication (socket) problems . . . . . . . . . . . . . . . . . . . . 246202456 - CC Clock Warm Up Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 247202457 - CC Card HW Test Error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 248202506 - Node B System Clock in Holdover Mode . . . . . . . . . . . . . . . . . . . . . . . . . 249202507 - Node B System Clock in Medium Accuracy . . . . . . . . . . . . . . . . . . . . . . . 251262041 - System call unsuccessful . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 252262042 - Unexpected software error . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253262043 - Error from Device Driver received. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 254262044 - Not enough memory to initialize software . . . . . . . . . . . . . . . . . . . . . . . . . 255262045 - Memory allocation failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256



262046 - Unexpected exception handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 257262047 - Uncaught exception handling. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 258

OutputsNode B

OML:Node B


Introduction

The goal of this manual is to describe all alarms and system information which can begenerated by the Node B. The OML:Node B provides information on handling thesealarms via the LMT.

A description of the general UTRAN maintenance concept and an example of how tosolve an alarm are provided in the Guide to Documentation.

The software attempts to provide a precise error description for each alarm containingall information for the operator and manufacturer in order to rapidly localize, investigateand eliminate the fault. There is no relation between the number of described faults andtheir 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 mod-ule (specified in the test report) following the procedure described in the according main-tenance manual.

This manual is organized according to the error-IDs where each one forms a chapterwith: Title Failure Event Report Error Description Troubleshooting

TitleComposed of error-ID and error string

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

Managed Object Class / Hardware TypeThe managed object class / hardware type identifies the managed object class of thefault or error.

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

Event TypeThe Event Type may have these possible values: communicationAlarm environmentalAlarm equipmentAlarm

iThis document is prepared as a standard edition that may include descriptions not ap-plying to your system.



qualityOfServiceAlarm processingErrorAlarm

Probable CauseIdentifies the probable cause of the fault or error. The probable cause is taken out of apredefined set of values defined for each alarm type.

SeverityAccording to the CCITT Rec. X.733 all alarm notifications produced in switching sys-tems have to be classified concerning the severity of their impact on the NEs (NetworkElement) 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. TheFault 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 theescalation timer expires, the escalation counter is reset.If the object raises the same alarm after expiry of the escalation timer, the alarmsseverity will be WARNING again.

If the object raises the same alarm a predefined number of times without having op-erated normally for the escalation counters expiration period or longer, i.e. if the es-calation counter crosses a predefined threshold, the severity will change fromWARNING to a predefined final alarm severity.The alarms final severity is then set in the Failure Event Report. The OML:Node Bdescribes 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 crit-ical , 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 BsDB 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 thefollowing 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

OutputsNode 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 loadare 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 tothe 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 commandto 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 orScanner.

2. Severity setting in the severities list of the Node Bs FaultMng MOI.3. Default built-in severity.

Error DescriptionDescribes the probable cause of the error concisely.

i NOTEThe severities attribute will be considered only for alarms that represent a conditionfor which a corresponding clearance event exists. In contrast, alarms that represent onlyone single event, will always be sent with severity warning .



TroubleshootingDescribes 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 isolatethe fault. Prior to contacting the Technical Assistance Center (TAC) pay attention to thefollowing 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 thediagnosis data upload is a zip file which should be attached to any fault report. The zipfile contains information on the exact time of occurrence of the error, the database andthe inventory data file (IDF) of the affected network element and the log file. For detailsabout the diagnosis data upload, refer to the Operator Guideline OGL:LMT NB.

OutputsNode 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 innumerical order. Each title is composed of the error-ID concatenated with the error stringand followed by the failure event report.

An error description gives a general understanding of the alarm at systems level andpoints out what impacts could be expected. Hints of other symptoms or alarms thatmight be associated are also given.

Checks, detailed actions or data collection procedures for troubleshooting tasks are de-scribed subsequently.



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

Failure Event Report

Error Description

The Node B system start-up is maintained by a dedicated software subsystem (Mas-terServiceTask: MST). Any error encountered during initialization of this subsystem willgenerate this fault report. The affected Node B Core Controller is not available. Probablereasons for these conditions are problems related either to hardware (e.g.: memoryproblem, input/output malfunction) or operating system environment. This conditionleads to a recovery reset of the whole Node B.

If the fault report relates to a HW problem, troubleshooting might require detailed knowl-edge of the Node B hardware structure (memory, boot system, ...). If the fault report re-lates to a SW problem, troubleshooting might require direct access to the Node B'soperating system console.

Troubleshooting

Due to the imponderable system behavior in such cases there is no statement about fur-ther system operations. Contact the technical assistance center (TAC) to get support inisolating 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.

Managed Object Class / Hardware Type: OsuEvent Type: processingErrorAlarmProbable Cause: ApplicationSubsystemFailureSeverity: critical

OutputsNode B

OML:Node B


200507 - System halt due to software watchdog detectedproblem


Error Description

This problem reports a situation, where the software health observation system has de-tected a missing health indication from any Node B software subsystem. The affectedsubsystem malfunction might (dependent of subsystem and error cause) be already no-ticeable by generated fault reports from it's own scope. This condition leads to a recov-ery reset of the whole Node B. The affected Node B Core Controller is temporary notavailable. This information has to be analyzed to find the malfunction originator. Due tothe 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. Forsuitable preparation save the error symptoms as described in "Collect Info for Assis-tance". Log files need to be analyzed and specific measures must be taken which areout of the operators scope.

Managed Object Class / Hardware Type: OsuEvent Type: processingErrorAlarmProbable Cause: WatchDogTimerExpiredSeverity: critical



200508 - System halt due to detected application processerror


Error Description

This problem reports a situation, where the software health observation system has de-tected a 'dead' Node B software subsystem. The affected subsystem (generally) couldnot be indicated by generated fault reports from it's own scope, but this problem reportcontains information about the originator of the error. This condition leads to a recoveryreset of the whole Node B. The affected Node B Core Controller is temporarily not avail-able. Due to the recovery reset, only the system log files could be used for 'post' analy-sis.

The probable reason for this alarm is a software problem.

Troubleshooting


Managed Object Class / Hardware Type: OsuEvent Type: processingErrorAlarmProbable Cause: SoftwareProgramAbnormallyTermi-

natedSeverity: critical

OutputsNode B

OML:Node B


200509 - System halt due to detected hardware exception


Error Description

This problem reports a situation, where the software health observation system has de-tected an 'unexpected' signal by the Node B hardware. This will be just logged by theobservation system. This problem report contains information about the signal origina-tor. This condition leads to a recovery reset of the whole Node B. The affected Node BCore Controller is temporarily not available. Due to the recovery reset, only the systemlog files could be used for 'post' analysis.

Troubleshooting


Managed Object Class / Hardware Type: OsuEvent Type: communicationAlarmProbable Cause: VendorSpecificSeverity: critical



200510 - System halt due to detected software loadingmalfunction


Error Description

This problem reports a situation, where the system loader detects a failure during soft-ware loading. This problem report contains information about the name of the failed soft-ware component. If the malfunction relates to a HW problem, it might be necessary toreplace the addressed card. If the malfunction relates to a software problem, it might besolved 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 BCore Controller is temporarily not available. Due to the recovery reset, only the systemlog 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 sup-

port in isolating the fault. For suitable preparation save the error symptoms as de-scribed in "Collect Info for Assistance". Log files need to be analyzed and specificmeasures must be taken which are out of the operators scope.

Managed Object Class / Hardware Type: OsuEvent Type: communicationAlarmProbable Cause: VendorSpecificSeverity: critical

OutputsNode B

OML:Node B


200656 - Iub link broke down


Error Description

An existing ATM connection between CRNC (controlling RNC) and Node B (Iub link) isbroken because the CRNC is down, the cable has been plugged off or is broken. There-fore the Node B performs a reset.

The following subsequent alarms may also be initiated depending on the used interfacetype (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 in-terface) via link equipment (LE) and in some rare cases by direct lines. If LE is in-volved the operation and maintenance system of this network has to be used forgetting 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.

Managed Object Class / Hardware Type: CcEvent Type: equipmentAlarmProbable Cause: LinkFailureSeverity: critical



Troubleshooting If RNC alarms for the Iub link to the affected Node B are reported to the RC concen-

trate 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 probablyalso eliminates the Iub link broke down alarm.

Check the cable connections:

1. In case of E1/J1/T1 lines check the OVPT or IUBCONElectrical Iub lines (E1/J1/T1) are connected to the Node B using an OVPT (over-voltage 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

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 Bpresent?

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 alarmsIf an equipment alarm of the CC is present try to fix this fault first which probably alsoeliminates the Iub link broke down alarm.

!WARNINGTo avoid damage to health, you must observe the regulations regarding protectionagainst radiation from laser devices (EN 60825 / IEC 60825). You must always use ded-icated laser-protective goggles. Never look into open fiber-optic cable ends, as this maydamage your eyes.

OutputsNode B

OML:Node B


200657 - SSCOP sent overrun


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


Managed Object Class / Hardware Type: CcEvent Type: equipmentAlarmProbable Cause: LinkFailureSeverity: critical



200658 - Transmit bandwidth limit for NBAP reached


Error Description

Under conditions with high traffic, the NBAP bandwidth set at the reporting Node Bs Iubinterface may not be sufficient. If the high-traffic condition persists, the Node B will startdropping messages.

This alarm therefore indicates a general lack of bandwidth to send messages at theNode Bs Iub interface. In other words, the Node Bs transmit bandwidth for NBAP con-nections 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 be-cause dedicated measurement reports will be dropped and RL setup or reconfigurationattempts will be rejected.

The reporting Node B continues operation. Service quality, however, is decreased. Theincreased traffic thus requires appropriate settings for the transmit bandwidth at theNode Bs Iub interface. In other words, the Node Bs database (DB) settings have to berevised 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 conditionin the future:

1. Revise the reporting Node Bs DB settings in such a way that the NBAP transmitbandwidth is increased.Increase both the ingress and the egress peak cell rate to an identical value, usingthe following commands: Set peakCellRateIngress TrafficDescriptor Set peakCellRateEgress TrafficDescriptor

2. If the first action did not clear the cause for this alarm, contact the technical assis-tance center (TAC) to get support in isolating the fault. For suitable preparation savethe error symptoms as described in "Collect Info for Assistance". Log files need tobe analyzed and specific measures must be taken which are out of the operatorsscope.

Managed Object Class / Hardware Type: NodeBFddEEvent Type: qualityOfServiceAlarmProbable Cause: System ResourcesOverloadSeverity: minor

OutputsNode B

OML:Node B


200659 - Core Controller overload protection activated


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 actionof 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 qualityis decreased.

The causes for the Node Bs high CPU load needs to be investigated.

Troubleshooting

First, investigate the causes for the high CC load.


Managed Object Class / Hardware Type: NodeBFddEEvent Type: qualityOfServiceAlarmProbable Cause: System ResourcesOverloadSeverity: minor



200706 - An error occurred in the nbDatabase


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

ware 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 fol-lowing 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 soft-ware. Proceed according to the OGL:Node B DB Editing Guide.

Adapt the database according to the results of this check. Proceed according tothe 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 accord-

ing to the OGL:Node B DB Editing Guide. Check the Node B database to generate a new database that matches the hard-

ware configuration. Use the mibCheck or mibCheckWin tool. Proceed accordingto 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 EditingGuide.

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, pro-

ceed 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. Forsuitable preparation save the error symptoms as described in "Collect Info for As-sistance". Log files need to be analyzed and specific measures must be taken whichare out of the operators scope.

Managed Object Class / Hardware Type: OsuEvent Type: processingErrorAlarmProbable Cause: SoftwareErrorSeverity: critical

OutputsNode B

OML:Node B


200707 - A warning occurred in the nbDatabase


Error Description

There may be an error in the nbDatabase. This warning only occurs during a version up-grade of the database.

There may be the following causes:

1. During version upgrade: There are missing attributes because of using a databasefrom an older version.

2. No version upgrade: The database is defective or a new database was installed butdoes 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 soft-ware. Proceed according to the OGL:Node B DB Editing Guide.

Adapt the database according to the results of this check. Proceed according tothe OGL:Node B DB Editing Guide.

Managed Object Class / Hardware Type: OsuEvent Type: processingErrorAlarmProbable Cause: SoftwareErrorSeverity: warning

i NOTESoftware load and database must base on the same InfoModel which isalso the basis for the Command Manual CML:Node B.



200756 - System call unsuccessful


Error Description

A fatal software error has occurred. This is a recoverable error situation caused by a po-tentially 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 anunsuccessful system call, the Node B resets automatically. Due to the reset, all serviceswill 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 cellsare build up again, connection with the RNC will be re-established and any cross con-nections 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 forAssistance". Log files need to be analyzed and specific measures must be takenwhich are out of the operators scope.

Managed Object Class / Hardware Type: *Event Type: processingErrorAlarmProbable Cause: SystemCallUnsuccesfulSeverity: critical

OutputsNode B

OML:Node B


200757 - Unexpected software error


Error Description

A fatal software error has occurred. This is a recoverable error situation caused by a po-tentially 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 anunexpected software error, the Node B resets automatically. Due to the reset, all servic-es will be interrupted.



Once the reset is completed, normal operational service should be resumed i.e. the cellsare build up again, connection with the RNC will be re-established and any cross con-nections 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 forAssistance". Log files need to be analyzed and specific measures must be takenwhich are out of the operators scope.

Managed Object Class / Hardware Type: *Event Type: processingErrorAlarmProbable Cause: SoftwareErrorSeverity: critical



200758 - Not enough memory


Error Description

A fatal software error has occurred. This is a recoverable error situation caused by a po-tentially serious software fault, which should be reported to customer services. The re-covery will result in a complete reset of the Node B. Due to the reset, all services will beinterrupted.



All connections to the management system will also be interrupted during this reset pe-riod. Once the reset is completed, normal operational service should be resumed i.e. thecells are built up again, connection with the RNC will be re-established and any crossconnections will be built up again. Any calls that were in operation before the reset arelost.

Troubleshooting


Managed Object Class / Hardware Type: *Event Type: processingErrorAlarmProbable Cause: OutOfMemorySeverity: critical

OutputsNode B

OML:Node B


200759 - A fatal error has occurred that may affect OAMcommand processing


Error Description

A fatal software error has occurred! This is a recoverable error situation caused by a po-tentially serious software fault, which should be reported to customer services. The re-covery will result in a complete reset of the Node B. Due to the reset, all services will beinterrupted.



All connections to the management system will also be interrupted during this reset pe-riod. Once the reset is completed, normal operational service should be resumed i.e. thecells are built up again, connection with the RNC will be re-established and any crossconnections will be built up again. Any calls that were in operation before the reset arelost.

Troubleshooting


Managed Object Class / Hardware Type: *Event Type: processingErrorAlarmProbable Cause: SystemCallUnsuccessfulSeverity: critical



200905 - VSWR alarm Low


Error Description

Each antenna port of the DUAMCO/RRH is monitored for the Voltage Standing WaveRatio (VSWR) of the connected antenna system. Two levels for the antenna return losscan be defined for which an alarm of the appropriate severity will be generated as soonas the relevant threshold is exceeded. The VSWR alarm Low is the minor one - whichis under consideration here - related with the lower threshold and may be received be-fore alarm 200906 - VSWR alarm High. The most likely reason for the VSWR alarms isa 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 antennasystem is equipped with a TMA / DTMA or not. This is known from the site specific doc-umentation 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-circuitfeeder cable or a faulty TMA itself

For an effective trouble-shooting the actions in the following order should be performedwith reference to the relevant manuals:

1. Inspect the antenna, the feeder cable and the TMA - if mounted - visually for anydamage 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 Mainte-

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

Managed Object Class / Hardware Type: Duamco, RrhEvent Type: equipmentAlarmProbable Cause: TransmitterAntennaNotAdjustedSeverity: minor

!WARNINGWhen replacing antenna cables, antennas, TMAs or DUAMCOs switch off the relevantbreakers which supply the LPAs/CATs involved in the affected antenna branch in orderto prevent an uncontrolled emission of microwave radiation. For RRHs, switch off thepower supply to prevent uncontrolled emission of microwave radiation.

OutputsNode B

OML:Node B


4. If none of the causes above can be identified for the alarm the DUAMCO or RRH isassumed to be defective. Replace the DUAMCO or RRH. Replacement must be done according to the

Maintenance Manual MMN:Node B



200906 - VSWR alarm High


Error Description

Each antenna port of the DUAMCO/RRH is monitored for the Voltage Standing WaveRatio (VSWR) of the connected antenna system. Two levels for the antenna return losscan be defined for which an alarm of the appropriate severity will be generated as soonas the releveant threshold is exceeded. The 200905 - VSWR alarm Low is the minor onerelated with the lower threshold and may be received before the VSWR alarm Highwhich is under consideration here. The most likely reason for the VSWR alarms is a de-fective antenna feeder cable or a damaged antenna.

As a consequence, cells or calls could potenitally be lost. Furthermore, the states of allaffected managed objects is changed accordingly.

Troubleshooting

To isolate the origin of the high return loss it is necessary to know whether the antennasystem is equipped with a TMA / DTMA or not. This is known from the site specific doc-umentation 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-circuitfeeder cable or a faulty TMA itself

For an effective trouble-shooting the actions in the following order should be performedwith reference to the relevant manuals:

1. Inspect the antenna, the feeder cable and the TMA - if mounted - visually for anydamage 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 Mainte-

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

Managed Object Class / Hardware Type: Duamco, RrhEvent Type: equipmentAlarmProbable Cause: TransmissionAntennaFailureSeverity: major

!WARNINGWhen replacing antenna cables, antennas, TMAs or DUAMCOs switch off the relevantbreakers which supply the LPAs/CATs involved in the affected antenna branch in orderto prevent an uncontrolled emission of microwave radiation. For RRHs, switch off thepower supply to prevent uncontrolled emission of microwave radiation.

OutputsNode 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



200907 - RX alarm Low


Error Description

This alarm occurred because one branch of an RX amplifier of the reporting LRU hasfailed. 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 DUAMCOor the TMA or the RRH as soon as possible. Perform the following tasks in the orderdescribed:

First, before replacing the equipment, try to reset the reporting MOC. Use the TREEView window of the LMT or apply the rst command to the relevant managed object.

If the alarm persists after the reset, replace the DUAMCO or the TMA or the RRH. Re-placement must be done according to the Maintenance Manual MMN:Node B.

Managed Object Class / Hardware Type: Duamco, Tma, RrhEvent Type: equipmentAlarmProbable Cause: ReceiverFailureSeverity: minor

i NOTEDuring the reset and the repair action the cell is not available.

!DANGERTo avoid the danger of an uncontrolled emission of microwave radiation, switch off thebreakers 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.

i NOTEBefore replacing the DUAMCO, set the DIP-switches on the front side of the DUAMCOin the same configuration as it was on the replaced DUAMCO.

i NOTEAfter replacing the TMA, reset the DUAMCO via LMT or reset button. When resettingthe 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.

OutputsNode B

OML:Node B


200908 - RX alarm High


Error Description

This alarm occurred because both branches of an RX amplifier of the reporting LRUhave failed.

If the alarm message is sent by the TMA, the MUCO mode in the DUAMCO will switchback to AMCO mode. After the reset, the DUAMCO will be in its original mode accordingto 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 allaffected managed objects change accordingly.

Troubleshooting

Reset the reporting MOC. Use the TREE View window of the LMT or apply the rst com-mand to the relevant MOC.

If the alarm persists after the reset, replace the DUAMCO or the TMA. Replacementmust be done according to the Maintenance Manual MMN:Node B.

Managed Object Class / Hardware Type: Duamco, Tma, RrhEvent Type: equipmentAlarmProbable Cause: ReceiverFailureSeverity: major

i NOTEDuring the reset and the repair action the cell is not available.

!DANGERTo avoid the danger of an uncontrolled emission of microwave radiation, switch off thebreakers 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.


i NOTEAfter replacing the TMA, reset the DUAMCO via LMT or reset button. When resettingthe 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 Viewwindow or the rst command.



200909 - TMA switched off, but not defective


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 per-formance. 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 (AM-CO 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 alarmlike 200908 - RX alarm High.

Troubleshooting

Check the power supply for the TMA at the associated DUAMCO. Furthermore, verifythat the TMA is connected to the DUAMCO and check if the DIP switch 1 of the DUAM-CO (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 beon (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 thecorresponding alarm description. Please note that the DIP switch 1 may be in the ONposition in this case.

Managed Object Class / Hardware Type: TmaEvent Type: equipmentAlarmProbable Cause: PowerSupplyFailureSeverity: minor

OutputsNode B

OML:Node B


200910 - TMA feeder alarm


Error Description

The DUAMCO monitors the 2.176 MHz signaling carrier coming from the TMA. A break-down of this carrier initiates the TMA Feeder Alarm. The amplifier is degraded in its per-formance. The combination of OST/AVS for the addressed TMA and the relatedlocalCellE managed object instance changes to disabled /failed and enabled /degrad-ed, 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 com-munication 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-establishthe communication between the DUAMCO and the TMA. A reset of the TMA managedobject is not possible while this failure persists.

Troubleshooting

1. First, reset the related DUAMCO to re-establish the communication between theDUAMCO 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 feedercable and measure the voltage at the antenna port of the DUAMCO. If the voltageis below the defined threshold, the DC/DC converter of the DUAMCO is defective.Replace the DUAMCO. Replacement must be done according to the Mainte-nance Manual MMN:Node B

If an additional VSWR alarm (200905 - VSWR alarm Low or 200906 - VSWRalarm 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, thefault is caused by a short circuit in the antenna feeder cable or an overchargedTMA. Check the antenna feeder cable.

Managed Object Class / Hardware Type: TmaEvent Type: equipmentAlarmProbable Cause: ReceiverFailureSeverity: minor

!DANGERTo avoid the danger of an uncontrolled emission of microwave radiation, switch off thebreakers for the related LPAs/CATs before replacing the TMA or DUAMCO.



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


i NOTEAfter replacing the TMA, reset the DUAMCO via LMT or reset button. When resettingthe DUAMCO via reset button, press the button for at least eight seconds. Otherwisethe reset will not become effective. Then reset the TMA (via LMT). Use the TREE Viewwindow or the rst command.

OutputsNode B

OML:Node B


200911 - TMA DC alarm


Error Description

The power supply for the TMA is fed via the antenna feeder cable from the DUAMCO tothe TMA. If the supply voltage for the TMA at the antenna port of the DUAMCO is belowthe 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 addition-ally active.

The TMA is overcharged. The current consumption of the TMA is too high.

The amplifier is degraded in its performance.

Troubleshooting

1. Unplug the antenna feeder cable and measure the voltage at the antenna port of theDUAMCO. If the voltage is below the defined threshold, the DC/DC converter of theDUAMCO is defective. Replace the DUAMCO. Replacement must be done accord-ing to the Maintenance Manual MMN:Node B

2. If the alarm message is cleared after unplugging the antenna feeder cable, the faultis 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 mustbe done according to the Maintenance Manual MMN:Node B

Managed Object Class / Hardware Type: DuamcoEvent Type: equipmentAlarmProbable Cause: EquipmentFailureSeverity: minor

!DANGERTo avoid the danger of an uncontrolled emission of microwave radiation, switch off thebreakers for the related LPAs/CATs before replacing the TMA or DUAMCO.


i NOTEAfter replacing the TMA, reset the DUAMCO via LMT or reset button. When resettingthe 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 Viewwindow or the rst command.



200914 - Fan unit failed


Error Description

One of the fan units in the Node B is defective. There might be a failure of componentssensitive to heat. Caused by the lack of air circulation, there might occur temperaturealarms, 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

Managed Object Class / Hardware Type: FanEvent Type: environmentalAlarmProbable Cause: FanFailureSeverity: major

i NOTEIf the reporting Node B is of type NB-441/NB-881, the lack of air circulation may becaused by a polluted membrane filter (MEF). Therefore, if the Node B site is located inheavily air-polluted environments combined with special temperature conditions, amaintenance 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 completelyblocked alarm is output. Refer to the relevant alarms error description and follow thetroubleshooting.

i NOTETo avoid toggling of this alarm from the same managed object, i.e. the alarm is raisedand 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 thesame alarm again for at least 100 seconds.Otherwise, this alarm will not be ceased but remains active. Troubleshooting tasks mustbe taken.

OutputsNode B

OML:Node B


Troubleshooting

1. Identify the defective fan unit. Use either the TREE View window or the ALARM Viewwindow of the LMT.

2. Replace the fan unit. Replacement must be done according to the MaintenanceManual MMN:Node B

i NOTEIf all fan units of the B-shelf are defective, self-disabling of B-shelf cards can occur as aconsequence. The Node B handles self-disabled cards as if a fatal board failure, suchas an on-board power supply failure, has occurred. In other words, the combination ofOST/AVS changes to disabled /not installed and the LED of the self-disabled card isoff.

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

!CAUTIONWhen pulling out the fan module, the rotor may still rotate for a few seconds. Watch yourfingers.



200915 - Site input alarm detected


Error Description

A site input alarm was detected.

This alarm is raised if one of the connected site input sensors is active, e.g. water de-tector, site door open switch, window broken, air condition system defect, etc.

The reported Probable Cause and Severity in the Failure Event Report depend onthe 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 equivalentstring.

The ExtEquipIn instances ExtEquipIn.4 to ExtEquipIn.12 at the RRH are reservedfor reporting alarms related to the power supply units for RRHs (PSRs). These Ex-tEquipIn instances have to exist in the database in configurations with RRHs.

Whereas the value of the probableCause attribute label is represented by a num-ber 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: PowerSupply-Failure) listed in the following table may be displayed.

For explanations of customizing a nbDatabase please refer to the relevant chapter ofthe OGL:Node B DB Description.

Managed Object Class / Hardware Type: ExtEquipInEvent Type: environmentalAlarmProbable Cause: ExternalEquipmentFailureSeverity: minor, major, critical

i NOTEChanging the ExtEquipIn managed objects alarm severity, alarm value, associatedstring, and probable cause attributes does not affect an existing 200915 - Site inputalarm detected alarm. The modified attributes will take effect for the next occurrence ofthis alarm.When modifying the attributes mentioned above, however, only one attribute can bechanged simultaneously. In other words, when using the relevant command for settingthese attributes, only one single attribute of one single managed object can be set.

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

OutputsNode 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/Mod-ules.

Troubleshooting

1. Inspect the supervised object for being in false condition and get rid of the alarmcausing conditions, e. g. window broken or air condition system defect.

2. If the alarm is active even though no unusual conditions are identifiable, the super-vision 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 assis-tance center (TAC) to get support in isolating the fault. For suitable preparation savethe error symptoms as described in "Collect Info for Assistance". Log files need tobe analyzed and specific measures must be taken which are out of the operatorsscope.

iIf the following alarm properties are displayed after the system was in battery backupoperation 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 ToleranceBefore re-charging is finished and battery is full again, it may happen that the alarm os-zillates sometimes. When battery is fully charged the alarm is ceased durable.



200916 - Rack Door open


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 isnot 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, resultingin the malfunction.

Troubleshooting

1. Inspect the doors f

Documents

nodeboml