Contents

Work Flows
KPI CSR Workflow Description
KPI CSR Workflow

CSR Common_WF

Common_WF Introduction
This description is to be used by engineers as a reference when investigating CSRs reporting KPI degradation. It outlines an investigation strategy but
Dropped_calls
does not cover every scenario due to the complexity of the WRAN system. It is not exhaustive and currently covers the standard Ericsson WRAN
RRC Setup Failure Retainibility and Accessibility KPIs.

Iu Sig Setup Failure

NAS_WF

Rab Setup Failure

Ericsson KPI formulae
The following are the KPI formulae these workflows are based on.

Investigation Speech Accessibility:

Procedures

Subrack_IP

Tn_IP

ModuleMP_IP

Iublink_IP

Utrancell_IP

Alarms_IP

LoadRejs_IP

UehExc_IP

Admission_Denied
Rev A
Contents
2

Packet Interactive Accessibility:

Work Flows

KPI CSR Workflow

CSR Common_WF

Common_WF

Dropped_calls

RRC Setup Failure

Iu Sig Setup Failure

NAS_WF

Rab Setup Failure

Investigation
Procedures

Subrack_IP Speech Drop Rate

Tn_IP

ModuleMP_IP

Iublink_IP
Packet Interactive Drop Rate
Utrancell_IP

Alarms_IP

LoadRejs_IP

UehExc_IP

Admission_Denied
Rev A
 3

CSR Common
CSR escalated Workflow
When a CSR is first received a number of
initial actions should always be performed,

1. Product No 1. Check the product the CSR is

D
Supported? written on is still supported and
e
has not entered ML4. If the
-
e product is no longer supported the
s CSR should be de-escalated stating
c this, after consultation with the
a relevant gatekeeper.
l
2. DCG No 2. Check that the CSR contains the
a
Attached? mandatory and if applicable DCG Link:
t https://ericoll.internal.ericsson.com/sites/PLM/WRAN/Pages/
e problem specific information. If DataCollectionGuidelines.aspx
C the DCG logs are not present then
S they should be requested either by
R email or returning the CSR with a
note.
3. Primus case update and
Search Primus Link:
3. After becoming Familiar with the http://e-support.ericsson.se/iview/ui/eserver.asp
CSR problem / request, update the
primus case and perform a search.

Investigation Procedures
Common Workflows Rev A
 4

4. If an existing primus case is found

that answers the CSR request /
problem link that case to the CSR
Yes
4. Existing and fetch it into the CSR. De-
primus case escalate the CSR.
D
found?
e
-
e
s
c
a
A l
a
t
e
C
S
R

Rev A

Common Workflows Investigation Procedures

 5

KPI Common Moshell Commands

Workflow
A
B
e
y
o
n 1. If the CSR reports KPI degradation
1. CSR reports No
d continue with this workflow.
KPI
Otherwise the CSR is beyond the
degradation?
S scope of this description.
c
o
p 2. Confirm the customer is using
e standard KPI formula. Analyse the
2. Establish exact level and RNC> pmr -r 3 -m <hours>
ROP files to confirm the level of
date / time when KPI
degradation began.
degradation reported. Also RNC> pmx utrancell <counter> -m <hours>
establish when the degradation
first began (when comparing KPIs
time of day and day of week
3. Check the System logs should be considered).
around the time the
degradation started. 3. Check Alarm, Event, and System
logs for entries that coincide with RNC> lgaesrm
the start of KPI degradation.

4. Check the System logs for OAM

4. Check System logs for RNC> lguoqlrm
activates carried out on or in the
OAM activities.
day before the degradation began.

Rev A

Common Workflows Investigation Procedures

 6

5. Did degradation occur after RAN

upgrade. If so was it after the RNC
Yes 6. Check Release notes or the RBS upgrade.
& NIR for new SW.
5.Degraded 6. Check the Network Impact Report
after and release notes for changes,
upgrade?
new features or TRs that could be
responsibe.
7. Perform kget diff on
before and after upgrade 7. Check for changed parameter
kgets. values, newly enabled features
RNC> diff . kget_before_upgrade.txt
etc.. (Note: Use complete MoM).
8. Check for worst affected 8. Breakdown the affected KPI(s) per,
Subrack, Transmission link,
MMP, Iublink, Cells  Subrack
 Transmission link (ET Board) RNC> pmr -r 5,50-53 -m <hours>
 Module MP RNC> pmr -r 46-49,56-57 -m <hours>
Subrack  Iublink RNC> pmr -r 4,42-45 -m <hours>
 Utrancell level RNC> pmr -r 33-37 -m <hours>
RNC> pmr -r 24,27-28,29-31 -m <hours>
TN 9. If there is a common component
Yes that is causing the degradation
9. Common
execute that investigation
component MMP
found? procedure. If more than one
component is affected but it is not
Iublink widespread start with worst
affected component. If necessary
return and continue with step 10.
Cells

