Introduction_to_BB5216_PA1.pptx..........

Introduction
to Gen2 (BB5216)
Mohan Gopalakrishnan
GCD Australia

Ericsson Internal | Mohan Gopalakrishnan | Page 2
› Product Highlights
› Operational Changes
› Troubleshooting
› Integration Overview
agenda

› Gen2 nodes are referred to as
– Baseband nodes
– Radio Nodes
– MSRBS_v2
– DUS52
– COM
– RCS
› Baseband 521x refers to G2 RBSs
› Baseband R refers to XMUs (R503)
› Baseband T refers to TCUs (T503)
Many names, one hw

Why this change
• Growth in Mobile
Network subscription
• Increase in Mobile
Network Traffic
(Especially data)
• Current system
incapable of handling
future demand

Why this change
• Future demand will be met through combination of technologies
• Customer expectation is to have one way of managing all
Access technologies (Uniformity, Ease of use, Energy
efficiency)

Gen2 MSRBS
Architecture

› New MP
– ARM Based
– Multi cores (8-12)
› Ethernet instead of sRIO
› New Cooling
› More Powerful EMCAs
– More DRBs
– More SEs/TTI
– Increased Antenna Bandwidth
– Higher Throughput
– More cells
– More users
Hw highlights

› 12 cores
› More powerful baseband processing
› 4000 Connected Users (up to 12000)
› Up to 1000 VOIP users with RoHC
› Max. 13000 DRBs across all UEs per eNB
› 48 SEs / TTI / DU - UL and DL
› 12 SEs/ TTI / Sector - UL and DL
› 600 Mbps Max throughput DL (Up to 1.6Gbps)
› 250 Mbps Max throughput UL (Up to 800Mbps)
› Pooled Antenna Bandwidths of up to 2.4 GHz
L16A Bb5216 specs

Interface name Connector Comment
Power ET20 No change
EC bus RJ-45 No change
LMT RJ-45 No change
TN A RJ-45 1 Gbps Electrical Ethernet
IDL A, B Xcede New connector, CPRI & Ethernet
RI A-F SFP+ 2,5 Gbps, 5Gbps and 10 Gbps
TN B, C SFP+ 1/10 Gbps Electrical/Optical Ethernet
SYNC RJ-45 New name
interfaces

CPP architecture
CPP is a complete platform
Provides functionality for the Operating System, O&M, Equipment,
Transport and Signalling

› Introducing Multi Standard SW
– Divided into CAT and RAT parts
– Support for large configuration nodes
› OAM redesigned
– One Node concept (3 x RATs)
– New MOM (ECIM)
– New Northbound Interface (COM)
› RBS Control System (RCS)
– Linux Based, which allows easier 3PP SWs
› New Transport (TN) SW
› New BB & Traffic Control SW for WCDMA & GSM
Sw Architecture &
highlights

The cats and the rats

Functional module
differences

New CPI structure
New folder “LTE” will be added below
LTE Radio Access Network Products
LTE
L15B
LTE L15B DU
LTE L15B Baseband
New library for Baseband nodes

› A number of ports have changed position on the board
compared to earlier boards. These interfaces are:
– Power
– SYNC (previously GPS)
– TN A, TN B and TN C
– RI A – F
– IDL A and IDL B (new interface)
› Due to this, new cable lengths are sometimes needed
when upgrading from old boards to Baseband 5216.
– Example: Power and EC bus cables in RBS 6601 MU
– All cable lengths per RBS type can be found in CPI
HW changes – port
positions

DUS 31/41 – Baseband
5216
P
o
w
e
r
S
Y
N
C
R
I
E
C
b
u
s
T
N
A
I
D
L
T
N
B
&
C
R
I
I
D
L
M
M
I
M
M
I
T
N
B
&
C
P
o
w
e
r
G
P
S
T
N
A
E
C
b
u
s

› New O&M interface compared to DU based
RBSs
› The new O&M interface is part of a new
Ericsson strategy for O&M and has already
been implemented for Baseband-T, the Pico
RBS and other non-RAN nodes
› OSS-RC “hides” the new interfaces which
gives a similar way of working compared to DU
based RBSes
› The MOM structure is partly changed
Changes oam
ME
SF
T
E
F

Changes - OAM
› New North bound Interfaces between
OSS and the Baseband 5216 based node:
– NETCONF (for MO management)
– ECLI (Ericsson CLI) (for MO management)
– SNMP (for alarms)
– HTTPS (for web pages)
– SFTP (for fetching logs, UP, ROP files)
› New Managed Object Model (MOM) based on
Ericsson Common Information Model (ECIM)
› CORBA interfaces removed

