Alarms Analysis

Download as xls, pdf, or txt
Download as xls, pdf, or txt
You are on page 1of 103

Severity

Major

Slogan
UtranCell_ServiceUnavailable

Counts
50162

Major

Rach_InternalResourceUnavailable

16279

Major

Fach_InternalResourceUnavailable

16058

Major

Pch_InternalResourceUnavailable

15199

Major

UtranCell_NbapMessageFailure

13424

Major

UtranCell_ExternalResourceUnavaila
ble
NbapDedicated_RncRbsControlLinkD
own

5981

Major

NodeSynch_Phase_Difference_Meas
urement_Failed

5371

Indeterminate
Major

Default router switch


Contact to Default Router 1 Lost

4106
3041

Major

Contact to Default Router 0 Lost

3039

Major

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

1486

Major

Indeterminate

5466

1228

Major

UtranCell_MaxNumberOfSystemInfor
mationUpdateReattemptsIsReached

830

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
Indeterminate
Major

Synchronization Start
Synchronization End
UtranCell_ComMeasFailAdmCon

104
104
103

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

84
72
57

Warning

MTP3b Link Out of Service

55

Indeterminate
Minor

PIU restarted
Ethernet Switch Port Congestion

54
48

Major

UtranCell_ComMeasFailCongCon

43

Warning

SCCP Remote Subsystem


Unavailable
DcDevice_DeviceDisabled

31

Major

30

Major

MTP3b Route Set Unavailable

29

Warning

26

Major

Gigabit Ethernet Link Redundancy


Fault
Ethernet Switch Port Fault

25

Critical
Indeterminate
Warning

Alarm Rate Threshold Crossed


SlotNew PIU detected
VC ete Alarm Indication Signal

25
15
12

Major

Ethernet Switch Port Overload

12

Critical
Minor

Heartbeat Failure
Remote IP Address Unreachable

10
10

Major

M3UA Association Down

Major
Minor

Loss of Signal
VC4 Degraded Signal

7
6

Major
Major

Hsdsch_CodeAllocationFailure
VC4 Unequipped Defect

5
4

Major
Indeterminate

CcDevice_DeviceDisabled
Link switched

4
4

Major
Gigabit Ethernet Link Fault
Indeterminate
Licensing_FeatureChange
Indeterminate RncFunction_NodeRestartCompleted

4
2
2

Indeterminate

Warning

PHY_Os155Spi_MI_AUTOLOCK_IN
D
MS Alarm Indication Signal

Critical

Rnsap_RemoteFailure

Warning

VC ete Remote Defect Indication

Major

Denib Device Configuration Fault

Causes
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

Responsibility
remote
remote

remote

remote

remote and/or field

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

remote

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)

remote and/or field

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.
event, not a fault
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.
Node synchronization failure.

remote and/or field

event, not a fault

none

none
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_NbapMessageFailure
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

remote

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

remote

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

remote

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.
event, not a fault
event, not a fault
RBS resources are unavailable because the maximum number of users
has been reached.
event, not a fault

remote

remote
none
none
remote and/or field
none

DlPowerDegradation

remote and/or field

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.

remote

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

remote and/or field

event, not a fault


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

none
remote

remote

remote
rt (SCCP) in the remote node is not accessible from this node. The fault can be permanent or
temporary. Normally, the ala
Device Disabled

remote and/or field

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.
One of two redundant links is in the operational state DISABLED.

remote

remote and/or field

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

remote and/or field

EWS
event, not a fault
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.

none
none
remote

remote and/or field

Link Failure
Remote IP address unreachable.

remote and/or field


remote and/or field

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:

remote

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.
Invalid downlink code configuration
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.
Device Disabled
event, not a fault

remote and field


remote

remote
remote

remote and/or field


none

There is no configured link with operational state ENABLED.


event, not a fault
event, not a fault

remote and/or field


none
none

event, not a fault

none

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 RNC
A restart in the remote RNC or intermediate system
A Radio Network Subsystem Application Part (RNSAP) failure in the RNC or the
remote RNC

remote and/or field

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.