Rev A

Common Workflows Investigation Procedures

 7

10. If it is a Retainibility KPI that is RNC> pmr -r 3 -m <hours>

Yes
10. Is affected choose Drop calls. If
Retainibility Drop calls multiple KPIs are degraded choose
affected? the KPI that was first affected.

11. If it is an accessibility KPI that is

affected choose degradation type,
RRC  RRC Success Rate RNC> pmr -r 3 -m <hours>
 Iu Signalling Setup Success
11. Is Yes Rate.
accessibility Iu Sig  Standalone Srb Success Rate RNC> pmxhn utrancell nassignrelease -m
affected? (NAS). <hours> -a
 Rab Success Rate
NAS
No
12. Currently the scope of this
Rab description is limited to
12. Beyond scope of
Retainibility and Accessibility KPI
this description
degradation

Rev A

Common Workflows Investigation Procedures

 8

Dropped Calls Commands

Drops
1. For the worst cell extract the Rab RNC> pmxh utrancell=<worst cell>
specific counters and determine if it is pmnosystemrabrelease -m <hours> -a
a single Rab type that is affected.
 pmNoSystemRabReleaseSpeech
 pmNoSystemRabReleaseAmrNb
 pmNoSystemRabReleaseAmrWb
 pmNoSystemRabReleaseCs64
1. Check if one Rab Type is  pmNoSystemRabReleaseCsStream
affected.  pmNoSystemRabReleasePacket
 pmNoSystemRabReleasePacketStrea
m
 pmNoSystemRabReleasePacketStrea
m128
 pmNoSystemRabReleasePacketUra
 pmNoSystemRabReleasePsStreamHs
 pmNoSystemRbReleaseEul
 pmNoSystemRbReleaseHs
2. Check if increased drops
are related to one or more
2. Extract Iurlink counters. Check if one
Iurlinks.
specific Iurlink is affected or the drop
rate over Iur has causing the increase.
RNC> pmr -r 39 -m <hours>
 pmNoSystemRabReleaseCs64
 pmNoSystemRabReleaseCsStream RNC> pmxnh iurlink pmnosystemrabrelease -m
 pmNoSystemRabReleasePacket <hours> -a
 pmNoSystemRabReleasePacketStrea
m
 pmNoSystemRabReleaseSpeech

Rev A

Common Workflows Investigation Procedures

 9

3. Check for changes to TNL and RNL RNC> lguoqlrm

QoS.

3. Check the OAM logs

specifically from changes to
QoS.
4. Check with CN concerned for any QoS
changes related to Rab Request.

4. Check for QoS changes

performed in CN.

5. Check Node Synch in RNC and RBS. RNC> sts

and Frame Synch. RBS> sts

5. Check Node Synch in

RNC and RBS.

6. Check that Frame synch has not

RNC> pmxh DchFrameSynch Frames -m <hours> -
degraded between RNC and RBS. a
Check for increase in the number of RBS> pmxh IubDataStreams late -m <hours> -a
discarded or control frames being
6. Check Frame Synch.
sent.
 pmNoDchDlTimingAdjContrFrames
 pmNoDchUlDataFramesOutsideWindo
w
 pmNoDlDchDiscardedDataFramesE
UEH Exception  pmNoDlDchDiscardedDataFramesL
Analysis.  pmNoUlDchDiscardedDataFramesE
 pmNoUlDchDiscardedDataFramesL

Rev A
Common Workflows
Investigation Procedures
 10

Check for Admission denied counters?

RRC setup failure Commands
RRC
1. Check RRC Rej counters due to RNC> pmxh utrancell=<worst cell> pmnorejrrc -m
feature RRLC Early Filter, CC Sp <hours> -a
flow control and MMP load.
 pmNoRejRrcConnRrcLc
Yes
1. Found  pmNoRejRrcConnSpFlowCtrl
RRC Load Rejs  pmNoRejRrcConnMpLoadC
Rejects?
2. For the worst affected Utrancell
End check if admission denied counters RNC> pmr -r 21 -m <hours>
have increased,
RNC> pmxh utrancell=<worst cell>
Yes  pmNoRrcReqDeniedAdm
 pmNoRrcCsReqDeniedAdm
reqdeniedadm$ -m <hours> -a
Yes 3. Denied  pmNoRrcPsReqDeniedAdm
2. Check for
Adm denied? due to load
sharing? 3. Are the admission denied counters RNC> pmxh utrancell=<worst cell>
stepped due to loadsharing, pmnoloadsharingrrcconn -m <hours> -a
 pmNoLoadSharingRrcConn
No  pmNoLoadSharingRrcConnCs
AdmDenied  pmNoLoadSharingRrcConnPs

4. Have RL setup failure increased

Yes RNC> pmxh utrancell=<worst cell>
4. TN due to Transport Network (TN)
TN pmnorrcconnreqblock -m <hours> -a
Congestion? congestion,
 pmNoRrcConnReqBlockTn
 pmNoRrcConnReqBlockNode

