Category

Problem

Metric

pmAverageRssi
Performance

High UL Noise
or RTM UL RSSI view

RTM means Real Time Monitoring

Actions
Confirm observation with RTM tool. Check history to observe when it may
have been triggered - also check alarms
Compare RSSI vs. Traffic, internal and external (Check number of active
EUL users)
Observe traffic distribution across cells and consider idle mode offset
changes between carriers and neighbour cells to balance traffic more
evenly if possible and reduce UL issues on the problem cell
Consider reducing eulMaxOwnUuload and eulMaxRotCoverage on RBS
Local Cell (if EUL throughput is currently good, otherewise we will be
reducing EUL thp to an unacceptable level) to 60 and 40 respectively
Reduce admittable EUL users on RNC (eulServingCellUsersAdm) and
nonserving
Set Sf4AdminUl to 0, set sf8AdmUl to 0 (if (not already done)

Comments

Additional actions

Confirm if this has grown with traffic growth or possibly was an issue even
with minimal traffic on site (could be problem with Andrews)

Check for any cells in the surroundings that

have Scrambling code clashes 1st, 2nd order

Category

Accessibility

Problem

Lack DL Power or
increasing DL Tx
Power

Metric

pmNoFailedRabEstAttemptL
ackDlPwr

Actions

Check Parameters and Status

1st Carrier Congesting - 2nd Carrier OK

1st & 2nd Carrier High DL Tx Power

Comments

Additional actions

RNC Max Power Setting = Calculated RBS Power Available

Check HS Power Margin = 0
Check RBS Maxtransmission pwr vs. Utran Cell Maximum capability
Check for faulty MCPA especially for 3202 NodeB's
Check that CPICH is not set above the default value
Check if any sites in the surroundings have gone down
Check IFLS is active towards 2nd Carrier (List Parameters)
LBHO should be active towards GSM - Check gsm relation activity
Remove Idle Offset (-50) from 2nd to 1st Carrier
Remove Idle Offset (+50) from 1st to 2nd Carrier
Consider DR to GSM activation if GSM capacity available

Can consider reconfiguring LBHO to IF and not

GSM
Monitor CM usage

Can overlapping GSM Cells(s) handle additional traffic?

Confirm LBHO GSM is active
Consider encouraging LBHO GSM with 2G Planner approval
Consider activating DR GSM with 2G Planner approval
Check status of traffic distribution of neighbouring cells and consider applying
(-ve) qOffsets to encourage traffic to camp on neighbouring cells
Consider increasing PWR ADM > 75% (Delay Soft Congestion)

Monitor CM usage

Category

Problem

Metric

pmNoFailedRabEstAttemptL
ackUlHw
or
Accessibility

Lack UL HW

Increasing HW Utilisation
from RTM Tool Reports
(cedh)
or
High Ul Credits Usage

Actions

Check Parameters & Status

3rd Carrier Available

3rd Carrier not available

Comments

Additional actions

Run Cedhr command to confirm high CE Usage

Set SF4ADMUL (384kbps ul)to 0 on utrancells
Considering adding another RAX/DUW (may need additional license)
Check available and licensed CE in both BB Pools
Check if grace period has expired
Check for faulty RAX - make sure all RAXs defined are operational
Check if any sites in the surroundings have gone down
Remove Idle Offset (-50) from 3rd to 1st Carrier
Remove Idle Offset (+50) from 1st to 3rd Carrier
Consider idle offsets to neighbouring sites if capacity available
If restricted by license capacity consider reducing the licensed fraction (get .
Frac) on rbs for BB pool 2

Can overlapping GSM Cells(s) handle additional traffic?

Consider activating DR GSM with 2G Planner approval
Check status of traffic distribution of neighbouring cells and consider applying
(-ve) qOffsets to encourage traffic to camp on neighbouring cells

Consider DR GSM anyway if GSM not

congested

Category

Problem

Metric

pmNoFailedRabEstAttemptL
ackDlHw
or
Accessibility

Lack DL HW

Increasing HW Utilisation
from RTM Tool Reports
(cedh)
or
High Dl Credits Usage

Actions

Check Parameters & Status

3rd Carrier Available

3rd Carrier not available

Comments

Additional actions

HW ADM should be set to 100% (both UL and DL)

Run Cedhr command to confirm high CE Usage
Set SF8ADM (384 dl) to 0 on utrancells
Consider reducing hscoderesources on txdevices
Considering adding another TXB (may need additional license or use
EMERGENCY UNLOCK)
Check available and licensed CE in both BB Pools
Check if grace period has expired
Check for faulty TXB - make sure all TXBs s defined are operational and none
are locked
Check if any sites in the surroundings have gone down
Remove Idle Offset (-50) from 3rd to 1st Carrier
Remove Idle Offset (+50) from 1st to 3rd Carrier
Consider idle offsets to neighbouring sites if capacity available
If restricted by license capacity consider reducing the licensed fraction (get .
Frac) on rbs for BB pool 2

Can overlapping GSM Cells(s) handle additional traffic?

Consider activating DR GSM with 2G Planner approval
Check status of traffic distribution of neighbouring cells and consider applying
(-ve) qOffsets to encourage traffic to camp on neighbouring cells

Consider DR GSM anyway if GSM not

congested

Category

Problem

Metric

pmNoFailedRabEstAttemptL
ackDlCode
Accessibility

Lack of or Increasing
DL Channelisation
Code Usage

or
Increasing DL
Channelisation Code Usage
in RTM Tool

Actions
Check RTM Tool DL Channelisation Code Usage

Check Parameters

1st Carrier Congesting - 2nd Carrier OK

1st & 2nd Carrier High DL Channelisation Code Usage

Comments
Check for Cells (both Carriers)

Additional actions

If HS active check numHsPdschCodes on RNC Utran Cell MO

Reduce SF8adm users (384 dl) on rnc utrancell
Check number of users in CM
Check if neighbouring site/cell has gone down
Consider reconfiguring LBHO to IF instead of GSM or encouraging LBHO GSM
more aggressively if GSM can handle additional traffic
Monitor CM Usage and target GSM
Remove Idle Offset (-50) from 2nd to 1st Carrier
Congestion
Remove Idle Offset (+50) from 1st to 2nd Carrier
May need to reduce CM usage

Can overlapping GSM Cells(s) handle additional traffic?

Confirm LBHO GSM is active
Consider encouraging LBHO GSM with 2G Planner approval
Consider activating DR GSM with 2G Planner approval
Check status of traffic distribution of neighbouring cells and consider applying
(-ve) qOffsets to encourage traffic to camp on neighbouring cells

Monitor CM Usage and target GSM

Congestion
May need to reduce CM usage

Category

Accessibility

Accessibility

Problem

Failed After
Admission

Metric

pmnoFailedAfterAdm

Non-HO Req Denied pmNoOfNonHoReqDenied

Adm
AdmXX

Actions
Check if applicable to RAB, RRC, CS, PS or Both
Check RTM tool for SF, Users and CM Usage.
Check for mismatch between RNC and RBS Users ADM
Check AAL2AP unsuccess on RBS and RNC
Request BSS to check te logs for errors
Check for alarms and errors on boards
Check RNC Iublink UL & DL HW Adm
Check for alarms
Consider adjusting qOffset between Carriers if it is Carrier specific failure
Consider qOffset changes to neighbouring cells to offload capacity
Could be other transmission issue!
If HS Users Check num users, RNC Cell, RBS Cell and License
If EUL Users Check num users, RNC Cell, RBS Cell and License
Check utilisation of various resources in RTM Tool
Consider adjusting HSDSCHInactivityTimer on RNC

Comments

May need to move Class B onto VC40 - Back Office Support

Check es

from 10s to less

Additional actions

Category

Problem

UL Throughput

Low EUL
Throughputs

DL Throughput

Low HS Throughputs

Metric

pmNoAllowedEul

Actions

Increase the "eulMaxOwnUuLoad" and "eulMaxRotCoverage" to a

higher value - not recommended too high due to contribution to
increased UL Int and impact to other services
Decrease no serving cell Eul users on RNC Utran Cell
Disable EUL Channel on Cell
Check RTM for numbers of HS Users and R99 Code Utilisation
Check HSTXB configuration, licenses & codes on RBS
Check Iub on RBS for MaxHsRate
Check Iub Limiting Ratio stats
Check pmRemainingResource Check on RBS Stats

Comments

This counter will effectively monitor cases where the RBS scheduler prevents
data being sent due to a Rise Over Thermal / interference. Quite often this can
occur when you have multiple EUL user connecting simultaneously and
subsequently noise is increased (UL_RSSI and ROT). Note in this case EUL
CSSR will look good as the RAB is given but the user will sit in limbo as the
RBS scheduler does not send any data due to interference detection.
Disabling EUL Channel: Note this is only for those extreme cases and should
only be considered as last resort should EUL be severely limiting data. What
determines severe. The threshold should be half a ROP period (may be even
more) i.e. 7 mins to 10 mins. So this translates to a counter value of 4200 (7
mins) and 6000 (10 mins) as congestion is sampled every 100ms. Breakdown
below:
4200 Counter Value = 7 min
6000 Counter Value = 10 min

Additional actions

Category

Problem

Metric
pmEs, pmSes, pmUas

Transmission

Errored Seconds on
Iub or Alarms

or
Alarm

Actions
Check status of e1 and ima (st e1 & st ima)
Confirm with pmx on Node B for es, ses and uas
Confirm impact to accessibility, retainability etc
Raise with front office to address with Telkom and check DXX etc
Consider locking E1 in meantime and possibly site altogether

Comments

Additional actions