Slides ServiceOn Element Manager

ServiceOn Element
Manager R16 for

Optical and Microwave
Network Operation
Introduction to ServiceOn Element Manager

Objectives
1 Identify the role of SOEM
2 Describe the main resources
3 Identify communication parameters
© Ericsson AB 2017 | Introduction to ServiceOn Element Manager | LZU1082305 R2A | Figure 1-2
TMN Structure
Business Management Layer
Network and Service Layer IPT NMS
Element Manager Layer ServiceOn Element Manager

NetOP
Media: microwave , opto

Network Element Layer Traffic: Ethernet, TDM, WDWM, IP
Ericsson Broadband NW
OSS Products
Customers’ OSS framework
IPTNMS NBIs
ENIQ
IPTNMS
Framework
Circuit Packet
Proprietary Proprietary
Interface Interface SOAP/HTTP
ServiceOn Element Manager NetOP
MHL EDA 3PP MW OMS SPO SE SSR

BROADBAND
CORE AGGREGATION IP EDGE
ACCESS
FCAPS systems
Configuration Performance
Fault Administration Security
ServiceOn Element Manager
› ServiceOn Element Manager covers the EM layer for

Ericsson’s SDH/DWDM/Radio and Packet transport
networks
› Allow remote control of the managed NEs
› Enable the operator to:
– Retrieve data from all Network Elements (NEs)
– Apply commands to all NEs
– Manage all the NEs’ alarms
– Manage the NEs’ Database (DB) backup/restore
– Download new software towards all NEs
ServiceOn EM NBI
3rd Party
NM
TMF
PIC PPM PFM
814
ServiceOn Element Manager
Notes page
› The content of this page is not seen in the presentation.
EM NBI: PFM
› Practical Fault Management – TCP/IP
› Uses the TCP/IP NBI for export of Fault Management
› Bi-directional interface providing a real time alarm feeding
› Main functionalities supported by the interface:
– From higher level management tool
› Acquisition of the alarm catalogue
› Commands to acknowledge or Clear alarms
› Commands defining the Filter settings
› Requests for synchronization PFM
EM NBI: PFM
› Functionality supported by the interface (continue..):
– From SO-EM to higher level management tool
› Synchronization notification
› Alarm details
› Element Level Alarms and Notification
› Core Element Manager Notifications
EM NBI: PFM-SNMP
› Uses the SNMP NBI for export of Fault Management

› Used for exporting alarms and NE configuration data to
other management tools.
› Compliant to SNMP v2c and a proprietary MIB SMIv2
conformant.
› Information is propagated as SNMP traps to:
– Notification about New/Ceased, acknowledged and deleted alarms
– Notification when NE’s are created/deleted or changed
– Notification about system Events generated in the SO-EM Server
EM NBI: PPM
› Practical Performance Management

› Uses the FTP NBI to export the PM values
› Supported functions by the interface are:
– From Higher level management tools
› Requests for Performance Data Formats
– From SO-EM to Higher level systems tools
› 15 minutes records (Collected and Current)
› 24 hour records (Collected and Current) PPM
› Details of the Performance Data format
EM NBI: PPM-FTP
› FTP Export for PM Data

› Applicable to PM data collected from MINI-LINK NEs
› The export creates one file for each PM standard.
› The output can be in comma separated text files and/or in
XML format.
› The export functionality is available and can be scheduled
via SO-EM GUI.
EM NBI: PIC
› Practical Inventory and Configuration

data
› Uses the FTP to export of Inventory
Management
› Provides access to the XML format of
the inventory data files
PIC
› The XML files are generated in
predefined directories and are
transferred via FTP
EM NBI: PIC-FTP
› FTP Export Interface for Inventory and Configuration Data

› Uses the FTP to export Inventory and/or Configuration
Data for MINI-LINK NEs
› The exports are formatted in either comma-separated text
files or in XML
› The export functionality is available and can be scheduled
via SO-EM GUI.
EM NBI: TMF 814
› TMF 814 (TeleManagement Forum)

› Based on standard CORBA services
› Provides the support to integrate the EM with a 3PP NM system,
managing NE inventory, configuration, alarms, performances
› Allows the integration between the IPT NMS and a customer’s
surveillance system, allowing
– Configuration management
› Inventory, MSP/MS-SPRing, topological links, cross connections
– Fault management
– Performance management
Hardware Resources
› SO EM requires x86 server architecture
› Allows co-location on the same host
› Need an TCP/IP DCN network for server-server, client-server, server-
network element communications
› One or more PC for client connection
IPTNMS
SO EM IP IP
PDH/SDH/ IP PDH/SDH/
DWDM/Packet NetOP Router DWDM/Packet
SO EM
Network Network
Packet
Network
Main Resources
› Hardware resources in a managed network:

