TN3270E Working Group
INTERNET DRAFT: <draft-ietf-tn3270e-tn3270-mib-04.txt>                                      Kenneth White
INTERNET DRAFT: <draft-ietf-tn3270e-tn3270-mib-05.txt>         IBM Corp.
Expiration Date: May, July, 1998                                 Robert Moore
                                                               IBM Corp.

                                                           November 1997
January 1998

                Base Definitions of Managed Objects for
                          TN3270E Using SMIv2

                 <draft-ietf-tn3270e-tn3270-mib-04.txt>
                <draft-ietf-tn3270e-tn3270-mib-05.txt>

Status of this Memo

This document is an Internet Draft.  Internet Drafts are working
documents of the Internet Engineering Task Force (IETF), its Areas, and
its Working Groups.  Note that other groups may also distribute working
documents as Internet Drafts.

Internet Drafts are draft documents valid for a maximum of six months.
Internet Drafts may be updated, replaced, or obsoleted by other
documents at any time.  It is not appropriate to use Internet Drafts as
reference material or to cite them other than as a "working draft" or
"work in progress."

Please check the I-D abstract listing contained in each Internet Draft
directory to learn the current status of this or any Internet Draft.
Distribution of this document is unlimited.

Abstract

Copyright Notice

Copyright (C) The purpose of this Internet Society (1998).  All Rights Reserved.

Abstract

This memo is to define defines a Management Information Base (MIB) for configuring
and managing TN3270E Servers. servers.  TN3270E, defined by RFC 1647 (reference
[14]), refers to the enhancements made to the Telnet 3270 (TN3270)
terminal emulation practices.  Refer to: RFC 1041, reference [4]; RFC
854, reference [2]; and RFC 860, reference [3] for a sample of what is
meant by TN3270 practices.

The MIB defined by this memo is intended to provide provides generic support for both Host host and Gateway
gateway TN3270E server implementations.  A host TN3270E server refers to
an implementation where the TN3270E server is collocated with the
Systems Network Architecture (SNA) System Services Control Point (SSCP)
for the dependent Secondary Logical Units (SLUs) that the server makes
available to its clients for connecting into a SNA network.

A gateway TN3270E server resides on an SNA node other than an SSCP,
either an SNA type 2.0 node or an APPN node acting in the role of a

Dependent LU Requester (DLUR).  Host and gateway TN3270E server
implementations typically differ greatly as to their internal
implementation and system definition (SYSDEF) requirements.

It is the intent that the MIB defined herein be extended by subsequent memos
memos, to provide non-generic configuration support and to enable
TN3270E Response Time Collection.

  It is the intent of this MIB to fully adhere to all prerequisite MIBs
  unless explicitly stated. Deviations will be documented in
  corresponding conformance statements. response time collection.  The specification of this MIB
  will utilize uses
the Structure of Management Information (SMI) for Version 2 of the
Simple Network Management Protocol Version (refer to
  RFC1902, RFC 1902, reference
[1]).

Table of Contents

Expires May 1998                                                [Page 1]~

White      TN3270E Management Information Base (TN3270E-MIB)    20 November 1997

1.0 Introduction.............................................  Introduction  . . . . . . . . . . . . . . . . . . . . . . . . .   2

2.0  The SNMPv2 Network Management Framework.................. 2
  2.1 Object Definitions....................................... Framework   . . . . . . . . . . .   3

3.0  Structure of the MIB..................................... MIB  . . . . . . . . . . . . . . . . . . . . .   3
3.1  TN3270E Server Control................................... Control  . . . . . . . . . . . . . . . . . . . .   4
  3.1.1 tn3270eSrvrConfTable................................... 4  tn3270eSrvrConfTable  . . . . . . . . . . . . . . . . . . .   5
  3.1.2 tn3270eSrvrPortTable...................................  tn3270eSrvrPortTable  . . . . . . . . . . . . . . . . . . .   5
  3.1.3 tn3270eSrvrStatsTable.................................. 5  tn3270eSrvrStatsTable   . . . . . . . . . . . . . . . . . .   6
3.2  TN3270E Server Resource Configuration.................... Configuration   . . . . . . . . . . . .   6
3.3 Resource/Client  Resource Name / Client Address Mappings......................... Mappings   . . . . . . . . . . .   6
  3.3.1 tn3270eSnaMapTable.....................................  tn3270eSnaMapTable  . . . . . . . . . . . . . . . . . . . .   6
  3.3.2 tn3270eResMapTable..................................... 6  tn3270eResMapTable  . . . . . . . . . . . . . . . . . . . .   7
  3.3.3 TCP Connection Table Additions.........................  tn3270eTcpConnTable   . . . . . . . . . . . . . . . . . . .   7
3.4  Advisory Spin Lock Usage  . . . . . . . . . . . . . . . . . . .   8
3.5  IANA Considerations   . . . . . . . . . . . . . . . . . . . . .   8

4.0 Definitions.............................................. 7  Definitions   . . . . . . . . . . . . . . . . . . . . . . . . .   8

5.0  Security Considerations..................................40 Considerations   . . . . . . . . . . . . . . . . . . .  41

6.0 Acknowledgments..........................................40  Intellectual Property   . . . . . . . . . . . . . . . . . . . .  42

7.0 References...............................................41  Acknowledgments   . . . . . . . . . . . . . . . . . . . . . . .  42

8.0  References  . . . . . . . . . . . . . . . . . . . . . . . . . .  42

9.0  Authors' Address.........................................42

1. Addresses  . . . . . . . . . . . . . . . . . . . . . .  43

10.0  Full Copyright Statement   . . . . . . . . . . . . . . . . . .  44

1.0  Introduction

This document is a product of the TN3270E Working Group.  Its purpose is
to define a MIB module for extending the traditional MIBs supported support by a TCP/IP implementation for
configuration and management of TN3270E servers.

2.

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED",  "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119, reference [13].

2.0  The SNMPv2 Network Management Framework

The SNMP SNMPv2 Network Management Framework presently consists of three seven major
components.  They are:

o the SMI, described in   RFC 1902 [1], - [1] which defines the SMI, the mechanisms used for
    describing and naming objects for the purpose of management.

o the MIB-II, STD 17,   RFC 1213 [5], - the core set of managed
    objects 1903 [6] defines textual conventions for the Internet suite of protocols. SNMPv2.

o the protocol,   RFC 1157 [9] and/or 1904 [8] defines conformance statements for SNMPv2.

o   RFC 1905 [7] - the protocol defines  transport mappings for SNMPv2.

o   RFC 1906 [5] defines the protocol operations used for accessing network access
    to managed information.

  Textual conventions are defined in objects.

o   RFC 1903 [6], and conformance
  statements are defined in 1907 [9] defines the Management Information Base for SNMPv2.

o   RFC 1904 [8]. 1908 [16] specifies coexistence between SNMP and SNMPv2.

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

Expires May 1998                                                [Page 2]~

White      TN3270E Management Information Base (TN3270E-MIB)    20 November 1997

This memo specifies a MIB module that is compliant to the SNMPv2 SMI.  A
semantically identical MIB conforming to the SNMPv1 SMI can be produced
through the appropriate translation.

2.1.  Object Definitions

  Managed objects are accessed via a virtual information store, termed
  the Management Information Base or MIB.  Objects in the MIB are
  defined using the subset of Abstract Syntax Notation One (ASN.1)
  defined in the SMI.  In particular, each object object type is named
  by an OBJECT IDENTIFIER, an administratively assigned name.  The
  object type together with an object instance serves to uniquely
  identify a specific instantiation of the object.  For human
  convenience, we often use a textual string, termed the descriptor, to
  refer to the object type.

3.

3.0  Structure of the MIB

The TN3270E-MIB is split into the following components:

o   TN3270E Server Control
o   TN3270E Server Resource Configuration
o   Resource/Client Address Mappings

There are two additional sections to address:

o   Advisory Spin Lock Usage
o   IANA Considerations

The TN3270E-MIB is defined primarily for TN3270E servers.  This memo
does not explicitly address use of the MIB by TN3270 servers that do not
support the TN3270E protocol.  Although  Even though a significant number of the
objects in the MIB do apply in the TN3270-only case, the case was not
  addressed
addressed, since it is unlikely that a TN3270-only server would
implement this MIB.

The SYSAPPL-MIB, reference [12], is a prerequisite for the TN3270E-
  MIB, so that contains the Utf8String Textual Convention textual
convention (TC) can be imported. that the TN3270E-MIB imports.  This TC, which is used
for some MIB objects containing textual information, enables
internationalization of text strings, whereas the DisplayString TC does
not.

It is important to note that implementation of the SYSAPPL-MIB is not
actually a prerequisite for implementing the TN3270E-MIB.  On the other
hand, implementation of the TN3270E-MIB does not preclude implementing
the SYSAPPL-MIB as well.  When both MIBs are implemented, the primary
index into most of the TN3270E-MIB tables, tn3270eSrvrConfIndex, SHOULD
equal one of the SYSAPPL-MIB's sysApplElmtRunIndex values.  In this case
the entry in the sysApplElmtRunTable provides additional information on
a TN3270E server.

The SNMP-FRAMEWORK-MIB, reference [15], contains the SnmpAdminString TC
that the TN3270E-MIB imports.  Like the Utf8String TC, this TC also
enables internationalization of text strings; in addition, it provides
some guidelines on the length and content of the strings.

The MIB defined by this memo handles both IPv4 and IPv6 addressing.  Two Textual Conventions,
textual conventions, Tn3270eAddrType and Tn3270eTAddress, are defined
for this purpose.  Tn3270eTAddress is essentially equivalent to TAddress, the
TAddress TC, defined by RFC 1903.  The difference between the two is
that Tn3270eTAddress allows a null-length zero-length octet string, while TAddress
doesn't.  Allowing a null IP Address  It is important, since in places important that Tn3270eTAddress object values are used as a component of allow for the absence of
an object
  instance, address, because some objects with this syntax are used as table
indexes, and need not actually have special meanings when they contain an IP Address. In general, use

Expires May 1998                                                [Page 3]~

White      TN3270E Management Information Base (TN3270E-MIB)    20 November 1997

  of Tn3270eTAddress replaces the prior use of IpAddress to represent IP
  Addresses. zero-length
strings.

The Tn3270eAddrType textual convention is functionally equivalent to used rather than the TDomain TC, also
  defined
TC (defined by RFC 1903. 1903) for identifying the contents of a
tn3270eTAddress object.  TDomain uses an OID to identify characterize the
contents of
  a an associated TAddress object.  Tn3270eAddrType was chosen
over TDomain because, with a SYNTAX of Unsigned32 (enumeration type), it
is much simpler
  than an OID to specify use as a component in an instance identifier.

3.1.

3.1  TN3270E Server Control

This group of objects provides for TN3270E server configuration, configuration and
control.  It consists of: of three tables:

o   tn3270eSrvrConfTable
o   tn3270eSrvrPortTable
o   tn3270eSrvrStatsTable

3.1.1.

The tn3270eSrvrConfTable is the primary table within the entire
TN3270E-MIB.  As section 3.1.1 indicates, each TN3270E server is
represented by an entry in this table, indexed by tn3270eSrvrConfIndex.
Most of the other tables defined by the TN3270E-MIB have
tn3270eSrvrConfIndex as their primary index.  Entries in these tables
MUST NOT exist for a TN3270E server when it does not have a
tn3270eSrvrConfigEntry.

3.1.1  tn3270eSrvrConfTable

The tn3270eSrvrConfTable contains a set of objects primarily used for
configuring and managing a TN3270E server. servers.  As with most of the other
tables in the TN3270E-MIB, this table is indexed by an unsigned integer,
tn3270eSrvrConfIndex.  This primary index element enables support of
multiple TN3270E servers on the same host.  Within by a host, single SNMP agent.  Within the set of MIB
objects returned by one SNMP agent, tn3270eSrvrConfIndex values must MUST be
unique, and need not be contiguous; otherwise these values are
implementation-dependent.

An earlier version of this memo had used the local IP Address address associated
with a TN3270E server server, along with tn3270eSrvrConfIndex tn3270eSrvrConfIndex, as the primary
indexes into most of its tables.  Use of a local IP
  Address address was thought
to enable use of these tables by management applications.  This approach
was dropped, since it introduces a introduced another level of complexity into MIB
table indexing for little actual benefit.

The tn3270eSrvrConfInactivityTimer object defines the inactivity period
for TN3270 and TN3270E Sessions. sessions.  The tn3270eSrvrConfSessionTermState
object defines how a session should SHOULD be terminated.  The three objects:

o   tn3270eSrvrConfActivityCheck
o   tn3270eSrvrConfActivityTimeout
o   tn3270eSrvrConfActivityInterval

define the parameters for performing the "Telnet Timing Mark Option" as
defined by RFC 860 [3].  The object tn3270eSrvrConfActivityCheck is
  defined allows
a Management Station to enable selection of select either a NOP command or a TIMEMARK

Expires May 1998                                                [Page 4]~

White      TN3270E Management Information Base (TN3270E-MIB)    20 November 1997
command.  Sending a NOP command results in less overhead then a TIMEMARK
command, since a client doesn't send a reply.

The objects tn3270eSrvrConfAdminStatus and tn3270eSrvrConfOperStatus
enable remote starting and stopping of a TN3270E server.
tn3270eSrvrConfFunctionsSupported indicates which of the TN3270 and
TN3270E options a server supports.  The object
tn3270eSrvrConfSessionTermState defines as a global option the
  processing steps that a TN3270E server should perform server-wide option
what SHOULD occur when the SNA portion of a TN3270 or TN3270E session
terminates with respect to the associated TCP connection.  The object
tn3270eSrvrConfSrvrType indicates whether the TN3270E server represented
by the a tn3270eSrvrConfEntry is a host or a gateway server.  The object
tn3270eSrvrConfContact provides a scratch pad area for a TN3270E server
administrator to store information for later retrieval.  The object
tn3270eSrvrConfRowStatus provides the capability to perform
  remote row creation
and deletion operations on this table.

3.1.2.

