Nokia 3G RAN Key Alarm Indicators 23

3G RAN Key Alarm Indicators

dn0628062 Issue 1-0

© Nokia Oyj

1 (23)


The information in this document is subject to change without notice and describes only the product defined in the introduction of this documentation. This document is intended for the use of Nokia's customers only for the purposes of the agreement under which the document is submitted, and no part of it may be reproduced or transmitted in any form or means without the prior written permission of Nokia. The document has been prepared to be used by professional and properly trained personnel, and the customer assumes full responsibility when using it. Nokia welcomes customer comments as part of the process of continuous development and improvement of the documentation.

The information or statements given in this document concerning the suitability, capacity, or performance of the mentioned hardware or software products cannot be considered binding but shall be defined in the agreement made between Nokia and the customer. However, Nokia has made all reasonable efforts to ensure that the instructions contained in the document are adequate and free of material errors and omissions. Nokia will, if necessary, explain issues which may not be covered by the document.

Nokia's liability for any errors in the document is limited to the documentary correction of errors. NOKIA WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN THIS DOCUMENT OR FOR ANY DAMAGES, INCIDENTAL OR CONSEQUENTIAL (INCLUDING MONETARY LOSSES), that might arise from the use of this document or the information in it.

This document and the product it describes are considered protected by copyright according to the applicable laws.

NOKIA logo is a registered trademark of Nokia Oyj.

Other product names mentioned in this document may be trademarks of their respective companies, and they are mentioned for identification purposes only.

Copyright © Nokia Oyj 2006. All rights reserved.

2 (23) © Nokia Oyj

dn0628062Issue 1-0

Contents

Contents

1 Introduction to Key Alarm Indicators ...................................................5 1.1 Concept of Key Alarm Indicator................................................................5 1.1.1 The original problem.................................................................................5 1.1.2 Solution offered via Key Alarm Indicators ................................................6 1.2 Hierarchy..................................................................................................6 1.2.1 System layers concerning alarms ............................................................7 1.3 KAI template.............................................................................................8

2 Currently available Key alarm Indicators.............................................9 2.1 Key Alarm Indicators based on services ..................................................9 2.2 Key Alarm Indicators related to resources ...............................................9 2.2.1 UTRAN access point out of use ...............................................................9 2.2.2 Base Station out of use ..........................................................................10 2.2.3 HSDPA not accessible in UTRAN access point .....................................12 2.2.4 RAN NE critical hardware failure............................................................13 2.2.5 System overload ....................................................................................15 2.2.6 System security violation........................................................................18 2.2.7 RNC hardware failure.............................................................................19 2.3 Key Alarm Indicators related to shared resources .................................23

dn0628062 Issue 1-0

© Nokia Oyj

3 (23)


4 (23) © Nokia Oyj

dn0628062Issue 1-0

Introduction to Key Alarm Indicators

1 Introduction to Key Alarm Indicators 1.1 Concept of Key Alarm Indicator

The concept of Key Alarm Indicator (KAI) has been developed because of various problems detected in previous RNC releases concerning the operability of the system performed via alarms.

In the first phase the KAIs are only documented and the monitoring tool support will become available later.

1.1.1 The original problem

Traditionally, a significant portion of the alarms has originated from lower level software design specifications whenever it has become apparent that a certain fault prohibits the normal functioning of the system. Since the people who define the alarms are responsible for only a small part of the system functionality, the effect of the alarms in a live network cannot be estimated for the whole system.

The large number of alarms, coming from different sources, makes system fault monitoring on RAN level challenging. The system does not give enough support to the end user in fault analysis and it is difficult to see which alarms are related to each other.

The affected entity should be reported from the viewpoint of the user and a fault be targeted, for example, to a base station instead of a certain computer unit in the network element. The user normally wants to see the affected part of the network, but this is currently not possible, for example, because the generic transmission layer alarms contain no information on the related radio network object (such as the base station).

dn0628062 Issue 1-0

© Nokia Oyj

5 (23)


1.1.2 Solution offered via Key Alarm Indicators

