rfc1289.txt

著名的RFC文档,其中有一些文档是已经翻译成中文的的.

Network Working Group                                         J. Saperia
Request for Comments: 1289                 Digital Equipment Corporation
                                                           December 1991


                     DECnet Phase IV MIB Extensions

Status of this Memo

   This memo is an extension to the SNMP MIB.  This RFC specifies an IAB
   standards track protocol for the Internet community, and requests
   discussion and suggestions for improvements.  Please refer to the
   current edition of the "IAB Official Protocol Standards" for the
   standardization state and status of this protocol.  Distribution of
   this memo is unlimited.

Table of Contents

   Abstract..........................................................  1
   1. Introduction...................................................  1
   2. Selected Objects...............................................  2
   3. Objects........................................................  3
   3.1 Format of Definitions.........................................  3
   3.2 Textual Conventions...........................................  4
   4. Object Definitions.............................................  4
   5. Acknowledgements............................................... 63
   6. References..................................................... 63
   7. Security Considerations........................................ 64
   8. Author's Address............................................... 64

Abstract

   This memo defines a set of DECnet Phase IV extensions that have been
   created for the Internet MIB.  When used in conjunction with the
   structure of management information (RFC 1155), the management
   information base for network management of TCP/IP-based internets
   (RFC 1213) and the Simple Network Management Protocol (RFC 1157), it
   will be possible to provide integrated network management of combined
   TCP/IP and DECnet Phase IV based internets.  This document was
   produced by the DECnet Phase IV MIB working group of the Internet
   Engineering Task Force (IETF).

1.  Introduction

   With the adoption of The Simple Network Management Protocol (RFC
   1157), the management information base for network management of
   TCP/IP-based internets (RFC 1213), and the structure of management
   information (RFC 1155), by the Internet, and a large number of vendor



DECnet Phase IV MIB Working Group                               [Page 1]

RFC 1289                  DECnet Phase IV MIB              December 1991


   implementations of these standards in commercially available
   products, it became possible to provide a higher level of effective
   network management in TCP/IP-based internets than previously
   available. With the growth in the use of these standards, network
   managers desired to use this environment as a base for providing
   integrated network management of multi-protocol networks.

   DECnet Phase IV is one widely used protocol which often coexists in
   IP-based internets. This memo provides the mechanisms by which IP-
   based management stations can effectively manage DECnet Phase IV
   based systems (especially router products) in an integrated fashion
   through the use of the standard Internet SMI, MIB and Simple Network
   Management Protocol.

   DECnet Phase IV objects have been defined to be used in conjunction
   with the Internet MIB to allow access and control of these new
   objects by the Internet community. Additional support for other
   DECnet-based protocols such as RBMS (remote bridge management
   software) or other Digital Equipment Corporation Specific Hardware
   platforms is not included in this document.

2.  Selected Objects

   The objects included in this memo have been created from the DIGITAL
   Network Architecture Network Management Functional Specification
   Version 4.0.0 Dated July 1983. An attempt has been made to provide a
   reasonable ordering of these variables into groups. These groups are:

     o  System Group

     o  Network Management Group

     o  Session Group

     o  End Group

     o  Routing Group

     o  Circuit Group

     o  DDCMP Group

     o  DDCMP Multipoint Control Group

     o  Ethernet Group

     o  Counters Group




DECnet Phase IV MIB Working Group                               [Page 2]

RFC 1289                  DECnet Phase IV MIB              December 1991


     o  Adjacency Group

     o  Line Group

     o  Non Broadcast Line Group

     o  Area Group

   An effort has also been made to preserve the original syntax of the
   object wherever possible, for example, a DECnet Phase IV object is
   Executor State. This was originally coded as a NICE (Network
   Information and Control Exchange) data type which is a Coded single
   field object of 1 byte in length. When converted for inclusion into
   the Internet MIB using the Internet SMI, it became an enumerated
   integer.