3.1.2  tn3270eSrvrPortTable

The tn3270eSrvrPortTable exists in order to assign and retrieve represents the local TCP ports associated with
a TN3270E server, since server.  This information is important because some TN3270E
server implementations support multiple local ports.  A
tn3270eSrvrPortEntry is indexed by:

o   tn3270eSrvrConfIndex
o   tn3270eSrvrConfPort

o   tn3270eSrvrConfPortAddrType
o   tn3270eSrvrConfPortAddress

Certain TN3270E server implementations retrict restrict a local TCP port to a
particular local IP Address, address, instead of allowing connections for any
local IP Address address to occur via the port.  tn3270eSrvrConfPortAddrType and
tn3270eSrvrConfPortAddress allow this restriction to be represented in
the MIB.  A TN3270E server that doesn't restrict connections over a port
to a local IP Address should SHOULD use the value
  'unknown(0)' unknown(0) for
tn3270eSrvrConfPortAddrType, and a null zero-length octet string for
tn3270eSrvrConfPortAddress.

3.1.3.

3.1.3  tn3270eSrvrStatsTable

The tn3270eSrvrStatsTable defines a series of objects used to that provide
general usage statistics on the use of for a TN3270E server.

Expires May 1998                                                [Page 5]~

White      TN3270E Management Information Base (TN3270E-MIB)    20 November 1997

3.2.

3.2  TN3270E Server Resource Configuration

The TN3270E Server Resource Configuration collection of objects consists
of following three tables: tables provide for configuration of resources at a
TN3270E server:

o   tn3270eClientGroupTable
o   tn3270eResPoolTable
o   tn3270eClientResMapTable

tn3270eClientGroupTable and tn3270eResPoolTable enable implementations
to define groupings of both client addresses and resource pools for
mapping client addresses to resources.  The tn3270eClientResMapTable
provides a mapping of from a client group to a resource pool is enabled via the tn3270eClientResMapTable.

3.3.  Resource/Client pool.

3.3  Resource Name / Client Address Mappings

Three

The TN3270E-MIB contains three tables are defined by this memo to enable for mapping of resource names to
client addresses, and client addresses to resource names:

o   tn3270eSnaMapTable
o   tn3270eResMapTable
o TCP Connection Table Additions

3.3.1.   tn3270eTcpConnTable

3.3.1  tn3270eSnaMapTable

The tn3270eSnaMapTable is a read-only table that maps a secondary LU's
SNA network name to the name by which it is known locally at the TN3270e TN3270E
server.  For correlation with data from a the SNA network provision is made
for representation network, the name of the associating
associated primary LU name also appears in a tn3270eSnaMapEntry.  An entry in
this table is created when the Activate LU (ACTLU) request carrying the
SNA network name of the SLU is received from the SSCP.  The entry is
deleted when the SLU is deactivated.

3.3.2.

A TN3270E server provides a client with access to an SNA application by
associating a TCP connection from the client with an SNA secondary LU
(SLU) at the server.  This SLU in turn has an SNA session with a primary
LU (PLU) running on an SNA host.  This PLU represents the application
with which the client is communicating.  The TN3270E-MIB includes two

tables for mapping back and forth among the SNA name identifying the
PLU, the SNA name identifying the SLU, and the TCP connection with the
client.

In order to understand how these name mappings work, it is necessary to
understand a subtlety involving the names of the SLUs at the TN3270E
server:  these names are often different from the names by which the
SLUs are known in the rest of the SNA network.  In the TN3270E-MIB,
these two types of SLU names are termed "local names" and "SSCP-supplied
names"; the latter term indicates that the name by which the SLU is
known in the SNA network comes to the TN3270E server from the SNA System
Services Control Point.

SSCPs don't always send SLU names down to the secondary LUs; in some
cases this capability must be turned on.  In the case of SLUs served by
a Dependent LU Requester (DLUR), the capability is always turned on.
For those associated with an SNA type 2.0 node (or with a boundary
function-attached type 2.1 node), however, inclusion of SLU names on
ACTLU must be enabled explicitly at the SSCP via local configuration.

3.3.2  tn3270eResMapTable

The tn3270eResMapTable is a read-only table that maps a resource name to
a client's address.  An entry in this table is created when a TCP
connection is received by a TN3270E server and mapped to a resource.
The entry is deleted when the resource-to-address association is no
longer valid.

Expires May 1998                                                [Page 6]~

White      TN3270E Management Information Base (TN3270E-MIB)    20 November 1997

3.3.3.  TCP Connection Table Additions

3.3.3  tn3270eTcpConnTable

The TCP Connection Table is defined by RFC 2012 (Refer to reference 10,
[10], TCP-MIB Definitions). Traditionally, the contents of the TCP Connection
Table have been implementation-dependent.  Its formal definition
consists of  It contains the following objects:

o   tcpConnState (INTEGER)
o   tcpConnLocalAddress (IpAddress)
o   tcpConnLocalPort (INTEGER)
o   tcpConnRemAddress (IpAddress)
o   tcpConnRemPort (INTEGER)

It is indexed by: tcpConnLocalAddress, tcpConnLocalPort,
tcpConnRemAddress, and tcpConnRemPort.

The tn3270eTcpConnTable contains objects for keeping a list of the
current set of TN3270 and TN3270E sessions at a TN3270E server.  The
relationship between the tcpConnTable and the Tn3270eTcpConnTable is not
one-to-one, since the tn3270eTcpConnTable contains information
pertaining only to TN3270(E) sessions.

The tn3270eTcpConnTable has a different indexing structure from that of
the tcpConnTable.  Instead of using IpAddress objects, Tn3270eTAddress
and Tn3270eAddrType object pairs are used to specify client addresses
(both local and remote).  This enables support of IPv6 addresses.  In
addition, the remote address pair precedes the local address pair in the
index clause, in order to enable a GET-NEXT operation using only the
remote address pair.

4.  Definitions

3.4  Advisory Spin Lock Usage

Within the TN3270E-MIB, the tn3270eConfSpinLock object provides an
advisory lock that an implementation MAY use to let cooperating
TN3270E-MIB DEFINITIONS ::= BEGIN

  IMPORTS
      -- Some MIB Compilers applications coordinate their use of the
tn3270eSrvrConfTable, the tn3270eSrvrPortTable, the
tn3270eClientGroupTable, the tn3270eResPoolTable, and the
tn3270eClientResMapTable.  When an application seeks to create a new
entry or alter an existing entry in any of the above mentioned tables,
an implementation MAY require BITS the application to be use the
tn3270eConfSpinLock to serialize its changes or additions relative to
those initiated by other applications.  Since this is an advisory lock,
an implementation is not required to support it.

3.5  IANA Considerations

The tn3270eSrvrFunctionsSupported, tn3270eTcpConnFunctions,
tn3270eTcpConnClientIdFormat, and tn3270eTcpConnLogInfo objects use
textual conventions imported from
      -- the SNMPv2-SMI IANATn3270eTC-MIB.  The purpose of
defining these textual conventions in a separate MIB module is to allow
additional values to be defined without having to issue a new version of
this document.  The Internet Assigned Number Authority (IANA) is
responsible for the assignment of all Internet numbers, including
various SNMP-related numbers; it will administer the values associated
with these textual conventions.

The rules for additions or changes to the IANATn3270eTC-MIB are outlined
in the DESCRIPTION clause associated with its MODULE-IDENTITY statement.

The current version of the IANATn3270eTC-MIB can be accessed from the
IANA homepage at: "http://www.iana.org/iana/".

4.0  Definitions

TN3270E-MIB DEFINITIONS ::= BEGIN

IMPORTS
    MODULE-IDENTITY, OBJECT-TYPE, Unsigned32,
    TimeTicks, IpAddress,
    Counter32, Gauge32, Counter64
        FROM SNMPv2-SMI
    TEXTUAL-CONVENTION, RowStatus RowStatus, TestAndIncr
        FROM SNMPv2-TC
    MODULE-COMPLIANCE, OBJECT-GROUP
        FROM SNMPv2-CONF
    snanauMIB
        FROM SNA-NAU-MIB

Expires May 1998                                                [Page 7]~

White      TN3270E Management Information Base (TN3270E-MIB)    20 November 1997
    Utf8String
        FROM SYSAPPL-MIB; SYSAPPL-MIB
    SnmpAdminString
        FROM SNMP-FRAMEWORK-MIB
    IANATn3270eClientType, IANATn3270eLogData,
    IANATn3270Functions
        FROM IANATn3270eTC-MIB;
  tn3270eMIB MODULE-IDENTITY
      LAST-UPDATED "9711200000Z" "9802020000Z" -- November 20, 1997 February 2, 1998
      ORGANIZATION "TN3270E Working Group"
      CONTACT-INFO
          "Kenneth White (kennethw@vnet.ibm.com)
           IBM Corp." Corp. - Dept. BRQA/Bldg. 501/G114
           P.O. Box 12195
           3039 Cornwallis
           RTP, NC 27709-2195
           (919) 254-0102

           Robert Moore (remoore@us.ibm.com)
           IBM Corp. - Dept. BRQA/Bldg. 501/G114
           P.O. Box 12195
           3039 Cornwallis
           RTP, NC 27709-2195
           (919) 254-4436"
      DESCRIPTION
          "This module defines a portion of the management
          information base (MIB) for managing TN3270E servers"
      ::= { 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 letter 'A' - 'Z' and the numerics '0' - '9',
         all encoded in ASCII, with the restriction that the
         first character of each must be a letter.  Trailing
         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))

Tn3270eAddrType ::= TEXTUAL-CONVENTION
    STATUS      current
    DESCRIPTION
        "The textual convention for defining the type of an Client
           Address." a
        client address.  The enumeration value unknown(0) is
        usually used to indicate that no actual address is
        present."
    SYNTAX      INTEGER {
                          unknown(0),

Expires May 1998                                                [Page 8]~

White      TN3270E Management Information Base (TN3270E-MIB)    20 November 1997
                          ipv4(1),
                          ipv6(2)
                        }

Tn3270ResourceType ::= TEXTUAL-CONVENTION
    STATUS      current
    DESCRIPTION
        "The type of resource defined by a resource pool.  Refer
        to tn3270eResPoolTable."
    SYNTAX      INTEGER {
                          other(0),
                          lu(1),
                          printer(2)
                        }

Tn3270eTAddress ::= TEXTUAL-CONVENTION
    STATUS       current
    DESCRIPTION
          "Denotes an Client Address. a client address.  The type of Client Address client
          address is determined by use of the Tn3270eAddrType Textual
  Convention.
          textual convention.  The length in octets of a
          Tn3270eTAddress object is:

          Tn3270eAddrType ENUM       Address Length
               unknown(0)       not known, must look at specified or unknown;
                                the actual length of the
                                Tn3270eTAddress OCTET STRING.
                   ipv4(1)                4 OCTETS
                   ipv6(2)                16 octet string
                                indicates if an address
                                is present
                  ipv4(1)       4 OCTETS
                  ipv6(2)       16 OCTETS

          This textual convention is similar to the TAddress
          TC defined by RFC1903 except that it allows a zero length
            OCTET STRING
          zero-length octet string and is not a full transport
          layer address."
    SYNTAX       OCTET STRING (SIZE (0..255))

  Tn3270Functions

Tn3270DeviceTypes ::= TEXTUAL-CONVENTION
    STATUS      current
    DESCRIPTION
        "This textual convention is intended to reflect defines the
          current set list of TN3270 and TN3270E functions device
        types that can be negotiated between a server and its client:

          RFC856
          transmitBinary    The sender of this command REQUESTS
                            permission to begin transmitting, or
                            confirms that it will now begin transmitting
                            characters which are to be interpreted

Expires May 1998                                                [Page 9]~

White      TN3270E Management Information Base (TN3270E-MIB)    20 November 1997 set, as 8 bits of binary data defined by RFC 1647."
    SYNTAX      INTEGER { -- terminals
                  unknown(0),
                  ibm3278d2(1),    -- (24 row x 80 col display)
                  ibm3278d2E(2),   -- (24 row x 80 col display)
                  ibm3278d3(3),    -- (32 row x 80 col display)
                  ibm3278d3E(4),   -- (32 row x 80 col display)
                  ibm3278d4(5),    -- (43 row x 80 col display)
                  ibm3278d4E(6),   -- (43 row x 80 col display)
                  ibm3278d5(7),    -- (27 row x 132 col display)
                  ibm3278d5E(8),   -- (27 row x 132 col display)
                  ibmDynamic(9),   -- (no pre-defined display size)
                  ibm3287d1(10)    -- printers
         }

Tn3270eTraceData ::= TEXTUAL-CONVENTION
      STATUS current
      DESCRIPTION
          "An octet string representing trace data from the receiver
          Telnet half of a TN3270E session, from the data.
          RFC820
          timeMark SNA half,
          or from both.  The sender octet string contains a sequence
          of this command REQUESTS that trace elements, with order in the receiver of this command return a WILL
                           TIMING-MARK octet string
          representing order in time of the data stream at trace elements,
          from earliest to latest.

          Each trace element has the
                           'appropriate place' ...
          RFC885
          endOfRecord      The sender following form:

                +------+----+----------------------+
                !length!type!data                  !
                +------+----+----------------------+

          where:

          length = one-octet length of this command requests
                           permission to begin transmission the data portion of the
                           Telnet END-OF-RECORD (EOR)
                   trace element, not including the length and
                   type octets

          type   = one-octet code when
                           transmitting data characters, or point characterizing the sender of this command confirms it will
                           now begin transmission of EORs with
                           transmitted data characters.
          RFC1091
          terminalType     Sender is willing to send terminal type
                           information in a subsequent sub-negotiation.
          RFC1041
          tn3270Regime     Sender is willing data;
                   defined values are:

                   X'01' outbound telnet PDU to send list of supported
                           3270 Regimes in a subsequent sub-negotiation.
          RFC1647
          scsCtlCodes     (Printer sessions only).  Allows the use
                          of client
                   X'02' inbound telnet PDU from the client
                   X'03' outbound SNA Character Stream (SCS) and SCS
                          control codes on data to the session.  SCS is
                          used with LU type 1 host
                   X'04' inbound SNA sessions.
          dataStreamCtl   (Printer sessions only).  Allows the use
                          of data from the standard 3270 host

          data stream.  This
                          corresponds   = initial part of a PDU.

          It is left to LU type 3 SNA sessions.
          responses       Provides support for positive and
                          negative response handling.  Allows the
                          server implementations to reflect determine how
          much of each PDU to the client any and
                          all definite, exception, and return in a trace element.

          The zero-length string indicates that no response
                          requests sent by the host application.
          bindImage       Allows the server to send the SNA Bind
                          image and Unbind notification to trace
          data is available."
      SYNTAX OCTET STRING (SIZE (0..256))

