Previous Page Next Page

Data Collection Protocols: CMISE/CMIP and GDMO

The fundamental function of the Common Management Information Service Element (CMISE) is the exchange of management information between manager and agent entities.

CMISE is specified in two parts:

CMIP was proposed as a replacement for SNMP as part of the ITU-T Telecommunications Management Network (TMN). The major advantages of CMIP over SNMP are as follows:

Guideline for Definition of Managed Objects (GDMO) provides a language for defining managed objects within TMN-based systems. GDMO is a structured description language for specifying object classes and the objects' behaviors, attributes, and class ancestry. While there is an analogy to the SNMP Structures of Managed Information (SMI), the GDMO format is not derived from Abstract Syntax Notation 1 (ASN.1).

Although the "S" for Simple in the SNMP acronym reflects the philosophy behind the SNMP protocol design, CMIP/CMIS was designed to be much more powerful and therefore is more complex and resource-intensive to implement. This, along with some performance issues, explains why CMIP/CMIS were not widely adopted throughout the industry. In the competition between the IETF SNMP and the OSI CMIP, the industry clearly selected SNMP as the winner because of quick developments and freely accessible standards. Although this section is interesting from a reference and quick overview point of view, the authors advise you not to investigate CMISE, CMIP, and GDMO further.

Note

CMIP/CMIS are defined in ISO (http://www.iso.org) documents 9595 and 9596 and ITU (http://www.itu.org) X.700 and X.711.

GDMO is specified in ISO/IEC 10165/ITU-T X.722.


Previous Page Next Page