OMS Training

Operation and Management Server (OMS) in
WCDMA RAN
In NSN
te
rn
al
!
Customer confidential
1 © Nokia Siemens Networks
RNC OMS Architecture
RNC Operation and Management Server (OMS)
Operation and Management Server (OMS) is a Linux OS based

management server in RNC, which is connected to the
Telecommunications Management Network of WCDMA.
OMS provides O&M data mediation, concentration and aggregation

functionality in 3G WCDMA RAN and in RNC.
RU
OMS is used for local, RNC-level changes that are made for one 2
be 0RNCa
at
fo nd to
a time and for mediation in NetAct originated changes that are targeted
managed objects under the control of the RNC. re
NetAct Framework is used for network-level changes, targeted to several

RNCs.
RNC OMS Unit, e.g. in RN5.0 / RNC2600 Solution
RU20/RN5.0 RNC OMS supports two HW

variants:
•Integrated OMS HW (MCP18-B)
•Standalone OMS HW
(HP Proliant, recommended)
RNC OMS HW Platform
The RN5.0 introduces the new standalone OMS HW. This OMS variant uses the commercial IT server HW:
HP DL360 Proliant.
• The new standalone RNC OMS HW comes with:
HP Proliant DL360 Generation 6 of
• Quad core Nehalem Intel processors
• Min 8 GB memory (scalable up to 128 GB)
• Mirrored hard discs (from 2 up to 6 x 146GB HDD)
• Dual port network card(100 Mbit/1Gbit)
• SCSI card for external devices like data tapes and magneto-optical
• Optional IP Sec extension
• USB 2.0 ports
• Height 1U
• The Integrated RNC OMS, old legacy HW comes with:

• MCP18-B B01 plug-in unit of
• Intel Dothan 1.8 GHz
• Single core processor
• Max 4GB memory
• 2 SCSI disks of either 73GB or 146GB (only in RN5.0)
• Dual port network card(10/100Mbit)
RNC OMS SW Platform
RU20/RN5.0 RNC OMS application SW is

based on NSN Flexiplatform that provides:
• EM, SW Mgmt & Commissioning support

• Basic O&M and messaging services
• Base platform services with OS &
HW adaptation
RNC OMS Operating System (OS)
The RN5.0 OMS uses OS provided by the underlying NSN Flexiplatform.
• Red Hat Enterprise Linux (RHEL) version 4
• Components are installed utilizing RPM files (Red Hat Package Management)
• Integrated OMS (MCP18-B) uses 32bit SW release / standalone OMS (HP Proliant) uses 64bit SW rel
• The operating system (OS) delivery is one part of the Flexiplatform base platform services together with
other important components such as backup, hardware and software management, and the high
availability services (HAS) middleware.
• The FlexiPlatform Linux distribution is not completely identical to the Red Hat Linux distribution.
• Many RPMs that are not needed by the FlexiPlatform and its applications, but are normally contained in
standard Red Hat Enterprise Linux, have been removed. This reduces the size of operating system and
removes potential vulnerabilities.
• Currently, the number of different Linux OS SW packages included in the FlexiPlatform OS installation
package has been reduced to roughly one-seventh of the original number of SW packages included in
Red Hat Enterprise Linux Release distribution.
• In addition to the RPMs selected from the Red Hat Distribution, the system contains roughly 100 RPMs
provided by Nokia Siemens Networks to add functionality to the system. The exemplary enhancements
provided by the mentioned RPMs include:
• the watchdog feeder subsystem WDMana
• network link monitor for automatic LAN failover support
High-level SW Architecture of WCDMA RNC OMS
OSS WS
NetAct
EM
NWI3 (IIOP) HTTPS EMI (IIOP) HTTPS
OMS
RNC O&M Common OMS
functionalities O&M
O&M for DMX Flexiplatform

based NEs
BTS O&M HTTP/

(TCP/IP) FTP BTS O&M
(IPoA)
RNC BTS
OMU O&M
HTTPS
OMS SW Architecture Domains
RNC OMS SOFTWARE ARCHITECTURE OVERVIEW
RNC OMS SW ARCHITECTURE
ELEMENT MANAGER UI
AL PM GUIs Active Sessions RNW Object Browser
PuTTY RU20
FM GUI Parameter Tool Log Viewer Ver Viewer
O&M APPLICATIONS
Fault Mgmt State Mgmt SW Mgmt License Mgmt
Configuration Mgmt Performance Mgmt HW Mgmt
O&M INTERFACE LAYER

