Alarms Analysis

Severity Slogan CountsMajor UtranCell_ServiceUnavailable 50162

Major Rach_InternalResourceUnavailable 16279

Major Fach_InternalResourceUnavailable 16058

Major Pch_InternalResourceUnavailable 15199

Major UtranCell_NbapMessageFailure 13424

Major 5981

Major 5466

Major 5371

Indeterminate Default router switch 4106Major Contact to Default Router 1 Lost 3041

Major Contact to Default Router 0 Lost 3039

Major 1486

Indeterminate 1228

UtranCell_ExternalResourceUnavailable

NbapDedicated_RncRbsControlLinkDown

NodeSynch_Phase_Difference_Measurement_Failed

NodeSynch_Phasedrift_Threshold_Exceeded

A Non-Local MAU Has Been Chosen as the Active Client

Major 830

Major Eul_NbapMessageFailure 552

Major Rach_NbapMessageFailure 471

Major Hsdsch_NbapMessageFailure 327

Warning VP ete Remote Defect Indication 306

Major Fach_NbapMessageFailure 190

UtranCell_MaxNumberOfSystemInformationUpdateReattemptsIsReached

Major Pch_NbapMessageFailure 142

Major UtranCell_RBSLocalCellNotAdded 129

Unknown Synchronization Start 104Indeterminate Synchronization End 104

Major UtranCell_ComMeasFailAdmCon 103

Indeterminate 84

Warning 72

Major VC ete Loss of Connectivity 57

Warning MTP3b Link Out of Service 55

Indeterminate PIU restarted 54Minor Ethernet Switch Port Congestion 48

Major UtranCell_ComMeasFailCongCon 43

Warning 31

IpEthPacketDataRouter_CnNotRespondingToGTPEcho

UtranCell_NbapReconfigurationFailure

SCCP Remote Subsystem Unavailable

Major DcDevice_DeviceDisabled 30Major MTP3b Route Set Unavailable 29

Warning 26

Major Ethernet Switch Port Fault 25

Critical Alarm Rate Threshold Crossed 25Indeterminate SlotNew PIU detected 15

Warning VC ete Alarm Indication Signal 12

Major Ethernet Switch Port Overload 12

Critical Heartbeat Failure 10Minor Remote IP Address Unreachable 10

Major M3UA Association Down 9

Major Loss of Signal 7Minor VC4 Degraded Signal 6

Major Hsdsch_CodeAllocationFailure 5

Gigabit Ethernet Link Redundancy Fault

Major VC4 Unequipped Defect 4

Major CcDevice_DeviceDisabled 4Indeterminate Link switched 4

Major Gigabit Ethernet Link Fault 4Indeterminate Licensing_FeatureChange 2Indeterminate RncFunction_NodeRestartCompleted 2

Indeterminate 2

Warning MS Alarm Indication Signal 2

Critical Rnsap_RemoteFailure 2

Warning VC ete Remote Defect Indication 2

Major Denib Device Configuration Fault 1

PHY_Os155Spi_MI_AUTOLOCK_IND

Causes Responsibilityremote

remote

remote

remote

remote and/or field

A problem with the Node B Application Protocol (NBAP) Audit Function remote

remote and/or field

remote and/or field

event, not a fault noneremote

remote

Node synchronization failure. remote

event, not a fault none

1.Node B Application Part (NBAP) common signaling errors. 2.No space for the IubLink in any module.

1.ATM resources 2. SP resources 3. IP resources

1. Faults in the ATM (Asynchronous Transfer Mode) Adaptation Layer type 2 (AAL2)

2.Faults on the Special Purpose Processor Board (SPB) 3. Faults in the Fach IP resources.

1. Faults in the ATM (Asynchronous Transfer Mode) Adaptation Layer type 2 (AAL2)

2.Faults on the Special Purpose Processor Board (SPB) 3. Faults in the Fach IP resources.

1. Cell not available 2.Power level not supported

3.Node B resource unavailable 4.Requested configuration not supported

5.Unknown local cell ID 6.Message not compatible with receiver state

7.Semantic error 8. Hardware failure 9. O&M intervention

10. NbapTimeout 11. NbapAuditNotReady

1.Temporary disturbances or interruptions in the Iub link 2.Temporary overload problems in the Iub link

3.An Exchange Terminal Board (ETB) failure in the RNC 4.Multiple module MP faults or over allocation of UNI-SAAL CEPs to the module

MPs are preventing allocation of UNI-SAAL terminations to module MPs. 5.An ETB failure in the Radio Base Station (RBS)

1.Radio Base Station (RBS) is faulty. 2.Timing Unit Board (TUB) SW is faulty in the RBS.

3.Exchange Terminal (ET) link is down. 4.Exchange Terminal Board (ETB) in the RNC is faulty.

5.Both Timing Units (TUs) in the RNC are faulty.

1. IP network problem.2. The router is not answering.

3. Wrong IP address configured for the router.

1. IP network problem.2. The router is not answering.

3. Wrong IP address configured for the router.

remote

remote

remote

remote

remote

remote

1. The RBS sends a System Information Update Failure message because it cannot process the update request.

2. The System Information Blocks (SIBs) or the scheduling information sent from the RNC is faulty.

1. DL shared channel type not supported 2. Unknown C-ID

3. HW failure 4. Requested configuration not supported

5. Semantic error 6. Cell not available

1. Rach_NbapMessageFailure2. Cell not available

3. Node B resource unavailable 4. HW Failure

5. Requested configuration not supported 6.Message not compatible with receiver state

7. Semantic error 8. NbapTimeout

9. NbapError 10. Binding Identity Mismatch

11. Transport Layer Address Mismatch 12. Unknown C-ID

1. DL shared channel type not supported 2. NbapError

3. Unknown C-ID 4. Cell not available

5. Node B resource unavailable 6. HW Failure

7. Requested configuration not supported 8. Message not compatible with receiver state

9. Semantic error 10. NbapTimeout

