User Group Introduction to ENM

2G/AXE ENM Management Readiness

Ethio Telecom

Stephen Wanjohi
ENM Overview: ENM Launcher Page
Search for Applications

Access to Favorite Applications

Integrated Online Help

Applications grouped by Categories

Applications grouped alphabetically
Fault Management: OSS-RC vs ENM
OSS-RC Feature ENM Feature Compatibility Change Additional Information Nodes

Alarm List Viewer Alarm Monitor Functionally compatible, - BSC, MSC-S, MSC-BC,
Alarm Log Browser Alarm History but significant changes APG, BB 52, MGW, LAN
Alarm Status Matrix Alarm Overview in UI and UI integration Switch, HLR
AXE Alarm Manager Alarm Supervision
Alarm Routing
FMX FMX Fully compatible - -

CORBA Alarm IRP CORBA Alarm IRP Fully compatible - -

Agent Agent
SNMP NBI SNMP NBI Fully compatible - -

BNSI NBI BNSI NBI Fully compatible - -

— ENM provides CORBA NBI. This interface has not changed from OSS-RC.
 Alarm presentation for 2G RAN

— ENM displays BTS alarms as Alarming Objects under the parent BSC Network Element.

— ENM will send BTS alarms Northbound with ObjectOfReference attribute in a format similar to below:
ObjectOfReference:
SubNetwork=ONRM_ROOT_MO,SubNetwork=GSM,MeContext=RBBSC7,ManagedElement=RBBSC7,BssFunction=BSS_Ma
nagedFunction,BtsSiteMgr=T20342
PM Applications – Subscription creation page
Create a PM Subscription
for initiation of a node type

Select Node List (Add Topology)

at the “Resources Tab”

At “Scheduler” Tab,
select ROP
Intervals &
activation schedule

Add selected counters to Inclusion List

Select “Counters” Tab and Select Counters to Include in Activation

2G / AXE Performance Management in ENM
— Support for mediation (PULL / Collection) of the following files from ENM:
— PM Statistics: ASN.1 STS files available in both Encoded 3GPP ASN.1 and Raw ASN.1 formats
— Traces: CTR, MTR
— RNO Recordings: RIR, BAR, MRR, CER
— Event Files: See Slide 14

— Support for PUSH mediation of the following files from Nodes to ENM:
— PM Statistics: STS (Raw ASN.1) from BSCs / MSCs / STPs / HLRs to ENM

— Support for decoding of all file-types (except ASN.1 STS) to human-readable text-based formats

— Performance Management initiation for PM statistics and RNO Recordings is manually performed (via WinFIOL)
for all file-types, except MTR, RTT & R-PMO (which will be supported in PMIC in ENM)
Performance Management Statistics: OSS-RC vs ENM
OSS-RC Feature ENM Feature Compatibility Change Nodes

SMIA, SGW: STS PMIC: Collect and NBI Functionally compatible, Manual PM Initiation on BSC, MSC-S, MSC-BC,
but significant changes Node APG, HLR-FE
in UI and UI integration (use e.g. MML via
WinFIOL).

PMR: MTR PMIC: Initiate, collect, For reports, use external BSC
decode & NBI. system
PMR: CTR & CER PMIC: Collect, decode & Manual PM Initiation on BSC
NBI. Node
(use e.g. MML via
WinFIOL).
Software and Hardware Mgt
Unified GUI SHM Use Cases

Backup Job

License Install Job

Upgrade Job

Schedulable SHM Jobs

 Software & Hardware Management
— ENM SHM supports
2G/MSC/HLR-FE Node
Upgrades in user friendly
workflows.
— Similar workflows for License,
Backups, Inventory

Workflow
Software & Hardware Inventory – 2G / AXE Nodes
— ENM supports Software & Hardware Inventory views in ENM GUI for AXE Nodes (BSCs, MSCs, HLR-FEs, STPs):
— Inventory is exportable from ENM SHM GUI to CSV files.

— Inventory Data for AXE (BSC, MSC, HLR-FE & STP) nodes is exportable in 3GPP XML format for external NBI systems

AXE_Inventory_data_only2.zip