› Platform independent model used by all Ericsson Nodes
› Has MO fragments that are common on all Ericsson nodes
like SwM, PM, FM, backup, Licenses etc
ECIM (Ericsson Common
information model)

› ECIM compliant
› The XML MOM in G1 is represented in ONE MOM file
› MOM for BB5216 is split into many fragments – MOM
fragment per functional area (PM, FM, Transport etc)
› Moshell combines all the mom fragments and creates one
single MOM file
› Moshell stores MOM fragments at
› ~/jarxml/momfragments/
› pv momparts
› pv momfile
› prm MO gives MOM fragment the MO belongs to
Managed Object
Model

Mom Structure

DU Based nodes - CPP
based MOM
ManagedElement
IpSystem
ENodeBFunction
EquipmentSupport-
Function
MceFunction
NodeManagement-
Function
Equipment
TransportNetwork
Common fragments for all CPP based nodes
Node specific fragments
IpOam
ManagedElement-
Data
ResourceAllocation-
Function
SectorEquipment-
Function
SupportSystem-
Configuration
SwManagement
SystemFunctions

Baseband nodes - ECIM
based MOM
ManagedElement
SystemFunctions
ENodeBFunction
NodeBFunction
BtsFunction
NodeSupport
Pm
Fm
SwM
Transport
Common fragments for all ECIM based nodes
Node specific fragments
Equipment
…
SectorEquipment-
Function

› Simplified MOM handling by introduction of
FieldReplacableUnit MO
› Replaces
– PlugInUnit
– AuxPlugInUnit
– HwUnit
Equipment Handling

“Unit” MOM DUS41/31
PlugInUnit
DeviceGroup
AuxPlugInUnit
DeviceGroup
DU RU
PiuType PiuType
XpProgram
AuxPlugInUnit
DeviceGroup
XMU
PiuType
XpProgram
HwUnit
APC Unit
PiuType
317 Equipment=1,Subrack=1,Slot=1,PlugInUnit=1
455 Equipment=1,RbsSubrack=1,RbsSlot=3,AuxPlugInUnit=RU-1-3
466 Equipment=1,RbsSubrack=1,RbsSlot=4,AuxPlugInUnit=RU-1-4
481 Equipment=1,AuxPlugInUnit=RRU-1

“Unit” MOM Baseband 5216
FieldReplaceableUnit
DU RU
FieldReplaceableUnit FieldReplaceableUnit
XMU
FieldReplaceableUnit
“APC Unit”
231 Equipment=1,FieldReplaceableUnit=DU-1
241 Equipment=1,FieldReplaceableUnit=RRU-1
271 Equipment=1,FieldReplaceableUnit=SUP-1

Backup handling
› For baseband nodes a backup is called
BackUp (for DU based nodes a backup
is called ConfigurationVersion (CV))
› Data base handling changed:
– Baseband nodes: the data base is always
stored persistently on a disk
– DU based nodes: the data base is only stored
on RAM; a CV stores a snapshot of the data
base on a disk persistently
› Since the data is always stored on a disk
no configuration is lost at restart
The data base is always
stored persistently

Performance
Management
› The way of working with PM counters and PM events in
OSS is the same as before.
› LTE specific counters are the same but TN counters are
changed
› Definition of counters are not MO attributes starting by
pm but are now MO instances of MO MeasurementType
› PM Events for Cell Trace are now visible in the MIB
› The format of the ROP file has changed to comply to
later 3GPP release (Rel 10.0)
› New ECLI command, “show-counters” to show real time
values of counters

› SNMP for Alarm Propogation
› Alarms are more specific
– Most alarms for a DU based node
are still used but new alarms
added
› All alarms now have the same
structure, e.g. HwFault is changed
to HW Fault
› Alarms and alarm handling are
visible in the MIB -> active alarms
can also be seen in AMOS and
EMCLI
FM - Alarm handling