– SOEM server running the EM application
– PCs for the operator access
– DCN connecting the resources together
Client PC
SOEM
MW
SDH DCN DCN DCN

DWDM
POTP Router POTP MW
SDH Eth MW
EM Architecture
› Hardware platform: HP Proliant G x86 based servers
› Operating System: SUSE 11 SP4
› Implementation of OSI protocol: Linux Xelas package
› IP BroadBand NMS base package:
› Ingres DBMS
› MySQL Enterprise Edition (PM data storage)
› MiCo (Corba implmentation)
› LiMa
› Wind/U Libraries 4.4/5.0/6.0 (for Windows SW porting)
› Java RTE 1.7
› SOEM Core application
› NE Plug-in in packages for EM
Client PC configuration
› The EM client is a Java-based application

› Supported software level on the client PC:
– Windows® 10 and Windows® 8
– Java RTE 7
› update 141 (*)
– Internet Explorer 9 and 11 or Firefox 52.1.1 Extended Support Release
› The operator connects to an https-based portal on the EM host
› The relevant applications are dynamically downloaded to the PC as
Java applications
(*) for the correct java version please refer to the latest Application Basic SW List document.
SOEM Main Modules
› Database Server Processes (DSP)

– Core EM functionalities
– One host only per SOEM installation
› Communication Server Processes (CSP)
– EM to Network Elements communcation management
– One ore more hosts per SOEM installation
› Performance Monitoring Database (EMPM or PM DB)
– Manage and store performance data
– One host only per SOEM installation
EM Performance Manager
› EMPM is the performance management module in the EM

architecture
› A dedicated server and database for PM management
› Can be co-located on the EM host
EMPM NE Performance samples SDH PDH

ADM Radio
EMPM Queries
SO EM OADM IP-STP
SOEM Installation Scenarios
› Co-location of IPTNMS and Element Manager on the same host

– Cost saving option
– Less scalable in case of network expansion
› Distributed installation of the NM/EM applications
› Multi-server installation of the SO EM
IPTNMS
SDH
ADM Network SO EM
Elements
SO EM DSP/CSP Network
CSP
Elements
PDH
Radio
SO EM
Network
Elements
SO EM
IP-STP CSP
OADM
Supported Server
Configurations
› Standalone with PM in co-located server (DSP, CSP and
EMPM)
– One platform supports all the EM services
› Standalone and PM dedicated server
– One host runs the EM services while the PM services run in a
separate platform
› Multi Server
– One host runs the DSP
– Additional CSPs (up to eleven) to expand the number of managed
NEs
– EMPM database can be co-located with the DSP
EM-NE Communication
Parameters
› Seamless communication to the NEs
› Appropriate protocol stack is automatically selected by the EM plug-in
› Supported protocols:
– OSI connection
– TCP/IP connection (and RFC1006)
– QD2 connection
SOEM GUI
SOEM
OSI
OSI TCP/IP QD2
NEs NEs NEs
ServiceOn Element
Manager R16 for
Network Operation
The Element Manager User Interface

Objectives
1 Describe how to access the SOEM GUI
2 Identify the GUI areas
3 Be familiar to the main commands
Graphical User Interface
› The EM client runs on the operator’s PC

› All the operations are run on the host
› The graphical output is generated on the local PC
Thick Client
Thin Client
SO EM
RDS
Accessing the EM
› Open the browser and type the address:

– https://<DSP server name/address>:30305
Notes page
EM Clients Installation
› Click on EM Installation
› Select the EM client to install on the client PC
– For MINI-LINK install MINIK-LINK Craft
Password Change
› Changes OS and EM
password for the user
› Before logging in
› Click on Change Password
› Enter current and new
password
Graphical User Interface
Layout controls Help Menu EM message box
Network
events
Operator’s
commands
View bar Network Network Network element

tree map data
Help Menu
› Help On Line function for

SOEM and for the installed
Plug-ins
› In “about Service on EM tab”

there is information about the
core system and the plug ins.
Help Menu
› Display the installed licenses for the SOEM application
EM Message box
› One way communication

from the EM to the user
› Details about:
– EM-core/EM Plug-in stop/start
– Scheduled jobs
Views Bar
› Provides access to the

main EM functionalities
› Each item is a network
operation area
› Click on the option to show
the relevant interface
Network Tree
› Provides an hierarchical
network view
› “Network” is the root of the
tree structure
› Allows easy navigation
› EM commands can be
applied from the Tree
› Nodes and subnetworks
can be dragged to the map
Find a Node
› Retrieves a node in the EM

