rfc1666.txt

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

      a BIND request.

3.2.3.  snaMgtTools group

   This is an optional group.  The snaMgtTools group consists of the
   following table:

      1) snaLuRtmTable - Each row contains Response Time Monitor (RTM)
      variables for an LU.  The table is indexed by Node and LU indices.
      Entries correspond to LU 2 entries in the snaLuAdminTable.  A
      Management Station can read collection of RTM statistics for a
      given LU.

3.2.4.  Conformance statement

   Compliance of the SNMPv2 management entity to the SNANAU MIB is
   defined in terms of following conformance units called groups.

   Unconditionally mandatory groups: snaNodeGroup, snaLuGroup,
   snaSessionGroup.

   Conditionally mandatory groups: snaPu20Group - mandatory only for
   those entities which implement PU type 2.0.  The snaMgtToolsRtmGroup
   - mandatory only for those entities which implement LU type 2 and
   RTM.

   Refinement of requirements for objects access: an Agent which does
   not implement row creation for snaNodeAdminTable
   snaNodeLinkAdminTable and snaLuAdminTable must at least support
   object modification requests (i.e., read-write access instead of
   read-create).

3.3.  SNANAU MIB special feature

   This section describes the mechanism used for row creation in the
   Admin tables and also presents critical state transitions for PUs,
   LUs and Sessions.






Kielczewski, Kostick & Shih                                     [Page 7]

RFC 1666                       SNANAU MIB                    August 1994


3.3.1.  Row Creation mechanism

   The row creation mechanism for the Admin tables in this MIB module is
   based on the use of the RowStatus object. Restriction of some
   operations for specific tables are described in each table.  In
   particular, before accepting the 'destroy' value for an entry, an
   Agent has to verify the operational state of the corresponding entry
   in the Oper table.

3.3.2.  State Diagrams

   The following state diagram models the state transitions for Nodes.
   When a row is created by a Management Station, an Agent creates the
   Oper table entry for that Node with the OperState equal to
   'inactive'. An Agent cannot accept any operations for that Node until
   the RowStatus is set to 'active'.

   OperState ->    inactive       active         waiting        stopping
   --------------I--------------I--------------I--------------I---------
   AdminState:   I              I              I              I
   active        I active       I active       I waiting      I no
                 I              I              I              I
   inactive      I inactive     I stopping     I inactive     I stopping
                                I or inactive  I

   The following state diagram models state transitions for Sessions.
   When a session goes to the 'unbound' state [1], the corresponding
   entry will be removed from the Session table by the Agent.

   OperState ->   unbound        pendingBind   bound      pendingUnbind
   --------------I--------------I--------------I----------I--------------
   AdminState:   I              I              I          I
   bound         I no           I no           I no       I no
                 I              I              I          I
   unbound       I unbound      I unbound      I unbound  I unbound
















Kielczewski, Kostick & Shih                                     [Page 8]

RFC 1666                       SNANAU MIB                    August 1994


4.  Object Definitions

SNA-NAU-MIB DEFINITIONS ::= BEGIN

-- This MIB module contains objects necessary
-- for management of the following SNA devices: PU types 1.0, 2.0, 2.1
-- and LU types 0, 1, 2, 3, 4, 7.  It also contains generic objects
-- which can be used to manage LU 6.2.

-- Naming conventions in this document:
-- The following names are used in object descriptors according to
-- SNA conventions.
-- The name 'PU' or 'Node' is used to describe Node type 1.0, 2.0 or
-- 2.1.
-- The name 'LU' is used to describe Logical Unit of type 0,1,2,3,
-- 4,7 or 6.2.



IMPORTS
        DisplayString, RowStatus, TimeStamp, InstancePointer
                FROM SNMPv2-TC

        Counter32, Gauge32, Integer32,
        OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE
                FROM SNMPv2-SMI

        MODULE-COMPLIANCE, OBJECT-GROUP
                FROM SNMPv2-CONF;


snanauMIB MODULE-IDENTITY
        LAST-UPDATED  "9405120900Z"
        ORGANIZATION  "IETF SNA NAU MIB Working Group"
        CONTACT-INFO
                "       Zbigniew Kielczewski
                        Eicon Technology Inc.
                        2196 32nd Avenue
                        Lachine, Que  H8T 3H7
                        Canada
                        Tel:    [phone]
                        E-mail: [e-mail]

                        Deirdre Kostick
                        Bellcore
                        331 Newman Springs Road
                        Red Bank, NJ 07701
                        Tel:    [phone]



Kielczewski, Kostick & Shih                                     [Page 9]

RFC 1666                       SNANAU MIB                    August 1994


                        E-mail: [e-mail]

                        Kitty Shih (editor)
                        Novell
                        890 Ross Drive
                        Sunnyvale, CA 94089
                        Tel:   [phone]
                        E-mail: [e-mail]"
        DESCRIPTION
                "This is the MIB module for objects used to
                 manage SNA devices."
::= { mib-2 34 }

-- The SNANAU MIB module contains an objects part and a conformance part.
-- Objects are organized into the following groups:
-- (1)snaNode group,
-- (2)snaLU group,
-- (3)snaMgtTools group.

