Professional Documents
Culture Documents
Alarm Descriptions For Rogers & Cingular: Did You Find This Post Helpful?
Alarm Descriptions For Rogers & Cingular: Did You Find This Post Helpful?
TmaDevice_AntennaSystemProblem
Which alarm shows up depends on whether the antenna is connected to a TMA
? check the antenna, jumper cables, cable connections visually and also by swapping them
among the sectors and see whether alarm moves
? check FU
? check the value of the supervision parameter (should be 49, but if set to 0 no alarm is reported)
? restart the RU
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: Nbap (in RNC) OR Equipment for RUDeviceGroup (in RBS)
Check in EMAS the equipment view for the RBS
Restart the specific RU/FU in RBSSubrack
ALARM: Carrier_UL_GainProblem
Check attenuation in BEMAS, RBS needs one of each, DPCL, TPA, TR
ALARM: Carrier_UL_GainTruncated
Check whether feeder loss is outside the acceptable range (max is 6db)
Check power
Are RU boards steady
ALARM : AuxPlugInUnit_PiuConnectionLost
Piu powered off? Cable problem?
FU/RU? => Check cabx
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: UtranCell_NbapMessageFailure (in RNC)
AIDevice_ExternalUnitFailure + CarrierRejectSignalFromHW (in RBS)
Check if antenna feeder is too low in t&e
Check FU
ALARM: UtranCell_NbapMessagefailure (RNC)
Ai_Device_ExternalUnitFailure (RBS, equipment malfunction, FU aidevice=1)
Carrier_RejectSignalFromHardware (RBS)
In RBS t&e: antennafeeder low/high
? turn off TMA power
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
-----------------------------------lhsh 001200/port_x_dev_yy fui get devstat
# get port information from cabx
Ensure that the devstat printout from above has ~16000mV for each sector and the current is
between 50mA-200mA, if and only if the site has TMAs defined and is being powered by the
UMTS RBS (MO:externalTMA, Attribute:internalpower).
Each RBS in the US market, has threshold when this alarm is generated. These thresholds are
input into the RBS using scripts. The thresholds vary for single band TMAs and dual band
TMAs. Make sure that the right threshold is set for the type of TMA. Below is the threshold
script for quick reference.
acc SystemConstants=1 writeConst
y
300
00001
acc SystemConstants=1 writeConst
y
301
135
acc SystemConstants=1 writeConst
y
302
270
acc SystemConstants=1 writeConst
y
303
135
acc SystemConstants=1 writeConst
y
304
270
For more information about the thresholds please see the following document.
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
==================================================
================================
1035 Synchronization=1 resetLossOfTracking 1
Parameter 1 of 1, syncReference (moRef-ManagedObject):
Enter mo LDN: Equipment=1,Subrack=1,Slot=1,PlugInUnit=1,Cbu=1,Et
mc1=1,T1PhysPathTerm=pp1
>>> Return value = null
==================================================
================================Total: 1 MOs attempted, 1 MOs actioned
RBS> acc 1035 resetLossOfTracking
==================================================
================================1035 TransportNetwork=1,Synchronization=1
==================================================
================================
Are you Sure [y/n] ? y
==================================================
================================
Proxy MO Action Nr of Params
==================================================
================================
1035 Synchronization=1 resetLossOfTracking 1
Parameter 1 of 1, syncReference (moRef-ManagedObject):
Enter mo LDN: Equipment=1,Subrack=1,Slot=1,PlugInUnit=1,Cbu=1,Et
mc1=1,T1PhysPathTerm=pp2
>>> Return value = null
==================================================
================================
Total: 1 MOs attempted, 1 MOs actioned
RBS> alt
Alarm should be gone.