› Enter the node
name/acronym
› Click on to find the node
› The node found will be
automatically selected
› Advanced search allows
further filtering:
– Acronym/Network address
– Ne type
Network Map
› Provides geographical
reference for nodes icons
› Different zoom levels
› Zoom management:
– Mouse wheel to zoom in or
out
– Double-click on the map to
zoom-in
– Double click with right mouse
button to zoom-out
– Zoom control widget on the
map
Network Data List
› Provides the details about the nodes selected on the

network tree
› EM functions can be directly applied from the list
› Multiple selection allowed
› Allows import and export of NE details
Selecting Nodes
› Node selection depends on the

selected View
› In the Tree section select the
subnetwork(s)
› Click on Network and select one
or more subnetworks
› Click on Network Elements
› Select one or more NEs
› The selected nodes are now
available as target nodes for the
selected application
Commands and Events
› Information: displays the
operations being performed
Show/hide all also by other EM users and
› My Commands: displays
the results of the
Filter data commands issued by the
user
› The pushbuttons on top
toggle show/hide the
relevant window
Other GUI Controls
Toggle map view Show

Help on Line
Show/hide Show Network Data
Network Tree only
Show Show Network map
Map & Network Data only
Hide/show
View bar
Hide/show
Commands and Events
Add and move nodes
› Drag and drop on map

› Single NE icon
› Whole subnetwork
› Node not on map:
› Node already on map:
› Shift + drag and drop allow node icon repositioning on map

› Drag and drop to move icons between subnetworks
Node Screen Tip
› Move the pointer over the

node
› The EM displays the overall
information about the node
GUI Messages
› The GUI provides messages and warnings

› A placeholder is located at the bottom right corner of the
GUI window
› Click on the icon to show the messages
Features Availability
› The GUI provides access according to the installed license

› Those features not included in the license file will be locked
Unlocked feature Locked feature
ServiceOn Element
Manager R16 for
Network Operation
First network commissioning

Objectives
1 Configure subnetworks
2 Install network elements
3 Identify communication parameters
Subnetwork Workflow
› Subnetworks are logical areas

› Used for network partitioning over different working areas
› Network is the default network tree root
› Network can host subnetworks only
› Network elements can only be installed in a subnetwork
Add Subnetwork
› To add a subnetwork:
– In the Network Tree, right click on “network” or a Subnetwork
– Select Add Subnetwork
– Fill in the Add Subnetwork window fields then confirm
Network Elements
Management
SOEM allows the node installation in different ways:
1. Manual installation, using the Network Data List menu

2. Manual Auto Discover
3. Automatic Auto Discover
4. Semi Automatic Auto Discover
› The capability to support the manual and/or automatic way

is based on the plug-in type.
Manual NE Installation
› Network Elements will be manually
Start
added to the EM; relevant icons will
be displayed in the Network tree and
Create a the map
NE manually › The following operations modify the
the EM Database and the GUI
Manage
the NE
End
Create NE
› Purpose: this operation add a new
Start Network Element information in the EM
Database only.
› Operation: in the Network data area click
on Create NE pushbutton ( )
Create a
› Action: fill in the Create NE window fields
NE manually defining the Name, the Acronym, the
Suffix, the Type, the Address and other
Manage optional information
the NE
End
Create NE Window
› Fill in the General tab:

– Name, Acronym, Suffix and
Type are mandatory
› Protocol tab: enter the node
network address
› Other values in remaining
tabs are optional
Notes page
Enable the NE Management
› In NE Data List, select Show Unmanaged

› Select the destination subnetwork
› Right click on the node name and click on Manage
Network Autodiscovery
› There are three ways to discover NEs connected

to the network:
– Manual Network Discovery, used to run a one-shot
network discovery
– Automatic Network Discovery, used to enable a
continuous network discovery
– Semi-automatic Network Discovery, used to enable a
continuous network discovery over some selected IP
ranges
› Network discovery is available according to the
plug-in type
Manual Autodiscovery
› Purpose: this option will open up the
Start
Autodiscovery GUI and make it
possible to add a NE automatically
Auto › Action: click on Autodiscovery in the
discovery Edit dropdown window or click this
Icon
Set
Parameters
Configure
NE
End
› Purpose: this option defines the
Start
discovery parameters
› Action: select
Auto – EM Plugin(s)
Discovery – IP addresses
– SNMP details (optional, defaults provided)
Set
Parameters
Configure
NE
End
Notes page
› Purpose: discovered nodes can be
Start
added to the EM database and, then,
managed
Auto › Action:
Discovery – select the node(s) from the list
– Select the destination subnetwork
– Click on Add
Set
Parameters › Note: By default the EM selects the
subnetwork Autodiscovery. If it
Configure doesn’t exists it will be automatically
NE created.
End
Autodiscovery view
Type of discovery
Protocol details
NE type and
address selection
Discovered NEs
Automatic Network Discovery
› Automatic Network Discovery activities allows the

