You are on page 1of 50

CHT Co. Ltd.

Engineering Support Service


RAN Operation Consultancy

Introduction to MegaMon and Emil
Carlo Magay
13
th
Flr. Ai Guo Building
July-2011
Copyright Nokia Siemens Network. This material, including documentation and any related computer programs, is
protected by copyright controlled by Nokia Siemens Networks. All rights are reserved. Copying, including
reproducing, storing, adapting or translating, any or all of this material requires the prior written consent of Nokia. This
material also contains confidential information, which may not be disclosed to others without the prior written consent
of Nokia Siemens Networks
Soc Classification level
2 Nokia Siemens Networks / CMagay
Workshop Scope
MegaMon
Description
Installation
Usage
Emil (L3 Analyzer)
Description
Usage


Soc Classification level
3 Nokia Siemens Networks / CMagay
RNC Data Collector Background
Network element usually provides measurements, alarms, counter
updates etc.
This is mostly statistical information, average over the time period
or just an indication of some phenomenon
Much more data is needed for network optimization,
troubleshooting, finding the actual root causes
Network element capacity i.e. processing power, memory etc. is
not enough to capture and analyze all the data
External servers are needed for detailed network monitoring
Soc Classification level
4 Nokia Siemens Networks / CMagay
RNC
CS-Core
PS-Core
WBTS
WBTS
WBTS
WBTS
WBTS
WBTS
Iub
Iub
Iu-CS
Iu-CS
Iu-PS
Iu-PS
Test UE
Test UE
Test UE
Iur
RNC (Data) Collector
RNC (Data) Collector
Trace
Trace
Trace
RNC
RNC (Data) Collector
Soc Classification level
5 Nokia Siemens Networks / CMagay
RNC Data Collector Description
The RNC Data Collector solution, consists of two main functionalities:
Data Collector (Megamon)
Data Analyzer/L3 Viewer (Emil).
The solution involves three (3) functional processes, as follows:
Interface process operating within the RNC
Data Collection process for gathering data from interface process
Data Analyzer process covering data parsing from the Data Collector
Next slides presents the basic configuration environment for the Megamon,
showing the interworking functions between the MegaMon server and its pair RNC.
Note that one (1) MegaMon server is needed for every RNC.