a fault in the PDH transport network a fault in the SDH transport network a fault in the ATM transport network

Unknown C-ID Cell not available

Node B resource unavailable Transport resource unavailable

Message not compatible with receiver state Semantic error NbapTimeout

UserPlane Transport Option Mismatch Transport Layer Address Mismatch

Binding Identity Mismatch

remote

remote

event, not a fault noneevent, not a fault none

remote and/or field


DlPowerDegradation remote and/or field

remote

remote and/or field

event, not a fault noneremote

remote

An alarm is issued when a user of the Signalling Connection Control Part (SCCP) in the remote node is not accessible from this node. The fault can be permanent or temporary. Normally, the alarm is temporary and ceases automatically.remote

Unknown C-ID Cell not available

Node B resource unavailable Transport resource unavailable

Message not compatible with receiver state Semantic error NbapTimeout

UserPlane Transport Option Mismatch Transport Layer Address Mismatch

Binding Identity Mismatch

The RBS Local Cell corresponding to the cell that the RNC is trying to activate is probably not configured.

RBS resources are unavailable because the maximum number of users has been reached.

The alarm is issued when no ATM cells are received in the ete ATM (end to end ATM) cell flow of the Virtual Circuit (VC) for 2.5 ±0.5 s.

An alarm is issued when the Message Transfer Part level 3 (MTP3) detects a faulty MTP3b signalling link. The fault can be permanent or

temporary. The possible causes are as follows: a transmission fault

a process or processor restart in this node a faulty ET board

a fault in the adjacent signalling node

The alarm is issued if the Ethernet switch port is becoming overloaded. The load is 80% or more of the maximum allowed load. The alarm

remains as long as the port is overloaded and ceases automatically when the load decreases. If the Ethernet switch port becomes more overloaded, this alarm is replaced by the alarm, Ethernet Switch

Port Overload. Causes:Maintenance of Ethernet switches.

Fault in the network.Under-dimensioning

Faulty link(s) in the node.

This alarm appears when the Radio Base Station (RBS) fails to report carrier power and uplink interference measurements to the Radio

Network Controller (RNC). Causes:RBS resources are unavailable.

An RBS hardware failure prevents it from performing the measurement

Device Disabled remote and/or fieldremote

One of two redundant links is in the operational state DISABLED. remote and/or field

remote and/or field

EWS noneevent, not a fault none

remote

remote and/or field

Link Failure remote and/or fieldremote and/or field

remote

remote and fieldremote

Invalid downlink code configuration remote

An alarm is issued when a user of the Message Transfer Part level 3 (MTP3) in the remote node is not accessible from this node. The fault

can be permanent or temporary.

The alarm is issued if the Ethernet Switch detects a "port fault" condition. The operational state of the port is changed to DISABLED. The alarm remains as long as the port is faulty. Normally, the fault

must be attended to on site. Causes: Link Down

The alarm is issued when an ete Alarm Indication Signal (end-to-end AIS) cell is received in the F5 Operation and Maintenance (O&M) flow

of the Virtual Circuit (VC).

The alarm is issued if the Ethernet switch port is overloaded. The load is 100% or more of the maximum allowed load. The alarm remains as long as the port is overloaded and ceases automatically when the load

decreases. If the Ethernet switch port load decreases, this alarm is replaced by the alarm, Ethernet Switch Port Congestion.

Remote IP address unreachable.

An alarm is issued when the Message Transfer Part level 3 (MTP3) detects a faulty M3UA Association. The fault can be permanent or temporary.

The possible causes are as follows:

a transmission fault a process or processor restart in this node

a faulty General Purpose processor Board (GPB) a fault in the adjacent signalling node

The alarm is issued when a specified number of the consecutive bad seconds has been detected. A second is defined as "bad" if the

detected percentage of the block errors is equal to, or greater than, the specified percentage. The values of the bad seconds (vcDegM attribute in the MO, Vc4Ttp) and errored blocks (vcDegThreshold

attribute in the MO, Vc4Ttp) can be specified. The default values are 7 seconds and 30%, respectively. The alarm indicates that the VC4 (Virtual Channel) path through the Synchronous Digital Hierarchy

(SDH) transport network is affected by bit errors.

remote

Device Disabled remote and/or fieldevent, not a fault none

There is no configured link with operational state ENABLED. remote and/or fieldevent, not a fault noneevent, not a fault none


remote and/or field

remote

remote

remote

The alarm is generated when the C2 byte received in Virtual Container 4 Path Overhead (VC4 POH) contains the pattern “00000000” in five consecutive frames. The alarm indicates that there is no payload on the affected VC4. As a consequence of the fault, the traffic on the

affected VC4 path is lost.

The alarm is generated when an Multiplexer Section Alarm Indication Signal (MS AIS) is detected in the K2 byte.

As a consequence of the fault, the traffic on the affected Synchronous Digital Hierarchy (SDH) link is lost.

The likely cause is that the MS is affected by the fault in the remote node.

Transport network errors between the RNC and the remote RNCA restart in the remote RNC or intermediate system

A Radio Network Subsystem Application Part (RNSAP) failure in the RNC or the remote RNC

The alarm is issued when an ete RDI (end-to-end RDI) cell is received in the F5 Operation and Maintenance (O&M) flow of the Virtual Circuit (VC).

The fault is not in the local node, but in a remote node, or between the two nodes through which the VC is routed. The remote node can be a

Plesiochronous Digital Hierarchy (PDH) or an Synchronous Digital Hierarchy (SDH) network element, or an ATM switch. Alarms, for example, Loss of Signal and Loss of Frame, identifying the failed entity, are reported from the network

element that detected the fault.As a consequence of the fault, the traffic is lost. If the repair of the fault requires

site visits, it might be feasible to use an alternative VC for the traffic.

A Denib device is any hardware device that is monitored utilizing the Denib protocol. Denib is an Ericsson proprietary protocol used when communicating

with certain hardware devices through a serial connection.