execution of a Network Discovery task at a time interval
› The job is automatically created at the installation of each
plug-in supporting the feature
› The first time the job is created the user must modify some
mandatory fields (IP address list, community..) before
starting it
Automatic Discovery:
parameters
Address
Scheduling and
details
Login
Semi-automatic Discovery
› Combines the best of manual and automatic discovery

› It is an ongoing discovery process only for some selected
IP address
› It needs a configuration file in the CSV format
› Once the node is detected it is automatically added to the
management system
› Compared to the other discovery mechanisms requires
less system resources and less operator’s effort
Semi-automatic Discovery
Modify NE Default Values
Checking the NE’s
› Applicable from the Network view or the Network Tree

› The operator can verify and setup the state of a NE
– Check the EM to NE communications

– Set the EM access rights
– NE date/time alignment
– Modify NE details
EM-NE Communication
To verify the EM-NE communication at
network protocol level:
› On the Network Tree, right click on the
node
› Select Ping from the menu
› The EM will automatically initiate the
appropriate ping session, regardless
the network protocol
› Results are displayed in the
Commands area
EM-NE Communication (2)
› The operator can control the communication processes to

the specific NE
› On the Network Tree, right click on the node
› Select Comms from the menu
› Three options available:

– Start, to initiate communications
– Stop, to terminate communications
– Restart, to start over the
communication process
Set EM Access Rights
› Right click on the node
› Select Access NE from the menu
› Read/write will prevent
configuration changes from the
LCT users
› Read Only will release the write
access to the LCT
› Read Only mode prevents SOEM
and upper layer OSS to perform
any change to the NE
configuration
NE Date/Time Alignment
› Align the NE date and time

with the SOEM DSP host
› On the Network Tree right
click on the NE icon,
DCN
› Select Broadcast Time
› Adjust the delay
› The NE timestamp in
NE NE NE reports is now aligned to
the EM date and time
Modify NE Details
› Allow changing some of the NE parameters
› On the Network Tree right click on the NE, Select Details
› It is possible to modify all the NE parameters (except the NE Type)
Default LCT/CLI Action
Click on the gearwheel icon
› User preferences allow

selecting the default action
› Users can individually
select between LCT and
CLI
› Selection according to NE
type
ServiceOn Element
Manager R16 for
Network Operation
Alarm Management
Objectives
1 Work with active network alarms
2 Display Events
3 Use the history tools
Fault Management view
› SOEM provides powerful tools to manage faults and events

for the managed Network Elements:
› Alarms - Manages the active alarms received by the nodes
› Events - Manages the active alarms and events from equipment and system
› Historical Alarms – Query the alarms archive
› Historical Events – Query the events archive
Detach Fault View
› By selecting the Fault view, the four display tabs are

available.
› Select the icon to detach the alarm window in a
separate one
› Fault in the Side Bar, the Detach action is available:
› A new window with the Fault view opens, which is

independent from Service on EM Main Window.
Alarm States
› Alarms are reported in:
– Network view through icons color
– Alarm view though detailed alarm message
– Historical alarms view through detailed alarm messages

and full alarm lifecycle
NE Icon
› Each NE icon layout provides two levels of information

› The inner icon border color reflects the current alarm or
communication state
› The icon border denotes the alarm acknowledgment state
Inner border represents

current alarm or Outer icon border:
communication state current alarm
acknowledgement
Alarm colors on NE Icon
Inner border colors Outer border colors
Color NE State Color Alarm
Magenta Alarm overflow
acknowledgment
Red Critical alarm

Red Critical alarms not
ack’d
Orange Major alarm
Orange Major alarms not ack’d
Yellow Minor alarm
Yellow Minor alarms not ack’d
Blue Warning
Green No active alarms Blue Warnings not ack’d
Sea green NE in parking state Green All alarms ack’d
Grey Loss of NE communications
Brown NE plug-in not running

Dark
NE plug-in removed
brown
Black NE management stopped
White Virtual NE
SUB NW Icon Colors
› The color of a subnetwork icon depends on the colors of the NEs in the
subnetwork itself
› Subnetwork icons do not have an acknowledgement state
› The EM GUI will show the most critical alarm state according to the
following priority:
Color State Priority Color State Priority

Magenta Discarding 1 Sea green Parking 7
Red Critical 2 Gray Disconnected 8
Orange Major 3 Brown Plug-in stopped 9
Yellow Minor 4 Black NE stopped 10
Blue Warning 5 White Virtual 11
Green No alarms 6 Dark brown Plug-in removed 12
Alarms view: Real time fault
management
Alarm management
toolbar
Node-level
filtering
Alarm filtering
criteria
Alarm
list
Alarm View
counters preferences
Alarms view: Main information
› Alarm: type of alarm

