tn3270e-mib

很不错java的SNMP应用例子

TN3270E-MIB DEFINITIONS ::= BEGIN

IMPORTS
    MODULE-IDENTITY, OBJECT-TYPE, Unsigned32, TimeTicks,
    IpAddress, Counter32, Gauge32, Counter64
        FROM SNMPv2-SMI
    TEXTUAL-CONVENTION, RowStatus, TestAndIncr, DateAndTime,
    TimeStamp
        FROM SNMPv2-TC
    MODULE-COMPLIANCE, OBJECT-GROUP
        FROM SNMPv2-CONF
    snanauMIB
        FROM SNA-NAU-MIB
    Utf8String
        FROM SYSAPPL-MIB
    SnmpAdminString
        FROM SNMP-FRAMEWORK-MIB
    IANATn3270eAddrType, IANATn3270eAddress,
    IANATn3270eClientType, IANATn3270Functions,
    IANATn3270ResourceType, IANATn3270DeviceType,
    IANATn3270eLogData
        FROM IANATn3270eTC-MIB;

  tn3270eMIB MODULE-IDENTITY
      LAST-UPDATED "9807270000Z" -- July 27, 1998
      ORGANIZATION "TN3270E Working Group"
      CONTACT-INFO
          "Kenneth White ([e-mail])
           IBM Corp. - Dept. BRQA/Bldg. 501/G114
           P.O. Box 12195
           3039 Cornwallis
           RTP, NC 27709-2195
           USA

           Robert Moore ([e-mail])
           IBM Corp. - Dept. BRQA/Bldg. 501/G114
           P.O. Box 12195
           3039 Cornwallis
           RTP, NC 27709-2195
           USA
           [phone]"
      DESCRIPTION
          "This module defines a portion of the management
          information base (MIB) for managing TN3270E servers."
      REVISION  "9807270000Z" -- July 27, 1998
      DESCRIPTION
          "RFC nnnn (Proposed Standard)" -- RFC Editor to fill in
      ::= { snanauMIB 8 }

-- Textual Conventions

SnaResourceName ::= TEXTUAL-CONVENTION
    STATUS      current
    DESCRIPTION
        "The textual convention for defining an SNA resource
         name. A fully qualified SNA resource name, consisting
         of a 1 to 8 character network identifier (NetId), a
         period ('.'), and a 1 to 8 character resource name
         (ResName).

         The NetId and ResName are constructed from the
         uppercase letters 'A' - 'Z' and the numerics '0' - '9',
         all encoded in ASCII, with the restriction that the
         first character of each must be a letter.  Blanks are
         not allowed.

         Earlier versions of SNA permitted three additional
         characters in NetIds and ResNames:  '#', '@', and '$'.
         While this use of these characters has been retired,
         a Management Station should still accept them for
         backward compatibility.

         Note: This Textual Convention is not subject to
         internationalization, and does not use the character
         encodings used by the Utf8String Textual Convention."
    SYNTAX     OCTET STRING (SIZE(0..17))

Tn3270eTraceData ::= TEXTUAL-CONVENTION
    STATUS      current
    DESCRIPTION
        "An octet string representing trace data from the
        Telnet half of a TN3270E session, from the SNA half,
        or from both.  The octet string contains a sequence
        of trace elements, with the trace elements in the
        string ordered from earliest to latest.

        Each trace element has the following form:

                +---+---+----+----------------------+
                !length !type!data                  !
                +---+---+----+----------------------+
          where:

          length = two-octet length of the data portion of the
                   trace element, not including the length and
                   type octets

          type   = one-octet code point characterizing the data;
                   defined values are:

                   X'01' telnet PDU from the server to the client
                   X'02' telnet PDU from the client to the server
                   X'03' SNA data from the server to the SNA host
                   X'04' SNA data from the SNA host to the server

          data   = initial part of a PDU.

        It is implementation-dependent where the 'initial part of
        a PDU' starts.  For SNA data, however, the starting point
        SHOULD be the first byte of the TH.  For IP data the
        starting point SHOULD be the first byte of the IP header.

        It is left to implementations to determine how much of
        each PDU to return in a trace element.

        The zero-length string indicates that no trace
        data is available."
    SYNTAX OCTET STRING (SIZE (0 | 3..4096))

-- Top-level structure of the MIB