Soc Classification level
6 Nokia Siemens Networks / CMagay
ICSU
RSMU
RNC
100 Mb Ethernet connection
1 Gb Ethernet connection
Private LAN
RNC Data collector, basic configuration
Data
Collector
Data
Analyzer
RNC (Data) Collector
Soc Classification level
7 Nokia Siemens Networks / CMagay
ICSU
RSMU
RNC
100 Mb Ethernet connection
1 Gb Ethernet connection
Private LAN
RNC Data Collector + local support for L3-Viewer
Data
Collector
Data
Analyzer
RNC (Data) Collector
HD
Windows based
L3-Viewer
All data are written
also to ring buffer
2 - 4 TB
Soc Classification level
8 Nokia Siemens Networks / CMagay
ICSU
RSMU
RNC
100 Mb Ethernet connection
1 Gb Ethernet connection
Private LAN
RNC data collector, with Windows L3-Viewer
Data
Collector
Analyzer
L3-Viewer
RNC (Data) Collector
HD
Windows based
L3-Viewer
All traces are written
to disk
2 - 4 TB
Remote desktop
Soc Classification level
9 Nokia Siemens Networks / CMagay
ICSU
RSMU
RNC
100 Mb Ethernet connection
1 Gb Ethernet connection
MessageData collector
(Megamon )server
Office LAN
Emil
L3-Analyzer
Local usage
OMU
Data Collector (Megamon) & Layer-3 Analyzer (Emil)
Soc Classification level
10 Nokia Siemens Networks / CMagay
Process GIVAXI is
located in each unit and
it packs and sends all
monitored message
data to Data Collector
Data Collector (MegaMon)
Emil
Data Collector
(MegaMon) stores the
data to local HDD. Local
L3-Analyzer (Emil) can
be also connected to
MegaMon Server
Soc Classification level
11 Nokia Siemens Networks / CMagay
HP DL380G7 Server Specifications (Megamon server)
Processor family
Intel Xeon 5600 series
Number of processors
2
Processor core available
6 or 4 or 2
Memory
Maximum memory
384 GB
Memory slots
18 DIMM slots
Memory type
PC3-10600R RDIMMs DDR3 or PC3-10600E UDIMMs DDR3
I/O
Expansion slots
6
Network Controller
(2) 1GbE NC382i Multifunction 2 Ports
Storage
Maximum drive bays
(16) SFF SAS/SATA
with optional second drive cage
Supported drives
Hot plug 2.5-inch SAS
Hot plug 2.5-inch SATA
Hot plug 3.5-inch SAS
Hot plug 3.5-inch SATA
Storage Controller
(1) Smart Array P410i Integrated
Soc Classification level
12 Nokia Siemens Networks / CMagay
RNC Data Collector Interfaces (HP DL380G7)
Back
Front
Soc Classification level
13 Nokia Siemens Networks / CMagay
Physical cable equipping positions and SW port
connection coordinates
Switch installation layout
picture and routing of
CHUS cables
Soc Classification level
14 Nokia Siemens Networks / CMagay
CHUS Ethernet cables for Megamon in RNC2600 RNAC
cabinet
CHUS Ethernet cables for
Megamon in RNAC cabinet
CHUS Ethernet cables for
Megamon in RNBC cabinet
Soc Classification level
15 Nokia Siemens Networks / CMagay
RNC 2600 Step 1
HP Server IP Address 10.10.10.6
RSMU 10.10.10.9
ICSU-0 10.10.10.10
ICSU-1 10.10.10.11
<etc>
ICSU-13 10.10.10.23
Soc Classification level
16 Nokia Siemens Networks / CMagay
37
HP Server IP Address 10.10.10.6
ICSU-14 10.10.10.24
ICSU-15 10.10.10.25
ICSU-16 10.10.10.26
<etc>
ICSU-25 10.10.10.35
RNC 2600 Step 2
Soc Classification level
17 Nokia Siemens Networks / CMagay
37 37
HP Server IP Address 10.10.10.6
ICSU-26 10.10.10.36
ICSU-27 10.10.10.37
ICSU-28 10.10.10.38
<etc>
ICSU-37 10.10.10.47
RNC 2600 Step 3
Soc Classification level
18 Nokia Siemens Networks / CMagay
CHT 3G Megamon for RN231 & RN232
OAM IP Address and SW Port Allocation
RN231 Collector
2U3OAMSW10
Slot 3 / Port 28
10.86.254.191
RN231 MegaMon SW
10.10.10.6
RN232 Collector
2U3OAMSW11
Slot 3 / Port 28
10.86.254.192
RN232 MegaMon SW
10.10.10.6
Soc Classification level
19 Nokia Siemens Networks / CMagay
MegaMon Installation (CHT 2U3)
RN231 MegaMon Server
RN232 MegaMon Server
RN231 Ethernet Switch
RN232 Ethernet Switch
Backplane Ethernet Cables
RJ-45 Patch Panels
Soc Classification level
20 Nokia Siemens Networks
MegaMon Setup
Soc Classification level
21 Nokia Siemens Networks / CMagay
Step1. Set up the RNC for MegaMon
Temporarily block alarms 3053 ETHERNET INTERFACE FAILURE and 3238 ETHERNET
INTERFACE DOWN for ICSU and RSMU units.
Prepare an external LAN switch with enough ports for all ICSU and RSMU units and the
MegaMon PC, and enough Ethernet cables to connect them.
Connect all ICSUs and RSMUs and the MegaMon Server to the LAN switch with the
cables.
There is no need to connect the LAN switch to the local site LAN.





Soc Classification level
22 Nokia Siemens Networks / CMagay
Step 2. Configure the private network 10.10.10.x
The following IP addresses are recommended:
MegaMon PC 10.10.10.6 ( and10.10.10.7 for 2
nd
Eth interface)
RSMU 10.10.10.9
ICSU-0 10.10.10.10
ICSU-1 10.10.10.11

ICSU-37 10.10.10.47

Use ZQRN command to configure the EL0 IP address in each computer unit:

ZQRN:RSMU:EL0:10.10.10.9,L:25::;
ZQRN:ICSU,0:EL0:10.10.10.10,P:25::;