› ID: alarm ID assigned by SOEM
› State: current alarm state
› Severity: alarm severity
› Probable cause: what potentially have caused the alarm
› Raising time: timestamp in the alarm message from the NE
› Promoting time: timestamp of the EM alarm acceptance
› Different physical/logical details on alarm source
Colors in the Alarm View
› Alarm strings are displayed with the appropriate colors
according to the severity and the state of the alarm
– Red critical (urgent) alarms
– Orange major alarms
– Yellow minor alarms
– Blue warning (indicative) alarms
– Grey selected alarms
› Acknowledged alarms are marked with a check symbol on

the relevant row
Colors in Event View
› All event strings are displayed with grey
Alarm Counters
› At the bottom of the alarm list window a set of counters

summarizes the number of current alarms of each severity.
› The counters show the total number of alarms (per
severity) and the number of acknowledged alarms:
Alarm Warning
› Can be used to view the warnings on the network elements

listed in the active alarm view. On placing the mouse on
the icon, a pop-up menu is displayed with the list of
available warnings.
Alarm view: Filtering
› Advanced tool to focus on specific alarms
› Allows creation of filter templates and default filters
Filter template toolbar
Alarm view : Toolbar
Acknowledge Clear
selected alarms selected alarms
Export selected
alarms
Alarm realignment
Export all
Alarm forced alarms in the view
realignment Acknowledge Clear alarm list
alarm list
› Quick access to alarm management functions

› Node alarm realignment
› Operations on selected alarms or the whole view
Notes page
All NE Selected
› The following icon gives the indication that the entire

network is selected and, as a consequence, all NE’s
alarms are displayed:
› Not all NE’s selected:
Alarms Realignment
› Realign the NE active alarms in the EM with the active

alarms database in the NE
› Two realignment modes:

– Normal: only the missing alarms are stored in the EM
– Forced: all the NE are cleared in the EM and the whole NE alarm list
is imported as new raised alarms
Automatic Alarm
Synchronization
› A logical flag
› On: the EM automatically realign alarms upon NE
(re)connection
› Off: alarm realignment is not automatic and requires an
operator’s command
Working on Alarms
› Right-click on one or more alarms

› Details: popup with all the alarm details
› Acknowledge: the operator is aware of
the fault
› Delete: fault is removed from SOEM
Alarms view
› Export: alarm data are stored in a file
› Send to Server: alarm data are stored
in the EM ticket directory
› Open LCT/Open CLI: start the relevant
application for the node
Sparkling Alarms
› Sparkling alarms are also known as intermittent alarms
› It is constantly fluctuating between the “ON” and “OFF” states generating
useless alarm information
› The system administrator can define a set of values to filter alarms in order to
– Prevent overflow
– Clean RTAM
– Easier to troubleshoot
› Those alarms matching the filtering criteria are automatically categorized as
”Sparkling”
› Alarm states:
– Sparkling On
– Sparkling On+Ack
– Sparkling Off
EM Alarm Overflow
OVERFLOW
› The EM has exceeded the maximum number of alarms supported by

the system
› This state triggers a set of automatic actions
› Default activation threshold: 20000 active alarms
› Affected NEs are displayed in magenta
A new alarm has been
raised…
› Check the alarm details
› Verify the equipment alarm guide in the relevant CPI
› Acknowledge the alarm
› Check the NE events
› Open the LCT/CLI and try to fix/isolate the trouble
Alarm Transition States
OFF
ON ON&ACK OFF
OFF&ACK - DELETE
OFF
ON ON&ACK OFF
OFF&ACK - DELETE
Notes page
Events View
› A report of the network events

› Two main events category:
– NE event (e.g. NE Link up, Protection switching, alarm realignment)
– SOEM event (e.g. NE plug-in start/stop, EM core start/stop)
Historical Alarms
› A powerful tool to query the alarm log

› Display the alarm details matching a specific filter
› Allows data export
Historical Events
› A powerful query tool for NE and EM events
› Operators can focus on specific event types
ServiceOn Element
Manager R16 for
Network Operation
Performance management
Objectives
1 Describe the performance handling
2 Manage the performance activities
3 Handle the performance reports
Performance Management
› Collection and storage of PM data in 15m and 24h intervals

– 15m intervals will be received at every quarter of an hour
– 24h interval data will be retrieved on a daily basis
› EMPM is the EM module dedicated to the performance
management
› Service on EM can generate a number of performance
reports by means of performance activities
Performance Management
› Report Tools for data presentation are available, via PM