The purpose of the KAI concept is to produce RAN level indicators that the system should offer to the user about faults in the network. This is achieved by specifying situations that should be reported to the user as alarms at the system level. These situations are limited to a few basic cases that the users have to deal with in their everyday work so that the consequences of the faults can be seen effectively. From the RAN operating personnel point of view, the status of an individual cell or base station is usually interesting, and this would therefore be one example of a KAI.

The KAIs themselves are not necessarily generated by the network elements but rather by the network monitoring tools. In practice this means alarm correlation according to rules that are applied to the alarms produced by the system in Nokia NetAct (in other words, the KAIs are very much like correlation rules). The main idea, however, is to steer the usage of alarms in network elements so that alarm correlation can be effectively utilized in the monitoring tools. This means that alarms that occur because of a certain fault in the system can be somehow linked to each other, for example through alarm target object. Furthermore, the defined alarms should cover the necessary parts of the system that are needed for a certain service, such as a working cell. This enables the user to see what kinds of faults there are in the system and what the affected part is.

The KAIs can also provide classification for alarms that arrive from the network elements. Such classification helps in analysing the alarm situation when certain kinds of faults are grouped together. These kinds of classification examples are, for example, alarms about overload or security violation situations.

1.2 Hierarchy

In the first phase the KAIs are resource-based, meaning that unavailability of resources (physical or logical) is informed as KAIs. Separate KAIs are to be defined for different scopes (for example, cell, base station or RNC). This means that the KAI tells to the user how large the affected area of a fault (or a group of faults) is.

In the second phase the KAIs can be also based on services. This means that the Key Performance Indicators (KPIs) can be used to trigger alarms if a defined threshold is exceeded. This kind of alarm is not necessarily a result from a certain clear fault in the system, but they can inform the user about temporal instabilities that cause performance data to be under expected results within certain periods of time. Since the performance management data is not handled in real time, it is essential to understand that these kinds of alarms cannot be reported with high priority since the problem may have already disappeared. However, this makes it possible to keep the system maintenance personnel

6 (23) © Nokia Oyj

dn0628062Issue 1-0

Introduction to Key Alarm Indicators

informed so that they can start appropriate troubleshooting actions even if there are no clear problems visible in alarm monitoring tools.

1.2.1 System layers concerning alarms

Figure 1 presents the system levels related to a service. Service is used here as a very generic concept, it can be for example RAB or cell (UTRAN access point) in working state. Service is thus something that the end user knows and that can be affected because of faults in the system.

Figure 1. System layers for services

The status of a service depends on the services and resources provided by the lower levels of the system. For example a cell in working state needs certain configuration parameters (management of resources), ATM resources for different control and user plane links (logical resources), physical layer links like STM-1 (physical layer) and finally certain hardware to provide all the mentioned services (signalling units, exchange terminals).

The lower the level of the fault is in the system, the more it affects the service level. This is because certain hardware resources can provide services for a number of cells, for example. Thus the lower level faults may have larger impact on system level than faults in upper layers.

This kind of categorization is to be taken into account when the KAIs are specified. The system already provides alarms for all these layers, but the connection between lower and upper layers is not visible from the alarms. Mapping the lower layers to upper layers is usually ambiguous, and some kind of metadata would therefore be needed in order to reflect the actual effects of lower level faults to upper layers.

dn0628062 Issue 1-0

© Nokia Oyj

7 (23)


1.3 KAI template

KAI NAME: <Descriptive name for the KAI. The name should specify the fault clearly from the user and system operability point of view.>

Published: <Publish date>

KAI ID: <KAI identifier, format RAN_KAI_XXXX>

KAI version: <version number x.y.z>

Description: <Clear description of the situations where the KAI is used and its context (related alarms and so on)>

KAI Class: <Resource, Service>

KAI scope: <Scope of the KAI (Cell, Base Station, RNC, RAN)>

Release: <RAN release that supports the KAI>

Trigger: <Alarms, KPIs>

Effect: <Effects on the system functionality when the KAI is triggered>

Alarms: <Alarms related to this KAI and their source (physical layer, logical layer, mapping to the KAI scope)>

8 (23) © Nokia Oyj

dn0628062Issue 1-0

Currently available Key alarm Indicators

