VODAFONE IN-HOUSE

ACADEMY

BY
MOHAMED IBRAHIM YOUSSIF
2
Wo r l d ’ s b e s t
Baseband
made better

1- BASEBAND G2
INTRODUCTION
 BASEBAND G2
INTRODUCTION
c o n t e n t s

•Baseband product capability introduction

•Baseband Function
•Baseband Technical Data
•Baseband Interfaces
BASEBAND 5212
HARDWARE CAPABILITIES
› WCDMA HW prepared
– 576 CE Downlink & 576 CE Uplink
– 960 CE EUL Uplink*
– 384 HSDPA & 384 EUL users
– 252 Mbps Downlink & 92 Mbps Uplink
– Up to 12 cell carriers / 180 HSDPA codes
› Single BB pool, perfect pooling of CE

› WCDMA HW capabilities W16A

– 576 CE Downlink & 384 CE Uplink
– 960 CE EUL Uplink*
– 384 HSDPA & 384 EUL users
– Up to 6 cell carriers / 90 HSDPA codes

› WCDMA HW capabilities W16B

– 576 CE Downlink & 384 CE Uplink
– 960 CE EUL Uplink*
– 384 HSDPA & 384 EUL users
– Up to 12 cell carriers / 180 HSDPA codes
› Single BB pool, perfect pooling of CE
BASEBAND 5216
HARDWARE CAPABILITIES
› WCDMA HW prepared
– 1152 CE Downlink & 1152 CE Uplink
– 1920 CE EUL Uplink*
– 768 HSDPA & 768 EUL users
– 336 Mbps Downlink & 138 Mbps Uplink
– Up to 24 cell carriers / 360 HSDPA codes
› Single BB pool, perfect pooling of CE

› WCDMA HW capabilities W16A

– 1152 CE Downlink & 768 CE Uplink
– 1920 CE EUL Uplink*
– 768 HSDPA & 384 EUL users
– Up to 6 cell carriers / 90 HSDPA codes

› WCDMA HW capabilities W16B

– 1152 CE Downlink & 768 CE Uplink
– 1920 CE EUL Uplink*
– 768 HSDPA & 384 EUL users
– Up to 12 cell carriers / 180 HSDPA codes
› Single BB pool, perfect pooling of CE
BASEBAND 5216
FUTURE MIXED MODE CAPABILITIES*
› WCDMA + LTE
– 576 CE Downlink & 576 CE Uplink
– 960 CE EUL Uplink
– 384 HSDPA & 384 EUL users
– 252 Mbps Downlink & 92 Mbps Uplink
– Up to 12 cell carriers / 180 HSDPA
codes
› Single BB pool, perfect pooling of CE

› WCDMA + GSM
– 576 CE Downlink & 576 CE Uplink
– 960 CE EUL Uplink
– 384 HSDPA & 384 EUL users
– 252 Mbps Downlink & 92 Mbps Uplink
– Up to 12 cell carriers / 180 HSDPA
codes
› Single BB pool, perfect pooling of CE

First mixed mode

in W16B
7
HW SUPPORT ASPECTS
› Baseband 5212 and 5216 cannot IDL

interconnect with DUW

– Will be treated as different logical RBS
› Dual Baseband 5212 and/or 5216 is not
planned to be supported supported in
W16A/B
– Will be supported in later releases

› Baseband 5212/5216 and DUW will support RRUS 12

connections towards same radio running

mixed mode configuration

› Baseband 5216 and 5212 fully supports multi- RRUW 01

standard radio units CPRI

Single standard radio units RUW/RRUW cannot be supported

BASEBAND 5216 FUNCTION

9
BASEBAND 5216 TECHNICAL DATA

10
BASEBAND 5216 INTERFACES

11
SUPPORTED BROWSERS

12
2
Wo r l d ’ s b e s t
Baseband
made better

2- BASEBAND5216
INTEGRATION
PRE-REQUISITE

Category Item Format Comment