Soc Classification level
23 Nokia Siemens Networks / CMagay
Megamon STEP 3: Check that GIVAXI-process is
running
Check that the version of GIVAXI1X is 1.15-0 or newer, otherwise it must be updated.
ZWQV:<unit>,<index>:GIVAXI1X:;
Log into the RNC via management LAN.
ZQRS:<unit>,<index>;
There should be a port *.8019 on listening, if not then give the following command to
each ICSU and RSMU:
ZDDE:<unit>,<index>:ZODR:728; and wait 20 seconds.
If the EL0 interfaces created for Megamon monitoring are in DOWN state, change
them to UP state with ZQRN MML command:
ZQRN:ICSU,0:EL0:::::UP;
ZQRN:ICSU,1:EL0:::::UP;
<etc>
Soc Classification level
24 Nokia Siemens Networks / CMagay
MegaMon Main Window
Shortcut buttons
Launches the commonly
used actions for MegaMon
Units Window
Displays unit status and
information. User can select
which units to monitor and what
monitoring filters to be used.
Event Log Window
Displays event logs in real.
Log entries are also stored in the
same directory as the monitoring
logs.
License information bar
Displays the license information
Soc Classification level
25 Nokia Siemens Networks / CMagay
Megamon Installation Folder
Copy the license file in the MegaMon folder
Soc Classification level
26 Nokia Siemens Networks / CMagay
Set the License File
Set License file (.mlc) located in the MegaMon folder
Soc Classification level
27 Nokia Siemens Networks / CMagay
Setting Control Connection Parameters
Setup Control Connection
Set the Name and IP address

Name RNC name (will also be used for the output filename)
Address IP address of the control unit (RSMU)
Soc Classification level
28 Nokia Siemens Networks / CMagay
Setting Output Files
Setup Set output files
Time Based
Collects logs at fixed time intervals
Size Limit
0.0 MB means the output file size is not limited
Settings for older data removal
and disk space management
Directory where the monitoring files will be saved
Soc Classification level
29 Nokia Siemens Networks / CMagay
Set the Monitoring Filter Condition
Default settings can be used but monitoring conditions
can be manually edited if necessary.
Setup Filter Condition
Default Monitored Families:
04FD RRC (RRC PRB)
509 IUV (RANAP PRB)
508 IUR (RNSAP PRB)
4B7 NRM (Transport Resource Manager PRB)
Soc Classification level
30 Nokia Siemens Networks / CMagay
Setting Special Parameters
Setup Special Parameters
Change TelnetHeartBeat to 300 (ms)
Set if using a 2
nd
Ethernet connection to MegaMon
Switch
Soc Classification level
31 Nokia Siemens Networks / CMagay
Log-Fetching Options
Default settings can be used
Soc Classification level
32 Nokia Siemens Networks / CMagay
Opening the Connection to RNC
Get Units
Connects to the RNC units where the GIVAXI
module is running
Soc Classification level
33 Nokia Siemens Networks / CMagay
Unit and Filter Selection
Select Units and Filters
From which units logs will be collected
and what filter will be applied.
1
2
3
Soc Classification level
34 Nokia Siemens Networks / CMagay
Starting the Log Collection
Status changes to OK after setting the filters are set
Click start to start log collection
Soc Classification level
35 Nokia Siemens Networks / CMagay
Check that Log Collection is running
Displays the incoming
and handling data
Soc Classification level
36 Nokia Siemens Networks / CMagay
Check the Megamon Output Folder
One folder is created for each monitoring interval
One file is generated for each
monitored unit per monitoring interval
Soc Classification level
37 Nokia Siemens Networks
Layer-3 Analyzer (Emil)