Rev A

Common Workflows Investigation Procedures

 11

5. Check RBS counters for Radio Link RBS> pmxh uplinkbasebandpool

5. RL Failures Yes setup failures, pmsetupfailuressf64 -m <hours>
in RBS?  pmSetupFailuresSf128
 pmSetupFailuresSf64 RBS> pmxh downlinkbasebandpool
pmsetupfailuressf128 -m <hours>

6. Enable tracing in RBS 6. Request the traces from affected

to investigate failures. RBS to investigate failures. RBS> lh mp te e all NBAP_RESOURCE
Request support from RBS RBS> lh mp te e all RADIOLINK_REJECT

UEH Exception
Analysis.
7. If issue cannot be resolved with
trace information, request support
from RBS.

7. Request RBS support.

End

Rev A
Common Workflows Investigation Procedures
 12

Iu Signalling
Iu Sig setup failure
1. Check Alarm, Event, and System
logs for entries relating to RANAP RNC> lgaesrm egrep -i “ranap|sccp”
Yes or SCCP. If alarm found execute
1. Found
Alarm IP then return to next step if
Alarms & Alarm
Events? necessary.

2. Check the te log on RANAP and RNC> lh sccpmp te log read

SCCP MPs for ERRORs or Info
traces. Execute Error IP then RNC> lh ranapmp te log read
return to next step if necessary.

2. Found Yes 3. Are Initial Direct Transfers being

RNC> pmxh cnoperator pmidtdiscarded -m
Errors in te Errors discarded due to RANAP Overload,
<hours>
log?  pmIdtDiscarded
 pmIdtDiscardedCs
 pmIdtDiscardedPs

Check MP load during time of

degradation. Also RncFunction RNC> pmr -r 7 -m <hours>
3. Check RANAP/SCCP MPs
Refused Request counter for SCCP,
for overload? RNC> pmxh rncfunction
 pmRefusedRequestSccpMpLoad.
pmrefusedrequestsccpmpload -m <hours>

Rev A

Common Workflows Investigation Procedures

 13

4. Check for RANAP or SCCP

4. Check RANAP/SCCP congestion. DCG logfile “<RNC
Congestion? name>_dcg_m.log”, printouts
“ranap cong”
“rof_congestion_info”. Also check
that connected Ids are not
reaching maxconn value in
command “ranap conn”.
Yes RNC> lh modX te e all UEH_EXCEPTION.
5. UEH 5. If MMP Ueh Exception log are
Exceptions Exception available check for exceptions that
logs Analysis.
relate to RANAP or SCCP. If the
Available?
problem is still present targeted
analysis can be performed.
RNC> lh ranapmp te filter set "([1] = 26)"
Execute IP then return to next step
RANAP_ASN
if necessary.
RNC> lh ranapmp te e bus_send bus_receive
6. Check for ongoing Reset Resource
6. Check for ResetResource RANAP_ASN
procedures between RNC and CN
messages on RANAP MP.
no RANAP MP.

Rev A

Common Workflows Investigation Procedures

 14

7. Update the primus case with new

information from investigation to
7. Primus case update date.
D 8. If an existing primus case is found
and Search
e
Yes that answers the CSR request /
-
problem link that case to the CSR
e
and fetch it into the CSR. De-
s
escalate the CSR.
c
al 9. Request support from CN to
8. Existing
a investigate this problem in Core.
primus case
found?
t
e
-
C
S
R

9. Create Support
case towards CN.

Rev A

Common Workflows
Investigation Procedures
 15

NAS
NAS Sig failure Commands
General: Covers failures during the
NAS signalling phase, which is the
period after the Iu Signalling
1. Found Yes connection has been established up
Alarms & Alarm until the Rab Assignment Req is
Events? received by the RNC.

1. Check Alarm, Event, and System RNC> LGAESRM egrep -i “sccp|ranap”

logs for entries relating to
SCCP/RANAP. If alarm found
execute Alarm IP then return to
next step if necessary.
Yes
2. Found
SCCP Errors? Errors 2. Check the te log on the SCCP & RNC> lh sccpmp te log read
RANAP MPs for Errors/Info traces. RNC> lh ranapmp te log read

3. Check counters, compare with

values before degradation on RNC RNC>
and then cell level. Sort so worst
affected cells appear first. RNC>
3. Check SrbOnly and  pmNoSystemReleaseSrbOnly136
Abnormal Rel counters?  pmNoSystemReleaseSrbOnly34
 pmNoSystemReleaseSrbOnlyEul RNC>
 pmNoSystemReleaseSrbOnlyHs
 pmNoCellDchDisconnectAbnorm