tn3270eNotifications  OBJECT IDENTIFIER ::= { tn3270eMIB 0 }
tn3270eObjects        OBJECT IDENTIFIER ::= { tn3270eMIB 1 }
tn3270eConformance    OBJECT IDENTIFIER ::= { tn3270eMIB 3 }

-- MIB Objects

tn3270eSrvrConfTable OBJECT-TYPE
    SYNTAX      SEQUENCE OF Tn3270eSrvrConfEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "This table defines the configuration elements for
        TN3270E servers.  The number of entries in this table
        is expected to vary depending on the location of the
        table.  A particular TN3270E server is expected to
        have a single entry.  Modeling of the configuration
        elements as a table allows multiple TN3270E
        servers to be serviced by the same SNMP agent.
        An implementation SHOULD NOT retain an SNMP-created
        entry in this table across re-IPLs (Initial Program
        Loads) of the corresponding TN3270E server."

    ::= { tn3270eObjects 1 }

tn3270eSrvrConfEntry OBJECT-TYPE
    SYNTAX      Tn3270eSrvrConfEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "Definition of the configuration elements for a single
        TN3270E server."
    INDEX       { tn3270eSrvrConfIndex }
    ::= { tn3270eSrvrConfTable 1 }

Tn3270eSrvrConfEntry ::= SEQUENCE {
    tn3270eSrvrConfIndex             Unsigned32,
    tn3270eSrvrConfInactivityTimeout Unsigned32,
    tn3270eSrvrConfConnectivityChk   INTEGER,
    tn3270eSrvrConfTmNopInactTime    Unsigned32,
    tn3270eSrvrConfTmNopInterval     Unsigned32,
    tn3270eSrvrFunctionsSupported    IANATn3270Functions,
    tn3270eSrvrConfAdminStatus       INTEGER,
    tn3270eSrvrConfOperStatus        INTEGER,
    tn3270eSrvrConfSessionTermState  INTEGER,
    tn3270eSrvrConfSrvrType          INTEGER,
    tn3270eSrvrConfContact           SnmpAdminString,
    tn3270eSrvrConfRowStatus         RowStatus,
    tn3270eSrvrConfLastActTime       DateAndTime,
    tn3270eSrvrConfTmTimeout         Unsigned32
  }

tn3270eSrvrConfIndex  OBJECT-TYPE
    SYNTAX      Unsigned32 (1..4294967295)
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
       "Identifier for a single TN3270E server.

       tn3270eSrvrConfIndex values need not be
       contiguous."
    ::= { tn3270eSrvrConfEntry 1 }

tn3270eSrvrConfInactivityTimeout OBJECT-TYPE
    SYNTAX      Unsigned32 (0..99999999)
    UNITS "seconds"
    MAX-ACCESS  read-create
    STATUS      current
    DESCRIPTION
       "The inactivity time-out specified in seconds.  When a
        connection has been inactive for the number of seconds
        specified by this object it is closed.  Only user traffic
        is considered when determining whether there has been
        activity on a connection.

        The default value 0 means that no inactivity time-out is
        in effect."
    DEFVAL { 0 }
    ::= { tn3270eSrvrConfEntry 2 }

tn3270eSrvrConfConnectivityChk OBJECT-TYPE
    SYNTAX      INTEGER {
                          timingMark(1),
                          nop(2),
                          noCheck(3)
                        }
    MAX-ACCESS  read-create
    STATUS      current
    DESCRIPTION
       "This object enables TIMING-MARK processing, NOP
        processing, or neither for a TN3270E server."
    DEFVAL { noCheck }
    ::= { tn3270eSrvrConfEntry 3 }

tn3270eSrvrConfTmNopInactTime OBJECT-TYPE
    SYNTAX      Unsigned32 (1..86400) -- 1 second to 24 hours
    UNITS "seconds"
    MAX-ACCESS  read-create
    STATUS      current
    DESCRIPTION
       "The amount of time a connection must have had no
       traffic on it in order for a TIMING-MARK or NOP request
       to be sent on the connection.  This value applies only
       when connections are being examined for recent activity
       on a scan interval controlled by the value of the
       tn3270eSrvrConfTmNopInterval object."
    DEFVAL { 600 }   -- 10 minutes
    ::= { tn3270eSrvrConfEntry 4 }

