Severity Slogan Counts

Major UtranCell_ServiceUnavailable 50162

Major Rach_InternalResourceUnavailable 16279

Major Fach_InternalResourceUnavailable 16058

Major Pch_InternalResourceUnavailable 15199

Major UtranCell_NbapMessageFailure 13424

Major UtranCell_ExternalResourceUnavaila 5981

ble
Major NbapDedicated_RncRbsControlLinkD 5466
own

Major NodeSynch_Phase_Difference_Meas 5371

urement_Failed

Indeterminate Default router switch 4106

Major Contact to Default Router 1 Lost 3041

Major Contact to Default Router 0 Lost 3039

Major NodeSynch_Phasedrift_Threshold_E 1486

xceeded
Indeterminate A Non-Local MAU Has Been Chosen 1228
as the Active Client
 Major UtranCell_MaxNumberOfSystemInfor 830
mationUpdateReattemptsIsReached

Major Eul_NbapMessageFailure 552

Major Rach_NbapMessageFailure 471

Major Hsdsch_NbapMessageFailure 327

Warning VP ete Remote Defect Indication 306

Major Fach_NbapMessageFailure 190

 Major Pch_NbapMessageFailure 142

Major UtranCell_RBSLocalCellNotAdded 129

Unknown Synchronization Start 104

Indeterminate Synchronization End 104
Major UtranCell_ComMeasFailAdmCon 103

Indeterminate IpEthPacketDataRouter_CnNotRespo 84
ndingToGTPEcho
Warning UtranCell_NbapReconfigurationFailur 72
e
Major VC ete Loss of Connectivity 57

Warning MTP3b Link Out of Service 55

Indeterminate PIU restarted 54

Minor Ethernet Switch Port Congestion 48

Major UtranCell_ComMeasFailCongCon 43

Warning SCCP Remote Subsystem 31

Unavailable
Major DcDevice_DeviceDisabled 30
 Major MTP3b Route Set Unavailable 29

Warning Gigabit Ethernet Link Redundancy 26

Fault
Major Ethernet Switch Port Fault 25

Critical Alarm Rate Threshold Crossed 25

Indeterminate SlotNew PIU detected 15
Warning VC ete Alarm Indication Signal 12

Major Ethernet Switch Port Overload 12

Critical Heartbeat Failure 10

Minor Remote IP Address Unreachable 10

Major M3UA Association Down 9

Major Loss of Signal 7

Minor VC4 Degraded Signal 6

Major Hsdsch_CodeAllocationFailure 5
Major VC4 Unequipped Defect 4
 Major CcDevice_DeviceDisabled 4
Indeterminate Link switched 4

Major Gigabit Ethernet Link Fault 4

Indeterminate Licensing_FeatureChange 2
Indeterminate RncFunction_NodeRestartCompleted 2

Indeterminate PHY_Os155Spi_MI_AUTOLOCK_IN 2
D
Warning MS Alarm Indication Signal 2

Critical Rnsap_RemoteFailure 2

Warning VC ete Remote Defect Indication 2

Major Denib Device Configuration Fault 1

