Telecomhall Experts PDF Free

09/04/2019
telecomHall Experts
Handbook
A Practical Guide for Telecom

Professionals
telecomHall Experts Handbook
Summary
1 Introduction......................................................................................................................... 8
1.1 Overview ....................................................................................................................... 8
1.2 The Structure of the Book ........................................................................................... 8
1.3 Authors ......................................................................................................................... 8
1.3.1 Who is it headed for? ........................................................................................... 9
1.3.2 How can I support/participate of this project? .................................................. 9
1.4 Hunter Methodology ................................................................................................. 10
1.4.1 Exporting Network Data .................................................................................... 10
1.4.2 TO BE CONTINUED.............................................................................................. 10
2 Boda BTS-CE ...................................................................................................................... 11
2.1 Background/Introduction .......................................................................................... 11
2.2 BTS-CE CM Features/Functionalities ........................................................................ 11
2.3 Supported vendor CM dump formats ...................................................................... 12
2.4 Minimum Requirements............................................................................................ 12
2.5 Built With .................................................................................................................... 12
2.6 Very Important Concepts .......................................................................................... 13
2.6.1 What is a Virtual Machine?................................................................................ 13
2.6.2 What is a Container? .......................................................................................... 14
2.6.3 Containers and Virtual Machines Together ...................................................... 14
2.6.4 What is Docker?.................................................................................................. 15
2.6.5 What Is Hyper-V?................................................................................................ 16
2.6.6 What is HyperKit? ............................................................................................... 16
2.6.7 What is Virtualbox? ............................................................................................ 16
2.6.8 Other concepts ................................................................................................... 17
2.7 Pre-Installation ........................................................................................................... 17
2.7.1 Enable/Disable Virtualization in BIOS ............................................................... 18
2.7.2 Enable/Disable Hyper-V ..................................................................................... 19
2.7.3 Install Oracle VM VirtualBox .............................................................................. 20
2.7.4 Install Docker ...................................................................................................... 22
2.7.5 Download Git (only if you want to contribute code) ....................................... 26
Page 2 of 85
2.8 GitHub ......................................................................................................................... 29

2.9 Installation .................................................................................................................. 29
2.10 Architecture ............................................................................................................ 31
2.10.1 Mediation ............................................................................................................ 32
2.10.2 Database ............................................................................................................. 33
2.10.3 Commands .......................................................................................................... 33
2.11 Processing your CM files ........................................................................................ 33
3 MODULES .......................................................................................................................... 36
3.1 CM (Configuration Management) ............................................................................. 36
3.1.1 ERICSSON 2G ....................................................................................................... 36
3.1.2 ERICSSON 3G ....................................................................................................... 36
3.1.3 ERICSSON 4G ....................................................................................................... 38
3.1.4 HUAWEI 2G ......................................................................................................... 39
3.1.5 HUAWEI 3G ......................................................................................................... 40
3.1.6 HUAWEI 4G ......................................................................................................... 41
3.1.7 NOKIA 2G ............................................................................................................ 42
3.1.8 NOKIA 3G ............................................................................................................ 43
3.1.9 NOKIA 4G ............................................................................................................ 44
3.1.10 ZTE 2G ................................................................................................................. 45
3.1.11 ZTE 3G ................................................................................................................. 45
3.1.12 ZTE 4G ................................................................................................................. 46
3.2 IM (Inventory Management) ..................................................................................... 47
3.2.1 ERICSSON 2G ....................................................................................................... 47
3.2.2 ERICSSON 3G ....................................................................................................... 49
3.2.3 ERICSSON 4G ....................................................................................................... 51
3.2.4 HUAWEI 2G ......................................................................................................... 52
3.2.5 HUAWEI 3G ......................................................................................................... 55
3.2.6 HUAWEI 4G ......................................................................................................... 55
3.2.7 NOKIA 2G ............................................................................................................ 55
3.2.8 NOKIA 3G ............................................................................................................ 55
3.2.9 NOKIA 4G ............................................................................................................ 55
Page 3 of 85
3.2.10 NOKIA 2G ............................................................................................................ 55

3.2.11 ZTE 3G ................................................................................................................. 55
3.2.12 ZTE 4G ................................................................................................................. 55
3.3 PM (Performance Management) .............................................................................. 56
3.3.1 ERICSSON 2G ....................................................................................................... 56
3.3.2 ERICSSON 3G ....................................................................................................... 56
3.3.3 ERICSSON 4G ....................................................................................................... 56
3.3.4 HUAWEI 2G ......................................................................................................... 56
3.3.5 HUAWEI 3G ......................................................................................................... 56
3.3.6 HUAWEI 4G ......................................................................................................... 56
3.3.7 NOKIA 2G ............................................................................................................ 56
3.3.8 NOKIA 3G ............................................................................................................ 56
3.3.9 NOKIA 4G ............................................................................................................ 56
3.3.10 NOKIA 2G ............................................................................................................ 56
3.3.11 ZTE 3G ................................................................................................................. 56
3.3.12 ZTE 4G ................................................................................................................. 56
3.4 FM (Fault Management) ............................................................................................ 57
3.4.1 ERICSSON 2G ....................................................................................................... 57
3.4.2 ERICSSON 3G ....................................................................................................... 57
3.4.3 ERICSSON 4G ....................................................................................................... 57
3.4.4 HUAWEI 2G ......................................................................................................... 57
3.4.5 HUAWEI 3G ......................................................................................................... 57
3.4.6 HUAWEI 4G ......................................................................................................... 57
3.4.7 NOKIA 2G ............................................................................................................ 57
3.4.8 NOKIA 3G ............................................................................................................ 57
3.4.9 NOKIA 4G ............................................................................................................ 57
3.4.10 NOKIA 2G ............................................................................................................ 57
3.4.11 ZTE 3G ................................................................................................................. 57
3.4.12 ZTE 4G ................................................................................................................. 57
3.5 TRACE (Logs) ............................................................................................................... 58
3.5.1 ERICSSON 2G ....................................................................................................... 59
Page 4 of 85
3.5.2 ERICSSON 3G ....................................................................................................... 59

3.5.3 ERICSSON 4G ....................................................................................................... 59
3.5.4 HUAWEI 2G ......................................................................................................... 59
3.5.5 HUAWEI 3G ......................................................................................................... 59
3.5.6 HUAWEI 4G ......................................................................................................... 62
3.5.7 NOKIA 2G ............................................................................................................ 62
3.5.8 NOKIA 3G ............................................................................................................ 62
3.5.9 NOKIA 4G ............................................................................................................ 62
3.5.10 NOKIA 2G ............................................................................................................ 62
3.5.11 ZTE 3G ................................................................................................................. 62
3.5.12 ZTE 4G ................................................................................................................. 62
3.6 Other ........................................................................................................................... 62
4 OSS Operations Support System ...................................................................................... 63
4.1 Ericsson: Network Management System (ENM / OSS-RC) ...................................... 63
4.1.1 OSS-RC (OSS Radio and Core) ............................................................................ 63
4.1.2 ENM (Ericsson Network Manager) .................................................................... 64
4.2 Huawei M2000/U2000 and Enterprise Network Management ............................. 64
4.2.1 M2000/U2000 Network Management System ................................................ 64
4.3 Nokia: NetAct ............................................................................................................. 65
4.3.1 Nokia NetAct Archive Cloud .............................................................................. 65
4.4 ZTE: NetNumen U31 (CN) Unified OSS Platform ..................................................... 66
4.4.1 NetNumen U31 (CN) .......................................................................................... 66
5 Finding Documentation .................................................................................................... 67
5.1 ERICSSON .................................................................................................................... 67
5.2 HUAWEI ...................................................................................................................... 68
5.3 NOKIA .......................................................................................................................... 69
5.4 ZTE ............................................................................................................................... 69
6 Tips ..................................................................................................................................... 70
6.1 Telecom Tips ............................................................................................................... 70
6.1.1 ERICSSON BB and DU Radios ............................................................................. 70
6.2 General Tips ................................................................................................................ 70
Page 5 of 85
6.2.1 Installing Linux on Windows .............................................................................. 70

6.3 ACRYS used in this BOOK ........................................................................................... 72
6.4 Commands in UNIX .................................................................................................... 73
6.4.1 Compress a file ................................................................................................... 73
6.4.2 Getting information............................................................................................ 74
6.5 Commands in ERICSSON ............................................................................................ 74
6.5.1 MOSHELL ............................................................................................................. 74
6.5.2 MOBATCH ........................................................................................................... 75
6.5.3 Passwords ........................................................................................................... 76
6.6 Naming Suggestions for Dump Files ......................................................................... 76
6.6.1 Ericsson GSM CM {TXT} ...................................................................................... 77
6.6.2 Ericsson WCDMA / LTE CM {XML} ..................................................................... 77
6.6.3 Huawei GSM / WCDMA / LTE CM {XML} .......................................................... 77
6.6.4 Huawei GSM / WCDMA / LTE INV {CSV} ........................................................... 77
6.6.5 Ericsson GSM INV {TXT} ..................................................................................... 77
7 Troubleshooting ................................................................................................................ 78
7.1 Error message: “Error checking TLS connection” .................................................... 78
7.2 Error Message: “Login attempt failed” ..................................................................... 78
7.3 Error Message: “Argument 'win \ Setup.ps1' … does not exist” ............................ 80
7.4 Error message: “Database is still being setup” ........................................................ 80
7.5 Error message: “This website could not be found.” ................................................ 81
7.6 Error message: “This site can’t be reached.” ........................................................... 82
7.7 Airflow not working ................................................................................................... 82
8 Roadmap............................................................................................................................ 84
8.1 Background ................................................................................................................. 84
8.2 2019 ............................................................................................................................ 84
8.2.1 List of planned functionalities (CM Module) .................................................... 85
8.2.2 List of planned functionalities (PM Module) .................................................... 85
8.2.3 List of planned functionalities (Trace Module) ................................................ 85
8.2.4 List of planned functionalities (All Modules) .................................................... 85
Page 6 of 85
Page 7 of 85
1 Introduction
1.1 Overview
During decades Telecommunications has changed a lot. Also, has changed the work of
Telecom Professional.
More and more new Technologies are introduced, with new algorithms, tools, demands,
creating a big challenge to the telecom professional. Urgent requirements on day to day
work don’t give the professional extra time to search for good information or resources
available. This situation often ends up with extra (or redundant) work being executed, while
some important tasks are postponed.
Thinking about these problems, this book was created: to meet the needs of those who
want to go straight to the point, knowing the best way to work with all current telecom
vendors.
1.2 The Structure of the Book