-- Top-level structure of the
                          client.
          sysreq          Allows 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 client and server configuration elements for
        TN3270E servers.  The number of entries in this table
        is expected to emulate
                          some (or all, vary depending on the server) location of the functions of the SYSREQ key in an SNA
                          environment."
      SYNTAX      BITS {
                         transmitBinary(0),-- rfc856
                         timemark(1),      -- rfc860
                         endOfRecord(2),   -- rfc885
                         terminalType(3),  -- rfc1091
                         tn3270Regime(4),  -- rfc1041
                         scsCtlCodes(5),   -- rfc1647

Expires May 1998                                               [Page 10]~

White      TN3270E Management Information Base (TN3270E-MIB)    20 November 1997

                         dataStreamCtl(6), -- rfc1647
                         responses(7),     -- rfc1647
                         bindImage(8),     -- rfc1647
                         sysreq(9)         -- rfc1647
                       }

  Tn3270DeviceTypes ::= TEXTUAL-CONVENTION
      STATUS      current
      DESCRIPTION
          "This textual convention defines the list of device types
          that can be set as defined by RFC 1647."
      SYNTAX      INTEGER { -- terminals
                    unknown(0),
                    ibm3278d2(1),    -- (24 row x 80 col display)
                    ibm3278d2E(2),   -- (24 row x 80 col display)
                    ibm3278d3(3),    -- (32 row x 80 col display)
                    ibm3278d3E(4),   -- (32 row x 80 col display)
                    ibm3278d4(5),    -- (43 row x 80 col display)
                    ibm3278d4E(6),   -- (43 row x 80 col display)
                    ibm3278d5(7),    -- (27 row x 132 col display)
                    ibm3278d5E(8),   -- (27 row x 132 col display)
                    ibmDynamic(9),   -- (no pre-defined display size)
                    ibm3287d1(10)    -- printers
           }

  -- 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
        table.  A particular TN3270E server is expected to
        have a single entry.  Modeling of the configuration
        elements as a table allows multiple
        TN3270E Servers servers to exist at be serviced by the same host." SNMP agent."
    ::= { tn3270eObjects 1 }

tn3270eSrvrConfEntry OBJECT-TYPE

Expires May 1998                                               [Page 11]~

White      TN3270E Management Information Base (TN3270E-MIB)    20 November 1997
    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,
    tn3270eSrvrConfActivityCheck     INTEGER,
    tn3270eSrvrConfActivityTimeout   Unsigned32,
    tn3270eSrvrConfActivityInterval  Unsigned32,
    tn3270eSrvrFunctionsSupported    Tn3270Functions,    IANATn3270Functions,
    tn3270eSrvrConfAdminStatus       INTEGER,
    tn3270eSrvrConfOperStatus        INTEGER,
    tn3270eSrvrConfSessionTermState  INTEGER,
    tn3270eSrvrConfSrvrType          INTEGER,
    tn3270eSrvrConfContact           Utf8String,           SnmpAdminString,
    tn3270eSrvrConfRowStatus         RowStatus
  }

tn3270eSrvrConfIndex  OBJECT-TYPE
    SYNTAX      Unsigned32 (1..4294967295)
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
         "Indicates the instance of
       "Identifier for a single TN3270E server that
          exists at an IP Host. Assignments server.

       Assignment of tn3270eSrvrConfIndex values need not be continuous and is implementation
          dependent. Within a host, assignment of
          tn3270eSrvrConfIndex left
       entirely up to an implementation.  The values must
       need not be unique." 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.  The default of
        0 means no inactivity time-out." time-out is in effect."
    DEFVAL { 0 }
    ::= { tn3270eSrvrConfEntry 2 }

Expires May 1998                                               [Page 12]~

White      TN3270E Management Information Base (TN3270E-MIB)    20 November 1997

tn3270eSrvrConfActivityCheck OBJECT-TYPE
    SYNTAX      INTEGER {
                          noCheck(0),
                          timeMark(1),
                          nop(2)
                        }
    MAX-ACCESS  read-create
    STATUS      current
    DESCRIPTION
       "This object is intended to enable either timemark or
        nop processing."
    DEFVAL { noCheck }
    ::= { tn3270eSrvrConfEntry 3 }

tn3270eSrvrConfActivityTimeout OBJECT-TYPE
    SYNTAX      Unsigned32 (1..99999999)
    UNITS "seconds"
    MAX-ACCESS  read-create
    STATUS      current
    DESCRIPTION
       "The TIMEMARK or NOP processing time-out specified in
        seconds.  Note that a value of 0 is not allowed for
        this object since the function that uses this object
        relies on tn3270eSrvrConfActivityCheck for function
        enablement."
    DEFVAL { 600 }   -- 10 minutes
    ::= { tn3270eSrvrConfEntry 4 }

tn3270eSrvrConfActivityInterval OBJECT-TYPE
    SYNTAX      Unsigned32 (1..99999999)
    UNITS "seconds"
    MAX-ACCESS  read-create
    STATUS      current
    DESCRIPTION
       "The scan interval to be used by a TN3270E server.
        TIMEMARK or NOP processing scans the Telnet sessions
        on the interval provided by this object looking for
        sessions that have been idle for more than the value
        provided by tn3270eSrvrConfActivityTimeout.
        Note that a value of 0 is not allowed for this object
        since the function that uses this object relies on
        tn3270eSrvrConfActivityCheck for function enablement."
    DEFVAL { 120 }   -- 2 minutes
    ::= { tn3270eSrvrConfEntry 5 }

tn3270eSrvrFunctionsSupported OBJECT-TYPE
    SYNTAX    Tn3270Functions    IANATn3270Functions
    MAX-ACCESS  read-only
    STATUS      current

Expires May 1998                                               [Page 13]~

White      TN3270E Management Information Base (TN3270E-MIB)    20 November 1997
    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: server represented
         by this entry in the table:

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

           Implementation

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

         The exact semantics behavior of either a server in response to a down(2)
         or stopImmediate(3) processing command is left as implementation implementation-
         dependent.  As an example, a TN3270E server that closes
         all of its TN3270 and TN3270E sessions during termination
         is typically considered a to have terminated gracefully.

         Often a stopImmediate(3) command 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
         down(2) or stopImmediate stopImmediate(3) transitions should not
         support stopImmediate." stopImmediate(3)."
    DEFVAL { up }
    ::= { tn3270eSrvrConfEntry 7 }

tn3270eSrvrConfOperStatus OBJECT-TYPE
    SYNTAX  INTEGER {
                      up(1),   -- TN3270E server is active
                      down(2)  -- TN3270E server is not active
                    }
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
       "The current operational state of a TN3270E server:

        up(1)   - The corresponding TN3270E server is active.
        down(2) - The corresponding TN3270E server is inactive." not active.

        A TN3270E server is considered  to be active when it can
        accept new client connections.  Thus a server in the
        process of performing a graceful shutdown returns the
        value down(2) in this object. "
    DEFVAL { up }
    ::= { tn3270eSrvrConfEntry 8 }

tn3270eSrvrConfSessionTermState OBJECT-TYPE
    SYNTAX  INTEGER {
                      terminate(1),

Expires May 1998                                               [Page 14]~

White      TN3270E Management Information Base (TN3270E-MIB)    20 November 1997
                      luSessionPend(2),
                      queueSession(3)
                    }
    MAX-ACCESS  read-create
    STATUS      current
    DESCRIPTION
       "The current state for determining what a TN3270E server
        should do when a TN3270 Session terminates:

       terminate(1)     => Terminate TCP connection.
       luSessionPend(2) => Do not drop the TCP Connection
                           associated with a client when their
                           TN3270 Session ends.  Processing
                           should redrive session initialization
                           as if the client was first connecting.
       queueSession(3)  => QUEUESESSION deals with CLSDST-Pass.
                           An example is the easiest explanation.
                           Assume APPL1 does a CLSDST-Pass
                           to APPL2.  Then the client logs off
                           APPL
                             Without without QUEUESESSION the
                           connection would now be broken.  With
                           QUEUESESSION the TN3270E server keeps
                           the LU around after getting the APPL2
                           unbind waiting for a bind from APPL1."
    DEFVAL { terminate }
    ::= { tn3270eSrvrConfEntry 9 }

tn3270eSrvrConfSrvrType OBJECT-TYPE
    SYNTAX      INTEGER {
                            unknown(0),
                          host(1),
                          gateway(2)
                        }
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "This object indicates the type of TN3270E server.
        The existence of MIB tables and objects that will be
        defined by follow-on MIBs may be predicated on whether
        the TN3270E server can be local to the same host as a
          Target Application
        target application (host(1)) or will always be remote
          (gateway(2))."
      ::= { tn3270eSrvrConfEntry 10 }

  tn3270eSrvrConfContact OBJECT-TYPE
      SYNTAX      Utf8String (SIZE(0..255))
      MAX-ACCESS  read-create
      STATUS      current

Expires May 1998                                               [Page 15]~

