TN3270E-MIB
Detailed view of the defined objects, syntax rules, and hierarchical paths.
108
Objects
Active
Status
8
Dependencies
Imported Objects
Objects
108 total| Object Name |
|---|
tn3270eMIB OBJECT IDENTIFIER .1.3.6.1.4.1.727.7.2.1.34.8 |
SNMPv2-SMI-v1 Unknown .1.3.6.1.4.1.727.7.2.1.34.8 |
tn3270eNotifications OBJECT IDENTIFIER .1.3.6.1.4.1.727.7.2.1.34.8.0 |
tn3270eObjects OBJECT IDENTIFIER .1.3.6.1.4.1.727.7.2.1.34.8.1 |
tn3270eSrvrConfTableThis 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. SEQUENCE OF Tn3270eSrvrConfEntry .1.3.6.1.4.1.727.7.2.1.34.8.1.1 |
tn3270eSrvrConfEntryDefinition of the configuration elements for a single
TN3270E server. Tn3270eSrvrConfEntry .1.3.6.1.4.1.727.7.2.1.34.8.1.1.1 |
tn3270eSrvrConfIndexIdentifier for a single TN3270E server.
tn3270eSrvrConfIndex values need not be
contiguous. Unsigned32 .1.3.6.1.4.1.727.7.2.1.34.8.1.1.1.1 |
tn3270eSrvrConfInactivityTimeoutThe 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.rw Unsigned32 .1.3.6.1.4.1.727.7.2.1.34.8.1.1.1.2 |
tn3270eSrvrConfConnectivityChkThis object enables TIMING-MARK processing, NOP
processing, or neither for a TN3270E server.rw Enumeration .1.3.6.1.4.1.727.7.2.1.34.8.1.1.1.3 |
tn3270eSrvrConfTmNopInactTimeThe 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.rw Unsigned32 .1.3.6.1.4.1.727.7.2.1.34.8.1.1.1.4 |
tn3270eSrvrConfTmNopIntervalThe 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.rw Unsigned32 .1.3.6.1.4.1.727.7.2.1.34.8.1.1.1.5 |
tn3270eSrvrFunctionsSupportedThis object indicates the functions supported by a
TN3270E server.ro IANATn3270Functions -- Rsyntax OCTET STRING .1.3.6.1.4.1.727.7.2.1.34.8.1.1.1.6 |
tn3270eSrvrConfAdminStatusThe 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).rw Enumeration .1.3.6.1.4.1.727.7.2.1.34.8.1.1.1.7 |
tn3270eSrvrConfOperStatusThe 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.ro Enumeration .1.3.6.1.4.1.727.7.2.1.34.8.1.1.1.8 |
tn3270eSrvrConfSessionTermStateThis 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.rw Enumeration .1.3.6.1.4.1.727.7.2.1.34.8.1.1.1.9 |
tn3270eSrvrConfSrvrTypeThis 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.ro Enumeration .1.3.6.1.4.1.727.7.2.1.34.8.1.1.1.10 |
tn3270eSrvrConfContactThis object provides a scratch pad for a TN3270E
server administrator for storing information for
later retrieval.rw SnmpAdminString -- Rsyntax OCTET STRING .1.3.6.1.4.1.727.7.2.1.34.8.1.1.1.11 |
tn3270eSrvrConfRowStatusThis 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.rw RowStatus -- Rsyntax INTEGER { -- active(1), -- notInService(2), -- notReady(3), -- createAndGo(4), -- createAndWait(5), -- destroy(6) -- } .1.3.6.1.4.1.727.7.2.1.34.8.1.1.1.12 |
tn3270eSrvrConfLastActTimeThis 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).ro DateAndTime -- Rsyntax OCTET STRING .1.3.6.1.4.1.727.7.2.1.34.8.1.1.1.13 |
tn3270eSrvrConfTmTimeoutThe TIMING-MARK time-out, specified in seconds.rw Unsigned32 .1.3.6.1.4.1.727.7.2.1.34.8.1.1.1.14 |
tn3270eSrvrPortTableThis 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. SEQUENCE OF Tn3270eSrvrPortEntry .1.3.6.1.4.1.727.7.2.1.34.8.1.2 |
tn3270eSrvrPortEntryDefinition 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. Tn3270eSrvrPortEntry .1.3.6.1.4.1.727.7.2.1.34.8.1.2.1 |
tn3270eSrvrPortIndicates a port assigned to a server. Unsigned32 .1.3.6.1.4.1.727.7.2.1.34.8.1.2.1.1 |
tn3270eSrvrPortAddrTypeIndicates 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. IANATn3270eAddrType -- Rsyntax INTEGER { -- unknown(0), -- ipv4(1), -- ipv6(2) -- } .1.3.6.1.4.1.727.7.2.1.34.8.1.2.1.2 |
tn3270eSrvrPortAddressA 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. IANATn3270eAddress -- Rsyntax OCTET STRING .1.3.6.1.4.1.727.7.2.1.34.8.1.2.1.3 |
tn3270eSrvrPortRowStatusThis 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.rw RowStatus -- Rsyntax INTEGER { -- active(1), -- notInService(2), -- notReady(3), -- createAndGo(4), -- createAndWait(5), -- destroy(6) -- } .1.3.6.1.4.1.727.7.2.1.34.8.1.2.1.4 |
tn3270eSrvrStatsTableThis 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. SEQUENCE OF Tn3270eSrvrStatsEntry .1.3.6.1.4.1.727.7.2.1.34.8.1.3 |
tn3270eSrvrStatsEntryA 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. Tn3270eSrvrStatsEntry .1.3.6.1.4.1.727.7.2.1.34.8.1.3.1 |
tn3270eSrvrStatsUpTimeThe 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.ro TimeStamp -- Rsyntax TimeTicks .1.3.6.1.4.1.727.7.2.1.34.8.1.3.1.2 |
tn3270eSrvrStatsMaxTermsIndicates 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).ro Unsigned32 -- Rsyntax Gauge32 -- Units -- LUs .1.3.6.1.4.1.727.7.2.1.34.8.1.3.1.3 |
tn3270eSrvrStatsInUseTermsIndicates 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).ro Gauge32 -- Units -- LUs .1.3.6.1.4.1.727.7.2.1.34.8.1.3.1.4 |
tn3270eSrvrStatsSpareTermsIndicates 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.ro Gauge32 -- Units -- LUs .1.3.6.1.4.1.727.7.2.1.34.8.1.3.1.5 |
tn3270eSrvrStatsMaxPtrsIndicates 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).ro Unsigned32 -- Rsyntax Gauge32 -- Units -- Printer Resources .1.3.6.1.4.1.727.7.2.1.34.8.1.3.1.6 |
tn3270eSrvrStatsInUsePtrsIndicates 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).ro Gauge32 -- Units -- Printer Resources .1.3.6.1.4.1.727.7.2.1.34.8.1.3.1.7 |
tn3270eSrvrStatsSparePtrsIndicates 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.ro Gauge32 -- Units -- Spare Printer Resources .1.3.6.1.4.1.727.7.2.1.34.8.1.3.1.8 |
tn3270eSrvrStatsInConnectsIndicates 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.ro Counter32 -- Units -- connections .1.3.6.1.4.1.727.7.2.1.34.8.1.3.1.9 |
tn3270eSrvrStatsConnResrceRejsIndicates 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.ro Counter32 -- Units -- connection attempts .1.3.6.1.4.1.727.7.2.1.34.8.1.3.1.10 |
tn3270eSrvrStatsDisconnectsIndicates 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.ro Counter32 -- Units -- disconnections .1.3.6.1.4.1.727.7.2.1.34.8.1.3.1.11 |
tn3270eSrvrStatsInOctetsLow-order 32 bits of tn3270eSrvrStatsHCInOctets for
this conceptual row.
A Management Station can detect discontinuities in
this counter by monitoring the tn3270eSrvrStatsUpTime
object.ro Counter32 -- Units -- octets .1.3.6.1.4.1.727.7.2.1.34.8.1.3.1.13 |
tn3270eSrvrStatsOutOctetsLow-order 32 bits of tn3270eSrvrStatsHCOutOctets for
this conceptual row.
A Management Station can detect discontinuities in
this counter by monitoring the tn3270eSrvrStatsUpTime
object.ro Counter32 -- Units -- octets .1.3.6.1.4.1.727.7.2.1.34.8.1.3.1.15 |
tn3270eSrvrStatsConnErrorRejsIndicates 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.ro Counter32 -- Units -- connection attempts .1.3.6.1.4.1.727.7.2.1.34.8.1.3.1.16 |
tn3270eClientGroupTableThis 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. SEQUENCE OF Tn3270eClientGroupEntry .1.3.6.1.4.1.727.7.2.1.34.8.1.4 |
tn3270eClientGroupEntryDefinition 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. Tn3270eClientGroupEntry .1.3.6.1.4.1.727.7.2.1.34.8.1.4.1 |
tn3270eClientGroupNameThe name of a client group. Note: client group
names are required to be unique only with respect
to a single TN3270E server. Utf8String .1.3.6.1.4.1.727.7.2.1.34.8.1.4.1.1 |
tn3270eClientGroupAddrTypeIndicates the type of the address represented in
tn3270eClientGroupAddress. IANATn3270eAddrType -- Rsyntax INTEGER { -- unknown(0), -- ipv4(1), -- ipv6(2) -- } .1.3.6.1.4.1.727.7.2.1.34.8.1.4.1.2 |
tn3270eClientGroupAddressThe client address of a member of a client group.
The value of tn3270eClientGroupAddrType indicates
the address type (IPv4 or IPv6, for example). IANATn3270eAddress -- Rsyntax OCTET STRING .1.3.6.1.4.1.727.7.2.1.34.8.1.4.1.3 |
tn3270eClientGroupSubnetMaskThe 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).rw IpAddress .1.3.6.1.4.1.727.7.2.1.34.8.1.4.1.4 |
tn3270eClientGroupPfxLengthThe corresponding IPv6 network prefix length.
This object's value is meaningful only if
tn3270eClientGroupAddrType has a value of ipv6(2).rw Unsigned32 .1.3.6.1.4.1.727.7.2.1.34.8.1.4.1.5 |
tn3270eClientGroupRowStatusThis 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.rw RowStatus -- Rsyntax INTEGER { -- active(1), -- notInService(2), -- notReady(3), -- createAndGo(4), -- createAndWait(5), -- destroy(6) -- } .1.3.6.1.4.1.727.7.2.1.34.8.1.4.1.6 |
tn3270eResPoolTableThis 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. SEQUENCE OF Tn3270eResPoolEntry .1.3.6.1.4.1.727.7.2.1.34.8.1.5 |
tn3270eResPoolEntryDefinition 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. Tn3270eResPoolEntry .1.3.6.1.4.1.727.7.2.1.34.8.1.5.1 |
tn3270eResPoolNameThe name of a resource pool. Utf8String .1.3.6.1.4.1.727.7.2.1.34.8.1.5.1.1 |
tn3270eResPoolElementNameThe name of a member of a resource pool. SnaResourceName -- Rsyntax OCTET STRING .1.3.6.1.4.1.727.7.2.1.34.8.1.5.1.2 |
tn3270eResPoolElementTypeThe type of the entity in a resource pool.rw IANATn3270ResourceType -- Rsyntax INTEGER { -- other(1), -- terminal(2), -- printer(3), -- terminalOrPrinter(4) -- } .1.3.6.1.4.1.727.7.2.1.34.8.1.5.1.3 |
tn3270eResPoolRowStatusThis 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.rw RowStatus -- Rsyntax INTEGER { -- active(1), -- notInService(2), -- notReady(3), -- createAndGo(4), -- createAndWait(5), -- destroy(6) -- } .1.3.6.1.4.1.727.7.2.1.34.8.1.5.1.4 |
tn3270eSnaMapTableThis 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. SEQUENCE OF Tn3270eSnaMapEntry .1.3.6.1.4.1.727.7.2.1.34.8.1.6 |
tn3270eSnaMapEntryDefinition 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. Tn3270eSnaMapEntry .1.3.6.1.4.1.727.7.2.1.34.8.1.6.1 |
tn3270eSnaMapSscpSuppliedNameThe 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. SnaResourceName -- Rsyntax OCTET STRING .1.3.6.1.4.1.727.7.2.1.34.8.1.6.1.1 |
tn3270eSnaMapLocalNameThe local name of the secondary LU (SLU).ro SnaResourceName -- Rsyntax OCTET STRING .1.3.6.1.4.1.727.7.2.1.34.8.1.6.1.2 |
tn3270eSnaMapPrimaryLuNameWhen 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.ro SnaResourceName -- Rsyntax OCTET STRING .1.3.6.1.4.1.727.7.2.1.34.8.1.6.1.3 |
tn3270eClientResMapTableThis 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. SEQUENCE OF Tn3270eClientResMapEntry .1.3.6.1.4.1.727.7.2.1.34.8.1.7 |
tn3270eClientResMapEntryDefinition of a single resource pool to client group
mapping. Tn3270eClientResMapEntry .1.3.6.1.4.1.727.7.2.1.34.8.1.7.1 |
tn3270eClientResMapPoolNameThe name of a resource pool. Utf8String .1.3.6.1.4.1.727.7.2.1.34.8.1.7.1.1 |
tn3270eClientResMapClientGroupNameThe name of the client group that is mapped to a
resource pool. Utf8String .1.3.6.1.4.1.727.7.2.1.34.8.1.7.1.2 |
tn3270eClientResMapClientPortA 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. Unsigned32 .1.3.6.1.4.1.727.7.2.1.34.8.1.7.1.3 |
tn3270eClientResMapRowStatusThis 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.rw RowStatus -- Rsyntax INTEGER { -- active(1), -- notInService(2), -- notReady(3), -- createAndGo(4), -- createAndWait(5), -- destroy(6) -- } .1.3.6.1.4.1.727.7.2.1.34.8.1.7.1.4 |
tn3270eResMapTableThis 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. SEQUENCE OF Tn3270eResMapEntry .1.3.6.1.4.1.727.7.2.1.34.8.1.8 |
tn3270eResMapEntryDefinition of the mapping of a Resource Element to
a client address. Tn3270eResMapEntry .1.3.6.1.4.1.727.7.2.1.34.8.1.8.1 |
tn3270eResMapElementNameThe 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. SnaResourceName -- Rsyntax OCTET STRING .1.3.6.1.4.1.727.7.2.1.34.8.1.8.1.1 |
tn3270eResMapAddrTypeIndicates the type of the client address represented
in tn3270eResMapAddress.ro IANATn3270eAddrType -- Rsyntax INTEGER { -- unknown(0), -- ipv4(1), -- ipv6(2) -- } .1.3.6.1.4.1.727.7.2.1.34.8.1.8.1.2 |
tn3270eResMapAddressA client address.ro IANATn3270eAddress -- Rsyntax OCTET STRING .1.3.6.1.4.1.727.7.2.1.34.8.1.8.1.3 |
tn3270eResMapPortA client port.ro Unsigned32 .1.3.6.1.4.1.727.7.2.1.34.8.1.8.1.4 |
tn3270eResMapElementTypeThe type of the associated resource element.ro IANATn3270ResourceType -- Rsyntax INTEGER { -- other(1), -- terminal(2), -- printer(3), -- terminalOrPrinter(4) -- } .1.3.6.1.4.1.727.7.2.1.34.8.1.8.1.5 |
tn3270eResMapSscpSuppliedNameThe 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.ro SnaResourceName -- Rsyntax OCTET STRING .1.3.6.1.4.1.727.7.2.1.34.8.1.8.1.6 |
tn3270eTcpConnTableThis 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. SEQUENCE OF Tn3270eTcpConnEntry .1.3.6.1.4.1.727.7.2.1.34.8.1.9 |
tn3270eTcpConnEntryProvides 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. Tn3270eTcpConnEntry .1.3.6.1.4.1.727.7.2.1.34.8.1.9.1 |
tn3270eTcpConnRemAddrTypeIndicates the type of the value of the
tn3270eTcpConnRemAddress object. For example,
ipv4(1) or ipv6(2). IANATn3270eAddrType -- Rsyntax INTEGER { -- unknown(0), -- ipv4(1), -- ipv6(2) -- } .1.3.6.1.4.1.727.7.2.1.34.8.1.9.1.1 |
tn3270eTcpConnRemAddressThe 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. IANATn3270eAddress -- Rsyntax OCTET STRING .1.3.6.1.4.1.727.7.2.1.34.8.1.9.1.2 |
tn3270eTcpConnRemPortThe 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. Unsigned32 .1.3.6.1.4.1.727.7.2.1.34.8.1.9.1.3 |
tn3270eTcpConnLocalAddrTypeIndicates the type of the value of the
tn3270eTcpConnLocalAddress object. For example,
ipv4(1) or ipv6(2). IANATn3270eAddrType -- Rsyntax INTEGER { -- unknown(0), -- ipv4(1), -- ipv6(2) -- } .1.3.6.1.4.1.727.7.2.1.34.8.1.9.1.4 |
tn3270eTcpConnLocalAddressThe local address associated with a TN3270E client.
tn3270eTcpConnRemAddrType indicates the address type
(IPv4 or IPv6, for example). IANATn3270eAddress -- Rsyntax OCTET STRING .1.3.6.1.4.1.727.7.2.1.34.8.1.9.1.5 |
tn3270eTcpConnLocalPortThe remote port associated with a TN3270E client. Unsigned32 .1.3.6.1.4.1.727.7.2.1.34.8.1.9.1.6 |
tn3270eTcpConnLastActivityThe number of 100ths of seconds since any data was
transferred for the associated TCP Connection.ro TimeTicks (SNMPv2-SMI) .1.3.6.1.4.1.727.7.2.1.34.8.1.9.1.7 |
tn3270eTcpConnBytesInThe 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.ro Counter32 -- Units -- octets .1.3.6.1.4.1.727.7.2.1.34.8.1.9.1.8 |
tn3270eTcpConnBytesOutThe number of bytes sent to TCP for this connection.
A Management Station can detect discontinuities in
this counter by monitoring the
tn3270eTcpConnActivationTime object.ro Counter32 -- Units -- octets .1.3.6.1.4.1.727.7.2.1.34.8.1.9.1.9 |
tn3270eTcpConnResourceElementLU/Print secondary name for connecting an client
into an SNA network.ro SnaResourceName -- Rsyntax OCTET STRING .1.3.6.1.4.1.727.7.2.1.34.8.1.9.1.10 |
tn3270eTcpConnResourceTypeIndicates the type of resource identified by
tn3270eTcpConnResourceElement.ro IANATn3270ResourceType -- Rsyntax INTEGER { -- other(1), -- terminal(2), -- printer(3), -- terminalOrPrinter(4) -- } .1.3.6.1.4.1.727.7.2.1.34.8.1.9.1.11 |
tn3270eTcpConnDeviceTypeIndicates 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.ro IANATn3270DeviceType -- Rsyntax INTEGER { -- ibm3278d2(1), -- ibm3278d2E(2), -- ibm3278d3(3), -- ibm3278d3E(4), -- ibm3278d4(5), -- ibm3278d4E(6), -- ibm3278d5(7), -- ibm3278d5E(8), -- ibmDynamic(9), -- ibm3287d1(10), -- unknown(100) -- } .1.3.6.1.4.1.727.7.2.1.34.8.1.9.1.12 |
tn3270eTcpConnFunctionsThis 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.ro IANATn3270Functions -- Rsyntax OCTET STRING .1.3.6.1.4.1.727.7.2.1.34.8.1.9.1.13 |
tn3270eTcpConnIdThe 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.ro Unsigned32 -- Rsyntax Gauge32 .1.3.6.1.4.1.727.7.2.1.34.8.1.9.1.14 |
tn3270eTcpConnClientIdFormatThe format of a corresponding tn3270eTcpConnClientId
object as defined by the IANSTn3270eClientType textual
convention imported from the IANATn3270eTC-MIB.ro IANATn3270eClientType -- Rsyntax INTEGER { -- none(1), -- other(2), -- ipv4(3), -- ipv6(4), -- domainName(5), -- truncDomainName(6), -- string(7), -- certificate(8), -- userId(9), -- x509dn(10) -- } .1.3.6.1.4.1.727.7.2.1.34.8.1.9.1.15 |
tn3270eTcpConnClientIdAdditional 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.ro OCTET STRING .1.3.6.1.4.1.727.7.2.1.34.8.1.9.1.16 |
tn3270eTcpConnTraceDataTrace data for this session.ro Tn3270eTraceData -- Rsyntax OCTET STRING .1.3.6.1.4.1.727.7.2.1.34.8.1.9.1.17 |
tn3270eTcpConnLogInfoLog information, encoded as specified in the
IANATn3270eLogData textual convention from the
IANAtn3270eTC-MIB.ro IANATn3270eLogData -- Rsyntax OCTET STRING .1.3.6.1.4.1.727.7.2.1.34.8.1.9.1.18 |
tn3270eTcpConnLuLuBindImageWhen 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
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.ro OCTET STRING .1.3.6.1.4.1.727.7.2.1.34.8.1.9.1.19 |
tn3270eTcpConnSnaStateThe 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.ro Enumeration .1.3.6.1.4.1.727.7.2.1.34.8.1.9.1.20 |
tn3270eTcpConnStateLastDiscReasonThe 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.ro Enumeration .1.3.6.1.4.1.727.7.2.1.34.8.1.9.1.21 |
tn3270eTcpConnSrvrConfIndextn3270eSrvrConfIndex of the tn3270eSrvrConfEntry
belonging to the TN3270E server to which this entry
belongs.ro Unsigned32 .1.3.6.1.4.1.727.7.2.1.34.8.1.9.1.22 |
tn3270eTcpConnActivationTimeThe value of the sysUpTime object the last time
this TCP connection became active.ro TimeStamp -- Rsyntax TimeTicks .1.3.6.1.4.1.727.7.2.1.34.8.1.9.1.23 |
tn3270eConfSpinLockAn 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.rw TestAndIncr -- Rsyntax INTEGER .1.3.6.1.4.1.727.7.2.1.34.8.1.10 |
tn3270eConformance OBJECT IDENTIFIER .1.3.6.1.4.1.727.7.2.1.34.8.3 |
tn3270eGroups OBJECT IDENTIFIER .1.3.6.1.4.1.727.7.2.1.34.8.3.1 |
tn3270eBasicGroup OBJECT IDENTIFIER .1.3.6.1.4.1.727.7.2.1.34.8.3.1.1 |
tn3270eSessionGroup OBJECT IDENTIFIER .1.3.6.1.4.1.727.7.2.1.34.8.3.1.2 |
tn3270eResMapGroup OBJECT IDENTIFIER .1.3.6.1.4.1.727.7.2.1.34.8.3.1.3 |
tn3270eHiCapacityGroup OBJECT IDENTIFIER .1.3.6.1.4.1.727.7.2.1.34.8.3.1.4 |
tn3270eCompliances OBJECT IDENTIFIER .1.3.6.1.4.1.727.7.2.1.34.8.3.2 |
tn3270eCompliance OBJECT IDENTIFIER .1.3.6.1.4.1.727.7.2.1.34.8.3.2.1 |