Network Management Dimensions Network Management Spring 2013 Bahador

Network Management Dimensions Network Management Spring 2013 Bahador Bakhshi CE & IT Department, Amirkabir University of Technology 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 solving a network management problem : Network 4

Introduction (cont’d) Ø Important fact: Ø These dimensions are (almost) orthogonal Ø Examples Ø It does not matter witch technology is managed Ø 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 Ø What is normally associated with network management Ø 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 type 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 systems involved in management able to interoperate Ø Managing systems with managed systems Ø Ø Layer 3 connectivity is not sufficient L 7 protocols Management applications with each other Ø Distribute computing issues Ø Requires agreed-upon rules for interactions Ø Standard management interfaces and protocols 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? Ø What if two messages with the same request are received Ø Execute the same request twice, or ignore? Ø 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 Ø Meta model: the modeling constructs at your disposal to define the model by which the managed system is referred to Ø Object oriented: collection of objects Ø Data oriented, table oriented: entries and columns of tables Ø Command oriented: commands and command parameters Ø Model: the actual representation of a type of managed system e. g. a router, a switch, a voicemail application Ø Standards specifies the meta model Ø Model of MOs of an agent is given by vendor 16

The Role of Standards Ø Goal: align the way in which things are managed Ø It’s all about interoperability Ø Not an issue if you only manage a single type of thing, but: Different vendors, Different device types, Different OS Ø More easily manage different devices Ø Less time, cost to integrate Ø Ø What to standardize Ø Management messages, encoding of information Ø Functions, parameters, return codes Ø Management information (typically, meta-models) 17

NM Standardization Bodies Ø Numerous standards bodies, sometimes competing Ø Industry consortia Ø Companies serving a common market interest Ø Tele. Management Forum (TMF), DSL Forum, Desktop Management Taskforce (DMTF), … Ø Professional organizations Ø Members are individuals of a profession Ø IEEE, … Ø Government-sanctioned bodies Ø ITU-T, ISO, IETF, W 3, … 18

Outline Ø Introduction Ø Lifecycle Ø Interoperability Ø Layers Ø Functions Ø Process & Organization Ø Summary 19

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 management systems for heterogeneous networks Ø Ø Currently Ø Has little commercial relevance Ø Used as reference model Ø An example of comprehensive management framework 20

TMN Layers 21

TMN Layers: Network Element Ø It is a manageable network device Ø It means “the management agent” Ø It provides agent services, mapping the physical aspects of the equipment into the TMN framework Ø Get management parameters Ø Set management parameters (configuration) Ø Alarm generation Ø… 22

TMN Layers: Element Management Ø Vendor 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 Ø … Ø 23

TMN Layers: Network Management Ø To manage the functions related to the interaction between multiple pieces of equipment Ø Involves with keeping the network running as a whole (endto-end) Ø Examples of functions Ø Creation of the complete network view Ø Creation of dedicated paths through the network to support the Qo. S Ø Ø Ø demands of end users Modification of routing tables Monitoring of link utilization Optimizing network performance Detection of faults … 24

TMN Layers: Service Management Ø Is concerned with management of those aspects that may directly be observed by the users of the network Ø These users may be end users (customers) but also other service providers Ø 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 Ø Address assignment 25

TMN Layers: Business Management Ø It is responsible for the management of the whole enterprise Ø It can better be related to strategical and tactical management Ø instead of operational management Ø Examples of functions Ø Billing and invoicing Ø Help desk management Ø Business forecasting Ø … 26

TMN Layers 27

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 28

Outline Ø Introduction Ø Lifecycle Ø Interoperability Ø Layers Ø Functions Ø Process & Organization Ø Summary 29

Functional Viewpoint Ø Categorization of different management tasks Ø Typically share similar characteristics and requirements Ø Often addressed by 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 (former IBM) 30

FCAPS: as an example of functions Ø First articulated in ITU-T TMN Reference Model Ø Popular in datacomm world Ø Fault Ø Configuration Ø Accounting Ø Performance Ø Security 31