— Periodic Inventory exports can be generated by scheduling an ENM python script in the scripting VMs (via crontab). This script will
contain a custom CM export command, based on a scope of required nodes, required file/data formats and filters
Software & Hardware Management: OSS vs ENM
OSS-RC ENM Feature Compatibility Change Additional Nodes
— The primary software Feature Information
management use-cases SMO SHM Compatible for Upgrade SHM to BSC, MSC-S,
are addressed in ENM, BSC and MSC procedures for support MSC-BC, HLR,
including upgrade and Upgrade. BSC and MSC orchestrated APG, BB 52,
continue to upgrade of MGW, BTS*,
backup for MSC, HLR & Functionally leverage OPS AXE nodes LAN Switch*
BSC and upgrade for compatible for upgrade
APG43 Software scripts
Inventory. delivered by
Ericsson
— Importantly, OPS is nodes.
migrated from OSS-RC – Note:
something that should OPS OPS For the - OPS GUI and * upgrade only
facilitate a large installed- purposes of OPS CLI
software delivered in
base of software assets upgrade, full different
(including MSC, HLR & BSC OPS phases.
upgrade) compatibility.

MSC Feature Retired - - - -

Inventory
 2G / MSC / AXE Scripting Support –WinFIOL & OPS
WinFIOL scripts execute here

ENM
Linux KVM
Execute Virtual Machine
ENM Client WinFIOL script
Linux KVM
Execute ENM Virtual Machine MSC/BSC/HLR
CLI command

Execute Linux KVM

OPS script Virtual Machine
ENM scripts execute here
OPS scripts execute here

— ENM scripts can be executed on Client — All OPS & WinFIOL scripts are executed inside
PC that consist of WinFIOL and OPS the ENM server domain – this is where both OPS
commands. and WinFIOL are deployed.

— ENM scripts are Python-based scripts — It is not currently possible to deploy WinFIOL on
that execute ENM CLI commands. local user client and have MML commands
These can be executed from Client PCs proxied through ENM. WinFIOL on Client PC can
only work like any other Linux Terminal
— Client PC accesses the WinFIOL GUI & Emulator (e.g. Putty)
CLI via ENM GUI
WinFIOL CLI & GUI views in ENM
WinFIOL CLI from Network Explorer or Topology Browser WinFIOL CLI from ENM Home Page WinFIOL CLI open in ENM GUI

WinFIOL GUI from Topology Browser / Network Explorer WinFIOL GUI open in ENM GUI
Use Winfiol to connect to a BSC/MSC interactively:
Using Node NEID which is the Node Name Using resolved Hostname of the Node
(assuming Nodes entered in /etc/hosts of all scripting servers or a DNS)
as exists in ENM
wfcli --neid BLBSC2 wfcli --host NLBSC2 --protocol tls

Using Node IP Address Using Node channel file

wfcli --host 10.111.144.165 --protocol tls (see slide 12 for channel file creation using WinFIOL CLI or GUI)
wfcli --channelfile ~/winfiol/channelfiles/NLBSC1.xml
-
 Scripting Support –WinFIOL & OPS ENM vs OSS
OSS-RC ENM Feature Compatibility Change Additional Nodes
— Element Management & Feature Information

Scripting are enhanced over OPS OPS Largely A number of OPS BSC
OSS-RC compatible commands will not be MSC-S
supported in ENM: MSC-BC
@SELPRINT STP
@PRINTER HLR-FE
— WinFIOL scripting is available GETPRINT()
@EVDELETE
EVLOADED()
GETSCHED()
— OPS Scripting (majority of INHISTORY()
TIMEEVSET()
commands) are also available. @P

WinFIOL WinFIOL GUI Fully - WinFIOL scripting can be EAW command

WinFIOL CLI compatible executed on the Scripting replaced by
— OPS scripts need to be Servers on ENM WinFIOL CLI
reviewed and potentially command “wfcli”,
- Slight change in executable via
changed with move to Linux Connecting to BSCs / Scripting VMs in a
execution environment MSCs Linux shell

- No “eaw” command
— New Python Scripting (Scripting CHA WinFIOL GUI Replaced No CHA application
SDK) feature can also be used WinFIOL CLI

to script ENM CLI commands.

Scripting SDK New Feature Enables Scripting of ENM Python based All Nodes
CLI commands
 CONFIGURATION
MANAGEMENT in 2G
(major change)
GSM/AXE Use Cases in ENM
Software & Configuration Event Based Performance Fault Scripting
Hardware Management Management Management & Automation
Management

