NMS

By
Rahul Wargad
Network Management Systems
A Telecom Network
SDH
Mux Fibre

backbone
RT

C optiMA
Main
XChg
O
FiLL .
T
corDECT RT . ...
RT
DIAS
... ...
... ... ...

2
Network Management Systems

Network “Storms”
Rapid escalation of cascading failures
Example:
Noise on a link
 packet loss
 queue buildup
 source retransmits
 congestion on other links

noise
 TX = trunk exchange
LE = local exchange
LE LE
LE
TX
TX TX1 TX2
LE
LE LE

 Trunk line fails

 alarms at TX1 and TX2
• Call failure rate exceeds threshold at several LEs
 alarms at many LEs
 alarms at many LEs
- LE operator ignores alarms
- network operator sees long list of alarms,
important ones may be missed

 need integrated network management system

- only relevant alarms to the right person

 SLA: DSL Access

Example: DSL Access to Internet Service

 SLA: DSL Access

Example: DSL Access to Internet Service

• Customer uses Telecom SP to connect to ISP

• ISP provides TCP/IP to Content SP
 Multiple SLAs between:
• CSP - ISP
• ISP - TSP
• TSP - Customer
 Network Management System

Network Management
Why?
Manage — monitor and control— heterogeneous,
graphically-distributed elements
What?
Configuration identify and control managed
objects
Faults detect, isolate, repair
Accounting charges for resource usage
limits on resource usage
Security protect access to objects
authentication, manage keys, logs
Performance gather statistics
analyze and plan
FCAPS 8
 EMS/NMS Overview for BSS
• Desktop Management:
• Desktop Management offers services like
Application Packaging, Inventory Management,
Patch Management, Remote Administration and
Remote Control.
• Application Packaging
• Application packaging offers software
distribution for desktops in push and pull
mechanisms providing Options for both
mandatory (Push)and Optional softwares(Pull).
 EMS/NMS Overview for BSS
• Inventory Management
• The Inventory Management Agent running on the clients will
perform continuous scans on the machines and will update the
configuration server database which will be synchronized with the
external
• database using Messaging Server Service. On comparing the
information with the existing asset management database, the
Reporting server will generate a report if any difference is found and
an e-mail will be sent to the administrator.
• Patch Manager
• The Patch Manager agent running on all the client machines will
update the CSDB with information related to existing patches and
newly installed patches and with the information related to the
patches that failed to be updated on the client machine to the
CSDB.
 EMS/NMS Overview for BSS
• Radia Management Portal
• Centralized administration for the desktop environment is provided by Radia
Management Portal which will provide enterprise level support for remote
administration and remote control. This will facilitate web based
management of the desktop environment.
• Centralized administration for the desktop environment includes enterprise
level support for remote administration and remote control.This is facilitated
through a web based management console.

• Database Management
The database management helps database administrators to
seamlessly detect, diagnose and resolve Oracle performance issues and
monitor Oracle 24X7. The database server monitoring tool is an agent
based monitoring software that provides out-of-the-box performance metrics
and helps to visualize the health and availability of an Oracle Database
server farm. Applications provide help in analyzing the database server
usage, Oracle database availability and database server health.
• HP integrated storage resource
management software encompasses
solutions for managing both infrastructure
and information.
• HP OpenView Operation’s technology provides
correlation capabilities on supported intelligent agent
platforms and on the central manager correlating data
from any combination of event sources.

• HP OpenView Event Correlation Composer is a graphical

user interface (GUI) that enables users to tailor the event
correlation behavior for correlations that are shipped with
HP OpenView products, and simplifies the development of
customer-created correlations.
• Correlations can be used out of the box or can be easily
fine tuned to fit the environment without any programming
knowledge
• HP OpenView Operations manages every
major operating system—including HP-
UX, Sun Solaris, Microsoft Windows®,
Linux, IBM AIX and HP Tru64—right out of
the box.
• Distributed system and fault management
—how does it work?
• HP OpenView Operations provides a
consistent system and fault-management
process and workflow. It enables
operators to use common techniques for
all managed multi-vendor objects across
the environment.
• HP OpenView PC Change and Configuration
Management:-
• The solution rapidly provisions desktops and notebooks,
enforces configuration compliance and automates the
management of all software layers on a PC, including
the operating system, patches, applications, content and
settings. HP’s automated change and configuration
management solution enables the management of
software throughout the entire PC life cycle—from
provisioning a new device to ongoing inventory,
packaging, configuration conflict analysis, application
deployment and self-healing, usage monitoring, and
migration to retirement.
• Network optimization:-
• Comprehensive bandwidth management capabilities—including
multi-casting, bandwidth throttling, configuration and component
differencing, compression and distributed caching—assure
optimized use of network resources and a minimum of traffic and
wait-time for bandwidth-constrained networks.
• Central Java™ operator console:-
• The HP OpenView Operations Java user interface combines the
familiar concepts of HP OpenView Operations with Microsoft
Windows-type concepts to minimize training time and to reduce the
operators’ learning curve. It provides a single-pane-of-glass view
across the environment, integrating many other HP OpenView
solutions into a single operations center.
EMS/NMS System
• When a device or a system that is being
monitored generates an event or an alert,
it is sent to the EMS/NMS monitoring
system.
• The EMS/NMS system then classifies the
data that it acquires and then sends it to
the specific EMS/NMS tool.
EMS System – Event Gneration
Mechanism
• The EMS/NMS systems continuoulsy monitors the OS parameters,
system log files and application log provided by the application
owners..The events that are generated are sent to the control
management source which takes the input and then based on the
settings defined, send a notification and if an automatic corrective
action is configured for that particular event, then the automatic
action is executed and if successful the process is stopped.
• Parallelly, a trouble ticket is generated. Based on the classification
of the event that is generated, it is assigned to the concerned
support group or an operator.
• The operator or the concerned will check for any actions that are
configured and will also work on the ticket to rectify it
• He can than add an annotation stating that the problem has been
resolved and will close the ticket. In case the operator or the
concerned is not able to close the ticket, it is escalated to the next
level.
NMS System – Polling
Mechanism
• The NMS System checks the status of the devices
according to the polling interval set. When the system
polls a device it will get the status of the device. If the
status of the device is up, the NMS system will wait for
the next interval and no action is taken. In case the
status is discovered as other than normal, the event is
classified and is sent to a ticket system where an alert
can be generated. If the polling interval devices that are
being managed have a problem, the device will send an
SNMP trap to the NMS system. This is then classified
and is sent to the ticketing system where it is assigned to
the respective group who will work on it to rectify the
problem.
OpenView Performance Insight
Network Node Manager
Architecture