pmxhn utrancell
SystemReleaseSrbOnly|DisconnectAbnorm
-m <hours>
pmx utrancell
pmNoSystemReleaseSrbOnly136 -m
<hours> -a | sort -k3 -n -r
pmx utrancell
pmNoCellDchDisconnectAbnorm -m
<hours> -m <hours> | sort -k3 -n -r

Rev A

Common Workflows Investigation Procedures

 16

4. Check the MMP logs for UEH

Exceptions relating to RANAP
(Pertinent ECs disconnectInd &
4. UEH Exc Yes
Exception Release Command with non
logs available? Analysis. “Normal” cause value). Compare
with logs from before degradation
began. Execute IP then return to
next step if necessary.

5. Request support from CN to

investigate this problem in Core.
5. Create Support
case towards CN.

Rev A

Common Workflows Investigation Procedures

 17

Rab Rab Setup failure Commands

2. Check RNC OAM log
for changes to Rab 1. Check for increase in Rab mapping
Yes Combination or QoS? or UE capability failures on node
level.
RNC> pmxhn utrancell
1. Failures in  pmNoInvalidRabEstablishAttemps failureUecap|invalidrabest -m <hours
UE Cap /  pmNoRabEstablishFailureUeCapa
mapping? 3. Request info from bility
customer wrt new UE 2. Check for changes to the support RNC> lgoqlnrm
releases? Rab Combinations in the RNC. Also
check for any changes to QoS
feature/parameters.

4. Create Support 3. Check if the degradation coincides

case towards CN. with the release of a new UE in the
market concerned.

4. Request support from Core wrt

any changes made to QoS
5. Adm parameters sent in Rab Req.
Denied
increased? 5. If increase in Adm denied for Rabs RNC> pmxhn utrancell [co]reqdeniedadm$ -m
execute IP. (From W12B the <hours>
Number of Rab Adm denied is
Yes
AdmDenied calculated as total Req denied RNC> pmxh utrancell
minus Rrc Req denied) pmNoReqDeniedAdm$|pmNoRrcReqDenie
 pmNoReqDeniedAdm dAdm$ -m <hours> -a | sort -k3 -n -r
 pmNoRrcReqDeniedAdm

Rev A

Common Workflows Investigation Procedures

 18

6. Enable tracing in RBS

to investigate failures.
6. For Speech Rabs check if number
of directed retries has changes.
 pmNoDirRetryAtt
RNC> pmxhn utrancell pmNoDirRetryAtt -m
Yes
7. TN 7. Check for increase in Rab failures <hours>
Congestion? TN RNC> pmxh utrancell pmNoDirRetryAtt -m
due to TN congestion or failure.
<hours> -a | sort -k3 -n -r
 pmNoRabEstBlockTnCs57
 pmNoRabEstBlockTnCs64
RNC> pmxhn utrancell pmNoRabEstBlockTn -m
 pmNoRabEstBlockTnPsIntHs
<hours>
 pmNoRabEstBlockTnPsIntNonHs
RNC> pmxh utrancell pmNoRabEstBlockTn -m
 pmNoRabEstBlockTnPsStrHs <hours> -a | sort -k3 -n -r
Yes  pmNoRabEstBlockTnPsStrNonHs
8. RL Failures  pmNoRabEstBlockTnSpeech
in RBS?
8. Check RBS counters for Radio Link
9. Enable tracing in RBS setup failure increase,
to investigate failures.  pmSetupFailuresSf256 RBS> pmxh uplinkbasebandpool
 pmSetupFailuresSf128 pmsetupfailuressf -m <hours>
 pmSetupFailuresSf64 RBS> pmxh downlinkbasebandpool
 pmSetupFailuresSf32 pmsetupfailuressf -m <hours>
UEH Exception
Analysis.  pmSetupFailuresSf16
10. Request RBS
support.  pmSetupFailuresSf8
 pmSetupFailuresSf4

End 9. Request the traces from affected

RBS to investigate failures.
RBS> lh mp te e all NBAP_RESOURCE
10. If issue cannot be resolved with RBS> lh mp te e all RADIOLINK_REJECT
trace information, request support
from RBS.

Rev A

Common Workflows Investigation Procedures

 19

INVESTIGATION
PROCEDURES
(IP)

Rev A
Contents
20

IP: Subrack Commands

Work Flows General: This investigation Procedure (IP) is
only to be used where KPI degradation is
KPI CSR Workflow
found to relate to a single Subrack (not a
CSR Common_WF single Transmission Link or MMP within the
subrack).
Common_WF
RNC> lgs
1. Check for ISL/ESL faults and Overload.
Dropped_calls RNC> lgt -g scx | egrep -i
- Check for crashes on Scb(x) boards “error|restart”
RRC Setup Failure - Check for errors on Scb(x) boards RNC> pmx . pmPeakBwLevel -m
- Check for ISL Overload <hours>
Iu Sig Setup Failure - Check the controlling MMP and ATM RNC> lkra
NAS_WF port for Iublinks are in same Subrack

Rab Setup Failure