EM I/F NWI3 I/F BTS O&M I/F
COMMON O&M SERVICE LAYER

Messaging Aggregation Mediation Configuration Monitoring Reporting Security
PLATFORM SW
OS Distro HW Mgmt SW Mgmt Alarm System Networking HAS CLI Commisioning User Mgmt
PIU
HARDWARE Stand-alone
WCDMA Operability & OMS Architecture Evolution
RU10: RU20: RU30: RU40:
NetAct NetAct
OMS OMS OMS
OMU
OMU
OMU
OMU
OMS
OMS
OMU
OMU
OMU
OMS
RNC RNC RNC RNC
RNC RNC
RNC
OMU OMU
BTSs
BTSs BTSs
BTSs BTSs BTSs

BTSs BTSs
- Stand alone OMS - 10 RNCs by one OMS - No MCP-18B OMS
- long distance RNC<->OMS
Soc Classification level
RU30 enhancements RU30
• OMS supports several RNCs

• Automatic OMS resiliency NetAct
• Common OMS SW in integrated & OMS

standalone OMS
– 64 bit version for Standalone OMS
OMU
32 bit version for integrated OMS
– OMS application changes will come to RNC
IPA RNC integrated OMS
OMU
• RNC Integrated OMS (MCP18-B) is still

supported, but integrated OMS supports
only one RNC BTSs
BTSs

RU20+RU30+RU40
RU30: Standalone OMS
• In new RU30 RNC deliveries NetAct
NWI3 OMS
EMT /
BTSOM
OMU
• Integrated OMS HW(MCP18-B) is still supported
• O&M interface (RNC-OMS) changed to BTSOM protocol
(protocol already used for BTS)
RNC
• Commercial HW -> latest & greatest HW available
BTS
– Number of network element has increased O&M
-> provides more connectivity (about 4 times more)
– Data amounts will increase -> Strong aggregation
– about 14 times more CPU power
• Evolution step towards to new technologies - Future proof Ultra
solution Flexi
– Support for multi-technologies

14 © Nokia Siemens Networks /
HP Proliant DL360 Gen 6 Server in OMS RU20+RU30+RU40
• Available for WCDMA in RU20 onwards with new RNC deliveries and for
all OMS deliveries and replacements after that.
• HP Proliant DL360 G6:
– 2 x Quad core Nehalem Intel processors
– 24 GB memory (RAM)
– 2 x Mirrored hard discs (total 4 x 146GB)
– dual port network card
– USB 2.0 ports
– Redundant 460 W power (AC)
– Height 1U
Dimensions
Height 4.32 cm (1.7 in)
Depth 70.49 cm (27.75 in)
Width 42.62 cm (16.78 in)
Weight (min configuration / max 14.51 kg (32 lb) /
configured) 17.92 kg (39.5 lb)

OMS HW generations on the field
2010 2011 2012 2013 2014 2015 2016
RU20 RU30 RU40 RU50 RU60 RU70 RU80
HP Proliant
DL360 G5
HP Proliant
DL360 G6
HP Proliant DL360 G7 not

supported by OMS
HP Proliant
DL360 G next
HP Proliant
DL360 G next+2
HP Proliant
DL360 G
next+4F HP G next delayed due to
Intel schedule change for
MCP-18B
Sandy Bridge CPU family
in sale
full support
SW support presented Preliminary
SW support termination
OMS Connectivity & Capacity