This document provides an insight into the different methods to work with multivendor
multi-technology networks. This includes data collection, processing and of course, using it
to get results.
Here you will find guides (steps by steps) to do each task. Either using GUI (Graphical User
Interface) or CLI (Command Line Interface). By following the steps or recommended
procedures, the professional will be able to collect and process any kind of important file to
evaluate the Network.
TIP: There’s often more than one way (as the presented here) to achieve these results. If
you know a better flow, please contact us and help to improve our handbook.
1.3 Authors
As the entire telecomHall mission, this book is also collaborative.
This book is written by a selected group of Experts, using the telecomHall platform to
collaborate.
http://www.telecomhall.net/t/telecomhall-experts-list/5077
There are currently more than 100 people contributing with the project in their spare time.
Page 8 of 85
1.3.1 Who is it headed for?

This guide is aimed at first time users or experienced users requiring a quick reference on
telecommunications.
This Handbook, its mission, vision (telecomHall, Hunter, Boda) is intended for anyone with
desire to collaborate, to learn and to share ideas.
This can be:
• Telecom Consultants: working for several vendors, and often needing to handle
different vendor data;
• Students: an opportunity to learn and understand how a complete telecom system
works through practical examples;
• Programmers: either to improve your skills or simply learn;
• Carrier (Operator) employee: to learn alternative tools/methods you can use in your
company, saving CAPEX and OPEX;
• Or simply a tech addict: if you want to participate in a project that aims to reach the
complete ecosystem (get and handle configuration data, performance data, fault
data, etc...) and present it in a dashboard.
1.3.2 How can I support/participate of this project?

Your support will ensure the success of the project.
There are different ways you can get involved:
• You can contribute code to the project.

• You can share the project with your friends and spread the word
• You can use the tool and provide feedback on any issues you may find
• You can write documentation and ‘how to’ guides
• You can answer questions for other users concerning usage
• You can suggest/request new features in the telecomHall Forum platform
Page 9 of 85
1.4 Hunter Methodology

There some differences from using each vendor/technology information. Each one can have
his own way.
In addition, the experts use the Hunter Methodology, a free group of the best practices
agreed on some theme (when everyone agrees on some best way to do some action).
1.4.1 Exporting Network Data