viewer applications:
– Historical Viewer
– Near Real Time Viewer
› Performance collection counters must be enabled in
advanced on the target entities in the NE
Opto
Micro Micro
wave wave
Opto
Standards and intervals
› Performance data are defined according to ITU-T Rec.

G.784 and G.826, G.821, G.828, G.829, EN 301 129,
RMON, Y1731
– Example: E1 Performance is included in the G.826 standard
› Performance collection intervals are hardware dependent
– Example: MLE performance is only 24h
Performance Data Collection
Node
Operator D
DCN
Node Node
A E
SOEM
Export Node
C
XML file
Text file
EMPM
Collecting 24h Performance
Data
› Performance data are collected throughout the day
› 24h sample available after midnight
› Sample incomplete on the very first activation
› Example:
– Day 1: start 24h PM counters, day 1 PM sample incomplete
– Day 2: collecting data, day 2 PM sample complete
– Day 3: collecting data, day 2 PM sample available
Collecting 15m Performance
data
› Service On EM polls the NE every 15 minutes for
performance data
› The NE provides the last available sample along with the
sampling results
SOEM
Opto
Micro Micro
wave wave
Opto
Collect performance data:
workflow
3. PM activity 4. First batch

activation time of data
1. Scheduling
1345
0000
13 001500
13 00
1300
30
2. Start/Stop activity
5. Second batch
of data
Preliminary Setup
› Access the NE via CLI/LCT Zoom-in

› Enable the PM counters of the port to monitor
› Check EM read/write access
Make sure the EM-NE

date/time is aligned
Performance Scheduling View
Shelf Card and slot Monitored
selection selection entity
Plug-in
selection
Node(s)
selection Scheduling
details
24 h PM Activities
› Upon NE installation
SOEM automatically
creates 24h PM activities
for all entities
› These activities are
created in SUSPENDED
state
› The functionality is
available for a subset of
plug-ins
Activities view
› This view controls the start/stop operations on PM jobs
› It is made of 4 areas:
– Activities management: start/stop of single PM jobs
– Filters: filter setup for the list of activities
– Template management: node type level enable/disable monitoring for a
specific entity
– PM Start/Stop: NE-level start/stop of PM
PM ACTIVITY States
– Running: the job is being executed
– Waiting; the job is set for execution but the start date/time is not arrived yet
– Suspended: the job is not set for execution
– Expired: the job has been executed and the finish date/time has arrived
PM Activities Management
Select a job
Check
monitored
entities
Manage
entities
PM Management
› Template Management
– Control the default PM jobs
– Based on node types
› PM Start/Stop
– PM jobs related to the node
will be activated or
suspended
Historical viewer
› Displays the performance data collected through the

scheduled jobs
› According to the selected nodes and entities it displays the
available data
SOEM
PM Historical Viewer: Select
Type Referral
of node standard
Node(s) Entities currently Performance

selection Entity monitored counters
Types to display
Historical Viewer: Basic
filtering
› Simple filtering of PM data based on Time
› Configuration of the query output:
– Sorting
– Paging
– Chart type
Historical Viewer: Advanced
filtering
› Allows filtering on specific PM data criteria
› Only the matching records shall be included in the view
PM Historical Viewer: Viewer
› Displays available performance data according to selection

and filtering
› Two tabs available for 15m and 24h
› Time controls allows paging among performance samples
› Data can be exported in XML or CSV
PM Historical Viewer: Chart
› Data in the Viewer tab can be displayed in a graphical format

› Chart displays a line or bar chart
› An automatic key is generated near the chart to identify the color
coding and the corresponding counter
› The chart can be adjusted in resolution and exported as an image
PM Near Real Time
› Available for specific node types (e.g. MINI-LINK)

› Real-time monitoring of PM data or counters
› Near Real Time tool works as the Historical viewer
› Viewer continuously polls the NE for performance data
› Minimum polling time is 30 seconds
› Viewer automatically shows and chart the collected records
PM Near Real Time Viewer
› In the Select area define:

– the target node
– the measure point
– the counters
PM Near Real Time Viewer
(2)
› Select the polling interval
› Adjust the Chart properties
› Click on Start
PM FTP Export
› This option is available only for a subset of plug-ins

› EM setup for exporting PM data by means of FTP NBI
› From Performance - FTP Export
ServiceOn Element
Manager R16 for
Network Operation
Handling software upgrade

Objectives
1 Load Software to repository
2 Download software to NE
3 Activate Software
Remote Software Upgrade
› Software management is under Software Upgrade view

› Upload the software bundle to the EM host
› Schedule the download of the software to the NE units
› Activation can be done from SOEM
Operator
2 DOWNLOAD
1 LOAD
EM 3 ACTIVATE NE
(bank switch
and commit)
Load software to repository
› Upload the node software package to the EM DSP host

