Ch02-Dimensions.pdf

Network Management Dimensions Network Management This presentation is based on the slides listed in references. Outline Introduction Lifecycle Interoperability Layers Functions Process & Organization Summary 2 Outline Introduction Lifecycle Interoperab...

Network Management Dimensions Network Management This presentation is based on the slides listed in references. Outline Introduction Lifecycle Interoperability Layers Functions Process & Organization Summary 2 Outline Introduction Lifecycle Interoperability Layers Functions Process & Organization Summary 3 Introduction Management dimensions Makes it easier to define a systemic approach to solve network management problems : Network 4 Introduction (cont’d) Important fact: These dimensions are (almost) orthogonal Examples It does not matter which management function The management protocols must be interoperable It does not matter which layer is managed The management functionalities are needed 5 Outline Introduction Lifecycle Interoperability Layers Functions Process & Organization Summary 6 Network Lifecycle 7 Network Lifecycle (cont’d) Planning Forecast user & service needs, equipment selection, topology planning, … Deployment Equipment installation and turn-up, physical setup, wiring, logical setup and initial configuration Operations Service provisioning, SLA guarantee (fault & performance issues), Accounting & Billing, … Decommissioning “Opposite” of deployment, early notification of users if affected, graceful shutdown, cutover of traffic, … 8 Network Management Lifecycle While the “network management” mainly implies the activities in the operation phase However, each step of network lifecycle needs its own management requirements, E.g., Network installation & documentation in “Deployment” Migration planning & implementation in “Decommissioning” phase Moreover, every technology & service has the similar lifecycle in a operational network Network management To manage the network lifecycle Is evolved in the lifecycle as a part of network 9 Outline Introduction Lifecycle Interoperability Layers Functions Process & Organization Summary 10 Management Interoperability NM is a distributed application, hence A central challenge: How are the systems involved in management able to interoperate? Managing systems with managed systems Management applications with each other Requires agreed-upon rules for interactions Standard management interfaces and protocols (Lecture 4, 8, 9, 10) 11 Management Interoperability (cont’d) Aspects of management interoperability 12 Communication Viewpoint NM at the most basic level, is implemented by messages exchanged between managers and agents Connectivity (e.g. IP) is a prerequisite but not sufficient IP connectivity: manager and agent can hear each other Does not mean they speak the same language, or understand each other? Not necessarily! Generally involves a management protocol The “common language” between manager and agent How is a management session established? What underlying transport do you use? How do you authenticate? 13 Communication Viewpoint (cont’d) How do you identify the request you have plus, what parameters are required How do you recognize a response to a request Is a time stamp required plus, what’s the format – there are dozens of them How is the message encoded XML? UTF-8? Who tears down the management session What happens if a response is not received after a certain amount of time 14 Function Viewpoint Describes the services a manager can expect from an agent Basic services Retrieve a piece of information Modify a configuration Initiate an action Receive an event Advanced services (examples) Transaction support: commit and roll back multiple operations as if they were one Event subscription: receive only events of interest Search and filter Communication protocol defines the message that are being exchanged to perform the function Advanced functions are implemented through multiple management primitives 15 Information Viewpoint The context of network management A common terminology between manager and agent Without a common terminology, no management interoperability Model: the actual representation of a data to be managed e.g. a router, a switch, a voicemail application Meta model: the modeling constructs that managed systems is described by it Object oriented: collection of objects Data oriented, table oriented: entries and columns of tables Command oriented: commands and command parameters Standards specifies the meta model Model of MOs of an agent is given by vendor 16 The Role of Standards What to standardize Management messages, encoding of information Functions, parameters, return codes Management information (typically, meta-models) Who? Industry consortia TeleManagement Forum (TMF), DSL Forum, Distributed Management Taskforce (DMTF), … Government-sanctioned bodies ITU-T, ISO, IETF, W3, … … 17 Outline Introduction Lifecycle Interoperability Layers Functions Process & Organization Summary 18 TMN: as an example of layering TMN (Telecommunication Management Network) It is much more then just a network management layering Problem Heterogeneous management systems for heterogeneous technologies Solution Standardized management network with aligned layered management systems for heterogeneous networks Currently Has little commercial relevance Used as reference model An example of comprehensive management framework 19 TMN Layers 20 TMN Layers: Network Element It is a manageable network device It means “the management agent” It provides agent services, mapping the physical/Logical aspects of the equipment into the TMN framework Get management parameters Set management parameters (configuration) Alarm generation … 21 TMN Layers: Element Management Vendor/device specific management functions Hides these differentiations from the Network Management Examples of functions Detection of equipment errors Measuring power consumption & temperature Measuring the resources that are being used Like CPU-time, buffer space, queue length etc. Logging of statistical data Updating firmware Basic configuration primitives … 22 TMN Layers: Network Management Involves with keeping the network running as a whole (end-to-end) To manage the functions related to the interaction/ communication between multiple pieces of equipment Examples of functions Creation of the complete network view Creation of dedicated paths through the network to support the QoS demands of end users Modification of routing tables Monitoring of link utilization Optimizing network performance … 23 TMN Layers: Service Management Is concerned with management of those aspects that may directly be observed by the users of the network Managing the services that the network provides and ensuring those services are running smoothly Service Provisioning and SLA guarantee Examples of functions Quality of Service management (delay, loss, etc.) Accounting Addition and removal of users … 24 TMN Layers: Business Management It is responsible for the management of the whole enterprise It can better be related to strategically and tactical management instead of operational management Examples of functions Billing and invoicing Help desk management Business forecasting Marketing … 25 TMN Layers 26 Considerations Different layers are often handled by different organizations; example? Technical layering can influence how a business is structured and define its business relationships For example, a transport provider might provide physical lines and transmission equipment Network service providers provide voice or data services, using the transmission services of a transport provider The multiple-layer approach is sometimes criticized management solutions consisting of multiple systems each working at a different layer cause an integration difficult, costly system administration 27 Outline Introduction Lifecycle Interoperability Layers Functions Process & Organization Summary 28 Functional Viewpoint Categorization of different management tasks Typically share similar characteristics and requirements Often addressed by the same management applications Can be basis for structure of management organizations Examples of categorization FCAPS (popular in data world) Starting point: Common functions/ purposes of management tools OAM&P (popular in telco world) Starting point: Common structure of organizations running a network Other categorizations are possible E.g., Fulfillment, Assurance, Billing (Telemanagement Forum) E.g., FCAPS + Change Management (IBM) 29 FCAPS: as an example of functions First articulated in ITU-T TMN Reference Model (Lecture 5, 6) Fault management Monitoring networks and services for faults Reacting to faults when they occur Configuration management Physical configuration, e.g. Equipment, line cards, physical connectivity Logical configuration, e.g. Protocol settings, address assignments, numbering plans, … 30 FCAPS (cont’d) Accounting management Account for usage of communication resources & services Metering: Measure what has been consumed by whom at what time Charging: Have the user pay for what has been consumed Performance management Monitoring performance and service levels → (SLA) Detecting performance trends for planning Security management Management of security mechanisms in the network 31 NM Functions in Time Horizon Short-term management In the scale of minute, second or even (near) real-time & automated Network monitoring Fault detection & Performance monitoring Medium-term management In the scale of hour(s) & in conjunction with human interaction Service provisioning, Fault elimination, Performance reporting Long-term management In the scale of weeks or even month, mainly performed by human with software assist Enhance management workflows, future (capacity) planning and strategies 32 Outline Introduction Lifecycle Interoperability Layers Functions Process & Organization Summary 33 Management Organization & Process The nontechnical dimension of network management, including How to organize management? The processes that are required to ensure that networks run smoothly and reliably The function, life cycle, and management dimensions described earlier can provide guidance for organizing management Standard procedures must be established and followed for the network to run smoothly A lack of documented standard operating procedures can cause problems → Inconsistent Network Management Inconsistent service configuration, Inconsistent Troubleshooting,… 34 TOM & eTOM Telecommunication Operation Map Enhanced version: eTOM (Lecture 11) TOM distinguishes three stages in operation (Fulfillment, Assurance, Billing) among other area of management organization Fulfillment ensure that a service order that was received is carried out Turning up any required equipment Performing configuration Reserving resources Assurance – includes all activities ensuring that a service run smoothly after it has been fulfilled Monitoring service for QoS purposes Diagnosing any faults and repairing Billing – making sure that services provided are accounted properly and can be billed to the user 35  Customer Strategy, Infrastructure & Product Operations Strategy & Infrastructure Product Operations Fulfillment Assurance Billing Commit Lifecycle Lifecycle Support & Management Management Readiness Marketing & Offer Management Customer Relationship Management Service Development & Management Service Management & Operations Resource Development & Management Resource Management & Operations (Application, Computing and Network) (Application, Computing and Network) Supply Chain Development & Management Supplier/Partner Relationship Management Enterprise Strategic & Brand Management, Stakeholder & External Disaster Recovery, Management Enterprise Market Research & Relations Management Security & Fraud Planning Advertising Management Research & Financial & Asset Human Resources Development, Enterprise Quality Management Management Technology Management, Process & IT Acquisition Planning & Architecture 36 Outline Introduction Lifecycle Interoperability Layers Functions Process & Organization Summary 37 Relation Between Models 38 Relation Between Functional Models 39 Relation Between Functional Models X: close relation, (X): not close relation, --: very loose relation if at all 40 References Reading Assignment: Chapter 4 of “Alexander Clemm, ‘Network Management Fundamentals’ , Cisco Press, 2007” Alexander Clemm, “Network Management”, Santa Clara University, http://www.engr.scu.edu/~aclemm Woraphon Lilakiatsakun, “Network Management”, Mahanakorn University of Technology, http://www.msit2005.mut.ac.th/msit_media/1_2553/ITEC4611/Lecture/ Thomas Cavaiani, “Network Management”, Biose State University, http://telecomm.itmbsu.net/itm460.fall.2012/index.html Bahador Bakhshi, CE & IT Department, Amirkabir University of Technology, Network Management Slide Presentation. 41