3.  Objects

   All objects in this memo are described using the standard Internet
   SMI and BER of RFC 1155. A complete description of an object will
   include the name, syntax and encoding. Just as with objects supported
   in the MIB (RFC 1156), an object name is identified with an object
   identifier which has been administratively assigned. This identifies
   an Object Type. When an object type is combined with a specific
   instance, the particular object is uniquely identified. The use of
   Object Descriptors in this memo is consistent with that of RFC 1156 -
   they are text strings meant to be read by humans. The descriptors
   have been taken from the original DIGITAL Network Architecture
   Network Management Functional Specification Version 4.0.0 Dated July
   1983 which defined DECnet Phase IV objects. These names were then
   massaged to put them in a form as consistent as possible with object
   type names listed in the standard Internet MIB. Object defintion
   information is also taken directly from the Network Architecture
   Network Managment Functional Specification cited above wherever
   possible. In this document, EXECUTOR is intended to reference only
   the DECnet software and is not intended to effect any other protocols
   which may be running on the system.

3.1  Format of Definitions

   An object in this memo is specified by five fields of information:
   Object, Syntax, Definition, Access, and Status.

   The OBJECT is a textual name (OBJECT DESCRIPTOR) for that object type
   combined with an administratively obtained OBJECT IDENTIFIER.

   SYNTAX: For each object type, its abstract syntax is presented using
   the ASN.1 specified in RFC 1155.



DECnet Phase IV MIB Working Group                               [Page 3]

RFC 1289                  DECnet Phase IV MIB              December 1991


   DEFINITION: A general description of the object type. Its original
   purpose in the DECnet Phase IV environment is given so that all
   implementers and users will consistently interpret the information
   contained in each object type. Changes in format to make the object
   consistent with RFC 1155 are also noted.

   ACCESS: The standard access keywords supported in RFC 1156 are used.
   The keywords used in this MIB are: read-only, read-write, and, not-
   accessible.

   STATUS: The status field is used to describe with a single keyword
   whether the object type is mandatory or optional. Status keywords of
   obsolete and deprecated are not used in this memo since this is the
   first version of the DECnet Phase IV MIB.

3.2  Textual Conventions

   New datatypes have been introduced as a textual conventions in this
   DECnet Phase IV MIB document. The purpose of these additions is to
   facilitate understanding of new objects in this MIB. No changes to
   the SMI or the SNMP are necessary to support these conventions which
   are described in 4.0 (Object Definitions).

4.  Object Definitions

            RFC1289-phivMIB

            DEFINITIONS ::= BEGIN

            IMPORTS
               Gauge
                  FROM RFC1155-SMI
                OBJECT-TYPE
                   FROM RFC-1212
                mib-2, DisplayString
                  FROM RFC1213-MIB;

       -- DECNet Phase-IV MIB

            phiv             OBJECT IDENTIFIER ::= { mib-2 18 }

       -- textual conventions

       PhivAddr ::= OCTET STRING (SIZE (2))
       -- This data type is intended as a short word representation of
       -- standard DECnet Phase IV addresses. DECnet addresses are
       -- hierarchically structured numbers assigned to a particular
       -- DECnet node. The address is structured so that the area



DECnet Phase IV MIB Working Group                               [Page 4]

