AD | Application | AWS | Azure | Cloud | Database | Enterprise | Environmental | Event Log | File System | Infra | IoT | IT Service | Linux | Network/System | Performance | Protocol | SaaS | Security | Service Level | SNMP | Storage | VMware | VoIP | Web | Wireless

Crumbtrail

MonitorTools.com » Technical documentation » SNMP » MIB » RFC » TN3270E-MIB » Objects

TN3270E-MIB.mib object view, vendor RFC

Introduction

Most network devices and programs ship with so-called MIB files to describe the parameters and meanings (i.e.: friendly names) which are available for monitoring via SNMP.
ActiveXperts Network Monitor 2024 can import vendor-specific MIB files, so it can be used to monitor specific OID's (Object Identifiers). This way, you can monitor your devices, computers, etc. by selecting your relevant OID's by name.

ActiveXperts Network Monitor 2024 can import MIB file TN3270E-MIB and use it to monitor vendor specific OID's.

TN3270E-MIB file content

Object view of TN3270E-MIB:

Scalar Object
tn3270eSrvrConfEntry .1.3.6.1.2.1.34.8.1.1.1
Definition of the configuration elements for a single TN3270E server.
tn3270eSrvrPortEntry .1.3.6.1.2.1.34.8.1.2.1
Definition of a single TCP port assignment to a TN3270E server. Assignment of a port on a local address basis is enabled though use of tn3270eSrvrPortAddrType and tn3270eSrvrPortAddress. A TCP port assignment that is not restricted to a local address SHALL specify a tn3270eSrvrPortAddrType of unknown(0), and SHALL use a zero-length octet string for the tn3270eSrvrPortAddress.
tn3270eSrvrStatsEntry .1.3.6.1.2.1.34.8.1.3.1
A collection of statistical and maximum usage objects for a single TN3270 server. An entry can represent the total activity of the server, or it can represent the activity occurring at the server on either a port or a port-and-local-address basis. Collection of the statistics represented by the objects in this table is not mandatory. An implementation of this table MUST use only one of the three levels of refinement that this table supports for the entries associated with each TN3270E server. The indexing for a row that represents total server statistics is as follows: tn3270eSrvrConfIndex value identifying the server tn3270eSrvrPort 0 tn3270eSrvrPortAddrType unknown(0) tn3270eSrvrPortAddress zero-length octet string. On a port basis: tn3270eSrvrConfIndex value identifying the server tn3270eSrvrPort > 0 tn3270eSrvrPortAddrType unknown(0) tn3270eSrvrPortAddress zero-length octet string. On a port-and-local-address basis: tn3270eSrvrConfIndex value identifying the server tn3270eSrvrPort > 0 tn3270eSrvrPortAddrType valid value other than unknown(0) tn3270eSrvrPortAddress non-zero-length octet string.
tn3270eClientGroupEntry .1.3.6.1.2.1.34.8.1.4.1
Definition of a single client address entry. All entries with the same first two indexes, tn3270eSrvrConfIndex and tn3270eClientGroupName, are considered to be in the same client group.
tn3270eResPoolEntry .1.3.6.1.2.1.34.8.1.5.1
Definition of a single resource pool member. All entries with the same first two indexes, tn3270eSrvrConfIndex and tn3270eResPoolName, are considered to be in the same pool.
tn3270eSnaMapEntry .1.3.6.1.2.1.34.8.1.6.1
Definition of a single mapping from an SSCP-supplied SLU name to a local SLU name. Note: In certain pathological cases, it is possible that an SSCP will send on an ACTLU for a local LU an SLU name currently represented by an entry in this table that associates it with a different local LU. In these cases the association from the newer ACTLU SHOULD be the one represented in this table.
tn3270eClientResMapEntry .1.3.6.1.2.1.34.8.1.7.1
Definition of a single resource pool to client group mapping.
tn3270eResMapEntry .1.3.6.1.2.1.34.8.1.8.1
Definition of the mapping of a Resource Element to a client address.
tn3270eTcpConnEntry .1.3.6.1.2.1.34.8.1.9.1
Provides information about a single TN3270/TN3270E session. Note: a tn3270eSrvrConfIndex is not needed in this table, since the combination of remote and local addresses and ports is sufficient to guarantee uniqueness across the TN3270E servers 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.
tn3270eConfSpinLock .1.3.6.1.2.1.34.8.1.10
An advisory lock used to allow cooperating TN3270E-MIB applications to coordinate their use of the tn3270eSrvrConfTable, the tn3270eSrvrPortTable, the tn3270eClientGroupTable, the tn3270eResPoolTable, and the tn3270eClientResMapTable. When creating a new entry or altering an existing entry in the any of the tables mentioned above, an application should make use of tn3270eRtSpinLock to serialize application changes or additions. Since this is an advisory lock, the use of this lock is not enforced.
Tabular Object
tn3270eSrvrConfIndex .1.3.6.1.2.1.34.8.1.1.1.1
Identifier for a single TN3270E server. tn3270eSrvrConfIndex values need not be contiguous.
tn3270eSrvrConfInactivityTimeout .1.3.6.1.2.1.34.8.1.1.1.2
The inactivity time-out specified in seconds. When a connection has been inactive for the number of seconds specified by this object it is closed. Only user traffic is considered when determining whether there has been activity on a connection. The default value 0 means that no inactivity time-out is in effect.
tn3270eSrvrConfConnectivityChk .1.3.6.1.2.1.34.8.1.1.1.3
This object enables TIMING-MARK processing, NOP processing, or neither for a TN3270E server.
tn3270eSrvrConfTmNopInactTime .1.3.6.1.2.1.34.8.1.1.1.4
The amount of time a connection must have had no traffic on it in order for a TIMING-MARK or NOP request to be sent on the connection. This value applies only when connections are being examined for recent activity on a scan interval controlled by the value of the tn3270eSrvrConfTmNopInterval object.
tn3270eSrvrConfTmNopInterval .1.3.6.1.2.1.34.8.1.1.1.5
The scan interval to be used by a TN3270E server when it examines its Telnet connections for recent activity. The server scans its Telnet connections on the interval provided by this object, looking for ones that have been idle for more than the value provided by the tn3270eSrvrConfTmNopInactTime object. A TIMING-MARK or NOP request is sent for each connection that has exhibited no activity for this period of time.
tn3270eSrvrFunctionsSupported .1.3.6.1.2.1.34.8.1.1.1.6
This object indicates the functions supported by a TN3270E server.
tn3270eSrvrConfAdminStatus .1.3.6.1.2.1.34.8.1.1.1.7
The desired state of the TN3270E server represented by this entry in the table: up(1) - Activate this TN3270E server. down(2) - Informs the associated TN3270E server to gracefully terminate its processing. stopImmediate(3) - Informs the associated TN3270E server to terminate itself immediately. When a managed system creates an entry in this table, tn3270eSrvrConfAdminStatus and tn3270eSrvrConfOperStatus are initialized as up(1) by default. The exact behavior of a server in response to a down(2) or stopImmediate(3) command is left implementation- dependent. A TN3270E server that is capable of it SHOULD close all of its TN3270 and TN3270E sessions during a graceful termination. Often the function enabled via stopImmediate(3) is used as a last resort by a system administrator, to attempt to either bring down a hung TN3270E server or free up its resources immediately to aid in general system availability, or to shut down a TN3270E server that is not recognizing a down(2) request. A TN3270E server that does not distinguish between down(2) or stopImmediate(3) transitions should not support stopImmediate(3).
tn3270eSrvrConfOperStatus .1.3.6.1.2.1.34.8.1.1.1.8
The current operational state of a TN3270E server. The following values are defined: up(1) - the server is active and accepting new client connections down(2) - the server is not active 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.
tn3270eSrvrConfSessionTermState .1.3.6.1.2.1.34.8.1.1.1.9
This object determines what a TN3270E server should do when a TN3270 Session terminates: terminate(1) => Terminate the TCP connection. luSessionPend(2) => Do not drop the TCP connection associated with a client when its TN3270 session ends. Processing should redrive session initialization as if the client were first connecting. queueSession(3) => This value relates to the Close Destination PASS (CLSDST PASS) operation in VTAM. An example provides the easiest explanation. Suppose a TN3270E client is in session with APPL1, and APPL1 does a CLSDST PASS of the client's session to APPL2. queueSession(3) specifies that the TN3270E server must keep the TCP connection with the client active after it receives the UNBIND from APPL1, waiting for the BIND from APPL2.
tn3270eSrvrConfSrvrType .1.3.6.1.2.1.34.8.1.1.1.10
This object indicates the type of TN3270E server. The existence of MIB tables and objects that will be defined by follow-on MIBs may be predicated on whether the TN3270E server can be local to the same host as a target application (host(1)) or will always be remote (gateway(2)). A host TN3270E server refers to an implementation where the TN3270E server is collocated with the Systems Network Architecture (SNA) System Services Control Point (SSCP) for the dependent Secondary Logical Units (SLUs) that the server makes available to its clients for connecting into an SNA network. A gateway TN3270E server resides on an SNA node other than an SSCP, either an SNA type 2.0 node or an APPN node acting in the role of a Dependent LU Requester (DLUR). Host and gateway TN3270E server implementations typically differ greatly as to their internal implementation and system definition (SYSDEF) requirements.
tn3270eSrvrConfContact .1.3.6.1.2.1.34.8.1.1.1.11
This object provides a scratch pad for a TN3270E server administrator for storing information for later retrieval.
tn3270eSrvrConfRowStatus .1.3.6.1.2.1.34.8.1.1.1.12
This object allows entries to be created and deleted 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 this object to destroy(6)), this has the side-effect of removing all the associated entries (i.e., those having the same tn3270eSrvrConfIndex) from the tn3270eSrvrPortTable, the tn3270eSrvrStatsTable, the tn3270eClientGroupTable, the tn3270eResPoolTable, the tn3270eSnaMapTable, the tn3270eClientResMapTable, and the tn3270eResMapTable. All entries in the tn3270eTcpConnTable that belong to a TN3270E server that has been deleted MUST also be removed. In other words, a tn3270eSrvrConfEntry must exist for a TN3270E server in order for it to have entries in any of the other tables defined by this MIB.
tn3270eSrvrConfLastActTime .1.3.6.1.2.1.34.8.1.1.1.13
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).
tn3270eSrvrConfTmTimeout .1.3.6.1.2.1.34.8.1.1.1.14
The TIMING-MARK time-out, specified in seconds.
tn3270eSrvrPort .1.3.6.1.2.1.34.8.1.2.1.1
Indicates a port assigned to a server.
tn3270eSrvrPortAddrType .1.3.6.1.2.1.34.8.1.2.1.2
Indicates the type of an address local to the host on which the TN3270E server resides that is represented in tn3270eSrvrPortAddress. A value of unknown(0) SHALL be used for this object when the port is not to be restricted to a local address.
tn3270eSrvrPortAddress .1.3.6.1.2.1.34.8.1.2.1.3
A local address on the host that a TN3270E server resides on that is associated with a TCP port that is to be used or is in use by a TN3270E server. tn3270eClientGroupAddrType indicates the address type (IPv4 or IPv6, for example). A zero-length octet string SHALL be used as the value of this object when a local address isn't being specified.
tn3270eSrvrPortRowStatus .1.3.6.1.2.1.34.8.1.2.1.4
This object allows entries to be created and deleted 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 to destroy(6). Deletion of a tn3270eSrvrPortEntry has no effect on any other table entry defined by this MIB.
tn3270eSrvrStatsUpTime .1.3.6.1.2.1.34.8.1.3.1.2
The value of the sysUpTime object the last time the TN3270E server was re-initialized. 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.
tn3270eSrvrStatsMaxTerms .1.3.6.1.2.1.34.8.1.3.1.3
Indicates the maximum number of terminal LUs available for use at a TN3270E server for the granularity of this conceptual row (server-wide, port, or port-and-local-address).
tn3270eSrvrStatsInUseTerms .1.3.6.1.2.1.34.8.1.3.1.4
Indicates the number of terminal LUs currently in use at a TN3270E server for the granularity of this conceptual row (server-wide, port, or port-and-local-address).
tn3270eSrvrStatsSpareTerms .1.3.6.1.2.1.34.8.1.3.1.5
Indicates the number of free terminal LUs at a TN3270E server for the granularity of this conceptual row (server-wide, port, or port-and-local-address). It is possible that the difference between tn3270eSrvrStatsMaxTerms and tn3270eSrvrStatsInUseTerms in a conceptual row does not equal the value of tn3270eSrvrStatsSpareTerms in that row: an LU may exist but not be usable by a client connection. Alternatively, the administrative ceiling represented by tn3270eSrvrStatsMaxTerms may have been lowered to a point where it is less than the current value of tn3270eSrvrStatsInUseTerms. In this case tn3270eSrvrStatsSpareTerms returns the value 0.
tn3270eSrvrStatsMaxPtrs .1.3.6.1.2.1.34.8.1.3.1.6
Indicates the maximum number of printer resources available for use by a TN3270E server for the granularity of this conceptual row (server-wide, port, or port-and-local-address).
tn3270eSrvrStatsInUsePtrs .1.3.6.1.2.1.34.8.1.3.1.7
Indicates the number of printer resources currently in use by a TN3270E server for the granularity of this conceptual row (server-wide, port, or port-and-local-address).
tn3270eSrvrStatsSparePtrs .1.3.6.1.2.1.34.8.1.3.1.8
Indicates the number of free printer resources at a TN3270E server for the granularity of this conceptual row (server-wide, port, or port-and-local-address). It is possible that the difference between 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. Alternatively, the administrative ceiling represented by tn3270eSrvrStatsMaxPtrs may have been lowered to a point where it is less than the current value of tn3270eSrvrStatsInUsePtrs. In this case tn3270eSrvrStatsSparePtrs returns the value 0.
tn3270eSrvrStatsInConnects .1.3.6.1.2.1.34.8.1.3.1.9
Indicates the number of client (TCP) connections that succeeded at a TN3270E server for the granularity of this conceptual row (server-wide, port, or port-and-local-address). The tn3270eSrvrStatsConnResrceRejs and tn3270eSrvrStatsConnErrorRejs objects provide a count of failed connection attempts. A Management Station can detect discontinuities in this counter by monitoring the tn3270eSrvrStatsUpTime object.
tn3270eSrvrStatsConnResrceRejs .1.3.6.1.2.1.34.8.1.3.1.10
Indicates the number of (TCP) connections rejected during connection setup at a TN3270E server for the granularity of this conceptual row (server-wide, port, or port-and-local-address) due to a lack of resources at the server. An example of when this counter would be incremented is when no terminal or printer resource is available to associate with a client's TCP connection. A Management Station can detect discontinuities in this counter by monitoring the tn3270eSrvrStatsUpTime object.
tn3270eSrvrStatsDisconnects .1.3.6.1.2.1.34.8.1.3.1.11
Indicates the number of (TCP) connections that were 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.
tn3270eSrvrStatsHCInOctets .1.3.6.1.2.1.34.8.1.3.1.12
Indicates the number of octets received from TN3270 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.
tn3270eSrvrStatsInOctets .1.3.6.1.2.1.34.8.1.3.1.13
Low-order 32 bits of tn3270eSrvrStatsHCInOctets for this conceptual row. A Management Station can detect discontinuities in this counter by monitoring the tn3270eSrvrStatsUpTime object.
tn3270eSrvrStatsHCOutOctets .1.3.6.1.2.1.34.8.1.3.1.14
Indicates the number of octets sent to TN3270 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.
tn3270eSrvrStatsOutOctets .1.3.6.1.2.1.34.8.1.3.1.15
Low-order 32 bits of tn3270eSrvrStatsHCOutOctets for this conceptual row. A Management Station can detect discontinuities in this counter by monitoring the tn3270eSrvrStatsUpTime object.
tn3270eSrvrStatsConnErrorRejs .1.3.6.1.2.1.34.8.1.3.1.16
Indicates the number of (TCP) connections rejected during connection setup at a TN3270E server for the granularity of this conceptual row (server-wide, port, or port-and-local-address) due to an error of some type. An example of when this counter would be incremented is when the client and the server cannot agree on a common set of TN3270E functions for the connection. A Management Station can detect discontinuities in this counter by monitoring the tn3270eSrvrStatsUpTime object.
tn3270eClientGroupName .1.3.6.1.2.1.34.8.1.4.1.1
The name of a client group. Note: client group names are required to be unique only with respect to a single TN3270E server.
tn3270eClientGroupAddrType .1.3.6.1.2.1.34.8.1.4.1.2
Indicates the type of the address represented in tn3270eClientGroupAddress.
tn3270eClientGroupAddress .1.3.6.1.2.1.34.8.1.4.1.3
The client address of a member of a client group. The value of tn3270eClientGroupAddrType indicates the address type (IPv4 or IPv6, for example).
tn3270eClientGroupSubnetMask .1.3.6.1.2.1.34.8.1.4.1.4
The corresponding subnet mask associated with tn3270eClientGroupAddress. A single IP address is represented by having this object contain the value of 255.255.255.255. This object's value is meaningful only if tn3270eClientGroupAddrType has a value of ipv4(1).
tn3270eClientGroupPfxLength .1.3.6.1.2.1.34.8.1.4.1.5
The corresponding IPv6 network prefix length. This object's value is meaningful only if tn3270eClientGroupAddrType has a value of ipv6(2).
tn3270eClientGroupRowStatus .1.3.6.1.2.1.34.8.1.4.1.6
This object allows entries to be created and deleted 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 to destroy(6). When the number of entries in this table for a given client group becomes 0, this has the side- effect of removing any entries for the group in the tn3270eClientResMapTable.
tn3270eResPoolName .1.3.6.1.2.1.34.8.1.5.1.1
The name of a resource pool.
tn3270eResPoolElementName .1.3.6.1.2.1.34.8.1.5.1.2
The name of a member of a resource pool.
tn3270eResPoolElementType .1.3.6.1.2.1.34.8.1.5.1.3
The type of the entity in a resource pool.
tn3270eResPoolRowStatus .1.3.6.1.2.1.34.8.1.5.1.4
This object allows entries to be created and deleted 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 to destroy(6). When all entries in this table associated with the same tn3270eResPoolElementName have been removed, then any associated (tn3270eResPoolElementName matching tn3270eClientResMapPoolName with same tn3270eSrvrConfIndex values) entries in the tn3270eClientResMapTable SHALL also be removed.
tn3270eSnaMapSscpSuppliedName .1.3.6.1.2.1.34.8.1.6.1.1
The name of the secondary LU (SLU) as it is known in the SNA network. This name is sent by the SSCP on the Activate Logical Unit (ACTLU) request.
tn3270eSnaMapLocalName .1.3.6.1.2.1.34.8.1.6.1.2
The local name of the secondary LU (SLU).
tn3270eSnaMapPrimaryLuName .1.3.6.1.2.1.34.8.1.6.1.3
When there is a currently active LU-LU session for this connection, this object returns the primary LU (PLU) name from the BIND. When there is no active LU-LU session, or when the PLU name is unavailable for some other reason, this object returns a zero-length octet string.
tn3270eClientResMapPoolName .1.3.6.1.2.1.34.8.1.7.1.1
The name of a resource pool.
tn3270eClientResMapClientGroupName .1.3.6.1.2.1.34.8.1.7.1.2
The name of the client group that is mapped to a resource pool.
tn3270eClientResMapClientPort .1.3.6.1.2.1.34.8.1.7.1.3
A port number restricting the scope of a mapping from a resource pool to a client group. The value 0 for this object indicates that the scope of the mapping is not restricted.
tn3270eClientResMapRowStatus .1.3.6.1.2.1.34.8.1.7.1.4
This object allows entries to be created and deleted 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 to destroy(6). Removing an entry from this table doesn't affect any other table entry defined in this MIB.
tn3270eResMapElementName .1.3.6.1.2.1.34.8.1.8.1.1
The name of a resource element. This is the name by which the server implementing this table knows the resource. It may be different from the name by which the resource is known in the SNA network. This latter name is returned in the tn3270eResMapSscpSuppliedName object.
tn3270eResMapAddrType .1.3.6.1.2.1.34.8.1.8.1.2
Indicates the type of the client address represented in tn3270eResMapAddress.
tn3270eResMapAddress .1.3.6.1.2.1.34.8.1.8.1.3
A client address.
tn3270eResMapPort .1.3.6.1.2.1.34.8.1.8.1.4
A client port.
tn3270eResMapElementType .1.3.6.1.2.1.34.8.1.8.1.5
The type of the associated resource element.
tn3270eResMapSscpSuppliedName .1.3.6.1.2.1.34.8.1.8.1.6
The name of the secondary LU (SLU) as it is known in a SNA network. This name is sent by the SSCP on the Activate Logical Unit (ACTLU) request. If this name is not known, this object returns a zero-length octet string.
tn3270eTcpConnRemAddrType .1.3.6.1.2.1.34.8.1.9.1.1
Indicates the type of the value of the tn3270eTcpConnRemAddress object. For example, ipv4(1) or ipv6(2).
tn3270eTcpConnRemAddress .1.3.6.1.2.1.34.8.1.9.1.2
The remote address associated with a TN3270E client. tn3270eTcpConnRemAddrType indicates the address type (IPv4 or IPv6, for example). If a TN3270(E) client is connected to its server via a proxy client the address represented by the value of this object shall be the remote client's address, not the proxy client's address.
tn3270eTcpConnRemPort .1.3.6.1.2.1.34.8.1.9.1.3
The remote port associated with a TN3270E client. The value 0 is used if the tn3270eTcpConnRemAddrType identifies an address type that does not support ports. If a TN3270(E) client is connected to its server via a proxy client, the port represented by the value of this object shall be the remote client's port, not the proxy client's port.
tn3270eTcpConnLocalAddrType .1.3.6.1.2.1.34.8.1.9.1.4
Indicates the type of the value of the tn3270eTcpConnLocalAddress object. For example, ipv4(1) or ipv6(2).
tn3270eTcpConnLocalAddress .1.3.6.1.2.1.34.8.1.9.1.5
The local address associated with a TN3270E client. tn3270eTcpConnRemAddrType indicates the address type (IPv4 or IPv6, for example).
tn3270eTcpConnLocalPort .1.3.6.1.2.1.34.8.1.9.1.6
The remote port associated with a TN3270E client.
tn3270eTcpConnLastActivity .1.3.6.1.2.1.34.8.1.9.1.7
The number of 100ths of seconds since any data was transferred for the associated TCP Connection.
tn3270eTcpConnBytesIn .1.3.6.1.2.1.34.8.1.9.1.8
The number of bytes received by the server from TCP for this connection. A Management Station can detect discontinuities in this counter by monitoring the tn3270eTcpConnActivationTime object.
tn3270eTcpConnBytesOut .1.3.6.1.2.1.34.8.1.9.1.9
The number of bytes sent to TCP for this connection. A Management Station can detect discontinuities in this counter by monitoring the tn3270eTcpConnActivationTime object.
tn3270eTcpConnResourceElement .1.3.6.1.2.1.34.8.1.9.1.10
LU/Print secondary name for connecting an client into an SNA network.
tn3270eTcpConnResourceType .1.3.6.1.2.1.34.8.1.9.1.11
Indicates the type of resource identified by tn3270eTcpConnResourceElement.
tn3270eTcpConnDeviceType .1.3.6.1.2.1.34.8.1.9.1.12
Indicates the device type if negotiated with the client. A value of unknown(100) should be used as the value of this object when a device type is not negotiated. Refer to RFC 2355 for how device types can be negotiated.
tn3270eTcpConnFunctions .1.3.6.1.2.1.34.8.1.9.1.13
This object indicates which of the TN3270 and TN3270E functions were negotiated by the server and the client for this TCP connection. Refer to tn3270eSrvrFunctionsSupported for the list of these functions supported by the server.
tn3270eTcpConnId .1.3.6.1.2.1.34.8.1.9.1.14
The connection identifier associated with a TN3270 or a TN3270E session's TCP connection. TCP implementations often assign a unique (with respect to itself) unsigned integer as an identifier for a TCP connection. The value 0 indicates that a connection does not have a valid connection identifier.
tn3270eTcpConnClientIdFormat .1.3.6.1.2.1.34.8.1.9.1.15
The format of a corresponding tn3270eTcpConnClientId object as defined by the IANSTn3270eClientType textual convention imported from the IANATn3270eTC-MIB.
tn3270eTcpConnClientId .1.3.6.1.2.1.34.8.1.9.1.16
Additional client identification information. The type of this information is indicated by the value of the corresponding tn3270eTcpConnClientIdFormat object. All values are returned in network-byte order. The purpose of this object is to provide an alternate means of identifying a client, other than though the remote address returned in tn3270eTcpConnRemAddress.
tn3270eTcpConnTraceData .1.3.6.1.2.1.34.8.1.9.1.17
Trace data for this session.
tn3270eTcpConnLogInfo .1.3.6.1.2.1.34.8.1.9.1.18
Log information, encoded as specified in the IANATn3270eLogData textual convention from the IANAtn3270eTC-MIB.
tn3270eTcpConnLuLuBindImage .1.3.6.1.2.1.34.8.1.9.1.19
When there is a currently active LU-LU session for this connection, this object returns the BIND Image (defined to be bytes 1-p of the complete BIND Request Unit -- see 'SNA Formats' for more information) that was received from the PLU during session activation. When there is no active LU-LU session, or when a BIND image is unavailable for some other reason, this object returns a zero-length octet string.
tn3270eTcpConnSnaState .1.3.6.1.2.1.34.8.1.9.1.20
The current state of the SNA side of the end-to-end TN3270 connection. The following states are defined: unknown(1) - The true state is not known. noSluSession(2) - The SLU has neither an SSCP-LU nor an LU-LU session active. sscpLuSession(3) - The SSCP-LU session for the SLU is active, but the SLU is not currently in session with a PLU. luLuSession(4) - The SLU is currently in session with a PLU, but the SSCP-LU session for the LU is not active. sscpLuSessionAndLuLuSession(5) - The SLU currently has an active session with a PLU, and the SSCP-LU session for the SLU is active.
tn3270eTcpConnStateLastDiscReason .1.3.6.1.2.1.34.8.1.9.1.21
The last disconnect reason. A session that has not experienced a disconnect shall use the value unknown(1) for this object. Depending on when an implementation removes entries from this table, certain states may never be returned.
tn3270eTcpConnSrvrConfIndex .1.3.6.1.2.1.34.8.1.9.1.22
tn3270eSrvrConfIndex of the tn3270eSrvrConfEntry belonging to the TN3270E server to which this entry belongs.
tn3270eTcpConnActivationTime .1.3.6.1.2.1.34.8.1.9.1.23
The value of the sysUpTime object the last time this TCP connection became active.
Table
tn3270eSrvrConfTable .1.3.6.1.2.1.34.8.1.1
This table defines the configuration elements for TN3270E servers. The number of entries in this table is expected to vary depending on the location of the table. A particular TN3270E server is expected to have a single entry. Modeling of the configuration elements as a table allows multiple TN3270E 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.
tn3270eSrvrPortTable .1.3.6.1.2.1.34.8.1.2
This table defines the TCP ports associated with TN3270E servers. No entry in this table shall exist without a corresponding (same tn3270eSrvrConfIndex) 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.
tn3270eSrvrStatsTable .1.3.6.1.2.1.34.8.1.3
This table defines a set of statistics concerning TN3270E server performance. No entry in this table shall exist without a corresponding (same tn3270eSrvrConfIndex) entry in the tn3270eSrvrConfTable existing.
tn3270eClientGroupTable .1.3.6.1.2.1.34.8.1.4
This table defines client address groupings for use by a TN3270E server. No entry in this table shall exist without a corresponding (same tn3270eSrvrConfIndex) 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.
tn3270eResPoolTable .1.3.6.1.2.1.34.8.1.5
This table defines resource groupings; the term 'pool' is used as it is defined by RFC 2355. No entry in this table shall exist without a corresponding (same tn3270eSrvrConfIndex) 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.
tn3270eSnaMapTable .1.3.6.1.2.1.34.8.1.6
This table provide a mapping from the name by which a secondary LU is known in the SNA network to the name by which it is known locally at the TN3270e server. This latter name serves as an index into the tn3270eResPoolTable and the tn3270eResMapTable. No entry in this table shall exist without a corresponding (same tn3270eSrvrConfIndex) entry in the tn3270eSrvrConfTable existing.
tn3270eClientResMapTable .1.3.6.1.2.1.34.8.1.7
This table defines resource-pool to client-group mappings. Since both the resource pool name and client group name are included in the index clause of this table, multiple resource pools can be assigned to the same client group. This enables use of multiple resource pools for use in client to resource mapping. Assigning multiple client groups to the same resource pool is also allowed, but is not the primary purpose for how the indexing is structured. Assignment of a resource pool to client group can be restricted based on TCP port. An index value of 0 for tn3270eClientResMapClientPort disables restriction of resource assignment based on client target port selection. No entry in this table shall exist without a corresponding (same tn3270eSrvrConfIndex) 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.
tn3270eResMapTable .1.3.6.1.2.1.34.8.1.8
This table defines the actual mapping of a resource to a client address. No entry in this table shall exist without a corresponding (same tn3270eSrvrConfIndex) entry in the tn3270eSrvrConfTable existing.
tn3270eTcpConnTable .1.3.6.1.2.1.34.8.1.9
This table has an entry for each TN3270(E) client connection that is currently active at a TN3270E server. An implementation MAY retain entries for connections that have been terminated, but which entries are retained, how many entries are retained, and how long they are retained is entirely implementation-dependent. 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.
Object Identifier
tn3270eMIB .1.3.6.1.2.1.34.8
This module defines a portion of the management information base (MIB) for managing TN3270E servers.
tn3270eNotifications .1.3.6.1.2.1.34.8.0
tn3270eObjects .1.3.6.1.2.1.34.8.1
tn3270eConformance .1.3.6.1.2.1.34.8.3
tn3270eGroups .1.3.6.1.2.1.34.8.3.1
tn3270eCompliances .1.3.6.1.2.1.34.8.3.2
Group
tn3270eBasicGroup .1.3.6.1.2.1.34.8.3.1.1
This group is mandatory for all hosts supporting the TN3270E-MIB.
tn3270eSessionGroup .1.3.6.1.2.1.34.8.3.1.2
This group is mandatory for all hosts supporting the TN3270E-MIB.
tn3270eResMapGroup .1.3.6.1.2.1.34.8.3.1.3
This group is optional for all hosts supporting the TN3270E-MIB.
tn3270eHiCapacityGroup .1.3.6.1.2.1.34.8.3.1.4
Support of these objects is REQUIRED when the Counter32 versions can potentially wrap too frequently. This group is optional for all other hosts supporting the TN3270E-MIB. The IF-MIB (RFC 2233) requires that the 64-bit versions of its counters be implemented when an interface can support rates of around 20 million bits per second or greater. This implies a minimum wrap rate of just over 28 minutes. It is recommended that this same guideline be used for determining 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.