rfc2232.txt

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

Network Working Group                                B. Clouston, Editor
Request for Comments: 2232                                 Cisco Systems
Category: Standards Track                               B. Moore, Editor
                                                         IBM Corporation
                                                           November 1997


                     Definitions of Managed Objects
                          for DLUR 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.

Copyright Notice

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

Table of Contents

   1.     Status of this Memo  ....................................  1
   2.     Introduction  ...........................................  1
   3.     The SNMP Network Management Framework  ..................  2
   4.     Overview  ...............................................  2
   4.1      DLUR MIB structure ....................................  3
   5.     Definitions  ............................................  5
   6.     Acknowledgments  ........................................ 18
   7.     References  ............................................. 19
   8.     Security Considerations  ................................ 19
   9.     Authors' Addresses  ..................................... 20
   10.    Full Copyright Statement ................................ 21

2.  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 monitoring and controlling
   network devices with DLUR (Dependent LU Requester) capabilities.
   This memo identifies managed objects for the DLUR protocol.







Clouston & Moore            Standards Track                     [Page 1]

RFC 2232         Managed Objects for DLUR using SMIv2      November 1997


3.  The SNMP Network Management Framework

   The SNMP Network Management Framework consists of several components.
   For the purpose of this specification, the applicable components of
   the Framework are the SMI and related documents [1, 2, 3], which
   define the mechanisms used for describing and naming objects for the
   purpose of management.

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

4.  Overview

   This document identifies objects for monitoring the configuration and
   active characteristics of devices with DLUR capabilities.  Dependent
   LU requester/server (DLUR/S) is an extension to the Advanced Peer-
   to-Peer Networking (APPN) architecture that provides dependent LU
   services in APPN networks.  See the SNANAU APPN MIB [4] for
   management of APPN networks.

   The base APPN architecture only provided for transport of data
   between independent logical units (LUs).  However, customers have an
   enormous investment in applications based on dependent LU types.
   DLUR/S provides for support of dependent LU sessions in an APPN
   network.

   A dependent LU server (DLUS) is an APPN node that provides System
   Services Control Point (SSCP) services over an APPN network to remote
   secondary dependent LUs by using SSCP-PU (physical unit) and SSCP-LU
   sessions whose flows are encapsulated on LU 6.2 session flows between
   the DLUS node and the appropriate dependent LU requester (DLUR) node.
   The secondary dependent LUs may be local to the DLUR node, or in
   adjacent type 2.0 or 2.1 nodes.

   The LU 6.2 control sessions between a DLUS node and a DLUR node are
   referred to as a CPSVRMGR pipe.  CPSVRMGR refers to the mode used for
   the sessions.

   In this document, we describe DLUR managed objects.

   The DLUR terms and overall architecture are described in [5].

   Highlights of the management functions supported by the DLUR MIB
   module include the following:







Clouston & Moore            Standards Track                     [Page 2]

RFC 2232         Managed Objects for DLUR using SMIv2      November 1997


   o    Identifying the node's DLUR capabilities

   o    Displaying the physical units (PUs) this node is supporting

   o    Identification of Dependent LU Servers

   o    Displaying the state of control sessions to Dependent LU
        Servers.

   This MIB module does not support:

   o    Management of dependent LU servers

   o    Configuration of DLUR nodes.

   o    Changing the state of control session to the DLUS

   o    Displaying the dependent LUs this node is supporting

   o    Traps.  The APPN MIB contains a trap for Alert conditions that
        may affect DLUR resources.  The value for the affectedObject
        object contained in the alertTrap is determined by the
        implementation.  It may contain a VariablePointer from the DLUR
        MIB.  The APPN/DLUR Alerts are defined in [6].

4.1.  DLUR MIB Structure

   Although DLUR is an extension to APPN, the DLUR MIB relies very
   little upon the APPN MIB.  The dlurNodeCpName object in this MIB has
   the same value as the appnNodeCpName object in the APPN MIB.  If the
   dlurPuLsName object in the MIB has the same value as the appnLsName
   object in the APPN MIB, then the two objects are referring to the
   same link station.

   The DLUR MIB module contains the following collections of objects:

   o    dlurNodeInfo--objects representing the capabilities and
        architecture options supported by the DLUR implementation, as
        well as default primary and backup DLUSs.

   o    dlurPuInfo--objects describing the PUs that this APPN node is
        supporting with DLUR.

   o    dlurDlusInfo--objects describing the control sessions with
        DLUSs.

   These are described below in more detail.




Clouston & Moore            Standards Track                     [Page 3]

RFC 2232         Managed Objects for DLUR using SMIv2      November 1997


4.1.1.  dlurNodeInfo group

   The dlurNodeInfo group consists of the following objects and table:

   1) dlurNodeCapabilities group

   These objects represent the capabilities and options of the DLUR
   implementation, such as the release level of the implementation

   2) dlurDefaultDefBackupDlusTable

   This table identifies the list of defined backup DLUSs for all PUs
   served by this DLUR, if there is no specific DLUS backup list for the
   PU.  The list is in descending order of preference as a backup DLUS.

4.1.2.  dlurPuInfo group

   The dlurPuInfo group consists of the following tables:

   1) dlurPuTable

   This table has an entry for each PU this node is supporting via DLUR,
   including the locally known name, the SSCP supplied name (if known),
   and the PU status.

   2) dlurPuDefBackupDlusTable

   This table contains the backup DLUS list defined on a PU basis.  The
   table has an entry for each specifically defined backup DLUS on each
   PU.  The first index to the entry is the PU name, which organizes the
   table by PU name. The second index is a ranking which further sorts
   the table in descending order of preference as a backup DLUS for the
   PU.

   If a PU name is not found in this table, the
   dlurDefaultDefBackupDlusNameTable is used as a backup list for that
   PU.

