RFC 1666 (rfc1666) - Page 2 of 68

Definitions of Managed Objects for SNA NAUs using SMIv2

RFC 1666                       SNANAU MIB                    August 1994


1.  Introduction

   This memo defines a portion of the Management Information Base (MIB)
   for use with network management protocols in the Internet community.
   In particular, it defines objects for managing the configuration,
   monitoring and control of Physical Units (PUs) and Logical Units
   (LUs) in an SNA environment.  PUs and LUs are two types of Network
   Addressable Units (NAUs) in the logical structure of an SNA network.
   NAUs are the origination or destination points for SNA data streams.
   This memo identifies managed objects for PU Type 1.0, 2.0 and Type
   2.1 and LU Type 0, 1, 2, 3, 4, 7.  The generic objects defined here
   can also be used to manage LU 6.2 and any LU-LU session.  The SNA
   terms and overall architecture are documented in [1].

2.  The SNMPv2 Network Management Framework

   The SNMPv2 Network Management Framework consists of four major
   components.  They are:

      o    RFC 1442 [2] which defines the SMI, the mechanisms used for
           describing and naming objects for the purpose of management.

      o    STD 17, RFC 1213 [3] defines MIB-II, the core set of
           managed objects for the Internet suite of protocols.

      o    RFC 1445 [4] which defines the administrative and other
           architectural aspects of the framework.

      o    RFC 1448 [5] which defines the protocol used for network
           access to managed objects.

   The Framework permits new objects to be defined for the purpose of
   experimentation and evaluation.

2.1.  Object Definitions

   Managed objects are accessed via a virtual information store, termed
   the Management Information Base or MIB.  Objects in the MIB are
   defined using the subset of Abstract Syntax Notation One (ASN.1)
   defined in the SMI (RFC 1442 [2]).  In particular, each object type
   is named by an OBJECT IDENTIFIER, an administratively assigned name.
   The object type together with an object instance serves to uniquely
   identify a specific instantiation of the object.  For human
   convenience, we often use a textual string, termed the descriptor, to
   refer to the object type.






Kielczewski, Kostick & Shih