Network Management Standards Architectures & Applications. Network Management

Transcription

1 Network Management Standards Architectures & Applications Network Management 1

2 Lectures Schedule Week Week 1 Topic Computer Networks - Network Management Architectures & Applications Week 2 Network Management Standards Architectures & Applications Week 3 Simple Network Management Protocol - SNMP v1, ASN, MIB, BER Week 4 Network Management Functions - Fault Week 5 Simple Network Management Protocol - SNMP v2 - Configuration Week 6 Network Management Functions - Accounting Week 7 Simple Network Management Protocol - SNMP v3 - Performance Week 8 Network Management Functions - Security Week 9 Midterm Week 10 Remote Network Monitoring RMON 1, SLA Week 11 Remote Network Monitoring RMON 2 Week 12 Management Tools, Systems and Applications Week 13 NM Project Presentations Week 14 NM Project Presentations Week 15 NM Project Presentations 2

3 Course project Create an application which is able to use SNMP to get specific information from MIB, on remote hosts with SNMP agents such as runing processes, runing applications, Installed applications One option is to have (or create one) list of legitimate processes aproved by SLA and to detect unallowed proccesses or applications on specific system. Operating system options are Windows or Linux Any programming language is allowed Create user manual 3

4 Introduction "Network management includes the deployment, integration and coordination of the hardware, software, and human elements to monitor, test, poll, configure, analyze, evaluate, and control the network and element resources to meet the real-time, operational performance, and Quality of Service requirements at a reasonable cost."

5 Data Communications and Computer Networks Chapter 14 5

6 definitions: Infrastructure for network management managing entity managing entity data network management protocol agent data agent data managed device agent data managed device agent data managed device managed devices contain managed objects whose data is gathered into a Management Information Base (MIB) managed device 9-6

7 SNMP overview: 4 key parts Management information base (MIB): distributed information store of network management data Structure of Management Information (SMI): data definition language for MIB objects SNMP protocol convey manager<->managed object info, commands security, administration capabilities Network Management 9-7

8 SNMP protocol Two ways to convey MIB info, commands: managing entity managing entity request response trap msg agent data agent data Managed device request/response mode Managed device trap mode Network Management 9-8

9 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 H-9

10 Network Management Platform Additional features for a platform include: Graphing Tools Application Programming Interface (API) System Security H-10

11 Network Management Architectures The Network Management Platform can use various architectures to provide functionality The 3 most common are: Centralized Hierarchical Distributed H-11

12 Network Managament F C A P S 12

13 Network Management System Architecture Business Data Communications, 4e 13

14 Components of the NMS All nodes run the Network Management Entity (NME) software Network control host or manager runs the Network Management Application (NMA) Other nodes are considered agents 14

15 Centralized Architecture The Network Management Platform resides on a single computer system For full redundancy, the computer system is backed up by another system Can allow access and forward events to other consoles on network H-15

16 Centralized Architecture Used for: All network alerts & events All network information Access all management applications H-16

17 Centralized Architecture Pros: Single location to view events & alerts Single place to access network management applications and information Security is easier to maintain H-17

18 Centralized Architecture Cons: Single system is not redundant or fault tolerant As network elements are added, may be difficult or expensive to scale system to handle load Having to query all devices from a single location H-18

19 Hierarchical Architecture Uses multiple computer systems One system acting as the central server Other systems working as clients Central server requires backups for redundancy H-19

20 Hierarchical Architecture Key features: Not dependent on a single system Distribution of network management tasks Network monitoring distributed throughout network Centralized information storage H-20

21 Hierarchical Architecture Pros: Multiple systems to manage the network Cons: Information gathering is more difficult and time consuming The list of managed devices managed by each client needs to be predetermined and manually configured H-21

22 Distributed Architecture Combines the centralized and hierarchical architectures Uses multiple peer network management systems Each peer can have a complete database Each peer can perform various tasks and report back to a central system H-22

23 Distributed Architecture Contains advantages from central & hierarchical architectures Single location for all network information, alerts & events Single location to access all management applications Not dependent on a single system Distribution of network management tasks Distribution of network monitoring throughout the network H-23

24 Network Management Applications Goals Effectively manage a specific set of devices Avoid functionality overlap with the platform Integrate with a platform through the API and menu system Reside on multiple platforms Applications do not share information H-24

25 Network Management Applications Applications that exist today HP Open View BayNetworks Optivity Cisco s CiscoWorks 3Com s Transcend Other H-25

26 Choosing a Network Management System Built from two major components: the Platform and Applications A practical approach follows these steps: Perform device inventory Prioritize the functional areas of network management Survey network management applications Choose the network management platform H-26

27 Other Topics Sniffers RMON Network Statistics H-27

28 RMON Remote monitoring MIB Agents Probes There are 9 groups of RMON Statistics, History, Alarm, Host, HostTopN, Matrix, Filter, Packet Capture, and Event Standardized to only operate on Ethernet segments H-28

29 RMON Goals Offline operation Preemptive monitoring Problem detection and reporting Value-added data Multiple managers H-29

30 RMON Statistics Group Contains objects that are measured for each Ethernet interface on the device Provides data for multiple segments simultaneously Used for fault, configuration, and performance management H-30

31 RMON History Group Enables periodic statistical samples and stores them at the probe for later retrieval and analysis Configurable as to what to monitor and how often to take the snapshot Useful for accomplishing performance management H-31

32 RMON Alarm Group Useful for accomplishing performance management Defines thresholds for a MIB object over a duration of time H-32

33 RMON Host Group Contains objects associated with each host known on the network segment where the probe is located Discovers hosts by keeping track of source and destination addresses Useful for configuration, performance, and accounting management H-33

34 RMON HostTopN Uses objects in the Host Group to prepare reports on a set of hosts over a given period of time Reports are based on a base statistic specified by the network management system H-34

35 RMON Matrix Group Contains tables of objects that keep statistics on the number of packets, bytes, and errors sent between two addresses Help determine traffic patters on a segment Useful for performance, security, and accounting management H-35

36 RMON Filter Group Used to configure the probe to look for specific packets on the segment Useful in fault and security management RMON Packet Capture Group Used to set up a buffering scheme for packets from the filter group H-36

37 RMON Event Group Allows you to define events for the probe Can create a log entry or send a SMTP trap Helps eliminate the need for the network management system to periodically poll network devices to discover faults Useful for fault, performance, and security management H-37

38 RMON RMON is not enough RMON 2 is a different standard than RMON 1 - it is not a superset Shows how traffic flows on a network Shows what applications are being used RMON probes should be used for segment visibility RMON 2 probes should be used on backbones H-38

39 Network Statistics Baseline Trouble shooting Capacity planning for the future Reports H-39

40 Aplications 40

41 MRTG F C A P S MRTG (Multi Router Traffic Grapher) mrtg/mrtg.html) and makes nice graphs: 41

42 Applications F C A P S 42

43 Globalni pogled Applications F C A P S

44 Applications F C A P S

45 Applications F C A P S

46 Applications HostTopN F C A P S Host 1 Host 2 Host 3 Host 4 Host 5 Host 6 Host 7 Host 8 Host 9 Host Giga Octets

47 Applications F C A P S

48 Applications F C A P S

49 Conclusion Standards Protocols Infrastructure Architestures Applications 49