CHT Co. Ltd. Engineering Support Service RAN Operation Consultancy Introduction to MegaMon and Emil Carlo Magay 13th 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
Workshop Scope • MegaMon – Description – Installation – Usage • Emil (L3 Analyz Analyzer) er) – Description – Usage
Workshop Scope • MegaMon – Description – Installation – Usage • Emil (L3 Analyz Analyzer) er) – Description – Usage
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
RNC (Data) Collector
RNC (Data) Collector
Trace
Iu-PS
WBTS Iub Test UE
RNC
Iu-CS
WBTS
CS-Core
WBTS
Test UE
Iur
Trace PS-Core WBTS WBTS
Iu-CS Iub
RNC
Iu-PS
Test UE
Trace WBTS
RNC (Data) Collector
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 f unctional 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 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.
RNC Data collector, basic configuration
RNC
Private LAN ICSU
RSMU
100 Mb Ethernet connection 1 Gb Ethernet connection
RNC (Data) Collector Data
Data
Collector
Analyzer
RNC Data Collector + local support for L3-Viewer
RNC
Private LAN RNC (Data) Collector
ICSU
RSMU
All data are written also to ring buffer
Data
Data
Collector
Analyzer
HD 2 - 4 TB
Windows based L3-Viewer
100 Mb Ethernet connection 1 Gb Ethernet connection
RNC data collector, with Windows L3-Viewer
RNC
Private LAN RNC (Data) Collector
ICSU
Data
Analyzer
Collector
L3-Viewer
All traces are written
RSMU
to disk
Remote desktop
HD 2 - 4 TB
Windows based L3-Viewer
100 Mb Ethernet connection 1 Gb Ethernet connection
Data Collector (Megamon) & Layer-3 Analyzer (Emil) MessageData collector (Megamon )server RNC
ICSU
Emil
L3-Analyzer Local usage
Office” LAN
“
RSMU OMU
100 Mb Ethernet connection 1 Gb Ethernet connection
Data Collector (MegaMon)
Emil
Process GIVAXI is located in each unit and it packs and sends all monitored message data to Data Collector
Data Collector (MegaMon) stores the data to local HDD. Local L3-Analyzer (Emil) can be also connected to MegaMon Server
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
RNC Data Collector Interfaces (HP DL380G7) Back
Front
Physical cable equipping positions and SW port connection coordinates
Switch installation layout picture and routing of CHUS cables
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
RNC 2600 Step 1 RSMU ICSU-0 ICSU-1 ICSU-13
10.10.10.9 10.10.10.10 10.10.10.11 10.10.10.23
HP Server IP Address 10.10.10.6
RNC 2600 Step 2 ICSU-14 ICSU-15 ICSU-16 ICSU-25
10.10.10.24 10.10.10.25 10.10.10.26 10.10.10.35
HP Server IP Address 10.10.10.6 37
RNC 2600 Step 3 HP Server IP Address 10.10.10.6
ICSU-26 ICSU-27 ICSU-28 ICSU-37
37
10.10.10.36 10.10.10.37 10.10.10.38 10.10.10.47
CHT 3G Megamon for RN231 & RN232 OAM IP Address and SW Port Allocation
RN231 MegaMon SW
RN231 Collector 10.86.254.191
10.10.10.6
2U3OAMSW10 Slot 3 / Port 28
RN232 MegaMon SW
RN232 Collector 10.10.10.6
10.86.254.192
2U3OAMSW11 Slot 3 / Port 28
MegaMon Installation (CHT 2U3)
RN232 Ethernet Switch
RN232 MegaMon Server
Backplane Ethernet Cables
RN231 Ethernet Switch
RN231 MegaMon Server RJ-45 Patch Panels
MegaMon Setup
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.
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 2nd 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::;
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:,:GIVAXI1X:;
• Log into the RNC via management LAN. ZQRS:,;
• There should be a port *.8019 on listening, if not then give the following command to each ICSU and RSMU: ZDDE:,:”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;
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
Megamon Installation Folder
Copy the license file in the MegaMon folder
Set the License File Set License file (.mlc) located in the MegaMon folder
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)
Setting Output Files
Setup → Set output files Directory where the monitoring files will be saved
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 r emoval and disk space management
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)
Setting Special Parameters Setup → Special Parameters
Set if using a 2 nd Ethernet connection to MegaMon Switch Change TelnetHeartBeat to 300 (ms)
Log-Fetching Options Default settings can be used
Opening the Connection to RNC
Get Units Connects to the RNC units where t he GIVAXI module is running
Unit and Filter Selection 3
2 1
Select Units and Filters From which units logs will be collected and what filter will be applied.
Starting the Log Collection
Click start to start log collection
Status changes to OK after setting the filters are set
Check that Log Collection is running
Displays the incoming and handling data
Check the Megamon Output Folder One folder is created for each monitoring interval
One file is generated for each monitored unit per monitoring interval
Layer-3 Analyzer (Emil)
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
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 .
Emil - views
Statistics window
L3 view
• 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
Note) Can trace and analyze “the problematic call” > save it (*.emil) > Send it to NSN Technical Support to further analysis
Detailed analysis
One call, one row • Parsing of huge amount of data • Quick view of different types of call cases and failures
Double clicking a row opens to the L3 viewer for that trace
Note) Can trace and analyze “the problematic call” > save it (*.emil) > Send it to NSN Technical Support to further analysis
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
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
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
Open Emil log
Can sort by Establishment Cause / RRC Failure/ RAB Type / RAB Ticket / PS Ticket etc.
Can sort by IMSI / TMSI / UE Model by capability / UE Model by IMEI / RNTI etc.
Can sort by IMSI / Ue model / Ue model by IMEI / Ue Rel
Note) Can trace and analyze “the problematic call” > save it (*.emil) > Send it to NSN Technical Support to further analysis
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
Open Emil log – Trace Problematic Subscriber using IMSI Filters
4 3 1
2
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
Note) Can trace and analyze “the problematic call” > save it (*.emil) > Send it to NSN Technical Support to further analysis
Open Emil log – Trace Problematic Subscriber using IMSI Filters
After activating the IMSI filter, only traces from the filtered IMSI is visible
Traces can be saved in HTML or CSV format
L3 messages can be displayed including the message details