Cell down Capacity reduced Performance impacted SAFyes yes yes

yes

yes yes yes

yes

yes yes yes

yes

yes yes yes

yes

yes yes yes

yes

yes yes yesyes

yes yes yes

yes

yes yes yes

yes

no no no no

maybe yes maybe

yes

maybe yes maybe

yes

no no nono

no no nono

yes yes yes

yes

no yes yes

yes

yes yes yes

yes

no yes yes

yes

maybe yes yes

yes

yes yes yes

yes

yes yes yes

yes

yes yes yesyes

no no no no

no no no no

yes yes yesyes

no no nono

no yes yesyes

maybe yes yes

yes

no maybe maybe yes

no no no no

no no no

no

no yes yes

yes

no yes yesyes

no yes yes yes

no yes yes

yes

no no nono

maybe yes yes

yes

no no no no

no no no no

maybe yes maybe yes

maybe yes yes

yes

maybe maybe maybe yesno yes yes

yes

no yes yes

yes

maybe yes yes yes

maybe yes yes

yes

no yes yes yes

maybe yes yes

yes

no yes yes yes

no no no no

maybe yes yes yes

no no no no

no no nono

no no nono

maybe yes yes

yes

no yes yes

yes

maybe yes yes

yes

no no no

no

Severity Specific problem CountsMajor NTP Server Reachability Fault 45496

Warning PDH Alarm Indication Signal 37800

Major IMA Group Configuration Aborted 20092

Warning Remote Defect Indication on IMA Link 14651

Critical Heartbeat Failure 12192Major System Clock in Holdover Mode 8751

Major IMA Group Insufficient Links 8138

Minor PDH Degraded Signal 7294

Major IMA Group Insufficient Links at Far End 6210

Major PDH Loss of Frame 5699

Major Synch Reference Not Reliable 5402

Major Carrier_RxDiversityLost 5055

Major PDH Loss of Signal 3908

Major Gigabit Ethernet Link Fault 3720

Critical NbapCommon_Layer3SetupFailure 2589

Major AntennaBranch_AntennaProblemInBranchA 2486

Major Loss of Tracking 2201

Major RuDeviceGroup_TemperatureExceptionallyHigh 1353

Major RuDeviceGroup_GeneralSwError 1349

Major Carrier_SignalNotReceivedWithinTime 1284

Major TimDevice_RadioClockIsNotStable 1059

Major Ethernet Switch Port Fault 1046

Major Loss of IMA Frame 956

Warning PDH RNCI 924

Major DbccDevice_GammaDownlinkFailure 807

Major DigitalCable_Disconnected 733Major AntennaBranch_AntennaSystemProblemInBranchB 497

Major RbsLocalCell_CellReleaseFailure 409Major GeneralHwError 270

Major AntennaBranch_AntennaProblemInBranchB 264

Major SystemUndervoltage 252

Major IMA Link Reception Misconnected 208

Major AuxPlugInUnit_PiuConnectionLost 203

Major Disconnected 136

Major Carrier_RejectSignalFromHardware 134

Major IMA Link Transmission Misconnected 130

Major AntennaBranch_AntennaSystemProblemInBranchA 120

Major Plug-In Unit General Problem 112

Major 103

Major Bfu_DcDistributionFailure 95

Major Carrier_NumberOfCarriersExceedsLicensedLimit 72

BfDevice_HighOperatingTemperatureSupervisionTooHighMainLoadDisconnected

Major Carrier_MaxDlPowerCapabilityOutOfRange 72

Minor Carrier_PowerClassTruncated 72

Major SectorAntenna_FeederCurrentTooLow 71

Major RaxDeviceGroup_RaxTxInterfaceCommunicationError 69

Critical License Key File Fault 65

Major IMA Config Aborted at Far End 62

Major UbchDeviceSet_CapacityLost 53

Major DigitalCable_CableFailure 52

Warning PDH Remote Defect Indication 49

Major BfDevice_BatteryVoltageSupervisionTooLowMainLoadDisconnected 49

Warning IMA Link Transmit Unusable at Far End 48

Major PowerSupplySystem_SystemUndervoltage 45

Major BatteryVoltageTooLowMainLoadDisconnected 44

Major TrDeviceSet_GeneralSwError 44

Major TxDeviceGroup_RaxTxInterfaceCommunicationError 41

Major IMA Link Out of Delay Synchronization 31

Major RuDeviceGroup_GammaUplinkFailure 30Major Slave TU Out of Synchronization 28

Major RfCable_Disconnected 27Major RaxDeviceGroup_GeneralSWError 25

Major TrDeviceSet_GeneralHwError 25Major IMA Group Start-Up at Far End 25

Major Inter-PIU Link Fault 23Critical Loss of System Clock 17

Major RuDeviceGroup_GeneralHwError 15Major TrDeviceSet_GeneralSwError 15

Major DeviceGroup_GeneralSwError 14

Major RuifDeviceGroup_GammaUplinkFailure 14Major DeviceGroup_TemperatureExceptionallyHigh 14

Major TxDeviceGroup_GammaLinkFailure 13

Major BfDevice_BatteryVoltageSupervisionTooLowPrioLoadDisconnected 12

Major TpaDevice_AmplificationError 10

Major RuDeviceGroup_PoorClockSignal 10

Major DeviceGroup_ExternalUnitFailure 10

Warning Auto-Configuration of Board Not Possible 10

Major 9

Minor Switch Internal Link Group 0 Fault 8

Major TU Synch Reference Loss of Signal 8

Major Plug-In Unit Synch Hardware Fault 8

Minor Switch Internal Link Port 0 Fault 7

Minor TxDeviceGroup_NumberOfProcessingResourcesNotSupported 5

Major TxDevicegroup_GeneralHWError 5Major RaxDeviceGroup_SoftwareDownloadFailure 5

Major FREQUENT AuxPlugInUnit_PiuConnectionLost 5

Major TimDeviceSet_ClockFrequencyStabilityMalfunction 5

