Contents

1 About ENM
Ericsson Network Manager (ENM) is an OSS platform, and suite of Network Management
applications supporting operation and maintenance of Radio, Transport, and Core networks.

The ENM platform and infrastructure is a distributed and parallel software system supporting
the following business-critical characteristics:

High Availability
This ensures that failures in software processes, whether controlled or
and Fault
not, are contained and not of consequence to operations.
Tolerance

This is the ability to scale up or scale down the capability of the OSS
system, by choosing different deployment variants (the software
Horizontal Scaling
components that are needed and the number of software components
that are needed).

This is a procedure that sequentially upgrades software components

“Rolling” Upgrade while remaining in-service. This eliminates the need for configuration
freeze periods.

ENM comprises a suite of different management applications supporting the various elements
associated with FCAPS management. ENM also contains more advanced management
applications, focusing on automation. Applications are controlled by human interfaces (GUI
and CLI) or machine interfaces, this varies from application to application. All applications
support integrated online help. This online help contains overviews, tutorials and videos to
help explain common network operations.

Target Groups

The document is intended for the following users:

 Alarm Operator
 Radio Network Engineer
 Solution Architect
 System Administrator
 Installation Engineer
 Field Technician
 Business Manager
 Switching Engineer

2 Definitions of ENM Applications

ENM applications can be divided into the following categories:

 Common applications

Common for all network domains and Network Element types

 Domain-specific applications

Apply to a single management domain

 System or infrastructure applications

2.1 Common Applications

The following applications are common for all network domains, and Network Element types.

In certain cases, a common function may not yet support all supported node types in
Note:
ENM. This is marked with an asterisk.

Alarm Monitor

This is a live alarm viewer, with integrated alarm details and alarm OPI publication.

Collection Management

This is an application supporting the administration of data groups (for example: groups of
Network Elements, or groups of network resources).

ENM Command-Line Interface (CLI)

This is a web-based command shell providing access to many different command interfaces
published by ENM applications.

Import / Export

This is a configuration management function supporting the bulk import (provisioning) and
export (retrieval) of configuration management data. This function supports both 3GPP file
formats (Bulk CM IRP TS32.615), and Ericsson Dynamic and concise file format.

Network Connectivity Manager (NCM)

Network Connectivity Manager application provides the capability to create, edit, view,
activate, deactivate and discover E-LAN, E-Line, Layer 3 VPN for a generic Mobile Back
Haul network domain IP or Ethernet based.

Network Explorer

This is an application supporting data search and grouping capabilities with powerful
querying capability. This application also supports parameter tuning.
Parameter Management

This is an application supporting parameter viewing and editing across different Network
Elements.

PM Initiation and Collection (PMIC)

This is an application for administering the collection of performance management data.

Release Independence Manager

This is a feature that enables ENM to support new Network Element versions without
requiring an ENM upgrade.

Software Hardware Manager (SHM)

This is used for software, hardware and license inventory management, and typical life cycle
management of Network Element software (upgrade, backup and restore).

Topology Browser

This is a tree browser supporting the rendering of data and navigation through data models.
This application also supports parameter tuning.

Alarm Search

This is an application supporting search functions for both live and historical alarms.

Alarm Overview

This is a dashboard application supporting various widgets or components capturing aspects

of fault management and fault management summaries.

Alarm Supervision Status

This is an application used to view and control the administration of alarm management
(where ENM subscribes to and manages alarm streams) from all Network Elements.

Alarm Routing

This supports various alarm routing procedures (for example, route alarms to email) for the
Alarm Monitor application.

Automatic Alarm Handling (FMX)

This is an application supporting the development of rules that can be used to correlate and
suppress alarms in ENM.

Desktop Session Management

This is an environment supporting the hosting of Element Manager applications (clients)
supported by the various Network Elements. This application is also used more generally to
support the hosting of applications that are not web-based.

Network Health Monitor (NHM){*}

This is a dashboard application supporting various widgets or components capturing aspects

of fault management, performance management, and configuration management (state
information).

Node Monitor{*}

This is a node-centric monitoring application supporting various widgets or components

capturing aspects of fault management, performance management, and configuration
management (state information).

Node Health Check

This is a web-based application used to perform health checks on nodes.

KPI Management{*}

This supports the creation of user-defined, customized Key Performance Indicators, which are
then published in Network Health Monitor.

VNF Life Cycle Manager{*}

This is a framework and application supporting various life cycle management use-cases for
virtualized Network Elements (for example: commission, decommission, scale).

Configurations

 Display the history of CM data changes made to one or more network elements in the
live configuration made by CM Bulk Import operations.
 Undo the changes performed on nodes by CM Bulk Import operations.

Configuration Templates

This is an application supporting the management of templates in ENM.

NetLog{*}

This supports the collection and persistence of NE logs.

Autonomic Incident Management

This is a node-centric monitoring application that detects network incidents autonomously and
prioritizes these incidents based on impact to network users.

UDC Dashboard
UDC Dashboard provides a Graphical User Interface (GUI) for monitoring system status and
performance information of UDC nodes by presenting the data on a single, easy-to-use web
interface. It allows operators to monitor the CUDB, HLR-FE, HSS-FE, HSS/SLF, EDA/PG
and IPWorks system through a web GUI.

UDC Dashboard Execution Environment is a virtual machine with configurations to support

deployment of the UDC Dashboard application. (UDC is a standalone application and its
capabilities are defined in the UDC product description.)

UDC has an independent application life cycle. Therefore, as newer versions of UDC are
released, they can be installed in any ENM versions that support execution of UDC
Dashboard. ENM does not provide UDC Dashboard installation, the application is installed in
a separate step after ENM installation.

2.2 Domain-Specific Applications

Domain-specific applications apply to a single management domain.

The following applications are domain-specific:

AMOS Offline

This is a command-based element management tool supporting WCDMA and LTE Radio
Access Networks.

Analytic Session Record for LTE (ASR-L) and NR (ASR-N)

Analytic Session Record provides mobility-based session records for LTE and NR, based on
Cell Trace event streams.

Automatic ID Management

This is a 3GPP SON function supporting the enforcement of uniqueness of physical cell
identities (PCI) across cellular topologies in the LTE Radio Access Network.

Auto-Provisioning

Auto Provisioning (AP) automates node provisioning activities.

The key features of AP are:

 Automatically integrate a new node in the customer network with user provided
information.
 Automatically expand an existing node configuration.
 Automatically configure a node for a hardware replace of an existing node.

Core Network Operations Manager (CNOM)

The Core Network Operations Manager (CNOM) allows the integration of CNOM into ENM
to manage EPC and IMS Network Elements. CNOM is a standalone product and its
capabilities are defined within that product.

CNOM has an independent application life cycle. Therefore, newer versions of CNOM can be
installed in older ENM versions.

ENM does not provide CNOM installation. CNOM is installed in a separate step after ENM
installation.

Element Manager

This enables direct configuration changes and troubleshooting on a single Network Element
(NE) instance.

Network Discovery

This supports the automatic detection of certain types of Network Elements in the Transport
domain.

Detected nodes are added to ENM to be managed.

Node Health Check

This is a diagnostic and troubleshooting application supporting the retrieval of node health
indicators, and the generation of reports.

Operations Procedure Support (OPS)

OPS is an ENM application that supports the development and runtime control of OPS scripts
containing MML and AP commands. As well as these commands for the nodes, OPS scripts
can be embedded with platform utility commands and OPS commands.

OPS provides a GUI environment for editing, debugging, and running OPS scripts using the
OPS script language. The main window displays the contents of an OPS script in one text
pane and the output from the OPS script execution in another text pane.

Existing OPS scripts can be loaded into the main window through a file browser, and new
files can be created. More than one OPS script can be managed in one session, although only
one can be displayed at a time. All managed OPS scripts are listed in the File menu, and
switching between them is possible.

OPS supports AXE-based nodes only.

Supported node types are:

 BSC
 MSC
 HLR-FE
You can work with OPS scripts using the following GUI modes:

 Edit

The script in the OPS Script area can be edited. An insertion cursor is available.

 Run

The script in the OPS Script area can be executed, but not edited. No insertion cursor
is available.

 Output

The result of an OPS script being executed is shown.

The following features are available in OPS GUI:

Create a New OPS

Create and store a new file in the current user’s OPS script directory.
Script

Execute an Existing Load an existing OPS script from your user’s OPS script directory
OPS Script into the OPS window and execute it.

Stop an Executing
Use the Stop button to stop a running OPS script.
OPS Script

Debug a Faulty OPS The debug option is available in the OPS GUI to debug a faulty OPS
Script script.

Develop an OPS script using the OPS Script language. It is possible

Develop an OPS
to write OPS scripts to perform management tasks for AXE-based
Script
nodes that are supported by the ENM system.

Monitor OPS Script After running an OPS script, monitor its progress in the Output
Progress mode.

Control OPS Scripts

Stop a running OPS script if any errors occur.
in Runtime

Run All Except a Run an OPS script while selectively not running some of the lines.
Few Lines of an OPS You can add tags in the Edit mode and then run the script from the
Script tagged location.

Interact During OPS OPS has User Input Output based commands and GUI features to
Script Execution take input during the execution of an OPS script.
 OPS supports scheduling with crontab. Log on to the OPS VM and
Schedule of Jobs provide the required configurations in crontab to schedule the
execution of an OPS script.

Shell Terminal

This is an alternative Access Point for the AMOS application, enabling direct access to a
dedicated resource pool.

WAN-SDN Controller

WAN-SDN Controller automates the control of segment routing and IP/MPLS flows in the
service provider, cloud provider, and large enterprise networks.

It provides the end user with granular visibility into network traffic flows while optimizing
network capacity through closed-loop automation. It monitors the network in real time,
gathering streaming telemetry, IGP, and BGP-LS data from the network and analyzing the
data to provision new service paths based on user-defined SLA constraints. After paths are
deployed, WAN-SDN re-computes or re-provisions paths as needed for SLA assurance. It
automates provisioning of these explicit routed network paths, regardless of the traffic load,
by pushing path information to the respective ingress routers.

The WAN-SDN Controller GUI provides a single view of the network and its KPIs in real
time, enabling control and management of network capacity dynamically.

The following are the use cases supported by WAN-SDN Controller:

 Manage, monitor, and provision Segment Routing and IP/MPLS paths in real time.
 View live network topology maps that show node status, link utilization, segment
routing paths, and label-switched paths (LSPs).
 Automate the discovery of nodes, links, and paths from the network.
 Provision LSP or segment routing paths directly onto the network.
 Create or schedule maintenance events to re-route traffic when issues arise.
 View status of KPIs for the live network.
 Optimize peering ingress and egress traffic according to network costs and SLAs.

With support for Representational State Transfer (REST) APIs, WAN-SDN Controller can
easily integrate into the operations environment and thus is ready to scale up and to
accommodate any network.

WAN-SDN Controller monitors and displays multiple network domains, providing a transport
network view in order to manage inter-domain traffic engineering and network slicing.

It can also help simplify migration to segment routing by allowing multiple control planes
over the same infrastructure at the same time.

For additional information, see the WAN-SDN Controller Installation Guide, available from
local Ericsson support.

WinFIOL CLI
This is a command-driven utility supporting access to AXE-based Ericsson Network Elements
(in the Circuit-Switched Core and GSM Radio Access Networks).

Flexible Counter Management (FCM)

This application provides the functionality to manage Flexible (Flex) counters for Event
Based Statistics for NR (EBS-N). A Flex counter is a base EBS counter which is refined with
additional filter parameters to provide more granular performance monitoring and
observability. Once created, Flex counters are available for selection with base EBS-N
counters in the PMIC application.

2.3 ENM System or Infrastructure Applications

Applications considered to be system or infrastructure-based.

ENM also contains the following important ancillary applications considered to be ENM
system or infrastructure-based:

Provides scheduled backup and disaster recovery of the entire ENM

Back Up and Restore
deployment.

ENM System Supports the monitoring of both the ENM infrastructure and ENM
Monitor applications.

Supports indexed search capability. It also supports log entries for all
Log Viewer
ENM applications.

Node Security Enables the control and administration of security settings for
Configuration individual Network Elements or groups of Network Elements.

Supports the publication and definition of user roles and capabilities

Role Management in the ENM system. Custom user roles are supported. Roles are one
aspect of the access control system implemented in ENM.

Supports the administration of all ENM users. This includes the

User Management addition and deletion of users, as well as password and certificate
management.

PKI Entity Supports the generation, allocation, revocation, and renewal of

Management certificates for individual people and Network Elements.

System Security Manages ENM system-wide security configurations, such as

Configuration password policies.

PKI Profile Supports the administration of certificate policies that are applied to
Management all people and Network Elements with certificates allocated.
 Supports the publication and definition of target groups in the ENM
Target Group
system. Target groups are one aspect of the access control system
Management
implemented in ENM.

Contains the integrated online application help. This contains

Help Center
overviews, tutorials, and videos.

License Control and Provides the infrastructure to manage feature and capacity licenses
Monitoring (LCM) and supports license enforcement.

Several important integration points or programmable interfaces (commonly referred to as

Northbound Interfaces) are also published and supported in ENM. These include the
following:

An implementation of the 3GPP TS 32.111-1, supporting the

CORBA-based Alarm
relay of all alarm state changes and operations to synchronize
IRP
with external systems.

A text-based alarm interface, supporting the relay of all alarm

BNSI Alarm Interface state changes and operations to synchronize with external
systems.

A REST-based querying interface supporting the publication of

Performance
file-system location details and the availability of stored counter
Management File Lookup
and event files in ENM (that is, whether a file is available to
Service (FLS)
collect or consume).

Configuration
A REST-based querying interface supporting the retrieval of all
Management Events
network configuration changes that are registered and recorded
Interface (CM Event
by ENM.
NBI)

A REST-based interface supporting simplified cell network

Cell Management Service provisioning, specifically the provisioning of cells, frequencies,
and relations.

A Python-based library that enables the native execution of any

Python Scripting
ENM command (exactly as the command is supported in the
Software Development
ENM CLI) in a Python script, executed externally to the ENM
Kit
management system.

3 ENM Deployments
For information related to ENM deployments, contact local Ericsson support.
4 Definitions of ENM Services
ENM services can be subdivided by category.

The categories are as follows:

 Services Based on Virtual Machines - Services and Mediation (SVC)

 Services Based on Virtual Machines - Event Based Applications (EVT) Cluster
 Services Based on Virtual Machines - Scripting and AMOS (SCP)
 Services Based on Virtual Machines: Streaming Value Pack Clusters
 Services Not Based on Virtual Machines in ENM on LITP Platform

4.1 Services Based on Virtual Machines - Services and

Mediation (SVC)
A glossary of services that are based on virtual machines and belong to the service group
Services and Mediation.

 VMs for Services and Mediation (apserv – dlms)

 VMs for Services and Mediation (eventbasedclient – ipsmserv)
 VMs for Services and Mediation (ltservices – mscmip)
 VMs for Services and Mediation (msfm – pmserv)
 VMs for Services and Mediation (said – shmcoreserv)
 VMs for Services and Mediation (solr - wpserv)
 Consolidated VMs for Services and Mediation for Extra Small ENM on OpenStack
Cloud Deployments

4.1.1 VMs for Services and Mediation (apserv – dlms)

Virtual
Service Description
Machine

apserv
The Auto Provisioning service is responsible for the automated rollout
(provisioning, commissioning, and integration) of new nodes into ENM.
Node plugins contain CM functions delivered by the node organization.
Node Plugins
These functions are begun internally by ENM Auto Provisioning to
support capabilities to build and validate (G2) node configurations.
The Basic Network Surveillance Interface (BNSI) provides Fault
bnsi Management (FM) capabilities (over ENM) to Northbound Network
Management Systems (NMS), according to the BNSI protocol.
The Basic Network Surveillance Interface (BNSI) NBI Service is
bnsiserv
responsible for providing Fault Management (FM) capabilities (over
ENM) to Northbound Network Management Systems (NMS), according to
the BNSI protocol.
 Virtual
Service Description
Machine
The Mediation Routing Policy service contains all routing policies for the
Ericsson Common Information Model (such as comecimcmrouterpolicy,
cmrouterpolicy,fmrouterpolicy, snmpfmrouterpolicy.) These
comecimpolicy
routing policies customize the routing of specific flows to mediation
service instances. When a policy is specified for a flow, the policy
overrides the default policies contained in the router.
The Configuration Management (CM) events service provides external
cmevents
systems such as Network Management Systems with access to CM event
data. Access is provided using a Machine to Machine interface that is
based on notifications about changes to the network.
The Configuration Management service:

 Provides services that handle the create, read, update, and delete
(CRUD) commands relevant to the CM EDIT network element.
cmserv These commands either read from or write to the Data Persistence
Service (DPS).
 Provides a script engine that manages messaging to and from the
Command-Line Interface.

The CM Utilities service provides services that support the management of

cmutilities templates in ENM by allowing a user to create, upload files to, list, view
details of, export, import, and delete templates.

dchistory
The Data Change History service stores Configuration Management (CM)
topology and network events persistently in the APACHE Solr database.
The Data Lifecycle Management service manages the life cycle for data
related to Configuration Management (CM), Fault Management (FM), and
dlms Performance Management (PM). CM and FM use this virtual machine to
manage data in APACHE Solr TM. PM uses this virtual machine to
manage data in the File Lookup Service (FLS).

cellserv
Cellserv provides services for the configuration and auditing of cells in
ENM.

4.1.2 VMs for Services and Mediation (eventbasedclient – ipsmserv)

Virtual Machine Service Description

The Mediation Event Based Client service receives mediation task
eventbasedclient requests and uses the mediation router to forward these requests to the
most suitable mediation services.
The File Lookup Service (FLS) provides a REST interface to the FLS
flsserv database. This interface reads and writes meta information for PM
files to and from the FLS.
 Virtual Machine Service Description
The Fault Management Alarm Processing service processes alarms
fmalarmprocessing received from the mediation layer through an FMAlarmOutBusTopic
queue. It comprises the core part of Fault Management within ENM.
The Fault Management History service provides the required
fmhistory privileges to view the alarm history and enables actions to be
performed on alarms such as ACK, Unack, Clear, and Comment.

fmserv
The Fault Management service enables actions to be performed on
nodes such as start or stop, supervision, and synchronization.
The Fault Management Expert service provides a rule inference
Fmx engine for processing distributed event streams used in Automatic
Alarm Handling.
Httpd Apache web server
The Import/Export service supports the bulk import of configuration
changes and the export of configuration data. Data is imported and
exported in XML files based on either of the following:
Impexpserv
 3rd Generation Partnership Project (3GPP) Bulk CM
Integration Reference Point (IRP)
 CSV or txt files based on the Ericsson Dynamic File Format.

TransportCIM normalization service provides, where applicable, the

mscmip transformation of a specific node model into a normalized one. AVC
event triggers the normalization process on a specific MO.
TransportCIM normalization service provides, where applicable, the
mscme transformation of a specific node model into a normalized one. AVC
event triggers the normalization process on a specific MO.
TransportCIM normalization service provides, where applicable, the
ipsmserv transformation of a specific node model into a normalized one. AVC
event triggers the normalization process on a specific MO.

4.1.3 VMs for Services and Mediation (ltservices – mscmip)

Virtual
Service Description
Machine

Itservices
The itservices service provides DNS, DHCP, and NTP services to support
the auto-integration of Network Elements in ENM.
The kpicalcserv service is responsible for calculating predefined and user-
kpicalcserv defined KPI formulas. PM counter statistics files are parsed to access the
counters used in the calculation of active KPIs.
The Key Performance Indicator service is responsible for defining,
kpiserv activating, deactivating, editing, and querying predefined and user-defined
KPI formulas.
 Virtual
Service Description
Machine

Lcmserv
The license Control and Monitoring service is responsible for the license
management and license enforcement in ENM.
The lvsrouter service load balances and maps IPv4 and IPv6 mediation
and storage traffic, allowing applications to present a Virtual IP address
(VIP) towards the NEs and share a small number of VIPs towards Network
lvsrouter
Address Storage (NAS). Network Address Translation (NAT) is used to map
between the internal and public or storage IP addresses. Direct Routing (DR)
is used for incoming server requests (IPv6), and through the virtual IP (VIP)
routes the request to the real servers. The real server processes the request
and sends the response directly to the client, bypassing the LVS router.

medrouter
The medrouter service selects the most suitable mediation service to
process an incoming Mediation Task Request.

msap
The msap service is responsible for communication between the Auto
Provisioning Service (apserv) and the nodes.
The mscm service performs configuration management activities on the
Network Elements managed by the ENM system. These activities include
mscm adding, deleting, synchronizing, TransportCIM normalizing, subscribing to,
and handling notifications from - and performing CRUD operations on - the
NEs.
The mscmapg service performs Configuration Management activities on
GSM Network Elements (NEs) that are relevant to common operation and
maintenance (O&M), and that comply with the Ericsson Common
Information Model.

Configuration Management activities performed by this virtual machine

include the following:
mscmapg
 Adding NEs
 Deleting NEs
 Synchronizing NEs
 Subscribing to NEs
 Handling notifications from NEs
 Performing create, read, update, and delete (CRUD) activities on
NEs

The mscmce service performs configuration management activities on NEs

that are relevant to Common Operation and Maintenance (O&M) and that
comply with the Ericsson Common Information Model (ECIM).

mscmce Configuration Management activities performed by this virtual machine

include the following:

 Adding NEs
 Deleting NEs
 Virtual
Service Description
Machine
 Synchronizing NEs
 TransportCIM normalization of specific NE models
 Subscribing to NEs
 Handling notifications from NEs
 Performing create, read, update, and delete (CRUD) activities on
NEs

The mscmip service performs CM activities on IP Network Elements

managed by the ENM system. These activities include adding and deleting
mscmip NEs, TransportCIM normalization of specific NE models, synchronizing
Network Elements, subscribing to, and handling notifications from the NEs,
and performing CRUD operations on the NEs.

ipsmserv
TransportCIM normalization service provides, where applicable, the
transformation of a specific node model into a normalized one.

4.1.4 VMs for Services and Mediation (msfm – pmserv)

Virtual
Service Description
Machine
The msfm service checks communication between the Common Object
Request Broker Architecture (CORBA), a Network Element, and the
msfm ENM system. When alarm supervision is started, this virtual machine
subscribes to the NE for alarms. After a successful subscription, the ENM
system starts receiving alarms.
The msnetlog service performs activities needed for one-shot retrieval of
msnetlog
network logs on the NEs managed by the ENM system. These logs enable
and facilitate troubleshooting of an ENM Operator to investigate network
issues.
The mspm service does performance management activities on the
Network Elements managed by the ENM system. These activities
include:
mspm
 Activation or deactivation of performance monitoring jobs on
Network Elements
 File collection from NEs

The mspmip service does performance management activities on the

Router6000 family, Cisco, and JUNIPER family Network Elements
mspmip
managed by the ENM system. These activities include:

 Activation or deactivation of performance monitoring jobs on

Network Elements
 Virtual
Service Description
Machine
 File collection from NEs

The mssnmpfm service checks the communication between the Simple

Network Management Protocol (SNMP), a Network Element, and the
mssnmpfm ENM system. When alarm supervision is started, this virtual machine
subscribes to the NE for alarms. After a successful subscription, the ENM
system starts receiving alarms.
The msosssnmpfm service checks the communication between the Simple
Network Management Protocol (SNMP), an ECI-LightSOFT
management system that manages ECI-Optical nodes, and the ENM
system. When alarm supervision is started on the ECI-LightSOFT
management system, this virtual machine subscribes to the ECI-
LightSOFT management system for alarms. After a successful
msosssnmpfm
subscription, the ENM system starts receiving alarms on the ECI-Optical
nodes.

This service group is available on the Ericsson Integrated LITP-

Note: based platform only. It is not available on ENM on OpenStack
Cloud deployments.
The mssnmpcm service performs CM activities on Network Elements with
mssnmpcm
SNMP that are managed by the ENM system. These activities include
synchronization, adding and deleting Network Elements, subscribing to
and handling notifications, and performing CRUD operations.

nbalarmirp
The nbalarmirp service is responsible for the communication between
the Network Management System (NMS) and ENM.
The netex service provides services for the Network Explorer, Topology
netex Browser and Add Node applications. Read and write (R-W) operations
are performed on Data Persistence Service (DPS) by these applications.
The Open Identity Management service provides the back end for the
openidm User Management service. This service is responsible for user creation
and security scope management.
The Public-Key Infrastructure Registration Authority service enrolls
online certificates for nodes. It uses Certificate Revocation List [CRL]
pkiraserv
Distribution Point Service (CDPS) functions and Trust Distribution Point
Service (TDPS) functions. A Registration Authority (RA) is an authority
in a network that verifies user requests for a digital certificate and tells
the Certificate Authority (CA) to issue it.
The Performance Management Router Policy service manages load
pmrouterpolicy balancing across the mediation service groups used for Performance
Management (PM) mediation.

pmserv
The Performance Management service provides the following:
 Virtual
Service Description
Machine
 Services to handle the PM Create, Read, Update, and Delete
(CRUD) commands for PM subscriptions.
 Setup of activation, deactivation, and file collection for PM
subscriptions

The msapgpfm service checks the communication between the

