The TN3270E TCP table describes the MIB module for objects used to manage the TN3270E server. This table has an entry for each TN3270(E) client connection that is active at the TN3270E server. The table was originally modeled after the TCPConnTable and was modified to support different client address types. It is indexed first by the remote address and port as opposed to local address and port, thus enabling use of a SNMP GET-NEXT operation while using only the remote address and port.
|
|
The fields on the TN3270E TCP table are:
Remote Address |
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 should be the remote client's address, not the proxy client's address. |
Remote Port |
The remote port associated with a TN3270E client. If a TN3270 (E) client is connected to its server via a proxy client the port represented by the value of this object should be the remote client's port, not the proxy client's port. |
Local Address |
The local address associated with a TN3270E client. TN3270ETcpConnRemAddrType indicates the address type (IPv4 or IPv6 for example). |
Local Port |
The local port associated with a TN3270E client. |
Bytes In |
The number of bytes received by the server from TCP for this connection. |
Bytes Out |
The number of bytes sent to TCP for this connection. |
SLUName |
LU/Printer secondary name for connecting a client into an SNA network. |
Logmode |
Indicates the device type if negotiated with client. This object is also known as Logmode. May be one of the following: 0 : Unknown 1 : IBM3278D2 2 : IBM3278D2E 3 : IBM3278D3 4 : IBM3278D3E 5 : IBM3278D4 6 : IBM3278D4E 7 : IBM3278D5 8 : IBM3278D5E 9 : IBMDynamic 10: IBM3287D1 |
SNA State |
The current state of the SNA side of the end-to-end TN3270 connection. The following states are defined: 0 : Unknown – the true state is not known. 1 : No SLU Session – the SLU has neither an SSCP-LU nor an LU-LU session active. 2 : SSCP LU Session – the SSCP-LU session for the SLU is active, but the SLU is not currently in session with a PLU. 3 : LU LU Session – the SLU currently has an active session with a PLU. |
See also: