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.
Parsed from file TN3270E-MIB.mib
Module: TN3270E-MIB
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.
tn3270eSrvrConfSessionTermState OBJECT-TYPE
SYNTAX INTEGER {
terminate(1),
luSessionPend(2),
queueSession(3)
}
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"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 clients
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."
DEFVAL { terminate }
View at oid-info.com
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.
Parsed from file rfc2561-TN3270E.mib.txt
Company: None
Module: TN3270E-MIB
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.
tn3270eSrvrConfSessionTermState OBJECT-TYPE SYNTAX INTEGER { terminate(1), luSessionPend(2), queueSession(3) } MAX-ACCESS read-create STATUS current DESCRIPTION "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." DEFVAL { terminate } ::= { tn3270eSrvrConfEntry 9 }
tn3270eSrvrConfSessionTermState OBJECT-TYPE SYNTAX INTEGER { terminate(1), luSessionPend(2), queueSession(3) } ACCESS read-write STATUS mandatory DESCRIPTION "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." DEFVAL { terminate } ::= { tn3270eSrvrConfEntry 9 }
Automatically extracted from Cisco "SNMP v2 MIBs".
tn3270eSrvrConfSessionTermState OBJECT-TYPE SYNTAX INTEGER { terminate(1), luSessionPend(2), queueSession(3) } MAX-ACCESS read-create STATUS current DESCRIPTION "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." DEFVAL { terminate } ::= { tn3270eSrvrConfEntry 9 }
tn3270eSrvrConfSessionTermState OBJECT-TYPE SYNTAX INTEGER { terminate(1), luSessionPend(2), queueSession(3) } MAX-ACCESS read-create STATUS current DESCRIPTION "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." DEFVAL { terminate } ::= { tn3270eSrvrConfEntry 9 }
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.10 | tn3270eSrvrConfSrvrType | 0 | 0 | This object indicates the type of TN3270E server. The existence of MIB tables and objects that will be defined by follow-on MIBs … |
| 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. |