White
        (gateway(2)).

        A host TN3270E Management Information Base (TN3270E-MIB)    20 November 1997

      DESCRIPTION
          "This object provides a scratch pad for a server refers to an implementation where
        the TN3270E server
          administrator for storing information is collocated with the Systems
        Network Architecture (SNA) System Services Control Point
        (SSCP) for later retrieval."
      ::= { tn3270eSrvrConfEntry 11 the dependent Secondary Logical Units (SLUs)
        that the server makes available to its clients for
        connecting into an SNA network.

        A gateway TN3270E server resides on an SNA node other
        than an SSCP, either an SNA type 2.0 node or an APPN node
        acting in the role of a Dependent LU Requester (DLUR).

        Host and gateway TN3270E server implementations typically
        differ greatly as to their internal implementation and
        system definition (SYSDEF) requirements."
    ::= { tn3270eSrvrConfEntry 10 }

tn3270eSrvrConfContact OBJECT-TYPE
    SYNTAX      SnmpAdminString
    MAX-ACCESS  read-create
    STATUS      current
    DESCRIPTION
        "This object provides a scratch pad for a TN3270E
        server administrator for storing information for
        later retrieval."
    ::= { tn3270eSrvrConfEntry 11 }

tn3270eSrvrConfRowStatus OBJECT-TYPE
    SYNTAX      RowStatus
    MAX-ACCESS  read-create
    STATUS      current
    DESCRIPTION
        "This object allows entries to be created and deleted
        in the tn3270eSrvrConfTable.

          An entry in this table

        When a tn3270eSrvrConfEntry is deleted by (by setting
        this object to destroy(6)." destroy(6)), this has the side-effect
        of removing all the associated entries (i.e., those
        having the same tn3270eSrvrConfIndex) from the
        tn3270eSrvrPortTable, the tn3270eSrvrStatsTable, the
        tn3270eClientGroupTable, the tn3270eResPoolTable,
        the tn3270eSnaMapTable, the tn3270eClientResMapTable,
        and the tn3270eResMapTable.  All entries in the
        tn3270eTcpConnTable that belong to a TN3270E server
        that has been deleted MUST also be removed.

        In other words, a tn3270eSrvrConfEntry must exist for
        a TN3270E server in order for it to have entries in
        any of the other tables defined by this MIB."
    REFERENCE
        "RFC 1903, 'Textual Conventions for version 2 of the
        Simple Network Management Protocol (SNMPv2).'"
    ::= { tn3270eSrvrConfEntry 12 }

tn3270eSrvrPortTable OBJECT-TYPE
    SYNTAX      SEQUENCE OF Tn3270eSrvrPortEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "This table defines the TCP ports associated with
        TN3270E
          Servers." servers.  No entry in this table SHALL exist
        without a corresponding (same tn3270eSrvrConfIndex)
        entry in the tn3270eSrvrConfTable existing."
    ::= { tn3270eObjects 2 }

tn3270eSrvrPortEntry OBJECT-TYPE
    SYNTAX      Tn3270eSrvrPortEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "Definition of a single TCP port assignment to a
         TN3270E server." server.  Assignment of a port on a local
         address basis is enabled though use of
         tn3270eSrvrPortAddrType and tn3270eSrvrPortAddress.

         A TCP port assignment that is not restricted to
         a local address SHALL specify a tn3270eSrvrPortAddrType
         of unknown(0), and SHALL use a zero-length octet string
         for the tn3270eSrvrPortAddress."
    INDEX       {
                  tn3270eSrvrConfIndex,
                  tn3270eSrvrPort,
                  tn3270eSrvrPortAddrType,
                  tn3270eSrvrPortAddress
                }
    ::= { tn3270eSrvrPortTable 1 }

Tn3270eSrvrPortEntry ::= SEQUENCE {
    tn3270eSrvrPort                 Unsigned32,
    tn3270eSrvrPortAddrType         Tn3270eAddrType,
    tn3270eSrvrPortAddress          Tn3270eTAddress,

Expires May 1998                                               [Page 16]~

White      TN3270E Management Information Base (TN3270E-MIB)    20 November 1997
    tn3270eSrvrPortRowStatus        RowStatus
  }

tn3270eSrvrPort OBJECT-TYPE
    SYNTAX      Unsigned32 (0..65535)
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
       "Indicates a port assigned to a server."
    ::= { tn3270eSrvrPortEntry 1 }

tn3270eSrvrPortAddrType OBJECT-TYPE
    SYNTAX      Tn3270eAddrType
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "Indicates the type of an address local to the Client Address host on
        which the TN3270E server resides that is represented
        in
           tn3270eSrvrPortAddress." tn3270eSrvrPortAddress.  A value of unknown(0)
        SHALL be used for this object when the port is not
        to be restricted to a local address."
    ::= { tn3270eSrvrPortEntry 2 }

tn3270eSrvrPortAddress OBJECT-TYPE
    SYNTAX      Tn3270eTAddress
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
          "The Client Address
        "A local address on the host that a TN3270E server
         resides on that is associated with a TCP port that
         is to be used or is in use by a TN3270E server port. server.
         tn3270eClientGroupAddrType indicates the
         address type (ipv4 or ipv6 for example)." example).

         A zero-length octet string SHALL be used as the
         value of this object when a local address isn't
         being specified."
    ::= { tn3270eSrvrPortEntry 3 }

tn3270eSrvrPortRowStatus OBJECT-TYPE
    SYNTAX      RowStatus
    MAX-ACCESS  read-create
    STATUS      current
    DESCRIPTION
        "This object allows entries to be created and deleted
        in the tn3270eSrvrPortTable.

        An entry in this table is deleted by setting this object
        to destroy(6)." destroy(6).  Deletion of a tn3270eSrvrPortEntry has
        no effect on any other table entry defined by this MIB."
    REFERENCE
        "RFC 1903, 'Textual Conventions for version 2 of the
        Simple Network Management Protocol (SNMPv2).'"
    ::= { tn3270eSrvrPortEntry 4 }

tn3270eSrvrStatsTable OBJECT-TYPE
    SYNTAX      SEQUENCE OF Tn3270eSrvrStatsEntry
    MAX-ACCESS  not-accessible

Expires May 1998                                               [Page 17]~

White      TN3270E Management Information Base (TN3270E-MIB)    20 November 1997
    STATUS      current
    DESCRIPTION
        "This table defines a set of statistics concerning
          global
        TN3270E server performance." performance.

        No entry in this table SHALL exist without
        a corresponding (same tn3270eSrvrConfIndex) entry in
        the tn3270eSrvrConfTable existing."
    ::= { tn3270eObjects 3 }

tn3270eSrvrStatsEntry OBJECT-TYPE
    SYNTAX      Tn3270eSrvrStatsEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
          "Collection of a set
        "A collection of statistic statistical objects for a single
        TN3270 server.  An entry can be global with respect to
          a single TN3270E server represent the total
        activity of the server, or be specified it can represent
        the activity occurring at the server on either
        a port level. or port-and-local-address basis.
        Refer to the text description for tn3270eSrvrStatsPort.

          It tn3270eSrvrPortEntry.

        Collection of the statistics represented by the objects
        in this table is possible that a TN3270E server not mandatory.  An implementation may
          not be structured
        limit itself to support resource usage on a port basis
          but provide keeping global statistics via an entry in this table for
          each port. a TN3270E
        server.  The recommended approach indexing for this is to
          provide a the row containing these
        global entry (a server statistics is as follows:

             tn3270eSrvrConfIndex       value of identifying the server
             tn3270eSrvrPort            0
             tn3270eSrvrPortAddrType    unknown(0)
             tn3270eSrvrPortAddress     zero-length octet string.

        The values of the following objects are implementation-
        dependent for
          tn3270eSrvrStatsPort) with: statistics that are being kept on either
        a port or port-and-local-address basis:

             tn3270eSrvrStatsMaxLus
             tn3270eSrvrStatsMaxLus
               tn3270eSrvrStatsLusInUse
             tn3270eSrvrStatsInUseLus
             tn3270eSrvrStatsSpareLus
             tn3270eSrvrStatsMaxPtrs
               tn3270eSrvrStatsPtrsInUse
             tn3270eSrvrStatsInUsePtrs
             tn3270eSrvrStatsSparePtrs

        set at this layer but set to zero at

        A TN3270E server that doesn't allow assignment of the
        resources being reported on by these objects on either
        a port layer." or port-and-local-address basis should use the
        values that would be associated with an entire TN3270E
        server."
    INDEX       {
                  tn3270eSrvrConfIndex, tn3270eSrvrStatsPort
                  tn3270eSrvrPort,
                  tn3270eSrvrPortAddrType,
                  tn3270eSrvrPortAddress
                }
    ::= { tn3270eSrvrStatsTable 1 }

Tn3270eSrvrStatsEntry ::= SEQUENCE {
      tn3270eSrvrStatsPort            Unsigned32,
    tn3270eSrvrStatsUpTime          TimeTicks,
    tn3270eSrvrStatsMaxLus          Unsigned32,
      tn3270eSrvrStatsLusInUse
    tn3270eSrvrStatsInUseLus        Gauge32,
    tn3270eSrvrStatsSpareLus        Gauge32,
    tn3270eSrvrStatsMaxPtrs         Unsigned32,
      tn3270eSrvrStatsPtrsInUse
    tn3270eSrvrStatsInUsePtrs       Gauge32,
    tn3270eSrvrStatsSparePtrs       Gauge32,
      tn3270eSrvrStatsConnectsIn
    tn3270eSrvrStatsInConnects      Counter32,
    tn3270eSrvrStatsConnRejects     Counter32,
    tn3270eSrvrStatsDisconnects     Counter32,
      tn3270eSrvrStatsOctetsIn
    tn3270eSrvrStatsHCInOctets      Counter64,

Expires May 1998                                               [Page 18]~

White      TN3270E Management Information Base (TN3270E-MIB)    20 November 1997

      tn3270eSrvrStatsOctetsInLow
    tn3270eSrvrStatsInOctets        Counter32,
      tn3270eSrvrStatsOctetsOut
    tn3270eSrvrStatsHCOutOctets     Counter64,
      tn3270eSrvrStatsOctetsOutLow
    tn3270eSrvrStatsOutOctets       Counter32
  }

  tn3270eSrvrStatsPort OBJECT-TYPE
      SYNTAX      Unsigned32 (0..65535)
      MAX-ACCESS  not-accessible
      STATUS      current
      DESCRIPTION
         "Indicates the port that the corresponding statistics are
          for. Implementation of collection of these statistics
          on a port basis is not mandatory. An implementation may
          limit itself to keeping this data on a global basis by
          using a value of 0."
      ::= { tn3270eSrvrStatsEntry 1 }

  tn3270eSrvrStatsUpTime

tn3270eSrvrStatsUpTime OBJECT-TYPE
    SYNTAX      TimeTicks
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
       "Indicates when either usage of a associating port becomes
          active (tn3270eSrvrStatsPort non-zero) or if the entry
          is being kept on activity begins for a global basis the time that the TN3270E server becomes active.
       as represented by an entry in this table.  The value
       of this object does not get reset based on port usage
       status changes or changes to tn3270eSrvrConfOperStatus."
    ::= { tn3270eSrvrStatsEntry 2 }

tn3270eSrvrStatsMaxLus OBJECT-TYPE
    SYNTAX      Unsigned32
    UNITS       "LUs"
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
       "Indicates the maximum number of LUs for use by a
        TN3270E server. The granularity of this data can be
          either global (corresponding tn3270eSrvrStatsPort index
          equal to 0) or on a port basis." server."
    ::= { tn3270eSrvrStatsEntry 3 }

  tn3270eSrvrStatsLusInUse

tn3270eSrvrStatsInUseLus OBJECT-TYPE
    SYNTAX      Gauge32
    UNITS       "LUs"
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
       "Indicates the current number of LUs in use by a
        TN3270E server. The granularity of this data can be

Expires May 1998                                               [Page 19]~

White      TN3270E Management Information Base (TN3270E-MIB)    20 November 1997

          either global (corresponding tn3270eSrvrStatsPort index
          equal to 0) or on a port basis." server."
    ::= { tn3270eSrvrStatsEntry 4 }

tn3270eSrvrStatsSpareLus OBJECT-TYPE
    SYNTAX      Gauge32
    UNITS       "LUs"
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
       "Indicates the number of free LUs for a particular
       TN3270E server.  It is possible that the difference
       between tn3270eSrvrStatsMaxLus and tn3270eSrvrStatsLusInUse
       tn3270eSrvrStatsInUseLus does not equal
       tn3270eSrvrStatsSpareLus.  An LU may exist
       but not be useable usable by an client connection.
          The granularity of this data can be
          either global (corresponding tn3270eSrvrStatsPort index
          equal to 0) or on a port basis." connection."
    ::= { tn3270eSrvrStatsEntry 5 }

tn3270eSrvrStatsMaxPtrs OBJECT-TYPE
    SYNTAX      Unsigned32
    UNITS       "Printer Resources"
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
       "Indicates the maximum number of Printer Resources for
        use by a TN3270E server. The granularity of this data
          can be either global (corresponding tn3270eSrvrStatsPort
          index equal to 0) or on a port basis." server."
    ::= { tn3270eSrvrStatsEntry 6 }

  tn3270eSrvrStatsPtrsInUse

tn3270eSrvrStatsInUsePtrs OBJECT-TYPE
    SYNTAX      Gauge32
    UNITS       "Printer Resources"
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
       "Indicates the current number of Printer Resources in
        use by a TN3270E server. The granularity of this data
          can be either global (corresponding tn3270eSrvrStatsPort
          index equal to 0) or on a port basis." server."
    ::= { tn3270eSrvrStatsEntry 7 }

tn3270eSrvrStatsSparePtrs OBJECT-TYPE
    SYNTAX      Gauge32
    UNITS       "Spare Printer Resources"
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
       "Indicates the number of free Printer Resources for a
        particular TN3270E server.  It is possible that the

Expires May 1998                                               [Page 20]~

White      TN3270E Management Information Base (TN3270E-MIB)    20 November 1997
        difference between tn3270eSrvrStatsMaxPtrs and
          tn3270eSrvrStatsPtrsInUse
        tn3270eSrvrStatsInUsePtrs does not equal
        tn3270eSrvrStatsSparePtrs.  A Printer resource may
        exist but not be useable usable by an client connection.
          The granularity of this data
          can be either global (corresponding tn3270eSrvrStatsPort
          index equal to 0) or on a port basis." connection."
    ::= { tn3270eSrvrStatsEntry 8 }

  tn3270eSrvrStatsConnectsIn

tn3270eSrvrStatsInConnects OBJECT-TYPE
    SYNTAX      Counter32
    UNITS       "connections"
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
       "Indicates the number of client (TCP) connections received by that
       succeeded at a TN3270E server. The granularity of this data
          can be either global (corresponding tn3270eSrvrStatsPort
          index equal to 0) or on a port basis."  tn3270eSrvrStatsConnRejects
       represents failed connection attempts."
    ::= { tn3270eSrvrStatsEntry 9 }

tn3270eSrvrStatsConnRejects OBJECT-TYPE
    SYNTAX      Counter32
    UNITS       "connection attempts"
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
       "Indicates the number of client (TCP) connections rejected
       during connection setup. setup at a TN3270E server.  An example
       of this is when no LU or
          Printer printer resource is available
       to associate with the the client's TCP Connection of an client. The granularity of this data
          can be either global (corresponding tn3270eSrvrStatsPort
          index equal to 0) or on a port basis." connection."
    ::= { tn3270eSrvrStatsEntry 10 }

tn3270eSrvrStatsDisconnects OBJECT-TYPE
    SYNTAX      Counter32
    UNITS       "disconnections"
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
       "Indicates the number all of client the (TCP) connections that were
       disconnected by at a TN3270E server. The granularity of this data
          can be either global (corresponding tn3270eSrvrStatsPort
          index equal to 0) or on a port basis." server."
    ::= { tn3270eSrvrStatsEntry 11 }

  tn3270eSrvrStatsOctetsIn

tn3270eSrvrStatsHCInOctets OBJECT-TYPE
    SYNTAX      Counter64
    UNITS       "octets"
    MAX-ACCESS  read-only
    STATUS      current

Expires May 1998                                               [Page 21]~

White      TN3270E Management Information Base (TN3270E-MIB)    20 November 1997
    DESCRIPTION
       "Indicates the number of octets received from TN3270
        and TN3270E Clients.  The granularity
          of this data  can be either global (corresponding
          tn3270eSrvrStatsPort index equal to 0) or on a port basis." clients."
    ::= { tn3270eSrvrStatsEntry 12 }

  tn3270eSrvrStatsOctetsInLow

tn3270eSrvrStatsInOctets OBJECT-TYPE
    SYNTAX      Counter32
    UNITS       "octets"
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
       "Low order 32 bits of tn3270eSrvrStatsOctetsIn." tn3270eSrvrStatsHCInOctets."
    ::= { tn3270eSrvrStatsEntry 13 }

  tn3270eSrvrStatsOctetsOut

tn3270eSrvrStatsHCOutOctets OBJECT-TYPE
    SYNTAX      Counter64
    UNITS       "octets"
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
       "Indicates the number of octets sent to TN3270
        and TN3270E Clients. The granularity
          of this data  can be either global (corresponding
          tn3270eSrvrStatsPort index equal to 0) or on a port basis." clients."
    ::= { tn3270eSrvrStatsEntry 14 }

  tn3270eSrvrStatsOctetsOutLow

tn3270eSrvrStatsOutOctets OBJECT-TYPE
    SYNTAX      Counter32
    UNITS       "octets"
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
       "Low order 32 bits of tn3270eSrvrStatsOctetsOut." tn3270eSrvrStatsHCOutOctets."
    ::= { tn3270eSrvrStatsEntry 15 }

tn3270eClientGroupTable OBJECT-TYPE
    SYNTAX      SEQUENCE OF Tn3270eClientGroupEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "This table defines client address groupings for use
        by a TN3270E server." server.

        No entry in this table SHALL exist without
        a corresponding (same tn3270eSrvrConfIndex) entry in
        the tn3270eSrvrConfTable existing."
    ::= { tn3270eObjects 4 }

tn3270eClientGroupEntry OBJECT-TYPE
    SYNTAX      Tn3270eClientGroupEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION

Expires May 1998                                               [Page 22]~

White      TN3270E Management Information Base (TN3270E-MIB)    20 November 1997
        "Definition of a single client address entry.  All
        entries with the same first two indexes,
        tn3270eSrvrConfIndex and tn3270eClientGroupName, are
        considered to be in the same client group."
    INDEX       { tn3270eSrvrConfIndex,
                  tn3270eClientGroupName,
                  tn3270eClientGroupAddrType,
                  tn3270eClientGroupAddress }
    ::= { tn3270eClientGroupTable 1 }

Tn3270eClientGroupEntry ::= SEQUENCE {
    tn3270eClientGroupName           Utf8String,
    tn3270eClientGroupAddrType       Tn3270eAddrType,
    tn3270eClientGroupAddress        Tn3270eTAddress,
    tn3270eClientGroupSubnetMask     IpAddress,
    tn3270eClientGroupPfxLength      Unsigned32,
    tn3270eClientGroupRowStatus      RowStatus }

tn3270eClientGroupName OBJECT-TYPE
    SYNTAX      Utf8String (SIZE(1..24))
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "The name of a client group." group.  Note: client group
        names are required to be unique only with respect
        to a single TN3270E server."
    ::= { tn3270eClientGroupEntry 1 }

tn3270eClientGroupAddrType OBJECT-TYPE
    SYNTAX      Tn3270eAddrType
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "Indicates the type of the address represented in
         tn3270eClientGroupAddress."
    ::= { tn3270eClientGroupEntry 2 }

tn3270eClientGroupAddress OBJECT-TYPE
    SYNTAX      Tn3270eTAddress
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "The client address of a member of a client group.
        The value of tn3270eClientGroupAddrType indicates
        the address type (ipv4 or ipv6 for example)."
    ::= { tn3270eClientGroupEntry 3 }

tn3270eClientGroupSubnetMask OBJECT-TYPE
    SYNTAX      IpAddress
    MAX-ACCESS  read-create

Expires May 1998                                               [Page 23]~

White      TN3270E Management Information Base (TN3270E-MIB)    20 November 1997
    STATUS      current
    DESCRIPTION
        "The corresponding subnet mask associated with
         tn3270eClientGroupAddress.  A single IP Address address is
         represented by having this object contain the value
         of 255.255.255.255.  This object object's value is valid
         meaningful only if tn3270eClientGroupAddrType has a
         value of ipv4(1)."
    DEFVAL { 'FFFFFFFF'H }
    ::= { tn3270eClientGroupEntry 4 }

tn3270eClientGroupPfxLength OBJECT-TYPE
    SYNTAX      Unsigned32 (0..128)
    UNITS       "bits"
    MAX-ACCESS  read-create
    STATUS      current
    DESCRIPTION
        "The corresponding IPv6 network prefix length.  This
         object is valid only if tn3270eClientGroupAddrType
         has a value of ipv6(2)."
    DEFVAL { 0 }
    ::= { tn3270eClientGroupEntry 5 }

tn3270eClientGroupRowStatus OBJECT-TYPE
    SYNTAX      RowStatus
    MAX-ACCESS  read-create
    STATUS      current
    DESCRIPTION
        "This object allows entries to be created and deleted
        in the tn3270eClientGroupTable.

        An entry in this table is deleted by setting this object
        to destroy(6)." destroy(6).  This has the side-effect of removing
        any entries in the tn3270eClientResMapTable for the client
        group being removed (tn3270eSrvrConfIndex values should be
        the same and tn3270eClientGroupName should match
        tn3270eClientResMapClientGroupName.)"
    REFERENCE
        "RFC 1903, 'Textual Conventions for version 2 of the
        Simple Network Management Protocol (SNMPv2).'"
    ::= { tn3270eClientGroupEntry 6 }

tn3270eResPoolTable OBJECT-TYPE
    SYNTAX      SEQUENCE OF Tn3270eResPoolEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "This table defines resource groupings; the term
        'pool' is used as it is defined by RFC 1647." 1647.

        No entry in this table SHALL exist without
        a corresponding (same tn3270eSrvrConfIndex) entry in
        the tn3270eSrvrConfTable existing."
    ::= { tn3270eObjects 5 }

tn3270eResPoolEntry OBJECT-TYPE
    SYNTAX      Tn3270eResPoolEntry
    MAX-ACCESS  not-accessible

Expires May 1998                                               [Page 24]~

White      TN3270E Management Information Base (TN3270E-MIB)    20 November 1997
    STATUS      current
    DESCRIPTION
        "Definition of a single resource pool member.  All entries
        with the same first two indexes, tn3270eSrvrConfIndex and
        tn3270eResPoolName, are considered to be in the same pool."
    INDEX  { tn3270eSrvrConfIndex,
             tn3270eResPoolName,
             tn3270eResPoolElementName }
    ::= { tn3270eResPoolTable 1 }

Tn3270eResPoolEntry ::= SEQUENCE {
    tn3270eResPoolName           Utf8String,
    tn3270eResPoolElementName    SnaResourceName,
    tn3270eResPoolElementType    Tn3270ResourceType,
    tn3270eResPoolRowStatus      RowStatus }

tn3270eResPoolName OBJECT-TYPE
    SYNTAX      Utf8String (SIZE(1..24))
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "The name of a resource pool.." pool."
    ::= { tn3270eResPoolEntry 1 }

tn3270eResPoolElementName OBJECT-TYPE
    SYNTAX      SnaResourceName
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "The name of a member of a resource pool."
    ::= { tn3270eResPoolEntry 2 }

tn3270eResPoolElementType OBJECT-TYPE
    SYNTAX      Tn3270ResourceType
    MAX-ACCESS  read-create
    STATUS      current
    DESCRIPTION
        "The type of the entity in a resource pool."
    ::= { tn3270eResPoolEntry 3 }

tn3270eResPoolRowStatus OBJECT-TYPE
    SYNTAX      RowStatus
    MAX-ACCESS  read-create
    STATUS      current
    DESCRIPTION
        "This object allows entries to be created and deleted in
        the tn3270eResPoolTable.

Expires May 1998                                               [Page 25]~

White      TN3270E Management Information Base (TN3270E-MIB)    20 November 1997

        An entry in this table is deleted by setting this object
        to destroy(6)." destroy(6).  When all entries in this table associated
        with the same tn3270eResPoolElementName have been removed,
        then any associated (tn3270eResPoolElementName matching
        tn3270eClientResMapPoolName with same tn3270eSrvrConfIndex
        values) entries in the tn3270eClientResMapTable SHALL
        also be removed."
    REFERENCE
        "RFC 1903, 'Textual Conventions for version 2 of the
        Simple Network Management Protocol (SNMPv2).'"
    ::= { tn3270eResPoolEntry 4 }

tn3270eSnaMapTable OBJECT-TYPE
    SYNTAX      SEQUENCE OF Tn3270eSnaMapEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "This table provide a mapping from the name by which
        a secondary LU is known in the SNA network to the
        name by which it is known locally at the TN3270e
        server.  This latter name serves as an index into
        the tn3270eResPoolTable and the tn3270eResMapTable." tn3270eResMapTable.

        No entry in this table SHALL exist without
        a corresponding (same tn3270eSrvrConfIndex) entry in
        the tn3270eSrvrConfTable existing."
    ::= { tn3270eObjects 6 }

tn3270eSnaMapEntry OBJECT-TYPE
    SYNTAX      Tn3270eSnaMapEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "Definition of a single mapping from an SSCP-supplied
         SLU name to a local SLU name."
    INDEX  { tn3270eSrvrConfIndex,
             tn3270eSnaMapSscpSuppliedName }
    ::= { tn3270eSnaMapTable 1 }

Tn3270eSnaMapEntry ::= SEQUENCE {
    tn3270eSnaMapSscpSuppliedName     SnaResourceName,
    tn3270eSnaMapLocalName            SnaResourceName,
    tn3270eSnaMapPrimaryLuName        SnaResourceName }

tn3270eSnaMapSscpSuppliedName OBJECT-TYPE
    SYNTAX      SnaResourceName
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "The name of the secondary LU (SLU) as it is known in
         the SNA network.  This name is sent by the SSCP on
         the Activate Logical Unit (ACTLU) request."
    ::= { tn3270eSnaMapEntry 1 }

tn3270eSnaMapLocalName OBJECT-TYPE
    SYNTAX      SnaResourceName
    MAX-ACCESS  read-only

Expires May 1998                                               [Page 26]~

White      TN3270E Management Information Base (TN3270E-MIB)    20 November 1997
    STATUS      current
    DESCRIPTION
        "The local name of the secondary LU (SLU)."
    ::= { tn3270eSnaMapEntry 2 }

tn3270eSnaMapPrimaryLuName  OBJECT-TYPE
      SYNTAX   SnaResourceName
      MAX-ACCESS   read-only
      STATUS   current
      DESCRIPTION
          "When there is a currently active LU-LU session for
          this connection, this object returns the primary LU
          (PLU) name from the BIND.  When there is no active
          LU-LU session, or when the PLU name is unavailable
          for some other reason, this object returns the empty a
          zero-length octet string."
      ::= { tn3270eSnaMapEntry 3 }

tn3270eClientResMapTable OBJECT-TYPE
    SYNTAX      SEQUENCE OF Tn3270eClientResMapEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "This table defines resource pool resource-pool to client group client-group
        mappings.  Since both the resource pool name and client
        group name are included in the index clause of this
        table, multiple resource pools can be assigned to the
        same client group.  This enables use of multiple
        resource pools for use in client to resource mapping.
        Assigning multiple client Groups to the same resource
        pool is also allowed, but is not the primary purpose
        for how the indexing is structured.

        Assignment of a resource pool to client group can be
        restricted based on TCP port.  An index value of 0 for
        tn3270eClientResMapClientPort disables restriction of
        resource assignment based on client target port selection."
        selection.

        No entry in this table SHALL exist without
        a corresponding (same tn3270eSrvrConfIndex) entry in
        the tn3270eSrvrConfTable existing."
    ::= { tn3270eObjects 7 }

tn3270eClientResMapEntry OBJECT-TYPE
    SYNTAX      Tn3270eClientResMapEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "Definition of a single resource pool to client group
        mapping."
    INDEX  { tn3270eSrvrConfIndex,
             tn3270eClientResMapPoolName,
             tn3270eClientResMapClientGroupName,
             tn3270eClientResMapClientPort }

Expires May 1998                                               [Page 27]~

White      TN3270E Management Information Base (TN3270E-MIB)    20 November 1997
    ::= { tn3270eClientResMapTable 1 }

Tn3270eClientResMapEntry ::= SEQUENCE {
    tn3270eClientResMapPoolName           Utf8String,
    tn3270eClientResMapClientGroupName    Utf8String,
    tn3270eClientResMapClientPort         Unsigned32,
    tn3270eClientResMapRowStatus          RowStatus }

tn3270eClientResMapPoolName OBJECT-TYPE
    SYNTAX      Utf8String (SIZE(1..24))
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "The name of a resource pool."
    ::= { tn3270eClientResMapEntry 1 }

tn3270eClientResMapClientGroupName OBJECT-TYPE
    SYNTAX      Utf8String (SIZE(1..24))
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "The name of the client group that is mapped to a
         resource pool."
    ::= { tn3270eClientResMapEntry 2 }

tn3270eClientResMapClientPort OBJECT-TYPE
    SYNTAX      Unsigned32 (0..65535)
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "The port to restrict a resource pool to a client
        group mapping.  A value of 0 for this objects implies
        that the mapping is not restricted."
    ::= { tn3270eClientResMapEntry 3 }

tn3270eClientResMapRowStatus OBJECT-TYPE
    SYNTAX      RowStatus
    MAX-ACCESS  read-create
    STATUS      current
    DESCRIPTION
        "This object allows entries to be created and deleted
        in the tn3270eClientResMapTable.

        An entry in this table is deleted by setting this object
        to destroy(6)." destroy(6).  Removing an entry from this table doesn't
        affect any other table entry defined by this MIB."
    REFERENCE
        "RFC 1903, 'Textual Conventions for version 2 of the
        Simple Network Management Protocol (SNMPv2).'"

Expires May 1998                                               [Page 28]~

White      TN3270E Management Information Base (TN3270E-MIB)    20 November 1997
    ::= { tn3270eClientResMapEntry 4 }

tn3270eResMapTable OBJECT-TYPE
    SYNTAX      SEQUENCE OF Tn3270eResMapEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "This table defines the actual mapping of a resource
        to a client Address." address.

        No entry in this table SHALL exist without
        a corresponding (same tn3270eSrvrConfIndex) entry in
        the tn3270eSrvrConfTable existing."
    ::= { tn3270eObjects 8 }

tn3270eResMapEntry OBJECT-TYPE
    SYNTAX      Tn3270eResMapEntry
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "Definition of the mapping of a Resource Element to
         a client Address." address."
    INDEX  { tn3270eSrvrConfIndex,
             tn3270eResMapElementName }
    ::= { tn3270eResMapTable 1 }

Tn3270eResMapEntry ::= SEQUENCE {
    tn3270eResMapElementName       SnaResourceName,
    tn3270eResMapAddrType          Tn3270eAddrType,
    tn3270eResMapAddress           Tn3270eTAddress,
    tn3270eResMapPort              Unsigned32,
    tn3270eResMapElementType       Tn3270ResourceType,
    tn3270eResMapSscpSuppliedName  SnaResourceName }

tn3270eResMapElementName OBJECT-TYPE
    SYNTAX      SnaResourceName
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "The name of a resource element.  This is the name by
        which the server implementing this table knows the
        resource.  It may be different from the name by which
        the resource is known in the SNA network.  In this case
        the name by which the resource is known in the SNA
        network is returned in the tn3270eResMapSscpSuppliedName
        object."
    ::= { tn3270eResMapEntry 1 }

tn3270eResMapAddrType OBJECT-TYPE
    SYNTAX      Tn3270eAddrType
    MAX-ACCESS  read-only
    STATUS      current

Expires May 1998                                               [Page 29]~

White      TN3270E Management Information Base (TN3270E-MIB)    20 November 1997
    DESCRIPTION
        "Indicates the type of the client Address address represented
        in tn3270eResMapAddress."
    ::= { tn3270eResMapEntry 2 }

tn3270eResMapAddress OBJECT-TYPE
    SYNTAX      Tn3270eTAddress
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "A client address."
    ::= { tn3270eResMapEntry 3 }

tn3270eResMapPort OBJECT-TYPE
    SYNTAX      Unsigned32 (0..65535)
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "A client Port." port."
    ::= { tn3270eResMapEntry 4 }

tn3270eResMapElementType OBJECT-TYPE
    SYNTAX      Tn3270ResourceType
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The type of the associating associated resource element."
    ::= { tn3270eResMapEntry 5 }

tn3270eResMapSscpSuppliedName OBJECT-TYPE
    SYNTAX      SnaResourceName
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The name of the secondary LU (SLU) as it is known in the a
        SNA network.  This name is sent by the SSCP on the
        Activate Logical Unit (ACTLU) request.  The value of
        this object is the empty a zero-length octet string if the
        tn3270eResMapElementName is the same as the
        SSCP-supplied name."
    ::= { tn3270eResMapEntry 6 }

-- Define the set of objects to add to supplement the Tcp TCP Connection Table

tn3270eTcpConnTable OBJECT-TYPE
    SYNTAX SEQUENCE OF Tn3270eTcpConnEntry
    MAX-ACCESS not-accessible
    STATUS current
    DESCRIPTION

Expires May 1998                                               [Page 30]~

White      TN3270E Management Information Base (TN3270E-MIB)    20 November 1997
         "Provides a table that has an entry for each TN3270(E)
          client connection that is active at a TN3270E server.
          The table was originally modeled after the tcpConnTable
          but was changed to support different client Address address types
          and to be indexed first by the remote address and port
          as oppose to local address and port.  This is to enable
          use of a SNMP GET-NEXT operation using only the remote
          address and port."
    ::= { tn3270eObjects 9 }

tn3270eTcpConnEntry OBJECT-TYPE
    SYNTAX Tn3270eTcpConnEntry
    MAX-ACCESS not-accessible
    STATUS current
    DESCRIPTION
         "Provides in formation about a single TN3270/TN3270E
          session.  Note: a tn3270eSrvrConfIndex is not needed
          in this table since the combination of both remote
          local addresses and ports is sufficient to
          guarantee uniqueness between TN3270E Servers on servers that
          may or may not be serviced by the same or actually different hosts." SNMP agent."
    INDEX { tn3270eTcpConnRemAddrType,
            tn3270eTcpConnRemAddress,
            tn3270eTcpConnRemPort,
            tn3270eTcpConnLocalAddrType,
            tn3270eTcpConnLocalAddress,
            tn3270eTcpConnLocalPort
          }
    ::= { tn3270eTcpConnTable 1 }

Tn3270eTcpConnEntry ::=
    SEQUENCE
    {
        tn3270eTcpConnRemAddrType          Tn3270eAddrType,
        tn3270eTcpConnRemAddress           Tn3270eTAddress,
        tn3270eTcpConnRemPort              Unsigned32,
        tn3270eTcpConnLocalAddrType        Tn3270eAddrType,
        tn3270eTcpConnLocalAddress         Tn3270eTAddress,
        tn3270eTcpConnLocalPort            Unsigned32,
        tn3270eTcpConnLastActivity         TimeTicks,
        tn3270eTcpConnBytesIn              Counter32,
        tn3270eTcpConnBytesOut             Counter32,
        tn3270eTcpConnResourceElement      SnaResourceName,
        tn3270eTcpConnResourceType         Tn3270ResourceType,
        tn3270eTcpConnDeviceType           Tn3270DeviceTypes,
        tn3270eTcpConnFunctions          Tn3270Functions,            IANATn3270Functions,
        tn3270eTcpConnId                   Unsigned32,
        tn3270eTcpConnClientIdFormat     INTEGER,

Expires May 1998                                               [Page 31]~

White      TN3270E Management Information Base (TN3270E-MIB)    20 November 1997       IANATn3270eClientType,
        tn3270eTcpConnClientId             OCTET STRING,
          tn3270eTcpConnMiscInfoFormat     BITS,
          tn3270eTcpConnMiscInfo           OCTET STRING,
        tn3270eTcpConnTraceData            Tn3270eTraceData,
        tn3270eTcpConnLogInfo              IANATn3270eLogData,
        tn3270eTcpConnLuLuBindImage        OCTET STRING,
        tn3270eTcpConnSnaState           INTEGER             INTEGER,
        tn3270eTcpConnStateLastDiscReason  INTEGER,
        tn3270eTcpConnSrvrConfIndex        Unsigned32
    }

tn3270eTcpConnRemAddrType OBJECT-TYPE
    SYNTAX   Tn3270eAddrType
    MAX-ACCESS   not-accessible
    STATUS   current
    DESCRIPTION
        "Indicates the type of the value of the
        tn3270eTcpConnRemAddress object.  For example,
        ipv4(1) or ipv6(2)."
    ::= { tn3270eTcpConnEntry 1 }

tn3270eTcpConnRemAddress OBJECT-TYPE
    SYNTAX      Tn3270eTAddress
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "The remote address associated with a TN3270E client.
         tn3270eTcpConnRemAddrType indicates the address type
         (ipv4 or ipv6 for example).

         If a TN3270(E) client is connected to its
         server via a proxy client the address represented by
         the value of this object should shall be the remote client's
         address, not the proxy client's address."
    ::= { tn3270eTcpConnEntry 2 }

tn3270eTcpConnRemPort OBJECT-TYPE
    SYNTAX      Unsigned32 (0..65535) (1..65535)
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "The remote port associated with a TN3270E client.

         If a TN3270(E) client is connected to its
         server via a proxy client the port represented by
         the value of this object should shall be the remote client's
         port, not the proxy client's port."
    ::= { tn3270eTcpConnEntry 3 }

tn3270eTcpConnLocalAddrType OBJECT-TYPE
    SYNTAX   Tn3270eAddrType
    MAX-ACCESS   not-accessible

Expires May 1998                                               [Page 32]~

White      TN3270E Management Information Base (TN3270E-MIB)    20 November 1997
    STATUS   current
    DESCRIPTION
        "Indicates the type of the value of the
        tn3270eTcpConnLocalAddress object.  For example,
        ipv4(1) or ipv6(2)."
    ::= { tn3270eTcpConnEntry 4 }

tn3270eTcpConnLocalAddress OBJECT-TYPE
    SYNTAX      Tn3270eTAddress
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "The local address associated with a TN3270E client.
         tn3270eTcpConnRemAddrType indicates the address type
         (ipv4 or ipv6 for example)."
    ::= { tn3270eTcpConnEntry 5 }

tn3270eTcpConnLocalPort OBJECT-TYPE
    SYNTAX      Unsigned32 (0..65535) (1..65535)
    MAX-ACCESS  not-accessible
    STATUS      current
    DESCRIPTION
        "The remote port associated with a TN3270E client."
    ::= { tn3270eTcpConnEntry 6 }

tn3270eTcpConnLastActivity OBJECT-TYPE
    SYNTAX   TimeTicks
    MAX-ACCESS   read-only
    STATUS   current
    DESCRIPTION
        "The number of 100ths of seconds since any data was
         transferred for the associating associated TCP Connection."
    DEFVAL  { 0 }
    ::= { tn3270eTcpConnEntry 7 }

tn3270eTcpConnBytesIn  OBJECT-TYPE
    SYNTAX   Counter32
    UNITS "octets"
    MAX-ACCESS   read-only
    STATUS   current
    DESCRIPTION
        "The number of bytes received by the server from TCP
         for this connection."
    ::= { tn3270eTcpConnEntry 8 }

tn3270eTcpConnBytesOut OBJECT-TYPE
    SYNTAX   Counter32
    UNITS "octets"

Expires May 1998                                               [Page 33]~

White      TN3270E Management Information Base (TN3270E-MIB)    20 November 1997
    MAX-ACCESS   read-only
    STATUS   current
    DESCRIPTION
        "The number of bytes sent to TCP for this connection."
    ::= { tn3270eTcpConnEntry 9 }

tn3270eTcpConnResourceElement OBJECT-TYPE
    SYNTAX   SnaResourceName
    MAX-ACCESS   read-only
    STATUS   current
    DESCRIPTION
        "LU/Print secondary name for connecting an client
         into an SNA network."
   ::= { tn3270eTcpConnEntry 10 }

tn3270eTcpConnResourceType OBJECT-TYPE
    SYNTAX   Tn3270ResourceType
    MAX-ACCESS   read-only
    STATUS   current
    DESCRIPTION
        "Indicates the type of resource identified by
         tn3270eTcpConnResourceElement."
   ::= { tn3270eTcpConnEntry 11 }

tn3270eTcpConnDeviceType OBJECT-TYPE
   SYNTAX   Tn3270DeviceTypes
   MAX-ACCESS   read-only
   STATUS   current
   DESCRIPTION
       "Indicates the device type if negotiated with the
       client.
          This  A value of unknown(0) should be used as the
       value of this object when a device type is also known as logmode." not
       negotiated.  Refer to RFC 1647 for how device types
       can be negotiated."
   ::= { tn3270eTcpConnEntry 12 }

tn3270eTcpConnFunctions OBJECT-TYPE
   SYNTAX   Tn3270Functions   IANATn3270Functions
   MAX-ACCESS   read-only
   STATUS   current
   DESCRIPTION
       "This object will indicates which of the TN3270 and TN3270E
       functions that are supported were negotiated by the server was negioted
          with a client. and the client
       for this TCP connection.

       Refer to tn3270eSrvrFunctionsSupported." tn3270eSrvrFunctionsSupported for the list of
       these functions supported by the server."
   ::= { tn3270eTcpConnEntry 13 }

tn3270eTcpConnId OBJECT-TYPE
    SYNTAX      Unsigned32
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION

Expires May 1998                                               [Page 34]~

White      TN3270E Management Information Base (TN3270E-MIB)    20 November 1997
        "The connection identifier associated with a TN3270 or
         a TN3270E session's TCP connection." connection.  TCP implementations
         often assign a unique (with respect to itself) unsigned
         integer as an identifier for a TCP connection.
         Implementations that do not support assignment of
         unsigned integer connection identifiers should not
         support this object."
    ::= { tn3270eTcpConnEntry 14 }

tn3270eTcpConnClientIdFormat OBJECT-TYPE
    SYNTAX      INTEGER {
                            unknown(0)
                          }      IANATn3270eClientType
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "The format of the a corresponding tn3270eTcpConnClientId
           object:

              ENUMERATION    OCTETs  DESCRIPTION
              unknown(0)       0"
         object as defined by the IANSTn3270eClientType
         textual convention imported from the
         IANATn3270eTC-MIB."
    ::= { tn3270eTcpConnEntry 15 }

tn3270eTcpConnClientId OBJECT-TYPE
    SYNTAX      OCTET STRING (SIZE (0..512))
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
        "Additional client identification information.  The
        type of this information whose
           content is defined indicated by the corresponding value of
           tn3270eTcpConnClientIdFormat."
      ::= { tn3270eTcpConnEntry 16 }

  tn3270eTcpConnMiscInfoFormat OBJECT-TYPE
      SYNTAX    BITS {
                      none(0),
                      unknown(1),
                      proxyIpv4(2),
                      proxyIpv6(3)
                     }
      MAX-ACCESS  read-only
      STATUS      current
      DESCRIPTION
         "This object defines
        the content of a corresponding
          tn3270eTcpConnMiscInfo tn3270eTcpConnClientIdFormat object. This

        The purpose of this object is defined
          using the BITS SYNTAX in order to enable the presents
          of multiple elements. The order of occurance provide an alternate
        means of the
          selected elements in identifying a tn3270eTcpConnMiscInfo must
          follow the precedence of the associating BIT definition
          with client, other than though the exception of unknown(1) which must be last
          if selected:

Expires May 1998                                               [Page 35]~

White      TN3270E Management Information Base (TN3270E-MIB)    20 November 1997

          ENUMERATION OCTETs DESCRIPTION
          none(0)       0
          unknown(1)  0..512 A variable length generic field.
          proxyIpv4(2)  4    The actual client is connected
                             via a proxy client whose
        remote address
                             is stored returned in tn3270eTcpConnClientId.
          proxyIpv6(3) tn3270eTcpConnRemAddress."
    ::= { tn3270eTcpConnEntry 16    The actual client is connected
                             via a proxy client whose address
                             is stored in tn3270eTcpConnClientId.

          For example, selection of unknown(1), proxyIpv4(2) and
          proxyIpv6(3) would result in the corresponding
          tn3270eTcpConnMiscInfo containing a proxyIpv6 value
          followed by a proxyIpv4 value and ended with a variable
          length unknown value." }

tn3270eTcpConnTraceData OBJECT-TYPE
    SYNTAX   Tn3270eTraceData
    MAX-ACCESS   read-only
    STATUS   current
    DESCRIPTION
        "Trace data for this session."
    ::= { tn3270eTcpConnEntry 17 }

  tn3270eTcpConnMiscInfo

tn3270eTcpConnLogInfo OBJECT-TYPE
    SYNTAX      OCTET STRING (SIZE (0..512))      IANATn3270eLogData
    MAX-ACCESS  read-only
    STATUS      current
    DESCRIPTION
          "Additional client information. The contents of this
           object is defined by
        "Log information, encoded as specified in the corresponding object
           tn3270eTcpConnMiscInfoFormat."
        IANATn3270eLogData textual convention from the
        IANAtn3270eTC-MIB."
    ::= { tn3270eTcpConnEntry 18 }

tn3270eTcpConnLuLuBindImage  OBJECT-TYPE
    SYNTAX   OCTET STRING (SIZE (0..256))
    MAX-ACCESS   read-only
    STATUS   current
    DESCRIPTION
        "When there is a currently active LU-LU session for
        this connection, this object returns the BIND Image
        (defined to be bytes 1-p of the complete BIND Request
        Unit) that was received from the PLU during session
        activation.  When there is no active LU-LU session,
        or when a BIND image is unavailable for some other
        reason, this object returns the empty a zero-length octet string."
   ::= { tn3270eTcpConnEntry 19 }

tn3270eTcpConnSnaState  OBJECT-TYPE
    SYNTAX   INTEGER {
                  unknown(0),
                  noSluSession(1),
                  sscpLuSession(2),  -- but no LU-LU session
                    luLuSession(3)
                  luLuSession(3),
                  establishingSscpLuSession(4),
                  establishingLuSession(5)
                     }

Expires May 1998                                               [Page 36]~

White      TN3270E Management Information Base (TN3270E-MIB)    20 November 1997
    MAX-ACCESS   read-only
    STATUS   current
    DESCRIPTION
        "The current state of the SNA side of the end-to-end
        TN3270 connection.  The following states are defined:

        unknown(0)          - The true state is not known.
        noSluSession(1)     - The SLU has neither an SSCP-LU
                              nor an LU-LU session active.
        sscpLuSession(2)    - The SSCP-LU session for the SLU
                              is active, but the SLU is not
                              currently in session with a PLU.
        luLuSession(3)      - The SLU currently has an active
                              session with a PLU." PLU.
        establishingSscpLuSession(4) - Currently, disconnected
                              and in the process of establishing
                              an SSCP to LU session.
        establishingLuSession(5) - Currently, disconnected
                              and in the process of establishing
                              an LU to LU session."
   ::= { tn3270eTcpConnEntry 20 }

  -- Conformance Definitions

  tn3270eGroups      OBJECT IDENTIFIER ::= { tn3270eConformance 1 }
  tn3270eCompliances OBJECT IDENTIFIER ::=

tn3270eTcpConnStateLastDiscReason OBJECT-TYPE
    SYNTAX   INTEGER { tn3270eConformance 2
                  unknown(0),
                  hostSendsUnbind(1),
                  hostDontAcceptConnection(2),
                  outOfResource(3),
                  clientProtocolError(4),
                  invalidDeviceName(5),
                  deviceInUse(6),
                  inactivityTimeout(7),
                  hostNotResponding(8),
                  clientNotResponding(9),
                  tcpClose(10),
                  serverClose(11),
                  sysreqLogoff(12),
                  serverSpecificHexCode(13)
                     }

  -- compliance statements

  tn3270eCompliance MODULE-COMPLIANCE
    MAX-ACCESS   read-only
    STATUS   current
    DESCRIPTION
        "The compliance statement for agents last disconnect reason.  Note: that support the
          TN3270E-MIB."
      MODULE -- a session
        that has not experienced a disconnect would use
        a value of unknown(0) for this module
          MANDATORY-GROUPS object."
   ::= { tn3270eTcpConnEntry 21 }

tn3270eTcpConnSrvrConfIndex OBJECT-TYPE
    SYNTAX   Unsigned32 (1..4294967295)
    MAX-ACCESS   read-only
    STATUS   current
    DESCRIPTION
        "tn3270eSrvrConfIndex of the tn3270eSrvrConfEntry
        belonging to the TN3270E server to whom this entry
        belongs."
   ::= { tn3270eTcpConnEntry 22 }

tn3270eConfSpinLock OBJECT-TYPE
    SYNTAX      TestAndIncr
    MAX-ACCESS  read-write
    STATUS      current
    DESCRIPTION
       "An advisory lock used to allow cooperating
       TN3270E-MIB applications to coordinate their
       use of the tn3270eSrvrConfTable, the
       tn3270eSrvrPortTable, the tn3270eClientGroupTable,
       the tn3270eResPoolTable, and the
       tn3270eClientResMapTable.

       When an application seeks to create a new entry or
       alter an existing entry in any of the above mentioned
       tables, an implementation MAY require the application
       to use the tn3270eConfSpinLock to serialize its changes
       or additions relative to those initiated by other
       applications.  Since this is an advisory lock, an
       implementation is not required to support it."
    ::= { tn3270eObjects 10 }

-- Conformance Definitions

tn3270eGroups      OBJECT IDENTIFIER ::= { tn3270eConformance 1 }

tn3270eCompliances OBJECT IDENTIFIER ::= { tn3270eConformance 2 }

-- compliance statements

tn3270eCompliance MODULE-COMPLIANCE
    STATUS  current
    DESCRIPTION
        "The compliance statement for agents that support the
        TN3270E-MIB."
    MODULE -- this module
        MANDATORY-GROUPS { tn3270eBasicGroup,
                           tn3270eSessionGroup
                         }
        GROUP       tn3270eResMapGroup
        DESCRIPTION
            "This group is optional and provides a method of
            performing tn3270eClientGroup to tn3270eResPool
            mapping."

        GROUP       tn3270eHiCapacityGroup
        DESCRIPTION
            "This group is optional and provides for support
            of high capacity counters."

        OBJECT tn3270eSrvrConfActivityCheck
           MIN-ACCESS  read-only
           DESCRIPTION
              "The agent is not required to support a set to this
               object if the associating associated TN3270E server doesn't
               support either TIMEMARK or NOP processing.  In
               this case an agent should return noCheck on
               retrieval."

        OBJECT tn3270eSrvrConfActivityTimeout
           MIN-ACCESS  read-only
           DESCRIPTION

Expires May 1998                                               [Page 37]~

White      TN3270E Management Information Base (TN3270E-MIB)    20 November 1997
              "The agent is not required to support a set to this
               object if the functions enabled by
               tn3270eSrvrConfActivityCheck are not supported.
               An agent in this case should return a value of 0."

        OBJECT tn3270eSrvrConfActivityInterval
           MIN-ACCESS  read-only
           DESCRIPTION
              "The agent is not required to support a set to this
               object if the functions enabled by
               tn3270eSrvrConfActivityCheck are not supported.
               An agent in this case should return a value of 0."

       OBJECT  tn3270eSrvrConfAdminStatus
           DESCRIPTION
              "A TN3270E server is not required to support a
               stopImmediate state transition."
      ::=

        OBJECT tn3270eSrvrConfRowStatus
           SYNTAX   INTEGER { tn3270eCompliances 1 }
                             active(1) -- units subset of conformance

  tn3270eBasicGroup OBJECT-GROUP
      OBJECTS {
          tn3270eSrvrConfInactivityTimeout,
          tn3270eSrvrConfActivityCheck,
          tn3270eSrvrConfActivityTimeout,
          tn3270eSrvrConfActivityInterval,
          tn3270eSrvrFunctionsSupported,
          tn3270eSrvrConfAdminStatus,
          tn3270eSrvrConfOperStatus,
          tn3270eSrvrConfSessionTermState,
          tn3270eSrvrConfSrvrType,
          tn3270eSrvrConfContact,
          tn3270eSrvrConfRowStatus,
          tn3270eSrvrPortRowStatus,
          tn3270eSrvrStatsUpTime,
          tn3270eSrvrStatsMaxLus,
          tn3270eSrvrStatsLusInUse,
          tn3270eSrvrStatsSpareLus,
          tn3270eSrvrStatsMaxPtrs,
          tn3270eSrvrStatsPtrsInUse,
          tn3270eSrvrStatsSparePtrs,
          tn3270eSrvrStatsConnectsIn,
          tn3270eSrvrStatsConnRejects,
          tn3270eSrvrStatsDisconnects,
          tn3270eSrvrStatsOctetsIn,
          tn3270eSrvrStatsOctetsInLow,
          tn3270eSrvrStatsOctetsOut,
          tn3270eSrvrStatsOctetsOutLow,
          tn3270eClientGroupSubnetMask,

Expires May 1998                                               [Page 38]~

White      TN3270E Management Information Base (TN3270E-MIB)    20 November 1997

          tn3270eClientGroupPfxLength,
          tn3270eClientGroupRowStatus,
          tn3270eSnaMapLocalName,
          tn3270eSnaMapPrimaryLuName RowStatus
                            }
      STATUS  current
           MIN-ACCESS read-only
           DESCRIPTION
          "This group
               "Write access is mandatory not required, and only one
               of the six enumerated values for all hosts supporting the
           TN3270E-MIB."
      ::= { tn3270eGroups 1 }

  tn3270eSessionGroup OBJECT-GROUP
      OBJECTS
               RowStatus textual convention need be
               supported, specifically: active(1)."

        OBJECT tn3270eSrvrPortRowStatus
           SYNTAX   INTEGER {
          tn3270eResMapAddrType,
          tn3270eResMapAddress,
          tn3270eResMapPort,
          tn3270eResMapElementType,
          tn3270eResMapSscpSuppliedName,
          tn3270eTcpConnLastActivity,
          tn3270eTcpConnBytesIn,
          tn3270eTcpConnBytesOut,
          tn3270eTcpConnResourceElement,
          tn3270eTcpConnResourceType,
          tn3270eTcpConnDeviceType,
          tn3270eTcpConnFunctions
                             active(1) -- subset of RowStatus
                            }
      STATUS  current
           MIN-ACCESS read-only
           DESCRIPTION
               "Write access is not required, and only one
               of the six enumerated values for the
               RowStatus textual convention need be
               supported, specifically: active(1)."

        OBJECT tn3270eClientGroupRowStatus
           SYNTAX   INTEGER {
                             active(1) -- subset of RowStatus
                            }
           MIN-ACCESS read-only
           DESCRIPTION
               "Write access is not required, and only one
               of the six enumerated values for the
               RowStatus textual convention need be
               supported, specifically: active(1)."

        OBJECT tn3270eResPoolRowStatus
           SYNTAX   INTEGER {
                             active(1) -- subset of RowStatus
                            }
           MIN-ACCESS read-only
           DESCRIPTION
               "Write access is not required, and only one
               of the six enumerated values for the
               RowStatus textual convention need be
               supported, specifically: active(1)."

        OBJECT tn3270eClientResMapRowStatus
           SYNTAX   INTEGER {
                             active(1) -- subset of RowStatus
                            }
           MIN-ACCESS read-only
           DESCRIPTION
               "Write access is not required, and only one
               of the six enumerated values for the
               RowStatus textual convention need be
               supported, specifically: active(1)."

        OBJECT tn3270eTcpConnId
           MIN-ACCESS  not-accessible
           DESCRIPTION
               "This object is not required of implementations
               that do not support assignment of unsigned
               integer connection identifiers."

        OBJECT tn3270eConfSpinLock
           MIN-ACCESS  not-accessible
           DESCRIPTION
               "The use and support of this object is optional."

    ::= { tn3270eCompliances 1 }

-- units of conformance

tn3270eBasicGroup OBJECT-GROUP
    OBJECTS {
        tn3270eSrvrConfInactivityTimeout,
        tn3270eSrvrConfActivityCheck,
        tn3270eSrvrConfActivityTimeout,
        tn3270eSrvrConfActivityInterval,
        tn3270eSrvrFunctionsSupported,
        tn3270eSrvrConfAdminStatus,
        tn3270eSrvrConfOperStatus,
        tn3270eSrvrConfSessionTermState,
        tn3270eSrvrConfSrvrType,
        tn3270eSrvrConfContact,
        tn3270eSrvrConfRowStatus,
        tn3270eSrvrPortRowStatus,
        tn3270eSrvrStatsUpTime,
        tn3270eSrvrStatsMaxLus,
        tn3270eSrvrStatsInUseLus,
        tn3270eSrvrStatsSpareLus,
        tn3270eSrvrStatsMaxPtrs,
        tn3270eSrvrStatsInUsePtrs,
        tn3270eSrvrStatsSparePtrs,
        tn3270eSrvrStatsInConnects,
        tn3270eSrvrStatsConnRejects,
        tn3270eSrvrStatsDisconnects,
        tn3270eSrvrStatsInOctets,
        tn3270eSrvrStatsOutOctets,
        tn3270eClientGroupSubnetMask,
        tn3270eClientGroupPfxLength,
        tn3270eClientGroupRowStatus,
        tn3270eSnaMapLocalName,
        tn3270eSnaMapPrimaryLuName,
        tn3270eConfSpinLock
    }
    STATUS  current
    DESCRIPTION
        "This group is mandatory for all hosts supporting the
         TN3270E-MIB."
    ::= { tn3270eGroups 1 }

tn3270eSessionGroup OBJECT-GROUP
    OBJECTS {
        tn3270eResMapAddrType,
        tn3270eResMapAddress,
        tn3270eResMapPort,
        tn3270eResMapElementType,
        tn3270eResMapSscpSuppliedName,
        tn3270eTcpConnLastActivity,
        tn3270eTcpConnBytesIn,
        tn3270eTcpConnBytesOut,
        tn3270eTcpConnResourceElement,
        tn3270eTcpConnResourceType,
        tn3270eTcpConnDeviceType,
        tn3270eTcpConnFunctions,
        tn3270eTcpConnSrvrConfIndex
      }
    STATUS  current
    DESCRIPTION
        "This group is mandatory for all hosts supporting the
         TN3270E-MIB."
    ::= { tn3270eGroups 2 }

tn3270eResMapGroup OBJECT-GROUP
    OBJECTS {
        tn3270eResPoolElementType,
        tn3270eResPoolRowStatus,
        tn3270eClientResMapRowStatus,
        tn3270eTcpConnId,
        tn3270eTcpConnClientIdFormat,
        tn3270eTcpConnClientId,
          tn3270eTcpConnMiscInfoFormat,
          tn3270eTcpConnMiscInfo,
        tn3270eTcpConnTraceData,
        tn3270eTcpConnLogInfo,
        tn3270eTcpConnLuLuBindImage,
          tn3270eTcpConnSnaState
        tn3270eTcpConnSnaState,
        tn3270eTcpConnStateLastDiscReason
      }
    STATUS  current
    DESCRIPTION
        "This group is optional for all hosts supporting the

Expires May 1998                                               [Page 39]~

White      TN3270E Management Information Base (TN3270E-MIB)    20 November 1997
         TN3270E-MIB."
    ::= { tn3270eGroups 3 }

  END

5.  Security Considerations

  Certain management information defined in this MIB may be considered
  sensitive in some network environments.  Therefore, authentication of
  received SNMP requests and controlled access to management information
  should be employed in such

tn3270eHiCapacityGroup OBJECT-GROUP
    OBJECTS {
        tn3270eSrvrStatsHCInOctets,
        tn3270eSrvrStatsHCOutOctets
      }
    STATUS  current
    DESCRIPTION
        "This group is optional for all hosts supporting the
         TN3270E-MIB.  Its contents is a list of Counter64
         objects.  An implementation that doesn't support
         these objects should return noSuchObject.
         Returning a zero is misleading.  Support of these
         objects is recommended when the Counter32 versions
         can potentially wrap too frequently.

         The IF-MIB (RFC 2233) requires that the 64 bit
         versions of its counters be implemented when an
         interface can support rates around 20 million bits
         per second or greater.  This implies a minimum wrap
         rate of just over 28 minutes.  It is recommended that
         this guidance be used for determining when an
         implementation should implement these objects."
    ::= { tn3270eGroups 4 }

END

5.0  Security Considerations

Certain management information defined in this MIB may be considered
sensitive in some network environments.  Therefore, authentication of
received SNMP requests and controlled access to management information
SHOULD be employed in such environments.  The method for this
authentication is a function of the SNMP Administrative Framework, and
has not been expanded by this MIB.

Several objects in this MIB allow write access or provide for remote row
creation.  Allowing this support in a non-secure environment can have a
negative effect on network operations.  It is recommended RECOMMENDED that
implementers seriously consider whether set operations or row creation
should be allowed without providing, at a minimum, authentication of
request origin.  It it recommended is RECOMMENDED that without such support that support, the
following objects be implemented as read-only:

o   tn3270eSrvrConfInactivityTimout
o   tn3270eSrvrConfActivityCheck
o   tn3270eSrvrConfActivityTimeout
o   tn3270eSrvrConfActivityInterval
o   tn3270eSrvrConfAdminStatus
o   tn3270eSrvrConfSessionTermState

o   tn3270eSrvrConfContact
o   tn3270eClientGroupSubnetMask
o   tn3270eResPoolElementType

  The following objects should either be implemented as read-only or not
  implemented when security is an issue as previously discussed:
o   tn3270eSrvrConfRowStatus
o   tn3270eSrvrPortRowStatus
o   tn3270eClientGroupRowStatus
o   tn3270eResPoolRowStatus
o   tn3270eResMapRowStatus

6.  Acknowledgments

  This document is a product

6.0  Intellectual Property

The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to pertain
to the TN3270E Working Group.

Expires May 1998                                               [Page 40]~

White      TN3270E Management implementation or use of the technology described in this
document or the extent to which any license under such rights might or
might not be available; neither does it represent that it has made any
effort to identify any such rights.  Information Base (TN3270E-MIB)    20 November 1997

7.  References

[1]  SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., on the IETF's
procedures with respect to rights in standards-track and
     Waldbusser S., "Structure
standards-related documentation can be found in BCP-11.  Copies of Management Information
claims of rights made available for version 2 publication and any assurances of
licenses to be made available, or the Simple Network Management Protocol (SNMPv2)", RFC 1902,
     January 1996.

[2]  Network result of an attempt made to
obtain a general license or permission for the use of such proprietary
rights by implementers or users of this specification can be obtained
from the IETF Secretariat.

The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary rights
which may cover technology that may be required to practice this
standard.  Please address the information to the IETF Executive
Director.

7.0  Acknowledgments

This document is a product of the TN3270E Working Group, Group.

8.0  References

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

[2]  Postel, J., and Reynolds, J., "Telnet Protocol Specification", RFC
     854, May 1983.

[3]  Network Working Group,  Postel, J., and Reynolds, J., "Telnet Timing Mark Option", RFC 860,
     May 1983.

[4]  Network Working Group and Rekhter  Rekhter, J., "Telnet 3270 Regime Option", RFC 1041, January 1988.

[5]  Case, J., McCloghrie, K., and M. Rose, Editors, "Management Information Base M., and Waldbusser, S., "Transport
     Mappings for Version 2 of the Simple Network Management of TCP/IP-based internets: MIB-II", STD 17, Protocol
     (SNMPv2)", RFC 1213, Hughes LAN Systems, Performance Systems International,
     March 1991. 1906, January 1996.

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

[7]  SNMPv2 Working Group,  Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, S., "Protocol
     Operations for version Version 2 of the Simple Network Management Protocol
     (SNMPv2)", RFC 1905, January 1996.

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

[9]  Case, J., M. Fedor, M. Schoffstall, J. Davin, "Simple McCloghrie, K., Rose, M., and Waldbusser, S., "Management
     Information Base for Version 2 of the Simple Network Management Protocol",
     Protocol (SNMPv2)", RFC 1157, SNMP Research, Performance Systems
     International, MIT Laboratory for Computer Science, May 1990. 1907, January 1996.

[10] IETF SNMPv2 Working Group and McCloghrie, K., "TCP-MIB

Expires May 1998                                               [Page 41]~

White      TN3270E Management Information Base (TN3270E-MIB)    20 November 1997 Definitions", November 1994.

[11] Hinden, R., Deering, S., "IP Version 6 Addressing Architecture",
     <draft-ietf-ipngwg-addr-arch-v2-02.txt>, July 16, 1997 1997.

[12] Krupczak, Cheryl, Saperia, Jonathan, "Definitions of System-Level
     Managed Objects for Applications", April 15, 1997.

8.

[13] Bradner, S., "Key words for use in RFCs to Indicate Requirement
     Levels", BCP 14, RFC 2119, March 1997.

[14] Kelly, B., "TN3270 Enhancements", RFC 1647, July 1994.

[15] Harrington, D., Presuhn, R., Wijnen, B., "An Architecture for
     Describing SNMP Management Frameworks", RFC 2271, January 1998.

[16] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S.,
     "Coexistence between Version 1 and Version 2 of the
     Internet-standard Network Management Framework", RFC 1908, January
     1996.

9.0  Authors' Address Addresses

  Kenneth D. White
  Dept. G80/Bldg 501 BRQA/Bldg. 501/G114
  IBM Corporation
  P.O.Box 12195
  3039 Cornwallis
  Research Triangle Park, NC 27709, USA
  Phone: +1-919-254-0102
  E-mail: kennethw@vnet.ibm.com

Expires May 1998                                               [Page 42]~

  Robert Moore
  Dept. BRQA/Bldg. 501/G114
  IBM Corporation
  P.O.Box 12195
  3039 Cornwallis
  Research Triangle Park, NC 27709, USA
  Phone: +1-919-254-7507
  E-mail: remoore@us.ibm.com

10.0  Full Copyright Statement

Copyright (C) The Internet Society (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.

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.

Appendix A.  IANATn3270eTC-MIB

This appendix defines the current content of the IANATn3270eTC-MIB.
This section should be removed from this document prior to its approval,
at which time this MIB will be administered by IANA.  IANATn3270eTC-MIB
DEFINITIONS ::= BEGIN

IMPORTS
    MODULE-IDENTITY, experimental
        FROM SNMPv2-SMI
    TEXTUAL-CONVENTION
        FROM SNMPv2-TC;

  ianaTn3270eTcMib MODULE-IDENTITY
      LAST-UPDATED "9802020000Z" -- February 2, 1998
      ORGANIZATION "IANA"
      CONTACT-INFO
          "Internet Assigned Numbers Authority

           Postal: USC/Information Sciences Institute
                   4676 Admiralty Way, Marina del Rey, CA 90292

           Tel:    +1  310 822 1511
           E-Mail: iana@isi.edu"
      DESCRIPTION
          "This module defines a set of textual conventions
          for use by the TN3270E-MIB and the TN3270E-RT-MIB.

          Any additions or changes to the contents of this
          MIB module must first be discussed on the tn3270e
          working group list at: tn3270e@list.nih.gov
          and approved by one of the following TN3270E
          working group contacts:

              Ed Bailey (co-chair) - elbailey@us.ibm.com
              Michael Boe (co-chair) - mboe@cisco.com
              Ken White - kennethw@vnet.ibm.com
              Robert Moore - remoore@us.ibm.com

          The above list of contacts can be altered with
          the approval of the two co-chairs.

          The Textual Conventions defined within this MIB have
          no security issues associated with them unless
          explicitly stated in their corresponding
          DESCRIPTION clause."
      -- Need a real OID assigned
      ::= { experimental 2001 }

IANATn3270Functions ::= TEXTUAL-CONVENTION
    STATUS      current
    DESCRIPTION
        "This textual convention reflects the current set of
        TN3270 and TN3270E functions that can be negotiated
        between a server and its client:

        RFC856
        transmitBinary   The sender of this command REQUESTS
                         permission to begin transmitting, or
                         confirms that it will now begin
                         transmitting characters which are to
                         be interpreted as 8 bits of binary
                         data by the receiver of the data.
        RFC820
        timeMark         The sender of this command REQUESTS
                         that the receiver of this command
                         return a WILL TIMING-MARK in the data
                         stream at the 'appropriate place' ...
        RFC885
        endOfRecord      The sender of this command requests
                         permission to begin transmission of
                         the Telnet END-OF-RECORD (EOR) code
                         when transmitting data characters, or
                         the sender of this command confirms it
                         will now begin transmission of EORs
                         with transmitted data characters.
        RFC1091
        terminalType     Sender is willing to send terminal
                         type information in a subsequent
                         sub-negotiation.
        RFC1041
        tn3270Regime     Sender is willing to send list of
                         supported 3270 Regimes in a
                         subsequent sub-negotiation.
        RFC1647
        scsCtlCodes     (Printer sessions only).  Allows the
                        use of the SNA Character Stream (SCS)
                        and SCS control codes on the session.
                        SCS is used with LU type 1 SNA sessions.
        dataStreamCtl   (Printer sessions only).  Allows the use
                        of the standard 3270 data stream.  This
                        corresponds to LU type 3 SNA sessions.
        responses       Provides support for positive and
                        negative response handling.  Allows the
                        server to reflect to the client any and
                        all definite, exception, and no response
                        requests sent by the host application.
        bindImage       Allows the server to send the SNA Bind
                        image and Unbind notification to the
                        client.
        sysreq          Allows the client and server to emulate
                        some (or all, depending on the server) of
                        the functions of the SYSREQ key in an SNA
                        environment."
    SYNTAX      BITS {
                       transmitBinary(0),-- rfc856
                       timemark(1),      -- rfc860
                       endOfRecord(2),   -- rfc885
                       terminalType(3),  -- rfc1091
                       tn3270Regime(4),  -- rfc1041
                       scsCtlCodes(5),   -- rfc1647
                       dataStreamCtl(6), -- rfc1647
                       responses(7),     -- rfc1647
                       bindImage(8),     -- rfc1647
                       sysreq(9)         -- rfc1647
                     }

IANATn3270eClientType ::= TEXTUAL-CONVENTION
    STATUS      current
    DESCRIPTION
        "The textual convention for defining the set of
         enumerations used by tn3270eTcpConnClientIdFormat
         in the TN3270E-MIB:

         ENUMERATION        OCTETs  DESCRIPTION

         none(0)              0     Not specified
         other(1)           1..512  Implementation specific
         ipv4(2)              6     4-octet IP Address plus
                                    2-octet TCP Port
         ipv6(3)              18    16-octet IPv6 Address
                                    plus 2-octet TCP Port
         domainName(4)      1..512  The DNS name of a
                                    client.
         truncDomainName(5) 1..512  The truncated DNS name
                                    of a client.
         string(6)          1..512  Unknown Utf8String
         certificate(7)     1..512  certificate
         userId(8)          1..8    Client's userid
         x509dn(9)          1..512  X.509 Distinguished Name

         Representation of a certificate(7) may be lead to
         a security exposure and is NOT RECOMMENDED without
         adequate security."
    SYNTAX     INTEGER {
                          none(0),
                          other(1),
                          ipv4(2),
                          ipv6(3),
                          domainName(4),
                          truncDomainName(5),
                          string(6),
                          certificate(7),
                          userId(8),
                          x509dn(9)
                        }

IANATn3270eLogData ::= TEXTUAL-CONVENTION
   STATUS current
   DESCRIPTION
      "An octet string representing log data as pertaining to
      either a TN3270 or TN3270E Session as reported from a
      TN3270E Server. Log data is stored in an octet string
      in time order (from earliest to latest).

      Each log element has the following form:

      +------+----+---------+------------+
      !length!type!TimeStamp! data       !
      +------+----+---------+------------+

      where

      length    = one-octet length of the data portion of the
                  trace element, not including the length,
                  type, and TimeStamp fields
      type      = one-octet code point characterizing the data.
      TimeStamp = A 4 octet field that follows the TimeStamp
                  (TimeTicks) textual convention as defined
                  by RFC 1903.
      data      = initial part of a PDU.

      length   type

        0-250  x'00' - unknown
        0      x'01' - inactivity timer expired
        0      x'02' - dynamic timer expired
        0      x'03' - actlu req
        0      x'04' - bind req
        0      x'05' - clear req
        0      x'06' - dactlu req
        0      x'07' - warm actpu req
        0      x'08' - sdt req
        0      x'09' - unbind req
        0      x'0A' - notify resp
        0      x'0B' - reply PSID neg rsp
        0      x'0C' - reply PSID pos rsp
        0      x'0D' - unbind rsp
        0      x'0E' - hierarchical reset
        0      x'0F' - client connect req
        0      x'10' - client disconnect req
        0      x'11' - timingmark received
        0      x'12' - flowControl timer expired
        0      x'13' - neg rsp to host
        0      x'14' - neg rsp from host
        0      x'15' - data contention
        0      x'16' - no buffer to send SNA data
        0      x'17' - receive response while inbound
        0      x'18' - client protocol error
        0      x'19' - badClientSequenceReceived
        1-250  x'1A' - utf8String
        2      x'1B' - hexCode, implementation dependent

        log event entries have a minimum length of 6 octets.
        The zero-length string indicates that no log data is
        available."
   SYNTAX OCTET STRING (SIZE (0..256))

END