rfc2051.txt

RFC 的详细文档！

   maximum session limit.

   For those implementations that have Mode definitions associated with
   each local and partner LU pair, multiple entries with the same
   appcModeAdminModeName could exist with different
   appcModeAdminLocLuName and appcModeAdminParLuName.  For those
   implementations in which Mode definitions apply to all local and/or
   all partner LUs, the appcModeAdminLocLuName and/or
   appcModeAdminParLuName are set to '*ALL'.

   6) appcModeOperTable

   This table contains objects which describe Mode run-time operational
   information for each local/partner LU pair.  The type of information
   includes the mode name and maximum session limit.

   Although the Admin table entries could be global to all local and
   partner LUs in a Node, the Oper table entries are always associated
   with one local and partner LU pair.

   A row in this table is created as soon as there is an active session
   between local and partner LU for this Mode. Two entries are present
   when both LUs in a pair are local.



Allen, et. al.              Standards Track                     [Page 7]

RFC 2051              SNANAU APPC MIB using SMIv2           October 1996


3.1.3.  appcTp group

   The appcTp group consists of the following table:

   1) appcTpAdminTable

   This table contains objects which describe transaction program (TP)
   configuration information. The type of information includes the TP
   name and TP operation, indicating how the TP will be started.

   For those implementations that have TP definitions associated with
   each local LU, multiple entries with the same appcTpAdminTpName could
   exist with different appcTpAdminLocLuName.  For those implementations
   in which TP definition applies to all local LUs, it will have
   appcTpAdminLocLuName set to '*ALL'.

   There is no appcTpOperTable. Run-time information about TP tends to
   be product-specific (e.g., process Id), and much of the information
   can be derived from the conversation tables.

3.1.4.  appcSession group

   The appcSession group consists of the following tables:

   1) appcActSessTable

   This table contains objects which describe LU6.2 session information.
   The type of information includes the PCID and the pacing counts.

   2) appcSessStatsTable

   This table contains statistical information about LU 6.2 sessions.
   The type of information includes counters of bytes and RUs sent and
   received.

   3) appcHistSessTable

   This table contains historical information about APPC sessions that
   have terminated abnormally.  The type of information includes the
   unbind type and sense data.

   4) appcSessRtpTable

   This table contains information about LU 6.2 sesions that are being
   transported by High Performance Routing.  The type of information
   includes the NCEID and TCID.





Allen, et. al.              Standards Track                     [Page 8]

RFC 2051              SNANAU APPC MIB using SMIv2           October 1996


3.1.5.  appcConversation group

   The appcConversation group consists of the following tables:

   1) appcActiveConvTable

   This table contains objects which describe active conversation
   information. The type of information includes the state and type.  An
   entry is created by an Agent when the conversation is started, and is
   removed when the conversation ends.

   2) appcHistConvTable

   This table contains objects which describe historical conversation
   information about abnormally terminated conversations.  The number of
   entries and how long they are kept depends on the Agent
   implementation.  The type of information inclues the sense data and
   log data.

3.1.6.  appcCPIC group

   The appcCPIC group consists of the following tables:

   1) appcCpicAdminTable

   This table contains objects which describe CPI-C side information.
   The type of information includes the symbolic destination name and
   partner LU name.

   For those implementations that have CPI-C definition associated with
   each local LU, multiple entries with the same
   appcCpicAdminSymbDestName could exist with different
   appcCpicAdminLocLuName.  For those implementations in which CPI-C
   definition applies to all local LUs, it will have
   appcCpicAdminLocLuName set to '*ALL'.

   2) appcCpicOperTable

   This table contains objects which describe CPI-C run-time operational
   information.  The type of information includes the symbolic
   destination name and partner LU name.










Allen, et. al.              Standards Track                     [Page 9]

RFC 2051              SNANAU APPC MIB using SMIv2           October 1996


4.  Definitions

APPC-MIB DEFINITIONS        ::= BEGIN

IMPORTS
      DisplayString, InstancePointer, TEXTUAL-CONVENTION, DateAndTime
                FROM SNMPv2-TC

      mib-2, Counter32, Gauge32, Integer32, TimeTicks,
      OBJECT-TYPE, MODULE-IDENTITY
                FROM SNMPv2-SMI

      snanauMIB
                FROM SNA-NAU-MIB

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

appcMIB MODULE-IDENTITY
      LAST-UPDATED  "9512150000Z"
      ORGANIZATION  "IETF SNA NAU MIB Working Group"
      CONTACT-INFO

                "
                        Michael Allen
                        Wall Data Inc.
                        P.O.Box 1120
                        Duval, WA 98019, USA
                        Tel:    [phone]
                        E-mail: [e-mail]

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

                        Zbigniew Kielczewski
                        Cisco Systems
                        3100 Smoketree Court
                        Raleigh, NC 27604, USA
                        Tel:    [phone]
                        E-mail: [e-mail]






Allen, et. al.              Standards Track                    [Page 10]