WCDMA OMS Connectivity (12/2010 roadmap)
Profiles OMS RNC RN4.0 RU20 / RN5.0 RU30 / RN6.0 / RU40 / RN7.0 /
HW type mcRNC 1.0 mcRNC 2.0
(tentative)
Max RNC196 #BTS = 512 + Gigabit + Gigabit NOT SUPPORTED
connectivity #Cell = 1152 #BTS = 600 #BTS = 600
Profile
OMS disk= 73GB #Cell = 1800 #Cell = 1800
OMS disk= 73GB / OMS disk= 147GB
147GB
RNC450 #BTS = 600 #BTS = 600 #BTS = 600 NOT SUPPORTED
MCP18 B #Cell = 1800 #Cell = 1800 #Cell = 1800
OMS disk= 73GB OMS disk= 73GB / OMS disk= 147GB
(73 / 147GB HW) 147GB
RNC2600 #BTS = 2800 #BTS = 2800 #BTS = 2800 NOT SUPPORTED
#Cell = 2800 #Cell = 2800 #Cell = 3800
OMS disk= 73GB 4800* OMS disk= 147GB
(73 / 147GB HW) OMS disk= 147GB
HP Proliant RNC196 / - #RNC = 1 #RNC = 10 #RNC = 10
DL 360 G6 RNC450 / #BTS = 2800 #BTS = 10 000 #BTS = 10 000
5540 RNC2600 #Cell = 4800 #Cell = 30 000 #Cell = 30 000
mcRNC - -
Capacity • Capacity steps • Capacity steps per 1 • Capacity steps per 1 • Capacity steps per 1
steps per 1 cell cell cell cell
Required • RAN1783 • RAN1786 OMS
features Standalone OMS for supports several RNCs
RNC • RAN1903 OMS
• RAN1782 OMS disc overload control
capacity increase • RAN1874 Automatic
OMS resilience

RU20
PM profiles with Integrated OMS (MCP18-B)
RNC type RN5.0

RNC196/RNC450 #BTS = 600 • 15 min interval for all measurement types
#Cell = 1800 • RCPM Cell level with 60 min measurement interval
• Collection of key counters feature can be used
• Autodef. measurements 24h measurement interval
RNC2600 #BTS = 600 • 15 min interval for all measurement types
#BTS = 2800 • Minimum measurement interval 30 min
#Cell = 2800 • RCPM cell level measurements can be used with 60 min interval
• Collection of key counters feature can not be used
#Cell = 3800 • RCPM cell level measurements can not be used
#Cell = 4800 • RCPM cell level measurements can not be used

RU20
PM profiles with Standalone OMS
RN5.0
#BTS = 2800 • 15 min interval for all measurement types
• Autodef. measurements 60min measurement interval
#BTS = 2800 • Minimum measurement interval 30 min for all measurement types
• Autodef. measurements 60 min measurement interval
RN6.0
#RNC = 10 • 15 min interval for all measurement types
#BTS = 3000 • RCPM Cell level with 60 min measurement interval
#Cell = 7500 • Collection of key counters feature can be used
• Autodef. measurements 60min measurement interval
#RNC = 10 • Minimum measurement interval 30 min
#BTS = 5000 • RCPM cell level measurements can be used with 60 min interval
#Cell = 15000 • Collection of key counters feature can not be used
#RNC = 10 • 60 min interval is used for all measurement types
#BTS = 10 000 • RCPM RNC level measurements used
#Cell = 30 000 • Collection of key counters feature can not be used
• RCPM cell level measurements can not be used
RNC OMS EM Applications

Element Manager Concept
Element Manager
Application Launcher EM Homepage
EM Applications

Element Manager installation pages
• The OMS EM installation page is the main

page for the OMS web server. It contains
information about the OMS server:
– running OMS SW: IP address, software

version (currentset), SystemId
– managed elements: IP address, ENV
version
• Application launcher and SSH Putty client

can be installed from EM installation page
that runs on the OMS web server
– Application Launcher can be installed

automatically or manually
– Windows and Linux operating systems
are supported
– Correct Java Runtime Environment
downloaded with AL

Starting Application Launcher
• Application Launcher can be started in;
– Windows client by using em.bat from the default download folder
(\opt\nokiasiemens\ALClient_2)
or doubleclicking Application Launcher icon on desktop
– Linux client by using ./em.sh from the default download folder
(\opt\nokiasiemens\ALClient_2)
or clicking Application Launcher icon on Applications menu.
– When Application Launcher is started, login screen is displayed
• Login screen has three different fields:
Network Element IP address, Login name
and Password
• Login dialog verifies the user and creates a
connection to the server

RU20
Application Launcher General
• Application Launcher is a collection of EM