› Software package must be stored in the client PC
› Select Repository tab
› Define the target EM plug-in and node type
› Software repository can host up to 3 different software
versions per node type
Repository View
Node family
selection
Node type
selection
Local path
to software
Repository
Repository View
Repository View
Maximum three
Software versions
per node type
When three SW versions

are uploaded ,
it is possible to
select the one to replace
Scheduling
› The operator can plan the software download to the NEs

› Select the Target NEs and the software package to
download
› The software download job delivers the software package
in the standby/inactive software bank
Scheduling View
Hardware
selection
Node(s)
selection Software
package
Scheduling
details
Activities View
› Provides the list of ongoing software download activities
› Each row describes a single activity
› Click on the activity row to get details
› Right click to Abort the activity
Activate
› The operator manually activates the downloaded software

› The new package is activated and validated
ServiceOn Element
Manager R16 for
Network Operation
Retrieving data from Network Elements

Objectives
1 Retrieve and display inventory data
2 Retrieve and display configuration data
3 Analyze inventory and configuration

differenses
Inventory View
SOEM
› Allows scheduling and
collection of inventory data
› Node Inventory
› Equipment inventory
› Inventory tools for MINI-LINK
and SP nodes
Micro
wave
› Collection of network element Micro

wave
Opto
configuration data
Opto
Inventory Activities
Activity Type Network or Network Element
Node selection
area Activity scheduling
details
Activity list
Results for the

selected activies
Nodes involved
in the selected
activies
Equipment Activities
› Setup and scheduling of

equipment data collection
› Collected inventory data are:
– Slot
– Card type
› Equipment data are stored in
individual files for each node
› The repository is the EM DSP
host
› File format is XML
Configuration Data Inventory
› Allows display of inventory data for the selected nodes.
Applicable for optical nodes
Configuration Data Equipment
› Allows display of inventory and equipment data for the
selected nodes. Applicable for optical nodes
Inf & Conf Viewer
› Inf&Conf Viewer tab allows access to tools specific for

MINI-LINK and SP nodes
› From the Inv&Conf Viewer tab it is possible to display the

Inventory viewer, the Configuration viewer, and the
Inventory log viewer applications
› The inventory viewer displays location, type and revision

state of hardware and software modules
Physical Inventory Viewer
Export button
Tree Hardware
View details
of Resources
Software
details
Inventory Differences
› All the changes of a resource occurring during the following activities
are automatically recorded:
– Added Network Elements
– Removed Network Elements
– Network Elements that have

changes in inventory respect
to the previous collection
Configuration Viewer
Export button
Configuration
Details
Configuration Differences
› The tree displays added or removed equipment and if
Configuration data has changed
Inventory Log Viewer
› Display the log about the job status
› Click on Log Viewer to start the user interface
› The report shows:
– NE name and NE id (SOEM assigned id)
– Type of Activity (Log Type)
– Date and result
PIC FTP Export
› Allows exporting the collected Inventory data by means of the FTP NBI
› Select the NEs and the type of data being exported
› Enter the FTP connection parameters
› Select the export data format and scheduling
ServiceOn Element
Manager R16 for
Network Operation
Network Element configuration

Objectives
1 Schedule the NE configuration backup
2 Understand Hardware Upgrade
3 Execute Bulk CLI
NE Database backup/restore
› Centralized NE database backup

› Remote database restore
› Database backup includes shelf configuration, traffic setup,
cross-connections, lines and traffic protections
EM NE
NE Database Backup
Activity
scheduling
details Activity
list
NE activity
compliance
NEs in
selected
activity
Network Level Backup
› In the Network Tree select the whole Network or a

Subnetwork
› The Activity Type will be changed to “Network”
› The activity includes ALL Network elements in the Sub NW
even if they are added to the Sub NW after creation of the
activity
› The backup of a Subnetwork can be scheduled to recur
weekly or daily
Single/Multiple NW Element
Backup
› In the Network Tree select the one or more NE’s

› The Activity Type in Schedule Collection will be changed to
Network element
› If new NE’s are added to the system a new backup activity
must be created
› The backup activity can be scheduled to recur daily
NE Database Restore
› Remote database restore for the selected NE

› EM GUI displays the database backup available for the
selected node
› DCN connectivity required
Hardware Upgrade
› The upgrade changes automatically the NE Type of the

node keeping the same IP address in Service On EM
AMM 6pD
AMM 2p
Hardware Upgrade
CLI Scripts
Start › SOEM provides CLI scripts

management and execution
Load › CLI scripts are managed in
the view Configuration →
Scheduling CLI Scripts
› Scripts are checked against
View
activities
a commands blacklist
View logs
End
Create CLI Script
› Use notepad to create the CLI scripts.

