1 / 12

TMN Overview

TMN Overview. Telecommunications Management Network Shervin Erfani. Customer 1. Exchange Carrier. Local Carrier. Customer 2. Present Network Management Environment. ?. EMS (?). EMS. NMS. NMS. EMS. SNMP. SNMP. TL1. Proprietary. Terminal Server. Frame Relay

aysha
Download Presentation

TMN Overview

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. TMN Overview Telecommunications Management Network Shervin Erfani

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

  3. 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)

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

  5. NM Hierarchical Model Example Banking Business • 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 Check Clearing ATM SNA Frame Relay Network X.25 EMS for NCR EMS for Diebold NCR Diebold

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

  7. 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 FCAPS Reference: ”TMN Management Functions,” ITU-T, M.3400

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

  9. 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)

  10. 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

  11. Managing System Manager Management operations (can use CMIP) Notifications Agent Managed objects in MIB Managed system …. Resource Resource Managed Resources 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

  12. 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 (OMNIPointfrom “Network Management Forum” (NMF)attempts to encompass both carriers and traditional LAN/WAN management) • Reference: • “L. Bernstein”, JNSM, vol. 3, no. 1, 1995

More Related