remote

remote

remote

Cell down
yes

Capacity reduced
yes

Performance impacted
yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

SAF
yes

yes

yes

yes

yes
yes
yes

yes

yes

yes

yes

yes

no
maybe

no
yes

no
maybe

maybe

yes

maybe

no

no

no

no

no

no

yes

yes
no

yes

yes
no
no

yes

yes

yes

no

yes

yes

yes

yes

yes

no

yes

yes

maybe

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

yes

no
no
yes

no
no
yes

no
no
yes

yes
yes
no
no
yes
no

no

no

no

yes

yes

maybe

yes

yes

no

maybe

maybe

no
no

no
no

no
no

no

yes

yes

no

yes

yes

no

yes

yes

no
yes

yes
yes

no

no

yes
yes
yes

no

yes

yes

no

no

no

yes
no
maybe

yes

yes

no
no
maybe

no
no
yes

no
no
maybe

maybe

yes

yes

maybe
no

maybe
yes

maybe
yes

no

yes

yes

maybe
maybe

yes
yes

yes
yes

no
maybe

yes
yes

yes
yes

no
no

yes
no

yes
no

yes
no
no
yes

yes
yes
yes

yes
yes

yes
yes

yes
yes
no

maybe
no
no

yes
no
no

yes
no
no

no

no

no

yes
no
no
no

maybe

yes

yes

no

yes

yes

maybe

yes

yes

no

no

no

yes

yes

yes

no

Severity
Indeterminate
Indeterminate
Indeterminate
Indeterminate
Indeterminate
Major

Specific problem
Ip over ATM Link Supervision Recovered
Ip over ATM Link Supervision Failed
NssSynchronization_SynchRefChanged
NssSynchronization_SystemClockStatusChanged
AuxPlugInUnit_SuccessfulRecoveryActionPerformedReestablishLink
NTP Server Reachability Fault

Counts
140633
132560
98702
90814
59183
45496

Indeterminate E1PhysPathTerm_NoCRC4Mfa
Warning
PDH Alarm Indication Signal

40204
37800

Minor
Unknown
Indeterminate
Major

AlmDevice_ExternalAlarm
Synchronization Start
Synchronization End
IMA Group Configuration Aborted

36907
24432
21853
20092

Warning

IMA Link Reception Unusable at Far End

18398

Minor
Warning

Anomalia funzionale CDZ


Remote Defect Indication on IMA Link

14751
14651

Major
Major
Critical
Indeterminate
Minor
Critical
Major

Synch Reference Path HW Fault


LossOfMains
Heartbeat Failure
Extensive Ethernet frame flooding
Loss of Synch Reference Redundancy
Anomalia impianto elettrico
System Clock in Holdover Mode

14144
14041
12192
10182
9999
9908
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
Critical
Critical
Major

Anomalia di blocco CDZ


Anomalia interruttore generale
None
AntennaBranch_FeederCurrentTooLowInBranchA

4466
4367
4336
4179

Major

PDH Loss of Signal

3908

Minor

DownLinkBaseBandPool_DLHWLessThanDLCapacity

3902

Major

Gigabit Ethernet Link Fault

3720

Critical
Mancanza rete
Indeterminate RuDeviceGroup_SuccessfulRecoveryActionPerformedBoardRestart
Major
AntennaBranch_FeederCurrentTooLowInBranchB

3597
3302
2933

Indeterminate Synchronization Aborted


Critical
NbapCommon_Layer3SetupFailure

2655
2589

Major

AntennaBranch_AntennaProblemInBranchA

2486

Critical
Minor

Allarme porta aperta


UpLinkBaseBandPool_ULHWLessThanULCapacity

2296
2219

Major

Loss of Tracking

2201

Major

AuxPlugInUnit_CommunicationLostWithAsc

2186

NodeBFunction_NodeRestarted
NodeBFunction_OaMApplicationRestarted
Allarme incendio
PIU restarted

2060
1927
1768
1447

Indeterminate
Indeterminate
Critical
Indeterminate