RFC 2051              SNANAU APPC MIB using SMIv2           October 1996


                        William Kwan
                        Jupiter Technology Inc.
                        200 Prospect Street
                        Waltham, MA 02254, USA
                        Tel:    [phone], x423
                        E-mail: [e-mail]

                        Bob Moore
                        IBM Corporation
                        800 Park Offices Drive
                        CNMA/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 APPC capabilities."

::= { snanauMIB 3 }

appcObjects          OBJECT IDENTIFIER ::= { appcMIB 1 }
  appcGlobal         OBJECT IDENTIFIER ::= { appcObjects 1 }
  appcLu             OBJECT IDENTIFIER ::= { appcObjects 2 }
  appcTp             OBJECT IDENTIFIER ::= { appcObjects 3 }
  appcSession        OBJECT IDENTIFIER ::= { appcObjects 4 }
  appcConversation   OBJECT IDENTIFIER ::= { appcObjects 5 }
  appcCPIC           OBJECT IDENTIFIER ::= { appcObjects 6 }


-- *********************************************************************
-- Objects in this MIB are used to model an SNA device that supports
-- APPC LUs.
-- Following is the overall organization of the MIB.
--
-- 1.   APPC Global Objects            - global values, defaults,
--                                       controls (including CNOS)
-- 2.   APPC Defined Lu Tables         - Admin and Oper
-- 3.   APPC Defined LU Pair Tables    - Admin and Oper
-- 4.   APPC Mode Tables               - Admin and Oper
-- 5.   APPC TP Tables                 - Admin only
-- 6.   APPC Session Tables            - Active, Stats, History, RTP
-- 7.   APPC Conversation Table        - Active, History
-- 8.   APPC CPIC side info            - Admin and Oper
-- *********************************************************************

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



Allen, et. al.              Standards Track                    [Page 11]

RFC 2051              SNANAU APPC MIB using SMIv2           October 1996


-- Textual Convention

-- ---------------------------------------------------------------------
SnaSenseData ::= TEXTUAL-CONVENTION
      STATUS current
      DESCRIPTION
          "To facilitate their display by a Management Station, sense
          data objects in the MIB are represented as DisplayStrings of
          size 8.  Eight '0' characters indicates that no sense data
          identifying an SNA error condition is available."

      SYNTAX DisplayString (SIZE (8))
-- *********************************************************************
-- APPC Control Objects
-- ---------------------------------------------------------------------
-- The following objects allow:
--    * the collection of APPC Session information counters
--      to be started and stopped
--    * the collection of APPC Session RSCVs
--      to be started and stopped
--    * the collection of APPC tracing information to be started and
--      stopped
--
-- These objects are for implementations that wish to provide
-- this level of operational control.  This group is
-- conditionally mandatory in the conformance section of the MIB.
--
-- *********************************************************************

-- *********************************************************************
-- Control Admin
--      These objects contain the desired states for the controls.
--      The actual states are in the Oper objects.
-- *********************************************************************
appcCntrlAdminGroup OBJECT IDENTIFIER ::= { appcGlobal 1 }

appcCntrlAdminStat OBJECT-TYPE
      SYNTAX INTEGER {
                      notActive(1),
                      active(2)
                     }
      MAX-ACCESS read-write
      STATUS current
      DESCRIPTION
          "Indicates the desired state of statistics collection:

              notActive  collection of counters is not active.
              active     collection of counters is active.



Allen, et. al.              Standards Track                    [Page 12]

RFC 2051              SNANAU APPC MIB using SMIv2           October 1996


           When this object is set to notActive, all of the entries are
           removed from the appcSessStatsTable."

      ::= { appcCntrlAdminGroup  1 }

appcCntrlAdminRscv OBJECT-TYPE
      SYNTAX INTEGER {
                      notActive(1),
                      active(2)
                     }
      MAX-ACCESS read-write
      STATUS current
      DESCRIPTION
          "Indicates the desired state of RSCV information collection:
              notActive  collection of route selection control vectors
                         is not active.
              active     collection of route selection control vectors
                         is active."

      ::= { appcCntrlAdminGroup  2 }

appcCntrlAdminTrace OBJECT-TYPE
      SYNTAX INTEGER {
                      notActive(1),
                      active(2)
                     }
      MAX-ACCESS read-write
      STATUS current
      DESCRIPTION
          "Indicates the desired state of tracing:

              notActive  collection of tracing information is not active
              active     collection of tracing information is active"

      ::= { appcCntrlAdminGroup  3 }

appcCntrlAdminTraceParm OBJECT-TYPE
      SYNTAX DisplayString (SIZE (0..128))
      MAX-ACCESS read-write
      STATUS current
      DESCRIPTION
          "Specifies the parameter to be used in conjunction with
          activating tracing.  The actual content is implementation
          dependent."

      ::= { appcCntrlAdminGroup  4 }

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



Allen, et. al.              Standards Track                    [Page 13]

RFC 2051              SNANAU APPC MIB using SMIv2           October 1996