RNC> lgt -g et | egrep -i
2. Check Subrack ETs for faults.
“error|restart”
3. Check MMP for usage and faults.
RNC> lh modxx te log read | egrep -i
Investigation “error|restart” (xx =
Procedures ms,es1,es2…)

Subrack_IP
4. Check the Subrack DcDevice RNC> std
Tn_IP RNC> lgt -g dcxx (xx = ms,es1,es2…)
allocation, usage and faults.
ModuleMP_IP
5. Check the Subrack CcDevice RNC> lgt -g ccxx (xx = ms,es1,es2…)
Iublink_IP allocation, usage and faults. For ATM if RNC> cedr
Ccdevice allocated in different Subrack than
Utrancell_IP
ET termination can cause ISL load. RNC> get IuLink
Alarms_IP atmUserPlaneTermSubrackRef
6. If ATM is used on Iu, check that
LoadRejs_IP atmUserPlaneTermSubrackRef is set in IuLink
MO, if not this can cause ISL load.
UehExc_IP
RNC> steg
7. Check RSTP configuration.
Admission_Denied
RNC> dcgx
8. Additional spas related information
can be gathered with dcgx command.

Rev A
Contents
21

IP: Transport Net Commands

Work Flows General: This investigation is only to be used
where KPI degradation is found to relate to
KPI CSR Workflow
Transport Network.
CSR Common_WF RNC> stv
1. Check TN/RSTP configuration.
RNC> sti
Common_WF
2. Check alarm log from bouncing links. RNC> steg
Dropped_calls
3. Check the System logs for OAM config RNC> lga
RRC Setup Failure changes associated with the TN.
RNC> lguoqlrm
Iu Sig Setup Failure 4. Check the ET board(s) for restarts or
NAS_WF errors.
RNC> lgt -g et | egrep -i
Rab Setup Failure 5. Check for Aal2 setup failures “error|restart”
RNC> lgs
6. Perform ping / ete loopback test on
suspected TN Links. RNC> pmr -r 57 -m <hours>
Investigation
Procedures 7. Check intermediate TN nodes RNC> stip
(Routers, RXIs etc..) for alarms or errors. RNC> acc <VclTp> eteLoopBack
Subrack_IP
8. Check intermediate TN nodes for OAM RXI> lga
Tn_IP RXI> lgt -g et | egrep -i
config changes.
“error|restart”
ModuleMP_IP
9. If a single far end node is involved RXI> lgs
Iublink_IP (MSC, SGSN, RBS) check this for alarm or
RXI> lguoqlrm
errors.
Utrancell_IP
10. Check far end node for OAM config
Alarms_IP RBS> lga
changes.
RBS> lgt -g et | egrep -i
LoadRejs_IP
11. Sometimes the nature of a TN fault “error|restart”
UehExc_IP
RBS> lgs
means isolating the faulty transmission link
requires removing it from service. This can be RBS> lguoqlrm
Admission_Denied
done by locking/unlocking TL in rotation until
the faulty link is found.

Rev A
Contents
22

IP: Module MP Commands

Work Flows General: This investigation is only to be used
where a KPI degradation is found to relate to
KPI CSR Workflow
a Module MP.
CSR Common_WF
1. Check the MMP for restarts or errors. RNC> lgs
Common_WF RNC> lgt -g modx | egrep -i
“error|restart”
Dropped_calls
2. Check MMP load.
RRC Setup Failure RNC> pmr -r 7 -m <hours>

Iu Sig Setup Failure

NAS_WF

Rab Setup Failure 3. Check the System logs for OAM RNC> Lguoqlrm
config changes associated with this MMP.

Investigation
Procedures 4. Check DCs associated with this MMP RNC> std
for overload and faults. RNC> pmr -r 9 -m <hours>
Subrack_IP RNC> pmxh dcdevice=<dc>
MeasLoad -m <hours>
Tn_IP
RNC> lgt -g dcx | egrep -i
“error|restart”
ModuleMP_IP
RNC> pmr -r 8 -m <hours>
Iublink_IP

Utrancell_IP
5. Check if large Location/Routing Areas RNC> get locationarea reserved
Alarms_IP could be causing high load due to paging. RNC> get Routingarea reserved
LoadRejs_IP

UehExc_IP

Admission_Denied

Rev A
Contents
23

IP: Iublink Commands

Work Flows General: This investigation is only to be used
where a KPI degradation is found to relate to
KPI CSR Workflow
all cells in a specific IubLink(s).
CSR Common_WF
1. Check the System logs for OAM config
changes associated with this site (RNC+RBS). RNC> Lguoqlrm
Common_WF
RBS> Lguoqlrm
Dropped_calls

RRC Setup Failure 2. Check system logs for recent entries RNC> lgaesrm
concerning Iublink/Utracells (RNC+RBS). RBS> lgaesrm
Iu Sig Setup Failure