Netconf RbsSummary File Netconf (xml)
(XML)
Script SiteBasic Template Netconf (xml)
SiteEquipment Template Netconf (xml)
TN Template Netconf (xml)
RN Template Netconf (xml)
MOS Feature Activation Script Moshell (.mos)
Script
Post Integration Script Moshell (.mos)
Cell Relation Script Moshell (.mos)
UP Upgrade Package (UP) ZIP
LKF License Key File (LKF) XML
PC Client PC
Cable Ethernet Cable Baseband LMT - PC
PRE-REQUISITE

• Baseband5216 should be installed in RBS6601 and should be power on.

• Scripts prepared and stored in Client PC

• SFTP Server installed in Client PC

• Moshell for latest version

1. CLIENT PC SETUP (1)

• Client PC connects to Baseband5216 LMT port

• Set Client PC IP address

- IP Address : 169.254.2.1
- Subnet mask : 255.255.0.0
- Default gateway : 169.254.2.2

• Stop Symantec Management

Client Service
(Services -> Symantec Management
Client and Press stop) and set
“Out of Ericsson premises”
1. CLIENT PC SETUP (2)

• Client PC SFTP Server Setting

- IP Address : 169.254.2.1
- Username : rbs
- Password : rbs

• Save integration files (XML, UP, MOS) to SFTP HOME Directory

• Turn on SFTP Server

- Recommended SFTP application : FreeFtpd
2. AUTO-INTEGRATION (PRECHECK)

• Check following from “xxx_RbsSummaryFile.xml” XML script

<summary:AutoIntegrationRbsSummaryFile
xmlns:summary=http://www.ericsson.se/RbsSummaryFileSchema
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance
xsi:schemaLocation="http://www.ericsson.se/RbsSummaryFileSchemaSummaryFile.xsd">
<Format revision="F"/>
Same with XML script
<ConfigurationFiles
In SFTP server
siteBasicFilePath="1_eNB11_SiteBasic.xml“
Same with License
siteEquipmentFilePath="2_eNB11_SiteEquipment_RBS6601.xml"
In SFTP server
licensingKeyFilePath="SKT_DVT_eNB11_BD2_BB5216_150910_061816.xml“
upgradePackageFilePath="CXP9024418_2-R1YV.zip“
initialSecurityConfigurationFilePath="%ForIPsec_path, not supported yet%"/>
</summary:AutoIntegrationRbsSummaryFile> Same with UPG in SFPT
2. AUTO-INTEGRATION (PRECHECK)

• Sometimes UP PKG is zipped twice, in case this UP should unzip once and
save in SFTP HOME folder. Otherwise auto integration will stop.

• Note that in this case, UP file name might be different from what in
“RBSSummary.xml” should change it according to “RBSSummary.xml”
2. AUTO-INTEGRATION (1)

• Auto-Integration Tool Page

- Tool Web Page : https://169.254.2.2

• Host : 169.254.2.1
• Username : rbs
• Password : rbs
• Site Installation File :
/<File_Name>
2. AUTO-INTEGRATION (1)

• Put in integration information for SFTP server and Site Installation file

Same with Client

PC SFTP
Server setting

Same with SFTP Site

Installation File name

After put in above

information, DOWNLOAD
button will be activated
2. AUTO-INTEGRATION (2)

• Click “Download Files” UP Download> Filesystem Preparation> UP unpack and

Installation shows in “AutoIntegration log” Box

SW Package Download
success (Finished)

Prepare Filesystem
success (Finished)

Unpack and Install SW

success (Successful)
2. AUTO-INTEGRATION (2)

• After UP Installation, shows “Download Completed” message in the

Auto-Integration log. “Integrate” button is activated and click it to
integrate

CLICK
2. AUTO-INTEGRATION (2)

• After press “Integrate” button Node will Restart and start integrate
Configuration File
• In case error happens during integration, integration should be
stopped and board will restore to factory setting.
• If integration finishes with no error no progress message in Auto-
Integration Log
• Wait until TN port LED is ON and access node with moshell to run
scripts.
2. AUTO-INTEGRATION (2)

• After Auto-Integration finishes, logon with moshell. Need to put in

“Username/Password” after “lt all”
Maintenance User Id/Password: “rbs/rbs”

Type rbs/rbs
3. RUN TN/RN SCRIPT

• Open an Terminal and run following TN/RN script running commands

