ALARM: Carrier_RejectSignalFromHardware
This alarm is issued from several HW, mainly RU, TXboard and RRU
? insert new HW
? if this doesnt help reboot the RBS (there has been a CSR which requires reboot)
ALARM: RuDeviceGroup_GeneralHWError
This alarm indicates problems with the component (written at beginning of alarm, in this
case RU)
? restart RU port, restart whole RU board
? if doesnt help, replace RU
ALARM: AiDevice_ExternalUnitFailure
This alarm appears if the feeder or jumper cable is connected incorrectly or damaged or the
TMA can be faulty
? check the antenna, jumper cables, cable connections visually and also by swapping them
among the sectors and see whether alarm moves
? check the TMA
ALARM: ExternalTma_LnaFailureBranchA
This alarm comes up when the two transistors amplifying the RF signals in the TMA fail. The
cell can still carry traffic as long as branch B is working, however, the RX might be
degraded.
=> run script to modify the TMA parameters
ALARM: Tma_LnaFailure
Check voltage (what TMA gives out),
if too low => check FU (bad or short circuit) => restart FU
if 0 => check if internalpower is set to yes (in ExternalTma MO)
check current (what antenna pulls out) => c heck if also AiDevice (antenna) alarm
ALARM: CLU_LossofMain
Lost power, node is in backup mode
ALARM: FCU_DeviceGroup_NumberofHWEntitiesMismatch
Was HW replaced? It then might have a different revision => restart PluginunitMO for that
piece
ALARM: FCU_DeviceGroup_FanFailure
1 FCU has fan, if enabled and unlocked, restart it
ALARM: RXDiversityLoss
Check if FU Is locked
ALARM: CarrierReject
If HSDPA is enabled, disable it, the alarm will then go away
ALARM: IMAGroupInsufficientLinks
IMAGroupInsufficientLinksatFarEnd
IMA is usually disabled, but IMA link is enabled
=> delete/recreate IMA, if that doesnt help,
=> or lock the active board (force it to go over to the redundant one), unlock after (so it goes
back)
=> or reset the processor on board
ALARM:PSUDeviceGroup_GeneralSWError
? restart PSUDeviceGroup
ALARM:Carrier_SingalNotReceivedWithinTime
i.e. Sector=1, Carrier=1
=> is TXboard up?
=> disable HSDPA, txdevicegroup on slot 10
ALARM:Bfu_BatteryChargingFailure
? check voltage on battery, should be around 50V, if not acc restartAuxUnit AuxPlugInUnit
(from PS1)
ALARM: ExternalTMA_degraded/Failed
Moshell <rbs>
cabx
# The cabx printout has PORT information at the end.
# For a 3 sector site there are 6 PORT information. One line for
# RU and FU devices (3 RU+3FU).
The printout shows the port, for example,
====================================
SMN APN PORT BOARD
====================================
0 12 port_0_dev_8 RU22
0 12 port_0_dev_8 FU
0 12 port_4_dev_9 RU22
0 12 port_4_dev_9 FU
0 12 port_8_dev_10 RU22
0 12 port_8_dev_10 FU
------------------------------------
even if the feeder attenuation is greater than 6db.The TRs HG19495 and HG67667
(WRNad12085) have been opened in PLM.
The problem occurs at sites with feeder losses bigger than 6dB and it is the entered feeder
loss value that triggers this alarm.
The alarm doesn't point out a real error (except in the case that the operator enters a value
that are bigger than 6dB by mistake), its more of an information that the feeder are large
and performance can get degraded with large feeder losses.
REMEDY:
This is a warning alarm issued when the UL amplification internally in the RBS cannot
compensate for the attenuation in the Antenna Feeder Cable. Optimal sensitivity is no
longer obtained.
Nothing in the RBS changes state because of this situation and trafic handling continues.
The external attenuation, that is the combination of the gain of the TMA and the UL
Attenuation of the Antenna Feeder (AntFeederCable), is larger than what the Low Noce
Amplifier (LNA) on the FU can compensate for. When that situation arise, the alarm
Carrier_ULGainTruncated is issued.
Accept the presence of the warning alarm. The ulAttenuation of AntennaFeederCable shall
not be changed to a false value, as that impacts the power measurements.
This alarm is planned to be removed in a later sw revision on the RBS.
The correction to this fault, WRNad12085, will be delivered by CR WRNad14794 in RBS
CXP 901 0809 R30A, included in RAN 4.0.12 which is planned to be released on June 22.
The P5ED package name is not known at the moment but will be released at the same time
as the P4 package.
ALARM: Loss of Tracking & Loss of Synch Reference Redundancy
RBS> alt
1969-12-31 21:44:18 M Loss of Tracking replaceable_unit_problem Synchronization=1
1969-12-31 21:45:18 w Loss of Synch Reference Redundancy replaceable_unit_problem
Synchronization=1
RBS> lpr sync
060810-10:16:56 172.20.229.73
==================================================
================================
Proxy MO
==================================================
================================
102 Equipment=1,Subrack=1,Slot=1,PlugInUnit=1,Cbu=1,Ti mingUnit=1,TuSyncRef=1
1035 TransportNetwork=1,Synchronization=1
1102 NodeBFunction=1,RBSxxxSynchronization=1
1164 NodeBFunction=1,Iub=RBS,NodeSynchTp=1
RBS> get 1035
================================================== ============
1035 TransportNetwork=1,Synchronization=1
================================================== ============
SynchronizationId 1
degradationIsFault 0 (degrNotFault)
syncRefActivity i[8] = 1 2 1 1 1 1 1 1
syncRefPriority i[8] = 1 2 0 0 0 0 0 0
syncRefStatus i[8] = 2 3 0 0 0 0 0 0
syncReference [8] =
>>> syncReference = Equipment=1,Subrack=1,Slot=1,PlugInUnit=1,Cbu=1,Et
mc1=1,T1PhysPathTerm=pp1
>>> syncReference = Equipment=1,Subrack=1,Slot=1,PlugInUnit=1,Cbu=1,Et
mc1=1,T1PhysPathTerm=pp2
>>> syncReference =
>>> syncReference =
>>> syncReference =
>>> syncReference =
>>> syncReference =
>>> syncReference =
systemClockA 2 (lockedMode)
systemClockB 7 (notApplicable)
systemClockRedundancy 0 (SYSTEM_CLOCK_USERS_USE_PLANE_A)
userLabel
==================================================
================================
Total: 1 MOs
RBS> acl 1035
==================================================
================================
Proxy MO Action Nr of Params
==================================================
================================
1035 Synchronization=1 addSyncRefResource 2
1035 Synchronization=1 changeSyncRefPriority 2
1035 Synchronization=1 removeSyncRefResource 1
1035 Synchronization=1 resetLossOfTracking 1
==================================================
================================
RBS> alt
Alarm should be gone.