Fault Management Ø Functions related to dealing with faults in network Ø Monitoring networks and services for faults Ø Reacting to faults when they occur Ø Managing resolution of faults Ø Being proactive about preventing faults before they occur Ø Important fault management functions Ø Alarm management Ø Fault diagnosis Ø Trouble ticketing Ø Proactive fault management 32

Configuration Management Ø Functions related to dealing with how network, services, devices are configured Ø Physical configuration, e. g. Equipment, line cards, physical connectivity Ø Logical configuration, e. g. Ø Protocol settings, logical interfaces, address assignments, numbering plans, … Ø Ø Important configuration management functions Ø Inventory Ø Auditing, Discovery, Auto-discovery Ø Synchronization Ø Image management Ø Backup and restore 33

Configuration Management: Provisioning Ø Provisioning: The steps required to set up network and system resources to provide, modify, or revoke a network service “Resources”: Ø Bandwidth, CPU, Memory, Port assignments, Address assignments (IP addresses, phone numbers, . . ), … Ø Scope: Ø Individual systems (“equipment provisioning”) E. g. set up a firewall Ø Systems across a network (“service provisioning”) Ø Ø Coordinated configuration changes across multiple systems Ø Often required to provide an end-to-end service 34

Accounting Management Ø Account for usage of communication resources and services Ø Metering: Measure what has been consumed by whom at what time Ø Charging: Have the user pay for what has been consumed Ø Often forgotten but arguably the most important function area of all Ø No accounting management, no revenue Ø Even as a user need to know what you pay for 35

Performance Management Ø Performance management tasks Ø Monitoring performance and service levels Ø Detecting performance trends, degradations Ø Tuning network for performance Ø Common support functions Ø Performance measurements Accuracy, calibration, sampling considerations as common issues Ø Collection of performance data Ø Often, large volumes of data Ø Sampling as a common technique to address scale concerns Ø Visualization of large data sets Ø Ø Charts, histograms, etc 36

Security Management Ø Management of security mechanisms, e. g. Ø ACL management Ø Consistency between routers on a network Ø Size of ACLs Ø Intrusion detection systems Ø Learning of patterns Ø How to protect against hitherto unknown patterns Ø System security, anti-virus, … 37

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 38

Outline Ø Introduction Ø Lifecycle Ø Interoperability Ø Layers Ø Functions Ø Process & Organization Ø Summary 39

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 because of: Inconsistent configurations, Troubleshooting problems that arise as a result of inconsistencies, … 40

TOM & e. TOM Ø Telecommunication Operation Map Ø Enhanced version: e. TOM Ø TOM distinguishes among three life cycle stages – FAB (Fulfillment, Assurance, Billing) Ø 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 Qo. S purposes Ø Diagnosing any faults and repairing Ø Billing – making sure that services provided are accounted properly and can be billed to the user 41

Customer Operations Strategy, Infrastructure & Product Strategy & Commit Infrastructure Lifecycle Management Product Lifecycle Management Operations Support & Readiness Fulfillment Assurance Marketing & Offer Management Customer Relationship Management Service Development & Management Service Management & Operations Resource Development & Management (Application, Computing and Network) Resource Management & Operations (Application, Computing and Network) Supply Chain Development & Management Supplier/Partner Relationship Management Enterprise Management Strategic & Enterprise Planning Brand Management, Market Research & Advertising Financial & Asset Management Human Resources Management 42 Stakeholder & External Relations Management Research & Development, Technology Acquisition Billing Disaster Recovery, Security & Fraud Management Enterprise Quality Management, Process & IT Planning & Architecture

Outline Ø Introduction Ø Lifecycle Ø Interoperability Ø Layers Ø Functions Ø Process & Organization Ø Summary 43

Relation Between Models 44

Relation Between Functional Models 45

Relation Between Models Ø X: close relation, (X): not close relation, --: very loose relation if at all 46

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. msit 2005. mut. ac. th/msit_media/1_2553/ITEC 4611/Lecture/ Ø Thomas Cavaiani, “Network Management”, Biose State University, http: //telecomm. itmbsu. net/itm 460. fall. 2012/index. html 47