Soc Classification level
38 Nokia Siemens Networks / CMagay
Layer-3 Analyzer (EMIL) can get the real-time
Megamon logs from Megamon Server
Real time receiving logs from MegaMon Server to your PC (L3-Analyzer)
10.86.254.191 is MegaMon Server IP
address (example) >> Your PC(L3-
Analyzer) can access MegaMon Server
remotely via DCN.
Logs can also be downloaded from the
MegaMon server
Soc Classification level
39 Nokia Siemens Networks / CMagay
Layer-3 Analyzer (Emil-tool) - Overview
The Emil is a tool for opening layer-3 messages, which are collected directly from Network
element. The real time usage is also possible (version 2.1)
The Emil can open several kinds of log files. At the moment these types: .BIN (DX Binary)
or .MGA (MegaMon) or .LOG (DX ASCII)
Files may be opened by drag-and-drop or from the File menu. BIN, MGA and LOG are
associated with Emil at setup so double click of such files is also possible, even straight from
Outlook.
If file extension is anything else than BIN or MGA then file will be opened as an ASCII-log.
Emil can save any log as a DX ASCII log.
Emil needs license file to open the logs.

Soc Classification level
40 Nokia Siemens Networks / CMagay
Emil - views
Tool operates in Windows
environment
Can be used to parse huge
amount of message monitoring
User friendly graphical interface
Several filtering possibilities to
handle monitoring data, for
example call filtering which shows
every call in own row
Uses user defined sack directory
to open messages
Opens messages in clear text and
decodes them if needed
Statistics
window
L3 view
Detailed
analysis
Note) Can trace and analyze the problematic call > save it (*.emil) > Send it to NSN Technical Support to further analysis
Soc Classification level
41 Nokia Siemens Networks / CMagay
One call, one row
Parsing of huge
amount of data
Quick view of different
types of call cases and
failures
Note) Can trace and analyze the problematic call > save it (*.emil) > Send it to NSN Technical Support to further analysis
Double clicking a row
opens to the L3 viewer
for that trace
Soc Classification level
42 Nokia Siemens Networks / CMagay
One call, L3 view
Different interfaces and their corresponding
messages are shown in one window
Note) Can trace and analyze the problematic call > save it (*.emil) > Send it to NSN Technical Support to further analysis
Soc Classification level
43 Nokia Siemens Networks / CMagay
Content of L3-Message
The detailed content of
NAS-Message
Double-clicking will
display the details of
the message.
Note) Can trace and analyze the problematic call > save it (*.emil) > Send it to NSN Technical Support to further analysis
Soc Classification level
44 Nokia Siemens Networks / CMagay
Measurements and reports
Statistics and reports can
be generated based on the
data

CPICH EcNo
CPICH RSCP
RL TX Power
Branch Throughput.
Note) Can trace and analyze the problematic call > save it (*.emil) > Send it to NSN Technical Support to further analysis
Soc Classification level
45 Nokia Siemens Networks / CMagay
Open Emil log
Can sort by Establishment Cause / RRC Failure/ RAB
Type / RAB Ticket / PS Ticket etc.
Can sort by IMSI / Ue model / Ue model by IMEI / Ue Rel
Can sort by IMSI / TMSI / UE Model by capability / UE
Model by IMEI / RNTI etc.
Note) Can trace and analyze the problematic call > save it (*.emil) > Send it to NSN Technical Support to further analysis
Soc Classification level
46 Nokia Siemens Networks / CMagay
Open Emil log Tracing the ROOT cause
Can trace ROOT Cause of Release Cause / RRC Failure = RNC Internal or Radio Interface
Can trace the detailed Root cause by
opening Trace ID=2215 in L3 Analyzer
Note) Can trace and analyze the problematic call > save it (*.emil) > Send it to NSN Technical Support to further analysis
Soc Classification level
47 Nokia Siemens Networks / CMagay
Open Emil log Trace Problematic Subscriber using IMSI
Filters
Can use the IMSI filter to filter in the
problematic IMSI (Ex: 466923201417189)
from Emil log in L3 Analyzer
After activating the IMSI filter, open or
reparse the ICSU log
1
2
3
Note) Can trace and analyze the problematic call > save it (*.emil) > Send it to NSN Technical Support to further analysis
4
Soc Classification level
48 Nokia Siemens Networks / CMagay
Open Emil log Trace Problematic Subscriber using
IMSI Filters
After activating the IMSI filter, only traces from the filtered IMSI is visible
Soc Classification level
49 Nokia Siemens Networks / CMagay
Traces can be saved in HTML or CSV format
L3 messages can be displayed including the message details
Soc Classification level
50 Nokia Siemens Networks / CMagay
Thank you!