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.
Parsed from file TN3270E-MIB.mib
Module: TN3270E-MIB
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.
tn3270eSrvrConfSrvrType OBJECT-TYPE
SYNTAX INTEGER {
host(1),
gateway(2)
}
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"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."
View at oid-info.com
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.
Parsed from file rfc2561-TN3270E.mib.txt
Company: None
Module: TN3270E-MIB
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.
tn3270eSrvrConfSrvrType OBJECT-TYPE SYNTAX INTEGER { host(1), gateway(2) } MAX-ACCESS read-only STATUS current DESCRIPTION "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." ::= { tn3270eSrvrConfEntry 10 }
tn3270eSrvrConfSrvrType OBJECT-TYPE SYNTAX INTEGER { host(1), gateway(2) } ACCESS read-only STATUS mandatory DESCRIPTION "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." ::= { tn3270eSrvrConfEntry 10 }
Automatically extracted from Cisco "SNMP v2 MIBs".
tn3270eSrvrConfSrvrType OBJECT-TYPE SYNTAX INTEGER { host(1), gateway(2) } MAX-ACCESS read-only STATUS current DESCRIPTION "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." ::= { tn3270eSrvrConfEntry 10 }
tn3270eSrvrConfSrvrType OBJECT-TYPE SYNTAX INTEGER { host(1), gateway(2) } MAX-ACCESS read-only STATUS current DESCRIPTION "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." ::= { tn3270eSrvrConfEntry 10 }
Internet Assigned Numbers Authority
OID | Name | Sub children | Sub Nodes Total | Description |
---|---|---|---|---|
1.3.6.1.2.1.34.8.1.1.1.1 | tn3270eSrvrConfIndex | 0 | 0 | Identifier for a single TN3270E server. tn3270eSrvrConfIndex values need not be contiguous. |
1.3.6.1.2.1.34.8.1.1.1.2 | tn3270eSrvrConfInactivityTimeout | 0 | 0 | The inactivity time-out specified in seconds. When a connection has been inactive for the number of seconds specified by this ob… |
1.3.6.1.2.1.34.8.1.1.1.3 | tn3270eSrvrConfConnectivityChk, tn3270eSrvrConfActivityCheck | 0 | 0 | This object enables TIMING-MARK processing, NOP processing, or neither for a TN3270E server. |
1.3.6.1.2.1.34.8.1.1.1.4 | tn3270eSrvrConfTmNopInactTime, tn3270eSrvrConfActivityTimeout | 0 | 0 | The TIMEMARK or NOP processing time-out specified in seconds. Note that a value of 0 is not allowed for this object since the fun… |
1.3.6.1.2.1.34.8.1.1.1.5 | tn3270eSrvrConfTmNopInterval, tn3270eSrvrConfActivityInterval | 0 | 0 | The scan interval to be used by a TN3270E server. TIMEMARK or NOP processing scans the Telnet sessions on the interval provided b… |
1.3.6.1.2.1.34.8.1.1.1.6 | tn3270eSrvrFunctionsSupported | 0 | 0 | This object indicates the functions supported by a TN3270E server. |
1.3.6.1.2.1.34.8.1.1.1.7 | tn3270eSrvrConfAdminStatus | 0 | 0 | The desired state of the TN3270E server represented by this entry in the table: up(1) - Activate this TN3270E server. d… |
1.3.6.1.2.1.34.8.1.1.1.8 | tn3270eSrvrConfOperStatus | 0 | 0 | The current operational state of a TN3270E server. The following values are defined: up(1) - the server is active and … |
1.3.6.1.2.1.34.8.1.1.1.9 | tn3270eSrvrConfSessionTermState | 0 | 0 | This object determines what a TN3270E server should do when a TN3270 Session terminates: terminate(1) => Terminate the TCP co… |
1.3.6.1.2.1.34.8.1.1.1.11 | tn3270eSrvrConfContact | 0 | 0 | This object provides a scratch pad for a TN3270E server administrator for storing information for later retrieval. |
1.3.6.1.2.1.34.8.1.1.1.12 | tn3270eSrvrConfRowStatus | 0 | 0 | This object allows entries to be created and deleted in the tn3270eSrvrConfTable. Entries may also be created and deleted as a r… |
1.3.6.1.2.1.34.8.1.1.1.13 | tn3270eSrvrConfLastActTime | 0 | 0 | tn3270eSrvrConfLastActTime OBJECT-TYPE SYNTAX DateAndTime MAX-ACCESS read-only STATUS current DESCRIPTION "This object reports … |
1.3.6.1.2.1.34.8.1.1.1.14 | tn3270eSrvrConfTmTimeout | 0 | 0 | The TIMING-MARK time-out, specified in seconds. |