Indeterminate RuifDeviceGroup_SuccessfulRecoveryActionPerformedReestablishLink

1408

Major

RuDeviceGroup_TemperatureExceptionallyHigh

1353

Major

RuDeviceGroup_GeneralSwError

1349

Major

Carrier_SignalNotReceivedWithinTime

1284

Major

TimDevice_RadioClockIsNotStable

1059

Critical
Major

Anomalia batterie
Ethernet Switch Port Fault

1059
1046

Major

Loss of IMA Frame

956

PDH RNCI

924

Anomalia SOV

905

Warning

Critical

Major

DbccDevice_GammaDownlinkFailure

807

Major
Major

DigitalCable_Disconnected
CluDeviceGroup_EnclosureDoorOpen

733
713

Major

SystemOvervoltage

711

Critical
Major

Minimo Batterie S.E.


VC ete Loss of Connectivity

697
694

Critical
Batterie in scarica
Indeterminate Licensing_FeatureChange
Major
Clu_LossOfMains

694
661
600

Major

RunningOnBatterySupply

Indeterminate DeviceGroup_SuccessfulRecoveryActionPerformedBoardRestart
Major
NumberOfHwEntitiesMismatch
Major
PowerSupplySystem_LossOfMains

580
538
506
504

Major

AntennaBranch_AntennaSystemProblemInBranchB

497

Minor

PowerSupplySystem_RunningOnBatterySupply

488

RaxDeviceGroup_SuccessfulRecoveryActionPerformedBoardRestart
Licensing_CapacityChange
Temperatura anomala
RbsLocalCell_CellReleaseFailure
AscDeviceGroup_SuccessfulRecoveryActionPerformedBoardRestart
EnclosureProductDataMismatch
Impianto elettrico sezionato
Piccolo Allarme CDZ
EnclosureDoorOpen
PHY_E1Ppt_MI_AUTOLOCK_IND
Mancanza alimentazione impianti TLC
Anomalia CDZ armadio TX
PsDevice_LossOfMains

477
459
426
409
391
380
377
365
355
344
334
280
276

Clu_ActiveCoolerFanFault

273

Indeterminate
Indeterminate
Critical
Major
Indeterminate
Major
Critical
Critical
Major
Indeterminate
Critical
Critical
Major

Major

Major

GeneralHwError

270

Major

AntennaBranch_AntennaProblemInBranchB

264

Indeterminate AuxPlugInUnit_NewAuxiliaryUnitDetectedMatchesTheDefinedConfiguratio
n
Major
SystemUndervoltage

Major

Power Failure Left Slot

Indeterminate SlotNew PIU detected, no predefined configuration exist


Major
Loss of Cell Delineation on IMA Link

261
252

239

227
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

Indeterminate UpgradePackage Warning: Unexpected condition detected


Indeterminate TxDeviceGroup_SuccessfulRecoveryActionPerformedBoardRestart

185
175

Major

OperatingTemperatureTooHighBatteryDisconnected

158

Critical
Critical

Anomalia impianto elettrico - Sito Hub


System Clock Quality Degradation

157
155

Major
Critical
Major

FanFailure
Anomalia stazione energia
Disconnected

152
138
136

Major

Carrier_RejectSignalFromHardware

134

Major

IMA Link Transmission Misconnected

130

Indeterminate SlotNew PIU detected, matches the defined configuration


Critical
Anomalia stazione d energia
Major
AntennaBranch_AntennaSystemProblemInBranchA

Critical

Anomalia PLC

126
123
120

114

Minor
Major

Anomalia stazione d'energia


Plug-In Unit General Problem

112
112

Minor
Major

Fase e Rete S.E.


BfDevice_HighOperatingTemperatureSupervisionTooHighMainLoadDiscon
nected

104
103

Major

BfDevice_BatteryChargingFailure

103

Critical
Critical
Major

Allarme Porta
Pressurizzatore
Bfu_DcDistributionFailure

101
99
95

Indeterminate Pccpch_DownLinkChannelResourceRedundancySwitchOver

84

Critical
Critical
Critical
Major

Anomalia e Guasto S.E.


