Open

INFORMATION-MESSAGE 1 (9)
Prepared (also subject responsible if other) No.

ERA/RWO/J ERATEEN EAB/RWA/FA ERAKLEB EAB/RWO-04:0081 Uen

Approved Checked Date Rev Reference

ERA/RWO/J [Peter Hagren] 2004-12-21 B

PLM info 179, ASC and AIU alarm handling

Affected Node: RBS

Slogan: PLM info 179, ASC and AIU alarm handling

Service Impact: Medium

Target groups: 1:st & 2:nd line support, O& M personnel, Customer O&M
personnel

Rev. A First distribution

Rev. B Information on deliveries and TRs added.

Affected Product:

UTRAN PHASE: 2.1

Product number: HRB 105 102/1
Product Name: RBS3101, RBS3202
Configuration info: RBS with ASC
TR reference WRNac54620, WRNac57543, WRNac57911,
WRNac55670, WRNac60327.
(internal Ericsson CRs/TRs)
PLM info reference -

Problem description

When there is a AuxPlugInUnit_PiuConnectionLost alarm on ASC there may

be other alarms in the alarm list that shall be acted on before any action shall
be performed towards ASC.

The reason is that the alarm for ASC is not suppressed if there are faults in
other parts of the node.

This document will assist in guidance of which alarms to act upon.

If there is only alarm on ASC this document will also advise in how to
determine the system impact which can be used in order to evaluate the
urgency when to exchange ASC. The fault situation may have limited or no
traffic impact.
 Open
INFORMATION-MESSAGE 2 (9)
Prepared (also subject responsible if other) No.

ERA/RWO/J ERATEEN EAB/RWA/FA ERAKLEB EAB/RWO-04:0081 Uen

Approved Checked Date Rev Reference

ERA/RWO/J [Peter Hagren] 2004-12-21 B

Workaround

The process for handling AuxPlugInUnit_PiuConnectionLost alarm on ASC

shall be handled in 3 steps:

1 Alarm analysis

2 Recovery process

3 System impact analyses

4 Checks before changing ASC HW

1 Alarm analysis
The communication and alarm detection is basically connected as below:
MP AIU

ATF ASC

RET

ATF = A transport function in AIU for communication between MP and

ASC/RET

Before change of HW the alarms shall be analysed in the following order:

AIU alarms

ATF alarms

ASC alarms

RET alarms

If combinations of alarms are sent, the actions of the alarms shall be made in
the following order:
 Open
INFORMATION-MESSAGE 3 (9)
Prepared (also subject responsible if other) No.

ERA/RWO/J ERATEEN EAB/RWA/FA ERAKLEB EAB/RWO-04:0081 Uen

Approved Checked Date Rev Reference

ERA/RWO/J [Peter Hagren] 2004-12-21 B

Priority 1, AIU alarms:

All alarms on AIU shall be handled first:

PlugInUnit_CelloPiuProcessorProblem
PlugInUnit_BoardNotInstalledFault
For following MO’s:
ManagedElement=1,Equipment=1,Subrack=2,Slot=6,PlugInUnit=1
ManagedElement=1,Equipment=1,Subrack=2,Slot=9,PlugInUnit=1
ManagedElement=1,Equipment=1,Subrack=2,Slot=12,PlugInUnit=1

AiuDeviceGroup_MpDbOrAuCommunicationFailure
For following MO’s:
ManagedElement=1,Equipment=1,Subrack=2,Slot=6,PlugInUnit=1,AiuDeviceGroup=1
ManagedElement=1,Equipment=1,Subrack=2,Slot=9,PlugInUnit=1,AiuDeviceGroup=1
ManagedElement=1,Equipment=1,Subrack=2,Slot=12,PlugInUnit=1,AiuDeviceGroup=1

The alarms are reporting problem with the AIU or MP communication with the AIU.
Note: There may also be other alarms on AIU that are not communication alarms.
All alarms on AIU shall be cleared before proceeding.

Priority 2, ATF alarms:

All alarms on ATF shall be handled before acting on ASC alarms:

AuxPlugInUnit_MpDbOrAuCommunicationFailure
For following MO’s:
ManagedElement=1,Equipment=1,Sector=1,AuxPlugInUnit=1
ManagedElement=1,Equipment=1,Sector=2,AuxPlugInUnit=1
ManagedElement=1,Equipment=1,Sector=3,AuxPlugInUnit=1

AscDeviceGroup_MpDbOrAuCommunicationFailure
For following MO’s:
ManagedElement=1,Equipment=1,Sector=1,AuxPlugInUnit=1,AscDeviceGroup=1
ManagedElement=1,Equipment=1,Sector=2,AuxPlugInUnit=1,AscDeviceGroup=1
ManagedElement=1,Equipment=1,Sector=3,AuxPlugInUnit=1,AscDeviceGroup=1