applications and runtime management GUIs
• During the Application Launcher startup the
user is authenticated and authorized and all
installed and configured applications become
available
• Application Launcher takes care of the EM
login security
• Parameter handling
• CORBA reference management (IOR
fetching)

RU20
Application Launcher Main Window
• Application Launcher main window

displays all services that the user is
authorized to use
• Applications can be started by double

clicking them.
• All used services can also be found

from the Launch-menu. Launch menu
contains also Personal Settings and
Active Sessions applications.

Application launcher main window concept
launch
EM Client Application
In OMS, permission to a certain application is

granted to a USER GROUP, not to a single user!

RU20
RNC OMS EM Applications
• The RNC Element Manager provides graphical element management applications for
frequently performed tasks. The RNC EM contains the following management
applications:
✓RNC RNW Object Browser ✓MMI Window
✓RNW Measurement Management ✓Active Sessions
✓RNW Measurement Presentation ✓PuTTY
✓RNW Online Monitoring ✓Parameter tool
✓NE Measurement Explorer ✓Fault Management
✓NE Threshold Management ✓State Handling
✓Diagnostics

RU20
RNW Measurement Management
• With the RNW Measurement Management

element manager GUI, the user can handle
measurements, that is, activate or
deactivate measurements as well as
interrogate them.

RU20
RNW Measurement Presentation
• Using the RNW Measurement Presentation

GUI, the user can view results of the radio
network measurements in graphical or written
form.

RU20
RNW Online Monitoring
• The RNW Online Monitoring

application has a graphical user
interface, with which the user can
perform real-time radio network
monitoring with selected
parameters.

RU20
NE Measurement Explorer
• The NE Measurement
Explorer is an application
which is used to view
measurement results in textual
form.

RU20
NE Threshold Management
• The Threshold Management GUI is used for creating and editing Threshold Rules, Threshold
Evaluations and KPIs.

RU20
Diagnostics
• Diagnostics handling GUI for OMS

is a Java application which has
enhanced functionality of the
previous diagnostics handling MML
program. With this GUI user is able
to run diagnostic tests for all units
and plug-in units in the network
element. The enhanced
functionalities are etc. automated
state handling when starting
diagnostics jobs and timed starting of
the diagnostics jobs.

RU20
MMI Window
• The EM MMI Window application

provides a way to use the traditional
MMLs in the Element Manager. With
the EM MMI Window you can send
MML commands to the network
element you are connected to. Upon
opening an MML session via the MMI
Window, the system does not ask you
to enter your user ID, providing that
the EM user has been mapped to an
MMI user.

RU20
Active sessions
• The Active Sessions dialog enables user to view active sessions. Each EM
user for whom appropriate user rights for this domain have been granted (that
is, permission to view) is able to view which sessions are currently active. The
dialog provides information on the session IDs and start times of the active
sessions, as well as the user identity of the EM users currently having an active
session and the management system the sessions were initiated by.
• The Active Sessions dialog also enables user to terminate sessions. Those
EM users for whom sufficient user rights (permission to modify) have been
granted using the User Authority Manager application, are able to terminate
sessions of other EM users as well, for example in cases where maintenenace
procedures need to be carried out and there may not be any other active
sessions. The dialog asks for confirmation before terminating a session.

RU20
Active Sessions
• The system reads the active sessions data

upon starting of the Active Sessions dialog;
therefore, in order to later view the current
situation, you must refresh the data using the
Refresh button.

RU20
Fault Management
The Fault Management GUI contains a graphical user interface for NE level alarm system to
get a view of active alarms issued for the object and vice versa.

RU20
State Handling
• With the State Handling application you Left hand side of the main view has a static
can inquire unit and I/O device states, tree which shows all RNC's units and I/O
change unit and I/O device states, change devices.
unit status info, restart units and restart
system. • Right hand side of the main view has a
tabbed pane with two tables which show state
• The main window of the State Handling is inquiry results for both units and I/O devices.
divided into two parts.

RU20
Parameter tool
• Parameter tool is a GUI were you

can modify or edit (add, delete,
rename, copy, or move) entries in
the LDAP directory.
• You can also browse
configuration information and
view entries (or managed object
instances stored in the directory)
and their attributes.