NAS_WF
3. Check for errors related to this Iublink RNC> lgt -g modx
Rab Setup Failure on terminating MMP.

4. Check if Iublink credit usage going RNC> pmxh IubLink=<Iublink>

pmdlCredits|pmulCredits -m
over 80%, AvgDlCredits/AvgUlCredits.
Investigation <hour>
Procedures 5. Check resource usage and hanging
RNC> cedh
Subrack_IP resources.
RNC> lh ranapmp ueregprint age
3600
Tn_IP

6. Check for high Ul RSSI in the cells for RNC> pmr -r 32 -m <hours>
ModuleMP_IP
the site.
Iublink_IP
RBS> get NodeBFunction license
7. In RBS check license state and
Utrancell_IP
capability.
Alarms_IP RNC> strt
8. Check that Iublink is residing in same
RNC> pmxh
LoadRejs_IP Subrack as user plane resources. IubLink=<Iublink>,NodeSynch
delay -m <hours>
UehExc_IP

Admission_Denied 9. Check for changes in nodesynch delay RBS> get Synchronization

RBS> pmxh IubDataStreams
and also the RBS Synch status. Also counters
pmDchFrames.*late -m
for discarded frames in RBS. <hours>

RNC> ntpconfig info

10. Check NTP synch in RBS and RNC. RBS> ntpconfig info

Rev A
Contents

24

IP: Utrancell Commands

Work Flows
General: This investigation is only to be used
KPI CSR Workflow where a KPI degradation is found in a
Utrancell(s) but not a complete site.
CSR Common_WF
1. Check system logs for recent entries RNC> lgaesrm
Common_WF
concerning the Utracell (RNC+RBS). RBS> lgaesrm
Dropped_calls
2. Check the System logs for OAM config RNC> Lguoqlrm
RRC Setup Failure changes associated with this cell (RNC+RBS). RBS> Lguoqlrm

Iu Sig Setup Failure 3. Check for errors related to this cell on RNC> lgt -g modx | egrep -i “<Cell
Id>”
NAS_WF terminating MMP.

4. Check in the RBS for errors/restarts RBS> lgt egrep -i “error|restart”

Rab Setup Failure
on RAX/TX boards for this cell.

5. Check for high Ul RSSI in this cell.

Investigation RNC> pmr -r 32 -m <hours
Procedures

Subrack_IP

Tn_IP

ModuleMP_IP

Iublink_IP

Utrancell_IP

Alarms_IP

LoadRejs_IP

UehExc_IP

Admission_Denied

Rev A
Contents
25

IP: Alarms
Work Flows This investigation is to be used when relevant
Alarm(s) is found.
KPI CSR Workflow

CSR Common_WF Alarms:

Common_WF Where a relevant alarm(s) is found the

corresponding Operational Instruction (OPI) CPI Store Link:
Dropped_calls http://cpistore.internal.ericsson.com/alex
found in CPI Store should be executed. The
RRC Setup Failure
correct OPI can be found by using the Specific
Problem text from the alarm to perform a
Iu Sig Setup Failure search in the relevant library (e.g. search for
“Fach_InternalResourceUnavailable” in library
NAS_WF
“WCDMA RNC 3820 W12.0”)
Rab Setup Failure

Investigation IP: Error codes

Procedures

Subrack_IP SCCP Errors:

Tn_IP 1. SCCP Error codes can be decoded at

cello work support tool, they are also Cello Work support tool Link:
ModuleMP_IP
described in Maintenance Instructions SCCP http://support.dach.ericsson.se/worksupport/t
(1/1541-CAA 901 437 Uen). ools/Cello_err.php3
Iublink_IP
2. It may be necessary to contact CPP
Utrancell_IP support where an SCCP Error has occurred as
Alarms_IP the Error code description is often cryptic.

LoadRejs_IP

UehExc_IP

Admission_Denied

Rev A
Contents
26

IP: Load Rejects

Work Flows 1. If pmNoRejRrcConnMpLoadC is being RNC> pmxh utrancell NoOfSwDown -
stepped, check if down switch due to soft m <hours> -a
KPI CSR Workflow
congestion is occurring. This can result in high
CSR Common_WF load on mMP.
 pmNoOfSwDownEulCong
Common_WF  pmNoOfSwDownHsCong
 pmNoOfSwDownNgCong
Dropped_calls
 pmSoftCongRbsUlHw
RRC Setup Failure  pmNoOfSwDownNgHo
If down switch due to congestion is
Iu Sig Setup Failure confirmed, consider enabling feature RRLC
Early Filter on the affected cells.
NAS_WF

Rab Setup Failure 2. If pmNoRejRrcConnRrcLc is being

stepped check alarms in RNC related to this
RNC> altk
feature
Investigation Check also alarms in RBS related to HW RBS> altk
Procedures failures, refer to IP Alarms.