Major TimDevice_PhaseLockFailure 4

AuxPlugInUnit_NewAuxiliaryUnitDetectedNotCorrespondingToTheDefinedConfiguration

Major Plug-In Unit HW Failure 4

Major TxDevicegroup_GeneralSWError 4

Minor IMA Group Timing Mismatch 3

Major Loss of Signal 3

Major DeviceGroup_GeneralHwError 3Major PdDevice_SystemVoltageTooLow 3

Major PdDevice_InputVoltageTooLow 3

Major BfDevice_DcDistributionFailure 3

Major Switch Plane A Fault 3

Major RruDeviceGroup_FanFailure 3

Major RaxDeviceGroup_BackplaneBusCollision 3

Minor Switch Core Fault 3

Major DeviceGroup_SoftwareDownloadFailure 2

Major TrDevice_GeneralHWError 2Major RruDeviceGroup_GammaLinkFailure 2

Major RuifDeviceGroup_ClockDistributionMalfunction 2Major FuDeviceGroup_GeneralSwError 2

Minor PowerSupplySystem_BatteryOvertemperature 2

Major Bfu_BatteryVoltageSupervisionTooLowPrioLoadDisconnected 2

Major Bfu_BatteryVoltageSupervisionTooLowMainLoadDisconnected 2

Major Clu_ActiveCoolerFault 2

Major RuDeviceGroup_LossOfSynch 2

Major ObifDeviceGroup_GammaLinkFailure 2

Minor OperatingTemperatureTooHighCapacityReduced 2

Major LoPowTxCable_Disconnected 1

Major AiDeviceSet_GeneralSwError 1

Major RaxDeviceGroup_GammaLinkFailure 1

Major Clu_ExternalFanFault 1

Major RuDeviceGroup_ExternalUnitFailure 1

Major TimDeviceSet_ClockMalfunction 1

Major TU Hardware Fault 1Major RfifDeviceGroup_IncorrectCableForDeliveredClock 1

Major RfifDeviceGroup_IncorrectCableForReceivedClock 1

Major RuDeviceGroup_GammaDownlinkFailure 1

Causes

Link failure

IP network problems IP Communication problems toward NTP serverWrong IP addressWrong domain name

For E1, T1, J1 and E3 signal formats, the alarm is generated when the pattern “1111...” is detected in the signalThe alarm is issued if there is a configuration mismatch between the two nodes that are connected to this Inverse Multiplexing ATM (IMA) group. That is, the two nodes have conflicting configuration data. The IMA group rejects the configuration data received from the corresponding IMA group in the remote (far-end) node.

The possible causes are as follows:a loss of cell delineation a fault in the physical layer

TU Synch Reference Loss of Signal Network Synch Time from GPS Missing Loss of Tracking Synch Reference Path HW Fault Synch Reference Not Reliable PDH physical path termination: PDH Loss of Signal, PDH Loss of Frame, PDH Alarm Indication Signal, PDH Degraded Signal, Plug-In Unit HW Failure, or ET Hardware Fault. SDH physical path termination: Loss of Signal, Loss of Frame, MS Alarm Indication Signal, MS Degraded Signal, MS Excessive Bit Error Rate, Plug-In Unit HW Failure, or ET Hardware Fault. IP Synchronization reference: NTP Server Reachability Fault, or Gigabit Ethernet Link Fault

The alarm is issued when one or more Inverse Multiplexing ATM (IMA) links have failed, reducing the number of working IMA links within the IMA group to fewer than the configured "required no of links" for the IMA group.

The possible causes are as follows:a faulty board a service degradation on the optical receiver a faulty laser a transmission media fault the alarm, PDH Remote Defect Indication

The alarm is issued when one or more Inverse Multiplexing ATM (IMA) links have failed at the remote (far-end) node, reducing the number of working IMA links within the IMA group to fewer than the configured "required number of links" for the IMA group.The possible causes are as follows:misconfigured framing between this and the remote nodeThe most likely misconfiguration is a wrong setting in the attribute, crc4Mode in the MOs, E1PhysPathTerm or E1Ttp.PDH equipment failure in the remote node a problem or a failure along the PDH physical line ET or CBU failure in this node

Synchronization problems on the Time ServerIP network problems

AntennaProblemInBranchA AntennaProblemInBranchB AntennaSystemProblemInBranchA AntennaSystemProblemInBranchB Disconnected GammaLinkFailure GammaUplinkFailure LnaFailure GeneralHwError GeneralSwError

The possible causes are as follows:fault in the remote node line interruption ET board fault in this node

Ethernet switch or router, or the network to which the links are connected, is faulty.Board or Ethernet link is faulty.There is no configured link with operational state ENABLED.

The Layer3SetupFailure alarm is issued for the Node B Application Protocol (NBAP) Common, and means that a signalling bearer is established and the Radio Base Station (RBS) requests an audit but the Radio Network Controller (RNC) is unable to initiate an audit at setup.The likely cause of this alarm is a fault in the RNC causing a communications failure between the RBS and the RNC.

This alarm is issued by the AntennaBranch Managed Object when one of the following units is faulty or a cable is faulty or disconnected:ASCAntenna jumper cable Antenna

The system or radio clock cannot track any synchronization referenceThe system or radio clock cannot track a synchronization reference

The cause of the problem is usually not the unit issuing the alarm, but climate or environmental reasons, particularly if several boards from different subracks have issued the alarm. RBS Temperature Out Of Range offers a systematic procedure for determining the correct cause. If the alarm is issued together with a fan alarm, then the most likely cause of the alarm is a faulty fan unit If the alarm is issued on only one board, then it is probable that the board has developed a fault, in which case, it is likely that an equipment alarm has also been issued for the board

A software faultAn incorrect version of the software

This alarm is issued when an RBS internal cable has been disconnected.

Release of a cell takes more than 1 minute.The alarm indicates that a component is faulty and must be replaced.