2 Currently available Key alarm Indicators 2.1 Key Alarm Indicators based on services

The service based key alarm indicators are not yet available in RAS05. The following are examples of KAIs considered for future releases:

• Sleeping UTRAN access point

• Service quality degraded

• Network quality degraded

2.2 Key Alarm Indicators related to resources

2.2.1 UTRAN access point out of use

KAI NAME UTRAN access point out of use

Published RAS05

KAI ID RAN_KAI_0001

KAI version 1.0.0

Description This indicator tells the user that the individual cell (UTRAN access point) in question is currently out of use and the cell cannot transmit any traffic. The cell is blocked by the system because of some fault that prevents the normal operation. Alarms related to this KAI need to be examined to deduce the actual root cause for the situation.

KAI Class Resource

dn0628062 Issue 1-0

© Nokia Oyj

9 (23)


KAI scope Individual Cell

Release RAS05

Trigger Triggered based on lower layer alarms

Evaluation NMS combines all alarms targeted to the cell in question under alarm 7771 WCDMA CELL OUT OF USE triggered by the RNC.

Effect The cell cannot transmit any traffic.

Alarms Base Station originated alarms:

7653 CELL FAULTY

• Hardware fault in the base station has an effect on the cell. The cell is unavailable for all traffic.

RNC originated alarms:

7761 RNW O&M SCENARIO FAILURE when targeted to a cell

• A cell-related scenario (such as cell unlocking) has failed. The target object of the alarm is not available for traffic.

7771 WCDMA CELL OUT OF USE

• This alarm follows unexpected state changes of a WCEL object and it is set whenever the state of the WCEL object changes from working to a blocked state.

2.2.2 Base Station out of use

This KAI indicates that all cells of a base station are down. There may also be related cell alarms but the effect is in the scope of a base station. No traffic is possible in the area of this base station.

KAI NAME Base Station out of use

Published RAS05

KAI ID RAN_KAI_0002

KAI version 1.0.0

Description This indicator tells the user that all WCDMA cells under certain base station are currently out of use and the base station cannot transmit any traffic. All of the cells are blocked by the system because of a fault that

10 (23) © Nokia Oyj

dn0628062Issue 1-0


prevents the normal operation. Alarms related to this KAI need to be examined to deduce the actual root cause for the situation.

KAI Class Resource

KAI scope Single Base Station

Release RAS05


Evaluation NMS combines all alarms targeted to the base station and its cells under single entity in NetAct alarm monitor.

Effect The base station cannot transmit any traffic.

Alarms HW problem in base station:

7650 BASE STATION FAULTY alarm triggered by the base station

• A critical fault has occurred in the base station. None the cells of this base station are capable of transmitting traffic.

Logical layer (ATM connections):

2499 CONTROL CHANNEL FAILURE

• NBAP or AAL 2 signalling fails because the control channel is not available. Control channel messages cannot be sent to the base station and no new user channels can therefore be established.

3117 FAILURE IN SAAL UNI SIGNALLING LINK ACTIVATION

• AAL type 2 signalling link activation has failed. Signalling connection towards the base station does not work.

3129 AAL TYPE 2 RESET FAILED

• AAL type 2 channel or channels cannot be made available for new traffic. Consequent AAL2 user data connection establishment may fail.

3264 AAL TYPE 2 UNBLOCKING FAILED

• Unblocking of AAL type 2 path (virtual connection endpoint) was not successful and the state of the connection is no longer working (WO-EX). The path cannot be therefore used for AAL2 connections.

dn0628062 Issue 1-0

© Nokia Oyj

11 (23)


RNC originated alarms:

7761 RNW O&M SCENARIO FAILURE (when targeted to a base station)

• A base station related scenario (such as WBTS initialization) has failed. The target object of the alarm is not available.

7771 WCDMA CELL OUT OF USE for all the cells of a certain base station

• This alarm follows unexpected state changes of a WCEL object and it is set whenever the state of the WCEL object changes from working to a blocked state. The alarm is set individually for specific WCEL objects and when all the WCEL objects under one WBTS object have this alarm, the whole base station is incapable of transmitting traffic.