Subrack_IP
3. If pmNoRejRrcConnSpFlowCtrl is
Tn_IP being stepped, check the number of cells RNC> std cc
allocated to that CC device.
ModuleMP_IP
4. Check that the CcDevice used by this
Iublink_IP RNC> str -I <Iublink Id>
cell is in the same Subrack as the Iublink TN
Utrancell_IP termination.

Alarms_IP
RNC> pmr -r 8 -m <hours>
5. Check the CC device load.
LoadRejs_IP

UehExc_IP

Admission_Denied

Rev A
Contents
27

IP: UEH Exception Commands

Work Flows

KPI CSR Workflow UEH Exception Identification

CSR Common_WF There are a number of stratages that can be
Common_WF used when analysing UEH Exception to
identify the exception associated with the
Dropped_calls degradation. The strategy used will depend
on a number of factors including,
RRC Setup Failure
 The size of degradation, is it 0.1% or
Iu Sig Setup Failure
10%.
NAS_WF  Nature of the degradation, is it
localised to cluster/site/area or widespread .
Rab Setup Failure
 Available data, is data availabe from
before degradation began for comparison
purposes.
Investigation
Procedures In general it is good to narrow the area of
investiagtion as much as possible. Use
Subrack_IP
targated tracing on,worst affected cells,sites
Tn_IP or mMP, only tracing on worst affected
UeRc(s), etc.
ModuleMP_IP
General analysis:
Iublink_IP
This is where all UEH Exception are included
Utrancell_IP
and an analysis is done to breakdown the
Alarms_IP number of exceptions per Exception code,
Cause code, Transition type, etc ... This is
LoadRejs_IP
most useful when the size of the degradation
UehExc_IP is relatively large compared to the ”normal”
number of failures that occur for that KPI, and
Admission_Denied
data is available from before the problem
began to compare against.

This analysis is performed in 3 steps,

RNC> lh modx te e all
1. Parse exception logs from before UEH_EXCEPTION
degradation.
Cygwin$ java -jar
2. Parse exception logs taken during
ExcAnalyser.jar <Raw Exc file before>
degradation.
<Parsed Exc file before>
3. Using uehExcAnalyser.xlsm import
and analysis the data in excel. Cygwin$ java -jar Analyser.jar
<Raw Exc file during> <Parsed Exc file
during>

Rev A
Contents
28

Targeted analysis:

Work Flows This is where only UEH Exceptions that have

been associated with the stepping (or not
KPI CSR Workflow
stepping in case of attempt/success counters)
CSR Common_WF of the counter that resulted in the KPI
degradation are included in the analysis.
Common_WF
Additional counter specific tracing are
Dropped_calls required along with the standard UEH
Exception trace. Due to the counter tracing
RRC Setup Failure requirement useful trace logs are usually not
Iu Sig Setup Failure availabe from before the problem began for
comparison.
NAS_WF
This analysis is performed in 3 steps, RNC> pmx <mo> <counter> -m
Rab Setup Failure <hours>
1. Identify what counter(s) within the
KPI formula that has changed resulting in the
Investigation degradation. Extract the values for the
Procedures counters concerned individually and compare
against those from before degradation.
Subrack_IP RNC> lh modx ue_pm print -counter
| egrep -i <counter>
Tn_IP 2. Request counter specific traces to be
RNC> lh modx ue_pm enable -
taken for the counter(s) identified in step 1 (if counter <counter1 Id>
ModuleMP_IP it is an attempt without a success, trace both RNC> lh modx ue_pm enable -
counters). counter <conter2 Id>
Iublink_IP
RNC> lh modx te e trace6
Utrancell_IP PM_OBS_IND

Alarms_IP
Cygwin$ java -jar
LoadRejs_IP ExcAnalyser.jar <Raw Except file
3. Parse the logfile to extract only the name> <Parsed Exc file name>
UehExc_IP
UEH Exceptions that are associated with the <counter name>
Admission_Denied releveant counter(s). Cygwin$ java -jar
ExcAnalyser.jar <Raw Exc file name>
<Parsed Exc file name> <attempt
counter name> <”^success counter
name”>

4. Using ExcAnalyser.xlsm import and

analysis the data in excel.

Rev A
Contents
29

Filtering:
RNC> lh modx traceCounter on
Where the degradtion has been identified as <counter1 Id>
affecting a particular Utrancell(s) or UeRc, RNC> lh modx traceCounter on
Work Flows <counter2 Id>
then it is useful to narrow the tracing,
outlined in step 2 above, to the worst RNC> lh modx te e trace9
KPI CSR Workflow
UE_COUNTERS_GENERAL
affected cell and/or UeRc. This is done using
CSR Common_WF RNC> lh modx te e all
UE Random tracing. UEH_EXCEPTION
Common_WF RNC> lh modx uerandtrace on -cell
cid <cid> -uerc <uerc>
Dropped_calls RNC> lh modx uerandtrace max -
unlim
RRC Setup Failure

