NMS Overview

© Tech Mahindra Limited 2008 Tech Mahindra Limited confidential

 Objectives of the Session
 At the end of this session, the participants will
understand,

 What is TMN?

 TMN Network Management Architecture.

 What is NMS?

 NMS Functional Architecture

 NMS Functional areas

07/04/21 CONFIDENTIAL© Copyright 2008 Tech Mahindra Limited 2

What is TMN?
 TMN provides a framework for achieving interconnectivity and
communication across heterogeneous operations system and
telecommunication networks.

 To achieve this, TMN defines a set of interface points for elements

which perform the actual communications processing (such as a
call processing switch) to be accessed by elements, such as
management workstations, to monitor and control them.

 The standard interface allows elements from different

manufacturers to be incorporated into a network under a single
management control.

07/04/21 CONFIDENTIAL© Copyright 2008 Tech Mahindra Limited 3

TMN Network Management Architecture

07/04/21 CONFIDENTIAL© Copyright 2008 Tech Mahindra Limited 4

What is TMN?
 TMN provides a framework for achieving interconnectivity and
communication across heterogeneous operations system and
telecommunication networks.

 To achieve this, TMN defines a set of interface points for elements

which perform the actual communications processing (such as a
call processing switch) to be accessed by elements, such as
management workstations, to monitor and control them.

 The standard interface allows elements from different

manufacturers to be incorporated into a network under a single
management control.

07/04/21 CONFIDENTIAL© Copyright 2008 Tech Mahindra Limited 5

TMN Network Element & Element Management
Layer

 Network Element Layer (NEL) defines interfaces for the network

elements, instantiating functions for device instrumentation, ideally
covering all FCAPS areas.

 Element Management Layer (EML) provides management functions

for network elements on an individual or group basis.

 It also supports an abstraction of the functions provided by the

network element layer.

 Examples include determining equipment errors, measuring device

temperatures, collecting statistical data for accounting purposes, and
logging event notifications and performance statistics

07/04/21 CONFIDENTIAL© Copyright 2008 Tech Mahindra Limited 6

TMN Network Management Layer

 Network Management Layer (NML) offers a holistic view of the

network, between multiple pieces of equipment and independent of
device types and vendors.

 This function takes input from multiple elements (which in reality

might be different applications), correlates the information received
from the various sources (also referred to as root cause analysis),
and identifies the event that has occurred.

 This is a level of abstraction above Element Management in that

operations personnel are not “weeding” through potentially
hundreds of Unreachable or Node Down alerts, but instead are
focusing on the event, such as "an area-border router has failed.“

 Examples include end-to-end network utilization reports, root cause

analysis, and traffic engineering.
07/04/21 CONFIDENTIAL© Copyright 2008 Tech Mahindra Limited 7
TMN Service Management Layer

 Service Management Layer (SML) is concerned with, and

responsible for, the contractual aspects of services that are being
provided to customers.

 The main functions of this layer are service creation, order

handling, service implementation, service monitoring, complaint
handling, and invoicing.

 This layer is responsible for adding intelligence and automation to

filtered events, event correlation and communication between
databases and incident management systems.

 Examples include QoS management (delay, loss, jitter), accounting

per service (VPN), and SLA monitoring and notification.

07/04/21 CONFIDENTIAL© Copyright 2008 Tech Mahindra Limited 8

TMN Business Management Layer

 Business Management Layer (BML) is responsible for the total

enterprise.

 Business management can be considered a goal-setting approach:

"What are the objectives, and how can the network (and network
management specifically) help achieve them?“

07/04/21 CONFIDENTIAL© Copyright 2008 Tech Mahindra Limited 9

TMN Business Management Layer

07/04/21 CONFIDENTIAL© Copyright 2008 Tech Mahindra Limited 10

What is EMS?

 manages one or more specific type of telecommunications network

element (NE).

 manages the functions and capabilities within each NE, but does
not manage the traffic between different NEs in the network.

07/04/21 CONFIDENTIAL© Copyright 2008 Tech Mahindra Limited 11

What is NMS?

 Network - Collection of computers, printers, routers, switches and

other devices that are able to communicate with each other over
some transmission medium.

 Management - involves the planning, organizing, monitoring,

accounting and controlling of activities and resources

 Network management is a service that employs a variety of tools,

applications, and devices to assist human network managers in
monitoring and maintaining networks.

07/04/21 CONFIDENTIAL© Copyright 2008 Tech Mahindra Limited 12

What is NMS?

 A Network Management System (NMS) is a combination of

hardware and software used to monitor and administer a network.

 Network Management doesn’t mean an application with a database

that contains huge chunk of data running the show. It is really an
integrated conglomeration of functions that may be on one
machine but may span thousands of miles, different support
organizations and many machines and databases.

07/04/21 CONFIDENTIAL© Copyright 2008 Tech Mahindra Limited 13

NMS Functional Architecture

Network management systems have four basic levels of functionality.

Each level has a set of tasks defined to provide, format, or collect data
necessary to manage the objects.

07/04/21 CONFIDENTIAL© Copyright 2008 Tech Mahindra Limited 14