CM Events NBI PM File Lookup BNSI NBI Scripting SDK

Cell Management Service CORBA NBI
NBI Layer
NBI SNMP NBI
Import/Export NBI

Applications • Upgrade/update • Parameter • Event Based • ASN.1 Decoder • Alarm Monitor • WinFIOL
and Services • Backup and Management Statistics – • Alarm History • OPS Scripting
restore • CM Editor CLI RPMO (file only, • PM, Trace & • Alarm Overview • Use Case
• H/W Inventory • Import / Export Not Realtime) Recordings • FMX Automation
• S/W Inventory • CM Events NBI Initiation • Alarm Routing
• License • Cell Management • Event Stream to (WinFiOL)
management • Network Explorer File – REDE, RTT
• Topology Browser (file only)
• Network Viewer

Netconf/WinFIOL NetConf Mediation Event Stream AXE PM Mediation AXE Alarm WinFIOL Mediation
Mediation Mediation Infrastructure Mediation
 Moving 2G from OSS-RC to ENM
OSS-RC Feature ENM Feature/Tools Compatibility and Changes
CNAI ENM Bulk Configuration App Functionally compatible in terms of a Bulk mechanism for
ENM CLI Import / Export configuring and extracting GSM cellular data.
CM2G script However, some noteworthy differences are:
— The features in
this table - Significant change in published Managed Object Model.
marked as OSS- CNAI/CNA legacy model contained small number of large
RC Feature do object classes. BSC model contains ~126 MOCs
not exist in ENM. CNA, BSM, GPRS-CM, GPRSG Cell Management, - Significant shift in paradigm from MML-based to model-
They have either Bulk Configuration App, based applications
been replaced or Parameter Management, - Use-cases like Move BSC, Move BTS, BTS Consistency not
retired. CM Editor (ENM CLI) supported by a dedicated application.
Topology Manager,
Network Explorer,
Move Cell
CM2G script
IRATHOM Cell Management - Functionally compatible, but interface is changed
- Cell Management supports both User Interface and NBI for
Cell operations
- MSC in Pool supported

Bulk CM IRP Notification CM Events NBI - CM Event NBI is functionally richer, but not compatible.
- CM Event NBI supports notification PULL rather than
PUSH.
Adapting 2G Management to ENM
Knowledge of ENM Knowledge of the Managed
• Use of Configuration Management Nodes
Concepts/Apps
o ENM WinFIOL / OPS
Bulk Configuration Application Imports: • Ericsson BSC Managed Object Model
o
o MOM Diagrams
o Bulk Configuration file imports
o ENM Command Line Interface o MOM Classes Information, and relations
o ENM Parameter Management
• Ericsson BTS (BaseBand) Managed Object
o ENM Cell Management
ENM Network Explorer Model
o
o MOM Diagrams
o ENM Topology Browser
o MOM Classes Information, and relations

• Use of PM Management (PMIC) in ENM

• Use of Software/Hardware Management in
ENM
BSC MOM Introduction
— The Managed Object Model (MOM) shows the information in a Parent-Children relationship
— MOM is also used in other Ericsson’s Technology nodes (RNC, NodeB, eNodeB, ...)
— Thanks to the MOM and ECIM, the Model Driven Applications in ENM can manage the BSC
— This aids for the configuration of BSC on APG43L using BscFunction MOM.
— All the different configuration items in the BSC has been modelled into the MOM
BSC MOM Introduction (BscM)

— The configuration of the

INTERNAL cell is done
in the GeranCell and its
Children Objects
 Bsc & BTS mapping naming conversion
BscM mapping Btsmapping
Classical description MO Class
Classical description MO Class RXOTG G12Tg

Internal Cell GeranCell RXOCF G12Cf

RXOIS G12Is
External Cell ExternalGeranCell
RXCON G12Con
External Utran Cell ExternalUtranCell RXOTRX G12Trxc

Neighbor Relation (cellr={Internal}) GeranCellRelation RXORX G12Rx

RXOTX G12Tx
Neighbor Relation (cellr={External}) ExternalGeranCellRelation
RXOTS G12Ts
Neighbor Relation (cellr={Ext,Utran}) UtranCellRelation RXSTG G31Tg
RXSAT G31At
RXSCF G31Scf
CNA Parameter to MOM Mapping is documented in ENM CPI Library RXSTF G31Tf
Configuration Management in ENM
ENM does not provide CM domain specific applications. Below Apps & Methods are used for CM in ENM:
 Use of WinFIOL and OPS
 This means that the way of working in the following areas
 Bulk Configuration Application Imports:
are very different to the standard methods in the OSS-RC, — Import files to Live configurations (no Planned Area)
— 3GPP XMLs files
when using OSS CNA:
— Ericsson Dynamic File Format (EDFF) TXT files
 Cell Management  Bulk Configuration file imports using CLI:
— cmedit command import in Command Line Interface
 2G Network Parameter Management
 Use of commands in the Command Line Interface
 External Cell management. — Individual commands
— Batch file execution
 Neighbor Relation management.  Use of Parameter Management
 Use of Cell Management
 Parameter propagation among related definitions across the
 Network Explorer
network nodes  Topology Browser
Application Support of 2G Main Use Cases
Use Case Applications w/o Cell Applications with Cell Applications with Cell
Consistency Consistency (Small Scale) Consistency (Large Scale)
Create UTRAN Cell CM CLI, CM Bulk Import Cell Mgmt NBI & UI CM Bulk Import
Cell Audit Service (roadmap)
Create Internal Cell CM CLI, CM Bulk Import Cell Mgmt NBI & UI CM Bulk Import
Cell Audit Service (roadmap)
Create Neighboring Relation CM CLI, CM Bulk Import Cell Mgmt NBI & UI CM Bulk Import
Cell Audit Service (roadmap)
Update Neighboring Cell Params CM CLI, CM Bulk Import Cell Mgmt NBI & U CM Bulk Import file from
Parameter Management
Move Cells between BSCs CM CLI, CM Bulk Import + Winfiol Move Cell Script CM Bulk Import
Cell Audit Service (roadmap)
Move BTS & Cells between BSCs CM CLI, CM Bulk Import + Winfiol Bulk + Move Cell Script CM Bulk Import
Cell Audit Service (roadmap)
Radio changes (i.e. CM CLI, CM Bulk Import + Winfiol Cell Mgmt NBI & UI CM Bulk Import
LAC/CI/BSIC./BCCH ) Cell Audit Service (roadmap)

Power changes (i.e. BSPWR/ CM CLI, CM Bulk Import Cell Mgmt NBI & UI CM Bulk Import file from
BSPWRT) or Freq changes (i.e. Parameter Management
BCCH)
Delete Cells CM CLI, CM Bulk Import Cell Mgmt NBI & UI CM Bulk Import
Cell Audit Service
CM Applications - Topology browser (Common)
FDN to track MOM path

Easy navigation of MOM

Attributes can be edited and searched for on the right panel
Cell and Neigh. Cell Management

Cell Management can be used for:

●Cell children’s attributes can be set in the creation
— Create / Delete GeranCell process (GSM)

— Create / Delete Relations: ●Relation attributes can be set in the creation process
●Relation creation updates related attributes in
— GeranCellRelation source Cell
— ExternalGeranCellRelation

— UtranCellRelation
●All the activities are executed using the GUI
— EUtranFrequency
●Creation are to be done in a one by one basis.
— UtranFDDFrequency
●The attribute’s values must be typed in the GUI
Cell and Neigh. Parameter Management
Parameter Management can be used for:

— Update attribute’s values in any ●Individual attribute’s set

Managed Object: ●Attribute’s set with same value in several Managed
— GeranCell Objects of the same type
●Attributes can be updated from several Managed
— GeranCell’s children objects Objects
— ExternalGeranCell ●Automatic parameter synchronization
— ExternalUtranCell

— G12Tg and children ●All the activities are executed using the GUI

— G31Tg and Children ●Output is a bulk CM File (3GPP or EDFF)

— ...
Cell Management
All Cells, Basic Paramaters

Select NEs (BSC)

Cell & Neighbor Operations

Select Cell(s)
Cell Management: Cell Relations
Create / View Relations

Edit Parameter for Many Relations Selection

Parameter Management (1/4)
Select NE from Topology Pane , MO Class and Parameters to be updated

Select MO e.g. GeranCell

Select BSC
Select MO Parameters

Apply
Parameter Management (2/4)
• After Selecting Parameters, Select
“Fetch Data” to Load attribute
values from the NE

• Change Attribute Values

• Click Save

