Introduction to Network Management

1. Introduction to Network Management

2. Objective of this chapter • Introduction to Network Management • Presents a brief overview of network management. • Network Management Architectures • Provides a brief overview of the common components of network management architectures. • components of network management system (NMS) • Open System Interconnection (OSI) Network Management Model • Introduces the ISO OSI network management model. chap 1: NMS

3. Definition

4. Definition

5. Network Management?

6. Function of Network Management • Designed to simplify the operation of large internetworks. This includes: • control corporate strategic assets from a central position • aids in strategically planning for network growth. • ? • operate independently of the system it monitors • support multiple protocols • operate as transparently as possible • improve services - maintaining network stability, tuning network performance, • balance various needs, including applications, systems and technologies • troubleshooting problems that might arise. • ? • ? chap 1: NMS

7. Challenges • Automated processes • Repetitive tasks can be performed reliably and predictably by automated processes. • Integration across diverse network environments (heterogeneous networks) • Management capabilities can be made available in geographically dispersed environments or in networks using multiple protocols or platforms. chap 1: NMS

8. Challenges (2) • ? • Constant monitoring alerts network administrators to problems quickly. • ? • Tracking past problems makes finding solutions easier, while recording values for performance, availability, and other areas can uncover trends that might affect future growth. chap 1: NMS

9. Network Management System (NMS) • A typical model of network management systems consists of • ?-- the central controller • ?-- network devices like routers and gateways which interconnect sub-networks • a protocol for communications, such as SNMP, between network devices and the controller, and • a set of parameters to be monitored and controlled chap 1: NMS

10. Components of NMS • Network management station • Managed Device • agent • management database • ? chap 1: NMS

11. CiscoWorks for Windows Health Monitor Configuration Builder Show Commands CiscoView HP OpenView for Windows network management platform Windows with WINSOCK compliant TCP/IP stack Network Management Station Network Management Platform and Applications • The NM station is a computer system that contains software processes known as management entities. • ? • should be installed with a network management platform (protocol) such as HP OpenView, SUN SuNet Manager, IBM NetView. • normally, network management application tools are also required, such as CiscoWorks chap 1: NMS

12. Network Management Station (2) • Management entities poll agents in managed devices (automatically or by user request) to check the values of certain variables. • Management entities also react to alerts from managed devices by executing one or more actions, such as notifying the network administrator, performing event logging, shutting down a system, or attempting system repairs. Network Management Protocols Management Station Network Devices request write MIB replies, trap read chap 1: NMS

13. MIB MIB Network Management Interactions • ? • network management station NMS queries each network devices ND periodically, so, consumes more bandwidth. • NMS sends ‘request’ message to NDs to get status information or set operation parameters (MIB variables) • network devices return ‘reply’ message carrying status information (MIB variables) • ? • Traps -- network devices generate warning messages when a critical threshold is reached • NMS log/record alarm messages and alert the network engineers • event-triggered, so, consumes little bandwidth request replies trap chap 1: NMS

14. Managed Devices • Managed devices • Managed devices are systems that fall under the control of an NMS. • Managed devices contain software modules called agents. • Agents compile and store information about the managed device in a management database and provide this information (proactively or reactively) to the NMS. • Agents define the parameters that an NMS can monitor or configure chap 1: NMS

15. Common NM Protocols • Simple Network Management Protocol (SNMP) • SNMP is a protocol that facilitates exchange of management information between network devices, primarily in TCP/IP environments. • In 1988, the Internet Activities Board IAB committee proposed the SNMP as the short-term solution for network management. • Since then, the simple structure and good performance of SNMP has make it popular around the world. It is likely that SNMP will be a long-term solution. • Remote Monitor (RMON) • RMON is a standard monitoring specification for exchanging network monitoring data. • Common Management Information Protocol (CMIP) • An OSI network management protocol created and standardized by ISO for the monitoring and control of heterogeneous network. chap 1: NMS

16. Network Management Architecture