NMS Functional Architecture
 Managed Objects
 Managed Objects (Managed Resources) are devices or systems that
require monitoring and management. Some examples of managed
objects include Routers, Concentrators, Hosts, Servers and Applications
like Oracle, Microsoft SMS, Lotus Notes, etc. The Managed Objects
does not have to be a piece of hardware but considered as a function
provided on the network.

 Element Management Systems (EMS)

 An EMS manages a specific portion of the network. For example SNet
Manager, a SNMP management application, is used to manage SNMP
elements. Element Managers may manage asynchronous lines,
multiplexers, PABX’s, proprietary systems or an application.

07/04/21 CONFIDENTIAL© Copyright 2008 Tech Mahindra Limited 15

NMS Functional Architecture

 Manager of Managers Systems (MoM)

 MoM systems integrates the information associated with several EMSs.
Several different products fall into this category that includes Boole &
Babbage’s CommandPost, NyNEX AllLink, International Telematics
MAXM, OSI NetExpert and others. In most of the cases, the actual data
to be collected comes from the ManagedObject, which is collected by
the EMS systems. The EMSs, in turn consolidates the data for
processing and retrieval.

 User Interface
 The user interface that shows the information such as real time alarms,
trend analysis graphs, etc. is the principal piece to deploy a successful
system. If the information cannot be distributed to the whole MIS
organization to keep people informed, then the real purpose of NMS
will be lost. Data would not mean anything, if it is not used to make
decisions about the optimization of the systems and functions. These
system components are mapped back as Management Functional Areas
(MFAs).
07/04/21 CONFIDENTIAL© Copyright 2008 Tech Mahindra Limited 16
NMS Functional Areas

 The most common framework depicted in the NMS design centers

around the Open Systems Interconnect (OSI) FCAPS model of
MFAs. However, most of the network management implementations
do not really cover all these areas. The components of the FCAPS
are:
 Fault Management
 Configuration Management
 Accounting
 Performance Management
 Security Management

07/04/21 CONFIDENTIAL© Copyright 2008 Tech Mahindra Limited 17

Fault Management

 The goal of fault management is to detect, log, notify users of, and
(to the extent possible) automatically fix network problems to keep
the network in effectively running condition. Since, faulty condition
cause downtime and network degradation, fault management is
perhaps the most widely implemented module of the ISO network
management elements.
 The major objectives of Fault Management are:
 Determining problem symptoms.
 Isolating the problem.
 Fix the problem.
 Test the fix on all important subsystems.
 Record the problem's detection and resolution.

07/04/21 CONFIDENTIAL© Copyright 2008 Tech Mahindra Limited 18

Configuration Management

 Configuration Management is usually the first issue for a network

manager. It begins at installation of the first network node and
never ends. The goal of configuration management is to monitor
network and system configuration information so that the effects
on network operation of various versions of hardware and software
elements can be tracked and managed.
 Each network element has a variety of version information
associated with it. Configuration Management subsystems store
these information in a database, which can be accessed and used,
when a problem occurs.

07/04/21 CONFIDENTIAL© Copyright 2008 Tech Mahindra Limited 19

Accounting Management

 The goal of accounting management is to measure the network

utilization parameters, so that the network usage can be regulated
appropriately. Such regulation minimizes network problems as the
network resources can be apportioned based on the resource
capacities, and maximizes the fairness of network access.
 The first step in accounting management is to measure the
utilization of the important resources. Analysis of the result provide
insight into current usage patterns of the network resources and
the quotas can be set appropriately. The measurement of the
resource yield billing information and can be used to access the
network resources in a continued, fair and optimal way.

07/04/21 CONFIDENTIAL© Copyright 2008 Tech Mahindra Limited 20

Performance Management

 The goal of Performance Management is to measure the various

aspects of network performance, so that internet work performance
can be maintained at acceptable levels.
 Example of the variables for which data collection is done are
network throughput, user response times and line utilization.
 The major steps involved in Performance Management are:
 Gather the performance data from the variables.
 Analyze the data to determine the normal levels.
 Determine appropriate performance thresholds for each important
variable, so that the network problem is detected whenever the
collected value goes above the threshold levels.

07/04/21 CONFIDENTIAL© Copyright 2008 Tech Mahindra Limited 21

Security Management

 The goal of Security Management is to control the access to the

network resources, so that the network cannot be sabotaged and
the sensitive information are accessed only by those with proper
authorization.
 The security management system, for example, can monitor users
logging on to a network resource, or can refuse the access to
unauthorized users. Security Management systems work by
partitioning network resources into authorized and unauthorized
areas.
 The functions performed by the Security Management system are:
 Identify sensitive network resources (including systems, files, and
other entities)
 Determine mappings between sensitive network resources and user
sets
 Monitor access points to sensitive network resources
 Log inappropriate access to sensitive network resources, etc.

07/04/21 CONFIDENTIAL© Copyright 2008 Tech Mahindra Limited 22

 Thank You

© Tech Mahindra Limited 2008 Tech Mahindra Limited confidential