draft-ietf-tn3270e-tn3270-mib-05.txt   draft-ietf-tn3270e-tn3270-mib-06.txt 
TN3270E Working Group Kenneth White TN3270E Working Group Kenneth White
INTERNET DRAFT: <draft-ietf-tn3270e-tn3270-mib-05.txt> IBM Corp. INTERNET DRAFT: <draft-ietf-tn3270e-tn3270-mib-06.txt> IBM Corp.
Expiration Date: July, 1998 Robert Moore Expiration Date: October, 1998 Robert Moore
IBM Corp. IBM Corp.
January 1998
Base Definitions of Managed Objects for Base Definitions of Managed Objects for
TN3270E Using SMIv2 TN3270E Using SMIv2
<draft-ietf-tn3270e-tn3270-mib-05.txt> <draft-ietf-tn3270e-tn3270-mib-06.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 37 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 (reference and managing TN3270E servers. TN3270E, defined by RFC 1647 [15], refers
[14]), refers to the enhancements made to the Telnet 3270 (TN3270) to the enhancements made to the Telnet 3270 (TN3270) terminal emulation
terminal emulation practices. Refer to: RFC 1041, reference [4]; RFC practices. Refer to RFC 1041 [14], RFC 854 [12], and RFC 860 [13] for a
854, reference [2]; and RFC 860, reference [3] for a sample of what is sample of what is meant by TN3270 practices.
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 host TN3270E server refers to gateway TN3270E server implementations. A TN3270E server connects a
an implementation where the TN3270E server is collocated with the Telnet client performing 3270 emulation to a target SNA host over both a
Systems Network Architecture (SNA) System Services Control Point (SSCP) client-side network (client to TN3270E server) and an SNA Network
for the dependent Secondary Logical Units (SLUs) that the server makes (TN3270E server to target SNA host). The client-side network is
available to its clients for connecting into a SNA network. typicaly TCP/IP, but it need not be.
A gateway TN3270E server resides on an SNA node other than an SSCP, A host TN3270E server refers to an implementation where the TN3270E
either an SNA type 2.0 node or an APPN node acting in the role of a server is collocated with the Systems Network Architecture (SNA) System
Dependent LU Requester (DLUR). Host and gateway TN3270E server Services Control Point (SSCP) for the dependent Secondary Logical Units
implementations typically differ greatly as to their internal (SLUs) that the server makes available to its clients for connecting
implementation and system definition (SYSDEF) requirements. into a SNA network. A gateway TN3270E server resides on an SNA node
other than an SSCP, either an SNA type 2.0 node or an APPN node acting
in the role of a Dependent LU Requester (DLUR). Host and gateway
TN3270E server implementations typically differ greatly as to their
internal implementation and system definition (SYSDEF) 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, to provide non-generic configuration support and to enable memos. For example, one such extension enables collection of TN3270E
TN3270E response time collection. The specification of this MIB uses response time data. The specification of this MIB uses the Structure of
the Structure of Management Information (SMI) for Version 2 of the Management Information (SMI) for Version 2 of the Simple Network
Simple Network Management Protocol Version (refer to RFC 1902, reference Management Protocol (refer to RFC1902 [3]).
[1]).
Table of Contents Table of Contents
1.0 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 2 1.0 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2.0 The SNMPv2 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 . . . . . . . . . . . . . . . . . . . 5
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 . . . . . . . . . . . 6
3.3.1 tn3270eSnaMapTable . . . . . . . . . . . . . . . . . . . . 6 3.3.1 tn3270eSnaMapTable . . . . . . . . . . . . . . . . . . . . 6
3.3.2 tn3270eResMapTable . . . . . . . . . . . . . . . . . . . . 7 3.3.2 tn3270eResMapTable . . . . . . . . . . . . . . . . . . . . 7
3.3.3 tn3270eTcpConnTable . . . . . . . . . . . . . . . . . . . 7 3.3.3 tn3270eTcpConnTable . . . . . . . . . . . . . . . . . . . 7
3.4 Advisory Spin Lock Usage . . . . . . . . . . . . . . . . . . . 8 3.4 Advisory Spin Lock Usage . . . . . . . . . . . . . . . . . . . 8
3.5 IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 3.5 Row Persistence . . . . . . . . . . . . . . . . . . . . . . . 8
3.6 IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8
4.0 Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 8 4.0 Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 9
5.0 Security Considerations . . . . . . . . . . . . . . . . . . . 41 5.0 Security Considerations . . . . . . . . . . . . . . . . . . . 44
6.0 Intellectual Property . . . . . . . . . . . . . . . . . . . . 42 6.0 Intellectual Property . . . . . . . . . . . . . . . . . . . . 45
7.0 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 42 7.0 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 45
8.0 References . . . . . . . . . . . . . . . . . . . . . . . . . . 42 8.0 References . . . . . . . . . . . . . . . . . . . . . . . . . . 45
9.0 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 43 9.0 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 47
10.0 Full Copyright Statement . . . . . . . . . . . . . . . . . . 44 10.0 Full Copyright Statement . . . . . . . . . . . . . . . . . . 47
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 [13]. document are to be interpreted as described in RFC 2119, reference [19].
2.0 The SNMPv2 Network Management Framework 2.0 The SNMP Network Management Framework
The SNMPv2 Network Management Framework consists of seven major The SNMP Network Management Framework presently consists of six major
components. They are: components. They are:
o RFC 1902 [1] which defines the SMI, the mechanisms used for o the overall architecture, described in RFC 2271 [7].
describing and naming objects for the purpose of management.
o RFC 1903 [6] defines textual conventions for SNMPv2. o the SMI, described in RFC 1902 [3], - the mechanisms used for
describing and naming objects for the purpose of management.
o RFC 1904 [8] defines conformance statements for SNMPv2. o the MIB-II, STD 17, RFC 1213 [2], - the core set of managed objects
for the Internet suite of protocols.
o RFC 1905 [7] defines transport mappings for SNMPv2. o the protocol, RFC 1157 [1] and/or RFC 1905 [6] and/or RFC 2272 [8]
-- the protocol for accessing managed information.
o RFC 1906 [5] defines the protocol operations used for network access o the user-based security model defined in RFC 2274 [10].
to managed objects.
o RFC 1907 [9] defines the Management Information Base for SNMPv2. o the view-based access control model defined in RFC 2275 [11].
o RFC 1908 [16] specifies coexistence between SNMP and SNMPv2. Textual conventions are defined in RFC 1903 [4], and conformance
statements are defined in RFC 1904 [5]. Common applications are defined
in RFC 2273 [9].
The Framework permits new objects to be defined for the purpose of The Framework permits new objects to be defined for the purpose of
experimentation and evaluation. experimentation and evaluation.
This memo specifies a MIB module that is compliant to the SNMPv2 SMI. A This memo specifies a MIB module that is compliant to the SMIv2. A MIB
semantically identical MIB conforming to the SNMPv1 SMI can be produced conforming to the SMIv1 can be produced through the appropriate
through the appropriate translation. translation.
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 two 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 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 [12], contains the Utf8String textual The SYSAPPL-MIB, reference [21], 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. not. The SNMP-FRAMEWORK-MIB, reference [7], contains the
SnmpAdminString TC that the TN3270E-MIB also imports. Like the
Utf8String TC, this TC also enables internationalization of text
strings; in addition, it provides some guidelines on the length and
content of the strings.
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 SNMP-FRAMEWORK-MIB, reference [15], contains the SnmpAdminString TC The MIB defined by this memo supports use of both IPv4 and IPv6
that the TN3270E-MIB imports. Like the Utf8String TC, this TC also addressing. Two textual conventions, Tn3270eAddrType and
enables internationalization of text strings; in addition, it provides Tn3270eTAddress, are defined for this purpose. Tn3270eTAddress is
some guidelines on the length and content of the strings. essentially equivalent to the TAddress TC, defined by RFC 1903. The
difference between the two is that Tn3270eTAddress allows a zero-length
The MIB defined by this memo handles both IPv4 and IPv6 addressing. Two octet string, while TAddress doesn't. It is important that
textual conventions, Tn3270eAddrType and Tn3270eTAddress, are defined Tn3270eTAddress allow for the absence of an address, because some
for this purpose. Tn3270eTAddress is essentially equivalent to the objects with this syntax are used as table indexes, and have special
TAddress TC, defined by RFC 1903. The difference between the two is meanings when they contain zero-length strings.
that Tn3270eTAddress allows a zero-length octet string, while TAddress
doesn't. It is important that Tn3270eTAddress allow for the absence of
an address, because some objects with this syntax are used as table
indexes, and have special meanings when they contain zero-length
strings.
The Tn3270eAddrType textual convention is used rather than the TDomain The Tn3270eAddrType textual convention is used rather than the TDomain
TC (defined by RFC 1903) for identifying the contents of a 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. Tn3270eAddrType was chosen
over TDomain because, with a SYNTAX of Unsigned32 (enumeration type), it over TDomain because, with a SYNTAX of Unsigned32 (enumeration type), it
is much simpler to use as a component in an instance identifier. is much simpler to use as a component in an instance identifier.
3.1 TN3270E Server Control 3.1 TN3270E Server Control
skipping to change at page 5, line 13 skipping to change at page 5, line 21
tn3270eSrvrConfigEntry. tn3270eSrvrConfigEntry.
3.1.1 tn3270eSrvrConfTable 3.1.1 tn3270eSrvrConfTable
The tn3270eSrvrConfTable contains a set of objects primarily used for The tn3270eSrvrConfTable contains a set of objects primarily used for
configuring and managing TN3270E servers. As with most of the other configuring and managing TN3270E servers. As with most of the other
tables in the TN3270E-MIB, this table is indexed by an unsigned integer, tables in the TN3270E-MIB, this table is indexed by an unsigned 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; otherwise these values are unique, and need not be contiguous.
implementation-dependent.
An earlier version of this memo had used the local IP address associated
with a TN3270E server, along with tn3270eSrvrConfIndex, as the primary
indexes into most of its tables. Use of a local IP address was thought
to enable use of these tables by management applications. This approach
was dropped, since it introduced another level of complexity into MIB
table indexing for little actual benefit.
The tn3270eSrvrConfInactivityTimer object defines the inactivity period The tn3270eSrvrConfInactivityTimer object defines the inactivity period
for TN3270 and TN3270E sessions. The tn3270eSrvrConfSessionTermState for TN3270 and TN3270E sessions.
object defines how a session SHOULD be terminated. The three objects:
The three objects:
o tn3270eSrvrConfActivityCheck o tn3270eSrvrConfActivityCheck
o tn3270eSrvrConfActivityTimeout o tn3270eSrvrConfActivityTimeout
o tn3270eSrvrConfActivityInterval o tn3270eSrvrConfActivityInterval
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 [3]. 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 TIMEMARK
command. Sending a NOP command results in less overhead then a TIMEMARK command. Sending a NOP command results in less overhead then a TIMEMARK
command, since a client doesn't send a reply. 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. enable remote starting and stopping of a TN3270E server, and report the
current state of the server. The object
tn3270eSrvrConfFunctionsSupported indicates which of the TN3270 and tn3270eSrvrConfFunctionsSupported indicates which of the TN3270 and
TN3270E options a server supports. The object TN3270E options a server supports. The object
tn3270eSrvrConfSessionTermState defines as a TN3270E server-wide option tn3270eSrvrConfSessionTermState defines as a TN3270E server-wide 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
by a tn3270eSrvrConfEntry is a host or a gateway server. The object by a tn3270eSrvrConfEntry is a host or a gateway server. The object
tn3270eSrvrConfContact provides a scratch pad area for a TN3270E server tn3270eSrvrConfContact provides a scratch pad area for a TN3270E server
administrator to store information for later retrieval. The object administrator to store information for later retrieval. The object
tn3270eSrvrConfRowStatus provides the capability to perform row creation tn3270eSrvrConfLastActTime reports the DateAndTime when the server was
and deletion operations on this table. most recently activated. The special value of all '00'Hs indicates that
the server has never been active.
The object tn3270eSrvrConfRowStatus provides the capability to perform
row creation and deletion operations on this table.
3.1.2 tn3270eSrvrPortTable 3.1.2 tn3270eSrvrPortTable
The tn3270eSrvrPortTable represents the local TCP ports associated with The tn3270eSrvrPortTable represents the local TCP ports associated with
a TN3270E server. This information is important because some TN3270E a TN3270E server. This information is important because some TN3270E
server implementations support multiple local ports. A server implementations support usage of multiple local ports. A
tn3270eSrvrPortEntry is indexed by: tn3270eSrvrPortEntry is indexed by:
o tn3270eSrvrConfIndex o tn3270eSrvrConfIndex
o tn3270eSrvrConfPort o tn3270eSrvrConfPort
o tn3270eSrvrConfPortAddrType o tn3270eSrvrConfPortAddrType
o tn3270eSrvrConfPortAddress o tn3270eSrvrConfPortAddress
Certain TN3270E server implementations restrict a local TCP port to a Certain TN3270E server implementations restrict a local TCP port to a
particular local IP address, instead of allowing connections for any particular local IP address, instead of allowing connections for any
local IP address to occur via the port. tn3270eSrvrConfPortAddrType and local IP address to occur via the port. tn3270eSrvrConfPortAddrType and
tn3270eSrvrConfPortAddress allow this restriction to be represented in tn3270eSrvrConfPortAddress allow this restriction to be represented in
the MIB. A TN3270E server that doesn't restrict connections over a port the MIB. A TN3270E server that doesn't restrict connections over a port
to a local IP Address SHOULD use the value unknown(0) for to a local IP Address SHALL use the value unknown(0) for
tn3270eSrvrConfPortAddrType, and a zero-length octet string for tn3270eSrvrConfPortAddrType, and a zero-length octet string for
tn3270eSrvrConfPortAddress. tn3270eSrvrConfPortAddress.
3.1.3 tn3270eSrvrStatsTable 3.1.3 tn3270eSrvrStatsTable
The tn3270eSrvrStatsTable defines a series of objects that provide The tn3270eSrvrStatsTable defines a series of objects that provide
general usage statistics for a TN3270E server. general usage statistics for a TN3270E server. An entry can represent
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
basis.
An implementation of this table MUST use only one of the three levels of
refinement that the indexing of this table supports.
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 35 skipping to change at page 7, line 48
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
The TCP Connection Table is defined by RFC 2012 (Refer to reference The TCP Connection Table is currently defined by RFC 2012 (Refer to
[10], TCP-MIB Definitions). It contains the following objects: reference [16], TCP-MIB Definitions). It contains the following
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.
skipping to change at page 8, line 7 skipping to change at page 8, line 21
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 Tn3270eAddrType object pairs are used to specify client addresses
(both local and remote). This enables support of IPv6 addresses. In (both local and remote). This enables support of IPv6 addresses. In
addition, the remote address pair precedes the local address pair in the addition, the remote address pair precedes the local address pair in the
index clause, in order to enable a GET-NEXT operation using only the index clause, in order to enable a GET-NEXT operation using only the
remote address pair. remote address pair.
3.4 Advisory Spin Lock Usage 3.4 Advisory Spin Lock Usage
Within the TN3270E-MIB, the tn3270eConfSpinLock object provides an Within the TN3270E-MIB, tn3270eConfSpinLock is defined as an advisory
advisory lock that an implementation MAY use to let cooperating lock that allows cooperating TN3270E-MIB applications to coordinate
TN3270E-MIB applications coordinate their use of the their use of the tn3270eSrvrConfTable, the tn3270eSrvrPortTable, the
tn3270eSrvrConfTable, the tn3270eSrvrPortTable, the
tn3270eClientGroupTable, the tn3270eResPoolTable, and the tn3270eClientGroupTable, the tn3270eResPoolTable, and the
tn3270eClientResMapTable. When an application seeks to create a new tn3270eClientResMapTable. When creating a new entry or altering an
entry or alter an existing entry in any of the above mentioned tables, existing entry in any of these tables, an application SHOULD make use of
an implementation MAY require the application to use the tn3270eConfSpinLock to serialize application changes or additions.
tn3270eConfSpinLock to serialize its changes or additions relative to Since this is an advisory lock, its use by management applications SHALL
those initiated by other applications. Since this is an advisory lock, NOT be not enforced by agents. Agents MUST, however, implement the
an implementation is not required to support it. tn3270eConfSpinLock object.
3.5 IANA Considerations 3.5 Row Persistence
The following tables enable remote creation of their entries by
including RowStatus objects:
o tn3270eSrvrConfTable
o tn3270eSrvrPortTable
o tn3270eClientGroupTable
o tn3270eResPoolTable
o tn3270eClientResMapTable
An implementation SHOULD NOT retain SNMP-created entries in these tables
across reIPLs (Initial Program Loads) of the corresponding TN3270E
server, since management applications need to see consistent behavior
with respect to the persistence of the table entries that they create.
It is expected that local, implementation-dependent configuration
information will be used to define the initial and persistent
configurations for TN3270E server usage. Thus it is not necessary to
enable persistence of table entries by adding StorageType (refer to RFC
1903 [4]) objects to these tables.
3.6 IANA Considerations
The tn3270eSrvrFunctionsSupported, tn3270eTcpConnFunctions, The tn3270eSrvrFunctionsSupported, tn3270eTcpConnFunctions,
tn3270eTcpConnClientIdFormat, and tn3270eTcpConnLogInfo objects use tn3270eTcpConnClientIdFormat, and tn3270eTcpConnLogInfo objects 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 8, line 42 skipping to change at page 9, line 22
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 homepage at: "http://www.iana.org/iana/". IANA homepage at: "http://www.iana.org/iana/".
4.0 Definitions 4.0 Definitions
TN3270E-MIB DEFINITIONS ::= BEGIN TN3270E-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, Unsigned32, MODULE-IDENTITY, OBJECT-TYPE, Unsigned32, TimeTicks,
TimeTicks, IpAddress, IpAddress, Counter32, Gauge32, Counter64
Counter32, Gauge32, Counter64
FROM SNMPv2-SMI FROM SNMPv2-SMI
TEXTUAL-CONVENTION, RowStatus, TestAndIncr TEXTUAL-CONVENTION, RowStatus, TestAndIncr, DateAndTime,
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, IANATn3270eClientType, IANATn3270eLogData,
skipping to change at page 9, line 4 skipping to change at page 9, line 39
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, IANATn3270eClientType, IANATn3270eLogData,
IANATn3270Functions IANATn3270Functions
FROM IANATn3270eTC-MIB; FROM IANATn3270eTC-MIB;
tn3270eMIB MODULE-IDENTITY tn3270eMIB MODULE-IDENTITY
LAST-UPDATED "9802020000Z" -- February 2, 1998 LAST-UPDATED "9804300000Z" -- April 30, 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
(919) 254-0102 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
(919) 254-4436" USA
+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."
::= { 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
period ('.'), and a 1 to 8 character resource name period ('.'), and a 1 to 8 character resource name
(ResName). (ResName).
The NetId and ResName are constructed from the The NetId and ResName are constructed from the
uppercase letter 'A' - 'Z' and the numerics '0' - '9', uppercase letters 'A' - 'Z' and the numerics '0' - '9',
all encoded in ASCII, with the restriction that the all encoded in ASCII, with the restriction that the
first character of each must be a letter. Trailing first character of each must be a letter. Blanks are
blanks are not allowed. not allowed.
Earlier versions of SNA permitted three additional Earlier versions of SNA permitted three additional
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."
skipping to change at page 11, line 18 skipping to change at page 11, line 54
ibmDynamic(9), -- (no pre-defined display size) ibmDynamic(9), -- (no pre-defined display size)
ibm3287d1(10) -- printers 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 order in the octet string of trace elements, with the trace elements in the
representing order in time of the trace elements, string ordered from earliest to latest.
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 = one-octet length of the data portion of the
skipping to change at page 11, line 49 skipping to change at page 12, line 30
X'03' outbound SNA data to the host X'03' outbound SNA data to the host
X'04' inbound SNA data from the host X'04' inbound SNA data from the host
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..256)) SYNTAX OCTET STRING (SIZE (0 | 2..257))
-- 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
SYNTAX SEQUENCE OF Tn3270eSrvrConfEntry SYNTAX SEQUENCE OF Tn3270eSrvrConfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table defines the configuration elements for "This table defines the configuration elements for
TN3270E servers. The number of entries in this table TN3270E servers. The number of entries in this table
is expected to vary depending on the location of the is expected to vary depending on the location of the
table. A particular TN3270E server is expected to table. A particular TN3270E server is expected to
have a single entry. Modeling of the configuration have a single entry. Modeling of the configuration
elements as a table allows multiple elements as a table allows multiple TN3270E
TN3270E servers to be serviced by the same SNMP agent." servers to be serviced by the same SNMP agent.
An implementation SHOULD NOT retain an SNMP-created
entry in this table across re-IPLs (Initial Program
Loads) of the corresponding TN3270E server."
::= { tn3270eObjects 1 } ::= { tn3270eObjects 1 }
tn3270eSrvrConfEntry OBJECT-TYPE tn3270eSrvrConfEntry OBJECT-TYPE
SYNTAX Tn3270eSrvrConfEntry SYNTAX Tn3270eSrvrConfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
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 }
skipping to change at page 12, line 41 skipping to change at page 13, line 25
tn3270eSrvrConfInactivityTimeout Unsigned32, tn3270eSrvrConfInactivityTimeout Unsigned32,
tn3270eSrvrConfActivityCheck INTEGER, tn3270eSrvrConfActivityCheck INTEGER,
tn3270eSrvrConfActivityTimeout Unsigned32, tn3270eSrvrConfActivityTimeout Unsigned32,
tn3270eSrvrConfActivityInterval Unsigned32, tn3270eSrvrConfActivityInterval 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
} }
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.
Assignment of tn3270eSrvrConfIndex values is left tn3270eSrvrConfIndex values need not be
entirely up to an implementation. The values contiguous."
need not be contiguous."
::= { 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
skipping to change at page 13, line 22 skipping to change at page 14, line 7
tn3270eSrvrConfActivityCheck OBJECT-TYPE tn3270eSrvrConfActivityCheck OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
noCheck(0), noCheck(0),
timeMark(1), timeMark(1),
nop(2) nop(2)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object is intended to enable either timemark or "This object enables timemark processing, nop
nop processing." processing, or neither for a TN3270E server."
DEFVAL { noCheck } DEFVAL { noCheck }
::= { tn3270eSrvrConfEntry 3 } ::= { tn3270eSrvrConfEntry 3 }
tn3270eSrvrConfActivityTimeout OBJECT-TYPE tn3270eSrvrConfActivityTimeout OBJECT-TYPE
SYNTAX Unsigned32 (1..99999999) 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 TIMEMARK or NOP processing time-out specified in
seconds. Note that a value of 0 is not allowed for seconds. Note that a value of 0 is not allowed for
this object since the function that uses this object this object since the function that uses this object
relies on tn3270eSrvrConfActivityCheck for function relies on tn3270eSrvrConfActivityCheck for function
enablement." enablement."
DEFVAL { 600 } -- 10 minutes DEFVAL { 600 } -- 10 minutes
::= { tn3270eSrvrConfEntry 4 } ::= { tn3270eSrvrConfEntry 4 }
tn3270eSrvrConfActivityInterval OBJECT-TYPE tn3270eSrvrConfActivityInterval OBJECT-TYPE
SYNTAX Unsigned32 (1..99999999) 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.
TIMEMARK or NOP processing scans the Telnet sessions TIMEMARK or NOP processing scans the Telnet sessions
on the interval provided by this object looking for on the interval provided by this object looking for
sessions that have been idle for more than the value sessions that have been idle for more than the value
provided by tn3270eSrvrConfActivityTimeout. provided by tn3270eSrvrConfActivityTimeout.
Note that a value of 0 is not allowed for this object Note that a value of 0 is not allowed for this object
skipping to change at page 14, line 40 skipping to change at page 15, line 25
stopImmediate(3) - Informs the associated TN3270E stopImmediate(3) - Informs the associated TN3270E
server to terminate itself server to terminate itself
immediately. immediately.
When a managed system creates an entry in this table, When a managed system creates an entry in this table,
tn3270eSrvrConfAdminStatus and tn3270eSrvrConfOperStatus tn3270eSrvrConfAdminStatus and tn3270eSrvrConfOperStatus
are initialized as up(1) by default. are initialized as up(1) by default.
The exact behavior of a server in response to a down(2) The exact behavior of a server in response to a down(2)
or stopImmediate(3) command is left implementation- or stopImmediate(3) command is left implementation-
dependent. As an example, a TN3270E server that closes dependent. A TN3270E server that is capable of it
all of its TN3270 and TN3270E sessions during termination SHOULD close all of its TN3270 and TN3270E sessions
is typically considered a to have terminated gracefully. during a graceful termination.
Often a stopImmediate(3) command is used as a last Often the function enabled via stopImmediate(3) is used
resort by a system administrator, to attempt to either as a last resort by a system administrator, to attempt
bring down a hung TN3270E server or free up its to either bring down a hung TN3270E server or free up
resources immediately to aid in general system its resources immediately to aid in general system
availability, or to shut down a TN3270E server that is availability, or to shut down a TN3270E server that is
not recognizing a down(2) request. not recognizing a down(2) request.
A TN3270E server that does not distinguish between A TN3270E server that does not distinguish between
down(2) or stopImmediate(3) transitions should not down(2) or stopImmediate(3) transitions should not
support stopImmediate(3)." support stopImmediate(3)."
DEFVAL { up } DEFVAL { up }
::= { tn3270eSrvrConfEntry 7 } ::= { tn3270eSrvrConfEntry 7 }
tn3270eSrvrConfOperStatus OBJECT-TYPE tn3270eSrvrConfOperStatus OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
up(1), -- TN3270E server is active up(1),
down(2) -- TN3270E server is not active down(2),
busy(3),
shuttingDown(4)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The current operational state of a TN3270E server: "The current operational state of a TN3270E server.
The following values are defined:
up(1) - The corresponding TN3270E server is active.
down(2) - The corresponding TN3270E server is not active.
A TN3270E server is considered to be active when it can up(1) - the server is active and accepting
accept new client connections. Thus a server in the new client connections
process of performing a graceful shutdown returns the down(2) - the server is not active
value down(2) in this object. " busy(3) - the server is active, but is not
accepting new client connections
because it lacks the resources to
do so
shuttingDown(4) - the server is active, but is not
accepting new client connections
because it is in the process of
performing a graceful shutdown."
DEFVAL { up } DEFVAL { up }
::= { tn3270eSrvrConfEntry 8 } ::= { tn3270eSrvrConfEntry 8 }
tn3270eSrvrConfSessionTermState OBJECT-TYPE tn3270eSrvrConfSessionTermState OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
terminate(1), terminate(1),
luSessionPend(2), luSessionPend(2),
queueSession(3) queueSession(3)
} }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The current state for determining what a TN3270E server "This object determines what a TN3270E server
should do when a TN3270 Session terminates: should do when a TN3270 Session terminates:
terminate(1) => Terminate TCP connection. terminate(1) => Terminate the TCP connection.
luSessionPend(2) => Do not drop the TCP Connection luSessionPend(2) => Do not drop the TCP connection
associated with a client when their associated with a client when its
TN3270 Session ends. Processing TN3270 session ends. Processing
should redrive session initialization should redrive session initialization
as if the client was first connecting. as if the client were first connecting.
queueSession(3) => QUEUESESSION deals with CLSDST-Pass. queueSession(3) => This value relates to the Close
An example is the easiest explanation. Destination PASS (CLSDST PASS) operation
Assume APPL1 does a CLSDST-Pass in VTAM. An example provides the
to APPL2. Then the client logs off easiest explanation. Suppose a TN3270E
APPL without QUEUESESSION the client is in session with APPL1, and
connection would now be broken. With APPL1 does a CLSDST PASS of the client's
QUEUESESSION the TN3270E server keeps session to APPL2. queueSession(3)
the LU around after getting the APPL2 specifies that the TN3270E server must
unbind waiting for a bind from APPL1." keep the TCP connection with the client
active after it receives the UNBIND from
APPL1, waiting for the BIND from APPL2."
DEFVAL { terminate } DEFVAL { terminate }
::= { tn3270eSrvrConfEntry 9 } ::= { tn3270eSrvrConfEntry 9 }
tn3270eSrvrConfSrvrType OBJECT-TYPE tn3270eSrvrConfSrvrType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
host(1), host(1),
gateway(2) gateway(2)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
skipping to change at page 16, line 36 skipping to change at page 17, line 30
::= { tn3270eSrvrConfEntry 10 } ::= { tn3270eSrvrConfEntry 10 }
tn3270eSrvrConfContact OBJECT-TYPE tn3270eSrvrConfContact OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object provides a scratch pad for a TN3270E "This object provides a scratch pad for a TN3270E
server administrator for storing information for server administrator for storing information for
later retrieval." later retrieval."
DEFVAL { ''H } -- the empty string
::= { tn3270eSrvrConfEntry 11 } ::= { tn3270eSrvrConfEntry 11 }
tn3270eSrvrConfRowStatus OBJECT-TYPE tn3270eSrvrConfRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object allows entries to be created and deleted "This object allows entries to be created and deleted
in the tn3270eSrvrConfTable. in the tn3270eSrvrConfTable. Entries may also be
created and deleted as a result of implementation-
dependent operations.
With the exception of tn3270eSrvrConfSrvrType, which
an implementation can easily fill in for itself, all
the columnar objects in this table have DEFVALs
associated with them. Consequently, a Management
Station can create a conceptual row via a SET
operation that specifies a value only for this object.
When a tn3270eSrvrConfEntry is deleted (by setting When a tn3270eSrvrConfEntry is deleted (by setting
this object to destroy(6)), this has the side-effect this object to destroy(6)), this has the side-effect
of removing all the associated entries (i.e., those of removing all the associated entries (i.e., those
having the same tn3270eSrvrConfIndex) from the having the same tn3270eSrvrConfIndex) from the
tn3270eSrvrPortTable, the tn3270eSrvrStatsTable, the tn3270eSrvrPortTable, the tn3270eSrvrStatsTable, the
tn3270eClientGroupTable, the tn3270eResPoolTable, tn3270eClientGroupTable, the tn3270eResPoolTable,
the tn3270eSnaMapTable, the tn3270eClientResMapTable, the tn3270eSnaMapTable, the tn3270eClientResMapTable,
and the tn3270eResMapTable. All entries in the and the tn3270eResMapTable. All entries in the
tn3270eTcpConnTable that belong to a TN3270E server tn3270eTcpConnTable that belong to a TN3270E server
that has been deleted MUST also be removed. that has been deleted MUST also be removed.
In other words, a tn3270eSrvrConfEntry must exist for In other words, a tn3270eSrvrConfEntry must exist for
a TN3270E server in order for it to have entries in a TN3270E server in order for it to have entries in
any of the other tables defined by this MIB." any of the other tables defined by this MIB."
REFERENCE REFERENCE
"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).'"
::= { tn3270eSrvrConfEntry 12 } ::= { tn3270eSrvrConfEntry 12 }
tn3270eSrvrConfLastActTime OBJECT-TYPE
SYNTAX DateAndTime
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"This object reports the DateAndTime when a TN3270E
server was most recently activated.
The special value of all '00'Hs indicates that the
server has never been active, i.e., that the value of
tn3270eSrvrOperStatus has never been anything other
than down(2)."
DEFVAL { '0000000000000000'H }
::= { tn3270eSrvrConfEntry 13 }
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.
An implementation SHOULD NOT retain SNMP-created
entries in this table across re-IPLs (Initial Program
Loads) of the corresponding TN3270E server."
::= { tn3270eObjects 2 } ::= { tn3270eObjects 2 }
tn3270eSrvrPortEntry OBJECT-TYPE tn3270eSrvrPortEntry OBJECT-TYPE
SYNTAX Tn3270eSrvrPortEntry SYNTAX Tn3270eSrvrPortEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Definition of a single TCP port assignment to a "Definition of a single TCP port assignment to a
TN3270E server. Assignment of a port on a local TN3270E server. Assignment of a port on a local
address basis is enabled though use of address basis is enabled though use of
skipping to change at page 18, line 24 skipping to change at page 19, line 47
tn3270eSrvrPortAddress OBJECT-TYPE tn3270eSrvrPortAddress OBJECT-TYPE
SYNTAX Tn3270eTAddress SYNTAX Tn3270eTAddress
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
value of this object when a local address isn't value of this object when a local address isn't
being specified." being specified."
::= { tn3270eSrvrPortEntry 3 } ::= { tn3270eSrvrPortEntry 3 }
tn3270eSrvrPortRowStatus OBJECT-TYPE tn3270eSrvrPortRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object allows entries to be created and deleted "This object allows entries to be created and deleted
in the tn3270eSrvrPortTable. in the tn3270eSrvrPortTable. Entries may also be
created and deleted as a result of implementation-
dependent operations.
Since this is the only accessible object in this table,
a Management Station can create a conceptual row via a SET
operation that specifies a value only for this object.
An entry in this table is deleted by setting this object An entry in this table is deleted by setting this object
to destroy(6). Deletion of a tn3270eSrvrPortEntry has to destroy(6). Deletion of a tn3270eSrvrPortEntry has
no effect on any other table entry defined by this MIB." no effect on any other table entry defined by this MIB."
REFERENCE REFERENCE
"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).'"
::= { tn3270eSrvrPortEntry 4 } ::= { tn3270eSrvrPortEntry 4 }
tn3270eSrvrStatsTable OBJECT-TYPE tn3270eSrvrStatsTable OBJECT-TYPE
SYNTAX SEQUENCE OF Tn3270eSrvrStatsEntry SYNTAX SEQUENCE OF Tn3270eSrvrStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table defines a set of statistics concerning "This table defines a set of statistics concerning
TN3270E server performance. TN3270E server performance.
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."
::= { tn3270eObjects 3 } ::= { tn3270eObjects 3 }
tn3270eSrvrStatsEntry OBJECT-TYPE tn3270eSrvrStatsEntry OBJECT-TYPE
SYNTAX Tn3270eSrvrStatsEntry SYNTAX Tn3270eSrvrStatsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of statistical objects for a single "A collection of statistical and maximum usage objects
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 activity of the server, or it can represent the activity
the activity occurring at the server on either occurring at the server on either a port or a
a port or port-and-local-address basis. port-and-local-address basis.
Refer to the text description for tn3270eSrvrPortEntry.
Collection of the statistics represented by the objects Collection of the statistics represented by the objects
in this table is not mandatory. An implementation may in this table is not mandatory. An implementation
limit itself to keeping global statistics for a TN3270E of this table MUST use only one of the three levels of
server. The indexing for the row containing these refinement that this table supports.
global server statistics is as follows:
The indexing for a row that represents total server
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.
The values of the following objects are implementation- On a port basis:
dependent for statistics that are being kept on either
a port or port-and-local-address basis:
tn3270eSrvrStatsMaxLus tn3270eSrvrConfIndex value identifying the server
tn3270eSrvrStatsMaxLus tn3270eSrvrPort > 0
tn3270eSrvrStatsInUseLus tn3270eSrvrPortAddrType unknown(0)
tn3270eSrvrStatsSpareLus tn3270eSrvrPortAddress zero-length octet string.
tn3270eSrvrStatsMaxPtrs
tn3270eSrvrStatsInUsePtrs
tn3270eSrvrStatsSparePtrs
A TN3270E server that doesn't allow assignment of the On a port-and-local-address basis:
resources being reported on by these objects on either
a port or port-and-local-address basis should use the tn3270eSrvrConfIndex value identifying the server
values that would be associated with an entire TN3270E tn3270eSrvrPort > 0
server." tn3270eSrvrPortAddrType valid value other than unknown(0)
tn3270eSrvrPortAddress non-zero-length octet string.
"
INDEX { INDEX {
tn3270eSrvrConfIndex, tn3270eSrvrConfIndex,
tn3270eSrvrPort, tn3270eSrvrPort,
tn3270eSrvrPortAddrType, tn3270eSrvrPortAddrType,
tn3270eSrvrPortAddress tn3270eSrvrPortAddress
} }
::= { tn3270eSrvrStatsTable 1 } ::= { tn3270eSrvrStatsTable 1 }
Tn3270eSrvrStatsEntry ::= SEQUENCE { Tn3270eSrvrStatsEntry ::= SEQUENCE {
tn3270eSrvrStatsUpTime TimeTicks, tn3270eSrvrStatsUpTime TimeStamp,
tn3270eSrvrStatsMaxLus Unsigned32, tn3270eSrvrStatsMaxLus Unsigned32,
tn3270eSrvrStatsInUseLus Gauge32, tn3270eSrvrStatsInUseLus Gauge32,
tn3270eSrvrStatsSpareLus Gauge32, tn3270eSrvrStatsSpareLus Gauge32,
tn3270eSrvrStatsMaxPtrs Unsigned32, tn3270eSrvrStatsMaxPtrs Unsigned32,
tn3270eSrvrStatsInUsePtrs Gauge32, tn3270eSrvrStatsInUsePtrs Gauge32,
tn3270eSrvrStatsSparePtrs Gauge32, tn3270eSrvrStatsSparePtrs Gauge32,
tn3270eSrvrStatsInConnects Counter32, tn3270eSrvrStatsInConnects Counter32,
tn3270eSrvrStatsConnRejects Counter32, tn3270eSrvrStatsConnRejects Counter32,
tn3270eSrvrStatsDisconnects Counter32, tn3270eSrvrStatsDisconnects Counter32,
tn3270eSrvrStatsHCInOctets Counter64, tn3270eSrvrStatsHCInOctets Counter64,
tn3270eSrvrStatsInOctets Counter32, tn3270eSrvrStatsInOctets Counter32,
tn3270eSrvrStatsHCOutOctets Counter64, tn3270eSrvrStatsHCOutOctets Counter64,
tn3270eSrvrStatsOutOctets Counter32 tn3270eSrvrStatsOutOctets Counter32
} }
tn3270eSrvrStatsUpTime OBJECT-TYPE tn3270eSrvrStatsUpTime OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeStamp
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates when activity begins for a TN3270E server "The value of the sysUpTime object the last time
as represented by an entry in this table. The value the TN3270E server was re-initialized.
of this object does not get reset based on port usage
status changes or changes to tn3270eSrvrConfOperStatus." Server re-initialization is the only discontinuity
event for the counters in this table. Even if table
entries are on a port or port-and-local-address
basis, port deactivation and reactivation do not
result in counter discontinuities."
::= { tn3270eSrvrStatsEntry 2 } ::= { tn3270eSrvrStatsEntry 2 }
tn3270eSrvrStatsMaxLus OBJECT-TYPE tn3270eSrvrStatsMaxLus 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 for use by a "Indicates the maximum number of LUs available for
TN3270E server." use at a TN3270E server for the granularity of this
conceptual row (server-wide, port, or
port-and-local-address)."
::= { tn3270eSrvrStatsEntry 3 } ::= { tn3270eSrvrStatsEntry 3 }
tn3270eSrvrStatsInUseLus OBJECT-TYPE tn3270eSrvrStatsInUseLus 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 current number of LUs in use by a "Indicates the number of LUs currently in use
TN3270E server." at a TN3270E server for the granularity of this
conceptual row (server-wide, port, or
port-and-local-address)."
::= { tn3270eSrvrStatsEntry 4 } ::= { tn3270eSrvrStatsEntry 4 }
tn3270eSrvrStatsSpareLus OBJECT-TYPE tn3270eSrvrStatsSpareLus 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 for a particular "Indicates the number of free LUs at a TN3270E
TN3270E server. It is possible that the difference server for the granularity of this conceptual
between tn3270eSrvrStatsMaxLus and row (server-wide, port, or port-and-local-address).
tn3270eSrvrStatsInUseLus does not equal
tn3270eSrvrStatsSpareLus. An LU may exist It is possible that the difference between
but not be usable by an client connection." tn3270eSrvrStatsMaxLus and tn3270eSrvrStatsInUseLus
in a conceptual row does not equal the value of
tn3270eSrvrStatsSpareLus in that row: an LU may
exist but not be usable by a client connection."
::= { 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 for "Indicates the maximum number of printer resources
use by a TN3270E server." available for use by a TN3270E server for the
granularity of this conceptual row (server-wide,
port, or port-and-local-address)."
::= { tn3270eSrvrStatsEntry 6 } ::= { tn3270eSrvrStatsEntry 6 }
tn3270eSrvrStatsInUsePtrs OBJECT-TYPE tn3270eSrvrStatsInUsePtrs OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
UNITS "Printer Resources" UNITS "Printer Resources"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the current number of Printer Resources in "Indicates the number of printer resources
use by a TN3270E server." currently in use by a TN3270E server for the
granularity of this conceptual row (server-wide,
port, or port-and-local-address)."
::= { tn3270eSrvrStatsEntry 7 } ::= { tn3270eSrvrStatsEntry 7 }
tn3270eSrvrStatsSparePtrs OBJECT-TYPE tn3270eSrvrStatsSparePtrs OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
UNITS "Spare Printer Resources" UNITS "Spare Printer Resources"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the number of free Printer Resources for a "Indicates the number of free printer resources at
particular TN3270E server. It is possible that the a TN3270E server for the granularity of this conceptual
difference between tn3270eSrvrStatsMaxPtrs and row (server-wide, port, or port-and-local-address).
tn3270eSrvrStatsInUsePtrs does not equal
tn3270eSrvrStatsSparePtrs. A Printer resource may It is possible that the difference between
exist but not be usable by an client connection." tn3270eSrvrStatsMaxPtrs and tn3270eSrvrStatsInUsePtrs
in a conceptual row does not equal the value of
tn3270eSrvrStatsSparePtrs in that row: a printer
resource may exist but not be usable by a client
connection."
::= { 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 that "Indicates the number of client (TCP) connections
succeeded at a TN3270E server. tn3270eSrvrStatsConnRejects that succeeded at a TN3270E server for the
represents failed connection attempts." granularity of this conceptual row (server-wide,
port, or port-and-local-address). The
tn3270eSrvrStatsConnRejects object provides a count
of failed connection attempts.
A Management Station can detect discontinuities in
this counter by monitoring the tn3270eSrvrStatsUpTime
object."
::= { tn3270eSrvrStatsEntry 9 } ::= { tn3270eSrvrStatsEntry 9 }
tn3270eSrvrStatsConnRejects OBJECT-TYPE tn3270eSrvrStatsConnRejects 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. An example during connection setup at a TN3270E server for the
of this is when no LU or printer resource is available granularity of this conceptual row (server-wide,
to associate with the the client's TCP connection." port, or port-and-local-address). An example of
when this counter would be incremented is when no LU
or printer resource is available to associate with a
client's TCP connection.
A Management Station can detect discontinuities in
this counter by monitoring the tn3270eSrvrStatsUpTime
object."
::= { tn3270eSrvrStatsEntry 10 } ::= { tn3270eSrvrStatsEntry 10 }
tn3270eSrvrStatsDisconnects OBJECT-TYPE tn3270eSrvrStatsDisconnects OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "disconnections" UNITS "disconnections"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates all of the (TCP) connections that were "Indicates the number of (TCP) connections that were
disconnected at a TN3270E server." disconnected at a TN3270E server for the
granularity of this conceptual row (server-wide,
port, or port-and-local-address).
A Management Station can detect discontinuities in
this counter by monitoring the tn3270eSrvrStatsUpTime
object."
::= { tn3270eSrvrStatsEntry 11 } ::= { tn3270eSrvrStatsEntry 11 }
tn3270eSrvrStatsHCInOctets OBJECT-TYPE tn3270eSrvrStatsHCInOctets OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
UNITS "octets" UNITS "octets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the number of octets received from TN3270 "Indicates the number of octets received from TN3270
and TN3270E clients." and TN3270E clients for the granularity of this
conceptual row (server-wide, port, or
port-and-local-address).
A Management Station can detect discontinuities in
this counter by monitoring the tn3270eSrvrStatsUpTime
object."
::= { tn3270eSrvrStatsEntry 12 } ::= { tn3270eSrvrStatsEntry 12 }
tn3270eSrvrStatsInOctets OBJECT-TYPE tn3270eSrvrStatsInOctets OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "octets" UNITS "octets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Low order 32 bits of tn3270eSrvrStatsHCInOctets." "Low-order 32 bits of tn3270eSrvrStatsHCInOctets for
::= { tn3270eSrvrStatsEntry 13 } this conceptual row.
A Management Station can detect discontinuities in
this counter by monitoring the tn3270eSrvrStatsUpTime
object."
::= { tn3270eSrvrStatsEntry 13 }
tn3270eSrvrStatsHCOutOctets OBJECT-TYPE tn3270eSrvrStatsHCOutOctets OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
UNITS "octets" UNITS "octets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Indicates the number of octets sent to TN3270 "Indicates the number of octets sent to TN3270
and TN3270E clients." and TN3270E clients for the granularity of this
conceptual row (server-wide, port, or
port-and-local-address).
A Management Station can detect discontinuities in
this counter by monitoring the tn3270eSrvrStatsUpTime
object."
::= { tn3270eSrvrStatsEntry 14 } ::= { tn3270eSrvrStatsEntry 14 }
tn3270eSrvrStatsOutOctets OBJECT-TYPE tn3270eSrvrStatsOutOctets OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "octets" UNITS "octets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Low order 32 bits of tn3270eSrvrStatsHCOutOctets." "Low-order 32 bits of tn3270eSrvrStatsHCOutOctets for
this conceptual row.
A Management Station can detect discontinuities in
this counter by monitoring the tn3270eSrvrStatsUpTime
object."
::= { tn3270eSrvrStatsEntry 15 } ::= { tn3270eSrvrStatsEntry 15 }
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
the tn3270eSrvrConfTable existing." the tn3270eSrvrConfTable existing.
An implementation SHOULD NOT retain SNMP-created
entries in this table across re-IPLs (Initial Program
Loads) of the corresponding TN3270E server."
::= { tn3270eObjects 4 } ::= { tn3270eObjects 4 }
tn3270eClientGroupEntry OBJECT-TYPE tn3270eClientGroupEntry OBJECT-TYPE
SYNTAX Tn3270eClientGroupEntry SYNTAX Tn3270eClientGroupEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Definition of a single client address entry. All "Definition of a single client address entry. All
entries with the same first two indexes, entries with the same first two indexes,
tn3270eSrvrConfIndex and tn3270eClientGroupName, are tn3270eSrvrConfIndex and tn3270eClientGroupName, are
skipping to change at page 23, line 34 skipping to change at page 26, line 17
tn3270eClientGroupAddrType, tn3270eClientGroupAddrType,
tn3270eClientGroupAddress } tn3270eClientGroupAddress }
::= { tn3270eClientGroupTable 1 } ::= { tn3270eClientGroupTable 1 }
Tn3270eClientGroupEntry ::= SEQUENCE { Tn3270eClientGroupEntry ::= SEQUENCE {
tn3270eClientGroupName Utf8String, tn3270eClientGroupName Utf8String,
tn3270eClientGroupAddrType Tn3270eAddrType, tn3270eClientGroupAddrType Tn3270eAddrType,
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 }
skipping to change at page 24, line 7 skipping to change at page 26, line 46
tn3270eClientGroupAddress." tn3270eClientGroupAddress."
::= { tn3270eClientGroupEntry 2 } ::= { tn3270eClientGroupEntry 2 }
tn3270eClientGroupAddress OBJECT-TYPE tn3270eClientGroupAddress OBJECT-TYPE
SYNTAX Tn3270eTAddress SYNTAX Tn3270eTAddress
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
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The corresponding subnet mask associated with "The corresponding subnet mask associated with
tn3270eClientGroupAddress. A single IP address is tn3270eClientGroupAddress. A single IP address is
represented by having this object contain the value represented by having this object contain the value
of 255.255.255.255. This object's value is of 255.255.255.255.
meaningful only if tn3270eClientGroupAddrType has a
value of ipv4(1)." This object's value is meaningful only if
tn3270eClientGroupAddrType has a value of ipv4(1)."
DEFVAL { 'FFFFFFFF'H } DEFVAL { 'FFFFFFFF'H }
::= { tn3270eClientGroupEntry 4 } ::= { tn3270eClientGroupEntry 4 }
tn3270eClientGroupPfxLength OBJECT-TYPE tn3270eClientGroupPfxLength OBJECT-TYPE
SYNTAX Unsigned32 (0..128) SYNTAX Unsigned32 (0..128)
UNITS "bits" UNITS "bits"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The corresponding IPv6 network prefix length. This "The corresponding IPv6 network prefix length.
object is valid only if tn3270eClientGroupAddrType
has a value of ipv6(2)." This object's value is meaningful only if
tn3270eClientGroupAddrType has a value of ipv6(2)."
DEFVAL { 0 } DEFVAL { 0 }
::= { tn3270eClientGroupEntry 5 } ::= { tn3270eClientGroupEntry 5 }
tn3270eClientGroupRowStatus OBJECT-TYPE tn3270eClientGroupRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object allows entries to be created and deleted "This object allows entries to be created and deleted
in the tn3270eClientGroupTable. in the tn3270eClientGroupTable. Entries may also be
created and deleted as a result of implementation-
dependent operations.
An entry in this table is deleted by setting this object An entry in this table is deleted by setting this object
to destroy(6). This has the side-effect of removing to destroy(6). When the number of entries in this table
any entries in the tn3270eClientResMapTable for the client for a given client group becomes 0, this has the side-
group being removed (tn3270eSrvrConfIndex values should be effect of removing any entries for the group in the
the same and tn3270eClientGroupName should match tn3270eClientResMapTable."
tn3270eClientResMapClientGroupName.)"
REFERENCE REFERENCE
"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 1647.
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.
::= { tn3270eObjects 5 }
An implementation SHOULD NOT retain SNMP-created
entries in this table across re-IPLs (Initial Program
Loads) of the corresponding TN3270E server."
::= { tn3270eObjects 5 }
tn3270eResPoolEntry OBJECT-TYPE tn3270eResPoolEntry OBJECT-TYPE
SYNTAX Tn3270eResPoolEntry SYNTAX Tn3270eResPoolEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Definition of a single resource pool member. All entries "Definition of a single resource pool member. All entries
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 Tn3270ResourceType,
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
skipping to change at page 26, line 6 skipping to change at page 28, line 53
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
DESCRIPTION DESCRIPTION
"This object allows entries to be created and deleted in "This object allows entries to be created and deleted
the tn3270eResPoolTable. in the tn3270eResPoolTable. Entries may also be
created and deleted as a result of implementation-
dependent operations.
An entry in this table is deleted by setting this object An entry in this table is deleted by setting this object
to destroy(6). When all entries in this table associated to destroy(6). When all entries in this table associated
with the same tn3270eResPoolElementName have been removed, with the same tn3270eResPoolElementName have been removed,
then any associated (tn3270eResPoolElementName matching then any associated (tn3270eResPoolElementName matching
tn3270eClientResMapPoolName with same tn3270eSrvrConfIndex tn3270eClientResMapPoolName with same tn3270eSrvrConfIndex
values) entries in the tn3270eClientResMapTable SHALL values) entries in the tn3270eClientResMapTable SHALL
also be removed." also be removed."
REFERENCE REFERENCE
"RFC 1903, 'Textual Conventions for version 2 of the "RFC 1903, 'Textual Conventions for version 2 of the
skipping to change at page 26, line 32 skipping to change at page 29, line 26
SYNTAX SEQUENCE OF Tn3270eSnaMapEntry SYNTAX SEQUENCE OF Tn3270eSnaMapEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table provide a mapping from the name by which "This table provide a mapping from the name by which
a secondary LU is known in the SNA network to the a secondary LU is known in the SNA network to the
name by which it is known locally at the TN3270e name by which it is known locally at the TN3270e
server. This latter name serves as an index into server. This latter name serves as an index into
the tn3270eResPoolTable and the tn3270eResMapTable. the tn3270eResPoolTable and the tn3270eResMapTable.
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."
::= { tn3270eObjects 6 } ::= { tn3270eObjects 6 }
tn3270eSnaMapEntry OBJECT-TYPE tn3270eSnaMapEntry OBJECT-TYPE
SYNTAX Tn3270eSnaMapEntry SYNTAX Tn3270eSnaMapEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Definition of a single mapping from an SSCP-supplied "Definition of a single mapping from an SSCP-supplied
SLU name to a local SLU name." SLU name to a local SLU name."
INDEX { tn3270eSrvrConfIndex, INDEX { tn3270eSrvrConfIndex,
tn3270eSnaMapSscpSuppliedName } tn3270eSnaMapSscpSuppliedName }
::= { tn3270eSnaMapTable 1 } ::= { tn3270eSnaMapTable 1 }
Tn3270eSnaMapEntry ::= SEQUENCE { Tn3270eSnaMapEntry ::= SEQUENCE {
tn3270eSnaMapSscpSuppliedName SnaResourceName, tn3270eSnaMapSscpSuppliedName SnaResourceName,
tn3270eSnaMapLocalName SnaResourceName, tn3270eSnaMapLocalName SnaResourceName,
tn3270eSnaMapPrimaryLuName SnaResourceName } tn3270eSnaMapPrimaryLuName SnaResourceName
}
tn3270eSnaMapSscpSuppliedName OBJECT-TYPE tn3270eSnaMapSscpSuppliedName OBJECT-TYPE
SYNTAX SnaResourceName SYNTAX SnaResourceName
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The name of the secondary LU (SLU) as it is known in "The name of the secondary LU (SLU) as it is known in
the SNA network. This name is sent by the SSCP on the SNA network. This name is sent by the SSCP on
the Activate Logical Unit (ACTLU) request." the Activate Logical Unit (ACTLU) request."
::= { tn3270eSnaMapEntry 1 } ::= { tn3270eSnaMapEntry 1 }
skipping to change at page 27, line 40 skipping to change at page 30, line 35
SYNTAX SEQUENCE OF Tn3270eClientResMapEntry SYNTAX SEQUENCE OF Tn3270eClientResMapEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table defines resource-pool to client-group "This table defines resource-pool to client-group
mappings. Since both the resource pool name and client mappings. Since both the resource pool name and client
group name are included in the index clause of this group name are included in the index clause of this
table, multiple resource pools can be assigned to the table, multiple resource pools can be assigned to the
same client group. This enables use of multiple same client group. This enables use of multiple
resource pools for use in client to resource mapping. resource pools for use in client to resource mapping.
Assigning multiple client Groups to the same resource Assigning multiple client groups to the same resource
pool is also allowed, but is not the primary purpose pool is also allowed, but is not the primary purpose
for how the indexing is structured. for how the indexing is structured.
Assignment of a resource pool to client group can be Assignment of a resource pool to client group can be
restricted based on TCP port. An index value of 0 for restricted based on TCP port. An index value of 0 for
tn3270eClientResMapClientPort disables restriction of tn3270eClientResMapClientPort disables restriction of
resource assignment based on client target port resource assignment based on client target port
selection. selection.
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
entries in this table across re-IPLs (Initial Program
Loads) of the corresponding TN3270E server."
::= { tn3270eObjects 7 } ::= { tn3270eObjects 7 }
tn3270eClientResMapEntry OBJECT-TYPE tn3270eClientResMapEntry OBJECT-TYPE
SYNTAX Tn3270eClientResMapEntry SYNTAX Tn3270eClientResMapEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Definition of a single resource pool to client group "Definition of a single resource pool to client group
mapping." mapping."
INDEX { tn3270eSrvrConfIndex, INDEX { tn3270eSrvrConfIndex,
tn3270eClientResMapPoolName, tn3270eClientResMapPoolName,
tn3270eClientResMapClientGroupName, tn3270eClientResMapClientGroupName,
tn3270eClientResMapClientPort } tn3270eClientResMapClientPort }
::= { tn3270eClientResMapTable 1 } ::= { tn3270eClientResMapTable 1 }
Tn3270eClientResMapEntry ::= SEQUENCE { Tn3270eClientResMapEntry ::= SEQUENCE {
tn3270eClientResMapPoolName Utf8String, tn3270eClientResMapPoolName Utf8String,
tn3270eClientResMapClientGroupName Utf8String, tn3270eClientResMapClientGroupName Utf8String,
tn3270eClientResMapClientPort Unsigned32, tn3270eClientResMapClientPort Unsigned32,
tn3270eClientResMapRowStatus RowStatus } tn3270eClientResMapRowStatus RowStatus
}
tn3270eClientResMapPoolName OBJECT-TYPE tn3270eClientResMapPoolName 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."
::= { tn3270eClientResMapEntry 1 } ::= { tn3270eClientResMapEntry 1 }
tn3270eClientResMapClientGroupName OBJECT-TYPE tn3270eClientResMapClientGroupName OBJECT-TYPE
skipping to change at page 28, line 41 skipping to change at page 31, line 41
DESCRIPTION DESCRIPTION
"The name of the client group that is mapped to a "The name of the client group that is mapped to a
resource pool." resource pool."
::= { tn3270eClientResMapEntry 2 } ::= { tn3270eClientResMapEntry 2 }
tn3270eClientResMapClientPort OBJECT-TYPE tn3270eClientResMapClientPort OBJECT-TYPE
SYNTAX Unsigned32 (0..65535) SYNTAX Unsigned32 (0..65535)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The port to restrict a resource pool to a client "A port number restricting the scope of a mapping
group mapping. A value of 0 for this objects implies from a resource pool to a client group. The
that the mapping is not restricted." value 0 for this object indicates that the scope
of the mapping is not restricted."
::= { tn3270eClientResMapEntry 3 } ::= { tn3270eClientResMapEntry 3 }
tn3270eClientResMapRowStatus OBJECT-TYPE tn3270eClientResMapRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object allows entries to be created and deleted "This object allows entries to be created and deleted
in the tn3270eClientResMapTable. in the tn3270eClientResMapTable. Entries may also be
created and deleted as a result of implementation-
dependent operations.
An entry in this table is deleted by setting this object An entry in this table is deleted by setting this object
to destroy(6). Removing an entry from this table doesn't to destroy(6). Removing an entry from this table doesn't
affect any other table entry defined by this MIB." affect any other table entry defined in this MIB."
REFERENCE REFERENCE
"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).'"
::= { tn3270eClientResMapEntry 4 } ::= { tn3270eClientResMapEntry 4 }
tn3270eResMapTable OBJECT-TYPE tn3270eResMapTable OBJECT-TYPE
SYNTAX SEQUENCE OF Tn3270eResMapEntry SYNTAX SEQUENCE OF Tn3270eResMapEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table defines the actual mapping of a resource "This table defines the actual mapping of a resource
to a client address. to a client address.
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."
::= { tn3270eObjects 8 } ::= { tn3270eObjects 8 }
tn3270eResMapEntry OBJECT-TYPE tn3270eResMapEntry OBJECT-TYPE
SYNTAX Tn3270eResMapEntry SYNTAX Tn3270eResMapEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Definition of the mapping of a Resource Element to "Definition of the mapping of a Resource Element to
skipping to change at page 29, line 37 skipping to change at page 32, line 40
INDEX { tn3270eSrvrConfIndex, INDEX { tn3270eSrvrConfIndex,
tn3270eResMapElementName } tn3270eResMapElementName }
::= { tn3270eResMapTable 1 } ::= { tn3270eResMapTable 1 }
Tn3270eResMapEntry ::= SEQUENCE { Tn3270eResMapEntry ::= SEQUENCE {
tn3270eResMapElementName SnaResourceName, tn3270eResMapElementName SnaResourceName,
tn3270eResMapAddrType Tn3270eAddrType, tn3270eResMapAddrType Tn3270eAddrType,
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. In this case the resource is known in the SNA network. This latter
the name by which the resource is known in the SNA name is returned in the tn3270eResMapSscpSuppliedName
network is returned in the tn3270eResMapSscpSuppliedName
object." object."
::= { tn3270eResMapEntry 1 } ::= { tn3270eResMapEntry 1 }
tn3270eResMapAddrType OBJECT-TYPE tn3270eResMapAddrType OBJECT-TYPE
SYNTAX Tn3270eAddrType SYNTAX Tn3270eAddrType
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."
skipping to change at page 30, line 36 skipping to change at page 33, line 39
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
DESCRIPTION DESCRIPTION
"The name of the secondary LU (SLU) as it is known in a "The name of the secondary LU (SLU) as it is known
SNA network. This name is sent by the SSCP on the in a SNA network. This name is sent by the SSCP on
Activate Logical Unit (ACTLU) request. The value of the Activate Logical Unit (ACTLU) request. If this
this object is a zero-length octet string if the name is not known, this object returns a zero-length
tn3270eResMapElementName is the same as the octet string."
SSCP-supplied name."
::= { tn3270eResMapEntry 6 } ::= { tn3270eResMapEntry 6 }
-- Define the set of objects to supplement the TCP Connection Table -- Define the set of objects to supplement the TCP Connection Table
tn3270eTcpConnTable OBJECT-TYPE tn3270eTcpConnTable OBJECT-TYPE
SYNTAX SEQUENCE OF Tn3270eTcpConnEntry SYNTAX SEQUENCE OF Tn3270eTcpConnEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Provides a table that has an entry for each TN3270(E) "This table has an entry for each TN3270(E) client
client connection that is active at a TN3270E server. connection that is currently active at a TN3270E server.
The table was originally modeled after the tcpConnTable An implementation MAY retain entries for connections
but was changed to support different client address types that have been terminated, but which entries are
and to be indexed first by the remote address and port retained, how many entries are retained, and how long
as oppose to local address and port. This is to enable they are retained is entirely implementation-dependent.
use of a SNMP GET-NEXT operation using only the remote
address and port." The indexing for this table is designed to support the
use of an SNMP GET-NEXT operation using only the remote
address type, remote address, and remote port, as a way
for a Management Station to retrieve the table entries
related to a particular TN3270(E) client."
::= { tn3270eObjects 9 } ::= { tn3270eObjects 9 }
tn3270eTcpConnEntry OBJECT-TYPE tn3270eTcpConnEntry OBJECT-TYPE
SYNTAX Tn3270eTcpConnEntry SYNTAX Tn3270eTcpConnEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Provides in formation about a single TN3270/TN3270E "Provides in formation about a single TN3270/TN3270E
session. Note: a tn3270eSrvrConfIndex is not needed session. Note: a tn3270eSrvrConfIndex is not needed
in this table since the combination of both remote in this table, since the combination of remote and
local addresses and ports is sufficient to local addresses and ports is sufficient to
guarantee uniqueness between TN3270E servers that guarantee uniqueness across the TN3270E servers
may or may not be serviced by the same SNMP agent." serviced by an SNMP agent. Because of this indexing
structure, however, this table does not support
view-based access control policies that provide
access to table rows on a per-server basis."
INDEX { tn3270eTcpConnRemAddrType, INDEX { tn3270eTcpConnRemAddrType,
tn3270eTcpConnRemAddress, tn3270eTcpConnRemAddress,
tn3270eTcpConnRemPort, tn3270eTcpConnRemPort,
tn3270eTcpConnLocalAddrType, tn3270eTcpConnLocalAddrType,
tn3270eTcpConnLocalAddress, tn3270eTcpConnLocalAddress,
tn3270eTcpConnLocalPort tn3270eTcpConnLocalPort
} }
::= { tn3270eTcpConnTable 1 } ::= { tn3270eTcpConnTable 1 }
Tn3270eTcpConnEntry ::= Tn3270eTcpConnEntry ::=
skipping to change at page 31, line 50 skipping to change at page 35, line 4
tn3270eTcpConnDeviceType Tn3270DeviceTypes, tn3270eTcpConnDeviceType Tn3270DeviceTypes,
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,
tn3270eTcpConnActivationTime TimeStamp
} }
tn3270eTcpConnRemAddrType OBJECT-TYPE tn3270eTcpConnRemAddrType OBJECT-TYPE
SYNTAX Tn3270eAddrType SYNTAX Tn3270eAddrType
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
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
address, not the proxy client's address." address, not the proxy client's address."
::= { tn3270eTcpConnEntry 2 } ::= { tn3270eTcpConnEntry 2 }
tn3270eTcpConnRemPort OBJECT-TYPE tn3270eTcpConnRemPort OBJECT-TYPE
SYNTAX Unsigned32 (1..65535) SYNTAX Unsigned32 (1..65535)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
skipping to change at page 32, line 53 skipping to change at page 36, line 8
ipv4(1) or ipv6(2)." ipv4(1) or ipv6(2)."
::= { tn3270eTcpConnEntry 4 } ::= { tn3270eTcpConnEntry 4 }
tn3270eTcpConnLocalAddress OBJECT-TYPE tn3270eTcpConnLocalAddress OBJECT-TYPE
SYNTAX Tn3270eTAddress SYNTAX Tn3270eTAddress
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)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The remote port associated with a TN3270E client." "The remote port associated with a TN3270E client."
::= { tn3270eTcpConnEntry 6 } ::= { tn3270eTcpConnEntry 6 }
skipping to change at page 33, line 26 skipping to change at page 36, line 36
DEFVAL { 0 } DEFVAL { 0 }
::= { tn3270eTcpConnEntry 7 } ::= { tn3270eTcpConnEntry 7 }
tn3270eTcpConnBytesIn OBJECT-TYPE tn3270eTcpConnBytesIn OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "octets" UNITS "octets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of bytes received by the server from TCP "The number of bytes received by the server from TCP
for this connection." for this connection.
A Management Station can detect discontinuities in
this counter by monitoring the
tn3270eTcpConnActivationTime object."
::= { tn3270eTcpConnEntry 8 } ::= { tn3270eTcpConnEntry 8 }
tn3270eTcpConnBytesOut OBJECT-TYPE tn3270eTcpConnBytesOut OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "octets" UNITS "octets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of bytes sent to TCP for this connection." "The number of bytes sent to TCP for this connection.
A Management Station can detect discontinuities in
this counter by monitoring the
tn3270eTcpConnActivationTime object."
::= { tn3270eTcpConnEntry 9 } ::= { tn3270eTcpConnEntry 9 }
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 }
skipping to change at page 34, line 35 skipping to change at page 37, line 53
tn3270eTcpConnId OBJECT-TYPE tn3270eTcpConnId OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The connection identifier associated with a TN3270 or "The connection identifier associated with a TN3270 or
a TN3270E session's TCP connection. TCP implementations a TN3270E session's TCP connection. TCP implementations
often assign a unique (with respect to itself) unsigned often assign a unique (with respect to itself) unsigned
integer as an identifier for a TCP connection. integer as an identifier for a TCP connection.
Implementations that do not support assignment of
unsigned integer connection identifiers should not The value 0 indicates that a connection does not have
support this object." 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 convention imported from the textual convention imported from the
skipping to change at page 35, line 4 skipping to change at page 38, line 22
::= { 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.
All values are returned in network-byte order.
The purpose of this object is to provide an alternate The purpose of this object is to provide an alternate
means of identifying a client, other than though the means of identifying a client, other than though the
remote address returned in tn3270eTcpConnRemAddress." remote address returned in tn3270eTcpConnRemAddress."
::= { tn3270eTcpConnEntry 16 } ::= { tn3270eTcpConnEntry 16 }
tn3270eTcpConnTraceData OBJECT-TYPE tn3270eTcpConnTraceData OBJECT-TYPE
SYNTAX Tn3270eTraceData SYNTAX Tn3270eTraceData
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
skipping to change at page 35, line 36 skipping to change at page 38, line 55
::= { tn3270eTcpConnEntry 18 } ::= { tn3270eTcpConnEntry 18 }
tn3270eTcpConnLuLuBindImage OBJECT-TYPE tn3270eTcpConnLuLuBindImage OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (0..256)) SYNTAX OCTET STRING (SIZE (0..256))
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"When there is a currently active LU-LU session for "When there is a currently active LU-LU session for
this connection, this object returns the BIND Image this connection, this object returns the BIND Image
(defined to be bytes 1-p of the complete BIND Request (defined to be bytes 1-p of the complete BIND Request
Unit) that was received from the PLU during session Unit -- see 'SNA Formats' for more information)
that was received from the PLU during session
activation. When there is no active LU-LU session, activation. When there is no active LU-LU session,
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 string." reason, this object returns a zero-length octet
string."
REFERENCE
"'Systems Network Architecture Formats', IBM
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),
establishingSscpLuSession(4), establishingSscpLuSession(4),
establishingLuSession(5) establishingLuSession(5)
skipping to change at page 36, line 30 skipping to change at page 39, line 54
unknown(0), unknown(0),
hostSendsUnbind(1), hostSendsUnbind(1),
hostDontAcceptConnection(2), hostDontAcceptConnection(2),
outOfResource(3), outOfResource(3),
clientProtocolError(4), clientProtocolError(4),
invalidDeviceName(5), invalidDeviceName(5),
deviceInUse(6), deviceInUse(6),
inactivityTimeout(7), inactivityTimeout(7),
hostNotResponding(8), hostNotResponding(8),
clientNotResponding(9), clientNotResponding(9),
tcpClose(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. Note: that a session "The last disconnect reason. A session that has not
that has not experienced a disconnect would use experienced a disconnect shall use the value unknown(0)
a value of unknown(0) for this object." for this object. Depending on when an implementation
removes entries from this table, certain states may
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
"tn3270eSrvrConfIndex of the tn3270eSrvrConfEntry "tn3270eSrvrConfIndex of the tn3270eSrvrConfEntry
belonging to the TN3270E server to whom this entry belonging to the TN3270E server to which this entry
belongs." belongs."
::= { tn3270eTcpConnEntry 22 } ::= { tn3270eTcpConnEntry 22 }
tn3270eTcpConnActivationTime OBJECT-TYPE
SYNTAX TimeStamp
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The value of the sysUpTime object the last time
this TCP connection became active."
::= { tn3270eTcpConnEntry 23 }
tn3270eConfSpinLock OBJECT-TYPE tn3270eConfSpinLock OBJECT-TYPE
SYNTAX TestAndIncr SYNTAX TestAndIncr
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An advisory lock used to allow cooperating "An advisory lock used to allow cooperating
TN3270E-MIB applications to coordinate their TN3270E-MIB applications to coordinate their use
use of the tn3270eSrvrConfTable, the of the tn3270eSrvrConfTable, the tn3270eSrvrPortTable,
tn3270eSrvrPortTable, the tn3270eClientGroupTable, the tn3270eClientGroupTable, the tn3270eResPoolTable,
the tn3270eResPoolTable, and the and the tn3270eClientResMapTable.
tn3270eClientResMapTable.
When an application seeks to create a new entry or When creating a new entry or altering an existing entry
alter an existing entry in any of the above mentioned in the any of the tables mentioned above, an application
tables, an implementation MAY require the application should make use of tn3270eRtSpinLock to serialize
to use the tn3270eConfSpinLock to serialize its changes application changes or additions.
or additions relative to those initiated by other
applications. Since this is an advisory lock, an Since this is an advisory lock, the use of this lock is
implementation is not required to support it." not enforced."
::= { tn3270eObjects 10 } ::= { tn3270eObjects 10 }
-- Conformance Definitions -- Conformance Definitions
tn3270eGroups OBJECT IDENTIFIER ::= { tn3270eConformance 1 } tn3270eGroups OBJECT IDENTIFIER ::= { tn3270eConformance 1 }
tn3270eCompliances OBJECT IDENTIFIER ::= { tn3270eConformance 2 } tn3270eCompliances OBJECT IDENTIFIER ::= { tn3270eConformance 2 }
-- compliance statements -- compliance statements
tn3270eCompliance MODULE-COMPLIANCE tn3270eCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for agents that support the "The compliance statement for agents that support the
TN3270E-MIB." TN3270E-MIB."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { tn3270eBasicGroup, MANDATORY-GROUPS { tn3270eBasicGroup,
tn3270eSessionGroup tn3270eSessionGroup
} }
GROUP tn3270eResMapGroup GROUP tn3270eResMapGroup
skipping to change at page 38, line 23 skipping to change at page 41, line 55
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
SYNTAX INTEGER {
active(1) -- subset of RowStatus
}
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required, and only one "Write access is not required."
of the six enumerated values for the
RowStatus textual convention need be
supported, specifically: active(1)."
OBJECT tn3270eSrvrPortRowStatus OBJECT tn3270eSrvrPortRowStatus
SYNTAX INTEGER {
active(1) -- subset of RowStatus
}
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required, and only one "Write access is not required."
of the six enumerated values for the
RowStatus textual convention need be
supported, specifically: active(1)."
OBJECT tn3270eClientGroupRowStatus OBJECT tn3270eClientGroupRowStatus
SYNTAX INTEGER {
active(1) -- subset of RowStatus
}
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required, and only one "Write access is not required."
of the six enumerated values for the
RowStatus textual convention need be
supported, specifically: active(1)."
OBJECT tn3270eResPoolRowStatus OBJECT tn3270eResPoolRowStatus
SYNTAX INTEGER {
active(1) -- subset of RowStatus
}
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required, and only one "Write access is not required."
of the six enumerated values for the
RowStatus textual convention need be
supported, specifically: active(1)."
OBJECT tn3270eClientResMapRowStatus OBJECT tn3270eClientResMapRowStatus
SYNTAX INTEGER {
active(1) -- subset of RowStatus
}
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required, and only one "Write access is not required."
of the six enumerated values for the
RowStatus textual convention need be
supported, specifically: active(1)."
OBJECT tn3270eTcpConnId
MIN-ACCESS not-accessible
DESCRIPTION
"This object is not required of implementations
that do not support assignment of unsigned
integer connection identifiers."
OBJECT tn3270eConfSpinLock
MIN-ACCESS not-accessible
DESCRIPTION
"The use and support of this object is optional."
::= { tn3270eCompliances 1 } ::= { tn3270eCompliances 1 }
-- units of conformance -- units of conformance
tn3270eBasicGroup OBJECT-GROUP tn3270eBasicGroup OBJECT-GROUP
OBJECTS { OBJECTS {
tn3270eSrvrConfInactivityTimeout, tn3270eSrvrConfInactivityTimeout,
tn3270eSrvrConfActivityCheck, tn3270eSrvrConfActivityCheck,
tn3270eSrvrConfActivityTimeout, tn3270eSrvrConfActivityTimeout,
tn3270eSrvrConfActivityInterval, tn3270eSrvrConfActivityInterval,
tn3270eSrvrFunctionsSupported, tn3270eSrvrFunctionsSupported,
tn3270eSrvrConfAdminStatus, tn3270eSrvrConfAdminStatus,
tn3270eSrvrConfOperStatus, tn3270eSrvrConfOperStatus,
tn3270eSrvrConfSessionTermState, tn3270eSrvrConfSessionTermState,
tn3270eSrvrConfSrvrType, tn3270eSrvrConfSrvrType,
tn3270eSrvrConfContact, tn3270eSrvrConfContact,
tn3270eSrvrConfRowStatus, tn3270eSrvrConfRowStatus,
tn3270eSrvrConfLastActTime,
tn3270eSrvrPortRowStatus, tn3270eSrvrPortRowStatus,
tn3270eSrvrStatsUpTime, tn3270eSrvrStatsUpTime,
tn3270eSrvrStatsMaxLus, tn3270eSrvrStatsMaxLus,
tn3270eSrvrStatsInUseLus, tn3270eSrvrStatsInUseLus,
tn3270eSrvrStatsSpareLus, tn3270eSrvrStatsSpareLus,
tn3270eSrvrStatsMaxPtrs, tn3270eSrvrStatsMaxPtrs,
tn3270eSrvrStatsInUsePtrs, tn3270eSrvrStatsInUsePtrs,
tn3270eSrvrStatsSparePtrs, tn3270eSrvrStatsSparePtrs,
tn3270eSrvrStatsInConnects, tn3270eSrvrStatsInConnects,
tn3270eSrvrStatsConnRejects, tn3270eSrvrStatsConnRejects,
skipping to change at page 40, line 36 skipping to change at page 43, line 28
tn3270eResMapPort, tn3270eResMapPort,
tn3270eResMapElementType, tn3270eResMapElementType,
tn3270eResMapSscpSuppliedName, tn3270eResMapSscpSuppliedName,
tn3270eTcpConnLastActivity, tn3270eTcpConnLastActivity,
tn3270eTcpConnBytesIn, tn3270eTcpConnBytesIn,
tn3270eTcpConnBytesOut, tn3270eTcpConnBytesOut,
tn3270eTcpConnResourceElement, tn3270eTcpConnResourceElement,
tn3270eTcpConnResourceType, tn3270eTcpConnResourceType,
tn3270eTcpConnDeviceType, tn3270eTcpConnDeviceType,
tn3270eTcpConnFunctions, tn3270eTcpConnFunctions,
tn3270eTcpConnSrvrConfIndex tn3270eTcpConnSrvrConfIndex,
tn3270eTcpConnActivationTime
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This group is mandatory for all hosts supporting the "This group is mandatory for all hosts supporting the
TN3270E-MIB." TN3270E-MIB."
::= { tn3270eGroups 2 } ::= { tn3270eGroups 2 }
tn3270eResMapGroup OBJECT-GROUP tn3270eResMapGroup OBJECT-GROUP
OBJECTS { OBJECTS {
tn3270eResPoolElementType, tn3270eResPoolElementType,
skipping to change at page 41, line 16 skipping to change at page 44, line 9
TN3270E-MIB." TN3270E-MIB."
::= { tn3270eGroups 3 } ::= { tn3270eGroups 3 }
tn3270eHiCapacityGroup OBJECT-GROUP tn3270eHiCapacityGroup OBJECT-GROUP
OBJECTS { OBJECTS {
tn3270eSrvrStatsHCInOctets, tn3270eSrvrStatsHCInOctets,
tn3270eSrvrStatsHCOutOctets tn3270eSrvrStatsHCOutOctets
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This group is optional for all hosts supporting the "Support of these objects is REQUIRED when the
TN3270E-MIB. Its contents is a list of Counter64 Counter32 versions can potentially wrap too
objects. An implementation that doesn't support frequently. This group is optional for all other
these objects should return noSuchObject. hosts supporting the TN3270E-MIB.
Returning a zero is misleading. Support of these
objects is recommended when the Counter32 versions
can potentially wrap too frequently.
The IF-MIB (RFC 2233) requires that the 64 bit The IF-MIB (RFC 2233) requires that the 64-bit
versions of its counters be implemented when an versions of its counters be implemented when an
interface can support rates around 20 million bits interface can support rates of around 20 million
per second or greater. This implies a minimum wrap bits per second or greater. This implies a minimum
rate of just over 28 minutes. It is recommended that wrap rate of just over 28 minutes. It is recommended
this guidance be used for determining when an that this same guideline be used for determining
implementation should implement these objects." whether an implementation implements these objects.
This group contains two objects with the syntax
Counter64. An implementation that doesn't support
these objects should return noSuchObject, since
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. The method for this SHOULD be employed in such environments. An authentication protocol is
authentication is a function of the SNMP Administrative Framework, and defined in [10]. A protocol for access control is defined in [11].
has not been expanded by this MIB.
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 42, line 4 skipping to change at page 44, line 53
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
o tn3270eSrvrConfActivityCheck o tn3270eSrvrConfActivityCheck
o tn3270eSrvrConfActivityTimeout o tn3270eSrvrConfActivityTimeout
o tn3270eSrvrConfActivityInterval o tn3270eSrvrConfActivityInterval
o tn3270eSrvrConfAdminStatus o tn3270eSrvrConfAdminStatus
o tn3270eSrvrConfSessionTermState o tn3270eSrvrConfSessionTermState
o tn3270eSrvrConfContact o tn3270eSrvrConfContact
o tn3270eClientGroupSubnetMask o tn3270eClientGroupSubnetMask
o tn3270eResPoolElementType o tn3270eResPoolElementType
o tn3270eSrvrConfRowStatus o tn3270eSrvrConfRowStatus
o tn3270eSrvrPortRowStatus o tn3270eSrvrPortRowStatus
o tn3270eClientGroupRowStatus o tn3270eClientGroupRowStatus
o tn3270eResPoolRowStatus o tn3270eResPoolRowStatus
o tn3270eResMapRowStatus o tn3270eResMapRowStatus
For all tables in the MIB except the tn3270eTcpConnTable, the first
index identifies an individual TN3270E server. This makes it easy to
implement an access control policy under which different principals have
access to objects related to different servers. Implementation of such
a policy is not possible for the entries in the tn3270eTcpConTable.
6.0 Intellectual Property 6.0 Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to pertain intellectual property or other rights that might be claimed to pertain
to the implementation or use of the technology described in this to the implementation or use of the technology described in this
document or the extent to which any license under such rights might or document or the extent to which any license under such rights might or
might not be available; neither does it represent that it has made any might not be available; neither does it represent that it has made any
effort to identify any such rights. Information on the IETF's effort to identify any such rights. Information on the IETF's
procedures with respect to rights in standards-track and procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11. Copies of standards-related documentation can be found in BCP-11. Copies of
skipping to change at page 42, line 38 skipping to change at page 45, line 39
from the IETF Secretariat. from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary rights copyrights, patents or patent applications, or other proprietary rights
which may cover technology that may be required to practice this which may cover technology that may be required to practice this
standard. Please address the information to the IETF Executive standard. Please address the information to the IETF Executive
Director. Director.
7.0 Acknowledgments 7.0 Acknowledgments
This document is a product of the TN3270E Working Group. This document is a product of the TN3270E Working Group. Thanks to
Randy Presuhn of BMC Software for his valuable review comments on
several versions of the document.
8.0 References 8.0 References
[1] Case, J., McCloghrie, K., Rose, M., and Waldbusser S., "Structure [1] Case, J., M. Fedor, M. Schoffstall, J. Davin, "Simple Network
of Management Information for Version 2 of the Simple Network Management Protocol", RFC 1157, SNMP Research, Performance Systems
Management Protocol (SNMPv2)", RFC 1902, January 1996. International, MIT Laboratory for Computer Science, May 1990.
[2] Postel, J., and Reynolds, J., "Telnet Protocol Specification", RFC
854, May 1983.
[3] Postel, J., and Reynolds, J., "Telnet Timing Mark Option", RFC 860,
May 1983.
[4] Rekhter, J., "Telnet 3270 Regime Option", RFC 1041, January 1988. [2] McCloghrie, K., and M. Rose, Editors, "Management Information Base
for Network Management of TCP/IP-based internets: MIB-II", STD 17,
RFC 1213, Hughes LAN Systems, Performance Systems International,
March 1991.
[5] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Transport [3] Case, J., McCloghrie, K., Rose, M., and Waldbusser S., "Structure
Mappings for Version 2 of the Simple Network Management Protocol of Management Information for Version 2 of the Simple Network
(SNMPv2)", RFC 1906, January 1996. Management Protocol (SNMPv2)", RFC 1902, January 1996.
[6] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Textual [4] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "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, January 1996.
[7] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Protocol [5] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S.,
"Conformance Statements for Version 2 of the Simple Network
Management Protocol (SNMPv2)", RFC 1904, January 1996.
[6] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Protocol
Operations for Version 2 of the Simple Network Management Protocol Operations for Version 2 of the Simple Network Management Protocol
(SNMPv2)", RFC 1905, January 1996. (SNMPv2)", RFC 1905, January 1996.
[8] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., [7] Harrington D., Presuhn, R., Wijnen, B., "An Architecture for
"Conformance Statements for Version 2 of the Simple Network Describing SNMP Management Frameworks", RFC 2271, Cabletron
Management Protocol (SNMPv2)", RFC 1904, January 1996. Systems, BMC Software, Inc., IBM T.J. Watson Research, January
1998.
[9] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Management [8] Harrington D., Presuhn, R., Wijnen, B., "Message Processing and
Information Base for Version 2 of the Simple Network Management Dispatching for the Simple Network Management Protocol (SNMP)", RFC
Protocol (SNMPv2)", RFC 1907, January 1996. 2272, Cabletron Systems, BMC Software, Inc., IBM T.J. Watson
Research, January 1998.
[10] McCloghrie, K., "TCP-MIB Definitions", November 1994. [9] Levi D., Meyer P., Stewart, B., "SNMPv3 Applications", RFC 2273,
SNMP Research, Inc., Secure Computing Corporation, Cisco Systems,
January 1998.
[11] Hinden, R., Deering, S., "IP Version 6 Addressing Architecture", [10] Blumenthal, U., Wijnen, B., "User-based Security Model (USM) for
<draft-ietf-ipngwg-addr-arch-v2-02.txt>, July 16, 1997. version 3 of the Simple Network Management Protocol (SNMPv3)", RFC
2274, IBM T. J. Watson Research, January 1998.
[12] Krupczak, Cheryl, Saperia, Jonathan, "Definitions of System-Level [11] Wijnen, B., Presuhn, R., McCloghrie, K., "View-based Access Control
Managed Objects for Applications", April 15, 1997. Model (VACM) for the Simple Network Management Protocol (SNMP)",
RFC 2275, IBM T.J. Watson Research, BMC Software, Inc., Cisco
Systems, Inc., January 1998.
[13] Bradner, S., "Key words for use in RFCs to Indicate Requirement [12] Postel, J., and Reynolds, J., "Telnet Protocol Specification", RFC
Levels", BCP 14, RFC 2119, March 1997. 854, May 1983.
[14] Kelly, B., "TN3270 Enhancements", RFC 1647, July 1994. [13] Postel, J., and Reynolds, J., "Telnet Timing Mark Option", RFC 860,
May 1983.
[15] Harrington, D., Presuhn, R., Wijnen, B., "An Architecture for [14] Rekhter, J., "Telnet 3270 Regime Option", RFC 1041, January 1988.
Describing SNMP Management Frameworks", RFC 2271, January 1998.
[16] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., [15] Kelly, B., "TN3270 Enhancements", RFC 1647, July 1994.
"Coexistence between Version 1 and Version 2 of the
Internet-standard Network Management Framework", RFC 1908, January [16] McCloghrie, K., "TCP-MIB Definitions", RFC 2012, November 1996.
1996.
[17] IBM, International Technical Support Centers, "Response Time Data
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.
[19] Bradner, S., "Key words for use in RFCs to Indicate Requirement
Levels", BCP 14, RFC 2119, March 1997.
[20] Hinden, R., Deering, S., "IP Version 6 Addressing Architecture",
<draft-ietf-ipngwg-addr-arch-v2-02.txt>, July 16, 1997.
[21] Krupczak, Cheryl, Saperia, Jonathan, "Definitions of System-Level
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
Phone: +1-919-254-0102
E-mail: kennethw@vnet.ibm.com E-mail: kennethw@vnet.ibm.com
Robert Moore Robert Moore
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
Phone: +1-919-254-7507 Phone: +1-919-254-4436
E-mail: remoore@us.ibm.com E-mail: remoore@us.ibm.com
10.0 Full Copyright Statement 10.0 Full Copyright Statement
Copyright (C) The Internet Society (1997). All Rights Reserved. Copyright (C) The Internet Society (1997). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it or others, and derivative works that comment on or otherwise explain it or
assist in its implementation may be prepared, copied, published and assist in its implementation may be prepared, copied, published and
distributed, in whole or in part, without restriction of any kind, distributed, in whole or in part, without restriction of any kind,
skipping to change at page 44, line 31 skipping to change at page 48, line 4
Standards process must be followed, or as required to translate it into Standards process must be followed, or as required to translate it into
languages other than English. languages other than English.
The limited permissions granted above are perpetual and will not be The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns. revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an "AS This document and the information contained herein is provided on an "AS
IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK
FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT
LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT
INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR
FITNESS FOR A PARTICULAR PURPOSE. FITNESS FOR A PARTICULAR PURPOSE.
Appendix A. IANATn3270eTC-MIB Appendix A. IANATn3270eTC-MIB
This appendix defines the current content of the IANATn3270eTC-MIB. This appendix defines the current content of the IANATn3270eTC-MIB.
This section should be removed from this document prior to its approval, This section should be removed from this document prior to its approval,
at which time this MIB will be administered by IANA. IANATn3270eTC-MIB at which time this MIB will be administered by IANA.
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 "9802020000Z" -- February 2, 1998
ORGANIZATION "IANA" ORGANIZATION "IANA"
skipping to change at page 45, line 51 skipping to change at page 49, 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."
-- Need a real OID assigned -- IANA will assign a real OID when they take over this module.
::= { experimental 2001 } ::= { experimental 2001 }
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
skipping to change at page 47, line 30 skipping to change at page 51, line 31
ENUMERATION OCTETs DESCRIPTION ENUMERATION OCTETs DESCRIPTION
none(0) 0 Not specified none(0) 0 Not specified
other(1) 1..512 Implementation specific other(1) 1..512 Implementation specific
ipv4(2) 6 4-octet IP Address plus ipv4(2) 6 4-octet IP Address plus
2-octet TCP Port 2-octet TCP Port
ipv6(3) 18 16-octet IPv6 Address ipv6(3) 18 16-octet IPv6 Address
plus 2-octet TCP Port plus 2-octet TCP Port
domainName(4) 1..512 The DNS name of a domainName(4) 1..512 The DNS name of a
client. client.
truncDomainName(5) 1..512 The truncated DNS name truncDomainName(5) 1..512 The (truncated) DNS name
of a client. of a client.
string(6) 1..512 Unknown Utf8String string(6) 1..512 Unknown Utf8String
certificate(7) 1..512 certificate certificate(7) 1..512 certificate
userId(8) 1..8 Client's userid userId(8) 1..8 Client's userid
x509dn(9) 1..512 X.509 Distinguished Name x509dn(9) 1..512 X.509 Distinguished Name
Representation of a certificate(7) may be lead to Representation of a certificate(7) may be lead to
a security exposure and is NOT RECOMMENDED without a security exposure and is NOT RECOMMENDED without
adequate security." adequate security."
SYNTAX INTEGER { SYNTAX INTEGER {
skipping to change at page 48, line 19 skipping to change at page 52, line 20
+------+----+---------+------------+ +------+----+---------+------------+
!length!type!TimeStamp! data ! !length!type!TimeStamp! data !
+------+----+---------+------------+ +------+----+---------+------------+
where where
length = one-octet length of the data portion of the length = one-octet length of the data portion of the
trace element, not including the length, trace element, not including the length,
type, and TimeStamp fields type, and TimeStamp fields
type = one-octet code point characterizing the data. type = one-octet code point characterizing the data.
TimeStamp = A 4 octet field that follows the TimeStamp TimeStamp = A 4-octet field representing the number of
(TimeTicks) textual convention as defined TimeTicks since the TN3270E server was last
by RFC 1903. activated. The server's last activation time
is available in the tn3270eSrvrConfLastActTime
object in the TN3270E MIB, which has the
syntax DateAndTime.
data = initial part of a PDU. data = initial part of a PDU.
length type length type
0-250 x'00' - unknown 0-250 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
skipping to change at page 48, line 54 skipping to change at page 53, line 4
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-250 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..256)) SYNTAX OCTET STRING (SIZE (0 | 6..261))
END END
 End of changes. 191 change blocks. 
424 lines changed or deleted 611 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/