• File path should be put in correctly.
ssh -o PubKeyAuthentication=no -o UserKnownHostsFile=/dev/null -o ForwardX11=no -p 830
[email protected] –s <TN XML Script File Name>
ssh -o PubKeyAuthentication=no -o UserKnownHostsFile=/dev/null -o ForwardX11=no -p 830
[email protected] –s <RN XML Script File Name>

• Command Example
ssh -o PubKeyAuthentication=no -o UserKnownHostsFile=/dev/null -o ForwardX11=no -p 830
[email protected] -s netconf < 3_eNB12_TN_netconfv2.xml
ssh -o PubKeyAuthentication=no -o UserKnownHostsFile=/dev/null -o ForwardX11=no -p 830
[email protected] -s netconf < 4_eNB12_RBS6601_RN_netconfv2.xml

Contact DT responsible in case error happens with script running.

4. RUN POST INTEGRATION SCRIPT

• Logon with moshell and run Post Integration Script

• Run script with following command
run <script_name>

• Run script example

run 5_featureActivation.mos
run 6_PostIntegration.mos
run 7_eutranfreq.mos

• After script running, “lt all” to load new configuration and save CV
cvmk <cv_name>
or
cvmk <cv_name> or acc BrM=1,BrmBackupManager=1
acc BrM=1,BrmBackupManager=1 createBackup createBackup
5. POST-CHECK

• After save CV, Node Cold Restart

acc FieldReplaceableUnit=1 restartUnit

• After node is up, check following with moshell

- Unlock TermPointToMME, EUtranCellFDD
- MME, EUtranCellFDD, Sector, SectorCarrier, Radio Unit Status
- “inv” to check License Status
- Node configuration parameter and System Constant Status
- Alarm Status
- Save CV
2
Wo r l d ’ s b e s t
Baseband
made better

3- BACKUP & RESTORE

BASEBAND
TOOLS & LAPTOP PREPARATION

› Ethernet cable (Pin Assignment: Straight)

› at least Java Runtime Environment (JRE) 6. You may therefore need to install
the latest update of the JRE. You can download one from Oracle's Java web
site.

› Cygwin & EMCLI

› SFTP

› Summary file for restore and exported backup for affected Baseband

› Baseband Software package

› Turn off all security accounts , security centers and Firewall on your PC

Baseband Restore | Ericsson Internal | prepared by Ahmed Eltarbany | 2016-09-24 | Page 30

CYGWIN & EMCLI INSTALLATION

› Cygwin Installation:
› Unzip "cygwinBin4Emcli.zip"
› Execute the setup-X86.exe file (32-bit installation).
› Choose "Install from Local Directory", then click Next.
› Root Directory "C:/cygwin" (It is not allowed to choose a different directory, especially if
it contains spaces). If prompted for "Default Text File Type", choose UNIX (not DOS).
Then click Next.
› Select Local Package Directory: "cygwin_emcli_x.x.x" (x.x.x: cygwin version). Then
click Next.
› Select Packages: Add the following packages: - under "Archive", select "zip" and
"unzip"
- under "Net", select "inetutils", "openssh", "openssl"
- under "Perl", select "perl" and "perl-XML-Simple"
- under "Libs", select "liblzma5", "libglib2.0_0" and "libuuid1"
- under "Tcl", select "expect"
- under "Shells", select "rxvt VT102"
› Click Next and installation of Cygwin will start. Wait for the installation to
complete.
› Open a Cygwin terminal window by double-clicking on the Cygwin icon in the start
menu or on the file c:/cygwin/cygwin.bat. The window should be black with white text
and the prompt should like this: [~]$ If not, then go through all the steps again and
make sure you haven't missed out anything. The Cygwin terminal window can then be
closed.

Baseband Restore | Ericsson Internal | prepared by Ahmed Eltarbany | 2016-09-24 | Page 31

CYGWIN & EMCLI INSTALLATION

› EMCLI Installation:

› Click on em_install.exe and then run it in order to install the Element

Management Launcher

› After completed installation, EMCLI is available by starting Element

Management Launcher from the Windows Start menu or a desktop short-
cut.

Baseband Restore | Ericsson Internal | prepared by Ahmed Eltarbany | 2016-09-24 | Page 32

SFTP PREPARATION

Create Folder named BB on partition C and use below settings