2
Change Values & update
Parameter Management (3/4)

Review Changes

Note: No direct execution like in 3G/4G Generate Bulk Import File for later execution using Bulk
Use Bulk CM Import App or CLI Configuration Import (3GPP or EDFF file)
Parameter Management (4/4)
The parameter changes are exported to Bulk CM files in either 3GPP XML or EDFF text file
Parameter Management: Export
The exported file can be easily imported in any database or standard office application
 Parameter Export: OSS-RC View
cnai export cna_export
Export from Table View
Parameter Export: ENM View
• Individual Objects and Group of objects (Object Type) can be exported by simply selecting
• The exported file can be easily imported in any database or standard office application
 Bulk Configuration Files (3GPP & EDFF)
Ericsson Dynamic File Format (EDFF) or 3GPP (xml) files are both available.

Bulk Configuration Files (EDFF or 3GPP) can be created: Bulk Configuration Files:
• As a result from the Parameter Management Are suitable for small or large changes
application
• Custom created “Comments” can be included for a better
understanding on the contents
Bulk Configuration Files (EDFF or 3GPP)
can be processed:
cmedit import commands in CLI
Bulk Configuration application

Bulk Configuration Files (EDFF or 3GPP)

can include any activity on any of the
Managed Objects:
• Create
• Delete
• Update (XML) / Set (EDFF txt)
 Bulk Configuration Files in ENM
3GPP XML Ericsson Dynamic File Format (EDFF)

— XML format
— Equivalent to the ones used in OSS-RC — Plain Text format
— The Objects’ structure may change compared to the — All the parameters are below the Object Id (FDN)
ones in OSS-RC, due to the different structure of the — One parameter per line -> mandatory line return
objects — Parameter : Value
— Same as in Node — Easy to use with Excel
— No Subnetwork (Master)
 ENM Command Line Interface
— Flexible App that allows the user to
perform most of the actions in ENM
— Several Command Sets
• cmedit
• config
— Help on App:
— Command syntax
— Examples
— Tutorials
 ENM CLI for Configuration Management

— cmedit get BLBSC3 gerancell.* -t

— “Example to display GeranCell and all parameters associated with each BSC cell in tabular format (-t) with no log in to the BSC
— “Ctrl-Enter” to Export the command Output to a CSV file
 ENM CLI for Configuration Management

— First to get the FDN of

the 2G BaseBand BTS
(BtsFunction)

— Then for example

fetching parameters
release and
gsmMcpaIpmCapacity
by simply copying FDN
of the MO into dialog
box along with
parameter attribute.
ENM CLI CM Export from ENM
cmedit get table format

Output can be saved into a text file by

using the Ctrl+Enter

Output can be saved into a

text file by using the
Ctrl+Enter
ENM CLI CM Import into ENM

Bulk Configuration with Graphical User Interface

Bulk Configuration Import with ENM CLI

cmedit import -f file:3gppImportFile.xml -ft 3GPP -t myConfig

cmedit import -f file:3gppImportFile.xml --filetype 3GPP --target myConfig
cmedit import -f file:3gppImportFile.xml --filetype dynamic --target myConfig

— File Contents:
Import file must be ordered by managed object hierarchy.
Parents must be created before their children.
2G Bulk Cell Management: CM2G Script
The CM2G is a solution for 2G Cell Management in bulk. It consists
of 2 console-based Python scripts: cm2g_bulk and cm2g_msc.

Its goal is to fill the current gap of ENM GUIs to provide similar
functionality to the OSS-RC CNA most basic operations, namely:
— Create 2G cells
— Delete 2G cells
— Create 2G-2G Cell Relations
— Delete 2G-2G Cell Relations
— Modify CGI of 2G Cells (e.g. for LAC change)
— Modify arbitrary parameters of 2G Cells (e.g. bcc, ncc, qsi,
bcchNo, ...)
 2G Move Cell Overview – Cell reparenting
move-cell is a script available via a Scripting Server - Linux OS shell.

The move-cell script is used to:

— Move GSM cells and their relations between BSCs (source and
target)
— Modify CGI values, cell names, or both.
— The script uses the Cell Management NBI to read cell data. It uses the
data to create NBI requests.
— These requests can delete the cell and recreate it on the Target BSC
along with its relations and attributes.
— The cells are moved by first running the prepare phase, then the
move phase.
— It has a rollback phase that can be used to recreate the cell
configuration of the From-node if necessary.
2G Move Cell: Use Cases