2.2.3 HSDPA not accessible in UTRAN access point

This KAI indicates the unavailability of HSDPA hardware and/or physical resources concerning certain UTRAN access point.

KAI NAME HSDPA not accessible in UTRAN access point

Published RAS05

KAI ID RAN_KAI_0007

KAI version 1.0.0

Description This indicator tells the user that HSDPA hardware and/or physical resources are not accessible concerning specific UTRAN access point.

KAI Class Resource

KAI scope Single WCDMA Cell

Release RAS05

Trigger Triggered based on alarms generated by the network.

Evaluation NMS combines all alarms targeted to the HSDPA under single entity in NetAct alarm monitor.

Effect HSDPA is not available in a certain UTRAN access point.


dn0628062Issue 1-0


Alarms Base station generated alarms from HW problems:

7650 BASE STATION FAULTY

• A critical fault has occurred in the base station. None the cells of the base station are capable of transmitting traffic and thus also HSDPA is unavailable in this base station.

7651 BASE STATION OPERATION DEGRADED

• A major fault (or faults) has occurred in the base station. Depending on the fault details this alarm may indicate problems with HSDPA (see also alarm 7776 below).

7653 CELL FAULTY

• Hardware fault in base station has an effect on a cell. The cell is unavailable for all traffic.

7654 CELL OPERATION DEGRADED

• Hardware fault in base station has an effect on a cell. Depending on the fault details this alarm may indicate problems with HSDPA (see also alarm 7776 below).

RNC generated alarms:

7772 PHYSICAL SHARED CHANNEL CONFIGURATION FAILED

• HSDPA channel configuration or reconfiguration to a base station has failed. HSDPA is not available in the given cell.

7776 HSDPA FAILURE IN WCEL

• Base station has informed the RNC that it cannot provide HSDPA. The reason for the fault is either a hardware failure or a lack of capacity in the base station. See base station generated alarms for fault details.

2.2.4 RAN NE critical hardware failure

This KAI indicates that certain hardware unit is faulty in the network element and it is disturbing the operation of the system.

KAI NAME RAN NE critical hardware failure

Published Not yet published.

dn0628062 Issue 1-0

© Nokia Oyj

13 (23)


KAI ID RAN_KAI_0008

KAI version 1.0.0

Description This indicator tells the user that all WCDMA cells under certain base station are currently out of use and the base station cannot transmit any traffic. All of the cells are blocked by the system because of a fault in the RNC or base station that prevents the normal operation. Alarms related to this KAI need to be examined to deduce the actual root cause for the situation.

KAI Class Resource

KAI scope Single Base Station

Release RAS05


Evaluation NMS combines all alarms targeted to the base station and its cells under single entity in NetAct alarm monitor.

Effect The base station cannot transmit any traffic.

Alarms Hardware problem in Base Station:

7650 BASE STATION FAULTY

• A critical fault has occurred in the base station. None the cells of this base station are capable of transmitting traffic. See the information about failed unit in the base station from the alarm supplementary information.

RNC originated critical hardware failures:

In general, all CRITICAL alarms when targeted to RNC functional units.

2693 ACTIVE UNIT FAULTY

• An active unit is faulty and the system cannot move the unit into testing state because there is no spare unit available. The effect on the system depends on the tasks that the faulty unit performs.

2699 CRITICAL UNIT IN INCORRECT WORKING STATE

• A non-redundant unit or a unit essential for the operation of the system is not in use. If the unit in question is a spare unit of a 2N-redundant unit, there is no redundancy for this unit type. The effect on the system depends on the tasks that the unit in question performs.


dn0628062Issue 1-0


2819 SCSI DEFECT

• SCSI access is not possible. Writing data to an SCSI device (such as a hard disk) fails. The device is diagnosed automatically.

2861 NO ACCESS TO DISK

• Hard disk access from a certain unit is not possible. The unit in question is treated as faulty and recovery actions are started.

2.2.5 System overload

This KAI indicates that there is a hardware-related overload situation in the network that may have an effect on the service level.

KAI NAME System overload


KAI ID RAN_KAI_0006

KAI version 1.0.0