Apertura Int. Quadro Interf. Apparati
Apertura int. Generale
Carrier_NumberOfCarriersExceedsLicensedLimit

84
80
76
72

Critical
Major

Riserva
Carrier_MaxDlPowerCapabilityOutOfRange

72
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
Critical

Allarme porta armadio TX


License Key File Fault

66
65

Major

IMA Config Aborted at Far End

62

Critical
Critical
Critical
Critical
Critical
Major

Apertura int. CC/CA armadio TX


Mancanza rete armadio TX
Anomalia batterie armadio TX
Allarme fumo (precablato in fabbrica)
Anomalia Sensore di fumo (precablato in fabbrica)
UbchDeviceSet_CapacityLost

60
56
56
55
54
53

Critical
Major

Anomalia raddrizz. armadio TX


DigitalCable_CableFailure

53
52

Warning

PDH Remote Defect Indication

49

BfDevice_BatteryVoltageSupervisionTooLowMainLoadDisconnected

49

IMA Link Transmit Unusable at Far End

48

Major

Warning

Indeterminate RfifDeviceGroup_SuccessfulRecoveryActionPerformedReestablishLink

47

Major

PowerSupplySystem_SystemUndervoltage

45

Major

BatteryVoltageTooLowMainLoadDisconnected

44

Major

TrDeviceSet_GeneralSwError

44

Critical
Major

Allarme Sov
TxDeviceGroup_RaxTxInterfaceCommunicationError

41
41

Critical
Minor
Major

Anomalia stazione denergia


Temperatura anomala armadio TX
LowBatteryCapacity

40
35
34

Minor

Password File Fault

31

Indeterminate McpaDeviceGroup_SuccessfulRecoveryActionPerformedBoardRestart
Major
IMA Link Out of Delay Synchronization

31
31

Major
RuDeviceGroup_GammaUplinkFailure
Indeterminate NodeBFunction_MpTrafficApplicationRestarted

30
29

Major

BfDevice_BatteryMissing

29

Major

Slave TU Out of Synchronization

28

Major

FcuDeviceGroup_EnclosureDoorOpen

28

Major

BatteryMissing

28

Major
Critical
Major

RfCable_Disconnected
Grande Allarme CDZ
RaxDeviceGroup_GeneralSWError

27
27
25

Minor

TmaDevice_LnaDegraded

25

Major
Major

TrDeviceSet_GeneralHwError
IMA Group Start-Up at Far End

25
25

Major
Major

Inter-PIU Link Fault


TpaDevice_NumberOf40WPowerAmplifiersExceedsLicensedLimit

23
22

Indeterminate Node restarts soon. Confirm change


Major
AuxPlugInUnit_CommunicationLostWithRet

Critical
Critical
Major
Major

Loss of System Clock


EnclosureSmoke
RuDeviceGroup_GeneralHwError
TrDeviceSet_GeneralSwError

22
21

17
15
15
15

Major

DeviceGroup_GeneralSwError

14

Major
Major

RuifDeviceGroup_GammaUplinkFailure
DeviceGroup_TemperatureExceptionallyHigh

14
14

Critical
Critical
Major

NodeB down
Anomalia stazione di energia
TxDeviceGroup_GammaLinkFailure

14
13
13

XalmDeviceGroup_SuccessfulRecoveryActionPerformedBoardRestart
PsuDeviceGroup_SuccessfulRecoveryActionPerformedBoardRestart
Apertura Int. Differenziale
Apertura Int. Magnetorermico
AntennaBranch_FeederCurrentTooHighInBranchA

13
13
13
13
12

Major

BfDevice_BatteryVoltageSupervisionTooLowPrioLoadDisconnected

12

Major

NodeBFunction_HsdpaFlexibleSchedulerLicenseNotValid

11

Indeterminate
Indeterminate
Critical
Critical
Major

Major

NodeBFunction_16QamLicenseNotValid

11

Major
Major

EnclosureSmokeDetectorFailure
TpaDevice_AmplificationError

11
10

Major

AntennaBranch_FeederCurrentTooHighInBranchB

