Professional Documents
Culture Documents
Optus VENM Solution Overview PA5
Optus VENM Solution Overview PA5
Optus VENM Solution Overview PA5
Rev
Optus vENM Solution Overview
© Ericsson AB 2017
All rights reserved. The information in this document is the property of
Ericsson. Except as specifically authorized in writing by Ericsson, the
receiver of this document shall keep the information contained herein
confidential and shall protect the same in whole or in part from disclosure
and dissemination to third parties. Disclosure and disseminations to the
receiver's employees shall only be made on a strict need to know basis.
Table of contents
1 Introduction........................................................................................
3 Product Overview..............................................................................
3.1 Ericsson Network Manager (ENM)......................................................
3.1.1 ENM Software Architecture..................................................................
3.1.2 ENM Features and Functionalities.......................................................
5 vENM SW BoQ..................................................................................
5.1 vENM Production SW........................................................................
5.2 vENM Test Lab SW...........................................................................
9 References........................................................................................
Revision History
1 Introduction
Ericsson is the market leader in Telecom Management solutions and has been
in the telecom management business for over 25 years. Today, Ericsson has
an installed base of more than 1000 Radio and Core Mobile management
systems worldwide and more than 80 Wireline management systems
worldwide.
ENM collects fault and performance data from underlying nodes which is
displayed on FM GUI and tools for efficient network monitoring and
troubleshooting. It provides complete FCAPS (fault management,
configuration management, administration, performance management
initiation and collection and security management) functionality from a unified
and centralized GUI.
ENIQ-S collects raw performance data in the form of counters and stores in
the database. It provides post processing tools to generate KPIs and reports
which can be used for performance analysis of network.
OMBS is existent for backup and restore of OSS servers. OMBS enables the
operator to backup, archive, and restore files or directories that reside on the
client system.
3 Product Overview
ENM software is separated into layers with the responsibilities for different
aspects of the system such as mediation, data storage, business processing
and presentation. Each of these layers is separately horizontally scalable and
is based in part on JEE technologies. SW deployment is via the LITP
deployment manager which allows for a unified HW and SW environment.
It also provides open APIs and SDKs to integrate with other 3rd party
tools/applications and to develop customized applications.
The ENM system provides applications with the ability to operate in a highly
available manner, however not all functions require the same level of
availability.
Ericsson Network Manager supports all the functionalities which are supported
through the existing OSS systems along with the new value added features
and functionalities. It brings more value to the customer in terms of capacity as
well as functionality support. Some of the key features supported through
ENM are:
ENM CLI and CM CLI: The ENM CLI is the essential tool for Configuration
Management. It enables the user to perform any and all 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. ENM CLI commands are provided
that can be issued towards cmedit and all other CLI command sets such
as BATCH, ALIAS and HELP.
ENM on Customer Cloud does not support event steaming, Event Based
statistics based on File (EBS-L and EBS-M) and Incident Management.
An NFS service must be included as part of the cloud infrastructure. This can
be either internal (ENM provided) or external (Customer Cloud provided).
Note: The ENM provided Internal NFS, where ENM creates a virtual NFS
service has:
limited capacity,
no scaling
no possibility to integrate to ENIQ Statistics
no possibility of migration to external NFS service
ENIQ integration with ENM requires an NFS share. vENM on Customer Cloud
supports only external NFS shares.
4.1.1 Compute
Over commitment values are indicative only. The product does not support
multiple availability zones to realize these values in a customer cloud so any
overcommit that is applied will affect all ENM VMs.
4.1.2 Storage
Total VMs 73
Block Storage Bandwidth MB/Sec Sum of #VMs per site Total Concurrent Bandwidth MB / Sec
0.2 138 27.6
1 4 4
3 1 3
4 1 4
4.5 1 4.5
5 3 15
(blank) 7 0
Grand Total 155 58.1
4.1.3 Network
(Overcommit 2.7)
(No Overcommit)
Storage [GB]
VM Count
VM Types
RAM (GB)
Persistent
Variant
vCPUs
vCPUs
vNIC
Local
Small
78 137 300 112 682 1644 785.6 2754 156
ENM
VNF LAF requires additional cloud resources which will be estimated post
actual small vENM infra requirement.
Note: The above figures for vENM Cloud Infrastructure requirements are
an estimation and can be changed. Actual figures should be calculated
from the vENM specifications mentioned in section 4.1 & 4.2.
5 vENM SW BoQ
Below vENM SW BoQ is an estimation with similar features existing currently
in OSS-RC. Actual feature list might change when vENM 18A will be GAed.
Lab software for both OSS-RC and ENM is licensed as CTS (Customer Test
System) that follows the same ESM model. Optus can use to test the SW
contained in the BP and VP corresponding to those installed in production
system without having to interfere with the production network. CTS licensed
SW can only be used for non-commercial systems.
These Basic and Optional OSS-RC features are now mapped into the BP and
VP presented in the tables below. The mapping of legacy software (Basic and
Optional features) into the new ESM Base Packages and Value Packages is
presented in section Error: Reference source not found.
The components of BP-Core are presented below. The features marked N/A
are not applicable or not licensed to Optus.
Note: License parameter values related to EPC network have been updated with Y3
EPC expansion values as follows:
- kSAU: from: 7960 to: 8760 increase: 800
- kIP Sessions from: 9485 to: 14420 increase: 4935
ENM functionality is offered and certified in are divided into the following
groups:
By using ENM Network Explorer, it allows the user to find and view all objects
that exist in the network.
Fault Management also provides a M2M interface between ENM and other
NMS. There are two interfaces are supported:
BNSI FM
BNSI is a protocol dedicated to the forwarding of alarm information
from various sources (for example, nodes or southbound EMs) to a
supervisory external NMS. According to the BNSI protocol, alarms are
modelled records which are coded as a sequence of lines with
readable text according to the syntax described in the BNSI protocol
specification.
ENM also provides the ability to receive PM Counter files sent from the
network. The counter files are available for the Report Output Periods
supported by the network elements.
The XML files containing the counters selected in system or user defined
subscriptions are located in designated directories and are available for a
configurable retention period. Notifications are available to the receiving
applications when a file has been stored and is available for consumption.
In ENM 17A, ENM adds the File Lookup Service (FLS) to provide an efficient
look-up service for NMS PM consumers. It enables consumers to fetch the
PM files from the ENM File System efficiently. The FLS can be queried using
various search criteria removing the need to scan the file-system.
SHM function handles what backups are on the network element themselves
as well as what backups are available on ENM for the network elements.
Backup comments are visible in the backup inventory view.
License Administration
Hardware Administration:
Note: Not all network element types are supported by SHM, and the level of
support varies. please refer to the supported NE document for details
ENM Security Management provides basic protection of the key assets of the
network from being subject to malicious internal and external attacks.
Launcher
Log Viewer
Log Viewer is a web-based application that provides easy access to all system
logs via the system platform. It provides advanced search functions to filter the
logs in order to isolate information required for troubleshooting and analysis
activities.
OSS Monitoring
The Network Health Monitor offers support to monitor the performance of the
network continuously in near real-time to determine if there is a fault that has
an impact to the KPIs. For network core nodes, this currently includes FM
states of monitored entities together with their operational states. Network
Health Monitor also provides access to trouble-shooting tools to dig deeper in
order to fix the fault. FMX and Autonomic Incident Management (separate
value pack) further facilitate this process by aiming for an increased level of
automation.
The Network Health Monitor consists of three main parts relevant for core
network nodes:
Monitoring
Health Check
Traffic Analysis
UE Trace
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. A common use case is to compare two reports (e.g. pre and
post-upgrade checks) to get information if crucial system parameters have
deteriorated.
Allows for user control of the workflows to allow for stepwise migration
to full automation
The Cloud Infrastructure details are not included in this solution document.
The figures mentioned in Section 4.4 are just an estimation and need to be
validated for the actual NFVi deployment.
Other Ericsson OSS products not mentioned in this document is not part of
the offer.
Any feature and tool/system that is not explicitly stated in this solution is
out of the scope of this solution.
For virtual ENM on Customer Cloud, the Backup & Restore function is
included as part of vENM on Customer cloud and provides support for
creating backups for ENM configurations and critical data.
9 References
[1] Hardware/Resource Analysis Report ENM, 1/177 63-4/FCP 130 2584
Uen Rev PC10.