— Move Single Cell

— Move Multiple Cells
— Move a Single Cell to a Node That is under a Different SubNetwork
— Move Multiple Cells to a Node That is Under a Different SubNetwork
— Move Single Cell, Change CGI Value, and Change Cell Name
— Move Multiple Cells, Change CGI Values, and Change Cell Names
— Restore Original Cell Configuration (Including Relations) on the Node
 Optimizers in 2G
(major change)
(No RNO & RPMO UIs in ENM)
RNO/RPMO Functions: OSS-RC vs ENM
OSS-RC Description ENM Functionality Change in ENM
Application
MRR Measures radio characteristics. Manual Initiation of recordings is performed for - No RNO GUI in ENM as in OSS-RC.
MRR/BAR/RIR - Manual Initiation of MRR, NCS, FAS
recordings via WinFIOL
NCS Provides reports on neighbouring cells. PMIC tool in ENM collects the MRR/RIR/BAR - User collects ready MRR/BAR/RIR files
raw files every 15min from PMIC folders
FAS Provides reports on frequency – cell - MRR files parsed into MSMT CSV result
allocation. Script-based report generator available which files and collected via SFTP client for
converts MRR/RIR/BAR raw files to msmt CSV external analysis
reports
RNO strategy changes are based on the move
A “bscrec” script available to automate manual from manual optimization to automated
initiation of recordings. optimization, by use of GSM RAN automation
(see slides on MRR, NCS, FAS functionality features below:
description in ENM) • Automatic Frequency Load Planning
• Automatic Neighbour Relations
FOX Similar to FAS + proposes improved Not in ENM - A-FLP automation feature is
• Quality Based Time Slot Allocation
frequency allocation. available in GSM RAN
• BTS Soft Synch
NOX Similar to NCS + proposes & configures Not in ENM - Retired as ANR feature is now
improved neighbouring cell relations. available in GSM RAN

RNDBI Storage of outputs from RNO features. No equivalence in ENM

R-PMO RPMO Monitors: Pre-defined monitors Pre-defined R-PMO monitors are published as - Real-time monitoring not possible.
capturing radio network performance 15min PM counters in ENM, activated using - 15min counter-based granularity
PMIC tool and Uses Additional hardware - No GUI application for EBS-G / RPMO
REDE: Enables file capture of any events - Additional Hardware required
and monitors provided by R-PMO server
software, in a file.
 BAR, MRR & RIR Recording Automation: Output Files
• Once the Initiated Recordings are complete on the BSCs, ENM PMIC will collect the
files automatically

• The collected files can then be manually moved to the MRR, NCS, BAR parsing script
input folders and uncompressed (see previous slides on MRR, RAR, BAR parsing)

Folders of the collected MRR, RIR, BAR recording file outputs in ENM (format is TXT.GZ):
Path Format:
/ericsson/pmic*/BscRecordings/mrr/mrr_processed/SubNetwork=ONRM_ROOT_MO,SubNetwork=GSM,MeContext=<BSC-NAME>,ManagedElement=<BSC-NAME>/<file_name.gz>

/ericsson/pmic*/BscRecordings/rir/rir_processed/SubNetwork=ONRM_ROOT_MO,SubNetwork=GSM,MeContext=<BSC-NAME>,ManagedElement=<BSC-NAME>/<file_name.gz>

/ericsson/pmic*/BscRecordings/bar/bar_processed/SubNetwork=ONRM_ROOT_MO,SubNetwork=GSM,MeContext=<BSC-NAME>,ManagedElement=<BSC-NAME>/<file_name.gz>

Example:
/ericsson/pmic1/BscRecordings/mrr/mrr_ processed/SubNetwork=ONRM_ROOT_MO,SubNetwork=GSM,MeContext=TPBSC3,ManagedElement=TPBSC3/ A20201022.1145+0200-
20201022.1200+0200_SubNetwork=ONRM_ROOT_MO,SubNetwork=GSM,MeContext=UMBSC9,ManagedElement=UMBSC9_MRRFIL00-0000000984.gz

/ericsson/pmic2/BscRecordings/mrr/mrr_ processed/SubNetwork=ONRM_ROOT_MO,SubNetwork=GSM,MeContext=TPBSC3,ManagedElement=TPBSC3/ A20201022.2145+0200-