› Can be several in the same file.
› One script per row
› Save it as a .txt file
Scripts Repository
Start › Upload and manage the

CLI scripts in the EM
Load script server host
Scheduling
View
activities
View logs
End
CLI Repository
Node selection Add a new script
area
Available scripts
Scheduling CLI scripts
Start › Schedule tab allows the

planning of script execution
Load script › Select:
– Target NEs
Scheduling – The CLI script
– Timeframe and recurrence
View
activities
View logs
End
CLI Schedule
Available scripts
Node type
Schedulle
Network Element
View Current Activities
Start › The Activities tab shows the list

of scheduled activities
› Two activity states:
Load script
– Waiting: it is not yet the activation
date/time
– Running: the activity is being
Scheduling
executed
› Right click and select Abort to
View
activities terminate the activity
View logs
End
CLI Activities
Execution Log
Start › Execution Logs summarize the

results of scripts execution
› Display the details about job
Load script
execution
Scheduling
View
activities
View logs
End
Execution Log
Result status
Script outcom
ServiceOn Element
Manager R16 for
Network Operation
License Management
Objectives
1 Display the SOEM licenses
2 Retrieve NE license information
3 Install NE license files
License View
› Check the license installed in the server and on the

controlled NEs
› Schedule a license collection job
› Create the new license request file (LRF) for specific NEs
› Install in the NE the obtained license file
License Activities View
Verifying the EM Licenses
› Element Manager Licenses

provides details about the
licensed EM features
› EM operations might be
limited in case of:
– Expired or missing license
– Max license capacity reached
Service On EM Licenses
NE Licenses Overview
› Display license details for the selected nodes

› Fingerprint value is the key for ordering and installing new
licenses
License management
› On specific NEs license can be unlocked at any time

› A grace period allows unlocking all the supported features
› This is intended as an emergency workaround
› A valid license must be installed
› When the grace period expires the node will be locked
Creating a License Request
File
› Help the operator in creating the proper file for license
request
› From the Network Element Licenses tab
› For each node/feature click in Qty to order
› Enter the required number
› Click on License Request File Creation
› The file is created in the local client PC
Creating a License request File
› The file is created in the local client PC
Creating a License RF
bulk creation
Click on Create License Request
Select wanted NE’s
Installing NE License Files
› Store license file(s) on the client PC

› Select the target node
› Click on Upload LKF and select the compressed license file
› Click on Install

Slides ServiceOn Element Manager

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Slides ServiceOn Element Manager

Încărcat de

Drepturi de autor:

Formate disponibile

ServiceOn Element

Manager R16 for

Introduction to ServiceOn Element Manager

1 Identify the role of SOEM

2 Describe the main resources

3 Identify communication parameters

Business Management Layer

Network and Service Layer IPT NMS

Element Manager Layer ServiceOn Element Manager

Media: microwave , opto

ServiceOn Element Manager NetOP

MHL EDA 3PP MW OMS SPO SE SSR

Fault Administration Security

› ServiceOn Element Manager covers the EM layer for

ServiceOn Element Manager

› The content of this page is not seen in the presentation.

› Uses the SNMP NBI for export of Fault Management

› Practical Performance Management

› FTP Export for PM Data

› Practical Inventory and Configuration

› FTP Export Interface for Inventory and Configuration Data

› TMF 814 (TeleManagement Forum)

› Hardware resources in a managed network:

SDH DCN DCN DCN

› The EM client is a Java-based application

› Database Server Processes (DSP)

› EMPM is the performance management module in the EM

EMPM NE Performance samples SDH PDH

› Co-location of IPTNMS and Element Manager on the same host

The Element Manager User Interface

1 Describe how to access the SOEM GUI

2 Identify the GUI areas

3 Be familiar to the main commands

› The EM client runs on the operator’s PC

› Open the browser and type the address:

› The content of this page is not seen in the presentation.

View bar Network Network Network element

› Help On Line function for

› In “about Service on EM tab”

› Display the installed licenses for the SOEM application

› One way communication

› Provides access to the

› Retrieves a node in the EM

› Provides the details about the nodes selected on the

› Node selection depends on the

Toggle map view Show

› Drag and drop on map

› Node already on map:

› Shift + drag and drop allow node icon repositioning on map

› Move the pointer over the

› The GUI provides messages and warnings

› The GUI provides access according to the installed license

Unlocked feature Locked feature

First network commissioning

2 Install network elements

3 Identify communication parameters

› Subnetworks are logical areas

SOEM allows the node installation in different ways:

1. Manual installation, using the Network Data List menu

› The capability to support the manual and/or automatic way

› Fill in the General tab:

› The content of this page is not seen in the presentation.

› In NE Data List, select Show Unmanaged

› There are three ways to discover NEs connected