Antenna Interface Unit (AIU) or Single Antenna Interface Unit (sAIU) Filter Unit (FU) Multicarrier Power Amplifier (MCPA) or Power Amplifier Unit (PAU) Radio Frequency Interface (RFIF) board Radio Unit (RU) Remote Radio Unit (RRU) Single Transceiver Board (sTRX) or Transceiver (TRX) board Transmit (TX) board

Faulty TUB, CBU or DUW. This alarm is critical if a single Timing Unit Boards (TUB), Control Base Unit (CBU) or Digital Unit WCDMA (DUW) is installed because the RBS is unable to carry traffic.

Hardware fault, network fault, or configuration fault.Autonegotiation has failed to meet the minimum configured requirements.The SFP Module does not meet all the initial conditions.Missing or faulty hardware.

Poor transmission qualityIncorrectly configured linksHardware faultFault in far end nodeFault in interconnecting network

The alarm is issued when the Cyclic Redundancy Check-4 (CRC-4) multiframe detector counts more than 990 far end block errors with no "far end defect second" detected, for 5 consecutive seconds.The possible causes are as follows:a faulty board a service degradation on the optical receiver a faulty laser a transmission media fault

The causes of the alarm are (depending on the RBS type):A faulty or disconnected gamma cable or digital cableA faulty BBIF boardA faulty Digital Unit WCDMA (DUW)A faulty RFIF boardA faulty Single Transceiver Board (sTRX)A faulty OBIF boardA faulty Transmitter (TX) boardA faulty RUA faulty RUIF boardA faulty REIF board

The antenna is supervised by the ASC or the RBS, which monitor Voltage Standing Wave Ratio (VSWR), DC resistance, or both. When a preset value is exceeded, the alarm is triggered.

The antenna is supervised by the ASC or the RBS, which monitor Voltage Standing Wave Ratio (VSWR), DC resistance, or both. When a preset value is exceeded, the alarm is triggered.

This alarm is issued by the PowerSupplySystem Managed Object (MO) when the system voltage is running low because of a problem with the power supply system.

The alarm is issued when there is a configuration mismatch between two nodes that are connected to this Inverse Multiplexing ATM (IMA) group. The IMA link in the receive direction is not connected to the same remote (far-end) IMA unit as the other reception links in the IMA group. It is likely that there is a corresponding IMA Link Transmission Misconnected alarm in the remote node.

This alarm is issued by the AuxPlugInUnit Managed Object (MO) when communication between one of the Auxiliary Units (AU) and the RBS is lost.

This alarm is issued when an RBS internal cable has been disconnected. The alarm is issued by the following Managed Objects (MOs):DigitalCable, for a digital cable between the Radio Unit (RU) and the Radio Unit Interface (RUIF) or between the RU and the Digital Unit WCDMA (DUW) or between two DUWs.RfCable, for cables between the RUs

The alarm is issued when processing requests to a unit are rejected by the hardware. No other unit faults are reported.The alarm is issued when there is a configuration mismatch between two nodes that are connected to this Inverse Multiplexing ATM (IMA) group. The IMA link in the transmit direction is not connected to the same remote (far-end) IMA unit as the other transmission links in the IMA group. It is likely that there is a corresponding IMA Link Reception Misconnected alarm in the remote node.

This alarm is issued by the AntennaBranch Managed Object when one of the following units is faulty or a cable is faulty or disconnected:ASCAntenna jumper cable Antenna

The alarm is issued when:All defined recovery attempts are performed for the PIU. Contact with the PIU is lost for at least five minutes.

This alarm is issued by BfDevice Managed Object (MO) when the battery temperature sensor detects a temperature above an operator-defined or hardware default value.The likely cause is one of the following:The cause of the problem is usually not the unit issuing the alarm, but climate or environmental reasons. RBS Temperature Out Of Range offers a systematic procedure for determining the correct cause. Battery failure

The cause of this alarm can be one of the following: A blown fuse or a tripped circuit breaker in the IDM/BFU or in the BFU. A circuit breaker set to OFF (all circuit breakers must be in the ON position, even if no equipment is connected)

Valid license key exceededValid license key missing

The dlAttenuation parameter for the affected antenna feeder cables is not in accordance with the information specified in the Site Installation Documentation (SID) The dlAttenuation parameter is incorrectly specified in the ExternalTma MO The dlAttenuation parameter is incorrectly specified in the TmaDeviceSet MO A faulty Antenna Interface Unit (AIU) or Single Antenna Interface Unit (sAIU) A faulty Multicarrier Power Amplifier (MCPA) or Power Amplifier Unit (PAU) A faulty Filter Unit (FU) A faulty Radio Unit (RU) A faulty Remote Radio Unit (RRU)

The calculated output power defined as MaxDlPowerCapability is 0.7 dB or more below the level reported as power class from the RU.This alarm can also occur when one of the branches in a Transmitter (TX) diversity configuration has its power class truncated.

Incorrectly connected feeder or jumper cable (if the alarm is raised immediately after antenna installation)Disconnected or broken antenna feeder cableDamaged or loosely connected jumper cable

This alarm is issued by the RaxDeviceGroup Managed Object (MO) or the TxDeviceGroup MO when there is a communication error between the Transmit (TX) board and the Random Access and Receiver (RAX) board. The connection is made through the backplane.The likely cause of this alarm is a software fault. Each TX board can handle several RAX boards. Depending on the configuration, the consequence of the fault is that the RBS capacity is reduced or that the RBS is unable to carry any traffic.

The License Key File (LKF) is corrupt.The LKF is for the wrong node.The LKF has been deleted.The LKF does not exist for other reasons.

The alarm is issued when there is a configuration mismatch between two nodes that are connected to the Inverse Multiplexing ATM (IMA) group, that is the two nodes have conflicting configuration data. The corresponding IMA group at the remote (far-end) node rejects the configuration data received from the IMA group in this node.

