draft-ietf-tn3270e-tn3270-mib-10.txt   rfc2561.txt 
TN3270E Working Group Kenneth White Network Working Group K. White
INTERNET DRAFT: <draft-ietf-tn3270e-tn3270-mib-10.txt> IBM Corp. Request for Comments: 2561 IBM Corp.
Expiration Date: January, 1999 Robert Moore Category: Standards Track R. Moore
IBM Corp. IBM Corp.
July 1998 April 1999
Base Definitions of Managed Objects for Base Definitions of Managed Objects for
TN3270E Using SMIv2 TN3270E Using SMIv2
<draft-ietf-tn3270e-tn3270-mib-10.txt>
Status of this Memo Status of this Memo
This document is an Internet Draft. Internet Drafts are working This document specifies an Internet standards track protocol for the
documents of the Internet Engineering Task Force (IETF), its Areas, and Internet community, and requests discussion and suggestions for
its Working Groups. Note that other groups may also distribute working improvements. Please refer to the current edition of the "Internet
documents as Internet Drafts. Official Protocol Standards" (STD 1) for the standardization state
and status of this protocol. Distribution of this memo is unlimited.
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.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (1998). All Rights Reserved. Copyright (C) The Internet Society (1999). All Rights Reserved.
Abstract Abstract
This memo defines a Management Information Base (MIB) for configuring This memo defines a Management Information Base (MIB) for configuring
and managing TN3270E servers. TN3270E, defined by RFC 2355 [19], refers and managing TN3270E servers. TN3270E, defined by RFC 2355 [19],
to the enhancements made to the Telnet 3270 (TN3270) terminal emulation refers to the enhancements made to the Telnet 3270 (TN3270) terminal
practices. Refer to RFC 1041 [18], RFC 854 [16], and RFC 860 [17] for a emulation practices. Refer to RFC 1041 [18], STD 8, RFC 854 [16],
sample of what is meant by TN3270 practices. and STD 31, RFC 860 [17] for a sample of what is meant by TN3270
practices.
The MIB defined by this memo provides generic support for both host and The MIB defined by this memo provides generic support for both host
gateway TN3270E server implementations. A TN3270E server connects a and gateway TN3270E server implementations. A TN3270E server
Telnet client performing 3270 emulation to a target SNA host over both a connects a Telnet client performing 3270 emulation to a target SNA
client-side network (client to TN3270E server) and an SNA Network host over both a client-side network (client to TN3270E server) and
(TN3270E server to target SNA host). The client-side network is an SNA Network (TN3270E server to target SNA host). The client-side
typically TCP/IP, but it need not be. network is typically TCP/IP, but it need not be.
A host TN3270E server refers to an implementation where the TN3270E A host TN3270E server refers to an implementation where the TN3270E
server is collocated with the Systems Network Architecture (SNA) System server is collocated with the Systems Network Architecture (SNA)
Services Control Point (SSCP) for the dependent Secondary Logical Units System Services Control Point (SSCP) for the dependent Secondary
(SLUs) that the server makes available to its clients for connecting Logical Units (SLUs) that the server makes available to its clients
into a SNA network. A gateway TN3270E server resides on an SNA node for connecting into a SNA network. A gateway TN3270E server resides
other than an SSCP, either an SNA type 2.0 node, a on an SNA node other than an SSCP, either an SNA type 2.0 node, a
boundary-function-attached type 2.1 node, or an APPN node acting in the boundary-function-attached type 2.1 node, or an APPN node acting in
role of a Dependent LU Requester (DLUR). Host and gateway TN3270E the role of a Dependent LU Requester (DLUR). Host and gateway
server implementations typically differ greatly as to their internal TN3270E server implementations typically differ greatly as to their
implementation and system definition (SYSDEF) methods. internal implementation and system definition (SYSDEF) methods.
It is the intent that the MIB defined herein be extended by subsequent It is the intent that the MIB defined herein be extended by
memos. For example, one such extension enables collection of TN3270E subsequent memos. For example, one such extension enables collection
response time data. of TN3270E response time data.
Table of Contents Table of Contents
1.0 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2 1.0 Introduction . . . . . . . . . . . . . . . . . . . . . . . 2
2.0 The SNMP Network Management Framework . . . . . . . . . . 3
2.0 The SNMP Network Management Framework . . . . . . . . . . . . 3 3.0 Structure of the MIB . . . . . . . . . . . . . . . . . . . 4
3.1 TN3270E Server Control . . . . . . . . . . . . . . . . . . 5
3.0 Structure of the MIB . . . . . . . . . . . . . . . . . . . . . 3 3.1.1 tn3270eSrvrConfTable . . . . . . . . . . . . . . . . . 5
3.1 TN3270E Server Control . . . . . . . . . . . . . . . . . . . . 5 3.1.2 tn3270eSrvrPortTable . . . . . . . . . . . . . . . . . 6
3.1.1 tn3270eSrvrConfTable . . . . . . . . . . . . . . . . . . . 5 3.1.3 tn3270eSrvrStatsTable . . . . . . . . . . . . . . . . 7
3.1.2 tn3270eSrvrPortTable . . . . . . . . . . . . . . . . . . . 6 3.2 TN3270E Server Resource Configuration . . . . . . . . . . 7
3.1.3 tn3270eSrvrStatsTable . . . . . . . . . . . . . . . . . . 6 3.3 Resource Name / Client Address Mappings . . . . . . . . . 8
3.2 TN3270E Server Resource Configuration . . . . . . . . . . . . 6 3.3.1 tn3270eSnaMapTable . . . . . . . . . . . . . . . . . . 8
3.3 Resource Name / Client Address Mappings . . . . . . . . . . . 7 3.3.2 tn3270eResMapTable . . . . . . . . . . . . . . . . . . 9
3.3.1 tn3270eSnaMapTable . . . . . . . . . . . . . . . . . . . . 7 3.3.3 tn3270eTcpConnTable . . . . . . . . . . . . . . . . . 9
3.3.2 tn3270eResMapTable . . . . . . . . . . . . . . . . . . . . 8 3.4 Advisory Spin Lock Usage . . . . . . . . . . . . . . . . . 9
3.3.3 tn3270eTcpConnTable . . . . . . . . . . . . . . . . . . . 8 3.5 Row Persistence . . . . . . . . . . . . . . . . . . . . . 10
3.4 Advisory Spin Lock Usage . . . . . . . . . . . . . . . . . . . 8 3.6 IANA Considerations . . . . . . . . . . . . . . . . . . . 10
3.5 Row Persistence . . . . . . . . . . . . . . . . . . . . . . . 9 4.0 Definitions . . . . . . . . . . . . . . . . . . . . . . . 11
3.6 IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 5.0 Security Considerations . . . . . . . . . . . . . . . . . 51
6.0 Intellectual Property . . . . . . . . . . . . . . . . . . 52
4.0 Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 9 7.0 Acknowledgments . . . . . . . . . . . . . . . . . . . . . 53
8.0 References . . . . . . . . . . . . . . . . . . . . . . . . 53
5.0 Security Considerations . . . . . . . . . . . . . . . . . . . 45 9.0 Authors' Addresses . . . . . . . . . . . . . . . . . . . . 55
Full Copyright Statement . . . . . . . . . . . . . . . . . . . 56
6.0 Intellectual Property . . . . . . . . . . . . . . . . . . . . 46
7.0 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 46
8.0 References . . . . . . . . . . . . . . . . . . . . . . . . . . 46
9.0 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 48
10.0 Full Copyright Statement . . . . . . . . . . . . . . . . . . 48
1.0 Introduction 1.0 Introduction
This document is a product of the TN3270E Working Group. Its purpose is This document is a product of the TN3270E Working Group. Its purpose
to define a MIB module for support by a TCP/IP implementation for is to define a MIB module for support by a TCP/IP implementation for
configuration and management of TN3270E servers. configuration and management of TN3270E servers.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119, reference [22]. document are to be interpreted as described in RFC 2119, reference
[22].
2.0 The SNMP Network Management Framework 2.0 The SNMP Network Management Framework
The SNMP Management Framework presently consists of five major The SNMP Management Framework presently consists of five major
components: components:
o An overall architecture, described in RFC 2271 [1]. o An overall architecture, described in RFC 2271 [1].
o Mechanisms for describing and naming objects and events for the o Mechanisms for describing and naming objects and events for the
purpose of management. The first version of this Structure of purpose of management. The first version of this Structure of
Management Information (SMI) is called SMIv1 and described in RFC Management Information (SMI) is called SMIv1 and described in STD
1155 [2], RFC 1212 [3] and RFC 1215 [4]. The second version, called 16, RFC 1155 [2], STD 16, RFC 1212 [3] and RFC 1215 [4]. The
SMIv2, is described in RFC 1902 [5], RFC 1903 [6] and RFC 1904 [7]. second version, called SMIv2, is described in RFC 1902 [5], RFC
1903 [6] and RFC 1904 [7].
o Message protocols for transferring management information. The o Message protocols for transferring management information. The
first version of the SNMP message protocol is called SNMPv1 and first version of the SNMP message protocol is called SNMPv1 and
described in RFC 1157 [8]. A second version of the SNMP message described in STD 15, RFC 1157 [8]. A second version of the SNMP
protocol, which is not an Internet standards track protocol, is message protocol, which is not an Internet standards track
called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10]. The protocol, is called SNMPv2c and described in RFC 1901 [9] and RFC
third version of the message protocol is called SNMPv3 and described 1906 [10]. The third version of the message protocol is called
in RFC 1906 [10], RFC 2272 [11] and RFC 2274 [12]. SNMPv3 and described in RFC 1906 [10], RFC 2272 [11] and RFC 2274
[12].
o Protocol operations for accessing management information. The first o Protocol operations for accessing management information. The
set of protocol operations and associated PDU formats is described first set of protocol operations and associated PDU formats is
in RFC 1157 [8]. A second set of protocol operations and associated described in STD 15, RFC 1157 [8]. A second set of protocol
PDU formats is described in RFC 1905 [13]. operations and associated PDU formats is described in RFC 1905
[13].
o A set of fundamental applications described in RFC 2273 [14] and the o A set of fundamental applications described in RFC 2273 [14] and
view-based access control mechanism described in RFC 2275 [15]. the view-based access control mechanism described in RFC 2275
[15].
Managed objects are accessed via a virtual information store, termed the Managed objects are accessed via a virtual information store, termed
Management Information Base or MIB. Objects in the MIB are defined the Management Information Base or MIB. Objects in the MIB are
using the mechanisms defined in the SMI. defined using the mechanisms defined in the SMI.
This memo specifies a MIB module that is compliant to the SMIv2. A MIB This memo specifies a MIB module that is compliant to the SMIv2. A
conforming to the SMIv1 can be produced through the appropriate MIB conforming to the SMIv1 can be produced through the appropriate
translations. The resulting translated MIB must be semantically translations. The resulting translated MIB must be semantically
equivalent, except where objects or events are omitted because no equivalent, except where objects or events are omitted because no
translation is possible (use of Counter64). Some machine readable translation is possible (use of Counter64). Some machine readable
information in SMIv2 will be converted into textual descriptions in information in SMIv2 will be converted into textual descriptions in
SMIv1 during the translation process. However, this loss of machine SMIv1 during the translation process. However, this loss of machine
readable information is not considered to change the semantics of the readable information is not considered to change the semantics of the
MIB. MIB.
3.0 Structure of the MIB 3.0 Structure of the MIB
The TN3270E-MIB is split into the following components: The TN3270E-MIB is split into the following components:
o TN3270E Server Control o TN3270E Server Control
o TN3270E Server Resource Configuration o TN3270E Server Resource Configuration
o Resource/Client Address Mappings o Resource/Client Address Mappings
There are three additional sections to address: There are three additional sections to address:
o Advisory Spin Lock Usage o Advisory Spin Lock Usage
o Row Persistence o Row Persistence
o IANA Considerations o IANA Considerations
The TN3270E-MIB is defined primarily for TN3270E servers. This memo 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 does not explicitly address use of the MIB by TN3270 servers that do
support the TN3270E protocol. Even though a significant number of the not support the TN3270E protocol. Even though a significant number
objects in the MIB do apply in the TN3270-only case, the case was not of the objects in the MIB do apply in the TN3270-only case, the case
addressed, since it is unlikely that a TN3270-only server would was not addressed, since it is unlikely that a TN3270-only server
implement this MIB. would implement this MIB.
The SYSAPPL-MIB, reference [24], contains the Utf8String textual The SYSAPPL-MIB, reference [24], contains the Utf8String textual
convention (TC) that the TN3270E-MIB imports. This TC, which is used convention (TC) that the TN3270E-MIB imports. This TC, which is used
for some MIB objects containing textual information, enables for some MIB objects containing textual information, enables
internationalization of text strings, whereas the DisplayString TC does internationalization of text strings, whereas the DisplayString TC
not. The SNMP-FRAMEWORK-MIB, reference [1], contains the does not. The SNMP-FRAMEWORK-MIB, reference [1], contains the
SnmpAdminString TC that the TN3270E-MIB also imports. Like the SnmpAdminString TC that the TN3270E-MIB also imports. Like the
Utf8String TC, this TC also enables internationalization of text Utf8String TC, this TC also enables internationalization of text
strings; in addition, it provides some guidelines on the length and strings; in addition, it provides some guidelines on the length and
content of the strings. content of the strings.
It is important to note that implementation of the SYSAPPL-MIB is 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 actually a prerequisite for implementing the TN3270E-MIB. On the
hand, implementation of the TN3270E-MIB does not preclude implementing other hand, implementation of the TN3270E-MIB does not preclude
the SYSAPPL-MIB as well. When both MIBs are implemented, the primary implementing the SYSAPPL-MIB as well. When both MIBs are
index into most of the TN3270E-MIB tables, tn3270eSrvrConfIndex, SHOULD implemented, the primary index into most of the TN3270E-MIB tables,
equal one of the SYSAPPL-MIB's sysApplElmtRunIndex values. In this case tn3270eSrvrConfIndex, SHOULD equal one of the SYSAPPL-MIB's
the entry in the sysApplElmtRunTable provides additional information on sysApplElmtRunIndex values. In this case the entry in the
a TN3270E server. sysApplElmtRunTable provides additional information on a TN3270E
server.
The MIB defined by this memo supports use of both IPv4 and IPv6 The MIB defined by this memo supports use of both IPv4 and IPv6
addressing. Two textual conventions, IANATn3270eAddrType and addressing. Two textual conventions, IANATn3270eAddrType and
Tn3270eAddress, are defined for this purpose. IANATn3270eAddress is Tn3270eAddress, are defined for this purpose. IANATn3270eAddress is
essentially equivalent to the TAddress TC, defined by RFC 1903. The essentially equivalent to the TAddress TC, defined by RFC 1903. The
difference between the two is that IANATn3270eAddress allows a difference between the two is that IANATn3270eAddress allows a zero-
zero-length octet string, while TAddress doesn't. It is important that length octet string, while TAddress doesn't. It is important that
IANATn3270eAddress allow for the absence of an address, because some IANATn3270eAddress allow for the absence of an address, because some
objects with this syntax are used as table indexes, and have special objects with this syntax are used as table indexes, and have special
meanings when they contain zero-length strings. meanings when they contain zero-length strings.
The IANATn3270eAddrType textual convention is used rather than the The IANATn3270eAddrType textual convention is used rather than the
TDomain TC (defined by RFC 1903) for identifying the contents of a TDomain TC (defined by RFC 1903) for identifying the contents of a
tn3270eTAddress object. TDomain uses an OID to characterize the tn3270eTAddress object. TDomain uses an OID to characterize the
contents of an associated TAddress object. IANATn3270eAddrType was contents of an associated TAddress object. IANATn3270eAddrType was
chosen over TDomain because, with a SYNTAX of Unsigned32 (enumeration chosen over TDomain because, with a SYNTAX of Unsigned32 (enumeration
type), it is much simpler to use as a component in an instance type), it is much simpler to use as a component in an instance
identifier. It was placed in the IANA-administered module to allow for identifier. It was placed in the IANA-administered module to allow
the addition of values to cover cases (such as proxy servers) not for the addition of values to cover cases (such as proxy servers) not
covered by the TN3270E-MIB itself. covered by the TN3270E-MIB itself.
3.1 TN3270E Server Control 3.1 TN3270E Server Control
This group of objects provides for TN3270E server configuration and This group of objects provides for TN3270E server configuration and
control. It consists of three tables: control. It consists of three tables:
o tn3270eSrvrConfTable o tn3270eSrvrConfTable
o tn3270eSrvrPortTable o tn3270eSrvrPortTable
o tn3270eSrvrStatsTable o tn3270eSrvrStatsTable
The tn3270eSrvrConfTable is the primary table within the entire The tn3270eSrvrConfTable is the primary table within the entire
TN3270E-MIB. As section 3.1.1 indicates, each TN3270E server is TN3270E-MIB. As section 3.1.1 indicates, each TN3270E server is
represented by an entry in this table, indexed by tn3270eSrvrConfIndex. represented by an entry in this table, indexed by
Most of the other tables defined by the TN3270E-MIB have tn3270eSrvrConfIndex. Most of the other tables defined by the
tn3270eSrvrConfIndex as their primary index. Entries in these tables TN3270E-MIB have tn3270eSrvrConfIndex as their primary index.
MUST NOT exist for a TN3270E server when it does not have a Entries in these tables MUST NOT exist for a TN3270E server when it
tn3270eSrvrConfigEntry. does not have a tn3270eSrvrConfigEntry.
3.1.1 tn3270eSrvrConfTable 3.1.1 tn3270eSrvrConfTable
The tn3270eSrvrConfTable contains a set of objects primarily used for The tn3270eSrvrConfTable contains a set of objects primarily used for
configuring and managing TN3270E servers. As with most of the other configuring and managing TN3270E servers. As with most of the other
tables in the TN3270E-MIB, this table is indexed by an unsigned integer, tables in the TN3270E-MIB, this table is indexed by an unsigned
tn3270eSrvrConfIndex. This primary index element enables support of integer, tn3270eSrvrConfIndex. This primary index element enables
multiple TN3270E servers by a single SNMP agent. Within the set of MIB support of multiple TN3270E servers by a single SNMP agent. Within
objects returned by one SNMP agent, tn3270eSrvrConfIndex values MUST be the set of MIB objects returned by one SNMP agent,
unique, and need not be contiguous. tn3270eSrvrConfIndex values MUST be unique, and need not be
contiguous.
The tn3270eSrvrConfInactivityTimer object defines the inactivity period The tn3270eSrvrConfInactivityTimer object defines the inactivity
for user traffic on TN3270 and TN3270E sessions. period for user traffic on TN3270 and TN3270E sessions.
The four objects: The four objects:
o tn3270eSrvrConfConnectivityChk o tn3270eSrvrConfConnectivityChk
o tn3270eSrvrConfTmNopInterval o tn3270eSrvrConfTmNopInterval
o tn3270eSrvrConfTmNopInactTime o tn3270eSrvrConfTmNopInactTime
o tn3270eSrvrConfTmTimeout o tn3270eSrvrConfTmTimeout
define the parameters for performing the "Telnet Timing Mark Option" as define the parameters for performing the "Telnet Timing Mark Option"
defined by RFC 860 [17]. The object tn3270eSrvrConfConnectivityChk as defined by RFC 860 [17]. The object
allows a Management Station to select either a NOP command or a tn3270eSrvrConfConnectivityChk allows a Management Station to select
TIMING-MARK command. Sending a NOP command results in less overhead either a NOP command or a TIMING-MARK command. Sending a NOP command
then a TIMING-MARK command, since a client doesn't send a reply. results in less overhead then a TIMING-MARK command, since a client
doesn't send a reply.
The objects tn3270eSrvrConfAdminStatus and tn3270eSrvrConfOperStatus The objects tn3270eSrvrConfAdminStatus and tn3270eSrvrConfOperStatus
enable remote starting and stopping of a TN3270E server, and report the enable remote starting and stopping of a TN3270E server, and report
current state of the server. The object the current state of the server. The object
tn3270eSrvrConfFunctionsSupported indicates which of the TN3270 and tn3270eSrvrConfFunctionsSupported indicates which of the TN3270 and
TN3270E options a server supports. The object TN3270E options a server supports. The object
tn3270eSrvrConfSessionTermState defines as a TN3270E server-wide option tn3270eSrvrConfSessionTermState defines as a TN3270E server-wide
what SHOULD occur when the SNA portion of a TN3270 or TN3270E session option what SHOULD occur when the SNA portion of a TN3270 or TN3270E
terminates with respect to the associated TCP connection. The object session terminates with respect to the associated TCP connection.
tn3270eSrvrConfSrvrType indicates whether the TN3270E server represented The object tn3270eSrvrConfSrvrType indicates whether the TN3270E
by a tn3270eSrvrConfEntry is a host or a gateway server. The object server represented by a tn3270eSrvrConfEntry is a host or a gateway
tn3270eSrvrConfContact provides a scratch pad area for a TN3270E server server. The object tn3270eSrvrConfContact provides a scratch pad
administrator to store information for later retrieval. The object area for a TN3270E server administrator to store information for
tn3270eSrvrConfLastActTime reports the DateAndTime when the server was later retrieval. The object tn3270eSrvrConfLastActTime reports the
most recently activated. The special value of all '00'Hs indicates that DateAndTime when the server was most recently activated. The special
the server has never been active. value of all '00'Hs indicates that the server has never been active.
The object tn3270eSrvrConfRowStatus provides the capability to perform The object tn3270eSrvrConfRowStatus provides the capability to
row creation and deletion operations on this table. perform row creation and deletion operations on this table.
3.1.2 tn3270eSrvrPortTable 3.1.2 tn3270eSrvrPortTable
The tn3270eSrvrPortTable represents the local TCP ports associated with The tn3270eSrvrPortTable represents the local TCP ports associated
a TN3270E server. This information is important because some TN3270E with a TN3270E server. This information is important because some
server implementations support usage of multiple local ports. A TN3270E server implementations support usage of multiple local ports.
tn3270eSrvrPortEntry is indexed by: A tn3270eSrvrPortEntry is indexed by:
o tn3270eSrvrConfIndex o tn3270eSrvrConfIndex
o tn3270eSrvrConfPort o tn3270eSrvrConfPort
o tn3270eSrvrConfPortAddrType o tn3270eSrvrConfPortAddrType
o tn3270eSrvrConfPortAddress o tn3270eSrvrConfPortAddress
Certain TN3270E server implementations restrict a local TCP port to a Certain TN3270E server implementations restrict a local TCP port to a
particular local IP address, instead of allowing connections for any particular local IP address, instead of allowing connections for any
local IP address to occur via the port. tn3270eSrvrConfPortAddrType and local IP address to occur via the port. tn3270eSrvrConfPortAddrType
tn3270eSrvrConfPortAddress allow this restriction to be represented in and tn3270eSrvrConfPortAddress allow this restriction to be
the MIB. A TN3270E server that doesn't restrict connections over a port represented in the MIB. A TN3270E server that doesn't restrict
to a local IP Address SHALL use the value unknown(0) for connections over a port to a local IP Address SHALL use the value
tn3270eSrvrConfPortAddrType, and a zero-length octet string for unknown(0) for tn3270eSrvrConfPortAddrType, and a zero-length octet
tn3270eSrvrConfPortAddress. string for tn3270eSrvrConfPortAddress.
3.1.3 tn3270eSrvrStatsTable 3.1.3 tn3270eSrvrStatsTable
The tn3270eSrvrStatsTable defines a series of objects that provide The tn3270eSrvrStatsTable defines a series of objects that provide
general usage statistics for a TN3270E server. An entry can represent general usage statistics for a TN3270E server. An entry can
the total activity for a server, or it can represent the activity represent the total activity for a server, or it can represent the
occurring at the server on either a port or a port-and-local-address activity occurring at the server on either a port or a port-and-
basis. local-address basis.
An implementation of this table MUST use only one of the three levels of An implementation of this table MUST use only one of the three levels
refinement that the indexing of this table supports for the entries of refinement that the indexing of this table supports for the
associated with a single TN3270E server. entries associated with a single TN3270E server.
The objects in this table reporting maximum, in-use, and spare LUs for The objects in this table reporting maximum, in-use, and spare LUs
terminals and printers presuppose an implementation where terminal for terminals and printers presuppose an implementation where
resources and printer resources come from disjoint, dedicated pools. An terminal resources and printer resources come from disjoint,
implementation where resources for the two types of LUs come from a dedicated pools. An implementation where resources for the two types
single shared pool should return the following values: of LUs come from a single shared pool should return the following
values:
o maximum: maximum size of the shared pool o maximum: maximum size of the shared pool
o in-use: number currently in use as this type of LU o in-use: number currently in use as this type of LU
o spare: maximum - (terminal in-use + printer in-use) o spare: maximum - (terminal in-use + printer in-use)
3.2 TN3270E Server Resource Configuration 3.2 TN3270E Server Resource Configuration
The following three tables provide for configuration of resources at a The following three tables provide for configuration of resources at
TN3270E server: a TN3270E server:
o tn3270eClientGroupTable o tn3270eClientGroupTable
o tn3270eResPoolTable o tn3270eResPoolTable
o tn3270eClientResMapTable o tn3270eClientResMapTable
tn3270eClientGroupTable and tn3270eResPoolTable enable implementations tn3270eClientGroupTable and tn3270eResPoolTable enable
to define groupings of both client addresses and resource pools for implementations to define groupings of both client addresses and
mapping client addresses to resources. The tn3270eClientResMapTable resource pools for mapping client addresses to resources. The
provides a mapping from a client group to a resource pool. tn3270eClientResMapTable provides a mapping from a client group to a
resource pool.
3.3 Resource Name / Client Address Mappings 3.3 Resource Name / Client Address Mappings
The TN3270E-MIB contains three tables for mapping resource names to The TN3270E-MIB contains three tables for mapping resource names to
client addresses, and client addresses to resource names: client addresses, and client addresses to resource names:
o tn3270eSnaMapTable o tn3270eSnaMapTable
o tn3270eResMapTable o tn3270eResMapTable
o tn3270eTcpConnTable o tn3270eTcpConnTable
3.3.1 tn3270eSnaMapTable 3.3.1 tn3270eSnaMapTable
The tn3270eSnaMapTable is a read-only table that maps a secondary LU's The tn3270eSnaMapTable is a read-only table that maps a secondary
SNA network name to the name by which it is known locally at the TN3270E LU's SNA network name to the name by which it is known locally at the
server. For correlation with data from the SNA network, the name of the TN3270E server. For correlation with data from the SNA network, the
associated primary LU also appears in a tn3270eSnaMapEntry. An entry in name of the associated primary LU also appears in a
this table is created when the Activate LU (ACTLU) request carrying the tn3270eSnaMapEntry. An entry in this table is created when the
SNA network name of the SLU is received from the SSCP. The entry is Activate LU (ACTLU) request carrying the SNA network name of the SLU
deleted when the SLU is deactivated. is received from the SSCP. The entry is deleted when the SLU is
deactivated.
A TN3270E server provides a client with access to an SNA application by A TN3270E server provides a client with access to an SNA application
associating a TCP connection from the client with an SNA secondary LU by associating a TCP connection from the client with an SNA secondary
(SLU) at the server. This SLU in turn has an SNA session with a primary LU (SLU) at the server. This SLU in turn has an SNA session with a
LU (PLU) running on an SNA host. This PLU represents the application primary LU (PLU) running on an SNA host. This PLU represents the
with which the client is communicating. The TN3270E-MIB includes two application with which the client is communicating. The TN3270E-MIB
tables for mapping back and forth among the SNA name identifying the includes two tables for mapping back and forth among the SNA name
PLU, the SNA name identifying the SLU, and the TCP connection with the identifying the PLU, the SNA name identifying the SLU, and the TCP
client. connection with the client.
In order to understand how these name mappings work, it is necessary to In order to understand how these name mappings work, it is necessary
understand a subtlety involving the names of the SLUs at the TN3270E to understand a subtlety involving the names of the SLUs at the
server: these names are often different from the names by which the TN3270E server: these names are often different from the names by
SLUs are known in the rest of the SNA network. In the TN3270E-MIB, which the SLUs are known in the rest of the SNA network. In the
these two types of SLU names are termed "local names" and "SSCP-supplied TN3270E-MIB, these two types of SLU names are termed "local names"
names"; the latter term indicates that the name by which the SLU is and "SSCP-supplied names"; the latter term indicates that the name by
known in the SNA network comes to the TN3270E server from the SNA System which the SLU is known in the SNA network comes to the TN3270E server
Services Control Point. from the SNA System Services Control Point.
SSCPs don't always send SLU names down to secondary LUs; in some cases SSCPs don't always send SLU names down to secondary LUs; in some
this capability must be turned on. In the case of SLUs served by a cases this capability must be turned on. In the case of SLUs served
Dependent LU Requester (DLUR), an SSCP always sends SLU names to the by a Dependent LU Requester (DLUR), an SSCP always sends SLU names to
DLUR. It is necessary, however, to enable the DLUR's PU/LU Network Name the DLUR. It is necessary, however, to enable the DLUR's PU/LU
Forwarding function, so that it forwards the SLU names it receives from Network Name Forwarding function, so that it forwards the SLU names
the SSCP down to the PUs that it serves. it receives from the SSCP down to the PUs that it serves.
For SLUs associated with an SNA type 2.0 node (or with a For SLUs associated with an SNA type 2.0 node (or with a boundary-
boundary-function-attached type 2.1 node) not served by a DLUR, function-attached type 2.1 node) not served by a DLUR, inclusion of
inclusion of SLU names on ACTLU must be enabled explicitly at the SSCP SLU names on ACTLU must be enabled explicitly at the SSCP via local
via local configuration. configuration.
3.3.2 tn3270eResMapTable 3.3.2 tn3270eResMapTable
The tn3270eResMapTable is a read-only table that maps a resource name to The tn3270eResMapTable is a read-only table that maps a resource name
a client's address. An entry in this table is created when a TCP 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. connection is received by a TN3270E server and mapped to a resource.
The entry is deleted when the resource-to-address association is no The entry is deleted when the resource-to-address association is no
longer valid. longer valid.
3.3.3 tn3270eTcpConnTable 3.3.3 tn3270eTcpConnTable
The TCP Connection Table is currently defined by RFC 2012 (Refer to The TCP Connection Table is currently defined by RFC 2012 (Refer to
reference [20], TCP-MIB Definitions). It contains the following reference [20], TCP-MIB Definitions). It contains the following
objects: objects:
o tcpConnState (INTEGER) o tcpConnState (INTEGER)
o tcpConnLocalAddress (IpAddress) o tcpConnLocalAddress (IpAddress)
o tcpConnLocalPort (INTEGER) o tcpConnLocalPort (INTEGER)
o tcpConnRemAddress (IpAddress) o tcpConnRemAddress (IpAddress)
o tcpConnRemPort (INTEGER) o tcpConnRemPort (INTEGER)
It is indexed by: tcpConnLocalAddress, tcpConnLocalPort, It is indexed by: tcpConnLocalAddress, tcpConnLocalPort,
tcpConnRemAddress, and tcpConnRemPort. tcpConnRemAddress, and tcpConnRemPort.
The tn3270eTcpConnTable contains objects for keeping a list of the The tn3270eTcpConnTable contains objects for keeping a list of the
current set of TN3270 and TN3270E sessions at a TN3270E server. The current set of TN3270 and TN3270E sessions at a TN3270E server. The
relationship between the tcpConnTable and the Tn3270eTcpConnTable is not relationship between the tcpConnTable and the Tn3270eTcpConnTable is
one-to-one, since the tn3270eTcpConnTable contains information not one-to-one, since the tn3270eTcpConnTable contains information
pertaining only to TN3270(E) sessions. pertaining only to TN3270(E) sessions.
The tn3270eTcpConnTable has a different indexing structure from that of The tn3270eTcpConnTable has a different indexing structure from that
the tcpConnTable. Instead of using IpAddress objects, Tn3270eAddress of the tcpConnTable. Instead of using IpAddress objects,
and IANATn3270eAddrType object pairs are used to specify client Tn3270eAddress and IANATn3270eAddrType object pairs are used to
addresses (both local and remote). This enables support of IPv6 specify client addresses (both local and remote). This enables
addresses. In addition, the remote address pair precedes the local support of IPv6 addresses. In addition, the remote address pair
address pair in the index clause, in order to enable a GET-NEXT precedes the local address pair in the index clause, in order to
operation using only the remote address pair. enable a GET-NEXT operation using only the remote address pair.
3.4 Advisory Spin Lock Usage 3.4 Advisory Spin Lock Usage
Within the TN3270E-MIB, tn3270eConfSpinLock is defined as an advisory Within the TN3270E-MIB, tn3270eConfSpinLock is defined as an advisory
lock that allows cooperating TN3270E-MIB applications to coordinate lock that allows cooperating TN3270E-MIB applications to coordinate
their use of the tn3270eSrvrConfTable, the tn3270eSrvrPortTable, the their use of the tn3270eSrvrConfTable, the tn3270eSrvrPortTable, the
tn3270eClientGroupTable, the tn3270eResPoolTable, and the tn3270eClientGroupTable, the tn3270eResPoolTable, and the
tn3270eClientResMapTable. When creating a new entry or altering an tn3270eClientResMapTable. When creating a new entry or altering an
existing entry in any of these tables, an application SHOULD make use of existing entry in any of these tables, an application SHOULD make use
tn3270eConfSpinLock to serialize application changes or additions. of tn3270eConfSpinLock to serialize application changes or additions.
Since this is an advisory lock, its use by management applications SHALL Since this is an advisory lock, its use by management applications
NOT be enforced by agents. Agents MUST, however, implement the SHALL NOT be enforced by agents. Agents MUST, however, implement the
tn3270eConfSpinLock object. tn3270eConfSpinLock object.
3.5 Row Persistence 3.5 Row Persistence
The following tables enable remote creation of their entries by The following tables enable remote creation of their entries by
including RowStatus objects: including RowStatus objects:
o tn3270eSrvrConfTable o tn3270eSrvrConfTable
o tn3270eSrvrPortTable o tn3270eSrvrPortTable
o tn3270eClientGroupTable o tn3270eClientGroupTable
o tn3270eResPoolTable o tn3270eResPoolTable
o tn3270eClientResMapTable o tn3270eClientResMapTable
An implementation SHOULD NOT retain SNMP-created entries in these tables An implementation SHOULD NOT retain SNMP-created entries in these
across reIPLs (Initial Program Loads) of the corresponding TN3270E tables across reIPLs (Initial Program Loads) of the corresponding
server, since management applications need to see consistent behavior TN3270E server, since management applications need to see consistent
with respect to the persistence of the table entries that they create. behavior with respect to the persistence of the table entries that
they create.
It is expected that local, implementation-dependent configuration It is expected that local, implementation-dependent configuration
information will be used to define the initial and persistent information will be used to define the initial and persistent
configurations for TN3270E server usage. Thus it is not necessary to configurations for TN3270E server usage. Thus it is not necessary to
enable persistence of table entries by adding StorageType (refer to RFC enable persistence of table entries by adding StorageType (refer to
1903 [6]) objects to these tables. RFC 1903 [6]) objects to these tables.
3.6 IANA Considerations 3.6 IANA Considerations
The tn3270eSrvrFunctionsSupported, tn3270eTcpConnFunctions, The tn3270eSrvrFunctionsSupported, tn3270eTcpConnFunctions,
tn3270eTcpConnClientIdFormat, and tn3270eTcpConnLogInfo objects, as well tn3270eTcpConnClientIdFormat, and tn3270eTcpConnLogInfo objects, as
as a number of objects identifying various address types, resource well as a number of objects identifying various address types,
types, and device types, use textual conventions imported from the resource types, and device types, use textual conventions imported
IANATn3270eTC-MIB. The purpose of defining these textual conventions in from the IANATn3270eTC-MIB. The purpose of defining these textual
a separate MIB module is to allow additional values to be defined conventions in a separate MIB module is to allow additional values to
without having to issue a new version of this document. The Internet be defined without having to issue a new version of this document.
Assigned Number Authority (IANA) is responsible for the assignment of The Internet Assigned Numbers Authority (IANA) is responsible for the
all Internet numbers, including various SNMP-related numbers; it will assignment of all Internet numbers, including various SNMP-related
administer the values associated with these textual conventions. numbers; it will administer the values associated with these textual
conventions.
The rules for additions or changes to the IANATn3270eTC-MIB are outlined The rules for additions or changes to the IANATn3270eTC-MIB are
in the DESCRIPTION clause associated with its MODULE-IDENTITY statement. outlined in the DESCRIPTION clause associated with its MODULE-
IDENTITY statement.
The current version of the IANATn3270eTC-MIB can be accessed from the The current version of the IANATn3270eTC-MIB can be accessed from the
IANA home page at: "http://www.iana.org/iana/". IANA home page at: "http://www.iana.org/".
4.0 Definitions 4.0 Definitions
TN3270E-MIB DEFINITIONS ::= BEGIN TN3270E-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, Unsigned32, TimeTicks, MODULE-IDENTITY, OBJECT-TYPE, Unsigned32, TimeTicks,
IpAddress, Counter32, Gauge32, Counter64 IpAddress, Counter32, Gauge32, Counter64
FROM SNMPv2-SMI FROM SNMPv2-SMI
TEXTUAL-CONVENTION, RowStatus, TestAndIncr, DateAndTime, TEXTUAL-CONVENTION, RowStatus, TestAndIncr, DateAndTime,
skipping to change at page 45, line 20 skipping to change at page 51, line 36
Counter64. An implementation that doesn't support Counter64. An implementation that doesn't support
these objects should return noSuchObject, since these objects should return noSuchObject, since
returning a zero is misleading." returning a zero is misleading."
::= { tn3270eGroups 4 } ::= { tn3270eGroups 4 }
END END
5.0 Security Considerations 5.0 Security Considerations
Certain management information defined in this MIB may be considered Certain management information defined in this MIB may be considered
sensitive in some network environments. Therefore, authentication of sensitive in some network environments. Therefore, authentication of
received SNMP requests and controlled access to management information received SNMP requests and controlled access to management
SHOULD be employed in such environments. An authentication protocol is information SHOULD be employed in such environments. An
defined in [12]. A protocol for access control is defined in [15]. authentication protocol is defined in [12]. A protocol for access
control is defined in [15].
Several objects in this MIB allow write access or provide for row Several objects in this MIB allow write access or provide for row
creation. Allowing this support in a non-secure environment can have a creation. Allowing this support in a non-secure environment can have
negative effect on network operations. It is RECOMMENDED that a negative effect on network operations. It is RECOMMENDED that
implementers seriously consider whether set operations or row creation implementers seriously consider whether set operations or row
should be allowed without providing, at a minimum, authentication of creation should be allowed without providing, at a minimum,
request origin. It is RECOMMENDED that without such support, the authentication of request origin. It is RECOMMENDED that without
following objects be implemented as read-only: such support, the following objects be implemented as read-only:
o tn3270eSrvrConfInactivityTimout o tn3270eSrvrConfInactivityTimout
o tn3270eSrvrConfConnectivityChk o tn3270eSrvrConfConnectivityChk
o tn3270eSrvrConfActivityTimeout o tn3270eSrvrConfActivityTimeout
o tn3270eSrvrConfActivityInterval o tn3270eSrvrConfActivityInterval
o tn3270eSrvrConfAdminStatus o tn3270eSrvrConfAdminStatus
o tn3270eSrvrConfSessionTermState o tn3270eSrvrConfSessionTermState
o tn3270eSrvrConfContact o tn3270eSrvrConfContact
o tn3270eClientGroupSubnetMask o tn3270eClientGroupSubnetMask
o tn3270eResPoolElementType o tn3270eResPoolElementType
o tn3270eSrvrConfRowStatus o tn3270eSrvrConfRowStatus
o tn3270eSrvrPortRowStatus o tn3270eSrvrPortRowStatus
o tn3270eClientGroupRowStatus o tn3270eClientGroupRowStatus
o tn3270eResPoolRowStatus o tn3270eResPoolRowStatus
o tn3270eResMapRowStatus o tn3270eResMapRowStatus
For all tables in the MIB except the tn3270eTcpConnTable, the first For all tables in the MIB except the tn3270eTcpConnTable, the first
index identifies an individual TN3270E server. This makes it easy to index identifies an individual TN3270E server. This makes it easy to
implement an access control policy under which different principals have implement an access control policy under which different principals
access to objects related to different servers. Implementation of such have access to objects related to different servers. Implementation
a policy is not possible for the entries in the tn3270eTcpConTable. of such a policy is not possible for the entries in the
tn3270eTcpConTable.
6.0 Intellectual Property 6.0 Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to pertain intellectual property or other rights that might be claimed to
to the implementation or use of the technology described in this pertain to the implementation or use of the technology described in
document or the extent to which any license under such rights might or this document or the extent to which any license under such rights
might not be available; neither does it represent that it has made any might or might not be available; neither does it represent that it
effort to identify any such rights. Information on the IETF's has made any effort to identify any such rights. Information on the
procedures with respect to rights in standards-track and IETF's procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11. Copies of standards-related documentation can be found in BCP-11. Copies of
claims of rights made available for publication and any assurances of claims of rights made available for publication and any assurances of
licenses to be made available, or the result of an attempt made to licenses to be made available, or the result of an attempt made to
obtain a general license or permission for the use of such proprietary obtain a general license or permission for the use of such
rights by implementers or users of this specification can be obtained proprietary rights by implementers or users of this specification can
from the IETF Secretariat. be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary rights copyrights, patents or patent applications, or other proprietary
which may cover technology that may be required to practice this rights which may cover technology that may be required to practice
standard. Please address the information to the IETF Executive this standard. Please address the information to the IETF Executive
Director. Director.
7.0 Acknowledgments 7.0 Acknowledgments
This document is a product of the TN3270E Working Group. Thanks to This document is a product of the TN3270E Working Group. Thanks to
Randy Presuhn of BMC Software for his valuable review comments on Randy Presuhn of BMC Software for his valuable review comments on
several versions of the document. several versions of the document.
8.0 References 8.0 References
[1] Harrington D., Presuhn, R., Wijnen, B., "An Architecture for [1] Harrington D., Presuhn, R. and B. Wijnen, "An Architecture for
Describing SNMP Management Frameworks", RFC 2271, Cabletron Describing SNMP Management Frameworks", RFC 2271, January 1998.
Systems, Inc., BMC Software, Inc., IBM T.J. Watson Research,
January 1998.
[2] Rose, M., and K. McCloghrie, "Structure and Identification of [2] Rose, M. and K. McCloghrie, "Structure and Identification of
Management Information for TCP/IP-based Internets", RFC 1155, Management Information for TCP/IP-based Internets", STD 16, RFC
Performance Systems International, Hughes LAN Systems, May 1990 1155, May 1990
[3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", RFC 1212, [3] Rose, M. and K. McCloghrie, "Concise MIB Definitions", STD 16,
Performance Systems International, Hughes LAN Systems, March 1991 RFC 1212, March 1991.
[4] M. Rose, "A Convention for Defining Traps for use with the SNMP", [4] Rose, M., "A Convention for Defining Traps for use with the
RFC 1215, Performance Systems International, March 1991 SNMP", RFC 1215, Performance Systems International, March 1991
[5] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Structure [5] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Structure
of Management Information for Version 2 of the Simple Network of Management Information for Version 2 of the Simple Network
Management Protocol (SNMPv2)", RFC 1902, SNMP Research,Inc., Cisco Management Protocol (SNMPv2)", RFC 1902, January 1996.
Systems, Inc., Dover Beach Consulting, Inc., International Network
Services, January 1996.
[6] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Textual [6] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Textual
Conventions for Version 2 of the Simple Network Management Protocol Conventions for Version 2 of the Simple Network Management
(SNMPv2)", RFC 1903, SNMP Research, Inc., Cisco Systems, Inc., Protocol (SNMPv2)", RFC 1903, January 1996.
Dover Beach Consulting, Inc., International Network Services,
January 1996.
[7] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Conformance [7] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser,
Statements for Version 2 of the Simple Network Management Protocol "Conformance Statements for Version 2 of the Simple Network
(SNMPv2)", RFC 1904, SNMP Research, Inc., Cisco Systems, Inc., Management Protocol (SNMPv2)", RFC 1904, January 1996.
Dover Beach Consulting, Inc., International Network Services,
January 1996.
[8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network [8] Case, J., Fedor, M., Schoffstall, M. and J. Davin, "Simple
Management Protocol", RFC 1157, SNMP Research, Performance Systems Network Management Protocol", STD 15, RFC 1157, May 1990.
International, Performance Systems International, MIT Laboratory
for Computer Science, May 1990.
[9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, [9] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser,
"Introduction to Community-based SNMPv2", RFC 1901, SNMP Research, "Introduction to Community-based SNMPv2", RFC 1901, January
Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., 1996.
International Network Services, January 1996.
[10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport [10] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Transport
Mappings for Version 2 of the Simple Network Management Protocol Mappings for Version 2 of the Simple Network Management Protocol
(SNMPv2)", RFC 1906, SNMP Research, Inc., Cisco Systems, Inc., (SNMPv2)", RFC 1906, January 1996.
Dover Beach Consulting, Inc., International Network Services,
January 1996.
[11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message [11] Case, J., Harrington D., Presuhn R. and B. Wijnen, "Message
Processing and Dispatching for the Simple Network Management Processing and Dispatching for the Simple Network Management
Protocol (SNMP)", RFC 2272, SNMP Research, Inc., Cabletron Systems, Protocol (SNMP)", RFC 2272, January 1998.
Inc., BMC Software, Inc., IBM T. J. Watson Research, January 1998.
[12] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for [12] Blumenthal, U. and B. Wijnen, "User-based Security Model (USM)
version 3 of the Simple Network Management Protocol (SNMPv3)", RFC for version 3 of the Simple Network Management Protocol
2274, IBM T. J. Watson Research, January 1998. (SNMPv3)", RFC 2274, January 1998.
[13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol [13] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Protocol
Operations for Version 2 of the Simple Network Management Protocol Operations for Version 2 of the Simple Network Management
(SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco Systems, Inc., Protocol (SNMPv2)", RFC 1905, January 1996.
Dover Beach Consulting, Inc., International Network Services,
January 1996.
[14] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC [14] Levi, D., Meyer, P. and B. Stewart, "SNMPv3 Applications", RFC
2273, SNMP Research, Inc., Secure Computing Corporation, Cisco 2273, January 1998.
Systems, January 1998
[15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access [15] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based Access
Control Model (VACM) for the Simple Network Management Protocol Control Model (VACM) for the Simple Network Management Protocol
(SNMP)", RFC 2275, IBM T. J. Watson Research, BMC Software, Inc., (SNMP)", RFC 2275, January 1998.
Cisco Systems, Inc., January 1998
[16] Postel, J., and Reynolds, J., "Telnet Protocol Specification", RFC [16] Postel, J. and J. Reynolds, "Telnet Protocol Specification", STD
854, May 1983. 8, RFC 854, May 1983.
[17] Postel, J., and Reynolds, J., "Telnet Timing Mark Option", RFC 860, [17] Postel, J. and J. Reynolds, "Telnet Timing Mark Option", STD 31,
May 1983. RFC 860, May 1983.
[18] Rekhter, J., "Telnet 3270 Regime Option", RFC 1041, January 1988. [18] Rekhter, J., "Telnet 3270 Regime Option", RFC 1041, January
1988.
[19] Kelly, B., "TN3270 Enhancements", RFC 2355, June 1998. [19] Kelly, B., "TN3270 Enhancements", RFC 2355, June 1998.
[20] McCloghrie, K., "TCP-MIB Definitions", RFC 2012, November 1996. [20] McCloghrie, K., "TCP-MIB Definitions", RFC 2012, November
1996.
[21] Hovey, R., and S. Bradner, "The Organizations Involved in the IETF [21] Hovey, R. and S. Bradner, "The Organizations Involved in the
Standards Process", BCP 11, RFC 2028, October 1996. IETF Standards Process", BCP 11, RFC 2028, October 1996.
[22] Bradner, S., "Key words for use in RFCs to Indicate Requirement [22] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119, March 1997. Levels", BCP 14, RFC 2119, March 1997.
[23] Hinden, R., Deering, S., "IP Version 6 Addressing Architecture", [23] Hinden, R. and S. Deering, "IP Version 6 Addressing
RFC 2373, July 1998. Architecture", RFC 2373, July 1998.
[24] Krupczak, Cheryl, Saperia, Jonathan, "Definitions of System-Level [24] Krupczak, C. and J. Saperia, "Definitions of System-Level
Managed Objects for Applications", RFC 2287, February 1998. Managed Objects for Applications", RFC 2287, February 1998.
9.0 Authors' Addresses 9.0 Authors' Addresses
Kenneth D. White Kenneth D. White
Dept. BRQA/Bldg. 501/G114 Dept. BRQA/Bldg. 501/G114
IBM Corporation IBM Corporation
P.O.Box 12195 P.O.Box 12195
3039 Cornwallis 3039 Cornwallis
Research Triangle Park, NC 27709, USA Research Triangle Park, NC 27709, USA
E-mail: kennethw@vnet.ibm.com
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-4436
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 "9807270000Z" -- July 27, 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."
REVISION "9807270000Z" -- July 27, 1998
DESCRIPTION
"Initial version transferred from the TN3270E
working group to IANA."
-- IANA will assign a real OID when they take over this module.
::= { experimental 2001 }
-- Textual Conventions
IANATn3270eAddrType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The textual convention for defining the type of a
client address. The enumeration value unknown(0) is
also used to indicate that no actual address is present."
SYNTAX INTEGER {
unknown(0),
ipv4(1),
ipv6(2)
}
IANATn3270eAddress ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"Denotes a client address. The type of client address is
determined by use of the IANATn3270eAddrType textual convention.
The length in octets of a IANATn3270eAddress object is:
IANATn3270eAddrType Address Length
+++++++++++++++++++ ++++++++++++++
unknown(0) not specified or unknown; the
actual length of the
IANATn3270eAddress 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 and is not a full transport
layer address."
SYNTAX OCTET STRING (SIZE (0..255))
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(1) 0 Not specified
other(2) 1..512 Implementation specific
ipv4(3) 6 4-octet IP Address plus
2-octet TCP Port
ipv6(4) 18 16-octet IPv6 Address
plus 2-octet TCP Port
domainName(5) 1..512 The DNS name of a
client.
truncDomainName(6) 1..512 The (truncated) DNS name
of a client.
string(7) 1..512 Unknown Utf8String
certificate(8) 1..512 certificate
userId(9) 1..8 Client's userid
x509dn(10) 1..512 X.509 Distinguished Name
Representation of a certificate(8) may be lead to
a security exposure and is NOT RECOMMENDED without
adequate security."
SYNTAX INTEGER {
none(1),
other(2),
ipv4(3),
ipv6(4),
domainName(5),
truncDomainName(6),
string(7),
certificate(8),
userId(9),
x509dn(10)
}
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.
RFC860
timingMark 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.
RFC2355
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), -- rfc2355
dataStreamCtl(6), -- rfc2355
responses(7), -- rfc2355
bindImage(8), -- rfc2355
sysreq(9) -- rfc2355
}
IANATn3270ResourceType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The type of resource defined by a resource pool. Refer
to tn3270eResPoolTable."
SYNTAX INTEGER {
other(1),
terminal(2),
printer(3),
terminalOrPrinter(4)
}
IANATn3270DeviceType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This textual convention defines the list of device
types that can be set, as defined by RFC 2355."
SYNTAX INTEGER {
-- terminals
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)
-- printers
ibm3287d1(10),
unknown(100)
}
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: EMail: kennethw@vnet.ibm.com
+------+----+---------+------------+ Robert Moore
!length!type!TimeStamp! data ! Dept. BRQA/Bldg. 501/G114
+------+----+---------+------------+ IBM Corporation
P.O.Box 12195
3039 Cornwallis
Research Triangle Park, NC 27709, USA
where Phone: +1-919-254-4436
EMail: remoore@us.ibm.com
length = one-octet length of the data portion of the Full Copyright Statement
trace element, not including the length,
type, and TimeStamp fields
type = one-octet code point characterizing the data.
TimeStamp = A 4-octet field representing the number of
TimeTicks since the TN3270E server was last
activated. The server's last activation time
is available in the tn3270eSrvrConfLastActTime
object in the TN3270E MIB, which has the
syntax DateAndTime.
data = initial part of a PDU.
length type Copyright (C) The Internet Society (1999). All Rights Reserved.
0-255 x'00' - unknown This document and translations of it may be copied and furnished to
0 x'01' - inactivity timer expired others, and derivative works that comment on or otherwise explain it
0 x'02' - dynamic timer expired or assist in its implementation may be prepared, copied, published
0 x'03' - actlu req and distributed, in whole or in part, without restriction of any
0 x'04' - bind req kind, provided that the above copyright notice and this paragraph are
0 x'05' - clear req included on all such copies and derivative works. However, this
0 x'06' - dactlu req document itself may not be modified in any way, such as by removing
0 x'07' - warm actpu req the copyright notice or references to the Internet Society or other
0 x'08' - sdt req Internet organizations, except as needed for the purpose of
0 x'09' - unbind req developing Internet standards in which case the procedures for
0 x'0A' - notify resp copyrights defined in the Internet Standards process must be
0 x'0B' - reply PSID neg rsp followed, or as required to translate it into languages other than
0 x'0C' - reply PSID pos rsp English.
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-255 x'1A' - utf8String
2 x'1B' - hexCode, implementation dependent
Log element entries have a minimum length of 6 octets. The limited permissions granted above are perpetual and will not be
The zero-length string indicates that no log data is revoked by the Internet Society or its successors or assigns.
available."
SYNTAX OCTET STRING (SIZE (0 | 6..2048))
END 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.
 End of changes. 110 change blocks. 
819 lines changed or deleted 496 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/