1 / 62

NETWORK MANAGEMENT

NETWORK MANAGEMENT. Course Supervisor MUHAMMAD KHALID KHAN. Do you really want good marks? Invest at-least 200 hours on this course. Any thing less may result in some thing that most probably you would not LIKE. 120 hours for the course-work and 80 hours for the project. Course Material.

winter-shannon
Télécharger la présentation

NETWORK MANAGEMENT

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. NETWORK MANAGEMENT Course Supervisor MUHAMMAD KHALID KHAN

  2. Do you really want good marks? • Invest at-least 200 hours on this course. Any thing less may result in some thing that most probably you would not LIKE. • 120 hours for the course-work and 80 hours for the project.

  3. Course Material Books: Network Management, Principles and Practices By Mani Sobramanian Reference Books: Network Management, A Practical Perspective By Allan Leinwend and Karen Fang SNMP, SNMPv2 and CMIP, The Practical Guide to Network Management Standards By William Stallings

  4. Marks Distribution • Hourly: 30 (n-1) • Sessional: 30 • Project: 15 • Quizzes: 10 • Assignment: 5 • Final: 40 ANY QUESTION

  5. Telephone Network • Characteristics: • Reliable - does what is expected of it • Dependable - always there when you need it. (remember 911?) • Good quality (connection) - hearing each other well • Reasons: • Good planning, design, and implementation • Good operation and management of network

  6. Telephone Network Model

  7. Telephone Network • Notice the hierarchy of switches • Primary and secondary routes programmed • Automatic routing • Where is the most likely failure? • Use of Operations Systems to ensure QoS

  8. Operations Systems / NOC • Monitor telephone network parameters • S/N ratio, transmission loss, call blockage, etc. • Real-time management of network • Trunk (logical entity between switches) maintenance system measures loss and S/N. Trunks not meeting QoS are removed before customer notices poor quality • Traffic measurement systems measure call blockage. Additional switch planned to keep the call blockage below acceptable level • Operations systems are distributed at central offices • Network management done centrally from Network Operations Center (NOC)

  9. Data and Telecommunication Network

  10. Data and Telecommunication Network • Computer data is carried over long distance by telephone (telecommunication network) • Output of telephone is analog and output of computers is digital • Modem is used to “modulate” and “demodulate” computer data to analog format and back • Clear distinction between the two networks is getting fuzzier with modern multimedia networks

  11. IBM SNA Architecture

  12. IBM SNA Architecture • IBM System Network Architecture (SNA) is a major step in network architecture • SNA is based on multitude of (dumb) terminals accessing a mainframe host at a remote location

  13. DCE with LAN DCE.. Distributed Computing Environment

  14. DCE with LAN • Driving technologies for DCE: • Desktop processor • LAN • LAN - WAN network

  15. LAN-WAN network

  16. LAN-WAN network • Major impacts of DCE: • No more monopolistic service provider • No centralized IT controller • Hosts doing specialized function • Client/Server architecture formed the core of DCE network

  17. Client/Server Model • Post-office analogy; clerk the server, and the customer the client • Client always initiates requests • Server always responds • Notice that control is handed over to the receiving entity.

  18. Client/Server Examples

  19. Client/Server Examples

  20. TCP/IP Based Networks • TCP/IP is a suite of protocols • Internet is based on TCP/IP • IP is Internet protocol at the network layer level • TCP is connection-oriented transport protocol and ensures end-to-end connection • UDP is connectionless transport protocol and provides datagram service • Internet e-mail and much of the network mgmt. messages are based on UDP/IP • ICMP component (used in ping) of TCP/IP suite

  21. Architecture, Protocols and Standards • Communication architecture • Modeling of communication systems, comprising • functional components and • operations interfaces between them • Communication protocols • Operational procedures • intra- and inter-modules • Communication standards • Agreement between manufacturers on protocols of communication equipment on • physical characteristics and • operational procedures

  22. Communication Architecture

  23. Communication Architecture

  24. Communication Architecture • Inter-layer interface: user and service provider • Peer-layer protocol interface • Analogy of hearing-impaired student • Role of intermediate systems • Gateway: Router with protocol conversion as gateway to an autonomous network or subnet

  25. OSI Reference Model

  26. OSI Reference Model

  27. OSI Reference Model

  28. PDU Communication Model

  29. Network Management • Network management is the process of controlling a complex data network to maximize its efficiency and productivity • The overall goal of network management is to help with the complexity of a data network and to ensure that data can go across it with maximum efficiency and transparency to the users

  30. Network Management and it’s Functional Grouping Network Network Network Provisioning Operation Maintenance Planning Fault Management Network Installation Design Configuration Management Network Repairs Performance Management Network Test Security Management Trouble-shooting Accounting Management

  31. Typical Network Management System

  32. Network Management Objectives At first glance and without starting a complex research, as network end-users, it is obvious that we expect fast, secure and reliable connections, as network manager we would like to easily configure and control network access and resources, and as corporate manager we expect a low usage cost. • Controlling Corporate strategic assets: Networks and distributed computing resources are increasingly vital resources for most organizations. Without effective control, these resources do not provide the pay-back that corporate management requires.

  33. Network Management Objectives • Controlling complexity: The continued growth in the number of network components, end users, interfaces, protocols, and vendors threatens management with loss of control over what is connected to the network and how network resources are used. • Improving services: End users expect the same or improved service as the information and computing resources of the organization grow and distribute.

  34. Network Management Objectives • Balancing various needs: The information and computing resources of an organization must provide a spectrum of end users with various applications at given levels of support, with specific requirements in the areas of performance, availability, and security. The network manager must assign and control resources to balance these various needs. • Reducing down-time: As the network resources of an organization become more important, minimum availability requirement approach 100 percent. In addition to proper redundant design, network management has an indispensable role to play in ensuring high availability of its resources. • Controlling costs: Resource utilization must be monitored and controlled to enable essential end-user needs to be satisfied with reasonable cost.

  35. Network Management • The International Organization for Standardization (ISO) Network Management Forum divided network management into five functional areas: • Fault Management • Configuration Management • Security Management • Performance Management • Accounting Management

  36. Fault Management • Is the process of locating problems, or faults, on the data network • It involves the following steps: • Discover the problem • Isolate the problem • Fix the problem (if possible)

  37. Configuration Management • The configuration of certain network devices controls the behavior of the data network • Configuration management is the process of finding and setting up (configuring) these critical devices

  38. Security Management • Is the process of controlling access to information on the data network • Provides a way to monitor access points and records information on a periodic basis • Provides audit trails and sounds alarms for security breaches

  39. Performance Management • Involves measuring the performance of the network hardware, software, and media • Examples of measured activities are: • Overall throughput • Percentage utilization • Error rates • Response time

  40. Accounting Management • Involves tracking individual’s utilization and grouping of network resources to ensure that users have sufficient resources • Involves granting or removing permission for access to the network

  41. Network Management Protocols • A simple protocol defines common data formats and parameters and allows for easy retrieval of information • A complex protocol adds some change capability and security • An advanced protocol remotely executes network management tasks

  42. Network Management Protocols • So where is technology today? • The most common protocols are: • SNMP (Simple Network Management Protocol) • SNMPv2 (SNMP version 2) • CMIS/CMIP (Common Management Information Services/Common Management Information Protocol) • RMON (Remote Monitoring)

  43. Network Management Protocols • SNMP is beyond the simple protocol with adequate monitoring capabilities and some change capabilities • SNMPv2 greatly enhances the SNMP feature set • CMIP approaches the advanced tool, but implementation issues have limited its use

  44. Network Management Protocols • These protocols do not state how to accomplish the goals of network management • They give methods to monitor and configure network devices • The challenge to analyze the information in an effective manner rests with software engineers who write network management applications

  45. Network Management Platform • Historically, network management revolved around multiple systems, each managing one specific set of components on the data network • Restrictions of money, physical space, and technical expertise led to the desire to have the components managed by a single system that would show their interconnections on a network map

  46. Network Management Platform • A network management platform is a software package that provides the basic functionality of network management for different network components • The goal for the platform is to provide generic functionality for managing a variety of network devices

  47. Network Management Platform • Basic features for any platform to include are: • Graphical User Interface (GUI) • Network Map • Database Management System (DBMS) • Standard Method to Query Devices • Customizable Menu System • Event Log

  48. Network Management Platform • Additional features for a platform include: • Graphing Tools • Application Programming Interface (API) • System Security

  49. Network Management Platform • Management Platforms that exist today • Sun’s SunNet Manager • HP’s OpenView • IBM’s Netview for AIX • Cabletron’s Spectrum

  50. Network Management Architectures • The Network Management Platform can use various architectures to provide functionality • The 3 most common are: • Centralized • Hierarchical • Distributed

More Related