Ericsson Internal

TZ L14B NEW SITE INTEGRATION 1 (23)

Prepared (also subject responsible if other) No.

Chao Xu O
Approved Checked Date Rev Reference

TZ TIGO LTE ON SITE INTEGRATION

1 Introduction

1.1 Background and Scope

This document describes the method of procedure for integrating a new eNodeB
into TZ Tigo LTE network. Activities include powering on the eNodeB, hardware
check before integration, health check before integration, upgrading SW to L14B,
loading 3 Sectors and 3 Cells configuration scripts, features and parameters
setting, and the post health check after integration.

The scope and basic process outline of the procedure is:

 eNodeB Pre-Integration Checks

 eNodeB Onsite Integration

 OSS Definition

 eNodeB Post-Integration Checks

1.2 Expected Network Impact

There is no expected network impact from the execution of this MoP.

2 Roles and Responsibilities and Timing

2.1 Activity Primes

 Ericsson Internal
TZ L14B NEW SITE INTEGRATION 2 (23)
Prepared (also subject responsible if other) No.

Chao Xu O
Approved Checked Date Rev Reference

CU
2.2 Role Timetable ofContact
Events Phone number
Project Manager Harold Tibanyenda +255 712800024

GSC China
Role Contact Phone number

Integration Engineer Chao Xu +255 716198862 / +86 13995538671

Tuning & OPT

Yuanqing Luo +86 18951989299
Engineer
Preparation Activities

 Power on RBS

 HW and Cabling Checks

 Upgrade Package and LKF checks

 Equipment and Tools

Network Integration

 Connecting to eNodeB locally

 Loading Transport Script

 Upgrade SW to L14B

 Loading Radio Scrips

 Loading Features and Parameters Scripts

 Install License key file

 OSS Definition

 Complete eNodeB Integration

Concluding Activities

 Ensure that Post-implementation check boxes are crossed of and

completed
 Ericsson Internal
TZ L14B NEW SITE INTEGRATION 3 (23)
Prepared (also subject responsible if other) No.

Chao Xu O
Approved Checked Date Rev Reference

3 Pre-requisites

3.1 Pre-Check

Check Description

Radio and Support System cables are connected correctly on the eNodeB as per installation
procedure.

eNodeB and radios powered up.

Site Configuration MO scripts review and taken on-site.

Upgrade Package taken on-site, Rollout Management Board decide the Final SW level.

License Key File taken on-site

3.2 Equipment and Tools Preparation

Check Description

Confirm MoShell has been installed correctly.

Confirm Ethernet cable to connect eNodeB to integration Engineer laptop PC