This alarm is issued when the Random Access Receiver (RAX) in a CBU-based or GPB-based RBS or the Digital Unit WCDMA (DUW) in a DU-based RBS is faulty. If there is more than one faulty RAX board , each board issues a separate alarm.

This alarm is issued when one or more of the units connected through the radio interface link reports a fault.The alarm is issued when the Remote Defect Indication (RDI) information is received in the Plesiochronous Digital Hierarchy (PDH) frame.This alarm is issued by the Bfu Managed Object (MO) and the BfDevice MO when the RBS is running on batteries only and the battery voltage is below a certain operator-defined or hardware default level. To protect the batteries from damage, the RBS is disconnected except for equipment connected to prioritized outputs.

The alarm indicates failure in one or more of the units in the gamma uplink path.

RfCable, for cables between the RUs

The alarm indicates that a component is faulty and must be replaced.

Cable between linked boards is missing, faulty or not properly connected.The alarm is issued when no system clock is available in the node.

The alarm is issued when the Inverse Multiplexing ATM (IMA) link at the far end has become unusable. It is likely that a corresponding alarm has been issued at the local node for the faulty IMA link.As a consequence of the fault, the IMA group does not function. However, the IMA group to which the link belongs can continue to function, provided that there are still enough working links available in the IMA group.The likely cause is a faulty IMA link at the far end.

The likely causes of this alarm are: AC supply failure A faulty Power Supply Unit (PSU) Too few installed PSUs

The main load is disconnected due to a low battery voltage. The disconnected level is defined by the mainLoadUnderVoltageDisconnect attribute.

Causes: A software faultAn incorrect version of the softwareA faulty configuration, depending on a software error (only when RruDeviceGroup issues the alarm)

This alarm is issued by the RaxDeviceGroup Managed Object (MO) or the TxDeviceGroup MO when there is a communication error between the Transmit (TX) board and the Random Access and Receiver (RAX) board. The connection is made through the backplane.The likely cause of this alarm is a software fault. Each TX board can handle several RAX boards. Depending on the configuration, the consequence of the fault is that the RBS capacity is reduced or that the RBS is unable to carry any traffic.

The alarm is issued when the delay times through the network differ by more than 25 milliseconds between the Inverse Multiplexing ATM (IMA) links. The IMA links take different paths, or routes, through the network. If there is a difference in the delay of more than 25 milliseconds between the IMA links within an IMA group, synchronization is lost.As a consequence of the fault, the IMA group does not function. However, the IMA group to which the link belongs can continue to function, provided that there are still enough working links available in the IMA group.

Fault in the cable connecting the boardsFault in the Timing Unit hardware

A software faultAn incorrect version of the softwareA faulty configuration, depending on a software error (only when RruDeviceGroup issues the alarm)

The alarm is issued for information to indicate that the Inverse Multiplexing ATM (IMA) group in the remote node is starting up.As a consequence of the fault, the IMA group does not function.The likely cause is that the IMA group is starting up. In these circumstances, the alarm disappears spontaneously within a short period.





The cause of the problem is usually not the unit issuing the alarm, but climate or environmental reasons, particularly if several boards from different subracks have issued the alarm. RBS Temperature Out Of Range offers a systematic procedure for determining the correct cause. If the alarm is issued together with a fan alarm, then the most likely cause of the alarm is a faulty fan unit If the alarm is issued on only one board, then it is probable that the board has developed a fault, in which case, it is likely that an equipment alarm has also been issued for the board

Cables carry the gamma link between the following: the Baseband Interface (BBIF) and Radio Frequency Interface (RFIF) boards; the Optical Baseband Interface (OBIF) board and the RRU; the Radio Unit Interface (RUIF) and the Radio Unit (RU). Between all other boards, the physical connections are made through the backplane of the boards.Depending on the configuration, the RBS can either work with reduced capacity as the RX diversity is lost or lose all traffic. In the RBS EM it is possible to identify the affected (disabled) cells.

This alarm is issued by the Bfu Managed Object (MO) or the BfDevice MO when the RBS is running on batteries only and the battery voltage is below a certain operator-defined or hardware default level. To protect the batteries from damage, the RBS is disconnected. Normally this alarm never reaches the operator, because the RBS is disabled when the alarm is issued. The alarm BatteryVoltageSupervisionTooLowMainLoadDisconnected is sent in advance.

The likely causes of this alarm are:A TPA algorithm error in the software An internal TPA hardware fault

The alarm indicates a problem with the Baseband (BB) clock or the Node B Frame Number (BFN) clock. The BB clock is generated by the Timing Unit Board (TUB) or the Control Base Unit (CBU) or the Digital Unit WCDMA (DUW) and distributed to the RBS by one of the following boards: RFIF, RUIF or REIF, OBIF, or sTRX. The BB clock is the RBS system clock. The consequence of the fault is that the board or unit issuing the alarm is unable to carry traffic. If the alarm is issued by a non-redundant RFIF board, RUIF or REIF board, OBIF, or sTRX, then the RBS is unable to carry traffic. The likely cause of the alarm is a faulty board or unit.

Incorrectly connected feeder or jumper cable (if the alarm is raised immediately after antenna installation)Damaged or incorrectly connected power and signal cable between Radio Unit (RU) and Filter Unit (FU)


Matching PiuType missing in configuration.Matching PiuType missing in SwAllocation RepertoireList.Auto-configuration disabled, the configuration doesn't match the inserted board.Auto-install for PiuType failed.Existing MO configuration not covered by the PiuType is blocking reconfiguration

This alarm is issued when a unit is replaced and the automatic reconfiguration fails.The causes of the alarm are the following:Incompatibility between the hardware version of the unit and the Radio Base Station (RBS) software version, if a unit is replaced with a unit of a later generation and there is no software support for the new unitAutoconfiguration is not allowedUpgrade package does not contain the required software for the newly installed hardware in the RBSLoad modules for the inserted Plug In Unit (PIU) type are included in the upgrade package, but it is not possible to install them in the RBS

