draft-ietf-tn3270e-tn3270-mib-06.txt   draft-ietf-tn3270e-tn3270-mib-07.txt 
TN3270E Working Group Kenneth White TN3270E Working Group Kenneth White
INTERNET DRAFT: <draft-ietf-tn3270e-tn3270-mib-06.txt> IBM Corp. INTERNET DRAFT: <draft-ietf-tn3270e-tn3270-mib-07.txt> IBM Corp.
Expiration Date: October, 1998 Robert Moore Expiration Date: November, 1998 Robert Moore
IBM Corp. IBM Corp.
Base Definitions of Managed Objects for Base Definitions of Managed Objects for
TN3270E Using SMIv2 TN3270E Using SMIv2
<draft-ietf-tn3270e-tn3270-mib-06.txt> <draft-ietf-tn3270e-tn3270-mib-07.txt>
Status of this Memo Status of this Memo
This document is an Internet Draft. Internet Drafts are working This document is an Internet Draft. Internet Drafts are working
documents of the Internet Engineering Task Force (IETF), its Areas, and documents of the Internet Engineering Task Force (IETF), its Areas, and
its Working Groups. Note that other groups may also distribute working its Working Groups. Note that other groups may also distribute working
documents as Internet Drafts. documents as Internet Drafts.
Internet Drafts are draft documents valid for a maximum of six months. Internet Drafts are draft documents valid for a maximum of six months.
Internet Drafts may be updated, replaced, or obsoleted by other Internet Drafts may be updated, replaced, or obsoleted by other
skipping to change at page 1, line 46 skipping to change at page 1, line 46
and managing TN3270E servers. TN3270E, defined by RFC 1647 [15], refers and managing TN3270E servers. TN3270E, defined by RFC 1647 [15], refers
to the enhancements made to the Telnet 3270 (TN3270) terminal emulation to the enhancements made to the Telnet 3270 (TN3270) terminal emulation
practices. Refer to RFC 1041 [14], RFC 854 [12], and RFC 860 [13] for a practices. Refer to RFC 1041 [14], RFC 854 [12], and RFC 860 [13] for a
sample of what is meant by TN3270 practices. 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 and
gateway TN3270E server implementations. A TN3270E server connects a gateway TN3270E server implementations. A TN3270E server connects a
Telnet client performing 3270 emulation to a target SNA host over both a Telnet client performing 3270 emulation to a target SNA host over both a
client-side network (client to TN3270E server) and an SNA Network client-side network (client to TN3270E server) and an SNA Network
(TN3270E server to target SNA host). The client-side network is (TN3270E server to target SNA host). The client-side network is
typicaly TCP/IP, but it need not be. 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) System
Services Control Point (SSCP) for the dependent Secondary Logical Units Services Control Point (SSCP) for the dependent Secondary Logical Units
(SLUs) that the server makes available to its clients for connecting (SLUs) that the server makes available to its clients for connecting
into a SNA network. A gateway TN3270E server resides on an SNA node 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 other than an SSCP, either an SNA type 2.0 node, a
in the role of a Dependent LU Requester (DLUR). Host and gateway boundary-function-attached type 2.1 node, or an APPN node acting in the
TN3270E server implementations typically differ greatly as to their role of a Dependent LU Requester (DLUR). Host and gateway TN3270E
internal implementation and system definition (SYSDEF) methods. server implementations typically differ greatly as to their 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 subsequent
memos. For example, one such extension enables collection of TN3270E memos. For example, one such extension enables collection of TN3270E
response time data. The specification of this MIB uses the Structure of response time data. The specification of this MIB uses the Structure of
Management Information (SMI) for Version 2 of the Simple Network Management Information (SMI) for Version 2 of the Simple Network
Management Protocol (refer to RFC1902 [3]). Management Protocol (refer to RFC1902 [3]).
Table of Contents Table of Contents
1.0 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.0 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.0 The SNMP Network Management Framework . . . . . . . . . . . . 3 2.0 The SNMP Network Management Framework . . . . . . . . . . . . 3
3.0 Structure of the MIB . . . . . . . . . . . . . . . . . . . . . 3 3.0 Structure of the MIB . . . . . . . . . . . . . . . . . . . . . 3
3.1 TN3270E Server Control . . . . . . . . . . . . . . . . . . . . 4 3.1 TN3270E Server Control . . . . . . . . . . . . . . . . . . . . 4
3.1.1 tn3270eSrvrConfTable . . . . . . . . . . . . . . . . . . . 5 3.1.1 tn3270eSrvrConfTable . . . . . . . . . . . . . . . . . . . 5
3.1.2 tn3270eSrvrPortTable . . . . . . . . . . . . . . . . . . . 5 3.1.2 tn3270eSrvrPortTable . . . . . . . . . . . . . . . . . . . 6
3.1.3 tn3270eSrvrStatsTable . . . . . . . . . . . . . . . . . . 6 3.1.3 tn3270eSrvrStatsTable . . . . . . . . . . . . . . . . . . 6
3.2 TN3270E Server Resource Configuration . . . . . . . . . . . . 6 3.2 TN3270E Server Resource Configuration . . . . . . . . . . . . 6
3.3 Resource Name / Client Address Mappings . . . . . . . . . . . 6 3.3 Resource Name / Client Address Mappings . . . . . . . . . . . 7
3.3.1 tn3270eSnaMapTable . . . . . . . . . . . . . . . . . . . . 6 3.3.1 tn3270eSnaMapTable . . . . . . . . . . . . . . . . . . . . 7
3.3.2 tn3270eResMapTable . . . . . . . . . . . . . . . . . . . . 7 3.3.2 tn3270eResMapTable . . . . . . . . . . . . . . . . . . . . 7
3.3.3 tn3270eTcpConnTable . . . . . . . . . . . . . . . . . . . 7 3.3.3 tn3270eTcpConnTable . . . . . . . . . . . . . . . . . . . 8
3.4 Advisory Spin Lock Usage . . . . . . . . . . . . . . . . . . . 8 3.4 Advisory Spin Lock Usage . . . . . . . . . . . . . . . . . . . 8
3.5 Row Persistence . . . . . . . . . . . . . . . . . . . . . . . 8 3.5 Row Persistence . . . . . . . . . . . . . . . . . . . . . . . 8
3.6 IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 3.6 IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
4.0 Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 9 4.0 Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 9
5.0 Security Considerations . . . . . . . . . . . . . . . . . . . 44 5.0 Security Considerations . . . . . . . . . . . . . . . . . . . 45
6.0 Intellectual Property . . . . . . . . . . . . . . . . . . . . 45 6.0 Intellectual Property . . . . . . . . . . . . . . . . . . . . 46
7.0 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 45 7.0 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 47
8.0 References . . . . . . . . . . . . . . . . . . . . . . . . . . 45 8.0 References . . . . . . . . . . . . . . . . . . . . . . . . . . 47
9.0 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 47 9.0 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 48
10.0 Full Copyright Statement . . . . . . . . . . . . . . . . . . 47 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 is
to define a MIB module for support by a TCP/IP implementation for 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 [19]. document are to be interpreted as described in RFC 2119, reference [18].
2.0 The SNMP Network Management Framework 2.0 The SNMP Network Management Framework
The SNMP Network Management Framework presently consists of six major The SNMP Network Management Framework presently consists of six major
components. They are: components. They are:
o the overall architecture, described in RFC 2271 [7]. o the overall architecture, described in RFC 2271 [7].
o the SMI, described in RFC 1902 [3], - the mechanisms used for o the SMI, described in RFC 1902 [3], - the mechanisms used for
describing and naming objects for the purpose of management. describing and naming objects for the purpose of management.
skipping to change at page 4, line 14 skipping to change at page 4, line 14
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 not
support the TN3270E protocol. Even though a significant number of the support the TN3270E protocol. Even though a significant number of the
objects in the MIB do apply in the TN3270-only case, the case was not objects in the MIB do apply in the TN3270-only case, the case was not
addressed, since it is unlikely that a TN3270-only server would addressed, since it is unlikely that a TN3270-only server would
implement this MIB. implement this MIB.
The SYSAPPL-MIB, reference [21], contains the Utf8String textual The SYSAPPL-MIB, reference [20], 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 does
not. The SNMP-FRAMEWORK-MIB, reference [7], contains the not. The SNMP-FRAMEWORK-MIB, reference [7], 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 other
hand, implementation of the TN3270E-MIB does not preclude implementing hand, implementation of the TN3270E-MIB does not preclude implementing
the SYSAPPL-MIB as well. When both MIBs are implemented, the primary the SYSAPPL-MIB as well. When both MIBs are implemented, the primary
index into most of the TN3270E-MIB tables, tn3270eSrvrConfIndex, SHOULD index into most of the TN3270E-MIB tables, tn3270eSrvrConfIndex, SHOULD
equal one of the SYSAPPL-MIB's sysApplElmtRunIndex values. In this case equal one of the SYSAPPL-MIB's sysApplElmtRunIndex values. In this case
the entry in the sysApplElmtRunTable provides additional information on the entry in the sysApplElmtRunTable provides additional information on
a TN3270E server. 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, Tn3270eAddrType and addressing. Two textual conventions, IANATn3270eAddrType and
Tn3270eTAddress, are defined for this purpose. Tn3270eTAddress is Tn3270eTAddress, are defined for this purpose. IANATn3270eTAddress 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 Tn3270eTAddress allows a zero-length difference between the two is that IANATn3270eTAddress allows a
octet string, while TAddress doesn't. It is important that zero-length octet string, while TAddress doesn't. It is important that
Tn3270eTAddress allow for the absence of an address, because some IANATn3270eTAddress 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 Tn3270eAddrType textual convention is used rather than the TDomain The IANATn3270eAddrType textual convention is used rather than the
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. Tn3270eAddrType was chosen contents of an associated TAddress object. IANATn3270eAddrType was
over TDomain because, with a SYNTAX of Unsigned32 (enumeration type), it chosen over TDomain because, with a SYNTAX of Unsigned32 (enumeration
is much simpler to use as a component in an instance identifier. 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
the addition of values to cover cases (such as proxy servers) not
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 tn3270eSrvrConfIndex.
Most of the other tables defined by the TN3270E-MIB have Most of the other tables defined by the TN3270E-MIB have
tn3270eSrvrConfIndex as their primary index. Entries in these tables tn3270eSrvrConfIndex as their primary index. Entries in these tables
MUST NOT exist for a TN3270E server when it does not have a MUST NOT exist for a TN3270E server when it does not have a
tn3270eSrvrConfigEntry. tn3270eSrvrConfigEntry.
skipping to change at page 5, line 24 skipping to change at page 5, line 26
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 integer,
tn3270eSrvrConfIndex. This primary index element enables support of tn3270eSrvrConfIndex. This primary index element enables support of
multiple TN3270E servers by a single SNMP agent. Within the set of MIB multiple TN3270E servers by a single SNMP agent. Within the set of MIB
objects returned by one SNMP agent, tn3270eSrvrConfIndex values MUST be objects returned by one SNMP agent, tn3270eSrvrConfIndex values MUST be
unique, and need not be contiguous. unique, and need not be contiguous.
The tn3270eSrvrConfInactivityTimer object defines the inactivity period The tn3270eSrvrConfInactivityTimer object defines the inactivity period
for TN3270 and TN3270E sessions. for user traffic on TN3270 and TN3270E sessions.
The three objects: The four objects:
o tn3270eSrvrConfActivityCheck o tn3270eSrvrConfActivityCheck
o tn3270eSrvrConfActivityTimeout o tn3270eSrvrConfTmNopInterval
o tn3270eSrvrConfActivityInterval o tn3270eSrvrConfTmNopInactTime
o tn3270eSrvrConfTmTimeout
define the parameters for performing the "Telnet Timing Mark Option" as define the parameters for performing the "Telnet Timing Mark Option" as
defined by RFC 860 [13]. The object tn3270eSrvrConfActivityCheck allows defined by RFC 860 [13]. The object tn3270eSrvrConfActivityCheck allows
a Management Station to select either a NOP command or a TIMEMARK a Management Station to select either a NOP command or a TIMING-MARK
command. Sending a NOP command results in less overhead then a TIMEMARK command. Sending a NOP command results in less overhead then a
command, since a client doesn't send a reply. 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 the
current state of the server. The object 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 option
what SHOULD occur when the SNA portion of a TN3270 or TN3270E session what SHOULD occur when the SNA portion of a TN3270 or TN3270E session
terminates with respect to the associated TCP connection. The object terminates with respect to the associated TCP connection. The object
tn3270eSrvrConfSrvrType indicates whether the TN3270E server represented tn3270eSrvrConfSrvrType indicates whether the TN3270E server represented
skipping to change at page 6, line 33 skipping to change at page 6, line 35
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 represent
the total activity for a server, or it can represent the activity the total activity for a server, or it can represent the activity
occurring at the server on either a port or a port-and-local-address occurring at the server on either a port or a port-and-local-address
basis. 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 of
refinement that the indexing of this table supports. refinement that the indexing of this table supports for the entries
associated with a single TN3270E server.
The objects in this table reporting maximum, in-use, and spare LUs for
terminals and printers presuppose an implementation where terminal
resources and printer resources come from disjoint, dedicated pools. An
implementation where resources for the two types of LUs come from a
single shared pool should return the following values:
o maximum: maximum size of the shared pool
o in-use: number currently in use as this type of LU
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 a
TN3270E server: TN3270E server:
o tn3270eClientGroupTable o tn3270eClientGroupTable
o tn3270eResPoolTable o tn3270eResPoolTable
o tn3270eClientResMapTable o tn3270eClientResMapTable
skipping to change at page 7, line 31 skipping to change at page 7, line 45
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 to
understand a subtlety involving the names of the SLUs at the TN3270E understand a subtlety involving the names of the SLUs at the TN3270E
server: these names are often different from the names by which the 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, 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 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 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 known in the SNA network comes to the TN3270E server from the SNA System
Services Control Point. Services Control Point.
SSCPs don't always send SLU names down to the secondary LUs; in some SSCPs don't always send SLU names down to secondary LUs; in some cases
cases this capability must be turned on. In the case of SLUs served by this capability must be turned on. In the case of SLUs served by a
a Dependent LU Requester (DLUR), the capability is always turned on. Dependent LU Requester (DLUR), an SSCP always sends SLU names to the
For those associated with an SNA type 2.0 node (or with a boundary DLUR. It is necessary, however, to enable the DLUR's PU/LU Network Name
function-attached type 2.1 node), however, inclusion of SLU names on Forwarding function, so that it forwards the SLU names it receives from
ACTLU must be enabled explicitly at the SSCP via local configuration. the SSCP down to the PUs that it serves.
For SLUs associated with an SNA type 2.0 node (or with a
boundary-function-attached type 2.1 node) not served by a DLUR,
inclusion of SLU names on ACTLU must be enabled explicitly at the SSCP
via local 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 to
a client's address. An entry in this table is created when a TCP 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
skipping to change at page 8, line 13 skipping to change at page 8, line 34
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 not
one-to-one, since the tn3270eTcpConnTable contains information 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 of
the tcpConnTable. Instead of using IpAddress objects, Tn3270eTAddress the tcpConnTable. Instead of using IpAddress objects, Tn3270eTAddress
and Tn3270eAddrType object pairs are used to specify client addresses and IANATn3270eAddrType object pairs are used to specify client
(both local and remote). This enables support of IPv6 addresses. In addresses (both local and remote). This enables support of IPv6
addition, the remote address pair precedes the local address pair in the addresses. In addition, the remote address pair precedes the local
index clause, in order to enable a GET-NEXT operation using only the address pair in the index clause, in order to enable a GET-NEXT
remote address pair. 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 of
tn3270eConfSpinLock to serialize application changes or additions. 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 SHALL
NOT be not enforced by agents. Agents MUST, however, implement the 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 tables
across reIPLs (Initial Program Loads) of the corresponding TN3270E across reIPLs (Initial Program Loads) of the corresponding TN3270E
server, since management applications need to see consistent behavior server, since management applications need to see consistent behavior
with respect to the persistence of the table entries that they create. 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
skipping to change at page 8, line 57 skipping to change at page 9, line 23
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 RFC
1903 [4]) objects to these tables. 1903 [4]) objects to these tables.
3.6 IANA Considerations 3.6 IANA Considerations
The tn3270eSrvrFunctionsSupported, tn3270eTcpConnFunctions, The tn3270eSrvrFunctionsSupported, tn3270eTcpConnFunctions,
tn3270eTcpConnClientIdFormat, and tn3270eTcpConnLogInfo objects use tn3270eTcpConnClientIdFormat, and tn3270eTcpConnLogInfo objects, as well
as a number of objects identifying the types of various addresses, use
textual conventions imported from the IANATn3270eTC-MIB. The purpose of textual conventions imported from the IANATn3270eTC-MIB. The purpose of
defining these textual conventions in a separate MIB module is to allow 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 additional values to be defined without having to issue a new version of
this document. The Internet Assigned Number Authority (IANA) is this document. The Internet Assigned Number Authority (IANA) is
responsible for the assignment of all Internet numbers, including responsible for the assignment of all Internet numbers, including
various SNMP-related numbers; it will administer the values associated various SNMP-related numbers; it will administer the values associated
with these textual conventions. 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 outlined
in the DESCRIPTION clause associated with its MODULE-IDENTITY statement. 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
skipping to change at page 9, line 36 skipping to change at page 9, line 58
TimeStamp TimeStamp
FROM SNMPv2-TC FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
snanauMIB snanauMIB
FROM SNA-NAU-MIB FROM SNA-NAU-MIB
Utf8String Utf8String
FROM SYSAPPL-MIB FROM SYSAPPL-MIB
SnmpAdminString SnmpAdminString
FROM SNMP-FRAMEWORK-MIB FROM SNMP-FRAMEWORK-MIB
IANATn3270eClientType, IANATn3270eLogData, IANATn3270eAddrType, IANATn3270eClientType,
IANATn3270Functions IANATn3270eLogData, IANATn3270Functions
FROM IANATn3270eTC-MIB; FROM IANATn3270eTC-MIB;
tn3270eMIB MODULE-IDENTITY tn3270eMIB MODULE-IDENTITY
LAST-UPDATED "9804300000Z" -- April 30, 1998 LAST-UPDATED "9805120000Z" -- May 12, 1998
ORGANIZATION "TN3270E Working Group" ORGANIZATION "TN3270E Working Group"
CONTACT-INFO CONTACT-INFO
"Kenneth White (kennethw@vnet.ibm.com) "Kenneth White (kennethw@vnet.ibm.com)
IBM Corp. - Dept. BRQA/Bldg. 501/G114 IBM Corp. - Dept. BRQA/Bldg. 501/G114
P.O. Box 12195 P.O. Box 12195
3039 Cornwallis 3039 Cornwallis
RTP, NC 27709-2195 RTP, NC 27709-2195
USA USA
Robert Moore (remoore@us.ibm.com) Robert Moore (remoore@us.ibm.com)
skipping to change at page 10, line 36 skipping to change at page 10, line 58
characters in NetIds and ResNames: '#', '@', and '$'. characters in NetIds and ResNames: '#', '@', and '$'.
While this use of these characters has been retired, While this use of these characters has been retired,
a Management Station should still accept them for a Management Station should still accept them for
backward compatibility. backward compatibility.
Note: This Textual Convention is not subject to Note: This Textual Convention is not subject to
internationalization, and does not use the character internationalization, and does not use the character
encodings used by the Utf8String Textual Convention." encodings used by the Utf8String Textual Convention."
SYNTAX OCTET STRING (SIZE(0..17)) SYNTAX OCTET STRING (SIZE(0..17))
Tn3270eAddrType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The textual convention for defining the type of a
client address. The enumeration value unknown(0) is
usually used to indicate that no actual address is
present."
SYNTAX INTEGER {
unknown(0),
ipv4(1),
ipv6(2)
}
Tn3270ResourceType ::= TEXTUAL-CONVENTION Tn3270ResourceType ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of resource defined by a resource pool. Refer "The type of resource defined by a resource pool. Refer
to tn3270eResPoolTable." to tn3270eResPoolTable."
SYNTAX INTEGER { SYNTAX INTEGER {
other(0), other(0),
lu(1), terminal(1),
printer(2) printer(2),
terminalOrPrinter(3)
} }
Tn3270eTAddress ::= TEXTUAL-CONVENTION Tn3270eTAddress ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Denotes a client address. The type of client "Denotes a client address. The type of client
address is determined by use of the Tn3270eAddrType address is determined by use of the IANATn3270eAddrType
textual convention. The length in octets of a textual convention. The length in octets of a
Tn3270eTAddress object is: Tn3270eTAddress object is:
Tn3270eAddrType Address Length IANATn3270eAddrType Address Length
unknown(0) not specified or unknown; unknown(0) not specified or unknown;
the actual length of the the actual length of the
Tn3270eTAddress octet string Tn3270eTAddress octet string
indicates if an address indicates if an address
is present is present
ipv4(1) 4 OCTETS ipv4(1) 4 OCTETS
ipv6(2) 16 OCTETS ipv6(2) 16 OCTETS
This textual convention is similar to the TAddress This textual convention is similar to the TAddress
TC defined by RFC1903 except that it allows a TC defined by RFC1903 except that it allows a
skipping to change at page 12, line 5 skipping to change at page 12, line 13
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An octet string representing trace data from the "An octet string representing trace data from the
Telnet half of a TN3270E session, from the SNA half, Telnet half of a TN3270E session, from the SNA half,
or from both. The octet string contains a sequence or from both. The octet string contains a sequence
of trace elements, with the trace elements in the of trace elements, with the trace elements in the
string ordered from earliest to latest. string ordered from earliest to latest.
Each trace element has the following form: Each trace element has the following form:
+------+----+----------------------+ +---+---+----+----------------------+
!length!type!data ! !length!type!data !
+------+----+----------------------+ +---+---+----+----------------------+
where: where:
length = one-octet length of the data portion of the length = two-octet length of the data portion of the
trace element, not including the length and trace element, not including the length and
type octets type octets
type = one-octet code point characterizing the data; type = one-octet code point characterizing the data;
defined values are: defined values are:
X'01' outbound telnet PDU to the client X'01' telnet PDU from the server to the client
X'02' inbound telnet PDU from the client X'02' telnet PDU from the client to the server
X'03' outbound SNA data to the host X'03' SNA data from the server to the SNA host
X'04' inbound SNA data from the host X'04' SNA data from the SNA host to the server
data = initial part of a PDU. data = initial part of a PDU.
It is left to implementations to determine how It is left to implementations to determine how
much of each PDU to return in a trace element. much of each PDU to return in a trace element.
The zero-length string indicates that no trace The zero-length string indicates that no trace
data is available." data is available."
SYNTAX OCTET STRING (SIZE (0 | 2..257)) SYNTAX OCTET STRING (SIZE (0 | 3..4096))
-- Top-level structure of the MIB -- Top-level structure of the MIB
tn3270eNotifications OBJECT IDENTIFIER ::= { tn3270eMIB 0 } tn3270eNotifications OBJECT IDENTIFIER ::= { tn3270eMIB 0 }
tn3270eObjects OBJECT IDENTIFIER ::= { tn3270eMIB 1 } tn3270eObjects OBJECT IDENTIFIER ::= { tn3270eMIB 1 }
tn3270eConformance OBJECT IDENTIFIER ::= { tn3270eMIB 3 } tn3270eConformance OBJECT IDENTIFIER ::= { tn3270eMIB 3 }
-- MIB Objects -- MIB Objects
tn3270eSrvrConfTable OBJECT-TYPE tn3270eSrvrConfTable OBJECT-TYPE
skipping to change at page 13, line 17 skipping to change at page 13, line 26
DESCRIPTION DESCRIPTION
"Definition of the configuration elements for a single "Definition of the configuration elements for a single
TN3270E server." TN3270E server."
INDEX { tn3270eSrvrConfIndex } INDEX { tn3270eSrvrConfIndex }
::= { tn3270eSrvrConfTable 1 } ::= { tn3270eSrvrConfTable 1 }
Tn3270eSrvrConfEntry ::= SEQUENCE { Tn3270eSrvrConfEntry ::= SEQUENCE {
tn3270eSrvrConfIndex Unsigned32, tn3270eSrvrConfIndex Unsigned32,
tn3270eSrvrConfInactivityTimeout Unsigned32, tn3270eSrvrConfInactivityTimeout Unsigned32,
tn3270eSrvrConfActivityCheck INTEGER, tn3270eSrvrConfActivityCheck INTEGER,
tn3270eSrvrConfActivityTimeout Unsigned32, tn3270eSrvrConfTmNopInactTime Unsigned32,
tn3270eSrvrConfActivityInterval Unsigned32, tn3270eSrvrConfTmNopInterval Unsigned32,
tn3270eSrvrFunctionsSupported IANATn3270Functions, tn3270eSrvrFunctionsSupported IANATn3270Functions,
tn3270eSrvrConfAdminStatus INTEGER, tn3270eSrvrConfAdminStatus INTEGER,
tn3270eSrvrConfOperStatus INTEGER, tn3270eSrvrConfOperStatus INTEGER,
tn3270eSrvrConfSessionTermState INTEGER, tn3270eSrvrConfSessionTermState INTEGER,
tn3270eSrvrConfSrvrType INTEGER, tn3270eSrvrConfSrvrType INTEGER,
tn3270eSrvrConfContact SnmpAdminString, tn3270eSrvrConfContact SnmpAdminString,
tn3270eSrvrConfRowStatus RowStatus, tn3270eSrvrConfRowStatus RowStatus,
tn3270eSrvrConfLastActTime DateAndTime tn3270eSrvrConfLastActTime DateAndTime,
tn3270eSrvrConfTmTimeout Unsigned32
} }
tn3270eSrvrConfIndex OBJECT-TYPE tn3270eSrvrConfIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Identifier for a single TN3270E server. "Identifier for a single TN3270E server.
tn3270eSrvrConfIndex values need not be tn3270eSrvrConfIndex values need not be
skipping to change at page 13, line 48 skipping to change at page 13, line 58
::= { tn3270eSrvrConfEntry 1 } ::= { tn3270eSrvrConfEntry 1 }
tn3270eSrvrConfInactivityTimeout OBJECT-TYPE tn3270eSrvrConfInactivityTimeout OBJECT-TYPE
SYNTAX Unsigned32 (0..99999999) SYNTAX Unsigned32 (0..99999999)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The inactivity time-out specified in seconds. When a "The inactivity time-out specified in seconds. When a
connection has been inactive for the number of seconds connection has been inactive for the number of seconds
specified by this object it is closed. The default of specified by this object it is closed. Only user traffic
0 means no inactivity time-out is in effect." is considered when determining whether there has been
activity on a connection.
The default value 0 means that no inactivity time-out is
in effect."
DEFVAL { 0 } DEFVAL { 0 }
::= { tn3270eSrvrConfEntry 2 } ::= { tn3270eSrvrConfEntry 2 }
tn3270eSrvrConfActivityCheck OBJECT-TYPE tn3270eSrvrConfActivityCheck OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
noCheck(0), noCheck(0),
timeMark(1), timingMark(1),
nop(2) nop(2)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object enables timemark processing, nop "This object enables TIMING-MARK processing, NOP
processing, or neither for a TN3270E server." processing, or neither for a TN3270E server."
DEFVAL { noCheck } DEFVAL { noCheck }
::= { tn3270eSrvrConfEntry 3 } ::= { tn3270eSrvrConfEntry 3 }
tn3270eSrvrConfActivityTimeout OBJECT-TYPE tn3270eSrvrConfTmNopInactTime OBJECT-TYPE
SYNTAX Unsigned32 (1..86400) -- 1 second to 24 hours SYNTAX Unsigned32 (1..86400) -- 1 second to 24 hours
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The TIMEMARK or NOP processing time-out specified in "The amount of time a connection must have had no
seconds. Note that a value of 0 is not allowed for traffic on it in order for a TIMING-MARK or NOP request
this object since the function that uses this object to be sent on the connection. This value applies only
relies on tn3270eSrvrConfActivityCheck for function when connections are being examined for recent activity
enablement." on a scan interval controlled by the value of the
tn3270eSrvrConfTmNopInterval object."
DEFVAL { 600 } -- 10 minutes DEFVAL { 600 } -- 10 minutes
::= { tn3270eSrvrConfEntry 4 } ::= { tn3270eSrvrConfEntry 4 }
tn3270eSrvrConfActivityInterval OBJECT-TYPE tn3270eSrvrConfTmNopInterval OBJECT-TYPE
SYNTAX Unsigned32 (1..86400) -- 1 second to 24 hours SYNTAX Unsigned32 (1..86400) -- 1 second to 24 hours
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The scan interval to be used by a TN3270E server. "The scan interval to be used by a TN3270E server when
TIMEMARK or NOP processing scans the Telnet sessions it examines its Telnet connections for recent activity.
on the interval provided by this object looking for The server scans its Telnet connections on the interval
sessions that have been idle for more than the value provided by this object, looking for ones that have been
provided by tn3270eSrvrConfActivityTimeout. idle for more than the value provided by the
Note that a value of 0 is not allowed for this object tn3270eSrvrConfTmNopInactTime object. A TIMING-MARK or
since the function that uses this object relies on NOP request is sent for each connection that has
tn3270eSrvrConfActivityCheck for function enablement." exhibited no activity for this period of time."
DEFVAL { 120 } -- 2 minutes DEFVAL { 120 } -- 2 minutes
::= { tn3270eSrvrConfEntry 5 } ::= { tn3270eSrvrConfEntry 5 }
tn3270eSrvrFunctionsSupported OBJECT-TYPE tn3270eSrvrFunctionsSupported OBJECT-TYPE
SYNTAX IANATn3270Functions SYNTAX IANATn3270Functions
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates the functions supported by a "This object indicates the functions supported by a
TN3270E server." TN3270E server."
skipping to change at page 18, line 29 skipping to change at page 18, line 44
"This object reports the DateAndTime when a TN3270E "This object reports the DateAndTime when a TN3270E
server was most recently activated. server was most recently activated.
The special value of all '00'Hs indicates that the The special value of all '00'Hs indicates that the
server has never been active, i.e., that the value of server has never been active, i.e., that the value of
tn3270eSrvrOperStatus has never been anything other tn3270eSrvrOperStatus has never been anything other
than down(2)." than down(2)."
DEFVAL { '0000000000000000'H } DEFVAL { '0000000000000000'H }
::= { tn3270eSrvrConfEntry 13 } ::= { tn3270eSrvrConfEntry 13 }
tn3270eSrvrConfTmTimeout OBJECT-TYPE
SYNTAX Unsigned32 (1..600) -- 1 second to 10 minutes
UNITS "seconds"
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The TIMING-MARK time-out, specified in seconds."
DEFVAL { 5 } -- 5 seconds
::= { tn3270eSrvrConfEntry 14 }
tn3270eSrvrPortTable OBJECT-TYPE tn3270eSrvrPortTable OBJECT-TYPE
SYNTAX SEQUENCE OF Tn3270eSrvrPortEntry SYNTAX SEQUENCE OF Tn3270eSrvrPortEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table defines the TCP ports associated with "This table defines the TCP ports associated with
TN3270E servers. No entry in this table shall exist TN3270E servers. No entry in this table shall exist
without a corresponding (same tn3270eSrvrConfIndex) without a corresponding (same tn3270eSrvrConfIndex)
entry in the tn3270eSrvrConfTable existing. entry in the tn3270eSrvrConfTable existing.
skipping to change at page 19, line 13 skipping to change at page 19, line 38
INDEX { INDEX {
tn3270eSrvrConfIndex, tn3270eSrvrConfIndex,
tn3270eSrvrPort, tn3270eSrvrPort,
tn3270eSrvrPortAddrType, tn3270eSrvrPortAddrType,
tn3270eSrvrPortAddress tn3270eSrvrPortAddress
} }
::= { tn3270eSrvrPortTable 1 } ::= { tn3270eSrvrPortTable 1 }
Tn3270eSrvrPortEntry ::= SEQUENCE { Tn3270eSrvrPortEntry ::= SEQUENCE {
tn3270eSrvrPort Unsigned32, tn3270eSrvrPort Unsigned32,
tn3270eSrvrPortAddrType Tn3270eAddrType, tn3270eSrvrPortAddrType IANATn3270eAddrType,
tn3270eSrvrPortAddress Tn3270eTAddress, tn3270eSrvrPortAddress Tn3270eTAddress,
tn3270eSrvrPortRowStatus RowStatus tn3270eSrvrPortRowStatus RowStatus
} }
tn3270eSrvrPort OBJECT-TYPE tn3270eSrvrPort OBJECT-TYPE
SYNTAX Unsigned32 (0..65535) SYNTAX Unsigned32 (0..65535)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates a port assigned to a server." "Indicates a port assigned to a server."
::= { tn3270eSrvrPortEntry 1 } ::= { tn3270eSrvrPortEntry 1 }
tn3270eSrvrPortAddrType OBJECT-TYPE tn3270eSrvrPortAddrType OBJECT-TYPE
SYNTAX Tn3270eAddrType SYNTAX IANATn3270eAddrType
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the type of an address local to the host on "Indicates the type of an address local to the host on
which the TN3270E server resides that is represented which the TN3270E server resides that is represented
in tn3270eSrvrPortAddress. A value of unknown(0) in tn3270eSrvrPortAddress. A value of unknown(0)
SHALL be used for this object when the port is not SHALL be used for this object when the port is not
to be restricted to a local address." to be restricted to a local address."
::= { tn3270eSrvrPortEntry 2 } ::= { tn3270eSrvrPortEntry 2 }
skipping to change at page 20, line 48 skipping to change at page 21, line 18
DESCRIPTION DESCRIPTION
"A collection of statistical and maximum usage objects "A collection of statistical and maximum usage objects
for a single TN3270 server. An entry can represent the total for a single TN3270 server. An entry can represent the total
activity of the server, or it can represent the activity activity of the server, or it can represent the activity
occurring at the server on either a port or a occurring at the server on either a port or a
port-and-local-address basis. port-and-local-address basis.
Collection of the statistics represented by the objects Collection of the statistics represented by the objects
in this table is not mandatory. An implementation in this table is not mandatory. An implementation
of this table MUST use only one of the three levels of of this table MUST use only one of the three levels of
refinement that this table supports. refinement that this table supports for the entries
associated with each TN3270E server.
The indexing for a row that represents total server The indexing for a row that represents total server
statistics is as follows: statistics is as follows:
tn3270eSrvrConfIndex value identifying the server tn3270eSrvrConfIndex value identifying the server
tn3270eSrvrPort 0 tn3270eSrvrPort 0
tn3270eSrvrPortAddrType unknown(0) tn3270eSrvrPortAddrType unknown(0)
tn3270eSrvrPortAddress zero-length octet string. tn3270eSrvrPortAddress zero-length octet string.
On a port basis: On a port basis:
skipping to change at page 21, line 28 skipping to change at page 21, line 54
INDEX { INDEX {
tn3270eSrvrConfIndex, tn3270eSrvrConfIndex,
tn3270eSrvrPort, tn3270eSrvrPort,
tn3270eSrvrPortAddrType, tn3270eSrvrPortAddrType,
tn3270eSrvrPortAddress tn3270eSrvrPortAddress
} }
::= { tn3270eSrvrStatsTable 1 } ::= { tn3270eSrvrStatsTable 1 }
Tn3270eSrvrStatsEntry ::= SEQUENCE { Tn3270eSrvrStatsEntry ::= SEQUENCE {
tn3270eSrvrStatsUpTime TimeStamp, tn3270eSrvrStatsUpTime TimeStamp,
tn3270eSrvrStatsMaxLus Unsigned32, tn3270eSrvrStatsMaxTerms Unsigned32,
tn3270eSrvrStatsInUseLus Gauge32, tn3270eSrvrStatsInUseTerms Gauge32,
tn3270eSrvrStatsSpareLus Gauge32, tn3270eSrvrStatsSpareTerms Gauge32,
tn3270eSrvrStatsMaxPtrs Unsigned32, tn3270eSrvrStatsMaxPtrs Unsigned32,
tn3270eSrvrStatsInUsePtrs Gauge32, tn3270eSrvrStatsInUsePtrs Gauge32,
tn3270eSrvrStatsSparePtrs Gauge32, tn3270eSrvrStatsSparePtrs Gauge32,
tn3270eSrvrStatsInConnects Counter32, tn3270eSrvrStatsInConnects Counter32,
tn3270eSrvrStatsConnRejects Counter32, tn3270eSrvrStatsConnResrceRejs Counter32,
tn3270eSrvrStatsDisconnects Counter32, tn3270eSrvrStatsDisconnects Counter32,
tn3270eSrvrStatsHCInOctets Counter64, tn3270eSrvrStatsHCInOctets Counter64,
tn3270eSrvrStatsInOctets Counter32, tn3270eSrvrStatsInOctets Counter32,
tn3270eSrvrStatsHCOutOctets Counter64, tn3270eSrvrStatsHCOutOctets Counter64,
tn3270eSrvrStatsOutOctets Counter32 tn3270eSrvrStatsOutOctets Counter32,
tn3270eSrvrStatsConnErrorRejs Counter32
} }
tn3270eSrvrStatsUpTime OBJECT-TYPE tn3270eSrvrStatsUpTime OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of the sysUpTime object the last time "The value of the sysUpTime object the last time
the TN3270E server was re-initialized. the TN3270E server was re-initialized.
Server re-initialization is the only discontinuity Server re-initialization is the only discontinuity
event for the counters in this table. Even if table event for the counters in this table. Even if table
entries are on a port or port-and-local-address entries are on a port or port-and-local-address
basis, port deactivation and reactivation do not basis, port deactivation and reactivation do not
result in counter discontinuities." result in counter discontinuities."
::= { tn3270eSrvrStatsEntry 2 } ::= { tn3270eSrvrStatsEntry 2 }
tn3270eSrvrStatsMaxLus OBJECT-TYPE tn3270eSrvrStatsMaxTerms OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "LUs" UNITS "LUs"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the maximum number of LUs available for "Indicates the maximum number of terminal LUs available
use at a TN3270E server for the granularity of this for use at a TN3270E server for the granularity of this
conceptual row (server-wide, port, or conceptual row (server-wide, port, or
port-and-local-address)." port-and-local-address)."
::= { tn3270eSrvrStatsEntry 3 } ::= { tn3270eSrvrStatsEntry 3 }
tn3270eSrvrStatsInUseLus OBJECT-TYPE tn3270eSrvrStatsInUseTerms OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
UNITS "LUs" UNITS "LUs"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the number of LUs currently in use "Indicates the number of terminal LUs currently in
at a TN3270E server for the granularity of this use at a TN3270E server for the granularity of this
conceptual row (server-wide, port, or conceptual row (server-wide, port, or
port-and-local-address)." port-and-local-address)."
::= { tn3270eSrvrStatsEntry 4 } ::= { tn3270eSrvrStatsEntry 4 }
tn3270eSrvrStatsSpareLus OBJECT-TYPE tn3270eSrvrStatsSpareTerms OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
UNITS "LUs" UNITS "LUs"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the number of free LUs at a TN3270E "Indicates the number of free terminal LUs at a TN3270E
server for the granularity of this conceptual server for the granularity of this conceptual row
row (server-wide, port, or port-and-local-address). (server-wide, port, or port-and-local-address).
It is possible that the difference between It is possible that the difference between
tn3270eSrvrStatsMaxLus and tn3270eSrvrStatsInUseLus tn3270eSrvrStatsMaxTerms and tn3270eSrvrStatsInUseTerms
in a conceptual row does not equal the value of in a conceptual row does not equal the value of
tn3270eSrvrStatsSpareLus in that row: an LU may tn3270eSrvrStatsSpareTerms in that row: an LU may
exist but not be usable by a client connection." exist but not be usable by a client connection.
Alternatively, the administrative ceiling represented
by tn3270eSrvrStatsMaxTerms may have been lowered to
a point where it is less than the current value of
tn3270eSrvrStatsInUseTerms. In this case
tn3270eSrvrStatsSpareTerms returns the value 0."
::= { tn3270eSrvrStatsEntry 5 } ::= { tn3270eSrvrStatsEntry 5 }
tn3270eSrvrStatsMaxPtrs OBJECT-TYPE tn3270eSrvrStatsMaxPtrs OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "Printer Resources" UNITS "Printer Resources"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the maximum number of printer resources "Indicates the maximum number of printer resources
available for use by a TN3270E server for the available for use by a TN3270E server for the
skipping to change at page 23, line 28 skipping to change at page 24, line 7
DESCRIPTION DESCRIPTION
"Indicates the number of free printer resources at "Indicates the number of free printer resources at
a TN3270E server for the granularity of this conceptual a TN3270E server for the granularity of this conceptual
row (server-wide, port, or port-and-local-address). row (server-wide, port, or port-and-local-address).
It is possible that the difference between It is possible that the difference between
tn3270eSrvrStatsMaxPtrs and tn3270eSrvrStatsInUsePtrs tn3270eSrvrStatsMaxPtrs and tn3270eSrvrStatsInUsePtrs
in a conceptual row does not equal the value of in a conceptual row does not equal the value of
tn3270eSrvrStatsSparePtrs in that row: a printer tn3270eSrvrStatsSparePtrs in that row: a printer
resource may exist but not be usable by a client resource may exist but not be usable by a client
connection." connection.
Alternatively, the administrative ceiling represented
by tn3270eSrvrStatsMaxPtrs may have been lowered to
a point where it is less than the current value of
tn3270eSrvrStatsInUsePtrs. In this case
tn3270eSrvrStatsSparePtrs returns the value 0."
::= { tn3270eSrvrStatsEntry 8 } ::= { tn3270eSrvrStatsEntry 8 }
tn3270eSrvrStatsInConnects OBJECT-TYPE tn3270eSrvrStatsInConnects OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "connections" UNITS "connections"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the number of client (TCP) connections "Indicates the number of client (TCP) connections
that succeeded at a TN3270E server for the that succeeded at a TN3270E server for the
granularity of this conceptual row (server-wide, granularity of this conceptual row (server-wide,
port, or port-and-local-address). The port, or port-and-local-address).
tn3270eSrvrStatsConnRejects object provides a count
The tn3270eSrvrStatsConnResrceRejs and
tn3270eSrvrStatsConnErrorRejs objects provide a count
of failed connection attempts. of failed connection attempts.
A Management Station can detect discontinuities in A Management Station can detect discontinuities in
this counter by monitoring the tn3270eSrvrStatsUpTime this counter by monitoring the tn3270eSrvrStatsUpTime
object." object."
::= { tn3270eSrvrStatsEntry 9 } ::= { tn3270eSrvrStatsEntry 9 }
tn3270eSrvrStatsConnRejects OBJECT-TYPE tn3270eSrvrStatsConnResrceRejs OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "connection attempts" UNITS "connection attempts"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the number of (TCP) connections rejected "Indicates the number of (TCP) connections rejected
during connection setup at a TN3270E server for the during connection setup at a TN3270E server for the
granularity of this conceptual row (server-wide, granularity of this conceptual row (server-wide,
port, or port-and-local-address). An example of port, or port-and-local-address) due to a lack of
when this counter would be incremented is when no LU resources at the server. An example of when this
counter would be incremented is when no terminal
or printer resource is available to associate with a or printer resource is available to associate with a
client's TCP connection. client's TCP connection.
A Management Station can detect discontinuities in A Management Station can detect discontinuities in
this counter by monitoring the tn3270eSrvrStatsUpTime this counter by monitoring the tn3270eSrvrStatsUpTime
object." object."
::= { tn3270eSrvrStatsEntry 10 } ::= { tn3270eSrvrStatsEntry 10 }
tn3270eSrvrStatsDisconnects OBJECT-TYPE tn3270eSrvrStatsDisconnects OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
skipping to change at page 25, line 34 skipping to change at page 26, line 22
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Low-order 32 bits of tn3270eSrvrStatsHCOutOctets for "Low-order 32 bits of tn3270eSrvrStatsHCOutOctets for
this conceptual row. this conceptual row.
A Management Station can detect discontinuities in A Management Station can detect discontinuities in
this counter by monitoring the tn3270eSrvrStatsUpTime this counter by monitoring the tn3270eSrvrStatsUpTime
object." object."
::= { tn3270eSrvrStatsEntry 15 } ::= { tn3270eSrvrStatsEntry 15 }
tn3270eSrvrStatsConnErrorRejs OBJECT-TYPE
SYNTAX Counter32
UNITS "connection attempts"
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"Indicates the number of (TCP) connections rejected
during connection setup at a TN3270E server for the
granularity of this conceptual row (server-wide,
port, or port-and-local-address) due to an error
of some type. An example of when this counter would
be incremented is when the client and the server
cannot agree on a common set of TN3270E functions for
the connection.
A Management Station can detect discontinuities in
this counter by monitoring the tn3270eSrvrStatsUpTime
object."
::= { tn3270eSrvrStatsEntry 16 }
tn3270eClientGroupTable OBJECT-TYPE tn3270eClientGroupTable OBJECT-TYPE
SYNTAX SEQUENCE OF Tn3270eClientGroupEntry SYNTAX SEQUENCE OF Tn3270eClientGroupEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table defines client address groupings for use "This table defines client address groupings for use
by a TN3270E server. by a TN3270E server.
No entry in this table shall exist without No entry in this table shall exist without
a corresponding (same tn3270eSrvrConfIndex) entry in a corresponding (same tn3270eSrvrConfIndex) entry in
skipping to change at page 26, line 13 skipping to change at page 27, line 21
tn3270eSrvrConfIndex and tn3270eClientGroupName, are tn3270eSrvrConfIndex and tn3270eClientGroupName, are
considered to be in the same client group." considered to be in the same client group."
INDEX { tn3270eSrvrConfIndex, INDEX { tn3270eSrvrConfIndex,
tn3270eClientGroupName, tn3270eClientGroupName,
tn3270eClientGroupAddrType, tn3270eClientGroupAddrType,
tn3270eClientGroupAddress } tn3270eClientGroupAddress }
::= { tn3270eClientGroupTable 1 } ::= { tn3270eClientGroupTable 1 }
Tn3270eClientGroupEntry ::= SEQUENCE { Tn3270eClientGroupEntry ::= SEQUENCE {
tn3270eClientGroupName Utf8String, tn3270eClientGroupName Utf8String,
tn3270eClientGroupAddrType Tn3270eAddrType, tn3270eClientGroupAddrType IANATn3270eAddrType,
tn3270eClientGroupAddress Tn3270eTAddress, tn3270eClientGroupAddress Tn3270eTAddress,
tn3270eClientGroupSubnetMask IpAddress, tn3270eClientGroupSubnetMask IpAddress,
tn3270eClientGroupPfxLength Unsigned32, tn3270eClientGroupPfxLength Unsigned32,
tn3270eClientGroupRowStatus RowStatus tn3270eClientGroupRowStatus RowStatus
} }
tn3270eClientGroupName OBJECT-TYPE tn3270eClientGroupName OBJECT-TYPE
SYNTAX Utf8String (SIZE(1..24)) SYNTAX Utf8String (SIZE(1..24))
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The name of a client group. Note: client group "The name of a client group. Note: client group
names are required to be unique only with respect names are required to be unique only with respect
to a single TN3270E server." to a single TN3270E server."
::= { tn3270eClientGroupEntry 1 } ::= { tn3270eClientGroupEntry 1 }
tn3270eClientGroupAddrType OBJECT-TYPE tn3270eClientGroupAddrType OBJECT-TYPE
SYNTAX Tn3270eAddrType SYNTAX IANATn3270eAddrType
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the type of the address represented in "Indicates the type of the address represented in
tn3270eClientGroupAddress." tn3270eClientGroupAddress."
::= { tn3270eClientGroupEntry 2 } ::= { tn3270eClientGroupEntry 2 }
tn3270eClientGroupAddress OBJECT-TYPE tn3270eClientGroupAddress OBJECT-TYPE
SYNTAX Tn3270eTAddress SYNTAX Tn3270eTAddress
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
skipping to change at page 32, line 36 skipping to change at page 33, line 44
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Definition of the mapping of a Resource Element to "Definition of the mapping of a Resource Element to
a client address." a client address."
INDEX { tn3270eSrvrConfIndex, INDEX { tn3270eSrvrConfIndex,
tn3270eResMapElementName } tn3270eResMapElementName }
::= { tn3270eResMapTable 1 } ::= { tn3270eResMapTable 1 }
Tn3270eResMapEntry ::= SEQUENCE { Tn3270eResMapEntry ::= SEQUENCE {
tn3270eResMapElementName SnaResourceName, tn3270eResMapElementName SnaResourceName,
tn3270eResMapAddrType Tn3270eAddrType, tn3270eResMapAddrType IANATn3270eAddrType,
tn3270eResMapAddress Tn3270eTAddress, tn3270eResMapAddress Tn3270eTAddress,
tn3270eResMapPort Unsigned32, tn3270eResMapPort Unsigned32,
tn3270eResMapElementType Tn3270ResourceType, tn3270eResMapElementType Tn3270ResourceType,
tn3270eResMapSscpSuppliedName SnaResourceName tn3270eResMapSscpSuppliedName SnaResourceName
} }
tn3270eResMapElementName OBJECT-TYPE tn3270eResMapElementName OBJECT-TYPE
SYNTAX SnaResourceName SYNTAX SnaResourceName
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The name of a resource element. This is the name by "The name of a resource element. This is the name by
which the server implementing this table knows the which the server implementing this table knows the
resource. It may be different from the name by which resource. It may be different from the name by which
the resource is known in the SNA network. This latter the resource is known in the SNA network. This latter
name is returned in the tn3270eResMapSscpSuppliedName name is returned in the tn3270eResMapSscpSuppliedName
object." object."
::= { tn3270eResMapEntry 1 } ::= { tn3270eResMapEntry 1 }
tn3270eResMapAddrType OBJECT-TYPE tn3270eResMapAddrType OBJECT-TYPE
SYNTAX Tn3270eAddrType SYNTAX IANATn3270eAddrType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the type of the client address represented "Indicates the type of the client address represented
in tn3270eResMapAddress." in tn3270eResMapAddress."
::= { tn3270eResMapEntry 2 } ::= { tn3270eResMapEntry 2 }
tn3270eResMapAddress OBJECT-TYPE tn3270eResMapAddress OBJECT-TYPE
SYNTAX Tn3270eTAddress SYNTAX Tn3270eTAddress
MAX-ACCESS read-only MAX-ACCESS read-only
skipping to change at page 34, line 38 skipping to change at page 35, line 46
tn3270eTcpConnRemPort, tn3270eTcpConnRemPort,
tn3270eTcpConnLocalAddrType, tn3270eTcpConnLocalAddrType,
tn3270eTcpConnLocalAddress, tn3270eTcpConnLocalAddress,
tn3270eTcpConnLocalPort tn3270eTcpConnLocalPort
} }
::= { tn3270eTcpConnTable 1 } ::= { tn3270eTcpConnTable 1 }
Tn3270eTcpConnEntry ::= Tn3270eTcpConnEntry ::=
SEQUENCE SEQUENCE
{ {
tn3270eTcpConnRemAddrType Tn3270eAddrType, tn3270eTcpConnRemAddrType IANATn3270eAddrType,
tn3270eTcpConnRemAddress Tn3270eTAddress, tn3270eTcpConnRemAddress Tn3270eTAddress,
tn3270eTcpConnRemPort Unsigned32, tn3270eTcpConnRemPort Unsigned32,
tn3270eTcpConnLocalAddrType Tn3270eAddrType, tn3270eTcpConnLocalAddrType IANATn3270eAddrType,
tn3270eTcpConnLocalAddress Tn3270eTAddress, tn3270eTcpConnLocalAddress Tn3270eTAddress,
tn3270eTcpConnLocalPort Unsigned32, tn3270eTcpConnLocalPort Unsigned32,
tn3270eTcpConnLastActivity TimeTicks, tn3270eTcpConnLastActivity TimeTicks,
tn3270eTcpConnBytesIn Counter32, tn3270eTcpConnBytesIn Counter32,
tn3270eTcpConnBytesOut Counter32, tn3270eTcpConnBytesOut Counter32,
tn3270eTcpConnResourceElement SnaResourceName, tn3270eTcpConnResourceElement SnaResourceName,
tn3270eTcpConnResourceType Tn3270ResourceType, tn3270eTcpConnResourceType Tn3270ResourceType,
tn3270eTcpConnDeviceType Tn3270DeviceTypes, tn3270eTcpConnDeviceType Tn3270DeviceTypes,
tn3270eTcpConnFunctions IANATn3270Functions, tn3270eTcpConnFunctions IANATn3270Functions,
tn3270eTcpConnId Unsigned32, tn3270eTcpConnId Unsigned32,
skipping to change at page 35, line 9 skipping to change at page 36, line 17
tn3270eTcpConnTraceData Tn3270eTraceData, tn3270eTcpConnTraceData Tn3270eTraceData,
tn3270eTcpConnLogInfo IANATn3270eLogData, tn3270eTcpConnLogInfo IANATn3270eLogData,
tn3270eTcpConnLuLuBindImage OCTET STRING, tn3270eTcpConnLuLuBindImage OCTET STRING,
tn3270eTcpConnSnaState INTEGER, tn3270eTcpConnSnaState INTEGER,
tn3270eTcpConnStateLastDiscReason INTEGER, tn3270eTcpConnStateLastDiscReason INTEGER,
tn3270eTcpConnSrvrConfIndex Unsigned32, tn3270eTcpConnSrvrConfIndex Unsigned32,
tn3270eTcpConnActivationTime TimeStamp tn3270eTcpConnActivationTime TimeStamp
} }
tn3270eTcpConnRemAddrType OBJECT-TYPE tn3270eTcpConnRemAddrType OBJECT-TYPE
SYNTAX Tn3270eAddrType SYNTAX IANATn3270eAddrType
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the type of the value of the "Indicates the type of the value of the
tn3270eTcpConnRemAddress object. For example, tn3270eTcpConnRemAddress object. For example,
ipv4(1) or ipv6(2)." ipv4(1) or ipv6(2)."
::= { tn3270eTcpConnEntry 1 } ::= { tn3270eTcpConnEntry 1 }
tn3270eTcpConnRemAddress OBJECT-TYPE tn3270eTcpConnRemAddress OBJECT-TYPE
SYNTAX Tn3270eTAddress SYNTAX Tn3270eTAddress
skipping to change at page 35, line 47 skipping to change at page 36, line 55
DESCRIPTION DESCRIPTION
"The remote port associated with a TN3270E client. "The remote port associated with a TN3270E client.
If a TN3270(E) client is connected to its If a TN3270(E) client is connected to its
server via a proxy client the port represented by server via a proxy client the port represented by
the value of this object shall be the remote client's the value of this object shall be the remote client's
port, not the proxy client's port." port, not the proxy client's port."
::= { tn3270eTcpConnEntry 3 } ::= { tn3270eTcpConnEntry 3 }
tn3270eTcpConnLocalAddrType OBJECT-TYPE tn3270eTcpConnLocalAddrType OBJECT-TYPE
SYNTAX Tn3270eAddrType SYNTAX IANATn3270eAddrType
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the type of the value of the "Indicates the type of the value of the
tn3270eTcpConnLocalAddress object. For example, tn3270eTcpConnLocalAddress object. For example,
ipv4(1) or ipv6(2)." ipv4(1) or ipv6(2)."
::= { tn3270eTcpConnEntry 4 } ::= { tn3270eTcpConnEntry 4 }
tn3270eTcpConnLocalAddress OBJECT-TYPE tn3270eTcpConnLocalAddress OBJECT-TYPE
SYNTAX Tn3270eTAddress SYNTAX Tn3270eTAddress
skipping to change at page 39, line 16 skipping to change at page 40, line 24
REFERENCE REFERENCE
"'Systems Network Architecture Formats', IBM "'Systems Network Architecture Formats', IBM
Publication GA27-3136." Publication GA27-3136."
::= { tn3270eTcpConnEntry 19 } ::= { tn3270eTcpConnEntry 19 }
tn3270eTcpConnSnaState OBJECT-TYPE tn3270eTcpConnSnaState OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
unknown(0), unknown(0),
noSluSession(1), noSluSession(1),
sscpLuSession(2), -- but no LU-LU session sscpLuSession(2), -- but no LU-LU session
luLuSession(3), luLuSession(3), -- but no SSCP-LU session
establishingSscpLuSession(4), sscpLuSessionAndLuLuSession(4)
establishingLuSession(5)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The current state of the SNA side of the end-to-end "The current state of the SNA side of the end-to-end
TN3270 connection. The following states are defined: TN3270 connection. The following states are defined:
unknown(0) - The true state is not known. unknown(0) - The true state is not known.
noSluSession(1) - The SLU has neither an SSCP-LU noSluSession(1) - The SLU has neither an SSCP-LU
nor an LU-LU session active. nor an LU-LU session active.
sscpLuSession(2) - The SSCP-LU session for the SLU sscpLuSession(2) - The SSCP-LU session for the SLU
is active, but the SLU is not is active, but the SLU is not
currently in session with a PLU. currently in session with a PLU.
luLuSession(3) - The SLU currently has an active luLuSession(3) - The SLU is currently in session
session with a PLU. with a PLU, but the SSCP-LU
establishingSscpLuSession(4) - Currently, disconnected session for the LU is not active.
and in the process of establishing sscpLuSessionAndLuLuSession(4) - The SLU currently has
an SSCP to LU session. an active session with a PLU,
establishingLuSession(5) - Currently, disconnected and the SSCP-LU session for the
and in the process of establishing SLU is active."
an LU to LU session."
::= { tn3270eTcpConnEntry 20 } ::= { tn3270eTcpConnEntry 20 }
tn3270eTcpConnStateLastDiscReason OBJECT-TYPE tn3270eTcpConnStateLastDiscReason OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
unknown(0), unknown(0),
hostSendsUnbind(1), hostSendsUnbind(1),
hostDontAcceptConnection(2), hostDontAcceptConnection(2),
outOfResource(3), outOfResource(3),
clientProtocolError(4), clientProtocolError(4),
invalidDeviceName(5), invalidDeviceName(5),
skipping to change at page 41, line 29 skipping to change at page 42, line 37
GROUP tn3270eHiCapacityGroup GROUP tn3270eHiCapacityGroup
DESCRIPTION DESCRIPTION
"This group is optional and provides for support "This group is optional and provides for support
of high capacity counters." of high capacity counters."
OBJECT tn3270eSrvrConfActivityCheck OBJECT tn3270eSrvrConfActivityCheck
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"The agent is not required to support a set to this "The agent is not required to support a set to this
object if the associated TN3270E server doesn't object if the associated TN3270E server doesn't
support either TIMEMARK or NOP processing. In support either TIMING-MARK or NOP processing. In
this case an agent should return noCheck on this case an agent should return noCheck on
retrieval." retrieval."
OBJECT tn3270eSrvrConfActivityTimeout OBJECT tn3270eSrvrConfTmNopInactTime
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"The agent is not required to support a set to this "The agent is not required to support a set to this
object if the functions enabled by object if the functions enabled by
tn3270eSrvrConfActivityCheck are not supported. tn3270eSrvrConfActivityCheck are not supported.
An agent in this case should return a value of 0." An agent in this case should return a value of 0."
OBJECT tn3270eSrvrConfActivityInterval OBJECT tn3270eSrvrConfTmNopInterval
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"The agent is not required to support a set to this "The agent is not required to support a set to this
object if the functions enabled by object if the functions enabled by
tn3270eSrvrConfActivityCheck are not supported. tn3270eSrvrConfActivityCheck are not supported.
An agent in this case should return a value of 0." An agent in this case should return a value of 0."
OBJECT tn3270eSrvrConfAdminStatus OBJECT tn3270eSrvrConfAdminStatus
DESCRIPTION DESCRIPTION
"A TN3270E server is not required to support a "A TN3270E server is not required to support a
stopImmediate state transition." stopImmediate state transition."
OBJECT tn3270eSrvrConfRowStatus OBJECT tn3270eSrvrConfRowStatus
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT tn3270eSrvrConfTmTimeout
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 tn3270eSrvrPortRowStatus OBJECT tn3270eSrvrPortRowStatus
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
OBJECT tn3270eClientGroupRowStatus OBJECT tn3270eClientGroupRowStatus
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required." "Write access is not required."
skipping to change at page 42, line 32 skipping to change at page 43, line 48
"Write access is not required." "Write access is not required."
::= { tn3270eCompliances 1 } ::= { tn3270eCompliances 1 }
-- units of conformance -- units of conformance
tn3270eBasicGroup OBJECT-GROUP tn3270eBasicGroup OBJECT-GROUP
OBJECTS { OBJECTS {
tn3270eSrvrConfInactivityTimeout, tn3270eSrvrConfInactivityTimeout,
tn3270eSrvrConfActivityCheck, tn3270eSrvrConfActivityCheck,
tn3270eSrvrConfActivityTimeout, tn3270eSrvrConfTmNopInactTime,
tn3270eSrvrConfActivityInterval, tn3270eSrvrConfTmNopInterval,
tn3270eSrvrFunctionsSupported, tn3270eSrvrFunctionsSupported,
tn3270eSrvrConfAdminStatus, tn3270eSrvrConfAdminStatus,
tn3270eSrvrConfOperStatus, tn3270eSrvrConfOperStatus,
tn3270eSrvrConfSessionTermState, tn3270eSrvrConfSessionTermState,
tn3270eSrvrConfSrvrType, tn3270eSrvrConfSrvrType,
tn3270eSrvrConfContact, tn3270eSrvrConfContact,
tn3270eSrvrConfRowStatus, tn3270eSrvrConfRowStatus,
tn3270eSrvrConfLastActTime, tn3270eSrvrConfLastActTime,
tn3270eSrvrConfTmTimeout,
tn3270eSrvrPortRowStatus, tn3270eSrvrPortRowStatus,
tn3270eSrvrStatsUpTime, tn3270eSrvrStatsUpTime,
tn3270eSrvrStatsMaxLus, tn3270eSrvrStatsMaxTerms,
tn3270eSrvrStatsInUseLus, tn3270eSrvrStatsInUseTerms,
tn3270eSrvrStatsSpareLus, tn3270eSrvrStatsSpareTerms,
tn3270eSrvrStatsMaxPtrs, tn3270eSrvrStatsMaxPtrs,
tn3270eSrvrStatsInUsePtrs, tn3270eSrvrStatsInUsePtrs,
tn3270eSrvrStatsSparePtrs, tn3270eSrvrStatsSparePtrs,
tn3270eSrvrStatsInConnects, tn3270eSrvrStatsInConnects,
tn3270eSrvrStatsConnRejects, tn3270eSrvrStatsConnResrceRejs,
tn3270eSrvrStatsDisconnects, tn3270eSrvrStatsDisconnects,
tn3270eSrvrStatsInOctets, tn3270eSrvrStatsInOctets,
tn3270eSrvrStatsOutOctets, tn3270eSrvrStatsOutOctets,
tn3270eSrvrStatsConnErrorRejs,
tn3270eClientGroupSubnetMask, tn3270eClientGroupSubnetMask,
tn3270eClientGroupPfxLength, tn3270eClientGroupPfxLength,
tn3270eClientGroupRowStatus, tn3270eClientGroupRowStatus,
tn3270eSnaMapLocalName, tn3270eSnaMapLocalName,
tn3270eSnaMapPrimaryLuName, tn3270eSnaMapPrimaryLuName,
tn3270eConfSpinLock tn3270eConfSpinLock
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This group is mandatory for all hosts supporting the "This group is mandatory for all hosts supporting the
skipping to change at page 46, line 52 skipping to change at page 48, line 22
[13] Postel, J., and Reynolds, J., "Telnet Timing Mark Option", RFC 860, [13] Postel, J., and Reynolds, J., "Telnet Timing Mark Option", RFC 860,
May 1983. May 1983.
[14] Rekhter, J., "Telnet 3270 Regime Option", RFC 1041, January 1988. [14] Rekhter, J., "Telnet 3270 Regime Option", RFC 1041, January 1988.
[15] Kelly, B., "TN3270 Enhancements", RFC 1647, July 1994. [15] Kelly, B., "TN3270 Enhancements", RFC 1647, July 1994.
[16] McCloghrie, K., "TCP-MIB Definitions", RFC 2012, November 1996. [16] McCloghrie, K., "TCP-MIB Definitions", RFC 2012, November 1996.
[17] IBM, International Technical Support Centers, "Response Time Data [17] Hovey, R., and S. Bradner, "The Organizations Involved in the IETF
Gathering", GG24-3212-01, November 1990.
[18] Hovey, R., and S. Bradner, "The Organizations Involved in the IETF
Standards Process", BCP 11, RFC 2028, October 1996. Standards Process", BCP 11, RFC 2028, October 1996.
[19] Bradner, S., "Key words for use in RFCs to Indicate Requirement [18] 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.
[20] Hinden, R., Deering, S., "IP Version 6 Addressing Architecture", [19] Hinden, R., Deering, S., "IP Version 6 Addressing Architecture",
<draft-ietf-ipngwg-addr-arch-v2-02.txt>, July 16, 1997. <draft-ietf-ipngwg-addr-arch-v2-02.txt>, July 16, 1997.
[21] Krupczak, Cheryl, Saperia, Jonathan, "Definitions of System-Level [20] Krupczak, Cheryl, Saperia, Jonathan, "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
skipping to change at page 49, line 55 skipping to change at page 50, line 55
The above list of contacts can be altered with The above list of contacts can be altered with
the approval of the two co-chairs. the approval of the two co-chairs.
The Textual Conventions defined within this MIB have The Textual Conventions defined within this MIB have
no security issues associated with them unless no security issues associated with them unless
explicitly stated in their corresponding explicitly stated in their corresponding
DESCRIPTION clause." DESCRIPTION clause."
-- IANA will assign a real OID when they take over this module. -- IANA will assign a real OID when they take over this module.
::= { experimental 2001 } ::= { 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
usually used to indicate that no actual address is
present."
SYNTAX INTEGER {
unknown(0),
ipv4(1),
ipv6(2)
}
IANATn3270Functions ::= TEXTUAL-CONVENTION IANATn3270Functions ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This textual convention reflects the current set of "This textual convention reflects the current set of
TN3270 and TN3270E functions that can be negotiated TN3270 and TN3270E functions that can be negotiated
between a server and its client: between a server and its client:
RFC856 RFC856
transmitBinary The sender of this command REQUESTS transmitBinary The sender of this command REQUESTS
permission to begin transmitting, or permission to begin transmitting, or
confirms that it will now begin confirms that it will now begin
transmitting characters which are to transmitting characters which are to
be interpreted as 8 bits of binary be interpreted as 8 bits of binary
data by the receiver of the data. data by the receiver of the data.
RFC820 RFC860
timeMark The sender of this command REQUESTS timingMark The sender of this command REQUESTS
that the receiver of this command that the receiver of this command
return a WILL TIMING-MARK in the data return a WILL TIMING-MARK in the data
stream at the 'appropriate place' ... stream at the 'appropriate place'.
RFC885 RFC885
endOfRecord The sender of this command requests endOfRecord The sender of this command requests
permission to begin transmission of permission to begin transmission of
the Telnet END-OF-RECORD (EOR) code the Telnet END-OF-RECORD (EOR) code
when transmitting data characters, or when transmitting data characters, or
the sender of this command confirms it the sender of this command confirms it
will now begin transmission of EORs will now begin transmission of EORs
with transmitted data characters. with transmitted data characters.
RFC1091 RFC1091
terminalType Sender is willing to send terminal terminalType Sender is willing to send terminal
skipping to change at page 52, line 30 skipping to change at page 53, line 45
TimeStamp = A 4-octet field representing the number of TimeStamp = A 4-octet field representing the number of
TimeTicks since the TN3270E server was last TimeTicks since the TN3270E server was last
activated. The server's last activation time activated. The server's last activation time
is available in the tn3270eSrvrConfLastActTime is available in the tn3270eSrvrConfLastActTime
object in the TN3270E MIB, which has the object in the TN3270E MIB, which has the
syntax DateAndTime. syntax DateAndTime.
data = initial part of a PDU. data = initial part of a PDU.
length type length type
0-250 x'00' - unknown 0-255 x'00' - unknown
0 x'01' - inactivity timer expired 0 x'01' - inactivity timer expired
0 x'02' - dynamic timer expired 0 x'02' - dynamic timer expired
0 x'03' - actlu req 0 x'03' - actlu req
0 x'04' - bind req 0 x'04' - bind req
0 x'05' - clear req 0 x'05' - clear req
0 x'06' - dactlu req 0 x'06' - dactlu req
0 x'07' - warm actpu req 0 x'07' - warm actpu req
0 x'08' - sdt req 0 x'08' - sdt req
0 x'09' - unbind req 0 x'09' - unbind req
0 x'0A' - notify resp 0 x'0A' - notify resp
skipping to change at page 52, line 56 skipping to change at page 54, line 17
0 x'10' - client disconnect req 0 x'10' - client disconnect req
0 x'11' - timingmark received 0 x'11' - timingmark received
0 x'12' - flowControl timer expired 0 x'12' - flowControl timer expired
0 x'13' - neg rsp to host 0 x'13' - neg rsp to host
0 x'14' - neg rsp from host 0 x'14' - neg rsp from host
0 x'15' - data contention 0 x'15' - data contention
0 x'16' - no buffer to send SNA data 0 x'16' - no buffer to send SNA data
0 x'17' - receive response while inbound 0 x'17' - receive response while inbound
0 x'18' - client protocol error 0 x'18' - client protocol error
0 x'19' - badClientSequenceReceived 0 x'19' - badClientSequenceReceived
1-250 x'1A' - utf8String 1-255 x'1A' - utf8String
2 x'1B' - hexCode, implementation dependent 2 x'1B' - hexCode, implementation dependent
log event entries have a minimum length of 6 octets. log event entries have a minimum length of 6 octets.
The zero-length string indicates that no log data is The zero-length string indicates that no log data is
available." available."
SYNTAX OCTET STRING (SIZE (0 | 6..261)) SYNTAX OCTET STRING (SIZE (0 | 6..2048))
END END
 End of changes. 102 change blocks. 
171 lines changed or deleted 259 lines changed or added

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