Element Manger and Integrate RBS downloaded from eNodeB and installed on PC
([Link] The Element Manager will be installed on your PC during the
first eNodeB Integration. Please refer to CPI Document “Installing an Element Management
Application”, 37/1543-LZA 701 6004 Uen B (Note: Version 1.5.0_12 of the Java Runtime
Environment (JRE) is needed.

Telnet application installed on PC. eg: SecureCRT

Confirm FileZilla FTP Server has been installed on PC. Make sure FTP Service has been
unlocked.

4 Implementation

4.1 Integration Readiness

4.1.1 Preliminary Preparation

 Ericsson Internal
TZ L14B NEW SITE INTEGRATION 4 (23)
Prepared (also subject responsible if other) No.

Chao Xu O
Approved Checked Date Rev Reference

Step Description

Preliminary Preparation and Tools check

1 Check FTP Service has been unlocked.

Right click “Computer” from windows start icon, click “Manage”.

Click “Services” on the left pane, make sure “FileZilla Server FTP server” in-service.

NOTE: FileZilla FTP Server is optional, other FTP server can be chosen in this step.

2 Shutdown the firewall on your PC.

3 Recursively check items in chapter 3 to make sure everything is ready.

4.1.2 Powering up eNodeBs

Step Description

Power Up the RBS and Check status

 Ericsson Internal
TZ L14B NEW SITE INTEGRATION 5 (23)
Prepared (also subject responsible if other) No.

Chao Xu O
Approved Checked Date Rev Reference

1 Verify RRUS cables are plugged into the appropriate connection points in the DUL and that
Ethernet cable is plugged in the appropriate connection between DUL and local router.

TN A - Local Router S1 CP/S1 UP/OAM/X2

RI A - Sector A, RRUS-1

RI B - Sector B, RRUS-3
RI C - Sector C, RRUS-5
RI D - Sector A, RRUS-2
RI E - Sector B, RRUS-4
RI F - Sector C, RRUS-6

Note: There are only one CPRI cable connected to DUS per secter (one AIR11),
so there are only 3 CPRI cable connected to DUS, and the ARUS(Inside AIR11)
will be cascaded.

2 Power on the RBS if not already done. Refer to CPI document “Installing RBS”.

3 Check optical indicators on the RBS HW; ensure that the green power indicators are on. If
there are any indications of faulty hardware follow the appropriate OPI to fix. If there are
still issues contact NIC for advice on how to further proceed.

4.1.3 Connect to eNodeB

Set the PC client IP and connect to the eNodeB

1 Connect an Ethernet cable from your PC to the eNodeB local Ethernet port (LMT).
 Ericsson Internal
TZ L14B NEW SITE INTEGRATION 6 (23)
Prepared (also subject responsible if other) No.

Chao Xu O
Approved Checked Date Rev Reference

2 Set the IP address of your PC in network settings to [Link], netmask to

[Link], and default router to [Link].

3 Open RBS Element Manager application for ENodeB on your PC.

NOTE: This will be under Start -> EM Applications -> RBS Element Manager.
 Ericsson Internal
TZ L14B NEW SITE INTEGRATION 7 (23)
Prepared (also subject responsible if other) No.

Chao Xu O
Approved Checked Date Rev Reference

4 From the RBS Element Manager application log into the rbs by entering the following IP
address in the “Address” field in the bottom, left corner:

[Link]

Click on “Connect” button at the bottom of the window.

 Ericsson Internal
TZ L14B NEW SITE INTEGRATION 8 (23)
Prepared (also subject responsible if other) No.

Chao Xu O
Approved Checked Date Rev Reference

5 Open your cygwin terminal and start moshell

moshell [Link]

lt all

4.2 Loading Transport Script.

This step will do the configuration for OAM, S1CP, S1UP and X2 interface on TNA port.

trun DAR020_TN.mo
 Ericsson Internal
TZ L14B NEW SITE INTEGRATION 9 (23)
Prepared (also subject responsible if other) No.

Chao Xu O
Approved Checked Date Rev Reference

This step should be done on site, after this script run completed, do a connectivity check
from eNodeB or call integration team to check the connectivity by remotely.

Notes: the following steps can be done on site and also can be done by remote
integration, if the connectivity is ok, the integrator can do the following activities
via OSS remotely.

4.3 SW Upgrading

Rollout Management Board should decide which SW level the new eNodeB will
be upgraded. According to the RAN solution design, the SW L14B R36AJ will be
used for TZ Tigo LTE trial project

Here lists the available upgrade path for reference.

Way1: Apply to the 6 trial FDD sites which already upgraded to L14A IP4.

L13A (R25BF)  L14A IP4(R28AY)  L14A IP5(R29BJ)  L14A IP7(R32BA)

 L14B GA(R36AJ)

Way 2: The normal upgrade path, will be applied to the rollout.

L13A (R25BF)  L14A IP7(R32BA)  L14B GA(R36AJ)

Upgrade eNodeB from Basic CV

Alarm Check before upgrade, notes down existing alarms for post-upgrade comparison.
1 Notes: the SW package name should be modified accordingly.

alt
 Ericsson Internal
TZ L14B NEW SITE INTEGRATION 10 (23)
Prepared (also subject responsible if other) No.

Chao Xu O
Approved Checked Date Rev Reference

Check the sw version of current basic CV.

2
cvls

Check the basic CV SW version, choose the appropriate Upgrade Package according to
Upgrade Path.

3 Check the FTP security mode.

secmode –s

If text in blue box is unsecure, skip step.

 Ericsson Internal
TZ L14B NEW SITE INTEGRATION 11 (23)
Prepared (also subject responsible if other) No.

Chao Xu O
Approved Checked Date Rev Reference

4 Change FTP security mode to un-secure

secmode –f u

Check the security state.

5 Create upgradepackage MO. For example:

cr SwManagement=1,UpgradePackage=CXP102051%12_R15AC

There are four attributes need to input:

ftpServerIpAddress: FTP Server IP, in this case, IP of PC.

upFilePathOnFtpServer: Path to UCP file.

user: user name for FTP account.

password: password for FTP account.

 Ericsson Internal
TZ L14B NEW SITE INTEGRATION 12 (23)
Prepared (also subject responsible if other) No.

Chao Xu O
Approved Checked Date Rev Reference

6 Install sw into eNodeB

acc <UP Proxy> nonBlockingForcedInstall

7 Monitor installation progress until attribute “state” reaches to “1

(INSTALL_COMPLETED)”.

get <UP Proxy> pro|head|stat

8 Upgrade new SW package.

acc <UP Proxy> rebootNodeUpgrade

9 Monitor upgrade progress until attribute “state” reach to “3

(AWAITING_CONFIRMATION)”

get <UP Proxy> stat|pro|head

 Ericsson Internal
TZ L14B NEW SITE INTEGRATION 13 (23)
Prepared (also subject responsible if other) No.

Chao Xu O
Approved Checked Date Rev Reference

10 Confirm upgrade

acc <UP Proxy> confirmUpgrade

11 Monitor confirm progress until attribute “state” reach to “7 (UPGRADE_COMPLETED)”

get <UP Proxy> stat|pro|head

12 Check eNodeB running on new sw version, Startable CV has prefix “Fi_CXP”, Fi CV

means upgrade process completes.

cvcu
 Ericsson Internal
TZ L14B NEW SITE INTEGRATION 14 (23)
Prepared (also subject responsible if other) No.

Chao Xu O
Approved Checked Date Rev Reference

13 Alarm Check Post-upgrade, compare with alarms got before upgrade, if something
exception happens, call NIC engineer to report the issue.

Alt

14 Repeat this section “SW Upgrading” until eNodeB runs at the required SW level.

4.4 Loading Radio Script

trun DAR020_RN.mo

After this step done, the ARUS, sectors and Cells should be configured, as well
as MME.

4.5 Loading Features and Parameters Scripts

run 3_ change_TuSync_to_GpsSync.mos //this will configure the SYNC via GPS

run 4_Intra_relation.mos // this script will configure the intra cell relation

run 5_fdd_mimo_ret.mos // this script will configure the RET for antenna tilt

run 6_Recommanded_parameter_PA1.mos //this script will do the paramters setting and

features activation.

run sup_master_single.mos // this script the SUP configuration to monitor the [Link].

Notes: After above scripts completed, need to configure the inter cell relation between
eNodeBs, and this script will be provided later according to the cell relation design.
 Ericsson Internal
TZ L14B NEW SITE INTEGRATION 15 (23)
Prepared (also subject responsible if other) No.

Chao Xu O
Approved Checked Date Rev Reference

4.6 License Key File Installation

License Key File Installation

1 Configure LogicalName attribute to eNodeB for LKF loading.

> trun 00_eNB_ FingerPrint_LKF.mo

Check if Emergency state is active. If emergencyStateInfo::state not equal to

2 0(NEVER_USED), call NIC to report this issue.

get licensing=1$

Put license key file into FTP server, eNodeB can access this file. ZIP file should be
3 unzipped to xml file.

Check the logical name for each eNodeB if it is compliant with design doc.
4
get ManagedElement=1 logicalName
 Ericsson Internal
TZ L14B NEW SITE INTEGRATION 16 (23)
Prepared (also subject responsible if other) No.

Chao Xu O
Approved Checked Date Rev Reference

Import LKF into eNodeB

acc licensing updateLicenseKeyFile

There are four parameter need to input:

userId: user name of FTP account

password: password of FTP account

ipAddres: IP address of FTP server

sFile: Path to access UCF file.

Then check LKF has been imported successfully, check attribute “fingerprint” is the correct
one.

get licensing=1$
 Ericsson Internal
TZ L14B NEW SITE INTEGRATION 17 (23)
Prepared (also subject responsible if other) No.

Chao Xu O
Approved Checked Date Rev Reference

5 Save a CV and give eNodeB a cold restart.

cvms fingerprint_license exxxxxx none

Check the capacity and license state:

Inv

4.7 OSS definition

Please refer to the attachment for the sites defined into OSS.

4.8 Post Integration

Post Integration Testing

These check are executed directly following the integration.

 Ericsson Internal
TZ L14B NEW SITE INTEGRATION 18 (23)
Prepared (also subject responsible if other) No.

Chao Xu O
Approved Checked Date Rev Reference

1 From the Element Manager window click on the drop down menu circled in the picture
below and select “Containment (MOM based)”.

Ensure that the “logicalName” is the correct name for the RBS site that you are integrating
as is circled in the picture below.
 Ericsson Internal
TZ L14B NEW SITE INTEGRATION 19 (23)
Prepared (also subject responsible if other) No.

Chao Xu O
Approved Checked Date Rev Reference

2 Check state of all cells.

Note: Doing this step will cause the Node to radiate. Please be mindful of this when
doing this step and take any necessary precautions to ensure no one is harmed by
the radiation.

From the Element Manager window click on the drop down menu circled in the picture
below and select “Radio Network”.

PATH:

Radio Network Configuration

Verify attribute “operationalState” is DISABLED for all cells.

Right click on the cell to list all the available actions and choose “Lock/Unlock” circled in
the picture below
 Ericsson Internal
TZ L14B NEW SITE INTEGRATION 20 (23)
Prepared (also subject responsible if other) No.

Chao Xu O
Approved Checked Date Rev Reference

From the drop down menu select “UNLOCKED” and then select the “Set” button as circled
in the picture below
 Ericsson Internal
TZ L14B NEW SITE INTEGRATION 21 (23)
Prepared (also subject responsible if other) No.

Chao Xu O
Approved Checked Date Rev Reference

Then select the “Refresh Values” button as circled in the below picture.

Verify attribute “operationalState” is ENABLED as is circled in the below picture

NOTE: Verify for all the cells in the eNodeB that the “operationalState” becomes ENABLED. If
not contact the NIC for advice on how the further proceed.
 Ericsson Internal
TZ L14B NEW SITE INTEGRATION 22 (23)
Prepared (also subject responsible if other) No.

Chao Xu O
Approved Checked Date Rev Reference

Generate an alarm in the eNodeB.

3
Disconnect a CPRI cable between the DUL and RU or RRU.

Verify the following alarm is issued in the eNodeB.

4
LinkFailure link_failure Subrack=1,Slot=1,PlugInUnit=1,RiPort=x

From the task bar click on Alarm, then click Alarm List.

Re-Connect the CPRI cable between the DUS and RU or RRU.

5
Verify the alarm is ceased in the eNodeB.
6
 Ericsson Internal
TZ L14B NEW SITE INTEGRATION 23 (23)
Prepared (also subject responsible if other) No.

Chao Xu O
Approved Checked Date Rev Reference

Collect kget file and store for reference.

7
> dcgk

8 Check the alarm in eNodeB. Cease alarms in this eNodeB.

> alt

9 Call NIC and have them verify site status and alarms. Once they have verified from the
NIC that the site is integrated correctly this procedure is complete.

5 Post Implementation

Check Description

Ensure that there are no alarms on the eNodeB.

Log files from this procedure are collected, this include integration log file from section 4.2 to 4.4.

NIC has been contacted and the have accepted the site as Integration Completed

Any outstanding items (eg. Missing cables, incorrect feeder connection), please note down and
contact with NIC.