The alarm is issued when a communication link is broken between the main switch module and an extension switch module. As a result of the fault, traffic is lost.

Fault in a synchronization reference cableFault in an external equipment that provides the synchronization reference signal to the TUFault in the Timing Unit HW

Fault in the system clock termination circuitFault in the main subrackFault in the extension subrackFault in the backplane

This alarm is issued when there is a communication fault in an Inter-Switch module Link (ISL) between the main switch module and an extension switch module in the node. In some cases, fault-free units may be indicated as well.

This alarm is issued when the number of processing resources is configured to a value that is higher than the value available for High-Speed Downlink Packet Access (HSDPA) and Enhanced Uplink (EUL) on the Transmitter (TX) board within a baseband (BB) pool or in the Digital Unit WCDMA (DUW).

The alarm indicates that software cannot be downloaded for the component for which the alarm is issued.

The likely cause is a faulty TUB/CBU. The RBS can still function with this fault, but traffic is disrupted in all cells. If the system is configured with two TUBs for redundancy, then it does not switch to the other TUB automatically.

This alarm is issued by the TimDevice Managed Object (MO), and indicates problems with the Timing Unit Board (TUB), the Control Base Unit (CBU) or the Digital Unit WCDMA (DUW.The likely cause of the alarm is an internal hardware fault in the TUB/CBU or DUW.The consequence of the fault is that no calls can be set up and no user data can be processed. If configured with redundancy, the RBS remains functional but without redundancy.

This alarm is issued when a Plug-In Unit is marked faulty after a hardware test of the board.



The alarm is issued when the clock frequency in the transmit direction at the remote node for the Inverse Multiplexing ATM (IMA) group is different from the clock frequency in the receive direction in this node for the IMA group. This node and the remote node are attempting to synchronize the IMA group in different, incompatible ways.As a consequence of the fault, the IMA group does not function.

The alarm is issued when the ET board cannot detect any signal at the input port.

The alarm is related to the Power Distributor (PD), which is the essential part of the Capacitor Unit (CU). The PD measures voltage and current load in the RBS.The likely causes of this alarm are: The input voltage is too low A faulty CU

This alarm is issued by the PdDevice Managed Object (MO) when the Power Distributor (PD) in the Capacitor Unit (CU) has detected that the input voltage is below the operator set or hardware default value. The PD measures voltage and current load in the RBS.The likely cause of this alarm is a fault in the external power supply system.

This alarm is issued by the BfDevice Managed Object (MO) or Bfu MO when there is a fault in the internal power supply. It is generated by the Internal Distribution Module and Battery Fuse Unit (IDM/BFU) or the BFU (or equivalent for RBSs with RBS-controlled power supply system located outside the cabinet).The cause of this alarm can be one of the following: A blown fuse or a tripped circuit breaker in the IDM/BFU or in the BFU. A circuit breaker set to OFF (all circuit breakers must be in the ON position, even if no equipment is connected)

The alarm is issued when there is a fault in the active switch plane in a switch module.As a consequence of the fault, the traffic is lost.The likely cause is that it is a consequence of the primary alarms:Switch Core Fault Switch Port Fault

The most likely cause of the alarm is a broken fan. If the cause of the problem is not the unit issuing the alarm, it could be environmental reasons. If so, RBS Temperature Out Of Range offers a systematic procedure for determining the correct cause.

This alarm is issued when a Random Access and Receiver Board (RAX board) is given a slot position that shares a backplane wire with a slot where another RAX board is already in operation.

One or more of these alarms is issued when there is a fault in the switch plane. A switch plane is distributed on all boards in a switch module. In some cases, fault-free units may be indicated as well. The alarm is also issued for a limited period of time for a Switch Core Board (SCB) or a Control Board Unit (CBU) in connection with upgrade, and node and board restart.


The alarm indicates clock failures or a broken clock path.

The alarm indicates that software cannot be downloaded for the component for which the alarm is issued. The consequences of the fault, and the subsequent corrective actions, depend on the board or unit for which the alarm is issued, and the RBS configuration.

Cables carry the gamma link between the following: the Baseband Interface (BBIF) and Radio Frequency Interface (RFIF) boards; the Optical Baseband Interface (OBIF) board and the RRU; the Radio Unit Interface (RUIF) and the Radio Unit (RU). Between all other boards, the physical connections are made through the backplane of the boards.


The likely cause is one of the following:The cause of the problem is usually not the unit issuing the alarm, but climate or environmental reasons. RBS Temperature Out Of Range offers a systematic procedure for determining the correct cause. A battery temperature sensor fault Battery failure

This alarm is issued by the Bfu Managed Object (MO) or the BfDevice MO when the RBS is running on batteries only and the battery voltage is below a certain operator-defined or hardware default level. To protect the batteries from damage, the RBS is disconnected. Normally this alarm never reaches the operator, because the RBS is disabled when the alarm is issued. The alarm BatteryVoltageSupervisionTooLowMainLoadDisconnected is sent in advance.

This alarm is issued by the Bfu Managed Object (MO) and the BfDevice MO when the RBS is running on batteries only and the battery voltage is below a certain operator-defined or hardware default level. To protect the batteries from damage, the RBS is disconnected except for equipment connected to prioritized outputs.

This alarm indicates one or more of the following faults: A faulty capacitor compressor A faulty expansion valve A faulty compressor A refrigerant leak If the cause of the problem is not the unit issuing the alarm, it could be climate or environmental reasons. If so, RBS Temperature Out Of Range offers a systematic procedure for determining the correct cause.

The board or unit issuing this alarm is unable to carry traffic. If the alarm is issued by a non-redundant board or unit, the RBS is unable to carry traffic.


The alarm is issued by the HwUnit MO (1) with hardware unit type PSU (2). The alarm is raised when the PSU operating temperature is too high and the PSU performance is reduced.

Faulty TU

DigitalCableLoPowTxCableRfCableTrxRfCable



The alarm can be issued for the following reasons:Slow rotation of the fan caused by defects in the bearings Defects in the fan motor A blown fuse If the cause of the problem is not the unit issuing the alarm, it could be environmental reasons. If so, RBS Temperature Out Of Range offers a systematic procedure for determining the correct cause.

Damaged or incorrectly connected feeder cableDamaged or incorrectly connected power and signal cable between Radio Unit (RU) and Filter Unit (FU)

A faulty TUB/CBU/DUW. If the RBS is configured with two redundant TUBs, then the alarm indicates that both TUBs are faulty. A faulty Radio Unit Interface (RUIF) board, or Radio and Enclosure Interface (REIF) board.A faulty timing cable.A faulty RFIF or BBIF board.

A faulty or incorrectly connected Radio Frequency Interface (RFIF) board to Baseband Interface (BBIF) board timing cable A faulty RFIF board A faulty or detached BBIF board

A faulty or incorrectly connected Baseband Interface (BBIF) board to Radio Frequency Interface (RFIF) board timing cable A faulty RFIF board A faulty or detached BBIF board

The causes of the alarm are (depending on the RBS type):A faulty or disconnected gamma cable or digital cableA faulty BBIF boardA faulty Digital Unit WCDMA (DUW)A faulty RFIF boardA faulty Single Transceiver Board (sTRX)A faulty OBIF boardA faulty Transmitter (TX) boardA faulty RUA faulty RUIF boardA faulty REIF boardThe various faults can be synchronization, alignment, parity, or ID.

Responsability(FIELD, REMOTE, REMOTE&FIELD)Cell down Capacity reduced Performance impactedremote maybe maybe maybe

remote and/or field maybe yes yes

remote and/or field yes yes yes


remote and/or field maybe maybe mayberemote yes yes yes

remote yes yes yes

remote maybe yes yes

remote yes yes yes


remote yes yes yes

field maybe yes yes


field maybe yes yes

remote yes yes yes

field maybe yes yes

remote maybe maybe maybe

field yes yes yes

remote and field yes yes yes



remote and field maybe yes yes


remote and field maybe no yes


remote yes yes yesfield maybe yes yes

remote yes yes yesfield maybe maybe maybe

field maybe yes yes

field maybe yes yes


field maybe maybe maybe

field yes yes yes



field maybe yes yes


field maybe yes yes

field maybe no no

remote yes yes yes


remote yes yes yes

field maybe yes yes



remote yes yes yes


field yes yes yes


field maybe yes yes



field yes yes yes



remote maybe maybe yes

remote yes yes yesfield yes yes yes

field maybe yes yesremote and/or field maybe yes yes

field yes yes yesremote yes yes yes

field maybe yes yesremote yes yes yes

field yes yes yesremote and/or field yes yes yes

remote and/or field maybe maybe maybe

field yes yes yesfield yes yes yes


field yes yes yes



field maybe yes yes




remote and field maybe maybe maybe




field maybe yes yesremote and/or field maybe yes yes


remote yes yes yes


field maybe yes yes


remote yes yes yes

field maybe yes yes

field maybe yes yesfield maybe maybe yes

field maybe maybe yes




field maybe yes yes

field yes yes yes


field yes yes yesremote and/or field yes yes yes

remote and/or field yes yes yesremote and/or field yes yes yes

remote maybe maybe maybe

remote yes yes yes

field maybe maybe yes





field yes yes yes


field yes yes yes


field maybe yes yes

field yes yes yes

field yes yes yesfield yes yes yes

field yes yes yes


SAFmaybe

yes

yes

yes

maybe Check if the cells are still up in RNC.yes

yes

yes

yes

yes

yes

No impact on traffic, if there is a working standby synchronization reference. Check if the node is synchronized.

yes

yes

yes

yes

yes

maybe

yes

yes

The clock quality is not affected when a stand-by reference is available, that is, the clock maintains locked mode by selecting a stand-by reference. However, the alarm stays active as long as any synchronization reference marked LOSS_OF_TRACKING remains. Check if there are any stand-by reference that was not affected by the alarm.

yes

yes

yes

yes

yes

yes

yesyes

yesmaybe

yes

SAF if the affected unit is any of: RRU, RU, RUW, TX, TRX, FU, RUIF, CBU, GPB, TUB, ASC, TMA, RAX, DUW, AIU, MCPA, OBIF.

yes

yes

maybe SAF if the affected unit is any of: ASC, TMA, FU, RU, MCPA, RRU, AIU.

yes

yes

yes

yes

maybe

yes

no

yes

SAF if the affected unit is any of: RAX, TX, RUIF, REIF, OBIF, TRX, AIU, DUW, RUW.

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

maybe If the system voltage drops further, the RBS is disconnected.

yes

yes

yes

yes

yesyes

yesyes

yesyes

yesyes

yesyes

maybe

yesyes

yes

yes

yes

yes

yes

SAF if the affected unit is any of: RAX, TX, RUIF, REIF, OBIF, TRX, AIU, DUW, RUW.

yes

yes

yes

maybe

yes

yes

yes

yesyes

maybe SAF if the affected unit is any of: ASC, TMA, FU, RU, MCPA, RRU, AIU.

yes

maybe

If no stand-by synchronization reference is available, the fault can stop or disturb the traffic or the network synchronization. Check if the node is still synchronized.

SAF if the RBS is not configured with sync redundancy. Check if the node is still synchronized.

yes

yes

yes

yes

yesyes

yes

maybe SAF only when issued together with Disconnected Alarm.

yes

no SAF only when issued together with Temperature Out of Range alarm.

yes

yes

maybe

yesyes

yesyes

maybe SAF only when issued together with RBS Temperature Out of Range alarm.

yes

yes


yes

yes


SAF if the affected unit is any of: RRU, RU, RUW, TX, TRX, FU, RUIF, CBU, GPB, TUB, ASC, TMA, RAX, DUW, AIU, MCPA, OBIF.

yes

yes

yes


yes

yes

yesyes

yes

yes

Alarms Analysis

Documents