10

Major

RuDeviceGroup_PoorClockSignal

10

Indeterminate ObifDeviceGroup_SuccessfulRecoveryActionPerformedReestablishLink
Major

10

DeviceGroup_ExternalUnitFailure

10

Auto-Configuration of Board Not Possible

10

Major

NodeBFunction_HsdpaDynamicCodeAllocationLicenseNotValid

Major

AuxPlugInUnit_NewAuxiliaryUnitDetectedNotCorrespondingToTheDefined
Configuration

Critical

Grande Allarme Elettrico

Warning

Minor

Switch Internal Link Group 0 Fault

Major

TU Synch Reference Loss of Signal

Indeterminate NodeBFunction_MainProcessorRestarted
Indeterminate FanDeviceGroup_SuccessfulRecoveryActionPerformedBoardRestart
Major
Plug-In Unit Synch Hardware Fault

8
8
8

Critical
Minor

Mancanza alimentazione impianti TLC - TIM


Switch Internal Link Port 0 Fault

8
7

Major

TmaDevice_LnaFailure

Major
PsuDeviceGroup_GeneralHwError
Critical
Anomalia stazione denergia
Indeterminate UpgradePackage Warning: Handling of the final Configuration Version
failed
Indeterminate RruDeviceGroup_SuccessfulRecoveryActionPerformedBoardRestart
Minor
TxDeviceGroup_NumberOfProcessingResourcesNotSupported

7
6
6

Major
Critical
Critical
Indeterminate
Critical
Major

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

5
5
5
5
5
5

Major

RaxDeviceGroup_SoftwareDownloadFailure

Major

PsDeviceSet_GeneralSwError

Major

BfDeviceSet_GeneralSwError

6
5

Major

AcDeviceSet_GeneralSwError

Major

ClDeviceSet_GeneralSwError

Major

FREQUENT AuxPlugInUnit_PiuConnectionLost

Major

TimDeviceSet_ClockFrequencyStabilityMalfunction

Major

CircuitBreakerTripped

Major

PdDevice_InputVoltageTooHigh

Major

PdDevice_SystemVoltageTooHigh

Major

TimDevice_PhaseLockFailure

Major

EulForLargeRbsConfigLicenseNotValid

Major

Plug-In Unit HW Failure

Major

Security Level Fault

Major

TxDevicegroup_GeneralSWError

Critical

Allarme porta DVB-H

Major

NodeBFunction_HsdpaMultiCarrierLicenseNotValid

Major
Minor

FREQUENT NodeB disturbances


IMA Group Timing Mismatch

4
3

Major

TpaDevice_NumberOf60WPowerAmplifiersExceedsLicensedLimit

Major

Loss of Signal

Major
Major

DeviceGroup_GeneralHwError
PcuDeviceGroup_GeneralSWError

3
3

Major
Major

AiDeviceSet_GeneralHwError
Loss of Frame

3
3

Critical
Critical
Critical
Critical
Major

Allarme incendio - TIM


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

3
3
3
3
3

Critical
Major

Alta Temperatura
AscDeviceGroup_RetPortCurrentTooHigh

Indeterminate CluDeviceGroup_SuccessfulRecoveryActionPerformedBoardRestart
Major
PdDevice_SystemVoltageTooLow

3
3

3
3

Major

PdDevice_InputVoltageTooLow

Major

BfDevice_DcDistributionFailure

Major
Critical
Critical
Major

Cabinet_EnclosureDoorOpen
Anomalia Int. Generale DVB-H
Anomalia blocco CDZ DVB-H
Switch Plane A Fault

3
3
3
3

Major

RruDeviceGroup_FanFailure

Major

RaxDeviceGroup_BackplaneBusCollision

Minor

Switch Core Fault

Indeterminate PHY_Os155Spi_MI_AUTOLOCK_IND
Major
DeviceGroup_SoftwareDownloadFailure

2
2

Indeterminate RuifDeviceGroup_SuccessfulRecoveryActionPerformedBoardRestart

Major
Indeterminate
Minor
Major

