Connection Drop Rate (CDR) This is evaluate disconnections/drops for all kind of services (QCI1 to QCI9)
E-RAB Release whilst Active/(Initial ERAB Setup Success+ Additional ERAB Setup Success)
Voice over LTE Drop Rate (VDR) - This is to evaluate call drops during Volte call.
E-RAB Release whilst Active*/(Initial ERAB Setup Success*+ Additional ERAB Setup Success*)
*Use values from only QCI1
Handover Success Rate (HOSR) This is to evaluate mobility performance of the network.
Inter eNB handover Success/Inter eNB handover Attempt
HOSR Troubleshooting
1. PCI & RSI Planning Validation- Refer Basic Parameter Guideline *
1. *If Auto PCI and Auto RSI is enabled (Check SON Profile from Netspan) then ignore this step.
2. Clock Issue: Refer Alarm Document for clock related issues
1. If No clock alarms but RRC Success Rate < 50% then swap L2 Switch & monitor the performance
2. If multiple cells are having poor RRC Success Rate then try CSS reboot.
3. Audit NRT table
1. Validate SMC installation plan along with surrounding Macro locations.
2. Check if all possible neighbours are reported in NRT and their X2 links are setup to form required NBR relationship.
3. Check stats to find out specific NBR relationship causing handover failures.
4. Neighbour cell Availability- Check if neighbouring cells are OOS and causing handover failure because of coverage gaps or poor
coverage areas generated.
5. Neighbour cell Accessibility Check if the neighbouring cells are having Accessibility issues, Refer to RRC Success Rate
troubleshooting module.
6. Walk Test
A. Pingpong HO
1. To identify Ping-Pong Handover, do walk test and check if Handovers are happening back n forth at same locations.
2. If both SMCs are strong (RSRP) then 1. Reduce power or 2. Physical optimization required.
3. If Macro interference causing this then increase power to make SMC dominant.
Copyright 2016 AIRSPAN NETWORKS INC.
HOSR Troubleshooting
4. else coordinate with Samsung Optimization to optimize the macro coverage
B. Coverage Gaps
1. Do walk test to identify if Handover failures are happening in poor coverage and bad SINR
2. Increase eNB power to coverage and check HOSR.
3. If power is at maximum, additional small cell planning is required.
10
11
100
Alarm Description
Severity
Critical
Probable Cause
Action
557
556
Loss of the S1AP SCTP connection to 1. Verify the extent of the alarms on the nearby nodes
a specific MME
2. Contact NOC for further advise
580
565
587
Wi-Fi Board
Connectivity
Major
579
eSON Server
connection Lost
Major
Server unreachable
Report to NOC
13
Alarm Description
570
Severity
Critical
Probable Cause
The node does not have a valid sync
source and remain in the OOS state
GM unreachable
Major
224
GPS Signal
Unacceptable
Minor
Minor
Action
No satellite detected
14
Yes
Yes
Actions to be taken :
b.
c.
d.
b.
No
Check
eNB
Reachabi
lity
Check
Routes in
CSS
No
Check
Power
No
Report to
concern
team
Yes
Check
Physical
connecti
vity
2. Power Failure:
a.
From CSS
Check
Netspan
Reachabil
ity
Yes
Take
necessary
actions
No
3. Backhaul Issue
Report to
NOC team
a.
b.
Check the physical connections between CSS to L2 Switch and L2 Switch to SMC e-NB. (Loose
connection check )
c.
Clean SFPs used at L2 Switch and SMC e-NB. (Dust /Moisture check )
d.
15
Channel OOS
Description The node is manageable but RF is not radiating
Probable Cause : Clock Issue, MME connectivity, PCI allocation failure
Impact : Services will be suspended
No
Actions to be taken :
1 . Clock Issue
Check
MME
Alarm
Yes
Check
PTP
Alarms
Report to IP
Team
Yes
No
Report to
NOC team
16
Actions to be taken :
1. Verify other nodes at the same site with the same MME connection if it has the same alarm
a. If it has same alarm report to IP team and check MME status
b. Otherwise, report to IP team to check:
i.
ii.
17
Actions to be taken :
1. Verify other nodes with the same SGW connection if it has the same alarm
a. If it has same alarm report to IP team and check SGW status
b. Otherwise, report to IP team to check :
i.
ii.
18
19
Actions to be taken :
1. Report to NOC for further advise
20
Actions to be taken :
1. Check Netspan status
2. Report to IP team to check connection to eSON server
21
PTP Degraded
stream
High PDV
(Event)
2.5 Min
Check Sky,
antenna no
obstruction
GPS Signal
Unacceptable
Node in Holdover
Node in Holdover
8 Hrs
Channel OOS
22
b.
If it is not Locked, check Grand Master or refer to PTP & GPS alarm chart
c.
Report to IP team
b.
c.
Check physical connectivity between eNB and GPS antenna (Moist, connector)
d.
23
24
Node in Holdover
Description Node has no valid clock source
Probable Cause : GM not reachable, High PDV
Impact : May lead to Holdover expire and probable service-affecting
Actions to be taken :
1. Verify additional alarms in Netspan like GPS SNR Low and Node PTP Grand Master Lost and events like
High PDV
2. Report to IP team to check connectivity to the GM.
3. If GPS problem, refer to the GPS SNR Low action item.
25
Actions to be taken :
1. Check additional alarms and events in Netspan
2. Report to NOC.
26
27
28
THANK YOU