Received: from cnri by ietf.org id aa03841; 2 Jun 97 8:39 EDT Received: from list.nih.gov by CNRI.Reston.VA.US id aa04955; 2 Jun 97 8:39 EDT Received: from list.nih.gov (terrific.net.nih.gov [165.112.130.6]) by list.nih.gov (8.8.5/8.8.5) with ESMTP id IAA26325; Mon, 2 Jun 1997 08:32:00 -0400 (EDT) Received: from LIST.NIH.GOV by LIST.NIH.GOV (LISTSERV-TCP/IP release 1.8c) with spool id 2728699 for TN3270E@LIST.NIH.GOV; Mon, 2 Jun 1997 08:31:55 -0400 Received: from gw.nist.gov (firewall-user@gw.nist.gov [129.6.92.30]) by list.nih.gov (8.8.5/8.8.5) with SMTP id IAA26058 for ; Mon, 2 Jun 1997 08:21:53 -0400 (EDT) Received: by gw.nist.gov; id IAA20826; Mon, 2 Jun 1997 08:23:51 -0400 Received: from trex.nist.gov(129.6.17.17) by gw.nist.gov via smap (3.2) id xma020822; Mon, 2 Jun 97 08:23:47 -0400 Received: from localhost (localhost [127.0.0.1]) by trex.nist.gov (AIX4.2/UCB 8.7/8.7) with SMTP id IAA28324; Mon, 2 Jun 1997 08:21:47 -0400 (EDT) From: dangona@nist.gov Date: Mon, 2 Jun 1997 08:21:47 -0400 (EDT) To: kennethw@vnet.ibm.com cc: tn3270e@list.nih.gov Subject: Re: In-Reply-To: <199705310113.VAA11418@list.nih.gov> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-tn3270e@list.nih.gov I believe there is a real need for this kind of effort. I think every new application should include some kind of application-level performance information. I realize it can be difficult agreeing on the 'how to' portion of an RFC - this process has been going on for years, but once done, a real product is likely the result. That real product requires support. Having to support real users in the real world typically means having to address performance issues/bugs. Sorting out the causes can be difficult, especially in increasingly complex networks. Having access to this kind of information would be of immense help to the companies' sysadmins you sell your product to. It would also help your own support staff. Monitoring can create a lot of overhead, so it would be nice if the monitoring can be turned off and on as needed. -- All opinions are my own, not those of my employer -- Steve D'Angona dangona@nist.gov On Fri, 30 May 1997 kennethw@VNET.IBM.COM wrote: > Date: Fri, 30 May 97 20:58:38 EDT > From: kennethw@VNET.IBM.COM > To: tn3270e@list.nih.gov > Subject: > > I work with Ed Bailey and have been involved with configuration of > a TN3270 and TN3270E Server for a number of years, was a Performance > Monitor Application developer and have been involved in several of > the Network Management Area working groups. I have submitted the > attached internet draft to address a need for TN3270 Configuring, > monitoring and correlation of a TN3270 or TN3270E session with its > corresponding TCP Connection. > > The monitoring portion is fairly basic, essentially the TCP Round-trip > ACK, and will certainly need to be enhanced to provide more vigorous > support. Please take a look at the draft and provide feedback. The text > portion is somewhat brief since I expect that substantial changes will > have to be made as the result of discussion. > > Ken > --------------------------------------------------------------------- > > > > > > > TN3270E Working Group > INTERNET DRAFT: Expiration Date: November, 1997 > IBM Corp. > > May 1997 > > Definitions of Managed Objects for > TN3270 Using SMIv2 > > > > > Status of this Memo > > This document is an Internet Draft. Internet Drafts are working > documents of the Internet Engineering Task Force (IETF), its Areas, > and its Working Groups. Note that other groups may also distribute > working documents as Internet Drafts. > > Internet Drafts are draft documents valid for a maximum of six > months. Internet Drafts may be updated, replaced, or obsoleted by > other documents at any time. It is not appropriate to use Internet > Drafts as reference material or to cite them other than as a "working > draft" or "work in progress." > > Please check the I-D abstract listing contained in each Internet > Draft directory to learn the current status of this or any Internet > Draft. Distribution of this document is unlimited. > > Abstract > > The purpose of this memo is to define the Management Information Base > (MIB) for configuring and monitoring TN3270 and TN3270E sessions. > The monitoring portion of the MIB is limited to AUGMENTation of > the TCP Connection Table (RFC 2012) with a set of objects collected > from the TCP Layer. It is the intent of this MIB to > fully adhere to all prerequisite MIBs unless explicitly stated. > Deviations will be documented in corresponding conformance statements. > The specification of this MIB will utilize the > Structure of Management Information (SMI) for Version 2 of the > Simple Network Management Protocol Version (refer to RFC1902, > reference [1]). > > > > Table of Contents > > > > > Expires November 1997 [Page 1]~ > > > > > > White TN3270 Management Information Base (TN3270-MIB) 30 May 1997 > > > 1.0 Introduction............................................. 2 > 2.0 The SNMPv2 Network Management Framework.................. 2 > 2.1 Object Definitions....................................... 3 > 3.0 Structure of the MIB..................................... 3 > 3.1 Base TN3270 MIB Definitions.............................. 3 > 3.2 MIB Definitions for AUGMENTing the TCP Connection Table.. 3 > 4.0 Definitions.............................................. 4 > 5.0 Security Considerations.................................. 30 > 6.0 Acknowledgments.......................................... 31 > 7.0 References............................................... 31 > 8.0 Authors' Addresses....................................... 33 > > > 1. Introduction > > This document is a product of the TN3270E Working Group. Its purpose > is to define a MIB module for extending the traditional MIBs supported > by a TCP/IP implementation for configuring and monitoring of TN3270 > and TN3270E sessions. > > > 2. The SNMPv2 Network Management Framework > > The SNMP Network Management Framework presently consists of three > major components. They are: > > o the SMI, described in RFC 1902 [1], - the mechanisms used for > describing and naming objects for the purpose of management. > > o the MIB-II, STD 17, RFC 1213 [5], - the core set of managed > objects for the Internet suite of protocols. > > o the protocol, RFC 1157 [9] and/or RFC 1905 [7] - the protocol > for accessing managed information. > > Textual conventions are defined in RFC 1903 [6], and conformance > statements are defined in RFC 1904 [8]. > > The Framework permits new objects to be defined for the purpose of > experimentation and evaluation. > > This memo specifies a MIB module that is compliant to the SNMPv2 SMI. > A semantically identical MIB conforming to the SNMPv1 SMI can be > produced through the appropriate translation. > > > > > > > > Expires November 1997 [Page 2]~ > > > > > > White TN3270 Management Information Base (TN3270-MIB) 30 May 1997 > > > 2.1. Object Definitions > > Managed objects are accessed via a virtual information store, termed > the Management Information Base or MIB. Objects in the MIB are > defined using the subset of Abstract Syntax Notation One (ASN.1) > defined in the SMI. In particular, each object object type is named > by an OBJECT IDENTIFIER, an administratively assigned name. The > object type together with an object instance serves to uniquely > identify a specific instantiation of the object. For human > convenience, we often use a textual string, termed the descriptor, to > refer to the object type. > > > > 3. Structure of the MIB > > The TN3270-MIB is split into the following components: > > o Base TN3270 MIB Definitions > o MIB Definitions for AUGMENTing the TCP Connection Table > > > > 3.1. Base TN3270 MIB Definitions > > The collection of MIB Objects defined by the tn3270BasicGroup. This > group of objects provides for TN3270 and TN3270E configuration. > > > 3.2. MIB Definitions for AUGMENTing the TCP Connection Table > > The TCP Connection Table is defined by RFC 2012 (Refer to reference > 10, TCP-MIB Definitions). Traditionally, the contents of the TCP > Connection Table has been implementation dependent. Its formal > definition consists of the following objects: > > o tcpConnState (INTEGER) > o tcpConnLocalAddress (IpAddress) > o tcpConnLocalPort (INTEGER) > o tcpConnRemAddress (IpAddress) > o tcpConnRemPort (INTEGER) > > and is indexed by: tcpConnLocalAddress, tcpConnLocalPort, > tcpConnRemAddress and tcpConnRemPort. The tn3270TcpConnTableGroup > contains the objects defined by the tn3270TcpConnTable for AUGMENTing > the tcpConnTable. The objects contained within the > tn3270TcpConnTableGroup can be set by either a TN3270 or TN3270E > Server or if TCP specific by the TCP Stack. > > > > Expires November 1997 [Page 3]~ > > > > > > White TN3270 Management Information Base (TN3270-MIB) 30 May 1997 > > > 4. Definitions > > TN3270-MIB DEFINITIONS ::= BEGIN > > IMPORTS > MODULE-IDENTITY, OBJECT-TYPE, > experimental, Integer32, IpAddress, TimeTicks > FROM SNMPv2-SMI > TEXTUAL-CONVENTION, RowStatus, TruthValue, > DisplayString > FROM SNMPv2-TC > MODULE-COMPLIANCE, OBJECT-GROUP > FROM SNMPv2-CONF > InterfaceIndex, InterfaceIndexOrZero > FROM IF-MIB > tcpConnEntry > FROM TCP-MIB > ; > > tn3270MIB MODULE-IDENTITY > LAST-UPDATED "9705300000Z" -- May 30, 1997 > ORGANIZATION "TN3270E Working Group" > CONTACT-INFO > "Kenneth White (kennethw@vnet.ibm.com) > IBM Corp." > DESCRIPTION > "This module defines a portion of the management > information base (MIB) for configuring and monitoring > TN3270 and TN3270E sessions." > -- Need an experimental OID from IANA > ::= { experimental 2001 } > > -- Textual Conventions > > VariableName ::= TEXTUAL-CONVENTION > STATUS current > DESCRIPTION > "A up to 8 octet string name, were a percent sign, '%', > can be used to represent one arbitrary character or an > asterisk , '*', to represent an arbitrary string of > characters. If an asterisk is specified it must appear > as the last character in the octet string." > SYNTAX DisplayString (SIZE(1..8)) > > > -- Top-level structure of the MIB > > tn3270Objects OBJECT IDENTIFIER ::= { tn3270MIB 1 } > > > > Expires November 1997 [Page 4]~ > > > > > > White TN3270 Management Information Base (TN3270-MIB) 30 May 1997 > > > tn3270Notifications OBJECT IDENTIFIER ::= { tn3270MIB 2 } > tn3270Conformance OBJECT IDENTIFIER ::= { tn3270MIB 3 } > > -- MIB Objects > > tn3270Control OBJECT IDENTIFIER ::= { tn3270Objects 1 } > > tn3270Port OBJECT-TYPE > SYNTAX Integer32 (1..65535) > MAX-ACCESS read-write > STATUS current > DESCRIPTION > "Indicates the port for use by the TN3270/TN3270E Server. > Port 23 is the well known Telnet port and if the default." > DEFVAL { 23 } > ::= { tn3270Control 1 } > > tn3270InactivityTimer OBJECT-TYPE > SYNTAX Integer32 (0..99999999) > MAX-ACCESS read-write > STATUS current > DESCRIPTION > "The inactivity time-out specified in seconds. When a > connection has been inactive for the number of seconds > specified by this object it is closed. The default of > 0 means no inactivity time-out." > DEFVAL { 0 } > ::= { tn3270Control 2 } > > tn3270Timemark OBJECT-TYPE > SYNTAX Integer32 > MAX-ACCESS read-write > STATUS current > DESCRIPTION > "The TIMEMARK processing time-out specified in seconds. > A value of 0 disables this function." > DEFVAL { 600 } -- 10 minutes > ::= { tn3270Control 3 } > > tn3270ScanInterval OBJECT-TYPE > SYNTAX Integer32 > MAX-ACCESS read-write > STATUS current > DESCRIPTION > "The scan interval to be used by the Telnet Server. > TIMEMARK processing scans the Telnet sessions every > tn3270ScanInterval period (specified in seconds) for > sessions that have been idle for more than the value > > > > Expires November 1997 [Page 5]~ > > > > > > White TN3270 Management Information Base (TN3270-MIB) 30 May 1997 > > > if tn3270Timemark. Sessions that are idle more than > the value of tn3270Timemark are checked by sending a > Telnet IAC Timemark command. > > A value of 0 implies that TIMEMARK processing is > not in effect." > DEFVAL { 120 } -- 2 minutes > ::= { tn3270Control 4 } > > tn3270BinaryLineMode OBJECT-TYPE > SYNTAX TruthValue > MAX-ACCESS read-write > STATUS current > DESCRIPTION > "A value of true(1) for this object allows incoming > Telnet line-mode sessions to operate in binary mode." > DEFVAL { false } > ::= { tn3270Control 5 } > > tn3270DisableSga OBJECT-TYPE > SYNTAX TruthValue > MAX-ACCESS read-write > STATUS current > DESCRIPTION > "A value of true(1) for this object suppresses the > transmission of GO AHEADs by Telnet. This must be > negotiated by both client and server. Selection of this > option reduces the overhead for a full duplex terminal > and a full duplex connection." > DEFVAL { false } > ::= { tn3270Control 6 } > > tn3270AdminStatus OBJECT-TYPE > SYNTAX INTEGER { > up(1), > down(2) > } > MAX-ACCESS read-write > STATUS current > DESCRIPTION > "The desired state of the Telnet Server." > ::= { tn3270Control 7 } > > tn3270OperStatus OBJECT-TYPE > SYNTAX INTEGER { > up(1), > down(2) > } > > > > Expires November 1997 [Page 6]~ > > > > > > White TN3270 Management Information Base (TN3270-MIB) 30 May 1997 > > > MAX-ACCESS read-only > STATUS current > DESCRIPTION > "The current operational state of the Telnet Server." > ::= { tn3270Control 8 } > > tn3270DefaultApplName OBJECT-TYPE > SYNTAX DisplayString (SIZE(0..8)) > MAX-ACCESS read-write > STATUS current > DESCRIPTION > "The default Application to use. Typically this is an > initial application which is either a network solictor or > front-end menu system. > > A null length octet string implies no default is in effect." > DEFVAL { ''H } > ::= { tn3270Control 9 } > > tn3270DefaultApplIpAddress OBJECT-TYPE > SYNTAX IpAddress > MAX-ACCESS read-write > STATUS current > DESCRIPTION > "The default Application's IP Address. A value of 0 implies > no IP Address has been set." > DEFVAL { 0 } > ::= { tn3270Control 10 } > > tn3270DefaultApplIpGroupName OBJECT-TYPE > SYNTAX DisplayString (SIZE(0..8)) > MAX-ACCESS read-write > STATUS current > DESCRIPTION > "The IP Group name to be used with the default Application. > A null octet string implies that IP Group name has not > been specified." > DEFVAL { ''H } > ::= { tn3270Control 11 } > > tn3270DefaultApplIfIndex OBJECT-TYPE > SYNTAX InterfaceIndexOrZero > MAX-ACCESS read-write > STATUS current > DESCRIPTION > "The ifEntry to be used by the default Application. > A value of 0 implies that this object has not been set." > DEFVAL { 0 } > > > > Expires November 1997 [Page 7]~ > > > > > > White TN3270 Management Information Base (TN3270-MIB) 30 May 1997 > > > ::= { tn3270Control 12 } > > tn3270TelnetAppl OBJECT-TYPE > SYNTAX DisplayString (SIZE(0..8)) > MAX-ACCESS read-write > STATUS current > DESCRIPTION > "The application to which to connect when a Telnet Client > establishes a 3270 connection." > DEFVAL { ''H } > ::= { tn3270Control 13 } > > tn3270LmApplName OBJECT-TYPE > SYNTAX DisplayString (SIZE(0..8)) > MAX-ACCESS read-write > STATUS current > DESCRIPTION > "The Application to use when a Telnet Client establishes > a line-mode connection. > > A null length octet string implies not set." > DEFVAL { ''H } > ::= { tn3270Control 14 } > > tn3270LmApplIpAddress OBJECT-TYPE > SYNTAX IpAddress > MAX-ACCESS read-write > STATUS current > DESCRIPTION > "The line-mode Application's IP Address. A value of 0 implies > no IP Address has been set." > DEFVAL { 0 } > ::= { tn3270Control 15 } > > tn3270LmApplIpGroupName OBJECT-TYPE > SYNTAX DisplayString (SIZE(0..8)) > MAX-ACCESS read-write > STATUS current > DESCRIPTION > "The IP Group name to be used with the line-mode Application. > A null octet string implies that IP Group name has not > been specified." > DEFVAL { ''H } > ::= { tn3270Control 16 } > > tn3270LmApplIfIndex OBJECT-TYPE > SYNTAX InterfaceIndexOrZero > MAX-ACCESS read-write > > > > Expires November 1997 [Page 8]~ > > > > > > White TN3270 Management Information Base (TN3270-MIB) 30 May 1997 > > > STATUS current > DESCRIPTION > "The ifEntry to be used by the line-mode Application. > A value of 0 implies that this object has not been set." > DEFVAL { 0 } > ::= { tn3270Control 17 } > > tn3270UsstcpTableName OBJECT-TYPE > SYNTAX DisplayString (SIZE(0..8)) > MAX-ACCESS read-write > STATUS current > DESCRIPTION > "The name of USS definition table for message 10. This > applies to 3270 devices only. It allows the mapping of > a customized USS message 1- screen to either a remote IP > address or a network interface using transparent-mode > operation to use as a Telnet logon screen. > > A null length octet string implies not set." > DEFVAL { ''H } > ::= { tn3270Control 18 } > > tn3270UsstcpIpAddress OBJECT-TYPE > SYNTAX IpAddress > MAX-ACCESS read-write > STATUS current > DESCRIPTION > "The USSTCP function's IP Address. A value of 0 implies > no IP Address has been set." > DEFVAL { 0 } > ::= { tn3270Control 19 } > > tn3270UsstcpIpGroupName OBJECT-TYPE > SYNTAX DisplayString (SIZE(0..8)) > MAX-ACCESS read-write > STATUS current > DESCRIPTION > "The IP Group name to be used with USSTCP processing. > A null octet string implies that IP Group name has not > been specified." > DEFVAL { ''H } > ::= { tn3270Control 20 } > > tn3270UsstcpIfIndex OBJECT-TYPE > SYNTAX InterfaceIndexOrZero > MAX-ACCESS read-write > STATUS current > DESCRIPTION > > > > Expires November 1997 [Page 9]~ > > > > > > White TN3270 Management Information Base (TN3270-MIB) 30 May 1997 > > > "The ifEntry to be used by USSTCP processing. > A value of 0 implies that this object has not been set." > DEFVAL { 0 } > ::= { tn3270Control 21 } > > tn3270SessionTermState OBJECT-TYPE > SYNTAX INTEGER { > terminate(1), > luSessionPend(2), > queueSession(3) > } > MAX-ACCESS read-write > STATUS current > DESCRIPTION > "The current state for determining what happens when > Telnet connection terminates: > > terminate(1) => Terminate connection. > luSessionPend(2) => Allows the client's session to revert > to their Default Application upon > termination of their Telnet connection. > queueSession(3) => ????" > DEFVAL { terminate } > ::= { tn3270Control 22 } > > tn3270Msg07Enabled OBJECT-TYPE > SYNTAX TruthValue > MAX-ACCESS read-write > STATUS current > DESCRIPTION > "The value of this object determines what happens when a > Telnet connection is trying to establish the connection > but goes down due to an error. Setting this object to > true(1) causes a USSMSG 7 (or other error type USSMSG) to > be displayed. The default is, false(2), to break the connection > without any indication of what the error was." > DEFVAL { false } > ::= { tn3270Control 23 } > > tn3270OldSolicitorEnabled OBJECT-TYPE > SYNTAX TruthValue > MAX-ACCESS read-write > STATUS current > DESCRIPTION > "The value of this object determines where the cursor is placed > on the Telnet solicitor screen. Setting this object to true(1) > causes the cursor to be placed on the userid entry of the > solicitor screen for the first display only. The default > > > > Expires November 1997 [Page 10]~ > > > > > > White TN3270 Management Information Base (TN3270-MIB) 30 May 1997 > > > (false(2) is to put the cursor on the application entry of the > solicitor screen." > DEFVAL { false } > ::= { tn3270Control 24 } > > > -- The ALLOWAPPL Table definitions > > tn3270AllowApplTable OBJECT-TYPE > SYNTAX SEQUENCE OF Tn3270AllowApplEntry > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "The Applications that the Telnet Server can access." > ::= { tn3270Objects 2 } > > tn3270AllowApplEntry OBJECT-TYPE > SYNTAX Tn3270AllowApplEntry > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "Information about a single Application that the Telnet > Server can access. > > An Application can be qualified with a list of LUs by > adding entries to the tn3270AllowApplLuTable. The > tn3270AllowApplLuTable is indexed by tn3270AllowApplName > and tn3270AllowApplLuName." > INDEX { tn3270AllowApplName } > ::= { tn3270AllowApplTable 1 } > > Tn3270AllowApplEntry ::= SEQUENCE { > tn3270AllowApplName VariableName, > tn3270AllowApplDisconnect TruthValue, > tn3270AllowApplRowStatus RowStatus } > > tn3270AllowApplName OBJECT-TYPE > SYNTAX VariableName > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "The name of the application that can be accessed." > ::= { tn3270AllowApplEntry 1 } > > tn3270AllowApplDisconnect OBJECT-TYPE > SYNTAX TruthValue > MAX-ACCESS read-create > STATUS current > > > > Expires November 1997 [Page 11]~ > > > > > > White TN3270 Management Information Base (TN3270-MIB) 30 May 1997 > > > DESCRIPTION > "When set to true this allows the application to be > notified to disconnect rather than log off a user when > the session is dropped." > DEFVAL { false } > ::= { tn3270AllowApplEntry 2 } > > tn3270AllowApplRowStatus OBJECT-TYPE > SYNTAX RowStatus > MAX-ACCESS read-create > STATUS current > DESCRIPTION > "This object allows entries to be created and deleted in the > tn3270AllowApplTable. > > When an entry in the tn3270AllowApplTable is deleted > deleted (by setting this object to destroy(6)), this has > the side-effect of removing all entries from the > tn3270AllowApplLuTable that are associated with the > entry being deleted." > REFERENCE > "RFC 1903, 'Textual Conventions for version 2 of the Simple > Network Management Protocol (SNMPv2).'" > ::= { tn3270AllowApplEntry 3 } > > tn3270AllowApplLuTable OBJECT-TYPE > SYNTAX SEQUENCE OF Tn3270AllowApplLuEntry > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "The LUs associated with a tn3270AllowApplEntry. > Use of this table is optional. The preferred method of > associating LUs to Applications is via the > tn3270LuMapTable." > ::= { tn3270Objects 3 } > > tn3270AllowApplLuEntry OBJECT-TYPE > SYNTAX Tn3270AllowApplLuEntry > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "Definition of a single LU associated with a > tn3270AllowApplEntry." > INDEX { tn3270AllowApplName, tn3270AllowApplLuName } > ::= { tn3270AllowApplLuTable 1 } > > Tn3270AllowApplLuEntry ::= SEQUENCE { > tn3270AllowApplLuName DisplayString, > > > > Expires November 1997 [Page 12]~ > > > > > > White TN3270 Management Information Base (TN3270-MIB) 30 May 1997 > > > tn3270AllowApplLuRowStatus RowStatus } > > tn3270AllowApplLuName OBJECT-TYPE > SYNTAX DisplayString (SIZE(1..8)) > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "The name of a LU associated with an Application." > ::= { tn3270AllowApplLuEntry 1 } > > tn3270AllowApplLuRowStatus OBJECT-TYPE > SYNTAX RowStatus > MAX-ACCESS read-create > STATUS current > DESCRIPTION > "This object allows entries to be created and deleted in the > tn3270AllowApplLuTable. > > When an entry in the tn3270AllowApplTable is deleted > deleted (by setting this object to destroy(6)) it has no > effect on the associating tn3270AllowApplEntry." > REFERENCE > "RFC 1903, 'Textual Conventions for version 2 of the Simple > Network Management Protocol (SNMPv2).'" > ::= { tn3270AllowApplLuEntry 2 } > > -- The RESTRICTAPPL Table definitions > > tn3270RestrictApplTable OBJECT-TYPE > SYNTAX SEQUENCE OF Tn3270RestrictApplEntry > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "The Applications that the Telnet Server provides > restricted access." > ::= { tn3270Objects 4 } > > tn3270RestrictApplEntry OBJECT-TYPE > SYNTAX Tn3270RestrictApplEntry > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "Definition of a single restricted Application that the Telnet > Server can access. > > An Application is qualified with a list of users that are > allowed access to the application via the > tn3270RestrictApplUserTable." > > > > Expires November 1997 [Page 13]~ > > > > > > White TN3270 Management Information Base (TN3270-MIB) 30 May 1997 > > > INDEX { tn3270RestrictApplName } > ::= { tn3270RestrictApplTable 1 } > > Tn3270RestrictApplEntry ::= SEQUENCE { > tn3270RestrictApplName VariableName, > tn3270RestrictApplDisconnect TruthValue, > tn3270RestrictApplRowStatus RowStatus } > > tn3270RestrictApplName OBJECT-TYPE > SYNTAX VariableName > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "The name of the application that can be accessed." > ::= { tn3270RestrictApplEntry 1 } > > tn3270RestrictApplDisconnect OBJECT-TYPE > SYNTAX TruthValue > MAX-ACCESS read-create > STATUS current > DESCRIPTION > "When set to true this allows the application to be > notified to disconnect rather than log off a user when > the session is dropped." > DEFVAL { false } > ::= { tn3270RestrictApplEntry 2 } > > tn3270RestrictApplRowStatus OBJECT-TYPE > SYNTAX RowStatus > MAX-ACCESS read-create > STATUS current > DESCRIPTION > "This object allows entries to be created and deleted in the > tn3270RestrictApplTable. > > When an entry in the tn3270RestrictApplTable is deleted > deleted (by setting this object to destroy(6)), this has > the side-effect of removing all entries from the > tn3270RestrictApplUserTable that are associated with the > entry being deleted." > REFERENCE > "RFC 1903, 'Textual Conventions for version 2 of the Simple > Network Management Protocol (SNMPv2).'" > ::= { tn3270RestrictApplEntry 3 } > > tn3270RestrictApplUserTable OBJECT-TYPE > SYNTAX SEQUENCE OF Tn3270RestrictApplUserEntry > MAX-ACCESS not-accessible > > > > Expires November 1997 [Page 14]~ > > > > > > White TN3270 Management Information Base (TN3270-MIB) 30 May 1997 > > > STATUS current > DESCRIPTION > "The Users associated with a tn3270RestrictApplEntry." > ::= { tn3270Objects 5 } > > tn3270RestrictApplUserEntry OBJECT-TYPE > SYNTAX Tn3270RestrictApplUserEntry > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "Definition of a single User associated with a > tn3270RestrictApplEntry." > INDEX { tn3270RestrictApplName, tn3270RestrictApplUserName } > ::= { tn3270RestrictApplUserTable 1 } > > Tn3270RestrictApplUserEntry ::= SEQUENCE { > tn3270RestrictApplUserName DisplayString, > tn3270RestrictApplUserRowStatus RowStatus } > > tn3270RestrictApplUserName OBJECT-TYPE > SYNTAX DisplayString (SIZE(1..8)) > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "The name of a User allowed access with the corresponding > Application." > ::= { tn3270RestrictApplUserEntry 1 } > > tn3270RestrictApplUserRowStatus OBJECT-TYPE > SYNTAX RowStatus > MAX-ACCESS read-create > STATUS current > DESCRIPTION > "This object allows entries to be created and deleted in the > tn3270RestrictApplUserTable. > > When an entry in the tn3270RestrictApplTable is deleted > deleted (by setting this object to destroy(6)) it has no > effect on the associating tn3270RestrictApplEntry. > However, corresponding tn3270RestrictApplULuTable entries > are deleted." > REFERENCE > "RFC 1903, 'Textual Conventions for version 2 of the Simple > Network Management Protocol (SNMPv2).'" > ::= { tn3270RestrictApplUserEntry 2 } > > tn3270RestrictApplULuTable OBJECT-TYPE > SYNTAX SEQUENCE OF Tn3270RestrictApplULuEntry > > > > Expires November 1997 [Page 15]~ > > > > > > White TN3270 Management Information Base (TN3270-MIB) 30 May 1997 > > > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "The LUs associated with a Restricted Application User. > Use of this table is optional. The preferred method of > associating LUs with Applications is via the > tn3270LuMapTable." > ::= { tn3270Objects 6 } > > tn3270RestrictApplULuEntry OBJECT-TYPE > SYNTAX Tn3270RestrictApplULuEntry > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "Definition of a single LU associated with a > tn3270RestrictApplLuEntry." > INDEX { tn3270RestrictApplName, tn3270RestrictApplUserName, > tn3270RestrictApplULuName } > ::= { tn3270RestrictApplULuTable 1 } > > Tn3270RestrictApplULuEntry ::= SEQUENCE { > tn3270RestrictApplULuName DisplayString, > tn3270RestrictApplULuRowStatus RowStatus } > > tn3270RestrictApplULuName OBJECT-TYPE > SYNTAX DisplayString (SIZE(1..8)) > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "The name of an LU." > ::= { tn3270RestrictApplULuEntry 1 } > > tn3270RestrictApplULuRowStatus OBJECT-TYPE > SYNTAX RowStatus > MAX-ACCESS read-create > STATUS current > DESCRIPTION > "This object allows entries to be created and deleted in the > tn3270RestrictApplULuTable. > > When an entry in the tn3270RestrictApplULuTable is deleted > deleted (by setting this object to destroy(6)) it has no > effect on the associating tn3270RestrictApplUserEntry." > REFERENCE > "RFC 1903, 'Textual Conventions for version 2 of the Simple > Network Management Protocol (SNMPv2).'" > ::= { tn3270RestrictApplULuEntry 2 } > > > > > Expires November 1997 [Page 16]~ > > > > > > White TN3270 Management Information Base (TN3270-MIB) 30 May 1997 > > > tn3270IpGroupTable OBJECT-TYPE > SYNTAX SEQUENCE OF Tn3270IpGroupEntry > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "This table defines IP Address grouping for use by the > Telnet Server." > ::= { tn3270Objects 7 } > > tn3270IpGroupEntry OBJECT-TYPE > SYNTAX Tn3270IpGroupEntry > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "Definition of a single IP Address entry. All entries with > the same 1st index, tn3270IpGroupName are considered to > be in the same IP Group." > INDEX { tn3270IpGroupName, tn3270IpGroupIpAddress } > ::= { tn3270IpGroupTable 1 } > > Tn3270IpGroupEntry ::= SEQUENCE { > tn3270IpGroupName DisplayString, > tn3270IpGroupIpAddress IpAddress, > tn3270IpGroupSubnetMask IpAddress, > tn3270IpGroupIpSubnet IpAddress, > tn3270IpGroupRowStatus RowStatus } > > tn3270IpGroupName OBJECT-TYPE > SYNTAX DisplayString (SIZE(1..8)) > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "The name of a IP Group." > ::= { tn3270IpGroupEntry 1 } > > tn3270IpGroupIpAddress OBJECT-TYPE > SYNTAX IpAddress > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "The IP Address of a member of a IP Group." > ::= { tn3270IpGroupEntry 2 } > > tn3270IpGroupSubnetMask OBJECT-TYPE > SYNTAX IpAddress > MAX-ACCESS read-create > STATUS current > DESCRIPTION > > > > Expires November 1997 [Page 17]~ > > > > > > White TN3270 Management Information Base (TN3270-MIB) 30 May 1997 > > > "The corresponding subnet mask associated with > tn3270IpGroupIpSubnet." > ::= { tn3270IpGroupEntry 3 } > > tn3270IpGroupIpSubnet OBJECT-TYPE > SYNTAX IpAddress > MAX-ACCESS read-create > STATUS current > DESCRIPTION > "The IP Subnet to be used with the objects > tn3270IpGroupIpAddress and tn3270IpGroupSubnetMask." > ::= { tn3270IpGroupEntry 4 } > > tn3270IpGroupRowStatus OBJECT-TYPE > SYNTAX RowStatus > MAX-ACCESS read-create > STATUS current > DESCRIPTION > "This object allows entries to be created and deleted in the > tn3270IpGroupTable. > > An entry in this table is deleted by setting this object > to destroy(6)." > REFERENCE > "RFC 1903, 'Textual Conventions for version 2 of the Simple > Network Management Protocol (SNMPv2).'" > ::= { tn3270IpGroupEntry 5 } > > tn3270LuGroupTable OBJECT-TYPE > SYNTAX SEQUENCE OF Tn3270LuGroupEntry > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "This table defines LU groups for use by the > Telnet Server." > ::= { tn3270Objects 8 } > > tn3270LuGroupEntry OBJECT-TYPE > SYNTAX Tn3270LuGroupEntry > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "Definition of a single LU Group member. All entries with > the same 1st index, tn3270LuGroupName are considered to > be in the same LU Group. > > The first entry in this table is used for defining the > default LU Group. By convention tn3270LuGroupName should > > > > Expires November 1997 [Page 18]~ > > > > > > White TN3270 Management Information Base (TN3270-MIB) 30 May 1997 > > > be set to 8 blanks to represent this entry." > INDEX { tn3270LuGroupName, tn3270LuGroupLuName } > ::= { tn3270LuGroupTable 1 } > > Tn3270LuGroupEntry ::= SEQUENCE { > tn3270LuGroupName DisplayString, > tn3270LuGroupLuName DisplayString, > tn3270LuGroupRowStatus RowStatus } > > tn3270LuGroupName OBJECT-TYPE > SYNTAX DisplayString (SIZE(1..8)) > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "The name of a LU Group." > ::= { tn3270LuGroupEntry 1 } > > tn3270LuGroupLuName OBJECT-TYPE > SYNTAX DisplayString (SIZE(1..8)) > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "The LU Name of a member of a Lu Group." > ::= { tn3270LuGroupEntry 2 } > > tn3270LuGroupRowStatus OBJECT-TYPE > SYNTAX RowStatus > MAX-ACCESS read-create > STATUS current > DESCRIPTION > "This object allows entries to be created and deleted in the > tn3270LuGroupTable. > > An entry in this table is deleted by setting this object > to destroy(6)." > REFERENCE > "RFC 1903, 'Textual Conventions for version 2 of the Simple > Network Management Protocol (SNMPv2).'" > ::= { tn3270LuGroupEntry 3 } > > tn3270PrtGroupTable OBJECT-TYPE > SYNTAX SEQUENCE OF Tn3270PrtGroupEntry > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "This table defines Printer groups for use by the > Telnet Server." > ::= { tn3270Objects 9 } > > > > Expires November 1997 [Page 19]~ > > > > > > White TN3270 Management Information Base (TN3270-MIB) 30 May 1997 > > > tn3270PrtGroupEntry OBJECT-TYPE > SYNTAX Tn3270PrtGroupEntry > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "Definition of a single Printer Group member. All entries with > the same 1st index, tn3270PrtGroupName are considered to > be in the same Printer Group." > INDEX { tn3270PrtGroupName, tn3270PrtGroupPrtName } > ::= { tn3270PrtGroupTable 1 } > > Tn3270PrtGroupEntry ::= SEQUENCE { > tn3270PrtGroupName DisplayString, > tn3270PrtGroupPrtName DisplayString, > tn3270PrtGroupRowStatus RowStatus } > > tn3270PrtGroupName OBJECT-TYPE > SYNTAX DisplayString (SIZE(1..8)) > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "The name of a Printer Group." > ::= { tn3270PrtGroupEntry 1 } > > tn3270PrtGroupPrtName OBJECT-TYPE > SYNTAX DisplayString (SIZE(1..8)) > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "The Printer Name of a member of a Printer Group." > ::= { tn3270PrtGroupEntry 2 } > > tn3270PrtGroupRowStatus OBJECT-TYPE > SYNTAX RowStatus > MAX-ACCESS read-create > STATUS current > DESCRIPTION > "This object allows entries to be created and deleted in the > tn3270PrtGroupTable. > > An entry in this table is deleted by setting this object > to destroy(6)." > REFERENCE > "RFC 1903, 'Textual Conventions for version 2 of the Simple > Network Management Protocol (SNMPv2).'" > ::= { tn3270PrtGroupEntry 3 } > > tn3270LuMapTable OBJECT-TYPE > > > > Expires November 1997 [Page 20]~ > > > > > > White TN3270 Management Information Base (TN3270-MIB) 30 May 1997 > > > SYNTAX SEQUENCE OF Tn3270LuMapEntry > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "This table defines LU to IP mappings. An IP Address or > IP Address group can only be assigned to a LU or LU > Group once." > ::= { tn3270Objects 10 } > > tn3270LuMapEntry OBJECT-TYPE > SYNTAX Tn3270LuMapEntry > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "Definition of the mapping of a single IP Address or IP > Address Group to either a LU or LU Group." > INDEX { tn3270LuMapLuName } > ::= { tn3270LuMapTable 1 } > > Tn3270LuMapEntry ::= SEQUENCE { > tn3270LuMapLuName DisplayString, > tn3270LuMapIpAddr IpAddress, > tn3270LuMapIpGroupName DisplayString, > tn3270LuMapRowStatus RowStatus } > > tn3270LuMapLuName OBJECT-TYPE > SYNTAX DisplayString (SIZE(1..8)) > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "The name of either a LU or LU Group Name." > ::= { tn3270LuMapEntry 1 } > > tn3270LuMapIpAddr OBJECT-TYPE > SYNTAX IpAddress > MAX-ACCESS read-create > STATUS current > DESCRIPTION > "The IP address to map to a LU. If this object is non-zero > then tn3270LuMapLuName MUST be a single LU Name and > tn3270LuMapIpGroupName MUST be a null octet string." > DEFVAL { 0 } > ::= { tn3270LuMapEntry 2 } > > tn3270LuMapIpGroupName OBJECT-TYPE > SYNTAX DisplayString (SIZE(0..8)) > MAX-ACCESS read-create > STATUS current > > > > Expires November 1997 [Page 21]~ > > > > > > White TN3270 Management Information Base (TN3270-MIB) 30 May 1997 > > > DESCRIPTION > "The IP addresses to map to a LU Group. If this object is > not a null octet string then tn3270LuMapLuName MUST be a > LU Group name and tn3270LuMapIpAddr MUST be zero." > DEFVAL { ''H } > ::= { tn3270LuMapEntry 3 } > > tn3270LuMapRowStatus OBJECT-TYPE > SYNTAX RowStatus > MAX-ACCESS read-create > STATUS current > DESCRIPTION > "This object allows entries to be created and deleted in the > tn3270LuMapTable. > > An entry in this table is deleted by setting this object > to destroy(6)." > REFERENCE > "RFC 1903, 'Textual Conventions for version 2 of the Simple > Network Management Protocol (SNMPv2).'" > ::= { tn3270LuMapEntry 4 } > > tn3270PrtMapTable OBJECT-TYPE > SYNTAX SEQUENCE OF Tn3270PrtMapEntry > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "This table defines Printer to IP mappings. An IP Address or > IP Address group can only be assigned to a single Printer or > Printer Group once." > ::= { tn3270Objects 11 } > > tn3270PrtMapEntry OBJECT-TYPE > SYNTAX Tn3270PrtMapEntry > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "Definition of the mapping of a single IP Address or IP > Address Group to either a Printer or Printer Group." > INDEX { tn3270PrtMapPrtName } > ::= { tn3270PrtMapTable 1 } > > Tn3270PrtMapEntry ::= SEQUENCE { > tn3270PrtMapPrtName DisplayString, > tn3270PrtMapIpAddr IpAddress, > tn3270PrtMapIpGroupName DisplayString, > tn3270PrtMapRowStatus RowStatus } > > > > > Expires November 1997 [Page 22]~ > > > > > > White TN3270 Management Information Base (TN3270-MIB) 30 May 1997 > > > tn3270PrtMapPrtName OBJECT-TYPE > SYNTAX DisplayString (SIZE(1..8)) > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "The name of either a Printer or Printer Group Name." > ::= { tn3270PrtMapEntry 1 } > > tn3270PrtMapIpAddr OBJECT-TYPE > SYNTAX IpAddress > MAX-ACCESS read-create > STATUS current > DESCRIPTION > "The IP address to map to a Printer. If this object is non- > zero > then tn3270PrtMapPrtName MUST be a single Printer and > tn3270PrtMapIpGroupName MUST be a null octet string." > DEFVAL { 0 } > ::= { tn3270PrtMapEntry 2 } > > tn3270PrtMapIpGroupName OBJECT-TYPE > SYNTAX DisplayString (SIZE(0..8)) > MAX-ACCESS read-create > STATUS current > DESCRIPTION > "The IP addresses to map to a Printer Group. If this object is > not a null octet string then tn3270PrtMapPrtName MUST be a > Printer Group name and tn3270PrtMapIpAddr MUST be zero." > DEFVAL { ''H } > ::= { tn3270PrtMapEntry 3 } > > tn3270PrtMapRowStatus OBJECT-TYPE > SYNTAX RowStatus > MAX-ACCESS read-create > STATUS current > DESCRIPTION > "This object allows entries to be created and deleted in the > tn3270PrtMapTable. > > An entry in this table is deleted by setting this object > to destroy(6)." > REFERENCE > "RFC 1903, 'Textual Conventions for version 2 of the Simple > Network Management Protocol (SNMPv2).'" > ::= { tn3270PrtMapEntry 4 } > > tn3270LogmodeTable OBJECT-TYPE > SYNTAX SEQUENCE OF Tn3270LogmodeEntry > > > > Expires November 1997 [Page 23]~ > > > > > > White TN3270 Management Information Base (TN3270-MIB) 30 May 1997 > > > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "This table defines the logmode to be used for a particular > interface entry." > ::= { tn3270Objects 12 } > > tn3270LogmodeEntry OBJECT-TYPE > SYNTAX Tn3270LogmodeEntry > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "Definition of the logmode setting for a single interface > entry." > INDEX { tn3270LogmodeIfIndex } > ::= { tn3270LogmodeTable 1 } > > Tn3270LogmodeEntry ::= SEQUENCE { > tn3270LogmodeIfIndex InterfaceIndex, > tn3270LogmodeName DisplayString, > tn3270LogmodeRowStatus RowStatus } > > tn3270LogmodeIfIndex OBJECT-TYPE > SYNTAX InterfaceIndex > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "The ifIndex of a interface entry to associate a logmode > with." > ::= { tn3270LogmodeEntry 1 } > > tn3270LogmodeName OBJECT-TYPE > SYNTAX DisplayString (SIZE(0..8)) > MAX-ACCESS read-create > STATUS current > DESCRIPTION > "The Logmode name to use for this particular interface. A > value of a null octet string implies that the default > logmode, which is dependent on the interface's type, should > be used." > DEFVAL { ''H } > ::= { tn3270LogmodeEntry 2 } > > tn3270LogmodeRowStatus OBJECT-TYPE > SYNTAX RowStatus > MAX-ACCESS read-create > STATUS current > DESCRIPTION > > > > Expires November 1997 [Page 24]~ > > > > > > White TN3270 Management Information Base (TN3270-MIB) 30 May 1997 > > > "This object allows entries to be created and deleted in the > tn3270LogmodeTable. > > An entry in this table is deleted by setting this object > to destroy(6)." > REFERENCE > "RFC 1903, 'Textual Conventions for version 2 of the Simple > Network Management Protocol (SNMPv2).'" > ::= { tn3270LogmodeEntry 3 } > > -- Define the set of objects to augment the Tcp Connection Table with. > > tn3270TcpConnTable OBJECT-TYPE > SYNTAX SEQUENCE OF Tn3270TcpConnEntry > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "Extends tcpConnTable to support TN3270 and TN3270E > performance monitoring." > ::= { tn3270Objects 13 } > > tn3270TcpConnEntry OBJECT-TYPE > SYNTAX Tn3270TcpConnEntry > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "Descibes a particular tcp connection entry." > AUGMENTS { tcpConnEntry } > ::= { tn3270TcpConnTable 1 } > > Tn3270TcpConnEntry ::= > SEQUENCE > { > tn3270TcpConnLastActivity TimeTicks, > tn3270TcpConnBytesIn Integer32, > tn3270TcpConnBytesOut Integer32, > tn3270TcpConnReXmt Integer32, > tn3270TcpConnReXmtCount Integer32, > tn3270TcpConnRoundTripTime Integer32, > tn3270TcpConnRoundTripVariance Integer32, > tn3270TcpConnTargetAppl DisplayString, > tn3270TcpConnLuName DisplayString, > tn3270TcpConnClientUserId DisplayString, > tn3270TcpConnLogMode DisplayString, > tn3270TcpConnProto OCTET STRING > } > > tn3270TcpConnLastActivity OBJECT-TYPE > > > > Expires November 1997 [Page 25]~ > > > > > > White TN3270 Management Information Base (TN3270-MIB) 30 May 1997 > > > SYNTAX TimeTicks > MAX-ACCESS read-only > STATUS current > DESCRIPTION > "The number of 100ths of seconds since this entry > was last used." > DEFVAL { 0 } > ::= { tn3270TcpConnEntry 1 } > > tn3270TcpConnBytesIn OBJECT-TYPE > SYNTAX Integer32 > MAX-ACCESS read-only > STATUS current > DESCRIPTION > "The number of bytes received from IP for this > connection." > DEFVAL { 0 } > ::= { tn3270TcpConnEntry 2 } > > tn3270TcpConnBytesOut OBJECT-TYPE > SYNTAX Integer32 > MAX-ACCESS read-only > STATUS current > DESCRIPTION > "The number of bytes sent to IP for this connection." > DEFVAL { 0 } > ::= { tn3270TcpConnEntry 3 } > > tn3270TcpConnReXmt OBJECT-TYPE > SYNTAX Integer32 > MAX-ACCESS read-only > STATUS current > DESCRIPTION > "Number of retransmissions" > DEFVAL { 0 } > ::= { tn3270TcpConnEntry 4 } > > tn3270TcpConnReXmtCount OBJECT-TYPE > SYNTAX Integer32 > MAX-ACCESS read-only > STATUS current > DESCRIPTION > "Current retransmission count" > DEFVAL { 0 } > ::= { tn3270TcpConnEntry 5 } > > tn3270TcpConnRoundTripTime OBJECT-TYPE > SYNTAX Integer32 > > > > Expires November 1997 [Page 26]~ > > > > > > White TN3270 Management Information Base (TN3270-MIB) 30 May 1997 > > > MAX-ACCESS read-only > STATUS current > DESCRIPTION > "The amount of time that has elapsed, measured in > milliseconds, from when the last TCP segment was > transmitted by the TCP Stack until the ACK was > received." > DEFVAL { 0 } > ::= { tn3270TcpConnEntry 6 } > > tn3270TcpConnRoundTripVariance OBJECT-TYPE > SYNTAX Integer32 > MAX-ACCESS read-only > STATUS current > DESCRIPTION > "Round trip time variance." > DEFVAL { 0 } > ::= { tn3270TcpConnEntry 7 } > > tn3270TcpConnTargetAppl OBJECT-TYPE > SYNTAX DisplayString (SIZE(0..8)) > MAX-ACCESS read-only > STATUS current > DESCRIPTION > "When the corresponding TCP connection is for a > 3172 Telnet session then this object contains the > Target VTAM Application name." > ::= { tn3270TcpConnEntry 8 } > > tn3270TcpConnLuName OBJECT-TYPE > SYNTAX DisplayString (SIZE(0..8)) > MAX-ACCESS read-only > STATUS current > DESCRIPTION > "When the corresponding TCP connection is for a > 3172 Telnet session then this object contains the > VTAM LU name." > ::= { tn3270TcpConnEntry 9 } > > tn3270TcpConnClientUserId OBJECT-TYPE > SYNTAX DisplayString (SIZE(0..8)) > MAX-ACCESS read-only > STATUS current > DESCRIPTION > "When the corresponding TCP connection is for a > 3172 Telnet session then this object contains the > Client's userid." > ::= { tn3270TcpConnEntry 10 } > > > > Expires November 1997 [Page 27]~ > > > > > > White TN3270 Management Information Base (TN3270-MIB) 30 May 1997 > > > tn3270TcpConnLogMode OBJECT-TYPE > SYNTAX DisplayString (SIZE(0..8)) > MAX-ACCESS read-only > STATUS current > DESCRIPTION > "When the corresponding TCP connection is for a > 3172 Telnet session then this object contains the > LOG Mode." > ::= { tn3270TcpConnEntry 11 } > > tn3270TcpConnProto OBJECT-TYPE > SYNTAX OCTET STRING (SIZE(4)) > MAX-ACCESS read-only > STATUS current > DESCRIPTION > "This flag will indicates the following Telnet modes: > -bit(1 - 28) = > -bit(29) = TN3270EE mode > -bit(30) = TN3270 mode > -bit(31) = TN3270E mode > -bit(32) = line mode" > ::= { tn3270TcpConnEntry 12 } > > > -- Conformance Definitions > > tn3270Groups OBJECT IDENTIFIER ::= { tn3270Conformance 1 } > tn3270Compliances OBJECT IDENTIFIER ::= { tn3270Conformance 2 } > > -- compliance statements tn3270Compliance MODULE-COMPLIANCE > STATUS current > DESCRIPTION > "The compliance statement for agents that support the TN3270 > MIB." > MODULE -- this module > MANDATORY-GROUPS { tn3270BasicGroup, > tn3270TcpConnTableGroup > } > ::= { tn3270Compliances 1 } > > -- units of conformance tn3270BasicGroup OBJECT-GROUP > OBJECTS { > tn3270Port, > tn3270InactivityTimer, > tn3270Timemark, > tn3270ScanInterval, > tn3270BinaryLineMode, > tn3270DisableSga, > > > > Expires November 1997 [Page 28]~ > > > > > > White TN3270 Management Information Base (TN3270-MIB) 30 May 1997 > > > tn3270AdminStatus, > tn3270OperStatus, > tn3270DefaultApplName, > tn3270DefaultApplIpAddress, > tn3270DefaultApplIpGroupName, > tn3270DefaultApplIfIndex, > tn3270TelnetAppl, > tn3270LmApplName, > tn3270LmApplIpAddress, > tn3270LmApplIpGroupName, > tn3270LmApplIfIndex, > tn3270UsstcpTableName, > tn3270UsstcpIpAddress, > tn3270UsstcpIpGroupName, > tn3270UsstcpIfIndex, > tn3270SessionTermState, > tn3270Msg07Enabled, > tn3270OldSolicitorEnabled, > tn3270AllowApplDisconnect, > tn3270AllowApplRowStatus, > tn3270AllowApplLuRowStatus, > tn3270RestrictApplDisconnect, > tn3270RestrictApplRowStatus, > tn3270RestrictApplUserRowStatus, > tn3270RestrictApplULuRowStatus, > tn3270IpGroupSubnetMask, > tn3270IpGroupIpSubnet, > tn3270IpGroupRowStatus, > tn3270LuGroupRowStatus, > tn3270PrtGroupRowStatus, > tn3270LuMapIpAddr, > tn3270LuMapIpGroupName, > tn3270LuMapRowStatus, > tn3270PrtMapIpAddr, > tn3270PrtMapIpGroupName, > tn3270PrtMapRowStatus, > tn3270LogmodeName, > tn3270LogmodeRowStatus > } > STATUS current > DESCRIPTION > "This group is mandatory for all hosts supporting the > TN3270 connections." > ::= { tn3270Groups 1 } > > tn3270TcpConnTableGroup OBJECT-GROUP > OBJECTS { > tn3270TcpConnLastActivity, > > > > Expires November 1997 [Page 29]~ > > > > > > White TN3270 Management Information Base (TN3270-MIB) 30 May 1997 > > > tn3270TcpConnBytesIn, > tn3270TcpConnBytesOut, > tn3270TcpConnReXmt, > tn3270TcpConnReXmtCount, > tn3270TcpConnRoundTripTime, > tn3270TcpConnRoundTripVariance, > tn3270TcpConnTargetAppl, > tn3270TcpConnLuName, > tn3270TcpConnClientUserId, > tn3270TcpConnLogMode, > tn3270TcpConnProto > } > STATUS current > DESCRIPTION > "This group is mandatory for all hosts supporting the > TN3270 connections." > ::= { tn3270Groups 2 } > > END > > > > 5. Security Considerations > > Certain management information defined in this MIB may be considered > sensitive in some network environments. Therefore, authentication of > received SNMP requests and controlled access to management information > should be employed in such environments. The method for this > authentication is a function of the SNMP Administrative Framework, and > has not been expanded by this MIB. > > Several objects in this MIB allow write access or provide for remote > creation. Allowing this support in a non-secure environment can have a > negative effect on network operations. It is recommended that > implementers seriously consider whether set operations should be > allowed without providing, at a minimum, authentication of request > origin. It it recommended that without such support that the following > objects be implemented as read-only: > > o tn3270Port > o tn3270InactivityTimer > o tn3270Timemark > o tn3270ScanInterval > o tn3270BinaryLineMode > o tn3270DisableSga > o tn3270AdminStatus > o tn3270DefaultApplName > o tn3270DefaultApplIpAddress > > > > Expires November 1997 [Page 30]~ > > > > > > White TN3270 Management Information Base (TN3270-MIB) 30 May 1997 > > > o tn3270DefaultApplIpGroupName > o tn3270DefaultApplIfIndex > o tn3270TelnetAppl > o tn3270LmApplName > o tn3270LmApplIpAddress > o tn3270LmApplIpGroupName > o tn3270LmApplIfIndex > o tn3270UsstcpTableName > o tn3270UsstcpIpAddress > o tn3270UsstcpIpGroupName > o tn3270UsstcpIfIndex > o tn3270SessionTermState > o tn3270Msg07Enabled > o tn3270OldSolicitorEnabled > o tn3270AllowApplDisconnect > o tn3270AllowApplLuRowStatus > o tn3270RestrictApplDisconnect > o tn3270RestrictApplUserRowStatus > o tn3270RestrictApplULuRowStatus > o tn3270IpGroupSubnetMask > o tn3270IpGroupIpSubnet > o tn3270LuGroupRowStatus > o tn3270PrtGroupRowStatus > o tn3270LuMapIpAddr > o tn3270LuMapIpGroupName > o tn3270PrtMapIpAddr > o tn3270PrtMapIpGroupName > o tn3270LogmodeName > > The following objects should either be implemented as read-only or not > implemented when security is an issue as previously discussed: > > o tn3270AllowApplRowStatus > o tn3270RestrictApplRowStatus > o tn3270IpGroupRowStatus > o tn3270LuMapRowStatus > o tn3270PrtMapRowStatus > o tn3270LogmodeRowStatus > > > 6. Acknowledgments > > This document is a product of the TN3270E Working Group. > > > 7. References > > > > > > Expires November 1997 [Page 31]~ > > > > > > White TN3270 Management Information Base (TN3270-MIB) 30 May 1997 > > > [1] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and > Waldbusser S., "Structure of Management Information for version 2 > of the Simple Network Management Protocol (SNMPv2)", RFC 1902, > January 1996. > > > [2] Network Working Group, Postel, J., and Reynolds, J., "Telnet > Protocol Specification", RFC 854, May 1983. > > > [3] Network Working Group, Postel, J., and Reynolds, J., "Telnet Timing > Mark Option", RFC 860, May 1983. > > > [4] Network Working Group and Rekhter J., "Telnet 3270 Regime Option", > RFC 1041, January 1988. > > > [5] McCloghrie, K., and M. Rose, Editors, "Management Information Base > for Network Management of TCP/IP-based internets: MIB-II", STD 17, > RFC 1213, Hughes LAN Systems, Performance Systems International, > March 1991. > > > [6] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. > Waldbusser, "Textual Conventions for version 2 of the Simple > Network Management Protocol (SNMPv2)", RFC 1903, January 1996. > > > [7] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. > Waldbusser, "Protocol Operations for version 2 of the Simple > Network Management Protocol (SNMPv2)", RFC 1905, January 1996. > > > [8] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. > Waldbusser, "Conformance Statements for version 2 of the Simple > Network Management Protocol (SNMPv2)", RFC 1904, January 1996. > > > [9] Case, J., M. Fedor, M. Schoffstall, J. Davin, "Simple Network > Management Protocol", RFC 1157, SNMP Research, Performance Systems > International, MIT Laboratory for Computer Science, May 1990. > > > [10] IETF SNMPv2 Working Group and McCloghrie, K., "TCP-MIB > Definitions", November 1994. > > > > > > Expires November 1997 [Page 32]~ > > > > > > White TN3270 Management Information Base (TN3270-MIB) 30 May 1997 > > > 8. Authors' Addresses > > Kenneth D. White > Dept. G80/Bldg 503 > IBM Corporation > Research Triangle Park, NC 27709, USA > E-mail: kennethw@vnet.ibm.com > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Expires November 1997 [Page 33]~ >   Received: from ietf.org by ietf.org id aa07571; 3 Jun 97 10:04 EDT Received: from ietf.ietf.org by ietf.org id aa06832; 3 Jun 97 9:55 EDT Mime-Version: 1.0 Content-Type: Multipart/Mixed; Boundary="NextPart" To: IETF-Announce@ietf.org cc: tn3270e@list.nih.gov Sender:ietf-announce-request@ietf.org From: Internet-Drafts@ietf.org Reply-to: Internet-Drafts@ietf.org Subject: I-D ACTION:draft-ietf-tn3270e-tn3270-mib-00.txt Date: Tue, 03 Jun 1997 09:55:25 -0400 X-Orig-Sender: cclark@ietf.org Message-ID: <9706030955.aa06832@ietf.org> --NextPart A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Telnet TN3270 Enhancements Working Group of the IETF. Title : Definitions of Managed Objects for TN3270 Using SMIv2 Author(s) : K. White Filename : draft-ietf-tn3270e-tn3270-mib-00.txt Pages : 33 Date : 06/02/1997 The purpose of this memo is to define the Management Information Base (MIB) for configuring and monitoring TN3270 and TN3270E sessions. The monitoring portion of the MIB is limited to AUGMENTation of the TCP Connection Table (RFC 2012) with a set of objects collected from the TCP Layer. It is the intent of this MIB to fully adhere to all prerequisite MIBs unless explicitly stated. Deviations will be documented in corresponding conformance statements. The specification of this MIB will utilize the Structure of Management Information (SMI) for Version 2 of the Simple Network Management Protocol Version (refer to RFC1902, reference [1]). Internet-Drafts are available by anonymous FTP. Login with the username "anonymous" and a password of your e-mail address. After logging in, type "cd internet-drafts" and then "get draft-ietf-tn3270e-tn3270-mib-00.txt". A URL for the Internet-Draft is: ftp://ds.internic.net/internet-drafts/draft-ietf-tn3270e-tn3270-mib-00.txt Internet-Drafts directories are located at: o Africa: ftp.is.co.za o Europe: ftp.nordu.net ftp.nis.garr.it o Pacific Rim: munnari.oz.au o US East Coast: ds.internic.net o US West Coast: ftp.isi.edu Internet-Drafts are also available by mail. Send a message to: mailserv@ds.internic.net. In the body type: "FILE /internet-drafts/draft-ietf-tn3270e-tn3270-mib-00.txt". NOTE: The mail server at ds.internic.net can return the document in MIME-encoded form by using the "mpack" utility. To use this feature, insert the command "ENCODING mime" before the "FILE" command. To decode the response(s), you will need "munpack" or a MIME-compliant mail reader. Different MIME-compliant mail readers exhibit different behavior, especially when dealing with "multipart" MIME messages (i.e., documents which have been split up into multiple messages), so check your local documentation on how to manipulate these messages. Below is the data which will enable a MIME compliant mail reader implementation to automatically retrieve the ASCII version of the Internet-Draft. --NextPart Content-Type: Multipart/Alternative; Boundary="OtherAccess" --OtherAccess Content-Type: Message/External-body; access-type="mail-server"; server="mailserv@ds.internic.net" Content-Type: text/plain Content-ID: <19970602100632.I-D@ietf.org> ENCODING mime FILE /internet-drafts/draft-ietf-tn3270e-tn3270-mib-00.txt --OtherAccess Content-Type: Message/External-body; name="draft-ietf-tn3270e-tn3270-mib-00.txt"; site="ds.internic.net"; access-type="anon-ftp"; directory="internet-drafts" Content-Type: text/plain Content-ID: <19970602100632.I-D@ietf.org> --OtherAccess-- --NextPart--   Received: from cnri by ietf.org id aa09408; 17 Jun 97 11:32 EDT Received: from list.nih.gov (list.nih.gov [165.112.130.6]) by cnri.reston.va.us (8.8.5/8.7.3) with ESMTPid LAA27493 for ; Tue, 17 Jun 1997 11:31:42 -0400 (EDT) Received: from list.nih.gov (terrific.net.nih.gov [165.112.130.6]) by list.nih.gov (8.8.5/8.8.5) with ESMTP id LAA10446; Tue, 17 Jun 1997 11:24:56 -0400 (EDT) Received: from LIST.NIH.GOV by LIST.NIH.GOV (LISTSERV-TCP/IP release 1.8c) with spool id 2752115 for TN3270E@LIST.NIH.GOV; Tue, 17 Jun 1997 11:24:53 -0400 Received: from VNET.IBM.COM (vnet.ibm.com [204.146.168.194]) by list.nih.gov (8.8.5/8.8.5) with SMTP id LAA10421 for ; Tue, 17 Jun 1997 11:24:49 -0400 (EDT) Received: from RALVM5 by VNET.IBM.COM (IBM VM SMTP V2R3) with BSMTP id 2851; Tue, 17 Jun 97 11:24:46 EDT From: bart@vnet.ibm.com Message-Id: <199706171524.LAA10421@list.nih.gov> Date: Tue, 17 Jun 97 10:39:42 EDT To: tn3270e@list.nih.gov Subject: Work Group Activities Sender: owner-tn3270e@list.nih.gov The following is a list of the current Enhancements being examined by the tn3270e Enhancements work group and the party responsible for each item. Please comment on these items as well as suggest other items that you feel are important but not listed. A decision will be reached by the work group on the final list by the December meeting in Washington DC based upon the perceived priority of the item and amount of work group resource available to work on it. ITEMS RESPONSIBLE PARTY ------------------- ------------------- Security, Firewalls Michael Boe Compression, Caching Service Location Keith Humphrey Session Balancing RTM, Network Mgmt Robert Moore Keyboard Restore, Roger Erickson Bid/Implicit Bid Unbind, Sense Data, Ed Bailey OIA Length Indicator, Mark Williams Abort Flow (Flush) FMH Deric Bolton An initial description of each item will be posted on the listsrv by the responsible party for discussion.   Received: from cnri by ietf.org id aa04297; 18 Jun 97 7:27 EDT Received: from list.nih.gov (list.nih.gov [165.112.130.6]) by cnri.reston.va.us (8.8.5/8.7.3) with ESMTPid HAA00409 for ; Wed, 18 Jun 1997 07:26:10 -0400 (EDT) Received: from list.nih.gov (terrific.net.nih.gov [165.112.130.6]) by list.nih.gov (8.8.5/8.8.5) with ESMTP id HAA16651; Wed, 18 Jun 1997 07:00:21 -0400 (EDT) Received: from LIST.NIH.GOV by LIST.NIH.GOV (LISTSERV-TCP/IP release 1.8c) with spool id 2762882 for TN3270E@LIST.NIH.GOV; Wed, 18 Jun 1997 07:00:16 -0400 Received: from smtp.datcon.co.uk (smtp.datcon.co.uk [192.91.191.4]) by list.nih.gov (8.8.5/8.8.5) with SMTP id HAA16638 for ; Wed, 18 Jun 1997 07:00:06 -0400 (EDT) Received: by smtp.datcon.co.uk with SMTP (Microsoft Exchange Server Internet Mail Connector Version 4.0.995.52) id <01BC7BDE.F2F48AC0@smtp.datcon.co.uk>; Wed, 18 Jun 1997 11:58:34 +0100 Message-ID: From: Nick Weeds To: "'kennethw@VNET.IBM.COM'" Cc: 'TN3270E list' Subject: RE: Date: Wed, 18 Jun 1997 11:57:13 +0100 X-Mailer: Microsoft Exchange Server Internet Mail Connector Version 4.0.995.52 Encoding: 2038 TEXT Sender: owner-tn3270e@list.nih.gov Ken, The proposed TN3270 MIB is certainly an extensive and thorough effort. I wouldn't claim to be a MIB expert, but I am concerned that several aspects of this MIB might make it difficult or impossible to implement except in very specific products. 1) The MIB includes a lot of information which is only available on the host and not on a TN3270E gateway (unless the gateway administrator enters a lot of extra configuration information, in which case I'd question its likely accuracy). I'm thinking here of all the information about host applications and users. Is it valid just to leave these tables empty ? 2) Some of the MIB objects are not really relevant to TN3270 or TN3270E, or are rather implementation dependent. For example, the MIB includes control over binary line-mode and over go-aheads, and is overly specific about TIMEMARK keep-alives while omitting NOP keep-alives completely. 3) The MIB includes information which is at too low a level in the TCP/IP stack. I doubt whether many TN3270E implementations have much involvement with network interfaces, TCP retransmits or TCP round-trip times. The MIB also presents information in a way which will be easy for some implementations and difficult for others, but to a certain extent that's unavoidable. (As an example, the LuMapTable maps LU names to IP addresses, which is easy if the server works that way, but more awkward if it maps IP addresses to LU names.) For the MIB to be reasonably widely implemented in practice, I think it needs to contain a clearly-identified subset which is based on the TN3270/TN3270E Specs and which is generally applicable. It's not clear to me that the proposed MIB achieves this. Nick. >---------- >From: kennethw@VNET.IBM.COM[SMTP:kennethw@VNET.IBM.COM] >Sent: 31 May 1997 01:58 >To: tn3270e@list.nih.gov >Subject: > >I work with Ed Bailey and have been involved with configuration of >a TN3270 and TN3270E Server for a number of years, was a Performance >Monitor Application developer and have been involved in several of >the Network Management Area working groups. I have submitted the >attached internet draft to address a need for TN3270 Configuring, >monitoring and correlation of a TN3270 or TN3270E session with its >corresponding TCP Connection. > >The monitoring portion is fairly basic, essentially the TCP Round-trip >ACK, and will certainly need to be enhanced to provide more vigorous >support. Please take a look at the draft and provide feedback. The text >portion is somewhat brief since I expect that substantial changes will >have to be made as the result of discussion. > >Ken >--------------------------------------------------------------------- > > > > > > >TN3270E Working Group >INTERNET DRAFT: Expiration Date: November, 1997 > IBM Corp. > > May 1997 > > Definitions of Managed Objects for > TN3270 Using SMIv2 > > > > >Status of this Memo > > This document is an Internet Draft. Internet Drafts are working > documents of the Internet Engineering Task Force (IETF), its Areas, > and its Working Groups. Note that other groups may also distribute > working documents as Internet Drafts. > > Internet Drafts are draft documents valid for a maximum of six > months. Internet Drafts may be updated, replaced, or obsoleted by > other documents at any time. It is not appropriate to use Internet > Drafts as reference material or to cite them other than as a "working > draft" or "work in progress." > > Please check the I-D abstract listing contained in each Internet > Draft directory to learn the current status of this or any Internet > Draft. Distribution of this document is unlimited. > >Abstract > > The purpose of this memo is to define the Management Information Base > (MIB) for configuring and monitoring TN3270 and TN3270E sessions. > The monitoring portion of the MIB is limited to AUGMENTation of > the TCP Connection Table (RFC 2012) with a set of objects collected > from the TCP Layer. It is the intent of this MIB to > fully adhere to all prerequisite MIBs unless explicitly stated. > Deviations will be documented in corresponding conformance statements. > The specification of this MIB will utilize the > Structure of Management Information (SMI) for Version 2 of the > Simple Network Management Protocol Version (refer to RFC1902, > reference [1]). > > > > Table of Contents > > > > >Expires November 1997 [Page 1]~ > > > > > >White TN3270 Management Information Base (TN3270-MIB) 30 May 1997 > > > 1.0 Introduction............................................. 2 > 2.0 The SNMPv2 Network Management Framework.................. 2 > 2.1 Object Definitions....................................... 3 > 3.0 Structure of the MIB..................................... 3 > 3.1 Base TN3270 MIB Definitions.............................. 3 > 3.2 MIB Definitions for AUGMENTing the TCP Connection Table.. 3 > 4.0 Definitions.............................................. 4 > 5.0 Security Considerations.................................. 30 > 6.0 Acknowledgments.......................................... 31 > 7.0 References............................................... 31 > 8.0 Authors' Addresses....................................... 33 > > >1. Introduction > > This document is a product of the TN3270E Working Group. Its purpose > is to define a MIB module for extending the traditional MIBs supported > by a TCP/IP implementation for configuring and monitoring of TN3270 > and TN3270E sessions. > > >2. The SNMPv2 Network Management Framework > > The SNMP Network Management Framework presently consists of three > major components. They are: > > o the SMI, described in RFC 1902 [1], - the mechanisms used for > describing and naming objects for the purpose of management. > > o the MIB-II, STD 17, RFC 1213 [5], - the core set of managed > objects for the Internet suite of protocols. > > o the protocol, RFC 1157 [9] and/or RFC 1905 [7] - the protocol > for accessing managed information. > > Textual conventions are defined in RFC 1903 [6], and conformance > statements are defined in RFC 1904 [8]. > > The Framework permits new objects to be defined for the purpose of > experimentation and evaluation. > > This memo specifies a MIB module that is compliant to the SNMPv2 SMI. > A semantically identical MIB conforming to the SNMPv1 SMI can be > produced through the appropriate translation. > > > > > > > >Expires November 1997 [Page 2]~ > > > > > >White TN3270 Management Information Base (TN3270-MIB) 30 May 1997 > > >2.1. Object Definitions > > Managed objects are accessed via a virtual information store, termed > the Management Information Base or MIB. Objects in the MIB are > defined using the subset of Abstract Syntax Notation One (ASN.1) > defined in the SMI. In particular, each object object type is named > by an OBJECT IDENTIFIER, an administratively assigned name. The > object type together with an object instance serves to uniquely > identify a specific instantiation of the object. For human > convenience, we often use a textual string, termed the descriptor, to > refer to the object type. > > > >3. Structure of the MIB > > The TN3270-MIB is split into the following components: > > o Base TN3270 MIB Definitions > o MIB Definitions for AUGMENTing the TCP Connection Table > > > >3.1. Base TN3270 MIB Definitions > > The collection of MIB Objects defined by the tn3270BasicGroup. This > group of objects provides for TN3270 and TN3270E configuration. > > >3.2. MIB Definitions for AUGMENTing the TCP Connection Table > > The TCP Connection Table is defined by RFC 2012 (Refer to reference > 10, TCP-MIB Definitions). Traditionally, the contents of the TCP > Connection Table has been implementation dependent. Its formal > definition consists of the following objects: > > o tcpConnState (INTEGER) > o tcpConnLocalAddress (IpAddress) > o tcpConnLocalPort (INTEGER) > o tcpConnRemAddress (IpAddress) > o tcpConnRemPort (INTEGER) > > and is indexed by: tcpConnLocalAddress, tcpConnLocalPort, > tcpConnRemAddress and tcpConnRemPort. The tn3270TcpConnTableGroup > contains the objects defined by the tn3270TcpConnTable for AUGMENTing > the tcpConnTable. The objects contained within the > tn3270TcpConnTableGroup can be set by either a TN3270 or TN3270E > Server or if TCP specific by the TCP Stack. > > > >Expires November 1997 [Page 3]~ > > > > > >White TN3270 Management Information Base (TN3270-MIB) 30 May 1997 > > >4. Definitions > > TN3270-MIB DEFINITIONS ::= BEGIN > > IMPORTS > MODULE-IDENTITY, OBJECT-TYPE, > experimental, Integer32, IpAddress, TimeTicks > FROM SNMPv2-SMI > TEXTUAL-CONVENTION, RowStatus, TruthValue, > DisplayString > FROM SNMPv2-TC > MODULE-COMPLIANCE, OBJECT-GROUP > FROM SNMPv2-CONF > InterfaceIndex, InterfaceIndexOrZero > FROM IF-MIB > tcpConnEntry > FROM TCP-MIB > ; > > tn3270MIB MODULE-IDENTITY > LAST-UPDATED "9705300000Z" -- May 30, 1997 > ORGANIZATION "TN3270E Working Group" > CONTACT-INFO > "Kenneth White (kennethw@vnet.ibm.com) > IBM Corp." > DESCRIPTION > "This module defines a portion of the management > information base (MIB) for configuring and monitoring > TN3270 and TN3270E sessions." > -- Need an experimental OID from IANA > ::= { experimental 2001 } > > -- Textual Conventions > > VariableName ::= TEXTUAL-CONVENTION > STATUS current > DESCRIPTION > "A up to 8 octet string name, were a percent sign, '%', > can be used to represent one arbitrary character or an > asterisk , '*', to represent an arbitrary string of > characters. If an asterisk is specified it must appear > as the last character in the octet string." > SYNTAX DisplayString (SIZE(1..8)) > > > -- Top-level structure of the MIB > > tn3270Objects OBJECT IDENTIFIER ::= { tn3270MIB 1 } > > > >Expires November 1997 [Page 4]~ > > > > > >White TN3270 Management Information Base (TN3270-MIB) 30 May 1997 > > > tn3270Notifications OBJECT IDENTIFIER ::= { tn3270MIB 2 } > tn3270Conformance OBJECT IDENTIFIER ::= { tn3270MIB 3 } > > -- MIB Objects > > tn3270Control OBJECT IDENTIFIER ::= { tn3270Objects 1 } > > tn3270Port OBJECT-TYPE > SYNTAX Integer32 (1..65535) > MAX-ACCESS read-write > STATUS current > DESCRIPTION > "Indicates the port for use by the TN3270/TN3270E Server. > Port 23 is the well known Telnet port and if the default." > DEFVAL { 23 } > ::= { tn3270Control 1 } > > tn3270InactivityTimer OBJECT-TYPE > SYNTAX Integer32 (0..99999999) > MAX-ACCESS read-write > STATUS current > DESCRIPTION > "The inactivity time-out specified in seconds. When a > connection has been inactive for the number of seconds > specified by this object it is closed. The default of > 0 means no inactivity time-out." > DEFVAL { 0 } > ::= { tn3270Control 2 } > > tn3270Timemark OBJECT-TYPE > SYNTAX Integer32 > MAX-ACCESS read-write > STATUS current > DESCRIPTION > "The TIMEMARK processing time-out specified in seconds. > A value of 0 disables this function." > DEFVAL { 600 } -- 10 minutes > ::= { tn3270Control 3 } > > tn3270ScanInterval OBJECT-TYPE > SYNTAX Integer32 > MAX-ACCESS read-write > STATUS current > DESCRIPTION > "The scan interval to be used by the Telnet Server. > TIMEMARK processing scans the Telnet sessions every > tn3270ScanInterval period (specified in seconds) for > sessions that have been idle for more than the value > > > >Expires November 1997 [Page 5]~ > > > > > >White TN3270 Management Information Base (TN3270-MIB) 30 May 1997 > > > if tn3270Timemark. Sessions that are idle more than > the value of tn3270Timemark are checked by sending a > Telnet IAC Timemark command. > > A value of 0 implies that TIMEMARK processing is > not in effect." > DEFVAL { 120 } -- 2 minutes > ::= { tn3270Control 4 } > > tn3270BinaryLineMode OBJECT-TYPE > SYNTAX TruthValue > MAX-ACCESS read-write > STATUS current > DESCRIPTION > "A value of true(1) for this object allows incoming > Telnet line-mode sessions to operate in binary mode." > DEFVAL { false } > ::= { tn3270Control 5 } > > tn3270DisableSga OBJECT-TYPE > SYNTAX TruthValue > MAX-ACCESS read-write > STATUS current > DESCRIPTION > "A value of true(1) for this object suppresses the > transmission of GO AHEADs by Telnet. This must be > negotiated by both client and server. Selection of this > option reduces the overhead for a full duplex terminal > and a full duplex connection." > DEFVAL { false } > ::= { tn3270Control 6 } > > tn3270AdminStatus OBJECT-TYPE > SYNTAX INTEGER { > up(1), > down(2) > } > MAX-ACCESS read-write > STATUS current > DESCRIPTION > "The desired state of the Telnet Server." > ::= { tn3270Control 7 } > > tn3270OperStatus OBJECT-TYPE > SYNTAX INTEGER { > up(1), > down(2) > } > > > >Expires November 1997 [Page 6]~ > > > > > >White TN3270 Management Information Base (TN3270-MIB) 30 May 1997 > > > MAX-ACCESS read-only > STATUS current > DESCRIPTION > "The current operational state of the Telnet Server." > ::= { tn3270Control 8 } > > tn3270DefaultApplName OBJECT-TYPE > SYNTAX DisplayString (SIZE(0..8)) > MAX-ACCESS read-write > STATUS current > DESCRIPTION > "The default Application to use. Typically this is an > initial application which is either a network solictor or > front-end menu system. > > A null length octet string implies no default is in effect." > DEFVAL { ''H } > ::= { tn3270Control 9 } > > tn3270DefaultApplIpAddress OBJECT-TYPE > SYNTAX IpAddress > MAX-ACCESS read-write > STATUS current > DESCRIPTION > "The default Application's IP Address. A value of 0 implies > no IP Address has been set." > DEFVAL { 0 } > ::= { tn3270Control 10 } > > tn3270DefaultApplIpGroupName OBJECT-TYPE > SYNTAX DisplayString (SIZE(0..8)) > MAX-ACCESS read-write > STATUS current > DESCRIPTION > "The IP Group name to be used with the default Application. > A null octet string implies that IP Group name has not > been specified." > DEFVAL { ''H } > ::= { tn3270Control 11 } > > tn3270DefaultApplIfIndex OBJECT-TYPE > SYNTAX InterfaceIndexOrZero > MAX-ACCESS read-write > STATUS current > DESCRIPTION > "The ifEntry to be used by the default Application. > A value of 0 implies that this object has not been set." > DEFVAL { 0 } > > > >Expires November 1997 [Page 7]~ > > > > > >White TN3270 Management Information Base (TN3270-MIB) 30 May 1997 > > > ::= { tn3270Control 12 } > > tn3270TelnetAppl OBJECT-TYPE > SYNTAX DisplayString (SIZE(0..8)) > MAX-ACCESS read-write > STATUS current > DESCRIPTION > "The application to which to connect when a Telnet Client > establishes a 3270 connection." > DEFVAL { ''H } > ::= { tn3270Control 13 } > > tn3270LmApplName OBJECT-TYPE > SYNTAX DisplayString (SIZE(0..8)) > MAX-ACCESS read-write > STATUS current > DESCRIPTION > "The Application to use when a Telnet Client establishes > a line-mode connection. > > A null length octet string implies not set." > DEFVAL { ''H } > ::= { tn3270Control 14 } > > tn3270LmApplIpAddress OBJECT-TYPE > SYNTAX IpAddress > MAX-ACCESS read-write > STATUS current > DESCRIPTION > "The line-mode Application's IP Address. A value of 0 implies > no IP Address has been set." > DEFVAL { 0 } > ::= { tn3270Control 15 } > > tn3270LmApplIpGroupName OBJECT-TYPE > SYNTAX DisplayString (SIZE(0..8)) > MAX-ACCESS read-write > STATUS current > DESCRIPTION > "The IP Group name to be used with the line-mode Application. > A null octet string implies that IP Group name has not > been specified." > DEFVAL { ''H } > ::= { tn3270Control 16 } > > tn3270LmApplIfIndex OBJECT-TYPE > SYNTAX InterfaceIndexOrZero > MAX-ACCESS read-write > > > >Expires November 1997 [Page 8]~ > > > > > >White TN3270 Management Information Base (TN3270-MIB) 30 May 1997 > > > STATUS current > DESCRIPTION > "The ifEntry to be used by the line-mode Application. > A value of 0 implies that this object has not been set." > DEFVAL { 0 } > ::= { tn3270Control 17 } > > tn3270UsstcpTableName OBJECT-TYPE > SYNTAX DisplayString (SIZE(0..8)) > MAX-ACCESS read-write > STATUS current > DESCRIPTION > "The name of USS definition table for message 10. This > applies to 3270 devices only. It allows the mapping of > a customized USS message 1- screen to either a remote IP > address or a network interface using transparent-mode > operation to use as a Telnet logon screen. > > A null length octet string implies not set." > DEFVAL { ''H } > ::= { tn3270Control 18 } > > tn3270UsstcpIpAddress OBJECT-TYPE > SYNTAX IpAddress > MAX-ACCESS read-write > STATUS current > DESCRIPTION > "The USSTCP function's IP Address. A value of 0 implies > no IP Address has been set." > DEFVAL { 0 } > ::= { tn3270Control 19 } > > tn3270UsstcpIpGroupName OBJECT-TYPE > SYNTAX DisplayString (SIZE(0..8)) > MAX-ACCESS read-write > STATUS current > DESCRIPTION > "The IP Group name to be used with USSTCP processing. > A null octet string implies that IP Group name has not > been specified." > DEFVAL { ''H } > ::= { tn3270Control 20 } > > tn3270UsstcpIfIndex OBJECT-TYPE > SYNTAX InterfaceIndexOrZero > MAX-ACCESS read-write > STATUS current > DESCRIPTION > > > >Expires November 1997 [Page 9]~ > > > > > >White TN3270 Management Information Base (TN3270-MIB) 30 May 1997 > > > "The ifEntry to be used by USSTCP processing. > A value of 0 implies that this object has not been set." > DEFVAL { 0 } > ::= { tn3270Control 21 } > > tn3270SessionTermState OBJECT-TYPE > SYNTAX INTEGER { > terminate(1), > luSessionPend(2), > queueSession(3) > } > MAX-ACCESS read-write > STATUS current > DESCRIPTION > "The current state for determining what happens when > Telnet connection terminates: > > terminate(1) => Terminate connection. > luSessionPend(2) => Allows the client's session to revert > to their Default Application upon > termination of their Telnet connection. > queueSession(3) => ????" > DEFVAL { terminate } > ::= { tn3270Control 22 } > > tn3270Msg07Enabled OBJECT-TYPE > SYNTAX TruthValue > MAX-ACCESS read-write > STATUS current > DESCRIPTION > "The value of this object determines what happens when a > Telnet connection is trying to establish the connection > but goes down due to an error. Setting this object to > true(1) causes a USSMSG 7 (or other error type USSMSG) to > be displayed. The default is, false(2), to break the connection > without any indication of what the error was." > DEFVAL { false } > ::= { tn3270Control 23 } > > tn3270OldSolicitorEnabled OBJECT-TYPE > SYNTAX TruthValue > MAX-ACCESS read-write > STATUS current > DESCRIPTION > "The value of this object determines where the cursor is placed > on the Telnet solicitor screen. Setting this object to true(1) > causes the cursor to be placed on the userid entry of the > solicitor screen for the first display only. The default > > > >Expires November 1997 [Page 10]~ > > > > > >White TN3270 Management Information Base (TN3270-MIB) 30 May 1997 > > > (false(2) is to put the cursor on the application entry of the > solicitor screen." > DEFVAL { false } > ::= { tn3270Control 24 } > > > -- The ALLOWAPPL Table definitions > > tn3270AllowApplTable OBJECT-TYPE > SYNTAX SEQUENCE OF Tn3270AllowApplEntry > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "The Applications that the Telnet Server can access." > ::= { tn3270Objects 2 } > > tn3270AllowApplEntry OBJECT-TYPE > SYNTAX Tn3270AllowApplEntry > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "Information about a single Application that the Telnet > Server can access. > > An Application can be qualified with a list of LUs by > adding entries to the tn3270AllowApplLuTable. The > tn3270AllowApplLuTable is indexed by tn3270AllowApplName > and tn3270AllowApplLuName." > INDEX { tn3270AllowApplName } > ::= { tn3270AllowApplTable 1 } > > Tn3270AllowApplEntry ::= SEQUENCE { > tn3270AllowApplName VariableName, > tn3270AllowApplDisconnect TruthValue, > tn3270AllowApplRowStatus RowStatus } > > tn3270AllowApplName OBJECT-TYPE > SYNTAX VariableName > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "The name of the application that can be accessed." > ::= { tn3270AllowApplEntry 1 } > > tn3270AllowApplDisconnect OBJECT-TYPE > SYNTAX TruthValue > MAX-ACCESS read-create > STATUS current > > > >Expires November 1997 [Page 11]~ > > > > > >White TN3270 Management Information Base (TN3270-MIB) 30 May 1997 > > > DESCRIPTION > "When set to true this allows the application to be > notified to disconnect rather than log off a user when > the session is dropped." > DEFVAL { false } > ::= { tn3270AllowApplEntry 2 } > > tn3270AllowApplRowStatus OBJECT-TYPE > SYNTAX RowStatus > MAX-ACCESS read-create > STATUS current > DESCRIPTION > "This object allows entries to be created and deleted in the > tn3270AllowApplTable. > > When an entry in the tn3270AllowApplTable is deleted > deleted (by setting this object to destroy(6)), this has > the side-effect of removing all entries from the > tn3270AllowApplLuTable that are associated with the > entry being deleted." > REFERENCE > "RFC 1903, 'Textual Conventions for version 2 of the Simple > Network Management Protocol (SNMPv2).'" > ::= { tn3270AllowApplEntry 3 } > > tn3270AllowApplLuTable OBJECT-TYPE > SYNTAX SEQUENCE OF Tn3270AllowApplLuEntry > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "The LUs associated with a tn3270AllowApplEntry. > Use of this table is optional. The preferred method of > associating LUs to Applications is via the > tn3270LuMapTable." > ::= { tn3270Objects 3 } > > tn3270AllowApplLuEntry OBJECT-TYPE > SYNTAX Tn3270AllowApplLuEntry > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "Definition of a single LU associated with a > tn3270AllowApplEntry." > INDEX { tn3270AllowApplName, tn3270AllowApplLuName } > ::= { tn3270AllowApplLuTable 1 } > > Tn3270AllowApplLuEntry ::= SEQUENCE { > tn3270AllowApplLuName DisplayString, > > > >Expires November 1997 [Page 12]~ > > > > > >White TN3270 Management Information Base (TN3270-MIB) 30 May 1997 > > > tn3270AllowApplLuRowStatus RowStatus } > > tn3270AllowApplLuName OBJECT-TYPE > SYNTAX DisplayString (SIZE(1..8)) > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "The name of a LU associated with an Application." > ::= { tn3270AllowApplLuEntry 1 } > > tn3270AllowApplLuRowStatus OBJECT-TYPE > SYNTAX RowStatus > MAX-ACCESS read-create > STATUS current > DESCRIPTION > "This object allows entries to be created and deleted in the > tn3270AllowApplLuTable. > > When an entry in the tn3270AllowApplTable is deleted > deleted (by setting this object to destroy(6)) it has no > effect on the associating tn3270AllowApplEntry." > REFERENCE > "RFC 1903, 'Textual Conventions for version 2 of the Simple > Network Management Protocol (SNMPv2).'" > ::= { tn3270AllowApplLuEntry 2 } > > -- The RESTRICTAPPL Table definitions > > tn3270RestrictApplTable OBJECT-TYPE > SYNTAX SEQUENCE OF Tn3270RestrictApplEntry > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "The Applications that the Telnet Server provides > restricted access." > ::= { tn3270Objects 4 } > > tn3270RestrictApplEntry OBJECT-TYPE > SYNTAX Tn3270RestrictApplEntry > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "Definition of a single restricted Application that the Telnet > Server can access. > > An Application is qualified with a list of users that are > allowed access to the application via the > tn3270RestrictApplUserTable." > > > >Expires November 1997 [Page 13]~ > > > > > >White TN3270 Management Information Base (TN3270-MIB) 30 May 1997 > > > INDEX { tn3270RestrictApplName } > ::= { tn3270RestrictApplTable 1 } > > Tn3270RestrictApplEntry ::= SEQUENCE { > tn3270RestrictApplName VariableName, > tn3270RestrictApplDisconnect TruthValue, > tn3270RestrictApplRowStatus RowStatus } > > tn3270RestrictApplName OBJECT-TYPE > SYNTAX VariableName > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "The name of the application that can be accessed." > ::= { tn3270RestrictApplEntry 1 } > > tn3270RestrictApplDisconnect OBJECT-TYPE > SYNTAX TruthValue > MAX-ACCESS read-create > STATUS current > DESCRIPTION > "When set to true this allows the application to be > notified to disconnect rather than log off a user when > the session is dropped." > DEFVAL { false } > ::= { tn3270RestrictApplEntry 2 } > > tn3270RestrictApplRowStatus OBJECT-TYPE > SYNTAX RowStatus > MAX-ACCESS read-create > STATUS current > DESCRIPTION > "This object allows entries to be created and deleted in the > tn3270RestrictApplTable. > > When an entry in the tn3270RestrictApplTable is deleted > deleted (by setting this object to destroy(6)), this has > the side-effect of removing all entries from the > tn3270RestrictApplUserTable that are associated with the > entry being deleted." > REFERENCE > "RFC 1903, 'Textual Conventions for version 2 of the Simple > Network Management Protocol (SNMPv2).'" > ::= { tn3270RestrictApplEntry 3 } > > tn3270RestrictApplUserTable OBJECT-TYPE > SYNTAX SEQUENCE OF Tn3270RestrictApplUserEntry > MAX-ACCESS not-accessible > > > >Expires November 1997 [Page 14]~ > > > > > >White TN3270 Management Information Base (TN3270-MIB) 30 May 1997 > > > STATUS current > DESCRIPTION > "The Users associated with a tn3270RestrictApplEntry." > ::= { tn3270Objects 5 } > > tn3270RestrictApplUserEntry OBJECT-TYPE > SYNTAX Tn3270RestrictApplUserEntry > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "Definition of a single User associated with a > tn3270RestrictApplEntry." > INDEX { tn3270RestrictApplName, tn3270RestrictApplUserName } > ::= { tn3270RestrictApplUserTable 1 } > > Tn3270RestrictApplUserEntry ::= SEQUENCE { > tn3270RestrictApplUserName DisplayString, > tn3270RestrictApplUserRowStatus RowStatus } > > tn3270RestrictApplUserName OBJECT-TYPE > SYNTAX DisplayString (SIZE(1..8)) > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "The name of a User allowed access with the corresponding > Application." > ::= { tn3270RestrictApplUserEntry 1 } > > tn3270RestrictApplUserRowStatus OBJECT-TYPE > SYNTAX RowStatus > MAX-ACCESS read-create > STATUS current > DESCRIPTION > "This object allows entries to be created and deleted in the > tn3270RestrictApplUserTable. > > When an entry in the tn3270RestrictApplTable is deleted > deleted (by setting this object to destroy(6)) it has no > effect on the associating tn3270RestrictApplEntry. > However, corresponding tn3270RestrictApplULuTable entries > are deleted." > REFERENCE > "RFC 1903, 'Textual Conventions for version 2 of the Simple > Network Management Protocol (SNMPv2).'" > ::= { tn3270RestrictApplUserEntry 2 } > > tn3270RestrictApplULuTable OBJECT-TYPE > SYNTAX SEQUENCE OF Tn3270RestrictApplULuEntry > > > >Expires November 1997 [Page 15]~ > > > > > >White TN3270 Management Information Base (TN3270-MIB) 30 May 1997 > > > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "The LUs associated with a Restricted Application User. > Use of this table is optional. The preferred method of > associating LUs with Applications is via the > tn3270LuMapTable." > ::= { tn3270Objects 6 } > > tn3270RestrictApplULuEntry OBJECT-TYPE > SYNTAX Tn3270RestrictApplULuEntry > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "Definition of a single LU associated with a > tn3270RestrictApplLuEntry." > INDEX { tn3270RestrictApplName, tn3270RestrictApplUserName, > tn3270RestrictApplULuName } > ::= { tn3270RestrictApplULuTable 1 } > > Tn3270RestrictApplULuEntry ::= SEQUENCE { > tn3270RestrictApplULuName DisplayString, > tn3270RestrictApplULuRowStatus RowStatus } > > tn3270RestrictApplULuName OBJECT-TYPE > SYNTAX DisplayString (SIZE(1..8)) > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "The name of an LU." > ::= { tn3270RestrictApplULuEntry 1 } > > tn3270RestrictApplULuRowStatus OBJECT-TYPE > SYNTAX RowStatus > MAX-ACCESS read-create > STATUS current > DESCRIPTION > "This object allows entries to be created and deleted in the > tn3270RestrictApplULuTable. > > When an entry in the tn3270RestrictApplULuTable is deleted > deleted (by setting this object to destroy(6)) it has no > effect on the associating tn3270RestrictApplUserEntry." > REFERENCE > "RFC 1903, 'Textual Conventions for version 2 of the Simple > Network Management Protocol (SNMPv2).'" > ::= { tn3270RestrictApplULuEntry 2 } > > > > >Expires November 1997 [Page 16]~ > > > > > >White TN3270 Management Information Base (TN3270-MIB) 30 May 1997 > > > tn3270IpGroupTable OBJECT-TYPE > SYNTAX SEQUENCE OF Tn3270IpGroupEntry > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "This table defines IP Address grouping for use by the > Telnet Server." > ::= { tn3270Objects 7 } > > tn3270IpGroupEntry OBJECT-TYPE > SYNTAX Tn3270IpGroupEntry > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "Definition of a single IP Address entry. All entries with > the same 1st index, tn3270IpGroupName are considered to > be in the same IP Group." > INDEX { tn3270IpGroupName, tn3270IpGroupIpAddress } > ::= { tn3270IpGroupTable 1 } > > Tn3270IpGroupEntry ::= SEQUENCE { > tn3270IpGroupName DisplayString, > tn3270IpGroupIpAddress IpAddress, > tn3270IpGroupSubnetMask IpAddress, > tn3270IpGroupIpSubnet IpAddress, > tn3270IpGroupRowStatus RowStatus } > > tn3270IpGroupName OBJECT-TYPE > SYNTAX DisplayString (SIZE(1..8)) > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "The name of a IP Group." > ::= { tn3270IpGroupEntry 1 } > > tn3270IpGroupIpAddress OBJECT-TYPE > SYNTAX IpAddress > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "The IP Address of a member of a IP Group." > ::= { tn3270IpGroupEntry 2 } > > tn3270IpGroupSubnetMask OBJECT-TYPE > SYNTAX IpAddress > MAX-ACCESS read-create > STATUS current > DESCRIPTION > > > >Expires November 1997 [Page 17]~ > > > > > >White TN3270 Management Information Base (TN3270-MIB) 30 May 1997 > > > "The corresponding subnet mask associated with > tn3270IpGroupIpSubnet." > ::= { tn3270IpGroupEntry 3 } > > tn3270IpGroupIpSubnet OBJECT-TYPE > SYNTAX IpAddress > MAX-ACCESS read-create > STATUS current > DESCRIPTION > "The IP Subnet to be used with the objects > tn3270IpGroupIpAddress and tn3270IpGroupSubnetMask." > ::= { tn3270IpGroupEntry 4 } > > tn3270IpGroupRowStatus OBJECT-TYPE > SYNTAX RowStatus > MAX-ACCESS read-create > STATUS current > DESCRIPTION > "This object allows entries to be created and deleted in the > tn3270IpGroupTable. > > An entry in this table is deleted by setting this object > to destroy(6)." > REFERENCE > "RFC 1903, 'Textual Conventions for version 2 of the Simple > Network Management Protocol (SNMPv2).'" > ::= { tn3270IpGroupEntry 5 } > > tn3270LuGroupTable OBJECT-TYPE > SYNTAX SEQUENCE OF Tn3270LuGroupEntry > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "This table defines LU groups for use by the > Telnet Server." > ::= { tn3270Objects 8 } > > tn3270LuGroupEntry OBJECT-TYPE > SYNTAX Tn3270LuGroupEntry > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "Definition of a single LU Group member. All entries with > the same 1st index, tn3270LuGroupName are considered to > be in the same LU Group. > > The first entry in this table is used for defining the > default LU Group. By convention tn3270LuGroupName should > > > >Expires November 1997 [Page 18]~ > > > > > >White TN3270 Management Information Base (TN3270-MIB) 30 May 1997 > > > be set to 8 blanks to represent this entry." > INDEX { tn3270LuGroupName, tn3270LuGroupLuName } > ::= { tn3270LuGroupTable 1 } > > Tn3270LuGroupEntry ::= SEQUENCE { > tn3270LuGroupName DisplayString, > tn3270LuGroupLuName DisplayString, > tn3270LuGroupRowStatus RowStatus } > > tn3270LuGroupName OBJECT-TYPE > SYNTAX DisplayString (SIZE(1..8)) > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "The name of a LU Group." > ::= { tn3270LuGroupEntry 1 } > > tn3270LuGroupLuName OBJECT-TYPE > SYNTAX DisplayString (SIZE(1..8)) > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "The LU Name of a member of a Lu Group." > ::= { tn3270LuGroupEntry 2 } > > tn3270LuGroupRowStatus OBJECT-TYPE > SYNTAX RowStatus > MAX-ACCESS read-create > STATUS current > DESCRIPTION > "This object allows entries to be created and deleted in the > tn3270LuGroupTable. > > An entry in this table is deleted by setting this object > to destroy(6)." > REFERENCE > "RFC 1903, 'Textual Conventions for version 2 of the Simple > Network Management Protocol (SNMPv2).'" > ::= { tn3270LuGroupEntry 3 } > > tn3270PrtGroupTable OBJECT-TYPE > SYNTAX SEQUENCE OF Tn3270PrtGroupEntry > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "This table defines Printer groups for use by the > Telnet Server." > ::= { tn3270Objects 9 } > > > >Expires November 1997 [Page 19]~ > > > > > >White TN3270 Management Information Base (TN3270-MIB) 30 May 1997 > > > tn3270PrtGroupEntry OBJECT-TYPE > SYNTAX Tn3270PrtGroupEntry > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "Definition of a single Printer Group member. All entries with > the same 1st index, tn3270PrtGroupName are considered to > be in the same Printer Group." > INDEX { tn3270PrtGroupName, tn3270PrtGroupPrtName } > ::= { tn3270PrtGroupTable 1 } > > Tn3270PrtGroupEntry ::= SEQUENCE { > tn3270PrtGroupName DisplayString, > tn3270PrtGroupPrtName DisplayString, > tn3270PrtGroupRowStatus RowStatus } > > tn3270PrtGroupName OBJECT-TYPE > SYNTAX DisplayString (SIZE(1..8)) > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "The name of a Printer Group." > ::= { tn3270PrtGroupEntry 1 } > > tn3270PrtGroupPrtName OBJECT-TYPE > SYNTAX DisplayString (SIZE(1..8)) > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "The Printer Name of a member of a Printer Group." > ::= { tn3270PrtGroupEntry 2 } > > tn3270PrtGroupRowStatus OBJECT-TYPE > SYNTAX RowStatus > MAX-ACCESS read-create > STATUS current > DESCRIPTION > "This object allows entries to be created and deleted in the > tn3270PrtGroupTable. > > An entry in this table is deleted by setting this object > to destroy(6)." > REFERENCE > "RFC 1903, 'Textual Conventions for version 2 of the Simple > Network Management Protocol (SNMPv2).'" > ::= { tn3270PrtGroupEntry 3 } > > tn3270LuMapTable OBJECT-TYPE > > > >Expires November 1997 [Page 20]~ > > > > > >White TN3270 Management Information Base (TN3270-MIB) 30 May 1997 > > > SYNTAX SEQUENCE OF Tn3270LuMapEntry > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "This table defines LU to IP mappings. An IP Address or > IP Address group can only be assigned to a LU or LU > Group once." > ::= { tn3270Objects 10 } > > tn3270LuMapEntry OBJECT-TYPE > SYNTAX Tn3270LuMapEntry > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "Definition of the mapping of a single IP Address or IP > Address Group to either a LU or LU Group." > INDEX { tn3270LuMapLuName } > ::= { tn3270LuMapTable 1 } > > Tn3270LuMapEntry ::= SEQUENCE { > tn3270LuMapLuName DisplayString, > tn3270LuMapIpAddr IpAddress, > tn3270LuMapIpGroupName DisplayString, > tn3270LuMapRowStatus RowStatus } > > tn3270LuMapLuName OBJECT-TYPE > SYNTAX DisplayString (SIZE(1..8)) > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "The name of either a LU or LU Group Name." > ::= { tn3270LuMapEntry 1 } > > tn3270LuMapIpAddr OBJECT-TYPE > SYNTAX IpAddress > MAX-ACCESS read-create > STATUS current > DESCRIPTION > "The IP address to map to a LU. If this object is non-zero > then tn3270LuMapLuName MUST be a single LU Name and > tn3270LuMapIpGroupName MUST be a null octet string." > DEFVAL { 0 } > ::= { tn3270LuMapEntry 2 } > > tn3270LuMapIpGroupName OBJECT-TYPE > SYNTAX DisplayString (SIZE(0..8)) > MAX-ACCESS read-create > STATUS current > > > >Expires November 1997 [Page 21]~ > > > > > >White TN3270 Management Information Base (TN3270-MIB) 30 May 1997 > > > DESCRIPTION > "The IP addresses to map to a LU Group. If this object is > not a null octet string then tn3270LuMapLuName MUST be a > LU Group name and tn3270LuMapIpAddr MUST be zero." > DEFVAL { ''H } > ::= { tn3270LuMapEntry 3 } > > tn3270LuMapRowStatus OBJECT-TYPE > SYNTAX RowStatus > MAX-ACCESS read-create > STATUS current > DESCRIPTION > "This object allows entries to be created and deleted in the > tn3270LuMapTable. > > An entry in this table is deleted by setting this object > to destroy(6)." > REFERENCE > "RFC 1903, 'Textual Conventions for version 2 of the Simple > Network Management Protocol (SNMPv2).'" > ::= { tn3270LuMapEntry 4 } > > tn3270PrtMapTable OBJECT-TYPE > SYNTAX SEQUENCE OF Tn3270PrtMapEntry > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "This table defines Printer to IP mappings. An IP Address or > IP Address group can only be assigned to a single Printer or > Printer Group once." > ::= { tn3270Objects 11 } > > tn3270PrtMapEntry OBJECT-TYPE > SYNTAX Tn3270PrtMapEntry > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "Definition of the mapping of a single IP Address or IP > Address Group to either a Printer or Printer Group." > INDEX { tn3270PrtMapPrtName } > ::= { tn3270PrtMapTable 1 } > > Tn3270PrtMapEntry ::= SEQUENCE { > tn3270PrtMapPrtName DisplayString, > tn3270PrtMapIpAddr IpAddress, > tn3270PrtMapIpGroupName DisplayString, > tn3270PrtMapRowStatus RowStatus } > > > > >Expires November 1997 [Page 22]~ > > > > > >White TN3270 Management Information Base (TN3270-MIB) 30 May 1997 > > > tn3270PrtMapPrtName OBJECT-TYPE > SYNTAX DisplayString (SIZE(1..8)) > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "The name of either a Printer or Printer Group Name." > ::= { tn3270PrtMapEntry 1 } > > tn3270PrtMapIpAddr OBJECT-TYPE > SYNTAX IpAddress > MAX-ACCESS read-create > STATUS current > DESCRIPTION > "The IP address to map to a Printer. If this object is non- > zero > then tn3270PrtMapPrtName MUST be a single Printer and > tn3270PrtMapIpGroupName MUST be a null octet string." > DEFVAL { 0 } > ::= { tn3270PrtMapEntry 2 } > > tn3270PrtMapIpGroupName OBJECT-TYPE > SYNTAX DisplayString (SIZE(0..8)) > MAX-ACCESS read-create > STATUS current > DESCRIPTION > "The IP addresses to map to a Printer Group. If this object is > not a null octet string then tn3270PrtMapPrtName MUST be a > Printer Group name and tn3270PrtMapIpAddr MUST be zero." > DEFVAL { ''H } > ::= { tn3270PrtMapEntry 3 } > > tn3270PrtMapRowStatus OBJECT-TYPE > SYNTAX RowStatus > MAX-ACCESS read-create > STATUS current > DESCRIPTION > "This object allows entries to be created and deleted in the > tn3270PrtMapTable. > > An entry in this table is deleted by setting this object > to destroy(6)." > REFERENCE > "RFC 1903, 'Textual Conventions for version 2 of the Simple > Network Management Protocol (SNMPv2).'" > ::= { tn3270PrtMapEntry 4 } > > tn3270LogmodeTable OBJECT-TYPE > SYNTAX SEQUENCE OF Tn3270LogmodeEntry > > > >Expires November 1997 [Page 23]~ > > > > > >White TN3270 Management Information Base (TN3270-MIB) 30 May 1997 > > > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "This table defines the logmode to be used for a particular > interface entry." > ::= { tn3270Objects 12 } > > tn3270LogmodeEntry OBJECT-TYPE > SYNTAX Tn3270LogmodeEntry > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "Definition of the logmode setting for a single interface > entry." > INDEX { tn3270LogmodeIfIndex } > ::= { tn3270LogmodeTable 1 } > > Tn3270LogmodeEntry ::= SEQUENCE { > tn3270LogmodeIfIndex InterfaceIndex, > tn3270LogmodeName DisplayString, > tn3270LogmodeRowStatus RowStatus } > > tn3270LogmodeIfIndex OBJECT-TYPE > SYNTAX InterfaceIndex > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "The ifIndex of a interface entry to associate a logmode > with." > ::= { tn3270LogmodeEntry 1 } > > tn3270LogmodeName OBJECT-TYPE > SYNTAX DisplayString (SIZE(0..8)) > MAX-ACCESS read-create > STATUS current > DESCRIPTION > "The Logmode name to use for this particular interface. A > value of a null octet string implies that the default > logmode, which is dependent on the interface's type, should > be used." > DEFVAL { ''H } > ::= { tn3270LogmodeEntry 2 } > > tn3270LogmodeRowStatus OBJECT-TYPE > SYNTAX RowStatus > MAX-ACCESS read-create > STATUS current > DESCRIPTION > > > >Expires November 1997 [Page 24]~ > > > > > >White TN3270 Management Information Base (TN3270-MIB) 30 May 1997 > > > "This object allows entries to be created and deleted in the > tn3270LogmodeTable. > > An entry in this table is deleted by setting this object > to destroy(6)." > REFERENCE > "RFC 1903, 'Textual Conventions for version 2 of the Simple > Network Management Protocol (SNMPv2).'" > ::= { tn3270LogmodeEntry 3 } > > -- Define the set of objects to augment the Tcp Connection Table with. > > tn3270TcpConnTable OBJECT-TYPE > SYNTAX SEQUENCE OF Tn3270TcpConnEntry > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "Extends tcpConnTable to support TN3270 and TN3270E > performance monitoring." > ::= { tn3270Objects 13 } > > tn3270TcpConnEntry OBJECT-TYPE > SYNTAX Tn3270TcpConnEntry > MAX-ACCESS not-accessible > STATUS current > DESCRIPTION > "Descibes a particular tcp connection entry." > AUGMENTS { tcpConnEntry } > ::= { tn3270TcpConnTable 1 } > > Tn3270TcpConnEntry ::= > SEQUENCE > { > tn3270TcpConnLastActivity TimeTicks, > tn3270TcpConnBytesIn Integer32, > tn3270TcpConnBytesOut Integer32, > tn3270TcpConnReXmt Integer32, > tn3270TcpConnReXmtCount Integer32, > tn3270TcpConnRoundTripTime Integer32, > tn3270TcpConnRoundTripVariance Integer32, > tn3270TcpConnTargetAppl DisplayString, > tn3270TcpConnLuName DisplayString, > tn3270TcpConnClientUserId DisplayString, > tn3270TcpConnLogMode DisplayString, > tn3270TcpConnProto OCTET STRING > } > > tn3270TcpConnLastActivity OBJECT-TYPE > > > >Expires November 1997 [Page 25]~ > > > > > >White TN3270 Management Information Base (TN3270-MIB) 30 May 1997 > > > SYNTAX TimeTicks > MAX-ACCESS read-only > STATUS current > DESCRIPTION > "The number of 100ths of seconds since this entry > was last used." > DEFVAL { 0 } > ::= { tn3270TcpConnEntry 1 } > > tn3270TcpConnBytesIn OBJECT-TYPE > SYNTAX Integer32 > MAX-ACCESS read-only > STATUS current > DESCRIPTION > "The number of bytes received from IP for this > connection." > DEFVAL { 0 } > ::= { tn3270TcpConnEntry 2 } > > tn3270TcpConnBytesOut OBJECT-TYPE > SYNTAX Integer32 > MAX-ACCESS read-only > STATUS current > DESCRIPTION > "The number of bytes sent to IP for this connection." > DEFVAL { 0 } > ::= { tn3270TcpConnEntry 3 } > > tn3270TcpConnReXmt OBJECT-TYPE > SYNTAX Integer32 > MAX-ACCESS read-only > STATUS current > DESCRIPTION > "Number of retransmissions" > DEFVAL { 0 } > ::= { tn3270TcpConnEntry 4 } > > tn3270TcpConnReXmtCount OBJECT-TYPE > SYNTAX Integer32 > MAX-ACCESS read-only > STATUS current > DESCRIPTION > "Current retransmission count" > DEFVAL { 0 } > ::= { tn3270TcpConnEntry 5 } > > tn3270TcpConnRoundTripTime OBJECT-TYPE > SYNTAX Integer32 > > > >Expires November 1997 [Page 26]~ > > > > > >White TN3270 Management Information Base (TN3270-MIB) 30 May 1997 > > > MAX-ACCESS read-only > STATUS current > DESCRIPTION > "The amount of time that has elapsed, measured in > milliseconds, from when the last TCP segment was > transmitted by the TCP Stack until the ACK was > received." > DEFVAL { 0 } > ::= { tn3270TcpConnEntry 6 } > > tn3270TcpConnRoundTripVariance OBJECT-TYPE > SYNTAX Integer32 > MAX-ACCESS read-only > STATUS current > DESCRIPTION > "Round trip time variance." > DEFVAL { 0 } > ::= { tn3270TcpConnEntry 7 } > > tn3270TcpConnTargetAppl OBJECT-TYPE > SYNTAX DisplayString (SIZE(0..8)) > MAX-ACCESS read-only > STATUS current > DESCRIPTION > "When the corresponding TCP connection is for a > 3172 Telnet session then this object contains the > Target VTAM Application name." > ::= { tn3270TcpConnEntry 8 } > > tn3270TcpConnLuName OBJECT-TYPE > SYNTAX DisplayString (SIZE(0..8)) > MAX-ACCESS read-only > STATUS current > DESCRIPTION > "When the corresponding TCP connection is for a > 3172 Telnet session then this object contains the > VTAM LU name." > ::= { tn3270TcpConnEntry 9 } > > tn3270TcpConnClientUserId OBJECT-TYPE > SYNTAX DisplayString (SIZE(0..8)) > MAX-ACCESS read-only > STATUS current > DESCRIPTION > "When the corresponding TCP connection is for a > 3172 Telnet session then this object contains the > Client's userid." > ::= { tn3270TcpConnEntry 10 } > > > >Expires November 1997 [Page 27]~ > > > > > >White TN3270 Management Information Base (TN3270-MIB) 30 May 1997 > > > tn3270TcpConnLogMode OBJECT-TYPE > SYNTAX DisplayString (SIZE(0..8)) > MAX-ACCESS read-only > STATUS current > DESCRIPTION > "When the corresponding TCP connection is for a > 3172 Telnet session then this object contains the > LOG Mode." > ::= { tn3270TcpConnEntry 11 } > > tn3270TcpConnProto OBJECT-TYPE > SYNTAX OCTET STRING (SIZE(4)) > MAX-ACCESS read-only > STATUS current > DESCRIPTION > "This flag will indicates the following Telnet modes: > -bit(1 - 28) = > -bit(29) = TN3270EE mode > -bit(30) = TN3270 mode > -bit(31) = TN3270E mode > -bit(32) = line mode" > ::= { tn3270TcpConnEntry 12 } > > > -- Conformance Definitions > > tn3270Groups OBJECT IDENTIFIER ::= { tn3270Conformance 1 } > tn3270Compliances OBJECT IDENTIFIER ::= { tn3270Conformance 2 } > > -- compliance statements tn3270Compliance MODULE-COMPLIANCE > STATUS current > DESCRIPTION > "The compliance statement for agents that support the TN3270 > MIB." > MODULE -- this module > MANDATORY-GROUPS { tn3270BasicGroup, > tn3270TcpConnTableGroup > } > ::= { tn3270Compliances 1 } > > -- units of conformance tn3270BasicGroup OBJECT-GROUP > OBJECTS { > tn3270Port, > tn3270InactivityTimer, > tn3270Timemark, > tn3270ScanInterval, > tn3270BinaryLineMode, > tn3270DisableSga, > > > >Expires November 1997 [Page 28]~ > > > > > >White TN3270 Management Information Base (TN3270-MIB) 30 May 1997 > > > tn3270AdminStatus, > tn3270OperStatus, > tn3270DefaultApplName, > tn3270DefaultApplIpAddress, > tn3270DefaultApplIpGroupName, > tn3270DefaultApplIfIndex, > tn3270TelnetAppl, > tn3270LmApplName, > tn3270LmApplIpAddress, > tn3270LmApplIpGroupName, > tn3270LmApplIfIndex, > tn3270UsstcpTableName, > tn3270UsstcpIpAddress, > tn3270UsstcpIpGroupName, > tn3270UsstcpIfIndex, > tn3270SessionTermState, > tn3270Msg07Enabled, > tn3270OldSolicitorEnabled, > tn3270AllowApplDisconnect, > tn3270AllowApplRowStatus, > tn3270AllowApplLuRowStatus, > tn3270RestrictApplDisconnect, > tn3270RestrictApplRowStatus, > tn3270RestrictApplUserRowStatus, > tn3270RestrictApplULuRowStatus, > tn3270IpGroupSubnetMask, > tn3270IpGroupIpSubnet, > tn3270IpGroupRowStatus, > tn3270LuGroupRowStatus, > tn3270PrtGroupRowStatus, > tn3270LuMapIpAddr, > tn3270LuMapIpGroupName, > tn3270LuMapRowStatus, > tn3270PrtMapIpAddr, > tn3270PrtMapIpGroupName, > tn3270PrtMapRowStatus, > tn3270LogmodeName, > tn3270LogmodeRowStatus > } > STATUS current > DESCRIPTION > "This group is mandatory for all hosts supporting the > TN3270 connections." > ::= { tn3270Groups 1 } > > tn3270TcpConnTableGroup OBJECT-GROUP > OBJECTS { > tn3270TcpConnLastActivity, > > > >Expires November 1997 [Page 29]~ > > > > > >White TN3270 Management Information Base (TN3270-MIB) 30 May 1997 > > > tn3270TcpConnBytesIn, > tn3270TcpConnBytesOut, > tn3270TcpConnReXmt, > tn3270TcpConnReXmtCount, > tn3270TcpConnRoundTripTime, > tn3270TcpConnRoundTripVariance, > tn3270TcpConnTargetAppl, > tn3270TcpConnLuName, > tn3270TcpConnClientUserId, > tn3270TcpConnLogMode, > tn3270TcpConnProto > } > STATUS current > DESCRIPTION > "This group is mandatory for all hosts supporting the > TN3270 connections." > ::= { tn3270Groups 2 } > > END > > > >5. Security Considerations > > Certain management information defined in this MIB may be considered > sensitive in some network environments. Therefore, authentication of > received SNMP requests and controlled access to management information > should be employed in such environments. The method for this > authentication is a function of the SNMP Administrative Framework, and > has not been expanded by this MIB. > > Several objects in this MIB allow write access or provide for remote > creation. Allowing this support in a non-secure environment can have a > negative effect on network operations. It is recommended that > implementers seriously consider whether set operations should be > allowed without providing, at a minimum, authentication of request > origin. It it recommended that without such support that the following > objects be implemented as read-only: > > o tn3270Port > o tn3270InactivityTimer > o tn3270Timemark > o tn3270ScanInterval > o tn3270BinaryLineMode > o tn3270DisableSga > o tn3270AdminStatus > o tn3270DefaultApplName > o tn3270DefaultApplIpAddress > > > >Expires November 1997 [Page 30]~ > > > > > >White TN3270 Management Information Base (TN3270-MIB) 30 May 1997 > > > o tn3270DefaultApplIpGroupName > o tn3270DefaultApplIfIndex > o tn3270TelnetAppl > o tn3270LmApplName > o tn3270LmApplIpAddress > o tn3270LmApplIpGroupName > o tn3270LmApplIfIndex > o tn3270UsstcpTableName > o tn3270UsstcpIpAddress > o tn3270UsstcpIpGroupName > o tn3270UsstcpIfIndex > o tn3270SessionTermState > o tn3270Msg07Enabled > o tn3270OldSolicitorEnabled > o tn3270AllowApplDisconnect > o tn3270AllowApplLuRowStatus > o tn3270RestrictApplDisconnect > o tn3270RestrictApplUserRowStatus > o tn3270RestrictApplULuRowStatus > o tn3270IpGroupSubnetMask > o tn3270IpGroupIpSubnet > o tn3270LuGroupRowStatus > o tn3270PrtGroupRowStatus > o tn3270LuMapIpAddr > o tn3270LuMapIpGroupName > o tn3270PrtMapIpAddr > o tn3270PrtMapIpGroupName > o tn3270LogmodeName > > The following objects should either be implemented as read-only or not > implemented when security is an issue as previously discussed: > > o tn3270AllowApplRowStatus > o tn3270RestrictApplRowStatus > o tn3270IpGroupRowStatus > o tn3270LuMapRowStatus > o tn3270PrtMapRowStatus > o tn3270LogmodeRowStatus > > >6. Acknowledgments > > This document is a product of the TN3270E Working Group. > > >7. References > > > > > >Expires November 1997 [Page 31]~ > > > > > >White TN3270 Management Information Base (TN3270-MIB) 30 May 1997 > > >[1] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and > Waldbusser S., "Structure of Management Information for version 2 > of the Simple Network Management Protocol (SNMPv2)", RFC 1902, > January 1996. > > >[2] Network Working Group, Postel, J., and Reynolds, J., "Telnet > Protocol Specification", RFC 854, May 1983. > > >[3] Network Working Group, Postel, J., and Reynolds, J., "Telnet Timing > Mark Option", RFC 860, May 1983. > > >[4] Network Working Group and Rekhter J., "Telnet 3270 Regime Option", > RFC 1041, January 1988. > > >[5] McCloghrie, K., and M. Rose, Editors, "Management Information Base > for Network Management of TCP/IP-based internets: MIB-II", STD 17, > RFC 1213, Hughes LAN Systems, Performance Systems International, > March 1991. > > >[6] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. > Waldbusser, "Textual Conventions for version 2 of the Simple > Network Management Protocol (SNMPv2)", RFC 1903, January 1996. > > >[7] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. > Waldbusser, "Protocol Operations for version 2 of the Simple > Network Management Protocol (SNMPv2)", RFC 1905, January 1996. > > >[8] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. > Waldbusser, "Conformance Statements for version 2 of the Simple > Network Management Protocol (SNMPv2)", RFC 1904, January 1996. > > >[9] Case, J., M. Fedor, M. Schoffstall, J. Davin, "Simple Network > Management Protocol", RFC 1157, SNMP Research, Performance Systems > International, MIT Laboratory for Computer Science, May 1990. > > >[10] IETF SNMPv2 Working Group and McCloghrie, K., "TCP-MIB > Definitions", November 1994. > > > > > >Expires November 1997 [Page 32]~ > > > > > >White TN3270 Management Information Base (TN3270-MIB) 30 May 1997 > > >8. Authors' Addresses > > Kenneth D. White > Dept. G80/Bldg 503 > IBM Corporation > Research Triangle Park, NC 27709, USA > E-mail: kennethw@vnet.ibm.com > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > >Expires November 1997 [Page 33]~ >   Received: from cnri by ietf.org id aa09793; 19 Jun 97 11:44 EDT Received: from list.nih.gov (list.nih.gov [165.112.130.6]) by cnri.reston.va.us (8.8.5/8.7.3) with ESMTPid LAA04055 for ; Thu, 19 Jun 1997 11:43:07 -0400 (EDT) Received: from list.nih.gov (terrific.net.nih.gov [165.112.130.6]) by list.nih.gov (8.8.5/8.8.5) with ESMTP id LAA07891; Thu, 19 Jun 1997 11:32:48 -0400 (EDT) Received: from LIST.NIH.GOV by LIST.NIH.GOV (LISTSERV-TCP/IP release 1.8c) with spool id 2771768 for TN3270E@LIST.NIH.GOV; Thu, 19 Jun 1997 11:32:45 -0400 Received: from msmail.walldata.com ([198.252.98.5]) by list.nih.gov (8.8.5/8.8.5) with SMTP id LAA07356 for ; Thu, 19 Jun 1997 11:22:38 -0400 (EDT) Received: from Microsoft Mail (PU Serial #1100) by msmail.walldata.com (PostalUnion/SMTP(tm) v2.1.8d for Windows NT(tm)) id AA-1997Jun19.081947.1100.868654; Thu, 19 Jun 1997 08:24:09 -0700 From: "Erickson, Rodger" To: tn3270e , bart Message-ID: <1997Jun19.081947.1100.868654@msmail.walldata.com> X-Mailer: Microsoft Mail via PostalUnion/SMTP for Windows NT Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Organization: Wall Data Inc. Date: Thu, 19 Jun 1997 08:24:09 -0700 Subject: RE: Work Group Activities Sender: owner-tn3270e@list.nih.gov I have already sent this out to the working group once, though I didn't receive any feedback. I'll take the opportunity of Ed's posting to send this again: ########################### As a result of our interim working group meeting in Raleigh, I am posting some "food-for-thought" on some holes in the current RFC (1647) with respect to: a) when is the keyboard *really* unlocked, and b) how should a BID be handled. I don't profess to be an SNA guru so while any and all comments are welcome, I would especially appreciate any corrections/additions that others want to make to any statements I make below with respect to SNA. "KEYBOARD RESTORE PROBLEM" The first problem concerns uncertainty about when the client can send data to the TN3270E server. TN3270E provides for an End-Of-Record (EOR) mechanism which allows the client to determine where the boundry is between 3270 Data Stream Commands. The Server sends EOR whenever it sends data to the client for which the LIC (Last-in-chain) indicator was set. Today, Clients have no choice but to interpret the presence of EOR as an indication that it is okay to go ahead and send data back to the host (providing the 3270 DataStream has restored the keyboard). Since it is not uncommon for the Server to receive a LIC from the host with no CDI (Change Direction Indicator) set, a serious problem is created where the Client will send data to the Server when it does not own the half-duplex Send State. The Server has three options, all of which are bad. It can: a) send the Client data up to the host which will result in an SNA State error (causing the session to be unbound), b) throw the client data away (resulting in lost data), or c) queue the client data until it owns the Send State. Option C seems to be the best of the three. However, there are still problems when data continues to flow inbound from the Server and gets treated by the Client as a response to what it has just sent out. This causes data synchronization problems because this new data has nothing to do with the data the Client just sent out (because it's still queued at the Server). Often, the end result is a hung session. The solution is for the Server to provide the Client with an indication that it is okay to go ahead and send data. Let's call this the SDI (Send Data Indicator). The Server should send the SDI to the Client under the following circumstances (NOTE: the items below refer to SNA information like CDI, EBI and DRI. These items do not flow down to the client and reference to them implies presence in the data received from the host before it is translated to TN3270E format and sent down to the Client): 1) If the TN3270E RESPONSES function has been negotiated and DRI (Definite Response Indicator) is set, as soon as it *receives* a response from the Client for a data chain that had the CDI or EBI (End Bracket Indicator) set. 2) If the TN3270E RESPONSES function has been negotiated and DRI is *NOT* set, as soon as it *sends* a chain to the Client that has either the CDI or EBI set. 3) If the TN3270E RESPONSES function has *NOT* been negotiated, as soon as it *sends* a chain to the Client that has either the CDI or EBI set. The actual mechanism for sending the SDI to the Client will be discussed later in the document. "BID PROBLEM" The second problem involves both explicit and implicit BID. When the SNA Session is in the BETB (Between Bracket) state, the host (PLU) may bid for the Send State by either sending an Explicit or Implicit BID. In normal SNA, the Client must process this BID, either granting the Send State to the host or rejecting the request. Having granted the request, it must wait its turn before attempting to send out any data. In the TN3270 world, there is no mechanism for including the Client in this BID process. Thus, the Server must process the BID on the Client's behalf. The Server has some options on how it can proceed -- all of them bad. It can: 1) always reject the explicit/implicit BID (this is bad because it will prevent some host applications from working properly, 2) accept the BID but forward Client data up to the host (will result in a state error and the session will be unbound), 3) accept the BID and throw away any subsequent data the Client sends the Server while the host owns the Send State (this results in lost data), or 4) accept the BID and queue any data sent by the Client until the Client has the Send State. Option 4) may seem on the surface as the best way to go. However, there are many applications that will be hosed by this approach (in a manner similar to the Keyboard Restore problem discussed previously). If the Client continues to send data up to the Server after the Server has granted a BID, the server will queue that data. However, the Client may interpret the data it receives from the host as a response to the data it has just sent out (that's still queued at the Server). This will result in a hung/confused application. This problem can be fixed by allowing the BID to be propagated down to the Client. Whenever the Server receives a valid BID (implicit or explicit) from the PLU (i.e. one that occurs in the BETB (Between Bracket) state), it should propagate it down to the Client. The client will then respond either positively or negatively. Having responded positively, the Client must enter the "input inhibited" state until the PLU has returned the Send State to the Client. IMPLEMENTATION OF SOLUTIONS: A new TN3270E FUNCTION will be introduced (e.g. 07). Negotiating this Function implies that both the Client and the Server will be able to handle both the SDI and the BID. The SDI will be sent by setting the "REQUEST-FLAG field" to 0x01. Currently, the REQUEST-FLAG field is defined only for a data-type of REQUEST. Given that this BYTE is pretty much wasted, it makes sense to use this field for SDI. A value of 0x01 in this field will be interpreted as SDI for all data types except REQUEST (for REQUEST it will retain its current definition from RFC1647). When the Client receives the SDI, it implies that after processing the current TN3270E message (i.e. when it sees the EOR) it will be okay to send data to the server. Note that the Client will still be allowed to send RESPONSES to the Server, even if it has not received the SDI. Also, in the case where the Server is waiting for a definite response from the Client before sending down the SDI, the RU sent to the Client that contains the SDI will be NULL. BID requires a new TN3270E datatype (e.g. 0x09). The Server will indicate that it has received either an implicit or explicit BID by sending this data type to the Client. Even if the RESPONSES function has not been negotiated, the Client MUST respond to the BID (the Server should also send a SEQ-NUM which should be used by the Client in its response). It sends a positive response to the server via the RESPONSE data type with the data byte containing POSITIVE-RESPONSE (as defined in the current RFC). It rejects the BID via the RESPONSE data type with the data byte containing NEGATIVE-RESPONSE (as defined in the current RFC). The server is then responsible for constructing the appropriate SNA response to the host. There is a potential race condition where the Client sends data to the Server after the Server has sent the BID to the Client (presumably the Client hadn't seen the BID before it sent data). In this race condition case where the Server sees data from the Client before it sees a positive/negative response to the BID, it should treat the Data as an implied negative response and reject the BID before sending the Client data up to the host. The Client will know that such a race has ocurred because it will see a BID come from the Server before it receives the SDI. In this case, the Client can just silently discard the BID (no response should be sent to the Server because the Server will already have responded negatively to the host). ******************************* This is intended as a starting point -- a straw man to throw things at (or you could even set it on fire if you're so inclined :-) Rodger Erickson Wall Data ---------- From: bart[SMTP:bart@VNET.IBM.COM] Sent: Tuesday, June 17, 1997 10:30 AM To: tn3270e Subject: Work Group Activities The following is a list of the current Enhancements being examined by the tn3270e Enhancements work group and the party responsible for each item. Please comment on these items as well as suggest other items that you feel are important but not listed. A decision will be reached by the work group on the final list by the December meeting in Washington DC based upon the perceived priority of the item and amount of work group resource available to work on it. ITEMS RESPONSIBLE PARTY ------------------- ------------------- Security, Firewalls Michael Boe Compression, Caching Service Location Keith Humphrey Session Balancing RTM, Network Mgmt Robert Moore Keyboard Restore, Roger Erickson Bid/Implicit Bid Unbind, Sense Data, Ed Bailey OIA Length Indicator, Mark Williams Abort Flow (Flush) FMH Deric Bolton An initial description of each item will be posted on the listsrv by the responsible party for discussion. ------ Message Header Follows ------ Received: from walldata.com by msmail.walldata.com (PostalUnion/SMTP(tm) v2.1.8d for Windows NT(tm)) id AA-1997Jun17.083514.1100.566197; Tue, 17 Jun 1997 08:35:14 -0700 Received: from list.nih.gov (list.nih.gov [165.112.130.6]) by walldata.com (8.8.5/8.8.5) with ESMTP id IAA24031 for ; Tue, 17 Jun 1997 08:34:42 -0700 (PDT) Received: from list.nih.gov (terrific.net.nih.gov [165.112.130.6]) by list.nih.gov (8.8.5/8.8.5) with ESMTP id LAA10446; Tue, 17 Jun 1997 11:24:56 -0400 (EDT) Received: from LIST.NIH.GOV by LIST.NIH.GOV (LISTSERV-TCP/IP release 1.8c) with spool id 2752115 for TN3270E@LIST.NIH.GOV; Tue, 17 Jun 1997 11:24:53 -0400 Received: from VNET.IBM.COM (vnet.ibm.com [204.146.168.194]) by list.nih.gov (8.8.5/8.8.5) with SMTP id LAA10421 for ; Tue, 17 Jun 1997 11:24:49 -0400 (EDT) Received: from RALVM5 by VNET.IBM.COM (IBM VM SMTP V2R3) with BSMTP id 2851; Tue, 17 Jun 97 11:24:46 EDT From: bart@VNET.IBM.COM Message-Id: <199706171524.LAA10421@list.nih.gov> Date: Tue, 17 Jun 97 10:39:42 EDT To: tn3270e@LIST.NIH.GOV Subject: Work Group Activities Sender: owner-tn3270e@LIST.NIH.GOV   Received: from cnri by ietf.org id aa08188; 20 Jun 97 12:37 EDT Received: from list.nih.gov (list.nih.gov [165.112.130.6]) by cnri.reston.va.us (8.8.5/8.7.3) with ESMTPid MAA06904 for ; Fri, 20 Jun 1997 12:36:56 -0400 (EDT) Received: from list.nih.gov (terrific.net.nih.gov [165.112.130.6]) by list.nih.gov (8.8.5/8.8.5) with ESMTP id MAA18161; Fri, 20 Jun 1997 12:28:13 -0400 (EDT) Received: from LIST.NIH.GOV by LIST.NIH.GOV (LISTSERV-TCP/IP release 1.8c) with spool id 2777714 for TN3270E@LIST.NIH.GOV; Fri, 20 Jun 1997 12:28:10 -0400 Received: from VNET.IBM.COM (vnet.ibm.com [204.146.168.194]) by list.nih.gov (8.8.5/8.8.5) with SMTP id MAA18148 for ; Fri, 20 Jun 1997 12:28:09 -0400 (EDT) Received: from RALVM12 by VNET.IBM.COM (IBM VM SMTP V2R3) with BSMTP id 8540; Fri, 20 Jun 97 12:28:06 EDT From: kennethw@vnet.ibm.com Message-Id: <199706201628.MAA18148@list.nih.gov> Date: Fri, 20 Jun 97 12:23:28 EDT To: tn3270e@list.nih.gov cc: NPW@datcon.co.uk Subject: Sender: owner-tn3270e@list.nih.gov Nick, >The proposed TN3270 MIB is certainly an extensive and thorough effort. >I wouldn't claim to be a MIB expert, but I am concerned that several >aspects of this MIB might make it difficult or impossible to implement >except in very specific products. >1) The MIB includes a lot of information which is only available on the >host and not on a TN3270E gateway (unless the gateway administrator >enters a lot of extra configuration information, in which case I'd >question its likely accuracy). I'm thinking here of all the information >about host applications and users. Is it valid just to leave these >tables empty ? >2) Some of the MIB objects are not really relevant to TN3270 or TN3270E, >or are rather implementation dependent. For example, the MIB includes >control over binary line-mode and over go-aheads, and is overly specific >about TIMEMARK keep-alives while omitting NOP keep-alives completely. >3) The MIB includes information which is at too low a level in the >TCP/IP stack. I doubt whether many TN3270E implementations have much >involvement with network interfaces, TCP retransmits or TCP round-trip >times. >The MIB also presents information in a way which will be easy for some >implementations and difficult for others, but to a certain extent that's >unavoidable. (As an example, the LuMapTable maps LU names to IP >addresses, which is easy if the server works that way, but more awkward >if it maps IP addresses to LU names.) >For the MIB to be reasonably widely implemented in practice, I think it >needs to contain a clearly-identified subset which is based on the >TN3270/TN3270E Specs and which is generally applicable. It's not clear >to me that the proposed MIB achieves this. The proposed MIB was a starting point for discussion. I have received similar comments as yours from other implementers and agree. The MIB that I have submitted is being completely re-done to clearly identify a subset of objects that should (hopefully) be common across implementations. These objects will be mandatory. The other objects will either be deleted on move into optional groups. I am also removing the TCP stack specific objects from the tcpConnTable AUGMENTation that I recommended and am submitting a separate proposal to the TCP Implementation Working Group to add these plus other objects to the TCP Group. I intend to distribute a new internet-draft that should be more in line with what is needed prior to Munich. Regards, Ken   Received: from cnri by ietf.org id aa08432; 20 Jun 97 12:56 EDT Received: from list.nih.gov (list.nih.gov [165.112.130.6]) by cnri.reston.va.us (8.8.5/8.7.3) with ESMTPid MAA06944 for ; Fri, 20 Jun 1997 12:55:50 -0400 (EDT) Received: from list.nih.gov (terrific.net.nih.gov [165.112.130.6]) by list.nih.gov (8.8.5/8.8.5) with ESMTP id MAA19490; Fri, 20 Jun 1997 12:46:31 -0400 (EDT) Received: from LIST.NIH.GOV by LIST.NIH.GOV (LISTSERV-TCP/IP release 1.8c) with spool id 2778091 for TN3270E@LIST.NIH.GOV; Fri, 20 Jun 1997 12:46:28 -0400 Received: from smtp.datcon.co.uk (smtp.datcon.co.uk [192.91.191.4]) by list.nih.gov (8.8.5/8.8.5) with SMTP id MAA19473 for ; Fri, 20 Jun 1997 12:46:23 -0400 (EDT) Received: by smtp.datcon.co.uk with SMTP (Microsoft Exchange Server Internet Mail Connector Version 4.0.995.52) id <01BC7DA1.B378DB20@smtp.datcon.co.uk>; Fri, 20 Jun 1997 17:45:11 +0100 Message-ID: From: Nick Weeds To: "'kennethw@VNET.IBM.COM'" Cc: 'TN3270E list' Subject: RE: Date: Fri, 20 Jun 1997 17:44:38 +0100 X-Mailer: Microsoft Exchange Server Internet Mail Connector Version 4.0.995.52 Encoding: 72 TEXT Sender: owner-tn3270e@list.nih.gov Thanks Ken. On reflection I wonder whether some of the mainframe-centric information (host applications, users etc.) might be better placed in a mainframe MIB separate from the TN3270 MIB. Presumably that information is applicable beyond TN3270 (e.g. normal SNA host access). If so, it is best kept on the mainframe in a mainframe MIB. Then - an administrator with a TN3270 gateway would query the mainframe for mainframe information and the gateway for TN3270 gateway information - an administrator with TN3270 access to the mainframe would query both MIBs on the mainframe - an administrator with SNA access to the host would query just the mainframe MIB Nick. >---------- >From: kennethw@VNET.IBM.COM[SMTP:kennethw@VNET.IBM.COM] >Sent: 20 June 1997 17:23 >To: tn3270e@list.nih.gov >Cc: Nick Weeds >Subject: > >Nick, > >>The proposed TN3270 MIB is certainly an extensive and thorough effort. >>I wouldn't claim to be a MIB expert, but I am concerned that several >>aspects of this MIB might make it difficult or impossible to implement >>except in very specific products. > >>1) The MIB includes a lot of information which is only available on the >>host and not on a TN3270E gateway (unless the gateway administrator >>enters a lot of extra configuration information, in which case I'd >>question its likely accuracy). I'm thinking here of all the information >>about host applications and users. Is it valid just to leave these >>tables empty ? > >>2) Some of the MIB objects are not really relevant to TN3270 or TN3270E, >>or are rather implementation dependent. For example, the MIB includes >>control over binary line-mode and over go-aheads, and is overly specific >>about TIMEMARK keep-alives while omitting NOP keep-alives completely. > >>3) The MIB includes information which is at too low a level in the >>TCP/IP stack. I doubt whether many TN3270E implementations have much >>involvement with network interfaces, TCP retransmits or TCP round-trip >>times. > >>The MIB also presents information in a way which will be easy for some >>implementations and difficult for others, but to a certain extent that's >>unavoidable. (As an example, the LuMapTable maps LU names to IP >>addresses, which is easy if the server works that way, but more awkward >>if it maps IP addresses to LU names.) > >>For the MIB to be reasonably widely implemented in practice, I think it >>needs to contain a clearly-identified subset which is based on the >>TN3270/TN3270E Specs and which is generally applicable. It's not clear >>to me that the proposed MIB achieves this. > >The proposed MIB was a starting point for discussion. I have received >similar comments as yours from other implementers and agree. The MIB >that I have submitted is being completely re-done to clearly identify >a subset of objects that should (hopefully) be common across >implementations. These objects will be mandatory. The other objects >will either be deleted on move into optional groups. I am also >removing the TCP stack specific objects from the tcpConnTable >AUGMENTation that I recommended and am submitting a separate proposal >to the TCP Implementation Working Group to add these plus other objects >to the TCP Group. I intend to distribute a new internet-draft that >should be more in line with what is needed prior to Munich. > >Regards, Ken >   Received: from cnri by ietf.org id aa04153; 21 Jun 97 8:38 EDT Received: from list.nih.gov (list.nih.gov [165.112.130.6]) by cnri.reston.va.us (8.8.5/8.7.3) with ESMTPid IAA08642 for ; Sat, 21 Jun 1997 08:37:29 -0400 (EDT) Received: from list.nih.gov (terrific.net.nih.gov [165.112.130.6]) by list.nih.gov (8.8.5/8.8.5) with ESMTP id IAA16471; Sat, 21 Jun 1997 08:28:49 -0400 (EDT) Received: from LIST.NIH.GOV by LIST.NIH.GOV (LISTSERV-TCP/IP release 1.8c) with spool id 2781230 for TN3270E@LIST.NIH.GOV; Sat, 21 Jun 1997 08:28:45 -0400 Received: from VNET.IBM.COM (vnet.ibm.com [204.146.168.194]) by list.nih.gov (8.8.5/8.8.5) with SMTP id IAA16458 for ; Sat, 21 Jun 1997 08:28:44 -0400 (EDT) Received: from RALVM12 by VNET.IBM.COM (IBM VM SMTP V2R3) with BSMTP id 6769; Sat, 21 Jun 97 08:28:43 EDT From: kennethw@vnet.ibm.com Message-Id: <199706211228.IAA16458@list.nih.gov> Date: Sat, 21 Jun 97 08:24:54 EDT To: NPW@datcon.co.uk cc: tn3270e@list.nih.gov Subject: RE: Sender: owner-tn3270e@list.nih.gov Nick, >On reflection I wonder whether some of the mainframe-centric information >(host applications, users etc.) might be better placed in a mainframe >MIB separate from the TN3270 MIB. Presumably that information is >applicable beyond TN3270 (e.g. normal SNA host access). If so, it is >best kept on the mainframe in a mainframe MIB. Then >- an administrator with a TN3270 gateway would query the mainframe for >mainframe information and the gateway for TN3270 gateway information >- an administrator with TN3270 access to the mainframe would query both >MIBs on the mainframe >- an administrator with SNA access to the host would query just the >mainframe MIB I agree. I will resubmit what I consider to be a base MIB that applies to both host and gateway TN3270E Servers. A second internet-draft will be submitted to basically provide for Target Application definition and mapping which Host Servers do but Gateway Servers don't. Bob Moore, Katie Lee and myself are also working on a third submission to define a MIB and explain how response time data can be collected for TN3270E sessions. This is intended to be a generic solution and prereqs only the base MIB, not the Target Application Mapping MIB. Ken   Received: from cnri by ietf.org id aa12647; 22 Jun 97 21:31 EDT Received: from list.nih.gov (list.nih.gov [165.112.130.6]) by cnri.reston.va.us (8.8.5/8.7.3) with ESMTPid VAA09726 for ; Sun, 22 Jun 1997 21:30:21 -0400 (EDT) Received: from list.nih.gov (terrific.net.nih.gov [165.112.130.6]) by list.nih.gov (8.8.5/8.8.5) with ESMTP id VAA13142; Sun, 22 Jun 1997 21:22:13 -0400 (EDT) Received: from LIST.NIH.GOV by LIST.NIH.GOV (LISTSERV-TCP/IP release 1.8c) with spool id 2789045 for TN3270E@LIST.NIH.GOV; Sun, 22 Jun 1997 21:22:08 -0400 Received: from ringer.cisco.com (ringer.cisco.com [171.69.176.7]) by list.nih.gov (8.8.5/8.8.5) with ESMTP id VAA13129 for ; Sun, 22 Jun 1997 21:21:57 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by ringer.cisco.com (8.8.4-Cisco.1/8.6.5) with SMTP id LAA19080; Mon, 23 Jun 1997 11:20:44 +1000 (EST) Date: Mon, 23 Jun 1997 11:20:44 +1000 (EST) From: Rajesh Agrawal Reply-To: Rajesh Agrawal Subject: Re: To: kennethw@vnet.ibm.com cc: NPW@datcon.co.uk, tn3270e@list.nih.gov In-Reply-To: <199706211228.IAA16458@list.nih.gov> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Sender: owner-tn3270e@list.nih.gov Ken, I appreciate your efforts in taking lead to develop a standard mib for TN3270. We would like to offer any help that you might require in your efforts. I was planning to stress the need of accomdating both type of server implementations - Host based servers and Gateway servers in standard mib development. But I realize from your discussion with Nick Weeds that you are already planning to do so. So instead of that, I would just like to contribute some ideas that might help you in accomdating the requirements of a gateway server implementation as well. As you might be aware, Cisco has a gateway based TN3270/TN3270E server implementation which is channel attached(other attachments optional). We have developed a Cisco mib to satisfy the SNMP needs of our product. It has proven very successful in the field in terms of usefulness. I would like to present it to you and the Community as representing our ideas. It (along with Ken's original proposal) could serve as a basis of developing a generic mib that will satisfy needs of most users. Some of the the key features of our mib CISCO-TN3270SERVER-MIB are: 1. It is a bridging mib among TCPIP mib, NAU mib and DLUR mib. This is minimalist approach from gateway point of view. So instead of duplicating information, it builds on top of them. 2. We have two tables client ip/port to LU mapping and LU to client ip/port table. This enables navigating the mib from either world - TCPIP or SNA in efficient manner. 3. We store extensive statistices on server ip/port basis as this gives good idea about overall server performance without having to access each connection statistics and adding them. This approach is effective as well as efficient. 4. We keep extensive configuration information in generic way about PU, ip/port listening points and client ip-LU mapping. 5. Various other bits and pieces which enable in disgnosing problems. While we tried to keep our mib as generic as possible for any gateway implementation, I am sure there could be a few things that donot go well with other Gateway server implementations. But as already pointed out by Nick and you, substantial discussion is needed to arrive at a mib that meets the needs of most implementations. I am sure you would find this mib very innovative and useful, and as a step forward in you efforts to develop a viable standard. Please do let me know your criticism and comments. Also, we look forward to any help we can provide in your efforts. Regards, Rajesh Note: The Cisco mib is attached at the end of this mail > Nick, > > >On reflection I wonder whether some of the mainframe-centric information > >(host applications, users etc.) might be better placed in a mainframe > >MIB separate from the TN3270 MIB. Presumably that information is > >applicable beyond TN3270 (e.g. normal SNA host access). If so, it is > >best kept on the mainframe in a mainframe MIB. Then > >- an administrator with a TN3270 gateway would query the mainframe for > >mainframe information and the gateway for TN3270 gateway information > >- an administrator with TN3270 access to the mainframe would query both > >MIBs on the mainframe > >- an administrator with SNA access to the host would query just the > >mainframe MIB > > I agree. I will resubmit what I consider to be a base MIB that > applies to both host and gateway TN3270E Servers. A second > internet-draft will be submitted to basically provide for Target > Application definition and mapping which Host Servers do but > Gateway Servers don't. Bob Moore, Katie Lee and myself are also working > on a third submission to define a MIB and explain how response > time data can be collected for TN3270E sessions. This is intended to > be a generic solution and prereqs only the base MIB, not the Target > Application Mapping MIB. > > Ken CISCO-TN3270SERVER-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, Counter32, -- Unsigned32, Gauge32, IpAddress FROM SNMPv2-SMI TEXTUAL-CONVENTION, DisplayString, MacAddress, TimeStamp, TruthValue FROM SNMPv2-TC MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF ciscoMgmt FROM CISCO-SMI ; ciscoTn3270ServerMIB MODULE-IDENTITY LAST-UPDATED "9701220000Z" ORGANIZATION "Cisco Systems, Inc." CONTACT-INFO " Cisco Systems Customer Service Postal: 170 W. Tasman Drive San Jose, CA 95134 USA Tel: +1 800 553-NETS e-mail: cs-tn3270@cisco.com" DESCRIPTION "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 " REVISION "9701220000Z" DESCRIPTION "Added tn3270sPuIpPrecedenceScreen, tn3270sPuIpPrecedencePrinter, tn3270sPuIpTosScreen and tn3270sPuIpTosPrinter to tn3270sPuTable. Added tn3270sPuNailTable and tn3270sIpNailTable. " REVISION "9609120000Z" DESCRIPTION "Obsoleted tn3270sLuLastEvent. Added ciscoTn3270ServerMIBGroupObsolete. Modified SYNTAX clause for tn3270sLuAppnLinkIndex. Introduced tn3270sRunningTime. Replaced tn3270sStatsInboundTransactions, tn3270sStatsOutboundTransactions, tn3270sStatsSampledInboundTransactions, tn3270sStatsNetSampledInboundTransactionRespTime, tn3270sStatsSampledOutboundTransactions, tn3270sStatsNetSampledOutboundTransactionRespTime, with tn3270sStatsInboundChains, tn3270sStatsOutboundChains, tn3270sStatsSampledHostResponses, tn3270sStatsNetSampledHostResponseTime, tn3270sStatsSampledClientResponses, tn3270sStatsNetSampledClientResponseTime respectively. " ::= { ciscoMgmt 54 } tn3270sObjects OBJECT IDENTIFIER ::= { ciscoTn3270ServerMIB 1 } tn3270sGlobal OBJECT IDENTIFIER ::= { tn3270sObjects 1 } tn3270sStats OBJECT IDENTIFIER ::= { tn3270sObjects 2 } tn3270sPu OBJECT IDENTIFIER ::= { tn3270sObjects 3 } tn3270sIp OBJECT IDENTIFIER ::= { tn3270sObjects 4 } tn3270sLu OBJECT IDENTIFIER ::= { tn3270sObjects 5 } tn3270sPuNail OBJECT IDENTIFIER ::= { tn3270sObjects 6 } tn3270sIpNail OBJECT IDENTIFIER ::= { tn3270sObjects 7 } Tn3270sUnsigned32 ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "Unsigned32 definition. To be replaced by Unsigned32 from SNMPv2-SMI when its implememted." SYNTAX INTEGER ( 0..4294967295 ) Tn3270sTCPPort ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "A range for tn3270 port addresses." SYNTAX INTEGER ( 0..65535 ) Tn3270sPUIndex ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "Address range for a PU." SYNTAX Tn3270sUnsigned32 Tn3270sLUIndex ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "Address range for a LU." SYNTAX Tn3270sUnsigned32 Tn3270sCpuCard ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "The identity of the board running the server. The values are as follows: 'Route Processor' 'CIP slot ' where slotNumber is a positive integer indicating the slot number the CIP is installed in." SYNTAX DisplayString ( SIZE ( 10..16 ) ) -- ************************************************************* -- * * -- * TN3270 Server - Global information * -- * * -- ************************************************************* tn3270sGlobalTable OBJECT-TYPE SYNTAX SEQUENCE OF Tn3270sGlobalEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A list of TN3270 server and DLUR global information." ::= { tn3270sGlobal 1 } tn3270sGlobalEntry OBJECT-TYPE SYNTAX Tn3270sGlobalEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Parameters values for a group." INDEX { tn3270sIndex } ::= { tn3270sGlobalTable 1 } Tn3270sGlobalEntry ::= SEQUENCE { tn3270sIndex Tn3270sUnsigned32, tn3270sCpuCard Tn3270sCpuCard, tn3270sMaxLus Tn3270sUnsigned32, tn3270sLusInUse Gauge32, tn3270sStartupTime TimeStamp, tn3270sGlobalTcpPort Tn3270sTCPPort, tn3270sGlobalIdleTimeout INTEGER, tn3270sGlobalKeepAlive INTEGER, tn3270sGlobalUnbindAction INTEGER, tn3270sGlobalGenericPool INTEGER, tn3270sTimingMarkSupported TruthValue, tn3270sRunningTime Tn3270sUnsigned32 } tn3270sIndex OBJECT-TYPE SYNTAX Tn3270sUnsigned32 MAX-ACCESS not-accessible STATUS current DESCRIPTION "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." ::= { tn3270sGlobalEntry 1 } tn3270sCpuCard OBJECT-TYPE SYNTAX Tn3270sCpuCard MAX-ACCESS read-only STATUS current DESCRIPTION "The identity of the board running the server." ::= { tn3270sGlobalEntry 2 } tn3270sMaxLus OBJECT-TYPE SYNTAX Tn3270sUnsigned32 (1..65535) MAX-ACCESS read-only STATUS current DESCRIPTION "The maximum number of LUs supported by the server." ::= { tn3270sGlobalEntry 3 } tn3270sLusInUse OBJECT-TYPE SYNTAX Gauge32 (0..65535) MAX-ACCESS read-only STATUS current DESCRIPTION "The number of LUs currently in use on the server." ::= { tn3270sGlobalEntry 4 } tn3270sStartupTime OBJECT-TYPE SYNTAX TimeStamp MAX-ACCESS read-only STATUS current DESCRIPTION "The timestamp when the tn3270 server started." ::= { tn3270sGlobalEntry 5 } tn3270sGlobalTcpPort OBJECT-TYPE SYNTAX Tn3270sTCPPort MAX-ACCESS read-only STATUS current DESCRIPTION "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." ::= { tn3270sGlobalEntry 6 } tn3270sGlobalIdleTimeout OBJECT-TYPE SYNTAX INTEGER (0..65534) UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "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." ::= { tn3270sGlobalEntry 7 } tn3270sGlobalKeepAlive OBJECT-TYPE SYNTAX INTEGER (0..65534) UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "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." ::= { tn3270sGlobalEntry 8 } tn3270sGlobalUnbindAction OBJECT-TYPE SYNTAX INTEGER { keep(1), disconnect(2) } MAX-ACCESS read-only STATUS current DESCRIPTION "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." ::= { tn3270sGlobalEntry 9 } tn3270sGlobalGenericPool OBJECT-TYPE SYNTAX INTEGER { permit(1), deny(2) } MAX-ACCESS read-only STATUS current DESCRIPTION "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." REFERENCE " 'SNA Formats', publication number GA27-3136, IBM Corporation, 'APPN Dependent LU Requester Architecture Reference' Document Number: SV40-1010-01, IBM Corporation. " ::= { tn3270sGlobalEntry 10 } tn3270sTimingMarkSupported OBJECT-TYPE SYNTAX TruthValue MAX-ACCESS read-only STATUS current DESCRIPTION "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 " ::= { tn3270sGlobalEntry 11 } tn3270sRunningTime OBJECT-TYPE SYNTAX Tn3270sUnsigned32 UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Total time elapsed since start of tn3270 server." ::= { tn3270sGlobalEntry 12 } -- ************************************************************* -- * * -- * TN3270 Server - Statistics and Load balancing parameters * -- * * -- ************************************************************* tn3270sStatsTable OBJECT-TYPE SYNTAX SEQUENCE OF Tn3270sStatsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A list of statistics for each TN3270 Server Listening IP/Port pair." ::= { tn3270sStats 1 } tn3270sStatsEntry OBJECT-TYPE SYNTAX Tn3270sStatsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The entry contains parameters which describe the statistics of the ip stacks." INDEX { tn3270sIndex, tn3270sStatsServerAddr, tn3270sStatsServerTcpPort } ::= { tn3270sStatsTable 1 } Tn3270sStatsEntry ::= SEQUENCE { tn3270sStatsServerAddr IpAddress, tn3270sStatsServerTcpPort Tn3270sTCPPort, tn3270sStatsMaxSess Gauge32, tn3270sStatsSpareSess Gauge32, tn3270sStatsConnectsIn Counter32, tn3270sStatsDisconnects Counter32, tn3270sStatsTN3270ConnectsFailed Counter32, tn3270sStatsInboundChains Counter32, tn3270sStatsOutboundChains Counter32, tn3270sStatsSampledHostResponses Counter32, tn3270sStatsNetSampledHostResponseTime Tn3270sUnsigned32, tn3270sStatsSampledClientResponses Counter32, tn3270sStatsNetSampledClientResponseTime Tn3270sUnsigned32 } tn3270sStatsServerAddr OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS not-accessible STATUS current DESCRIPTION "The ip address of this TN3270 Server Listen endpoint." ::= { tn3270sStatsEntry 1 } tn3270sStatsServerTcpPort OBJECT-TYPE SYNTAX Tn3270sTCPPort MAX-ACCESS not-accessible STATUS current DESCRIPTION "The TCP port in this TN3270 Server Listen endpoint." ::= { tn3270sStatsEntry 2 } tn3270sStatsMaxSess OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION "Number of Tn3270 sessions configured which are available to be used by tn3270 clients." ::= { tn3270sStatsEntry 3 } tn3270sStatsSpareSess OBJECT-TYPE SYNTAX Gauge32 MAX-ACCESS read-only STATUS current DESCRIPTION "Spare number of TN3270 sessions available for connect at query time." ::= { tn3270sStatsEntry 4 } tn3270sStatsConnectsIn OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Total number of TN3270 session connects-in received." ::= { tn3270sStatsEntry 5 } tn3270sStatsDisconnects OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Total number of TN3270 sessions disconnected." ::= { tn3270sStatsEntry 6 } tn3270sStatsTN3270ConnectsFailed OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Total number of attempted sessions which failed to negotiate TN3270/E or were rejected by control point." ::= { tn3270sStatsEntry 7 } tn3270sStatsInboundChains OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "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." ::= { tn3270sStatsEntry 8 } tn3270sStatsOutboundChains OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Total number of Outbound(from host to client) RU Chains (identified by EOR) processed." ::= { tn3270sStatsEntry 9 } tn3270sStatsSampledHostResponses OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "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." ::= { tn3270sStatsEntry 10 } tn3270sStatsNetSampledHostResponseTime OBJECT-TYPE SYNTAX Tn3270sUnsigned32 UNITS "10milliseconds" MAX-ACCESS read-only STATUS current DESCRIPTION "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." ::= { tn3270sStatsEntry 11 } tn3270sStatsSampledClientResponses OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Total number of sampled outbound timing marks on which response time computed." ::= { tn3270sStatsEntry 12 } tn3270sStatsNetSampledClientResponseTime OBJECT-TYPE SYNTAX Tn3270sUnsigned32 UNITS "10milliseconds" MAX-ACCESS read-only STATUS current DESCRIPTION "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." ::= { tn3270sStatsEntry 13 } -- ************************************************************* -- * * -- * TN3270 Server - PU parameters * -- * * -- ************************************************************* tn3270sPuTable OBJECT-TYPE SYNTAX SEQUENCE OF Tn3270sPuEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table contains objects which describe the PU configuration parameters not defined in the NAU mib, APPN mib or DLUR mib" ::= { tn3270sPu 1 } tn3270sPuEntry OBJECT-TYPE SYNTAX Tn3270sPuEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A list of TN3270 server PU parameters" INDEX { tn3270sIndex, tn3270sPuIndex } ::= { tn3270sPuTable 1 } Tn3270sPuEntry ::= SEQUENCE { tn3270sPuIndex Tn3270sPUIndex, tn3270sPuIpAddr IpAddress, tn3270sPuTcpPort Tn3270sTCPPort, tn3270sPuIdleTimeout INTEGER, tn3270sPuKeepAlive INTEGER, tn3270sPuUnbindAction INTEGER, tn3270sPuGenericPool INTEGER, tn3270sPuState INTEGER, tn3270sPuType INTEGER, tn3270sPuLuSeed DisplayString, tn3270sLocalSapAddress INTEGER, tn3270sRemoteSapAddress INTEGER, tn3270sRemoteMacAddress MacAddress, tn3270sPuIpPrecedenceScreen INTEGER, tn3270sPuIpPrecedencePrinter INTEGER, tn3270sPuIpTosScreen INTEGER, tn3270sPuIpTosPrinter INTEGER } tn3270sPuIndex OBJECT-TYPE SYNTAX Tn3270sPUIndex MAX-ACCESS not-accessible STATUS current DESCRIPTION "Index used to uniquely identify each Node instance. This is the same as snaNodeAdminIndex in the NAU MIB." ::= { tn3270sPuEntry 1 } tn3270sPuIpAddr OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-only STATUS current DESCRIPTION "The ip address of this TN3270 server." ::= { tn3270sPuEntry 2 } tn3270sPuTcpPort OBJECT-TYPE SYNTAX Tn3270sTCPPort MAX-ACCESS read-only STATUS current DESCRIPTION "The TCP port of this TN3270 server telnet session." ::= { tn3270sPuEntry 3 } tn3270sPuIdleTimeout OBJECT-TYPE SYNTAX INTEGER (0..65535) MAX-ACCESS read-only STATUS current DESCRIPTION "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." ::= { tn3270sPuEntry 4 } tn3270sPuKeepAlive OBJECT-TYPE SYNTAX INTEGER (0..65535) MAX-ACCESS read-only STATUS current DESCRIPTION "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." ::= { tn3270sPuEntry 5 } tn3270sPuUnbindAction OBJECT-TYPE SYNTAX INTEGER { keep(1), disconnect(2), inherit(3) } MAX-ACCESS read-only STATUS current DESCRIPTION "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." ::= { tn3270sPuEntry 6 } tn3270sPuGenericPool OBJECT-TYPE SYNTAX INTEGER { permit(1), deny(2), inherit(3) } MAX-ACCESS read-only STATUS current DESCRIPTION "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." ::= { tn3270sPuEntry 7 } tn3270sPuState OBJECT-TYPE SYNTAX INTEGER { shut (1), reset (2), inactive (3), test (4), xid (5), pActpu (6), active (7), actBusy (8) } MAX-ACCESS read-only STATUS current DESCRIPTION "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. " ::= { tn3270sPuEntry 8 } tn3270sPuType OBJECT-TYPE SYNTAX INTEGER { dlur(1), direct(2) } MAX-ACCESS read-only STATUS current DESCRIPTION "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." ::= { tn3270sPuEntry 9 } tn3270sPuLuSeed OBJECT-TYPE SYNTAX DisplayString ( SIZE ( 1..6 ) ) MAX-ACCESS read-only STATUS current DESCRIPTION "For Direct PU this defines the LU name prefix (LU seed) which is concatinated with the locaddr to form a unique name." ::= { tn3270sPuEntry 10 } tn3270sLocalSapAddress OBJECT-TYPE SYNTAX INTEGER (1..254) MAX-ACCESS read-only STATUS current DESCRIPTION "SAP address of the local direct node." ::= { tn3270sPuEntry 11 } tn3270sRemoteSapAddress OBJECT-TYPE SYNTAX INTEGER (1..254) MAX-ACCESS read-only STATUS current DESCRIPTION "SAP address of the remote node; valid for direct PU only." ::= { tn3270sPuEntry 12 } tn3270sRemoteMacAddress OBJECT-TYPE SYNTAX MacAddress MAX-ACCESS read-only STATUS current DESCRIPTION "MAC address of the remote node; valid for direct PU only." ::= { tn3270sPuEntry 13 } tn3270sPuIpPrecedenceScreen OBJECT-TYPE SYNTAX INTEGER (0..7) MAX-ACCESS read-only STATUS current DESCRIPTION "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." REFERENCE "RFC791, RFC1349" ::= { tn3270sPuEntry 14 } tn3270sPuIpPrecedencePrinter OBJECT-TYPE SYNTAX INTEGER (0..7) MAX-ACCESS read-only STATUS current DESCRIPTION "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." REFERENCE "RFC791, RFC1349" ::= { tn3270sPuEntry 15 } tn3270sPuIpTosScreen OBJECT-TYPE SYNTAX INTEGER (0..15) MAX-ACCESS read-only STATUS current DESCRIPTION "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." REFERENCE "RFC791, RFC1349" ::= { tn3270sPuEntry 16 } tn3270sPuIpTosPrinter OBJECT-TYPE SYNTAX INTEGER (0..15) MAX-ACCESS read-only STATUS current DESCRIPTION "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." REFERENCE "RFC791, RFC1349" ::= { tn3270sPuEntry 17 } -- ************************************************************* -- * * -- * TN3270 Server - IP mapping * -- * * -- ************************************************************* tn3270sIpTable OBJECT-TYPE SYNTAX SEQUENCE OF Tn3270sIpEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A list of IP to LU mapping entries" ::= { tn3270sIp 1 } tn3270sIpEntry OBJECT-TYPE SYNTAX Tn3270sIpEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "A list of entries to relate a client IP address to the LU" INDEX { tn3270sIndex, tn3270sIpClientAddr, tn3270sIpClientTcpPort } ::= { tn3270sIpTable 1 } Tn3270sIpEntry ::= SEQUENCE { tn3270sIpClientAddr IpAddress, tn3270sIpClientTcpPort Tn3270sTCPPort, tn3270sIpPuIndex Tn3270sPUIndex, tn3270sIpLuIndex Tn3270sLUIndex } tn3270sIpClientAddr OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS not-accessible STATUS current DESCRIPTION "The ip address of the TN3270 client." ::= { tn3270sIpEntry 1 } tn3270sIpClientTcpPort OBJECT-TYPE SYNTAX Tn3270sTCPPort MAX-ACCESS not-accessible STATUS current DESCRIPTION "The TCP port of the TN3270 client." ::= { tn3270sIpEntry 2 } tn3270sIpPuIndex OBJECT-TYPE SYNTAX Tn3270sPUIndex MAX-ACCESS read-only STATUS current DESCRIPTION "The PU index associated with NAU and PU objects" ::= { tn3270sIpEntry 3 } tn3270sIpLuIndex OBJECT-TYPE SYNTAX Tn3270sLUIndex MAX-ACCESS read-only STATUS current DESCRIPTION "The LU index associated with NAU and LU objects." ::= { tn3270sIpEntry 4 } -- ************************************************************* -- * * -- * TN3270 Server - LU mapping * -- * * -- ************************************************************* tn3270sLuTable OBJECT-TYPE SYNTAX SEQUENCE OF Tn3270sLuEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This helps map LU to client ip/port. Also it provides other useful parameters not available elsewhere." ::= { tn3270sLu 1 } tn3270sLuEntry OBJECT-TYPE SYNTAX Tn3270sLuEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Parameters values for a group." INDEX { tn3270sIndex, tn3270sLuPuIndex, tn3270sLuIndex } ::= { tn3270sLuTable 1 } Tn3270sLuEntry ::= SEQUENCE { tn3270sLuPuIndex Tn3270sPUIndex, tn3270sLuIndex Tn3270sLUIndex, tn3270sLuClientAddr IpAddress, tn3270sLuClientTcpPort Tn3270sTCPPort, tn3270sLuTelnetType INTEGER, tn3270sLuTermModel DisplayString, tn3270sLuState INTEGER, tn3270sLuCurInbPacing INTEGER, tn3270sLuCurInbQsize INTEGER, tn3270sLuCurOutQsize INTEGER, tn3270sLuIdleTime INTEGER, tn3270sLuType INTEGER, tn3270sLuAppnLinkIndex DisplayString, tn3270sLuLfsid INTEGER, tn3270sLuLastEvent TimeStamp, tn3270sLuEvents OCTET STRING, tn3270sLuNail TruthValue } tn3270sLuPuIndex OBJECT-TYPE SYNTAX Tn3270sPUIndex MAX-ACCESS not-accessible STATUS current DESCRIPTION "Index used to uniquely identify each PU instance. This is the same as snaNodeAdminIndex in the NAU MIB." ::= { tn3270sLuEntry 1 } tn3270sLuIndex OBJECT-TYPE SYNTAX Tn3270sLUIndex MAX-ACCESS not-accessible STATUS current DESCRIPTION "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." ::= { tn3270sLuEntry 2 } tn3270sLuClientAddr OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-only STATUS current DESCRIPTION "The ip address of the TN3270 client connected to this LU." ::= { tn3270sLuEntry 3 } tn3270sLuClientTcpPort OBJECT-TYPE SYNTAX Tn3270sTCPPort MAX-ACCESS read-only STATUS current DESCRIPTION "The TCP port of the TN3270 client connected to this LU." ::= { tn3270sLuEntry 4 } tn3270sLuTelnetType OBJECT-TYPE SYNTAX INTEGER { tn3270(1), tn3270e(2), neverConnect(3) } MAX-ACCESS read-only STATUS current DESCRIPTION "This indicates whether the negotiated TN3270 session. TN3270, TN3270E or never connected." ::= { tn3270sLuEntry 5 } tn3270sLuTermModel OBJECT-TYPE SYNTAX DisplayString ( SIZE ( 1..17 ) ) MAX-ACCESS read-only STATUS current DESCRIPTION "Terminal type or model number of the incoming TN3270 client." REFERENCE "rfc1647" ::= { tn3270sLuEntry 6 } tn3270sLuState OBJECT-TYPE SYNTAX INTEGER { inactive (1), active (2), pSdt (3), actSession (4), pActlu (5), pNotifyAv (6), pNotifyUa (7), pReset (8), pPsid (9), pBind (10), pUnbind (11), unbindWt (12), sdtWt (13) } MAX-ACCESS read-only STATUS current DESCRIPTION "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 " ::= { tn3270sLuEntry 7 } tn3270sLuCurInbPacing OBJECT-TYPE SYNTAX INTEGER( 0..63 ) MAX-ACCESS read-only STATUS current DESCRIPTION "The number of inbound frames allowed to be sent to the host without receiving a pacing response from the host." ::= { tn3270sLuEntry 8 } tn3270sLuCurInbQsize OBJECT-TYPE SYNTAX INTEGER( 0..63 ) MAX-ACCESS read-only STATUS current DESCRIPTION "After inbound pacing credit is exhausted, the inbound data is queued. This is the number of inbound frames queued waiting for host pacing response." ::= { tn3270sLuEntry 9 } tn3270sLuCurOutQsize OBJECT-TYPE SYNTAX INTEGER( 0..63 ) MAX-ACCESS read-only STATUS current DESCRIPTION "The number of TCP packets in the server queued for transmission to the client" ::= { tn3270sLuEntry 10 } tn3270sLuIdleTime OBJECT-TYPE SYNTAX INTEGER( 0..65535 ) UNITS "seconds" MAX-ACCESS read-only STATUS current DESCRIPTION "Time since last activity was recorded on this LU." ::= { tn3270sLuEntry 11 } tn3270sLuType OBJECT-TYPE SYNTAX INTEGER { dynamic(1), static(2) } MAX-ACCESS read-only STATUS current DESCRIPTION "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. " ::= { tn3270sLuEntry 12 } tn3270sLuAppnLinkIndex OBJECT-TYPE SYNTAX DisplayString (SIZE (1..8) ) MAX-ACCESS read-only STATUS current DESCRIPTION "This is the link index into APPN mib for link on which bind flowed; only valid for DLUR LU." ::= { tn3270sLuEntry 13 } tn3270sLuLfsid OBJECT-TYPE SYNTAX INTEGER( 0..65535 ) MAX-ACCESS read-only STATUS current DESCRIPTION "This is the session identifier on a PU 2.1 link." ::= { tn3270sLuEntry 14 } tn3270sLuLastEvent OBJECT-TYPE SYNTAX TimeStamp MAX-ACCESS read-only STATUS obsolete DESCRIPTION "Time at which the last data was logged for this LU." ::= { tn3270sLuEntry 15 } tn3270sLuEvents OBJECT-TYPE SYNTAX OCTET STRING ( SIZE ( 0..16 ) ) MAX-ACCESS read-only STATUS current DESCRIPTION "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 } tn3270sLuNail OBJECT-TYPE 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 * -- * * -- ************************************************************* tn3270sPuNailTable OBJECT-TYPE 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 } tn3270sPuNailEntry OBJECT-TYPE 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 } tn3270sPuNailClientIpAddr OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-only STATUS current DESCRIPTION "The IP address of the nailed TN3270 client." ::= { tn3270sPuNailEntry 1 } tn3270sPuNailClientIpMask OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-only STATUS current DESCRIPTION "The subnet mask of the nailed TN3270 client." ::= { tn3270sPuNailEntry 2 } tn3270sPuNailType OBJECT-TYPE SYNTAX INTEGER { screen(1), printer(2) } MAX-ACCESS read-only STATUS current DESCRIPTION "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. " ::= { tn3270sPuNailEntry 3 } tn3270sPuNailLuFirst OBJECT-TYPE SYNTAX INTEGER ( 1..255 ) MAX-ACCESS read-only STATUS current DESCRIPTION "The first LU in this range nailed to this client ip address." ::= { tn3270sPuNailEntry 4 } tn3270sPuNailLuLast OBJECT-TYPE SYNTAX INTEGER( 1..255 ) MAX-ACCESS read-only STATUS current DESCRIPTION "The last LU in this range nailed to this client ip address." ::= { tn3270sPuNailEntry 5 } -- ************************************************************* -- * * -- * TN3270 Server - LU Nail Mapping * -- * * -- ************************************************************* tn3270sIpNailTable OBJECT-TYPE SYNTAX SEQUENCE OF Tn3270sIpNailEntry 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 PU index is known but the client IP address is not known, a more efficient way to access this info is via tn3270sPuNailTable. " ::= { tn3270sIpNail 1 } tn3270sIpNailEntry OBJECT-TYPE SYNTAX Tn3270sIpNailEntry 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 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. " INDEX { tn3270sIndex, tn3270sIpNailClientIpAddr, tn3270sPuIndex, tn3270sIpNailLuFirst } ::= { tn3270sIpNailTable 1 } Tn3270sIpNailEntry ::= SEQUENCE { tn3270sIpNailClientIpAddr IpAddress, tn3270sIpNailClientIpMask IpAddress, tn3270sIpNailType INTEGER, tn3270sIpNailLuFirst INTEGER, tn3270sIpNailLuLast INTEGER } tn3270sIpNailClientIpAddr OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-only STATUS current DESCRIPTION "The IP address of the nailed TN3270 client." ::= { tn3270sIpNailEntry 1 } tn3270sIpNailClientIpMask OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-only STATUS current DESCRIPTION "The subnet mask of the nailed TN3270 client." ::= { tn3270sIpNailEntry 2 } tn3270sIpNailType OBJECT-TYPE SYNTAX INTEGER { screen(1), printer(2) } MAX-ACCESS read-only STATUS current DESCRIPTION "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. " ::= { tn3270sIpNailEntry 3 } tn3270sIpNailLuFirst OBJECT-TYPE SYNTAX INTEGER( 1..255 ) MAX-ACCESS read-only STATUS current DESCRIPTION "The first LU in this range nailed to this client ip address." ::= { tn3270sIpNailEntry 4 } tn3270sIpNailLuLast OBJECT-TYPE SYNTAX INTEGER( 1..255 ) MAX-ACCESS read-only STATUS current DESCRIPTION "The last LU in this range nailed to this client ip address." ::= { tn3270sIpNailEntry 5 } -- Notifications ciscoTn3270ServerMIBNotificationPrefix OBJECT IDENTIFIER ::= { ciscoTn3270ServerMIB 2 } -- No notifications currently defined. -- conformance information ciscoTn3270ServerMIBConformance OBJECT IDENTIFIER ::= { ciscoTn3270ServerMIB 3 } ciscoTn3270ServerMIBCompliances OBJECT IDENTIFIER ::= { ciscoTn3270ServerMIBConformance 1 } ciscoTn3270ServerMIBGroups OBJECT IDENTIFIER ::= { ciscoTn3270ServerMIBConformance 2 } -- compliance statements ciscoTn3270ServerMIBCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for entities which implement the Cisco Tn3270s MIB" MODULE -- this module MANDATORY-GROUPS { ciscoTn3270ServerMIBGroup } ::= { ciscoTn3270ServerMIBCompliances 1 } -- units of conformance ciscoTn3270ServerMIBGroup OBJECT-GROUP OBJECTS { tn3270sCpuCard, tn3270sMaxLus, tn3270sLusInUse, tn3270sStartupTime, tn3270sGlobalTcpPort, tn3270sGlobalIdleTimeout, tn3270sGlobalKeepAlive, tn3270sGlobalUnbindAction, tn3270sGlobalGenericPool, tn3270sTimingMarkSupported, tn3270sRunningTime, tn3270sStatsMaxSess, tn3270sStatsSpareSess, tn3270sStatsConnectsIn, tn3270sStatsDisconnects, tn3270sStatsTN3270ConnectsFailed, tn3270sStatsInboundChains, tn3270sStatsOutboundChains, tn3270sStatsSampledHostResponses, tn3270sStatsNetSampledHostResponseTime, tn3270sStatsSampledClientResponses, tn3270sStatsNetSampledClientResponseTime, tn3270sPuIpAddr, tn3270sPuTcpPort, tn3270sPuIdleTimeout, tn3270sPuKeepAlive, tn3270sPuUnbindAction, tn3270sPuGenericPool, tn3270sPuState, tn3270sPuType, tn3270sPuLuSeed, tn3270sLocalSapAddress, tn3270sRemoteSapAddress, tn3270sRemoteMacAddress, tn3270sIpPuIndex, tn3270sIpLuIndex, tn3270sLuClientAddr, tn3270sLuClientTcpPort, tn3270sLuTelnetType, tn3270sLuTermModel, tn3270sLuState, tn3270sLuCurInbPacing, tn3270sLuCurInbQsize, tn3270sLuCurOutQsize, tn3270sLuIdleTime, tn3270sLuType, tn3270sLuAppnLinkIndex, tn3270sLuLfsid, tn3270sLuEvents } STATUS current DESCRIPTION "A collection of objects providing Tn3270 ability to a Cisco agent." ::= { ciscoTn3270ServerMIBGroups 1 } ciscoTn3270ServerMIBComplianceObsolete MODULE-COMPLIANCE STATUS obsolete DESCRIPTION "The compliance statement for obsolete entities." MODULE -- this module GROUP ciscoTn3270ServerMIBGroupObsolete DESCRIPTION "list of obsolete objects." ::= { ciscoTn3270ServerMIBCompliances 2 } ciscoTn3270ServerMIBGroupObsolete OBJECT-GROUP OBJECTS { tn3270sLuLastEvent } STATUS obsolete DESCRIPTION "A collection of objects providing Tn3270 ability to a Cisco agent." ::= { ciscoTn3270ServerMIBGroups 2 } ciscoTn3270ServerMIBComplianceRev1 MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for the TN3270 Server." MODULE -- this module MANDATORY-GROUPS { ciscoTn3270ServerMIBGroup, ciscoTn3270ServerMIBGroupRev1 } ::= { ciscoTn3270ServerMIBCompliances 3 } ciscoTn3270ServerMIBGroupRev1 OBJECT-GROUP OBJECTS { -- IP precedence objects tn3270sPuIpPrecedenceScreen, tn3270sPuIpPrecedencePrinter, tn3270sPuIpTosScreen, tn3270sPuIpTosPrinter, -- Nail objects tn3270sLuNail, -- tn3270sPuNailTable tn3270sPuNailClientIpAddr, tn3270sPuNailClientIpMask, tn3270sPuNailType, tn3270sPuNailLuFirst, tn3270sPuNailLuLast, -- tn3270sIpNailTable tn3270sIpNailClientIpAddr, tn3270sIpNailClientIpMask, tn3270sIpNailType, tn3270sIpNailLuFirst, tn3270sIpNailLuLast } STATUS current DESCRIPTION "A collection of objects providing LU nailing and IP precedence features." ::= { ciscoTn3270ServerMIBGroups 3 } END   Received: from cnri by ietf.org id aa02887; 23 Jun 97 22:15 EDT Received: from list.nih.gov (list.nih.gov [165.112.130.6]) by cnri.reston.va.us (8.8.5/8.7.3) with ESMTPid WAA12715 for ; Mon, 23 Jun 1997 22:14:35 -0400 (EDT) Received: from list.nih.gov (terrific.net.nih.gov [165.112.130.6]) by list.nih.gov (8.8.5/8.8.5) with ESMTP id WAA17802; Mon, 23 Jun 1997 22:05:54 -0400 (EDT) Received: from LIST.NIH.GOV by LIST.NIH.GOV (LISTSERV-TCP/IP release 1.8c) with spool id 2799094 for TN3270E@LIST.NIH.GOV; Mon, 23 Jun 1997 22:05:51 -0400 Received: from VNET.IBM.COM (vnet.ibm.com [204.146.168.194]) by list.nih.gov (8.8.5/8.8.5) with SMTP id WAA17789 for ; Mon, 23 Jun 1997 22:05:50 -0400 (EDT) Received: from RALVM12 by VNET.IBM.COM (IBM VM SMTP V2R3) with BSMTP id 0594; Mon, 23 Jun 97 22:05:48 EDT From: kennethw@vnet.ibm.com Message-Id: <199706240205.WAA17789@list.nih.gov> Date: Mon, 23 Jun 97 22:00:25 EDT To: tn3270e@list.nih.gov cc: ragrawal@cisco.com Subject: Re: Sender: owner-tn3270e@list.nih.gov Rajesh, Thanks a lot for a copy of the your tn3270 MIB. I just finished a base version of the tn3270e-mib that has been discussed. I need to put it a side for the night and make some more revisions before rewriting the internet-draft text and resubmitting to the list for comments. Some quick comparisons between what I now have and what you sent: 1. The new MIB that I plan on resubmitting is a series of tables that except for what is defined to extend the tcpConnTable has a server's local IP Address and port as the first indexes. I did this to enable representation of the tables at either a management application or to enable multi-tn3270(e) Server environments. A question for all those who are reading this is does any one know of a TN3270 Server implementation that can be configured to listen on multiple ports at the same time or an implementation where two Telnet Servers in the same host can listen on the same port? I tried to stay away from using integer indexes based on the experiences of the ifMib working group. 2. I don't yet have the equivalent of: tn3270sCpuCard <= consider sysDescr to be equivalent from the local server's system group. tn3270sGlobalGenericPool tn3270sGlobalStartupTime <= I have a object that keeps TimeTicks from when a server was started. I may change this to a TimeAndDate object. Not sure if this plus tn3270sRunningTime is necessary. tn3270sStatsSpareSess <= I have a total count of the number of available LUs and a inUseCnt. Figured the difference is equivalent to this. tn3270sStatsInBoundChains, OutBoundChains, SampledHostResponses, sampledHostResponseTime, SampledClientResponses, SampledClientResponseTime <= I assumed that there are tools available to monitor the SNA side and that server didn't need to keep RU counts. I'm also not sure of the method of sampling response times. A Response Time Monitoring MIB is being worked on by myself, Bob Moore and Katie Lee. I think we should re-visit these after it has been submitted to the working group for consideration. tn3270sPuTable <= In discussing the first MIB submitted with some Gateway Server implementers I learned that not all implementations have access to the PU information so I left it out of the base MIB. 3. IP to LU mappings are hard to generalize. I will submit something that we all can pick a part. I'm thinking that IP Address to LU/Prt Mappings is the primary search path from a Server prospective and that a management application may prefer to map LU/Prt to IP Address. Disagreement? 4. The level of detail that you provide on a LU is not something that I have as of yet. I also don't have an equivalent of the tn3270sPuNailTable nor tn3270sIpNailTable. 5. The tables in the base MIB that I will resubmit were modeled with RowStatus objects to enable remote creation/deletion. Thanks again for a look at your MIB. There actually was a fair amount of overlap with what I have. I will re-post the base MIB in a day or two so that we all can pick it a part, compare it to yours, and decide were to go from there. Thanks, Ken   Received: from cnri by ietf.org id aa02764; 24 Jun 97 5:46 EDT Received: from list.nih.gov (list.nih.gov [165.112.130.6]) by cnri.reston.va.us (8.8.5/8.7.3) with ESMTPid FAA13198 for ; Tue, 24 Jun 1997 05:45:13 -0400 (EDT) Received: from list.nih.gov (terrific.net.nih.gov [165.112.130.6]) by list.nih.gov (8.8.5/8.8.5) with ESMTP id FAA25927; Tue, 24 Jun 1997 05:40:48 -0400 (EDT) Received: from LIST.NIH.GOV by LIST.NIH.GOV (LISTSERV-TCP/IP release 1.8c) with spool id 2801643 for TN3270E@LIST.NIH.GOV; Tue, 24 Jun 1997 05:40:45 -0400 Received: from smtp.datcon.co.uk (smtp.datcon.co.uk [192.91.191.4]) by list.nih.gov (8.8.5/8.8.5) with SMTP id FAA25914 for ; Tue, 24 Jun 1997 05:40:43 -0400 (EDT) Received: by smtp.datcon.co.uk with SMTP (Microsoft Exchange Server Internet Mail Connector Version 4.0.995.52) id <01BC808A.EE5373E0@smtp.datcon.co.uk>; Tue, 24 Jun 1997 10:39:45 +0100 Message-ID: From: Nick Weeds To: "'kennethw@VNET.IBM.COM'" Cc: 'TN3270E list' Subject: RE: Date: Tue, 24 Jun 1997 10:39:14 +0100 X-Mailer: Microsoft Exchange Server Internet Mail Connector Version 4.0.995.52 Encoding: 84 TEXT Sender: owner-tn3270e@list.nih.gov Ken, You asked about TN3270 implementations which can listen on multiple ports. We ship a TN3270 gateway which provides this capability. Also, if the TN3270 gateway is configured to use the standard TELNET port (23), the TN3270 gateway will hand off the connection to the standard TELNET daemon if the client is not a TN3270 client. Nick. >---------- >From: kennethw@VNET.IBM.COM[SMTP:kennethw@VNET.IBM.COM] >Sent: 24 June 1997 03:00 >To: tn3270e@LIST.NIH.GOV >Cc: ragrawal@cisco.com >Subject: Re: > >Rajesh, > Thanks a lot for a copy of the your tn3270 MIB. I just finished >a base version of the tn3270e-mib that has been discussed. I need >to put it a side for the night and make some more revisions before >rewriting the internet-draft text and resubmitting to the list >for comments. Some quick comparisons between what I now have and >what you sent: > >1. The new MIB that I plan on resubmitting is a series of tables > that except for what is defined to extend the tcpConnTable > has a server's local IP Address and port as the first indexes. > I did this to enable representation of the tables at > either a management application or to enable multi-tn3270(e) > Server environments. > > A question for all those who are reading this is does any one > know of a TN3270 Server implementation that can be configured > to listen on multiple ports at the same time or an implementation > where two Telnet Servers in the same host can listen on the same > port? > > I tried to stay away from using integer indexes based on the > experiences of the ifMib working group. >2. I don't yet have the equivalent of: > tn3270sCpuCard <= consider sysDescr to be equivalent from the > local server's system group. > tn3270sGlobalGenericPool > tn3270sGlobalStartupTime <= I have a object that keeps TimeTicks > from when a server was started. I may change > this to a TimeAndDate object. Not sure if > this plus tn3270sRunningTime is necessary. > tn3270sStatsSpareSess <= I have a total count of the number > of available LUs and a inUseCnt. Figured the > difference is equivalent to this. > tn3270sStatsInBoundChains, OutBoundChains, SampledHostResponses, > sampledHostResponseTime, SampledClientResponses, > SampledClientResponseTime <= I assumed that there are tools > available to monitor the SNA side and that > server didn't need to keep RU counts. I'm > also not sure of the method of sampling > response times. A Response Time Monitoring > MIB is being worked on by myself, Bob Moore > and Katie Lee. I think we should re-visit > these after it has been submitted to the > working group for consideration. > tn3270sPuTable <= In discussing the first MIB submitted with some > Gateway Server implementers I learned that not > all implementations have access to the PU > information so I left it out of the base MIB. >3. IP to LU mappings are hard to generalize. I will submit something > that we all can pick a part. I'm thinking that IP Address to > LU/Prt Mappings is the primary search path from a Server > prospective and that a management application may prefer to > map LU/Prt to IP Address. Disagreement? >4. The level of detail that you provide on a LU is not something > that I have as of yet. I also don't have an equivalent of the > tn3270sPuNailTable nor tn3270sIpNailTable. >5. The tables in the base MIB that I will resubmit were modeled > with RowStatus objects to enable remote creation/deletion. > >Thanks again for a look at your MIB. There actually was a fair amount >of overlap with what I have. I will re-post the base MIB in a day or >two so that we all can pick it a part, compare it to yours, and >decide were to go from there. > >Thanks, Ken >   Received: from cnri by ietf.org id aa04760; 24 Jun 97 8:37 EDT Received: from list.nih.gov (list.nih.gov [165.112.130.6]) by cnri.reston.va.us (8.8.5/8.7.3) with ESMTPid IAA13466 for ; Tue, 24 Jun 1997 08:36:04 -0400 (EDT) Received: from list.nih.gov (terrific.net.nih.gov [165.112.130.6]) by list.nih.gov (8.8.5/8.8.5) with ESMTP id IAA28229; Tue, 24 Jun 1997 08:28:11 -0400 (EDT) Received: from LIST.NIH.GOV by LIST.NIH.GOV (LISTSERV-TCP/IP release 1.8c) with spool id 2802291 for TN3270E@LIST.NIH.GOV; Tue, 24 Jun 1997 08:28:08 -0400 Received: from tai.cisco.com (tai.cisco.com [171.69.160.33]) by list.nih.gov (8.8.5/8.8.5) with ESMTP id IAA28216 for ; Tue, 24 Jun 1997 08:28:07 -0400 (EDT) Received: from foobar.cisco.com (sj-dial-3-37.cisco.com [171.68.179.38]) by tai.cisco.com (8.8.4-Cisco.1/8.6.5) with SMTP id IAA10334; Tue, 24 Jun 1997 08:27:15 -0400 (EDT) Date: Tue, 24 Jun 1997 08:21:41 -0500 (Central Daylight Time) From: Michael Boe Reply-To: Michael Boe Subject: RE: To: Nick Weeds cc: "'kennethw@VNET.IBM.COM'" , 'TN3270E list' Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII Sender: owner-tn3270e@list.nih.gov >Ken, > >You asked about TN3270 implementations which can listen on multiple >ports. We ship a TN3270 gateway which provides this capability. Also, >if the TN3270 gateway is configured to use the standard TELNET port >(23), the TN3270 gateway will hand off the connection to the standard >TELNET daemon if the client is not a TN3270 client. And the cisco implementation can listen on multiple ports and multiple IP addresses. /msb > > Nick. > >>---------- >>From: kennethw@VNET.IBM.COM[SMTP:kennethw@VNET.IBM.COM] >>Sent: 24 June 1997 03:00 >>To: tn3270e@LIST.NIH.GOV >>Cc: ragrawal@cisco.com >>Subject: Re: >> >>Rajesh, >> Thanks a lot for a copy of the your tn3270 MIB. I just finished >>a base version of the tn3270e-mib that has been discussed. I need >>to put it a side for the night and make some more revisions before >>rewriting the internet-draft text and resubmitting to the list >>for comments. Some quick comparisons between what I now have and >>what you sent: >> >>1. The new MIB that I plan on resubmitting is a series of tables >> that except for what is defined to extend the tcpConnTable >> has a server's local IP Address and port as the first indexes. >> I did this to enable representation of the tables at >> either a management application or to enable multi-tn3270(e) >> Server environments. >> >> A question for all those who are reading this is does any one >> know of a TN3270 Server implementation that can be configured >> to listen on multiple ports at the same time or an implementation >> where two Telnet Servers in the same host can listen on the same >> port? >> >> I tried to stay away from using integer indexes based on the >> experiences of the ifMib working group. >>2. I don't yet have the equivalent of: >> tn3270sCpuCard <= consider sysDescr to be equivalent from the >> local server's system group. >> tn3270sGlobalGenericPool >> tn3270sGlobalStartupTime <= I have a object that keeps TimeTicks >> from when a server was started. I may change >> this to a TimeAndDate object. Not sure if >> this plus tn3270sRunningTime is necessary. >> tn3270sStatsSpareSess <= I have a total count of the number >> of available LUs and a inUseCnt. Figured the >> difference is equivalent to this. >> tn3270sStatsInBoundChains, OutBoundChains, SampledHostResponses, >> sampledHostResponseTime, SampledClientResponses, >> SampledClientResponseTime <= I assumed that there are tools >> available to monitor the SNA side and that >> server didn't need to keep RU counts. I'm >> also not sure of the method of sampling >> response times. A Response Time Monitoring >> MIB is being worked on by myself, Bob Moore >> and Katie Lee. I think we should re-visit >> these after it has been submitted to the >> working group for consideration. >> tn3270sPuTable <= In discussing the first MIB submitted with some >> Gateway Server implementers I learned that not >> all implementations have access to the PU >> information so I left it out of the base MIB. >>3. IP to LU mappings are hard to generalize. I will submit something >> that we all can pick a part. I'm thinking that IP Address to >> LU/Prt Mappings is the primary search path from a Server >> prospective and that a management application may prefer to >> map LU/Prt to IP Address. Disagreement? >>4. The level of detail that you provide on a LU is not something >> that I have as of yet. I also don't have an equivalent of the >> tn3270sPuNailTable nor tn3270sIpNailTable. >>5. The tables in the base MIB that I will resubmit were modeled >> with RowStatus objects to enable remote creation/deletion. >> >>Thanks again for a look at your MIB. There actually was a fair amount >>of overlap with what I have. I will re-post the base MIB in a day or >>two so that we all can pick it a part, compare it to yours, and >>decide were to go from there. >> >>Thanks, Ken >>   Received: from cnri by ietf.org id aa07999; 24 Jun 97 10:53 EDT Received: from list.nih.gov (list.nih.gov [165.112.130.6]) by cnri.reston.va.us (8.8.5/8.7.3) with ESMTPid KAA00311 for ; Tue, 24 Jun 1997 10:52:19 -0400 (EDT) Received: from list.nih.gov (terrific.net.nih.gov [165.112.130.6]) by list.nih.gov (8.8.5/8.8.5) with ESMTP id KAA03368; Tue, 24 Jun 1997 10:46:26 -0400 (EDT) Received: from LIST.NIH.GOV by LIST.NIH.GOV (LISTSERV-TCP/IP release 1.8c) with spool id 2803688 for TN3270E@LIST.NIH.GOV; Tue, 24 Jun 1997 10:46:23 -0400 Received: from ntrlink (ntrlink.hq.interlink.com [138.42.128.44]) by list.nih.gov (8.8.5/8.8.5) with SMTP id KAA03345 for ; Tue, 24 Jun 1997 10:46:18 -0400 (EDT) Received: from fab.md.interlink.com by ntrlink (SMI-8.6/SMI-SVR4) id HAA29396; Tue, 24 Jun 1997 07:49:45 -0700 Received: by fab.md.interlink.com (SMI-8.6/SMI-SVR4) id KAA01201; Tue, 24 Jun 1997 10:46:34 -0400 Date: Tue, 24 Jun 1997 10:46:34 -0400 From: Fred Bohle Message-Id: <199706241446.KAA01201@fab.md.interlink.com> To: kennethw@vnet.ibm.com, NPW@datcon.co.uk Subject: RE: Cc: tn3270e@list.nih.gov X-Sun-Charset: US-ASCII Sender: owner-tn3270e@list.nih.gov Ken, > > You asked about TN3270 implementations which can listen on multiple > ports. We ship a TN3270 gateway which provides this capability. Also, > if the TN3270 gateway is configured to use the standard TELNET port > (23), the TN3270 gateway will hand off the connection to the standard > TELNET daemon if the client is not a TN3270 client. > We also have a Telnet which can listen on multiple ports, and are working on a TCP which will support multiple Telnet servers listening on the SAME port. Fred   Received: from cnri by ietf.org id aa08767; 24 Jun 97 11:26 EDT Received: from list.nih.gov (list.nih.gov [165.112.130.6]) by cnri.reston.va.us (8.8.5/8.7.3) with ESMTPid LAA00407 for ; Tue, 24 Jun 1997 11:25:06 -0400 (EDT) Received: from list.nih.gov (terrific.net.nih.gov [165.112.130.6]) by list.nih.gov (8.8.5/8.8.5) with ESMTP id LAA04905; Tue, 24 Jun 1997 11:20:22 -0400 (EDT) Received: from LIST.NIH.GOV by LIST.NIH.GOV (LISTSERV-TCP/IP release 1.8c) with spool id 2804163 for TN3270E@LIST.NIH.GOV; Tue, 24 Jun 1997 11:20:19 -0400 Received: from VNET.IBM.COM (vnet.ibm.com [204.146.168.194]) by list.nih.gov (8.8.5/8.8.5) with SMTP id LAA04887 for ; Tue, 24 Jun 1997 11:20:16 -0400 (EDT) Received: from RALVM12 by VNET.IBM.COM (IBM VM SMTP V2R3) with BSMTP id 6970; Tue, 24 Jun 97 11:20:13 EDT From: kennethw@vnet.ibm.com Message-Id: <199706241520.LAA04887@list.nih.gov> Date: Tue, 24 Jun 97 11:11:55 EDT To: tn3270e@list.nih.gov cc: NPW@datcon.co.uk, mboe@cisco.com, fab@md.interlink.com, mike_capello@ccmail.orl.lmco.com Subject: RE: TN3270E Server Port Usage Sender: owner-tn3270e@list.nih.gov Thanks for all of the responses. I thought that the requirement for multiple server port usage would occur. Sharing a port between TN3270E Servers is also a requirement that I accept with respect to the modeling of the MIB. Currently, the MIB has most of its tables index by: tn3270eSrvrConfIpAddr IpAddress AND tn3270eSrvrConfPort Integer32 tn3270eSrvrConfIpAddr is any local IP Address that can be used to reach a particular TN3270E Server. There are a couple of approaches that can be used to handle the sharing problem: 1. Require that a entry be added for each port used by a TN3270E server. A TN3270E Server that was listening on multiple ports would have a tn3270eSrvrConfAdminStatus object for example for each port. The only problem with this approach is that it doesn't allow multiple instances of a server to share the same port. 2. Instead of using the local port use an integer index that would have the requirement of being unique between multi-server instances. The indexes would be: tn3270eSrvrConfIpAddr IpAddress AND tn3270eSrvrConfsIndex Integer32 Two options then would exist as to handling port usage: A. Create a port assignment table to show which ports are assigned to which servers. B. Add an object to the tn3270eSrvrConfTable to show port and require that multiple port usage create unique entries in this table. I'm thinking that 2.A is the best choice. Opinions? I plan on going this way unless someone objects. I will post an informal copy of the MIB module in a few hours after I get it to cleanly compile so that you can all start looking at it while I work on the text. Ken   Received: from cnri by ietf.org id aa16198; 24 Jun 97 15:00 EDT Received: from list.nih.gov (list.nih.gov [165.112.130.6]) by cnri.reston.va.us (8.8.5/8.7.3) with ESMTPid OAA01507 for ; Tue, 24 Jun 1997 14:59:47 -0400 (EDT) Received: from list.nih.gov (terrific.net.nih.gov [165.112.130.6]) by list.nih.gov (8.8.5/8.8.5) with ESMTP id OAA11057; Tue, 24 Jun 1997 14:54:49 -0400 (EDT) Received: from LIST.NIH.GOV by LIST.NIH.GOV (LISTSERV-TCP/IP release 1.8c) with spool id 2805902 for TN3270E@LIST.NIH.GOV; Tue, 24 Jun 1997 14:54:46 -0400 Received: from VNET.IBM.COM (vnet.ibm.com [204.146.168.194]) by list.nih.gov (8.8.5/8.8.5) with SMTP id OAA11039 for ; Tue, 24 Jun 1997 14:54:44 -0400 (EDT) Received: from RALVM12 by VNET.IBM.COM (IBM VM SMTP V2R3) with BSMTP id 7132; Tue, 24 Jun 97 14:54:44 EDT From: kennethw@vnet.ibm.com Message-Id: <199706241854.OAA11039@list.nih.gov> Date: Tue, 24 Jun 97 14:48:10 EDT To: tn3270e@list.nih.gov cc: dbolton@cisco.com Subject: Re: > Sender: owner-tn3270e@list.nih.gov Derek, >> A question for all those who are reading this is does any one >> know of a TN3270 Server implementation that can be configured >> to listen on multiple ports at the same time >Yes - ours. PUs can be grouped onto different ports, so by >selecting a target port the client selects a subset of the PUs. >There are many uses for this. E.g. the PUs could have different >LUGROUPs at VTAM. I created a port table to configure which ports that a server is using as I described in my last note to the list. Handling restricting resource assignments based on client port selection is a requirement that I will try to accommodate. I've attempted to do this in a generic way such that servers that don't do this would use a port value of 0 to imply no restriction. I've created two tables to define IP Groups and Resource Pools. A Resource Pool is a collection of LU/Printer resources. The Resource Pool table provides objects to map the entry to a IP Group and restrict it to a particular client port selection. Two additional tables were defined, tn3270eResMapTable and tn3270eIpMapTable, to provide actual mappings. The IP Groups and Resource Pool tables are optional. When an entry is added to the tn3270eResPoolTable entries are suppose to be automatically created in the tn3270eIpMapTable and tn3270eResMapTable. Deletion works in a similar fashion. The tn3270eIpMapTable and tn3270eResMapTable can be used directly as oppose to doing IP Groupings and Resource Pool definitions. My intent is to provide flexibility in how a server can configure this in order to cover most implementations. >> tn3270sStatsSpareSess <= I have a total count of the number >> of available LUs and a inUseCnt. Figured the >> difference is equivalent to this. >We made the same subtle mistake at first. If a PU supports >ANS=CONT then it can find itself in the position of having >active LU-LU sessions but no SSCP-PU session (during SSCP takeover). >In this state, the PU does not contribute to total usable LUs >(no new clients can be accepted in this state) but does want to >count its active sessions as "in use". Taking the difference to >produce "spare LUs" gets the wrong answer. OKay, I will add this in. I'm thinking of the three different counts (total, inUse, spare) for both Resource types: LU and Printer. >> tn3270sPuTable <= In discussing the first MIB submitted with some >> Gateway Server implementers I learned that not >> all implementations have access to the PU >> information so I left it out of the base MIB. >OK, but where PU info is available we need some way to tie the >MIBs together. In the Cisco CIP TN3270 Server case, we also support >the NAU MIB. The tn3270sPuTable parallels this (same indices) so that >tn3270-specific config of the PUs can be associated with the NAU MIB >entries. In current MIB that I will be posting I don't as of yet have a PU Index element. Please take a look at the posting and let me know what you want to recommend. A possibility is that I add a PU Index object to these tables and state that it is optional. Another is that you can contribute to what we were calling a Host oriented MIB with a series of table definitions and add the indexes in what you need. If we go this way we can call this the TN3270E Supplemental MIB as oppose to a Host MIB. Ken   Received: from cnri by ietf.org id aa16538; 24 Jun 97 15:13 EDT Received: from list.nih.gov (list.nih.gov [165.112.130.6]) by cnri.reston.va.us (8.8.5/8.7.3) with ESMTPid PAA01562 for ; Tue, 24 Jun 1997 15:12:51 -0400 (EDT) Received: from list.nih.gov (terrific.net.nih.gov [165.112.130.6]) by list.nih.gov (8.8.5/8.8.5) with ESMTP id PAA11493; Tue, 24 Jun 1997 15:05:06 -0400 (EDT) Received: from LIST.NIH.GOV by LIST.NIH.GOV (LISTSERV-TCP/IP release 1.8c) with spool id 2806023 for TN3270E@LIST.NIH.GOV; Tue, 24 Jun 1997 15:05:03 -0400 Received: from VNET.IBM.COM (vnet.ibm.com [204.146.168.194]) by list.nih.gov (8.8.5/8.8.5) with SMTP id PAA11480 for ; Tue, 24 Jun 1997 15:05:01 -0400 (EDT) Received: from RALVM12 by VNET.IBM.COM (IBM VM SMTP V2R3) with BSMTP id 7603; Tue, 24 Jun 97 15:04:59 EDT From: kennethw@vnet.ibm.com Message-Id: <199706241905.PAA11480@list.nih.gov> Date: Tue, 24 Jun 97 14:51:43 EDT To: tn3270e@list.nih.gov Subject: New Base MIB Module Sender: owner-tn3270e@list.nih.gov I've appended to this note a current copy of a base tn3270e MIB. It looks very different from the prior posting. Some high level changes: 1. Removed the Host unique objects and reorganized to focus on the common set of objects between TN3270/TN3270E Server architectures. 2. Added a new object, tn3270eSrvrConfProtoSupported, to reflect the TN3270E functions that a server can support. tn3270eTcpConnProto was modified to reflect the negotiated functions on a session basis. The tn3270eTcpConnTable was modified to use the indexes of the tcpConnTable and not AUGMENT it since the relationship between these tables is sparse not one-to-one. Also, the objects that were not available at the server layer were removed. 3. The objects at the beginning of the MIB were restructured to be table entry elements. I did this in order to create a table that could be used at both the manager side as well as at a TN3270 Server instance. If there are objections to this I'm willing to change it back! Take a look at tn3270eSrvrConfTable. 4. I attempted to redefine the three objects that previously were intended for TIMEMARK processing to be more generic to allow use of a NOP instead of a TIMEMARK subcommand. The three new objects are: tn3270eSrvrConfActivityCheck tn3270eSrvrConfActivityTimeout tn3270eSrvrConfActivityInterval 5. Created a tn3270eSrvrStatsTable to keep track of global Server statistics. 6. Create four tables: tn3270eIpGroupTable, tn3270eResPoolTable, tn3270eResMapTable and tn3270eIpMapTable, to provide for defining these mappings. Is any one interested in adding: - An LU in use threshold to monitor the number of available LUs and generate a TRAP when the threshold is reached. If we do this then I would recommend a resolution threshold to indicate that the available number of LUs has fallen below an acceptable level. - negotiated terminalType to the tn3270eTcpConnTable. The appended MIB is my first draft at what we have discussed. I would appreciate feedback while I start work on a new internet-draft submission. It compiles but that all at this time. Ken ---------------------------------------------------------------------- TN3270E-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, BITS, Unsigned32, experimental, Integer32, IpAddress, TimeTicks, Counter32 FROM SNMPv2-SMI TEXTUAL-CONVENTION, RowStatus, DisplayString FROM SNMPv2-TC MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF tcpConnLocalAddress, tcpConnLocalPort, tcpConnRemAddress, tcpConnRemPort FROM TCP-MIB ; tn3270eMIB MODULE-IDENTITY LAST-UPDATED "9706200000Z" -- June 20, 1997 ORGANIZATION "TN3270E Working Group" CONTACT-INFO "Kenneth White (kennethw@vnet.ibm.com) IBM Corp." DESCRIPTION "This module defines a portion of the management information base (MIB) for managing TN3270E Servers" -- Need an experimental OID from IANA ::= { experimental 2001 } -- *************************************************************** -- Textual Conventions -- *************************************************************** ResourceType ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "The type of resource defined by a Resource Pool. Refer to tn3270eResPoolTable." SYNTAX INTEGER { other(0), lu(1), printer(2) } Tn3270Functions ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "This textual convention is intended to reflect the current set of TN3270 and TN3270E functions that can be negiotiated between a server and its client: RFC856 transmitBinary The sender of this command REQUESTS permission to begin transmitting, or confirms that it will now begin transmitting characters which are to be interpreted as 8 bits of binary data by the receiver of the data. RFC820 timeMark The sender of this command REQUESTS that the receiver of this command return a WILL TIMING-MARK in the data stream at the 'appropriate place' ... RFC885 endOfRecord The sender of this command requests permission to begin transmission of the Telnet END-OF-RECORD (EOR) code when transmitting data characters, or the sender of this command confirms it will now begin transmission of EORs with transmitted data characters. RFC1091 terminalType Sender is willing to send terminal type information in a subsequent sub-negotiation. RFC1041 tn3270Regime Sender is willing to send list of supported 3270 Regimes in a subsequent sub-negotiation. RFC1647 scsCtlCodes (Printer sessions only). Allows the use of the SNA Character Stream (SCS) and SCS control codes on the session. SCS is used with LU type 1 SNA sessions. dataStreamCtl (Printer sessions only). Allows the use of the standard 3270 data stream. This corresponds to LU type 3 SNA sessions. responses Provides support for positive and negative response handling. Allows the server to reflect to the client any and all definite, exception, and no response requests sent by the host application. bindImage Allows the server to send the SNA Bind image and Unbind notification to the client. sysreq Allows the client and server to emulate some (or all, depending on the server) of the functions of the SYSREQ key in an SNA environment." SYNTAX BITS { transmitBinary(0),-- rfc856 timemark(1), -- rfc860 endOfRecord(2), -- rfc885 terminalType(3), -- rfc1091 tn3270Regime(4), -- rfc1041 scsCtlCodes(5), -- rfc1647 dataStreamCtl(6), -- rfc1647 responses(7), -- rfc1647 bindImage(8), -- rfc1647 sysreq(9) -- rfc1647 } DeviceTypes ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "This textual convention defines the list of device types that can be set as defined by RFC 1647." SYNTAX INTEGER { -- terminals unknown(0), ibm3278d2(1), -- (24 row x 80 col display) ibm3278d2E(2), -- (24 row x 80 col display) ibm3278d3(3), -- (32 row x 80 col display) ibm3278d3E(4), -- (32 row x 80 col display) ibm3278d4(5), -- (43 row x 80 col display) ibm3278d4E(6), -- (43 row x 80 col display) ibm3278d5(7), -- (27 row x 132 col display) ibm3278d5E(8), -- (27 row x 132 col display) ibmDynamic(9), -- (no pre-defined display size) ibm3287d1(10) -- printers } -- Top-level structure of the MIB tn3270eNotifications OBJECT IDENTIFIER ::= { tn3270eMIB 0 } tn3270eObjects OBJECT IDENTIFIER ::= { tn3270eMIB 1 } tn3270eConformance OBJECT IDENTIFIER ::= { tn3270eMIB 3 } -- MIB Objects tn3270eSrvrConfTable OBJECT-TYPE SYNTAX SEQUENCE OF Tn3270eSrvrConfEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table defines the configuration elements for TN3270 Servers. The number of entries in this table is expected to vary depending on the location of the table. A particular TN3270 Server is expected to have a single entry. Modeling of the configuration elements as a table enable use of the table by management applications as well as allowing multiple TN3270 Servers to exist at the same host." ::= { tn3270eObjects 1 } tn3270eSrvrConfEntry OBJECT-TYPE SYNTAX Tn3270eSrvrConfEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Definition of the configuration elements for a single TN3270 Server." INDEX { tn3270eSrvrConfIpAddr, tn3270eSrvrConfIndex } ::= { tn3270eSrvrConfTable 1 } Tn3270eSrvrConfEntry ::= SEQUENCE { tn3270eSrvrConfIpAddr IpAddress, tn3270eSrvrConfIndex Unsigned32, tn3270eSrvrConfInactivityTimer Unsigned32, tn3270eSrvrConfActivityCheck INTEGER, tn3270eSrvrConfActivityTimeout Unsigned32, tn3270eSrvrConfActivityInterval Unsigned32, tn3270eSrvrConfProtoSupported Tn3270Functions, tn3270eSrvrConfAdminStatus INTEGER, tn3270eSrvrConfOperStatus INTEGER, tn3270eSrvrConfSessionTermState INTEGER, tn3270eSrvrConfSrvrType INTEGER, tn3270eSrvrConfRowStatus RowStatus } tn3270eSrvrConfIpAddr OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS not-accessible STATUS current DESCRIPTION "Indicates the local IP Address associated with a TN3270 Server. A value of 0 is allowed when the entry exists at a single TN3270 Server instance host." ::= { tn3270eSrvrConfEntry 1 } tn3270eSrvrConfIndex OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS not-accessible STATUS current DESCRIPTION "Indicates the instance of a TN3270/TN3270E Server that exists at the IP Host pointed to by tn3270eSrvrConfIpAddr." ::= { tn3270eSrvrConfEntry 2 } tn3270eSrvrConfInactivityTimer OBJECT-TYPE SYNTAX Unsigned32 (0..99999999) UNITS "seconds" MAX-ACCESS read-create STATUS current DESCRIPTION "The inactivity time-out specified in seconds. When a connection has been inactive for the number of seconds specified by this object it is closed. The default of 0 means no inactivity time-out." DEFVAL { 0 } ::= { tn3270eSrvrConfEntry 3 } tn3270eSrvrConfActivityCheck OBJECT-TYPE SYNTAX INTEGER { noCheck(0), timeMark(1), nop(2) } MAX-ACCESS read-create STATUS current DESCRIPTION "This object is intended to enable either timemark or nop processing." DEFVAL { noCheck } ::= { tn3270eSrvrConfEntry 4 } tn3270eSrvrConfActivityTimeout OBJECT-TYPE SYNTAX Unsigned32 UNITS "seconds" MAX-ACCESS read-create STATUS current DESCRIPTION "The TIMEMARK or NOP processing time-out specified in seconds." DEFVAL { 600 } -- 10 minutes ::= { tn3270eSrvrConfEntry 5 } tn3270eSrvrConfActivityInterval OBJECT-TYPE SYNTAX Unsigned32 UNITS "seconds" MAX-ACCESS read-create STATUS current DESCRIPTION "The scan interval to be used by the Telnet Server. TIMEMARK or NOP processing scans the Telnet sessions on the interval provided by this object looking for sessions that have been idle for more than the value provided by tn3270eSrvrConfActivityTimeout." DEFVAL { 120 } -- 2 minutes ::= { tn3270eSrvrConfEntry 6 } tn3270eSrvrConfProtoSupported OBJECT-TYPE SYNTAX Tn3270Functions MAX-ACCESS read-only STATUS current DESCRIPTION "This object indicates the TN3270 functions supported by a TN3270 Server." DEFVAL { { scsCtlCodes, dataStreamCtl, responses, bindImage, sysreq } } ::= { tn3270eSrvrConfEntry 7 } tn3270eSrvrConfAdminStatus OBJECT-TYPE SYNTAX INTEGER { up(1), down(2), stopImmediate(3) } MAX-ACCESS read-create STATUS current DESCRIPTION "The desired state of the Telnet Server. The stopImmediate state is intended to enable Servers to gracefully terminate via down or to terminate immediate without ending its client connections. There is no requirement for support of stopImmediate." ::= { tn3270eSrvrConfEntry 8 } tn3270eSrvrConfOperStatus OBJECT-TYPE SYNTAX INTEGER { up(1), down(2) } MAX-ACCESS read-only STATUS current DESCRIPTION "The current operational state of the Telnet Server." ::= { tn3270eSrvrConfEntry 9 } tn3270eSrvrConfSessionTermState OBJECT-TYPE SYNTAX INTEGER { terminate(1), luSessionPend(2), queueSession(3) } MAX-ACCESS read-create STATUS current DESCRIPTION "The current state for determining what happens when Telnet connection terminates: terminate(1) => Terminate connection. luSessionPend(2) => Allows the client's session to revert to their Default Application upon termination of their Telnet connection. queueSession(3) => ????" DEFVAL { terminate } ::= { tn3270eSrvrConfEntry 10 } tn3270eSrvrConfSrvrType OBJECT-TYPE SYNTAX INTEGER { unknown(0), host(1), gateway(2) } MAX-ACCESS read-only STATUS current DESCRIPTION "This object indicates the type of TN3270/TN3270E Server. The existence of MIB tables and objects that will be defined by follow-on MIBs may be predicated on whether the TN3270/TN3270E Server is local to the same host as the secondary LU used to attach the IP client into a SNA network." ::= { tn3270eSrvrConfEntry 11 } tn3270eSrvrConfRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "This object allows entries to be created and deleted in the tn3270eSrvrConfTable. Creating an entry in this table at a management application informs enable that application to manage the associating TN3270 Server. Deleting an entry removes it from that application's management domain. A server based implementation of this table may chose to not support creation or deletion of its (probably only) entry in this table via this object. An entry in this table is deleted by setting this object to destroy(6)." REFERENCE "RFC 1903, 'Textual Conventions for version 2 of the Simple Network Management Protocol (SNMPv2).'" ::= { tn3270eSrvrConfEntry 12 } tn3270eSrvrPortTable OBJECT-TYPE SYNTAX SEQUENCE OF Tn3270eSrvrPortEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table defines the ports associated with TN3270/ TN3270E Servers." ::= { tn3270eObjects 2 } tn3270eSrvrPortEntry OBJECT-TYPE SYNTAX Tn3270eSrvrPortEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Definition of a single server port assignment." INDEX { tn3270eSrvrConfIpAddr, tn3270eSrvrConfIndex, tn3270eSrvrPort } ::= { tn3270eSrvrPortTable 1 } Tn3270eSrvrPortEntry ::= SEQUENCE { tn3270eSrvrPort Unsigned32, tn3270eSrvrPortRowStatus RowStatus } tn3270eSrvrPort OBJECT-TYPE SYNTAX Unsigned32 (0..65535) MAX-ACCESS not-accessible STATUS current DESCRIPTION "Indicates a port assigned to a server." ::= { tn3270eSrvrPortEntry 1 } tn3270eSrvrPortRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "This object allows entries to be created and deleted in the tn3270eSrvrPortTable. An entry in this table is deleted by setting this object to destroy(6)." REFERENCE "RFC 1903, 'Textual Conventions for version 2 of the Simple Network Management Protocol (SNMPv2).'" ::= { tn3270eSrvrPortEntry 2 } tn3270eSrvrStatsTable OBJECT-TYPE SYNTAX SEQUENCE OF Tn3270eSrvrStatsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table defines a set of statistics concerning global TN3270 Server performance." ::= { tn3270eObjects 3 } tn3270eSrvrStatsEntry OBJECT-TYPE SYNTAX Tn3270eSrvrStatsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Collection of a set of statistic objects for a single TN3270 Server." INDEX { tn3270eSrvrConfIpAddr, tn3270eSrvrConfIndex } ::= { tn3270eSrvrStatsTable 1 } Tn3270eSrvrStatsEntry ::= SEQUENCE { tn3270eSrvrStatsUpTime TimeTicks, tn3270eSrvrStatsMaxLus Integer32, tn3270eSrvrStatsLusInUse Integer32, tn3270eSrvrStatsSpareLus Integer32, tn3270eSrvrStatsMaxPtrs Integer32, tn3270eSrvrStatsPtrsInUse Integer32, tn3270eSrvrStatsSparePtrs Integer32, tn3270eSrvrStatsConnectsIn Counter32, tn3270eSrvrStatsConnRejects Counter32, tn3270eSrvrStatsDisconnects Counter32 } tn3270eSrvrStatsUpTime OBJECT-TYPE SYNTAX TimeTicks MAX-ACCESS read-only STATUS current DESCRIPTION "Indicates the amount of time that a particular TN3270 has be active. This is total time since the server was started and is not reset on tn3270eSrvrConfOperStatus." ::= { tn3270eSrvrStatsEntry 1 } tn3270eSrvrStatsMaxLus OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "Indicates the maximum number of LUs for use by a TN3270 Server." ::= { tn3270eSrvrStatsEntry 2 } tn3270eSrvrStatsLusInUse OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "Indicates the current number of LUs in use by a TN3270 Server." ::= { tn3270eSrvrStatsEntry 3 } tn3270eSrvrStatsSpareLus OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "Indicates the number of free LUs for a particular TN3270 Server." ::= { tn3270eSrvrStatsEntry 4 } tn3270eSrvrStatsMaxPtrs OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "Indicates the maximum number of Printer Resources for use by a TN3270 Server." ::= { tn3270eSrvrStatsEntry 5 } tn3270eSrvrStatsPtrsInUse OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "Indicates the current number of Printer Resources in use by a TN3270 Server." ::= { tn3270eSrvrStatsEntry 6 } tn3270eSrvrStatsSparePtrs OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "Indicates the number of free Printer Resources for a particular TN3270 Server." ::= { tn3270eSrvrStatsEntry 7 } tn3270eSrvrStatsConnectsIn OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Indicates the number of client connections received by a TN3270 Server." ::= { tn3270eSrvrStatsEntry 8 } tn3270eSrvrStatsConnRejects OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Indicates the number of client connections rejected during connection setup." ::= { tn3270eSrvrStatsEntry 9 } tn3270eSrvrStatsDisconnects OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Indicates the number of client connections disconnected by a TN3270 Server." ::= { tn3270eSrvrStatsEntry 10 } tn3270eIpGroupTable OBJECT-TYPE SYNTAX SEQUENCE OF Tn3270eIpGroupEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table defines IP Address groupings for use by the Telnet Server." ::= { tn3270eObjects 4 } tn3270eIpGroupEntry OBJECT-TYPE SYNTAX Tn3270eIpGroupEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Definition of a single IP Address entry. All entries with the same 1st index, tn3270eIpGroupName are considered to be in the same IP Group." INDEX { tn3270eSrvrConfIpAddr, tn3270eSrvrConfIndex, tn3270eIpGroupName, tn3270eIpGroupIpAddress } ::= { tn3270eIpGroupTable 1 } Tn3270eIpGroupEntry ::= SEQUENCE { tn3270eIpGroupName DisplayString, tn3270eIpGroupIpAddress IpAddress, tn3270eIpGroupSubnetMask IpAddress, tn3270eIpGroupRowStatus RowStatus } tn3270eIpGroupName OBJECT-TYPE SYNTAX DisplayString (SIZE(1..8)) MAX-ACCESS not-accessible STATUS current DESCRIPTION "The name of a IP Group." ::= { tn3270eIpGroupEntry 1 } tn3270eIpGroupIpAddress OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS not-accessible STATUS current DESCRIPTION "The IP Address of a member of a IP Group." ::= { tn3270eIpGroupEntry 2 } tn3270eIpGroupSubnetMask OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-create STATUS current DESCRIPTION "The corresponding subnet mask associated with tn3270eIpGroupIpAddress. A single IP Address is represented by having this object contain the value of 255.255.255.255." ::= { tn3270eIpGroupEntry 3 } tn3270eIpGroupRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "This object allows entries to be created and deleted in the tn3270eIpGroupTable. An entry in this table is deleted by setting this object to destroy(6)." REFERENCE "RFC 1903, 'Textual Conventions for version 2 of the Simple Network Management Protocol (SNMPv2).'" ::= { tn3270eIpGroupEntry 4 } tn3270eResPoolTable OBJECT-TYPE SYNTAX SEQUENCE OF Tn3270eResPoolEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table defines Resource groupings and using the term pool as defined by RFC 1647." ::= { tn3270eObjects 5 } tn3270eResPoolEntry OBJECT-TYPE SYNTAX Tn3270eResPoolEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Definition of a single Resource Pool member. All entries with the same 1st index, tn3270eResPoolName are considered to be in the same Pool." INDEX { tn3270eSrvrConfIpAddr, tn3270eSrvrConfIndex, tn3270eResPoolName, tn3270eResPoolElementName } ::= { tn3270eResPoolTable 1 } Tn3270eResPoolEntry ::= SEQUENCE { tn3270eResPoolName DisplayString, tn3270eResPoolElementName DisplayString, tn3270eResPoolIpGroupName DisplayString, tn3270eResPoolElementType ResourceType, tn3270eResPoolClientPort Unsigned32, tn3270eResPoolRowStatus RowStatus } tn3270eResPoolName OBJECT-TYPE SYNTAX DisplayString (SIZE(1..255)) MAX-ACCESS not-accessible STATUS current DESCRIPTION "The name of a Resource Pool.." ::= { tn3270eResPoolEntry 1 } tn3270eResPoolElementName OBJECT-TYPE SYNTAX DisplayString (SIZE(1..8)) MAX-ACCESS not-accessible STATUS current DESCRIPTION "The Name of a member of a Resource Pool." ::= { tn3270eResPoolEntry 2 } tn3270eResPoolIpGroupName OBJECT-TYPE SYNTAX DisplayString (SIZE(1..8)) MAX-ACCESS read-create STATUS current DESCRIPTION "The name of a IP Group to map a Resource Element to." ::= { tn3270eResPoolEntry 3 } tn3270eResPoolElementType OBJECT-TYPE SYNTAX ResourceType MAX-ACCESS read-create STATUS current DESCRIPTION "The type of the entity in a Resource Pool." ::= { tn3270eResPoolEntry 4 } tn3270eResPoolClientPort OBJECT-TYPE SYNTAX Unsigned32 (0..65535) MAX-ACCESS read-create STATUS current DESCRIPTION "If specified this a pool to a specific client port." ::= { tn3270eResPoolEntry 5 } tn3270eResPoolRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "This object allows entries to be created and deleted in the tn3270eResPoolTable. An entry in this table is deleted by setting this object to destroy(6)." REFERENCE "RFC 1903, 'Textual Conventions for version 2 of the Simple Network Management Protocol (SNMPv2).'" ::= { tn3270eResPoolEntry 6 } tn3270eResMapTable OBJECT-TYPE SYNTAX SEQUENCE OF Tn3270eResMapEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table defines Resource Element to IP Address mappings." ::= { tn3270eObjects 6 } tn3270eResMapEntry OBJECT-TYPE SYNTAX Tn3270eResMapEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Definition of the mapping of a Resource Element to a IP Address." INDEX { tn3270eSrvrConfIpAddr, tn3270eSrvrConfIndex, tn3270eResMapClientPort, tn3270eResMapElementName } ::= { tn3270eResMapTable 1 } Tn3270eResMapEntry ::= SEQUENCE { tn3270eResMapClientPort Unsigned32, tn3270eResMapElementName DisplayString, tn3270eResMapIpAddress IpAddress, tn3270eResMapSubnetMask IpAddress, tn3270eResMapElementType ResourceType, tn3270eResMapRowStatus RowStatus } tn3270eResMapClientPort OBJECT-TYPE SYNTAX Unsigned32 (0..65535) MAX-ACCESS not-accessible STATUS current DESCRIPTION "The port that this assignment is restricted to. Note that a value of 0 for this object implies that the assignment is global to all client ports." ::= { tn3270eResMapEntry 1 } tn3270eResMapElementName OBJECT-TYPE SYNTAX DisplayString (SIZE(1..8)) MAX-ACCESS not-accessible STATUS current DESCRIPTION "The Name of a resource element." ::= { tn3270eResMapEntry 2 } tn3270eResMapIpAddress OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-create STATUS current DESCRIPTION "A client IP Address or subnet if tn3270eResMapSubnetMask is set to 255.255.255.255." ::= { tn3270eResMapEntry 3 } tn3270eResMapSubnetMask OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-create STATUS current DESCRIPTION "The corresponding subnet mask associated with tn3270eResMapIpAddress. A single IP Address is represented by having this object contain the value of 255.255.255.255." ::= { tn3270eResMapEntry 4 } tn3270eResMapElementType OBJECT-TYPE SYNTAX ResourceType MAX-ACCESS read-create STATUS current DESCRIPTION "The type of the entity in a Resource Pool." ::= { tn3270eResMapEntry 5 } tn3270eResMapRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "This object allows entries to be created and deleted in the tn3270eResMapTable. Entries in this table should occur automatically when an entry is created in the tn3270eResPoolTable. Deleting an entry in the tn3270eResPoolTable should remove all corresponding entries in this table. The tn3270eResPoolTable is optional. This implies that entries can be added directly to this table." REFERENCE "RFC 1903, 'Textual Conventions for version 2 of the Simple Network Management Protocol (SNMPv2).'" ::= { tn3270eResMapEntry 6 } tn3270eIpMapTable OBJECT-TYPE SYNTAX SEQUENCE OF Tn3270eIpMapEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table defines IP Address to Resource Element mappings." ::= { tn3270eObjects 7 } tn3270eIpMapEntry OBJECT-TYPE SYNTAX Tn3270eIpMapEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Definition of the mapping of a IP Address or Group to a Resource Element." INDEX { tn3270eSrvrConfIpAddr, tn3270eSrvrConfIndex, tn3270eIpMapIpAddress, tn3270eIpMapSubnetMask, tn3270eIpMapClientPort } ::= { tn3270eIpMapTable 1 } Tn3270eIpMapEntry ::= SEQUENCE { tn3270eIpMapIpAddress IpAddress, tn3270eIpMapSubnetMask IpAddress, tn3270eIpMapClientPort Unsigned32, tn3270eIpMapResElementName DisplayString, tn3270eIpMapElementType ResourceType, tn3270eIpMapRowStatus RowStatus } tn3270eIpMapIpAddress OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS not-accessible STATUS current DESCRIPTION "The IP Address of a member of a IP Group." ::= { tn3270eIpMapEntry 1 } tn3270eIpMapSubnetMask OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS not-accessible STATUS current DESCRIPTION "The corresponding subnet mask associated with tn3270eIpGroupIpAddress. A single IP Address is represented by having this object contain the value of 255.255.255.255." ::= { tn3270eIpMapEntry 2 } tn3270eIpMapClientPort OBJECT-TYPE SYNTAX Unsigned32 (0..65535) MAX-ACCESS not-accessible STATUS current DESCRIPTION "The port that this assignment is restricted to. Note that a value of 0 for this object implies that the assignment is global to all client ports." ::= { tn3270eIpMapEntry 3 } tn3270eIpMapResElementName OBJECT-TYPE SYNTAX DisplayString (SIZE(0..8)) MAX-ACCESS read-create STATUS current DESCRIPTION "The Resource Element mapping to IP Address(es)." ::= { tn3270eIpMapEntry 4 } tn3270eIpMapElementType OBJECT-TYPE SYNTAX ResourceType MAX-ACCESS read-create STATUS current DESCRIPTION "The type resource element." ::= { tn3270eIpMapEntry 5 } tn3270eIpMapRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "This object allows entries to be created and deleted in the tn3270eIpMapMapTable. Entries in this table should occur automatically when an entry is created in the tn3270eResPoolTable. Deleting an entry in the tn3270eResPoolTable should remove all corresponding entries in this table. The tn3270eResPoolTable is optional. This implies that entries can be added directly to this table." REFERENCE "RFC 1903, 'Textual Conventions for version 2 of the Simple Network Management Protocol (SNMPv2).'" ::= { tn3270eIpMapEntry 6 } -- Define the set of objects to add to the Tcp Connection Table tn3270eTcpConnTable OBJECT-TYPE SYNTAX SEQUENCE OF Tn3270eTcpConnEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Extends tcpConnTable to support TN3270 and TN3270E performance monitoring." ::= { tn3270eObjects 8 } tn3270eTcpConnEntry OBJECT-TYPE SYNTAX Tn3270eTcpConnEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Provides in formation about a single TN3270/TN3270E session." INDEX { tcpConnLocalAddress, tcpConnLocalPort, tcpConnRemAddress, tcpConnRemPort } ::= { tn3270eTcpConnTable 1 } Tn3270eTcpConnEntry ::= SEQUENCE { tn3270eTcpConnLastActivity TimeTicks, tn3270eTcpConnBytesIn Counter32, tn3270eTcpConnBytesOut Counter32, tn3270eTcpConnTargetAppl DisplayString, tn3270eTcpConnResourceName DisplayString, tn3270eTcpConnResourceType ResourceType, tn3270eTcpConnClientUserId DisplayString, tn3270eTcpConnDeviceType DeviceTypes, tn3270eTcpConnProto Tn3270Functions } tn3270eTcpConnLastActivity OBJECT-TYPE SYNTAX TimeTicks MAX-ACCESS read-only STATUS current DESCRIPTION "The number of 100ths of seconds since this entry was last used." DEFVAL { 0 } ::= { tn3270eTcpConnEntry 1 } tn3270eTcpConnBytesIn OBJECT-TYPE SYNTAX Counter32 UNITS "octets" MAX-ACCESS read-only STATUS current DESCRIPTION "The number of bytes received by the Server from TCP for this connection." ::= { tn3270eTcpConnEntry 2 } tn3270eTcpConnBytesOut OBJECT-TYPE SYNTAX Counter32 UNITS "octets" MAX-ACCESS read-only STATUS current DESCRIPTION "The number of bytes sent to TCP for this connection." ::= { tn3270eTcpConnEntry 3 } tn3270eTcpConnTargetAppl OBJECT-TYPE SYNTAX DisplayString (SIZE(0..8)) MAX-ACCESS read-only STATUS current DESCRIPTION "When the corresponding TCP connection is for a 3172 Telnet session then this object contains the Target VTAM Application name. For gateway server implementations this object will not be known and should be returned as a null OCTET STRING." ::= { tn3270eTcpConnEntry 4 } tn3270eTcpConnResourceName OBJECT-TYPE SYNTAX DisplayString (SIZE(0..8)) MAX-ACCESS read-only STATUS current DESCRIPTION "LU/Print secondary name for connecting a IP Client into a SNA network." ::= { tn3270eTcpConnEntry 5 } tn3270eTcpConnResourceType OBJECT-TYPE SYNTAX ResourceType MAX-ACCESS read-only STATUS current DESCRIPTION "Indicates the type of resource identified by tn3270eTcpConnResourceName." ::= { tn3270eTcpConnEntry 6 } tn3270eTcpConnClientUserId OBJECT-TYPE SYNTAX DisplayString (SIZE(0..8)) MAX-ACCESS read-only STATUS current DESCRIPTION "When the corresponding TCP connection is for a 3172 Telnet session then this object contains the Client's userid." ::= { tn3270eTcpConnEntry 7 } tn3270eTcpConnDeviceType OBJECT-TYPE SYNTAX DeviceTypes MAX-ACCESS read-only STATUS current DESCRIPTION "Indicates the device type if negiotiated with client." ::= { tn3270eTcpConnEntry 8 } tn3270eTcpConnProto OBJECT-TYPE SYNTAX Tn3270Functions MAX-ACCESS read-only STATUS current DESCRIPTION "This flag will indicates which of the TN3270 and TN3270E functions that are supported by the Server was negioted with a client. Refer to tn3270eSrvrConfProtoSupported." ::= { tn3270eTcpConnEntry 9 } -- Conformance Definitions tn3270eGroups OBJECT IDENTIFIER ::= { tn3270eConformance 1 } tn3270eCompliances OBJECT IDENTIFIER ::= { tn3270eConformance 2 } -- compliance statements tn3270eCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for agents that support the TN3270 MIB." MODULE -- this module MANDATORY-GROUPS { tn3270eBasicGroup, tn3270eSessionGroup } GROUP tn3270ePoolGroup DESCRIPTION "This group is optional." OBJECT tn3270eSrvrConfActivityCheck MIN-ACCESS read-only DESCRIPTION "The agent is not required to support a set to this object if the associating TN3270 Server doesn't support either TIMEMARK or NOP processing. In this case an agent should return noCheck on retrieval." OBJECT tn3270eSrvrConfActivityTimeout MIN-ACCESS read-only DESCRIPTION "The agent is not required to support a set to this object if the functions enabled by tn3270eSrvrConfActivityCheck are not supported. An agent in this case should return a value of 0." OBJECT tn3270eSrvrConfActivityInterval MIN-ACCESS read-only DESCRIPTION "The agent is not required to support a set to this object if the functions enabled by tn3270eSrvrConfActivityCheck are not supported. An agent in this case should return a value of 0." OBJECT tn3270eTcpConnTargetAppl DESCRIPTION "A TN3270 Server is not required to support this object if it doesn't provide for Target Application mapping. In this case either a null OCTET STRING can be returned or noSuchObject." OBJECT tn3270eTcpConnClientUserId DESCRIPTION "A TN3270 Server is not required to support this object if it doesn't provide for Target Application mapping. In this case either a null OCTET STRING can be returned or noSuchObject." ::= { tn3270eCompliances 1 } -- units of conformance tn3270eBasicGroup OBJECT-GROUP OBJECTS { tn3270eSrvrConfInactivityTimer, tn3270eSrvrConfActivityCheck, tn3270eSrvrConfActivityTimeout, tn3270eSrvrConfActivityInterval, tn3270eSrvrConfProtoSupported, tn3270eSrvrConfAdminStatus, tn3270eSrvrConfOperStatus, tn3270eSrvrConfSessionTermState, tn3270eSrvrConfSrvrType, tn3270eSrvrConfRowStatus, tn3270eSrvrPortRowStatus, tn3270eSrvrStatsUpTime, tn3270eSrvrStatsMaxLus, tn3270eSrvrStatsLusInUse, tn3270eSrvrStatsSpareLus, tn3270eSrvrStatsMaxPtrs, tn3270eSrvrStatsPtrsInUse, tn3270eSrvrStatsSparePtrs, tn3270eSrvrStatsConnectsIn, tn3270eSrvrStatsConnRejects, tn3270eSrvrStatsDisconnects, tn3270eResMapIpAddress, tn3270eResMapSubnetMask, tn3270eResMapElementType, tn3270eResMapRowStatus, tn3270eIpMapResElementName, tn3270eIpMapElementType, tn3270eIpMapRowStatus } STATUS current DESCRIPTION "This group is mandatory for all hosts supporting the TN3270E-MIB." ::= { tn3270eGroups 1 } tn3270ePoolGroup OBJECT-GROUP OBJECTS { tn3270eIpGroupSubnetMask, tn3270eIpGroupRowStatus, tn3270eResPoolElementType, tn3270eResPoolIpGroupName, tn3270eResPoolClientPort, tn3270eResPoolRowStatus } STATUS current DESCRIPTION "This group is optional and allows a server to configure a collection of IP Address and Resource Pools and their mappings." ::= { tn3270eGroups 2 } tn3270eSessionGroup OBJECT-GROUP OBJECTS { tn3270eTcpConnLastActivity, tn3270eTcpConnBytesIn, tn3270eTcpConnBytesOut, tn3270eTcpConnTargetAppl, tn3270eTcpConnResourceName, tn3270eTcpConnResourceType, tn3270eTcpConnClientUserId, tn3270eTcpConnDeviceType, tn3270eTcpConnProto } STATUS current DESCRIPTION "This group is mandatory for all hosts supporting the TN3270E-MIB." ::= { tn3270eGroups 3 } END   Received: from cnri by ietf.org id aa15755; 27 Jun 97 18:30 EDT Received: from list.nih.gov (list.nih.gov [165.112.130.6]) by cnri.reston.va.us (8.8.5/8.7.3) with ESMTPid SAA12210 for ; Fri, 27 Jun 1997 18:29:12 -0400 (EDT) Received: from list.nih.gov (terrific.net.nih.gov [165.112.130.6]) by list.nih.gov (8.8.5/8.8.5) with ESMTP id SAA12055; Fri, 27 Jun 1997 18:19:52 -0400 (EDT) Received: from LIST.NIH.GOV by LIST.NIH.GOV (LISTSERV-TCP/IP release 1.8c) with spool id 2818913 for TN3270E@LIST.NIH.GOV; Fri, 27 Jun 1997 18:19:46 -0400 Received: from VNET.IBM.COM (vnet.ibm.com [204.146.168.194]) by list.nih.gov (8.8.5/8.8.5) with SMTP id SAA12037 for ; Fri, 27 Jun 1997 18:19:40 -0400 (EDT) Received: from RALVM12 by VNET.IBM.COM (IBM VM SMTP V2R3) with BSMTP id 1387; Fri, 27 Jun 97 18:19:39 EDT From: kennethw@vnet.ibm.com Message-Id: <199706272219.SAA12037@list.nih.gov> Date: Fri, 27 Jun 97 18:14:01 EDT To: tn3270e@list.nih.gov Subject: Sender: owner-tn3270e@list.nih.gov I just submitted a new internet-draft for the tn3270e-mib that I posted earlier this week. No changes were made to the mib module itself. Ken -------------------------------------------------------------------- TN3270E Working Group INTERNET DRAFT: Kenneth White Expiration Date: December, 1997 IBM Corp. June 1997 Base Definitions of Managed Objects for TN3270E Using SMIv2 Status of this Memo This document is an Internet Draft. Internet Drafts are working documents of the Internet Engineering Task Force (IETF), its Areas, and its Working Groups. Note that other groups may also distribute working documents as Internet Drafts. Internet Drafts are draft documents valid for a maximum of six months. Internet Drafts may be updated, replaced, or obsoleted by other documents at any time. It is not appropriate to use Internet Drafts as reference material or to cite them other than as a "working draft" or "work in progress." Please check the I-D abstract listing contained in each Internet Draft directory to learn the current status of this or any Internet Draft. Distribution of this document is unlimited. Abstract The purpose of this memo is to define a Management Information Base (MIB) for configuring and managing TN3270E Servers. The MIB defined by this memo is intended to provide generic support for both Host and Gateway TN3270E Server implementations. It is the intent that the MIB defined herein be extended by subsequent memos to provide non-generic configuration support and to enable TN3270E Response Time Monitoring. It is the intent of this MIB to fully adhere to all prerequisite MIBs unless explicitly stated. Deviations will be documented in corresponding conformance statements. The specification of this MIB will utilize the Structure of Management Information (SMI) for Version 2 of the Simple Network Management Protocol Version (refer to RFC1902, reference [1]). Expires December 1997 [Page 1] White TN3270E Management Information Base (TN3270E-MIB)26 June 1997 Table of Contents 1.0 Introduction............................................. 2 2.0 The SNMPv2 Network Management Framework.................. 2 2.1 Object Definitions....................................... 3 3.0 Structure of the MIB..................................... 3 3.1 TN3270E Server Control................................... 3 3.1.1 tn3270eSrvrConfTable................................... 3 3.1.2 tn3270eSrvrPortTable................................... 4 3.1.3 tn3270eSrvrStatsTable.................................. 4 3.2 TN3270E Server Resource Configuration.................... 5 3.2.1 tn3270eIpGroupTable and tn3270eResPoolTable............ 5 3.2.2 tn3270eResMapTable and tn3270eIpMapTable............... 5 3.3 TCP Connection Table Additions........................... 5 4.0 Definitions.............................................. 6 5.0 Security Considerations..................................29 6.0 Acknowledgments..........................................30 7.0 References...............................................30 8.0 Authors' Address.........................................31 1. Introduction This document is a product of the TN3270E Working Group. Its purpose is to define a MIB module for extending the traditional MIBs supported by a TCP/IP implementation for configuration and management of TN3270E Servers. 2. The SNMPv2 Network Management Framework The SNMP Network Management Framework presently consists of three major components. They are: o the SMI, described in RFC 1902 [1], - the mechanisms used for describing and naming objects for the purpose of management. o the MIB-II, STD 17, RFC 1213 [5], - the core set of managed objects for the Internet suite of protocols. o the protocol, RFC 1157 [9] and/or RFC 1905 [7] - the protocol for accessing managed information. Textual conventions are defined in RFC 1903 [6], and conformance statements are defined in RFC 1904 [8]. The Framework permits new objects to be defined for the purpose of experimentation and evaluation. Expires December 1997 [Page 2] White TN3270E Management Information Base (TN3270E-MIB)26 June 1997 This memo specifies a MIB module that is compliant to the SNMPv2 SMI. A semantically identical MIB conforming to the SNMPv1 SMI can be produced through the appropriate translation. 2.1. Object Definitions Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. Objects in the MIB are defined using the subset of Abstract Syntax Notation One (ASN.1) defined in the SMI. In particular, each object object type is named by an OBJECT IDENTIFIER, an administratively assigned name. The object type together with an object instance serves to uniquely identify a specific instantiation of the object. For human convenience, we often use a textual string, termed the descriptor, to refer to the object type. 3. Structure of the MIB The TN3270E-MIB is split into the following components: o TN3270E Server Control o TN3270E Server Resource Configuration o TCP Connection Table Additions The TN3270E-MIB is defined for support primarily by TN3270E Servers. Use of this MIB by TN3270 Servers that do not support the TN3270E protocol is not explicitly addressed by this memo. A significant portion of the objects do apply in the TN3270 only case. Addressing the TN3270 only case was not done since it is unlikely that this MIB would be implemented by TN3270 only servers. 3.1. TN3270E Server Control This group of objects provides for TN3270 and TN3270E configuration and consists of: o tn3270eSrvrConfTable o tn3270eSrvrPortTable o tn3270eSrvrStatsTable 3.1.1. tn3270eSrvrConfTable The tn3270eSrvrConfTable contains a set of objects primarily for Expires December 1997 [Page 3] White TN3270E Management Information Base (TN3270E-MIB)26 June 1997 configuring and managing a TN3270E Server. This table, as well most of the tables in the TN3270E-MIB, are structured to be indexed by the local IP Address (tn3270eSrvrConfIpAddr) and a unsigned integer (tn3270eSrvrConfIndex). The primary index, tn3270eSrvrConfIpAddr, was added to the tables in order for the tables to be used at both a TN3270E Server host implementation as well as by a management application that supports multiple TN3270E capable hosts. The second index element, tn3270eSrvrConfigIndex, was added in order to support multiple TN3270E Servers on the same host. tn3270eSrvrConfInactivityTimer defines the inactivity period for TN3270 and TN3270E Sessions. tn3270eSrvrConfSessionTermState defines how a session should be terminated. The three objects: o tn3270eSrvrConfActivityCheck o tn3270eSrvrConfActivityTimeout o tn3270eSrvrConfActivityInterval defines the parameters for performing the "Telnet Timing Mark Option" as defined by RFC 860 [3]. The object tn3270eSrvrConfActivityOption was defined to enable sending of a NOP command as oppose to a TIMEMARK command. Sending a NOP command results in less overhead then a TIMEMARK command since a client doesn't send a reply. The objects tn3270eSrvrConfAdminStatus and tn3270eSrvrConfOperStatus exists in order to enable remote starting and stopping of a TN3270E Server. tn3270eSrvrConfProtoSupported indicates which of the TN3270 and TN3270E options that a server supports. The object tn3270eSrvrConfSrvrType indicates the implementation type of TN3270E Server that the tn3270eSrvrConfEntry represents. The object tn3270eSrvrConfRowStatus provides the capability to perform remote creation and deletion operations on this table. 3.1.2. tn3270eSrvrPortTable The tn3270eSrvrPortTable exists in order to assign and retrieve the local ports associated with a TN3270E Server. Some implementations support multiple local port usage. 3.1.3. tn3270eSrvrStatsTable The tn3270eSrvrStatsTable defines a series of objects used to provide general statistics on the use of a TN3270E Server. Expires December 1997 [Page 4] White TN3270E Management Information Base (TN3270E-MIB)26 June 1997 3.2. TN3270E Server Resource Configuration The TN3270E Server Resource Configuration collection of objects consists of four tables: o tn3270eIpGroupTable o tn3270eResPoolTable o tn3270eResMapTable o tn3270eIpMapTable 3.2.1. tn3270eIpGroupTable and tn3270eResPoolTable enable implementations to define groupings of both IP Addresses and Resource Pools for mapping IP Addresses to resources. The mapping of a IP Group to a Resource Pool is enabled via tn3270eResPoolIpGroupName. Creating an entry in the tn3270eResPoolTable results in creation of an entry or entries in both the tn3270eResMapTable and tn3270eIpMapTable. Both the tn3270eIpGroupTable and the tn3270eResPoolTable are optional since not every TN3270E Server has the ability to define their IP to Resource mappings in this manner. tn3270eResPoolClientPort exists to enable implementations to restrict a collection of resources to a particular local port. This object is optional since not every implementation provides this type of support. 3.2.2. tn3270eResMapTable and tn3270eIpMapTable The tables: tn3270eResMapTable and tn3270eIpMapTable provide mappings of IP Address(es) to Resource(s) and Resource(s) to IP Address(es). The index objects, tn3270eResMapClientPort and tn3270eIpMapClientPort, as allowed to be zero when these tables are implemented by TN3270E Servers that do provide local port to resource mapping. 3.3. TCP Connection Table Additions The TCP Connection Table is defined by RFC 2012 (Refer to reference 10, TCP-MIB Definitions). Traditionally, the contents of the TCP Connection Table has been implementation dependent. Its formal definition consists of the following objects: o tcpConnState (INTEGER) o tcpConnLocalAddress (IpAddress) o tcpConnLocalPort (INTEGER) o tcpConnRemAddress (IpAddress) o tcpConnRemPort (INTEGER) Expires December 1997 [Page 5] White TN3270E Management Information Base (TN3270E-MIB)26 June 1997 and is indexed by: tcpConnLocalAddress, tcpConnLocalPort, tcpConnRemAddress and tcpConnRemPort. The tn3270eTcpConnTableGroup contains the objects defined by the tn3270eTcpConnTable for keeping a list of the current set of TN3270 and TN3270E sessions at a TN3270E Server. The tn3270eTcpConnTable has the same index elements as the tcpConnTable but doesn't AUGMENT it since the relationship is not one-to-one. 4. Definitions TN3270E-MIB DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, BITS, Unsigned32, experimental, Integer32, IpAddress, TimeTicks, Counter32 FROM SNMPv2-SMI TEXTUAL-CONVENTION, RowStatus, DisplayString FROM SNMPv2-TC MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF tcpConnLocalAddress, tcpConnLocalPort, tcpConnRemAddress, tcpConnRemPort FROM TCP-MIB ; tn3270eMIB MODULE-IDENTITY LAST-UPDATED "9706200000Z" -- June 20, 1997 ORGANIZATION "TN3270E Working Group" CONTACT-INFO "Kenneth White (kennethw@vnet.ibm.com) IBM Corp." DESCRIPTION "This module defines a portion of the management information base (MIB) for managing TN3270E Servers" -- Need an experimental OID from IANA ::= { experimental 2001 } -- Textual Conventions ResourceType ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "The type of resource defined by a Resource Pool. Refer to tn3270eResPoolTable." SYNTAX INTEGER { other(0), Expires December 1997 [Page 6] White TN3270E Management Information Base (TN3270E-MIB)26 June 1997 lu(1), printer(2) } Tn3270Functions ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "This textual convention is intended to reflect the current set of TN3270 and TN3270E functions that can be negiotiated between a server and its client: RFC856 transmitBinary The sender of this command REQUESTS permission to begin transmitting, or confirms that it will now begin transmitting characters which are to be interpreted as 8 bits of binary data by the receiver of the data. RFC820 timeMark The sender of this command REQUESTS that the receiver of this command return a WILL TIMING-MARK in the data stream at the 'appropriate place' ... RFC885 endOfRecord The sender of this command requests permission to begin transmission of the Telnet END-OF-RECORD (EOR) code when transmitting data characters, or the sender of this command confirms it will now begin transmission of EORs with transmitted data characters. RFC1091 terminalType Sender is willing to send terminal type information in a subsequent sub-negotiation. RFC1041 tn3270Regime Sender is willing to send list of supported 3270 Regimes in a subsequent sub-negotiation. RFC1647 scsCtlCodes (Printer sessions only). Allows the use of the SNA Character Stream (SCS) and SCS control codes on the session. SCS is used with LU type 1 SNA sessions. dataStreamCtl (Printer sessions only). Allows the use of the standard 3270 data stream. This corresponds to LU type 3 SNA sessions. responses Provides support for positive and negative response handling. Allows the server to reflect to the client any and Expires December 1997 [Page 7] White TN3270E Management Information Base (TN3270E-MIB)26 June 1997 all definite, exception, and no response requests sent by the host application. bindImage Allows the server to send the SNA Bind image and Unbind notification to the client. sysreq Allows the client and server to emulate some (or all, depending on the server) of the functions of the SYSREQ key in an SNA environment." SYNTAX BITS { transmitBinary(0),-- rfc856 timemark(1), -- rfc860 endOfRecord(2), -- rfc885 terminalType(3), -- rfc1091 tn3270Regime(4), -- rfc1041 scsCtlCodes(5), -- rfc1647 dataStreamCtl(6), -- rfc1647 responses(7), -- rfc1647 bindImage(8), -- rfc1647 sysreq(9) -- rfc1647 } DeviceTypes ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "This textual convention defines the list of device types that can be set as defined by RFC 1647." SYNTAX INTEGER { -- terminals unknown(0), ibm3278d2(1), -- (24 row x 80 col display) ibm3278d2E(2), -- (24 row x 80 col display) ibm3278d3(3), -- (32 row x 80 col display) ibm3278d3E(4), -- (32 row x 80 col display) ibm3278d4(5), -- (43 row x 80 col display) ibm3278d4E(6), -- (43 row x 80 col display) ibm3278d5(7), -- (27 row x 132 col display) ibm3278d5E(8), -- (27 row x 132 col display) ibmDynamic(9), -- (no pre-defined display size) ibm3287d1(10) -- printers } -- Top-level structure of the MIB tn3270eNotifications OBJECT IDENTIFIER ::= { tn3270eMIB 0 } tn3270eObjects OBJECT IDENTIFIER ::= { tn3270eMIB 1 } tn3270eConformance OBJECT IDENTIFIER ::= { tn3270eMIB 3 } -- MIB Objects Expires December 1997 [Page 8] White TN3270E Management Information Base (TN3270E-MIB)26 June 1997 tn3270eSrvrConfTable OBJECT-TYPE SYNTAX SEQUENCE OF Tn3270eSrvrConfEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table defines the configuration elements for TN3270 Servers. The number of entries in this table is expected to vary depending on the location of the table. A particular TN3270 Server is expected to have a single entry. Modeling of the configuration elements as a table enable use of the table by management applications as well as allowing multiple TN3270 Servers to exist at the same host." ::= { tn3270eObjects 1 } tn3270eSrvrConfEntry OBJECT-TYPE SYNTAX Tn3270eSrvrConfEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Definition of the configuration elements for a single TN3270 Server." INDEX { tn3270eSrvrConfIpAddr, tn3270eSrvrConfIndex } ::= { tn3270eSrvrConfTable 1 } Tn3270eSrvrConfEntry ::= SEQUENCE { tn3270eSrvrConfIpAddr IpAddress, tn3270eSrvrConfIndex Unsigned32, tn3270eSrvrConfInactivityTimer Unsigned32, tn3270eSrvrConfActivityCheck INTEGER, tn3270eSrvrConfActivityTimeout Unsigned32, tn3270eSrvrConfActivityInterval Unsigned32, tn3270eSrvrConfProtoSupported Tn3270Functions, tn3270eSrvrConfAdminStatus INTEGER, tn3270eSrvrConfOperStatus INTEGER, tn3270eSrvrConfSessionTermState INTEGER, tn3270eSrvrConfSrvrType INTEGER, tn3270eSrvrConfRowStatus RowStatus } tn3270eSrvrConfIpAddr OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS not-accessible STATUS current DESCRIPTION "Indicates the local IP Address associated with a TN3270 Server. A value of 0 is allowed when the entry exists at a single TN3270 Server instance host." Expires December 1997 [Page 9] White TN3270E Management Information Base (TN3270E-MIB)26 June 1997 ::= { tn3270eSrvrConfEntry 1 } tn3270eSrvrConfIndex OBJECT-TYPE SYNTAX Unsigned32 MAX-ACCESS not-accessible STATUS current DESCRIPTION "Indicates the instance of a TN3270/TN3270E Server that exists at the IP Host pointed to by tn3270eSrvrConfIpAddr." ::= { tn3270eSrvrConfEntry 2 } tn3270eSrvrConfInactivityTimer OBJECT-TYPE SYNTAX Unsigned32 (0..99999999) UNITS "seconds" MAX-ACCESS read-create STATUS current DESCRIPTION "The inactivity time-out specified in seconds. When a connection has been inactive for the number of seconds specified by this object it is closed. The default of 0 means no inactivity time-out." DEFVAL { 0 } ::= { tn3270eSrvrConfEntry 3 } tn3270eSrvrConfActivityCheck OBJECT-TYPE SYNTAX INTEGER { noCheck(0), timeMark(1), nop(2) } MAX-ACCESS read-create STATUS current DESCRIPTION "This object is intended to enable either timemark or nop processing." DEFVAL { noCheck } ::= { tn3270eSrvrConfEntry 4 } tn3270eSrvrConfActivityTimeout OBJECT-TYPE SYNTAX Unsigned32 UNITS "seconds" MAX-ACCESS read-create STATUS current DESCRIPTION "The TIMEMARK or NOP processing time-out specified in seconds." DEFVAL { 600 } -- 10 minutes ::= { tn3270eSrvrConfEntry 5 } Expires December 1997 [Page 10] White TN3270E Management Information Base (TN3270E-MIB)26 June 1997 tn3270eSrvrConfActivityInterval OBJECT-TYPE SYNTAX Unsigned32 UNITS "seconds" MAX-ACCESS read-create STATUS current DESCRIPTION "The scan interval to be used by the Telnet Server. TIMEMARK or NOP processing scans the Telnet sessions on the interval provided by this object looking for sessions that have been idle for more than the value provided by tn3270eSrvrConfActivityTimeout." DEFVAL { 120 } -- 2 minutes ::= { tn3270eSrvrConfEntry 6 } tn3270eSrvrConfProtoSupported OBJECT-TYPE SYNTAX Tn3270Functions MAX-ACCESS read-only STATUS current DESCRIPTION "This object indicates the TN3270 functions supported by a TN3270 Server." DEFVAL { { scsCtlCodes, dataStreamCtl, responses, bindImage, sysreq } } ::= { tn3270eSrvrConfEntry 7 } tn3270eSrvrConfAdminStatus OBJECT-TYPE SYNTAX INTEGER { up(1), down(2), stopImmediate(3) } MAX-ACCESS read-create STATUS current DESCRIPTION "The desired state of the Telnet Server. The stopImmediate state is intended to enable Servers to gracefully terminate via down or to terminate immediate without ending its client connections. There is no requirement for support of stopImmediate." ::= { tn3270eSrvrConfEntry 8 } tn3270eSrvrConfOperStatus OBJECT-TYPE SYNTAX INTEGER { up(1), down(2) } MAX-ACCESS read-only STATUS current Expires December 1997 [Page 11] White TN3270E Management Information Base (TN3270E-MIB)26 June 1997 DESCRIPTION "The current operational state of the Telnet Server." ::= { tn3270eSrvrConfEntry 9 } tn3270eSrvrConfSessionTermState OBJECT-TYPE SYNTAX INTEGER { terminate(1), luSessionPend(2), queueSession(3) } MAX-ACCESS read-create STATUS current DESCRIPTION "The current state for determining what happens when Telnet connection terminates: terminate(1) => Terminate connection. luSessionPend(2) => Allows the client's session to revert to their Default Application upon termination of their Telnet connection. queueSession(3) => ????" DEFVAL { terminate } ::= { tn3270eSrvrConfEntry 10 } tn3270eSrvrConfSrvrType OBJECT-TYPE SYNTAX INTEGER { unknown(0), host(1), gateway(2) } MAX-ACCESS read-only STATUS current DESCRIPTION "This object indicates the type of TN3270/TN3270E Server. The existence of MIB tables and objects that will be defined by follow-on MIBs may be predicated on whether the TN3270/TN3270E Server is local to the same host as the secondary LU used to attach the IP client into a SNA network." ::= { tn3270eSrvrConfEntry 11 } tn3270eSrvrConfRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "This object allows entries to be created and deleted in the tn3270eSrvrConfTable. Creating an entry in this table Expires December 1997 [Page 12] White TN3270E Management Information Base (TN3270E-MIB)26 June 1997 at a management application informs enable that application to manage the associating TN3270 Server. Deleting an entry removes it from that application's management domain. A server based implementation of this table may chose to not support creation or deletion of its (probably only) entry in this table via this object. An entry in this table is deleted by setting this object to destroy(6)." REFERENCE "RFC 1903, 'Textual Conventions for version 2 of the Simple Network Management Protocol (SNMPv2).'" ::= { tn3270eSrvrConfEntry 12 } tn3270eSrvrPortTable OBJECT-TYPE SYNTAX SEQUENCE OF Tn3270eSrvrPortEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table defines the ports associated with TN3270/ TN3270E Servers." ::= { tn3270eObjects 2 } tn3270eSrvrPortEntry OBJECT-TYPE SYNTAX Tn3270eSrvrPortEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Definition of a single server port assignment." INDEX { tn3270eSrvrConfIpAddr, tn3270eSrvrConfIndex, tn3270eSrvrPort } ::= { tn3270eSrvrPortTable 1 } Tn3270eSrvrPortEntry ::= SEQUENCE { tn3270eSrvrPort Unsigned32, tn3270eSrvrPortRowStatus RowStatus } tn3270eSrvrPort OBJECT-TYPE SYNTAX Unsigned32 (0..65535) MAX-ACCESS not-accessible STATUS current DESCRIPTION "Indicates a port assigned to a server." ::= { tn3270eSrvrPortEntry 1 } tn3270eSrvrPortRowStatus OBJECT-TYPE Expires December 1997 [Page 13] White TN3270E Management Information Base (TN3270E-MIB)26 June 1997 SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "This object allows entries to be created and deleted in the tn3270eSrvrPortTable. An entry in this table is deleted by setting this object to destroy(6)." REFERENCE "RFC 1903, 'Textual Conventions for version 2 of the Simple Network Management Protocol (SNMPv2).'" ::= { tn3270eSrvrPortEntry 2 } tn3270eSrvrStatsTable OBJECT-TYPE SYNTAX SEQUENCE OF Tn3270eSrvrStatsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table defines a set of statistics concerning global TN3270 Server performance." ::= { tn3270eObjects 3 } tn3270eSrvrStatsEntry OBJECT-TYPE SYNTAX Tn3270eSrvrStatsEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Collection of a set of statistic objects for a single TN3270 Server." INDEX { tn3270eSrvrConfIpAddr, tn3270eSrvrConfIndex } ::= { tn3270eSrvrStatsTable 1 } Tn3270eSrvrStatsEntry ::= SEQUENCE { tn3270eSrvrStatsUpTime TimeTicks, tn3270eSrvrStatsMaxLus Integer32, tn3270eSrvrStatsLusInUse Integer32, tn3270eSrvrStatsSpareLus Integer32, tn3270eSrvrStatsMaxPtrs Integer32, tn3270eSrvrStatsPtrsInUse Integer32, tn3270eSrvrStatsSparePtrs Integer32, tn3270eSrvrStatsConnectsIn Counter32, tn3270eSrvrStatsConnRejects Counter32, tn3270eSrvrStatsDisconnects Counter32 } tn3270eSrvrStatsUpTime OBJECT-TYPE SYNTAX TimeTicks Expires December 1997 [Page 14] White TN3270E Management Information Base (TN3270E-MIB)26 June 1997 MAX-ACCESS read-only STATUS current DESCRIPTION "Indicates the amount of time that a particular TN3270 has be active. This is total time since the server was started and is not reset on tn3270eSrvrConfOperStatus." ::= { tn3270eSrvrStatsEntry 1 } tn3270eSrvrStatsMaxLus OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "Indicates the maximum number of LUs for use by a TN3270 Server." ::= { tn3270eSrvrStatsEntry 2 } tn3270eSrvrStatsLusInUse OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "Indicates the current number of LUs in use by a TN3270 Server." ::= { tn3270eSrvrStatsEntry 3 } tn3270eSrvrStatsSpareLus OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "Indicates the number of free LUs for a particular TN3270 Server." ::= { tn3270eSrvrStatsEntry 4 } tn3270eSrvrStatsMaxPtrs OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "Indicates the maximum number of Printer Resources for use by a TN3270 Server." ::= { tn3270eSrvrStatsEntry 5 } tn3270eSrvrStatsPtrsInUse OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current Expires December 1997 [Page 15] White TN3270E Management Information Base (TN3270E-MIB)26 June 1997 DESCRIPTION "Indicates the current number of Printer Resources in use by a TN3270 Server." ::= { tn3270eSrvrStatsEntry 6 } tn3270eSrvrStatsSparePtrs OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "Indicates the number of free Printer Resources for a particular TN3270 Server." ::= { tn3270eSrvrStatsEntry 7 } tn3270eSrvrStatsConnectsIn OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Indicates the number of client connections received by a TN3270 Server." ::= { tn3270eSrvrStatsEntry 8 } tn3270eSrvrStatsConnRejects OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Indicates the number of client connections rejected during connection setup." ::= { tn3270eSrvrStatsEntry 9 } tn3270eSrvrStatsDisconnects OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS current DESCRIPTION "Indicates the number of client connections disconnected by a TN3270 Server." ::= { tn3270eSrvrStatsEntry 10 } tn3270eIpGroupTable OBJECT-TYPE SYNTAX SEQUENCE OF Tn3270eIpGroupEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table defines IP Address groupings for use by the Telnet Server." Expires December 1997 [Page 16] White TN3270E Management Information Base (TN3270E-MIB)26 June 1997 ::= { tn3270eObjects 4 } tn3270eIpGroupEntry OBJECT-TYPE SYNTAX Tn3270eIpGroupEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Definition of a single IP Address entry. All entries with the same 1st index, tn3270eIpGroupName are considered to be in the same IP Group." INDEX { tn3270eSrvrConfIpAddr, tn3270eSrvrConfIndex, tn3270eIpGroupName, tn3270eIpGroupIpAddress } ::= { tn3270eIpGroupTable 1 } Tn3270eIpGroupEntry ::= SEQUENCE { tn3270eIpGroupName DisplayString, tn3270eIpGroupIpAddress IpAddress, tn3270eIpGroupSubnetMask IpAddress, tn3270eIpGroupRowStatus RowStatus } tn3270eIpGroupName OBJECT-TYPE SYNTAX DisplayString (SIZE(1..8)) MAX-ACCESS not-accessible STATUS current DESCRIPTION "The name of a IP Group." ::= { tn3270eIpGroupEntry 1 } tn3270eIpGroupIpAddress OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS not-accessible STATUS current DESCRIPTION "The IP Address of a member of a IP Group." ::= { tn3270eIpGroupEntry 2 } tn3270eIpGroupSubnetMask OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-create STATUS current DESCRIPTION "The corresponding subnet mask associated with tn3270eIpGroupIpAddress. A single IP Address is represented by having this object contain the value of 255.255.255.255." ::= { tn3270eIpGroupEntry 3 } tn3270eIpGroupRowStatus OBJECT-TYPE Expires December 1997 [Page 17] White TN3270E Management Information Base (TN3270E-MIB)26 June 1997 SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "This object allows entries to be created and deleted in the tn3270eIpGroupTable. An entry in this table is deleted by setting this object to destroy(6)." REFERENCE "RFC 1903, 'Textual Conventions for version 2 of the Simple Network Management Protocol (SNMPv2).'" ::= { tn3270eIpGroupEntry 4 } tn3270eResPoolTable OBJECT-TYPE SYNTAX SEQUENCE OF Tn3270eResPoolEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table defines Resource groupings and using the term pool as defined by RFC 1647." ::= { tn3270eObjects 5 } tn3270eResPoolEntry OBJECT-TYPE SYNTAX Tn3270eResPoolEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Definition of a single Resource Pool member. All entries with the same 1st index, tn3270eResPoolName are considered to be in the same Pool." INDEX { tn3270eSrvrConfIpAddr, tn3270eSrvrConfIndex, tn3270eResPoolName, tn3270eResPoolElementName } ::= { tn3270eResPoolTable 1 } Tn3270eResPoolEntry ::= SEQUENCE { tn3270eResPoolName DisplayString, tn3270eResPoolElementName DisplayString, tn3270eResPoolIpGroupName DisplayString, tn3270eResPoolElementType ResourceType, tn3270eResPoolClientPort Unsigned32, tn3270eResPoolRowStatus RowStatus } tn3270eResPoolName OBJECT-TYPE SYNTAX DisplayString (SIZE(1..255)) MAX-ACCESS not-accessible STATUS current DESCRIPTION Expires December 1997 [Page 18] White TN3270E Management Information Base (TN3270E-MIB)26 June 1997 "The name of a Resource Pool.." ::= { tn3270eResPoolEntry 1 } tn3270eResPoolElementName OBJECT-TYPE SYNTAX DisplayString (SIZE(1..8)) MAX-ACCESS not-accessible STATUS current DESCRIPTION "The Name of a member of a Resource Pool." ::= { tn3270eResPoolEntry 2 } tn3270eResPoolIpGroupName OBJECT-TYPE SYNTAX DisplayString (SIZE(1..8)) MAX-ACCESS read-create STATUS current DESCRIPTION "The name of a IP Group to map a Resource Element to." ::= { tn3270eResPoolEntry 3 } tn3270eResPoolElementType OBJECT-TYPE SYNTAX ResourceType MAX-ACCESS read-create STATUS current DESCRIPTION "The type of the entity in a Resource Pool." ::= { tn3270eResPoolEntry 4 } tn3270eResPoolClientPort OBJECT-TYPE SYNTAX Unsigned32 (0..65535) MAX-ACCESS read-create STATUS current DESCRIPTION "If specified this a pool to a specific client port." ::= { tn3270eResPoolEntry 5 } tn3270eResPoolRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "This object allows entries to be created and deleted in the tn3270eResPoolTable. An entry in this table is deleted by setting this object to destroy(6)." REFERENCE "RFC 1903, 'Textual Conventions for version 2 of the Simple Expires December 1997 [Page 19] White TN3270E Management Information Base (TN3270E-MIB)26 June 1997 Network Management Protocol (SNMPv2).'" ::= { tn3270eResPoolEntry 6 } tn3270eResMapTable OBJECT-TYPE SYNTAX SEQUENCE OF Tn3270eResMapEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table defines Resource Element to IP Address mappings." ::= { tn3270eObjects 6 } tn3270eResMapEntry OBJECT-TYPE SYNTAX Tn3270eResMapEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Definition of the mapping of a Resource Element to a IP Address." INDEX { tn3270eSrvrConfIpAddr, tn3270eSrvrConfIndex, tn3270eResMapClientPort, tn3270eResMapElementName } ::= { tn3270eResMapTable 1 } Tn3270eResMapEntry ::= SEQUENCE { tn3270eResMapClientPort Unsigned32, tn3270eResMapElementName DisplayString, tn3270eResMapIpAddress IpAddress, tn3270eResMapSubnetMask IpAddress, tn3270eResMapElementType ResourceType, tn3270eResMapRowStatus RowStatus } tn3270eResMapClientPort OBJECT-TYPE SYNTAX Unsigned32 (0..65535) MAX-ACCESS not-accessible STATUS current DESCRIPTION "The port that this assignment is restricted to. Note that a value of 0 for this object implies that the assignment is global to all client ports." ::= { tn3270eResMapEntry 1 } tn3270eResMapElementName OBJECT-TYPE SYNTAX DisplayString (SIZE(1..8)) MAX-ACCESS not-accessible STATUS current DESCRIPTION "The Name of a resource element." ::= { tn3270eResMapEntry 2 } Expires December 1997 [Page 20] White TN3270E Management Information Base (TN3270E-MIB)26 June 1997 tn3270eResMapIpAddress OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-create STATUS current DESCRIPTION "A client IP Address or subnet if tn3270eResMapSubnetMask is set to 255.255.255.255." ::= { tn3270eResMapEntry 3 } tn3270eResMapSubnetMask OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS read-create STATUS current DESCRIPTION "The corresponding subnet mask associated with tn3270eResMapIpAddress. A single IP Address is represented by having this object contain the value of 255.255.255.255." ::= { tn3270eResMapEntry 4 } tn3270eResMapElementType OBJECT-TYPE SYNTAX ResourceType MAX-ACCESS read-create STATUS current DESCRIPTION "The type of the entity in a Resource Pool." ::= { tn3270eResMapEntry 5 } tn3270eResMapRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "This object allows entries to be created and deleted in the tn3270eResMapTable. Entries in this table should occur automatically when an entry is created in the tn3270eResPoolTable. Deleting an entry in the tn3270eResPoolTable should remove all corresponding entries in this table. The tn3270eResPoolTable is optional. This implies that entries can be added directly to this table." REFERENCE "RFC 1903, 'Textual Conventions for version 2 of the Simple Network Management Protocol (SNMPv2).'" ::= { tn3270eResMapEntry 6 } Expires December 1997 [Page 21] White TN3270E Management Information Base (TN3270E-MIB)26 June 1997 tn3270eIpMapTable OBJECT-TYPE SYNTAX SEQUENCE OF Tn3270eIpMapEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "This table defines IP Address to Resource Element mappings." ::= { tn3270eObjects 7 } tn3270eIpMapEntry OBJECT-TYPE SYNTAX Tn3270eIpMapEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Definition of the mapping of a IP Address or Group to a Resource Element." INDEX { tn3270eSrvrConfIpAddr, tn3270eSrvrConfIndex, tn3270eIpMapIpAddress, tn3270eIpMapSubnetMask, tn3270eIpMapClientPort } ::= { tn3270eIpMapTable 1 } Tn3270eIpMapEntry ::= SEQUENCE { tn3270eIpMapIpAddress IpAddress, tn3270eIpMapSubnetMask IpAddress, tn3270eIpMapClientPort Unsigned32, tn3270eIpMapResElementName DisplayString, tn3270eIpMapElementType ResourceType, tn3270eIpMapRowStatus RowStatus } tn3270eIpMapIpAddress OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS not-accessible STATUS current DESCRIPTION "The IP Address of a member of a IP Group." ::= { tn3270eIpMapEntry 1 } tn3270eIpMapSubnetMask OBJECT-TYPE SYNTAX IpAddress MAX-ACCESS not-accessible STATUS current DESCRIPTION "The corresponding subnet mask associated with tn3270eIpGroupIpAddress. A single IP Address is represented by having this object contain the value of 255.255.255.255." ::= { tn3270eIpMapEntry 2 } tn3270eIpMapClientPort OBJECT-TYPE Expires December 1997 [Page 22] White TN3270E Management Information Base (TN3270E-MIB)26 June 1997 SYNTAX Unsigned32 (0..65535) MAX-ACCESS not-accessible STATUS current DESCRIPTION "The port that this assignment is restricted to. Note that a value of 0 for this object implies that the assignment is global to all client ports." ::= { tn3270eIpMapEntry 3 } tn3270eIpMapResElementName OBJECT-TYPE SYNTAX DisplayString (SIZE(0..8)) MAX-ACCESS read-create STATUS current DESCRIPTION "The Resource Element mapping to IP Address(es)." ::= { tn3270eIpMapEntry 4 } tn3270eIpMapElementType OBJECT-TYPE SYNTAX ResourceType MAX-ACCESS read-create STATUS current DESCRIPTION "The type resource element." ::= { tn3270eIpMapEntry 5 } tn3270eIpMapRowStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS current DESCRIPTION "This object allows entries to be created and deleted in the tn3270eIpMapMapTable. Entries in this table should occur automatically when an entry is created in the tn3270eResPoolTable. Deleting an entry in the tn3270eResPoolTable should remove all corresponding entries in this table. The tn3270eResPoolTable is optional. This implies that entries can be added directly to this table." REFERENCE "RFC 1903, 'Textual Conventions for version 2 of the Simple Network Management Protocol (SNMPv2).'" ::= { tn3270eIpMapEntry 6 } -- Define the set of objects to add to the Tcp Connection Table tn3270eTcpConnTable OBJECT-TYPE Expires December 1997 [Page 23] White TN3270E Management Information Base (TN3270E-MIB)26 June 1997 SYNTAX SEQUENCE OF Tn3270eTcpConnEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Extends tcpConnTable to support TN3270 and TN3270E performance monitoring." ::= { tn3270eObjects 8 } tn3270eTcpConnEntry OBJECT-TYPE SYNTAX Tn3270eTcpConnEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "Provides in formation about a single TN3270/TN3270E session." INDEX { tcpConnLocalAddress, tcpConnLocalPort, tcpConnRemAddress, tcpConnRemPort } ::= { tn3270eTcpConnTable 1 } Tn3270eTcpConnEntry ::= SEQUENCE { tn3270eTcpConnLastActivity TimeTicks, tn3270eTcpConnBytesIn Counter32, tn3270eTcpConnBytesOut Counter32, tn3270eTcpConnTargetAppl DisplayString, tn3270eTcpConnResourceName DisplayString, tn3270eTcpConnResourceType ResourceType, tn3270eTcpConnClientUserId DisplayString, tn3270eTcpConnDeviceType DeviceTypes, tn3270eTcpConnProto Tn3270Functions } tn3270eTcpConnLastActivity OBJECT-TYPE SYNTAX TimeTicks MAX-ACCESS read-only STATUS current DESCRIPTION "The number of 100ths of seconds since this entry was last used." DEFVAL { 0 } ::= { tn3270eTcpConnEntry 1 } tn3270eTcpConnBytesIn OBJECT-TYPE SYNTAX Counter32 UNITS "octets" MAX-ACCESS read-only STATUS current Expires December 1997 [Page 24] White TN3270E Management Information Base (TN3270E-MIB)26 June 1997 DESCRIPTION "The number of bytes received by the Server from TCP for this connection." ::= { tn3270eTcpConnEntry 2 } tn3270eTcpConnBytesOut OBJECT-TYPE SYNTAX Counter32 UNITS "octets" MAX-ACCESS read-only STATUS current DESCRIPTION "The number of bytes sent to TCP for this connection." ::= { tn3270eTcpConnEntry 3 } tn3270eTcpConnTargetAppl OBJECT-TYPE SYNTAX DisplayString (SIZE(0..8)) MAX-ACCESS read-only STATUS current DESCRIPTION "When the corresponding TCP connection is for a 3172 Telnet session then this object contains the Target VTAM Application name. For gateway server implementations this object will not be known and should be returned as a null OCTET STRING." ::= { tn3270eTcpConnEntry 4 } tn3270eTcpConnResourceName OBJECT-TYPE SYNTAX DisplayString (SIZE(0..8)) MAX-ACCESS read-only STATUS current DESCRIPTION "LU/Print secondary name for connecting a IP Client into a SNA network." ::= { tn3270eTcpConnEntry 5 } tn3270eTcpConnResourceType OBJECT-TYPE SYNTAX ResourceType MAX-ACCESS read-only STATUS current DESCRIPTION "Indicates the type of resource identified by tn3270eTcpConnResourceName." ::= { tn3270eTcpConnEntry 6 } tn3270eTcpConnClientUserId OBJECT-TYPE SYNTAX DisplayString (SIZE(0..8)) MAX-ACCESS read-only STATUS current Expires December 1997 [Page 25] White TN3270E Management Information Base (TN3270E-MIB)26 June 1997 DESCRIPTION "When the corresponding TCP connection is for a 3172 Telnet session then this object contains the Client's userid." ::= { tn3270eTcpConnEntry 7 } tn3270eTcpConnDeviceType OBJECT-TYPE SYNTAX DeviceTypes MAX-ACCESS read-only STATUS current DESCRIPTION "Indicates the device type if negiotiated with client." ::= { tn3270eTcpConnEntry 8 } tn3270eTcpConnProto OBJECT-TYPE SYNTAX Tn3270Functions MAX-ACCESS read-only STATUS current DESCRIPTION "This flag will indicates which of the TN3270 and TN3270E functions that are supported by the Server was negioted with a client. Refer to tn3270eSrvrConfProtoSupported." ::= { tn3270eTcpConnEntry 9 } -- Conformance Definitions tn3270eGroups OBJECT IDENTIFIER ::= { tn3270eConformance 1 } tn3270eCompliances OBJECT IDENTIFIER ::= { tn3270eConformance 2 } -- compliance statements tn3270eCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement for agents that support the TN3270 MIB." MODULE -- this module MANDATORY-GROUPS { tn3270eBasicGroup, tn3270eSessionGroup } GROUP tn3270ePoolGroup DESCRIPTION "This group is optional." OBJECT tn3270eSrvrConfActivityCheck MIN-ACCESS read-only DESCRIPTION "The agent is not required to support a set to this object if the associating TN3270 Server doesn't support either TIMEMARK or NOP processing. In Expires December 1997 [Page 26] White TN3270E Management Information Base (TN3270E-MIB)26 June 1997 this case an agent should return noCheck on retrieval." OBJECT tn3270eSrvrConfActivityTimeout MIN-ACCESS read-only DESCRIPTION "The agent is not required to support a set to this object if the functions enabled by tn3270eSrvrConfActivityCheck are not supported. An agent in this case should return a value of 0." OBJECT tn3270eSrvrConfActivityInterval MIN-ACCESS read-only DESCRIPTION "The agent is not required to support a set to this object if the functions enabled by tn3270eSrvrConfActivityCheck are not supported. An agent in this case should return a value of 0." OBJECT tn3270eTcpConnTargetAppl DESCRIPTION "A TN3270 Server is not required to support this object if it doesn't provide for Target Application mapping. In this case either a null OCTET STRING can be returned or noSuchObject." OBJECT tn3270eTcpConnClientUserId DESCRIPTION "A TN3270 Server is not required to support this object if it doesn't provide for Target Application mapping. In this case either a null OCTET STRING can be returned or noSuchObject." ::= { tn3270eCompliances 1 } -- units of conformance tn3270eBasicGroup OBJECT-GROUP OBJECTS { tn3270eSrvrConfInactivityTimer, tn3270eSrvrConfActivityCheck, tn3270eSrvrConfActivityTimeout, tn3270eSrvrConfActivityInterval, tn3270eSrvrConfProtoSupported, tn3270eSrvrConfAdminStatus, tn3270eSrvrConfOperStatus, tn3270eSrvrConfSessionTermState, tn3270eSrvrConfSrvrType, tn3270eSrvrConfRowStatus, tn3270eSrvrPortRowStatus, tn3270eSrvrStatsUpTime, tn3270eSrvrStatsMaxLus, tn3270eSrvrStatsLusInUse, Expires December 1997 [Page 27] White TN3270E Management Information Base (TN3270E-MIB)26 June 1997 tn3270eSrvrStatsSpareLus, tn3270eSrvrStatsMaxPtrs, tn3270eSrvrStatsPtrsInUse, tn3270eSrvrStatsSparePtrs, tn3270eSrvrStatsConnectsIn, tn3270eSrvrStatsConnRejects, tn3270eSrvrStatsDisconnects, tn3270eResMapIpAddress, tn3270eResMapSubnetMask, tn3270eResMapElementType, tn3270eResMapRowStatus, tn3270eIpMapResElementName, tn3270eIpMapElementType, tn3270eIpMapRowStatus } STATUS current DESCRIPTION "This group is mandatory for all hosts supporting the TN3270E-MIB." ::= { tn3270eGroups 1 } tn3270ePoolGroup OBJECT-GROUP OBJECTS { tn3270eIpGroupSubnetMask, tn3270eIpGroupRowStatus, tn3270eResPoolElementType, tn3270eResPoolIpGroupName, tn3270eResPoolClientPort, tn3270eResPoolRowStatus } STATUS current DESCRIPTION "This group is optional and allows a server to configure a collection of IP Address and Resource Pools and their mappings." ::= { tn3270eGroups 2 } tn3270eSessionGroup OBJECT-GROUP OBJECTS { tn3270eTcpConnLastActivity, tn3270eTcpConnBytesIn, tn3270eTcpConnBytesOut, tn3270eTcpConnTargetAppl, tn3270eTcpConnResourceName, tn3270eTcpConnResourceType, tn3270eTcpConnClientUserId, tn3270eTcpConnDeviceType, tn3270eTcpConnProto Expires December 1997 [Page 28] White TN3270E Management Information Base (TN3270E-MIB)26 June 1997 } STATUS current DESCRIPTION "This group is mandatory for all hosts supporting the TN3270E-MIB." ::= { tn3270eGroups 3 } END 5. Security Considerations Certain management information defined in this MIB may be considered sensitive in some network environments. Therefore, authentication of received SNMP requests and controlled access to management information should be employed in such environments. The method for this authentication is a function of the SNMP Administrative Framework, and has not been expanded by this MIB. Several objects in this MIB allow write access or provide for remote creation. Allowing this support in a non-secure environment can have a negative effect on network operations. It is recommended that implementers seriously consider whether set operations should be allowed without providing, at a minimum, authentication of request origin. It it recommended that without such support that the following objects be implemented as read-only: o tn3270eSrvrConfInactivityTimer o tn3270eSrvrConfActivityCheck o tn3270eSrvrConfActivityTimeout o tn3270eSrvrConfActivityInterval o tn3270eSrvrConfAdminStatus o tn3270eSrvrConfSessionTermState o tn3270eIpGroupSubnetMask o tn3270eResPoolIpGroupName o tn3270eResPoolElementType o tn3270eResPoolClientPort o tn3270eResMapIpAddress o tn3270eResMapSubnetMask o tn3270eResMapElementType o tn3270eIpMapResElementName o tn3270eIpMapElementType The following objects should either be implemented as read-only or not implemented when security is an issue as previously discussed: o tn3270eSrvrConfRowStatus o tn3270eSrvrPortRowStatus Expires December 1997 [Page 29] White TN3270E Management Information Base (TN3270E-MIB)26 June 1997 o tn3270eIpGroupRowStatus o tn3270eResPoolRowStatus o tn3270eResMapRowStatus o tn3270eIpMapRowStatus 6. Acknowledgments This document is a product of the TN3270E Working Group. 7. References [1] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and Waldbusser S., "Structure of Management Information for version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1902, January 1996. [2] Network Working Group, Postel, J., and Reynolds, J., "Telnet Protocol Specification", RFC 854, May 1983. [3] Network Working Group, Postel, J., and Reynolds, J., "Telnet Timing Mark Option", RFC 860, May 1983. [4] Network Working Group and Rekhter J., "Telnet 3270 Regime Option", RFC 1041, January 1988. [5] McCloghrie, K., and M. Rose, Editors, "Management Information Base for Network Management of TCP/IP-based internets: MIB-II", STD 17, RFC 1213, Hughes LAN Systems, Performance Systems International, March 1991. [6] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Textual Conventions for version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1903, January 1996. [7] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol Operations for version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1905, January 1996. Expires December 1997 [Page 30] White TN3270E Management Information Base (TN3270E-MIB)26 June 1997 [8] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Conformance Statements for version 2 of the Simple Network Management Protocol (SNMPv2)", RFC 1904, January 1996. [9] Case, J., M. Fedor, M. Schoffstall, J. Davin, "Simple Network Management Protocol", RFC 1157, SNMP Research, Performance Systems International, MIT Laboratory for Computer Science, May 1990. [10] IETF SNMPv2 Working Group and McCloghrie, K., "TCP-MIB Definitions", November 1994. 8. Authors' Address Kenneth D. White Dept. G80/Bldg 503 IBM Corporation Research Triangle Park, NC 27709, USA E-mail: kennethw@vnet.ibm.com Expires December 1997 [Page 31]   Received: from cnri by ietf.org id aa05358; 30 Jun 97 8:01 EDT Received: from list.nih.gov (list.nih.gov [165.112.130.6]) by cnri.reston.va.us (8.8.5/8.7.3) with ESMTPid IAA15164 for ; Mon, 30 Jun 1997 08:00:26 -0400 (EDT) Received: from list.nih.gov (terrific.net.nih.gov [165.112.130.6]) by list.nih.gov (8.8.5/8.8.5) with ESMTP id HAA28834; Mon, 30 Jun 1997 07:54:00 -0400 (EDT) Received: from LIST.NIH.GOV by LIST.NIH.GOV (LISTSERV-TCP/IP release 1.8c) with spool id 2818148 for TN3270E@LIST.NIH.GOV; Mon, 30 Jun 1997 07:53:58 -0400 Received: from nmi-gate.netmanage.co.il (root@nmi-gate.netmanage.co.il [156.27.240.10]) by list.nih.gov (8.8.5/8.8.5) with SMTP id HAA28821 for ; Mon, 30 Jun 1997 07:53:55 -0400 (EDT) Received: from Paula_lt.netmanage.co.il (paula2.netmanage.co.il [156.27.241.176]) by nmi-gate.netmanage.co.il (8.6.9/8.6.9) with SMTP id OAA07488; Mon, 30 Jun 1997 14:53:47 +0300 Date: Mon, 30 Jun 1997 14:51:53 +0200 From: Paula Parash Subject: 3270E server required To: tn3270e@list.nih.gov Cc: yoav@netmanage.co.il, zivo@netmanage.co.il X-Mailer: Z-Mail Pro ZM61_26 (Win32 - 021297), NetManage Inc. X-Face: 2}PO!JC`@AsQt_C!/L=&b7#i7Sx}n5wNP??S_@q^udbbj5>4)t|J@n(1wrB+Rb`JlA.n1GG nsTN>mxYSRg(cVqDz>QO6x*L_9ixh<@qS~$LhOEI0Uas.CRJNSlu39}"G/_"r+E'"TQEF(eoq=9_sA '^})vU];Xx3j/0,d(ay\:-!Z*!oC X-Priority: 3 (Normal) Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=ISO-8859-1 Sender: owner-tn3270e@list.nih.gov Netmanage is about to release a new product which will include its improved 3270E client. For the stage of my final tests, I am now looking for 3270E servers out there which I can access and work against. I am interested in testing both our terminal and printer clients. If anyone knows of such servers, I'd appreciate any information you can supply. Thanks, Paula ================================================================================ Paula Parash - Phone ext. 486 SQA Engineer , Haifa. NetManage Israel Ltd. Fax :(972)-4-8550123 E-mail: paulaP@netmanage.co.il Date : 06/30/97 ** Complete PC Connectivity to IBM Mainframe and Midrange ** NetManage Home Page : http://www.NetManage.com For FREE software www.netmanage.com ................................................................................... "At every layer of the protocols, there is a general rule whose application can lead to enormous benefits in robustness and interoperability : BE LIBERAL IN WHAT YOU ACCEPT, AND CONSERVATIVE IN WHAT YOU SEND" ................................................................................... ===================================================================================