Академический Документы
Профессиональный Документы
Культура Документы
Problem
Metric
pmAverageRssi
Performance
High UL Noise
or RTM UL RSSI view
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)
Category
Accessibility
Problem
Lack DL Power or
increasing DL Tx
Power
Metric
pmNoFailedRabEstAttemptL
ackDlPwr
Actions
Comments
Additional actions
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
Comments
Additional actions
Category
Problem
Metric
pmNoFailedRabEstAttemptL
ackDlHw
or
Accessibility
Lack DL HW
Increasing HW Utilisation
from RTM Tool Reports
(cedh)
or
High Dl Credits Usage
Actions
Comments
Additional actions
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
Comments
Check for Cells (both Carriers)
Additional actions
Category
Accessibility
Accessibility
Problem
Failed After
Admission
Metric
pmnoFailedAfterAdm
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
Check es
Additional actions
Category
Problem
UL Throughput
Low EUL
Throughputs
DL Throughput
Low HS Throughputs
Metric
pmNoAllowedEul
Actions
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