Firewall
configuration
- AutoIntegration web GUI, see CPI “Integrate Node”
-Collection of ESI package, see CPI “Data Collection Guideline”
Baseband
AI Interface, Maintenance User, ESI
443/tcp HTTPS Yes Both Bi-directional
Amos/EMCLI command Line Interface using SSH
Dependency to SysM:CliSsh:port
ECLI, OM Configurable 2023/tcp SSH/2.0 Yes Server Ingress
Transfer of PM ROP-files to OSS PM, ROP-files 2024/tcp SFTP Yes Server Ingress
Ericsson Support, COLI commands ESCI 4192/tcp SSH/2.0 Yes Server Ingress
Amos/EMCLI command Line Interface using TLS ECLI 9830/tcp TLS/tls-1.2 Yes Server Ingress
Ericsson support, Amos/EMCLI command Line Interface using TLS ESCI 9831/tcp TLS/tls-1.2 Yes Server Ingress
Ericsson Support, L1-L2 traces Ericsson troubleshooting 33079/udp - Yes Server Egress
Ericsson Support, Ericsson troubleshooting CPM traces Ericsson troubleshooting 5342/tcp - Yes Client Bi-directional
Ericsson Support, Ericsson troubleshooting CPM traces Ericsson troubleshooting 5343/tcp - Yes Client Bi-directional
EMCLI file transfer, e.g. ESI-package, logfiles etc. EMCLI, Windows-client callback 10001/tcp Egress

› OAM Security is not an optional component
– No option to switch security levels (unlike SL3)
› Secure certificate based OAM communication protocols
(TLS)
› Single logon, personal user accounts, centralized
authentication and authorization
› No default user preinstalled (No rbs/rbs)
› Telnet, ftp no longer used
› Vendor creds ensures genuine HW
› Signed Sw ensures genuine SW
› No access to OS, OS prompt and file system
– Hardware rooted secure boot, Signed SW, No access CMD line
access to OS – Cannot access eNB logs like alarm, system logs!
OAM security

› LDAP used for user look up and authentication
– LDAP over TLS and SSH supported. TLS recommended
› Role Based (RBAC) and Target Based Access Control
(TBAC)for shell commands and Managed Object Classes
› Default Roles and corresponding rules available in the eNB
› Ability to customize roles
Oam security-User
management
OSS
A B C
Baseband

› Concept of Maintenance User for Standalone mode
operation – E.g: LDAP is unavailable
The first Maintenance user (MU) has to be defined at
Integration
› Subsequent MUs can be defined any time
› Light-weight passwords not accepted
– Shortest password length is 12
– Minimum lower case characters: 3
– Minimum upper case characters: 3
– Minimum numeric characters: 2
– Minimum special characters: 1
Maintenance user
OSS

Online security
enrollment

Online security
enrollment
OSS Infra
LDAP RA
OMSAS
(Certificate Server)
VC
VC
NeCA
MSCA
DsDA
OminfRootCA
MSRootCA
RACSA
VC used to
identify
Ericsson
node
OSS LDAP
Enrollment parameter
sent to G2
Using Enrollment
parameter, eNB
connects to OSS
RA
RA Authentication
OSS
Trust certificates
transferred to eNB

Real time Security Event
Logging
FAJ 121 3027, R1 Optional
› Introduction of security log events to enable:
– Triage of security breaches
– “Application of counter measures” to stop threats in progress
– Audit trails
› In combination with the remote system log gives the operator the
capability to in real time send security events to a centralized syslog-
server
Security
Log
Server
:
Analysis

› Element Manager and CabViewer don’t exist for G2 nodes
› Two new tools: EM-CLI and EM-GUI
› EM-CLI uses the same base as Amos
– Access to MOs
– Execute Scripts
– Restricted access to COLI shell
› EM-GUI currently targeting 16B
› SMO replaced by SHM
› Moshell: Use the latest Moshell version (or at least
versions 11.0n and above)
tools

Two new element
managers
RBS Element Manager and Cabinet Viewer are not applicable
for Baseband 5216 based nodes. Instead two new EM tools
are introduced.
EMCLI: uses the same base as
AMOS; works in L15B
EM GUI: shows a graphical view
of the node; Currently planned for
L16B?

EMCLI
Viewing the MIB
Viewing MO attributes
• EMCLI ~ AMOS for DU based nodes,
except that batch does not work (since it is
an EM tool)
• About 85-90% of the RBS commands in
AMOS for DU based nodes works in EMCLI
• Scripts can be run in the same way as in
AMOS
• Ericsson CLI (ECLI) a “mode” in EMCLI
that operates on the model. Also some
specific commands mainly for TN

EMCLI opened from OSS

EMCLI opened from PC
(on site)

