CISCO-TN3270SERVER-MIB: View SNMP OID List / Download MIB

The MIB module for TN3270 Server. MIB description The PU and LU MIB are defined in RFC 1666. This MIB provides additional information on IP and LU mapping. The following entities are managed: 1) TN3270S Global 2) TN3270S Stats on Listen IP/Port basis 3) TN3270S PU 4) TN3270S IP to LU Mapping 5) TN3270S LU to IP Mapping

A list of TN3270 server and DLUR global information.

Parameters values for a group.

Index used to uniquely identify each tn3270 server instance. This index value shall not be reused when the server is shut down and a new instance invoked.

The identity of the board running the server.

The maximum number of LUs supported by the server.

The number of LUs currently in use on the server.

The timestamp when the tn3270 server started.

The default TCP port of this TN3270 Server, which is inherited by the PU if it doesn't have the TCP port explicitly defined in the router configuration for this PU.

The number of seconds of LU inactivity (from either host or client) before the TN3270 session is disconnected. Zero seconds means that LU sessions, by default, will not be disconnected when inactive, regardless of the amount of idle time spent.

The number of seconds of inactivity from client side which the TN3270 Server allows to elapse before sending DO-TIMING-MARK to the TN3270 client. If the client does not reply within thirty minutes of such a TIMING-MARK sending, the server disconnects the tn3270 session. Zero seconds indicates that no keepalives will be sent.

This variable indicates whether or not a tn3270 session will be disconnected upon UNBIND. keep indicates that no automatic disconnect will be made by the server upon receipt of an UNBIND. disconnect indicates that the session will be disconnected upon receipt of an UNBIND. Enumeration: 'disconnect': 2, 'keep': 1.

This variable indicates whether or not leftover LUs will be made available to tn3270 sessions which do not request a specific LU or LU pool. A 'leftover' LU is defined as one for which all of the following conditions hold true: .the SSCP did not send an ACTLU during PU startup; and .the PU controlling the LU is capable of carrying PSID vectors on NMVT messages(thus allowing DDDLU operation for that LU). deny indicates that the leftover LUs should not be given to a generic pool (ie, the PU is not automatically fully populated with 255 LOCADDR definitions); permit indicates leftover LUs should be made available to tn3270 users wanting 'generic' sessions. All LUs in the generic pool are (by definition) Dynamic Definition of Dependant (DDDLU) capable. Enumeration: 'deny': 2, 'permit': 1.

This variable indicates whether to send a timing mark to solicit a response before sending a response to the host. true indicates that a timing mark is sent, false indicates that it is not sent. By using timing mark, an application can determine the response time from the client. Some existing clients do not implement the timing mark correctly and will not work with this server if this parameter is set to true

Total time elapsed since start of tn3270 server.

A list of statistics for each TN3270 Server Listening IP/Port pair.

The entry contains parameters which describe the statistics of the ip stacks.

The ip address of this TN3270 Server Listen endpoint.

The TCP port in this TN3270 Server Listen endpoint.

Number of Tn3270 sessions configured which are available to be used by tn3270 clients.

Spare number of TN3270 sessions available for connect at query time.

Total number of TN3270 session connects-in received.

Total number of TN3270 sessions disconnected.

Total number of attempted sessions which failed to negotiate TN3270/E or were rejected by control point.

Total number of inbound(from client to host) RU chains (identified by end of record (EOR)) processed. Since every inbound RU chain is accompanied by client giving host the direction(CD), it is also a count of number of client transactions.

Total number of Outbound(from host to client) RU Chains (identified by EOR) processed.

Total number of Sampled Inbound Transactions (identified by EOR) on which response time is computed since restart of last listen on ServerAddress/TcpPort. Counters get reset at that point.

Total response time for all sampled inbound transactions for which response time is computed. Response time is the time difference between receiving EOR from the client, and receiving the response from the host. Note that the average response time is given by this object divided by tn3270sStatsSampledHostResponses.

Total number of sampled outbound timing marks on which response time computed.

Total response time for all sampled timing marks on which response time is computed. Response time is the time diference between sending the timeing mark to the client and receiving the response from the client. Note that this is only valid if timeing mark is configured. Note that the average outbound response time is given by this object divided by tn3270sStatsSampledClientResponses.

This table contains objects which describe the PU configuration parameters not defined in the NAU mib, APPN mib or DLUR mib

A list of TN3270 server PU parameters

Index used to uniquely identify each Node instance. This is the same as snaNodeAdminIndex in the NAU MIB.

The ip address of this TN3270 server.

The TCP port of this TN3270 server telnet session.

The number of seconds of LU inactivity (from either host or client) before the TN3270 session is disconnected. Zero seconds means that LU sessions, by default, will not be disconnected when inactive, regardless of the amount of idle time spent. 65535 (not valid in server context) indicates that the idletime value should be taken from the server context.

