Академический Документы
Профессиональный Документы
Культура Документы
Majo
Majorr Utra
Utran
nCell
Cell_E
_Ext
xte
ernal
rnalRe
Reso
sou
urceU
rceUna
nava
vail
ila
a 5981
ble
Majo
Majorr Nbap
NbapDe
Dedi
dica
cate
ted_
d_Rn
RncRcRb
bsCon
sContr
trol
olLi
Link
nkD
D 5466
own
Major
jor NodeSynch_Phase_Diffe
fferen
rence_Meas 5371
urement_Failed
Major
jor NodeSynch_Phasedriftrift_
_Thr
Threshold_E 1486
xceeded
Indete
Indetermin
rminate
ate A Non-L
Non-Loca
ocall MAU
MAU Has
Has Been
Been Chos
Chosen
en 1228
as the Active Client
Major
jor Utra
tranCell_MaxNumbe
mberOfS
rOfSy
ystemIn
mInfor
for 830
mationUpdateReattemptsIsReached
Indete
Indetermin
rminate
ate IpEthP
IpEthPacke
acketDa
tDataR
taRout
outer_
er_CnN
CnNotR
otResp
espoo 84
ndingToGTPEcho
Warni
Warning
ng Utra
UtranC
nCel
ell_
l_Nb
Nbap
apRe
Reco
conf
nfig
igur
urat
atio
ionF
nFai
ailu
lur
r 72
e
Major VC ete Loss of Connectivity 57
Major UtranCell_ComMeasFailCongCon 43
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
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 li nk. The fault can be permanent or
temporary. The possible causes are as foll ows:
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
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
the remote node is not accessible from this node. The fault can be per remote
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.
An alarm is issued when the Message Transfer Part level 3 (MTP3) detects a remote
faulty M3UA Association. The fault can be permanent or temporary.
The possible causes are as f ollows:
a transmission fault
a process or processor restart in this node
a faulty General Purpose processor Board (GPB)
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.
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 inter mediate 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 propri etary 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
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
Indeterminate Ip over ATM Link Supervision Recovered 140633
Indeterminate Ip over ATM Link Supervision Failed 132560
Indeterminate NssSynchronization_SynchRefChanged 98702
Indeterminate NssSynchronization_SystemClockStatusChanged 90814
Indeterminate AuxPlugInUnit_SuccessfulRecoveryActionPerformedReestablishLink 59183
Major NTP Server Reachability Fault 45496
Indeterminate Pccpch_DownLinkChannelResourceRedundancySwitchOver 84
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
Major BfDevice_BatteryVoltageSupervisionTooLowMainLoadDisconnected 49
Indeterminate RfifDeviceGroup_SuccessfulRecoveryActionPerformedReestablishLink 47
Major PowerSupplySystem_SystemUndervoltage 45
Major BatteryVoltageTooLowMainLoadDisconnected 44
Major TrDeviceSet_GeneralSwError 44
Indeterminate McpaDeviceGroup_SuccessfulRecoveryActionPerformedBoardRestart 31
Major IMA Link Out of Delay Synchronization 31
Major RuDeviceGroup_GammaUplinkFailure 30
Indeterminate NodeBFunction_MpTrafficApplicationRestarted 29
Major BfDevice_BatteryMissing 29
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 RuifDeviceGroup_GammaUplinkFailure 14
Major DeviceGroup_TemperatureExceptionallyHigh 14
Indeterminate XalmDeviceGroup_SuccessfulRecoveryActionPerformedBoardRestart 13
Indeterminate PsuDeviceGroup_SuccessfulRecoveryActionPerformedBoardRestart 13
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
Indeterminate ObifDeviceGroup_SuccessfulRecoveryActionPerformedReestablishLink 10
Major DeviceGroup_ExternalUnitFailure 10
Major NodeBFunction_HsdpaDynamicCodeAllocationLicenseNotValid 9
Major AuxPlugInUnit_NewAuxiliaryUnitDetectedNotCorrespondingToTheDefined 9
Configuration
Indeterminate NodeBFunction_MainProcessorRestarted 8
Indeterminate FanDeviceGroup_SuccessfulRecoveryActionPerformedBoardRestart 8
Major Plug-In Unit Synch Hardware Fault 8
Major TmaDevice_LnaFailure 7
Major PsuDeviceGroup_GeneralHwError 7
Critical Anomalia stazione dýenergia 6
Indeterminate UpgradePackage Warning: Handling of the final Configuration Version 6
failed
Indeterminate RruDeviceGroup_SuccessfulRecoveryActionPerformedBoardRestart 6
Minor TxDeviceGroup_NumberOfProcessingResourcesNotSupported 5
Major TxDevicegroup_GeneralHWError 5
Critical Batterie in scarica armadio P.R. 5
Critical Mancanza alimentazione impianti TLC TIM 5
Indeterminate RuDeviceGroup_PreloadFailed 5
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 TimDeviceSet_ClockFrequencyStabilityMalfunction 5
Major CircuitBreakerTripped 4
Major PdDevice_InputVoltageTooHigh 4
Major PdDevice_SystemVoltageTooHigh 4
Major TimDevice_PhaseLockFailure 4
Major EulForLargeRbsConfigLicenseNotValid 4
Major TxDevicegroup_GeneralSWError 4
Major TpaDevice_NumberOf60WPowerAmplifiersExceedsLicensedLimit 3
Major DeviceGroup_GeneralHwError 3
Major PcuDeviceGroup_GeneralSWError 3
Major AiDeviceSet_GeneralHwError 3
Major Loss of Frame 3
Indeterminate CluDeviceGroup_SuccessfulRecoveryActionPerformedBoardRestart 3
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
Indeterminate PHY_Os155Spi_MI_AUTOLOCK_IND 2
Major DeviceGroup_SoftwareDownloadFailure 2
Indeterminate RuifDeviceGroup_SuccessfulRecoveryActionPerformedBoardRestart 2
Major TrDevice_GeneralHWError 2
Indeterminate Licensing_FaultySignature 2
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
Indeterminate Licensing_FingerPrintMismatch 2
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
Indeterminate Licensing_FaultySeqNum 2
Indeterminate RuDeviceGroup_HardwareTestEndIndication 2
Major Bfu_BatteryVoltageSupervisionTooLowPrioLoadDisconnected 2
Major Bfu_BatteryVoltageSupervisionTooLowMainLoadDisconnected 2
Major Clu_ActiveCoolerFault 2
Indeterminate PcuDeviceGroup_SuccessfulRecoveryActionPerformedBoardRestart 2
Major RuDeviceGroup_LossOfSynch 2
Major ObifDeviceGroup_GammaLinkFailure 2
Minor OperatingTemperatureTooHighCapacityReduced 2
Major AiDeviceSet_GeneralSwError 1
Major PsDeviceSet_NumberOfHwEntitiesMismatch 1
Major NodeBFunction_StandardizedTmaLicenseNotValid 1
Major Clu_ExternalFanFault 1
Major TemperatureSensorFailure 1
Major RuDeviceGroup_ExternalUnitFailure 1
Major TimDeviceSet_ClockMalfunction 1
Major RfifDeviceGroup_IncorrectCableForReceivedClock 1
Indeterminate RfifDeviceGroup_SuccessfulRecoveryActionPerformedBoardRestart 1
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
Wron 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 si nal
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 fault IMA link.
external alarm
The possible causes are as f ollows:
a loss of cell delineation
a fault in the physical layer
Fault in the synchronization reference path
Commercial Power Failure
Link failure
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 l inks" for the IMA group.
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 r equirements.
The SFP Module does not m eet 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 f ollows:
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 operator-
defined threshold is reached.
To prevent the RBS boards being dam aged 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 f ollows:
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 forcin the RBS to run on batter su l .
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 tri ered.
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 tri ered.
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
s stem.
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
ca acit 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.
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
The alarm is issued when processing requests to a unit are rejected by the
hardware. No other unit faults are re orted.
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.
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
rou 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 GPB-
based RBS or the Digital Unit WCDMA (DUW) in a DU-based RBS is faulty. If there is more
than one faulty RAX board , each board issues a separate alarm.
external alarm
This alarm is issued when one or more of the units connected through the radio
interface link re orts 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 prioriti zed
out uts.
The alarm is issued when the Inverse Multiplexing ATM (IMA) link at the far end has
become unusable. It is lik ely 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 f unction, 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.
The alarm indicates failure in one or more of the units i n 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 Timin Unit hardware
This alarm is issued by the CluDeviceGroup Managed Object (MO) or by the
FcuDeviceGrou MO when an RBS door is o ened.
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) f ails.
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.
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.
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 reconf iguration
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 t he 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 sof tware 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 Timin 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 erformance is de raded.
The alarm indicates that a component is faulty and must be replaced.
external alarm
event, not 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 r edundancy, 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 rotection a ainst 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 diff erent, 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
ort.
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 aff ected 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 confi uration.
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
ca acit of the batter backu s stem.
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
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 non-
redundant 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 back plane 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 differ ent 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 back plane of the boards.
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 I D.
ponsability(FIELD, REMOTE, REMOTE&FIE Cell down Capacity reduced Performance impacted
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
field no no no
remote and/or field maybe yes yes
remote no no no
no no no
no no no
no no no
field no yes yes
no no no
no no no
field no yes yes
no no no
remote yes yes yes
no no no
none, if no other alarm that indicate a RAX no, if no other no, if no other alarm no, if no other alarm that
fault is present alarm that that indicate a RAX indicate a RAX fault is
indicate a fault is present present
RAX fault is
present
remote maybe maybe maybe
no no no
no no no
no no no
no no no
no no no
field yes yes yes
no no no
remote and field maybe yes yes
no no no
remote and/or field yes yes yes
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 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
no no no
field maybe yes yes
field no no no
no no no
remote no yes yes
field 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
no no no
field yes 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
field no no no
no no no
remote maybe 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
no no no
field maybe maybe maybe
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
field no no no
field no no no
no no no
remote and/or field no no no
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 no no no
remote and/or field yes yes yes
no no no
field maybe yes yes
no no no
remote and field yes yes yes
no no no
no no no
remote and field maybe yes yes
no no no
remote and field maybe yes yes
field no no no
no no no
no no no
no no no
remote and/or field maybe yes yes
field no no no
remote no no no
no no no
remote no yes yes
no no no
remote yes yes yes
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 no no no
no no no
no no no
remote and/or 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
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
no no no
remote and/or field yes yes yes
no no no
field yes yes yes
no no no
field no no no
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
no no no
no no no
no no no
field no yes yes
no no no
field yes yes yes
field no no no
field maybe 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
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.
yes
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
yes
yes
no
no
yes
yes
no
no
no
no
no
yes
no
yes
yes
yes
yes
no
maybe If the system voltage drops further, the RBS is disconnected.
yes
yes
no
yes
no
no
no
no
no
yes
yes
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
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
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