Logging in via moshell
› Moshell <node IP>
› Moshell will automatically detect the node type (CPP / RCS
/ Pico / etc) and use appropriate ports
› For COM nodes, moshell will by default access the MO
interface via COMCLI over SSH
– Option to use COMCLI over TLS too
› To change access method
› Moshell –v comcli=<value>,username=x,password=y
<node IP>
#-------------------------------------------------------------------------------
# COMCLI special values.
#
# VALUE NODE TYPE
# comcli=10 pico commercial
# comcli=11 pico RnD
# comcli=12 NetSim and APG43L 1.x
# comcli=13 pico commercial via netconf
# comcli=20 g2 commercial via COMCLI/SSH
# comcli=21 g2 RnD via COMCLI/SSH
# comcli=22 g2 RCSsim via COMCLI/SSH
# comcli=23 g2 commercial via netconf/SSH
# comcli=24 g2 RnD via netconf/SSH
# comcli=25 g2 via comcli/TLS + sam.p12
# comcli=26 g2 via comcli/TLS + pemfiles
# comcli=27 g2 via comcli/TLS + ssucredentials
# comcli=28 g2 via comcli/SSH+TLS with connection menu
# comcli=30 NetSim
# comcli=31 BSP
# comcli=32 PGM
# comcli=33 Nestim via netconf
# comcli=34 APG43L 2.x
# comcli=35 EPG/SSR

mOSHELL
› Most moshell commands from G1 works on G2
– get, set, acc, bl, deb, st, pget…
› Changes to COLI commands
› New commands to collect ESI logs – Ericsson Support
Information

› Same tracing principles from G1 for MP tracing
› Target Monitor (tm) replaced by Trace Session (ts)
– mon command used to activate ts
– Firewall Ports 5342(Control) and 5343 (Data) need to be opened up
› Much larger MP T&E buffer
– 6MB / 12 Cores
› Much larger EMCA buffer size
– 4 * 10MB
› fte command not yet available
– mon? command lists active traces too
tracing

› GCPUs are referred to as EMCAs
› bbte listagents lists the available EMCAs
› bbte status bbEqm000004 | egrep -i random_access
› bbte log enable bbEqm000004 UpcUlCellCeFt_RANDOM_ACCESS
› bbte log disable bbEqm000004 UpcUlCellCeFt_RANDOM_ACCESS
› bbte log read bbEqm000004 G2
- EMCA buffer: 4*10MB (4*100K B in G1)
› Use bbte command to get a list of all available options
› Same mechanism to activate mtd commands
Baseband (EMCA)
tracing

› No access to enb logs on the disc – No access to file
system
› Moshell exports the moshell server for processing
› Port Range 10001 used to export logs to the server
› Incorrect Firewall config in Telstra’s current config
› Use export_method=1 as a workaround
– export to the existing SFTP server running on port 22 on the
moshell workstation
› Username and password for the server to be specified
– User variables export_username, export_password
Enb Logs

› llog –l to list restarts
› COLI command dump lists the PMDs on the node
› Not possible to fetch PMDs from node via sftp
– Dumps at /rcs/dumps
› DCGm includes PMDs
› Decoder at:
– https://plf-pmda.rnd.ki.sw.ericsson.se/
CRASH analysis

› Ping is a COMCLI action on the Router MO
– Transport=1,Router=LTE
– Transport=1,Router=vr_OAM
› mcc router=<> ping <IP> -c <n>
connectivity

› Restarts - Action on the FRU that defines the DU
› Sw Upgrade
– Action on MO: Swm to create upgrade package
– Action on Upgrade package to Prepare (Install), Activate
(rebootnodeupgrade) and Confirm (Confirm Upgrade)
› License Key Install
– Action on MO: KeyFileManagement
› License Install can be performed from OSS via SHM
– COLI based LKF install
› Sync MO replaced with:
– Transport=1,Synchronization=1,RadioEquipmentClock=1
› RadioEquipmentClock=1,RadioEquipmentClockReference=1
›
Misc

› HW and SW is prepared for AutoIntegration
› BSIM in OSS-RC is not ready for Baseband 5216/5212
› So, partly manual process is needed in L15B and L16A,
when using OSS-RC
AUTO INTEGRATION

Integration overview
RBS Summary
Site Basic
Site Equipment
TN
RN
Post Install

Migration procedure
Prereqs
in place
Perform
preparations All preps
ready
Change
HW
Power
On
SW and
On Site
integration
OAM
connection
RN, TN
integration
using OSS-RC
Integration
completed
Product
verification

› OAM Introductory Module for BB5216
› LTE Service Delivery Information
› LTE L16A Baseband CPI
› Online Security Enrollment – G2RBS
› G2 Troubleshooting Wiki
› G2 DCGm
references

Introduction_to_BB5216_PA1.pptx..........

Introduction_to_BB5216_PA1.pptx..........

Recommended

Recommended

More Related Content

Similar to Introduction_to_BB5216_PA1.pptx..........

Similar to Introduction_to_BB5216_PA1.pptx.......... (20)

Recently uploaded

Recently uploaded (20)

Introduction_to_BB5216_PA1.pptx..........

Editor's Notes