17. NM Architectures & model • Most network management architectures are implemented using similar structures and sets of relationships. • Three network management architecture • Centralized • Distributed • Hierarchical • Regardless the NM architecture, there are two basic components in a typical network management environment: • Managed devices • a network host with an agent • Network Management System (NMS) • for example: HP OpenView chap 1: NMS

18. MIB MIB MIB Centralized Architecture • all queries are sent to a single management system • applications are installed on the central NMS • responds to trap messages sent from managed nodes • strength • ? • ideal for small to medium-size networks • weakness • NMS can easily be overburdened • NMS may be bombarded by numerous traps send from managed nodes NMS Agent Agent Agent chap 1: NMS

19. MIB MIB MIB MIB MIB MIB Distributed Architecture • at least two peer NMS • distributed architecture is usually for networks in different places (geographically) • strength • not be overburnded • suitable for medium to large-sized networks • ? • provide fault-tolerant • NMS can poll managed nodes on other areas NMS NMS Agent Agent Agent Agent chap 1: NMS

20. MIB MIB MIB MIB MIB MIB Hierarchical Architecture • combine a centralized system with a distributed system • most complex architecture • suitable for large and complex network configuration • Strength • ? Centralized NMS NMS NMS Agent Agent Agent Agent chap 1: NMS

21. ISO-OSI Network Management Model also known as FCAPS model

22. Open System Interconnection (OSI) NM Model • The Open System Interconnection (OSI) network management model provides a broad framework for network management implementations. • The model is specified by the International Organization for Standardization (ISO) Security Accounting Fault Performance Configuration chap 1: NMS

23. OSI NM Model • The OSI network management model divides network management into five key areas: • Also known as FCAPS model • fault, configure, account, performance & security • Fault management • Fault management manages network problems in order to keep the network running effectively. • Configuration management • Configuration management monitors network and system configuration information. chap 1: NMS

24. OSI NM Model (2) • Accounting management • Accounting management measures and regulates network utilization. • ? • Performance management maintains internetwork performance at acceptable levels. • Security management • Security management controls access to network resources. chap 1: NMS

25. Fault Management • Manages network problems to keep the network running reliably and efficiently. • Fault management process involves the following steps • Detecting the problem symptoms. • Isolating the problem. • Fixing the problem automatically (if possible) or manually. • Testing the fix on all important subsystems. • Logging the detection and resolution of the problem. chap 1: NMS

26. Fault Management (2) • Test all major sub-system and record the result for future reference • Common display messages in networking devices • Green: ? • Yellow: May have problems • Red: in a state of error and is no longer in service • Blue: is running but has experience an error • Orange: configuration error • Gray: no information about the device is available • Purple: device is being queried or polled chap 1: NMS

27. Configuration Management • Configuration Management monitors network and system configuration information and stores it in a configuration management database. • The maintenance of this database allows network administrators to track hardware, software, and other network resources chap 1: NMS

28. Configuration Management (2) • Each network device has a variety of information associated with it: • Software version information for the operating system, protocol software, or management software. • Hardware version information for the interfaces or hardware controllers. • Contact information indicating who to contact if problems with the device arise. • Location information indicating the physical location of the device. chap 1: NMS

29. Configuration Management (3) • CM Information Associated with a Managed Device chap 1: NMS

30. Accounting Management • Measures network ? parameters in order to regulate individual and group uses of the network. • Minimizes network problems and maximizes fairness of user access to the network because network resources can be portioned based on network capacity and user needs. chap 1: NMS

31. Account Management (2) • There are 4 Steps in Account Management: • Measuring the use of all important network resources. • Analyzing the results to determine the current usage patterns. • Setting usage quotas. • Measuring resource utilization on an ongoing basis. chap 1: NMS

32. Performance Management • Maintains internetwork performance at acceptable levels by measuring and managing various network performance variables. • Performance variables include network ?, user response times, line utilization, and others. • Performance management involves three basic steps: • Gathering data relating to key performance variables. • Analyzing data to determine the normal (baseline) performance levels. • Determining appropriate performance thresholds for each variable so that exceeding these thresholds indicates a network problem worthy of attention. chap 1: NMS

