Next Generation Structure of Management Information (SMIng) Mappings to the Simple Network Management Protocol (SNMP)
RFC 3781

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 05

Network Working Group                                         F. Strauss
Request for Comments: 3781                               TU Braunschweig
Category: Experimental                                  J. Schoenwaelder
                                         International University Bremen
                                                                May 2004

      Next Generation Structure of Management Information (SMIng)
       Mappings to the Simple Network Management Protocol (SNMP)

Status of this Memo

   This memo defines an Experimental Protocol for the Internet
   community.  It does not specify an Internet standard of any kind.
   Discussion and suggestions for improvement are requested.
   Distribution of this memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (2004).  All Rights Reserved.

Abstract

   SMIng (Structure of Management Information, Next Generation)
   (RFC3780), is a protocol-independent data definition language for
   management information.  This memo defines an SMIng language
   extension that specifies the mapping of SMIng definitions of
   identities, classes, and their attributes and events to dedicated
   definitions of nodes, scalar objects, tables and columnar objects,
   and notifications, for application to the SNMP management framework.

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  3
   2.  SNMP Based Internet Management . . . . . . . . . . . . . . . .  3
       2.1.   Kinds of Nodes. . . . . . . . . . . . . . . . . . . . .  4
       2.2.   Scalar and Columnar Object Instances. . . . . . . . . .  5
       2.3.   Object Identifier Hierarchy . . . . . . . . . . . . . .  7
   3.  SMIng Data Type Mappings . . . . . . . . . . . . . . . . . . .  8
       3.1.   ASN.1 Definitions . . . . . . . . . . . . . . . . . . .  9
   4.  The snmp Extension Statement . . . . . . . . . . . . . . . . . 10
       4.1.   The oid Statement . . . . . . . . . . . . . . . . . . . 10
       4.2.   The node Statement. . . . . . . . . . . . . . . . . . . 10
              4.2.1. The node's oid Statement . . . . . . . . . . . . 10
              4.2.2. The node's represents Statement. . . . . . . . . 10
              4.2.3. The node's status Statement. . . . . . . . . . . 11
              4.2.4. The node's description Statement . . . . . . . . 11
              4.2.5. The node's reference Statement . . . . . . . . . 11

Strauss & Schoenwaelder       Experimental                      [Page 1]
RFC 3781                 SMIng Mappings to SNMP                 May 2004

              4.2.6. Usage Examples . . . . . . . . . . . . . . . . . 11
       4.3.   The scalars Statement . . . . . . . . . . . . . . . . . 11
              4.3.1. The scalars' oid Statement . . . . . . . . . . . 12
              4.3.2. The scalars' object Statement  . . . . . . . . . 12
              4.3.3. The scalars' status Statement  . . . . . . . . . 13
              4.3.4. The scalars' description Statement . . . . . . . 14
              4.3.5. The scalars' reference Statement . . . . . . . . 14
              4.3.6. Usage Example. . . . . . . . . . . . . . . . . . 14
       4.4.   The table Statement . . . . . . . . . . . . . . . . . . 14
              4.4.1. The table's oid Statement. . . . . . . . . . . . 15
              4.4.2. Table Indexing Statements. . . . . . . . . . . . 15
              4.4.3. The table's create Statement . . . . . . . . . . 17
              4.4.4. The table's object Statement . . . . . . . . . . 17
              4.4.5. The table's status Statement . . . . . . . . . . 19
              4.4.6. The table's description Statement  . . . . . . . 19
              4.4.7. The table's reference Statement  . . . . . . . . 19
              4.4.8. Usage Example  . . . . . . . . . . . . . . . . . 19
       4.5.   The notification Statement  . . . . . . . . . . . . . . 20
              4.5.1. The notification's oid Statement . . . . . . . . 20
              4.5.2. The notification's signals Statement . . . . . . 20
              4.5.3. The notification's status Statement  . . . . . . 20
              4.5.4. The notification's description Statement . . . . 21
              4.5.5. The notification's reference Statement . . . . . 21
              4.5.6. Usage Example. . . . . . . . . . . . . . . . . . 21
       4.6.   The group Statement . . . . . . . . . . . . . . . . . . 21
              4.6.1. The group's oid Statement  . . . . . . . . . . . 22
              4.6.2. The group's members Statement  . . . . . . . . . 22
              4.6.3. The group's status Statement . . . . . . . . . . 22
              4.6.4. The group's description Statement  . . . . . . . 22
              4.6.5. The group's reference Statement  . . . . . . . . 22
              4.6.6. Usage Example  . . . . . . . . . . . . . . . . . 22
       4.7.   The compliance Statement. . . . . . . . . . . . . . . . 23
              4.7.1. The compliance's oid Statement . . . . . . . . . 23