Description This indicator tells the user that there is a hardware resource overload situation in the network. This may have an effect on the user-perceived service quality.

The overload situation may occur because of insufficient resources, system configuration problem or hardware malfunction. The actual reason for the problem is found in the detailed alarm data.

KAI Class Resource

KAI scope RNC

Release RAS05

Trigger Triggered based on alarms reported by the network elements.

Evaluation NetAct evaluates the overload-related alarms received from the network elements and combines them under this KAI.

Effect Part of the RNC is overloaded.

Alarms RNC alarm system overflow indications:

2018 OVERFLOW IN HANDLING ALARM EVENTS

• Distributed part of the alarm system in RNC DMX units has not been able to process an

dn0628062 Issue 1-0

© Nokia Oyj

15 (23)


alarm event because all records in a work file are in use. The alarm observations are lost until free records can be found in the work file.

2724 ACTIVE ALARMS OVERFLOW

• The database of the centralized part of the alarm system in the RNC is full of live alarms. New alarms cannot be stored to the alarm database but the alarms are written to alarm history in the normal way.

3078 ALLOWED AMOUNT OF OBSERVATIONS EXCEEDED

• Distributed part of the alarm system in RNC Chorus units has not been able to process an alarm event because all records in a work file are in use. The alarm observations are lost until free records can be found in the work file.

RNC unit level overload indications:

2076 SS7 UNIT UPDATE FAILURE

• Data updating to distributed signalling unit has failed. This can have an effect on the network element’s ability to switch calls.

3197 PLUG-IN UNIT OVERHEATED

• Temperature of a plug-in unit in the RNC has overheated. The effect on the system depends on the tasks that the unit in question performs.

3186 UPPER LIMIT OF PROCESSOR LOAD EXCEEDED

• The average processor load rate of the unit has exceeded the defined limit. The effect on the system depends on the tasks that the overloaded unit in question performs.

3208 DISK UTILISATION

• The utilization rate of the hard disk has exceeded a threshold value. If the disk utilization continues to increase, the disk may fill up and cause subsequent write operations to fail.

RNC memory or resource shortage indications:

2386 OVERWRITING UNTRANSFERRED RING FILE

• Data that was expected to be transferred for post-processing is being written over because the space reserved in hard disk for this data is


dn0628062Issue 1-0


full. The data in question is usually measurement data which means that some of it is lost.

2381 AMOUNT OF FREE MEMORY CRITICALLY REDUCED

• The amount of free memory in the computer unit in the RNC is below the alarm limit used in supervision. When there is no free memory, memory reservations fail and this may disturb the functionality of the computer unit in question.

2652 PHYSICAL DISK IS FULL

• A data file creation fails because the disk is full. This alarm is usually related to measurement data collection.

2684 RUNNING OUT OF HANDS

• It is not possible to create resources (hand processes) in the RNC for handling new traffic related tasks, for example. This alarm is issued when the ratio of successful and unsuccessful hand reservations exceeds a defined error ratio limit. New reservations will succeed when existing resources (hand processes) are released.

2733 NO FREE RING DISK FILE

• The space reserved on hard disk or removable disk is full and if there are no spare storing connections, the data is lost. This alarm is usually related to measurement data collection.

3038 EVENT FORWARDER SUBSCRIBER LIST OVER FLOW

• RNC internal fault indicating that event forwarding service subscriber list is full. The effect on the system depends on the tasks of the program block that failed to subscribe events.

3045 RECOVERY EVENT SUBSCRIPTION FAILED

• Recovery event cannot receive subscriptions for recovery events. This fault has an effect on the RNC program blocks that expect to get information about activated recovery events (for example in unit switchover situations).

3054 NAME SERVICE PENDING REQUEST TABLE FULL

• The name service functionality in the RNC cannot process incoming requests. This has an

dn0628062 Issue 1-0

© Nokia Oyj

17 (23)


effect on the operation of RNC program blocks that do not get the required information (the location of a service provider in the RNC).

3102 DELAY BUFFER OVERFLOW IN SAAL

• The delay buffer of SAAL maintained by SSCF-NNI layer has filled up. Signalling message transfer of the signalling link in question is disturbed.

