1 / 30

Telecommunications Network Management Systems Overview

Understand TMN layered architecture, management requirements, ISO functional areas, and network element activities for effective network management.

dwebber
Download Presentation

Telecommunications Network Management Systems 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. Introduction Prof. Choong Seon HONG

  2. TMN (Telecommunications Management Network) • TNM Layering Concept • BML (Business Management Layer) : • Goal setting, finance, budgeting • Planning product definition • agreements between jurisdictions (domains) • SML (Service Management Layer) : • contacts with customers and with other service providers • identification of customer access to network • reporting service usage for billing • maintaining and reporting quality of service data • NML (Network Management Layer) : • wider geographical area than EML • complete visibility of the whole network, nodes and links

  3. TMN (2) • Control and coordination of the network view of all NEs within its scope or domain • provision, cessation, or modification of network capabilities for the support of service to customers • maintenance of statistics and history pertaining to circuits, etc. • EML (Element Management Layer) • control and coordination of a subnet of NEs on an individual basis • control and coordination of a subnet of NEs on a collective basis (carrier system, ring, etc) • Provisioning a gateway to NEs for the NML and higher layers • maintenance of statistics and history pertaining to individuals NEs

  4. TMN(3) • Network Element Layer • telecommunication activities of the resource components of NEs • implementations of management commands • detection of problems (potential alarm events, severe error seconds, etc.) • autonomous activities (protection switching, diagnostics, etc.)

  5. TMN Layered Architecture Business Management Layer Service Management Layer Network Management Layer Element Management Layer Network Element

  6. Network management requirement • ISO Management Functional Areas (FCAPS) • Fault management : detection, isolation, and correction of abnormal operation • Accounting management : charging for using managed objects • Configuration : initialization and control for providing services • Performance management : evaluation of behavior of managed objects • Security management : addressing OSI security and protection managed objects • Fault management • Localization • Isolating the rest of network for the failure • reconfigure or modify the network to minimize the impact of operation without the failed component(s). • Repair or replace the failed components • Fault (abnormal condition) vs Error (a single event)

  7. Network management requirement (2) • User requirements • Immediate notification • Requiring rapid and reliable fault detection • Fast and reliable problem solution • Use of redundant components for meeting fault-tolerant requirement • Problem tracking and control : reassurance of correct network operation and confidence test • Accounting Management • Charge for the use of network services • Tracking the use of network resources • Improving performance • Planing for network growth • User requirements • Network manger needs to be able to specify the kinds of accounting information to be recorded at various nodes • Desired interval between sending the recorded information to higher-level management nodes. • Authorization to access and manipulate for charging information

  8. Network management requirement (3) • Configuration management • Initialization of networks • Shutting down part or all of the network • Maintaining, adding, and updating the relationship between components and status of components • User requirements • Start-up and shut-down operations on networks • Maintaining default configuration attributes • Reconfiguration of network caused by performance evaluation or network upgrade, fault recovery or security checks • Informing changes in network configuration • Performance Management • Monitoring : tracking activities on the network • Controlling : adjustments to improve network performance

  9. Network management requirement (4) • Performance Issues • Level of capacity utilization • Excessive traffic • Throughput • Bottlenecks • Response time • User requirements • Average and worst case response times and reliability of network • Performance statistics --> appropriate corrective action, capacity planning • Security Management • Managing information protection and access control facilities • Generating, distributing, and storing encryption keys • Logging access history and examining audit records

  10. Network Management Systems • Network management entity (NME) • Collecting statistics on communications and network-related activities • Storing statistics locally • Responding to command from the network control center : • sending statistics information to network center • changing parameter • providing status information • generating artificial traffic to perform a test • Sending local status when undergoing significant change • Manager/agent

  11. NMA NME Appl Comm OS NME Appl Comm OS NME Comm OS NME Appl Comm OS Network Management Systems (2) Network Control Host (manager) Server (agent) Router (agent) Workstation (agent) NMA : Network Mgmt Application NME : Network Mgmt Entity Appl : Application Comm : Communication Software OS : Operating System

  12. Network Management Systems (2) • Several observation • Network management software for single vendor’s equipment --> multi-vendor • Dual network management system • Network management software architecture • User presentation software • Network management software • Communication and database support software • Architecture model of a network management system • Network management applications : FCAPS • Application elements : generating alarm, summarizing data • Network management data transport service : transfer protocol, service interface (GET, SET, Notify, etc)

  13. Unified User Interface Presentation of network management information to users Network management application Network management application Application element Application element Application element Network management data transport service MIB access module Communications protocol stack MIB Managed network Architecture model of a network management system

  14. MIB (Management Information Base) • Local MIB at agent • Reflecting the configuration and behavior of the node • Containing parameters to be used to control the operation of the node • Local MIB at manager • Node specific information and summary information about agent • MIB access module • Basic file management software that enables access to the MIB • MIB format conversion to standard

  15. Distributed Network Management • Motivation • Proliferation of low-cost, high-power PCs and workstations • Proliferation of departmental LAN • Need for local control and optimization of distributed applications • Benefits • Minimization of network management traffic overhead • Greater scalability : adding additional management capability • Eliminating the single point of failure that exists with centralized schemes

  16. Management Clients (PCs, workstations) Network Management server Management server MIB MIB Management application Management application Network Element manager Element manager Network resources (servers, routers, hosts) with management agents Typical distributed management system architecture

  17. Proxy management architecture • Enabling a management application to manage a proprietary resource through standard operations and event reports which are translated by the proxy system into proprietary operations and event reports Management application Proxy manager Proprietary management interface Client stub Server stub Client proxy stub Server proxy stub Protocol stack Protocol stack Protocol stack Protocol stack Standard operations and event reports Proprietary operations and event reports

  18. Why Manage Networks? • What is “Network Management”? • Network resources • each resource supports more than one user • hubs, switches, routers, WAN devices • Goal • Access (within organizational policy restrictions) to any of the network resources at any time

  19. Why Manage Networks? • A Network is NETWORK NODE USER DEVICE (CPE) Network Node Interface User Network Interface

  20. Why Manage Networks? • PSTN (Public Switched Telephone Network) • Local exchange switch (Network node) • Telephone (User device) • Local loop (User network interface) • Trunk (Network node interface) • Internet • Router (Network node) • PC or server (User device) • Modem or leased line (User network interface) • Leased line (Network node interface) • ATM (Asynchronous Transfer Mode) • ATM switch (Network node) • Router or PC (user device) • UNI (User network interface) • NNI (Network node interface)

  21. Why Manage Networks? • History of PSTN • Telegraph (Samuel Morse, 1838) • at home/office • faster • one message at a time • Telephone (Alexander Graham Bell,1876) • PSTN Service Carriers • LATA (Local Access and Transport Areas) • IXC (Inter-exchange Carriers) • LEC (Local Exchange Carriers) • Telecommunications Act (1996) • CLEC (Competitive LEC) • ILEC (Incumbent LEC) • POP (Point of Presence) • Toll

  22. IXC IXC B IXC IXC IXC A IXC IXC IXC IXC LATA 2 LATA 1 LATA 3 POP POP POP POP LE LE Toll Toll Toll LE LE LE LE LE LE LE LE LEC A (RBOC) LEC B (RBOC) LEC C (Independent) Why Manage Networks? • PSTN Today (U.S.A.) such as AT &T, MCI, Sprint

  23. Why Manage Networks? • Increasing loads and trunks phone Local loops Local loops phone phone phone phone phone Trunk phone phone Central Office Switch Central Office Switch phone phone ? ? phone phone phone phone phone phone RTR PC INTERNET ISP

  24. Why Manage Networks? • History of Internet • 1969: creating ARPANET • 1973: Connecting to UK and Norway ARPANET • 1983: separating MILNET for Military • 1985: Incorporating BITNET (educational Net) • 1988: Incorporating into NSFNET • 1990: Terminating ARPANET • 1992: Creating Internet Society • 국내 발전 과정 • HANA망, KREN(서울대), KREOnet(과학기술원)으로 망 구축 • 1983: UUCP로 미국과 연결 • 1984: X.25를 이용 유럽과 연결 • 1988: KREN이 BITNET과 연결 • 1990: HANA망이 인공위성을 통해 Hawaii 대학과 연결 • 1993: 한국통신이 Internet 접속 서비스 개시

  25. 전화 IXC POP Home A PC Local Exchange Tandem Switch 전화 ISP POP Home B Trunk groups: two 64 kbps channels (CIRCUIT SWITCHING) PC 전화 IXC POP Home A PC Local Exchange Tandem Switch ISP POP 전화 Home B Unchannelized trunk of 128 kbps (PACKET SWITCHING) PC Why Manage Networks? • Circuit Switching vs Packet Switching

  26. Why Manage Networks? • Internet Today NAP NAP NAP NAP LARGE ISP LARGE ISP LARGE ISP S S c S c c c c Regional ISP Regional ISP Regional ISP Region ISP S S S c c c c c Local ISP Local ISP Local ISP Local ISP S c c c c c c c c c

  27. Dedicated Cable Dial XDSL Why Manage Networks? • Internet Topology (Internet Service Provider) Access Network Backbone Network Leased Line Frame Relay ATM 기업 가입자 가정 가입자 전용선 Frame Relay X.25 PSTN ISDN ADSL CATV 56K~45M 56K~2M ~56K ~56K ~128K 1M ~ 8M 10 ~ 30M

  28. Why Manage Networks? • Leased lines • dedicated services (non-switched) Digital cross connect (DACS) private line (non-switched) services Private line data PSTN switch (switched services) MDF (Main distribution frame) - wire center Trunk transport system (e.g. T3) Access lines Trunk group Analog or ISDN dial-up modem data

  29. Why Manage Networks? Global-one(T2) MCI(T2) MCI(T1) CHT (512K) UUNET(20Mbps) KDD(E1) NETVALLEY ST (E1) BBN(T3) KOSINet ELIMNET KORNET 나우콤(T1) Sprint (T3) PUBNET Imnet(256K) SDSNET 하이텔(T1) 100Mbps MCInet(E1) KREN 천리안(T1) CHANNEL-I T3 MCInet(T2) GIX(T1) KREONet Uunet(E1*2) KIX KT-IX AUNET(T1) NETSGO Uunet(E1*4) AUNET AT&T(T1*5) Dacom-IX IX-Seoul UNITEL Sprint (T1*4) HIMAGIC KDD(6M) 유니텔 KOTISnet LAN HKT(512K) BORANET MCInet(T3) KOTIS Telstra(2M) HANQ NEXTEL CT(128K) LAN LAN CHT(128K) SHINBIRO BBN(KT-IX) T2 천리안 KOLnet ST(256K) NowNET KTNET EYES INET MCInet(T2*2) HITEL Uunet(T3) 나우누리 MCI(T1) Uunet(E1) Digital Island (T3) ABONE(T1) BBN(E1) Uunet(T1*2)

  30. Why Manage Networks? • Inside the ISP PSTN Internet NAP or other ISP Terminal servers Router IDS Firewall Mail and News server Other servers Content servers Firewall

More Related