RFC2232 日本語訳

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

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

Definitions of Managed Objects for DLUR using SMIv2

Status of this Memo

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.

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 Notice

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

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

Table of Contents

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

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

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.

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

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

3.  The SNMP Network Management Framework

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 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.

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

4.  Overview

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.

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.

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.

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.

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.

In this document, we describe DLUR managed objects.

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

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

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

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

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

   o    Identifying the node's DLUR capabilities

o Identifying the node's DLUR capabilities

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

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

   o    Identification of Dependent LU Servers

o Identification of Dependent LU Servers

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

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

   This MIB module does not support:

This MIB module does not support:

   o    Management of dependent LU servers

o Management of dependent LU servers

   o    Configuration of DLUR nodes.

o Configuration of DLUR nodes.

   o    Changing the state of control session to the DLUS

o Changing the state of control session to the DLUS

   o    Displaying the dependent LUs this node is supporting

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].

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

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.

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:

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 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 dlurPuInfo--objects describing the PUs that this APPN node is supporting with DLUR.

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

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

   These are described below in more detail.

These are described below in more detail.

Clouston & Moore            Standards Track                     [Page 3]

RFC 2232         Managed Objects for DLUR using SMIv2      November 1997

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

4.1.1.  dlurNodeInfo group

4.1.1. dlurNodeInfo group

   The dlurNodeInfo group consists of the following objects and table:

The dlurNodeInfo group consists of the following objects and table:

   1) dlurNodeCapabilities group

1) dlurNodeCapabilities group

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

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

   2) dlurDefaultDefBackupDlusTable

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.

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

4.1.2. dlurPuInfo group

   The dlurPuInfo group consists of the following tables:

The dlurPuInfo group consists of the following tables:

   1) dlurPuTable

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.

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

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.

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.

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

4.1.3. dlurDlusInfo group

   This group consists of the following table:

This group consists of the following table:

   1) dlurDlusTable

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.

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

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

5.  Definitions

5. Definitions

APPN-DLUR-MIB DEFINITIONS ::= BEGIN

APPN-DLUR-MIB DEFINITIONS ::= BEGIN

IMPORTS
        DisplayString, TruthValue
                FROM SNMPv2-TC

IMPORTS DisplayString, TruthValue FROM SNMPv2-TC

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

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

        MODULE-COMPLIANCE, OBJECT-GROUP
                FROM SNMPv2-CONF

MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF

        snanauMIB
                FROM SNA-NAU-MIB

snanauMIB FROM SNA-NAU-MIB

        SnaControlPointName
                FROM APPN-MIB;

SnaControlPointName FROM APPN-MIB;

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

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:    1 919 472 2333
                        E-mail: clouston@cisco.com

" Bob Clouston Cisco Systems 7025 Kit Creek Road P.O. Box 14987 Research Triangle Park, NC 27709, USA Tel: 1 919 472 2333 E-mail: clouston@cisco.com

                        Bob Moore
                        IBM Corporation
                        800 Park Offices Drive
                        RHJA/664
                        P.O. Box 12195
                        Research Triangle Park, NC 27709, USA
                        Tel:    1 919 254 4436
                        E-mail: remoore@ralvm6.vnet.ibm.com
                "
      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

Bob Moore IBM Corporation 800 Park Offices Drive RHJA/664 P.O. Box 12195 Research Triangle Park, NC 27709, USA Tel: 1 919 254 4436 E-mail: remoore@ralvm6.vnet.ibm.com " 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

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)."

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 }

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

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

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

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

-- ********************************************************************* 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 }

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."

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 }