snanauObjects   OBJECT IDENTIFIER ::= { snanauMIB 1 }

  snaNode       OBJECT IDENTIFIER ::= { snanauObjects 1 }
  snaLu         OBJECT IDENTIFIER ::= { snanauObjects 2 }
  snaMgtTools   OBJECT IDENTIFIER ::= { snanauObjects 3}


-- ***************************************************************
-- snaNode group
--
-- It contains Managed Objects related to any type of Node and
-- some specific objects for Node Type 2.0.
-- ***************************************************************


-- ***************************************************************
-- The following table contains generic Node configuration
-- parameters.
-- ***************************************************************

snaNodeAdminTable OBJECT-TYPE
        SYNTAX  SEQUENCE OF SnaNodeAdminEntry
        MAX-ACCESS  not-accessible
        STATUS  current
        DESCRIPTION
                "This table contains objects which describe the
                configuration parameters for an SNA Node.  Link
                specific configuration objects are contained in
                a separate MIB module (e.g., SNA DLC MIB)



Kielczewski, Kostick & Shih                                    [Page 10]

RFC 1666                       SNANAU MIB                    August 1994


                corresponding to the link type.
                The table snaNodeAdminLinkTable contains objects
                which identify the relationship between node instances
                and link instances.

                The entries (i.e., rows) in this table can be created
                by either an Agent or a Management Station.
                The Management Station can do this through setting
                the appropriate value in the snaNodeAdminRowStatus.

                The snaNodeAdminRowStatus object describes the
                status of an entry and is used to change the status
                of an entry.  The entry is deleted by an Agent based
                on the value of the snaNodeAdminRowStatus.

                The snaNodeAdminState object describes the desired
                operational state of a Node and is used to change the
                operational state of a Node.  For example, such
                information may be obtained from a configuration file.

                How an Agent or a Management Station obtains the
                initial value of each object at creation time is an
                implementation specific issue.

                For each entry in this table, there is a corresponding
                entry in the snaNodeOperTable.
                While the objects in this table describe the desired
                or configured operational values of the SNA Node, the
                actual runtime values are contained in
                snaNodeOperTable."
        ::= { snaNode 1 }

snaNodeAdminEntry OBJECT-TYPE
        SYNTAX  SnaNodeAdminEntry
        MAX-ACCESS  not-accessible
        STATUS  current
        DESCRIPTION
                "An entry contains the configuration parameters for
                one SNA Node instance. The objects in the entry
                have read-create access.
                An entry can be created, modified or deleted.  The
                object snaNodeAdminRowStatus is used (i.e., set) to
                create or delete a row entry."
        INDEX  { snaNodeAdminIndex }
        ::= { snaNodeAdminTable 1 }

SnaNodeAdminEntry ::= SEQUENCE {
        snaNodeAdminIndex



Kielczewski, Kostick & Shih                                    [Page 11]

RFC 1666                       SNANAU MIB                    August 1994


                Integer32,
        snaNodeAdminName
                DisplayString,
        snaNodeAdminType
                INTEGER,
        snaNodeAdminXidFormat
                INTEGER,
        snaNodeAdminBlockNum
                DisplayString,
        snaNodeAdminIdNum
                DisplayString,
        snaNodeAdminEnablingMethod
                INTEGER,
        snaNodeAdminLuTermDefault
                INTEGER,
        snaNodeAdminMaxLu
                Integer32,
        snaNodeAdminHostDescription
                DisplayString,
        snaNodeAdminStopMethod
                INTEGER,
        snaNodeAdminState
                INTEGER,
        snaNodeAdminRowStatus
                RowStatus
        }

snaNodeAdminIndex OBJECT-TYPE
        SYNTAX  Integer32
        MAX-ACCESS  not-accessible
        STATUS  current
        DESCRIPTION
                "Index used to uniquely identify each Node instance.
                If an Agent creates the entry, then it will assign
                this number otherwise a Management Station
                generates a random number when it reserves the
                entry for creation."
        ::= { snaNodeAdminEntry 1 }

snaNodeAdminName OBJECT-TYPE
        SYNTAX  DisplayString (SIZE(0..17))
        MAX-ACCESS  read-create
        STATUS  current
        DESCRIPTION
                "The value indicates the desired name of the
                Node for use during Node activation.
                In Type 2.1 networks, this is a fully-qualified name,
                meaning that the Node name is preceded by the NetId (if



Kielczewski, Kostick & Shih                                    [Page 12]

RFC 1666                       SNANAU MIB                    August 1994


                present) with a period as the delimiter.

                A write operation to this object will
                not change the operational value reflected
                in snaNodeOperName until the Node has
                been re-activated (e.g., after the next initialization
                of the SNA services)."
        ::= { snaNodeAdminEntry 2 }

snaNodeAdminType OBJECT-TYPE
        SYNTAX  INTEGER {
                other(1),
                pu10(2),
                pu20(3),
                t21len(4),
                endNode(5),
                networkNode(6)
                }
        MAX-ACCESS  read-create
        STATUS  current
        DESCRIPTION
                "The value indicates the type of SNA Node.