The report covers the evaluation of the network management protocols SNMP (Simple Network Management Protocol) and CMIP (Common Management Information Protocol). The history of the network management protocol is explained in the beginning to set the base for an understanding of the need for efficient network management protocols, which carry management information in their payload. The description and thorough comparison of the two protocols reveal several highlights: SNMP and CMIP are designed with different backgrounds and purposes. SNMP is appreciated due to its simplicity and ease of implementation and criticized for its lack of security issues and overall performance. CMIP was designed to overcome the shortcomings of SNMP and to outweigh it in every field. This aim has been achieved but what renders the protocol useless is the fact that it requires too much network resources. SNMP remains the network management protocol of choice.
After the presentation of the two protocols the attention is drawn to the impact of middleware on the management processes. Middleware can be considered as a layer of software that supports multiple communication protocols, multiple programming languages, and runs on various computer platforms. It helps to integrate otherwise incompatible system components by providing standardized mechanisms that distributed components can use to communicate over a network. With middleware the best of both worlds (SNMP versus CMIP) can be achieved. The most important middleware technologies are the Distributed Component Object Model (DCOM) and the Common Object Request Broker Architecture (CORBA). Although middleware eats up network resources significantly, it adds value to the corporative network due to its high performance and standardized interfaces that enable managers to employ network devices with the focus on the gained benefit rather than on their potential integration in the current network environment. One can see that network management, supported by middleware, moves towards the coverage of all layers in the OSI reference model.
Table of Contents
1 NETWORK MANAGEMENT PROTOCOLS
1.1 EXECUTIVE SUMMARY
1.2 PURPOSE AND SCOPE OF SMNP AND CMIP
1.2.1 SNMP (Simple Network Management Protocol)
1.2.1.1 SNMP at a glance
1.2.1.1.1 History of the network management protocol
1.2.1.1.2 About the protocol
1.2.1.2 SNMP Architecture
1.2.2 CMIP (Common Management Information Protocol)
1.2.2.1 CMIP at a glance
1.2.2.2 CMIP architecture
1.3 SNMP VERSUS CMIP – COMPARISON
1.3.1 Management Information System
1.3.1.1 MIB Structure
1.3.1.1.1 SNMP MIB
1.3.1.1.2 CMIP MIB
1.3.1.2 Object Naming
1.3.1.3 Syntax
1.3.1.4 Structure of Management Information
1.3.1.5 Feature Comparison
1.3.2 Management Access Model
1.3.3 Scalability
1.3.4 Performance
1.3.5 Reliability
1.3.6 Security
1.4 ASSESSMENT OF THE IMPACT OF THE MIDDLEWARE
1.4.1 CORBA (Common Object Request Broker Architecture)
1.4.2 DCOM (Distributed Component Object Model)
2 CRITIQUE OF VARIOUS NETWORK MANAGEMENT TOOLS
2.1 SELECTION OF SUITABLE NETWORK MANAGEMENT PRODUCTS
2.1.1 Network Management Tools
2.1.1.1 Diagnostic Tools
2.1.1.2 Monitoring Tools
2.1.1.3 Management Tools
2.1.2 Network Management Solutions
2.1.2.1 Novell ManageWise
2.1.2.2 Hewlett Packard OpenView
2.1.2.3 IBM (Tivoli) NetView
2.2 MANAGEMENT INFORMATION BASE (MIB)
2.3 EVALUATION OF COMMERCIAL TOOLS FOR NETWORK MANAGEMENT
2.3.1 Sniffer
2.3.2 Ping
2.3.3 Traceroute
2.3.4 Multi Router Traffic Grapher (MRTG)
2.3.5 Fluke LANMeter
Objectives and Topics
This report aims to evaluate and compare key network management protocols (SNMP and CMIP) and analyze the role of middleware technologies in modern, heterogeneous network environments to enhance management efficiency and interoperability.
- Evaluation of SNMP and CMIP architecture and their differences.
- Analysis of the impact of middleware on network management processes.
- Comparison of CORBA and DCOM as distributed object technologies.
- Critique and classification of commercial network management tools (Diagnostic, Monitoring, Management).
- Assessment of specific tools including Sniffer, Ping, Traceroute, MRTG, and Fluke LANMeter.
Excerpt from the Book
1.2.1.1.1 History of the network management protocol
With the declaration in 1983 of the Ministry Of Defence that TCP/IP should be the new standard Internet protocol, the ARPANET died and was replaced through the Internet. The Internet grew rapidly without having any management control standard. Therefore developers tried to build up a network management model. The earliest one was das High-Level Entity Management System (HEMS), however it did not find its use on the Internet. (Klein[1], 1999; Selegran, 1999)
In 1987 the Open Systems Interconnection group (OSI) presented a new model that was called CMIP (Common Management Information Protocol). It could only be used for OSI-based networks; therefore it was replaced by CMOT (CMIP over TCP), which has been declared as the new network management protocol standard. However, CMOT was not widely used.
In 1987 a group of network developers introduced a new protocol, SGMP (Simple Gateway Management Protocol). Its architecture was simple and it could be integrated seamlessly into an existing network. It found acceptance relatively fast. (Klein[1], 1999; Selegran, 1999)
Summary of Chapters
1 NETWORK MANAGEMENT PROTOCOLS: Provides a comprehensive evaluation of SNMP and CMIP, compares their technical features, and assesses the impact of middleware like CORBA and DCOM on management architectures.
2 CRITIQUE OF VARIOUS NETWORK MANAGEMENT TOOLS: Categorizes and evaluates different types of tools—diagnostic, monitoring, and management—and reviews specific products used in enterprise environments.
Keywords
SNMP, CMIP, Network Management, Middleware, CORBA, DCOM, Diagnostic Tools, Monitoring Tools, MIB, Network Protocols, Enterprise Networks, Interoperability, System Management, Traffic Analysis, OSI Reference Model
Frequently Asked Questions
What is the primary focus of this report?
The report focuses on evaluating and contrasting the two major network management protocols, SNMP and CMIP, while examining how middleware technologies like CORBA and DCOM support modern network management.
What are the central themes of the work?
Central themes include protocol architecture, the role of management information bases (MIBs), the impact of middleware on heterogeneous systems, and a critique of various commercial network management tools.
What is the main objective of the study?
The main objective is to provide a detailed comparison between SNMP and CMIP, and to analyze how middleware facilitates efficient management in complex, multi-vendor network environments.
Which scientific method is used for analysis?
The work employs a comparative and descriptive analysis method, contrasting protocol specifications, architectures, and performance metrics, supported by existing research and commercial product evaluations.
What is covered in the main section?
The main section covers the history and architecture of SNMP and CMIP, a thorough comparison of their MIB structures and access models, an assessment of middleware impacts, and a critique of diagnostic, monitoring, and management tools.
Which keywords characterize this work?
The work is characterized by terms such as Network Management, SNMP, CMIP, Middleware, CORBA, DCOM, MIB, and Diagnostic Tools.
Why is SNMP often chosen over CMIP despite CMIP's advanced features?
Although CMIP is more advanced and feature-rich, it is significantly more complex and requires far more network resources, making SNMP the more practical and widely adopted protocol of choice.
How does CORBA contribute to network management?
CORBA provides an infrastructure for interoperability that allows disparate hardware and software components to communicate seamlessly, enabling platform-independent management applications in heterogeneous environments.
- Quote paper
- Thomas Kramer (Author), 2000, Network Management Protocols and Tools Study, Munich, GRIN Verlag, https://www.grin.com/document/1892