::= { 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

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

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'."

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

      ::= { dlurNodeCapabilities 2 }

::= { 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.

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.

- '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.

- '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 = 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."

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

      ::= { dlurNodeCapabilities 3 }

::= { 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."

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 }

::= { 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

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]

RFC 2232         Managed Objects for DLUR using SMIv2      November 1997

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

          particular PU by a defined primary DLUS for that PU,
          represented by the dlurPuDefPrimDlusName object."

particular PU by a defined primary DLUS for that PU, represented by the dlurPuDefPrimDlusName object."

      ::= { dlurNodeCapabilities 5 }

::= { dlurNodeCapabilities 5 }

dlurNetworkNameForwardingSupport OBJECT-TYPE
      SYNTAX TruthValue
      MAX-ACCESS read-only
      STATUS current
      DESCRIPTION
          "Indication of whether this DLUR implementation supports
          forwarding of Network Name control vectors on ACTPUs and
          ACTLUs to DLUR-served PUs and their associated LUs.

dlurNetworkNameForwardingSupport OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-only STATUS current DESCRIPTION "Indication of whether this DLUR implementation supports forwarding of Network Name control vectors on ACTPUs and ACTLUs to DLUR-served PUs and their associated LUs.

          This object corresponds to byte 9. bit 3 of cv51."

This object corresponds to byte 9. bit 3 of cv51."

      ::= { dlurNodeCapabilities 6 }

::= { dlurNodeCapabilities 6 }

dlurNondisDlusDlurSessDeactSup OBJECT-TYPE
      SYNTAX TruthValue
      MAX-ACCESS read-only
      STATUS current
      DESCRIPTION
          "Indication of whether this DLUR implementation supports
          nondisruptive deactivation of its DLUR-DLUS sessions.
          Upon receiving from a DLUS an UNBIND for the CPSVRMGR pipe
          with sense data X'08A0 000B', a DLUR that supports this
          option immediately begins attempting to activate a CPSVRMGR
          pipe with a DLUS other than the one that sent the UNBIND.

dlurNondisDlusDlurSessDeactSup OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-only STATUS current DESCRIPTION "Indication of whether this DLUR implementation supports nondisruptive deactivation of its DLUR-DLUS sessions. Upon receiving from a DLUS an UNBIND for the CPSVRMGR pipe with sense data X'08A0 000B', a DLUR that supports this option immediately begins attempting to activate a CPSVRMGR pipe with a DLUS other than the one that sent the UNBIND.

          This object corresponds to byte 9. bit 4 of cv51."

This object corresponds to byte 9. bit 4 of cv51."

      ::= { dlurNodeCapabilities 7 }

::= { dlurNodeCapabilities 7 }

-- *********************************************************************
-- DLUR default defined backup DLUS table
-- *********************************************************************

-- ********************************************************************* -- DLUR default defined backup DLUS table -- *********************************************************************

dlurDefaultDefBackupDlusTable OBJECT-TYPE
      SYNTAX SEQUENCE OF DlurDefaultDefBackupDlusEntry
      MAX-ACCESS not-accessible
      STATUS current
      DESCRIPTION
          "This table contains an ordered list of defined backup DLUSs
          for all of the PUs served by this DLUR.  These can be
          overridden for a particular PU by a list of defined backup
          DLUSs for that PU, represented by the
          dlurPuDefBackupDlusNameTable.  Entries in this table are

dlurDefaultDefBackupDlusTable OBJECT-TYPE SYNTAX SEQUENCE OF DlurDefaultDefBackupDlusEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains an ordered list of defined backup DLUSs for all of the PUs served by this DLUR. These can be overridden for a particular PU by a list of defined backup DLUSs for that PU, represented by the dlurPuDefBackupDlusNameTable. Entries in this table are

Clouston & Moore            Standards Track                     [Page 8]

RFC 2232         Managed Objects for DLUR using SMIv2      November 1997

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

          ordered from most preferred default backup DLUS to least
          preferred."

ordered from most preferred default backup DLUS to least preferred."

      ::= { dlurNodeInfo 2 }

::= { dlurNodeInfo 2 }

dlurDefaultDefBackupDlusEntry OBJECT-TYPE
      SYNTAX DlurDefaultDefBackupDlusEntry
      MAX-ACCESS not-accessible
      STATUS current
      DESCRIPTION
          "This table is indexed by an integer-valued index, which
          orders the entries from most preferred default backup DLUS
          to least preferred."

dlurDefaultDefBackupDlusEntry OBJECT-TYPE SYNTAX DlurDefaultDefBackupDlusEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table is indexed by an integer-valued index, which orders the entries from most preferred default backup DLUS to least preferred."

      INDEX { dlurDefaultDefBackupDlusIndex }

INDEX { dlurDefaultDefBackupDlusIndex }

      ::= { dlurDefaultDefBackupDlusTable 1 }

::= { dlurDefaultDefBackupDlusTable 1 }

DlurDefaultDefBackupDlusEntry ::= SEQUENCE {
      dlurDefaultDefBackupDlusIndex      Unsigned32,
      dlurDefaultDefBackupDlusName       SnaControlPointName
                     }

DlurDefaultDefBackupDlusEntry ::= SEQUENCE { dlurDefaultDefBackupDlusIndex Unsigned32, dlurDefaultDefBackupDlusName SnaControlPointName }

dlurDefaultDefBackupDlusIndex OBJECT-TYPE
      SYNTAX Unsigned32 (1..4294967295)
      MAX-ACCESS not-accessible
      STATUS current
      DESCRIPTION
          "Index for this table.  The index values start at 1,
          which identifies the most preferred default backup DLUS."

dlurDefaultDefBackupDlusIndex OBJECT-TYPE SYNTAX Unsigned32 (1..4294967295) MAX-ACCESS not-accessible STATUS current DESCRIPTION "Index for this table. The index values start at 1, which identifies the most preferred default backup DLUS."

      ::= { dlurDefaultDefBackupDlusEntry 1 }

::= { dlurDefaultDefBackupDlusEntry 1 }

dlurDefaultDefBackupDlusName OBJECT-TYPE
      SYNTAX SnaControlPointName
      MAX-ACCESS read-only
      STATUS current
      DESCRIPTION
          "Fully qualified name of a default backup DLUS for PUs served
          by this DLUR."

dlurDefaultDefBackupDlusName OBJECT-TYPE SYNTAX SnaControlPointName MAX-ACCESS read-only STATUS current DESCRIPTION "Fully qualified name of a default backup DLUS for PUs served by this DLUR."

      ::= { dlurDefaultDefBackupDlusEntry 2 }

::= { dlurDefaultDefBackupDlusEntry 2 }

-- *********************************************************************
-- PU Information
--
--  The following table carries information about the PUs that this APPN
--  node is supporting via DLUR.

-- ********************************************************************* -- PU Information -- -- The following table carries information about the PUs that this APPN -- node is supporting via DLUR.

Clouston & Moore            Standards Track                     [Page 9]

RFC 2232         Managed Objects for DLUR using SMIv2      November 1997

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

-- *********************************************************************
dlurPuInfo OBJECT IDENTIFIER ::= { dlurObjects 2 }

-- ********************************************************************* dlurPuInfo OBJECT IDENTIFIER ::= { dlurObjects 2 }

dlurPuTable OBJECT-TYPE
      SYNTAX SEQUENCE OF DlurPuEntry
      MAX-ACCESS not-accessible
      STATUS current
      DESCRIPTION
          "Information about the PUs supported by this DLUR."

dlurPuTable OBJECT-TYPE SYNTAX SEQUENCE OF DlurPuEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Information about the PUs supported by this DLUR."

      ::= { dlurPuInfo 1 }

::= { dlurPuInfo 1 }

dlurPuEntry OBJECT-TYPE
      SYNTAX DlurPuEntry
      MAX-ACCESS not-accessible
      STATUS current
      DESCRIPTION
          "Entry in a table of PU information, indexed by PU name."

dlurPuEntry OBJECT-TYPE SYNTAX DlurPuEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Entry in a table of PU information, indexed by PU name."

      INDEX { dlurPuName  }

INDEX { dlurPuName }

      ::= { dlurPuTable 1 }

::= { dlurPuTable 1 }

DlurPuEntry ::= SEQUENCE {
      dlurPuName                  DisplayString,
      dlurPuSscpSuppliedName      DisplayString,
      dlurPuStatus                INTEGER,
      dlurPuAnsSupport            INTEGER,
      dlurPuLocation              INTEGER,
      dlurPuLsName                DisplayString,
      dlurPuDlusSessnStatus       INTEGER,
      dlurPuActiveDlusName        DisplayString,
      dlurPuDefPrimDlusName       DisplayString
                     }

DlurPuEntry ::= SEQUENCE { dlurPuName DisplayString, dlurPuSscpSuppliedName DisplayString, dlurPuStatus INTEGER, dlurPuAnsSupport INTEGER, dlurPuLocation INTEGER, dlurPuLsName DisplayString, dlurPuDlusSessnStatus INTEGER, dlurPuActiveDlusName DisplayString, dlurPuDefPrimDlusName DisplayString }

dlurPuName OBJECT-TYPE
      SYNTAX DisplayString (SIZE (1..17))
      MAX-ACCESS not-accessible
      STATUS current
      DESCRIPTION
          "Locally administered name of the PU."

dlurPuName OBJECT-TYPE SYNTAX DisplayString (SIZE (1..17)) MAX-ACCESS not-accessible STATUS current DESCRIPTION "Locally administered name of the PU."

      ::= { dlurPuEntry 1 }

::= { dlurPuEntry 1 }

dlurPuSscpSuppliedName OBJECT-TYPE
      SYNTAX DisplayString (SIZE (0..17))
      MAX-ACCESS read-only

dlurPuSscpSuppliedName OBJECT-TYPE SYNTAX DisplayString (SIZE (0..17)) MAX-ACCESS read-only

Clouston & Moore            Standards Track                    [Page 10]

RFC 2232         Managed Objects for DLUR using SMIv2      November 1997

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

      STATUS current
      DESCRIPTION
          "The SNA name of the PU.  This value is supplied to a PU by the
          SSCP that activated it.  If a value has not been supplied, a
          zero-length string is returned."

STATUS current DESCRIPTION "The SNA name of the PU. This value is supplied to a PU by the SSCP that activated it. If a value has not been supplied, a zero-length string is returned."

      ::= { dlurPuEntry 2 }

::= { dlurPuEntry 2 }

dlurPuStatus OBJECT-TYPE
      SYNTAX INTEGER {
                      reset(1),
                      pendReqActpuRsp(2),
                      pendActpu(3),
                      pendActpuRsp(4),
                      active(5),
                      pendLinkact(6),
                      pendDactpuRsp(7),
                      pendInop(8),
                      pendInopActpu(9)
                     }
      MAX-ACCESS read-only
      STATUS current
      DESCRIPTION
          "Status of the DLUR-supported PU.  The following values are
          defined:

dlurPuStatus OBJECT-TYPE SYNTAX INTEGER { reset(1), pendReqActpuRsp(2), pendActpu(3), pendActpuRsp(4), active(5), pendLinkact(6), pendDactpuRsp(7), pendInop(8), pendInopActpu(9) } MAX-ACCESS read-only STATUS current DESCRIPTION "Status of the DLUR-supported PU. The following values are defined:

             reset(1)           -  reset
             pendReqActpuRsp(2) -  pending a response from the DLUS
                                   to a Request ACTPU
             pendActpu(3)       -  pending an ACTPU from the DLUS
             pendActpuRsp(4)    -  pending an ACTPU response from the PU
             active(5)          -  active
             pendLinkact(6)     -  pending activation of the link to a
                                   downstream PU
             pendDactpuRsp(7)   -  pending a DACTPU response from the PU
             pendInop(8)        -  the CPSVRMGR pipe became inoperative
                                   while the DLUR was pending an ACTPU
                                   response from the PU
             pendInopActpu(9)   -  when the DLUR was in the pendInop
                                   state, a CPSVRMGR pipe became active
                                   and a new ACTPU was received over it,
                                   before a response to the previous
                                   ACTPU was received from the PU."

reset(1) - reset pendReqActpuRsp(2) - pending a response from the DLUS to a Request ACTPU pendActpu(3) - pending an ACTPU from the DLUS pendActpuRsp(4) - pending an ACTPU response from the PU active(5) - active pendLinkact(6) - pending activation of the link to a downstream PU pendDactpuRsp(7) - pending a DACTPU response from the PU pendInop(8) - the CPSVRMGR pipe became inoperative while the DLUR was pending an ACTPU response from the PU pendInopActpu(9) - when the DLUR was in the pendInop state, a CPSVRMGR pipe became active and a new ACTPU was received over it, before a response to the previous ACTPU was received from the PU."

      ::= { dlurPuEntry 3 }

::= { dlurPuEntry 3 }

dlurPuAnsSupport OBJECT-TYPE
      SYNTAX INTEGER {

dlurPuAnsSupport OBJECT-TYPE SYNTAX INTEGER {

Clouston & Moore            Standards Track                    [Page 11]

RFC 2232         Managed Objects for DLUR using SMIv2      November 1997

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

                     continue(1),
                     stop(2)
                     }
      MAX-ACCESS read-only
      STATUS current
      DESCRIPTION
          "The Automatic Network Shutdown (ANS) support configured for
          this PU.  This value (as configured by the network
          administrator) is sent by DLUS with ACTPU for each PU.

continue(1), stop(2) } MAX-ACCESS read-only STATUS current DESCRIPTION "The Automatic Network Shutdown (ANS) support configured for this PU. This value (as configured by the network administrator) is sent by DLUS with ACTPU for each PU.

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

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

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

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

      ::= { dlurPuEntry 4 }

::= { dlurPuEntry 4 }

dlurPuLocation OBJECT-TYPE
      SYNTAX INTEGER {
                      internal(1),
                      downstream(2) }
      MAX-ACCESS read-only
      STATUS current
      DESCRIPTION
          "Location of the DLUR-support PU:
              internal(1)   - internal to the APPN node itself (no link)
              downstream(2) - downstream of the APPN node (connected via
                              a link)."

dlurPuLocation OBJECT-TYPE SYNTAX INTEGER { internal(1), downstream(2) } MAX-ACCESS read-only STATUS current DESCRIPTION "Location of the DLUR-support PU: internal(1) - internal to the APPN node itself (no link) downstream(2) - downstream of the APPN node (connected via a link)."

      ::= { dlurPuEntry 5 }

::= { dlurPuEntry 5 }

dlurPuLsName OBJECT-TYPE
      SYNTAX DisplayString (SIZE (0..10))
      MAX-ACCESS read-only
      STATUS current
      DESCRIPTION
          "Administratively assigned name of the link station through
          which a downstream PU is connected to this DLUR.  A zero-length
          string is returned for internal PUs.  If this object has the
          same value as the appnLsName object in the APPN MIB, then the
          two are identifying the same link station."

dlurPuLsName OBJECT-TYPE SYNTAX DisplayString (SIZE (0..10)) MAX-ACCESS read-only STATUS current DESCRIPTION "Administratively assigned name of the link station through which a downstream PU is connected to this DLUR. A zero-length string is returned for internal PUs. If this object has the same value as the appnLsName object in the APPN MIB, then the two are identifying the same link station."

      ::= { dlurPuEntry 6 }

::= { dlurPuEntry 6 }

dlurPuDlusSessnStatus OBJECT-TYPE
      SYNTAX INTEGER {

dlurPuDlusSessnStatus OBJECT-TYPE SYNTAX INTEGER {

Clouston & Moore            Standards Track                    [Page 12]

RFC 2232         Managed Objects for DLUR using SMIv2      November 1997

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

                      reset(1),
                      pendingActive(2),
                      active(3),
                      pendingInactive(4)
                     }
      MAX-ACCESS read-only
      STATUS current
      DESCRIPTION
          "Status of the control session to the DLUS identified in
          dlurPuActiveDlusName.  This is a combination of the separate
          states for the contention-winner and contention-loser sessions:

reset(1), pendingActive(2), active(3), pendingInactive(4) } MAX-ACCESS read-only STATUS current DESCRIPTION "Status of the control session to the DLUS identified in dlurPuActiveDlusName. This is a combination of the separate states for the contention-winner and contention-loser sessions:

          reset(1)           - none of the cases below
          pendingActive(2)   - either contention-winner session or
                               contention-loser session is pending active
          active(3)          - contention-winner and contention-loser
                               sessions are both active
          pendingInactive(4) - either contention-winner session or
                               contention-loser session is pending
                               inactive - this test is made AFTER the
                               'pendingActive' test.

reset(1) - none of the cases below pendingActive(2) - either contention-winner session or contention-loser session is pending active active(3) - contention-winner and contention-loser sessions are both active pendingInactive(4) - either contention-winner session or contention-loser session is pending inactive - this test is made AFTER the 'pendingActive' test.

          The following matrix provides a different representation of
          how the values of this object are related to the individual
          states of the contention-winner and contention-loser sessions:

The following matrix provides a different representation of how the values of this object are related to the individual states of the contention-winner and contention-loser sessions:

               Conwinner
               | pA | pI | A | X = !(pA | pI | A)
          C ++++++++++++++++++++++++++++++++++
          o pA | 2  |  2 | 2 | 2
          n ++++++++++++++++++++++++++++++++++
          l pI | 2  |  4 | 4 | 4
          o ++++++++++++++++++++++++++++++++++
          s A  | 2  |  4 | 3 | 1
          e ++++++++++++++++++++++++++++++++++
          r X  | 2  |  4 | 1 | 1
            ++++++++++++++++++++++++++++++++++
          "

Conwinner | pA | pI | A | X = !(pA | pI | A) C ++++++++++++++++++++++++++++++++++ o pA | 2 | 2 | 2 | 2 n ++++++++++++++++++++++++++++++++++ l pI | 2 | 4 | 4 | 4 o ++++++++++++++++++++++++++++++++++ s A | 2 | 4 | 3 | 1 e ++++++++++++++++++++++++++++++++++ r X | 2 | 4 | 1 | 1 ++++++++++++++++++++++++++++++++++ "

      ::= { dlurPuEntry 7 }

::= { dlurPuEntry 7 }

dlurPuActiveDlusName OBJECT-TYPE
      SYNTAX DisplayString (SIZE (0..17))
      MAX-ACCESS read-only
      STATUS current
      DESCRIPTION
          "The SNA name of the active DLUS for this PU.  If its length
          is not zero, this name follows the SnaControlPointName textual

「SNAはアクティブなDLUSについてこのPUにちなんで命名する」dlurPuActiveDlusName OBJECT-TYPE SYNTAX DisplayString(SIZE(0 .17))のマックス-ACCESSの書き込み禁止のSTATUSの現在の記述。 この名前が長さがゼロでないなら、SnaControlPointNameに続く、原文

Clouston & Moore            Standards Track                    [Page 13]

RFC 2232         Managed Objects for DLUR using SMIv2      November 1997

SMIv2 November 1997を使用するDLURのためのCloustonとムーア標準化過程[13ページ]RFC2232管理オブジェクト

          convention.  A zero-length string indicates that the PU does
          not currently have an active DLUS."

コンベンション。 「ゼロ長ストリングは、PUにはアクティブなDLUSが現在ないのを示します。」

      ::= { dlurPuEntry 8 }

::= dlurPuEntry8

dlurPuDefPrimDlusName OBJECT-TYPE
      SYNTAX DisplayString (SIZE (0..17))
      MAX-ACCESS read-only
      STATUS current
      DESCRIPTION
          "The SNA name of the defined primary DLUS for this PU, if one
          has been defined.  If present, this name follows the
          SnaControlPointName textual convention.  A zero-length string
          indicates that no primary DLUS has been defined for this PU, in
          which case the global default represented by the
          dlurDefaultDefPrimDlusName object is used."

「1つがこのPUのための定義された第一のDLUS定義されたなら、SNAは命名する」dlurPuDefPrimDlusName OBJECT-TYPE SYNTAX DisplayString(SIZE(0 .17))のマックス-ACCESSの書き込み禁止のSTATUSの現在の記述。 存在しているなら、この名前はSnaControlPointNameの原文のコンベンションに続きます。 「ゼロ長ストリングは、どんな第一のDLUSもこのPUのために定義されていないのを示します、その場合、dlurDefaultDefPrimDlusName物によって表されたグローバルなデフォルトは使用されています。」

      ::= { dlurPuEntry 9 }

::= dlurPuEntry9

-- *****************************************
-- Defined backup DLUS table for a PU
-- *****************************************

-- ***************************************** -- 定義されて、PUのためにDLUSテーブルのバックアップをとってください--*****************************************

dlurPuDefBackupDlusTable OBJECT-TYPE
      SYNTAX SEQUENCE OF DlurPuDefBackupDlusEntry
      MAX-ACCESS not-accessible
      STATUS current
      DESCRIPTION
          "This table contains an ordered list of defined backup DLUSs
          for those PUs served by this DLUR that have their own defined
          backup DLUSs.  PUs that have no entries in this table use the
          global default backup DLUSs for the DLUR, represented by the
          dlurDefaultDefBackupDlusNameTable.  Entries in this table are
          ordered from most preferred backup DLUS to least preferred for
          each PU."

dlurPuDefBackupDlusTable OBJECT-TYPEのSYNTAX SEQUENCE OF DlurPuDefBackupDlusEntryのマックス-ACCESSのアクセスしやすくないSTATUS現在の記述、「このテーブルはそれら自身の定義されたバックアップDLUSsを持っているこのDLURによって役立たれたそれらのPUsのための定義されたバックアップDLUSsの規則正しいリストを含んでいます」。 このテーブルにエントリーを全く持っていないPUsはdlurDefaultDefBackupDlusNameTableによって表されたDLURにグローバルなデフォルトバックアップDLUSsを使用します。 「最少へのDLUSが各PUのために好んだ中で最も都合のよいバックアップからこのテーブルのエントリーを取り寄せます。」

      ::= { dlurPuInfo 2 }

::= dlurPuInfo2

dlurPuDefBackupDlusEntry OBJECT-TYPE
      SYNTAX DlurPuDefBackupDlusEntry
      MAX-ACCESS not-accessible
      STATUS current
      DESCRIPTION
          "This table is indexed by PU name and by an integer-valued
          index, which orders the entries from most preferred backup DLUS
          for the PU to least preferred."

dlurPuDefBackupDlusEntry OBJECT-TYPE SYNTAX DlurPuDefBackupDlusEntryのマックス-ACCESSのアクセスしやすくないSTATUS現在の記述、「このテーブルが索引をつけられることごとの」。

      INDEX { dlurPuDefBackupDlusPuName,

インデックス、dlurPuDefBackupDlusPuName

Clouston & Moore            Standards Track                    [Page 14]

RFC 2232         Managed Objects for DLUR using SMIv2      November 1997

SMIv2 November 1997を使用するDLURのためのCloustonとムーア標準化過程[14ページ]RFC2232管理オブジェクト

              dlurPuDefBackupDlusIndex }

dlurPuDefBackupDlusIndex

      ::= { dlurPuDefBackupDlusTable 1 }

::= dlurPuDefBackupDlusTable1

DlurPuDefBackupDlusEntry ::= SEQUENCE {
      dlurPuDefBackupDlusPuName          DisplayString,
      dlurPuDefBackupDlusIndex           Unsigned32,
      dlurPuDefBackupDlusName            SnaControlPointName
                     }

DlurPuDefBackupDlusEntry:、:= 系列dlurPuDefBackupDlusPuName DisplayString、dlurPuDefBackupDlusIndex Unsigned32、dlurPuDefBackupDlusName SnaControlPointName

dlurPuDefBackupDlusPuName OBJECT-TYPE
      SYNTAX DisplayString (SIZE (1..17))
      MAX-ACCESS not-accessible
      STATUS current
      DESCRIPTION
          "Locally administered name of the PU.  If this object has the
          same value as the dlurPuName object, then the two are
          identifying the same PU."

dlurPuDefBackupDlusPuName OBJECT-TYPE SYNTAX DisplayString(SIZE(1 .17))のマックス-ACCESSのアクセスしやすくないSTATUS現在の記述は「局所的に、PUという名前を管理しました」。 「この物にdlurPuName物と同じ値があるなら、2は同じPUを特定しています。」

      ::= { dlurPuDefBackupDlusEntry 1 }

::= dlurPuDefBackupDlusEntry1

dlurPuDefBackupDlusIndex OBJECT-TYPE
      SYNTAX Unsigned32 (1..4294967295)
      MAX-ACCESS not-accessible
      STATUS current
      DESCRIPTION
          "Secondary index for this table.  The index values start at 1,
          which identifies the most preferred backup DLUS for the PU."

「これのための二次索引はテーブルの上に置く」dlurPuDefBackupDlusIndex OBJECT-TYPE SYNTAX Unsigned32(1 .4294967295)のマックス-ACCESSのアクセスしやすくないSTATUS現在の記述。 「インデックス値は1のときに開始します」。(1はPUのために特定します中でバックアップDLUS最も都合のよい)。

      ::= { dlurPuDefBackupDlusEntry 2 }

::= dlurPuDefBackupDlusEntry2

dlurPuDefBackupDlusName OBJECT-TYPE
      SYNTAX SnaControlPointName
      MAX-ACCESS read-only
      STATUS current
      DESCRIPTION
          "Fully qualified name of a backup DLUS for this PU."

dlurPuDefBackupDlusName OBJECT-TYPE SYNTAX SnaControlPointNameのマックス-ACCESSの書き込み禁止のSTATUSの現在の記述、「このPUのためのバックアップDLUSの完全に修飾された名前。」

      ::= { dlurPuDefBackupDlusEntry 3 }

::= dlurPuDefBackupDlusEntry3

-- *********************************************************************
--               DLUS Control Sessions (CPSVRMGR Pipes)
--
--  This table contains information about DLUS control sessions, also
--  known as CPSVRMGR pipes.  Although DLUR uses a pair of CPSVRMGR
--  sessions for communication, for the purpose of status, information
--  about these two sessions is combined to yield a single status for the
--  requester/server connection.

-- ********************************************************************* -- DLUS Controlセッションズ(CPSVRMGRパイプス)----また、このテーブルはDLUSコントロールおよそセッション情報を含んでいます--CPSVRMGRが運ぶので、知っています。 DLURが結合されたaただ一つの状態をもたらすこれらの2つのセッションに関して1組のCPSVRMGR(コミュニケーション、状態、情報の目的のためのセッション)を使用する、--リクエスタ/サーバ接続。

Clouston & Moore            Standards Track                    [Page 15]

RFC 2232         Managed Objects for DLUR using SMIv2      November 1997

SMIv2 November 1997を使用するDLURのためのCloustonとムーア標準化過程[15ページ]RFC2232管理オブジェクト

-- *********************************************************************

-- *********************************************************************

dlurDlusInfo OBJECT IDENTIFIER ::= { dlurObjects 3 }

dlurDlusInfo物の識別子:、:= dlurObjects3

dlurDlusTable OBJECT-TYPE
      SYNTAX SEQUENCE OF DlurDlusEntry
      MAX-ACCESS not-accessible
      STATUS current
      DESCRIPTION
           "Information about DLUS control sessions."

dlurDlusTable OBJECT-TYPE SYNTAX SEQUENCE OF DlurDlusEntryのマックス-ACCESSのアクセスしやすくないSTATUS現在の記述、「DLUSコントロールおよそセッション情報。」

      ::= { dlurDlusInfo 1}

::= dlurDlusInfo1

dlurDlusEntry OBJECT-TYPE
      SYNTAX DlurDlusEntry
      MAX-ACCESS not-accessible
      STATUS current
      DESCRIPTION
           "This entry is indexed by the name of the DLUS."

dlurDlusEntry OBJECT-TYPE SYNTAX DlurDlusEntryのマックス-ACCESSのアクセスしやすくないSTATUS現在の記述、「DLUSという名前によってこのエントリーは索引をつけられます」。

      INDEX { dlurDlusName }

インデックスdlurDlusName

      ::= { dlurDlusTable 1 }

::= dlurDlusTable1

DlurDlusEntry ::= SEQUENCE {
      dlurDlusName          SnaControlPointName,
      dlurDlusSessnStatus   INTEGER
                     }

DlurDlusEntry:、:= 系列dlurDlusName SnaControlPointName、dlurDlusSessnStatus整数

dlurDlusName OBJECT-TYPE
      SYNTAX SnaControlPointName
      MAX-ACCESS not-accessible
      STATUS current
      DESCRIPTION
          "The SNA name of a DLUS with which this DLUR currently has a
          CPSVRMGR pipe established."

「SNAはこのDLURが現在CPSVRMGRパイプを設立させるDLUSについて命名する」dlurDlusName OBJECT-TYPE SYNTAX SnaControlPointNameのマックス-ACCESSのアクセスしやすくないSTATUS現在の記述。

      ::= { dlurDlusEntry 1 }

::= dlurDlusEntry1

dlurDlusSessnStatus OBJECT-TYPE
      SYNTAX INTEGER {
                      reset(1),
                      pendingActive(2),
                      active(3),
                      pendingInactive(4)
                     }
      MAX-ACCESS read-only
      STATUS current

dlurDlusSessnStatus OBJECT-TYPE SYNTAX INTEGERはマックス-ACCESS書き込み禁止STATUS現在で(1)、pendingActive(2)、アクティブな(3)、pendingInactive(4)をリセットしました。

Clouston & Moore            Standards Track                    [Page 16]

RFC 2232         Managed Objects for DLUR using SMIv2      November 1997

SMIv2 November 1997を使用するDLURのためのCloustonとムーア標準化過程[16ページ]RFC2232管理オブジェクト

      DESCRIPTION
          "Status of the CPSVRMGR pipe between the DLUR and this DLUS.
          This is a combination of the separate states for the
          contention-winner and contention-loser sessions:

「CPSVRMGRの状態はDLURとこのDLUSの間へ運ぶ」記述。 これは主張勝者と主張敗者セッションのための別々の州の組み合わせです:

          reset(1)           - none of the cases below
          pendingActive(2)   - either contention-winner session or
                               contention-loser session is pending active
          active(3)          - contention-winner and contention-loser
                               sessions are both active
          pendingInactive(4) - either contention-winner session or
                               contention-loser session is pending
                               inactive - this test is made AFTER the
                               'pendingActive' test.

リセット(1)--どちらかの主張勝者セッションか主張敗者セッションの主張勝者セッションか主張敗者セッションのどちらかが未定のアクティブなアクティブな(3)です--主張勝者と主張敗者セッションがともにアクティブなpendingInactive(4)であるというpendingActive(2)の下のケースのいずれも不活発までありません--このテストは'pendingActive'がテストする人工のAFTERです。

          The following matrix provides a different representation of
          how the values of this object are related to the individual
          states of the contention-winner and contention-loser sessions:

以下のマトリクスはこの物の値がどう主張勝者と主張敗者セッションの個々の州に関連するかに関する異なった表現を提供します:

               Conwinner
               | pA | pI | A | X = !(pA | pI | A)
          C ++++++++++++++++++++++++++++++++++
          o pA | 2  |  2 | 2 | 2
          n ++++++++++++++++++++++++++++++++++
          l pI | 2  |  4 | 4 | 4
          o ++++++++++++++++++++++++++++++++++
          s A  | 2  |  4 | 3 | 1
          e ++++++++++++++++++++++++++++++++++
          r X  | 2  |  4 | 1 | 1
            ++++++++++++++++++++++++++++++++++
          "

Conwinner| pA| パイ| A| X=!、(pA|pI|a)C+++++++++++ + + + + + + + + + + + + + + + + + + + + + + + o pA| 2 | 2 | 2 | 2++++++++++ + + + + + + + + + + + + + + + + + + + + + + n++l pI| 2 | 4 | 4 | 4○++++++++++++ + + + + + + + + + + + + + + + + + + + + + + s A| 2 | 4 | 3 | 1 e++++++++++++++++++++++++++++++++++r X| 2 | 4 | 1 | 1 ++++++++++++++++++++++++++++++++++ "

      ::= { dlurDlusEntry 2 }

::= dlurDlusEntry2

-- ***************************************************************
-- Conformance information
-- ***************************************************************

-- *************************************************************** -- 順応..情報

dlurConformance       OBJECT IDENTIFIER ::= { dlurMIB 2 }

dlurConformance物の識別子:、:= dlurMIB2

dlurCompliances       OBJECT IDENTIFIER ::= { dlurConformance 1 }
dlurGroups            OBJECT IDENTIFIER ::= { dlurConformance 2 }

dlurCompliances物の識別子:、:= dlurConformance1dlurGroups物の識別子:、:= dlurConformance2

-- Compliance statements

-- 承諾声明

dlurCompliance MODULE-COMPLIANCE
      STATUS current
      DESCRIPTION

dlurCompliance MODULE-COMPLIANCE STATUSの現在の記述

Clouston & Moore            Standards Track                    [Page 17]

RFC 2232         Managed Objects for DLUR using SMIv2      November 1997

SMIv2 November 1997を使用するDLURのためのCloustonとムーア標準化過程[17ページ]RFC2232管理オブジェクト

          "The compliance statement for the SNMPv2 entities which
          implement the DLUR MIB."

「DLUR MIBを実行するSNMPv2実体のための承諾声明。」

      MODULE -- this module

MODULE--このモジュール

--    Unconditionally mandatory groups
      MANDATORY-GROUPS  { dlurConfGroup }

-- 無条件に義務的なグループMANDATORY-GROUPSdlurConfGroup

      ::= { dlurCompliances 1 }

::= dlurCompliances1

-- Units of conformance
dlurConfGroup OBJECT-GROUP
      OBJECTS {
               dlurNodeCpName,
               dlurReleaseLevel,
               dlurAnsSupport,
               dlurMultiSubnetSupport,
               dlurNetworkNameForwardingSupport,
               dlurNondisDlusDlurSessDeactSup,
               dlurDefaultDefPrimDlusName,
               dlurDefaultDefBackupDlusName,
               dlurPuSscpSuppliedName,
               dlurPuStatus,
               dlurPuAnsSupport,
               dlurPuLocation,
               dlurPuLsName,
               dlurPuDlusSessnStatus,
               dlurPuActiveDlusName,
               dlurPuDefPrimDlusName,
               dlurPuDefBackupDlusName,
               dlurDlusSessnStatus
              }
      STATUS current
      DESCRIPTION
          "A collection of objects providing information on an
          implementation of APPN DLUR."

-- ユニットの順応dlurConfGroup OBJECT-GROUP OBJECTS、dlurNodeCpName、dlurReleaseLevel、dlurAnsSupport、dlurMultiSubnetSupport、dlurNetworkNameForwardingSupport、dlurNondisDlusDlurSessDeactSup、dlurDefaultDefPrimDlusName、dlurDefaultDefBackupDlusName、dlurPuSscpSuppliedName、dlurPuStatus、dlurPuAnsSupport、dlurPuLocation、dlurPuLsName、dlurPuDlusSessnStatus、dlurPuActiveDlusName、dlurPuDefPrimDlusName、dlurPuDefBackupDlusName、dlurDlusSessnStatus; STATUSの現在の記述、「APPN DLURの実現の情報を提供する物の収集。」

      ::= { dlurGroups 1 }

::= dlurGroups1

-- end of conformance statement

-- 順応声明の終わり

END

終わり

6.  Acknowledgments

6. 承認

   This MIB module is the product of the IETF SNA NAU MIB WG and the AIW
   APPN/HPR MIBs SIG.

このMIBモジュールはIETF SNA NAU MIB WGとAIW APPN/HPR MIBs SIGの製品です。

Clouston & Moore            Standards Track                    [Page 18]

RFC 2232         Managed Objects for DLUR using SMIv2      November 1997

SMIv2 November 1997を使用するDLURのためのCloustonとムーア標準化過程[18ページ]RFC2232管理オブジェクト

7.  References

7. 参照

   [1]  Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
        "Structure of Management Information for version 2 of
        the Simple Network Management Protocol (SNMPv2)", RFC 1902,
        January 1996.

[1]ケース、J.、McCloghrie、K.、ローズ、M.、およびS.Waldbusser、「Simple Network Managementプロトコル(SNMPv2)のバージョン2のためのManagement情報の構造」、RFC1902(1996年1月)。

   [2]  Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
        "Textual Conventions for Version 2 of the Simple
        Network Management Protocol (SNMPv2)", RFC 1903, January 1996.

[2]ケース、J.、McCloghrie、K.、ローズ、M.、およびS.Waldbusser、「簡単なネットワークマネージメントのバージョン2のための原文のコンベンションは(SNMPv2)について議定書の中で述べます」、RFC1903、1996年1月。

   [3]  Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
        "Conformance Statements for Version 2 of the Simple
        Network Management Protocol (SNMPv2)", RFC 1904, January 1996.

[3]ケース、J.、McCloghrie、K.、ローズ、M.、およびS.Waldbusser、「簡単なネットワークマネージメントのバージョン2のための順応声明は(SNMPv2)について議定書の中で述べます」、RFC1904、1996年1月。

   [4]  Clouston, B., and B. Moore, "Definition of Managed Objects for
        APPN", RFC 2155, June 1997.

1997年6月の[4] Clouston、B.とB.ムーア、「APPNのための管理オブジェクトの定義」RFC2155。

   [5]  IBM, Systems Network Architecture Advanced Peer-to-Peer
        Networking Dependent LU Requester Architecture Reference,
        Version 1.2, SV40-1010-01, December 1995.

[5] IBM、システム・ネットワーク・アーキテクチャは1995年12月に依存するLuリクエスタ構造参照、バージョン1.2、SV40-1010-01をネットワークでつなぐピアツーピアを進めました。

   [6]  IBM, SNA/MS Formats, GC31-8302-00.

[6]IBM、SNA/MS形式、GC31-8302-00。

8.  Security Considerations

8. セキュリティ問題

   In most cases, MIBs are not themselves security risks; if SNMP
   security is operating as intended, the use of a MIB to view
   information about a system, or to change some parameter at the
   system, is a tool, not a threat.

多くの場合、MIBsは自分たちでセキュリティリスクではありません。 SNMPセキュリティがそうであるなら、意図されるとしての作動(システムの情報を見るか、またはシステムの何らかのパラメタを変えるMIBの使用)はツールです、脅威でない。

   None of the read-only objects in the DLUR MIB reports a password,
   user data, or anything else that is particularly sensitive.  Some
   enterprises view their network configuration itself, as well as
   information about network usage and performance, as corporate assets;
   such enterprises may wish to restrict SNMP access to most of the
   objects in the MIB.

DLUR MIBの書き込み禁止物のいずれもパスワード、利用者データ、または特に機密の他の何も報告しません。 いくつかの企業がそれらのネットワーク・コンフィギュレーション自体とネットワーク用法の情報と企業資産としての性能を見ます。 そのような企業はMIBでSNMPアクセスを物の大部分に制限したがっているかもしれません。

   There are no read-write objects in the DLUR MIB.

読書して書いている物が全くDLUR MIBにありません。

Clouston & Moore            Standards Track                    [Page 19]

RFC 2232         Managed Objects for DLUR using SMIv2      November 1997

SMIv2 November 1997を使用するDLURのためのCloustonとムーア標準化過程[19ページ]RFC2232管理オブジェクト

9.  Authors' Addresses

9. 作者のアドレス

   Bob Clouston
   Cisco Systems
   7025 Kit Creek Road
   P.O. Box 14987
   Research Triangle Park, NC 27709, USA

7025年のボブCloustonシスコシステムズキットクリーク道路私書箱14987リサーチトライアングル公園、NC 27709、米国

   Phone: +1 919 472 2333
   EMail: clouston@cisco.com

以下に電話をしてください。 +1 2333年の919 472メール: clouston@cisco.com

   Bob Moore
   IBM Corporation
   800 Park Offices Drive
   CNMA/664
   P.O. Box 12195
   Research Triangle Park, NC 27709, USA

ボブムーアIBM社800の公園オフィスはCNMA/664私書箱12195リサーチトライアングル公園、NC 27709、米国を運転します。

   Phone: +1 919 254 4436
   EMail: remoore@ralvm6.vnet.ibm.com

以下に電話をしてください。 +1 4436年の919 254メール: remoore@ralvm6.vnet.ibm.com

Clouston & Moore            Standards Track                    [Page 20]

RFC 2232         Managed Objects for DLUR using SMIv2      November 1997

SMIv2 November 1997を使用するDLURのためのCloustonとムーア標準化過程[20ページ]RFC2232管理オブジェクト

10.  Full Copyright Statement

10. 完全な著作権宣言文

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

Copyright(C)インターネット協会(1997)。 All rights reserved。

   This document and translations of it may be copied and furnished to
   others, and derivative works that comment on or otherwise explain it
   or assist in its implementation may be prepared, copied, published
   and distributed, in whole or in part, without restriction of any
   kind, provided that the above copyright notice and this paragraph are
   included on all such copies and derivative works.  However, this
   document itself may not be modified in any way, such as by removing
   the copyright notice or references to the Internet Society or other
   Internet organizations, except as needed for the purpose of
   developing Internet standards in which case the procedures for
   copyrights defined in the Internet Standards process must be
   followed, or as required to translate it into languages other than
   English.

それに関するこのドキュメントと翻訳は、コピーして、それが批評するか、またはそうでなければわかる他のもの、および派生している作品に提供するか、または準備されているかもしれなくて、コピーされて、発行されて、全体か一部広げられた実現を助けるかもしれません、どんな種類の制限なしでも、上の版権情報とこのパラグラフがそのようなすべてのコピーと派生している作品の上に含まれていれば。 しかしながら、このドキュメント自体は何らかの方法で変更されないかもしれません、インターネット協会か他のインターネット組織の版権情報か参照を取り除くのなどように、それを英語以外の言語に翻訳するのが著作権のための手順がインターネットStandardsの過程で定義したどのケースに従わなければならないか、必要に応じてさもなければ、インターネット標準を開発する目的に必要であるのを除いて。

   The limited permissions granted above are perpetual and will not be
   revoked by the Internet Society or its successors or assigns.

上に承諾された限られた許容は、永久であり、インターネット協会、後継者または案配によって取り消されないでしょう。

   This document and the information contained herein is provided on an
   "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
   TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
   BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
   HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
   MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

このドキュメントとそして、「そのままで」という基礎とインターネットの振興発展を目的とする組織に、インターネット・エンジニアリング・タスク・フォースが速達の、または、暗示しているすべての保証を放棄するかどうかというここにことであり、他を含んでいて、含まれて、情報の使用がここに侵害しないどんな保証も少しもまっすぐになるという情報か市場性か特定目的への適合性のどんな黙示的な保証。

Clouston & Moore            Standards Track                    [Page 21]

Cloustonとムーア標準化過程[21ページ]