Documente Academic
Documente Profesional
Documente Cultură
User Name
Password
Log in
Remember Me?
Custom Search
Search
Forum
FAQCalendarForum Actions Quick Links
What's New?
vBQuiz
Submit
Advanced Search
HomeForumTelecom SoftwaresSoftware and Planning toolsNetwork Planning ALARM
DESCRIPTIONS FOR ROGERS & CINGULAR Results 1 to 1 of 1
Thread: ALARM DESCRIPTIONS FOR ROGERS & CINGULAR
Thread Tools
Display
10-02-2011, 01:31 PM #1
mosesdam
Valued Member mosesdam is offline
Valued Member
Reputation: 16 Add to this user's reputation Join Date
Apr 2011
Posts
38
Credits
3
Thanks (Given)
0
Thanks (Received)
1
Likes (Given)
0
Likes (Received)
4
Dislikes (Given)
0
Dislikes (Received)
0
Rep Power
0
The following alarms were seen during the Cingular Rollout on the RNC/RXI/RBS and
are still being seen in the Rogers HSDPA Rollout.
This document will be updated any time new alarms with workarounds come in.
If you come across an alarm that hasnt been reported please send the details to
Michael Cerulli (lmcmcer) so this document can be updated.
ALARM: Synchronization (RBS)
Mostly synchronization alarms are one of the following
Loss of Tracking
TU Synch Reference Loss of Signal
PDH Loss of Signal or PDH Loss of Frame or only Loss of Signal or Loss of
Frame
In most cases, the node lost one of the synchronization references and the node
needs to be resynched
TU Synch Reference Loss of Signal: TUB or CBU doesnt get the signal
? check the input port, cables, boards themselves
Loss of Tracking: Node is not in locked mode but in holdover mode
? resetLossOfTracking on Sync MO (use LDN of pp1 and pp2 which are the sync
references
PDH Loss of Signal/Frame or Loss of Signal/Frame: ET doesnt detect the signal
? check port, cables, board (put cable between Tx and Rx on the ET), if
everything is ok, then remove this port from the sync reference
ALARM: 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), see below for more info
ALARM: AiDevice_AntennaSystemProblem or
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: 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: AiDevice_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.
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
------------------------------------
In the RBS antenna branch A is TX/RX while branch B is RX only. Hence there are two
RX paths (RX diversity). The RBS monitors the two RX paths and compares the signal
received from both of these paths. If there is significant mismatch between these
paths (like TMA failure on branch B. Remember branch B has no supervision) then
this alarm is generated.
Symptom:
Warn IMA Link Reception Unusable at Far End remote_node_transmission_error
ImaGroup=1-1-ima1,ImaLink=3
Warn IMA Link Reception Unusable at Far End remote_node_transmission_error
ImaGroup=1-1-ima1,ImaLink=4
Warn IMA Link Transmit Unusable at Far End remote_node_transmission_error
ImaGroup=1-1-ima1,ImaLink=3
Warn IMA Link Transmit Unusable at Far End remote_node_transmission_error
ImaGroup=1-1-ima1,ImaLink=4
Warn Remote Defect Indication on IMA Link remote_node_transmission_error
ImaGroup=1-1-ima1,ImaLink=3
Warn Remote Defect Indication on IMA Link remote_node_transmission_error
ImaGroup=1-1-ima1,ImaLink=4
Solution:
Make a cv on the RBS and cold restart RBS to clear alarms for imalink=3 and
imalink=4.
cvms <cv name> <user> <comment>
acc 0 restart
Alarm: Carrier_ULGainTruncated
Symptoms
The RBS sectors which have long feed cables with feeder loss bigger than 6db get
alarm Carrier_ULGainTruncated, Bad Coverage on UE
RBS> alt
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> alt
Similar Threads:
GSM RF Optimization Guidelines Cingular
NSN 3G Allarms Descriptions
UltraSite EDGE BTS Unit Descriptions
RU20 Feature Descriptions
Reply With Quote Reply With Quote
Online LTE Tutorial by Ericsson
LTE 10A Air Interface
Introduction to LTE and Evolved Network Architecture
Carrier Aggregation Concepts for LTE Rel-10
Quick Navigation Network Planning Top
Previous Thread | Next Thread
Thread Information
There are currently 1 users browsing this thread. (0 members and 1 guests)
Tags for this Thread
antenna, hsdpa, moshell
View Tag Cloud
Bookmarks
Submit to Digg Digg Submit to del.icio.us del.icio.us Submit to StumbleUpon
StumbleUpon Submit to Google Google
Posting Permissions
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is On
[VIDEO] code is Off
HTML code is Off
Forum Rules