20201022.2200+0200_SubNetwork=ONRM_ROOT_MO,SubNetwork=GSM,MeContext=UMBSC9,ManagedElement=UMBSC9_MRRFIL00-0000000984.gz
MRR parsing in ENM - Description
— An MRR script runs on one ENM Scripting Virtual Machine
— BSC recordings are activated manually with relevant MML commands using WinFIOL.
— PMIC job is defined in ENM for periodic collection of MRR files (15min intervals)
— MRR files fetched by ENM PMIC tool are the input for the MRR script

Output files
BSC MRR Recording
files MRR Files (compressed text format) ENM
Binary format ENM Stored on ENM pmic File System

Scripting
VM MRR_KPI_20190902_10751.msmt

MRR
Script MRR_Details_20190902_10751.msmt
PMIC BSC1_MRR_File.gz

MML initiation sequence Detail

RAMII; // To initiate the recording
Initiate MRR Recordings RAMDC:RID=MRRID00,CELL=ALL;
RAMDP:RID=MRRID00;
// required cells
//To print associated cell with recording

(via MML Commands using RAMDC:RID=MRRID00,CONTYPE=EFR,VAMOSF

ILTER=VAMOS,MEASTYPE=TAVAL,MEASINT=LT
BSC WinFIOL or via bscrec OE,MEASLIM=7; // required Filter

RAMRI:RID=MRRID00,DTIME=30,RESET; // required duration

automation script) RAMRP:RID=ALL; // To Check status of Recording )
RAMTI:RID=MRRID00; //generate file output of MRR
RAMRE:RID=MRRID00; //terminate recording
RAMIE:RID=MRRID00; //release RID
NCS parsing in ENM -Description
— The NCS script runs on one ENM Scripting Virtual Machine
— BSC recordings are activated manually with relevant MML commands using WinFIOL
— PMIC job is defined in ENM for periodic collection of BAR files (15 min intervals)
— BAR files fetched by ENM PMIC tool are the input for the NCS script

BAR Files (compressed text format) Output files

BSC BAR Recording files
Stored in ENM pmic File System ENM
Binary format ENM
Scripting
VM NCS example output.msmt

NCS
Script
PMIC -Bulk CM Files
(XML from ENM CM export schedule)
PDB configuration info
(mandatory)
MML initiation sequence Detail
RABII; // To initiate the recording
RABDC:RID=BARID00,CELL=ALL; // required cells
RABDP:RID=BARID00; //To print associated cell with recording
RABDC:RID=BARID00,NCELLTYPE=BOTH,RELSSP=3,RELSS2N=4,RELSS3P=1
Initiate BAR Recordings 0,RELSS4P=2,RELSS5P=5,ABSS=75,NUMFREQ=5,SEGTIME=10; // required Filter

BSC RABDC:RID=BARID00,TMBCCHNO=85&86&87&88&89&90&91&92&93&94&9

(via MML Commands using WinFIOL or 5&97&99&102;

RABRI:RID=BARID00,DTIME=60;
//BA List for recording
// required duration ( in min )

via bscrec automation script) RABRP:RID=BARID00; // To Check status of Recording

RABTI:RID=BARID00; //generate file output of BAR ( after recording period )

RABRE:RID=BARID00; //terminate recording
RABIE:RID=BARID00; //release RID
2G/AXE Security
2G/AXE Security: OSS-RC vs ENM

— OSS-RC includes an application called TSS that handles — In addition to ENM Application usage Roles, support is
user authorization and TBAC (target-based access control) offered for both Role-Based Access Control (RBAC) and
for AXE-based nodes – in other words, controlling which Target-Based Access Control (TBAC)
MML commands a user can send to each node (target). — Users can be allocated roles (which control the types of
— It is possible to support different sets of commands for actions they can perform) against various targets.
different nodes for the same user. — It is not possible (through ENM) to allow users to issue
different commands towards different nodes/targets
— However, through a security model on the APG43, it is
possible to allocate COM roles to users.
— COM roles are mapped to pre-defined groups of MML
commands (COCA groups), granting certain capabilities to
users.
— These same roles are mirrored in ENM and used by the
APG node to authenticate users
— Through this mechanism, more fine-grained command
access/capability can be allocated to BSC users