TMN Overview Telecommunications Management Network Shervin Erfani Lucent

Present Network Management Environment Customer 1 EMS (? ) EMS Exchange Carrier NMS EMS

Managing Network Management • What is structured approach to NM? An organized architecture for

Network Management in the TMN Environment Conceptually Separate Management Network TMN Management System Data

NM Hierarchical Model • Banking Business Management Layer (BML) – – Example Goal setting,

Management Function Areas • Fault Management • Configuration Management • Accounting Management FCAPS •

FCAPS • Fault Management – – – • • Performance Management – – •

A Total NM Environment FCAPS BML Information Model F C A P S Protocol-based

NM-Layer Characteristics • Lower Layers are Managed by Upper Layers • Each Layer manages

Generic NM Architecture • Functional Architecture - provides the means to process and transport

NM Information Architecture • Based on – Object-oriented approach for information exchange Allows for

Where does this take us ? • Industry will move ahead with layered architecture

Slides: 12

Download presentation

TMN Overview Telecommunications Management Network Shervin Erfani Lucent Technologies - Proprietary

Present Network Management Environment Customer 1 EMS (? ) EMS Exchange Carrier NMS EMS TL 1 Proprietary Frame Relay Network T 1 -Fractional T 1 Network Router Ring Router ? Customer 2 SNMP Terminal Server Local Carrier Host • 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 Lucent Technologies - Proprietary 2

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) Lucent Technologies - Proprietary 3

Network Management in the TMN Environment Conceptually Separate Management Network TMN Management System Data Communication Network (DCN) Terminal Server Router Frame Relay Workstation ATM Router Telecommunications network Lucent Technologies - Proprietary • Interconnection of service providers and user management infrastructures 4

NM Hierarchical Model • Banking Business Management Layer (BML) – – Example Goal setting, Finance, Budgeting Planning product definition . . . • Service Management Layer (SML) – – – Check Clearing Customer contact and interface Quality of Service Interaction between services ATM . . . • Network Management Layer (NML) – – – SNA Connectivity among nodes Network control and coordination Network statistical data/reports Frame Relay Network . . . • Element Management Layer (EML) – – – Control of subsets of network elements Gateway access to network elements Maintaining statistical log and events . . . • X. 25 EMS for NCR EMS for Diebold Network Element Layer (NEL) – – Implementation of management commands Detection of problems Lucent Technologies - Proprietary NCR Diebold

Management Function Areas • Fault Management • Configuration Management • Accounting Management FCAPS • Performance Management • Security Management Reference: “TMN Management Functions, ” ITU-T, M. 3400 Lucent Technologies - Proprietary 6

FCAPS • Fault Management – – – • • Performance Management – – • Configuration Management – – – • Alarm Surveillance Fault Localization Fault Correction Testing Trouble Administration Reliability, Availability, & Survivability (RAS) Quality Assurance Network Planning & Engineering Installation Service Planning & Negotiation Provisioning Status & Control Performance Quality Assurance Performance Monitoring Performance Management Control Performance Analysis Security Management – – Prevention Detection Containment & Recovery Security Administration Accounting Management – – Tariff/Pricing Usage Measurement Collections & Finance Enterprise Control Reference: ”TMN Management Functions, ” ITU-T, M. 3400 Lucent Technologies - Proprietary 7

A Total NM Environment FCAPS BML Information Model F C A P S Protocol-based messages F C A P S b c (SNMP) b F C A P S NML NM messages RAS SML F C A P S d e (T 7) T 1 Mux F C A P S f (SNMP) c T 3 Line d Frame Relay Network e FRAD f MIB a EML NEL • Logical Layers are implementation-independent g Lucent Technologies - Proprietary NM expertise 8

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) Lucent Technologies - Proprietary 9

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 Lucent Technologies - Proprietary 10

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 Managing Manager System managed and managing system – The management information exchange (can use OSI ASN. 1) Notifications Management operations (can use CMIP) Allows for standard description of data structures • Shared Management Knowledge (SMK) scope Agent – Integrated Naming and Addressing Scheme for Objects Human and machine readable – Object Classes Allows for extensions to new services/technologies – Object Attributes/Services Managed objects in MIB Managed system Resource …. Resource Allows for vendor extensions and options – Manager/Agent/Objects Relationships Managed Resources Allows for data abstraction at upper layers Lucent Technologies - Proprietary 11

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; M 3 -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 Lucent Technologies - Proprietary 12