Causes Responsibility
1.Node B Application Part (NBAP) common signaling errors. remote
2.No space for the IubLink in any module.
1.ATM resources remote
2. SP resources
3. IP resources
1. Faults in the ATM (Asynchronous Transfer Mode) Adaptation Layer type 2 remote
(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 remote
(AAL2)
2.Faults on the Special Purpose Processor Board (SPB)
3. Faults in the Fach IP resources.
 1. Cell not available remote and/or field
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

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

1.Temporary disturbances or interruptions in the Iub link remote and/or field

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. remote and/or field

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.
event, not a fault none
1. IP network problem. remote
2. The router is not answering.
3. Wrong IP address configured for the router.
1. IP network problem. remote
2. The router is not answering.
3. Wrong IP address configured for the router.
Node synchronization failure. remote

event, not a fault none

1. The RBS sends a System Information Update Failure message because remote
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 remote
2. Unknown C-ID
3. HW failure
4. Requested configuration not supported
5. Semantic error
6. Cell not available
 1. Rach_NbapMessageFailure remote
2. 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 remote

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 remote

a fault in the SDH transport network
a fault in the ATM transport network
Unknown C-ID remote
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

Unknown C-ID remote

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 remote
activate is probably not configured.
event, not a fault none
 event, not a fault none
RBS resources are unavailable because the maximum number of users remote and/or field
has been reached.
event, not a fault none

DlPowerDegradation remote and/or field

The alarm is issued when no ATM cells are received in the ete ATM remote
(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) remote and/or field
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
event, not a fault none
The alarm is issued if the Ethernet switch port is becoming remote
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 remote
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

n the remote node is not accessible from this node. The fault can be remote
perm
Device Disabled remote and/or field

An alarm is issued when a user of the Message Transfer Part level 3 remote
(MTP3) in the remote node is not accessible from this node. The fault
can be permanent or temporary.
One of two redundant links is in the operational state DISABLED. remote and/or field

The alarm is issued if the Ethernet Switch detects a "port fault" remote and/or field
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
 EWS none
event, not a fault none
The alarm is issued when an ete Alarm Indication Signal (end-to-end remote
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 remote and/or field
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.

Link Failure remote and/or field

Remote IP address unreachable. remote and/or field

An alarm is issued when the Message Transfer Part level 3 (MTP3) detects remote
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 remote and field

The alarm is issued when a specified number of the consecutive bad remote
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.
Invalid downlink code configuration remote
The alarm is generated when the C2 byte received in Virtual Container remote
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.
Device Disabled remote and/or field
event, not a fault none

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

event, not a fault none

The alarm is generated when an Multiplexer Section Alarm Indication Signal (MS remote and/or field
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 RNC remote
A 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 remote
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 remote
protocol. Denib is an Ericsson proprietary protocol used when communicating
with certain hardware devices through a serial connection.

Cell down Capacity reduced Performance impacted SAF

yes yes yes
yes
yes yes yes

yes
yes yes yes

yes
yes yes yes

yes
yes yes yes

yes
yes yes yes
yes
 yes yes yes

yes
yes yes yes

yes
no no no no
maybe yes maybe

yes
maybe yes maybe

yes
no no no
no
no no no
no

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 yes
yes
no no no no
no no no no
yes yes yes
yes
no no no
no
no yes yes
yes
maybe yes yes

yes
 no maybe maybe yes

no no no no
no no no

no
no yes yes

yes
no yes yes
yes
no yes yes yes

no yes yes

yes
no no no
no
maybe yes yes

yes
no no no no
no no no no
maybe yes maybe yes
maybe yes yes

yes
maybe maybe maybe yes
no 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 no
no
no no no
no
maybe yes yes

yes
 no yes yes

yes
maybe yes yes

yes
no no no

no

Severity Specific problem Counts

Indeterminat Ip over ATM Link Supervision Recovered 140633
e
Indeterminat Ip over ATM Link Supervision Failed 132560
e
Indeterminat NssSynchronization_SynchRefChanged 98702
e
Indeterminat NssSynchronization_SystemClockStatusChanged 90814
e
Indeterminat AuxPlugInUnit_SuccessfulRecoveryActionPerformedReestablishLink 59183
e
Major NTP Server Reachability Fault 45496

Indeterminat E1PhysPathTerm_NoCRC4Mfa 40204

e
Warning PDH Alarm Indication Signal 37800

Minor AlmDevice_ExternalAlarm 36907

Unknown Synchronization Start 24432
Indeterminat Synchronization End 21853
e
Major IMA Group Configuration Aborted 20092

Warning IMA Link Reception Unusable at Far End 18398

Minor Anomalia funzionale CDZ 14751

 Warning Remote Defect Indication on IMA Link 14651

Major Synch Reference Path HW Fault 14144

Major LossOfMains 14041
Critical Heartbeat Failure 12192
Indeterminat Extensive Ethernet frame flooding 10182
e
Minor Loss of Synch Reference Redundancy 9999
Critical Anomalia impianto elettrico 9908
Major System Clock in Holdover Mode 8751

Major IMA Group Insufficient Links 8138

Minor Remote IP Address Unreachable 7722

Minor PDH Degraded Signal 7294

Major FcuDeviceGroup_NumberOfHwEntitiesMismatch 6770

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

Critical Anomalia di blocco CDZ 4466

Critical Anomalia interruttore generale 4367
Critical None 4336
Major AntennaBranch_FeederCurrentTooLowInBranchA 4179

Major PDH Loss of Signal 3908

Minor DownLinkBaseBandPool_DLHWLessThanDLCapacity 3902

Major Gigabit Ethernet Link Fault 3720

Critical Mancanza rete 3597

Indeterminat RuDeviceGroup_SuccessfulRecoveryActionPerformedBoardRestart 3302
e
Major AntennaBranch_FeederCurrentTooLowInBranchB 2933

Indeterminat Synchronization Aborted 2655

e
Critical NbapCommon_Layer3SetupFailure 2589

Major AntennaBranch_AntennaProblemInBranchA 2486

Critical Allarme porta aperta 2296

Minor UpLinkBaseBandPool_ULHWLessThanULCapacity 2219

Major Loss of Tracking 2201

Major AuxPlugInUnit_CommunicationLostWithAsc 2186

Indeterminat NodeBFunction_NodeRestarted 2060

e
Indeterminat NodeBFunction_OaMApplicationRestarted 1927
e
Critical Allarme incendio 1768
Indeterminat PIU restarted 1447
e

Indeterminat RuifDeviceGroup_SuccessfulRecoveryActionPerformedReestablishLink 1408

e
Major RuDeviceGroup_TemperatureExceptionallyHigh 1353

Major RuDeviceGroup_GeneralSwError 1349

 Major Carrier_SignalNotReceivedWithinTime 1284

Major TimDevice_RadioClockIsNotStable 1059

Critical Anomalia batterie 1059

Major Ethernet Switch Port Fault 1046

Major Loss of IMA Frame 956

Warning PDH RNCI 924

Critical Anomalia SOV 905

Major DbccDevice_GammaDownlinkFailure 807

Major DigitalCable_Disconnected 733

Major CluDeviceGroup_EnclosureDoorOpen 713

Major SystemOvervoltage 711

 Critical Minimo Batterie S.E. 697
Major VC ete Loss of Connectivity 694

Critical Batterie in scarica 694

Indeterminat Licensing_FeatureChange 661
e
Major Clu_LossOfMains 600

Major RunningOnBatterySupply 580

Indeterminat DeviceGroup_SuccessfulRecoveryActionPerformedBoardRestart 538

e
Major NumberOfHwEntitiesMismatch 506
Major PowerSupplySystem_LossOfMains 504

Major AntennaBranch_AntennaSystemProblemInBranchB 497

 Minor PowerSupplySystem_RunningOnBatterySupply 488

Indeterminat RaxDeviceGroup_SuccessfulRecoveryActionPerformedBoardRestart 477

e
Indeterminat Licensing_CapacityChange 459
e
Critical Temperatura anomala 426
Major RbsLocalCell_CellReleaseFailure 409
Indeterminat AscDeviceGroup_SuccessfulRecoveryActionPerformedBoardRestart 391
e
Major EnclosureProductDataMismatch 380
Critical Impianto elettrico sezionato 377
Critical Piccolo Allarme CDZ 365
Major EnclosureDoorOpen 355
Indeterminat PHY_E1Ppt_MI_AUTOLOCK_IND 344
e
Critical Mancanza alimentazione impianti TLC 334
Critical Anomalia CDZ armadio TX 280
Major PsDevice_LossOfMains 276

Major Clu_ActiveCoolerFanFault 273

Major GeneralHwError 270

Major AntennaBranch_AntennaProblemInBranchB 264

Indeterminat AuxPlugInUnit_NewAuxiliaryUnitDetectedMatchesTheDefinedConfiguratio 261

e
Major n 252
SystemUndervoltage
 Major Power Failure Left Slot 239

Indeterminat SlotNew PIU detected, no predefined configuration exist 227

e
Major Loss of Cell Delineation on IMA Link 220

Major ExternalTma_LnaFailureBranchB 213

Major IMA Link Reception Misconnected 208

Major FcuDeviceGroup_FanFailure 205

Minor Emergency Unlock of Software Licensing 204

Major AuxPlugInUnit_PiuConnectionLost 203

Major Loss of Cell Delineation 199

Major ExternalTma_LnaFailureBranchA 187

Indeterminat UpgradePackage Warning: Unexpected condition detected 185

e
Indeterminat TxDeviceGroup_SuccessfulRecoveryActionPerformedBoardRestart 175
e

Major OperatingTemperatureTooHighBatteryDisconnected 158

Critical Anomalia impianto elettrico - Sito Hub 157

 Critical System Clock Quality Degradation 155

Major FanFailure 152

Critical Anomalia stazione energia 138
Major Disconnected 136

Major Carrier_RejectSignalFromHardware 134

Major IMA Link Transmission Misconnected 130

Indeterminat SlotNew PIU detected, matches the defined configuration 126

e
Critical Anomalia stazione d energia 123
Major AntennaBranch_AntennaSystemProblemInBranchA 120

Critical Anomalia PLC 114

Minor Anomalia stazione d'energia 112

Major Plug-In Unit General Problem 112

Minor Fase e Rete S.E. 104

 Major BfDevice_HighOperatingTemperatureSupervisionTooHighMainLoadDiscon 103
nected

Major BfDevice_BatteryChargingFailure 103

Critical Allarme Porta 101

Critical Pressurizzatore 99
Major Bfu_DcDistributionFailure 95

Indeterminate Pccpch_DownLinkChannelResourceRedundancySwitchOver 84

Critical Anomalia e Guasto S.E. 84

Critical Apertura Int. Quadro Interf. Apparati 80
Critical Apertura int. Generale 76
Major Carrier_NumberOfCarriersExceedsLicensedLimit 72

Critical Riserva 72
Major Carrier_MaxDlPowerCapabilityOutOfRange 72

Minor Carrier_PowerClassTruncated 72

Major SectorAntenna_FeederCurrentTooLow 71

Major RbsLocalCell_MaxNumHsPdschCodesExceedsLicensedLimit 70

Major RbsLocalCell_MaxNumHsdpaUsersExceedsLicensedLimit 70

Major RbsLocalCell_MaxNumEulUsersExceedsLicensedLimit 70
 Major RaxDeviceGroup_RaxTxInterfaceCommunicationError 69

Major ClDevice_LossOfMains 68

Critical Allarme porta armadio TX 66

Critical License Key File Fault 65

Major IMA Config Aborted at Far End 62

Critical Apertura int. CC/CA armadio TX 60

Critical Mancanza rete armadio TX 56
Critical Anomalia batterie armadio TX 56
Critical Allarme fumo (precablato in fabbrica) 55
Critical Anomalia Sensore di fumo (precablato in fabbrica) 54
Major UbchDeviceSet_CapacityLost 53

Critical Anomalia raddrizz. armadio TX 53

Major DigitalCable_CableFailure 52

Warning PDH Remote Defect Indication 49

Major BfDevice_BatteryVoltageSupervisionTooLowMainLoadDisconnected 49

Warning IMA Link Transmit Unusable at Far End 48

Indeterminat RfifDeviceGroup_SuccessfulRecoveryActionPerformedReestablishLink 47
e
 Major PowerSupplySystem_SystemUndervoltage 45

Major BatteryVoltageTooLowMainLoadDisconnected 44

Major TrDeviceSet_GeneralSwError 44

Critical Allarme Sov 41

Major TxDeviceGroup_RaxTxInterfaceCommunicationError 41

Critical Anomalia stazione denergia 40

Minor Temperatura anomala armadio TX 35
Major LowBatteryCapacity 34

Minor Password File Fault 31

Indeterminat McpaDeviceGroup_SuccessfulRecoveryActionPerformedBoardRestart 31
e
Major IMA Link Out of Delay Synchronization 31

Major RuDeviceGroup_GammaUplinkFailure 30
Indeterminat NodeBFunction_MpTrafficApplicationRestarted 29
e
 Major BfDevice_BatteryMissing 29

Major Slave TU Out of Synchronization 28

Major FcuDeviceGroup_EnclosureDoorOpen 28

Major BatteryMissing 28

Major RfCable_Disconnected 27
Critical Grande Allarme CDZ 27
Major RaxDeviceGroup_GeneralSWError 25

Minor TmaDevice_LnaDegraded 25

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

Major Inter-PIU Link Fault 23

Major TpaDevice_NumberOf40WPowerAmplifiersExceedsLicensedLimit 22

Indeterminat Node restarts soon. Confirm change 22

e
Major AuxPlugInUnit_CommunicationLostWithRet 21

Critical Loss of System Clock 17

Critical EnclosureSmoke 15
Major RuDeviceGroup_GeneralHwError 15
Major TrDeviceSet_GeneralSwError 15
 Major DeviceGroup_GeneralSwError 14

Major RuifDeviceGroup_GammaUplinkFailure 14
Major DeviceGroup_TemperatureExceptionallyHigh 14

Critical NodeB down 14

Critical Anomalia stazione di energia 13
Major TxDeviceGroup_GammaLinkFailure 13

Indeterminat XalmDeviceGroup_SuccessfulRecoveryActionPerformedBoardRestart 13
e
Indeterminat PsuDeviceGroup_SuccessfulRecoveryActionPerformedBoardRestart 13
e
Critical Apertura Int. Differenziale 13
Critical Apertura Int. Magnetorermico 13
Major AntennaBranch_FeederCurrentTooHighInBranchA 12

Major BfDevice_BatteryVoltageSupervisionTooLowPrioLoadDisconnected 12
 Major NodeBFunction_HsdpaFlexibleSchedulerLicenseNotValid 11

Major NodeBFunction_16QamLicenseNotValid 11

Major EnclosureSmokeDetectorFailure 11
Major TpaDevice_AmplificationError 10

Major AntennaBranch_FeederCurrentTooHighInBranchB 10

Major RuDeviceGroup_PoorClockSignal 10

Indeterminat ObifDeviceGroup_SuccessfulRecoveryActionPerformedReestablishLink 10
e
Major DeviceGroup_ExternalUnitFailure 10

Warning Auto-Configuration of Board Not Possible 10

Major NodeBFunction_HsdpaDynamicCodeAllocationLicenseNotValid 9
 Major AuxPlugInUnit_NewAuxiliaryUnitDetectedNotCorrespondingToTheDefined 9
Configuration

Critical Grande Allarme Elettrico 9

Minor Switch Internal Link Group 0 Fault 8

Major TU Synch Reference Loss of Signal 8

Indeterminat NodeBFunction_MainProcessorRestarted 8
e
Indeterminat FanDeviceGroup_SuccessfulRecoveryActionPerformedBoardRestart 8
e
Major Plug-In Unit Synch Hardware Fault 8

Critical Mancanza alimentazione impianti TLC - TIM 8

Minor Switch Internal Link Port 0 Fault 7

Major TmaDevice_LnaFailure 7

Major PsuDeviceGroup_GeneralHwError 7
Critical Anomalia stazione dýenergia 6
Indeterminat UpgradePackage Warning: Handling of the final Configuration Version 6
e failed
Indeterminat RruDeviceGroup_SuccessfulRecoveryActionPerformedBoardRestart 6
e
Minor TxDeviceGroup_NumberOfProcessingResourcesNotSupported 5

Major TxDevicegroup_GeneralHWError 5
Critical Batterie in scarica armadio P.R. 5
Critical Mancanza alimentazione impianti TLC TIM 5
Indeterminat RuDeviceGroup_PreloadFailed 5
e
Critical Apertura Interruttore CC/C Armadio TX 5
Major ClDevice_DcInputVoltageFault 5

Major RaxDeviceGroup_SoftwareDownloadFailure 5

Major PsDeviceSet_GeneralSwError 5

Major BfDeviceSet_GeneralSwError 5

Major AcDeviceSet_GeneralSwError 5

Major ClDeviceSet_GeneralSwError 5

Major FREQUENT AuxPlugInUnit_PiuConnectionLost 5

Major TimDeviceSet_ClockFrequencyStabilityMalfunction 5

Major CircuitBreakerTripped 4

Major PdDevice_InputVoltageTooHigh 4

Major PdDevice_SystemVoltageTooHigh 4

Major TimDevice_PhaseLockFailure 4
Major EulForLargeRbsConfigLicenseNotValid 4

Major Plug-In Unit HW Failure 4

Major Security Level Fault 4

Major TxDevicegroup_GeneralSWError 4

Critical Allarme porta DVB-H 4

Major NodeBFunction_HsdpaMultiCarrierLicenseNotValid 4

Major FREQUENT NodeB disturbances 4

Minor IMA Group Timing Mismatch 3

Major TpaDevice_NumberOf60WPowerAmplifiersExceedsLicensedLimit 3

Major Loss of Signal 3

Major DeviceGroup_GeneralHwError 3
Major PcuDeviceGroup_GeneralSWError 3

Major AiDeviceSet_GeneralHwError 3
Major Loss of Frame 3

Critical Allarme incendio - TIM 3

Critical Allarme porta TIM 3
Critical Anomalia di blocco CDZ - Sito Hub 3
Critical Batterie in scarica - Sito Hub 3
 Major Accu_LossOfMains 3

Critical Alta Temperatura 3

Major AscDeviceGroup_RetPortCurrentTooHigh 3

Indeterminat CluDeviceGroup_SuccessfulRecoveryActionPerformedBoardRestart 3
e
Major PdDevice_SystemVoltageTooLow 3

Major PdDevice_InputVoltageTooLow 3

Major BfDevice_DcDistributionFailure 3
 Major Cabinet_EnclosureDoorOpen 3
Critical Anomalia Int. Generale DVB-H 3
Critical Anomalia blocco CDZ DVB-H 3
Major Switch Plane A Fault 3

Major RruDeviceGroup_FanFailure 3

Major RaxDeviceGroup_BackplaneBusCollision 3

Minor Switch Core Fault 3

Indeterminat PHY_Os155Spi_MI_AUTOLOCK_IND 2
e
Major DeviceGroup_SoftwareDownloadFailure 2

Indeterminat RuifDeviceGroup_SuccessfulRecoveryActionPerformedBoardRestart 2
e

Major TrDevice_GeneralHWError 2
Indeterminat Licensing_FaultySignature 2
e
Minor Porta aperta 2
 Major Psu_LossOfMains 2

Major RruDeviceGroup_GammaLinkFailure 2

Major RuifDeviceGroup_ClockDistributionMalfunction 2
Major FuDeviceGroup_GeneralSwError 2

Minor PowerSupplySystem_BatteryOvertemperature 2

Minor FanDeviceGroup_LeftFanSpeedTooLow 2

Indeterminat Licensing_FingerPrintMismatch 2
e
Critical Anomalia Batteria Armadio Tx 2
 Critical Anomalia SE DVB-H 2
Critical Allarme alta temperatura DVB-H 2
Critical Mancanza rete - DVB-H 2
Critical Batterie in scarica - DVB-H 2
Critical Minima tensione batterie DVB-H 2
Warning Large Number of Counters 2
Major PsuDeviceGroup_GeneralSwError 2

Indeterminat Licensing_FaultySeqNum 2
e
Indeterminat RuDeviceGroup_HardwareTestEndIndication 2
e
Major Bfu_BatteryVoltageSupervisionTooLowPrioLoadDisconnected 2

Major Bfu_BatteryVoltageSupervisionTooLowMainLoadDisconnected 2

Major Clu_ActiveCoolerFault 2

Indeterminat PcuDeviceGroup_SuccessfulRecoveryActionPerformedBoardRestart 2
e
Major RuDeviceGroup_LossOfSynch 2

Major ObifDeviceGroup_GammaLinkFailure 2

Minor OperatingTemperatureTooHighCapacityReduced 2

Minor Overspeanding net 2

Major LoPowTxCable_Disconnected 1

Critical Anomalia stazione d energia (C.O VODAFONE) 1

 Major OptoCommCable_OptoCommunicationFailure 1

Major AiDeviceSet_GeneralSwError 1

Major PsDeviceSet_NumberOfHwEntitiesMismatch 1

Critical Allarme incendio - Sito Hub 1

Critical Allarme porta aperta (vodafone) 1
Critical Anomalia batterie (vodafone) 1
Critical Anomalia impianto elettrico (vodafone) 1
Critical Anomalia interruttore generale (vodafone) 1
Critical Anomalia SOV (vodafone) 1
Critical Anomalia stazione di energia - Sito Hub 1
Critical Apertura Magnetotermico 1
Critical Batterie in scarica (vodafone) 1
Critical Batterie in scarica TIM 1
Minor Fase e Rete S.E - TIM 1
Indeterminat FcuDeviceGroup_SuccessfulRecoveryActionPerformedBoardRestart 1
e
Critical Mancanza rete - Sito Hub 1
Critical Temperatura anomala (vodafone) 1
Major TmaDevice_GeneralSWError 1

Major NodeBFunction_StandardizedTmaLicenseNotValid 1

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

e
Critical Anomalia stazione di enrgia 1
Minor ANOMALIA S.E. 1
Major TmaDeviceSet_GeneralHWError 1
Indeterminat FuDeviceGroup_HardwareTestEndIndication 1
e
Major RaxDeviceGroup_GammaLinkFailure 1
 Major Clu_ExternalFanFault 1

Major TemperatureSensorFailure 1

Major RuDeviceGroup_ExternalUnitFailure 1

Major TimDeviceSet_ClockMalfunction 1

Major TU Hardware Fault 1

Critical Hoej Rumtemperatur 1
Minor None 1
Major RfifDeviceGroup_IncorrectCableForDeliveredClock 1

Major RfifDeviceGroup_IncorrectCableForReceivedClock 1

Indeterminat RfifDeviceGroup_SuccessfulRecoveryActionPerformedBoardRestart 1
e
Major RuDeviceGroup_GammaDownlinkFailure 1

Causes
event, not alarm
event, not alarm
event, not alarm
event, not alarm
event, not alarm
IP network problems IP Communication problems toward NTP server
Wrong IP address
Wrong domain name
event, not alarm
For E1, T1, J1 and E3 signal formats, the alarm is generated when the pattern
“1111...” is detected in the signal
Unconfigured external alarm
event, not alarm
event, not alarm
The 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 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.
external alarm
The possible causes are as follows:
a loss of cell delineation a
fault in the physical layer
Fault in the synchronization reference path
Commercial Power Failure
Link failure

All but one of the defined Synchronization references are unavailable

external alarm
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.

Remote IP address unreachable.

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 most likely causes of the alarm are:
A faulty or disconnected fan unit cable
Too few fans installed
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
The possible causes are as follows: misconfigured
framing between this and the remote node
The 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 Server
IP network problems
AntennaProblemInBranchA
AntennaProblemInBranchB
AntennaSystemProblemInBranchA
AntennaSystemProblemInBranchB
Disconnected
GammaLinkFailure
GammaUplinkFailure
LnaFailure
GeneralHwError
GeneralSwError

external alarm
external alarm
Unconfigured external alarm
Incorrectly connected feeder or jumper cable (if the alarm is raised immediately after
antenna installation)
Antenna feeder short circuit
Damaged or loosely connected jumper cable
RET Interface Unit (RIU)
Remote Electrical Tilt Unit (RETU)
AISG/3GPP Remote Electrical Tilt Unit (ARETU)
External Tower Mounted Amplifier (TMA)
Antenna System Controller (ASC)
AISG/3GPP Tower Mounted Amplifier (ATMA)

The possible causes are as

follows: fault in the remote node
line interruption
ET board fault in this node
The installed LKF defines a capacity that is greater than the available capacity for DCH
given by the installed Transmitter (TX) boards or by the Digital Unit WCDMA (DUW) and
the current configuration of High-Speed Downlink Packet Access (HSDPA) and
Enhanced Uplink (EUL).
Hardware failure in the TX board or in the DUW decreases the available capacity below the
capacity defined by the License Key (LK).
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.
external alarm
event, not alarm
Incorrectly connected feeder or jumper cable (if the alarm is raised immediately after
antenna installation)
Antenna feeder short circuit
Damaged or loosely connected jumper cable
RET Interface Unit (RIU)
Remote Electrical Tilt Unit (RETU)
AISG/3GPP Remote Electrical Tilt Unit (ARETU)
External Tower Mounted Amplifier (TMA)
Antenna System Controller (ASC)
AISG/3GPP Tower Mounted Amplifier (ATMA)

event, not alarm

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:
ASC
Antenna jumper cable
Antenna
external alarm
The installed license key file defines a capacity that is greater than the available capacity
for DCH given by the installed Random Access and Receiver (RAX) boards.
A HW failure in the RAX board decreases the available capacity below the capacity defined
by the license key.

The system or radio clock cannot track any synchronization reference

The system or radio clock cannot track a synchronization reference

A communication fault between a device and an Antenna System Controller (ASC) or an

AISG/3GPP Tower Mounted Amplifier (ATMA)
A fault in an ASC or an ATMA
event, not alarm
event, not alarm
external alarm
event, not alarm

event, not alarm

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 fault
An incorrect version of the software
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.
external alarm
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 quality
Incorrectly configured links
Hardware fault
Fault in far end node
Fault 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
external alarm
The causes of the alarm are (depending on the RBS type):
A faulty or disconnected gamma cable or digital cable
A faulty BBIF board
A faulty Digital Unit WCDMA (DUW)
A faulty RFIF board
A faulty Single Transceiver Board (sTRX)
A faulty OBIF board
A faulty Transmitter (TX) board
A faulty RU
A faulty RUIF board
A faulty REIF board

This alarm is issued when an RBS internal cable has been disconnected.
This alarm is issued by the CluDeviceGroup Managed Object (MO) or by the
FcuDeviceGroup MO when an RBS door is opened.
This alarm is issued by the PowerSupplySystem Managed Object (MO) when one or more
Power Supply Units (PSU) deliver excessive voltage. The alarm is issued when an
operatordefined threshold is reached.
To prevent the RBS boards being damaged by excessive voltage, the faulty PSU is shut
down if the voltage reaches -60 V. If the failing PSU is not redundant, then the RBS runs
partly on battery.
external alarm
The possible causes are as follows: a fault in the PDH transport network a fault in the
SDH transport network a fault in the ATM transport network a mis-configuration where
continuity check is active in the local node, but not in the remote node that terminates the
VC.

external alarm
event, not alarm
A faulty Alternating Current Connection Unit (ACCU)
A fault in the Remote Radio Unit (RRU), or with the incoming power
A faulty cable between the Climate Unit (CLU) and the ACCU, or a fault in the
CLU which consequently works with reduced capacity
A fault in the incoming power supply. The severity of this alarm is related to the
capacity of the battery backup system
The RBS is running on batteries. The RBS remains functional as long as the
battery backup system has enough capacity.
The RBS is running on batteries. The RBS remains functional as long as the
battery backup system has enough capacity.
A fault with the incoming power
If the alarm is issued by one or a few PSUs in the RBS, then the probable cause
of this alarm is a faulty power cable or a fault in the Power Supply Unit (PSU).
Depending on configuration, the RBS can remain functional with one or more
faulty PSUs.
If the alarm is issued by one or a few PSUs in the RBS, then the probable
cause of this alarm is a faulty power cable or a fault in the Power Supply Unit
(PSU). Depending on configuration, the RBS can remain functional with one or
more faulty PSUs.
If the alarm is issued by all PSUs in the RBS, then the probable cause is a fault
in the incoming power supply. The severity of this alarm is related to the
capacity of the battery backup system.
The likely cause of this alarm is a fault in the external power supply system or
AC mains failure forcing the RBS to run on battery supply.
event, not alarm
mismatch between defined and installed number of units
The alarm is identified with the following specific problems in the alarm list details:
Accu_LossOfMains
AuxPlugInUnit_LossOfMains
ClDevice_LossOfMains
Clu_LossOfMains
PowerSupplySystem_LossOfMains
PsDevice_LossOfMains
PsDeviceSet_LossOfMains
Psu_LossOfMains
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 likely cause of this alarm is a fault in the external power supply system or
AC mains failure forcing the RBS to run on battery supply.
event, not alarm
event, not alarm
external alarm
Release of a cell takes more than 1 minute.
event, not alarm
Configuration or Customizing Error
external alarm
external alarm
Door open
event, not alarm
external alarm
external alarm
 A faulty Alternating Current Connection Unit (ACCU)
A fault in the Remote Radio Unit (RRU), or with the incoming power
A faulty cable between the Climate Unit (CLU) and the ACCU, or a fault in the CLU which
consequently works with reduced capacity
A fault in the incoming power supply. The severity of this alarm is related to the capacity of
the battery backup system
A fault in the incoming power supply. The severity of this alarm is related to the capacity of
the battery backup system
A faulty power cable or a fault in the Power Supply Unit (PSU). Depending on configuration,
the RBS can remain functional with one or several faulty PSUs.
The RBS is running on batteries. The RBS remains functional as long as the battery
backup system has enough capacity. A fault with the incoming power
If the alarm is issued by one or a few PSUs in the RBS, then the probable cause of this
alarm is a faulty power cable or a fault in the Power Supply Unit (PSU). Depending on
configuration, the RBS can remain functional with one or more faulty PSUs.
If the alarm is issued by all PSUs in the RBS, then the probable cause is a fault in the
incoming power supply. The severity of this alarm is related to the capacity of the battery
backup system.

This alarm is issued by the ClDevice Managed Object (MO) or the Clu MO when
there is a problem with the condenser fan, also called active cooler fan, in the

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

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.
event, not alarm
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 possible causes of the alarm are as follows:
A cable fault on the left side.
A power supply fault on the left side.
A voltage outside or close to the limit of the allowed voltage range.
A hardware fault on the board.
event, not alarm
Degradation of transmission quality
Hardware fault
Fault in remote node
Fault in interconnecting network
The cause of the alarm is:
A failure in the two transistors amplifying the RF signals in the external TMA
Incorrectly set supervision parameters
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: FcuDevice Managed Object (MO) when there is a problem with
one or more fans controlled by the Fan Control Unit
The alarm is issued when someone activates the Emergency state, using the
action, setEmergencyState. The purpose of this Emergency state is to free the
software of all license restrictions in an emergency situation, so that the
capacity of the node is maximized.
This alarm is issued by the AuxPlugInUnit Managed Object (MO) when
communication between one of the Auxiliary Units (AU) and the RBS is lost.

The alarm is issued when the ATM port has lost synchronization with the ATM
cells, and cannot extract them from the time slots from the physical layer.

The cause of the alarm is:

A failure in the two transistors amplifying the RF signals in the external TMA
Incorrectly set supervision parameters
event, not alarm
event, not alarm

This alarm is raised when the battery is disconnected because of high battery temperature
according to the attribute batteryDisconnectTemp. The battery is reconnected when the
battery temperature decrease. The likely cause is one of the following:
Disconnected battery temperature sensor
A configuration fault
High environmental temperature or a fault in the climate system
Frequent battery discharge and charge, possibly in combination with high environmental
temperature
A battery temperature sensor fault
Battery failure

external alarm
The alarm is issued if the system or radio clock enters the free-running mode in a Timing
Unit (TU). It gives information about the fault indicated in the corresponding primary alarm,
which can be:
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

There is a failure on a fan group.

external alarm
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.

event, not alarm

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

external alarm
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.
external alarm
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 likely causes of the alarm are:

A disconnected cable
A faulty battery temperature sensor or faulty sensor cable
A faulty Battery Fuse Unit (BFU)
external alarm
external alarm
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)
Event, not alarm. New hardware has been allocated. The channels BCH and PCCPCH
have been set up on the new hardware, and have started sending system information.
An FM event is sent to indicate a successful switch over to the other TXB.
external alarm
external alarm
external alarm
Valid license key exceeded
Valid license key missing
external alarm
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 cable
Damaged or loosely connected jumper cable
Number of HS-PDSCH Codes exceeds value of licensed limit
License has expired or has been removed
Number of HSDPA users exceeds value of licensed limit
License has expired or has been removed

Number of EUL users exceeds value of licensed limit

License has expired or has been removed
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.
A faulty cable between the Climate Unit (CLU) and the ACCU, or a fault in the CLU which
consequently works with reduced capacity

external alarm
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.
external alarm
external alarm
external alarm
external alarm
external alarm
This alarm is issued when the Random Access Receiver (RAX) in a CBU-based or
GPBbased 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.
external 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 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.
event, not alarm

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 fault

An incorrect version of the software
A faulty configuration, depending on a software error (only when RruDeviceGroup issues
the alarm)
external 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.
external alarm
external alarm
This alarm can be raised in two different situations. This is indicated by the alarms
additional text:
Low voltage at intermittent charge
The battery voltage reached the configured limit intermittentChargeConnectVoltage while
the battery was disconnected during intermittent charging.
Insufficient recharged capacity
The alarm is raised if the batteries are not sufficiently recharged after a discharge. This
indicates poor battery performance.
The alarm indicates that the password required at Security Level 1 and 2, for user access
via Telnet, SSH, FTP, SFTP or a serial port, was never set or that the locally stored passwd
file has been found to be corrupt. A missing or corrupt passwd file disables authentication
at the access points mentioned above. As a result of the fault, the node has reduced
protection against unauthorized access. A corrupt passwd file is automatically removed
from the file system.
event, not alarm
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.

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

The likely causes of the alarm are:

A disconnected or faulty cable between the battery and the Battery Fuse Unit (BFU)
A faulty BFU
A faulty battery
The consequence of the fault is that the battery power backup system is disconnected and
not available in case of power failure.
Fault in the cable connecting the boards
Fault in the Timing Unit hardware
This alarm is issued by the CluDeviceGroup Managed Object (MO) or by the
FcuDeviceGroup MO when an RBS door is opened.
The likely causes of the alarm are:
A disconnected or faulty cable between the battery and the Battery Fuse Unit (BFU)
A faulty BFU
A faulty battery
The consequence of the fault is that the battery power backup system is disconnected and
not available in case of power failure.
RfCable, for cables between the RUs
external alarm
A software fault
An incorrect version of the software
A faulty configuration, depending on a software error (only when RruDeviceGroup issues
the alarm)
This alarm is issued by the TmaDevice Managed Object (MO) when one of the two
transistors amplifying the RF signals in the Antenna System Controller (ASC) or the
AISG/3GPP Tower Mounted Amplifier (ATMA) fails.
The alarm indicates that a component is faulty and must be replaced.
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.
Cable between linked boards is missing, faulty or not properly connected.
The license for 40 W power amplifiers does not exist or has expired
A license exists but the number of 40 W power amplifiers is larger than permitted by the
new license
event, not alarm
The causes of the alarm are the following:
Communication fault between the RBS and the RETU or ARETU
Fault in the RETU or ARETU
Faulty ARETU or the removal of an ARETU in a cascaded chain
If one ARETU in a cascaded chain is faulty or has been removed, all the ARETUs after the
lost one in the cascaded chain may issue the CommunicationLostWithRet alarm.

The alarm is issued when no system clock is available in the node.

There is smoke in the cabinet.
The alarm indicates that a component is faulty and must be replaced.
A software fault
An incorrect version of the software
A faulty configuration, depending on a software error (only when RruDeviceGroup issues
the alarm)

A software fault
An incorrect version of the software
A faulty configuration, depending on a software error (only when RruDeviceGroup issues
the alarm)
The alarm indicates that a component is faulty and must be replaced.
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

external alarm
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.

event, not alarm

event, not alarm
external alarm
external alarm
Incorrectly connected feeder or jumper cable (if the alarm is raised immediately after
antenna installation)
Antenna feeder short circuit
Damaged or loosely connected jumper cable
RET Interface Unit (RIU)
Remote Electrical Tilt Unit (RETU)
AISG/3GPP Remote Electrical Tilt Unit (ARETU)
External Tower Mounted Amplifier (TMA) (if TMA type is set to ATMA_AND_TMA, the
possible impact is on co-sited RBSs)
Antenna System Controller (ASC)
AISG/3GPP Tower Mounted Amplifier (ATMA)

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.

HSDPA Flexible Scheduler license expired

HSDPA Flexible Scheduler license removed
Node identity is in an undefined state

16 QAM modulation license expired

16 QAM modulation license removed
Node identity is in an undefined state
This alarm is raised when the smoke detector hardware is faulty.
The likely causes of this alarm are:
A TPA algorithm error in the software
An internal TPA hardware fault
Incorrectly connected feeder or jumper cable (if the alarm is raised immediately after
antenna installation)
Antenna feeder short circuit
Damaged or loosely connected jumper cable
RET Interface Unit (RIU)
Remote Electrical Tilt Unit (RETU)
AISG/3GPP Remote Electrical Tilt Unit (ARETU)
External Tower Mounted Amplifier (TMA) (if TMA type is set to ATMA_AND_TMA, the
possible impact is on co-sited RBSs)
Antenna System Controller (ASC)
AISG/3GPP Tower Mounted Amplifier (ATMA)

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.
event, not alarm

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
HSDPA Dynamic Code Allocation license expired.
HSDPA Dynamic Code Allocation license removed.
Node identity is in an undefined state
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 unit Autoconfiguration is not allowed
Upgrade package does not contain the required software for the newly installed hardware in
the RBS
Load 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

external alarm

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 cable
Fault in an external equipment that provides the synchronization reference
signal to the TU
Fault in the Timing Unit HW
event, not alarm
event, not alarm
Fault in the system clock termination circuit
Fault in the main subrack
Fault in the extension subrack
Fault in the backplane
external alarm
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.

The fault is located in the Low Noise Amplifier (LNA), which amplifies the RF
signals in the receiver (RX) chain. When the transistors in one branch have
failed, the cell is able to carry traffic as long as the other branch works, but the
RX chain performance is degraded.
The alarm indicates that a component is faulty and must be replaced.
external alarm
event, not alarm

event, not alarm

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 a component is faulty and must be replaced.

external alarm
external alarm
event, not alarm
external alarm
This alarm is issued by the Clu Managed Object (MO) or ClDevice MO when there is a
problem with the Climate Unit (CLU), or the DC power connection to CLU.
The CLU is supplied with DC power from the Internal Power Distribution Battery Fuse Unit
(IDM/BFU) or the DC Connection Unit (DCCU) depending on RBS type.
The alarm indicates that software cannot be downloaded for the component for
which the alarm is issued.
A software fault
An incorrect version of the software
A faulty configuration, depending on a software error (only when RruDeviceGroup issues
the alarm)
A software fault
An incorrect version of the software
A faulty configuration, depending on a software error (only when RruDeviceGroup issues
the alarm)

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

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.
The alarm is raised by the HwUnit Managed Object (MO) with hwUnitType Battery Fuse
Unit (BFU), when the battery has been disconnected due to a tripped circuit breaker either
by user intervention or as an automatic BFU safe guard.
The battery backup is not available. The RBS will not be able to provide any service in case
of main power failure.
This alarm is issued when the Power Distributor (PD) in the Capacitor Unit (CU)
has detected that the input voltage is above the operator set or hardware
default value. The PD measures voltage and current load in the RBS.

This alarm is issued by the PdDevice Managed Object (MO) when the power distribution
system voltage is above an operator set or hardware default value. The alarm is related to
the Power Distributor (PD). The PD is the essential part of the Capacitor Unit (CU). The PD
measures voltage and current load in the RBS.
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.
License expired
License expired, removed or not installed.
The alarm can also occur if there is an attempt to activate the feature but the license is not
installed.
Node identity is in an undefined state
This alarm is issued when a Plug-In Unit is marked faulty after a hardware test of the
board.
The alarm indicates that the operational (actual) security level of the node is
lower than the requested security level. As a result of the fault, the node has
reduced protection against unauthorized access.
A software fault
An incorrect version of the software
A faulty configuration, depending on a software error (only when RruDeviceGroup issues
the alarm)
external alarm

License expired
License expired, removed or not installed.
The alarm can also occur if there is an attempt to activate the feature but the license is not
installed.
Node identity is in an undefined state
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 license for 60 W power amplifiers does not exist or has expired
A license exists but the number of 60 W power amplifiers is larger than permitted by the
new license
The alarm is issued when the ET board cannot detect any signal at the input
port.
The alarm indicates that a component is faulty and must be replaced.
A software fault
An incorrect version of the software
A faulty configuration, depending on a software error
The alarm indicates that a component is faulty and must be replaced.
The alarm is issued when the frame alignment for the Synchronous Digital Hierarchy (SDH)
or Synchronous Optical Network (SONET) frame is lost. Frame alignment is contained in
the A1 and A2 bytes of the SDH or SONET frame.
As a consequence of the fault, the traffic on the affected transmission link is lost.
external alarm
s
external alarm
external alarm
A faulty Alternating Current Connection Unit (ACCU)
A fault in the Remote Radio Unit (RRU), or with the incoming power
A faulty cable between the Climate Unit (CLU) and the ACCU, or a fault in the
CLU which consequently works with reduced capacity
A fault in the incoming power supply. The severity of this alarm is related to the
capacity of the battery backup system
The RBS is running on batteries. The RBS remains functional as long as the
battery backup system has enough capacity.
The RBS is running on batteries. The RBS remains functional as long as the
battery backup system has enough capacity.
A fault with the incoming power
If the alarm is issued by one or a few PSUs in the RBS, then the probable cause
of this alarm is a faulty power cable or a fault in the Power Supply Unit (PSU).
Depending on configuration, the RBS can remain functional with one or more
faulty PSUs.
If the alarm is issued by one or a few PSUs in the RBS, then the probable
cause of this alarm is a faulty power cable or a fault in the Power Supply Unit
(PSU). Depending on configuration, the RBS can remain functional with one or
more faulty PSUs.
If the alarm is issued by all PSUs in the RBS, then the probable cause is a fault
in the incoming power supply. The severity of this alarm is related to the
capacity of the battery backup system.

external alarm
Damaged Remote Electrical Tilt Unit (RETU) cable or short circuit in RETU cable
Too high current to the RETU or AISG/3GPP Remote Electrical Tilt Unit (ARETU)
RETU
ARETU
Antenna System Controller (ASC)
Remote Radio Unit (RRU)
event, not alarm
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)
Door open
external alarm
external alarm
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.
event, not alarm
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.
event, not alarm
The alarm indicates that a component is faulty and must be replaced.
event, not alarm
external alarm
A faulty Alternating Current Connection Unit (ACCU)
A fault in the Remote Radio Unit (RRU), or with the incoming power
A faulty cable between the Climate Unit (CLU) and the ACCU, or a fault in the
CLU which consequently works with reduced capacity
A fault in the incoming power supply. The severity of this alarm is related to the
capacity of the battery backup system
The RBS is running on batteries. The RBS remains functional as long as the
battery backup system has enough capacity.
The RBS is running on batteries. The RBS remains functional as long as the
battery backup system has enough capacity.
A fault with the incoming power
If the alarm is issued by one or a few PSUs in the RBS, then the probable cause
of this alarm is a faulty power cable or a fault in the Power Supply Unit (PSU).
Depending on configuration, the RBS can remain functional with one or more
faulty PSUs.
If the alarm is issued by one or a few PSUs in the RBS, then the probable
cause of this alarm is a faulty power cable or a fault in the Power Supply Unit
(PSU). Depending on configuration, the RBS can remain functional with one or
more faulty PSUs.
If the alarm is issued by all PSUs in the RBS, then the probable cause is a fault
in the incoming power supply. The severity of this alarm is related to the
capacity of the battery backup system.
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 alarm indicates clock failures or a broken clock path.
A software fault
An incorrect version of the software
A faulty configuration, depending on a software error (only when RruDeviceGroup issues
the alarm)
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

The LeftFanSpeedTooLow alarm indicates that there are faults in one or more of following
units:
BaseBand (BB) Subrack Fan Unit
Radio Frequency (RF) Subrack Fan Unit
Multi-Carrier Power Assembly (MCPA) Subrack Fan Unit
Power Subrack (PS) Fan Unit
If the fan units need to be replaced, then do it at the next planned service of the RBS.
The consequence of this alarm is that different RBS components can be overheated.
event, not alarm
external alarm

external alarm
external alarm
external alarm
external alarm
external alarm
Too many counters.
A software fault
An incorrect version of the software
A faulty configuration, depending on a software error (only when RruDeviceGroup issues
the alarm)
event, not alarm
event, not alarm
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.
event, not alarm
The board or unit issuing this alarm is unable to carry traffic. If the alarm is issued by a
nonredundant board or unit, the RBS is unable to carry traffic.
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 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.
external alarm
DigitalCable
LoPowTxCable
RfCable
TrxRfCable
external alarm
The alarm is issued by the OptoCommCable Managed Object (MO) when the
communication between the different units in the RBS power supply system has failed.
When this alarm is issued, the power system control function (POSS) cannot communicate
with the Main Processor (MP). No other alarm can be sent from the POSS units.

A software fault
An incorrect version of the software
A faulty configuration, depending on a software error (only when RruDeviceGroup issues
the alarm)
The most likely causes of this alarm are:
The number of configured PSUs is less than the actual number of PSU units
The number of configured PSUs is more than the actual number of PSU units
external alarm
external alarm
external alarm
external alarm
external alarm
external alarm
external alarm
external alarm
external alarm
external alarm
external alarm
event, not alarm
external alarm
external alarm
A software fault
An incorrect version of the software
A faulty configuration, depending on a software error (only when RruDeviceGroup issues
the alarm)
This alarm is issued by the NodeBFunction Managed Object (MO) when the AISG/3GPP
Tower Mounted Amplifier (ATMA) is configured without a valid license.
event, not alarm
external alarm
external alarm
The alarm indicates that a component is faulty and must be replaced.
event, not alarm
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 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.
 This alarm is raised when the battery temperature sensor is detected to be
faulty.

Damaged or incorrectly connected feeder cable

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

Faulty TU
external alarm
Unconfigured external alarm
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
event, not alarm
The causes of the alarm are (depending on the RBS type):
A faulty or disconnected gamma cable or digital cable
A faulty BBIF board
A faulty Digital Unit WCDMA (DUW)
A faulty RFIF board
A faulty Single Transceiver Board (sTRX)
A faulty OBIF board
A faulty Transmitter (TX) board
A faulty RU
A faulty RUIF board
A faulty REIF board
The various faults can be synchronization, alignment, parity, or ID.

sponsability(FIELD, REMOTE, Cell down Capacity reduced Performance impacted

REMOTE&FIE
none no no no
none no no no
none no no no
none no no no
none no no no
remote maybe maybe maybe

none no no no
remote and/or field maybe yes yes
 remote no no no
none no no no
none no no no
remote and/or field yes yes yes

remote and/or field no yes yes

field no no no
remote and/or field maybe yes yes

remote and/or field yes, if no nno no

redu
field no no no
remote and/or field maybe maybe maybe
remote no yes yes
remote and/or field no no no
no no no
remote yes yes yes

remote yes yes yes

remote yes (if no no no

redundancy)

remote maybe yes yes

remote no no no
 remote yes yes yes

remote maybe yes yes

remote yes yes yes

field maybe yes yes

no no no
no no no
no no no
field no yes yes

remote and/or field maybe yes yes

none, if no other alarm that indicate a TX fault no, if no no, if no other alarm no, if no other alarm that
is present other alarm that indicate a TX indicate a TX fault is
that indicate fault is present present
a TX fault is
present

field maybe yes yes

no no no
 no no no
field no yes yes

no no no
remote yes yes yes

field maybe yes yes

no no no
none, if no other alarm that indicate a RAX no, if no no, if no other alarm no, if no other alarm that
fault is present other alarm that indicate a RAX indicate a RAX fault is
that indicate fault is present present
a RAX fault
is present
remote maybe maybe maybe

remote no yes yes

no no no
no no no
no no no
no no no

no no no
 field yes yes yes

remote and field yes yes yes

remote and/or field yes yes yes

remote and/or field yes yes yes

no no no
remote and field maybe yes yes

remote maybe yes yes

remote and field maybe no yes

no no no
remote and/or field yes yes yes

remote yes yes yes

field no no no

field no no no

no no no
remote no yes yes

no no no
no no no
 field no no no

field no no no

no no no
remote and/or field no no no
field no no no

field maybe yes yes

field no no no

no no no
no no no
no no no
remote yes yes yes
no no no
remote no no no
no no no
no no no
 field no no no
no no no
no no no
no no no
field no no no

field no no no

field maybe maybe maybe

field maybe yes yes

no no no
field maybe yes yes

field no no no

no no no
remote no yes yes

field no yes yes

remote maybe yes yes

field no no no

remote no no no

field maybe maybe maybe

remote no maybe maybe

field no yes yes

no no no
no no no

field no no no

no no no

no no no
 no no no
no no no
field yes yes yes

remote and/or field yes yes yes

remote maybe yes yes

no no no
no no no
field maybe yes yes

no no no

no no no
field maybe maybe maybe

no no no
field maybe yes yes

field no no no

no no no
no no no
field maybe no no
 none

no no no
no no no
no no no
no no no
remote yes yes yes

no no no
remote and/or field yes yes yes

remote yes yes yes

field maybe yes yes

remote no yes yes

remote no yes yes

remote no yes yes

remote and/or field maybe yes yes

field no no no

no no no
remote maybe yes yes
 remote yes yes yes

no no no
no no no
no no no
no no no
no no no
remote and/or field maybe yes yes

no no no
field yes yes yes

remote maybe yes yes

field maybe yes yes

remote maybe yes yes

no no no

field maybe maybe maybe

field yes yes yes

remote and/or field yes yes yes

no no no
remote and/or field yes yes yes

no no no
no no no
remote and field no no no

remote no no no

no no no
remote maybe maybe yes

remote yes yes yes

no no no

field no no no

field yes yes yes

field no no no
 field no no no

field maybe yes yes

no no no
remote and/or field maybe yes yes

field no yes yes

field yes yes yes

remote yes yes yes

field maybe yes yes

remote no yes yes

no no no
remote and/or field no no no

remote yes yes yes

field no, if no other no, if no other alarms ano, if no other alarms are
pre
field yes yes yes
remote and/or field yes yes yes

remote and/or field maybe maybe maybe

field yes yes yes

 field yes yes yes

no no no
no no no
remote maybe yes yes

no no no
no no no
no no no
no no no
field no yes yes

field yes yes yes

remote no yes yes

remote no yes yes

field no no no
remote and/or field yes yes yes

field no yes yes

remote and field yes yes yes

no no no
field maybe yes yes

remote maybe yes yes

remote no yes yes

remote maybe yes yes

no no no

remote and field yes yes yes

 remote and field maybe maybe maybe

no no no
no no no
remote and field maybe yes yes

no no no
remote and field maybe yes yes

field no yes yes

field no no no
no no no

no no no
no no no
remote and/or field maybe yes yes

field maybe yes yes

no no no
no no no
no no no
no no no
field no no no

remote and/or field maybe yes yes

remote and/or field no no no

remote and/or field no no no

remote and/or field no no no

remote and/or field no no no

field maybe maybe maybe

remote yes yes yes

field no no no

remote and/or field no no no

remote and/or field no no no

remote and/or field maybe maybe maybe

remote no yes yes

field maybe yes yes

remote no no no

remote and/or field maybe yes yes

no no no
 remote no yes yes

no no no
remote yes yes yes

remote no yes yes

field maybe yes yes

field maybe yes yes

remote and/or field no no no

no no no

no no no
no no no
no no no
no no no
no no no
field no no no

no no no
field no no yes

no no no
field maybe maybe yes

field maybe maybe yes

field maybe maybe maybe

field no no no
 no no no
no no no
remote and/or field yes yes yes

field maybe maybe maybe

field maybe yes yes

field yes yes yes

no no no
remote and/or field maybe maybe maybe

no no no

field yes yes yes

no no no
no no no
 field no no no

remote and/or field yes yes yes

remote and/or field yes yes yes

remote and/or field yes yes yes

remote maybe maybe maybe

remote and/or field no no no

no no no
no no no

no no no
 no no no
no no no
no no no
no no no
remote no no no
remote and/or field no no no

no no no
no no no
remote yes yes yes

field maybe maybe yes

field maybe maybe maybe

no no no
remote and/or field yes yes yes

remote and/or field yes yes yes

field maybe maybe maybe

no no no
field yes yes yes

no no no
 field no no no

remote and/or field yes yes yes

remote no no no

no no no
no no no
no no no
no no no
no no no
no no no
no no no
no no no
no no no
no no no
no no no
no no no
no no no
no no no
remote and/or field no yes yes

remote no yes yes

no no no
no no no
no no no
field no yes yes
no no no
field yes yes yes
 field maybe maybe maybe

field no no no

field maybe yes yes

field yes yes yes

field yes yes yes

no no no
no no no
field yes yes yes

field yes yes yes

no no no
remote and/or field yes yes yes

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

no
yes

no
no
no
yes

yes

no
yes

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

yes

no
yes

no

yes

yes

yes

yes

no
no
no
yes

yes
no Check for TX board alarms

yes

no
no
yes

no
yes

yes

no
no Check for RAX board alarms

maybe 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

no
no
no
no
no

yes

yes

yes

yes

no
yes

yes

yes

no
yes

yes
no

no

no
yes

no
no
no
maybe 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
no

no
no
yes
no

no

no
yes
yes

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

maybe Could be traffic affecting if the synchronization is lost. Check if the

synchronization is lost.

yes

no
no

no
no

no
no

no
no
yes

yes

yes

no
no
yes

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

no
yes

no

no
no
no

no

no
no
no
yes

no
yes

yes

yes
yes

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

yes
yes
yes

yes

no
yes
no

no
yes

no
yes
no
no

no
no
no
no
no
yes
no

no
yes

yes
no
yes
yes

yes

yes
no

no
no

yes

no

no

yes
no
yes

yes

yes
yes

yes
yes

no
no

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

yes
yes

no
no
yes

no
no
no
no
yes

yes

yes
yes

no
yes

yes

yes

no

yes

yes

yes

yes

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

no
no
yes

no
yes

yes

no
no
no

no
yes

yes
no
no
no
no
no

yes

no
no
no

no

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

yes

no

no

no

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

yes

yes

no

yes

no
yes

no
yes

yes

yes

yes
no

no
no

no
no
no
no
no
no
no

no
yes

yes

maybe SAF only when issued together with Disconnected Alarm.

no
no
no
yes

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

yes

yes

no
maybe 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.

no

yes
no
no
no

yes

yes
yes

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

no
no

no
no
no
no
no
no
no

no
no
yes

yes

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

no
yes
yes

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

no
yes

no

no

yes

no

no
no
no
no
no
no
no
no
no
no
no
no
no
no
yes

yes

no
no
no
yes
no
yes

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

no

yes

yes

yes
no
no
yes

yes

no
yes