Instead of exporting chunks of data for each specific need, we prefer to export ALL network
data. Every vendor has a method of configuring data for large networks (for example using
XML files) adhering to a defined structure and are compliant with 3GPP standards.
• In Ericsson for example we have the BCG Bulk Configuration (BCG), that works
conforms to the 3GPP requirements for uploading (export) and downloading
(import) configuration files.
• In Huawei, we also have the files (GExport).
1.4.2 TO BE CONTINUED
Page 10 of 85
2 Boda BTS-CE
2.1 Background/Introduction
In 2017, we wrote about an initiative to develop useful tools for the community (Free Tools
Initiative http://www.telecomhall.net/t/free-tools-initiative/1613).
We started by sharing free CM dump PARSERS for Ericsson, Huawei, ZTE and Nokia. Anyone
was able to download each parser and process their network data by themselves.
In 2018, the initiative has continued with the release of BTS-CE an open source network
management platform (Free Tools Initiative http://www.telecomhall.net/t/free-tools-
initiative-continued/3652).
During last year there were several enhancements, mainly with the help with the Experts
group.
In 2019, we’re ready to give a step ahead, now with the global launch of the tool, making it
available to everyone.
The first version of the tool will handle only CM domain. The intention is to make it clear for
anyone participating in the Open Source project to be familiar with the tool, architecture,
etc. Then, in the collaborative platform, we’ll soon move forward to PM, FM, Geo, Trace
and even SON. (*All these functionalities are planned in the roadmap, but deliver it all could
lose focus, due to too many questions and requests.)
So, in this initial release, we’re going to have BTS-CE CM.
2.2 BTS-CE CM Features/Functionalities

Built on CM parses, the tool provides the following functionality in this release:
1. Automatic generation of network topology – HUNTER KEY PARAMETERS
2. Automatic network baseline generation– HUNTER BASELINE
3. Radio network element browsing
4. CM managed object browsing
5. Radio Access Network (RAN) audit (relations, conflicts, parameter values vs
baseline)
6. Reporting
This release handles 2 vendors: Ericsson and Huawei.
ZTE and Nokia will be added in the next release.
Page 11 of 85
A detailed roadmap will be shared in a different post.
2.3 Supported vendor CM dump formats

Below are the file formats current supported:
• Ericsson: CNAIV2 for 2G, bullkcm XML for 3G and 4G

• Huawei: all formats but GExport is preferred as it contains much more information
• Nokia: all XML formats (in test).
• ZTE: all XML formats (in test).
Note: You can find more details on how to collect all vendors data (CM, PM, etc…) in below
chapters.
2.4 Minimum Requirements

Before starting the installation, you must check if you have the following minimum
requirements that are needed to run BTS-CE:
1. 4GB memory
2. 64-bit OS
3. 5GB hard disk space. More will be required depending on your network size
4. Latest web browser
5. Support for virtualization for Windows
IMPORTANT: Before you get started, you should test your computer’s hardware
performance to make sure your virtual machine will run smoothly. Even if we say 4GB
of RAM is “sufficient”, you should ideally have 8GB to 16GB. There is a difference
between “the software works” and “the software is usable.”
You should also make sure your hard drive has enough space for an additional OS. Ideally
it should be SSD, for I/O swap.
Keep in mind that
2.5 Built With

For those who want to collaborate in code, the tool is built mainly using:
• Python
• PostgreSQL
• Apache Airflow
Page 12 of 85
• ReactJs
2.6 Very Important Concepts

Before continuing, there are some important concepts you need to know.
The tool will need a Virtual Machine (VM) and will also use Containers. So, let's quickly know
what this is.
2.6.1 What is a Virtual Machine?

There are many reasons to use a virtual machine. In most cases, they are used to run
software that does not work on your OS. Whether you’re using a Windows, Mac or Linux
OS, a VM will remove its limitations. For example, if you have a Windows machine and want
to install an application that is only available for Mac, you can run a macOS instance on your
Windows computer to install it.
It doesn’t even have to be the case that the software doesn’t run on Windows. Maybe you
work faster on the Linux or Mac version of it because you’re more familiar with its shortcuts
and usability.
Most software developers like to work on terminals, so they prefer Linux. That said, since
many of us were accompanied by Windows through our school days, we do paperwork
faster on it.
Another thing to consider is that programs on Windows are rarely uninstalled without a
trace. You will find old settings, registry entries or other artefacts that will slow down your
operating system. If you want to use an application temporarily, set up a VM, use the
program and remove the VM when you have finished. That way you won’t have to clean
your notebook afterward.
Using a virtual machine also makes sense for protection. With the virtualized OS, you bring
an extra layer of security into play. If you’re not quite sure you should run a file you
downloaded from an untrusted source on your productive OS, use a VM.
A VM will let you get through the dark web more safely, too. At this point, you need to know
that a VM is extremely slow. It will bog down your active OS and the virtual one. You should
think twice about whether you want to use the slow Tor browser on a slow VM to surf the
dark web.
IMPORTANT: Remember a VM uses a lot of memory an space. So make sure your

computer’s hardware is fine, to continue.
Page 13 of 85
2.6.2 What is a Container?

A container is a standard unit of software that packages up code and all its dependencies,
so the application runs quickly and reliably from one computing environment to another. A
container image is a lightweight, standalone, executable package of software that includes
everything needed to run an application: code, runtime, system tools, system libraries and
settings.
Containers allow a developer to package up an application with all of the parts it needs,
such as libraries and other dependencies, and ship it all out as one package. By doing so,
thanks to the container, the developer can rest assured that the application will run on any
other Linux machine regardless of any customized settings that machine might have that
could differ from the machine used for writing and testing the code.
Containers isolate software from its environment and ensure that it works uniformly
despite differences for instance between development and staging.
2.6.3 Containers and Virtual Machines Together

Containers and virtual machines have similar resource isolation and allocation benefits, but
function differently because containers virtualize the operating system instead of
hardware. Containers are more portable and efficient.
Containers and VMs used together provide a great deal of flexibility in deploying and
managing app.
2.6.3.1 CONTAINERS
Containers are an abstraction at the app layer that packages code and dependencies
together. Multiple containers can run on the same machine and share the OS kernel with
other containers, each running as isolated processes in user space. Containers take up less
space than VMs (container images are typically tens of MBs in size), can handle more
applications and require fewer VMs and Operating systems.
2.6.3.2 VIRTUAL MACHINES

Virtual machines (VMs) are an abstraction of physical hardware turning one server into
many servers. The hypervisor allows multiple VMs to run on a single machine. Each VM
includes a full copy of an operating system, the application, necessary binaries and libraries
- taking up tens of GBs. VMs can also be slow to boot.
Page 14 of 85
2.6.4 What is Docker?

Docker is a tool designed to make it easier to create, deploy, and run applications by using
containers.
In a way, Docker is a bit like a virtual machine. But unlike a virtual machine, rather than
creating a whole virtual operating system, Docker allows applications to use the same Linux
kernel as the system that they're running on and only requires applications be shipped with
things not already running on the host computer. This gives a significant performance boost
and reduces the size of the application.
Available for both Linux and Windows-based applications, containerized software will
always run the same, regardless of the infrastructure.
And importantly, Docker is open source.
Container images become containers at runtime. In the case of Docker containers images
become containers when they run on Docker Engine.
Docker containers that run on Docker Engine:
• Standard: Docker created the industry standard for containers, so they could be
portable anywhere
• Lightweight: Containers share the machine’s OS system kernel and therefore do not
require an OS per application, driving higher server efficiencies and reducing server
and licensing costs
• Secure: Applications are safer in containers and Docker provides the strongest
default isolation capabilities in the industry
Docker Containers Are Everywhere: Linux, Windows, Data center, Cloud, Serverless, etc.
Docker container technology was launched in 2013 as an open source Docker Engine.
It leveraged existing computing concepts around containers and specifically in the Linux
world, primitives known as cgroups and namespaces. Docker's technology is unique
because it focuses on the requirements of developers and systems operators to separate
application dependencies from infrastructure.
Success in the Linux world drove a partnership with Microsoft that brought Docker
containers and its functionality to Windows Server (sometimes referred to as Docker
Windows containers).
Technology available from Docker and its open source project, Moby has been leveraged by
all major data center vendors and cloud providers. Many of these providers are leveraging
Docker for their container-native IaaS offerings. Additionally, the leading open source
serverless frameworks utilize Docker container technology.
Page 15 of 85
2.6.5 What Is Hyper-V?

Hyper-V is a Windows virtualization software that, well, virtualizes software. It can not only
virtualize operating systems but also entire hardware components, such as hard drives and
network switches.
Unlike Fusion and Virtualbox, Hyper-V is not limited to the user’s device. You can use it for
server virtualization, too.
Hyper-V is available in three versions.
• Hyper-V for Windows Servers

• Hyper-V Servers
• Hyper-V on Windows 10
Hyper-V for Windows Servers is an add-on to the Windows Server OS. Hyper-V Servers, on
the other hand, is a standalone solution that can be used to manage virtual and dedicated
server instances, just like Hyper-V for Windows Servers.
Hyper-V on Windows 10 is the version that runs on most computers.
To enable Hyper-V on your Windows device, you need a 64-bit OS. It doesn’t have to be
Windows 10, though. Windows 8.1 works too.
2.6.6 What is HyperKit?

Similar to Hyper-V on Windows, HyperKit is a lightweight macOS virtualization solution built
on top of the Hypervisor.framework.
2.6.7 What is Virtualbox?

When you can not use Hyper-V or HyperKit, you can install the Oracle Virtualbox
virtualization solution.
Of course, performance will be degraded compared to native Hyper-V or Hyperkit - because

they are Windows/Mac native software, we have processing gains.
Page 16 of 85
2.6.8 Other concepts

Of course, there are some other new important concepts, but it’s not our intention here to
cover it all. Also, above we’ve tried to state only the basics of these concepts, and we
encourage you to
But for now, it’s enough. So, let’s move and install it.
2.7 Pre-Installation
As we have said, before proceeding to install BTS-CE in your computer, you need to
‘prepare’ it to support it.
Basically, your computer needs:
• To be able to support virtualization;

• To allow installation of a VM (Virtual Machine) Software: it can be Windows Hyper-
V, Oracle VirtualBox, etc…
• To allow installation of Docker: it has the containers that will run on the VM.
Depending on your OS, there are some different steps you need to follow.
Note for Docker: Win 10 Build required for Docker Desktop is >= 14393. This means, that,
even if you have Windows 10 Pro, but with build number does not support Docker Desktop
Page 17 of 85
(like shown below) you need to install Docker Toolbox instead. Or upgrade your Win 10 Pro
build.
Check Windows 10 Build Version:
• Win + R. Open up the run command with the Win + R key combo. [winver]
• Launch winver. Simply type in winver into the run command text box and hit OK.
That is it.
You should now see a dialog screen revealing the OS build and registration information.
2.7.1 Enable/Disable Virtualization in BIOS

First, you need a computer that allow virtualization, and you can do this in BIOS.
You can check whether your computer has the ability of virtualization enabled by running
Task Manager.
Page 18 of 85
You can enable or disable the Intel® Virtualization Technology in the BIOS setup. The default
behavior is disabled. To change the settings, follow these steps.
Access the system BIOS by pressing <F1> or <F2> during the system power-on. (It depends
on your computer model)
Click Advanced > Processor Configuration.
2.7.2 Enable/Disable Hyper-V

Hyper-V is an optional feature available on some versions of Windows 10 (Like Enterprise,
Professional and Education). If you are using Windows 10 Home or any other windows
release, you will need to either upgrade or use Oracle VirtualBox.
Page 19 of 85
You can disable Hyper-V on your PC by following the steps shown below.
Go to Control Panel → Programs → Turn Windows features on or off. [optionalfeatures]
Uncheck Hyper-V settings, and click OK.
To enable, do the opposite: check Hyper-V.
2.7.3 Install Oracle VM VirtualBox

If your computer don´t meet the requirements to enable Hyper-V, you need to install Oracle
VM VirtualBox.
Go to https://www.virtualbox.org/wiki/Downloads
Look for the latest VirtualBox packages, see VirtualBox builds.
Note: Check if your computer is 32 or 64 bits.

In Windows Explorer, right click My Computer, and select Property.
In the VirtualBox Builds page, click on Windows hosts.
Page 20 of 85
Page 21 of 85
2.7.4 Install Docker

When installing Docker you can either use Hyper-V, Hyperkit or Oracle VirtualBox,
depending on your requirements (these are used to create virtual machines from which
your Docker containers will run).
Depending on the requirements your computer met, you must install:
• Docker Desktop for Windows/Mac

• Docker Tollbox for Windows/Mac
• docker-ce and docker-compose on Linux
2.7.4.1 Install Docker Desktop for Windows

The fastest and easiest way to get started with Docker on Windows or Mac.
Install Docker on Windows 10
• Download Docker.
• Double-click InstallDocker.msi to run the installer.
• Follow the Install Wizard: accept the license, authorize the installer, and proceed
with the install.
• Click Finish to launch Docker.
• Docker starts automatically.
Link: https://hub.docker.com/editions/community/docker-ce-desktop-windows
Page 22 of 85
Leave unchecked the option “Use Windows containers instead of Linux containers (this can
be changed after installation)”. Because bts-ce use Linux containers.
After logout, it will ask you to enable Containers feature. Click OK.
After restart, again, it will ask to run docker services. Click Start.
Page 23 of 85
Click Yes when Windows ask you for permission.
Maybe you find some problems due to lack of memory.
In this case, one option would be right click the red whale, and click “Settings…” try to free
memory.
Page 24 of 85
IMPORTANT: The problem above (lack of memory) happens to low performance (hardware)
users (for example with 4GB RAM only). Although we’re investigating solutions to run boda
on low computers, we must be aware that this kind of solution is not intended to run in
such poor hardware.
We’re trying to find a solution for these users can have boda. And will let you know via
WhatsApp group.
2.7.4.2 Install Docker Desktop for Mac

The fastest and easiest way to get started with Docker on Mac.
Double-click Docker.dmg to open the installer, then drag Moby the whale to the
Applications folder.
• Double-click Docker.app in the Applications folder to start Docker. ...

• Click the whale ( ) to get Preferences and other options.
• Select About Docker to verify that you have the latest version.
• Install Docker for Mac | Docker Documentation
Link: https://docs.docker.com/v17.12/docker-for-mac/install/
2.7.4.3 Install Docker Toolbox for Windows/Mac

Docker Toolbox is an installer for quick setup and launch of a Docker environment on older
Mac and Windows systems that do not meet the requirements of the new Docker Desktop
for Mac and Docker Desktop for Windows apps.
Visit: https://docs.docker.com/toolbox/overview/
Page 25 of 85
And proceed with installation.
2.7.4.4 Install docker-ce and docker-compose on Linux (Ubuntu)

Visit: https://docs.docker.com/install/linux/docker-ce/ubuntu/
And proceed with installation.
Note: for other Unix OS, visit: https://docs.docker.com/v17.12/install/#server
2.7.5 Download Git (only if you want to contribute code)

Finally, download and install Git.
Visit https://git-scm.com/download/win and download the latest version of Git for

Windows (the most recent maintained build).
Page 26 of 85
Page 27 of 85
2.7.5.1 How to contribute code? (only if you want to contribute code)
1. Create your GitHub account

2. Fork the tool repository
3. Clone your forked repo locally
a. git clone url_to_repo
4. Add origin repo to your remotes. This will be used to keep the master branch in sync
with the original repo
a. git remote add upstream url_to_original_repo
5. Create feature/patch branch
a. git checkout -b patch_branch
6. Make changes to file
7. Stage the changes
a. git add ./*
8. Commit the changes
a. git commit -m "Fix issue ..."
9. Push feature/patch to github
a. git push origin patch_branch
10. Create pull request (PR)
11. Go to you forked repo and create PR
Submit another change

1. checkout the master branch
a. git checkout master
2. Pull changes from the original repo’s master to your local master.
a. git fetch upstream
3. Merge changes into local master
a. git merge --ff upstream/master
4. Create feature/patch branch
a. git checkout -b patch_branch
5. Make changes to file
6. Stage the changes
a. git add ./*
7. Commit the changes
a. git commit -m "Fix issue ..."
8. Push feature/patch to github
a. git push origin patch_branch
9. Create PR
Page 28 of 85
a. Go to you forked repo and create PR
2.8 GitHub
All the code for BTS-CE will be shared using GitHub.
GitHub is a web-based Git repository hosting service that provides access control and
collaboration features for every project. GitHub provides a space for open source projects,
working with peers, and even a venue for recruiting. As of 2014, GitHub is the largest code
host in the world.
Note: Git is a distributed version-control system for tracking changes in source code during
software development. It is designed for coordinating work among programmers, but it can
be used to track changes in any set of files. Its goals include speed, data integrity, and
support for distributed, non-linear workflows.
The Open Source Philosophy - Recursively Share Work for Others to Build Upon! GitHub will
help you contribute to the open-source community. You can set up your profile for free,
start your projects, or build on top of others’ work. Over time, people can learn from you
too!
To joint, first create a GitHub user, if you still don’t have one.
Next, visit GitHub and find the latest repository for the Boda Telecom Suite Community
Edition (BTS-CE) - An open source telecommunication network management platform.
2.9 Installation
Once you have the minimum requirements, you can follow below steps to install:
• Download latest release files (bts-ce-version)

➢ You can find the latest version at:
➢ http://www.telecomhall.net/t/bts-ce-release-v2-0-0-rc8/5015
(PLEASE NOTE THAT CURRENTLY ONLY EXPERTS HAVE ACCESS TO IT)
• Unzip the downloaded files
➢ Currently, in Windows, you should put it under user folders, to make sure it
will have all the needed permissions.
The reason for this is Docker has limited access to the filesystem on the host computer. The
steps to share the folders when using Virtualbox and Docker Toolbox are a bit long and we
want to keep the process short for first time users.
Page 29 of 85
For the curious and brave, you can check out this article on how to share a folder outside
C:\Users: http://support.divio.com/local-development/docker/how-to-use-a-directory-
outside-cusers-with-docker-toolboxdocker-for-windows
We will provide our own writeup or try to automate it if it's possible.
• Launch Windows Command Line interface (from now on CMD)

• From CMD navigate to unzipped BTS-CE folder
cd /path/to/bts-ce-<version>
• Run setup command and follow any given instructions

bts setup
At this point, please be patient, and wait for the installation to finish.
If everything goes fine, up to this point, then you should be able to see the log in page.
• Open web browser and paste the URL http://localhost/ on windows or

http://192.168.99.100:8888
• Login with username: btsuser@bodastage.org and password: password
Again, everything going fine, you should be able to see the BTS-CE Main page.
Page 30 of 85
To be continued…
2.10 Architecture
Page 31 of 85
2.10.1 Mediation
One of the biggest challenges we have had to address is how to handle the many
complex depend data pipelines/workflows necessary to load data into the database,
transform it, and perform other domain specific processing.
Rather than re-invent the wheel we carefully surveyed the available open source data
pipeline and ETL tools. We narrowed down on Apache’s Airflow project started at
Airbnb. What it does is pure magic! Below is a sample of the Ericsson 3g4g ETL process
defined as a DAG (Directed Acyclic Graph) in Airflow. Each dependency is clearly
defined and easy to track.
The next figure below shows the duration of the entire process with the time each sub- task
took displayed in a Gantt chart. Identifying which process is the bottleneck become a trivial
task.
Page 32 of 85
2.10.2 Database
BTS-CE uses PostgreSQL database. Versions from 9.6 onwards are recommended.
You can get the PostgreSQL database from https://www.postgresql.org.
2.10.3 Commands
Here you a list of some commands you can use, in CMD, at the tool folder:
• bts setup: setup the tool in your computer.

• bts rm: remove the installation.
• bts recreate: recreate the tool.
• bts logs bts-api: will show the logs of api
• bts logs bts-database: will show the logs of database
To be continued…
2.11 Processing your CM files

At this first moment, you need to manually copy the CM raw dump files to specific folder.
Later, the idea is to link it directly from the OSS.
So, for now, copy your configuration management dumps to
mediation/data/cm/VENDOR_NAME/in folder.
Log into the application web interface with the details provided above.
Go to Processes > Airflow -> Enable cm_load. This is the processing job.
If you have all your raw CM data in appropriate folders, you can continue and process it.
Page 33 of 85
You can track the progress by clicking on the processing Graph. Click the cm_load > Graph
View job from the Airflow UI.
Below you can see some screenshots showing the graphical processing.
Once the cm_load job is completed, you can view the other modules
Page 34 of 85
Page 35 of 85
3 MODULES
3.1 CM (Configuration Management)

3.1.1 ERICSSON 2G
3.1.1.1 Exporting via GUI
3.1.1.2 Exporting via CLI

Log in into “Ericsson OSS” via Citrix.
Launch > Applications > Utilities > Terminal
Run command CNAI version 2:
cnai export valid -i > YourFileName.txt

The resulting file will be exported to the directory where you did run the command.
3.1.1.3 Processing
Open DOS Command Prompt
Run boda parser:

java -jar boda-ericssoncnaiparser.jar input_dir output_dir
Files will be created at: output_dir
Example:
java -jar C:\HUNTER\Boda\Parsers\boda-ericssoncnaiparser.jar

C:\Hunter\Boda\Ericsson_2G_CNAIV2_in\
C:\Hunter\Boda\Ericsson_2G_CNAIV2_out\
3.1.2 ERICSSON 3G
Ericsson BULK CM export
Launch “OSS Common Explorer”

Start > Applications > Ericsson > OSS Common Explorer
Page 36 of 85
Wait the “OSS Common Explorer” to load; After it is loaded, we can see the Main Window.
At the left, under Topology, there is WCDMA Networks.
Right click WCDMA Topology (in this example: “ONRM_ROOT_MO_R”).

In the right click pop up Menu, choose “Export RNS”.
TIP: if you want to export only one (or few) RNC, use SHIFT key pressed while selecting.
Than the Bulk CM Export dialog appears, with the Parameters Configuration Options.
Under “Export Details”, configure:
• Export to: where to save the Parameters Export (in the RNC)
(“/var/opt/ericsson/nms_umts_wran_bcg/files/export/”)
• File Name: the name of the file. For example, “My3GCmDump.XML”
• Filter Details: “Radio and Transport Network”
• Check “Use Compress Export”
Note: if this name already exists, it will be replaced in the Ericsson Server.
During the file export we can see the Exports Details.
At this point (at the Successful Status) the file is already exported from Network to Ericsson
Server.
Now we can “Exit” the “OSS Common Explorer”.
The file was exported to:
/var/opt/ericsson/nms_umts_wran_bcg/files/export/

#Sync all 3G/4G nodes
/opt/ericsson/ddc/util/bin/mibutil -adjust
SubNetwork=ONRM_ROOT_MO_R
#Export Configuration Parameters

/opt/ericsson/nms_umts_wran_bcg/bin/start_rah_export.sh both
/var/opt/ericsson/nms_umts_wran_bcg/files/export/My_3G4G_Bulk
CM_Export.xml
Page 37 of 85
Files exported to: /var/opt/ericsson/nms_umts_wran_bcg/files/export/
3.1.2.3 Processing
Run boda parser:
java -jar boda-bulkcmparser.jar input_dir output_dir
Example:
java -jar C:\HUNTER\Boda\Parsers\ boda-bulkcmparser.jar
C:\Hunter\Boda\Ericsson_3G_XML_in\
C:\Hunter\Boda\Ericsson_3G_XML_out\
3.1.3 ERICSSON 4G
Ericsson BULK CM Export
Launch > Applications > Ericsson > OSS Common Explorer
Wait the “OSS Common Explorer” to load; After it is loaded, we can see the Main Window.
Under Topology, choose the 4G/LTE Technology
Right click the desired element and click “Export...”.

In the “Bulk CM Export” Window, under “Export Details”, configure:
• Export to: where to save the Parameters Export

• File Name: the name of the file. For example, “My4GCmDump.XML”
• Filter Details: “Radio and Transport Network”
• Check “Use Compress Export”.
Note: at this point, it is useful to copy this path and file, because we will use it later.
Click the “Export” button.

In the “Bulk CM Progress” Tab:
Wait until “Status” message is “Successful”, meaning the file were exported successfully.
Page 38 of 85

#Sync all 3G/4G nodes
/opt/ericsson/ddc/util/bin/mibutil -adjust
SubNetwork=ONRM_ROOT_MO_R
#Export Configuration Parameters

/opt/ericsson/nms_umts_wran_bcg/bin/start_rah_export.sh both
/var/opt/ericsson/nms_umts_wran_bcg/files/export/My_3G4G_Bulk
CM_Export.xml
Files exported to: /var/opt/ericsson/nms_umts_wran_bcg/files/export/
3.1.3.3 Processing
Run boda parser:

java -jar boda-bulkcmparser.jar input_dir output_dir
Example:
java -jar C:\HUNTER\Boda\Parsers\boda-bulkcmparser.jar
C:\Hunter\Boda\Ericsson_4G_XML_in\
C:\Hunter\Boda\Ericsson_4G_XML_out\
3.1.4 HUAWEI 2G
3.1.4.1 CM (CFGMML Format)
3.1.4.1.1 Exporting via GUI
Launch “iManager M2000”.

Access Menu: Maintenance > MML Command
RUN command “EXP CFGMML”

Give your file a proper NAME.
The file will be saved at:
Page 39 of 85
“\bam\version_a\ftp\export_cfgmml” or “\bam\version_b\ftp\export_cfgmml”,
depending on current BAM.
3.1.4.1.2 Exporting via CLI
3.1.4.1.3 Processing CM

Run boda parser:
java -jar boda-huaweimmlparser.jar input_dir output_dir

Example:
java -jar C:\HUNTER\Boda\Parsers\boda-huaweimmlparser.jar
C:\Hunter\Boda\Huawei_2G_CFGMML_in\ C:\Hunter\Boda\Huawei_2G_
CFGMML _out\
3.1.5 HUAWEI 3G
3.1.5.1 CM (CFGMML Format)
Huawei CFGMML export procedure.

Access Menu: Maintenance > MML Command.
RUN command “EXP CFGMML”.

Give your file a proper NAME.
The file will be saved at:

“\bam\version_a\ftp\export_cfgmml” or “\bam\version_b\ftp\export_cfgmml”,
depending on current BAM.
Using your ftp User/Password, and any ftp client, download this file to your Computer.
Page 40 of 85
3.1.5.1.3 Processing

Run boda parser:
java -jar boda-huaweimmlparser.jar input_dir output_dir
Example:
java -jar C:\HUNTER\Boda\Parsers\boda-huaweimmlparser.jar
C:\Hunter\Boda\Huawei_3G_CFGMML_in\ C:\Hunter\Boda\
Huawei_3G_ CFGMML _out\
3.1.6 HUAWEI 4G
3.1.6.1 CM (XML Backup Format)

The steps bellow depends on which M2000 version you are using.
For Huawei M2000 Version R12
• Access Menu: Maintenance > Backup Management > NE Backup.

• Select the site you want to backup.
• Download the configuration file from M2000 to your computer.
For Huawei M2000 Version R13 or Above
• Access Menu: “Software Management”

• Access Menu: NE File > NE Backup
• Select one eNodeB, at the left panel tree.
• At the central panel, you can see main window
• At the central panel, select the latest version (backup file) of this eNodeB by clicking
on it.
• Tip: you can see ‘Backup Time’ field.
Page 41 of 85
• Click ‘Download to OSS Client…’ button.

• Save this file at any desired folder at in your computer hard disk.
3.1.6.2 CM (XML GExport Format)
3.1.7 NOKIA 2G
From the Citrix Program Neighborhood select:
Application Set Manager > NetAct OSS Application Set > NetAct StartPage.
From NetAct Start Page select Configuration > CM Operations Manager.

Then in “CM Operations Manager” select Menu File > Export Actual Configuration.
From the export window select BSC's to include in CONFIG file.
Select all object classes, under BSC tab.
Specify export target file name, ensure that the drive selected is for your local machine or
a location that you can ftp the file from.
Finally, under export options select “Include related BTSM objects” and “Include SITE
information”.
Select Start to generate the XML file.
Page 42 of 85
3.1.7.3 Processing
Run boda parser:
java -jar boda-nokiacmdataparser.jar input_dir output_dir
Example:
java -jar C:\HUNTER\Boda\Parsers\boda-nokiacmdataparser.jar
C:\Hunter\Boda\Nokia_2G_XML_in\
C:\Hunter\Boda\Nokia_2G_XML_out\
3.1.8 NOKIA 3G
3.1.8.1 Exporting CM via GUI
Launch “CM Operations Manager” and select Menu File > Export Actual Configuration.
In the “Current Configuration Export” Window:
• Uncheck ALL Objects.

• In the RNC Tab, check All RNC objects.
• In “Export Target”: define the name of output file.
Select Start to generate the XML file.
3.1.8.2 Exporting CM via CLI
3.1.8.3 Processing
Run boda parser:
Example:
Page 43 of 85
3.1.9 NOKIA 4G
Launch “CM Operations Manager” and select Menu File > Export Actual Configuration.
In the “Current Configuration Export” Window:
• Uncheck ALL Objects.

• In the LTE Tab, check All LTE objects.
• In “Export Target”: define the name of output file.
3.1.9.3 Processing
Run boda parser:


Example:
Page 44 of 85
3.1.10 ZTE 2G
Launch “ZTE NetNumen OSS”.
In the left topology tree of NetNumen U31 main interface, right-click the shortcut menu
Corresponding to the created GSM NE agent, select Start.
Right-click the started GSM NE and select Start.

After the NE is started, in the left topology tree of NetNumen U31 main interface, right-click
shortcut menu corresponding to created GSM NE agent, select NE Agent Management >
Configuration Management.
The Configuration Management tab is displayed.
In the configure resource tree window, right-click OMC > GERAN subnet user ID > BSC
Management Element ID > Config Set ID > BSC Function ID > Export Configuration Data >
Export Network Plan Data.
Click Export Network Plan Data, and the Choose MOC to be Exported dialog box appears.
Select the parameter list to be exported, and click Next, as shown in Figure.
In the Choose Attributes of Each MOC to be Exported (RDN Excluded) dialog box, select
attribute of the parameter list to be exported, and click OK. Here, suppose the MOC selected
is IBSCFUNCTION_TABLE.
Select the file type to be exported and click OK. Here, suppose the data is exported to be an
Excel file.
Set the saving path and file name for the exported data and click Save.
3.1.10.3 Processing
3.1.11 ZTE 3G
Launch “ZTE NetNumen OSS”.
Page 45 of 85
In the Topology Management window, right-click the NE agent, and select NE Management
> Configuration Management. The Configuration Management window is displayed.
In the Configuration Resource Tree, click the RNC Managed Element node, and select RNC
Managed Element > Configuration Data Export from the menu. The Data Export dialog box
is displayed.
Select the RNC from the RNC Identity drop-down list.
Select a configuration set from the Config Set Identity drop-down list.
Select XLS from the Export Format Type drop-down list.
Click the Radio Management Object tab (Data Export Dialog Box - Radio Management
Object Tab).
Select the check boxes corresponding to the radio management objects to be exported.
Click Export Data. A dialog box is displayed.
Select the directory where the live radio parameters are to be saved, and then click Save. A
message box is displayed, prompting that the information of the selected objects has been
saved in a compressed Excel file (ZIP file).
3.1.11.3 Processing
3.1.12 ZTE 4G
3.1.12.3 Processing
Page 46 of 85
3.2 IM (Inventory Management)

3.2.1 ERICSSON 2G
3.2.1.1 Inventory BTS

Run command BSM:

bsm_hw_export -H > YourFileName.txt
The resulting file will be exported to the directory where you did run the command.
TIP: Option -H will add Column Header, and also print the Date of Export in the file.
Recommended, but not required for the parser.
Run boda parser:

java -jar boda-ericssonbsmparser.jar input_dir output_file
Example:
java -jar C:\HUNTER\Boda\Parsers\boda-ericssonbsmparser.jar
C:\Hunter\Boda\Ericsson_2G_BSM_in\
C:\Hunter\Boda\Ericsson_2G_BSM_out\bsm.csv
3.2.1.2 Inventory BSC
Page 47 of 85

Launch > Applications > Ericsson > Configuration > Manage Hardware and Software
Inventory
In the Left navigation pane, select 'Network'

Right click ONRM_RootMo, and choose 'Select By Type...'
Select 'BSC,TRC' and click 'OK'
All BSC from this OSS will be selected.
Right click the selected BSC’s and choose 'Hardware Export'.
In the Hardware Export window:
Export XML file name. Filename: Click 'Add file name' button and give a name (for the file
that will be exported), and finally click 'Add'.
Options: choose 'Add time stamp' so the date/time will be appended to the filename.
Click 'OK' and wait for the Job to finish - so the file will be exported.

user@oss> smoaxe
smoaxe> export -hw
smoaxe> exit
user@oss>
Files exported to: /var/opt/ericsson/nms_smo_srv/smo_file_store/Export/AXE/
Run boda parser:

java -jar boda-ericssoninventorybscparser.jar input_dir
output_file
Page 48 of 85
Example:
java -jar C:\HUNTER\Boda\Parsers\boda-
ericssoninventorybscparser.jar
C:\Hunter\Boda\Ericsson_Inventory_in\
C:\Hunter\Boda\Ericsson_Inventory_out\
3.2.2 ERICSSON 3G
3.2.2.1 Inventory RBS/RNC
Inventory
Right click ONRM_ROOT_MO, and choose 'Select By Type...'

Select 'RBS' and click 'OK' (you will repeat this process, replacing RBS by RNC)
All RBS from this OSS will be selected.

Right click the selected ‘RBS’s and choose 'Export'.
In the Export window:
Selected NEs: Select all NEs. TIP: click first NE and type CTRL + SHIFT + END.
Software: Export Software file name. Filename: Click 'Add file name' button and give a name
(for the file that will be exported), and finally click 'Add'.
Hardware: Export Hardware file name. Filename: Click 'Add file name' button and give a
name (for the file that will be exported), and finally click 'Add'.
License: Export License file name. Filename: Click 'Add file name' button and give a name
Page 49 of 85

SHM uses BCG commands directly to export the inventory data, for more information refer
to BCG User Guide Reference. Path for BCG base directory: cd
/opt/ericsson/nms_umts_wran_bc g/bin.
3.2.2.1.2.1 For BB Radios (SHM)

user@oss> cd /opt/ericsson/nms_umts_wran_bcg/bin
user@oss> ./bcgtool.sh -e YourFileName.xml
NOTE: these parameters can be extracted in Bulk CM dump. So, if you have a Bulk CM
Export, you don’t need to export/process this data.
3.2.2.1.2.2 For DU Radios (SMO)

user@oss> smocpp
smocpp> export -hw
smocpp> export -sw
smocpp> export -lic
smocpp> exit
user@oss>
Files exported to: /var/opt/ericsson/nms_smo_srv/smo_file_store/Export/CPP/
Run boda parser:

java -jar boda-ericssoninventoryrbsrncparser.jar input_dir
output_file
Example:
ericssoninventoryrbsrncparser.jar
Page 50 of 85
3.2.3 ERICSSON 4G
3.2.3.1 Inventory ERBS
Inventory
Right click ONRM_ROOT_MO, and choose 'Select By Type...'
Select 'ERBS' and click 'OK'
All ERBS from this OSS will be selected.

Right click the selected ‘ERBS’s and choose 'Export'.
In the Export window:

Selected NEs: Select all NEs. TIP: click first NE and type CTRL + SHIFT + END.
Software: Export Software file name. Filename: Click 'Add file name' button and give a name
Hardware: Export Hardware file name. Filename: Click 'Add file name' button and give a
name (for the file that will be exported), and finally click 'Add'.
License: Export License file name. Filename: Click 'Add file name' button and give a name
Page 51 of 85
Run boda parser:

java -jar boda-ericssoninventoryrbsrncparser.jar input_dir
output_file

Example:
ericssoninventoryrbsrncparser.jar
3.2.4 HUAWEI 2G
3.2.4.1 Huawei Feature: Inventory Management
The inventory file interface allows users to export inventory data from the network to files
at the scheduled time. The files are saved in specified directories for third-party systems to
gain access to the files.
To ensure data transmission security, the M2000 supports SFTP-based file transfer with the
third-party system. For details, see the optional feature WOFD-210100 Encrypted
Transmission.
Benefits: The third-party system can be connected to the M2000 through the inventory file
interface. In this way, the inventory data on the entire network is centrally handled, and
OPEX is reduced. The interface files are featured by simple formats, easy interconnection,
and low R&D costs.
Description: This feature periodically exports the inventory data to files. The third-party
system can obtain files through either of the following methods:
- The M2000 automatically uploads the exported inventory files using FTP to the specified
directory of the third-party system.
- The third-party system actively obtains the inventory files from the M2000 using FTP. After
obtaining the files, the third-party system parses the files to obtain the inventory data.
Page 52 of 85
The inventory file interface supports the following functions:

The file formats of XML, CSV and TXT are supported.
The M2000 provides a default file naming convention.

Users can also customize file naming convention according to the actual requirement.
Supporting centralized management and scheduling of tasks.
Users can set export task names, start time of export tasks, execution period of export tasks,
file formats, and NEs.
The M2000 automatically uploads the exported inventory files using FTP to the specified
directory of the third-party system.
Customers can select an upload mode according to actual requirements.
Dependency: This feature provides the NMS with NE inventory data and it is based on the
feature Inventory Management. To use the feature Inventory File Interface, users need to
purchase the feature Inventory Management.
This feature, together with the feature Automatic File Upload, allows the M2000 to actively
upload inventory files to the third-party system or other systems.
Huawei Inventory export procedure.

Launch “iManager U2000”.
In the "Function Search", do a search for Inventory Management;

Or in the Application Center, choose:
• Application: Trace and Maintenance

• Menu Path: Monitor
• Function: Inventory Management
TIP: You can add it to "My Favorites", so next time access will be faster.
In the left navigation tree, right click 'Inventory Management' and choose 'Export...'
Alternatively, click 'ALT + S' -> 'Export Inventory Data'

In the 'Inventory Export Settings' window:
• In the 'Select NEs' area, select all NEs.
Page 53 of 85
• In the 'Select Objects' area, select all MOC.

IMPORTANT: here we have several options (Accessory, Antenna, Board, BTS,
Cabinet, Host, HostVer, North Bound Interfaces, Port, RRN, Slot, Subrack). One of
the most important is the Board, but you can select all, as it will export to separate
files.
• Export Mode: By MOC
• Export range: All Data
• File Format: CSV
• Encoding: UTF-8
• Export Path: choose the appropriate path to save the file.
Click Export and wait for the files to be exported.
Task Management -> Inventory Data Export.

Simply configure periodicity.

Run boda parser:
java -jar boda-huaweiinventoryparser.jar input_dir output_file
Example:
huaweiinventoryparser.jar C:\Hunter\Boda\Huawei_Inventory_in\
C:\Hunter\Boda\Huawei_Inventory_out\
Page 54 of 85
3.2.5 HUAWEI 3G
See 3.1.4 HUAWEI 2G (same procedure)

3.2.5.3 Processing
3.2.6 HUAWEI 4G

3.2.6.3 Processing
3.2.7 NOKIA 2G
3.2.8 NOKIA 3G
3.2.9 NOKIA 4G
3.2.10 NOKIA 2G
3.2.11 ZTE 3G
3.2.12 ZTE 4G
Page 55 of 85
3.3 PM (Performance Management)

3.3.1 ERICSSON 2G
3.3.2 ERICSSON 3G
3.3.3 ERICSSON 4G
3.3.4 HUAWEI 2G
3.3.5 HUAWEI 3G
3.3.6 HUAWEI 4G
3.3.7 NOKIA 2G
3.3.8 NOKIA 3G
3.3.9 NOKIA 4G
3.3.10 NOKIA 2G
3.3.11 ZTE 3G
3.3.12 ZTE 4G
Page 56 of 85
3.4 FM (Fault Management)

3.4.1 ERICSSON 2G
3.4.2 ERICSSON 3G
3.4.3 ERICSSON 4G
3.4.4 HUAWEI 2G
3.4.5 HUAWEI 3G
3.4.6 HUAWEI 4G
3.4.7 NOKIA 2G
3.4.8 NOKIA 3G
3.4.9 NOKIA 4G
3.4.10 NOKIA 2G
3.4.11 ZTE 3G
3.4.12 ZTE 4G
Page 57 of 85
3.5 TRACE (Logs)

It is easy to understand what a trace is when we look into the following image (for a 3G
network):
We can think of a Trace as information we can get from different points of the network
flow.
There are a lot of trace types: GPEH, PCHR, CHR, MR, SIG, CTUM, CELL TRACE, UETR
Our goal is to develop parser solutions for all 2G, 3G and 4G NSS and BSS elements covering
Ericsson, Huawei, NSN and ZTE interfaces.
The parsers should efficiently transform various standard (ASN.1, XML etc.) and vendor-
based formats to database-ready formats and loads them to database tables efficiently.
They must have:
• Enhanced Error Handling

• Enhanced Log Management
• Secure FTP Connection if Desired
• Multiple Parser Co-Existence for Different Versions of the Same Type.
• Multi-threaded efficient operation.
• Parser Modules for all entities (RNC, BSC, GPEH, TRLOG, ENUM, HLR, MSU, FNR etc.)
Page 58 of 85
3.5.1 ERICSSON 2G
3.5.2 ERICSSON 3G
Ericsson GPEH (General Performance Event Handler) is a recording feature allowing
operators to freely create subscriptions on various system levels.
The GPEH function handles the management and collection of predefined events in the
WCDMA-RAN. these events are either node internal or inter-node as listed below:
• RNC internal events

• RBS internal events
• RRC inter-node events
• NBAP inter-node events
• RANAP inter-node events
• RNSAP inter-node events
Three different types of events are available to the GPEH recording function:
• RNC node internal events

• RNC node external (protocol) events
• RBS node internal events
File Size: GPEH file ROP is 15 minutes and each RNC produces 10 to 15 Gzip files. Total
unzipped files size is ~400 MB. There are about 400 Events in the files. Events could be
filtered in OSS or through Parser Configuration files.
3.5.3 ERICSSON 4G
3.5.4 HUAWEI 2G
3.5.5 HUAWEI 3G
3.5.5.1 What is Huawei CHR?
Huawei CHR is a trace logging feature in RNC and NodeB. It collects call and cell information,
radio measurement and messages for all calls in the network.
3.5.5.2 What does the CHR file contain?

The RNC CHR file contains following information:
Page 59 of 85
• User call log—Information about the call messages such as call setup, RAB setup,
Handover and Call Release.
• Cell Log—User load and Power measurement of the cell over time which includes RTP%
and RTWP.
• Internal RNC log—Internal signaling information which less interesting for RF engineer.
3.5.5.3 Can the CHR collect every call in the RNC?

Unlike the normal call trace, the CHR log contains call trace from every call in the RNC
3.5.5.4 What user call information is captured in the CHR?

The RNC CHR file contains following user call information:
• Call Start information such as RRC Establishment cause, Ec/No, serving cell
andpropagation delay. It also captured IMSI for user identification and IMEI for
phoneidentification.
• Handover information for Soft-Handover, Hard-Handover and Inter-RAT Handoversuch as

target cell and RF measurement
• Radio Bearer setup information for both CS and PS calls such as RAB type andrequested
but-rate.
• Call Release information such as release cause, fault description and error codes.
• RF measurement from Measurement Report such as Active Set and Monitored SetEc/No
and RSCP and GSM cell RSSI
3.5.5.5 How to enable CHR recording?

CHR file is automatically collected in the RNC. The CHR file can be found in the RNC
BAMfolder /bam/common/fam/famlogfmt. There are two type of logs: DEBUG and UCHR.
OnlyUCHR log contains call trace data. The filename would look like this
“BSC0110_[UCHR]00Log20110626170002_20110626170026.log.zip” as for NodeB CHR log,
uses "SET CHRSW" MML command to initiate the recording.
It’s important to say that the CHR is available also for UMTS and you must collect for all
subracks. For example, the file name
“BSC0110_[UCHR]00Log20110626170002_20110626170026.log.zip” belongs for the cells
located only in the subrack 00. If the BSC or RNC have 4 subracks you must collect the logs
Page 60 of 85
for 00, 01, 02 and 03 to guarantee that you will analyse all the cells in the network an all
regions covered by the cells instead of all RNC or BSC.
When you are operating and downloading your CHRs it’s common to file be ordered by
name. In this case all of the files that begins with 00 will appear In front. Its common to
download this group first. But for a good and accuracy analysis it’s important to download
files for all subracks.
3.5.5.6 How can CHR help me to improve the network quality?

Since CHR log contains call information from the real users in the network, it allows
RFEngineer to perform various optimization tasks. Here is the list of optimization tasks that
canbe performed through analyzing CHR file:
• Abnormal Call Release analysis—RF Engineer can go through each dropped orblocked call
in the network and identify the fault result and call sequences that leadto the abnormal
release.
• Missing Neighbour Identification—Using the Detected Set information, RF Engineercan

identify any missing neighbour in the network.
• Pilot Pollution Analysis –The measurement report form all UE allow RF Engineer toidentify
interference in the network.
• Over-shooting cell analysis—Using the propagation delay during the call setuptogether
with the RF measurement, RF Engineer can identify cells that cover toolarge area.
• VIP Analysis—Using the IMSI, RF Engineer can find out the cause of complain fromthe VIP
customer.
• Phone Model Analysis—Operator can study the performance of each phone in

thenetwork
3.5.5.7 What tool can I use to analyze CHR log?

Since CHR file is in a binary format, it requires specialized application to post-process the
filebefore you can analyze the data. Some of these application are as following:
• Huawei Nastar WCDMA (Commercial)
• Huawei Omstar and PCHR (Huawei Internal tools)

• Third-party product such as BODA BTS-CE
Page 61 of 85
3.5.6 HUAWEI 4G
3.5.7 NOKIA 2G
3.5.8 NOKIA 3G
3.5.9 NOKIA 4G
3.5.10 NOKIA 2G
3.5.11 ZTE 3G
3.5.12 ZTE 4G
3.6 Other
3.6.1.1 HUAWEI
3.6.1.2 ERICSSON
3.6.1.3 NOKIA
3.6.1.4 ZTE
Page 62 of 85
4 OSS Operations Support System

Operations Support Systems (OSS) are computer systems used by telecommunications
service providers to manage their networks (e.g., telephone networks). They support
management functions such as network inventory, service provisioning, network
configuration and fault management.
Together with Business Support Systems (BSS), they are used to support various end-to-end
telecommunication services. BSS and OSS have their own data and service responsibilities.
The two systems together are often abbreviated OSS/BSS, BSS/OSS or simply B/OSS.
The acronym OSS is also used in a singular form to refer to all the Operations Support
Systems viewed as a whole system.
Following are the main vendors OSS.
4.1 Ericsson: Network Management System (ENM / OSS-RC)

4.1.1 OSS-RC (OSS Radio and Core)
Today operators manage extremely large networks, varying from Wireline, GSM, CORE to
3G and LTE networks. This could mean that up to 30,000 cells may need to be configured,
troubleshooted and monitored. Do you know how operators manage their network
elements?
Ericsson’s Operation Support System for Radio & Core (OSS-RC) is designed to manage,
configure, monitor, troubleshoot and upgrade all the various networks available i.e:
wireline Core, 2G, 3G and LTE.
The Operations Support System – Radio and Core (OSS-RC) provides a centralized interface
into the radio and core components of Ericsson’s Public Safety LTE network. The OSS-RC
communicates up to the network management system that oversees the complete Public
Safety LTE solution.
The Ericsson OSS-RC is designed with standards-based OSS systems in mind.

Ericsson OSS Services simplify the introduction of new services and technologies while
assuring customer, service and network quality and performance. Through automation and
analytics, Ericsson's OSS services help operators deliver customer experiences while
monetizing infrastructure investments.
Part of Ericsson Systems Integration services portfolio, Ericsson OSS provide a full set of
transformative services, solutions and capabilities.
Page 63 of 85
Ericsson OSS engagement model embraces strategic assessment, planning and design,
implementation, and continuous operation and support. It help evolve operator OSS into
business assets that enable revenue generation, customer experience and operations and
technology migrations.
4.1.2 ENM (Ericsson Network Manager)

Network virtualization, SDN and analytics provide the automation, programmability and
agility needed to deliver complex services and new use cases in 5G networks. Networks
must be flexible and scalable to support massive numbers of devices across different
verticals. As these networks continue to transform, for the foreseeable future the networks
will consist of both legacy and virtualized network functions thereby creating hybrid
networks. To manage these flexible, programmable, scalable, evolving hybrid networks, we
need network management that manages end-to-end across Radio, Transport, and Core
network technologies.
Ericsson Network Manager is an entirely unified Network manager with Universal

applications for all Network technologies and with ease of navigation between apps,
throughout the network and network layers creating a seamless and efficient operation.
More info: https://www.ericsson.com/en/portfolio/digital-services/automated-network-

operations/network-management/network-manager
4.2 Huawei M2000/U2000 and Enterprise Network Management

4.2.1 M2000/U2000 Network Management System
Powerful network management system manages a wide range of elements in wireless
enterprise networks such as eNodeBs (DBS3900), Core Network (eCNS600s), and IPCLKs.
It incorporates many O&M functions from Huawei’s proven LTE carrier-grade management
platform, including plug and play. High integration and reliability reduce TCO and OPEX across the
enterprise.
Other features include express configuration and unified visual management of network
diagnostics, faults, software upgrades, and high performance.
Bring efficiency to converged radio networks and optimize quality, performance, and security with
M2000/U2000.
Page 64 of 85
Huawei is always willing to comply with the commissioning of the equipment, dedicating extra time
in opportunities to achieve the objective and satisfy the needs that arise from a facility of this type.
More info: https://e.huawei.com/en/products/wireless/elte-access/service-engine/m2000
Enterprise Network Management
Hawei ENM provides multi-vendor device management, integrated wired and wireless
management, network traffic management, network quality monitoring and security policy
management. Visible network quality diagnosis and full lifecycle management helps to
enable proactive O&M on wired and wireless networks and rapid fault location. These
functions effectively simplify wired and wireless network O&M and improve O&M
efficiency.
More info: https://e.huawei.com/en/products/software/mgmt-sys/esight/network-management
4.3 Nokia: NetAct

4.3.1 Nokia NetAct Archive Cloud
Is the Nokia agile, innovative and cloud-ready back-up and restore system for the telco
cloud market. The system provides continuous, real-time monitoring capabilities, giving
service providers greater visibility into network conditions at any point in time.
NetAct Archive Cloud answers the most critical challenges of the back-up market in cloud:
data growth, business changes and data analysis and delivery. Today, stored data is under-
leveraged - valuable insights that could improve network operations are not being utilized.
With Nokia NetAct Archive Cloud, service providers can access a rich set of functionalities
that provide in depth information for upper level management systems and secure the data
flow.
More info: https://networks.nokia.com/solutions/netact
Page 65 of 85
4.4 ZTE: NetNumen U31 (CN) Unified OSS Platform

4.4.1 NetNumen U31 (CN)
Established based on ZTE unified OSS platform, NetNumen U31 (CN) realizes centralized
management of each system (GSM/WCDMA/TD-SCDMA/CDMA/Wimax/IMS/LTE) core network
equipment, including MSC, MSC Server, MGW, HLR, SGSN, GGSN, MSCe, PDSN, AGW, AAA, MGCF,
MME, SAE-GW,CG etc.
Besides, CTS (Call Trace System), NetBAS (Network Business Analysis System) etc. products can also
be managed by U31 (CN). U31 (CN) provides failure, topology, performance, configuration, security,
log, trace, assets, system management etc. U31 (CN) locates in EMS layer of TMN module, supports
CORBA, SNMP, FILE, MML etc. northbound interfaces.
Cloud Core Network
More info:
https://www.zte.com.cn/global/products/core_network/intelligent_operation_management/425
487
Page 66 of 85
5 Finding Documentation
Documentation are provided only by the vendors, so each user is responsible to get their
own documentation.
5.1 ERICSSON
For years, Ericsson have used ALEX as it's Products Viewer.
Ericsson creates Libraries, with .alx extensions, that can be both readed by client ALEX
Software or viewed in a web browser.
The Manuals and Instructions includes all technical documentation for the Ericsson
products and is the supply channel for customer and partner use. The contents are unique
for each Portal (CPI profile), and only products included in the commercial agreement for
each customer are displayed.
CPI Extranet is the repository for all technical Product Information needed to handle
Ericsson products throughout the product life cycle. It contains released product
information and information useful during early phases of a system introduction.
ELEX is a modern application based on responsive web design and is optimized for use in
modern browsers and on mobiles.
Getting Started with Active Library Explorer (ALEX) for Windows
Active Library Explorer (ALEX) for Windows ® is a stand-alone application that enables
users to browse Ericsson document libraries on a Windows PC, without any network
connection. The document libraries (xxxx.alx) must be stored on a local disk.
• ALEX can always be opened by selecting All Programs-> ALEXwin from the
Windows Start menu, or by double-clicking on an ALEX library icon in the
Windows file explorer.
• The ALEX for Windows user interface will open in Internet Explorer ®. If this web
browser is not installed, then ALEX will be launched in the default web browser.
Due to differences in the web browsers, some user interface features may work
differently. After starting ALEX, you can also give the ALEX for Windows start
address (http://localhost:9032/alex) to any other web browser.
• Once started, ALEX will look for libraries in the default library directory
(c:\libraries). If the default directory is not available then, the application will ask
you to specify a correct library directory in the Preferences window.
• ALEX takes about a minute to notice any new libraries added to the library
directory. After this, next time the library list is refreshed in the browser window
(right-click and select Refresh), the new library will be included.
Page 67 of 85
• When ALEX is running, it is shown as an icon in the Windows system tray. This is
typically located in the bottom right corner of your screen, but on some systems
you need to click on an up-arrow to see all available icons.
• To open the Preferences window, right-click on the ALEX icon and
select Preferences...
5.2 HUAWEI
https://support.huawei.com/carrierindex/en/anony/index.html
There are a lot of topics:
• Wireless Network
• Carrier Software
• Cloud Core Network
• Data Communication
• Fixed Network Solution
• SingleOSS&NCE
• Network Energy
• Public Cloud
• Intelligent Computing
• Carrier Data Center
• Global Service
Specifically, for Wireless Network, we have:
Page 68 of 85
• LTE FDD(eNodeB/eRAN/NBI/UE/LiTRA)
• LTE TDD(DBS3900 LTE TDD/eRAN TDD/NBI/LTE TDD Terminal)
• SingleRAN(MBSC/MBTS/ECO6910)
• Small Cell(Micro/Pico)
• WCDMA-RAN(RNC/NodeB/RAN Solution)
• GSM-BSS(GBSC/GBTS/GBSS Solution/NBI)
• CDMA-BSS(CBSC/CBTS)
• SingleOSS-MBB(U2020-M/U2020-CME/mAOS/U2000-M/U2000-
CME/PRS/SONMaster)
• And More…
To view Huawei Documentation, you should use HedEx Lite.
HedEx Lite is software used to view, search for, and upgrade electronic documentation for
Huawei products. It is the single-user edition of HedEx and occupies little disk space and
little memory space.
After starting HedEx Lite, you can right-click the HedEx Lite tray icon and choose Help from the
shortcut menu to view the online Help. If HedEx Lite cannot start, you can view the help.chm file
contained in the HedEx Lite software package.
Important: HedEx Lite does not require installation, double-click Startup.exe to start HedEx Lite (if
the software package is compressed, decompress it).
5.3 NOKIA
5.4 ZTE
Page 69 of 85
6 Tips
6.1 Telecom Tips

6.1.1 ERICSSON BB and DU Radios
Ericsson has 2 types of radios: it can be DU Radio or BaseBand Radios
Depending on the type, corresponding information is extracted from different sources.
For example, if you want to get the Inventory Information of the entire network (DU Radios
+ BB Radios) you need to query 2 MOs: AuxPlugInUnit (for DU Radios) and
FieldReplaceableUnit (for BB Radios).
Fortunately, the 2 output (in the above example the MOs) have almost the same columns,
so it’s easy to join it.
6.2 General Tips

6.2.1 Installing Linux on Windows
There are several scenarios in which you may want to install WSL Linux distros.
To do this, you must be using a version of Windows that support the installation.
Note: Command-line shell environments including Cmd, PowerShell, and Linux/WSL distros
are not permitted to run on Windows 10 S Mode. This restriction exists in order to ensure
the integrity and safety goals that S Mode delivers.
Run the command optionalfeatures.exe AND select Windows Subsystem for Linux.
Page 70 of 85
Open Microsoft Store
Search for the Linux version you want. In this case, we choose UBUNTU.
Page 71 of 85
Click Get button and wait for the Download.
When download finish, click Launch button and wait for the installation.
Provide a unix username and password when prompted.
Done!
6.3 ACRYS used in this BOOK

CMD – Windows Command Line Interface
CLI – Command Line Interface
GUI – Graphical User Interface (the Interface, or Client Program you use)
CM – Configuration Management (the Configuration Parameters)
Page 72 of 85
CPP – WCDMA, LTE, Ericsson Connectivity Packet Platform

AXE – GSM, Ericsson Automatic Cross-Connection Equipment (Ericsson digital telephone)
TO BE CONTINUED
6.4 Commands in UNIX

6.4.1 Compress a file
After running some export commands, big files can be generated.
As it is not recommended to download it (via ftp) with original. Instead, compress the file.
gzip NameOFTheFile.ext
But maybe you can get an error, because the file owner can be other (nmsadm). So, you can
use tar (your user will be the owner of the new tar file).
tar -cvf file.tar file.ext
c == Creates a new .tar archive file.
v == Verbosely show the .tar file progress.
f == File name type of the archive file.
But still another problem can appear when trying to tar a very big file: “tar: YourFileName
too large to archive. Use E function modifier.”
Then the solution is to use:

tar -cvEf file.tar file.ext
TIP: in some UNIX GNU (version) the tar command has the ‘z’ option (to zip the archive).
In case you don’t have it, you can use following command in one line (tar and zip):
tar cvf – file.ext | gzip -c > file.tgz

To do the inverse (unzip and untar):
gzip -d < file.tgz | tar xvf -
Note: to create the file, you need to have write permissions. If you still find an error
(Permission denied) you can specify where will your file be created (for example in your
home folder).
Page 73 of 85
tar cvEf - file.xml | gzip -c > /home/ossuser/file.tgz
6.4.2 Getting information

For example, when you need to get from several files, and add it to another file
grep Current *.log > result.txt
6.5 Commands in ERICSSON

There are several ways to use commands in Ericsson. One of the most common is using
AMOS / Moshell - an extremely powerful command line utility (use it carefully).
6.5.1 MOSHELL
AMOS and Moshell commands are the same, except the lab commands and internal
ericsson commands which are not available in AMOS.
Run the UNIX command that will launch AMOS against the specified Network Element:
moshell <node name>

TIP: Alternatively, you can use <node ip address> instead of <node name>
WHEN YOU RUN MOSHELL, it will open a window, and you’ll be “connected” to the element.
There you can run commands, to list/view the information you need.
6.5.1.1 Ipdatabase
The ipdatabase is a file where you can store for each node of the network:
nodename (arbitrary)
ipaddress or dns name

password (optional)
It's recommended to save it as: /home/youruser/moshell/sitefiles/ipdatabase
6.5.1.2 Main Moshell commands

There's plenty of commands, here we'll show only some important examples.
Page 74 of 85
• get/lget: This command fetches one or several attributes from one or several MO's.
• kget: “kget” is identical to “get” except that the output has slightly different format
in order to allow importing of data in some external tools. “kget” should mainly be
used when taking MO dumps (lt all ; kget)
• lt/ltc: Load MO tree (full or partial) and build proxy table.
• lt all: Load MO tree for all
• run CommandFile.txt: Run a command file in moshell format
This applies to commands such as "lt/ltc", "lc/lcc", "del", "bl", "set", where
confirmation is automatically entered when running a command file.
Comments can be put in the command file using the # sign. The command file should
be one command per line
6.5.2 MOBATCH
Mobatch is used for running moshell sessions on several nodes in parallel.
The list of nodes must be defined in a “sitefile”.
Each node can be listed by its node name.

There is no limit on how many nodes can be listed inside a sitefile.
Mobatch will execute one moshell session per node listed in the sitefile.
Up to 10 sessions will run in parallel at any time. This limit can be changed with the “-p”
option
Usage: mobatch SiteFile.txt CommandFile.txt LogDirectory
WHEN YOU RUN MOBATCH, it will run the commands in the commands file for each
element in the sites file. The output will be save in another directory (it will be shown by
the command where it will be stored) and you will need to parse it.
6.5.2.1 Example of SiteFile.txt

RNC1
RNC2
NodeB1
NodeB2
Page 75 of 85
6.5.2.2 Example of CommandFile.txt

lt all
inv
exit
6.5.2.3 Mobatch Examples

• Print all CV’s from all sites: mobatch /home/user/sites.txt 'lt all; cvcu'
• Print history alarms from all sites: mobatch /home/user/sites.txt 'lt all; lga -s
20090404'
• Print electrical tilt from all sites: mobatch /home/user/sites.txt 'lt all; get .
electricalAntennaTilt '
• Print E1 state from all sites: mobatch /home/user/sites.txt 'lt all; st e1'
As we can see, mobatch is extremely powerful. Here we will show the main commands you
need, for do each job.
6.5.3 Passwords
Some default passwords:
RNC -> rnc
Nodes -> rbs
Of course, it can vary, but this is default.
6.6 Naming Suggestions for Dump Files

When we export the raw dump files (for example CM or PM), we can choose the ‘name’ we
want for them.
Here you find some suggestions, aiming to organize a little bit.
The best on, is always to add timestamp on it. And use the aammdd: year four digit, month
2 digit, day 2 digit.
Page 76 of 85
6.6.1 Ericsson GSM CM {TXT}

cm + oss_name + CNAI_v2 + aaaammdd
Example: cm_oss_gsm_1_CNAI_v2_20181210.txt
6.6.2 Ericsson WCDMA / LTE CM {XML}

cm + oss_name + BULK + aaaammdd
Example: cm_oss_lte_1_BULK_20181210.xml
6.6.3 Huawei GSM / WCDMA / LTE CM {XML}

Huawei GExport files are exported by the system (U2000) and have its proper naming – no
need to change.
GExport...<default>
6.6.4 Huawei GSM / WCDMA / LTE INV {CSV}

Huawei Inventory dump via GUI: files are automatically generated by U2000, so there’s no
need to change.
One suggestion is to add a prefix, with the oss_name.
6.6.5 Ericsson GSM INV {TXT}
Page 77 of 85
7 Troubleshooting
7.1 Error message: “Error checking TLS connection”

Question: I had an older version of bts-ce installed (bts-ce-1.0.22), and I have tried to
reinstall the new release V2.0.0-rc8.
But I am getting error
"Error checking TLS connection: Error checking and/or regenerating the certs: There was an
error validating certificates for host “192.168.99.100:2376”: dial tcp 192.168.99.100:2376:
connectex: No connection could be made because the target machine actively refused it.
You can attempt to regenerate them using ‘docker-machine regenerate-certs [name]’.
Be advised that this will trigger a Docker daemon restart which might stop running
containers.
ERROR: Couldn’t connect to Docker daemon - you might need to run docker-machine start
default."
Answer: You should first uninstall (remove) any previous version, then you can install the
new version.
From Windows CMD, go to the folder with the previous installation and run command:
bts rm
7.2 Error Message: “Login attempt failed”

Question: After trying to login with correct username and password, I receive an error
"Login attempt failed".
Answer:
Go to CMD and open kitematic
From bts-ce folder, via command prompt, run:

bts logs bts-database
Then you can look for the error message.
Page 78 of 85
This error points to missing user called airflow. This means the database setup script
(mediation/db/create_bts_database.sh) was not run successfully.
This is caused by this file having windows line endings(\r\n). It should have unix style line
endings (\r).
There 2 ways to fix this.
Option 1:
1. Open the file bts-ce/db/setup/create_bts_database.sh using Notepad++.
2. Show all characters.
3. Replace the windows style line endings (\r\n) to Unix style line endings (\n)
Option 2:
1. Launch the Docker QuickStart Terminal

2. Go to the bts installation folder from the terminal
3. Run dos2unix mediation/db/setup/create_bts_database.sh
Page 79 of 85
7.3 Error Message: “Argument 'win \ Setup.ps1' … does not exist”

Question: After running the command:
bts setup
The following message is displayed (after "Creating default folders…”):
“The argument 'win \ Setup.ps1' for the -File parameter does not exist. Provide the path to
an existing '.ps1' file as an argument to the -File parameter.”
Answer: Checking the “win” folder, there were 4 files.
A normal installation has 5 files. We can see the error is due file “Setup.ps1” missing.
So, please download again, and extract it again, to make sure you have all the needed files.
Note: this problem may be caused by Antivirus (that put the file in quarantine). To solve
this, create exceptions for the bts folder.
7.4 Error message: “Database is still being setup”

Question: After I installed everything, I try to login and receive following error:
“Database is still being setup”
Page 80 of 85
Answer: this is normal.
Just wait some time, for the tables to be created at database.

If you want to see the progress, run the command:
bts logs bts-api
7.5 Error message: “This website could not be found.”

Question: Yesterday I installed bts-ce normally (it was working). Now (today) I am receiving
an error message:
"This website could not be found. Error Code: INET_E_RESOURCE_NOT_FOUND"
Answer: This happens because the tool is NOT running.
To fix this, you should start, running command:

bts start
Currently it does not automatically restart on computer startup (although it can be done).
But let's leave this way for now: when you want to use the tool, you manually start it. Later
we can define a better way to set this.
Page 81 of 85
7.6 Error message: “This site can’t be reached.”

Question: I am receiving an error message:
“This site can’t be reached 192.168.99.100 took too long to respond.

Try:
• Checking the connection

• Checking the proxy and the firewall
• Running Windows Network Diagnostics
ERR_CONNECTION_TIMED_OUT”
Answer: Same issue as Error message: “This website could not be found.”
7.7 Airflow not working

Question: Whe I open Airflow, it seem to be “off”
Page 82 of 85
Answer: tbd
Page 83 of 85
8 Roadmap
Our project has been done by years.
8.1 Background
1996 – 1990
• Initial phase.
• Simply distribution list with engineers from some countries.
2000 – 2009
• Launch of the blog (www.telecomhall.com)

• Focus on writing articles to help the community.
2010 – 2016
• Focus on “homemade” tools (Hunter Suite) to help each professional of the

community is their daily work.
2016 – 2018
• Launch of the forum (www.telecomhall.net)

• Boda: Focus on parsers and professional development of an opensource tool.
8.2 2019
Month Roadmap
January • Created Draft of Handbook
February • Created group of Experts
March • Launched bts-ce (for CM)
Where we are: all experts are expected to have the bts-ce installed.
Discussions ongoing in the group.
Page 84 of 85
8.2.1 List of planned functionalities (CM Module)

• Parameter Report (testing)
• Baseline Generation (testing)
• Inconsistency Reports -- BCCH, PCI, PSC
• Scripts (MML) Generation
• GIS -- Site/Cell Map
• Network Dump Comparison
8.2.2 List of planned functionalities (PM Module)

PM Report
8.2.3 List of planned functionalities (Trace Module)

Cell Trace processing
Optimization: coverage analysis, overshooting/pollution
8.2.4 List of planned functionalities (All Modules)

Crossing information from all modules.
Page 85 of 85

Telecomhall Experts PDF Free

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Telecomhall Experts PDF Free

Uploaded by

Copyright:

Available Formats

09/04/2019

A Practical Guide for Telecom

2.8 GitHub ......................................................................................................................... 29

3.2.10 NOKIA 2G ............................................................................................................ 55

3.5.2 ERICSSON 3G ....................................................................................................... 59

6.2.1 Installing Linux on Windows .............................................................................. 70

1.2 The Structure of the Book

1.3.1 Who is it headed for?

1.3.2 How can I support/participate of this project?

There are different ways you can get involved:

• You can contribute code to the project.

1.4 Hunter Methodology

1.4.1 Exporting Network Data

So, in this initial release, we’re going to have BTS-CE CM.

2.2 BTS-CE CM Features/Functionalities

ZTE and Nokia will be added in the next release.

A detailed roadmap will be shared in a different post.

2.3 Supported vendor CM dump formats

• Ericsson: CNAIV2 for 2G, bullkcm XML for 3G and 4G

2.4 Minimum Requirements

2.5 Built With

2.6 Very Important Concepts

2.6.1 What is a Virtual Machine?

IMPORTANT: Remember a VM uses a lot of memory an space. So make sure your

2.6.2 What is a Container?

2.6.3 Containers and Virtual Machines Together

2.6.3.2 VIRTUAL MACHINES

2.6.4 What is Docker?

And importantly, Docker is open source.

Docker containers that run on Docker Engine:

2.6.5 What Is Hyper-V?

• Hyper-V for Windows Servers

Hyper-V on Windows 10 is the version that runs on most computers.

2.6.6 What is HyperKit?

2.6.7 What is Virtualbox?

Of course, performance will be degraded compared to native Hyper-V or Hyperkit - because

2.6.8 Other concepts

Basically, your computer needs:

• To be able to support virtualization;

Check Windows 10 Build Version:

2.7.1 Enable/Disable Virtualization in BIOS

Click Advanced > Processor Configuration.

2.7.2 Enable/Disable Hyper-V

Uncheck Hyper-V settings, and click OK.

To enable, do the opposite: check Hyper-V.

2.7.3 Install Oracle VM VirtualBox

Note: Check if your computer is 32 or 64 bits.

In the VirtualBox Builds page, click on Windows hosts.

2.7.4 Install Docker

Depending on the requirements your computer met, you must install:

• Docker Desktop for Windows/Mac

2.7.4.1 Install Docker Desktop for Windows

Install Docker on Windows 10

Click Yes when Windows ask you for permission.

Maybe you find some problems due to lack of memory.

2.7.4.2 Install Docker Desktop for Mac

• Double-click Docker.app in the Applications folder to start Docker. ...

2.7.4.3 Install Docker Toolbox for Windows/Mac

And proceed with installation.

2.7.4.4 Install docker-ce and docker-compose on Linux (Ubuntu)

And proceed with installation.

Note: for other Unix OS, visit: https://docs.docker.com/v17.12/install/#server

2.7.5 Download Git (only if you want to contribute code)