The alarms are reporting communication problems in the interaction between MP and the
ASC ATF server in the AIU.
 Open
INFORMATION-MESSAGE 4 (9)
Prepared (also subject responsible if other) No.

ERA/RWO/J ERATEEN EAB/RWA/FA ERAKLEB EAB/RWO-04:0081 Uen

Approved Checked Date Rev Reference

ERA/RWO/J [Peter Hagren] 2004-12-21 B

Priority 3, ASC alarms:

AuxPlugInUnit_PiuConnectionLost
For following MO’s:
ManagedElement=1,Equipment=1,Sector=1,AuxPlugInUnit=1
ManagedElement=1,Equipment=1,Sector=2,AuxPlugInUnit=1
ManagedElement=1,Equipment=1,Sector=3,AuxPlugInUnit=1

The alarms are reporting communication problems in the interaction between ATF
function in AIU and ASC.

Priority 4 RET alarms

Before acting on RET alarms all above mentioned alarms have to be cleared.

AuxPlugInUnit_PiuConnectionLost
For following MO’s:
ManagedElement=1,Equipment=1,Sector=1,AuxPlugInUnit=2
ManagedElement=1,Equipment=1,Sector=2,AuxPlugInUnit=2
ManagedElement=1,Equipment=1,Sector=3,AuxPlugInUnit=2

The alarm is reporting communication problem in the interaction between ATF function in
AIU and RET.

Note: Try restart the RET in BEM before acting on this alarm.

2 Recovery process
If the alarm analysis shows that there is only an
AuxPlugInUnit_PiuConnectionLost alarm on ASC following, the following
procedure shall be done in order to try to get the communication working
again.

Restart the node.

Lock AIU and wait 5 minutes then unlock AIU.

Check if alarm on ASC is still present.

 Open
INFORMATION-MESSAGE 5 (9)
Prepared (also subject responsible if other) No.

ERA/RWO/J ERATEEN EAB/RWA/FA ERAKLEB EAB/RWO-04:0081 Uen

Approved Checked Date Rev Reference

ERA/RWO/J [Peter Hagren] 2004-12-21 B

3 System impact analysis

By tracing on TRX the interference level will indicate if the UL gain
amplification is working in ASC or not. The ASC may still do the amplification
even though the communication to the processor is down.

Start trace on TRX

lhsh 010400 te e trace9 * (if ASC is in sector 1)
lhsh 010700 te e trace9 * (if ASC is in sector 2)
lhsh 011000 te e trace9 * (if ASC is in sector 3)

Wait 15 –20 minutes.

Read the trace and error log from TRX
lhsh 010400 te log read (for sector 1)
lhsh 010700 te log read (for sector 2)
lhsh 011000 te log read (for sector 3)

By evaluation of pGamma data (interference levels) it can be determined if

traffic is possible in the sector.

Note: In order to get the printout in the trace and error log the cell has to be
set up. If there is no printout, check if the cell is setup.

Remove traces on TRX:

lhsh 010400 te default

lhsh 010700 te default
lhsh 011000 te default
 Open
INFORMATION-MESSAGE 6 (9)
Prepared (also subject responsible if other) No.

ERA/RWO/J ERATEEN EAB/RWA/FA ERAKLEB EAB/RWO-04:0081 Uen

Approved Checked Date Rev Reference

ERA/RWO/J [Peter Hagren] 2004-12-21 B

Example of trace printout from a node without alarms:

$ lhsh 010400 te log read
[2004-10-27 10:49:44.152] trxMeasIntLevelC ../src/TrxMeasIntLevelC.cpp:135 TRACE9:RSSI
measurement:
TR device 1025, -110 to -63 dBm (step 1 dBm).
pGamma for 0;0;0;8707;293;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;
branch A [2004-10-27 10:49:44.152] trxMeasIntLevelC ../src/TrxMeasIntLevelC.cpp:135 TRACE9:RSSI pGamma
measurement:
TR device 1025, 32 to 118 dBm (step 2 dBm). K_UBP_DBM = -145.900000
To reference the plotted power to ARP add K_UBP_DBM
0;0;0;0;9000;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;
[2004-10-27 10:49:44.160] trxMeasIntLevelC ../src/TrxMeasIntLevelC.cpp:135 TRACE9:RSSI
measurement:
TR device 1026, -110 to -63 dBm (step 1 dBm).
0;0;0;0;8999;1;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;
[2004-10-27 10:49:44.160] trxMeasIntLevelC ../src/TrxMeasIntLevelC.cpp:135 TRACE9:RSSI pGamma
measurement:
TR device 1026, 32 to 118 dBm (step 2 dBm). K_UBP_DBM = -145.900000
To reference the plotted power to ARP add K_UBP_DBM
0;0;0;0;8999;1;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;

