draft-ietf-tn3270e-tn3270-mib-09.txt   draft-ietf-tn3270e-tn3270-mib-10.txt 
TN3270E Working Group Kenneth White TN3270E Working Group Kenneth White
INTERNET DRAFT: <draft-ietf-tn3270e-tn3270-mib-09.txt> IBM Corp. INTERNET DRAFT: <draft-ietf-tn3270e-tn3270-mib-10.txt> IBM Corp.
Expiration Date: December, 1998 Robert Moore Expiration Date: January, 1999 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-09.txt> <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 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 36 skipping to change at page 1, line 36
directory to learn the current status of this or any Internet Draft. directory to learn the current status of this or any Internet Draft.
Distribution of this document is unlimited. Distribution of this document is unlimited.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (1998). All Rights Reserved. Copyright (C) The Internet Society (1998). 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 1647 [15], refers and managing TN3270E servers. TN3270E, defined by RFC 2355 [19], 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 [18], RFC 854 [16], and RFC 860 [17] 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
typically 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
skipping to change at page 2, line 16 skipping to change at page 2, line 16
(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, a 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 the
role of a Dependent LU Requester (DLUR). Host and gateway TN3270E role of a Dependent LU Requester (DLUR). Host and gateway TN3270E
server implementations typically differ greatly as to their internal server implementations typically differ greatly as to their internal
implementation and system definition (SYSDEF) methods. 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.
Management Information (SMI) for Version 2 of the Simple Network
Management Protocol (refer to RFC1902 [3]).
Table of Contents Table of Contents
1.0 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 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 . . . . . . . . . . . . . . . . . . . . . 3 3.0 Structure of the MIB . . . . . . . . . . . . . . . . . . . . . 3
3.1 TN3270E Server Control . . . . . . . . . . . . . . . . . . . . 4 3.1 TN3270E Server Control . . . . . . . . . . . . . . . . . . . . 5
3.1.1 tn3270eSrvrConfTable . . . . . . . . . . . . . . . . . . . 5 3.1.1 tn3270eSrvrConfTable . . . . . . . . . . . . . . . . . . . 5
3.1.2 tn3270eSrvrPortTable . . . . . . . . . . . . . . . . . . . 6 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 . . . . . . . . . . . 7 3.3 Resource Name / Client Address Mappings . . . . . . . . . . . 7
3.3.1 tn3270eSnaMapTable . . . . . . . . . . . . . . . . . . . . 7 3.3.1 tn3270eSnaMapTable . . . . . . . . . . . . . . . . . . . . 7
3.3.2 tn3270eResMapTable . . . . . . . . . . . . . . . . . . . . 7 3.3.2 tn3270eResMapTable . . . . . . . . . . . . . . . . . . . . 8
3.3.3 tn3270eTcpConnTable . . . . . . . . . . . . . . . . . . . 8 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 . . . . . . . . . . . . . . . . . . . . . . . 9
3.6 IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 3.6 IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
4.0 Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 9 4.0 Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 9
5.0 Security Considerations . . . . . . . . . . . . . . . . . . . 46 5.0 Security Considerations . . . . . . . . . . . . . . . . . . . 45
6.0 Intellectual Property . . . . . . . . . . . . . . . . . . . . 46 6.0 Intellectual Property . . . . . . . . . . . . . . . . . . . . 46
7.0 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 47 7.0 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 46
8.0 References . . . . . . . . . . . . . . . . . . . . . . . . . . 47 8.0 References . . . . . . . . . . . . . . . . . . . . . . . . . . 46
9.0 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 48 9.0 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 48
10.0 Full Copyright Statement . . . . . . . . . . . . . . . . . . 49 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 [18]. 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 Network Management Framework presently consists of six major The SNMP Management Framework presently consists of five major
components. They are: components:
o the overall architecture, described in RFC 2271 [7].
o the SMI, described in RFC 1902 [3], - the mechanisms used for
describing and naming objects for the purpose of management.
o the MIB-II, STD 17, RFC 1213 [2], - the core set of managed objects o An overall architecture, described in RFC 2271 [1].
for the Internet suite of protocols.
o the protocol, RFC 1157 [1] and/or RFC 1905 [6] and/or RFC 2272 [8] o Mechanisms for describing and naming objects and events for the
-- the protocol for accessing managed information. purpose of management. The first version of this Structure of
Management Information (SMI) is called SMIv1 and described in RFC
1155 [2], RFC 1212 [3] and RFC 1215 [4]. The second version, called
SMIv2, is described in RFC 1902 [5], RFC 1903 [6] and RFC 1904 [7].
o the user-based security model defined in RFC 2274 [10]. o Message protocols for transferring management information. The
first version of the SNMP message protocol is called SNMPv1 and
described in RFC 1157 [8]. A second version of the SNMP message
protocol, which is not an Internet standards track protocol, is
called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10]. The
third version of the message protocol is called SNMPv3 and described
in RFC 1906 [10], RFC 2272 [11] and RFC 2274 [12].
o the view-based access control model defined in RFC 2275 [11]. o Protocol operations for accessing management information. The first
set of protocol operations and associated PDU formats is described
in RFC 1157 [8]. A second set of protocol operations and associated
PDU formats is described in RFC 1905 [13].
Textual conventions are defined in RFC 1903 [4], and conformance o A set of fundamental applications described in RFC 2273 [14] and the
statements are defined in RFC 1904 [5]. Common applications are defined view-based access control mechanism described in RFC 2275 [15].
in RFC 2273 [9].
The Framework permits new objects to be defined for the purpose of Managed objects are accessed via a virtual information store, termed the
experimentation and evaluation. Management Information Base or MIB. Objects in the MIB are 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 MIB
conforming to the SMIv1 can be produced through the appropriate conforming to the SMIv1 can be produced through the appropriate
translation. translations. The resulting translated MIB must be semantically
equivalent, except where objects or events are omitted because no
translation is possible (use of Counter64). Some machine readable
information in SMIv2 will be converted into textual descriptions in
SMIv1 during the translation process. However, this loss of machine
readable information is not considered to change the semantics of the
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 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 [20], 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 does
not. The SNMP-FRAMEWORK-MIB, reference [7], contains the 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 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, IANATn3270eAddrType and addressing. Two textual conventions, IANATn3270eAddrType and
Tn3270eTAddress, are defined for this purpose. IANATn3270eTAddress 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 IANATn3270eTAddress allows a difference between the two is that IANATn3270eAddress allows a
zero-length octet string, while TAddress doesn't. It is important that zero-length octet string, while TAddress doesn't. It is important that
IANATn3270eTAddress 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 for
skipping to change at page 5, line 36 skipping to change at page 5, line 43
for user traffic on TN3270 and TN3270E sessions. 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" as
defined by RFC 860 [13]. The object tn3270eSrvrConfConnectivityChk defined by RFC 860 [17]. The object tn3270eSrvrConfConnectivityChk
allows a Management Station to select either a NOP command or a allows a Management Station to select either a NOP command or a
TIMING-MARK command. Sending a NOP command results in less overhead TIMING-MARK command. Sending a NOP command results in less overhead
then a TIMING-MARK command, since a client doesn't send a reply. 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 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
skipping to change at page 8, line 14 skipping to change at page 8, line 19
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
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 [16], 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 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, Tn3270eAddress
and IANATn3270eAddrType object pairs are used to specify client and IANATn3270eAddrType object pairs are used to specify client
addresses (both local and remote). This enables support of IPv6 addresses (both local and remote). This enables support of IPv6
addresses. In addition, the remote address pair precedes the local addresses. In addition, the remote address pair precedes the local
address pair in the index clause, in order to enable a GET-NEXT address pair in the index clause, in order to enable a GET-NEXT
operation using only the 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
skipping to change at page 9, line 18 skipping to change at page 9, line 25
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
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 [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 well
as a number of objects identifying the types of various addresses, use as a number of objects identifying various address types, resource
textual conventions imported from the IANATn3270eTC-MIB. The purpose of types, and device types, use textual conventions imported from the
defining these textual conventions in a separate MIB module is to allow IANATn3270eTC-MIB. The purpose of defining these textual conventions in
additional values to be defined without having to issue a new version of a separate MIB module is to allow additional values to be defined
this document. The Internet Assigned Number Authority (IANA) is without having to issue a new version of this document. The Internet
responsible for the assignment of all Internet numbers, including Assigned Number Authority (IANA) is responsible for the assignment of
various SNMP-related numbers; it will administer the values associated all Internet numbers, including various SNMP-related numbers; it will
with these textual conventions. 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 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
IANA home page at: "http://www.iana.org/iana/". IANA home page at: "http://www.iana.org/iana/".
4.0 Definitions 4.0 Definitions
TN3270E-MIB DEFINITIONS ::= BEGIN TN3270E-MIB DEFINITIONS ::= BEGIN
skipping to change at page 9, line 58 skipping to change at page 10, line 10
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
IANATn3270eAddrType, IANATn3270eClientType, IANATn3270eAddrType, IANATn3270eAddress,
IANATn3270eLogData, IANATn3270Functions IANATn3270eClientType, IANATn3270Functions,
IANATn3270ResourceType, IANATn3270DeviceType,
IANATn3270eLogData
FROM IANATn3270eTC-MIB; FROM IANATn3270eTC-MIB;
tn3270eMIB MODULE-IDENTITY tn3270eMIB MODULE-IDENTITY
LAST-UPDATED "9806050000Z" -- June 5, 1998 LAST-UPDATED "9807270000Z" -- July 27, 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)
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
+1-919-254-4436" +1-919-254-4436"
DESCRIPTION DESCRIPTION
"This module defines a portion of the management "This module defines a portion of the management
information base (MIB) for managing TN3270E servers." information base (MIB) for managing TN3270E servers."
REVISION "9807270000Z" -- July 27, 1998
DESCRIPTION
"RFC nnnn (Proposed Standard)" -- RFC Editor to fill in
::= { snanauMIB 8 } ::= { snanauMIB 8 }
-- Textual Conventions -- Textual Conventions
SnaResourceName ::= TEXTUAL-CONVENTION SnaResourceName ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The textual convention for defining an SNA resource "The textual convention for defining an SNA resource
name. A fully qualified SNA resource name, consisting name. A fully qualified SNA resource name, consisting
of a 1 to 8 character network identifier (NetId), a of a 1 to 8 character network identifier (NetId), a
skipping to change at page 10, line 58 skipping to change at page 11, line 16
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))
Tn3270ResourceType ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"The type of resource defined by a resource pool. Refer
to tn3270eResPoolTable."
SYNTAX INTEGER {
other(0),
terminal(1),
printer(2),
terminalOrPrinter(3)
}
Tn3270eTAddress ::= 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
Tn3270eTAddress object is:
IANATn3270eAddrType Address Length
unknown(0) not specified or unknown;
the actual length of the
Tn3270eTAddress 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))
Tn3270DeviceTypes ::= TEXTUAL-CONVENTION
STATUS current
DESCRIPTION
"This textual convention defines the list of device
types that can be set, as defined by RFC 1647."
SYNTAX INTEGER { -- terminals
unknown(0),
ibm3278d2(1), -- (24 row x 80 col display)
ibm3278d2E(2), -- (24 row x 80 col display)
ibm3278d3(3), -- (32 row x 80 col display)
ibm3278d3E(4), -- (32 row x 80 col display)
ibm3278d4(5), -- (43 row x 80 col display)
ibm3278d4E(6), -- (43 row x 80 col display)
ibm3278d5(7), -- (27 row x 132 col display)
ibm3278d5E(8), -- (27 row x 132 col display)
ibmDynamic(9), -- (no pre-defined display size)
ibm3287d1(10) -- printers
}
Tn3270eTraceData ::= TEXTUAL-CONVENTION Tn3270eTraceData ::= TEXTUAL-CONVENTION
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:
skipping to change at page 14, line 19 skipping to change at page 13, line 32
is considered when determining whether there has been is considered when determining whether there has been
activity on a connection. activity on a connection.
The default value 0 means that no inactivity time-out is The default value 0 means that no inactivity time-out is
in effect." in effect."
DEFVAL { 0 } DEFVAL { 0 }
::= { tn3270eSrvrConfEntry 2 } ::= { tn3270eSrvrConfEntry 2 }
tn3270eSrvrConfConnectivityChk OBJECT-TYPE tn3270eSrvrConfConnectivityChk OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
noCheck(0),
timingMark(1), timingMark(1),
nop(2) nop(2),
noCheck(3)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object enables TIMING-MARK 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 }
tn3270eSrvrConfTmNopInactTime OBJECT-TYPE tn3270eSrvrConfTmNopInactTime OBJECT-TYPE
skipping to change at page 19, line 44 skipping to change at page 18, line 57
tn3270eSrvrConfIndex, tn3270eSrvrConfIndex,
tn3270eSrvrPort, tn3270eSrvrPort,
tn3270eSrvrPortAddrType, tn3270eSrvrPortAddrType,
tn3270eSrvrPortAddress tn3270eSrvrPortAddress
} }
::= { tn3270eSrvrPortTable 1 } ::= { tn3270eSrvrPortTable 1 }
Tn3270eSrvrPortEntry ::= SEQUENCE { Tn3270eSrvrPortEntry ::= SEQUENCE {
tn3270eSrvrPort Unsigned32, tn3270eSrvrPort Unsigned32,
tn3270eSrvrPortAddrType IANATn3270eAddrType, tn3270eSrvrPortAddrType IANATn3270eAddrType,
tn3270eSrvrPortAddress Tn3270eTAddress, tn3270eSrvrPortAddress IANATn3270eAddress,
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 }
skipping to change at page 20, line 14 skipping to change at page 19, line 27
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 }
tn3270eSrvrPortAddress OBJECT-TYPE tn3270eSrvrPortAddress OBJECT-TYPE
SYNTAX Tn3270eTAddress SYNTAX IANATn3270eAddress
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A local address on the host that a TN3270E server "A local address on the host that a TN3270E server
resides on that is associated with a TCP port that resides on that is associated with a TCP port that
is to be used or is in use by a TN3270E server. is to be used or is in use by a TN3270E server.
tn3270eClientGroupAddrType indicates the tn3270eClientGroupAddrType indicates the
address type (IPv4 or IPv6, for example). address type (IPv4 or IPv6, for example).
A zero-length octet string SHALL be used as the A zero-length octet string SHALL be used as the
skipping to change at page 27, line 28 skipping to change at page 26, line 39
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 IANATn3270eAddrType, tn3270eClientGroupAddrType IANATn3270eAddrType,
tn3270eClientGroupAddress Tn3270eTAddress, tn3270eClientGroupAddress IANATn3270eAddress,
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
skipping to change at page 27, line 54 skipping to change at page 27, line 11
tn3270eClientGroupAddrType OBJECT-TYPE tn3270eClientGroupAddrType OBJECT-TYPE
SYNTAX IANATn3270eAddrType 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 IANATn3270eAddress
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The client address of a member of a client group. "The client address of a member of a client group.
The value of tn3270eClientGroupAddrType indicates The value of tn3270eClientGroupAddrType indicates
the address type (IPv4 or IPv6, for example)." the address type (IPv4 or IPv6, for example)."
::= { tn3270eClientGroupEntry 3 } ::= { tn3270eClientGroupEntry 3 }
tn3270eClientGroupSubnetMask OBJECT-TYPE tn3270eClientGroupSubnetMask OBJECT-TYPE
SYNTAX IpAddress SYNTAX IpAddress
skipping to change at page 29, line 6 skipping to change at page 28, line 19
"RFC 1903, 'Textual Conventions for version 2 of the "RFC 1903, 'Textual Conventions for version 2 of the
Simple Network Management Protocol (SNMPv2).'" Simple Network Management Protocol (SNMPv2).'"
::= { tn3270eClientGroupEntry 6 } ::= { tn3270eClientGroupEntry 6 }
tn3270eResPoolTable OBJECT-TYPE tn3270eResPoolTable OBJECT-TYPE
SYNTAX SEQUENCE OF Tn3270eResPoolEntry SYNTAX SEQUENCE OF Tn3270eResPoolEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table defines resource groupings; the term "This table defines resource groupings; the term
'pool' is used as it is defined by RFC 1647. 'pool' is used as it is defined by RFC 2355.
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
the tn3270eSrvrConfTable existing. the tn3270eSrvrConfTable existing.
An implementation SHOULD NOT retain SNMP-created An implementation SHOULD NOT retain SNMP-created
entries in this table across re-IPLs (Initial Program entries in this table across re-IPLs (Initial Program
Loads) of the corresponding TN3270E server." Loads) of the corresponding TN3270E server."
::= { tn3270eObjects 5 } ::= { tn3270eObjects 5 }
skipping to change at page 29, line 33 skipping to change at page 28, line 46
with the same first two indexes, tn3270eSrvrConfIndex and with the same first two indexes, tn3270eSrvrConfIndex and
tn3270eResPoolName, are considered to be in the same pool." tn3270eResPoolName, are considered to be in the same pool."
INDEX { tn3270eSrvrConfIndex, INDEX { tn3270eSrvrConfIndex,
tn3270eResPoolName, tn3270eResPoolName,
tn3270eResPoolElementName } tn3270eResPoolElementName }
::= { tn3270eResPoolTable 1 } ::= { tn3270eResPoolTable 1 }
Tn3270eResPoolEntry ::= SEQUENCE { Tn3270eResPoolEntry ::= SEQUENCE {
tn3270eResPoolName Utf8String, tn3270eResPoolName Utf8String,
tn3270eResPoolElementName SnaResourceName, tn3270eResPoolElementName SnaResourceName,
tn3270eResPoolElementType Tn3270ResourceType, tn3270eResPoolElementType IANATn3270ResourceType,
tn3270eResPoolRowStatus RowStatus tn3270eResPoolRowStatus RowStatus
} }
tn3270eResPoolName OBJECT-TYPE tn3270eResPoolName 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 resource pool." "The name of a resource pool."
::= { tn3270eResPoolEntry 1 } ::= { tn3270eResPoolEntry 1 }
tn3270eResPoolElementName OBJECT-TYPE tn3270eResPoolElementName OBJECT-TYPE
SYNTAX SnaResourceName SYNTAX SnaResourceName
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The name of a member of a resource pool." "The name of a member of a resource pool."
::= { tn3270eResPoolEntry 2 } ::= { tn3270eResPoolEntry 2 }
tn3270eResPoolElementType OBJECT-TYPE tn3270eResPoolElementType OBJECT-TYPE
SYNTAX Tn3270ResourceType SYNTAX IANATn3270ResourceType
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of the entity in a resource pool." "The type of the entity in a resource pool."
::= { tn3270eResPoolEntry 3 } ::= { tn3270eResPoolEntry 3 }
tn3270eResPoolRowStatus OBJECT-TYPE tn3270eResPoolRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
skipping to change at page 33, line 57 skipping to change at page 33, line 15
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 IANATn3270eAddrType, tn3270eResMapAddrType IANATn3270eAddrType,
tn3270eResMapAddress Tn3270eTAddress, tn3270eResMapAddress IANATn3270eAddress,
tn3270eResMapPort Unsigned32, tn3270eResMapPort Unsigned32,
tn3270eResMapElementType Tn3270ResourceType, tn3270eResMapElementType IANATn3270ResourceType,
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
skipping to change at page 34, line 31 skipping to change at page 33, line 44
tn3270eResMapAddrType OBJECT-TYPE tn3270eResMapAddrType OBJECT-TYPE
SYNTAX IANATn3270eAddrType 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 IANATn3270eAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A client address." "A client address."
::= { tn3270eResMapEntry 3 } ::= { tn3270eResMapEntry 3 }
tn3270eResMapPort OBJECT-TYPE tn3270eResMapPort OBJECT-TYPE
SYNTAX Unsigned32 (0..65535) SYNTAX Unsigned32 (0..65535)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
skipping to change at page 34, line 45 skipping to change at page 34, line 4
"A client address." "A client address."
::= { tn3270eResMapEntry 3 } ::= { tn3270eResMapEntry 3 }
tn3270eResMapPort OBJECT-TYPE tn3270eResMapPort OBJECT-TYPE
SYNTAX Unsigned32 (0..65535) SYNTAX Unsigned32 (0..65535)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A client port." "A client port."
::= { tn3270eResMapEntry 4 } ::= { tn3270eResMapEntry 4 }
tn3270eResMapElementType OBJECT-TYPE tn3270eResMapElementType OBJECT-TYPE
SYNTAX Tn3270ResourceType SYNTAX IANATn3270ResourceType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of the associated resource element." "The type of the associated resource element."
::= { tn3270eResMapEntry 5 } ::= { tn3270eResMapEntry 5 }
tn3270eResMapSscpSuppliedName OBJECT-TYPE tn3270eResMapSscpSuppliedName OBJECT-TYPE
SYNTAX SnaResourceName SYNTAX SnaResourceName
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
skipping to change at page 36, line 4 skipping to change at page 35, line 17
tn3270eTcpConnLocalAddrType, tn3270eTcpConnLocalAddrType,
tn3270eTcpConnLocalAddress, tn3270eTcpConnLocalAddress,
tn3270eTcpConnLocalPort tn3270eTcpConnLocalPort
} }
::= { tn3270eTcpConnTable 1 } ::= { tn3270eTcpConnTable 1 }
Tn3270eTcpConnEntry ::= Tn3270eTcpConnEntry ::=
SEQUENCE SEQUENCE
{ {
tn3270eTcpConnRemAddrType IANATn3270eAddrType, tn3270eTcpConnRemAddrType IANATn3270eAddrType,
tn3270eTcpConnRemAddress Tn3270eTAddress, tn3270eTcpConnRemAddress IANATn3270eAddress,
tn3270eTcpConnRemPort Unsigned32, tn3270eTcpConnRemPort Unsigned32,
tn3270eTcpConnLocalAddrType IANATn3270eAddrType, tn3270eTcpConnLocalAddrType IANATn3270eAddrType,
tn3270eTcpConnLocalAddress Tn3270eTAddress, tn3270eTcpConnLocalAddress IANATn3270eAddress,
tn3270eTcpConnLocalPort Unsigned32, tn3270eTcpConnLocalPort Unsigned32,
tn3270eTcpConnLastActivity TimeTicks, tn3270eTcpConnLastActivity TimeTicks,
tn3270eTcpConnBytesIn Counter32, tn3270eTcpConnBytesIn Counter32,
tn3270eTcpConnBytesOut Counter32, tn3270eTcpConnBytesOut Counter32,
tn3270eTcpConnResourceElement SnaResourceName, tn3270eTcpConnResourceElement SnaResourceName,
tn3270eTcpConnResourceType Tn3270ResourceType, tn3270eTcpConnResourceType IANATn3270ResourceType,
tn3270eTcpConnDeviceType Tn3270DeviceTypes, tn3270eTcpConnDeviceType IANATn3270DeviceType,
tn3270eTcpConnFunctions IANATn3270Functions, tn3270eTcpConnFunctions IANATn3270Functions,
tn3270eTcpConnId Unsigned32, tn3270eTcpConnId Unsigned32,
tn3270eTcpConnClientIdFormat IANATn3270eClientType, tn3270eTcpConnClientIdFormat IANATn3270eClientType,
tn3270eTcpConnClientId OCTET STRING, tn3270eTcpConnClientId OCTET STRING,
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,
skipping to change at page 36, line 39 skipping to change at page 35, line 52
SYNTAX IANATn3270eAddrType 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 IANATn3270eAddress
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The remote address associated with a TN3270E client. "The remote address associated with a TN3270E client.
tn3270eTcpConnRemAddrType indicates the address type tn3270eTcpConnRemAddrType indicates the address type
(IPv4 or IPv6, for example). (IPv4 or IPv6, for example).
If a TN3270(E) client is connected to its If a TN3270(E) client is connected to its
server via a proxy client the address represented by server via a proxy client the address represented by
the value of this object shall be the remote client's the value of this object shall be the remote client's
skipping to change at page 37, line 23 skipping to change at page 36, line 36
SYNTAX IANATn3270eAddrType 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 IANATn3270eAddress
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The local address associated with a TN3270E client. "The local address associated with a TN3270E client.
tn3270eTcpConnRemAddrType indicates the address type tn3270eTcpConnRemAddrType indicates the address type
(IPv4 or IPv6, for example)." (IPv4 or IPv6, for example)."
::= { tn3270eTcpConnEntry 5 } ::= { tn3270eTcpConnEntry 5 }
tn3270eTcpConnLocalPort OBJECT-TYPE tn3270eTcpConnLocalPort OBJECT-TYPE
SYNTAX Unsigned32 (1..65535) SYNTAX Unsigned32 (1..65535)
skipping to change at page 38, line 33 skipping to change at page 37, line 45
tn3270eTcpConnResourceElement OBJECT-TYPE tn3270eTcpConnResourceElement OBJECT-TYPE
SYNTAX SnaResourceName SYNTAX SnaResourceName
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"LU/Print secondary name for connecting an client "LU/Print secondary name for connecting an client
into an SNA network." into an SNA network."
::= { tn3270eTcpConnEntry 10 } ::= { tn3270eTcpConnEntry 10 }
tn3270eTcpConnResourceType OBJECT-TYPE tn3270eTcpConnResourceType OBJECT-TYPE
SYNTAX Tn3270ResourceType SYNTAX IANATn3270ResourceType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the type of resource identified by "Indicates the type of resource identified by
tn3270eTcpConnResourceElement." tn3270eTcpConnResourceElement."
::= { tn3270eTcpConnEntry 11 } ::= { tn3270eTcpConnEntry 11 }
tn3270eTcpConnDeviceType OBJECT-TYPE tn3270eTcpConnDeviceType OBJECT-TYPE
SYNTAX Tn3270DeviceTypes SYNTAX IANATn3270DeviceType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the device type if negotiated with the "Indicates the device type if negotiated with the
client. A value of unknown(0) should be used as the client. A value of unknown(100) should be used as
value of this object when a device type is not the value of this object when a device type is not
negotiated. Refer to RFC 1647 for how device types negotiated. Refer to RFC 2355 for how device types
can be negotiated." can be negotiated."
::= { tn3270eTcpConnEntry 12 } ::= { tn3270eTcpConnEntry 12 }
tn3270eTcpConnFunctions OBJECT-TYPE tn3270eTcpConnFunctions OBJECT-TYPE
SYNTAX IANATn3270Functions SYNTAX IANATn3270Functions
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object indicates which of the TN3270 and TN3270E "This object indicates which of the TN3270 and TN3270E
functions were negotiated by the server and the client functions were negotiated by the server and the client
skipping to change at page 39, line 30 skipping to change at page 38, line 43
The value 0 indicates that a connection does not have The value 0 indicates that a connection does not have
a valid connection identifier." a valid connection identifier."
::= { tn3270eTcpConnEntry 14 } ::= { tn3270eTcpConnEntry 14 }
tn3270eTcpConnClientIdFormat OBJECT-TYPE tn3270eTcpConnClientIdFormat OBJECT-TYPE
SYNTAX IANATn3270eClientType SYNTAX IANATn3270eClientType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The format of a corresponding tn3270eTcpConnClientId "The format of a corresponding tn3270eTcpConnClientId
object as defined by the IANSTn3270eClientType object as defined by the IANSTn3270eClientType textual
textual convention imported from the convention imported from the IANATn3270eTC-MIB."
IANATn3270eTC-MIB."
::= { tn3270eTcpConnEntry 15 } ::= { tn3270eTcpConnEntry 15 }
tn3270eTcpConnClientId OBJECT-TYPE tn3270eTcpConnClientId OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (0..512)) SYNTAX OCTET STRING (SIZE (0..512))
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Additional client identification information. The "Additional client identification information. The
type of this information is indicated by the value of type of this information is indicated by the value of
the corresponding tn3270eTcpConnClientIdFormat object. the corresponding tn3270eTcpConnClientIdFormat object.
skipping to change at page 40, line 34 skipping to change at page 39, line 46
or when a BIND image is unavailable for some other or when a BIND image is unavailable for some other
reason, this object returns a zero-length octet reason, this object returns a zero-length octet
string." string."
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(1),
noSluSession(1), noSluSession(2),
sscpLuSession(2), -- but no LU-LU session sscpLuSession(3), -- but no LU-LU session
luLuSession(3), -- but no SSCP-LU session luLuSession(4), -- but no SSCP-LU session
sscpLuSessionAndLuLuSession(4) sscpLuSessionAndLuLuSession(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(1) - The true state is not known.
noSluSession(1) - The SLU has neither an SSCP-LU
noSluSession(2) - 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(3) - 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 is currently in session luLuSession(4) - The SLU is currently in session
with a PLU, but the SSCP-LU with a PLU, but the SSCP-LU
session for the LU is not active. session for the LU is not active.
sscpLuSessionAndLuLuSession(4) - The SLU currently has sscpLuSessionAndLuLuSession(5) - The SLU currently has
an active session with a PLU, an active session with a PLU,
and the SSCP-LU session for the and the SSCP-LU session for the
SLU is active." SLU is active."
::= { tn3270eTcpConnEntry 20 } ::= { tn3270eTcpConnEntry 20 }
tn3270eTcpConnStateLastDiscReason OBJECT-TYPE tn3270eTcpConnStateLastDiscReason OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
unknown(0), unknown(1),
hostSendsUnbind(1), hostSendsUnbind(2),
hostDontAcceptConnection(2), hostDontAcceptConnection(3),
outOfResource(3), outOfResource(4),
clientProtocolError(4), clientProtocolError(5),
invalidDeviceName(5), invalidDeviceName(6),
deviceInUse(6), deviceInUse(7),
inactivityTimeout(7), inactivityTimeout(8),
hostNotResponding(8), hostNotResponding(9),
clientNotResponding(9), clientNotResponding(10),
serverClose(10), serverClose(11),
sysreqLogoff(11), sysreqLogoff(12),
serverSpecificHexCode(12) serverSpecificHexCode(13)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The last disconnect reason. A session that has not "The last disconnect reason. A session that has not
experienced a disconnect shall use the value unknown(0) experienced a disconnect shall use the value unknown(1)
for this object. Depending on when an implementation for this object. Depending on when an implementation
removes entries from this table, certain states may removes entries from this table, certain states may
never be returned." never be returned."
::= { tn3270eTcpConnEntry 21 } ::= { tn3270eTcpConnEntry 21 }
tn3270eTcpConnSrvrConfIndex OBJECT-TYPE tn3270eTcpConnSrvrConfIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 46, line 4 skipping to change at page 45, line 15
wrap rate of just over 28 minutes. It is recommended wrap rate of just over 28 minutes. It is recommended
that this same guideline be used for determining that this same guideline be used for determining
whether an implementation implements these objects. whether an implementation implements these objects.
This group contains two objects with the syntax This group contains two objects with the syntax
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 information
SHOULD be employed in such environments. An authentication protocol is SHOULD be employed in such environments. An authentication protocol is
defined in [10]. A protocol for access control is defined in [11]. 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 a
negative effect on network operations. It is RECOMMENDED that 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 creation
should be allowed without providing, at a minimum, authentication of should be allowed without providing, at a minimum, authentication of
request origin. It is RECOMMENDED that without such support, the request origin. It is RECOMMENDED that without such support, the
following objects be implemented as read-only: following objects be implemented as read-only:
o tn3270eSrvrConfInactivityTimout o tn3270eSrvrConfInactivityTimout
skipping to change at page 47, line 22 skipping to change at page 46, line 35
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] Case, J., M. Fedor, M. Schoffstall, J. Davin, "Simple Network [1] Harrington D., Presuhn, R., Wijnen, B., "An Architecture for
Management Protocol", RFC 1157, SNMP Research, Performance Systems Describing SNMP Management Frameworks", RFC 2271, Cabletron
International, MIT Laboratory for Computer Science, May 1990. Systems, Inc., BMC Software, Inc., IBM T.J. Watson Research,
January 1998.
[2] McCloghrie, K., and M. Rose, Editors, "Management Information Base [2] Rose, M., and K. McCloghrie, "Structure and Identification of
for Network Management of TCP/IP-based internets: MIB-II", STD 17, Management Information for TCP/IP-based Internets", RFC 1155,
RFC 1213, Hughes LAN Systems, Performance Systems International,
March 1991.
[3] Case, J., McCloghrie, K., Rose, M., and Waldbusser S., "Structure [3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", RFC 1212,
[4] M. Rose, "A Convention for Defining Traps for use with the SNMP",
[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, January 1996. Management Protocol (SNMPv2)", RFC 1902, SNMP Research,Inc., Cisco
Systems, Inc., Dover Beach Consulting, Inc., International Network
Services, January 1996.
[4] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "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 Protocol
(SNMPv2)", RFC 1903, January 1996. (SNMPv2)", RFC 1903, SNMP Research, Inc., Cisco Systems, Inc.,
Dover Beach Consulting, Inc., International Network Services,
January 1996.
[5] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., [7] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Conformance
"Conformance Statements for Version 2 of the Simple Network Statements for Version 2 of the Simple Network Management Protocol
Management Protocol (SNMPv2)", RFC 1904, January 1996. (SNMPv2)", RFC 1904, SNMP Research, Inc., Cisco Systems, Inc.,
Dover Beach Consulting, Inc., International Network Services,
January 1996.
[6] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Protocol [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network
Operations for Version 2 of the Simple Network Management Protocol Management Protocol", RFC 1157, SNMP Research, Performance Systems
(SNMPv2)", RFC 1905, January 1996. International, Performance Systems International, MIT Laboratory
for Computer Science, May 1990.
[7] Harrington D., Presuhn, R., Wijnen, B., "An Architecture for [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
Describing SNMP Management Frameworks", RFC 2271, Cabletron "Introduction to Community-based SNMPv2", RFC 1901, SNMP Research,
Systems, BMC Software, Inc., IBM T.J. Watson Research, January Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc.,
1998. International Network Services, January 1996.
[8] Harrington D., Presuhn, R., Wijnen, B., "Message Processing and [10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport
Dispatching for the Simple Network Management Protocol (SNMP)", RFC Mappings for Version 2 of the Simple Network Management Protocol
2272, Cabletron Systems, BMC Software, Inc., IBM T.J. Watson (SNMPv2)", RFC 1906, SNMP Research, Inc., Cisco Systems, Inc.,
Research, January 1998. Dover Beach Consulting, Inc., International Network Services,
January 1996.
[9] Levi D., Meyer P., Stewart, B., "SNMPv3 Applications", RFC 2273, [11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message
SNMP Research, Inc., Secure Computing Corporation, Cisco Systems, Processing and Dispatching for the Simple Network Management
January 1998. Protocol (SNMP)", RFC 2272, SNMP Research, Inc., Cabletron Systems,
Inc., BMC Software, Inc., IBM T. J. Watson Research, January 1998.
[10] Blumenthal, U., Wijnen, B., "User-based Security Model (USM) for [12] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for
version 3 of the Simple Network Management Protocol (SNMPv3)", RFC version 3 of the Simple Network Management Protocol (SNMPv3)", RFC
2274, IBM T. J. Watson Research, January 1998. 2274, IBM T. J. Watson Research, January 1998.
[11] Wijnen, B., Presuhn, R., McCloghrie, K., "View-based Access Control [13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol
Model (VACM) for the Simple Network Management Protocol (SNMP)", Operations for Version 2 of the Simple Network Management Protocol
RFC 2275, IBM T.J. Watson Research, BMC Software, Inc., Cisco (SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco Systems, Inc.,
Systems, Inc., January 1998. Dover Beach Consulting, Inc., International Network Services,
January 1996.
[12] Postel, J., and Reynolds, J., "Telnet Protocol Specification", RFC [14] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC
2273, SNMP Research, Inc., Secure Computing Corporation, Cisco
Systems, January 1998
[15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access
Control Model (VACM) for the Simple Network Management Protocol
(SNMP)", RFC 2275, IBM T. J. Watson Research, BMC Software, Inc.,
Cisco Systems, Inc., January 1998
[16] Postel, J., and Reynolds, J., "Telnet Protocol Specification", RFC
854, May 1983. 854, May 1983.
[13] Postel, J., and Reynolds, J., "Telnet Timing Mark Option", RFC 860, [17] 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. [18] Rekhter, J., "Telnet 3270 Regime Option", RFC 1041, January 1988.
[15] Kelly, B., "TN3270 Enhancements", RFC 1647, July 1994. [19] Kelly, B., "TN3270 Enhancements", RFC 2355, June 1998.
[16] McCloghrie, K., "TCP-MIB Definitions", RFC 2012, November 1996. [20] McCloghrie, K., "TCP-MIB Definitions", RFC 2012, November 1996.
[17] Hovey, R., and S. Bradner, "The Organizations Involved in the IETF [21] 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.
[18] 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.
[19] Hinden, R., Deering, S., "IP Version 6 Addressing Architecture", [23] Hinden, R., Deering, S., "IP Version 6 Addressing Architecture",
<draft-ietf-ipngwg-addr-arch-v2-02.txt>, July 16, 1997. RFC 2373, July 1998.
[20] Krupczak, Cheryl, Saperia, Jonathan, "Definitions of System-Level [24] 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 50, line 20 skipping to change at page 50, line 20
IANATn3270eTC-MIB DEFINITIONS ::= BEGIN IANATn3270eTC-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, experimental MODULE-IDENTITY, experimental
FROM SNMPv2-SMI FROM SNMPv2-SMI
TEXTUAL-CONVENTION TEXTUAL-CONVENTION
FROM SNMPv2-TC; FROM SNMPv2-TC;
ianaTn3270eTcMib MODULE-IDENTITY ianaTn3270eTcMib MODULE-IDENTITY
LAST-UPDATED "9802020000Z" -- February 2, 1998 LAST-UPDATED "9807270000Z" -- July 27, 1998
ORGANIZATION "IANA" ORGANIZATION "IANA"
CONTACT-INFO CONTACT-INFO
"Internet Assigned Numbers Authority "Internet Assigned Numbers Authority
Postal: USC/Information Sciences Institute Postal: USC/Information Sciences Institute
4676 Admiralty Way, Marina del Rey, CA 90292 4676 Admiralty Way, Marina del Rey, CA 90292
Tel: +1 310 822 1511 Tel: +1 310 822 1511
E-Mail: iana@isi.edu" E-Mail: iana@isi.edu"
DESCRIPTION DESCRIPTION
skipping to change at page 50, line 52 skipping to change at page 50, line 52
Ken White - kennethw@vnet.ibm.com Ken White - kennethw@vnet.ibm.com
Robert Moore - remoore@us.ibm.com Robert Moore - remoore@us.ibm.com
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."
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. -- IANA will assign a real OID when they take over this module.
::= { experimental 2001 } ::= { experimental 2001 }
-- Textual Conventions -- Textual Conventions
IANATn3270eAddrType ::= TEXTUAL-CONVENTION IANATn3270eAddrType ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The textual convention for defining the type of a "The textual convention for defining the type of a
client address. The enumeration value unknown(0) is client address. The enumeration value unknown(0) is
usually used to indicate that no actual address is also used to indicate that no actual address is present."
present."
SYNTAX INTEGER { SYNTAX INTEGER {
unknown(0), unknown(0),
ipv4(1), ipv4(1),
ipv6(2) 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 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
skipping to change at page 51, line 46 skipping to change at page 53, line 4
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
type information in a subsequent type information in a subsequent
sub-negotiation. sub-negotiation.
RFC1041 RFC1041
tn3270Regime Sender is willing to send list of tn3270Regime Sender is willing to send list of
supported 3270 Regimes in a supported 3270 Regimes in a
subsequent sub-negotiation. subsequent sub-negotiation.
RFC1647 RFC2355
scsCtlCodes (Printer sessions only). Allows the scsCtlCodes (Printer sessions only). Allows the
use of the SNA Character Stream (SCS) use of the SNA Character Stream (SCS)
and SCS control codes on the session. and SCS control codes on the session.
SCS is used with LU type 1 SNA sessions. SCS is used with LU type 1 SNA sessions.
dataStreamCtl (Printer sessions only). Allows the use dataStreamCtl (Printer sessions only). Allows the use
of the standard 3270 data stream. This of the standard 3270 data stream. This
corresponds to LU type 3 SNA sessions. corresponds to LU type 3 SNA sessions.
responses Provides support for positive and responses Provides support for positive and
negative response handling. Allows the negative response handling. Allows the
server to reflect to the client any and server to reflect to the client any and
all definite, exception, and no response all definite, exception, and no response
requests sent by the host application. requests sent by the host application.
bindImage Allows the server to send the SNA Bind bindImage Allows the server to send the SNA Bind
image and Unbind notification to the image and Unbind notification to the
client. client.
sysreq Allows the client and server to emulate sysreq Allows the client and server to emulate
some (or all, depending on the server) of some (or all, depending on the server) of
skipping to change at page 52, line 23 skipping to change at page 53, line 35
sysreq Allows the client and server to emulate sysreq Allows the client and server to emulate
some (or all, depending on the server) of some (or all, depending on the server) of
the functions of the SYSREQ key in an SNA the functions of the SYSREQ key in an SNA
environment." environment."
SYNTAX BITS { SYNTAX BITS {
transmitBinary(0),-- rfc856 transmitBinary(0),-- rfc856
timemark(1), -- rfc860 timemark(1), -- rfc860
endOfRecord(2), -- rfc885 endOfRecord(2), -- rfc885
terminalType(3), -- rfc1091 terminalType(3), -- rfc1091
tn3270Regime(4), -- rfc1041 tn3270Regime(4), -- rfc1041
scsCtlCodes(5), -- rfc1647 scsCtlCodes(5), -- rfc2355
dataStreamCtl(6), -- rfc1647 dataStreamCtl(6), -- rfc2355
responses(7), -- rfc1647 responses(7), -- rfc2355
bindImage(8), -- rfc1647 bindImage(8), -- rfc2355
sysreq(9) -- rfc1647 sysreq(9) -- rfc2355
} }
IANATn3270eClientType ::= TEXTUAL-CONVENTION IANATn3270ResourceType ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The textual convention for defining the set of "The type of resource defined by a resource pool. Refer
enumerations used by tn3270eTcpConnClientIdFormat to tn3270eResPoolTable."
in the TN3270E-MIB: SYNTAX INTEGER {
other(1),
terminal(2),
printer(3),
terminalOrPrinter(4)
}
ENUMERATION OCTETs DESCRIPTION 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)
none(0) 0 Not specified -- printers
other(1) 1..512 Implementation specific ibm3287d1(10),
ipv4(2) 6 4-octet IP Address plus
2-octet TCP Port
ipv6(3) 18 16-octet IPv6 Address
plus 2-octet TCP Port
domainName(4) 1..512 The DNS name of a
client.
truncDomainName(5) 1..512 The (truncated) DNS name
of a client.
string(6) 1..512 Unknown Utf8String
certificate(7) 1..512 certificate
userId(8) 1..8 Client's userid
x509dn(9) 1..512 X.509 Distinguished Name
Representation of a certificate(7) may be lead to unknown(100)
a security exposure and is NOT RECOMMENDED without
adequate security."
SYNTAX INTEGER {
none(0),
other(1),
ipv4(2),
ipv6(3),
domainName(4),
truncDomainName(5),
string(6),
certificate(7),
userId(8),
x509dn(9)
} }
IANATn3270eLogData ::= TEXTUAL-CONVENTION IANATn3270eLogData ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An octet string representing log data as pertaining to "An octet string representing log data as pertaining to
either a TN3270 or TN3270E Session as reported from a either a TN3270 or TN3270E Session as reported from a
TN3270E Server. Log data is stored in an octet string TN3270E Server. Log data is stored in an octet string
in time order (from earliest to latest). in time order (from earliest to latest).
skipping to change at page 54, line 20 skipping to change at page 55, line 27
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-255 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 element 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..2048)) SYNTAX OCTET STRING (SIZE (0 | 6..2048))
END END
 End of changes. 108 change blocks. 
252 lines changed or deleted 297 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/