4.1.3.  dlurDlusInfo group

   This group consists of the following table:

   1) dlurDlusTable

   This table contains information about the control sessions (CPSVRMGR
   pipes) with the DLUS, including the control point (CP) name of the
   DLUS and the status of the control session.




Clouston & Moore            Standards Track                     [Page 4]

RFC 2232         Managed Objects for DLUR using SMIv2      November 1997


5.  Definitions

APPN-DLUR-MIB DEFINITIONS ::= BEGIN

IMPORTS
        DisplayString, TruthValue
                FROM SNMPv2-TC

        OBJECT-TYPE, MODULE-IDENTITY, Unsigned32
                FROM SNMPv2-SMI

        MODULE-COMPLIANCE, OBJECT-GROUP
                FROM SNMPv2-CONF

        snanauMIB
                FROM SNA-NAU-MIB

        SnaControlPointName
                FROM APPN-MIB;

dlurMIB MODULE-IDENTITY
        LAST-UPDATED  "9705101500Z"
        ORGANIZATION  "IETF SNA NAU MIB WG / AIW APPN/HPR MIBs SIG"
        CONTACT-INFO

                "
                        Bob Clouston
                        Cisco Systems
                        7025 Kit Creek Road
                        P.O. Box 14987
                        Research Triangle Park, NC 27709, USA
                        Tel:    [phone]
                        E-mail: [e-mail]

                        Bob Moore
                        IBM Corporation
                        800 Park Offices Drive
                        RHJA/664
                        P.O. Box 12195
                        Research Triangle Park, NC 27709, USA
                        Tel:    [phone]
                        E-mail: [e-mail]
                "
      DESCRIPTION
                "This is the MIB module for objects used to manage
                network devices with DLUR capabilities.  This MIB
                contains information that is useful for managing an APPN
                product that implements a DLUR (Dependent Logical Unit



Clouston & Moore            Standards Track                     [Page 5]

RFC 2232         Managed Objects for DLUR using SMIv2      November 1997


                Requester).  The DLUR product has a client/server
                relationship with an APPN product that implements a DLUS
                (Dependent Logical Unit Server)."

::= { snanauMIB 5 }
-- snanauMIB ::= { mib-2 34 }

-- *********************************************************************
-- Textual Convention
-- *********************************************************************
-- SnaControlPointName is imported from the APPN MIB

-- *********************************************************************
  dlurObjects OBJECT IDENTIFIER ::= { dlurMIB 1 }
-- *********************************************************************


dlurNodeInfo OBJECT IDENTIFIER ::= { dlurObjects 1 }
-- *********************************************************************
-- DLUR Capabilities of the node
--
--  This group represents the capabilities and options of the DLUR
--  implementation.
-- *********************************************************************
dlurNodeCapabilities OBJECT IDENTIFIER ::= { dlurNodeInfo 1 }

dlurNodeCpName OBJECT-TYPE
      SYNTAX SnaControlPointName
      MAX-ACCESS read-only
      STATUS current
      DESCRIPTION
          "Administratively assigned network name for the APPN node where
          this DLUR implementation resides.  If this object has the same
          value as the appnNodeCpName object in the APPN MIB, then the
          two objects are referring to the same APPN node."

      ::= { dlurNodeCapabilities 1 }

dlurReleaseLevel OBJECT-TYPE
      SYNTAX DisplayString (SIZE (2))
      MAX-ACCESS read-only
      STATUS current
      DESCRIPTION
          "The DLUR release level of this implementation.  This is the
          value that is encoded in the DLUR/DLUS Capabilites (CV 51).
          To insure consistent display, this one-byte value is encoded
          here as two displayable characters that are equivalent to a
          hexadecimal display.  For example, if the one-byte value as



Clouston & Moore            Standards Track                     [Page 6]

RFC 2232         Managed Objects for DLUR using SMIv2      November 1997


          encoded in CV51 is X'01', this object will contain the
          displayable string '01'."

      ::= { dlurNodeCapabilities 2 }

dlurAnsSupport OBJECT-TYPE
      SYNTAX INTEGER {
                     continueOrStop(1),
                     stopOnly(2)
                     }
      MAX-ACCESS read-only
      STATUS current
      DESCRIPTION
          "Automatic Network Shutdown (ANS) capability of this node.

              -  'continueOrStop' indicates that the DLUR implementation
                 supports either ANS value (continue or stop) as
                 specified by the DLUS on ACTPU for each PU.

              -  'stopOnly' indicates that the DLUR implementation only
                 supports the ANS value of stop.

           ANS = continue means that the DLUR node will keep LU-LU
           sessions active even if SSCP-PU and SSCP-LU control sessions
           are interrupted.

           ANS = stop means that LU-LU sessions will be interrupted when
           the SSCP-PU and SSCP-LU sessions are interrupted."

      ::= { dlurNodeCapabilities 3 }

dlurMultiSubnetSupport OBJECT-TYPE
      SYNTAX TruthValue
      MAX-ACCESS read-only
      STATUS current
      DESCRIPTION
          "Indication of whether this DLUR implementation can support
          CPSVRMGR sessions that cross NetId boundaries."

      ::= { dlurNodeCapabilities 4 }

dlurDefaultDefPrimDlusName OBJECT-TYPE
      SYNTAX SnaControlPointName
      MAX-ACCESS read-only
      STATUS current
      DESCRIPTION
          "The SNA name of the defined default primary DLUS for all of
          the PUs served by this DLUR.  This can be overridden for a



Clouston & Moore            Standards Track                     [Page 7]