2.2.6 System security violation

KAI NAME System security violation


KAI ID RAN_KAI_0009

KAI version 1.0.0

Description This indicator tells the user that there is a suspected security violation in the network.

The security violation situation may happen because of attempted misuse of the system or plain user error. The actual reason for the problem is found in the detailed alarm data.

KAI Class Resource

KAI scope RNC

Release RAS05

Trigger Triggered based on alarms reported by the network elements.

Evaluation NetAct evaluates the security violation related alarms received from the network elements and combines them under this KAI.

Effect Possible misuse of the system in case of security violation. Part of the system may be unavailable due to incorrect usage.

Alarms RNC originated alarms concerning security:

0430 MMI-SESSION ANNOUNCEMENT

• Logging into MML session failed due to a faulty user ID or password. The severity of this alarm is WARNING.

0808 NEMU AUTHENTICATION FAILURES

• The limit defined for consecutive authentication


dn0628062Issue 1-0


errors in the NEMU has exceeded. The severity of this alarm is WARNING.

1569 CRITICAL LIMIT IN SECURITY REPORTING REACHED

• A critical limit of a security reporting counter has been reached. The severity of this alarm is WARNING.

2832 NE HAS INVALID USER ACCOUNT TO LDAP DIRECTORY

• A connection to the LDAP directory server or to Nokia NetAct cannot be established. The RNC cannot use its unique account for Nokia NetAct.

2.2.7 RNC hardware failure

This KAI indicates that the RNC is suffering from a hardware failure. This can have a direct effect on the user-perceived services.

KAI NAME RNC hardware failure


KAI ID RAN_KAI_0010

KAI version 1.0.0

Description This indicator tells the user that part of the network is suffering from a hardware failure.

KAI Class Resource

KAI scope RNC

Release RAS05

Trigger Triggered based on alarms received from the network element.

Evaluation NetAct monitors the alarms arriving from the network element and combines the hardware alarms under a single KAI.

Effect Some of the hardware in the RNC is not working properly. This may have an effect on RAN level functionality depending on the faulty hardware.

Alarms RNC originated alarms in case of non-critical hardware failures:

2054 CHECKSUM ERROR IN BOOT PROM

dn0628062 Issue 1-0

© Nokia Oyj

19 (23)


• The checksum of a computer unit’s initial loading program has changed. The fault may cause the unit software loading to fail at unit restart.

2347 POWER SUPPLY FAILURE IN CPU

• Power supply voltage is faulty. This has an effect on situations where a switchover is required as a recovery measure.

2379 VOLTAGE IN CLOCK CIRCUIT OF CPU HAS FAILED

• The voltage in clock circuit of the computer unit has failed. The unit is not capable of maintaining the correct time during possible power failures. This fault has no effect on the system as such because correct time is retrieved from the main clock of the RNC after the computer unit starts.

2380 CPU TIME DIFFERS FROM CALENDAR TIME

• Clock time of the computer unit differs from the calendar time of the system. The unit is not capable of maintaining the correct time during possible power failures. This fault has no effect on the system as such because correct time is retrieved from the main clock of the RNC after the computer unit starts.

2389 WATCHDOG DISABLED

• Computer unit watchdog is not functioning. This may have an effect on unit recovery actions in fault situations.

2391 CPU TYPE DIFFERS FROM EQUIPMENT

• The type of the plug-in unit differs from the equipment table. This is a possible configuration error.

2715 BROKEN INTERNAL COMMUNICATION CHANNEL

• Communication channel between two functional units does not work and communication between these functional units is not possible. The effect on the system depends on the tasks performed by the units in question.

2784 FAULTY LASER IN SDH SIGNAL TRANSMITTER

• Optical transmitter power in SDH interface has decreased and is not within the required range anymore. Eventually the transmission of the


dn0628062Issue 1-0


signal will not work in the SDH interface in question.

2794 HW BLOCK FAILURE IN PLUG-IN UNIT

• Plug-in unit hardware failure has been detected. It is considered defective and cannot perform tasks defined for it.

2818 INCORRECT OPERATING STATE

