Professional Documents
Culture Documents
Alarms With Solutions
Alarms With Solutions
Go to Top
Page 1
Go to Top
Page 2
ALARM 2: Device_AntennaSystemProblem
Use the following RBS command:
Moshell <rbs>
lt antennabranch
get antennabranch antennaSupervisionThreshold
lt tma
get tma power
In the RBS there is feature to measure the VSWR (Voltage Standing Wave
Ratio). In simple words, the VSWR is a measure of the reflection in the RF
path caused by faulty equipment between the RBS and the Antenna. In case of
non-TMA sites, the RBS has another feature call DC resistance. See the
following table to see which features are used for the US market.
Go to Top
Page 3
No
No
Yes
No
4. TMA, power supply by FU/AIU
Yes
No
No
Yes
Yes
5. ASC
Yes
No
No
No
No
Go to Top
Page 4
ALARM 4: Carrier_RXDiversityLost
This alarm will cause a degraded carrier
check whether the RU or FU is locked
if connection is ok, try to restart the port for that sector "lhsh 001200/xxx
restart"
might be combined with antenna alarm (AiDevice_AntennaSystemProblem or
TmaDevice_AntennaSystemProblem)
ALARM 6: 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 7: RuDeviceGroup_GeneralHWError
Go to Top
Page 5
ALARM 8: Device_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 9: 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
Make sure the currentHighLimA TMA parameter is set to 180 just like the
currentHighLimB.
ALARM 10: Nbap (in RNC) OR Equipment for RUDeviceGroup (in RBS)
Check with Moshell the equipment view for the RBS
Restart the specific RU/FU in RBS Subrack
ALARM 11: Carrier_UL_GainProblem
Check attenuation , RBS needs one of each, DPCL, TPA, TR
ALARM 12: Carrier_UL_GainTruncated
Check whether feeder loss is outside the acceptable range (max is 6db)
Check power
Are RU boards steady
ALARM 13: AuxPlugInUnit_PiuConnectionLost
Piu powered off? Cable problem?
FU/RU? => Check "cabx"
Go to Top
Page 6
EC BUS disconnected
Power to FCU was cut
ALARM 14: 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 15: CLU_LossofMain
Lost power, node is in backup mode
ALARM 16: FCU_DeviceGroup_NumberofHWEntitiesMismatch
Was HW replaced? It then might have a different revision => restart
PluginunitMO for that piece
ALARM 17: FCU_DeviceGroup_FanFailure
1 FCU has fan, if enabled and unlocked, restart it
ALARM 18: RXDiversityLoss
Check if FU Is locked or the RX cable has been pulled out
ALARM 19: CarrierReject
If HSDPA is enabled, disable it, the alarm will then go away
ALARM 20: 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 21: PSUDeviceGroup_GeneralSWError
restart PSUDeviceGroup
ALARM 22: Carrier_SingalNotReceivedWithinTime
Go to Top
Page 7
Go to Top
Page 8
Go to Top
Page 9
y
301
135
acc SystemConstants=1 writeConst
y
302
270
acc SystemConstants=1 writeConst
y
303
135
acc SystemConstants=1 writeConst
y
304
270
Go to Top
Page 10
RBS> alt
Go to Top
Page 11
Go to Top
Page 12
>>> 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> acc 1035 resetLossOfTracking
=============================================================================
=====
1035 TransportNetwork=1,Synchronization=1
=============================================================================
=====
Are you Sure [y/n] ? y
=============================================================================
=====
Proxy MO Action Nr of Params
=============================================================================
=====
Go to Top
Page 13
Go to Top
Page 14
Go to Top
Page 15
Go to Top
Page 16
:
Activate emergency unlock keys on the licenses
Set the node to the correct recent timestamp. Refer to the RNC for correct
timestamp.
Alarm would be gone.
: ::
: ::
ALARM 36: Node Status Analyzer doesnt open
If you get the following error when opening "NODE STATUS ANALYZER" to view
cell activity remotely:
"mismatch: struct IDL:Configuration/DataTypes/UndefinedValue:1.0
UndefinedValue{long dummy} != string[0] vmcid: 0x0 minor code: 0
completed: No
Please run the Iub consistency report on the RNC.
How to open NODE STATUS ANALYZER:
In WCDMA RAN Explorer, Select the RBSRight click on itGo to "Tools"Select
"Node Status Analyzer"
How to run the Iub consistency report:
In WCDMA RAN Explorer, Select the RNC that RBS belongs toRight click on
itGo to "Consistency"Select "IUB Consistency Report"
# 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 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 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).
ALARM 37: RfCable_Disconnected equipment_malfunction
Due to the TX plugin from FU board being disconnected.
Plug it back in.
A restart of the plugin unit may be required to eliminate the alarm.
Go to Top
Page 17
Go to Top
Page 18
Go to Top
Page 19
Go to Top
Page 20