tn3270eSrvrConfTmNopInterval OBJECT-TYPE
    SYNTAX      Unsigned32 (1..86400) -- 1 second to 24 hours
    UNITS "seconds"
    MAX-ACCESS  read-create
    STATUS      current
    DESCRIPTION
       "The scan interval to be used by a TN3270E server when
       it examines its Telnet connections for recent activity.
       The server scans its Telnet connections on the interval
       provided by this object, looking for ones that have been
       idle for more than the value provided by the
       tn3270eSrvrConfTmNopInactTime object.  A TIMING-MARK or
       NOP request is sent for each connection that has
       exhibited no activity for this period of time."
    DEFVAL { 120 }   -- 2 minutes
    ::= { tn3270eSrvrConfEntry 5 }

tn3270eSrvrFunctionsSupported OBJECT-TYPE
    SYNTAX    IANATn3270Functions
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
       "This object indicates the functions supported by a
        TN3270E server."
    DEFVAL { { scsCtlCodes, dataStreamCtl,
               responses, bindImage, sysreq } }
    ::= { tn3270eSrvrConfEntry 6 }

tn3270eSrvrConfAdminStatus OBJECT-TYPE
    SYNTAX  INTEGER {
                      up(1),
                      down(2),
                      stopImmediate(3)
                    }
    MAX-ACCESS  read-create
    STATUS      current
    DESCRIPTION
        "The desired state of the TN3270E server represented
         by this entry in the table:

         up(1)            - Activate this TN3270E server.
         down(2)          - Informs the associated TN3270E
                            server to gracefully terminate
                            its processing.
         stopImmediate(3) - Informs the associated TN3270E
                            server to terminate itself
                            immediately.

         When a managed system creates an entry in this table,
         tn3270eSrvrConfAdminStatus and tn3270eSrvrConfOperStatus
         are initialized as up(1) by default.

         The exact behavior of a server in response to a down(2)
         or stopImmediate(3) command is left implementation-
         dependent.  A TN3270E server that is capable of it
         SHOULD close all of its TN3270 and TN3270E sessions
         during a graceful termination.

         Often the function enabled via stopImmediate(3) is used
         as a last resort by a system administrator, to attempt
         to either bring down a hung TN3270E server or free up
         its resources immediately to aid in general system
         availability, or to shut down a TN3270E server that is
         not recognizing a down(2) request.

         A TN3270E server that does not distinguish between
         down(2) or stopImmediate(3) transitions should not
         support stopImmediate(3)."
    DEFVAL { up }
    ::= { tn3270eSrvrConfEntry 7 }

tn3270eSrvrConfOperStatus OBJECT-TYPE
    SYNTAX  INTEGER {
                     up(1),
                     down(2),
                     busy(3),
                     shuttingDown(4)
                    }
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
       "The current operational state of a TN3270E server.
       The following values are defined:

        up(1)            - the server is active and accepting
                           new client connections
        down(2)          - the server is not active
        busy(3)          - the server is active, but is not
                           accepting new client connections
                           because it lacks the resources to
                           do so
        shuttingDown(4)  - the server is active, but is not
                           accepting new client connections
                           because it is in the process of
                           performing a graceful shutdown."
    DEFVAL { up }
    ::= { tn3270eSrvrConfEntry 8 }

tn3270eSrvrConfSessionTermState OBJECT-TYPE
    SYNTAX  INTEGER {
                      terminate(1),
                      luSessionPend(2),
                      queueSession(3)
                    }
    MAX-ACCESS  read-create
    STATUS      current
    DESCRIPTION
       "This object determines what a TN3270E server
        should do when a TN3270 Session terminates:
       terminate(1)     => Terminate the TCP connection.
       luSessionPend(2) => Do not drop the TCP connection
                           associated with a client when its
                           TN3270 session ends.  Processing
                           should redrive session initialization
                           as if the client were first connecting.
       queueSession(3)  => This value relates to the Close
                           Destination PASS (CLSDST PASS) operation
                           in VTAM.  An example provides the
                           easiest explanation.  Suppose a TN3270E
                           client is in session with APPL1, and
                           APPL1 does a CLSDST PASS of the client's
                           session to APPL2.  queueSession(3)
                           specifies that the TN3270E server must
                           keep the TCP connection with the client
                           active after it receives the UNBIND from
                           APPL1, waiting for the BIND from APPL2."