Password :
rbs

Baseband Restore | Ericsson Internal | prepared by Ahmed Eltarbany | 2016-09-24 | Page 33

RESTORE & BACKUP SCENARIOS

› Scenario1
› HW issue and BB replacement is a must
› Node connected to OSS and accessible by AMOS , Backup exported
remotely
› Backup to be sent to Field engineer onsite
› Field engineer to load exported backup (using Web interface to BB5216 ,
backup file , restoreSummaryFile , SW package)
› Scenario2
› Lost remote connection to BB5216 but local access is guaranteed
› Field engineer to export backup from BB5216 via EMCLI
› Field engineer to load exported backup (using Web interface to
BB5216 , backup file , restoreSummaryFile , SW package)

Baseband Restore | Ericsson Internal | prepared by Ahmed Eltarbany | 2016-09-24 | Page 34

EXPORT BACKUP FROM BASEBAND ONSITE

•› Connect Ethernet cable between LMT port in BB5216 and PC LAN cable
•› Set PC IP setting as below
• › IP: 169.254.2.3
• › Subnetmask: 255.255.0.0
• › Gateway: 169.254.2.2
•› Open EMCLI , insert IP address and click on EMCLI button

Baseband Restore | Ericsson Internal | prepared by Ahmed Eltarbany | 2016-09-24 | Page 35

EXPORT BACKUP FROM BASEBAND ONSITE

› Once EMCLI connect to baseband , enter command lt all and enter username: rbs and
password rbs
› Use command cvls to get last created backup with it’s number (BrmBackup=7 in below
example) , so you should extract this backup

Baseband Restore | Ericsson Internal | prepared by Ahmed Eltarbany | 2016-09-24 | Page 36

EXPORT BACKUP FROM BASEBAND ONSITE

› Make export action as shown below using password : rbs

› Backup will be extracted to path C:/BB which configured on SFTP

Baseband Restore | Ericsson Internal | prepared by Ahmed Eltarbany | 2016-09-24 | Page 37

LOAD BACKUP TO NEW BASEBAND

› path C:/BB should have below

› RBSSummaryRestoreFile.xml
› Baseband SW package ( ex: Baseband_SW_Upgrade_Package_16B_R13FT.zip)
- Note: you must use the same SW level on the old BB to be compatible with
exported backup)
› Exported backup ( ex :
Final_backup_for_Baseband_CXP9024418_4_R13FT_20160904T152437+0000
_RBS0695_RadioNode_20160921T212820+0000.zip)

› Connect to new Baseband