TrDevice_GeneralHWError
Licensing_FaultySignature
Porta aperta
Psu_LossOfMains

2
2
2
2

Major

RruDeviceGroup_GammaLinkFailure

Major
Major

RuifDeviceGroup_ClockDistributionMalfunction
FuDeviceGroup_GeneralSwError

2
2

Minor

PowerSupplySystem_BatteryOvertemperature

Minor

FanDeviceGroup_LeftFanSpeedTooLow

Indeterminate Licensing_FingerPrintMismatch
Critical
Anomalia Batteria Armadio Tx

2
2

Critical
Critical
Critical
Critical
Critical
Warning
Major

Anomalia SE DVB-H
Allarme alta temperatura DVB-H
Mancanza rete - DVB-H
Batterie in scarica - DVB-H
Minima tensione batterie DVB-H
Large Number of Counters
PsuDeviceGroup_GeneralSwError

Indeterminate Licensing_FaultySeqNum
Indeterminate RuDeviceGroup_HardwareTestEndIndication
Major
Bfu_BatteryVoltageSupervisionTooLowPrioLoadDisconnected

2
2
2
2
2
2
2

2
2
2

Major

Bfu_BatteryVoltageSupervisionTooLowMainLoadDisconnected

Major

Clu_ActiveCoolerFault

Indeterminate PcuDeviceGroup_SuccessfulRecoveryActionPerformedBoardRestart
Major
RuDeviceGroup_LossOfSynch

2
2

Major

ObifDeviceGroup_GammaLinkFailure

Minor

OperatingTemperatureTooHighCapacityReduced

Minor
Major

Overspeanding net
LoPowTxCable_Disconnected

2
1

Critical

Anomalia stazione d energia (C.O VODAFONE)

Major

OptoCommCable_OptoCommunicationFailure

Major

AiDeviceSet_GeneralSwError

Major

PsDeviceSet_NumberOfHwEntitiesMismatch

Allarme incendio - Sito Hub


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

1
1
1
1
1
1
1
1
1
1
1
1
1
1
1

NodeBFunction_StandardizedTmaLicenseNotValid

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


Anomalia stazione di enrgia
ANOMALIA S.E.
TmaDeviceSet_GeneralHWError
FuDeviceGroup_HardwareTestEndIndication
RaxDeviceGroup_GammaLinkFailure

1
1
1
1
1
1

Major

Clu_ExternalFanFault

Major

TemperatureSensorFailure

Critical
Critical
Critical
Critical
Critical
Critical
Critical
Critical
Critical
Critical
Minor
Indeterminate
Critical
Critical
Major

Major
Indeterminate
Critical
Minor
Major
Indeterminate
Major

Major

RuDeviceGroup_ExternalUnitFailure

Major

TimDeviceSet_ClockMalfunction

Major
Critical
Minor
Major

TU Hardware Fault
Hoej Rumtemperatur
None
RfifDeviceGroup_IncorrectCableForDeliveredClock

1
1
1
1

Major

RfifDeviceGroup_IncorrectCableForReceivedClock

Indeterminate RfifDeviceGroup_SuccessfulRecoveryActionPerformedBoardRestart
Major
RuDeviceGroup_GammaDownlinkFailure

1
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
links"
for the
IMA group.
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
Climate Unit (CLU).

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.

Responsability(FIELD, REMOTE, REMOTE&FIELD)


Cell down
none
no
none
no
none
no
none
no
none
no
remote
maybe

Capacity reduced
no
no
no
no
no
maybe

Performance impacted
no
no
no
no
no
maybe

none
remote and/or field

no
maybe

no
yes

no
yes

remote
none
none
remote and/or field

no
no
no
yes

no
no
no
yes

no
no
no
yes

remote and/or field

no

yes

yes

field
remote and/or field

no
maybe

no
yes

no
yes

remote and/or field


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

yes, if no reduncancy
no
no
no
maybe
maybe
no
yes
no
no
no
no
yes
yes

no
no
maybe
yes
no
no
yes

remote

yes

yes

remote

yes (if no
no
redundancy)

yes