RFC 1289                  DECnet Phase IV MIB              December 1991


       -- number is contained in the most significant 6 bits of the
       -- first octet.  The next 2 bits of the first octet contain
       -- the first two bits of the host address.  The remainder of
       -- the host address is contained in the second octet.

       PhivCounter ::= INTEGER
       -- This data type has been created for DECnet  counters.  These
       -- counters latch at their maximum specified value until either
       -- the system is restared, or they are reset to zero by the user
       -- or management software.

       -- groups in the decnetiv mib

             phivSystem             OBJECT IDENTIFIER ::= { phiv 1 }
             phivManagement         OBJECT IDENTIFIER ::= { phiv 2 }
             session                OBJECT IDENTIFIER ::= { phiv 3 }
             end                    OBJECT IDENTIFIER ::= { phiv 4 }
             routing                OBJECT IDENTIFIER ::= { phiv 5 }
             circuit                OBJECT IDENTIFIER ::= { phiv 6 }
             ddcmp                  OBJECT IDENTIFIER ::= { phiv 7 }
             control                OBJECT IDENTIFIER ::= { phiv 8 }
             ethernet               OBJECT IDENTIFIER ::= { phiv 9 }
             counters               OBJECT IDENTIFIER ::= { phiv 10 }
             adjacency              OBJECT IDENTIFIER ::= { phiv 11 }
             line                   OBJECT IDENTIFIER ::= { phiv 12 }
             nonBroadcastLine       OBJECT IDENTIFIER ::= { phiv 14 }
             area                   OBJECT IDENTIFIER ::= { phiv 15 }

       -- System Group

       -- The implementation of the System Group is mandatory for
       -- all systems.

       phivSystemState OBJECT-TYPE
            SYNTAX INTEGER {
                on (1),
                off (2),
                shut (3),
                restricted (4)
            }
            ACCESS read-write
            STATUS mandatory
            DESCRIPTION
                "This represents the operational state of the executor
                node.
                The possible states are:
                ON          Allows logical links.
                OFF         Allows no new links, terminates existing



DECnet Phase IV MIB Working Group                               [Page 5]

RFC 1289                  DECnet Phase IV MIB              December 1991


                            links, and stops routing traffic through.
                SHUT        Allows no new logical links, does not
                            destroy existing logical links, and goes
                            to the OFF state when all logical links are
                            gone.
                RESTRICTED  Allows no new incoming logical links from
                            other nodes.

                NOTE: These values are incremented by one compared to
                the standard DECnet values in order to maintain
                compliance with RFC 1155)."
            ::= { phivSystem 1 }

       phivExecIdent OBJECT-TYPE
           SYNTAX DisplayString ( SIZE (0..32) )
           ACCESS read-write
           STATUS mandatory
           DESCRIPTION
               "This is a text string that describes the executor node
               (for example, 'Research Lab').  The string is up to 32
               characters of any type."
           ::= { phivSystem 2 }

       -- Network Management Group

       -- The implementation of the Network Management Group is
       -- mandatory for all systems which contain a DECnet style
       -- management version.


       phivMgmtMgmtVers OBJECT-TYPE
            SYNTAX DisplayString (SIZE (0..255) )
            ACCESS read-only
            STATUS mandatory
            DESCRIPTION
                "This is the read-only Network Management Version,
                consisting of the version number, the Engineering
                Change Order (ECO) number, and the user ECO number
                (for example, 3.0.0). This parameter applies to the
                executor node only."
            ::= { phivManagement 1 }

       -- Session Layer Group

       -- The implementation of the Session Layer Group is mandatory for
       -- all systems that implement session layer communications.





DECnet Phase IV MIB Working Group                               [Page 6]

RFC 1289                  DECnet Phase IV MIB              December 1991


       phivSessionSystemName OBJECT-TYPE
           SYNTAX DisplayString ( SIZE (0..6) )
           ACCESS read-only
           STATUS mandatory
           DESCRIPTION
               "Name to be associated with the node identification.
               Only one name can be assigned to a node address or a
               circuit identification. No name should be used more than
               once in a DECnet network. Node-name is one to six upper
               case alphanumeric characters with at least one alpha
               character. A length of 0 indicates no name."
           ::= { session 1 }

       phivSessionInTimer OBJECT-TYPE
           SYNTAX INTEGER (0..65535)
           ACCESS read-write
           STATUS mandatory
           DESCRIPTION
               "This value represents the maximum duration between the
               time a connect is received for a process at the
               executor node and the time that process accepts or
               rejects it. If the connect is not accepted or rejected
               by the user within the number of seconds specified,
               Session Control rejects it for the user.  A 0
               indicates no timer is running."
           ::= { session 2 }

       phivSessionOutTimer OBJECT-TYPE
           SYNTAX INTEGER (0..65535)
           ACCESS read-write
           STATUS mandatory