› Open internet explorer and type (https://169.254.2.2)
› Insert below data
› Host IP : 169.254.2.3
› username: rbs
› password: rbs
› site installation file : RBSSummaryRestoreFile.xml

› Press Download and after receiving message Download completed press integrate ad
wait 10 minutes then try logging using EMCLI and ea access webpage

Baseband Restore | Ericsson Internal | prepared by Ahmed Eltarbany | 2016-09-24 | Page 38

LOAD BACKUP TO NEW BASEBAND

2 4

3
Baseband Restore | Ericsson Internal | prepared by Ahmed Eltarbany | 2016-09-24 | Page 39
CHECK BASEBAND STATUS AFTER BACKUP
RESTORATION

• Open internet explorer and use Url : https://169.254.2.2/ea.html

• Check that node status is Working
• Open EMCLI and use cvls to check that backup restored

Baseband Restore | Ericsson Internal | prepared by Ahmed Eltarbany | 2016-09-24 | Page 40

2
Wo r l d ’ s b e s t
Baseband
made better

4- BASEBAND MODEL
INSTALLATION
ERICSSON MODEL (LAUNCH PHASE 1, NO IMPACT ON 3G
CAPACITY )
Current High Capacity “384+ HS Users” (M1) High Capacity upgrade (M2)

210 210 210 210 210 210 180

0 0 900 0 0 900 0 0 900
RR 0
RR RR RR RR RR RR RR RR
US0 US0 U RR
US0 US0 U US0 US0 U
1 1 1 1 1 1 U

L1800
L2100
introduction /
introduction
4th sector

CPRI
MUX

DUW DUG900
DUW DUG900 DUW DUG900 5216
5216 (UMTS (GSM
(GSM (LTE)
(UMTS (GSM (LTE) (UMTS
Only) Only)
Only) Only) Only) Only)

DUW DUG1800
DUW (UMTS (GSM Only)
(UMTS Only)
Only)
Notes: Notes:
1. This model will be used in LTE rollout phase 1 1. 4th sector and L1800 upgrade
2. For 4 sector site, LTE will be activated on 3 sectors only 2. CPRI MUX, CPRI cables will be added
th

3. U2100 will be configured on Primary DUW41 , U900 on

secondary DUW

42
ERICSSON MODEL (2ND PHASE, SITES WITH LESS THAN 384 USERS)
Current Medium Capacity (M3) Medium Capacity upgrade
(M4) 210 210 180
210 210 210 210
900 0 0 0 900
0 0 900 0 0
RR RR RR RR RR RR RR
RR RR RR US0 US0 US1 U
US0 US0
US0 US0 U
U 1 1 1 1 2
1 1
L1800
L2100
introduction
introduction
+ 4th sector

CPRI
MUX

5216 DUW DUG900

DUW DUG900 DUW (Mixed Mode) (UMTS Only) (GSM Only)
5216 DUG900
(UMTS (GSM (Mixed (UMTS (GSM Only)
Only) Only) Mode) Only)

DUG1800
(GSM Only)
Notes: Notes:
1. This model will be used in LTE phase2 1. 4th sector sites, CPRI Mux is
2. 4th sector ready required
3. Configuration Complexity (cons)
4. W17A, OSS16B are needed

43
44
2
Wo r l d ’ s b e s t
Baseband
made better

5- BASEBAND KNOWLEDGE
SYSTEM FUNCTIONS

System Functions Description

BrM: Backup and restore Mgmt -Create, delete and restore backups on a ManagedElement.
-Export + import of backups in file format to/from a remote location

FM: Fault Mgmt -Fetch the set of alarm types supported by a ManagedElement
-Fetch the list of active alarms which are present on the ManagedElement at a given
point in time

HwInventory: Hardware Inventory Mgmt -Check which hardware items are present on a ManagedElement

LM: License Mgmt -Download and activate license key files

-Fetch an inventory of the licenses on a ManagedElement.

PM: Performance Mgmt -Determine the PM capabilities of the ManagedElement, for example
 Supported job types: Measurement Job (periodic collection), real time jobs or
threshold monitoring jobs
 System limits: max number of jobs or files or measurements
-Determine the set of counters (instances of PmGroup + MeasurementType)
supported
by the ManagedElement
-Configuration of PM jobs on the ManagedElement

PM EventM: PM Event Mgmt -Similar to PM except it covers event based PM

Baseband G2 Introduction | Ericsson Internal | 2015-12-03 | Page

46
SYSTEM FUNCTIONS

System Functions Description

SecM: Security Mgmt -Configuration of authentication and authorization methods and data used for verifying
user credentials and permissions.
- LDAP Authentication
- Local Authorization
 Retrieval of predefined user roles and the associated rules
 Configuration of custom user roles and the associated rules
-CertM: Certificate Mgmt
 Management of node credentials and trusted certificates

SwInventory: Software Inventory Mgmt -Check which software items are loaded on a ManagedElement and which of those
items are active

SwM: Software Mgmt -Download, activate and delete upgrade packages

SysM: System Mgmt -SNMP: SNMP Mgmt

-Configure the use of the SNMP protocol by the ManagedElement
-Configure NTP client association to remote NTP servers
-Find the schema files for ECIM MIM fragments supported by the ManagedElement
-OSS uses this to determine which MIM fragments + versions are supported by a
ManagedElement and to fetch the MIM files

Baseband G2 Introduction | Ericsson Internal | 2015-12-03 | Page

47
MO MAPPING

DUS BB5216
RBSLocalCell NodeBLocal Cell
Sector NodeBSectorCarrier
SectorAntenna SectorEquipmentFuncti
Carrier XX
InterfaceIPv4 IpInterface
AddressIPv4 ipaccesshostet
xx RouteTableIPv4Static

Baseband G2 Introduction | Ericsson Internal | 2015-12-03 | Page

48
BASIC COMMANDS

› # Log on node : ( moshell <Node IP> )

› #Make CV: acc BrmBackupManager createBackup
› #Delete CV: acc BrmBackupManager deleteBackup
› #cvls: hget brmbackup= !progress|id$|swversion
› #cvset & node restart on startable CV: acc BrmBackup=XX restore
› #Restart Node: acc FieldReplaceableUnit=1 restartUnit
acc 000100 restartunit
To restart individual board from COLI: restart –c

Baseband G2 Introduction | Ericsson Internal | 2015-12-03 | Page

49
LICENSE ALARMS

Alarm MO Severity Description

License Key File Fault Lm CRITICAL No License File

Installed
Configuration Requires Feature Activation SectorEquipment MAJOR Missing Feature in
License Key file
Function/NodeBL
ocalCell
Emergency Unlock Reset Key Required EmergencyUnlock WARNING Emergency Unlock Is
activated

Baseband G2 Introduction | Ericsson Internal | 2015-12-03 | Page

50
SYNC ALARMS

Alarm MO Severity Description

Sync Frequency Reference Not Reliable RadioEquipmentC WARNING No License File

lockReference Installed
Sync Frequency Server Reachability RadioEquipmentC WARNING Missing Feature in
Fault lockReference License Key file
SyncE Reference Failed RadioEquipmentC WARNING Emergency Unlock Is
lockReference activated

Baseband G2 Introduction | Ericsson Internal | 2015-12-03 | Page

51
CELL ALARMS

Alarm MO Severity Description

Inconsistent Configuration NodeBLocalCell MAJOR available

hardware or
software is
incompatible with
the Local Cell
configuration
RNC Connection Failure NBAPCOMMON MAJOR Iub Link is down

Baseband G2 Introduction | Ericsson Internal | 2015-12-03 | Page

52
 POWER ALARM

Alarm MO Severity Description

Loss of Mains PowerSupply MAJOR Commmercial
Power Down
High Operating PowerDistrubution MAJOR
Temperature Main
Load Disconnected

Battery BatteryBackup MAJOR Batteries Are

Disconnected discharged
Battery Missing BatteryBackup MAJOR

Baseband G2 Introduction | Ericsson Internal | 2015-12-03 | Page

53
2
Wo r l d ’ s b e s t
Baseband
made better

6- BB5216 LICENSE
55
2
Wo r l d ’ s b e s t
Baseband
made better

7- ADD BASEBAND IN OSS

6. Add Node in OSS-RC

• Access OSS-RC and run OSS Explorer

6. Add Node in OSS-RC (2)

• ONMR  Topology  LTE  Right Button  Add

Network Element
6. Add Node in OSS-RC (3)

• “Add Network Element” window “Signature”

1 eNB Name

1 eNB12
2 MSRBS_V2
2
3 3 True
4
4 1

5 NEXT

5
6. Add Node in OSS-RC (4)

• “Topology1”

1
2
3
1 LTE
4 2 According to Site
5
3 MSRBS_V2

4 L16A

5 ENodeB
6 6 Next
6. Add Node in OSS-RC (5)

• “Topology2”

1 ONRM

2 Next

2
6. Add Node in OSS-RC (6)

• “Connectivity 1”

1
1 IP Address
2 2 FTP SW Store

3 ON

4 Next
3

4
6. Add Node in OSS-RC (7)

• “Connectivity 2”

Fills in automatically

1 Next

1
6. Add Node in OSS-RC (8)

• “Protocols (Protocol-0)”

1 2022

2 Next
1

2
6. Add Node in OSS-RC (10)

• “Protocols (Protocol-2)”
– Add  Protocol-2  SNMP

1
1 161
2
2 v2c

3 public

3 4 Next

4
6. Add Node in OSS-RC (11)

• “Protocols (Protocol-3)”
– Add  Protocol-3  SSH

1 2023
2 Next
1

2
6. Add Node in OSS-RC (11)

• “Security”

1 User name
/Password

1
2 Next

2
6. Check Node Synch

• OSS Common Explorer Launch

6. Check Node Synch

• Synchronize Node
– Select Node  Right Button
 Synchronize Node
– Check Node is Synchronized
VODAFONE IN-HOUSE ACADEMY