Definitions of Managed Objects for SNA NAUs using SMIv2
RFC 1666
Document | Type |
RFC - Historic
(August 1994; No errata)
Obsoletes RFC 1665
|
|
---|---|---|---|
Authors | Deirdre Kostick , Kitty Shih , Zbigniew Kielczewski | ||
Last updated | 2013-03-02 | ||
Stream | Legacy stream | ||
Formats | plain text html pdf htmlized (tools) htmlized bibtex | ||
Stream | Legacy state | (None) | |
Consensus Boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | RFC 1666 (Historic) | |
Telechat date | |||
Responsible AD | (None) | ||
Send notices to | (None) |
Network Working Group Z. Kielczewski Request for Comments: 1666 Eicon Technology Corporation Obsoletes: 1665 D. Kostick Category: Standards Track Bell Communications Research K. Shih Novell Editors August 1994 Definitions of Managed Objects for SNA NAUs using SMIv2 Status of this Memo This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited. Table of Contents 1. Introduction ................................................ 2 2. The SNMPv2 Network Management Framework ..................... 2 2.1 Object Definitions ......................................... 2 3. Overview .................................................... 3 3.1 Applying MIB II to managing SNA NAUs ....................... 4 3.2 SNANAU MIB Structure ....................................... 4 3.2.1 snaNode group ............................................ 5 3.2.2 snaLu group .............................................. 6 3.2.3 snaMgtTools group ........................................ 7 3.2.4 Conformance statement .................................... 7 3.3 SNANAU MIB special feature ................................. 7 3.3.1 Row Creation mechanism ................................... 8 3.3.2 State Diagrams ........................................... 8 4. Object Definitions .......................................... 9 5. Acknowledgments ............................................. 67 6. References .................................................. 67 7. Security Considerations ..................................... 68 8. Authors' Addresses .......................................... 68 Kielczewski, Kostick & Shih [Page 1] 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 [Page 2] RFC 1666 SNANAU MIB August 1994 3. Overview This document identifies the proposed set of objects for managing the configuration, monitoring and control of Physical Units (PUs) andShow full document text