no

remote

maybe

yes

yes

remote

no

no

no

remote

yes

yes

yes

remote

maybe

yes

yes

remote

yes

yes

yes

field

maybe

yes

yes

field

no
no
no
no

no
no
no
yes

no
no
no
yes

maybe

yes

yes

remote and/or field

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

no, if no other alarm that


indicate a TX fault is
present

field

maybe

yes

yes

field

no
no
no

no
no
yes

no
no
yes

remote

no
yes

no
yes

no
yes

maybe

yes

yes

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

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

remote

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

maybe

maybe

remote

no

yes

yes

no
no
no
no

no
no
no
no

no
no
no
no

field

none, if no other alarm that indicate a RAX


fault is present

field

no
yes

no
yes

no
yes

remote and field

yes

yes

yes

remote and/or field

yes

yes

yes

remote and/or field

yes

yes

yes

remote and field

no
maybe

no
yes

no
yes

remote

maybe

yes

yes

remote and field

maybe

no

yes

no

no

no

remote and/or field

yes

yes

yes

remote
field

yes
no

yes
no

yes
no

field

no

no

no

remote

no
no

no
yes

no
yes

field

no
no
no

no
no
no

no
no
no

field

no

no

no

remote and/or field


field

no
no
no

no
no
no

no
no
no

field

maybe

yes

yes

field

no

no

no

field

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

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

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

field

no

no

no

remote
remote

field

field

maybe

maybe

maybe

field

maybe

yes

yes

field

no
maybe

no
yes

no
yes

field

no

no

no

remote

no
no

no
yes

no
yes

field

no

yes

yes

maybe

yes

yes

field

no

no

no

remote

no

no

no

maybe

maybe

maybe

remote

no

maybe

maybe

field

no

yes

yes

no
no

no
no

no
no

remote

field

field

no

no

no

no

no

no

field

no
no
no
yes

no
no
no
yes

no
no
no
yes

remote and/or field

yes

yes

yes

remote

maybe

yes

yes

field

no
no
maybe

no
no
yes

no
no
yes

no

no

no

field

no
maybe

no
maybe

no
maybe

field

no
maybe

no
yes

no
yes

field

no

no

no

field

no
no
maybe

no
no
no

no
no
no

remote

no
no
no
no
yes

no
no
no
no
yes

no
no
no
no
yes

remote and/or field

no
yes

no
yes

no
yes

remote

yes

yes

yes

maybe

yes

yes

remote

no

yes

yes

remote

no

yes

yes

none

field

remote

no

yes

yes

maybe

yes

yes

no

no

no

remote

no
maybe

no
yes

no
yes

remote

yes

yes

yes

no
no
no
no
no
maybe

no
no
no
no
no
yes

no
no
no
no
no
yes

no
yes

no
yes

no
yes

remote

maybe

yes

yes

field

maybe

yes

yes

remote

maybe

yes

yes

no

no

no

remote and/or field

field

remote and/or field

field

field

maybe

maybe

maybe

field

yes

yes

yes

remote and/or field

yes

yes

yes

remote and/or field

no
yes

no
yes

no
yes

remote and field

no
no
no

no
no
no

no
no
no

remote

no

no

no

remote

no
maybe

no
maybe

no
yes

yes
no

yes
no

yes
no

remote

field

no

no

no

field

yes

yes

yes

field

no

no

no

field

no

no

no

field

maybe
no
maybe

yes
no
yes

yes
no
yes

field

no

yes

yes

field
remote

yes
yes

yes
yes

yes
yes

field
remote

maybe
no

yes
yes

yes
yes

remote and/or field

no
no

no
no

no
no

remote
field
field
remote and/or field

yes
yes
yes
no, if no other alarms
no, if noare
other
present
alarms are
no, present
if no other alarms are present
yes
yes
yes
yes
yes
yes

remote and/or field

remote and/or field

maybe

maybe

maybe

yes
yes

yes
yes

yes
yes

no
no
maybe

no
no
yes

no
no
yes

field

no
no
no
no
no

no
no
no
no
yes

