General Navigation Buttons - Home | Search | Contact Us | Site Map | Whats New
products graphic
white space
products
Software Technology Roadmap
What's New
Background & Overview
Technology Descriptions
Defining Software Technology
Technology Categories
Template for Technology Descriptions
Taxonomies
Glossary & Indexes
Feedback & Participation
Software Engineering Information Repository (SEIR)
white space
About SEI|Mgt|Eng|Acq|Collaboration|Prod.& Services|Pubs
pixel
Rollover Popup Hints for Topic Navigation Buttons above
pixel
Common Management Information Protocol


Status

Advanced

Note

We recommend Network Management--An Overview as prerequisite reading for this technology description.

Purpose and Origin

Common Management Information Protocol (CMIP) is an Open Systems Interconnection (OSI)1 -based network management protocol that supports information exchange between network management applications and management agents. CMIP is part of the X.700 (CCITT2 number for the OSI Management Framework, also designated as ISO/IEC 7498-43) OSI series of management standards. Its design is similar to the Simple Network Management Protocol (SNMP). CMIP was developed and funded by government and corporations to replace and makeup for the deficiencies in SNMP, thus improving the capabilities of network management systems.

Technical Detail

CMIP is a well designed protocol that defines how network management information is exchanged between network management applications and management agents. It uses an ISO reliable connection-oriented transport mechanism and has built in security that supports access control, authorization and security logs. The management information is exchanged between the network management application and management agents thru managed objects. Managed objects are a characteristic of a managed device that can be monitored, modified or controlled and can be used to perform tasks. The network management application can initiate transactions with management agents using the following operations:

  • ACTION - Request an action to occur as defined by the managed object.
  • CANCEL_GET - Cancel an outstanding GET request.
  • CREATE - Create an instance of a managed object.
  • DELETE - Delete an instance of a managed object.
  • GET - Request the value of a managed object instance.
  • SET - Set the value of a managed object instance.
A management agent can initiate a transaction with the network management application using the EVENT_REPORT operation. This operation can be used to send notifications or alarms to the network management application based upon predetermined conditions set by the network management application using the ACTION operation.

CMIP does not specify the functionality of the network management application, it only defines the information exchange mechanism of the managed objects and not how the information is to be used or interpreted.

The major advantages of CMIP over SNMP are [Vallillee 96]:

  • CMIP variables not only relay information, but also can be used to perform tasks. This is impossible under SNMP.
  • CMIP is a safer system as it has built in security that supports authorization, access control, and security logs.
  • CMIP provides powerful capabilities that allow management applications to accomplish more with a single request.
  • CMIP provides better reporting of unusual network conditions
The CMIP specification for TCP/IP networks is called CMOT (CMIP Over TCP) and the version for IEEE 802 LAN's is called CMOL (CMIP Over LLC) [Stallings 93].

Usage Considerations

CMIP is widely used in the telecommunication domain and telecommunication devices typically support CMIP. The International Telecommunication Union (ITU)4 endorses CMIP as the protocol for the management of devices in the Telecommunication Management Network (TMN)5 standard.

The CMIP protocol is designed to run on the ISO protocol stack [Stallings 93]. However, the technology standard used today in most LAN environments is TCP/IP and most LAN devices only support SNMP. Implementations of CMOT are extremely scarce.

CMIP requires a large amount of system resources, this has resulted in very few implementations. Additionally, CMIP is very complex thus making it difficult to program; therefore skilled personnel with specialized training may be required to deploy, maintain and operate a CMIP based network management system.

Maturity

CMIP was developed over a decade ago; however few implementations exist because of the problems described above in Usage Considerations.

Costs and Limitations

Systems may not be capable of supporting the resource requirements of CMIP and difficulties may exist in the procurement of CMIP software because of limited availability.

Alternatives

SNMP is widely available and is the de facto standard network management protocol; however, it does not provide all of the functionality of CMIP. SNMP deficiencies are discussed in Usage Considerations for SNMP.

Index Categories

This technology is classified under the following categories. Select a category for a list of related topics.

Name of technology

Common Management Information Protocol (CMIP)

Application category

Protocols (AP.2.2.3)
Network Management (AP.2.2.2)

Quality measures category

Maintainability (QM.3.1)
Simplicity (QM.3.2.2)
Complexity (QM.3.2.1)
Efficiency/Resource Utilization (QM.2.2)
Scalability (QM.4.3)
Security (QM.2.1.5)

Computing reviews category

Network Operations (C.2.3)
Distributed Systems (C.2.4)

References and Information Sources

[Korinko 96] Korinko, Joe. CMIP-Common Management Information Protocol [online]. Available WWW
<URL: http://www.rit.edu/~jek0539/icsa750/exam2/ex2pg1.htm> (1996).
[Stallings 93] Stallings, William. SNMP, SNMPv2, and CMIP: The Practical Guide to Network Management Standards. Reading, MA: Addison-Wesley, 1993.
[Vallillee 96] Vallillee, Tyler. SNMP & CMIP: An Introduction To Network Management [online]. Available WWW
<URL: http://www.inforamp.net/~kjvallil/t/snmp.html> (1996).
[X.700 96] X.700 and Other Network Management Services [online]. Available WWW
<URL: http://ganges.cs.tcd.ie/4ba2/x700/index.html> (1996).

Current Author/Maintainer

Dan Plakosh, SEI

Modifications

9 February 98: minor modifications

13 May 97 (Original)

Footnotes

1 The OSI model is a framework for defining communications protocols. It consists of seven layers of protocols that range from low level methods for dealing with a physical communications medium, to high level methods for dealing with the communications needs of user applications. Developed by the International Standards Organization (ISO), specific protocols have been designed to implement the functionality specified by the OSI model.

2 International Telegraph and Telephone Consultative Committee: This organization is part of the United National International Telecommunications Union (ITU) and is responsible for making technical recommendations about telephone and data communications systems.

3 International Organization for Standardization (ISO). A voluntary, non-treaty organization founded in 1946 which is responsible for creating international standards in many areas, including computers and communications. Its members are the national standards organizations of the 89 member countries, including ANSI for the U.S.
International Electrotechnical Commission (NEC). The international standards and conformity assessment body for all fields of electrotechnology. IEC and ISO technical committees collaborate in fields of mutual interest.

4 The ITU is an international organization within which governments and the private sector coordinate global telecom networks and services. It also develops standards to facilitate the interconnection of telecommunication systems on a worldwide scale regardless of the type of technology used.

5 A management architecture framework developed by the International Telecommunication Union (ITU), which provides an environment for interfacing a telecommunication network with computer systems to provide different management functions at several different levels. The framework allows the management of business information between different components (operations systems, communication equipment, network and computer systems) and provides control of service operations and information flow.



The Software Engineering Institute (SEI) is a federally funded research and development center sponsored by the U.S. Department of Defense and operated by Carnegie Mellon University.

Copyright 2007 by Carnegie Mellon University
Terms of Use
URL: http://www.sei.cmu.edu/str/descriptions/cmip_body.html
Last Modified: 11 January 2007