33. Performance Console Window Help Action View Favorites Tree Favorites Console Root System Monitor Performance Logs and Alerts 100 80 60 40 20 10 Last 3.000 Average 16.154 2.000 Minimum Maximum 63.000 Duration 1:40 Color Scale Counter Instance Parent Object Computer - - - - - - - - - - - - - - - 1.000 1.000 1.000 1.000 1.000 % Processor Time % Processor Time % Disk Time Page/sec Bytes Received/sec _Total explorer 0 C: D: - - - Default FTP Site Processor Process PhysicalDisk Memory FTP Service \\LONDON \\LONDON \\LONDON \\LONDON \\LONDON Performance Management (2) chap 1: NMS

34. Performance Management (3) • ? • when performance becomes unacceptable (that is, a user-defined threshold is exceeded), the managed device reacts by sending an alert to the network management system (NMS). • Proactive • simulation is used to project how network growth will affect performance metrics. These simulations alert administrators to impending problems before they affect network users. chap 1: NMS

35. Performance Management (4) • Reactive PM Components • The management entity continually monitors performance variables in managed devices. • When a particular performance threshold is exceeded, the NMS or the managed device detects the problem. • If the managed device detects the problem, it generates an alert and sends it to the NMS. • The NMS takes an appropriate action, such as alerting the network administrator. chap 1: NMS

36. Windows Task Manager Windows Task Manager Windows Task Manager File Options View Windows Help File Options View Help File Options View Help Applications Applications Applications Processes Processes Processes Performance Performance Performance CPU Usage CPU Usage History Image Name PID Task Status CPU CPU Time Mem Usage Building Schematic - Paint Memo to Supervisor - WordPad Calculator My Computer Running Running Running Running System Idle Process System smss.exe csrss.exe winlogon.exe services.exe lsass .exe svchost .exe spoolsv .exe mspaint .exe msdtc .exe inojobsv .exe dfssvc .exe svchost .exe ismserv .exe llssrv .exe ntfrs.exe regsvc.exe 0 8 168 196 220 148 160 472 492 624 704 808 824 840 864 880 928 968 96 00 00 00 00 00 00 00 00 00 02 00 00 00 00 00 00 00 4:52:37 0:00:27 0:00:00 0:00:20 0:00:09 0:00:14 0:00:32 0:00:00 0:00:00 0:00:04 0:00:00 0:07:46 0:00:00 0:00:00 0:00:00 0:00:01 0:00:09 0:00:00 16 K 212 K 344 K 1,820 K 4,408 K 8,228 K 15,768 K 2,648 K 4,184 K 352 K 3,428 K 5,704 K 2,336 K 3,416 K 5,348 K 3,860 K 1,108 K 844 K 3% MEM Usage Memory Usage History 10 1600K Physical Memory (K) Totals Handles Threads Processes 5932 381 30 Total Available System Cache 130612 27740 50704 Kernel Memory (K) Commit Charge (K) Total Limit Peak 101600 310892 116896 Total Paged Nonpaged 22804 15704 7100 Show processes from all users End Process End Task Switch To New Task... CPU Usage: 2% Mem Usage: 103500K / 310892K Processes: 30 CPU Usage: 6% Processes: 30 CPU Usage: 3% Mem Usage: 101600K / 310892K Mem Usage: 103452K / 310892K Processes: 30 Windows Task Manager chap 1: NMS

37. Security Management • controls access to network resources, and prevents network sabotage (intentional or unintentional) and unauthorized access to sensitive information. • aids administrators in creating a secure network environment. This includes: • partitioning network resources into authorized and unauthorized areas, • mapping groups of users to those areas, and • monitoring, policing, and logging user access to resources in those areas. chap 1: NMS

38. Summary • Objective and challenge of Network management • Network management Archiectures: centralized, distributed, hierarchical • Components: NM Station, Managed device, protocol • ISO-OSI model: FCAPS • fault • configuration • account • performance • security chap 1: NMS