tmn overview

Lucent Technologies - Proprietary

TMN Overview

Telecommunications Management Network

Shervin Erfani

2Lucent Technologies - Proprietary

Present Network Management

Environment

• Multiple vendors, mixed protocols, proprietary interfaces and systems

• Diverse networks

• Loosely-organized applications (i.e., gaps and overlaps)

• Multiple management domains, no clear boundaries and responsibilities

• Manual interventions and uncommon duplicate data bases

EMS (?)

EMS NMS NMS EMS

Customer 1 Exchange Carrier Local Carrier Customer 2

SNMP

Host

RingRouterT1-Fractional T1

Network

TL1

?

Proprietary

Frame Relay Network

Router

Ring

Terminal Server

SNMP


Managing Network Management

• What is structured approach to NM?An organized architecture for a conceptually separate management

network to interconnect NMSs & equipment using standardized

– functions (e.g., FCAPS)– Information Models (i.e., MIB)– Network Management Protocols (CMIP as base, but SNMP

supported)– NM expertise and tools (e.g., event correlator; NM m&p)

• Why is it important?– Ability to scale NMSs for large number of devices– Support for new technologies, equipment and services– Promote flexibility and system integration based on modularity and

interoperability– Defining a common information model (i.e., an agent MIB)


Management System

Workstation

RouterTerminal

Server Router

Data Communication Network (DCN)

Telecommunications network

Network Management in the TMN Environment

• Interconnection of service providers and user management infrastructures

Management System

Management System

FrameRelay ATM

TMN Conceptually Separate Management Network

Lucent Technologies - Proprietary

NM Hierarchical Model Example

Banking Business

ATMCheck Clearing

SNA

Frame Relay Network

X.25

EMS for NCR EMS for Diebold

NCR Diebold

• Business Management Layer (BML)– Goal setting, Finance, Budgeting– Planning product definition

.

.

.

• Service Management Layer (SML)– Customer contact and interface– Quality of Service– Interaction between services

.

.

.

• Network Management Layer (NML)– Connectivity among nodes– Network control and coordination– Network statistical data/reports

.

.

.

• Element Management Layer (EML)– Control of subsets of network elements– Gateway access to network elements– Maintaining statistical log and events

.

.

.

• Network Element Layer (NEL)– Implementation of management commands– Detection of problems


Management Function Areas

• Fault Management

• Configuration Management

• Accounting Management

• Performance Management

• Security Management

FCAPS

Reference: “TMN Management Functions,” ITU-T, M.3400


FCAPS• Fault Management

– Alarm Surveillance– Fault Localization– Fault Correction– Testing– Trouble Administration– Reliability, Availability, &

Survivability (RAS) Quality Assurance

• Configuration Management– Network Planning & Engineering– Installation– Service Planning & Negotiation– Provisioning– Status & Control

• Accounting Management– Tariff/Pricing– Usage Measurement– Collections & Finance– Enterprise Control

• Performance Management– Performance Quality Assurance– Performance Monitoring– Performance Management Control– Performance Analysis

• Security Management– Prevention– Detection– Containment & Recovery– Security Administration

Reference: ”TMN Management Functions,” ITU-T, M.3400


F C A P SF C A P SF C A P S F C A P S F C A P S

T1Mux

RAS T3 Line

F C A P S

F C A P SF C A P S

Frame Relay Network

FRADb c d e f

FCAPSBML

SML

NML

EML

NEL

b c d e f

ag• Logical Layers are implementation-independent

A Total NM Environment

(SNMP) (T7) (SNMP)

MIB

Info

rmat

ion

Mod

el

NM messages NM messages

Protocol-based messages

NM expertise


NM-Layer Characteristics

•Lower Layers are Managed by Upper Layers

•Each Layer manages multiple occurrences of the layer directly below

• Each layer uses network management functions/services of lower layers

• An FCAPS application in a layer may communicate with other FCAPS applications in the same layer (e.g., SONET

applications may talk to ATM applications)


Generic NM Architecture

•Functional Architecture - provides the means to process and transport information

– Function Blocks (packaging FCAPSs, protocol converters, workstation functions)

– Reference Points (Conceptual interfaces between Management Systems)

•Information Architecture - provides an object-oriented approach for management-oriented information exchanges

– Management Information Model (MIBs)

– Manager/Agent Relationship

•Physical Architecture

– Management System Architecture

– Interface Realization


NM Information Architecture

• Based on

– Object-oriented approach for information exchange

Allows for object properties to be extended through “inheritance”

– Manager/Agent concept

Allows for hierarchical exchange of management information

• Perspectives of Management Information

– The management information model (can use GDMO)

Allows for a common data structure in the

managed and managing system

– The management information exchange (can use OSI ASN.1)

Allows for standard description of data structures

• Shared Management Knowledge (SMK) scope

– Integrated Naming and Addressing Scheme for Objects

Human and machine readable

– Object Classes

Allows for extensions to new services/technologies

– Object Attributes/Services

Allows for vendor extensions and options

– Manager/Agent/Objects Relationships

Allows for data abstraction at upper layers

Manager

Agent

Managing

System

Management operations (can use CMIP)Notifications

Managed objects in MIBManaged system

Managed Resources

Resource …. Resource


Where does this take us ?

• Industry will move ahead with layered architecture (NMSs and EMSs are being developed for SDH/SONET equipment)

•Network Management will be Platform-Based and use an increasing number of standard objects (mostly technology-based objects)

•Network Management tools and applications (expertise driven)

•Distributed applications using client/server computing become more prevalent (TMN is designed for client/server architecture)

• Customer network management will be integrated into overall network management (Frame relay and ATM forums have developed standard network interfaces to carriers; M3-ATMF; VPN management)

•SNMP plays a bigger role (OMNIPoint from “Network Management Forum” (NMF) attempts to encompass both carriers and traditional LAN/WAN management)

Reference:

“L. Bernstein”, JNSM, vol. 3, no. 1, 1995

tmn overview

Documents