RU20
PuTTY (Telnet/SSH Client)
• PuTTY is a Telnet and a SSH client

for Win32 and Unix platforms, along
with an xterm terminal emulator.
• You can connect to the OMS/FEWS
with PuTTY (or any other SSH-client)
NOTE! When you open SSH connection to FEWS

or OMS and you receive following error during
logging procedure:
@ WARNING: REMOTE HOST IDENTIFICATION
HAS CHANGED! @
That appears, because the target has been
reinstalled with new software and the old
identification key isn’t valid anymore.
Remove the known_hosts row (which is
informed on the error message) from your home
directory.
E.g .Offending key in /home/userid/.ssh/known_hosts:4
Or if that doesn’t help, remove the known_host file.
rm /home/userid/.ssh/known_hosts

OMS application changes in RU30 with IPA- RU30
RNC comparing to RU20 OMS applications

• Radio Network Object Browser
– Application is replaced with new Web GUI based application called
‘Topology browser with NE Parameter Editor’.
• NE PM Explorer
– Application is removed.
Transport&HW measurement management is added to the RNW Measurement
Management GUI
– Measurement results are viewed using RNW Measurement Presentation GUI.
• Radio Network Online Monitoring

– Measurement types : ‘OLPC monitoring’ and ‘Handover monitoring’ support is ended
• Diagnostics
– Application is removed. Functionality available via RNC MMI.
• State Handling
– Application is removed. Functionality available via RNC MMI.

BTS O&M mediation
NMS
• The O&M connection between the BTS and NWI3
NetAct is built via BTS O&M mediation. RAN O&M
• BTS O&M mediation means that the RNC's backbone
mediation function converts messages between RNC
the BTS O&M interface and network EBR
OMS
management interface (NWI3), as well as the
messages between the BTS O&M and the RNC
element management interface (EMI). EMT if.
BTS Iub O&M Mediation Function
OMU
OMU
SFU
NIU NIU NIU NIU NIU
BTS Iub O&M
BTS BTS
BTS

Features related to BTS O&M mediation
RNW Alarm System
• The RNWAlarm System in RNC uses BTS O&M mediation to receive alarms from BTS.
Reset and Initialisation
• The Reset and Initialisation feature uses BTS O&M mediation to send commands from RNC to BTS.
SW Management
• The SW management feature uses BTS O&M mediation to mediate commands between BTS and
NetAct.
• WBTS SW download and query, OMS SW query
HW Configuration upload
• The HW Configuration upload feature uses BTS O&M mediation to mediate commands between BTS
and NetAct.
- WBTS and RNC HW query
BTS Performance Management data transfer
• OMS collects measurement data directly from the WBTS using O&M interface.
BTS Licence Management
• The LM operation (download, upload, delete and status query) uses BTS O&M mediation to mediate
commands between BTS and NetAct.
OMS SW broadcast
• NetAct can update BTS’s SW using one sw download request. OMS saves the BTS software packages
to its own ftp server and BTS downloads the needed files from there.

RU20
O&M mediation protocol stack
Iub O&M NWI3

(ASN.1 coded BTS O&M msg) (ORB coded O&M msg)
WBTS Router in AXC RNC NetAct

OMU OMS
Application Applications Applications Applications Applications
Layer
Iub O&M Iub O&M IIOP IIOP
Network TCP TCP TCP/UDP TCP/UDP
Layer IP IP IP IP IP IP
LLC/SNAP LLC/SNAP LLC/SNAP LLC/SNAP

Transport/
AAL5 AAL5 AAL5 AAL5
Transmission LAN/WAN LAN/WAN
Layer ATM ATM ATM ATM
SDH/PDH SDH/PDH SDH/PDH SDH/PDH
EMT
(DX BUS coded O&M msg)

OMS Troubleshooting issues

Instructions given in customer documentation &
NSN internal instruction doc
• See, the RU20 RNC OMS Troubleshooting doc:
https://sharenet-
ims.inside.nokiasiemensnetworks.com/Open/426979378
• Also refer to RU20 ”Command Line Interface Tools and
Management Scripts in RNC OMS” doc that lists available
commands for OMS Status checking!
• FYI: used RNC OMS R&D instructions for PRONTO issues