• The operating state of an I/O device is not the normal working state (WO-EX). The device may be out of use.

2860 DISK FAILURE

• The system has detected a serious error that may have been caused by the hard disk or the SCSI controller plug-in unit breaking down. Hard disk usage is not possible.

3000 PLUG-IN UNIT POWER FAILURE

• Power failure in plug-in unit has been detected. The unit in question does not work or it works unreliably.

3002 ATM TRAFFIC ERROR

• ATM traffic terminating into the plug-in unit is defective. This may be an indication of a faulty plug-in unit. If several of these alarms are active, it is possible that the fault is in the ATM multiplexer, ATM switching matrix or in the originating unit that sends the ATM message. The communication of the plug-in unit may not work or it works unreliably.

3012 DIGITAL SIGNAL PROCESSOR FAILURE

• There is a processor error in digital signal processor (DSP) or some some other hardware failure in the plug-in unit containing signal processors. Due to the failure the signal processor and the data channels handled by it are out of use.

3013 SUBRACK FAN FAILURE

• One or more fans that are cooling the subrack have been damaged. The plug-in units located in this subrack might get damaged as a consequence of rising temperature.

3015 SUBRACK FUSE FAILURE

• A fuse has blown in the PD20 plug-in unit that protects the fan tray of the subrack. A fuse of a wrong type, a faulty plug-in unit or a faulty fan may have caused this. Depending on the status

dn0628062 Issue 1-0

© Nokia Oyj

21 (23)


of other fuses the plug-in units are supplied with only one supply branch or the plug-in units may be without power.

3016 HMS POWER FAILURE

• The power supplied from the backplane of the subrack may be failing or the TSS3 plug-in unit supplying voltage for the HMS may be damaged. In the first case the redundancy of the power is lost, and in the latter case the plug-in units in the subrack are out of power.

3049 FAILURE IN PORT CONFIGURATION

• General alarm about failures in unit initialization. The unit in question is out of use. The effects of the fault depend on the tasks that the failed unit performs.

3050 NO RESPONSE FROM PLUG-IN UNIT

• The plug-in unit does not respond to messages sent to it by the hardware management system. The plug-in unit is either damaged or the connection to it is cut. The unit in question is out of use. The effects of the fault depend on the tasks that the failed unit performs.

3097 DATABASE DISK UPDATING CAN NOT ACCESS DATAFILE ON DISK

• Data access on disk fails, the disk is corrupted or full, or there is a hardware failure. This alarm is not likely to appear alone. Access of database services fails until the fault has been corrected. This has possibly a serious effect on the system because databases are used in different kinds of operations (such as radio network configuration and alarm handling).

3136 IO-DEVICE PLUG-IN UNIT POWER FAILURE

• Voltage supplied to the I/O device is not within the permitted range. The unit does not work or it is working unreliably.

3198 FAN SPEED CAN NOT BE SET

• The speed of the fan tray unit cannot be set. This may lead to rising temperature in the subrack and disturb the fuctioning of the system.

3199 EXCEPTIONALLY HIGH TEMPERATURE IN SUBRACK

• Defined upper threshold of the subrack temperature has been reached. Plug-in units can stil function but the temperature should not


dn0628062Issue 1-0


rise or the plug-in units will be damaged.

3226 EXCESSIVE HW ALARM INPUT OSCILLATION NOTICED BY HMS NODE

• State changes of hardware alarm input of a plug-in unit have exceeded the supervision limit. The most likely cause is in power feeding of a plug-in unit. The plug-in unit is probably not able to function properly any longer.

2.3 Key Alarm Indicators related to shared resources

This chapter is for further study. The system is divided into resources that are unambiguously mapped to certain radio network objects (such as base stations) and to shared resources that may have an effect on a larger part of the radio network (for example, interface unit failures in the RNC may have an effect on multiple base stations). Failures in these shared resources will lead to alarm indications for radio network objects as well, but it should be always analysed what kind of failures in shared resources there are, before attempting to correct individual radio network object specific faults.

dn0628062 Issue 1-0

© Nokia Oyj

23 (23)

Documents

Nokia 3G RAN Key Alarm Indicators 23