1 / 28

Remote Monitoring and Desktop Management

Remote Monitoring and Desktop Management. (Stallings Ch 7). Remote Monitoring. SNMP designed for management of a limited range of devices and a limited range of functions Monitoring is difficult in both WANs and the newer switched LANs. Remote Monitoring (Stallings Ch.7).

doloresv
Télécharger la présentation

Remote Monitoring and Desktop 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. Remote Monitoring andDesktop Management (Stallings Ch 7)

  2. Remote Monitoring • SNMP designed for management of a limited range of devices and a limited range of functions • Monitoring is difficult in both WANs and the newer switched LANs. FIT2018 (c) Monash University

  3. Remote Monitoring(Stallings Ch.7) • SNMP network management tools can support the monitoring of individual devices. • However, it is difficult to learn about traffic on a particular subnetwork using SNMP. FIT2018 (c) Monash University

  4. Protocol Analysers as Monitors • Protocol analysers can support viewing of each packet that passes on a network. • In a network using routing or switches, monitors will only see the traffic on their part of the network. • Thus, the devices cannot cover whole network… FIT2018 (c) Monash University

  5. Remote Network Monitors • Could have one monitor per subnetwork or switched section - may be excessively costly if use protocol analysers. • If dedicated monitoring modules are used that report back to a network management station, this may be possible. This is called remote monitoring. FIT2018 (c) Monash University

  6. Remote Monitor - RMON • A range of standard functions have been defined for remote monitoring within SNMP - RMON. • RMON agents may be dedicated hardware devices attached to a subnetwork or may be software running in networked devices (computers, switches, routers, printers, etc) FIT2018 (c) Monash University

  7. RMON normally supports: Off-line operation • Monitor collects statistics (packet counts, error rates, etc) with management station retrieving data after some time duration. • Reduces network traffic. FIT2018 (c) Monash University

  8. RMON normally supports: Preemptive Monitoring • Monitor runs diagnostics and collects statistics continuously, reporting failure to management station and supplying diagnostic information to assist problem resolution. FIT2018 (c) Monash University

  9. RMON normally supports: Problem detection and reporting • Monitor passively observes its subnetwork and reports to management station on specific problems that are observed. FIT2018 (c) Monash University

  10. RMON normally supports: Value-added data • Monitor can provide information of greater detail and with analysis that would normally only be available to an analyser attached to that subnetwork - eg, hosts generating most traffic. FIT2018 (c) Monash University

  11. RMON normally supports: Multiple managers • Monitors may be expected to provide support for more than one management station. FIT2018 (c) Monash University

  12. Monitor Control • A monitor is required to perform tasks that are more sophisticated than the devices normally managed using SNMP (routers, bridges, etc). • Thus it must be able to interact with a management station to provide data and receive commands of some complexity. FIT2018 (c) Monash University

  13. Monitor Control • SNMP was not originally intended for this and so needs some minor changes to support RMON. • This is done via an RMON MIB. FIT2018 (c) Monash University

  14. RMON Overview • A standard MIB • Described in RFC 1757 • Defines MAC-layer statistics and control objects • Monitors basic Ethernet operations • Powerful alarm and event mechanism • Automatic historical data collection • Utilisation • Collisions • Usage patterns • Planning data FIT2018 (c) Monash University

  15. RMON Architecture Router Router WAN LAN segments LAN segments RMON DCM FIT2018 (c) Monash University

  16. RMON Group objects • statistics - utilisation and error rates • history - periodic samples are stored • alarm - alarm thresholds can be set • host - traffic to/from hosts on subnetwork • hostTopN - maintains a list of highest recorded (peak) statistics for hosts • matrix - error and utilisation data can be returned as a matrix for all addresses of nodes recorded FIT2018 (c) Monash University

  17. RMON Group objects • filter - permits the setup of selective monitoring • packet capture - determines how the monitor delivers data to the management station • event - table of all events generated by the RMON probe FIT2018 (c) Monash University

  18. Network Overload • RMON agents may be set to retain information for a period of time, or to return data immediately. In either case, the volume of data may reduce network performance. • However, the trade-off may be to the lack of network knowledge. FIT2018 (c) Monash University

  19. Monitoring Device Overload • The volume / detail of information required to be accessed by RMON agents may be so great that it may affect monitoring device performance. • In high-volume situations (high speed switches, etc) dedicated devices are preferable. FIT2018 (c) Monash University

  20. Desktop Management

  21. Desktop Management • Desktop Management Task Force a collection of computer industry parties (Microsoft, Intel, etc see www.dmtf.org ) have been working on the development of an agent that can reside in device to be managed. FIT2018 (c) Monash University

  22. DTMF - DMI • The DMTF developed the Desktop Management Interface (DMI) a standardised system to carry out the task. • Hardware or firmware (program emedded in device eg ROM-based control system) implements DMI functions • Software interface resides as a TSR (terminate and stay resident program) or as a windows DLL provides network access. FIT2018 (c) Monash University

  23. Desktop management Interface FIT2018 (c) Monash University

  24. Initial development of the user agent has centred around the IBM-compatible PC-style machines. • However, there is intended to be a standard interface for all operating environments and platforms. FIT2018 (c) Monash University

  25. Application of DMI functions A remote management station can then provide a wide range of supportive functions • "over-the-shoulder" remote viewing of user actions while helping the user by phone • taking over of the keyboard and "becoming the user" to run through a sequence of operations and show the use how it is done • inventory of equipment, resources and software FIT2018 (c) Monash University

  26. Application of DMI functions • The management station can also provide many remote management functions like backup and automatic software upgrades, independent of the users involvement. • The management agent will be a standardised product that is compatible with the current and future management standards (CMIP, SNMP, WBEM). FIT2018 (c) Monash University

  27. Application of DMI functions • Desktop management using a local agent offers many advantages, particularly in the areas of system security and reliability of client computers, and it may be necessary for the support of network administration in complex networking environments. FIT2018 (c) Monash University

  28. (end)

More Related