47 © Nokia Siemens Networks 2008
OMS Master-syslog
• Master syslog is a logfile which holds the most important data about the system events.
e.g. alarms, errors and user operations.
• You can monitor the syslog with the following command:
tail -f /var/log/master-syslog
or view the full log with the less command or filter output by using the grep command.

Core dumps
• When a program terminates abnormally, it makes a core dump

• Core dump is a memory image of the process. It tells what the process was doing before the crash.
• You can find the OMS core dumps in the /var/crash/ -folder

Tracelogs
• Tracelogs are debug logs which are produced by GUI server processes running on OMS. They are useful
to developers when troubleshooting GUI issues.
• You can find OMS trace logs in /var/log/oms/ -folder

RNC OMS CLI & Z-commanding
• E.g.
– fscheckforexecshield.sh
– reloadrncalarms
– zaho
– zahp
– Zdxversion
– Zmmimapping
– znwi3logging
– zomscli
– zomuip
– zpr
– zrg
– zru
– zship
– zstatus
– Zupt
Please, check the RU20 RNC OMS customer documentation: ”CLI Tools and Management Script in OMS”
https://sharenet-ims.inside.nokiasiemensnetworks.com/Download/D427491509

WCDMA O&M DCN

RU20 WCDMA O&M DCN –integrated OMS

RU20 WCDMA O&M DCN –standalone OMS

RN5.0 OMS locations with IPA-RNC
NetAct site
OMS (b)
NetAct
IP
Network VLAN OMS (c)
VLAN
RNC site
IPA-RNC
IP Network ESA-12/24/40
Site Router integrated OMS
BTS-1 net VLAN Ethernet switch
OMU-0
OMS locations OMU-1

a) at the RNC site
b) at the NetAct site OMS (a)
c) at the own site

Security on Management Plane Interfaces

Thank you!


OMS Training

Uploaded by

Copyright:

Available Formats

OMS Training

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

OMS Training

Uploaded by

Copyright:

Available Formats

Operation and Management Server (OMS) in

Operation and Management Server (OMS) is a Linux OS based

OMS provides O&M data mediation, concentration and aggregation

NetAct Framework is used for network-level changes, targeted to several

RU20/RN5.0 RNC OMS supports two HW

• The Integrated RNC OMS, old legacy HW comes with:

RU20/RN5.0 RNC OMS application SW is

• EM, SW Mgmt & Commissioning support

NWI3 (IIOP) HTTPS EMI (IIOP) HTTPS

O&M for DMX Flexiplatform

BTS O&M HTTP/

Configuration Mgmt Performance Mgmt HW Mgmt

O&M INTERFACE LAYER

COMMON O&M SERVICE LAYER

OMS OMS OMS

BTSs BTSs BTSs

• OMS supports several RNCs

• Common OMS SW in integrated & OMS

• RNC Integrated OMS (MCP18-B) is still

Soc Classification level

• In new RU30 RNC deliveries NetAct

– Support for multi-technologies

Soc Classification level

Soc Classification level

2010 2011 2012 2013 2014 2015 2016

RU20 RU30 RU40 RU50 RU60 RU70 RU80

HP Proliant DL360 G7 not

Soc Classification level

Soc Classification level

RNC type RN5.0

Soc Classification level

Soc Classification level

Application Launcher EM Homepage

Soc Classification level

• The OMS EM installation page is the main

– running OMS SW: IP address, software

• Application launcher and SSH Putty client

– Application Launcher can be installed

Soc Classification level

Soc Classification level

• Application Launcher is a collection of EM

Soc Classification level

• Application Launcher main window

• Applications can be started by double

• All used services can also be found

Soc Classification level

In OMS, permission to a certain application is

Soc Classification level

✓RNC RNW Object Browser ✓MMI Window

✓RNW Measurement Management ✓Active Sessions

✓RNW Measurement Presentation ✓PuTTY

✓RNW Online Monitoring ✓Parameter tool

✓NE Measurement Explorer ✓Fault Management

✓NE Threshold Management ✓State Handling

Soc Classification level

• With the RNW Measurement Management

Soc Classification level

• Using the RNW Measurement Presentation

Soc Classification level