APG(ECIM), a Network Element, and the ENM system. When alarm
msapgfm supervision is started, this virtual machine subscribes to the NE for
alarms. After a successful subscription, the ENM system starts receiving
alarms.
A client of ncmagent, that provides methods that are used to manage end-
to-end connectivity services in a distributed network. The distributed
ncm
network is managed by ENM and contains heterogeneous, packet-enabled
Network Elements.
A server of ncm, that provides methods that are used to manage end-to-
end connectivity services in a distributed network. The distributed
ncmagent
network is managed by ENM and contains heterogeneous, packet-enabled
Network Elements.

4.1.5 VMs for Services and Mediation (said – shmcoreserv)

Virtual
Service Description
Machine

said
The Service Automatic ID service is responsible for LTE Physical Cell
Identity (PCI) optimizations in ENM.
Solrautoid service stores information of historical conflicts that are
SolrAutoId resolved by AutoId as part of closed loop profile, and conflicts scheduled
for resolution automatically.
The saserv service conducts spectrum sampling activities and manages
sample files. Spectrum sampling activities include sending capability
saserv requests to Network Elements, starting and stopping the sampling of
Network Elements, transforming sample files, and managing the retention of
sample files.
The secserv service hosts security-related services including the following:

 Generic Identity Management

 Software Management Distribution Repository Services (SMRS)
secserv
service hosts security-related services including the following:
 Identity Management Service
 Node Security
 Access Control for Nodes Supporting Ericsson Common Information
Model (ECIM)
 Virtual
Service Description
Machine
The Software Hardware Manager (SHM) Core service enables users to
perform the following SHM use cases:

 Upgrade node software

 Install license key files on node.
 Create backups of node software.
 Restore backups on the node.
 Manage node backups.
shmcoreserv
 Delete node backups.
 Housekeeping tasks related to backups on the node
 Restart node from the SHM CLI.
 Delete upgrade packages on the node.
 Perform the following Node Health Check use cases:
o Execute Node Health Checks
o View and compare Node Health Check reports.

The Software/Hardware Manager service enables the following

software/hardware management tasks:

 View and export software inventory.

 View and export hardware inventory.
 View and export license inventory.
 View backup inventory.
 Automatic inventory synchronization.
 Import, view, and delete software packages on ENM.
 Import, view, and delete license key files on ENM.
 View available node software packages on the Network Element
shmserv Software Store (CAS).
 Import software packages from the Network Element Software Store.
 Perform housekeeping of software packages on ENM before
automatic import from Network Element Software Store.
 Automate the software package import from the Network Element
Software Store.
 Download Release Notes.
 Perform the following node health check use cases:
o Create Node Health Check Profiles.
o View Node Health Check Profiles.
o Delete Node Health Check Profiles.

4.1.6 VMs for Services and Mediation (solr - wpserv)

Virtual
Service Description
Machine

solr
The solr service stores information of historical alarms/events in a shared
file system.
 Virtual
Service Description
Machine
The Security Peer service provides the ENM Public Key Infrastructure
sps (PKI) implementation and is responsible for ENM certificate management
through the Credential Manager Service.

sso
The Single Sign-On (SSO) service is responsible for the authentication of
users when they log on to the system.
The Supervision Client service listens for data changed events that require
supervc supervision from the Data Provisioning Service (DPS), and sends a
Supervision Mediation Task Request to the Mediation Event Based Client.
The UI Server service provides services for the Launcher and User
uiserv
Interface (UI) Settings applications. The Presentation Server service
services both of these applications, providing configuration data to the
Launcher and managing a cache for UI Settings.
The visinamingnb service holds Interoperable Object Reference (IOR)
visinamingnb files that are used by a NMS user to connect to ENM to receive alarms and
events, and to perform alarm operations
The visinamingsb service is a CORBA service that is called by Cell
visinamingsb Packet Platform (CPP) nodes to send the Node-Up message to ENM as part
of the automated rollout of the CPP nodes into ENM.
The web push service handles streaming/push communication, that is
wpserv asynchronous and unidirectional events sent from a server to a client. The
push mechanism is based on HTML5 Server Sent Events (SSE).

4.1.7 Consolidated VMs for Services and Mediation for Extra Small ENM on
OpenStack Cloud Deployments

A consolidated VM is a VM that has two or more services consolidated or co-deployed on to

a single VM.

Descriptions of services contained in the consolidations are found in their respective tables in
the preceding sections.

Virtual
Description
Machine
consautoprov This VM consists of the apserv, msap, and nodeplugins services.
conscmeditor This VM consists of the cmserv, cmutilities, and dchistory services.

conscommonmed
This VM consists of the comecimpolicy, eventbasedclient,
medrouter, and supervc services.

consfm
This VM consists of the fmalarmprocessing, fmhistory, and fmserv
services.
consguiserv This VM consists of the httpd, uiserv, and wpserv services.
conskpi This VM consists of the kpicalcserv and kpiserv services.
 Virtual
Description
Machine
conslicensemgt This VM consists of the lcmserv and sentinel services.
autocellmgt This VM consists of the said and solrautoid services.
consshm This VM consists of the shmcoreserv and shmserv services.

4.2 Services Based on Virtual Machines - Scripting and

AMOS (SCP)
A glossary of services that are based on virtual machines and belong to the service group
Scripting and AMOS.

Virtual Machine Service Description

amos
Provides an interactive environment for Advanced MO Scripting
users.

elementmanager
Provides an environment for X11 applications with the desktop
visible in a browser tab.

scripting
Provides an environment in which to run scripts either for users who
connect using SSH or for scripts initiated by the cron service.
Load balances and maps storage traffic, allowing applications to
share a Virtual IP address (VIP) towards Network Attached Storage
(NAS).
scriptinglvsrouter

Network Address Translation (NAT) is used to map between the

internal and storage IP addresses.
winfiol Used for terminal emulation to configure and test NEs.
UDC Dashboard is an application which provides a Graphical User
Interface (GUI) for monitoring system status and performance
udcdashboard
information of UDC nodes by presenting the data on a single, easy-
to-use web interface. It allows operators to monitor the CUDB,
HLR-FE, HSS-FE, HSS/SLF, EDA/PG, and IPWorks system
through a web GUI.

4.3 Services Based on Virtual Machines - Automation

Cluster (AUT)
A glossary of services that are based on virtual machines and belong to the service group
Automation.
 Virtual
Service Description
Machine
The Autonomic Incident Management service detects network incidents
imserv autonomously and prioritizes these incidents based on impact to network
users.
The Anomaly Detection service does the following:

imadserv  Detects anomalies on monitored KPIs.

 Tags KPI anomalies that have a Utilization Impact.

imfmalarmserv The FM alarm service processes alarms received from FM.

The Knowledge Base service does the following:

imkbserv  Manages the learning process.

 Stores information that is learned.

The Grouping service groups events into an incident. The grouping is

imgroupingserv based on correlation confidence information stored in the Knowledge
Base.

4.4 Services Based on Virtual Machines: Streaming Value

Pack Clusters
A glossary of services based on virtual machines that belong to the Streaming (STR) cluster,
the Event Based Statistics (EBS) cluster, the Analytic Session Record (ASR) cluster, and the
Event Based Applications (EBA) cluster.

The services apply to the following Value Packs:

 Event Based Statistics for LTE (EBS-L), with stream-based input.

 Event Based Statistics for NR (EBS-N), with stream-based input.
 Analytic Session Record for LTE (ASR-L)
 Analytic Session Record for NR (ASR-N)
 BSC Event Handling

4.4.1 Streaming (STR) Cluster

Virtual Machine Service Description

The apeps service parses raw event streams from kafka's raw
apeps bus and converts to Avro format before placing events onto the
decoded bus in kafka.
The Schema Registry service stores Avro schemas in kafka so
streamingschemaregdef
that streaming applications can encode and decode events. It
provides a REST interface for publishing and consuming Avro
schemas. It is based on Confluent Schema Registry.
 Virtual Machine Service Description
The zoo service manages the instances of the kafka and
zoo streamingschemaregistrydef services and is based on Apache
Zookeeper.

4.4.2 Event Based Statistics (EBS) Cluster

Virtual Machine Service Description

The Event Based Statistics (EBS) Kafka service provides High
ebskafka
Availability for stream-based EBS, allowing the recovery of
ongoing event processing and counter generation if there is VM
failover.
The Event Based Statistics (EBS) Stream service performs
ebsstream
counter generation logic for EBS counters and writes output
counter XML files to the Performance Management (PM)
Northbound Interface.
The Event Based Statistics (EBS) Stream Controller service
ebsstreamcontroller
interfaces to Performance Management Initiation and Collection
(PMIC) to retrieve the required subscription information for EBS
counter generation.
The Event Based Statistics (EBS) Stream Topology service
ebsstreamtopology
provides the required CM topology information to ebsstream
services so that EBS counters can be enriched, aggregated, and
reported on the required CM objects.
The streamingebslvsrouter service load balances and maps
storage traffic, allowing applications to share a Virtual IP
streamingebslvsrouter address (VIP) towards NAS. Network Address Translation
(NAT) is used to map between the internal and storage IP
addresses.

4.4.3 Analytic Session Record (ASR) Cluster

Virtual Machine Service Description

The asrlfwd service acts as a forwarder for Analytic Session
asrlfwd Record (ASR). It forwards completed ASR Sessions to the
configured NBI IP and Port in the Avro format.
The asrlservicedef provides the REST endpoint to access the
asrlservice Avro Schema required for the NBI client to decode the Avro
encoded Analytic Session Record (ASR) records.
The sparkMaster service provides an API through which new
sparkMaster Spark Jobs are submitted. The master distributes the jobs across
the available Spark Workers.
 Virtual Machine Service Description
The sparkWorker service consists of a job that performs the
sparkWorker
correlations for ASR. It receives the job to be run from
sparkMaster and then executes that job until the worker is shut
down.
The streamingasrlvsrouter service load balances and maps
streaming and storage traffic, allowing applications to share a
streamingasrlvsrouter Virtual IP address (VIP) towards NAS. Network Address
Translation (NAT) is used to map between the internal and
storage IP addresses.
The asrltopologyservice provides the required CM topology
asrltopologyservice information to the sparkWorker service so that Analytic
Session Records can be enriched with topology data.
The Analytic Session Record (ASR) Kafka service provides high
asrkafka availability by providing recovery of ongoing ASR record
generation at VM failover.

4.4.4 EBA Cluster

Virtual Machine Service Description

The ebaapeps service contains parsing logic for BSC
ebaapeps
RPMO and RTT events based on BSC IWD. The service
converts events into AVRO encoded compact binary
format for data serialization.
The ebakafka service provides the following:

 A raw topic which stores undecoded BSC RPMO

and RTT raw events.
ebakafka  A decoded topic which stores decoded BSC RPMO
and RTT events from ebaapeps service. These
decoded events are later processed by rpmoflow,
rttflow, and ebsgflow services.

The ebalvsrouter service load balances and maps

storage traffic, allowing applications to share a Virtual IP
ebalvsrouter address (VIP) towards NAS. Network Address Translation
(NAT) is used to map between the internal and storage IP
addresses.
The ebamsstr service terminates and multiplexes BSC
event streams and publishes events to the raw topic on the
Kafka event bus. This service uses the Stream Indicator
ebamsstr event, which is received from the BSC after the connection
is established, to update a cache with stream identification
information.The cache data is consumed by the ebaapeps
service.
 Virtual Machine Service Description
The ebaserv service fetches CM topology information to
enable the rpmoflow, rttflow, and ebsgflow services to
enrich event data with additional CM information. The
service writes to the File Lookup Service (FLS) to publish
ebaserv
the following file types on PM NBI:

 BSC Performance Events files

 RTT files
 BSC Performance Event Statistics files

The ebastreamingschemaregistry service stores Avro

schemas in Kafka to enable streaming applications to
ebastreamingschemaregistry encode and decode events. It provides a REST interface
for publishing and consuming Avro schemas. This solution
is based on Confluent Schema Registry.
The ebazoo service manages the instances of the Kafka
ebazoo and ebastreamingschemaregistry services. This service
is based on Apache Zookeeper Framework.
The service contains correlation and transformation logic
for creating BSC Performance Event Statistics counter
files in 3GPP XML format.

The ebsgflow service contains correlation and

transformation logic for creating the following output file
ebsgflow types:

 BSC Performance Event Statistics files in 3GPP

XML format
 BSC Performance Event Monitors files in tab-
separated text format.

The rpmoflow service contains correlation and

rpmoflow transformation logic for creating text-based tab-separated
BSC Performance Events files and Control files.
The rpmokafka service provides high availability,
rpmokafka allowing for the recovery of ongoing event processing in
the event of VM failover.
The rttflow service contains correlation logic for
rttflow creating IMSI/IMEI based event trace text files for RTT
events.

4.5 Services Based on Virtual Machines - Event Based

Applications (EVT) Cluster
A glossary of services based on virtual machines that belong to the Event Based Applications
(EVT) cluster.

The services apply to the following Value Packs:

 Event Based Statistics for MME (EBS-M), with file-based input.

 Event Based Statistics for LTE (EBS-L), with file-based input.
 Event Based Statistics for NR (EBS-N), with file-based input.

Virtual Machine Service Description

The Event Based Statistics (EBS) Mediation service performs counter
ebsm generation logic for EBS counters and writes output counter XML files
to the Performance Management (PM) Northbound Interface.
The Event Based Statistics (EBS) Mediation Controller service
coordinates the allocation of Event Based Monitoring (EBM) and Cell
Trace Report Output Period (ROP) files to EBSM VMs. This VM
ebsmcontroller interfaces to Performance Management Initiation and Collection (PMIC)
to listen for EBM and Cell Trace File Collection Notifications and to
retrieve the required subscription information for EBS counter
generation.
The Event Based Statistics (EBS) Topology service provides the
ebstopology
required CM topology information to EBSM services so that EBS
counters can be enriched, aggregated and reported on the required CM
objects.
The eventslvsrouter service load balances and maps storage traffic,
eventslvsrouter
allowing applications to share a Virtual IP address (VIP) towards NAS.
Network Address Translation (NAT) is used to map between the internal
and storage IP addresses.
The Event Based Statistics (EBS) Mediation Controller service
coordinates the allocation of Event Based Monitoring (EBM) and Cell
Trace Report Output Period (ROP) files to EBSM VMs. This VM
ebsmcontroller
interfaces to Performance Management Initiation and Collection (PMIC)
to receive EBM and Cell Trace File Collection Notifications and to
retrieve the required subscription information for EBS counter
generation. This VM also provides the services for the Flexible Counter
Management application.

4.6 Services Not Based on Virtual Machines in ENM on

LITP Platform
Service Description
The ElasticSearch service is a third party product (3PP) that
ElasticSearch
indexes logs generated on the VMs and routed through rsyslog. It
also provides a Representational State Transfer (REST) interface
that allows querying and management of the indexes.
 Service Description

HAProxy Ext
The HAProxy Ext service acts as a load balancing solution for
HTTPD and SSO services.

HAProxy SouthBound
The HAProxy South Bound service acts as a load balancer solution
for PKIRA services.
The Java Message Service is a messaging standard that allows
application components based on Java Platform Enterprise Edition
(Java EE) to create, send, receive, and read messages. It enables
JMS
distributed communication that is loosely coupled, reliable, and
asynchronous.

ENM applications use JMS for asynchronous communication. The

JMS provider is HornetQ.
The Model Deployment service is started by LITP as part of an
Model Deployment
installation and upgrade process. As part of the installation or
upgrade, LITP extracts all model packages (RPMs) and collates
them to a central location.

OpenDJ
The OpenDJ service is a 3PP implementation of Lightweight
Directory Access Protocol (LDAP) used for identity data.
The Postgresql service is the generic RDBMS used in ENM for
applications that require a DB back end. These include cmconfig,
Postgresql
import and export services, Web Feature Service
(WFS)/Autoprovisioning, mapping using PostGIS, itservices
(DHCP,NTP), EBS, PKI, and SFWK, and some Identity
Management services.
The streaminglvsrouter service is deployed in the optional
streaminglvsrouter
Streaming (STR) cluster. The service provides IPv4 and IPv6 load
balancing for Stream Terminator and fault tolerance by rerouting
traffic to a standby service at failover.
The msstr service is deployed in the optional Streaming (STR)
msstr cluster. The Stream Terminator service ends and multiplexes event
streams and publishes encoded events to the raw event bus.
The kafka service is deployed in the optional Streaming (STR)
kafka
cluster. The Kafka Event Bus service provides High Availability and
allows applications and services to store and retrieve events on the
event buses.
The Neo4j service is the Graph Database Management System used
to store the Network Model (implemented and planned) and all the
associated Network Model data provided by the DPS. The database
Neo4j
also stores alarms and notification instances of the NEs to be
consumed by various services in ENM (such as FM, PM, and so on).
A Neo4j deployment in Medium or Large ENM has a single instance
while Extra Large ENM has a 3 instance causal cluster based
configuration.
4.7 Services Based on Virtual Machines in Integrated
ENM and ENM on Cloud
VM Description
The ENM Management Portal (EMP) is a VM provided in the
Cloud deployment for various System Administration and
EMP troubleshooting activities. Some of the tasks executed on the
Management Server in the physical deployment can be executed
from the EMP VM.
The Models deployment service is deployed in a VM as part of an
Models installation and upgrade process. All model packages are installed
into this VM and the model repository is then created.
 Nfscommon
 Nfsnrbk
These are the VMs that provide the NFS file systems by acting as
 Nfspm
 Nfspmlink
NFS servers. Clients who need access to NFS file systems can
 Nfssmrs
mount from these VMs.

Nodemigration
The node migration VM is provided to host the node migration
SW and procedures.
 Vnflafservices
These VMs provide the VNF-LCM used to execute the ENM
 Vvnlafdb
deployment workflows for install, upgrade, and so on.

Sentinel
The Sentinel VM hosts the Sentinel server. This is the back end of
the License Management service.
The ServiceReg VM hosts the Consul service. This is used to
provide Service registration and resolution. Services in ENM
Servicereg register their service name and where (IP) they can be resolved to.
The Service registry VMs also host the Key Value (KV) store.
This is a store for configuration parameters.
The ElasticSearch service is a third party product (3PP) that
ElasticSearch
indexes logs generated on the VMs and routed through rsyslog. It
also provides a Representational State Transfer (REST) interface
that allows querying and management of the indexes.

HAProxy
The HAProxy VMs act as a load balancing solution for HTTPD
and SSO services.

HAProxy SouthBound
The HAProxy South Bound service acts as a load balancing
solution for PKIRA services.
The Java Message Service is a messaging standard that allows
application components based on Java Platform Enterprise Edition
JMS
(Java EE) to create, send, receive, and read messages. It enables
distributed communication that is loosely coupled, reliable, and
asynchronous. ENM applications use JMS for asynchronous
communication. The JMS provider is HornetQ.
 VM Description

OpenDJ
The OpenDJ service is a 3PP implementation of Lightweight
Directory Access Protocol (LDAP) used for identity data.
The PostgreSQL service is the generic RDBMS used in ENM for
applications that require a DB back end. These include cmconfig,
PostgreSQL import and export services, Web Feature Service
(WFS)/Autoprovisioning, mapping using PostGIS, itservices
(DHCP,NTP), ebs, PKI, and sfwk, and some idenmgmt services.
The Neo4j service is the Graph Database (GDB) used to store the
Network Model (Implemented and Planned) and all the associated
Neo4j
Network Model Data provided by the DPS. The database also
stores alarms and notification instances of the NEs to be
consumed by various services in ENM (such as FM, PM, and so
on).

4.7.1 Consolidated VMs for Services Based on Virtual Machines in Extra

Small ENM on OpenStack Cloud

For Extra Small ENM on OpenStack Cloud, the following services are consolidated, all other
services remain the same.

Descriptions of services contained in the consolidation are found in their respective tables in
Services Based on Virtual Machines in Integrated ENM and ENM on Cloud.

Virtual
Description
Machine

consnfs
This VM consists of the nfscommon, nfsnorollback, nfspm, nfspmlinks,
and nfssmrs services.

5 NAS-Based File Systems

ENM uses shared file systems to store and process customer-specific data. Shared file systems
are created on a Network Attached Storage (NAS) appliance that is highly scalable, highly
available, and clustered.

Storage is available through a Storage Area Network (SAN) and is mounted by any
combination of the following:

 Physical nodes
 Virtual machines running on physical nodes through a mount point

Shared file systems can be included in snapshots and backups.

Table 1 Properties of an ENM NAS-Based File System

 File System Name
<ENM_NAS_storage_pool_name>-cust_fs/ericsson/custom
(Syntax)
The file system hosts customer-specific data.
Purpose of File
System
(ENM actively monitors the file system, but no application uses it.)
Mount Point for
/ericsson/custom
Storage
 MS
Available  All blades
(Mounted) On:  All virtual machines

Size 70 GB in all deployments

Snapshot Occurs
No
During Upgrade
File system is not backed up by default as part of backup and restore.
Backed Up
A backup can be included in the backup-to-live policy.

6 Browser and Operating System

Requirements
ENM can run on both iOS (iPad) and Windows PC. It has the following browser and
operating system requirements.

Table 2 Requirements
Operating
Device Browser CPU RAM
System
1GB
iPad iOS Safari Apple A7
min
Firefox (latest ESR release
candidate)
CPU benchmark of 4GB
(1)
2000 min
PC Windows
(3) (4)
Chrome (latest stable channel)
(2)

