IBM-TN3270E-MIB
Standard SNMP MIB module defining data structures for IBM-TN3270E-MIB.
Imported Objects
Objects
9 total| Object Name |
|---|
ibmtn3270eMIB OBJECT IDENTIFIER .1.3.6.1.4.1.1.3.6.1.4.1.2.2.1.3.6.1.4.1.2.6.6.1.3.6.1.4.1.2.6.119.119.1.3.6.1.4.1.2.6.119.4.4.1.3.6.1.4.1.2.6.119.4.18.18.1 |
SNMPv2-SMI-v1 Unknown .1.3.6.1.4.1.1.3.6.1.4.1.2.2.1.3.6.1.4.1.2.6.6.1.3.6.1.4.1.2.6.119.119.1.3.6.1.4.1.2.6.119.4.4.1.3.6.1.4.1.2.6.119.4.18.18.1 |
ibmtn3270eConnRejectTableA table of information about TN3270E connection rejections.
This table does not contain information for connections that
were successfully established, but terminated abnormally. SEQUENCE OF Ibmtn3270eConnRejectEntry .1.3.6.1.4.1.1.3.6.1.4.1.2.2.1.3.6.1.4.1.2.6.6.1.3.6.1.4.1.2.6.119.119.1.3.6.1.4.1.2.6.119.4.4.1.3.6.1.4.1.2.6.119.4.18.18.1.1 |
ibmtn3270eConnRejectEntryInformation indicating why a particular client connection
was rejected. Ibmtn3270eConnRejectEntry .1.3.6.1.4.1.1.3.6.1.4.1.2.2.1.3.6.1.4.1.2.6.6.1.3.6.1.4.1.2.6.119.119.1.3.6.1.4.1.2.6.119.4.4.1.3.6.1.4.1.2.6.119.4.18.18.1.1.1 |
ibmtn3270eConnRejectIndexA unique identifier of a row in the connection rejection table. INTEGER .1.3.6.1.4.1.1.3.6.1.4.1.2.2.1.3.6.1.4.1.2.6.6.1.3.6.1.4.1.2.6.119.119.1.3.6.1.4.1.2.6.119.4.4.1.3.6.1.4.1.2.6.119.4.18.18.1.1.1.1 |
ibmtn3270eConnRejectAddrTypeA indication of the type of client address provided in
ibmtn3270eConnRejectClient.ro Enumeration .1.3.6.1.4.1.1.3.6.1.4.1.2.2.1.3.6.1.4.1.2.6.6.1.3.6.1.4.1.2.6.119.119.1.3.6.1.4.1.2.6.119.4.4.1.3.6.1.4.1.2.6.119.4.18.18.1.1.1.2 |
ibmtn3270eConnRejectClientThe IP address of the client whose connection was rejected.ro OCTET STRING .1.3.6.1.4.1.1.3.6.1.4.1.2.2.1.3.6.1.4.1.2.6.6.1.3.6.1.4.1.2.6.119.119.1.3.6.1.4.1.2.6.119.4.4.1.3.6.1.4.1.2.6.119.4.18.18.1.1.1.3 |
ibmtn3270eConnRejectReasonThe reason the connection was rejected. Some of the values sound
similar, but represent different failure points within the TN3270E
server software. Also, some values are very specific to the TN3270E
server software internals, so they may seem a bit cryptic to the user.
noportinfo (1) // GetPortInfo failed to retrieve Port information
cliunknown (2) // HostName filter failure - client_hostname unknown
clinoauth (3) // Client is not authorized by FilterUser
sockblock (4) // Could not make socket nonblocking
nodeterm (5) // Node is terminating
createfail (6) // TN3270Create failed to create session environment
seqnum (7) // 0xFF seq number not doubled
negfailed (8) // Negotiation failed
notelquale (9) // Not TELQUALE_REQUEST
termtypefail (10) // Verification of terminal type failed
notypeprtgen (11) // TELQUALE_ASSOCIATE req but not TYPE_PRINTER_GENERIC
clirplyfail (12) // Sending reply to client failed.
valtelquale (13) // Validation of TELQUALE_REQUEST failed
clisendfail (14) // Send to client failed
failtelquale (15) // Verification of TELQUAL_IS failed
termtypagain (16) // Received invalid terminal type for 2nd time
noportagain (17) // GetPortInfo failed to retrieve Port information
prtnoluname (18) // Associated printer req. with no LU name specified
clinoauthent (19) // Client is not authorized by Filter entries
clinoauthflt (20) // Client not authorized by Filter entries after retry
noluconf (21) // REJECT_UNSUPP_REQ: No LUs configured.
noportmore (22) // GetPortInfo failed to retrieve Port information
noresource (23) // No resource spe+cified on Port & no name requested
nameresource (24) // Resource specified on Port doesn't match name requested
prtnoluagain (25) // Associated printer req. with no LU name specified
noimplu (26) // No implicit LUs are available
lunotfound (27) // Specified LU not found/available
valluprt (28) // Validation of LU type failed for assoc. printer
vallu (29) // Validation of LU type failed
prtlunofind (30) // LU for associated printer not found
nameinuse (31) // LU name requested currently in use
reqlunofind (32) // LU requested not found
valprtagain (33) // Validation of LU type failed for assoc. printer
valluagain (34) // Validation of LU type failed
luprtnofind (35) // LU for associated printer not found
poolluinuse (36) // Requested pooled LU is already in use
poollunofind (37) // Requested pooled LU is not found for assoc. printer
restypnofind (38) // Requested type of resource is not found
poolluconf (39) // Requested pooled LU is not found in config. list
lucapreach (40) // LU capping value reached for this client address
noappnmem (41) // APPN memory above the constrained threashold
nomoreconn (42) // Max. number of TN3270 connection reached
pooldep (43) // The pool from which the resource was requested has been depleted
termnorsp (44) // The session was terminated before receiving a response from APPNro Enumeration .1.3.6.1.4.1.1.3.6.1.4.1.2.2.1.3.6.1.4.1.2.6.6.1.3.6.1.4.1.2.6.119.119.1.3.6.1.4.1.2.6.119.4.4.1.3.6.1.4.1.2.6.119.4.18.18.1.1.1.4 |
ibmtn3270eConnRejectTimeA string providing the date and time the connection was rejected.ro DisplayString -- Rsyntax OCTET STRING .1.3.6.1.4.1.1.3.6.1.4.1.2.2.1.3.6.1.4.1.2.6.6.1.3.6.1.4.1.2.6.119.119.1.3.6.1.4.1.2.6.119.4.4.1.3.6.1.4.1.2.6.119.4.18.18.1.1.1.5 |
More MIBs from Proteon
Browse all ProteonMIBs →SNMP MIB module
The LANCOM-1711-PLUS-MIB provides the management information base definitions required for SNMP-based monitoring and configuration of the LANCOM 1711 PLUS router, enabling the retrieval of device-specific operational metrics such as interface statistics, system health indicators, and routing table states.
The LANCOM-1722-MIB module enables SNMP-based monitoring and management of the LANCOM 1722 VoIP gateway, specifically exposing Annex B-defined metrics for voice session states, call quality parameters, and telephony interface statistics.
The LANCOM-1721-MIB module provides SNMP management capabilities for the LANCOM 1721 VPN router, specifically exposing metrics defined in Annex B to monitor VPN tunnel states, security associations, and interface statistics. This module enables network administrators to track connection status, throughput counters, and error conditions for the device's integrated VPN functionality.
The LANCOM-1711-MIB module enables monitoring and management of VPN tunnel states, cryptographic session statistics, and interface parameters specifically for LANCOM 1711+ series routers. It provides access to counters for IPsec and PPTP tunnel establishment failures, throughput metrics, and device health indicators required for maintaining secure WAN connectivity on this hardware platform.
The LCOS-SX-MIB module provides SNMP management definitions for Brocade (now Broadcom) LCOS SX switches, enabling the monitoring of Layer 2 Ethernet switch metrics including port status, traffic counters, error statistics, and spanning tree states.