The number of seconds of inactivity from client side which the TN3270 Server allows to elapse before sending DO-TIMING-MARK to the TN3270 client. If the client does not reply within thirty minutes of such a TIMING-MARK sending, the server disconnect the tn3270 session. Zero seconds indicates that no keepalives will be sent. 65535 (not valid in server context) indicates that the default keepalive value for an LU is taken from whatever value had been defined in the server context for this CIP card.

This variable indicates whether or not a tn3270 session will be disconnected upon UNBIND. keep indicates that no automatic disconnect will be made by the server upon receipt of an UNBIND. disconnect indicates that the session will be disconnected upon receipt of an UNBIND. inherit indicates that the default keepalive value of an LU is taken from whatever value had been defined in the server context for this CIP card. Enumeration: 'disconnect': 2, 'inherit': 3, 'keep': 1.

This variable indicates whether or not leftover LUs will be made available to tn3270 sessions which do not request a specific LU or LU pool. A 'leftover' LU is defined as one for which all of the following conditions hold true: .the SSCP did not send an ACTLU during PU startup; and .the PU controlling the LU is capable of carrying PSID vectors on NMVT messages (thus allowing DDDLU operation for that LU). inherit indicates that the value of tn3270sPuGenericPool is to be the same as tn3270sGlobalGenericPool. deny indicates that the leftover LUs should not be given to a generic pool (ie, the PU is not automatically fully populated with 255 LOCADDR definitions); permit indicates leftover LUs should be made available to tn3270 users wanting 'generic' sessions. All LUs in the generic pool are (by definition) DDDLU capable. Enumeration: 'deny': 2, 'inherit': 3, 'permit': 1.

The value identifies the current PU state. This has a different meaning for direct or DLUR PU before the link station is established. For DLUR PU, the PU is in reset state, for direct PU, this will be either sending a TEST or XID shut (1) - The PU is configured but in shut state reset (2) - The link station of this PU is not active. inactive (3) - The PU is not activated and the link-station or DLUR state is unknown. test (4) - PU is sending a TEST to establish link. xid (5) - TEST is responded, XID is sent. pActpu (6) - The link station is up but no ACTPU is received. active (7) - ACTPU is received and acknowledged positively. actBusy (8) - Awaiting host to acknowledge the SSCP-PU data. Enumeration: 'reset': 2, 'shut': 1, 'xid': 5, 'pActp': 6, 'active': 7, 'inactive': 3, 'test': 4, 'actBusy': 8.

This defines whether the connection to the host is via DLUR or direct link. If DLUR, LuSeed, lmac/sap, and rmac/sap in this table are undefined. Enumeration: 'dlur': 1, 'direct': 2.

For Direct PU this defines the LU name prefix (LU seed) which is concatinated with the locaddr to form a unique name.

SAP address of the local direct node.

SAP address of the remote node; valid for direct PU only.

MAC address of the remote node; valid for direct PU only.

The value of the PRECEDENCE field in the Type of Service octet in the IP header set by the TN3270 server for outbound IP packets destined to the TN3270 client screen. That is from the router to the TN3270 client screen.

The value of the PRECEDENCE field in the Type of Service octet in the IP header set by the TN3270 server for outbound IP packets destined to the TN3270 client printer. That is from the router to the TN3270 client printer.

The value of the TOS field in the Type of Service octet in the IP header set by the TN3270 server for outbound IP packets destined to the TN3270 client screen. That is from the router to the TN3270 client screen.

The value of the TOS field in the Type of Service octet in the IP header set by the TN3270 server for outbound IP packets destined to the TN3270 client printer. That is from the router to the TN3270 client printer.

A list of IP to LU mapping entries

A list of entries to relate a client IP address to the LU

The ip address of the TN3270 client.

The TCP port of the TN3270 client.

The PU index associated with NAU and PU objects

The LU index associated with NAU and LU objects.

This helps map LU to client ip/port. Also it provides other useful parameters not available elsewhere.

Parameters values for a group.

Index used to uniquely identify each PU instance. This is the same as snaNodeAdminIndex in the NAU MIB.

Index used to uniquely identify the LU instance within a PU. It is the locaddr. This is the same as snaLuAdminLuIndex in the NAU MIB.

The ip address of the TN3270 client connected to this LU.

The TCP port of the TN3270 client connected to this LU.

This indicates whether the negotiated TN3270 session. TN3270, TN3270E or never connected. Enumeration: 'tn3270e': 2, 'neverConnect': 3, 'tn3270': 1.

Terminal type or model number of the incoming TN3270 client.