no
no
no
no
yes

field

yes

yes

yes

remote

no

yes

yes

field
field

remote

remote

no

yes

yes

field
remote and/or field

no
yes

no
yes

no
yes

field

no

yes

yes

remote and field

yes

yes

yes

field

no
maybe

no
yes

no
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

remote and field

no
no
maybe

no
no
yes

no
no
yes

remote and field

no
maybe

no
yes

no
yes

field

no

yes

yes

field

no
no

no
no

no
no

no
no
maybe

no
no
yes

no
no
yes

field

maybe
no
no
no
no
no

yes
no
no
no
no
no

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

field

remote and/or field

no

no

no

remote and/or field

no

no

no

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

no

yes

yes

maybe

yes

yes

no

no

no

maybe

yes

yes

no

no

no

field

remote

field
remote

remote and/or field

remote

no

yes

yes

remote

no
yes

no
yes

no
yes

remote

no

yes

yes

field

maybe

yes

yes

field
remote and/or field

maybe
no

yes
no

yes
no

no

no

no

no
no
no
no
no
no

no
no
no
no
no
no

no
no
no
no
no
no

field

field

no
no

no
no

no
yes

field

no
maybe

no
maybe

no
yes

field

maybe

maybe

yes

field

maybe

maybe

maybe

field

no
no
no
yes

no
no
no
yes

no
no
no
yes

field

maybe

maybe

maybe

field

maybe

yes

yes

field

yes

yes

yes

no
maybe

no
maybe

no
maybe

no

no

no

remote and/or field

remote and/or field

field

field

yes
no
no
no

yes
no
no
no

yes
no
no
no

remote and/or field

yes

yes

yes

remote and/or field


remote and/or field

yes
yes

yes
yes

yes
yes

maybe

maybe

maybe

no

no

no

no
no

no
no

no
no

remote

remote and/or field

remote
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

remote

no
no
yes

no
no
yes

no
no
yes

field

maybe

maybe

yes

field

maybe

maybe

maybe

remote and/or field

no
yes

no
yes

no
yes

remote and/or field

yes

yes

yes

field

maybe

maybe

maybe

field

no
yes

no
yes

no
yes

no

no

no

field

no

no

no

remote and/or field

yes

yes

yes

remote

no

no

no

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

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

remote

no

yes

yes

field

no
no
no
no
no
yes

no
no
no
yes
no
yes

no
no
no
yes
no
yes

field

maybe

maybe

maybe

field

no

no

no

field

field

maybe

yes

yes

field

yes

yes

yes

field

field

yes
no
no
yes

yes
no
no
yes

yes
no
no
yes

field

yes

yes

yes

remote and/or field

no
yes

no
yes

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

yes

no

Check if the cells are still up in RNC.

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

maybe

yes

no
no
no
no

Check for RAX board alarms

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.

no
yes

yes
yes

yes

no
yes

yes

yes

no

yes

yes
no
no

no
yes

no
no
no

no
no
no
no

yes

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

no

no
yes

yes

yes

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
yes

yes
yes

no
no
yes

no

no
maybe

no
yes

no

no
no
no

no

no
no
no
yes
no
yes

yes

yes

yes
yes

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

yes
yes

no

no
yes

yes

no
no
no
no
no
yes

no
yes
yes
yes

yes

no

maybe

yes

yes

no
yes

no
no
no

no

no
yes

yes
no

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

no

yes
no
no

yes
no
yes

yes

yes
yes

yes
yes

no
no

yes
no
yes
yes

maybe

yes
yes

no
no
yes

no
no
no
no
yes

yes

yes

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

yes

no
yes

yes

yes

no
yes

yes

yes

yes

no

yes

maybe

no
no
yes

no
yes

yes

no
no
no
no
yes

yes
no
no
no
no
no

yes
no

no

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

maybe

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

yes

no

no

no

maybe

yes

yes
no

yes

no

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

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

no

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

yes
yes

maybe

no

no
no

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

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

no
yes

no

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

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

no

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

yes

yes

yes
no
no
yes

yes

no
yes

You might also like