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
Alarm List Viewer
Alarm Log Browser
Alarm Status Matrix
AXE Alarm Manager
Alarm Monitor
Alarm History
Alarm Overview
Alarm Supervision
Alarm Routing
Functionally compatible,
but significant changes
in UI and UI integration
FMX
FMX
Fully compatible
-
-
CORBA Alarm IRP
Agent
CORBA Alarm IRP
Agent
Fully compatible
-
-
SNMP NBI
SNMP NBI
Fully compatible
-
-
BNSI NBI
BNSI NBI
Fully compatible
-
-
— ENM provides CORBA NBI. This interface has not changed from OSS-RC.
Additional Information
Nodes
-
BSC, MSC-S, MSC-BC,
APG, BB 52, MGW, LAN
Switch, HLR
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,
but significant changes
in UI and UI integration
Manual PM Initiation on
Node
(use e.g. MML via
WinFIOL).
BSC, MSC-S, MSC-BC,
APG, HLR-FE
PMR: MTR
PMIC: Initiate, collect,
decode & NBI.
For reports, use external
system
BSC
PMR: CTR & CER
PMIC: Collect, decode &
NBI.
Manual PM Initiation on
Node
(use e.g. MML via
WinFIOL).
BSC
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
— The primary software
management use-cases
are addressed in ENM,
including upgrade and
backup for MSC, HLR &
BSC and upgrade for
APG43
— Importantly, OPS is
migrated from OSS-RC –
something that should
facilitate a large installedbase of software assets
(including MSC, HLR & BSC
upgrade)
OSS-RC
Feature
ENM Feature
Compatibility
Change
Additional
Information
Nodes
SMO
SHM
Compatible for
BSC and MSC
Upgrade.
Upgrade
procedures for
BSC and MSC
continue to
leverage OPS
upgrade
scripts
delivered by
Ericsson
nodes.
SHM to
support
orchestrated
upgrade of
AXE nodes
BSC, MSC-S,
MSC-BC, HLR,
APG, BB 52,
MGW, BTS*,
LAN Switch*
Functionally
compatible for
Software
Inventory.
OPS
OPS
For the
purposes of
software
upgrade, full
OPS
compatibility.
-
OPS GUI and
OPS CLI
delivered in
different
phases.
MSC Feature
Inventory
Retired
-
-
-
Note:
* upgrade only
-
2G / MSC / AXE Scripting Support –WinFIOL & OPS
WinFIOL scripts execute here
ENM
ENM Client
Execute
WinFIOL script
Execute ENM
CLI command
ENM scripts execute here
Execute
OPS script
Linux KVM
Virtual Machine
Linux KVM
Virtual Machine
MSC/BSC/HLR
Linux KVM
Virtual Machine
OPS scripts execute here
— ENM scripts can be executed on Client
PC that consist of WinFIOL and OPS
commands.
— All OPS & WinFIOL scripts are executed inside
the ENM server domain – this is where both OPS
and WinFIOL are deployed.
— ENM scripts are Python-based scripts
that execute ENM CLI commands.
These can be executed from Client PCs
— It is not currently possible to deploy WinFIOL on
local user client and have MML commands
proxied through ENM. WinFIOL on Client PC can
only work like any other Linux Terminal
Emulator (e.g. Putty)
— Client PC accesses the WinFIOL GUI &
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 GUI from Topology Browser / Network Explorer
WinFIOL CLI open in ENM GUI
WinFIOL GUI open in ENM GUI
Use Winfiol to connect to a BSC/MSC interactively:
Using Node NEID which is the Node Name
as exists in ENM
wfcli --neid BLBSC2
Using Node IP Address
wfcli --host 10.111.144.165 --protocol tls
Using resolved Hostname of the Node
(assuming Nodes entered in /etc/hosts of all scripting servers or a DNS)
wfcli --host NLBSC2 --protocol tls
Using Node channel file
(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
— Element Management &
Scripting are enhanced over
OSS-RC
OSS-RC
Feature
ENM Feature
Compatibility
Change
OPS
OPS
Largely
compatible
A number of OPS
commands will not be
supported in ENM:
Additional
Information
BSC
MSC-S
MSC-BC
STP
HLR-FE
@SELPRINT
@PRINTER
GETPRINT()
@EVDELETE
EVLOADED()
GETSCHED()
INHISTORY()
TIMEEVSET()
@P
— WinFIOL scripting is available
— OPS Scripting (majority of
commands) are also available.
WinFIOL
— OPS scripts need to be
reviewed and potentially
changed with move to Linux
execution environment
WinFIOL GUI
WinFIOL CLI
Fully
compatible
- WinFIOL scripting can be
executed on the Scripting
Servers on ENM
- Slight change in
Connecting to BSCs /
MSCs
Nodes
EAW command
replaced by
WinFIOL CLI
command “wfcli”,
executable via
Scripting VMs in a
Linux shell
- No “eaw” command
— New Python Scripting (Scripting
SDK) feature can also be used
to script ENM CLI commands.
CHA
WinFIOL GUI
WinFIOL CLI
Replaced
No CHA application
Scripting SDK
New Feature
Enables Scripting of ENM
CLI commands
Python based
All Nodes
CONFIGURATION
MANAGEMENT in 2G
(major change)
GSM/AXE Use Cases in ENM
Software &
Hardware
Management
Mediation
Event Based
CM Events NBI
Cell Management
NBI
Import/Export NBI
NBI Layer
Applications
and Services
Configuration
Management
• Upgrade/update
• Backup and
restore
• H/W Inventory
• S/W Inventory
• License
management
• Parameter
Management
• CM Editor CLI
• Import / Export
• CM Events NBI
• Cell Management
• Network Explorer
• Topology Browser
• Network Viewer
• Event Based
Statistics –
RPMO (file only,
Not Realtime)
Netconf/WinFIOL
Mediation
NetConf Mediation
Event Stream
Infrastructure
• Event Stream to
File – REDE, RTT
(file only)
Fault
Management
Performance
Management
PM File Lookup
Service
BNSI NBI
CORBA NBI
SNMP NBI
• ASN.1 Decoder
•
•
•
•
•
• PM, Trace &
Recordings
Initiation
(WinFiOL)
AXE PM Mediation
Alarm Monitor
Alarm History
Alarm Overview
FMX
Alarm Routing
AXE Alarm
Mediation
Scripting
& Automation
Scripting SDK
• WinFIOL
• OPS Scripting
• Use Case
Automation
WinFIOL Mediation
Moving 2G from OSS-RC to ENM
— The features in
this table
marked as OSSRC Feature do
not exist in ENM.
They have either
been replaced or
retired.
OSS-RC Feature
ENM Feature/Tools
Compatibility and Changes
CNAI
ENM Bulk Configuration App
ENM CLI Import / Export
CM2G script
Functionally compatible in terms of a Bulk mechanism for
configuring and extracting GSM cellular data.
However, some noteworthy differences are:
- Significant change in published Managed Object Model.
CNAI/CNA legacy model contained small number of large
object classes. BSC model contains ~126 MOCs
CNA, BSM, GPRS-CM, GPRSG
Cell Management,
Bulk Configuration App,
Parameter Management,
CM Editor (ENM CLI)
Topology Manager,
Network Explorer,
Move Cell
CM2G script
- Significant shift in paradigm from MML-based to modelbased applications
- Use-cases like Move BSC, Move BTS, BTS Consistency not
supported by a dedicated application.
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
• Use of Configuration Management
Concepts/Apps
o
o
o
o
o
o
o
o
ENM WinFIOL / OPS
Bulk Configuration Application Imports:
Bulk Configuration file imports
ENM Command Line Interface
ENM Parameter Management
ENM Cell Management
ENM Network Explorer
ENM Topology Browser
• Use of PM Management (PMIC) in ENM
• Use of Software/Hardware Management in
ENM
Knowledge of the Managed
Nodes
• Ericsson BSC Managed Object Model
o MOM Diagrams
o MOM Classes Information, and relations
• Ericsson BTS (BaseBand) Managed Object
Model
o MOM Diagrams
o MOM Classes Information, and relations
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
External Cell
ExternalGeranCell
RXOIS
G12Is
RXCON
G12Con
External Utran Cell
ExternalUtranCell
RXOTRX
G12Trxc
Neighbor Relation (cellr={Internal})
GeranCellRelation
RXORX
G12Rx
Neighbor Relation (cellr={External})
ExternalGeranCellRelation
RXOTX
G12Tx
RXOTS
G12Ts
Neighbor Relation (cellr={Ext,Utran})
UtranCellRelation
RXSTG
G31Tg
RXSAT
G31At
RXSCF
G31Scf
RXSTF
G31Tf
CNA Parameter to MOM Mapping is documented in ENM CPI Library
Configuration Management in ENM
Below Apps & Methods are used for CM in ENM:
ENM does not provide CM domain specific applications.

This means that the way of working in the following areas

Use of WinFIOL and OPS

Bulk Configuration Application Imports:
— Import files to Live configurations (no Planned Area)
are very different to the standard methods in the OSS-RC,
— 3GPP XMLs files
when using OSS CNA:

Cell Management

2G Network Parameter Management

External Cell management.

Neighbor Relation management.

Parameter propagation among related definitions across the
network nodes
— Ericsson Dynamic File Format (EDFF) TXT files

Bulk Configuration file imports using CLI:
— cmedit command import in Command Line Interface

Use of commands in the Command Line Interface
— Individual commands
— Batch file execution

Use of Parameter Management

Use of Cell Management

Network Explorer

Topology Browser
Application Support of 2G Main Use Cases
Use Case
Applications w/o Cell
Consistency
Applications with Cell
Applications with Cell
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.
LAC/CI/BSIC./BCCH )
CM CLI, CM Bulk Import + Winfiol
Cell Mgmt NBI & UI
CM Bulk Import
Cell Audit Service (roadmap)
Power changes (i.e. BSPWR/
BSPWRT) or Freq changes (i.e.
BCCH)
CM CLI, CM Bulk Import
Cell Mgmt NBI & UI
CM Bulk Import file from
Parameter Management
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:
— Create / Delete GeranCell
●Cell children’s attributes can be set in the creation
process (GSM)
— Create / Delete Relations:
●Relation attributes can be set in the creation process
— GeranCellRelation
●Relation creation updates related attributes in
source Cell
— ExternalGeranCellRelation
— UtranCellRelation
— EUtranFrequency
— UtranFDDFrequency
●All the activities are executed using the GUI
●Creation are to be done in a one by one basis.
●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
Managed Object:
●Individual attribute’s set
— GeranCell
●Attribute’s set with same value in several Managed
Objects of the same type
— GeranCell’s children objects
●Attributes can be updated from several Managed
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
1
2
Change Values & update
Parameter Management (3/4)
Review Changes
Note: No direct execution like in 3G/4G
Use Bulk CM Import App or CLI
Generate Bulk Import File for later execution using Bulk
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
Export from Table View
cnai export
cna_export
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:
• As a result from the Parameter Management
application
• Custom created
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:
Are suitable for small or large changes
“Comments” can be included for a better
understanding on the contents
Bulk Configuration Files in ENM
3GPP XML
Ericsson Dynamic File Format (EDFF)
— XML format
— Equivalent to the ones used in OSS-RC
— The Objects’ structure may change compared to the
ones in OSS-RC, due to the different structure of the
objects
— Same as in Node
— No Subnetwork (Master)
— Plain Text format
—
—
—
—
All the parameters are below the Object Id (FDN)
One parameter per line -> mandatory line return
Parameter : Value
Easy to use with Excel
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
Application
Description
ENM Functionality
Change in ENM
MRR
Measures radio characteristics.
Manual Initiation of recordings is performed for
MRR/BAR/RIR
-
NCS
Provides reports on neighbouring cells.
-
FAS
Provides reports on frequency – cell
allocation.
PMIC tool in ENM collects the MRR/RIR/BAR
raw files every 15min
Script-based report generator available which
converts MRR/RIR/BAR raw files to msmt CSV
reports
A “bscrec” script available to automate manual
initiation of recordings.
(see slides on MRR, NCS, FAS functionality
description in ENM)
FOX
Similar to FAS + proposes improved
frequency allocation.
Not in ENM - A-FLP automation feature is
available in GSM RAN
NOX
Similar to NCS + proposes & configures
improved neighbouring cell relations.
Not in ENM - Retired as ANR feature is now
available in GSM RAN
RNDBI
Storage of outputs from RNO features.
No equivalence in ENM
R-PMO
RPMO Monitors: Pre-defined monitors
capturing radio network performance
Pre-defined R-PMO monitors are published as
15min PM counters in ENM, activated using
PMIC tool and Uses Additional hardware
REDE: Enables file capture of any events
and monitors provided by R-PMO server
software, in a file.
-
No RNO GUI in ENM as in OSS-RC.
Manual Initiation of MRR, NCS, FAS
recordings via WinFIOL
User collects ready MRR/BAR/RIR files
from PMIC folders
MRR files parsed into MSMT CSV result
files and collected via SFTP client for
external analysis
RNO strategy changes are based on the move
from manual optimization to automated
optimization, by use of GSM RAN automation
features below:
•
Automatic Frequency Load Planning
•
Automatic Neighbour Relations
Quality Based Time Slot Allocation
•
•
BTS Soft Synch
-
Real-time monitoring not possible.
15min counter-based granularity
No GUI application for EBS-G / RPMO
Additional Hardware required
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+020020201022.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+020020201022.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
BSC MRR Recording
files
Binary format
Output files
ENM
MRR Files (compressed text format)
Stored on ENM pmic File System
ENM
Scripting
VM
MRR
Script
PMIC
MRR_KPI_20190902_10751.msmt
MRR_Details_20190902_10751.msmt
BSC1_MRR_File.gz
MML initiation sequence
BSC
Initiate MRR Recordings
(via MML Commands using
WinFIOL or via bscrec
automation script)
Detail
RAMII;
RAMDC:RID=MRRID00,CELL=ALL;
RAMDP:RID=MRRID00;
RAMDC:RID=MRRID00,CONTYPE=EFR,VAMOSF
ILTER=VAMOS,MEASTYPE=TAVAL,MEASINT=LT
OE,MEASLIM=7;
// To initiate the recording
// required cells
//To print associated cell with recording
RAMRI:RID=MRRID00,DTIME=30,RESET;
RAMRP:RID=ALL;
RAMTI:RID=MRRID00;
RAMRE:RID=MRRID00;
RAMIE:RID=MRRID00;
// required duration
// To Check status of Recording )
//generate file output of MRR
//terminate recording
//release RID
// required Filter
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
BSC BAR Recording files
Binary format
ENM
BAR Files (compressed text format)
Stored in ENM pmic File System
Output files
ENM
Scripting
VM
NCS example output.msmt
NCS
Script
PMIC
-Bulk CM Files
(XML from ENM CM export schedule)
PDB configuration info
(mandatory)
BSC
Initiate BAR Recordings
(via MML Commands using WinFIOL or
via bscrec automation script)
MML initiation sequence
Detail
RABII;
RABDC:RID=BARID00,CELL=ALL;
RABDP:RID=BARID00;
RABDC:RID=BARID00,NCELLTYPE=BOTH,RELSSP=3,RELSS2N=4,RELSS3P=1
0,RELSS4P=2,RELSS5P=5,ABSS=75,NUMFREQ=5,SEGTIME=10;
RABDC:RID=BARID00,TMBCCHNO=85&86&87&88&89&90&91&92&93&94&9
5&97&99&102;
RABRI:RID=BARID00,DTIME=60;
RABRP:RID=BARID00;
// To initiate the recording
// required cells
//To print associated cell with recording
RABTI:RID=BARID00;
RABRE:RID=BARID00;
RABIE:RID=BARID00;
//generate file output of BAR ( after recording period )
//terminate recording
//release RID
// required Filter
//BA List for recording
// required duration ( in min )
// To Check status of Recording
2G/AXE Security
2G/AXE Security: OSS-RC vs ENM
— OSS-RC includes an application called TSS that handles
user authorization and TBAC (target-based access control)
for AXE-based nodes – in other words, controlling which
MML commands a user can send to each node (target).
— It is possible to support different sets of commands for
different nodes for the same user.
— In addition to ENM Application usage Roles, support is
offered for both Role-Based Access Control (RBAC) and
Target-Based Access Control (TBAC)
— Users can be allocated roles (which control the types of
actions they can perform) against various targets.
— 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