Difference between revisions of "XML Management Protocol"
(→Implementations) |
(→Structure of Management Information) |
||
Line 26: | Line 26: | ||
We enhanced the Internet Management Framework SMI in several ways. | We enhanced the Internet Management Framework SMI in several ways. | ||
− | First, we did away with object-identifiers (OIDS) and instance-identifiers. We use the tuple of MIB-name, object-name, and instance-name to uniquely identify an item of management information. For example, the [http://www.ietf.org/rfc/ | + | First, we did away with object-identifiers (OIDS) and instance-identifiers. We use the tuple of MIB-name, object-name, and instance-name to uniquely identify an item of management information. For example, the [http://www.ietf.org/rfc/rfc1213.txt MIB-2] object ''ifInOctets'' for the first interface is can be represented by the rather obtuse OID 1.3.6.1.2.1.2.2.1.10.1. In the XMP SMI, the same MIB object would be represented by the object name ''mib2.ifTable.ifInOctets.if0''. |
We added several data types. | We added several data types. |
Revision as of 13:29, 31 March 2007
Contents |
Overview
Basic Architecture
Entities acting as managers initiate communication with agents. Manager closes session when finished.
Structure of Management Information
The Structure of Management Information or SMI defines the syntax and semantics of management exchanges. For XMP, we borrowed heavily from the Internet Management Framework SMI and only modified it in a few places. The Internet Management Framework's SMI is defined in several documents including SMIv1 and SMIv2.
We enhanced the Internet Management Framework SMI in several ways.
First, we did away with object-identifiers (OIDS) and instance-identifiers. We use the tuple of MIB-name, object-name, and instance-name to uniquely identify an item of management information. For example, the MIB-2 object ifInOctets for the first interface is can be represented by the rather obtuse OID 1.3.6.1.2.1.2.2.1.10.1. In the XMP SMI, the same MIB object would be represented by the object name mib2.ifTable.ifInOctets.if0.
We added several data types.
Data Description and Transfer Syntax
Message Formats and Syntax
Implementations
XMP has been implemented in C and Java. Bindings for Perl are in the works. An XMP adapter has also been written for use with MRTG.
The acronym XMP and protocol should not be confused with the IETF XMPP Extensible Messaging and Presence Protocol.