pGamma for pGamma for branch

branch B B is 40 dBm

The rows indicate hits for each measurement during a 15-20 min period.

If there is more than 90% hits for pGamma in 32 dBm then the branch
will not be able to handle traffic.
 Open
INFORMATION-MESSAGE 7 (9)
Prepared (also subject responsible if other) No.

ERA/RWO/J ERATEEN EAB/RWA/FA ERAKLEB EAB/RWO-04:0081 Uen

Approved Checked Date Rev Reference

ERA/RWO/J [Peter Hagren] 2004-12-21 B

Example of a sector where both branches will not handle traffic:

Branch A
$ lhsh 011000 te log read
[2004-10-27 10:49:44.692] trxMeasIntLevelC ../src/TrxMeasIntLevelC.cpp:135 TRACE9:RSSI
measurement:
PGamma TR device 1537, -110 to -63 dBm (step 1 dBm).
branch A is 9000;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;
32 dBm [2004-10-27 10:49:44.692] trxMeasIntLevelC ../src/TrxMeasIntLevelC.cpp:135 TRACE9:RSSI
pGamma measurement:
TR device 1537, 32 to 118 dBm (step 2 dBm). K_UBP_DBM = -145.200000
To reference the plotted power to ARP add K_UBP_DBM
9000;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;
[2004-10-27 10:49:44.700] trxMeasIntLevelC ../src/TrxMeasIntLevelC.cpp:135 TRACE9:RSSI
measurement:
TR device 1538, -110 to -63 dBm (step 1 dBm).
9000;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;
Branch B [2004-10-27 10:49:44.704] trxMeasIntLevelC ../src/TrxMeasIntLevelC.cpp:135 TRACE9:RSSI
pGamma measurement:
TR device 1538, 32 to 118 dBm (step 2 dBm). K_UBP_DBM = -145.200000
To reference the plotted power to ARP add K_UBP_DBM
9000;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;0;

PGamma Determine the system impact:

branch B is
32 dBm
A. No traffic is possible in sector. Both branches have too low interference
levels (pGamma is 32 dBm)

B. Degraded, One branch has too low interference level. The diversity is lost
and the sector range will be decreased with app. 30 %

C. No traffic impact. Both branches have interference (pGamma) above 32

dBm

D. No traffic impact and RET is working.

o Note: for category D there is only alarm on ASC, not on RET.

The system impact shall be used together with the operator in order to
determine when the ASC shall be changed. If there is no traffic impact,
there is no need to change the ASC on short notice.
 Open
INFORMATION-MESSAGE 8 (9)
Prepared (also subject responsible if other) No.

ERA/RWO/J ERATEEN EAB/RWA/FA ERAKLEB EAB/RWO-04:0081 Uen

Approved Checked Date Rev Reference

ERA/RWO/J [Peter Hagren] 2004-12-21 B

4 Check before changing ASC HW

Loss of communication can be caused by mixed up feeders.

Check that branch A is connected to RX-TXA on ASC and branch B is

connected to RX-TXB, if not swap the cables.

Disconnected feeders, damaged feeders or water intrusion in the cables or

connectors can cause low interference levels and/or communication loss.

Check antenna feeder cables for any damages.

Solution

Alarms that are regarded as secondary shall be suppressed, there shall only
be one alarm present for a fault.

Solution by sending just one alarm for communication problem in the area of
AIU, ASC and RET will be implemented in RAN 2.1.6-CU5 (RBS CXP901913
R13J) by TR WRNac54620, WRNac57596 and WRNac57911.
Solutions are also implemented in RAN P3.0-UM8-CU2 (CXP9010373 R11B)
by WRNac55670 and WRNac60327, but the TRs are not one to one
transparent.

Alarms need to be handled in the right priority order, or else there is a risk of
HW replacement for HW that works correctly (e.g. making sure not to replace
ASC when there is a problem on AIU or feeder).
 Open
INFORMATION-MESSAGE 9 (9)
Prepared (also subject responsible if other) No.

ERA/RWO/J ERATEEN EAB/RWA/FA ERAKLEB EAB/RWO-04:0081 Uen

Approved Checked Date Rev Reference

ERA/RWO/J [Peter Hagren] 2004-12-21 B

Contact information:

If you require more information in regards to this PLM Info please raise a CSR
and send it to our Front office and we will endeavour to answer your question
as quickly as possible, The 3rd line front office queue is PWRN/Gate.

Archive information:

This PLM-INFO is stored together with other PLM-INFO at:

http://internal.ericsson.se/page/hub_radionetwork/products/plm/index.html