The value identifies the current LU state. inactive (1) - LU didn't receive ACTLU. active (2) - LU received ACTLU and acknowledged positively. pSdt (3) - LU is bound but there is no SDT yet. act/session (4) - LU is bound and in session. pActlu (5) - telnet connects in and is awating for ACTLU. pNotifyAv (6) - awaiting host notify-available response. pNotifyUa (7) - awaiting host notify-unavailable response. pReset (8) - awaiting for a buffer to send DACTLU response. pPsid (9) - awaiting for NMVT Reply psid response. pBind (10) - awaiting for host to send bind. pUnbind (11) - awaiting host unbind response. unbindWt (12) - awaiting for client to acknowledge disconnection. sdtWt (13) - awaiting for client to acknowledge SDT Enumeration: 'pUnbind': 11, 'pNotifyAv': 6, 'pNotifyUa': 7, 'sdtWt': 13, 'unbindWt': 12, 'pPsid': 9, 'actSession': 4, 'inactive': 1, 'pReset': 8, 'pSdt': 3, 'active': 2, 'pBind': 10, 'pActl': 5.

The number of inbound frames allowed to be sent to the host without receiving a pacing response from the host.

After inbound pacing credit is exhausted, the inbound data is queued. This is the number of inbound frames queued waiting for host pacing response.

The number of TCP packets in the server queued for transmission to the client

Time since last activity was recorded on this LU.

This indicates whether LU is dynamic or static. dynamic (1) - LU is configured as DDDLU. static (2) - LU is configured as specific. Host will send ACTLU as soon as PU is active. Enumeration: 'static': 2, 'dynamic': 1.

This is the link index into APPN mib for link on which bind flowed; only valid for DLUR LU.

This is the session identifier on a PU 2.1 link.

Time at which the last data was logged for this LU.

An array of octets indicating the latest events which happened in this LU. Octet 1 is the most recent event, octet 2 the next most recent and so on. Although the maximum number of events kept is 16, the actual number of events kept may be lower than that. When more events are generated than are kept, the oldest ones are discarded. Events are encoded as: 1 inactivity timer expired. 2 dynamic timer expired, 3 actlu from host 4 bind from host 5 clear from host 6 dactlu from host 7 hierarchical reset from PU (warn actpu) 8 sdt from host 9 unbind from host 10 notify response from host 11 Reply psid negative response from host 12 Reply psid pos response from host 13 unbind response from host 14 hierarchical reset from pu 15 connect from client 16 disconnect from client 17 timing-mark response from client 18 flow control timer expired 19 negative response to host 20 negative response from host 21 data contention happened 22 no buffer to send response 23 receive a sna response while inbound

This variable indicates whether this LU has been configured (Nailed) for a specific TN3270 client. TRUE -> LU is nailed to the client IP address FALSE -> LU is not nailed to the client IP address

A list of reserved LUs and their associated IP addresses is represented here for the containing PU. Each LU is configured for a specific client IP address. This association between the LU and the client IP Address is called nailing. The client is said to be nailed to its LU and visa-versa. If the client IP address is known but the PU index is not known, a more efficient way to access this info is via tn3270sIpNailTable.

A list of entries to relate a PU to nailed clients.This table contains the same info as tn3270sIpNailTable. The indices are ordered to facilitate access to the information when the PU index is known but not the client IP address. This is necessitated due to the potentially large number of rows in the table.

The IP address of the nailed TN3270 client.

The subnet mask of the nailed TN3270 client.

The nailing type configured for the range of LUs within this PU is either screen or printer. screen - The range of LUs will only be connected to TN3270 clients with a device type which is not 328*. If an LU is statically configured at the host, then it should be configured with a screen DLOGMOD definition. printer - The range of LUs will only be connected to TN3270 clients with device type which is 328*. If an LU is statically configured at the host, then it should be configured with a printer DLOGMOD definition. Enumeration: 'screen': 1, 'printer': 2.

The first LU in this range nailed to this client ip address.

The last LU in this range nailed to this client ip address.

A list of reserved LUs and their associated IP addresses is represented here for the containing PU. Each LU is configured for a specific client IP address. This association between the LU and the client IP Address is called nailing. The client is said to be nailed to its LU and visa-versa. If the PU index is known but the client IP address is not known, a more efficient way to access this info is via tn3270sPuNailTable.

A list of entries to relate a PU to nailed clients. This table contains the same info as tn3270sPuNailTable. The indices are ordered to facilitate access to the info when the client IP address is known but not the PU index. This is necessitated due to the potentially large number of rows in the table.

The IP address of the nailed TN3270 client.

The subnet mask of the nailed TN3270 client.

The nailing type configured for the range of LUs within this PU is either screen or printer. screen - The range of LUs will only be connected to TN3270 clients with a device type which is not 328*. If an LU is statically configured at the host, then it should be configured with a screen DLOGMOD definition. printer - The range of LUs will only be connected to TN3270 clients with device type which is 328*. If an LU is statically configured at the host, then it should be configured with a printer DLOGMOD definition. Enumeration: 'screen': 1, 'printer': 2.

The first LU in this range nailed to this client ip address.

The last LU in this range nailed to this client ip address.

The compliance statement for entities which implement the Cisco Tn3270s MIB

The compliance statement for obsolete entities.

The compliance statement for the TN3270 Server.

A collection of objects providing Tn3270 ability to a Cisco agent.

A collection of objects providing Tn3270 ability to a Cisco agent.

A collection of objects providing LU nailing and IP precedence features.