tn3270sLuEvents - tn3270s Lu Events - CISCO-TN3270SERVER-MIB

MIBs list

With IPHost Network Monitor you can run simple snmp requests against a Cisco device in your network.

tn3270sLuEvents

tn3270s Lu Events
1.3.6.1.4.1.9.9.54.1.5.1.1.16

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 ::= { tn3270sLuEntry 16 } SYNTAX TruthValue MAX-ACCESS read-only STATUS current DESCRIPTION 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 ::= { tn3270sLuEntry 17 } -- ************************************************************* -- * * -- * TN3270 Server - LU Nail Mapping * -- * * -- ************************************************************* SYNTAX SEQUENCE OF Tn3270sPuNailEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION 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. ::= { tn3270sPuNail 1 } SYNTAX Tn3270sPuNailEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION 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. INDEX { tn3270sIndex, tn3270sPuIndex, tn3270sPuNailClientIpAddr, tn3270sPuNailLuFirst } ::= { tn3270sPuNailTable 1 } Tn3270sPuNailEntry ::= SEQUENCE { tn3270sPuNailClientIpAddr IpAddress, tn3270sPuNailClientIpMask IpAddress, tn3270sPuNailType INTEGER, tn3270sPuNailLuFirst INTEGER, tn3270sPuNailLuLast INTEGER } SYNTAX IpAddress MAX-ACCESS read-only STATUS current DESCRIPTION The IP address of the nailed TN3270 client.

Back to CISCO-TN3270SERVER-MIB MIB page.

IPHost Network monitor allows you to monitor tn3270sLuEvents on Cisco device via the SNMP protocol. Download IPHost Network Monitor (500 monitors for 30 days, 50 monitors free forever) to start monitoring Cisco firewalls right now.

Easy monitoring of tn3270sLuEvents with IPHost tools

MIBs list