RBS HARDWARE & Configuration
LTE Configuration Overview
RBS 6000 Series
Objectives of Chapter 1
After this chapter the participants will be able to:
1
Explain LTE L17 interfaces and the integration of RBS 6000
1.1 Describe the interfaces S1, X2 and Mul to an eNodeB in LTE L15
1.2 Identify the main differences between various RBS 6000 products, such
as RBS 6101, RBS 6102, RBS 6201, RBS 6202 and RBS 6601
1.3 Summarize the integration process of an RBS 6000 and differentiate
between the manual integration and auto integration procedures
1.4 Identify the tools that are used in the different steps of the integration
procedure
1.5 Explain what the Managed Object Model (MOM) is, why it is important
in configuration and where to find information about it
LTE Logical Interfaces
Core Network
Other Management Systems
MME
S/P GW
Mun
OSS-RC
Mul
S1
Mul
S1
S1
RBS
RBS
X2
X2
RBS
Uu
UE
Radio Access
Network
Uu
Network
Management
Environment
Verify active UEs in eNodeB
• There are multiple ways to verify traffic on an active cell.
• Command to check traffic on a single DU site
Ue print –admitted
For example:
TEST> ue print -admitted
Trying rbs's password from amos lookupAccount ... OK
170502-15:12:34 11.179.131.148 17.0e ERBS_NODE_MODEL_H_1_263 stopfile=/tmp/7844
$ ue print -admitted
CellId #UE:s #Bearers
1 38
73
2 21
44
3 54 109
$
•
Verify
active
UEs
in
eNodeB
Command to check traffic on a Cascaded DU site
lh mp ue print –admitted
•
TEST> lh mp ue print -admitted
•
•
•
•
•
•
•
•
•
•
170502-15:15:13 11.179.131.148 17.0e ERBS_NODE_MODEL_H_1_263 stopfile=/tmp/7844
Created following board-groups: all, allp, mp, bp, tu, coremp, ommp, scb, sxb, scx, sccpmp, et, etmfg,
etmfx, aal2ap, aal2ncc, aal2cpsrc, aal2rh, xp, rax, tx, ru, ru[0-6], gcpu.
>>> Type "bp" to view available board-groups and "bp <group>" to view group contents.
======================================================================================
=======
$ lhsh 000100 ue print -admitted
0001: CellId #UE:s #Bearers
0001: 1 31
61
0001: 2 20
43
0001: 3 61 125
======================================================================================
=======
$ lhsh 000200 ue print -admitted
0002: CellId #UE:s #Bearers
0002: 11
4
9
0002: 12 49
94
0002: 13 11
21
0002: 21 35
74
0002: 22 85 185
0002: 23 25
57
•
$
•
•
•
•
•
•
•
•
Verify Performance in eNodeB
TEST> pmr
170502-15:18:59 11.179.131.148 17.0e ERBS_NODE_MODEL_H_1_263
stopfile=/tmp/7844
.........
101) LTE Node Traffic Performance, Whole Period
102) LTE Node Traffic Performance, Hour by Hour
103) LTE Node Traffic Performance, ROP by ROP
104) LTE EUtranCell Traffic Performance, Whole Period
105) LTE EUtranCell Traffic Performance, Hour by Hour
106) LTE EUtranCell Traffic Performance, ROP by ROP
201) GigabitEthernet Tput in Mbps, Whole Period
202) GigabitEthernet Tput in Mbps, ROP by ROP
203) Sctp PacketLossRatio, Whole Period
204) Sctp PacketLossRatio, ROP by ROP
205) IpInterface Tput in Mbps, ROP by ROP
Verify Performance in eNodeB
•
•
•
103) LTE Node Traffic Performance, ROP by ROP
Report from 2017-05-02 21:15 UTC to 2017-05-02 22:14 UTC (4 ropfiles)
Node SW: CXP102051/27_R5B26 (L17B)
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
Date: 2017-05-02
Object Counter
21:15 21:30 21:45 22:00
Acc_AddedERabEstabFailRateDueToMultipleLicense
0 0 0 0
Acc_AddedERabEstabSuccRate
99.4 99.6 99.7 99.8
Acc_InitialERabEstabFailureRateDueToMultipleLicense
0 0 0 0
Acc_InitialERabEstabSuccRate
99.9 99.9 99.9 99.9
Acc_InitialErabSetupSuccRate
99.9 99.9 99.9 99.9
Acc_InitialUEContextEstabSuccRate
99.9 99.8 99.9 99.9
Acc_PagingDiscardRate
0 0 0 0
Acc_RandomAccessDecodingRate
32.4 45.8 40.3 42.7
Acc_RandomAccessMSG2Congestion
0 0 0 0
Acc_RrcConnSetupFailureRateDueToLackOfConnectedUsersLicense 0 0 0
Acc_RrcConnSetupRatioForEmergency
0 0 0 0
Acc_RrcConnSetupRatioForHighPrioAccess
0.1 0.1 0.1 0.2
Acc_RrcConnSetupRatioForMOData
55.1 55.0 53.4 54.2
Acc_RrcConnSetupRatioForMOSignalling
6.3 7.1 6.4 5.7
Acc_RrcConnSetupRatioForMobileTerminating
38.4 37.8 40.1 39.9
Acc_RrcConnSetupSuccRate
100.0 100 100.0 100.0
Acc_S1SigEstabSuccRate
100 100 100 100
0
•
Sector Power and power licenses
How to check status of Sectors
•
TEST> st sector
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
170502-15:52:26 11.179.131.148 17.0e ERBS_NODE_MODEL_H_1_263 stopfile=/tmp/7844
===================================================================================
Proxy Adm State Op. State MO
===================================================================================
2793
1 (ENABLED) ENodeBFunction=1,SectorCarrier=1
2794
1 (ENABLED) ENodeBFunction=1,SectorCarrier=2
2795
1 (ENABLED) ENodeBFunction=1,SectorCarrier=3
2796
1 (ENABLED) ENodeBFunction=1,SectorCarrier=4
2797
1 (ENABLED) ENodeBFunction=1,SectorCarrier=5
2798
1 (ENABLED) ENodeBFunction=1,SectorCarrier=6
2799
1 (ENABLED) ENodeBFunction=1,SectorCarrier=7
2800
1 (ENABLED) ENodeBFunction=1,SectorCarrier=8
2801
1 (ENABLED) ENodeBFunction=1,SectorCarrier=9
3157 1 (UNLOCKED) 1 (ENABLED) SectorEquipmentFunction=1
3158 1 (UNLOCKED) 1 (ENABLED) SectorEquipmentFunction=2
3159 1 (UNLOCKED) 1 (ENABLED) SectorEquipmentFunction=3
3160 1 (UNLOCKED) 1 (ENABLED) SectorEquipmentFunction=4
3161 1 (UNLOCKED) 1 (ENABLED) SectorEquipmentFunction=5
3162 1 (UNLOCKED) 1 (ENABLED) SectorEquipmentFunction=6
3163 1 (UNLOCKED) 1 (ENABLED) SectorEquipmentFunction=7
3164 1 (UNLOCKED) 1 (ENABLED) SectorEquipmentFunction=8
3165 1 (UNLOCKED) 1 (ENABLED) SectorEquipmentFunction=9
===================================================================================
Total: 18 MOs
Sector Power and power licenses
• How to check configured Sector power
• TEST> hget sector configuredMaxTxPower
• 170502-15:54:29 11.179.131.148 17.0e
ERBS_NODE_MODEL_H_1_263 stopfile=/tmp/7844
• .
• =======================================================
=======================================================
===
• MO
configuredMaxTxPower
• =======================================================
=======================================================
===
• SectorCarrier=1 120000
• SectorCarrier=2 120000
• SectorCarrier=3 120000
Sector Power and power licenses
• configuredMaxTxPower = 20000 { 0..10000000
}Maximum output power to be used in a SectorCarrier.
The output power is evenly distributed over antenna
connectors used for TX transmission allocated for the
SectorCarrier.
To prevent the cell from transmitting, it must be
locked.
Unit: 1 mW
Disturbances: Changing this attribute can affect traffic
Takes effect: Object unlocked
Precondition: Attribute can be set only when cell is
locked.
License Status & Features
• License Management:
• LTE basic functionality can be enhanced by
adding features and capacity. This is done by ordering and
installing licenses for SW features and Hardware Activation
Codes (HWAC) for HW capabilities.
• Operators order feature licenses and HWAC in bulk,
separately from ordering the RBS hardware. The licenses
are distributed through Operations Support System (OSS)
to each RBS by matching the fingerprint (unique logical
name) of the RBS with the fingerprint information in the
license keys
License Activation with OSS-RC
Activate Features
• A licensed feature requires correct license
• Steps:
• Find the MO instance of OptionalFeatureLicense that
controls the feature state. This is automatically created
when the license is installed. Find the MO instance for
each feature in the applicable feature description.
Capacity feature activation and deactivation is
performed in an MO instance
of CapacityFeatureLicense .
• Set the attribute featureState for the feature MO
instance to ACTIVATED.
Activate Features
• Example:
•
TEST> set Licensing=1,OptionalFeatureLicense=QuadAntUlPerfPkg
•
•
•
170502-17:04:55 11.179.131.148 17.0e ERBS_NODE_MODEL_H_1_263 stopfile=/tmp/3616
Set featureState on following 1 MOs ?
===========================================================================
========
29 SystemFunctions=1,Licensing=1,OptionalFeatureLicense=QuadAntUlPerfPkg
===========================================================================
========
Set featureState on 1 MOs. Are you Sure [y/n] ? y
•
•
•
•
•
•
•
•
•
featureState 1
===========================================================================
=================================
Id MO
featureState
Result
===========================================================================
=================================
29 Licensing=1,OptionalFeatureLicense=QuadAntUlPerfPkg
1
>>> Set.
===========================================================================
=================================
Total: 1 MOs attempted, 1 MOs set
Activate Features
• Verify Feature activation:
•
TEST> get Licensing=1,OptionalFeatureLicense=QuadAntUlPerfPkg featureState
•
170502-17:07:10 11.179.131.148 17.0e ERBS_NODE_MODEL_H_1_263
stopfile=/tmp/3616
===================================================================
==============================================
MO
Attribute
Value
===================================================================
==============================================
Licensing=1,OptionalFeatureLicense=QuadAntUlPerfPkg featureState 1
(ACTIVATED)
===================================================================
==============================================
Total: 1 MOs
•
•
•
•
•
•
DU (Digital Unit )
• The DU provides switching, traffic management,
timing, baseband processing, and radio interfacing.
• DUL 20 01
• DUS 31 01
• DUS 41 01
• DUS 41 02
Function Description
The DU has the following functions:
• Timing function
• Loadable software
• Downlink baseband processing
• Uplink baseband processing
• IP traffic management
• Radio interface
• Transmission handling
• Controlling power and climate of the RBS
Technical Data
RU (Radio Unit – Radio Network)
RRUS Overview
• The RRUS remotely extends the reach of the RBS by
up to 40 km. The RRUS is designed to be located
near the antenna. A fiber optic cable connects
the RRUS to the RBS main unit or an expanded
macro RBS.
RRUS Overview
Hardware Management Overview
• HARDWARE STATUS
•
TEST> st plug
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
170502-20:22:58 11.179.131.148 17.0e ERBS_NODE_MODEL_H_1_263 stopfile=/tmp/4588
===================================================================================
Proxy Adm State Op. State MO
===================================================================================
416 1 (UNLOCKED) 1 (ENABLED) Equipment=1,Subrack=1,Slot=1,PlugInUnit=1
523 1 (UNLOCKED) 1 (ENABLED) Equipment=1,Subrack=1,Slot=2,PlugInUnit=1
700 1 (UNLOCKED) 1 (ENABLED) Equipment=1,HwUnit=PDU-5,PlugInModule=5
732 1 (UNLOCKED) 1 (ENABLED) Equipment=1,AuxPlugInUnit=RRU-1
743 1 (UNLOCKED) 1 (ENABLED) Equipment=1,AuxPlugInUnit=RRU-2
754 1 (UNLOCKED) 1 (ENABLED) Equipment=1,AuxPlugInUnit=RRU-3
765 1 (UNLOCKED) 1 (ENABLED) Equipment=1,AuxPlugInUnit=RRU-4
784 1 (UNLOCKED) 1 (ENABLED) Equipment=1,AuxPlugInUnit=RRU-5
803 1 (UNLOCKED) 1 (ENABLED) Equipment=1,AuxPlugInUnit=RRU-6
822 1 (UNLOCKED) 1 (ENABLED) Equipment=1,AuxPlugInUnit=RRU-7
833 1 (UNLOCKED) 1 (ENABLED) Equipment=1,AuxPlugInUnit=RRU-8
844 1 (UNLOCKED) 1 (ENABLED) Equipment=1,AuxPlugInUnit=RRU-9
1034 1 (UNLOCKED) 1 (ENABLED) Equipment=1,AuxPlugInUnit=XMU03-1-7
===================================================================================
Total: 13 MOs
HARDWARE STATUS
•
TEST> st ret
•
•
•
•
•
•
•
•
•
•
•
•
•
•
•
170502-20:26:23 11.179.131.148 17.0e ERBS_NODE_MODEL_H_1_263 stopfile=/tmp/4588
===================================================================================
Proxy Adm State Op. State MO
===================================================================================
896
1 (ENABLED) Equipment=1,AntennaUnitGroup=1,AntennaNearUnit=1,RetSubUnit=1
898
1 (ENABLED) Equipment=1,AntennaUnitGroup=1,AntennaNearUnit=3,RetSubUnit=1
905
1 (ENABLED) Equipment=1,AntennaUnitGroup=2,AntennaNearUnit=1,RetSubUnit=1
907
1 (ENABLED) Equipment=1,AntennaUnitGroup=2,AntennaNearUnit=3,RetSubUnit=1
932
1 (ENABLED) Equipment=1,AntennaUnitGroup=3,AntennaNearUnit=1,RetSubUnit=1
934
1 (ENABLED) Equipment=1,AntennaUnitGroup=3,AntennaNearUnit=3,RetSubUnit=1
943
1 (ENABLED) Equipment=1,AntennaUnitGroup=4,AntennaNearUnit=1,RetSubUnit=1
952
1 (ENABLED) Equipment=1,AntennaUnitGroup=5,AntennaNearUnit=1,RetSubUnit=1
961
1 (ENABLED) Equipment=1,AntennaUnitGroup=6,AntennaNearUnit=1,RetSubUnit=1
===================================================================================
Total: 9 Mos
HARDWARE LOG
• Lgs:
•
•
•
•
•
•
•
•
•
•
•
•
•
•
2017-05-02 07:33:21 INFO
2017-05-02 07:33:21 INFO
L17B
2017-05-02 07:33:21 INFO
2017-05-02 07:33:54 INFO
2017-05-02 07:33:54 INFO
2017-05-02 07:34:59 INFO
2017-05-02 07:35:27 INFO
2017-05-02 07:37:25 INFO
2017-05-02 07:37:25 INFO
2017-05-02 07:37:27 INFO
(control_f15f)
2017-05-02 07:37:27 INFO
(int_tran_f15)
2017-05-02 07:37:27 INFO
(ip_tran_rbs_)
2017-05-02 07:37:28 INFO
2017-05-02 07:37:28 INFO
Active CIM ready.
Configuration Version = SU_CXP102051%27_R5B26_170502_0732
Set upgrade supervision timer to 3600 seconds
choseNodeId
No.of clients are:1
Set upgrade supervision timer to 5400 seconds
Set error escalation to Node Restart
Set upgrade supervision timer to 5400 seconds
Set error escalation to Node Restart
Program CXC1725790%12_R94F01 on PIU 0.1 stopped at upgrade
Program CXC1729125%11_R94F01 on PIU 0.1 stopped at upgrade
Program CXC1726201%24_R94F01 on PIU 0.1 stopped at upgrade
Set error escalation to default
Cancel upgrade supervision timer
LTE Fault Management Overview
• Fault Handling:
This function represents the lowest level of fault
management. It is performed close to the fault cause
location. Fault handling also monitors the system for
hardware, software, and configuration faults and
sends an alarm report if it detects a fault it cannot
automatically recover from, that is, manual
intervention by an operator is required. The fault
handling function also covers state handling.
LTE Fault Management Overview
• Alarm Handling:
• This function maintains a list of active
alarms.Alarms have states which means they are
first raised and then become active. When the fault
is repaired the alarm will be cleared and become
not active or ceased.
LTE Fault Management Overview
• ALARM LOGS:
• In LTE RAN, the operator can retrieve fault
management related information from the
following
different logs: RAN Alarm Log, NE Alarm Log
and NE FM Event Log.
• Command: lga
LTE Fault Management Overview
•
Automatic Recovery:
For faults where a recovery action
might resolve the issue, the RBS will automatically try and
recover from the fault before issuing an alarm. If recovery is
successful, no alarm will be generated.
The possible recovery actions include, but are not limited
to, the following actions:
• Restarting the DU
• Restarting the RU
• Resetting the baseband
• Resetting the CPRI link
• Locking or unlocking the cell
LTE L17 Operation
Fault Management in LTE RAN – High Level Overview
•
Explain the Fault Management Framework Model
•
Solve some common alarms by following Procedural Information using tools:
a)
OSS-RC (Operations Support System-Radio Core)
•
ALV (Alarm List Viewer)
•
ASV (Alarm Status Matrix)
b)
AMOS (Advanced Managed Object Scripting)
c)
EM (Element Manager)
•
Functions of the Command Line Interface (CLI) and Node Command Line Interface (NCLI)
•
Demonstrate basic RBS 6000 configuration procedures using OSS-RC and Element Manager
•
Describe the main steps in RBS 6000 integration
•
Note the different tools and procedures available for node configuration
•
Demonstrate configuration changes in an existing eNodeB using Element Manager and/or
OSS-RC and/or AMOS
30