RFC 1442 (rfc1442) - Page 2 of 54
Structure of Management Information for version 2 of the Simple Network Management Protocol (SNMPv2)
Alternative Format: Original Text Document
RFC 1442 SMI for SNMPv2 April 1993
1. Introduction
A network management system contains: several (potentially
many) nodes, each with a processing entity, termed an agent,
which has access to management instrumentation; at least one
management station; and, a management protocol, used to convey
management information between the agents and management
stations. Operations of the protocol are carried out under an
administrative framework which defines both authentication and
authorization policies.
Network management stations execute management applications
which monitor and control network elements. Network elements
are devices such as hosts, routers, terminal servers, etc.,
which are monitored and controlled through access to their
management information.
Management information is viewed as a collection of managed
objects, residing in a virtual information store, termed the
Management Information Base (MIB). Collections of related
objects are defined in MIB modules. These modules are written
using a subset of OSI's Abstract Syntax Notation One (ASN.1)
[1]. It is the purpose of this document, the Structure of
Management Information (SMI), to define that subset.
The SMI is divided into three parts: module definitions,
object definitions, and, trap definitions.
(1) Module definitions are used when describing information
modules. An ASN.1 macro, MODULE-IDENTITY, is used to
concisely convey the semantics of an information module.
(2) Object definitions are used when describing managed
objects. An ASN.1 macro, OBJECT-TYPE, is used to
concisely convey the syntax and semantics of a managed
object.
(3) Notification definitions are used when describing
unsolicited transmissions of management information. An
ASN.1 macro, NOTIFICATION-TYPE, is used to concisely
convey the syntax and semantics of a notification.
Case, McCloghrie, Rose & Waldbusser