(1) Firefox ESR (release road map and qualifying release candidates:
https://www.mozilla.org/en-US/firefox/organizations/) is the recommended desktop browser
because of its longer maintenance window (annual). Download the latest ESR release at the
following address: https://ftp.mozilla.org/pub/firefox/releases/
(2) The stable channel is fully tested by the Chrome OS team and is the best option to avoid
issues. It is updated every 2 to 3 weeks for minor changes, and every 6 weeks for major
changes. To download the latest stable channel release of Chrome, go to
https://chromereleases.googleblog.com/search/label/Stable%20updates
(3) A minimum CPU benchmark of 2000 is required to run 5 browser tabs simultaneously
(see www.cpubenchmark.net for CPU benchmark ratings).
(4) A minimum of 4GB with 1GB free is required for every 5 tabs opened simultaneously in a
browser. The higher the CPU spec the better the performance when many tabs are opened.
The following browser guidelines apply:

 Maintenance support is provided only on the latest browser version currently available
from the browser vendor.
 To ensure that the latest available version is installed, browser versions should be kept
up to date using the Browser Auto Update mechanism or Corporate IT policy.
 ENM should continue to work as expected on the latest available browser version.
 Firefox ESR is the recommended desktop browser owing to its longer maintenance
window (annual).
 See the browser help documentation to check if you are on the latest available version.
 Browsers must support the Transport Layer Security (TLS) protocol version 1.0 or
greater. By default browsers normally use TLS unless configured not to.
 ENM client instances running in a browser place resource needs on the device being
used.
 A security improvement requires the installation of a valid certificate in the browser to
access the ENM Launcher. For more information, refer to Create a User Account in
ENM Identity and Access Management System Administrator Guide, 2/1543-AOM 901
151-1 .

iPad devices have the following limitations:

Table 3 iPad Limitations
Item Limitation
Downloads can require the installation of an appropriate file handling app
File Download (for example, File Manager). Otherwise, content displays as plain text in
the browser.
File Upload Safari Mobile does not support file upload.
Fault Manager
This classic desktop application is not designed for mobile devices.
Expert (FMX)
The default keyboard does not support certain operations (for example,
Keyboard key combinations). The purchase of appropriate soft keyboards or physical
keyboards can make these keyboard operations possible.
Only iPads that support hover functionality can display tooltip
Tooltips
information.

7 Monitoring
Monitoring enables you to detect, diagnose, and resolve immediate issues in the network.

7.1 Applications Used in Monitoring

ENM supports tracking with both the Fault Management application set and the Network
Monitoring application set.

The Fault Management applications provide a variety of capabilities including configuration,

search, correlation, and presentation of alarm data from the network.

 The Alarm Monitor application displays open alarms based on the applied Network
Elements and alarm attributes.
 The Alarm Overview application allows you to customize workspace layouts using
widgets. These widgets include: Most Problematic Node by Count, Most Problematic
Alarm Type by Count, Severity Summary, and Alarm Type Summary.
 The Alarm Routing application allows you to configure alarm routes based on selected
alarm attributes and applied on selected Network Elements. Auto acknowledgement of
alarms and email sending on alarms are supported.
 The Alarm Search application allows you to search open or historical alarms based on
event time, alarm attributes, and node list.
 The Alarm Supervision Status application displays information related to node status
and allows you to enable, disable, and synchronize supervision on single or multiple
nodes.
 The Automatic Alarm Handling (FMX) application incorporates expert knowledge
within Fault Manager to reduce and improve the alarm information presented. With
FMX, you can automate routine correction procedures, alter or ignore alarms, create
new alarms, automatically start actions (including operating system commands),
collect more information from the network, and more.

The Network Health applications provide an overview of the network, showing alarm,
network configuration management, and KPI information all in one place.

The following applications are provided:

 Network Health Monitor

 Network Health Analysis
 Node Monitor

The Health Check application provides a health status of the node and generates reports.

 Node Health Check

Monitoring and Troubleshooting Flows is executed through the Flow Automation application.
It provides flows which can be used for monitoring the ENM system and troubleshooting
network issues.

The following flow is provided:

 Network Performance Acceptance Flow

You can execute this flow to monitor performance before and after Massive MIMO
introduction.

7.1.1 Alarm Monitor

The Alarm Monitor application displays open alarms based on the applied Network Elements
and alarm attributes.

The user can also perform alarm and node operations. The alarms are monitored for Network
Element, Management System, and Virtual Network Function Manager (VNFM). The Alarm
Monitor application displays the VNFM alarms correlated to a Network Element that
represents a Virtual Network Function (VNF) managed by the VNFM, if the VNF is
associated to the VNFM and the ECX_VNF_Alarm_Correlation rule module is enabled in
FMX. For more information, refer to Web CLI online help.

Display Open Alarm

Alarm Monitor displays all the open alarms present in the ENM database.

Acknowledge Alarm

Acknowledging an alarm informs other users that the operator has taken ownership of the
alarm and has started working on the problem.

The acknowledged alarm is visible in the UI. When the alarm is no longer active, the alarm
automatically gets cleared from Alarm Monitor UI.

The operator can also acknowledge alarms that are cleared to remove these alarms from the
Alarm Monitor UI.

If a VNF Network Element is associated with a VNFM, the acknowledgment of VNFM

alarms is propagated on the correlated VNF alarms.

Conversely, acknowledgment of VNF alarms is propagated on the correlated VNFM alarms.

Unacknowledge Alarm

An alarm that is already acknowledged can be unacknowledged to indicate that the operator is
no longer working on the alarm.

An unacknowledged alarm is visible in the system and the operator can clear this alarm.

Clear Alarm

The operator can clear both acknowledged and unacknowledged alarms. Clearing an
acknowledged alarm removes the alarm from the Alarm Monitor UI.

If a VNF Network Element is associated with a VNFM, the clearance of VNFM alarms is
propagated on the correlated VNF alarms, and the clearance of VNF alarms is propagated on
the original VNFM alarms.

Alarms on the ECM target are cleared only if the root cause VM alarms have already been
cleared.

Comment Alarm
The user can add comments on an alarm.

Enable or Disable Supervision

The operator can enable alarm supervision on Network Element and Virtual Network
Function Manager (VNFM) to start receiving alarm notifications from those nodes. ENM
automatically sets the target destination on the Network Element except for the following
node types for which the target destination must be set manually:

 EPG, vEPG, WMG, vWMG

 SBG-IS
 TSP family (CCN-TSP, CSCF-TSP, HSS-FE-TSP, MTAS-TSP, VPN-TSP, cSAPC-
TSP)
 PCC, PCG
 ESA-based nodes (GenericESA, CUDB, vCUDB, vAFG, vECE)
 EDA
 UDM (CCPC, CCRC, CCDM, CCSM, CCES) and SC

Similarly, the operator can disable alarm supervision on Network Element and Virtual
Network Function Manager (VNFM) to stop receiving alarms from those nodes, but the
existing alarms continue to be seen in the Alarm Monitor.
ENM automatically removes the target destination from the Network Element except for the
following node types for which the target destination must be removed manually:

 EPG, vEPG, WMG, vWMG

 SBG-IS
 TSP family (CCN-TSP, CSCF-TSP, HSS-FE-TSP, MTAS-TSP, VPN-TSP, cSAPC-
TSP)
 PCC, PCG
 EDA
 UDM (CCPC, CCRC, CCDM, CCSM, CCES) and SC
 vDU

If a VNF Network Element is attached to a VNFM, the operator also starts receiving alarms
from VNFM correlated to the VNF provided that alarm supervision is enabled on the VNFM
itself and that the VNFM FMX Rule module has been activated for the VNF and the VNFM.

Alarm Synchronization

Alarm Synchronization synchronizes an ENM alarm list and a node alarm list. There are two
types of synchronization:

 Manual Synchronization:

Performed only when Alarm Supervision is enabled.

 Auto Synchronization:

Performed only when automatic synchronization on FMAlarmSupervision MO is

TRUE. This occurs in the following cases:
 o State transition FM Alarm Supervision OFF > ON
o State transition FM Alarm Heartbeat FAIL > CLEAR

Filter Alarm List

An alarm list can be filtered based on the alarm attributes.

Find in Alarm List

A word or phrase can be searched in the alarm list.

Display Node List

This displays a list of the nodes on which an operator wants to monitor the alarms.

Import Nodes from Add Network Objects Flyout Panel

An operator can import the nodes using the Add Topology Data button, which opens a flyout
panel.
Valid ENM browser certificates must be installed to ensure proper behavior of the
Note: application. For instructions on how to export and install valid ENM certificates for
your browser, refer to the Security System Administrator Guide.

7.1.2 Alarm Overview

Alarm Overview provides the following features:

Add a Widget

Allows users to add a widget in the Alarm Overview UI.

Customize Layout

Allows users to customize the layout of the Alarm Overview UI

Create New Workspace

Allows users to create new workspaces on the Alarm Overview UI. The following widgets
can be added from the Add a Widget drop-down:

Most Problematic Displays node information in descending order based on the number of
Node by Alarm active alarms present on the imported nodes or selected nodes, if any. A
Count drop-down provides the option to select 5, 10 (default), or 20 nodes.

Displays the severity of open alarms on the imported or selected nodes.

Alarm Severity
Users can show or hide alarms of different severity by selecting the
Summary
corresponding check boxes in the Settings widget.
Most Problematic Displays information for imported or selected nodes, sorted by the
Alarm Type by number of active alarms per alarm type. Users can choose to display
Count information for 5, 10 (default), or 20 nodes.

Displays a graphical representation of the active alarm types present on

Alarm Type the imported or selected nodes. Under Settings, users can search for and
Summary select the alarm types to be included. Users can select up to ten alarm
types. None is selected by default.
Valid ENM browser certificates have to be installed to ensure proper
behavior of the application. For instructions on how to export and install
Note:
valid ENM certificates for your browser, refer to the Security System
Administrator Guide.

7.1.3 Alarm Routing

The Alarm Routing application provides a method to automatically acknowledge alarms and
also send email notifications about alarms to specified email addresses. A route consists of
alarms that match selected attributes and that are raised from selected nodes (Network
Elements or ENM).

The alarms that match the attributes and are raised by the nodes mentioned in the route are
filtered and action is performed based on the route type. When an alarm route is enabled,
either alarms matching the criteria are automatically acknowledged (Auto-ack route) or an
email notification is sent (email route).

The user can perform the following operations on the routes:

 Create route
 Edit route
 Enable route
 Disable route
 Delete route

Valid ENM browser certificates must be installed to ensure proper behavior of the
Note: application. For instructions on how to export and install valid ENM certificates for
your browser, refer to the Security System Administrator Guide.

7.1.4 Alarm Search

Alarm Search displays details for open or historical alarms.

Users can search for alarms using the following criteria: node, alarm attributes, alarm time.

Users can also customize the Alarm Search UI, configure table columns, and export alarms to
a file.'

7.1.5 Alarm Supervision Status

Alarm Supervision Status displays information related to node status and allows the user to
enable, disable, and synchronize supervision on single or multiple nodes. The alarms are
supervised for Network Element, Management System, and Virtual Network Function
Manager (VNFM).

Valid ENM browser certificates must be installed to ensure proper behavior of the
application. To learn how to export and install valid ENM certificates for your browser, refer
to the Security System Administrator Guide.

7.1.6 Automatic Alarm Handling

Automatic Alarm Handling is a framework for the development, instrumentation,

management and execution of event processing rules for providing automatic event and
incident management.

Automatic Alarm Handling is built on the 3rd Generation of Fault Management Expert
(FMX). FMX provides the capability to define complex alarm filtering, correlation,
enrichment and decision support rules based on alarm information, node interaction, or
external data sources. This is translated into automatic troubleshooting and root cause analysis
(RCA) capabilities.

In addition, the incident resolution procedure can also be automatically executed, or a Trouble
Ticket or a Work Order can be automatically generated to the appropriate receiver based on
issue type. FMX increases NOC efficiency by decreasing Mean Time to Resolution (MTTR),
as well as improving customers' network availability. Turnkey rules are provided within ENM
for most of the common alarm handling situations. Customized FMX rules are requested from
Ericsson as a service or created by the user. Education for re-engineering NOC processes into
rules is also available as an Ericsson service.

FMX features incorporate expert knowledge within the Fault Manager in order to reduce and
improve the alarm information presented to the operators. With FMX, the Fault Manager is
able to automate routine correction procedures, alter or ignore alarms, create new alarms,
automatically invoke actions (including operating system commands), collect more
information from the network and more.

An expert in the managed domain must specify the following:

 Attributes identifying the incoming alarms to be processed by FMX

 Rules to execute in order to analyze the situation
 Actions to be performed
 Resulting alarms to be presented

The Fault Management System receives alarms in the form of standard Alarm Records,
updates the Alarm Monitor, updates the Alarm Search and further distributes the Alarm
records. Without FMX, alarms are processed as follows:

 Alarms arrive in the Fault Management System

 The alarms are converted to Alarm Records
 The Alarm Search is updated with the Alarm Records
 The Alarm Monitor is updated with the Alarm Records
  In addition to the Alarm Search and Alarm Monitor applications, various other
presentation functions may exist and have access to the alarms in order to graphically
present them to the operator.

If FMX is present, some additional steps are taken:

 All incoming alarms are examined; alarms that satisfy certain criteria are sent to FMX
for processing. Such Alarm Records generate FMX events.
 Depending on the type of processing specified, these alarms may or may not be
written to the Alarm Search and Alarm Monitor.
 FMX processes the FMX events by executing FMX rules.
 New or changed alarms may be the result of FMX processing and corresponding
Alarm Records are transferred to the Fault Management System as incoming alarms to
be processed as usual. Various actions may also result from FMX processing.

Runtime and Development Environment

FMX includes both a Runtime environment for processing events and managing rules and a
Development environment for creating and verifying rules.

This provides a workflow rule editor where business processes for

FMX
alarm handling can be defined graphically as step-by-step decision logic
Development
trees (rules) and stored in containers for modularity and reusability (rule
Environment
modules).

This provides a distributed event stream processing rule inference

FMX Runtime
engine for processing events and a state machine with pluggable
Environment
connection modules for interaction towards external data sources.

Applications

The main component of FMX is the Rule Inference Engine (fmxie) service which subscribes
to preconfigured ENM FM events and listens to the real-time FM event flow. When an event
is triggered, the FMX Engine executes the corresponding rule(s), which are logical decision
tree flows for automatic alarm processing and action execution (such as filtering, correlation,
enrichment, troubleshooting and node interaction).

FMX provides an automation framework with the following Graphical User Interface (GUI)
applications that enable users to create, manage and monitor rules for providing Automated
Alarm Handling:

facilitates rule and utility modules administration, modification of module

Module
runtime rule policy parameters, viewing active rule module triggers and
Management
viewing rule execution statistics.

Monitor dashboard for tracking the number of processed events and executed rules.

Rule Trace
 graphical Rule IDE for creation of event processing rules in form of logical
flows with pluggable and configurable utility blocks.supports subscription
Rule Editor
to real-time block-by-block rule execution trace messages. Used for rule
development and troubleshooting purposes.

Event allows creation and injection of pre-defined alarm and error sequences into
Simulator the FM system to facilitate rule modules validation.

supports definition of individual time events and recurring time events

Time Periods (weekends, holidays, maintenance time, rush hour, and so on) for use in the
rule modules as rule triggers or rule logic conditions.

FMX also provides a CLI for Module Management.

7.1.7 Network Health Monitor

Network Health Monitor (NHM) is a primary application or starting point for network
monitoring.

It provides a graphical overview of current network health data, and supplies configuration
state information, alarm data, and Key Performance Indicator (KPI) information.

NHM can be easily expanded to monitor faults within the network by adding new widget
instances, with new widget settings to suit particular needs. A widget is a small application
which represents a set of functionality to monitor the network.

The first time NHM is launched (for a user), all nodes on the system are automatically added
for network monitoring.

7.1.7.1 Widgets in the Network Health Monitor

When opened, the Network Health Monitor web-based user interface consists of the following
widgets which can be used to monitor selected nodes (monitoring scope). The scope is used to
determine the data returned in the widgets:

Network
Health
Information Function
Monitor
Widgets
Most
Displays a list of the most problematic alarm types in
Problematic Alarm
descending order based on the alarm count of the
Alarm Type by Information
monitoring scope.
Count
Displays a list of the most problematic nodes in
Most Alarm
descending order based on the alarm count of the
Problematic Information
monitoring scope.
 Network
Health
Information Function
Monitor
Widgets
Node by Alarm
Count
Alarm Severity Alarm Displays a table of the alarm count grouped by severity
Summary Information based on the monitoring scope.
Displays a table of the alarm count grouped by type
Alarm Type Alarm
based on the monitoring scope. Alarm types to be
Summary Information
included are selected from the widget settings.
Displays the number of nodes monitored per node type
and a summary of node state. The node states are:
Configuration
Operational, Partial, Non-Operational, and Unknown.
Network State State
Details are provided for eNodeB DU Radio Node,
Information
eNodeB Baseband Radio Node, eNodeB Pico Radio
Node, and RNC Radio node types.
Displays the number of nodes monitored per node type
Configuration
Network Sync and a summary of node synchronized state
Sync
Status (Synchronized and Not Synchronized for all supported
Information
Network Elements).
Displays the number of nodes, based on the monitoring
scope, that are in breach of the KPI Threshold value for
the selected KPIs.
Nodes
Breached per KPI Information
For KPIs defined on multi-instance reporting objects, for
KPI
example EUtranCellFDD, a node is considered in breach
if any of the object instances are in breach of the KPI
Threshold value.
Displays a list of the worst performing nodes for a single
selected KPI, in descending order of KPI value.
Worst
For KPIs defined on multi-instance reporting objects, for
Performing KPI Information
example EUtranCellFDD, the nodes are ranked based on
Node by KPI
the KPI values of the underlying cells. The node with the
worst performing underlying cell is presented first. The
remaining nodes are presented in descending order.

Data for each of these widgets is retrieved and presented in the Network Health Monitor user
interface.

Based on analysis of the information presented in the Network Health Monitor view, you can
choose to navigate to the following:

 The Network Health Analysis view (for a selection of nodes)

  The Node Monitor view (for a single node to refine the scope of your monitoring or
fault detection)

7.1.8 Network Health Analysis

Network Health Analysis (NHA) facilitates operational engineers by displaying node by node
Configuration Management (CM) state, FM Alarm, and Key Performance Indicator (KPI)
data for selected Network Elements.

Historical KPI data can be viewed to analyze the KPI trend over a period of up to 12 hours.

Real time KPI calculations can be triggered from NHA for up to 20 Network Elements, to
view KPI results on a one-minute interval for 60 minutes.

NHA displays CM state, FM Alarm, and KPI data using the following tabs:

This displays node-level KPI values, synchronization state, operational state, and
Node tab
FM Alarm information.

This displays cell-level KPI values, administrative state, operational state, and
Cell tab
availability status information.

This displays KPI values for KPIs reporting on non-cell reporting objects, or a
KPIs tab
mix of cell and non-cell reporting objects.

This monitors and displays the data for selected KPIs on a one-minute basis.

The tab displays the KPI values in an Objects table. A different row is created
Real time per reporting object instance for each KPI selected.
KPI tab
The KPI results can be viewed in a chart when 12 or less distinct objects are in
the real time table. Each KPI is displayed in a separate chart and each line
represents an object.
This tab displays up to 12 hours of values for the monitored KPIs on a 15-
minute basis. Each KPI is displayed in a separate chart and each line
KPI Trend represents an object.
Charts tab
The KPI Trend Charts tab can be opened when up to 10 objects are selected in
the Node, Cell, or KPIs tab.

The Network Health Analysis (NHA) web-based UI allows you to monitor a refined set of
Network Elements providing the CM state, FM Alarm, and KPI data on a node-by-node basis
or node-by-node and cell-by-cell basis. NHA displays up to 500 rows. If the scope, when
launched, contains more than 500 elements, you can use the sort, filter, and export functions
to display the elements of interest (from the complete scope of elements).

When launched from the Nodes Breached by KPI widget for a node-level KPI, the following
information is displayed in the Node tab:
  Network Element Name
 Synchronization State of the Node
 Operational State of the Node
 Network Element Type
 KPI Information
 KPI Breach Information
 FM Alarm Information by Severity

When launched from the Nodes Breached by KPI widget for a cell-level KPI, the following
information is displayed in the Cell tab:

 Network Element Name

 Cell Name
 Administrative State of the Cell
 Operational State of the Cell
 Availability Status of the Cell
 Network Element Type
 KPI Information
 KPI Breach Information

When launched from the Nodes Breached by KPI widget for a KPI having transport node type
(or a mix of Transport/WCDMA/LTE node types), the following information is displayed in
the KPIs tab:

 Object Name
 Network Element Name
 Network Element Type
 Object Type
 KPI Information
 KPI Breach Information

When launched from the Network State widget, the user interface shows the following
information in the Cell tab:

 Network Element Name

 Cell Name
 Administrative State of the Cell
 Operational State of the Cell
 Availability Status of the Cell
 Network Element Type

When launched from the Network Sync Status widget, the user interface shows the following
information in the Node tab:

 Network Element Name

 Synchronize State of the Node
 Operational State of the Node
 Network Element Type
 FM Alarm Information by Severity
Based on analysis of the information presented in the Network Health Analysis view you can
choose several actions available for the selected resource. For example, you can navigate to
the Node Monitor view for a single node to refine the scope of your monitoring or fault
detection.

You can also choose to export the data being displayed in the view.

7.1.9 Node Monitor

Node Monitor facilitates operational engineers with both fault localization and fault finding
for a selected Network Element.

Real time KPI calculations can be triggered from Node Monitor to view KPI results on a one-
minute interval for 60 minutes.

Node Monitor can be expanded to monitor additional KPIs by adding new widget instances
with new widget settings to suit particular needs.

A widget is a small application which represents a set of functionality to monitor the network.
Node Monitor provides the following widgets:

 Alarm Severity Summary

A bar chart shows the number of nodes raising alarms for selected severity levels.
Click a bar to get details of affected nodes. You can also determine which severity
levels are displayed in the bar chart.

The following severity levels are available:

o Critical: Displays the serious events in the network to be cleared immediately.

o Major: Displays the disruptive events to be cleared immediately.
o Minor: Displays non-disruptive events to be cleared as soon as possible.
o Warning: Displays abnormal condition events. These are temporary and do not
necessarily require any subsequent action.
o Indeterminate: Displays non-categorized events.
o Cleared: Displays events previously cleared.
 Alarm Type Summary

A bar chart shows the number of nodes raising alarms for selected alarm types. Click a
bar to get details of affected nodes. You can also determine which alarm types are
displayed in the bar chart.

 Cell Status
 KPI Viewer
 Most Problematic Alarm Type
 Realtime KPI Viewer

The Node Monitor web-based UI allows you to monitor a selected node's specific health
information. A list of all available actions is displayed in the top section. You can add
multiple widgets with different configurations which makes it possible to view information
for a number of KPIs simultaneously.

7.1.9.1 Widgets in Node Monitor

When launched, Node Monitor contains the following widgets and provides a node-level
view:

Node Monitor
Information Function
Widgets
Most
Displays a list of the most problematic alarm types in
Problematic Alarm
descending order based on the alarm count of the Network
Alarm Type By Information
Element.
Count
Alarm Severity Alarm Displays a table of the alarm count grouped by severity for
Summary Information the Network Element.
Displays a table of the alarm count grouped by type for the
Alarm Type Alarm
Network Element. Alarm types to be included are selected
Summary Information
from the widget settings.
Displays a KPI for the individual cells for a specific
Network Element. Each cell is displayed in an individual
row, and contains the cell type and cell ID and a hexagonal
icon showing the operational state. The latest value for the
selected KPI is visible under KPI.
KPI
Cell Status The widget contains a graphical representation of the values
Information
calculated for the specified KPI over the past 2 hours at 15
minute intervals. These values can be viewed by hovering
over the graph at the required point. A trend arrow is
located to the right of the graph. This indicates the overall
trend of the KPI. The calculation is based on the values for
the previous two hours using a linear regression formula.
Displays KPI data for all selected Network Element objects
for selected KPIs.
KPI
KPI Viewer The object name and corresponding KPI value are
Information
displayed in the KPI Viewer table. Data for up to 48 Report
Output Periods (ROPs) of selected KPIs can be exported to
a CSV file.
Displays KPI data on a one-minute basis. The widget
provides a graphical representation of the values calculated
for the specified KPI, with a line per reporting object
Realtime KPI KPI
instance.
Viewer Information
Selecting a KPI from the widget settings triggers the real
time calculation to start. To view the values for a particular
 Node Monitor
Information Function
Widgets
minute, hover over the graph at the required point. The KPI
name and unit are displayed in the widget header.

A timeline is shown below the graph. This can be used to

adjust the time window shown in the graph.

7.1.10 Node Health Check

Node Health Check (NHC) is a web-based application used to perform health checks on
nodes/Network Elements (NEs) in your network.

The following operations can be performed in the NHC application:

 Create health check profiles by customizing health check rule parameters.

o View and delete health check profiles.
 Execute health check reports in the following ways:
o Selecting predefined sets of rules with default parameters.
o Selecting health check profiles with customized rule parameters.
 View detailed information in health check reports about the health status of nodes.
 Compare health check reports.

7.1.11 Network Performance Acceptance Flow

Network Performance Acceptance Flow collects a set of user-selected KPIs for selected
network elements and associated cells.

The application can be configured to run at a scheduled time or executed immediately. It can
be configured to send the KPI Results Report and Flow Configuration Summary Report to a
specified email address.

The KPI Results Report is available to download once KPI collection has started. It retrieves
KPIs every fifteen minutes until the flow execution period has completed. The report is
available to download for seven days after the flow has finished.

Email support is also available.

7.2 Network Viewer

Network Viewer is a web application that renders Network Elements and supported
relationships in a graphical way.

The representation of the network is made up of two views:

 Tree View
 This view is used to select which Network Elements to view in the map. All nodes are
represented in a hierarchical folder structure. The hierarchy can be selectively changed
between the following structures:

o Network Data Structure

Nodes are shown below folders (possibly nested) representing the containing
subnetwork.

o Transport Topology Structure

Nodes are shown within collections (possibly nested) representing a flexible

partitioning of the network.

 Map View
o Selected nodes can be rendered on a geographically referenced map or on a
logical map.
o A geographical map only renders nodes if they have coordinates.
o A logical map renders all nodes.
o Both geographical and logical maps render any supported relationships as a
line between the relevant nodes.

Network Elements can be manipulated through a set of actions on nodes. Available actions
depend on the view being worked from, as follows:

 Creation of nodes is available irrespective of the map view being used.

 Placement of nodes is only available from the geographical map view.
 Deletion of nodes from ENM is available from the Action bar, the Applied list, and the
network map, irrespective of the map view being used.

The Network Viewer link is located in the Monitoring section of the ENM Launcher.

All Network Elements supported by ENM are rendered in the map. Supported relationships
between Network Elements are also rendered in the map.

The following table outlines the actions that can be completed using the Network Viewer.

Activity Description
The network resources (subnetworks, collections, and nodes) are
Display network shown in the tree view.
resources
The map view is not populated.
The network resources (subnetworks, collections, and nodes) are
Navigate network data shown in the tree view with expandable or collapsible folders.
in the tree view
The map view is not changed.
 The applied network resources (subnetworks, collections, and
nodes) are shown in the applied tab.

The applied network resources are rendered in the geographical

map or the logical map depending on which map is being used.
Render the applied
selection on the map In a geographical map, nodes that have coordinates are rendered
view as icons.

In a logical map, all nodes are rendered regardless of whether

they have coordinates or not.

Subnetworks and collections are not represented in the map view.

Relationship lines are rendered between nodes on a map if the
View relationships rendered nodes are relevant to the supported relationships and the
relationships are configured in the network.
Zoom in or out on the
Zoom in or out on the selected portion of the map view.
map view
Pan the map view Pan so that a different portion of the map view is shown.
Show related nodes For a selected node, the related nodes can be shown.
Set the coordinates of a The node with the specified coordinates is displayed on the
node geographical map view.
Select the transport
A different topology hierarchy of the tree view is shown.
topology hierarchy.
Render the alarm state
A summary of the alarm state of nodes is shown on geographical
of nodes on the map
and logical map views.
view.
Add node The Add Node application is launched.
Delete Node is started. On confirmation, this causes the node to
Delete node
be deleted from ENM.
Launch Alarm Monitor
The Alarm Monitor application is launched for the selected node.
on a selected node
Launch Alarm Monitor The Alarm Monitor application is launched in the context of
for related nodes related nodes.
Launch Element
Manager on a selected The Element Manager is launched for the selected node.
node
Launch Topology
The Topology Browser application is launched for the selected
Browser on a selected
node.
node
Launch Node CLI on a
The Node CLI is launched for the selected node.
selected node
Set a tile server for the The map view is shown with a geographically referenced map as
map view the background.
7.3 CLI Command Sets Used in Monitoring
The following command sets are used in Monitoring:

 alarm
 fmedit
 netlog
 nhc

Full information about the commands within the command sets, including command
Note:
syntax and role requirements, is provided in the online help.

7.3.1 Manage Alarms - alarm Command Set

Command Description
Ack Acknowledge an alarm for network nodes.
Clear Clear an alarm for network nodes.
 Add a comment to alarms for the network nodes.
Comment  View alarm comments for the network nodes.

Disable supervision for the nodes in the network and change any or all the
attributes (automaticSynchronization, heartbeatTimeout, and heartbeatInterval).
Disable
These attributes can only be used after the alarm supervision status is set to to
enabled.
Enable supervision for the nodes in the network and change any or all the
Enable
attributes (automaticSynchronization, heartbeatTimeout, and heartbeatInterval).
Query alarms for the network nodes. The output is ordered by severity from
Get
critical to cleared, then by event time from the most recent.
Hist Query history alarms for the network nodes.
Get alarm supervision status for the network nodes either in a list or in a table
Status
(depending on option selection).
Sync Synchronize all alarms for the network nodes.
Unack Unacknowledge an alarm for network nodes.
cmedit command must not be used to perform
Note:
any of the above actions.

7.3.2 Perform Fault Management Operations - fmedit Command Set

Command Purpose
Create alarm routes in ENM.
Create
 Command Purpose
Create an association between targetType and CPI library.
Modify alarm routes.

Set Modify an association between targetType and CPI library.

Modify alarm severity in the system on a per-neType basis.

Query alarm routes.

Get Query an association between targetType and CPI library.

Query alarm severity that were modified in ENM.

Delete alarm routes.

Delete Delete an association between targetType and CPI library.

Delete alarm severity that was modified in ENM.

cmedit command must not be used to perform any of the
Note:
above actions.

7.3.3 Retrieve NE Logs - Netlog Command Set

Command Purpose
Describe Get log types for one or more Network Elements.
Upload Upload log files from one or more Network Elements to ENM.
Check the status of the upload action for the log types for one or more Network
Status
Elements.
Download Download log files from ENM to a user device.
Delete Delete, in ENM, the collected log files for one or more Network Elements.

7.3.4 Perform Node Health Checks and Manage Their Acceptance Criteria -
nhc Command Set

Command Purpose
Upload, download, overwrite, or delete acceptance criteria for the node health
ac
check.
rep Run and manage node health check jobs and download the report.
compare Create an NHC comparison job, which compares selected NHC Reports and
run generates a comparison report.
Display statuses of NHC comparison jobs that currently are in progress or are
compare -st
completed (successful or failed).
 Command Purpose
compare -dl Download selected NHC Comparison Report that is in completed state.

7.4 Node Health Check from CLI

Node Health Check (NHC) is a CLI-based diagnostic tool that allows the user to determine
the state of a Network Element (NE) based on user-defined acceptance criteria.

The user specifies the NEs of interest and the acceptance criteria to use. For example, the user
specifies there should be no alarms on the network element and then executes a check to
confirm that the network element is in the desired state. It is possible to run the health check
without specifying any user-defined acceptance criteria in which case default criteria are
applied. The acceptance criteria are defined in XML files and then imported into ENM for use
in executing health check jobs with the verdicts stored in report files which are downloaded
and analyzed. It is also possible to compare two reports (for example, pre and post-upgrade
checks) to get information if crucial system parameters have deteriorated. LTE Network
Elements of type eNodeB in DU Radio Node, Core Network Elements of type MGW, RBS
and RNC are supported.

Node Health Check is implemented using the nhc command set (see Perform Node Health
Checks and Manage Their Acceptance Criteria - nhc Command Set.)

7.4.1 Diagnostic Checks

NHC supports the following diagnostic checks:

Check Name Explanation

Abnormal
Displays all the NE boards that have abnormal restarts.
Restarts
Alarms Displays the list of alarms active on the NEs.
Errors Displays all the errors on the NE boards.
Disabled Displays NEs that have Plug-In Units (PIUs) with an UNLOCKED
Unlocked PIUs administrative state and DISABLED operational state.
Checks the available disk space on the NE. This lists the C Drive and D
Disk Space
Drive, and displays the result in megabytes.
Hardware
Displays all the hardware installed in subracks and slots in the NEs.
Version
Displays links with a DISABLED operational state and devices which
Link and
have both a DISABLED operational state and an UNLOCKED
Device Status
administrative state.
Red LED Status Displays all the NE boards that have red LED switched on.
Upgrade
Displays the upgrade packages currently executing on the NEs.
Package
7.4.2 Acceptance Criteria

Acceptance criteria are defined by the user in XML files that are uploaded to the NHC
application. The criteria for the diagnostic checks that are performed in a single node Health
Check job are all defined in a single XML file.

After uploading, the Acceptance Criteria are available to all users. If the criteria need to be
modified, users can download and modify the existing acceptance criteria XML file. Users
can then upload the modified XML file and overwrite the existing acceptance criteria.

7.4.3 Reports

The output of the NHC commands, together with results of the applied Acceptance Criteria,
are stored in a single HTML report file. Users can download this file to their local file system
to view this information.

7.4.4 Comparison Reports

Comparison reports are outputs that contain information from both inputs (two reports being
compared) with additional verdicts referring to possible deterioration of check results.

For example, if the newer of two reports contains new alarms, the alarm check comparison
verdict is Failure.

7.4.5 Supported Network Elements

The following node types are supported by the Node Health Check application:

 LTE Network Elements of type eNodeB in DU Radio Node

 Core Network Elements of type MGW
 RBS
 RNC

7.5 Fault Management

Fault Management (FM) monitors the network for faults and events.

Faults and events can occur in any of the following locations:

 Network Elements (NE)

 Virtual Network Function Managers (VNFM)
 Ericsson Network Manager (ENM)

FM verifies that alarms are received and processed in ENM through web-based Command-
Line Interface (CLI) commands and a web-based GUI. FM also receives and processes events
from ENIQ-S (external system). It then sends these events to the GUI, to the CLI, and to the
Network Management System (NMS) as other events. ENM supports alarm history for 90
days. Alarms older than 90 days are automatically removed from ENM storage. Alarm history
can be viewed through the CLI or through the GUI five minutes after the alarms are received
in the ENM system. A CORBA-based Northbound Interface (NBI) can be used to integrate
and communicate alarms from ENM to external systems.

Architecture

The FM solution in ENM is implemented over a layered architecture. The web-based

responsive GUI with integrated help is terminated in a REST interface at the service layer.
FM connects to the network element from the service layer through mediation using either an
asynchronous supervision or an event-based interface.

Mediation resolves the events resulting in the execution of flows on a CAMEL engine. The
flows execute tasks such as activating or deactivating the alarm monitoring on the network
element. Mediation requests are routed to available FM instances running across the pay load
blades in a load-balanced manner. Whenever an alarm or event is received by FM, the alarm
is communicated by the mediation layer to the service layer. After correlation and persistence,
the alarm is communicated to the presentation layer to display in the FM GUIs.

In parallel, the alarms are communicated to the NBI layer to be communicated to external
systems through the FM NBI.

Usability

Using the FM GUIs and CLIs, it is easy to perform operations for Network Elements, alarms,
and events.

The Network Elements that the user wants to monitor can be imported from the Network
Explorer. Enabling or disabling alarm monitoring for one or more selected Network Elements
can be performed by a single action.

Alarms generated by ENM can be seen by adding ENM Management System in the Network
Elements. Alarm processing in FM does not involve integer or string conversions for any
alarm attribute. The FM GUI reflects alarm attributes with values received from the network
element.

A fully integrated Help shows the user how to enable or disable the alarm supervision using
the CLI or the Alarm Monitor application. The web-based CLIs provide similar user-friendly
functionality. Northbound Interface is supported for the FM GUIs.

A range of applications is available:

 Alarm Monitor
 Alarm Supervision Status
 Alarm Search
 Alarm Routing
 Alarm Overview

 An operator can see heartbeat failure alarms for nodes created to test for FMX-
Note:
generated alarms.
  Even if the node with a dummy IP address shows a heartbeat failure alarm, it is
possible to see FMX-generated alarms in FM for that node.

Northbound Interface

The following protocols are used by the Northbound Interface:

 Fault Management (FM) Basic Network Surveillance Interface (BNSI)

 Fault Management (FM) CORBA
 Fault Management (FM) Simple Network Management Protocol (SNMP)

8 Performance and Optimization

Performance and Optimization enables you to manage performance data and KPIs, and
optimize Physical Layer Cell Identities (PCI).

8.1 Applications Used in Performance and Optimization

A set of applications for Performance and Optimization is available.

 The Performance Management Initiation and Collection application enables you to

control which performance counters and events are produced and/or collected for
nodes in the network. Files are also made available on a Northbound Interface (NBI).
 The KPI Management application enables you to set, create and activate performance
KPIs against the network.
 The Automatic ID Management application is used to detect and resolve Physical
Layer Cell Identity (PCI) conflicts in an LTE Network.
 The Spectrum Measurement Management application (together with the Uplink
Spectrum File Collection (ULFC) application) allows the operator to remotely capture
and analyze the Radio Frequency (RF) information received by a base station.
 The Analytic Session Record (ASR) application provides a near real-time Analytic
Session Record for LTE (ASR-L) and NR (ASR-N). ASR supports Time Division
Duplex (TDD), Frequency Division Duplex (FDD), and Mixed Duplex mode.
 The Flexible Counter Management application allows the operator to manage Flexible
EBS-N counters.

8.1.1 Performance Management Initiation and Collection

Performance Management Initiation and Collection (PMIC) provides the capability to:

 Initiate the periodic output of counters and events, and collect the output files from the
node.
 Request the periodic upload of PM statistical files from nodes, process the files, and
generate output files in the required format.
 Periodically collect counters through SNMP GET operations and generate the PM
statistical files.
These files are provided to Performance Management Northbound Interface (PM NBI).

PMIC Subscriptions

PMIC subscriptions contain information about the Network Elements being managed, active
counters or events, and the schedule information for data to be collected. Subscriptions are
mapped directly to scanners or jobs on the Network Element, where applicable, with a
representation of each scanner/job stored in the Data Persistence Service (DPS) in ENM.

There are two main subscription categories for PMIC:

1. Statistical (also called counters)

2. Events

 Automatically polled for, collected, and stored in designated directories.Counters are

output to a file. Events can be output to a file, to a stream terminating in a northbound
application, or both. The output files coming from the node are:
 Pushed from the node to ENM where the files are processed and stored in designated
directories.

For details on the supported nodes, see ENM Supported Network Elements, 3/1029-AOM 901
151.

PMIC supports the following four subscription types:

1. User-defined
2. Criteria-based
3. System-defined
4. Application-defined

User-Defined Subscriptions

A user-defined subscription is one that can be manually created by a user. A user can
manually select nodes, counters or events (where applicable), and scheduling information.

Only nodes with PmFunction.pmEnabled=true are allowed to be added to subscriptions.

When PmFunction.pmEnabled is set to false, the affected nodes are removed from the
subscriptions.

The following user-defined subscriptions are supported:

1. Statistical:
o Standard
o MO Instance (WRAN)
o Cell Instance (WRAN)
o Radio Environment Statistics (WRAN)
2. Events/Recording:
o Cell Trace / EBS-L (LRAN)
o Cell Trace / EBS-N (NRAN)
 o UE Trace (LRAN, NRAN, and Core)
o EBM / EBS-M (Core)
o GPEH (WRAN)
o CTR (WRAN)
o UETR (WRAN)
o BSC Recordings (GRAN)
o MTR (GRAN)
o BSC Performance Events (GRAN)
o RTT (GRAN)

The BSC Performance Events (GRAN) subscription activates RPMO events on the
BSC (ECIM) nodes. These events are streamed to ENM where they are processed and
stored as encoded BSC Performance Events binary files or as decoded BSC
Note:
Performance Events text files. Additionally, BSC Performance Event Statistics files
and BSC Performance Event Monitors files can be generated from the terminated
RPMO event streams.

Criteria-Based Subscriptions

Criteria-Based Subscription (CBS) is a user-defined subscription with a dynamic node list

which is populated according to specific criteria. The criteria used in a CBS is a saved search
which the user can import from the Network Explorer application.

If any of the following changes occur in the network, the subscriptions are updated to include
or delete the node:

 Addition of a new node

 Deletion of a node
 Upgrade of a node
 Change in any of the MO attribute values mentioned in the criteria

Only nodes with PmFunction.pmEnabled=true are allowed to be added to a CBS

The following user-defined subscriptions support CBS:

 Statistics-based subscriptions
 Cell Trace
 General Performance Event Handling (GPEH)
 Mobile Traffic Recording (MTR)
 BSC Performance Events
 Real Time Tracing (RTT)

System-Defined Subscriptions

System-defined subscriptions are automatically created by PMIC because of the presence of

particular node types and node versions.

System-defined subscriptions can be active or inactive by default.

The following system-defined subscriptions are supported:

  CTUM (Cell Trace UE ID Mapping)
 CCTR (Continuous Cell Trace)
o ContinuousCellTraceSubscription
o Continuous Cell Trace NRAN
 Statistical
o (v)EPG System Statistical Subscription
o (v)EPG-OI System Defined Statistical Subscription
o (v)WMG System Statistical Subscription
o (v)WMG-OI System Defined Statistical Subscription
o ERBS System Defined Statistical Subscription
o Fronthaul 6020 Primary System Defined Statistical Subscription
o Fronthaul 6080 Primary System Defined Statistical Subscription
o Fronthaul-6392 Primary15min System Defined Statistical Subscription
o Fronthaul-6392 Primary24h System Defined Statistical Subscription
o MINI-LINK-6351 Primary15min System Defined Statistical Subscription
o MINI-LINK-6351 Primary24h System Defined Statistical Subscription
o MINI-LINK-6352 Primary15min System Defined Statistical Subscription
o MINI-LINK-6352 Primary24h System Defined Statistical Subscription
o MINI-LINK-PT2020 Primary15min System Defined Statistical Subscription
o MINI-LINK-PT2020 Primary24h System Defined Statistical Subscription
o RadioNode System Defined Statistical Subscription
o RBS System Defined Statistical Subscription
o RNC Primary System Defined Statistical Subscription
o RNC Secondary System Defined Statistical Subscription
o SBG-IS System Defined Statistical Subscription
o SIU02 System Defined Statistical Subscription
o TCU02 System Defined Statistical Subscription
o vTIF System Defined Statistical Subscription
o cSAPC-TSP System Defined Statistical Subscription
o CSCF-TSP System Defined Statistical Subscription
o HSS-FE-TSP System Defined Statistical Subscription
o MTAS-TSP System Defined Statistical Subscription

Only nodes with PmFunction.pmEnabled=true can be part of a system-defined

subscription.

A system-defined subscription is deleted automatically when

PmFunction.pmEnabled=false for the last node of the given node type.

Application-Defined Subscription

An Application-defined subscription is created and managed outside PMIC, by the

application. PMIC is involved in the activation or deactivation of the subscription, scanner
master activities where applicable, and subscription audit.

The only actions that are available for application-defined subscription types in PMIC UI are:

 View Subscription
 View PM Node Processes
 View Subscription Logs
Application-defined subscription can have NEs with either PmFunction enabled or disabled.

Activation of application-defined subscription results in the activation of only those NEs with
PmFunction enabled. Any NEs that are part of the subscription with PmFunction disabled are
not activated. This is reflected in the subscription operational state as follows:

 OK - All NEs are provisioned successfully.

 ERROR - Some of the NEs are not provisioned successfully.
 LIMITED - Some of the NEs are not provisioned since PmFunction is disabled for
those Network Elements.
 N/A - The Subscription is currently not activated.

The LIMITED operational status is only applicable for application-defined subscription and is
included in the legend of the Subscription Operational Status active chart in PMIC UI, if at
least one active subscription is in LIMITED state.

The View Subscription page in PMIC UI for application-defined subscription contains a new
filterable column in the resources tab, to show the PmFunction status for each Network
Element.

PMIC supports the following application-defined subscriptions:

 Analytic Session Record for LTE (ASR-L)

 Analytic Session Record for NRAN (ASR-N)

Activation

The activation of a subscription initiates jobs on the nodes included in the subscription, where
applicable. The job initiation can be for the output of both counters and events depending on
the type of subscription. The security information required to connect to the node is retrieved
during the activation.

PMIC does not support PM job initiation on the node for the following Network
Element types:

 BSC (ECIM)
 CCDM
 CCES
 CCPC
 CCRC
 CCSM
Note:
 Compact CTC
 Compact IP-STP
 Compact MSC-S
 Compact vCTC
 Compact vIP-STP
 Compact vMSC-S
 CTC BC (BSP)
 CTC BC (IS)
 CTC DB
  EIR-FE, vEIR-FE
 Fronthaul-6392
 HLR-FE (APZ)
 HLR-FE (BSP)
 HLR-FE (IS)
 IP-STP
 MINI-LINK 6251
 MINI-LINK 6252
 MINI-LINK 6262
 MINI-LINK 6291
 MINI-LINK-6351
 MINI-LINK-6352
 MINI-LINK 6366
 MINI-LINK 6651
 MINI-LINK 6654
 MINI-LINK 6655
 MINI-LINK 6691
 MINI-LINK 6692
 MINI-LINK 6693
 MINI-LINK 6694
 MINI-LINK CN210
 MINI-LINK CN510R1
 MINI-LINK CN510R2
 MINI-LINK CN810R1
 MINI-LINK CN810R2
 MINI-LINK LH
 MINI-LINK-PT2020
 MINI-LINK TN
 MSC-S BC (BSP)
 MSC-S BC (IS)
 MSC-S DB
 SBG-IS
 SC
 Switch-6391
 vAFG
 vCTC HC
 vDU
 vHLR-FE
 vMSC-S HC
 CUDB
 vCUDB
 ESA Based nodes
 cSAPC-TSP
 CSCF-TSP
 HSS-FE-TSP
 MTAS-TSP

More information about these is available in the ENM Performance Management

System Administrator Guide.
The counters or events supported by the node version, as well as the parameters required by
the node, are sent during the activation request. An object representing the job and its state on
the node is stored in the DPS.

Internal notifications are sent on the success or failure of the activation and are used to update
the status of the subscription. The success or failure of each job initiation on a node is logged.

On activation of a statistical subscription, the user is warned if selected counters are already
included in another active subscription.

1. RNC Network Element types support a maximum of 2 active ROP’s

simultaneously . PMIC displays an error, blocking the activation in case the
user attempts to activate more than 2 ROPs on the selected RNC NE(s).
2. RNC Network element type supports activation of up to 10% of the overall
Note: counters available for selection, in a 5 min ROP. At subscription creation,
PMIC displays a warning, advising the user to include only 10% of the
counters while creating a 5min ROP subscription.

For details refer to ENM Online Help, AOM 901 151.

Deactivation

The deactivation of a subscription results in the jobs on those nodes included in the
subscription being removed or suspended. File collection tasks for the nodes in the
subscriptions are removed and file collection ceases. For each job removed or suspended on
the node, the corresponding object representing it in the DPS is removed or updated with the
status of the job. This depends on the job and the node being managed.

Notifications are sent on success or failure of the deactivation and are used to update the
status of the subscription. The success or failure of each deactivation request on a node is
logged.

Scanner Master

Scanner master uses the output of scanner polling to actively manage the scanners/jobs on the
node by comparing the output of scanner polling against the Network Element with the
expected status as stored in the DPS.

PULL-Based File Collection

The update of the scanner object in DPS results in DPS notifications being sent. The PMIC
service layer listens for these notifications. The update of a scanner object to active state
results in the nodes being included in an initiation cache. These updates also use the interface
for file collection so that jobs are added to or removed from file collection.

The activation of a subscription schedules the file collection tasks to be initiated. The
collection tasks are based on the set of nodes included in the subscription and the Report
Output Period (ROP) supported by the node. Depending on the node type, a ROP is selected
which can be of 1 minute, 5 minutes, 15 minutes, 30 minutes, 1 hour, 12 hours, or 24 hours
duration.
File collection depends on the subscription schedule. If the subscription is activated
immediately after creation, PMIC collects the first ROP after the activation time. If the
subscription is scheduled to be activated at a later date, file collection collects the first ROP
following the deferred activation time. This can continue indefinitely if the subscription has
no end date defined or the subscription will end at a specific date and time as per its schedule.
Scanner polling is run at regular intervals by PMIC and sends a scanner polling request to
mediation for each Network Element being managed by PM. This results in the triggering of a
mediation flow which retrieves all scanners for a particular node, the result of which is sent
back in the form of a scanner polling result.

Once initiated, file collection continues to run autonomously. Success or failure on individual
collections is logged and summary information relating to files missed and data processes is
reported on the UI. File collection requests use the connectivity information for each node
when setting up the connection and retrieve the files over SFTP. Up to three attempts are
made to retrieve a file. If unsuccessful, further attempts are made with Performance
Management File Recovery. Notifications are sent on success or failure and are used to update
metrics and heartbeats. On retrieval, the files are stored in designated directories for use by
north bound applications. The collected files are stored on the ENM shared storage.

The Data Rate/Minute heartbeat in the UI shows a summary of the volume of PM files
collected for each minute over the last 60 minutes.

PUSH-Based File Collection

The activation of a subscription schedules the files to be pushed from the managed Network
Elements to the Software Management Repository Service (SMRS). The SMRS is responsible
for accepting SFTP requests from the set of nodes included in the subscription.

An SMRS audit procedure - based on either a lag time or a marker file depending on the
network element type - is used to determine the completion of file transfers.

On completion of the audit, any files identified will result in the triggering of a post
processing flow. Success or failure on individual processed files is logged and summary
information relating to files missed and data processes is reported on the UI. Notifications are
sent on success or failure and are used to update metrics and heartbeats.

Once the post processing flow has successfully processed all files, it will result in them being
stored in their designated directories for use by north bound applications. The processed files
are stored in ENM shared storage.

File Generation

The activation of a subscription schedules the files to be generated through SNMP GET
operations. The generation task is based on the set of nodes included in the subscription and
the ROP.

Model Identity Support

PMIC supports the use of different model identity versions. When editing a subscription, the
user is not allowed to include a node with an invalid model identity. PMIC presents a super
set of counters or events based on the model identities of the nodes in the subscription.

When the subscription is activated, PMIC ensures that only the counters and events supported
by each node are added to the created scanner on that node.

PM Node Processes

Scanner polling is run at regular intervals by PMIC. The PM Node Processes page displays
the status of the scanners/jobs in the network, and the user can locate those nodes that have
processes in error.

The page can be viewed for an individual subscription or for a specific node (by selecting the
node from a subscription’s Resources tab).

When viewing the page for a specific node, all its processes are shown, including predefined
processes where the node type supports them. Also, the user can activate or deactivate
predefined processes for counters from this page.

PULL-Based File Recovery

PM data is generated periodically by Network Elements and is stored in the form of files.
PMIC collects these files and places them in a central location where they can be accessed by
external systems.

Except for one-minute ROP (for which file recovery is not supported), PMIC tries to recover
uncollected files in the following scenarios:

 Missed file during ROP: PMIC retries file collection of the missed file in the next
ROP only.
 Node reconnected to ENM: When a node reconnects, PMIC tries to recover any
missing statistical files for this node for the preceding 24 hours.
 Scheduled recovery: Scheduled file recovery runs to recover any missing statistical
files based on two different recovery periods that can be configured for a combination
of ROP granularity and node types.

For complete details, see the ENM Performance Management System Administrator
Guide.

 Network Element is added: When a node is added to an active subscription, PMIC

tries to recover statistical files up to the recovery period or the subscription start date
and time, whichever is shortest.
 Recovery on startup: When PMIC is started, it recovers missing statistical files for all
the nodes for the configured recovery period.

PUSH Based File Recovery

PM data is generated periodically by Network Elements and is stored in the form of files.
These files are pushed towards the SMRS. If a file is not successfully received by the SMRS
the following recovery scenarios apply:

 Missed file during ROP: The Network Element tries to re-establish an SFTP connect
towards the ENM for every ROP until a successful connection is made. The node
pushes the current and any previous ROP files.
 Node reconnected to ENM: When a node reconnects, the Network Element pushes the
current and any previous ROP files.
 Recovery during file collection: This is currently supported for MINI-LINK Outdoor
nodes (MINI-LINK 6351,MINI-LINK 6352, MINI-LINK PT 2020, Switch 6391,
Fronthaul 6392). These are nodes that push all previous 95 ROPs along with the
current ROP in a single file. While processing the file, any ROPs that had not been
received and processed in a previous ROP (for up to the previous 95 ROPs) are
processed in the current ROP.
 Contiguous file recovery (Push): During file collection where node pushes files on
demand, if there are missed ROPs, then files will be collected in the subsequent ROP
up to 3 contiguous ROPs. The missed ROPs which are non-contiguous and more than
3 contiguous ROPs will be collected during Scheduled Recovery. This behavior is
supported by MINI-LINK Indoor family of nodes ( MINI-LINK TN, MINI-LINK LH,
MINI-LINK CN210,MINI-LINK CN510R1,MINI-LINK CN810R1,MINI-LINK
CN810R2,MINI-LINK CN510R2, MINI-LINK 6691, MINI-LINK 6692, MINI-LINK
6693,MINI-LINK 6291, MINI-LINK 6694, MINI-LINK 6651 , MINI-LINK 6654,
MINI-LINK 6655, MINI-LINK 6366, MINI-LINK 6251, MINI-LINK 6252, MINI-
LINK 6262).
 Contiguous file recovery (historical counters): During file collection where ENM
generates historical files, if there are missed ROPs, then the files will be collected in
subsequent ROP up to 1 missed ROP. If there are any missed ROPs in previous ROPs,
then they are recovered during Scheduled recovery. This behavior is supported by
MINI-LINK Indoor family of nodes ( MINI-LINK TN, MINI-LINK LH, MINI-LINK
CN210,MINI-LINK CN510R1,MINI-LINK CN810R1,MINI-LINK CN810R2,MINI-
LINK CN510R2, MINI-LINK 6691, MINI-LINK 6692, MINI-LINK 6693,MINI-
LINK 6291, MINI-LINK 6694, MINI-LINK 6651 , MINI-LINK 6654, MINI-LINK
6655, MINI-LINK 6366, MINI-LINK 6251, MINI-LINK 6252, MINI-LINK 6262).

Northbound Access to PM Files

Collected files are stored on the NFS in designated directories and data about each file -
including its storage location - is stored in the FLS (File Lookup Service). NB consumers of
PM files can query the FLS for the locations of desired files, and then SFTP them using the
scripting service.

PM files of different types have separate and configurable retention periods. PMIC deletes
both the file and FLS record once the retention period has expired.

In addition, a symbolic link can be created for each file. ENIQ uses these links to access the
files and it deletes the link once it has consumed the file.

8.1.2 KPI Management

KPI Management allows system administrators to:

 Assign Network Elements to existing KPIs and start KPI calculation for those
Network Elements.
 Create user-defined KPIs and manage both user-defined KPIs and predefined KPIs.
 Export one or more KPI definitions as a JSON file.
 Import one or more KPI definitions from a ZIP or JSON file.

Operational engineers can view or export information about available KPIs. Only system
administrators can create, manage, and import KPIs.

Start KPI Calculation

Start KPI calculation for relevant Network Elements by selecting and editing an existing KPI
(or creating a new KPI). Assign the relevant Network Elements to the KPI, define the
formula, and activate the KPI.

Predefined KPIs

For information on the Ericsson Predefined KPIs supported by the KPI Management
application, refer to Network Health Monitor KPIs, 1/100 56-CNA 403 2994 available in the
relevant ENM CPI library.

Criteria-Based KPIs

Criteria-based KPIs have a dynamic node list that is populated according to specific criteria.
The criteria are derived from a Saved Search (query) which has been assigned to the KPI.

Subscriptions are updated (include or delete nodes) every 24 hours to reflect any changes that
have occurred in the network in relation to:

 Addition of a new node

 Deletion of a node

Up to 25 KPIs can be configured in this way.

8.1.3 Automatic ID Management

Automatic ID Management is a web-based application for the detection and resolution of

Physical-layer Cell Identity (PCI) conflicts in the network.

Automatic ID Management is used to detect and resolve Physical-layer Cell Identity (PCI)
conflicts in an LTE Network.

You can use the following Automatic ID Management functions:

 PCI Check detects PCI conflicts in your network.

 PCI Calculate proposes new PCI values to resolve PCI conflicts detected in your
network.
 The proposed new PCI selection is based on the criteria for Check and Calculate
selected in the Automatic ID Management profile. Automatic ID Management ensures
that no new conflicts occur because of any change.

 PCI Resolve addresses conflicts by applying the proposed PCI Values to the relevant
cells.
 Automatic ID Management profiles - Manual, Open Loop (semi-automatic), or Closed
Loop (Automatic) - can be used when checking PCI Conflicts, calculating new PCI
values, and fixing conflicts in the network.

Note: Changing PCI values affects live traffic.

Supported Nodes

Automatic ID Management currently supports:

 eNodeB DU Radio Nodes

 eNodeB Baseband Radio Nodes
 eNodeB Pico Radio Nodes

Physical-layer Cell Identity (PCI)

The LTE network uses PCIs to distinguish between different cells. PCIs consist of two
identities:

 PhysicalLayerCellIdGroup which divides all PCIs into 168 unique groups

 PhysicalLayerSubCellId which subdivides the PhysicalLayerCellIdGroup into 3
unique subidentities

Each cell uses one PCI out of a possible total of 504 PCIs. An LTE network can contain tens
of thousands of cells. In large networks many cells can use the same PCI. This causes PCI
conflicts in the network if both the PCI and frequency are the same for a cell.

Two types of PCI conflict exist:

Collision This occurs when a cell has a neighbor with the same PCI and frequency.

Confusion This occurs when a cell has two neighbors with the same PCI and frequency.

Automatic ID Management performs PCI checks to identify all cells involved in a PCI
conflict. Automatic ID Management performs PCI calculations and proposes new PCI values
to resolve the conflicts (collisions and confusions) that are identified. The proposed new PCI
selection is based on available PCI values, ensuring that no other conflicts are introduced as a
result of any change.

Automatic ID Management performs a PCI resolve which applies the proposed values,
updates the relevant configuration attributes, and resolves the conflicts (collisions and
confusions).
8.1.4 Spectrum Measurement Management

Spectrum Measurement Management (SMM) allows an operator to remotely capture and

analyze Radio Frequency (RF) information received by a base station.

Spectrum information is collected from the node in a file and SMM then transforms the
information into a spectrum. This allows an operator to troubleshoot radio frequency
performance and detect interference.

Uplink Spectrum File Collection

Spectrum Analyzer

User Interface

8.1.5 Analytic Session Record (ASR)

The Analytic Session Record (ASR) Value Packs provide near real-time Analytic Session
Records for LTE (ASR-L) and NR (ASR-N). ASR supports Time Division Duplex (TDD),
Frequency Division Duplex (FDD), and Mixed Duplex modes.

The record is produced from Performance Management Cell Trace streams, with record
boundaries based on subscriber mobility and network behavior. The records are made
available to northbound consumers in Apache Avro format streams. Northbound consumers
can use a REST interface to retrieve the Apache Avro schemas that are needed to process
ASR records from the Northbound Interface (NBI).

ASR-L and ASR-N are licensed Value Packs in ENM.

Features of Analytic Session Record for LTE (ASR-L)

Converts raw LTE CellTrace events to a mobility-driven call session record for each
subscriber, containing information such as:

 Subscriber/Terminal capabilities
 Call type - for example, RRC connection, RRC re-establishment, or handover
 Call release reason
 Call location (where in the network the session started and ended)
 MDT-based geolocation information
 Frequency Band Class
 Data volume transferred
 Throughput and latency
 Channel quality
 Radio experience and integrity for the call
 Errors encountered
 Per Radio Bearer details
 NR-NSA Dual Connectivity capability

Features of Analytic Session Record for NR (ASR-N)

Converts raw NR Cell Trace events to a mobility-driven call session record for each
subscriber in NR SA configurations, containing information such as:

 Call type - for example, RRC connection

 Call location - which gNodeB and cell the session started and ended
 Accessibility information - for example, RRC Establishment Cause and Result, NG
Signaling Connection Result
 PDU Session Setup information
 Per Radio Bearer details
 UE Context Release information - for example, Normal or Abnormal UE Context
Release, and which network function initiated the release procedure
 Outgoing NR handover execution type and result

Trigger Conditions

ASR Characteristics

 Each ASR record contains instrumentation fields:

o sessionStatus field

(with 0 indicating a complete session record, and a non-zero integer indicating

an incomplete session record)

For more information on the sessionStatus field, see Analytic Session

Note: Record (LTE) Specification, 1551-CNA 403 3416 and Analytic Session
Record (NR) Specification, 1/1551-CNA 403 3416

o Number of events processed to produce the record

 Northbound Interface (NBI): TCP near-real time stream, encoded in Apache Avro

Example of Mobility-Based Session Records for ASR-L

8.1.6 Flexible Counter Management

Flexible Counter Management (FCM) is a web-based application which provides the

functionality to create Flexible (Flex) EBS-N counters. A Flex counter is a base EBS-N
counter which is refined with additional filter parameters. The FCM application allows the
operator to perform the following actions on Flex EBS-N counters:

 Create
 View
 Import
 Export
 Duplicate
 Delete

Once created, Flex counters are available for selection with base EBS-N counters in the PMIC
application.

8.2 CLI Command Sets Used in Performance and

Optimization
The following command sets are used in Performance and Optimization:
  ulsa

Full information about the commands within the command sets, including command
Note:
syntax and role requirements, is provided in the online help.

8.2.1 Manage Uplink Spectrum Sampling - ulsa Command Set

Command Description
start Start uplink spectrum sampling on nodes.
capability Fetch uplink spectrum analyzer capabilities of the selected radio unit.
stop sampling Stop an ongoing continuous or conditional measurement.
stop scheduling Stop an ongoing scheduled measurement.

9 Provisioning
Provisioning refers to all activities that involve making changes to a managed network.

In ENM, provisioning is divided into the following distinct areas:

 Configuration – All Configuration Management applications (applications that

simplify the configuration of Network Element resources)
 Element Management – Applications supporting direct access towards the different
Network Elements supported in ENM
 Adding Network Elements – Various applications for adding Network Element
instances to ENM (from manual to automatic)
 Auto Provisioning – Auto Provisioning automates node provisioning activities such as
node integration, hardware replace and expansion.
 Add Node – Procedures and tools supporting the addition and removal of Network
Elements from ENM
 Auto Node Discovery – An ENM application supporting the automatic detection and
addition to ENM of various transport network nodes
 Software & Hardware Management – Applications supporting the activities associated
with the life cycle management and inventory of Network Elements
 Life cycle Management of Virtual Nodes – Applications supporting specific aspects of
life cycle management for virtual Network Elements (instantiation, expansion,
decommission)

Configuration

This area is for ENM applications and tools that are used for Configuration Management.
These applications and tools can be used for general purpose exploring, searching, viewing,
analysis, data extraction, and modification of network nodes and their configuration data.

9.1 Applications Used in Provisioning

A set of Provisioning applications is available from the ENM Application Launcher.
The applications are as follows:

 Add Node, see Add Node

 Advanced Managed Object Scripting (AMOS), see Advanced Managed Object
Scripting (AMOS)
 Auto-Provisioning, see Auto Provisioning
 Autonomic Incident Management, see Autonomic Incident Management
 Bulk Configuration, see Bulk Configuration
 Cabinet Viewer, see Cabinet Viewer
 Cendio Desktop, see Cendio Desktop
 Cell Management, see Cell Management
 CM Audit, see CM Audit
 Command Line Interface, see Command-Line Interface
 Configuration Templates, see Configuration Templates
 Desktop Session Management, see Desktop Session Management
 Element Manager, see Element Manager
 Network Discovery, see Network Discovery
 Network Explorer, see Network Explorer
 Parameter Management, see Parameter Management
 Release Independence Manager, see Release Independence Manager
 Shell Terminal, see Shell Terminal
 Software Hardware Manager, see Software Hardware Manager
 Software Management Repository Services, see Software Management Repository
Services
 Topology Browser, see Topology Browser
 VNF Life Cycle Manager, see VNF Life Cycle Manager
 WinFIOL CLI, see WinFIOL CLI

9.1.1 Add Node

The Add Node web application is a wizard application used to create nodes in ENM as an
alternative to the CLI commands.

The Add Node link is located in the Provisioning section of the ENM Launcher.

When adding data in the Add Node wizard, note the following:

 Only fields marked with a red asterisk are mandatory.

 Added data must comply with the constraints related to the relevant field.

For example, the IP address must match the xxx.xxx.xxx.xxx format.

 Sensitive information (for example, the password) is hidden.

 The user can move back to the previous step by clicking the Previous button.

The user chooses the type of the network element to add in ENM and then adds data
following the wizard steps:

1. Define Network Element

 The user adds the Network Element attributes such as NE name, and OSS model
identity.

2. Define Connectivity Information

The user adds connectivity information such as IP address and port number.

3. Define Security

The user adds security information such as username, passwords, and keys.
Optionally, the user can enable the sso flag if the node is enabled with AAA
authentication using TACACS+ or RADIUS.

sso can be enabled for Router6000 with ENM LDAP also.

4. Define positioning attribute

The user optionally adds the coordinates of a node so that it is possible to position
nodes upon creation.

5. Define supervision functions

The user optionally specifies supervision of a node.

6. Display all attributes

All data added are displayed to let the user verify the choices made. If the data added
are correct, the user can choose the Finish button. A popup reports the result of node
creation (either a success message for the successful creation, or a reason why the
node creation failed).

9.1.2 Advanced Managed Object Scripting (AMOS)

Advanced MO Scripting (AMOS) provides a Command-Line Interface (CLI) towards

supported CPP, COM-ECIM, and Transport based Network Elements. It is a production-ready
version of the MO Shell tool.

AMOS adds logging, user authorization, user authentication, and license checking, which
were not present in MO Shell. AMOS provides limited support for Transport nodes
TCU02/SIU02. Only the node's own commands are supported. MO Shell commands such as
"lt" and"get" are not supported.

AMOS provides the functionality listed above for the following nodes:

 LTE Network Elements of type eNodeB DU Radio Node

 LTE Network Elements of type eNodeB Baseband Radio Node configured as Single
Mode Baseband (SMB)
 LTE Network Elements of type eNodeB Pico Radio Node
 Core Network Elements of type MGW
 WCDMA Network Elements of type RNC
  WCDMA Network Elements of type Node B DU Radio Node
 WCDMA Network Elements of type Node B Baseband Radio Node
 IMS Network Elements of type DSC
 UDM Network Elements of type BSP
 UDM Network Elements of Type vHSS-FE
 UDM Network Elements of Type HSS-FE

The ENM Log Viewer allows the activities performed by operators to be checked with
AMOS.

AMOS can be launched in offline mode from the ENM Launcher. It can also be launched for
a selected Network Element from search results in ENM Network Explorer.

An SSH client can be used to launch AMOS in offline mode. From a dedicated ENM virtual
machine that allows SSH connectivity into ENM, an SSH client can also be used to launch
AMOS for a selected Network Element.

9.1.3 Auto Provisioning

The Auto Provisioning (AP) application supports the automated roll out of Network Elements
into a network.

AP automatically executes the following functions (driven by the input configuration data
provided by the user):

 Configuration of the security data

 Configuration of the node licenses
 Configuration of the radio and transport data
 Configuration of the optional features
 Configuration of the baselines
 Configuration of the remote nodes
 Enabling FM and PM supervision
 Bringing cells into service
 Verification of the geo-location
 Creation and upload of CV/backup

AP provides a User Interface (UI) and a Command-Line Interface (CLI) to support the
integration of the following:

 LTE Network Elements of type eNodeB DU Radio Node (Macro/Micro/Radio Dot

System (RDS))
 LTE Network Elements of type eNodeB Baseband Radio Node
 WCDMA Network Elements of type NodeB Baseband Radio Node
 GSM Network Elements of type NodeB Baseband Radio Node
 NR Network Elements of type NodeB Baseband Radio Node
 LTE Network Elements of type Pico Radio Node
 WCDMA Network Elements of type Pico Radio Node
 LTE Network Elements of VNF type vPP(Virtual Packet Processing)
 LTE Network Elements of VNF type vSD(Virtual Service Discovery)
 LTE Network Elements of VNF type vTIF(Virtual Transport Intelligent Function)
  Network Elements of type Router 6672 Node, Router 6675 Node and Router 6x71
Node
 LTE Network Elements of type gNodeB Baseband Radio Node

Auto-provisioning CLI operations are implemented using the ap command set (see
Automatically Integrate, Expand or Replace a Node - ap Command Set.)

9.1.4 Autonomic Incident Management

Autonomic Incident Management enables the automated detection, prioritization, and

monitoring of network incidents.

The system monitors and correlates events happening around the same time. It groups related
events that degrade either network performance or services into an incident. Incidents are
prioritized based on their impact either on network performance, on services, or both.

Self-learning algorithms learn continuously from changes in performance indicators about

traffic patterns. The learning involves correlating changes in network conditions and service
impacts. As time elapses, problems are correlated more accurately with the network
conditions that triggered them and incident detection improves.

From the user interface, the operator can accomplish the following:

 View network incidents sorted by priority

 View details of particular incidents
 View KPI charts at incident level and at system level.

9.1.5 Bulk Configuration

Bulk Configuration UI is a web-based application that enables the user to view and to execute
import jobs towards the live configuration.

Bulk Configuration executes import jobs using a Stop, Preview, and Continue flow. After the
job is parsed and validated, the job stops. At the stop point, the user can:

1. Preview the results of all validation phases for all operations.

2. Make an informed decision about whether to continue to the execution phase.

If the user chooses to execute the job, the job only executes valid operations.

View Jobs

Lists jobs that are stored in the system. The list shows the number of jobs stored as well as
key information for each job. Job information includes the number of operations and the
number of validation and execution errors. Jobs for the current user are shown by default. The
user can choose to display all jobs in the system.

Create and Validate a Job

The user can:

  Create a job, give it a name, and upload the 3GPP or EDFF file.
 Select whether instance validation is performed.
 Determine the error handling behavior.

After the user executes the job, the file is parsed. Schema validation, model validation, and -
optionally - instance validation occur before the job stops for the preview.

Preview Job

The user can view the following details before execution towards the live configuration:

 Job metadata
 Total number of operations
 Total number of valid operations and invalid operations.
 Details of individual operations, both valid and invalid.

Update operations show both the attribute supplied in the job and the current attribute on the
network. Create operations only show the attribute supplied in the job. Invalid operations are
highlighted in red along with the associated error message.

The file errors tab shows file errors that occur during the parsing phase.

Execute Job

Executes all valid operations in the job. Invalid operations are ignored. The error handling
behavior that the user selected when the job was created is applied during the execution
phase.

Review Job

The user can view:

 Job details after execution towards the live configuration

 Total number of operations
 Total number of operations with a particular status

Totals are provided for valid operations, invalid operations, executed operations, and
operations with execution errors.

 Details of individual operations

Details are provided for valid operations, invalid operations, executed operations, and
operations with execution errors.

Invalid and failed operations are highlighted in red along with the associated error message.

9.1.6 Cabinet Viewer

The Cabinet Viewer terminal appears inside the user's Cendio Thinlinc desktop, in a new
browser tab, after the user selects a node of a supported neType from Network Explorer or
Topology Browser and clicks the Launch Cabinet Viewer button. It is launched alongside any
applications which are already open on this desktop.

The following node is supported: eNodeB DU Radio Node

Users must be assigned the Element_Manager_Operator role in ENM to launch Cabinet

Viewer.

Cabinet Viewer Role

The following Cabinet Viewer Resource and Operations are available for creating Custom
Roles.

 element_manager (resource)
o Read (operations)
o Write (operations)

Custom roles are created and assigned for users. There are two operations available for these
roles:

 Read-only
 Write

The following actions are available for the operations:

Read-
launch Cabinet Viewer in read mode.
only

launch Cabinet Viewer in write mode to perform actions which includes restart,
Write
lock, unlock and so on.

9.1.7 Cendio Desktop

The Cendio Thinlinc is a remote desktop server, that makes it possible to run X11
applications remotely in the browser on one of the Element Manager VMs, a standard Linux
desktop with Openbox window manager.

There is one desktop session per user. By closing the viewer in the browser, the session of
X11 Desktop remains running on the server and the user lands on the same desktop
application upon reconnecting.

By logging out of ENM, the user schedules the closing of the desktop session, which will
trigger closing all applications and desktop up to 30 seconds after user logs out.

The Cendio Desktop System Bar has been customized to display the attributes of the
connection with the Cendio Desktop (see image).
The components of the Cendio Desktop System Bar, numbered in the image, are as follows:

1. ENM Logo

Ericsson Network Management logo and description.

2. User and element manager VM [<user>@<VM>]

This is the username and instance of the element manager VM. This info is shown if
there is an established connection with the server.

3. ENM Host

This is the name of the ENM system.

4. Help menu

Links to the online help.

5. Clipboard

Shows the content of the Cendio clipboard.

9.1.8 Cell Management

The Cell Management application provides a simple way to view and manage cells, cell
relations and frequency relations on selected NR, LTE, WCDMA, NBIOT and GSM nodes.

It provides the following functionality:

 Allows nodes to be selected from the network topology, collections, saved searches, or
the results of a user search.
 Displays cells for selected nodes in a table including the cell status and other
important data for each cell.
 Highlights cells which need attention.
 Provides actions to lock, soft lock, and unlock cells.
 Provides an action to launch Parameter Management with a fixed set of managed
objects and parameters determined by the cells or editable relations selected.
 Provides filtering and Sorting on supported attributes for LTE and WCDMA cells.
 GSM BSC or 5G NR Radio Node to be selected to Create a Cell.
 Delete of Cell.
 Export of Cells to a CSV File.

Supported Node Types

 ERBS
 RadioNode
 MSRBS_V1
 BSC
 RNC
For more information see the ENM Supported Network Elements, 3/1029-AOM 901 151.

9.1.9 CM Audit

The CM Audit application can be used to identify inconsistencies, for a specific network
element, in the network..

At present, the default audit type supported is cell audit. Cell audit checks that the attribute
values of external cells match the attribute values of WCDMA and GSM cells managed by the
supplied network element.

External cells are checked across managed LTE, WCDMA and GSM network elements.

For GSM cells the nccPerm attribute is also checked to ensure it contains the ncc values of
neighboring cells.

Once all inconsistencies have been identified, CM Audit will create a CM Bulk Import job
that will contain the corrective operations needed to return the network to a consistent state.

A maximum of 1400 audit jobs are maintained in the system- Audit Service will periodically
remove older jobs to enforce this limit.

9.1.10 Reparenting Flow

Reparenting Flow facilitates moving cells and cell relations between network controllers
(BSC) in GSM networks.

The scope of a reparenting activity is specified by means of an input file which lists the base
stations (G12Tg/G31Tg) connected to the cells to be moved. It is also possible to specify
updated names and CGI values for individual cells in the input file.

All configuration changes made to the network in the reparenting activity are made using CM
Bulk Import.

The flow consists of two distinct phases: preparation and cutover. During preparation the cells
are created on the target network controller via CM Bulk Import, and the remaining
configuration changes are planned by creating further CM Bulk Import jobs. During cutover
the rest of the CM Bulk Import jobs are executed in a prescribed order to complete the
reparenting activity.

Reparented cells are created with the same configuration as the original cells. Relations are
preserved by the activity, including relations to and from other RATs, i.e. WCDMA cells and
LTE cells.

9.1.11 Command-Line Interface

The ENM CLI is the essential tool for Configuration Management. It enables the user to
perform any CM operations on nodes managed by the OSS.
The ENM CLI is model-driven, therefore it functions towards any Managed Object Class
defined in any Managed Object Model which the OSS supports. The ENM CLI does not have
any knowledge or logic regarding the CM Data it operates on beyond what it can determine
from the model. All ENM CLI and CM CLI command sets use a common user interface (UI).

ENM CLI

ENM CLI provides the following common commands that can be used with any other CLI
command set:

 BATCH – this command can be used to execute a batch file of CLI commands.
 ALIAS – this command can be used to create alias commands for actual CLI
commands.
 HELP - this command can be used to fetch help for CLI commands. It is interactive
with the online help and tutorial pages.
 COLLECTION- this command set supports reading Collection information. Creation,
modification, and deletion of a collection is also supported.
 SAVEDSEARCH- this command set supports reading Saved Search information.

Configuration Management CLI

CM Editor (cmedit) CLI commands support various ways to manage modeled data:

 GET – this command can be used to fetch one or more instances of a managed object.
A get can have various filter criteria associated with it.
 SET – this command can be used to modify one or more instances of a managed object.
A set can have various filter criteria associated with it.
 CREATE – this command can be used to create an instance of a managed object.
 DELETE – this command can be used to delete one or more instances of a managed
object. It can be used to force the delete on an entire MO hierarchical structure.
 ACTION - this command can be used to initiate a modeled action on a MOI in your
network through the ENM Command-Line Interface (CLI). This task is used by a
configuration engineer who needs to initiate an action on a node in the live system.
 DESCRIBE – this command can be used to describe an MO Class, MO Instance or any
of its attributes.
 EXPORT - this command can be used to create a bulk export of node data from the Live
configuration. The bulk export can produce an XML file, compliant to 3GPP
standards, or a CSV file, compliant to Ericsson Dynamic file format.
 IMPORT - this command can be used to bulk import MO instances into the Live
configuration from a 3GPP compliant XML file or from a CSV file, compliant to
Ericsson Dynamic File Format (EDFF).

9.1.12 Configuration Templates

Configuration Templates (CT) is a service that supports the management of templates in

ENM.

CT is one of the services under Configuration Management in ENM and is for template reuse.
A template is a resource characterized by metadata (for example, Name, Description, Node
Types, Template Type, Created, Labels) and content (for example, files with the
AutoIntegration template type).

CT is a UI-based application which allows you to create and delete configuration templates,
view the list of available templates, export templates, import templates, and view the details
of a single template.

An ENM user with the role ConfigurationTemplates_Operator is allowed to list, view

details of, and export templates. An ENM user with role
ConfigurationTemplates_Administrator is allowed to create, list, view details of, delete,
export, and import templates.

CT supports the following use cases:

 Create template
 List templates
 View template details
 Delete templates
 Export templates
 Import templates

9.1.13 Desktop Session Management

Desktop Session Management provides a table showing all running sessions and allows the
user (with the role DesktopSession_Administrator or ENM Administrator) to end running
desktop sessions when appropriate.

Details of running desktop sessions, include the following:

 User ID (User logged on to the VM)

 VM (In which VM the session was created)
 Start Time (When the session was created)

9.1.14 Element Manager

Element Manager (EM) is an application for applying configuration changes to the selected
network element instance.

Element Manager (EM) is a software application that Ericsson provides to customers along
with the network element itself. Element Manager is used to apply configuration changes
directly on a single network element instance and can also be used for troubleshooting.

Most Element Managers are not developed within ENM, but ENM users can run a Network
Element's Element Manager inside ENM. ENM checks that you have an appropriate role to
launch the Element Manager. ENM writes an entry to the system logs whenever you request
the launch of an Element Manager.

Element Managers are launched from Network Explorer by selecting a particular network
element, if that network element has an associated Element Manager.
9.1.15 Network Discovery

Network Discovery (ND) is a web-based application for discovering NEs in the network and
adding them automatically to ENM.

ND uses SNMP to scan a range of IP addresses for the NEs.

ND enables the specification of the following functionalities:

 The IP range to be scanned for the NEs.

 The SNMP (v2c or v3) parameters to use when scanning.
 A schedule for scanning periodically.
 The connectivity and security information to be used when a discovered NE is added
to ENM.

Optionally, the user can enable the sso flag if the node is enabled with AAA
authentication using TACACS+ or RADIUS.

 If CM should be enabled for added NEs.

 If FM should be enabled for added NEs.
 If PM should be enabled for added NEs.
 A collection name which can be used to filter discovered NEs.
 Enables the user to execute a scan on demand.

Discovery Activity (DA)

A discovery activity holds the parameters to use when scanning the network, and specifies
what actions to take when adding a discovered NE to ENM. It references a connection profile.
A discovery activity also represents the task to scan the network using the parameters defined.
It can be started, canceled, and scheduled.

Connection Profile (CP)

A connection profile holds the connectivity and security information to use when an NE is
added to ENM. The data in the connection profile is used to create the Connectivity
Information (CI) managed object and the Network Element Security (NES) managed object.
The same connection profile can be used for multiple discovery activities.

Architecture

ND consists of two applications namely, Connection Profile (CP) and Discovery Activity
(DA). These applications interact with Discovery Service which is managed within ipsmserv
service group. The network IP Range provided in DA is scanned using SNMP protocol by
triggering an SNMP GET operation. Network IP Range provided in DA is scanned using
SNMP protocol by triggering an SNMP GET operation. 'sysObjectID' 'sysDescr' and
'sysName' OIDs in the systems group of the SNMP MIB-2 are used for the scan. From the
received response, only user-selected NE types are selected and added to ENM.

9.1.16 Network Explorer

Network Explorer allows you to search through objects using a flexible, user-friendly search
syntax.

You can build queries with a flexible and user-friendly search syntax. Alternatively, you can
use the intuitive, model-drive UI to build complex and powerful search queries.

Functionality to group data is provided through Collections and Saved Searches. Managed
Objects (MOs) returned in search results can be grouped into collections which can be easily
updated later by adding or removing objects. A default limit of 25,000 exists on the number of
objects that can be added to a collection. This limit is a configurable parameter which can be
adjusted by a System Administrator. Searches can be saved for re-execution later, providing a
more dynamic view of the network.

You can navigate to Network Explorer from another ENM application, perform a search, and
select individual results from the table to bring back to the originating application.

9.1.17 Parameter Management

Parameter Management provides a visual summary of the state of a network configuration. It

is used to analyze and modify the current state of selected Managed Objects (MO).

Parameter Management uses Network Explorer to select saved searches. These saved searches
provide dynamic views of the network configuration (including selection based on parameter
values).

Parameter Management provides functions to view and configure network configuration data.

These functions include:

 Allow changes to be made to the data which can then be activated on the network.
 Allow changes to be made directly to the nodes.
 Provide a summary of the statistics for the Configuration Management Data.

Parameter Management also provides a view of parameter values across multiple MOs.
Configuration changes can be made to update individual or multiple MO instances. It is also
possible to update one or more parameter values across multiple MO instances.

9.1.18 Release Independence Manager

Release Independence Manager is a web-based application that supports node software

versions that are not managed.

Release Independence Manager allows Network Elements to be upgraded independently from

OSS, and the OSS to be upgraded independently from Network Elements.

The Release Independence Manager application adds support to ENM for the new node
versions with new alarm types, configuration data, and new PM counters and events. Release
Independence Manager validates the models downloaded from the network element before
adding the support.
Release Independence Manager Process After Node Software Upgrade

The Release Independence Manager application is triggered by a full sync on a node on which
software has been upgraded.

When a node is upgraded to a new software version and a full sync is triggered on it, the
following happens:

1. The Release Independence Manager application downloads and validates new models
from the node.
2. The Release Independence Manager application informs the user that a new node
version is awaiting ENM support to be added.
3. The Release Independence Manager user (with operator rights) can download and
view the new models.
4. The Release Independence Manager user (with administration rights) can initiate
support for the new node version.

At the end of the procedure, all native data of the newly supported node version is
available to be managed by ENM.

Support for Node Versions Added by Release Independence Manager

For a breakdown of the features (applications, Northbound Interfaces, and so on) that support
node versions added by Release Independence Manager, see the following:

 Monitoring Features That Support Node Versions Added by Release Independence

Manager
 Performance and Optimization Features That Support Node Versions Added by
Release Independence Manager
 Provisioning Features That Support Node Versions Added by Release Independence
Manager

Model Validation

The Release Independence Manager application performs a model validation for each of the
unsupported node version and displays the result on the Release Independence Manager UI.

Once validated, a model of an unsupported node version can be in one of the following states:

 Ready for Support

 Ready for Support (Validation passed with workarounds)
 Not Supportable

The validation consists of the following two steps:

1. Standalone Validation

The model is validated to be compliant with the associated grammar and general or
common semantics rules.
 To view a table of Standalone Validation checks, see Standalone Validation Checks.

2. Comparative Validation

The model is validated against all models already deployed into the ENM system to
check for incompatible changes, and if possible, resolve them.

To view a table of Comparative Validation checks, see Comparative Validation

Checks.

If all validation checks pass, or any validation failures can be worked around, ENM can
support the model.

9.1.18.1 Monitoring Features That Support Node Versions Added by Release

Independence Manager

In the Monitoring section of the ENM Launcher, only the applications and features listed in
the following table support the node versions added by Release Independence Manager. Other
applications and features are not supported.

Feature Feature Type Comment

FM Integrated OPI is included within this
Alarm Monitor Application
application.
Alarm Overview Application
Alarm Search Application
Fault Manager
Application
Expert (FMX)
FM NBI Northbound Interface
FM CLI Command-Line Interface
Feature of KPI New counters for supported reporting objects
User-defined KPIs
Management Application are available for use in user-defined KPIs.

9.1.18.2 Performance and Optimization Features That Support Node Versions Added by
Release Independence Manager

In the Performance and Optimization section of the ENM Launcher, only the applications and
features listed in the following table support the node versions added by Release
Independence Manager. Other applications and features do not.

Feature Feature Type Comment

New counters are available for selection in subscriptions
Statistics File Statistical and present in the mediated files. New system-defined
Mediation Subscriptions counters are present in mediated files for active
subscriptions.
 Feature Feature Type Comment
New counters are available for selection in subscriptions
Event File Statistical and present in the mediated files. New system-defined
Mediation Subscriptions counters are present in mediated files for active
subscriptions.
New events are available for selection in subscriptions and
Event Stream Event
present in the mediated streams. New parameters for
Mediation Subscriptions
existing streamed events are present in mediated streams..

9.1.18.3 Provisioning Features That Support Node Versions Added by Release

Independence Manager

In the Provisioning section of the ENM Launcher, only the applications and features listed in
the following table support the node versions added by Release Independence Manager. Other
applications and features do not.

Feature Feature Type Comment

In some situations, the following functions are
affected when Release Independence Manager adds
Configuration new node versions: saved searches, aliases,
Management referenced MOs, and referenced attributes. For
Application
Command-Line example, the following saved search returns an error
Interface (CLI) if you remove the lac attribute from the model:

select UtranCell where attribute lac > 10

In some situations, the following functions are

affected when Release Independence Manager adds
new node versions: saved searches, aliases,
Network Explorer Application referenced MOs, and referenced attributes. For
example, the following saved search returns an error
if you remove the lac attribute from the model:

select UtranCell where attribute lac > 10

Topology Browser Application
Scripting
Includes the following:

 Software Inventory
 Hardware Inventory
 License Inventory
Software Hardware
Application  Upgrade
Manager (SHM)
 Backup
 Restore
 License Key File Handling
 SHM CLI
 Feature Feature Type Comment
Configuration
Import Export Management
Function
Auto-Provisioning Application
Configuration
Northbound
Management Event
Interface
NBI
Advanced Managed
This application operates directly on the node and is
Object Scripting Application
node version independent by default.
(AMOS)
Node CLIs / These applications operate directly on the node and
Application
Element Managers are node version independent by default.

9.1.18.4 Standalone Validation Checks

Validation results in Release Independence Manager are available only for node versions with
validation failed or passed with workarounds. To access the validation results, select the Node
Version and click the View Validation Result button on the top-left action bar. The following
table shows the standalone validation checks.

Table 4 Standalone Validation Checks

Validation Check Result Action Description
Check the model syntactically
against the meta-model, that
means against any of the
following: No workaround as the
model cannot be parsed. It
Model cannot
 mp.dtd (CPP / ECIM) is possible to add best
be supported NA
 YANG effort support for the
by ENM.
 SMIv2 model but the results are
unpredictable.
For example, check if the
model syntax is correct in
respect of the language.
Currently MDT checks
that all hierarchical
Primary Types with at
least one attribute must
Model cannot
All classes must have an ID have a key attribute.
be supported NA
attribute.
by ENM.
For CPP/ECIM, all
Managed Object Classes
(MOCs) must have at
least a single "key"
 Table 4 Standalone Validation Checks
Validation Check Result Action Description
attribute. In the absence
of an explicitly marked
"key" attribute the ID
attribute (<MOC
Name>Id) is assumed to
be the key.

In YANG, keys are not

mandatory.
Check internal coherence in
relation to referenced types, for
example:
Remove the
 enumRef pointing to Model can be attribute that
existing enum supported by uses the
 structRef pointing to ENM with enumRef or
existing struct workarounds. structRef from
 ddtRef pointing to the model.
existing
derivedDataType

Model can be
Remove both
Duplicate attributes must not supported by
attributes from
be present in a class. ENM with
the model.
workarounds.
Remove the
Model can be attributes that
No duplicate struct types or
supported by use the struct,
enum types, or derivedData
ENM with the enum, or
types.
workarounds. the ddt from
the model.
Remove the
attributes that
Model can be refer to the
Struct and enum must not have supported by struct or enum
duplicate members. ENM with and the struct
workarounds. type or enum
type from the
model.
Model can be Remove the Remove the default value
The default value for an
supported by default value from the model. For
attribute must be in accordance
ENM with from the example, for boolean
with the type of the attribute.
workarounds. model. attributes the default
 Table 4 Standalone Validation Checks
Validation Check Result Action Description
value must be either true
or false.
Remove the range
Remove the constraint from the
The range value for an
range model. For example, for
attribute must be in accordance
constraint from integer attributes the
with the type of the attribute.
the model. range values must be
integers.
Model can be
Node handles actual
Relationship cardinality must supported by Make the
cardinality and reject the
be numeric. ENM with cardinality 0..*
change if it's exceeded.
workarounds.
Node handles actual
cardinality and rejects the
change if it's exceeded.
Model can be Make
Minimum cardinality of an
supported by minimum 0 This and the
attribute must be less than or
ENM with and maximum previous rule
equal to maximum cardinality.
workarounds unlimited. apply to other
Note:
numeric values
(for example
string lengths).
Minimum value of a struct
member must be less than or Model can be Make
Node handles actual
equal to its' maximum value. supported by minimum 0
cardinality and rejects the
Also the default value must be ENM with and maximum
change if it's exceeded.
inclusively between min and workarounds. unlimited.
max.

9.1.18.5 Comparative Validation Checks

Validation results in Release Independence Manager are available only for node versions with
validation failed or passed with workarounds. To access the validation results in Release
Independence Manager, select the Node Version and click the View Validation Result button
on the top-left action bar.

Table 5 Comparative Validation Checks

Validation Check Result Action Description
The data type of an attribute or an
action in a class must not change. Model can be Make the new
Allowed data type changes are: supported by ENM attribute version
enumRef < - > String and moRef < with workarounds. non-persistent.
- > String.
 Table 5 Comparative Validation Checks
Validation Check Result Action Description
The data type of Struct Member Make the attribute
Model can be
must not change. The allowed data that refers to the
supported by ENM
type changes are: enumRef < - > struct non-
with workarounds.
String and moRef < - > String. persistent.
Make the attribute
Struct name must not be modified. Model can be
that refers to the
supported by ENM
struct non-
with workarounds.
persistent.

9.1.19 Shell Terminal

The Shell Terminal is a terminal emulator based on a web browser. With the Shell Terminal
you can run all text-based Linux commands, including cursor and font control. The Advanced
Managed Object Scripting (AMOS) can also be launched from Shell Terminal.

9.1.20 Software Hardware Manager

Software Hardware Manager (SHM) is a web-based ENM application for administering the
Nodes/Network Elements (NEs) in your network.

SHM provides an intuitive web-based user interface to manage the node inventories like
software, hardware, and license. SHM provides an interface to perform software upgrades,
take the backup of node software, restore the node backup, and install licenses on groups of
nodes. SHM supports the following key features:

 Inventory
 Backup administration
 License administration
 Software administration

Inventory

The inventory feature allows the operator to view the software, hardware, license, and backup
inventories of nodes.

It supports the following functions:

 View software inventory

 View hardware inventory
 View license inventory
 View backup inventory
 Automatic inventory synchronization
 Manual inventory synchronization
 Export inventory information using CM Bulk export
 Export inventory information using SHM inventory export
Backup Administration

The backup administration feature allows the operator to generate a backup on the nodes and
transfer it back to the ENM using the Backup Job Wizard in SHM.

It supports the following functions:

 Create a backup.
 Set the created backup first in rollback list.
 Set the created backup as startable.
 Upload the created backup to ENM.
 Delete backups on the node and ENM.
 Manage backups.
 Restore the backup.

License Administration

The licensing feature allows the operator to install License Key File batches across the nodes.

It supports the following functions:

 Import license key batch files.

 Delete imported license key files.
 Install license key files on the node.
 Generate license request file for selected nodes.
 Instantaneous licensing.

Software Administration

The software administration function allows the operator to perform node software upgrades.

It supports the following functions:

 Import software packages.

 View imported software packages.
 Delete imported software package.
 Install software packages on the node.
 Verify if the node can be upgraded using the selected software package.
 Activate the installed software package on the node.
 Confirm the activated software package to make it permanent.
 View Upgrade Packages on the node.
 Delete upgrade packages on the node.
 Onboard software packages to NFV Orchestrator (NFVO).
 Delete software packages from NFVO.
 View available node software packages on the Network Element Software Store
(CAS).
 Import software packages from the Network Element Software Store.
 Perform housekeeping of software packages on ENM before automatic import from
Network Element Software Store.
 Automate the software package import from the Network Element Software Store.
  Download Release Notes.

9.1.21 Software Management Repository Services

The Software Management Repository Service (SMRS) provides the interface API to get
directories, structures, account details, and the IP address of the Secure File Transfer Protocol
(SFTP) server.

Network Elements and applications use the SFTP server to download files from the SMRS
file system and to upload files to the SMRS file system. The SMRS file system is mounted on
a Shared File System that uses Network Attached Storage. SMRS supports the following key
features:

Provides the API to get the account details such as directory structures,
SMRS Account the SFTP username, and the SFTP IP address. It also provides the API
to clean up the accounts for ENM applications.

is available for the backup account type in the Software Hardware

SMRS
Manager (SHM). SMRS automatically cleans up files from the SMRS
Housekeeping of
file system based on the configured retention policy parameters for the
Accounts
account and the network element type set by the operator.

9.1.22 Topology Browser

Topology Browser is a web-based application accessed from the ENM Launcher.

Topology Browser allows different types of topologies (modeled topology or custom

topology) to be viewed in a navigable tree view. It also allows a user to modify the values of
network object attributes.

A modeled topology is a view of the modeled network managed by ENM.

A custom topology is a hierarchical view of the network chosen by the user for their own
OAM purposes. It can by predefined or customized according to the user's OAM needs.

Topologies presented in the browser are not a continuous live view of the network; a refresh
is needed to get the latest view.

Through Target Based Access Control (TBAC), the user only sees nodes to which they have
authorized access.

9.1.23 VNF Life Cycle Manager

VNF Life Cycle Manager (VNF-LCM) is a cloud-based application that provides life cycle
management for Ericsson Virtual Network Functions (VNFs).

The VNF Life Cycle Manager implements the "Specific VNF Lifecycle management"
functionality with reference to European Telecommunications Standards Institute (ETSI)
reference architecture. VNF-LCM application provides a consistent and unified user interface
and experience for life cycle management of all VNFs in the Ericsson portfolio. VNF Life
Cycle Management use cases consist of:

 VNF Instantiation
 VNF Scaling Up/Down
 VNF Heal
 VNF Termination

These VNF Life Cycle Management use cases are implemented using VNF Life Cycle
Automation Framework. The framework enables VNF teams to develop VNF-specific life
cycle management use cases as workflows that are executed and managed by the VNF Life
Cycle Manager application.

If a workflow does not reach COMPLETED state, one of the following error events is generated
and displayed in the ENM GUI.

 Workflow Failure Error Event

The LCM operation has failed and cannot be retried or rolled back.

 Workflow Rollback Error Event

The LCM operation has been rolled back. The state of the VNF prior to the original
operation invocation has been restored as closely as possible.

Access for workflow execution can be controlled using Role-Based Access Control (RBAC).
Using RBAC, an ENM administrator can restrict or allow the execution of a use case on
VNF-LCM by a specific user from the GUI or NBI. For example, an ENM user is not able to
view or execute workflows when the required custom roles are not assigned.

Furthermore, if a workflow does not have a bundle descriptor, it is not displayed on the GUI.

A fully-deployed ENM is required for error event integration and RBAC.

9.1.24 WinFIOL CLI

The WinFIOL CLI is a Command-Line Interface for executing commands toward Network
Elements.

WinFIOL CLI can be launched in two different ways, directly without connecting to any
Network Element and from the 'Open With' context menu by selecting a Network Element.
When launching without a Network Element the user sees a shell with a custom WinFIOL
prompt. When launching with a Network Element selected, a logon prompt towards the node
is shown in the shell. Port 22 is always used for SSH connections.

WinFIOL Prompt
 Table 6 Commands Available in this Shell
Command Information
Open a channel to the <host> (IP or hostname).
If <port> not supplied, the standard port for
protocol is used.

Port must be in range (0, 65535].

open <hostname>[:<port>][-protocol
<protocol> -l <logfile> [-o]] Valid <protocol> values are: SSH, telnet, sea.
Default is SSH.

Traffic logs are put into <logfile>.

'-o' is an optional flag to overwrite the log file

(it is appended by default).
Open a channel with the parameters from the
<channel_file>.
open <channel_file.xml> [-l
<logfile> [-o]] Traffic logs are put into <logfile>.

'-o' is an optional flag to overwrite the log file

(it is appended by default).

reopen
Reopen the last channel. If '-o' was used, the
flag is omitted and logging is appended.
exit (or Ctrl-C anytime) Quit WinFIOL CLI.
help Display this help.

User Roles

Users must be authorized to run WinFIOL CLI by being assigned the WinFIOL_Operator
role.

The users must also be assigned with a POSIX Role (Scripting_Operator, Amos_Operator, or
Element_Manager_Operator).

9.1.25 Physical Link Management

The Physical Link Management application provides the capability to create, edit, view, and
delete links between endpoints residing on Network Elements.

Physical Link Management ensures consistency across all the possible states that a link can
assume based on the existing, configured node port. The link types supported are Ethernet,
Microwave, E1/T1, and Optical. The basic link attributes are speed and state.

Physical Link Management Terminology

 Node
 A node is any Network Element within the network domains that can be managed by
ENM (for example, ERBS, RadioNode, PICO, MGW).

 Physical Link

A physical link in ENM is an actual connection between nodes. It means the

connection does not have an underlying transport server (LSP for example), but it is
purely physical media (cable, fiber) or radio transmission. The connections end on the
physical interfaces/ports hosted on the node.

 Logical Link

A logical link in ENM is a connection between nodes ending on logical

representations of interfaces/ports, according to the defined standard model.

The user has the ability to manage physical links between all nodes supported by ENM. For
example, it is possible to create links between an RBS and a Router6000 and then to a MINI-
LINK node.

Physical Link Management Overview

From ENM it is possible to:

 Create links by selecting the end nodes and ports or by importing from a file. A link
can only be created if both ends of the link have the same capabilities (that is type and
speed).
 Automatically generate the name of the link or allow the operator to specify the name.
 Edit existing links. There is only provision to edit the name and description.
 View the link details.
 Delete links.
 Import and exports links.
 Create, modify, view, and delete links using the Command Line Interface (CLI).

9.1.26 Network Connectivity Manager

Network Connectivity Manager application provides the capability to create, edit, view,
discover, activate, and deactivate E-LAN, E-Line, Layer 3 VPN for a generic Mobile Back
Haul network domain IP or Ethernet based.

NCM provides the following capabilities:

 Service summary panel

 Logical graphical representation of the network in terms of network nodes and the
associated links or paths connecting them
 Logical groups of connectivity resources between connected NEs of the same
technology type that share the same protocol instance
 Service Provisioning
 Service Discovery
 Service Routing
9.2 CLI Command Sets Used in Provisioning
The following command sets are used in Provisioning:

 ap
 cmedit
 collection
 config
 shm

Full information about the commands within the command sets, including command
Note:
syntax and role requirements, is provided in the online help.

9.2.1 Automatically Integrate, Expand or Replace a Node - ap Command Set

Command Description
Bind a logical node in ENM to a hardware serial number. All resources (node
bind
artifacts and MOs) in ENM are allocated to the dedicated node with that
hardware serial number. It can be requested for an individual node or multiple
nodes.
Cancel the integration for a node. It can be used if the node integration has
cancel
failed, and the node is waiting for cancel or resume (This can be seen using the
ap status command.) The ap cancel command is only supported by LTE
Baseband Radio Node.

delete
Delete a project or node from AP and ENM. It deletes all integration data
generated during the order process (including the NetworkElement MO).

download
Download node-related samples, schema artifacts, imported artifacts, or
artifacts generated during the ordering of a node.

order
Order node integration, hardware replace or expansion for a project file, or a
node.

resume
Used when node integration has failed, and the node is waiting for cancel or
resume. (Use the ap status command to view node status).
status Display the current status of all projects, individual projects or individual nodes.
upload Replace an existing configuration file for a node.
view View the properties for all projects, individual projects, or individual nodes.

9.2.2 Read, Manipulate, and Export Configuration Management Data - cmedit

Command Set

Command Description
Initiate a modeled action on an MOI in the network. This task is used by a
action configuration engineer who needs to initiate an action on a node in the live
system.
Command Description

get
Return all the attributes values of the specified MO instance for the provided
FDN.

set
Modify one or more instances of a managed object. The set command can have
various filter criteria associated with it.

delete
Delete a hierarchical structure of node Managed Object Instances (MOI) (such
as an entire node) or delete individual MOIs in the network.
describe Describe an MO Class, an MO Instance, or any of its attributes.
create Create an instance of a managed object.
read Read the description of modeled data in the system.
import Bulk import CM data.
Start an export job, query the status of an export job, download the export file
export for a completed job, list the available filters on export jobs, or remove
completed jobs.

9.2.3 Read, Create, Modify, and Delete Collection Data - collection Command
Set

Command Description
get List display details of all collections visible to the current user.
create Create a new collection.
modify Modify an existing collection.
delete Delete an existing collection.

9.2.4 Access the ENM Configuration Handling Feature - config Command Set

The live configuration is the database representing the Live network configuration in ENM.
This is automatically created by ENM and cannot be deleted by a user.

Configuration Handling enables the user to perform the following:

 Display the history of CM data changes made to one or more network elements in the
live configuration made by CM Bulk Import operations.
 Undo the changes performed on nodes by CM Bulk Import operations.

Command Description

history
Display the history of CM data changes made to one or more Network Elements
in the live configuration (executed with CM Bulk import jobs)
Revoke Configuration Management changes that have been applied to Network
undo
with the CM Bulk Import application. This command generates a file in the
required format, which contains the necessary operations to reverse the changes
originally applied to the network by the specified job.
9.2.5 Import SW Packages and License Key Files for Network Nodes and
Export Inventory Data - shm Command Set

The shm command manages the import of software packages and license key files on network
nodes and also manages the export of Inventory data from network nodes to an XML format.
Exported files are in a compressed file format.

Command Description
Initiate an export of inventory node data from the network (CPP-based
export nodes only. For other node types, use cmedit.) License inventory data is
exported using a Non-3GPP compatible, proprietary format.
Import a software package or a license key file.
import
This feature is only used when importing from your local
Note:
workstation.
status View the list of jobs or job status for a particular job.

listdomaintype
List supported backup domains and types for a particular network
element.

backup
Create a backup of a node asynchronously (only supported for CPP and
COM/ECIM based nodes.)
restart Restart a node asynchronously (only supported for CPP based nodes.)

9.3 Configuration Handling

A live configuration is the ENM model of the current (live) configuration of the network. This
is automatically created by ENM and cannot be deleted by a user.

Configuration Handling enables you to do the following:

 Display the history of CM data changes made to one or more Network Elements in the
live configuration made by CM Bulk import.
 Revoke Configuration Management changes that have been applied to the network
where the source of the changes is the CM Bulk import to the live configuration.

User Interface

The user can access Configuration Handling in the following ways:

 ENM Command-Line Interface (CLI)

 REST CM Northbound Interface (NBI)

9.4 CM Supervision
CM Supervision ensures that ENM is constantly up to date with Configuration Management
changes on the network.
CM Supervision

CM Supervision is a feature in ENM that constantly listens and updates the ENM Database
with the current Network Nodes Configuration.

When CM Supervision is started, it initiates the node synchronization and processes node
notifications. In this way, it keeps ENM up to date with CM changes on the network.

Use the ENM CLI to activate or deactivate the CM Supervision for each node.

CM Heartbeat Mechanism

CM Heartbeat validates the Network Node Notification Subscription and confirms that there
is an open communication between the node and the ENM system.

Periodically, ENM monitors the status of the node connection and interrogates the node
subscription using a request sent through the node-specific protocol.

If a connectivity issue is detected, then CmFunction.syncStatus attribute is marked as

UNSYNCHRONIZED, and ENM tries immediately to re-create the subscription for CM
notifications (if required) and to re-sync the node.

If this re-sync fails, ENM will attempt to re-sync the node again at the next heartbeat interval.

Heartbeat Intervals

The Heartbeat Interval is 7 minutes.

 MINI-LINK Indoor CM support

CM solution for MINI-LINK Indoor type nodes is implemented with polling instead
of relying on notifications. The polling interval is 60 seconds.

 CISCO-ASR9000, CISCO-ASR900, and JUNIPER-MX, JUNIPER-PTX, JUNIPER-

SRX, JUNIPER-vMX, JUNIPER-vSRX CM support

CM solution for CISCO-ASR9000, CISCO-ASR900, and JUNIPER-MX, JUNIPER-

PTX, JUNIPER-SRX, JUNIPER-vMX, JUNIPER-vSRX nodes is implemented with
polling instead of relying on notifications. The polling interval is 60 seconds.

9.5 Node CLI Launch

The ENM operator can use Node CLI to launch the node-specific CLIs for a selected node
from Network Explorer.

The tasks the ENM operator can perform are as follows:

 Launch the CLI from Network Explorer for a selected node.

 Full ENM functionality is available. No additional application in the client machine
needs to be installed. The operator does not have to remember the IP address of the
node.

 Execute CLI commands for a selected node for the following purposes:
o Debugging
o Troubleshooting
o Additional node configuration
 Log in automatically.

The following functions are supported:

o Standard SSH username and password authentication.

o Passing a node-dependent fixed string as a username for SSH authentication
and doing the proper authentication afterwards.
o Telnet authentication (for MINI-LINK Indoor nodes).

For a list of nodes that ENM supports for CLI launch, refer to Supported Nodes for CLI
launch section.

9.6 Supported Nodes for CLI Launch

Table 7 Supported Nodes for CLI Launch
Node ne Type
Baseband T (T605) RadioTNode
BSC BSC
BSP BSP
Cisco Router ASR900 family CISCO-ASR900
Cisco Router ASR9000 family CISCO-ASR9000
CSCFv CSCF
DSC DSC
RBS
DU/Baseband Radio Node (Micro & Macro RBS)
RadioNode
EPG EPG

vEPG VEPG
Fronthaul 6080 FRONTHAUL-6080
Fronthaul 6622 FRONTHAUL-6020
Fronthaul 6624 FRONTHAUL-6020
Router6672 Router6672
Router6x71 Router6x71
 Table 7 Supported Nodes for CLI Launch
Node ne Type
Router6675 Router6675
Router6274 Router6274
Router6273 Router6273
Juniper Router MX family JUNIPER-MX
Juniper Router PTX family JUNIPER-PTX
Juniper Router SRX family JUNIPER-SRX
Juniper Router vMX family JUNIPER-vMX
Juniper Router vSRX family JUNIPER-vSRX
MINI-LINK Indoor nodes MINI-LINK-Indoor
MINI-LINK Outdoor MINI-LINK-Outdoor
MTASv MTAS
Pico Radio MSRBS_V1
RNC RNC
Router8801 Router8800
SBGv SBG
SCU SCU
SGSN-MME SGSN-MME
SIU02 SIU02
SSR 8004

SSR 8010 SSR

SSR 8020
TCU02 TCU02
CSCF-TSP

CCN-TSP

cSAPC-TSP
TSP
HSS-FE-TSP

MTAS-TSP

VPN-TSP
vBNG vBNG
vSAPC SAPC
 Table 7 Supported Nodes for CLI Launch
Node ne Type
WMG vWMG

9.7 Import and Export

3GPP Bulk CM Import/Export and Dynamic CM Import/Export provide the capability to
perform bulk manipulation (import and export) of configuration management data.

Import

Configuration engineers can perform the import task when they need to add large amounts of
network data to the management system. Import allows a configuration engineer to import
proposed configuration changes using a 3GPP Bulk CM IRP XML file or a CSV File
compliant to Ericsson Dynamic File Format (EDFF) into ENM and apply those changes to the
network.

Export

The configuration engineer can export the live configuration into a 3GPP XML export file
which can then be downloaded to the user's client machine. Export can be used in the
following ways:

 Export all CM data for one, several or all Network Elements, on demand.
 Export a subset of the CM data for one, several or all Network Elements using a
predefined filter or user-defined filter, on demand.
 Perform a regular scheduled export.

File Format

Import and export files are structured according to the 3GPP Bulk CM IRP XML file format.
Files can be imported and exported uncompressed or using zip compression.

User Interface

Import and export can be accessed in the following ways:

 The Import and Export commands of the Configuration Management CLI (see Read,
Manipulate, and Export Configuration Management Data - cmedit Command Set).
 Client scripting
 REST Configuration Management Northbound Interface

Dynamic CM Import/Export

Dynamic Bulk CM Import/Export provides the capability to perform bulk manipulation

(import and export) of configuration management data using Ericsson Dynamic File Format
(DFF).
Import

Configuration engineers can perform the import task when they need to add large amounts of
network data to the management system. Import allows a configuration engineer to import
proposed configuration changes using a file in Ericsson Dynamic File Format into ENM and
apply those changes to the network. Import can be performed in two ways:

 Import to the live configuration, whereby the CM data is applied to the network
immediately.
 Import to a non-live configuration, whereby the CM data is imported to a non-live
configuration and can be applied to the network as a separate action or can be
discarded if no longer required.

Export

The configuration engineer can export live and non-live network configuration into an
Ericsson Dynamic File Format export file which can then be downloaded to the user's client
machine. Export can be used in the following ways:

 Export all CM data for one, several or all Network Elements, on demand.
 Export a subset of the CM data for one, several or all Network Elements using a
predefined filter, on demand.
 Perform a regular scheduled export.

File Format

Import and export files are structured according to the Ericsson Dynamic File Format. Files
can be imported and exported uncompressed or using zip compression.

User Interface

Import and export can be accessed in the following ways:

 The Import and Export commands of the Configuration Management CLI (see Read,
Manipulate, and Export Configuration Management Data - cmedit Command Set).
 REST Configuration Management Northbound Interface

9.8 Bulk Node CLI

ENM Bulk Node CLI enables you to configure node-native CLI commands on single or bulk
nodes.

With ENM Bulk Node CLI, you can:

 Manage blacklist files by using upload, download, and delete functions. Blacklist files
are used to reject execution on a node if any of the blacklisted commands are found in
command script files.
 Manage command script files by using upload, download, list, and delete functions. A
maximum of five jobs can be executed in parallel and a maximum of five parallel
 users can perform the execution of the commands. Commands can be executed in two
ways:
o Execute line by line - for node-native CLI commands present in the command
script file.
o Execute by uploading a configuration file - for node types using the Router
6000 platform only.
 Manage jobs (list individual jobs and cancel functions or do the same for all jobs).
 Download log files. When jobs have completed, you can download the resulting log
file by using configurable parameters defined at system level. The default option is to
display commands by row.

The result log file is a CSV file with the following details :

o NodeType
o NeName
o IpAddress
o Date
o commandId
o command
o response

The node can refuse the disabling of echo for the Command Line Interface connection.
When this happens, the response can contain the echo of the typed command.

Jobs and resulting files that have lifetimes exceeding 30 days are managed by ENM.

 Use Bulk Node CLI functions to perform the reconfiguration of MINI-LINK MW

Radio links. You can download default ENM templates and rename them with unique
command script files. Do not delete the template files.

Table 8 Transport Nodes Supporting the Feature

Network Element Type neType
Ericsson Site Controller ESC
SIU02 SIU02
TCU02 TCU02
FRONTHAUL-
Fronthaul 6080
6080
FRONTHAUL-
Fronthaul 6622
6020
FRONTHAUL-
Fronthaul 6624
6020
Router6672 Router6672
Router6675 Router6675
Router6x71 Router6x71
Router6274 Router6274
 Table 8 Transport Nodes Supporting the Feature
Network Element Type neType
Router6273 Router6273
Router8801 Router8800
MINI-LINK-
MINI-LINK TN
Indoor
MINI-LINK-
MINI-LINK LH, MINI-LINK LH
Indoor
MINI-LINK-
MINI-LINK CN210
CN210
MINI-LINK-
MINI-LINK CN510R1
CN510R1
MINI-LINK-
MINI-LINK CN510R2
CN510R2
MINI-LINK-
MINI-LINK CN810R1
CN810R1
MINI-LINK-
MINI-LINK CN810R2
CN810R2
MINI-LINK 6691, MINI-LINK 6692, MINI-LINK 6693, MINI-LINK
6694, MINI-LINK 6291, MINI-LINK 6251, MINI-LINK 6252, MINI- MINI-LINK-669x
LINK 6262
MINI-LINK 6366 MINI-LINK-6366
MINI-LINK 6651, MINI-LINK 6654, MINI-LINK 6655 MINI-LINK-665x
MINI-LINK 6352 MINI-LINK-6352
MINI-LINK 6351 MINI-LINK-6351
MINI-LINK-
MINI-LINK PT 2020
PT2020
Fronthaul 6392 Fronthaul-6392
CISCO-ASR9000 series CISCO-ASR9000
CISCO-ASR900 series CISCO-ASR900
JUNIPER-MX series JUNIPER-MX
JUNIPER-SRX series JUNIPER-SRX
JUNIPER-PTX series JUNIPER-PTX
JUNIPER-vMX series JUNIPER-vMX
JUNIPER-vSRX series JUNIPER-vSRX
SCU SCU
SSR 8020, SSR 8010, SS8004 SSR
10 System
The System area deals with the management of ENM as an entity.

This management includes:

 Installation (physical and cloud)

 Upgrade (physical and cloud)
 Backup (physical and cloud)
 Restore (physical and cloud)
 Hardware maintenance on physical configuration

Many of these tasks are performed by Ericsson staff.

The main user of the Log Viewer is the system administrator. The Log Viewer allows the
system administrator to view the user activities that have been performed in the system at any
given time or over a specific time period.

Network Management Workflows

The System Administrator Guides provide information on the system administration activities.
These are available in the ENM CPI Library, EN/LZN 703 0205. The relevant ENM CPI
library is available from the ENM Launcher under Documentation.

10.1 Applications Used in System

A set of System Applications is available.

The applications are as follows:

 ENM Application Launcher

 ENM System Monitor
 Log Viewer

10.1.1 ENM Application Launcher

The ENM Application Launcher is a web-based application that provides easy one-click
access to all available web and desktop applications.

Launcher

The Application Launcher implements the online help interface which displays all the help
content associated with an application in one centralized view.

Click Help to see what changes have been implemented in the current release, for information
on how to use the application, and for frequently asked questions.

Online tutorials are now available in the ENM online help.

You can group applications alphabetically, by domain, or by using the Favorites function.

The search function allows global search on all applications by acronym or application name.
Click the info icon beside each link to find out more about the application.

Getting Started

To launch the ENM User Interface (UI), open a browser and enter the
URL:https://<HOST_NAME>:<PORT>/.

Figure 1 ENM Logon Page

Contact your system administrator for the relevant <HOST_NAME> and <PORT>.

You cannot connect to multiple ENM systems at the same time using the same domain
Note:
name.

The ENM Application Launcher lists the applications you can access. To launch an
application, click the application name.

You can mark applications which you access and use regularly as a favorite by clicking the
following icon:

To get more information on an application, click the following icon, which is next to the
application name:

Individual Help Applications and the Help Center offer comprehensive contextual online help
content.

10.1.2 ENM System Monitor

ENM System Monitor (ESM) provides operators with an efficient way to monitor basic
application, hardware and operating system metrics for the ENM system. It provides the
operator with stateful alarms which can be sent to ENM Fault Management.
ESM

ESM provides the operator with the following functions:

 Monitoring of hardware metrics for all server platforms

 Monitoring of operating system metrics for all server platforms
 Monitoring of metrics that are exposed by ENM applications
 Alerting of any breach of a configured threshold on a metric
 Forwarding of alerts as stateful alarms to ENM Fault Management
 Near real-time and historic viewing of metrics

ESM consists of a single-instance Server Layer and multiple agents. The ESM server runs on
a VM on the Management Server. The agents are installed on the various platforms (servers)
and MS which are monitored.

The information is sent from the agents to the server where it is displayed on a portal. The
portal can be viewed using a supported web browser.

ESM provides powerful alerting where the operator can set their own thresholds for any of the
metrics measured on the ENM system. ESM provides the operator with the ability to create
stateful alarms. This enables them to raise, escalate, de-escalate, and clear the alarms in FM.

10.1.3 Log Viewer

Log Viewer provides easy access to ENM System Logs.

The application provides an interface to query (using full text searching and complex
filtering) and view details of the provided logs.

Different types of logs are recorded in ENM:

 Security Logs used to track security-related information.

 Privacy Logs are the logs containing privacy information.
 Privacy Security Logs are the security logs containing privacy information.
 Audit Logs inform you about specific events.
 Trace Logs are used for debugging and troubleshooting applications.

Info/Debug/Notice Trace Logs are not available in Log Viewer but can be accessed from
server.log on every Virtual Machine (VM).

Log Viewer also implements an online help interface.

10.2 Backup and Restore

ENM Backup and Restore provides scheduled backup of the whole ENM deployment and
disaster recovery restore of the whole ENM deployment.

ENM Backup
ENM Backup is built on standalone, Solaris-based Operation and Maintenance Backup Server
(OMBS) that includes Symantec NetBackup. ENM Backup provides scripts for activating and
configuring the scheduled backups for the ENM deployment. Once activated, ENM backups
periodically back up all file systems used by the databases as well as all local and shared file
systems from the ENM deployment. The backup mechanism is model-based and client-
driven. This means that once the backup job is triggered by OMBS, the orchestration of the
backup operation takes place on the ENM backup client side. ENM system backup can be
divided to two phases that are executed sequentially:

Uses LITP architecture for snapshotting ENM file systems defined in the
Snapshotting
model

Streams snapshots (or live file systems) from ENM peer servers and SFS to
Backup
back up media (disk) in OMBS

ENM Restore

ENM Restore is orchestrated from OMBS by proprietary scripts delivered within ENM
Backup and Restore.

ENM Restore provides total disaster recovery and supports the restore of the whole ENM
deployment to the same hardware. Restore consists of three phases that can be executed
simultaneously or phase by phase. Phases are:

 Management Server restore from bare metal to fully functional

 ENM peer node redeployment: Initial install for ENM peer servers by using LITP
functionality
 ENM data restore: Actual data restoration by restoring file systems from backup
media

Additional system restore types include the MS restore with or without HW change, in case of
data corruption or hardware failure in MS, and partial data restore of Neo4j and dependent file
systems, to be used when Neo4j is inconsistent or as rollback option for release independence.

10.3 Cloud Backup and Restore

The Cloud Backup and Restore application provides the following for an ENM on Cloud
deployment: a framework for backing up the deployment manually, and a corresponding full
restore method for a disaster recovery scenario.

Cloud Backup

Cloud Backup relies on the OpenStack Cinder backup service, which must be enabled on the
cloud infrastructure. The Cinder backup service must be configured with the NFS backup
driver. For information about the provisioning of additional resources required for backup, see
ENM on Cloud Resource Configuration Data, 1/127 04-AOM 901 151 Uen, available from
local Ericsson support.
Backups are taken at the volume level using snapshots, based on the configuration provided in
the Site Engineering Document (SED). The backup process is run using VNF-LCM
Workflows.

The steps in the backup workflow are as follows:

1. Read the configuration provided in the SED.

2. Take backup snapshots.
3. Back up snapshots.
4. Remove snapshots.

Cloud Restore

Cloud Restore is orchestrated in a VNF-LCM Restore workflow as part of the Cloud Backup
and Restore application. This is a full restore, providing data recovery for the ENM on Cloud
deployment .

1. Read the configuration provided in the SED.

2. Find backups.
3. Delete ENM.
4. Recreate volumes.
5. Restore volumes from backup.
6. ENM initial install.

10.4 ENM Email Relay Service

ENM Email Relay Service provides communication capabilities to send emails out of ENM to
preconfigured destinations. This allows customers to be sent notifications about the network
through email.

Email Relay Service

An email relay service has been deployed (via Postfix) in ENM to provide email capability
from all hosts within the ENM deployment. These hosts can be on either physical or virtual
deployments.

This allows services to send emails regarding performance, fault management, and other
notifications to interested parties.

An email exchange server - reachable on the external network - is required. This forwards the
email to its destination.

ENM Email Relay service is available via the alias "emailrelay".

To configure the email relay service to forward mails to a relay host, the SED variable
EMAIL_DOMAIN must be updated to a domain, relay host alias, or specific IP address. You
must then redefine both LVS Router VMs and restart them.

Postfix provides the main.cf file to configure the destination.

For more information, refer to the section Configure ENM Email Relay Service to Add
Routing Notifications via Email in ENM System Administrator Guide 1/1543-AOM 901 151.

10.5 ENM on Cloud HA Solution

The vENM High Availability (HA) solution is the mechanism by which ENM ensures
availability of its VMs/applications.

All VMs in vENM are recovered by this mechanism (except vnflaf-services and vnflaf-
db which have their own HA mechanism).

The HA Solution is provided by three main parts:

 Simple-Availability-Manager (SAM) Agents, which monitors the health of each VM

via healthchecks.
 Simple-Availability-Manager (SAM), which triggers a HA workflow for all VMs in
failed state or in critical health.
 HA Workflow, which recovers all given VMs using Openstack requests.

10.5.1 HA Solution Terms

Consul

Consul is a 3PP that provides service registration and service discovery. Every VM in vENM
(except vnflaf-db) is a Consul member, that is, part of a Consul cluster. The state of a VM in
vENM is shown by its state in the Consul cluster.

Table 9 VM States in a Consul Cluster

State Description
alive The member is healthy.
failed The member is unreachable.
left The member has left the Consul cluster.

Consul members manage the state of their own cluster using a peer to peer gossip protocol.
Any member of the cluster that is unreachable for longer than the time-out period is
considered failed.

The time-out is scaled with the size of the cluster and is determined by the following formula:

4* log(N+1), where N is the cluster size.

Healthcheck

A healthcheck is a script that verifies that an application or service is healthy. Healthchecks

used in vENM are:

 Written by applications to verify their own behavior.

  Provided by default in Consul as built-in availability and network checks.

The execution result of the healthchecks and the state of the VM in Consul reflects the overall
Consul health status of a VM.

High Availability in vENM is concerned with two states - passing and critical.

Table 10 Consul Health Status of a VM

Status Description
passing Member healthchecks are passing.
critical Member healthchecks are failing.

Stacks

All vENM applications are (from OpenStack's point of view) described as Heat Orchestration
Templates or stacks. The general structure of a vENM stack is as follows:

 Outer stack (OpenStack resource representing an entire Service Group)

o Server Group
o Resource Group
 Inner stack* (OpenStack resource representing all OpenStack resources
for a single instance of a Service Group)
 VM (OpenStack resource representing the VM instance)
 Ports (OpenStack resource representing the internal and external
IPs for a VM)

* A resource group can contain one or multiple inner stacks, each with VM and ports.

10.5.2 HA Solution Requirements and Triggers

Requirements for a HA Event to Start

 A healthy VNF-LCM.
 A healthy servicereg instance in the capacity of leader.

Reasons Why a HA Event Will Occur

A HA event occurs in the following scenarios:

 A VM has failed a vENM member healthcheck. That is to say, the Consul health status
of the VM is critical.
 An infrastructure level outage, such as compute node failure or power outage. That is
to say, the Consul member status of the VM has become failed.

10.5.3 HA Event Overview

10.5.3.1 Simple-Availability-Manager (SAM) Agents

SAM Agents is an application in the HA solution that is installed on every VM in vENM
(except vnflaf-services and vnflaf-db).

SAM Agents is the first component in the HA solution and it has two responsibilities:

 Run healthchecks on a 30-second interval.

 Examine the results of those healthchecks to determine if the VM should be set to
critical.

During a VM initial boot sequence, a VM is given a default of 10 minutes to become

Note: healthy. During this initial stage, it is expected for a VM to fail its healthchecks.
Doing so does not result in a HA event.

10.5.3.2 Simple-Availability-Manager (SAM)

SAM is an application in the HA solution that is installed on every servicereg instance in

vENM. Of these, only a single delegated instance performs the action required by SAM.

SAM is the second component in the HA solution and it has a single responsibility:

 On a 30-second interval, the delegated instance notifies VNF-LCM of all VMs that
have a Consul member state of failed or a Consul health status of critical
(determined by SAM Agents).

When VNF-LCM is notified of VMs to recover, it moves those VMs to Consul state
left.

10.5.3.3 HA Workflow

HA Workflow is the main application in the HA solution that recovers VM instances using a
series of OpenStack commands. A single HA workflow is started for all VMs reported by
SAM. The HA Workflow asks the Cloud infrastructure to replace each stack containing the
VM with a newly created identical stack.

Note: The steps taken to recover a stack depend on whether a vENM Upgrade is ongoing.

Upgrade Not in Progress

The default way that HA Workflow recovers a stack is as follows:

1. VM is stopped (graceful shutdown period).

2. Inner stack is deleted (to destroy the VM and its resources).
3. Inner stack resource is marked 'unhealthy' (to inform OpenStack about which resource
needs to be re-created).
4. Stack is updated on the Resource Group (to replace all inner stacks marked 'unhealthy'
in OpenStack with new resources).

The benefit of this flow is that it is capable of recovering VMs that failed because of an
infrastructure outage.
Upgrade in Progress

If an upgrade is in progress, HA Workflow recovers a stack using the following steps:

1. VM is stopped (graceful shutdown period).

2. Server volumes are detached (to ensure that the volume resources are available to be
attached to the new instance).
3. VM resource is marked 'unhealthy' (to inform OpenStack about which resource needs
to be re-created).
4. Inner stack is updated (to replace all VMs marked 'unhealthy' in OpenStack with new
VMs).

Unlike the default (upgrade not in progress) flow, this flow prevents HA from inadvertently
undoing upgrade work on a stack. It is not capable of recovering VMs that failed because of
infrastructure outages.

10.5.3.4 HA Workflow Retry

If HA is unable to recover a VM on the first execution of the recovery commands, it retries

the workflow sequence after a wait interval of one minute.

Subsequent retries, up to 29 attempts, also have a wait interval of one minute. There is then a
back-off of 2 minutes, 4 minutes, 8 minutes, and 16 minutes, respectively. Following this, the
retry wait interval stays at 30 minutes.

HA retries the flow (if it is unsuccessful) 1000 times or for about 21 days. The long duration
is to give the best chance of recovery.

An extended HA workflow retry may cause the workflow to appear stalled (not progressing)
for a long period of time.

Reasons why a HA workflow would enter an extended retry are:

 Failure to recover a VM.

 Infrastructure failures in OpenStack.

11 Security
ENM's software security system aims to protect ENM internal and managed network assets
from malicious attacks and use.

ENM Security

ENM consists of a number of security management functions and specific security controls
which adhere to industry-wide security standards. The following security management
functions are in place:

 Identity and Access Management (IdAM)

 PKI Management System
  Node Security Configuration Service (NSCS)
 Logging and log viewing

A number of security controls are in place to ensure minimal exposure to security risks. The
controls implement various principles:

 Confidentiality through protection of key communication channels (internal to ENM

and external towards the managed network and northbound systems)
 Defense in Depth through protection of key system assets (system data, configuration,
and models, as well as private data where applicable) and perimeter protection
(security zones)
 Assurance processes applied during system development (risk assessments and regular
security testing)

The ENM security framework is documented in the following guides:

 ENM Security System Administrator Guide Provides an overview of the security

solution in ENM.
 ENM Identity and Access Management System Administrator Guide Provides Identity
Management and control of authentication and authorization of ENM users involved
in the operation and maintenance of the network.
 ENM Network Security Configuration System Administrator Guide Provides ENM-
related business logic needed to configure Network Elements to support different
security features.
 ENM Public-Key Infrastructure System Administrator Guide Provides PKI functions
and certificates management.
 ENM Node Hardening Instructions and Guidelines Specifies measures that must be
taken after installation to ensure that both the operating system and application surface
of vulnerabilities is as small as possible.
 Identity and Access Management Programmers Guide Specifies the REST-based
interface that can be used to integrate ENM and an external IdAM system.

Each security function has online help.

Security Functions

Identity and Access Management

IdAM is a set of capabilities focusing on provisioning, authentication, and authorization of

users and roles required to operate both ENM and the managed network (where applicable).
The high-level summary of supported capabilities is as follows:

 User Management consists of Create, Retrieve, Update, Delete (CRUD) operations for
ENM user accounts and capability to assign or unassign users to roles (both predefined
and user-defined roles).
 Role Management enables the creation of new user-defined roles based on application-
specific use cases (custom-defined roles).
 Centralized user management for Baseband radio nodes (including assignment of
nodes as Targets).
  Single Sign-On (SSO) enables the user to log on to the ENM system only once and
browse based on their access privileges.
 Configuration of some system parameters, such as password complexity and idle and
active session time-outs.

All ENM Identity Management and access control can be achieved through a simple-to-use
graphical interface.

The system also offers a Northbound Interface based on Representational State Transfer
(REST) to enable the integration of external systems. The ENM System Security
Configuration Programmers Guide contains the interface specification and the configuration
description for the integration of the SSO capability.

PKI Management

ENM offers PKI Management System to meet the requirements of a managed network and
support ENM internal services.

Apart from offering basic PKI functions (issue/reissue/revoke certificates), the system also
supports certificate publishing for trust distribution, Registration Authority (RA) with SCEP
and CMPv2, Vendor Credential Management and certificates for external entities (for
example,web servers, SeGW). Certificate enrollment can be done for use in Baseband radio
nodes.

Node Security Configuration Service

NSCS provides CLI and UI (limited capabilities) for managing specific network element
security configurations such as security levels, keys, SNMP etc.

Logging and Log Viewing

ENM logs all user and system-relevant events (application, operating system, 3PPs) in a
predefined structure.

ENM application logs can be viewed and exported through the Log Viewer application.

Security Controls

System data, configuration and models are embedded within internal security zones which
reduce the potential scope of malicious attacks on the system. Recommendations are provided
to set up physical firewalls to secure the access towards the Network Elements. Software
firewalls are defined on all ENM peers containing the valid rules for both outgoing and
incoming access.

Key internal and external communication channels are protected using security protocols such
as HTTPS, SSH, and SFTP.

Identity and access management configuration established through the IdAM function is
applied throughout the system to ensure that principles of accountability and non-repudiation
and least privilege are applied to all access to system resources. Those principles are
implemented through role-based access control (RBAC).

Even though a large portion of potential vulnerability is removed by system pre-hardening,

ENM also provides the ENM Node Hardening Guidelines and Instructions which must be
followed as mandatory steps after installation for additional system hardening.

Development processes in ENM ensure that activities like risk assessments and regular
security testing, analysis and corrections are executed on regular basis.

11.1 Applications Used in Security

A set of security applications is available from the ENM Application Launcher.

The applications are as follows:

 Node Security Configuration

 PKI Entity Management
 PKI Profile Management
 Role Management
 System Security Configuration
 Target Group Management
 User Management
 User Profile

11.1.1 Node Security Configuration

The Node Security Configuration application shows the security levels of all the nodes and
allows the user to filter and to switch the security levels of the nodes.

11.1.2 PKI Entity Management

This tool allows the configuring of the following entities:

 PKI CA Entity
 PKI End Entity

The following additional features are available:

 Display the PKI certificates assigned to a PKI entity.

 Issue a PKI certificate for both the PKI CA entities and the PKI end entities.
 Reissue a PKI certificate for the PKI end entities.

PKI CA Entity

The PKI CA entity is the entity responsible for all operations related to certificate
management, for example the PKI CA entity issues the certificates to end entities or sub CAs.

PKI End Entity

The PKI end entity is the end user entity that is the subject of a certificate. End Entity uses the
certificate to identify itself to any other parties.

11.1.3 PKI Profile Management

This tool allows the configuration of the following profiles:

 PKI Certificate Profile

 PKI Trust Profile
 PKI Entity Profile

PKI Certificate Profile

A certificate profile is a description of a set of configuration settings that can be applied for a
set of certificates. This makes it possible for one CA to issue certificates to different purposes.
These certificates can have different signature and hashing algorithms or different certificate
extension fields.

PKI Trust Profile

A trust profile is a template that describes the CA trust certificates between the entities. The
entities must have trust with other entities. This is achieved by distributing the CA trusted
certificates.

PKI Entity Profile

An entity profile is a description of a set of configuration settings that can be applied for a set
of entities that have very similar certificates. Therefore the entity profile is a template for a set
of entities and the PKI can issue the certificate for these entities.

11.1.4 Role Management

Role Management allows the administrator to manage ENM System roles, COM roles, COM
role aliases and custom roles.

 System roles are roles predefined in the ENM system. There is no possibility to
modify system roles.
 COM roles allocate specific privileges on nodes supporting ECIM.
 COM role alias is a set of COM roles, which groups these roles for easier assignment
to user.
 Custom roles consist of a combination of ENM application privileges and COM roles.
Custom roles allow creation of a fine-grained set of application access rights in the
form of resource-action pairs.

11.1.5 System Security Configuration

System Security Configuration enables a Security Administrator to manage security

configurations.
  General Settings enables the Security Administrator to enable or disable the Logon
Successful screen.
 Password Settings provides an interface to manage password complexity, password
aging, and account lockout.
 Session Settings enables the Security Administrator to enforce session duration and
idle time-outs.
 User Profile Settings enables the Security Administrator to grant or deny users
permission to edit their own data.

11.1.6 Target Group Management

A Target is a network element. A Target Group is a logical grouping of Targets. Target

Groups are used for granting access to a grouping of Network Elements. The Target Group
Management application allows the administrator or operator to perform the following
operations:

 Define a Target Group

 Delete a Target Group
 Update an existing Target Group

There are two predefined Target Groups:

 ALL - Target Group containing all Network Elements.

 NONE - Target Group containing no Network Elements.

By default, all users in ENM are assigned roles with predefined Target Group ALL, which
means the user has privileges on all Network Elements. It is possible to define a target group
for a user to allow the user to access part of ENM network i.e. to only targets in the associated
target groups.

11.1.7 User Management

User Management allows a Security Administrator to create and delete users, assign users
with roles, and manage password functions. The mapping of roles, target groups, and users is
also performed in this application.

Available operations for Security Administrator:

 Creation of Users
 Editing of existing Users
 Assigning User Roles and Target Groups
 Changing User Password
 Deleting Users
 Duplicating a User
 Filtering Users
 Revoking User Certificate
 Retrieving User Credentials

Only users with the assigned role SECURITY_ADMIN have access to User Management.
11.1.8 User Profile

User Profile is an application that enables users to manage their profiles.

The functions supported by the application include: editing data, getting credentials, and
changing a password.

11.2 CLI Commands Used in Security

The following command sets are used in Security:

 credm, see Manage Security Configuration and Administration for ENM services -
credm Command Set
 lcmadm, see Add, Edit, and Remove Licenses and Manage the License Usage
Information - lcmadm Command Set
 pkiadm, see Perform CRUD Operations on Profiles, Entities, and Certificates - pkiadm
Command Set
 secadm, see Manage Security Configuration and Administration for Network Nodes -
secadm Command Set

Full information about the commands within the command sets, including
Note:
command syntax and role requirements, is provided in the online help.

11.2.1 Manage Security Configuration and Administration for ENM services -

credm Command Set

Command Description
reissue Reissues certificates to services with new keys, and revoke old certificates.
list Lists ENM and 3PP services.

lock
Changes the ismodifiable attribute of a profile to false, so that the profile
cannot be modified further.

unlock
Changes the ismodifiable attribute of the profile to true, so that the profile
can be updated using CLI/UI.

11.2.2 Add, Edit, and Remove Licenses and Manage the License Usage
Information - lcmadm Command Set

Command Description
activate Activate emergency unlock in the management system through the CLI.
export Export license usage in the management system.
install Install licenses in your management system
get Retrieve license information from the management system
list List all licenses in your management system.
 Command Description
remove Remove a license from the management system.
set Set license usage.
delete Delete an existing collection.

11.2.3 Perform CRUD Operations on Profiles, Entities, and Certificates -

pkiadm Command Set

Command Description
Certmgmt Generate, reissue, export, and list certificates.
Manage and retrieve algorithms and create, update, list, or delete
Configmgmt EntityCategory for Ericsson Network Manager (ENM) security
configuration.
Entitymgmt Manage and retrieve entities in the PKI System.
Extcaexport Export a certificate associated with an external CA into PEM format.

Extcaimport
Import an external CA certificate. The format of the imported certificate
file must be in PEM.

Extcalist
Retrieve a list of information about an external CA or all CAs imported
into the ENM system.

Extcaremove
Remove an external CA from ENM completely, including all the
associated certificates and CRL files.
Remove from an external CA the CRL with the specified issuer name. If
Extcaremovecrl the issuer name is not specified, remove all the CRLs for an external CA
from ENM completely.
Extcaupdate Add or update a CRL file related to an existing external CA.
Profilemgmt Manage and retrieve the certificate and entity profiles in a PKI System.
Revmgmt Revoke a CA certificate or an end entity certificate.

Crlmgmt
Generate a CRL on demand, download a CRL, list CRLs, publish a CRL
to CDPS, or unpublish CRL from CDPS.
Publish CA Entity and End Entity Certificates to TDPS, or unpublish CA
Trustmgmt Entity and End Entity certificates from TDPS, or list all CA and End
Entity certificates published to TDPS.

11.2.4 Manage Security Configuration and Administration for Network Nodes

- secadm Command Set

Command Description
Certificate Manage certificates on the network nodes.
Credentials Manage security credentials on the network nodes.
 Command Description
Crl Manage the CRL on the network nodes.
Disable Disable the CRL Check on the network nodes.
Enable Enable the CRL Check on the network nodes.
Get List the supported and enabled ciphers on the network nodes.
Job Manage the status of a secadm running command.

ldap
Configure and reconfigure the LDAP settings on a single or multiple
nodes.
Read Read the status of CRL Check on the network nodes.
 Get: Display the current operational security level on a Cello
Packet Platform (CPP) node
 Set: Switch the security level for a list of nodes from level 1 to
Securitylevel
level 2 (SL2 Activation) or from level 2 to level 1 (SL2
deactivation).

Set Set ciphers on the network nodes.

Snmp Manage both the authnopriv and the authpriv SNMPv3 security levels.
Generates and updates the ENM public and private SSH keys (key pair).
SShkey This key pair is stored into the node to allow an SSH connection between
the ENM and the node.
 Distribute: Start a job for trust distribution to the nodes.
 Remove: Start a job for trust removal from the nodes.
Trust
 Get: Return the status of the trust certificate installation.

11.3 License Control and Monitoring Service

The License Control and Monitoring (LCM) service provides the infrastructure in ENM to
manage feature licenses (RTU: Right to Use) and capacity licenses (RTC: Right to Connect)
as well as support license enforcement.

The LCM service supports both feature and capacity licenses. Feature licenses control user
access to available functions. Capacity licenses apply a blocking action when the system
resource usage exceeds the capacity limit for an installed capacity license.

Administrators can use LCM to:

 Set license alarms based on defined thresholds.

 Allow emergency unlock activation.
 Manage grace periods.
 Get the network resource usage for a price parameter .
 Get license status.
 Export license usage information.
  Manage license inventory.
 Install license files in ENM.

LCM prevents the use of Value Pack features if a valid feature license is not installed. LCM
also periodically measures the system resource usage defined for each capacity license and
prevents adding a new node when usage exceeds the limit.

ENM applies a blocking action if one of the following occurs:

 The system resource usage exceeds the capacity limit for an installed capacity license.
 A license has expired.
 A license is not installed.

For a network package capacity license, license service controls the adding of a node into
ENM by validating the network usage against the capacity license limit according to the price
parameters in the license file.

A grace period applies to specific capacity licenses. The grace period is triggered for a license
when the usage exceeds the capacity limit, and lasts for a predetermined amount of time.
Blocking actions related to the license do not take place during the grace period, irrespective
of the resource usage.

The LCM CLI activates the emergency unlock to last for a predetermined amount of time.
Blocking actions relating to a license do not take place during the emergency unlock,
irrespective of the resource usage or if licenses are installed.

The following RTC licenses are supported for ENM:

 Capacity License: LTE #5 MHz Sector Carrier Price Parameter enforcement

 Capacity License: SGSN-MME #KSAU Price Parameter enforcement
 Capacity License: MGW #SCC Price Parameter enforcement
 Capacity License: R6000 #NodesPrice Parameter enforcement
 Capacity License: Fronthaul 6080 #Nodes Price Parameter enforcement
 Capacity License: Fronthaul 6020 #Nodes Price Parameter enforcement
 Capacity License: MINI-LINK #Nodes Price Parameter enforcement
 Capacity License: CISCO-ASR9000 #Nodes Price Parameter enforcement
 Capacity License: JUNIPER-MX #Nodes Price Parameter enforcement
 Capacity License: JUNIPER-PTX #Nodes Price Parameter enforcement
 Capacity License: JUNIPER-SRX #Nodes Price Parameter enforcement
 Capacity License: JUNIPER-vMX #Nodes Price Parameter enforcement
 Capacity License: JUNIPER-vSRX #Nodes Price Parameter enforcement
 Capacity License: SSR #Nodes Price Parameter enforcement
 Capacity License: vBNG #Nodes Price Parameter enforcement
 Capacity License: Router8800 #Nodes Price Parameter enforcement
 Capacity License: GenericESA #Nodes Price Parameter enforcement
 Capacity License: HLR-FE #Nodes Price Parameter enforcement
 Capacity License: HLR-FE-IS #Nodes Price Parameter enforcement
 Capacity License: HLR-FE-BSP #Nodes Price Parameter enforcement
 Capacity License: vHLR-FE #Nodes Price Parameter enforcement
 Capacity License: MRS #SCC Price Parameter enforcement
  Capacity License: FAT1024077 #Management System Price Parameter enforcement

12 Northbound Interfaces Used in ENM

An overview of the Northbound Interfaces used in ENM.

12.1 REST File Lookup Service (FLS)

The File Lookup Service Northbound Interface (FLS NBI) is a REST NBI application that
provides metadata about files stored in the ENM system to external systems such as Ericsson
Network IQ (ENIQ), Self-Organizing Network (SON), and external customer applications.

A Machine to Machine interface gathers the metadata.

Functionality Overview

Using the FLS NBI, external applications running outside ENM execute queries to get file
location details and other meta information. ENM uses the general scripting service to support
external systems in accessing the files from the ENM file system, based on the file location.

Currently the FLS NBI supports the following files:

 Performance Management files

After the PM Report Output Period (ROP) file is collected from the network element,
Performance Management Initiation and Collection (PMIC) adds the file metadata into
FLS. FLS maintains the file metadata as long as it is present in PMIC file system.

PM files include:

o All types of PM ROP files collected from the nodes (Stats files and Recording
files)
o PM ROP files generated by ENM (Event-Based Statistics files)
 Uplink Spectrum File Collection (ULFC) files

After an Uplink Sample File is collected from the network element, ULFC adds the
file metadata into FLS. The FLS maintains the file information as long as it is present
in the Uplink Spectrum Analyzer (ULSA) file system.

The FLS NBI feature consists of the interface suite REST GET FILE METADATA that provides
an interface for fetching the metadata of files. FLS supports advance filtering using the Feed
Item Query Language (FIQL).

For details about PM and ULSA files for the FLS NBI, see the following:

 PM Fields for FLS NBI

 ULSA Fields for FLS NBI
12.1.1 PM Fields for FLS NBI

The meta information that can be obtained from querying FLS for a Performance
Management (PM) file is based on the following fields:

Table 11 PM Fields for FLS NBI

Field Name Description
id The unique identifier or token of the file.
The Fully Distinguished Name (FDN) of the network element from
nodeName where the file is collected. Contains the complete Distinguished
Name from the root element.
The absolute path where the file is located in ENM File system,
fileLocation
including the filename.
The creation time of the file in the ENM File System, based on the
fileCreationTimeInOss Linux time stamp. Producers can use this attribute to get the files
that are older than the retention period.
nodeType The node type.
dataType The file type, for example PM Data file.
fileType The format of the file. For example, compressed, decoded.
startRopTimeInOss The start ROP time of the file in the ENM server time zone.
endRopTimeInOss The end ROP time in the ENM server time zone.
fileSize The size of the file in Bytes

12.1.2 ULSA Fields for FLS NBI

The meta information that can be obtained from querying FLS for an Uplink Spectrum
Analyzer (ULSA) file is based on the following fields:

Table 12 ULSA Fields for FLS NBI

Field Name Description
id The unique identifier or token of the file.
The Fully Distinguished Name (FDN) of the network element
nodeName from where the file is collected. Contains the complete
Distinguished Name from the root element.

fileLocation
The absolute path where the file is located in ENM File system,
including the filename.
The creation time of the file in the ENM File System, based on
fileCreationTimeInOss the Linux time stamp. Producers can use this attribute to get the
files that are older than the retention period.
nodeType The node type.
dataType The file type, for example PM Data file.
 Table 12 ULSA Fields for FLS NBI
Field Name Description
fileType The format of the file - for example, compressed, decoded.
sampleTime The measurement time reported by the node inside the file.
radioUnit The radio unit identifier.
rfPort The Radio Frequency (RF) port identifier.

12.2 Configuration Management Events

Configuration Management Events Interface (CM Event NBI) is a REST-based querying
interface supporting the retrieval of all network configuration changes that are registered and
recorded by ENM.

The CM Events Northbound Interface (NBI) application is deployed in the ENM domain
management system to provide external systems, such as Network Resource Management
System, access to CM event data using a Machine to Machine interface. The CM Events NBI
application is part of the Dynamic CM NBI feature.

The Dynamic CM NBI feature offers a set of interfaces for external machine systems to
perform CM-related operations towards nodes managed by ENM. The following section
describes the Dynamic CM NBI interface for CM Events NBI.

The CM Events actions are Machine to Machine interfaces comparable to the CM Editor
commands in the ENM CLI.

The features of the CM Events NBI include:

 External systems can receive events for CM changes that occur on nodes managed by
ENM and any other CM data that ENM may retain regarding those nodes.
 External systems can access historical CM event data, which is event data for events
that have already been received and processed by ENM.
 External systems can request a batch of CM Events. The request can include a
reference to a saved filter or an explicit set of filter criteria. The request can also
include a maximum number of events to return.

The CM Events NBI feature consists of the following interface suite:

GET Events This provides an interface for retrieving CM Events

This provides an interface for the following:

 Returns a complete list of Event filters

GET Event filters
 Returns a filter based on the filter ID attribute
 Creation and deletion of filters for retrieving CM Events
REST Northbound Interface is an OSS feature that is deployed in the ENM domain
management. It provides external systems (such as Network Resource Management System)
read and write accesses to CM data using a Machine to Machine interface.

12.3 REST Configuration Management Northbound

Interface
The REST CM actions are Machine to Machine interfaces. These are comparable to the CM
Editor commands in the ENM CLI.

The REST CM NBI benefits include:

 CM data can be imported and exported to an external system.

 CM data can be manipulated by an external system.

The REST CM Northbound Interface feature consists of the following interface suites:

Provides an interface for importing and exporting CM data. It uses

file-based transfer. The file format supported can be a 3GPP
compliant XML format, or an Ericsson Dynamic file format. Links
REST CM BULK
(TCIM-Transport Common Model) are imported or exported using
NBI
3GPP format in live configuration. See TCIM Model Description,
3/15519-CNA 403 3141, for detailed information on the managed
objects, attributes and relationships.

Provides an interface for the following configuration functionalities:

REST
 Undo configuration changes made to Live Network by CM
CONFIGURATION
Bulk import to Live operation
NBI
 Get all jobs of undo Config

12.4 Fault Management (FM) Basic Network Surveillance

Interface (BNSI)
FM BNSI NBI implements the Basic Network Surveillance Interface protocol (see BNSI,
Basic Network Surveillance Interface Protocol Specification, Interface) which is a text-based
protocol for providing Fault Management capabilities over a supervised EMS, in this scenario
ENM itself.

The Network Management System (NMS) implementing the BNSI interface on the client side
can connect to the BNSI NBI in ENM to receive alarms, error messages and to perform
operations (acknowledge, clear, and synchronize in several ways) on alarms and error
messages of nodes supervised by ENM at a given time.

Filtering capabilities, which can be configured offline and enabled on the fly over the BNSI
session, are supported.
The forwarded alarm records are coded as a sequence of lines with readable text according to
a syntax described in the BNSI protocol specification.

The supported transport mechanisms used to transfer alarm records in BNSI format are SSH,
RSH, and REXEC.

Stop!

High security risk.

The use of RSH and REXEC protocols for connecting to ENM BNSI NBI is supported just
for backward compatibility towards the legacy product, however it is discouraged. RSH and
REXEC protocols are considered highly vulnerable and open for exploitation. They can
expose the systems as authentication data is sent in clear text, which means that someone can
gain unauthorized access to ENM. This risk does not apply to BNSI sessions started over SSH
protocol.

The protocol is data-driven and no polling mechanism is needed (the protocol supports the
push of heartbeat messages over the BNSI session towards the NMS).

Only Version 3 of BNSI protocol is supported.

Further details about ENM FM BNSI NBI implementation and how to connect to it can be
found in the FM BNSI Northbound Interface Integration Programmers Guide.

12.5 Fault Management (FM) CORBA

The FM CORBA NBI implements the CIRP solution set defined by 3GPP.

One or more Network Management Systems (NMS) implementing the CORBA Alarm IRP
(CIRP) interface for fault management can connect to the Fault Management (FM) NBI in
ENM to receive alarms and error messages, and perform operations
(ACK/UNACK/GetAlarmList) on alarms and error messages. A naming service is used to
connect to NBI and a notification service is used to push alarms to NMS.

Alarm and Event IRP CORBA objects are registered in the ENM Name service accessible to
NMS systems.

The CORBA Notification service is the standard OMG Notification service. Notification IRP
is exposed as CORBA Notification Service as per the CIRP protocol.

The following are the alarm and notification IRP versions that need to be supported.

Version IRP Type Specification

3G TS 32.106-1 Notification IRP Requirement Specification v3.2.0
3G TS 32.106-2 Notification IRP Information Service v3.2.0
3G TS 32.106-3 Notification IRP CORBA Solution Set v 3.2.0
3G TS 32.111-1 Alarm IRP Requirement Specification v3.2.0
 Version IRP Type Specification
3G TS 32.111-2 Alarm IRP Information Service v3.2.0
3G TS 32.111-3 Alarm IRP CORBA Solution Set v 3.2.0

Alarm OPI information is forwarded to NMSs CORBA NBI in the form of a structured event.

The 3GPP FM NBI provides configurable Quality of Service attributes to control the
communication of events and alarms to external systems.

12.6 Fault Management (FM) Simple Network

Management Protocol (SNMP)
The Fault Management (FM) Simple Network Management Protocol (SNMP) NBI enables
ENM Fault Management to communicate with the Network Management System (NMS)
through SNMP. This makes it possible to communicate alarms from ENM FM to subscribers.

The Network Management System (NMS) implementing the SNMP interface on client side
can connect to the SNMP NBI in ENM to receive alarms and alert messages.

For more information about this NBI implementation and how to connect to it, see the FM
SNMP Northbound Interface Integration Programmers Guide, 1/19817-CNA 403 3436.

13 Automated Generic Acceptance Test

(AGAT)
AGAT is a function that automates a selection of Generic Acceptance Test Cases (typically
performed after upgrades).

AGAT leads to reduced cost when introducing a new ENM version into a customer lab
environment by reducing the manual acceptance test effort.

It increases the confidence in the quality of test case execution by having less manual (and
thus less error prone) acceptance test execution.

It is an enabler for true continuous deployment of ENM where functionality is continuously

delivered to a customer.

Test Executor (TE)

Test Executor (TE) is a Docker-based solution for test case scheduling, test execution, and
test reporting.

It provides an easy way to distribute the execution of testware and run it in an isolated
environment for the quickest feedback possible.
For more information, consult the online help and the documentation for Test Executor
Configuration and Operation, 1531 - CXP 903 3012 Uen, available from local Ericsson
support.

AGAT

AGAT contains a selection of automated GAT test cases from the various ENM GAT
documents. Once the AGAT ISO is deployed and set up, TE is used to execute the test cases
and view reports for the test execution outcome.

For more information, consult the ENM AGAT Setup and User Guide.

Reference List
[1] Overview of ENM Deployments,3/1551-AOM 901 151
[2] Analytic Session Record (LTE) Specification,1551-CNA 403 3416
[3] ENM Supported Network Elements,3/1029-AOM 901 151
ENM on Cloud Backup and Restore System Administrator Guide, 1/127 04-AOM 901
151
[4]
Contact Local Ericsson Support
ENM FM SNMP Northbound Interface Integration Programmers Guide,1/198 17-CNA
[5]
403 3436
[6] ENM Security System Administrator Guide,2/1543-AOM 901 151
ENM Identity and Access Management System Administrator Guide,2/1543-AOM 901
[7]
151-1
ENM Network Security Configuration System Administrator Guide, 2/1543-AOM 901
[8]
151-2
[9] ENM Public Key Infrastructure System Administrator Guide,2/1543-AOM 901 151-3
ENM Online Help, available from ENM Launcher
[10]
Contact Local Ericsson Support.
[11] Network Health Monitor KPIs,1/100 56-CNA 403 2994
[12] ENM Performance Management System Administrator Guide,1/1543-AOM 901 151-3
WAN-SDN Controller Installation Guide, 1531-CNA 403 3594
[13]
Contact local Ericsson support.
[14] ENM AGAT Setup and User Guide, 1/1553-6/AOM 901 151 Uen
[15] Analytic Session Record (NR) Specification, 1/1551-CNA 403 3416
Legal |© Ericsson AB 2017-2020