Iu Sig Setup Failure Examples: Worked Example: Speech drop rate

degradation.
NAS_WF
1. Increase in Speech Drop Rate KPI,
RNC> lh mod80 traceCounter on 4284
Rab Setup Failure with Utrancell cid 4217 being worst affected . RNC> lh mod80 te e trace9
UE_COUNTERS_GENERAL
RNC> lh mod80 te e all UEH_EXCEPTION
RNC> lh mod80 uerandtrace on -cell cid
Investigation 4217
RNC> lh mod80 uerandtrace max -unlim
Procedures
Cygwin$ java -jar ExcAnalyser.jar Inputfile.log
Subrack_IP outputfile.csv
PMNOSYSTEMRABRELEASESPEECH
Tn_IP
Worked Example: Eul Accessibility
ModuleMP_IP 2. Degradation of Eul Accessibility with degradation.
UeRc=25 in Utrancell cid=4200 worst
Iublink_IP RNC> lh mod8 traceCounter on 4564
affected. Worst affect UeRc found using
RNC> lh mod8 traceCounter on 4565
Utrancell_IP Attempt and Success UeRc MO counters. RNC> lh mod8 te e trace9
UE_COUNTERS_GENERAL
Alarms_IP RNC> lh mod8 te e all UEH_EXCEPTION
RNC> lh mod8 uerandtrace on -cell cid 4200
LoadRejs_IP -uerc 25
RNC> lh mod8 uerandtrace max -unlim
UehExc_IP
Cygwin$ java -jar ExcAnalyser.jar Inputfile.log
outputfile.csv
Admission_Denied
PMNORABESTABLISHATTEMPTPACKETINTERAC
TIVEEUL -crossreference
"^PMNORABESTABLISHSUCCESSPACKETINTERA
CTIVEEUL"

Rev A
Contents
30

UEH Exception Meaning

Where a relevant Ueh Exception is found

there are a number of options for further
Work Flows investigation,
KPI CSR Workflow CEH Link:
1. The exception mean and description
https://wcdma-
CSR Common_WF of the scenario in which it would occur, along commonexception.rnd.ki.sw.ericsson.se
with further trace suggestion can be found in
Common_WF the Common Exception Handler (CEH).
2. If the Exception is not present in the
Dropped_calls CDM Link UEH Exception Definition:
CEH (not all Ueh Exception are added to this
32/1551-CRA 403 38/1
RRC Setup Failure tool yet) then the exception meaning can be
found in UEH Exception Definition document
Iu Sig Setup Failure
(available in CDM).
NAS_WF 3. For further explanation and details it
is also possible to submit a support request
Rab Setup Failure
to the UEH Subsystem within RNC.

Investigation
Procedures

Subrack_IP

Tn_IP

ModuleMP_IP

Iublink_IP

Utrancell_IP

Alarms_IP

LoadRejs_IP

UehExc_IP

Admission_Denied

Rev A
Contents
31

IP: Admission
Work Flows
Denied Commands
KPI CSR Workflow
RRC Related:
CSR Common_WF
1. Check the following resource specific RNC> pmxh utrancell=<worst cell>
Common_WF counters for indication of RBS HW, Power or pmNoRrcReqDeniedAdm -m
downlink code congestion. Compare values <hours>
Dropped_calls
with those from before degradation began.
RRC Setup Failure  pmNoRrcReqDeniedAdmDlHw
 pmNoRrcReqDeniedAdmUlHw
Iu Sig Setup Failure  pmNoRrcReqDeniedAdmDlPwr
 pmNoRrcReqDeniedAdmDlChnlCode
NAS_WF
2. Check for hanging resources in the
Rab Setup Failure
RBS
RNC> cedh
Rab Related: RNC> lh ranapmp ueregprint age
Investigation 3600
Procedures 1. Check the following resource specific
counters for indication of RBS HW, Power or
Subrack_IP downlink code congestion. Compare values RNC> pmxh utrancell=<worst cell>
with those from before degradation began. FailedRabEstAt-m <hours>
Tn_IP
 pmNoFailedRabEstAttemptExceedConnLi
ModuleMP_IP mit
 pmNoFailedRabEstAttemptLackDlAse
Iublink_IP  pmNoFailedRabEstAttemptLackUlAse
 pmNoFailedRabEstAttemptLackDlChnlCo
Utrancell_IP
de
Alarms_IP  pmNoFailedRabEstAttemptLackDlHw
 pmNoFailedRabEstAttemptLackUlHw
LoadRejs_IP  pmNoFailedRabEstAttemptLackUlHwBest
 pmNoFailedRabEstAttemptLackDlHwBest
UehExc_IP  pmNoFailedRabEstAttemptLackDlPwr
 pmNoFailedRabEstAttEulRateCong
Admission_Denied

2. Check for hanging resources in the RNC> cedh

RBS. RNC> lh ranapmp ueregprint age
3600

Rev A