idnits 2.17.1 draft-ietf-tn3270e-tn3270-mib-04.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-26) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity. ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 1) being 2518 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 83 instances of too long lines in the document, the longest one being 8 characters in excess of 72. ** The abstract seems to contain references ([1]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 1093 has weird spacing: '...is data can b...' == Line 1112 has weird spacing: '...is data can b...' -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (November 1997) is 9659 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: '2' is defined on line 2098, but no explicit reference was found in the text == Unused Reference: '4' is defined on line 2104, but no explicit reference was found in the text == Unused Reference: '10' is defined on line 2128, but no explicit reference was found in the text == Unused Reference: '11' is defined on line 2136, but no explicit reference was found in the text ** Obsolete normative reference: RFC 1902 (ref. '1') (Obsoleted by RFC 2578) ** Downref: Normative reference to an Historic RFC: RFC 1041 (ref. '4') ** Obsolete normative reference: RFC 1903 (ref. '6') (Obsoleted by RFC 2579) ** Obsolete normative reference: RFC 1905 (ref. '7') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 1904 (ref. '8') (Obsoleted by RFC 2580) ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. '9') -- Possible downref: Non-RFC (?) normative reference: ref. '10' -- Possible downref: Non-RFC (?) normative reference: ref. '11' -- Possible downref: Non-RFC (?) normative reference: ref. '12' Summary: 16 errors (**), 0 flaws (~~), 8 warnings (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 TN3270E Working Group 3 INTERNET DRAFT: Kenneth White 4 Expiration Date: May, 1998 5 IBM Corp. 7 November 1997 9 Base Definitions of Managed Objects for 10 TN3270E Using SMIv2 12 14 Status of this Memo 16 This document is an Internet Draft. Internet Drafts are working 17 documents of the Internet Engineering Task Force (IETF), its Areas, 18 and its Working Groups. Note that other groups may also distribute 19 working documents as Internet Drafts. 21 Internet Drafts are draft documents valid for a maximum of six 22 months. Internet Drafts may be updated, replaced, or obsoleted by 23 other documents at any time. It is not appropriate to use Internet 24 Drafts as reference material or to cite them other than as a "working 25 draft" or "work in progress." 27 Please check the I-D abstract listing contained in each Internet 28 Draft directory to learn the current status of this or any Internet 29 Draft. Distribution of this document is unlimited. 31 Abstract 33 The purpose of this memo is to define a Management Information Base 34 (MIB) for configuring and managing TN3270E Servers. 35 The MIB defined by this memo is intended to provide generic 36 support for both Host and Gateway TN3270E server implementations. 37 It is the intent that the MIB defined herein be extended 38 by subsequent memos to provide non-generic configuration support 39 and to enable TN3270E Response Time Collection. 41 It is the intent of this MIB to fully adhere to all prerequisite MIBs 42 unless explicitly stated. Deviations will be documented in 43 corresponding conformance statements. The specification of this MIB 44 will utilize the Structure of Management Information (SMI) for 45 Version 2 of the Simple Network Management Protocol Version (refer to 46 RFC1902, reference [1]). 48 Table of Contents 50 Expires May 1998 [Page 1]~ 52 White TN3270E Management Information Base (TN3270E-MIB) 20 November 1997 54 1.0 Introduction............................................. 2 55 2.0 The SNMPv2 Network Management Framework.................. 2 56 2.1 Object Definitions....................................... 3 57 3.0 Structure of the MIB..................................... 3 58 3.1 TN3270E Server Control................................... 4 59 3.1.1 tn3270eSrvrConfTable................................... 4 60 3.1.2 tn3270eSrvrPortTable................................... 5 61 3.1.3 tn3270eSrvrStatsTable.................................. 5 62 3.2 TN3270E Server Resource Configuration.................... 6 63 3.3 Resource/Client Address Mappings......................... 6 64 3.3.1 tn3270eSnaMapTable..................................... 6 65 3.3.2 tn3270eResMapTable..................................... 6 66 3.3.3 TCP Connection Table Additions......................... 7 67 4.0 Definitions.............................................. 7 68 5.0 Security Considerations..................................40 69 6.0 Acknowledgments..........................................40 70 7.0 References...............................................41 71 8.0 Authors' Address.........................................42 73 1. Introduction 75 This document is a product of the TN3270E Working Group. Its purpose 76 is to define a MIB module for extending the traditional MIBs supported 77 by a TCP/IP implementation for configuration and management of TN3270E 78 servers. 80 2. The SNMPv2 Network Management Framework 82 The SNMP Network Management Framework presently consists of three 83 major components. They are: 85 o the SMI, described in RFC 1902 [1], - the mechanisms used for 86 describing and naming objects for the purpose of management. 88 o the MIB-II, STD 17, RFC 1213 [5], - the core set of managed 89 objects for the Internet suite of protocols. 91 o the protocol, RFC 1157 [9] and/or RFC 1905 [7] - the protocol 92 for accessing managed information. 94 Textual conventions are defined in RFC 1903 [6], and conformance 95 statements are defined in RFC 1904 [8]. 97 The Framework permits new objects to be defined for the purpose of 98 experimentation and evaluation. 100 Expires May 1998 [Page 2]~ 102 White TN3270E Management Information Base (TN3270E-MIB) 20 November 1997 104 This memo specifies a MIB module that is compliant to the SNMPv2 SMI. 105 A semantically identical MIB conforming to the SNMPv1 SMI can be 106 produced through the appropriate translation. 108 2.1. Object Definitions 110 Managed objects are accessed via a virtual information store, termed 111 the Management Information Base or MIB. Objects in the MIB are 112 defined using the subset of Abstract Syntax Notation One (ASN.1) 113 defined in the SMI. In particular, each object object type is named 114 by an OBJECT IDENTIFIER, an administratively assigned name. The 115 object type together with an object instance serves to uniquely 116 identify a specific instantiation of the object. For human 117 convenience, we often use a textual string, termed the descriptor, to 118 refer to the object type. 120 3. Structure of the MIB 122 The TN3270E-MIB is split into the following components: 124 o TN3270E Server Control 125 o TN3270E Server Resource Configuration 126 o Resource/Client Address Mappings 128 The TN3270E-MIB is defined primarily for TN3270E servers. This memo 129 does not explicitly address use of the MIB by TN3270 servers that do 130 not support the TN3270E protocol. Although a significant number of 131 the objects do apply in the TN3270-only case, the case was not 132 addressed since it is unlikely that a TN3270-only server would 133 implement this MIB. 135 The SYSAPPL-MIB, reference [12], is a prerequisite for the TN3270E- 136 MIB, so that the Utf8String Textual Convention (TC) can be imported. 137 This TC, which is used for some MIB objects containing textual 138 information, enables internationalization of text strings, whereas the 139 DisplayString TC does not. 141 The MIB defined by this memo handles both IPv4 and IPv6 addressing. 142 Two Textual Conventions, Tn3270eAddrType and Tn3270eTAddress, are 143 defined for this purpose. Tn3270eTAddress is essentially equivalent 144 to TAddress, defined by RFC 1903. The difference is that 145 Tn3270eTAddress allows a null-length octet string, while TAddress 146 doesn't. Allowing a null IP Address is important, since in places 147 Tn3270eTAddress object values are used as a component of an object 148 instance, and need not actually contain an IP Address. In general, use 150 Expires May 1998 [Page 3]~ 152 White TN3270E Management Information Base (TN3270E-MIB) 20 November 1997 154 of Tn3270eTAddress replaces the prior use of IpAddress to represent IP 155 Addresses. 157 Tn3270eAddrType is functionally equivalent to the TDomain TC, also 158 defined by RFC 1903. TDomain uses an OID to identify the contents of 159 a TAddress object. Tn3270eAddrType was chosen over TDomain because, 160 with a SYNTAX of Unsigned32 (enumeration type), it is much simpler 161 than an OID to specify in an instance identifier. 163 3.1. TN3270E Server Control 165 This group of objects provides for TN3270E server configuration, and 166 consists of: 168 o tn3270eSrvrConfTable 169 o tn3270eSrvrPortTable 170 o tn3270eSrvrStatsTable 172 3.1.1. tn3270eSrvrConfTable 174 The tn3270eSrvrConfTable contains a set of objects primarily for 175 configuring and managing a TN3270E server. As with most of the other 176 tables in the TN3270E-MIB, this table is indexed by an unsigned 177 integer, tn3270eSrvrConfIndex. This primary index element enables 178 support of multiple TN3270E servers on the same host. Within a host, 179 tn3270eSrvrConfIndex values must be unique, and need not be 180 contiguous; otherwise these values are implementation-dependent. 182 An earlier version of this memo had used the local IP Address 183 associated with a TN3270E server along with tn3270eSrvrConfIndex as 184 the primary indexes into most of its tables. Use of a local IP 185 Address was thought to enable use of these tables by management 186 applications. This approach was dropped, since it introduces a level 187 of complexity into MIB table indexing for little actual benefit. 189 tn3270eSrvrConfInactivityTimer defines the inactivity period for 190 TN3270 and TN3270E Sessions. tn3270eSrvrConfSessionTermState defines 191 how a session should be terminated. The three objects: 193 o tn3270eSrvrConfActivityCheck 194 o tn3270eSrvrConfActivityTimeout 195 o tn3270eSrvrConfActivityInterval 197 define the parameters for performing the "Telnet Timing Mark Option" 198 as defined by RFC 860 [3]. The object tn3270eSrvrConfActivityCheck is 199 defined to enable selection of either a NOP command or a TIMEMARK 201 Expires May 1998 [Page 4]~ 203 White TN3270E Management Information Base (TN3270E-MIB) 20 November 1997 205 command. Sending a NOP command results in less overhead then a 206 TIMEMARK command, since a client doesn't send a reply. 208 The objects tn3270eSrvrConfAdminStatus and tn3270eSrvrConfOperStatus 209 enable remote starting and stopping of a TN3270E server. 210 tn3270eSrvrConfFunctionsSupported indicates which of the TN3270 and 211 TN3270E options a server supports. The object 212 tn3270eSrvrConfSessionTermState defines as a global option the 213 processing steps that a TN3270E server should perform when a TN3270E 214 session terminates with respect to the associated TCP connection. The 215 object tn3270eSrvrConfSrvrType indicates whether the TN3270E server 216 represented by the tn3270eSrvrConfEntry is a host or a gateway server. 217 The object tn3270eSrvrConfContact provides a scratch pad area for a 218 TN3270E server administrator to store information for later retrieval. 219 The object tn3270eSrvrConfRowStatus provides the capability to perform 220 remote creation and deletion operations on this table. 222 3.1.2. tn3270eSrvrPortTable 224 The tn3270eSrvrPortTable exists in order to assign and retrieve the 225 local TCP ports associated with a TN3270E server, since some TN3270E 226 server implementations support multiple local ports. A 227 tn3270eSrvrPortEntry is indexed by: 229 o tn3270eSrvrConfIndex 230 o tn3270eSrvrConfPort 231 o tn3270eSrvrConfPortAddrType 232 o tn3270eSrvrConfPortAddress 234 Certain TN3270E server implementations retrict a local TCP port to a 235 particular local IP Address, instead of allowing connections for any 236 local IP Address to occur via the port. tn3270eSrvrConfPortAddrType 237 and tn3270eSrvrConfPortAddress allow this restriction to be 238 represented in the MIB. A TN3270E server that doesn't restrict 239 connections over a port to a local IP Address should use the value 240 'unknown(0)' for tn3270eSrvrConfPortAddrType, and a null octet string 241 for tn3270eSrvrConfPortAddress. 243 3.1.3. tn3270eSrvrStatsTable 245 The tn3270eSrvrStatsTable defines a series of objects used to provide 246 general statistics on the use of a TN3270E server. 248 Expires May 1998 [Page 5]~ 250 White TN3270E Management Information Base (TN3270E-MIB) 20 November 1997 252 3.2. TN3270E Server Resource Configuration 254 The TN3270E Server Resource Configuration collection of objects consists 255 of three tables: 257 o tn3270eClientGroupTable 258 o tn3270eResPoolTable 259 o tn3270eClientResMapTable 261 tn3270eClientGroupTable and tn3270eResPoolTable enable implementations 262 to define groupings of both client addresses and resource pools for 263 mapping client addresses to resources. The mapping of a client group to 264 a resource pool is enabled via the tn3270eClientResMapTable. 266 3.3. Resource/Client Address Mappings 268 Three tables are defined by this memo to enable mapping of resource 269 names to client addresses, and client addresses to resource names: 271 o tn3270eSnaMapTable 272 o tn3270eResMapTable 273 o TCP Connection Table Additions 275 3.3.1. tn3270eSnaMapTable 277 The tn3270eSnaMapTable is a read-only table that maps a secondary LU's 278 SNA network name to the name by which it is known locally at the TN3270e 279 server. For correlation with data from a SNA network provision is made 280 for representation of the associating primary LU name in a 281 tn3270eSnaMapEntry. An entry in this table is created when the Activate 282 LU (ACTLU) request carrying the SNA network name of the SLU is received 283 from the SSCP. The entry is deleted when the SLU is deactivated. 285 3.3.2. tn3270eResMapTable 287 The tn3270eResMapTable is a read-only table that maps a resource name to 288 a client's address. An entry in this table is created when a TCP 289 connection is received by a TN3270E server and mapped to a resource. The 290 entry is deleted when the resource-to-address association is no longer 291 valid. 293 Expires May 1998 [Page 6]~ 295 White TN3270E Management Information Base (TN3270E-MIB) 20 November 1997 297 3.3.3. TCP Connection Table Additions 299 The TCP Connection Table is defined by RFC 2012 (Refer to reference 10, 300 TCP-MIB Definitions). Traditionally, the contents of the TCP Connection 301 Table have been implementation-dependent. Its formal definition 302 consists of the following objects: 304 o tcpConnState (INTEGER) 305 o tcpConnLocalAddress (IpAddress) 306 o tcpConnLocalPort (INTEGER) 307 o tcpConnRemAddress (IpAddress) 308 o tcpConnRemPort (INTEGER) 310 It is indexed by: tcpConnLocalAddress, tcpConnLocalPort, 311 tcpConnRemAddress, and tcpConnRemPort. 313 The tn3270eTcpConnTable contains objects for keeping a list of the 314 current set of TN3270 and TN3270E sessions at a TN3270E server. The 315 relationship between the tcpConnTable and the Tn3270eTcpConnTable is not 316 one-to-one, since the tn3270eTcpConnTable contains information 317 pertaining only to TN3270(E) sessions. 319 The tn3270eTcpConnTable has a different indexing structure from that of 320 the tcpConnTable. Instead of using IpAddress objects, Tn3270eTAddress 321 and Tn3270eAddrType object pairs are used to specify client addresses 322 (both local and remote). This enables support of IPv6 addresses. In 323 addition, the remote address pair precedes the local address pair in the 324 index clause, in order to enable a GET-NEXT operation using only the 325 remote address pair. 327 4. Definitions 329 TN3270E-MIB DEFINITIONS ::= BEGIN 331 IMPORTS 332 -- Some MIB Compilers require BITS to be imported from 333 -- the SNMPv2-SMI 334 MODULE-IDENTITY, OBJECT-TYPE, Unsigned32, 335 TimeTicks, IpAddress, 336 Counter32, Gauge32, Counter64 337 FROM SNMPv2-SMI 338 TEXTUAL-CONVENTION, RowStatus 339 FROM SNMPv2-TC 340 MODULE-COMPLIANCE, OBJECT-GROUP 341 FROM SNMPv2-CONF 342 snanauMIB 343 FROM SNA-NAU-MIB 345 Expires May 1998 [Page 7]~ 347 White TN3270E Management Information Base (TN3270E-MIB) 20 November 1997 349 Utf8String 350 FROM SYSAPPL-MIB; 352 tn3270eMIB MODULE-IDENTITY 353 LAST-UPDATED "9711200000Z" -- November 20, 1997 354 ORGANIZATION "TN3270E Working Group" 355 CONTACT-INFO 356 "Kenneth White (kennethw@vnet.ibm.com) 357 IBM Corp." 358 DESCRIPTION 359 "This module defines a portion of the management 360 information base (MIB) for managing TN3270E servers" 361 ::= { snanauMIB 8 } 363 -- Textual Conventions 365 SnaResourceName ::= TEXTUAL-CONVENTION 366 STATUS current 367 DESCRIPTION 368 "The textual convention for defining an SNA resource 369 name. A fully qualified SNA resource name, consisting of 370 a 1 to 8 character network identifier (NetId), a 371 period ('.'), and a 1 to 8 character resource name 372 (ResName). 374 The NetId and ResName are constructed from the uppercase 375 letter 'A' - 'Z' and the numerics '0' - '9', all encoded 376 in ASCII, with the restriction that the first character 377 of each must be a letter. Trailing blanks are not allowed. 379 Earlier versions of SNA permitted three additional 380 characters in NetIds and ResNames: '#', '@', and '$'. 381 While this use of these characters has been retired, 382 a Management Station should still accept them for 383 backward compatibility. 385 Note: This Textual Convention is not subject to 386 internationalization, and does not use the character 387 encodings used by the Utf8String Textual Convention." 388 SYNTAX OCTET STRING (SIZE(0..17)) 390 Tn3270eAddrType ::= TEXTUAL-CONVENTION 391 STATUS current 392 DESCRIPTION 393 "The textual convention for defining the type of an Client 394 Address." 395 SYNTAX INTEGER { 396 unknown(0), 398 Expires May 1998 [Page 8]~ 400 White TN3270E Management Information Base (TN3270E-MIB) 20 November 1997 402 ipv4(1), 403 ipv6(2) 404 } 406 Tn3270ResourceType ::= TEXTUAL-CONVENTION 407 STATUS current 408 DESCRIPTION 409 "The type of resource defined by a resource pool. Refer 410 to tn3270eResPoolTable." 411 SYNTAX INTEGER { 412 other(0), 413 lu(1), 414 printer(2) 415 } 417 Tn3270eTAddress ::= TEXTUAL-CONVENTION 418 STATUS current 419 DESCRIPTION 420 "Denotes an Client Address. The type of Client Address is 421 determined by use of the Tn3270eAddrType Textual 422 Convention. 423 The length in octets of a Tn3270eTAddress object is: 425 Tn3270eAddrType ENUM 426 unknown(0) not known, must look at the 427 actual length of the 428 Tn3270eTAddress OCTET STRING. 429 ipv4(1) 4 OCTETS 430 ipv6(2) 16 OCTETS 432 This textual convention is similar to the TAddress TC 433 defined by RFC1903 except that it allows a zero length 434 OCTET STRING and is not a full transport layer address." 435 SYNTAX OCTET STRING (SIZE (0..255)) 437 Tn3270Functions ::= TEXTUAL-CONVENTION 438 STATUS current 439 DESCRIPTION 440 "This textual convention is intended to reflect the 441 current set of TN3270 and TN3270E functions that can 442 be negotiated between a server and its client: 444 RFC856 445 transmitBinary The sender of this command REQUESTS 446 permission to begin transmitting, or 447 confirms that it will now begin transmitting 448 characters which are to be interpreted 450 Expires May 1998 [Page 9]~ 452 White TN3270E Management Information Base (TN3270E-MIB) 20 November 1997 454 as 8 bits of binary data by 455 the receiver of the data. 456 RFC820 457 timeMark The sender of this command REQUESTS that 458 the receiver of this command return a WILL 459 TIMING-MARK in the data stream at the 460 'appropriate place' ... 461 RFC885 462 endOfRecord The sender of this command requests 463 permission to begin transmission of the 464 Telnet END-OF-RECORD (EOR) code when 465 transmitting data characters, or 466 the sender of this command confirms it will 467 now begin transmission of EORs with 468 transmitted data characters. 469 RFC1091 470 terminalType Sender is willing to send terminal type 471 information in a subsequent sub-negotiation. 472 RFC1041 473 tn3270Regime Sender is willing to send list of supported 474 3270 Regimes in a subsequent sub-negotiation. 475 RFC1647 476 scsCtlCodes (Printer sessions only). Allows the use 477 of the SNA Character Stream (SCS) and SCS 478 control codes on the session. SCS is 479 used with LU type 1 SNA sessions. 480 dataStreamCtl (Printer sessions only). Allows the use 481 of the standard 3270 data stream. This 482 corresponds to LU type 3 SNA sessions. 483 responses Provides support for positive and 484 negative response handling. Allows the 485 server to reflect to the client any and 486 all definite, exception, and no response 487 requests sent by the host application. 488 bindImage Allows the server to send the SNA Bind 489 image and Unbind notification to the 490 client. 491 sysreq Allows the client and server to emulate 492 some (or all, depending on the server) of 493 the functions of the SYSREQ key in an SNA 494 environment." 495 SYNTAX BITS { 496 transmitBinary(0),-- rfc856 497 timemark(1), -- rfc860 498 endOfRecord(2), -- rfc885 499 terminalType(3), -- rfc1091 500 tn3270Regime(4), -- rfc1041 501 scsCtlCodes(5), -- rfc1647 503 Expires May 1998 [Page 10]~ 505 White TN3270E Management Information Base (TN3270E-MIB) 20 November 1997 507 dataStreamCtl(6), -- rfc1647 508 responses(7), -- rfc1647 509 bindImage(8), -- rfc1647 510 sysreq(9) -- rfc1647 511 } 513 Tn3270DeviceTypes ::= TEXTUAL-CONVENTION 514 STATUS current 515 DESCRIPTION 516 "This textual convention defines the list of device types 517 that can be set as defined by RFC 1647." 518 SYNTAX INTEGER { -- terminals 519 unknown(0), 520 ibm3278d2(1), -- (24 row x 80 col display) 521 ibm3278d2E(2), -- (24 row x 80 col display) 522 ibm3278d3(3), -- (32 row x 80 col display) 523 ibm3278d3E(4), -- (32 row x 80 col display) 524 ibm3278d4(5), -- (43 row x 80 col display) 525 ibm3278d4E(6), -- (43 row x 80 col display) 526 ibm3278d5(7), -- (27 row x 132 col display) 527 ibm3278d5E(8), -- (27 row x 132 col display) 528 ibmDynamic(9), -- (no pre-defined display size) 529 ibm3287d1(10) -- printers 530 } 532 -- Top-level structure of the MIB 534 tn3270eNotifications OBJECT IDENTIFIER ::= { tn3270eMIB 0 } 535 tn3270eObjects OBJECT IDENTIFIER ::= { tn3270eMIB 1 } 536 tn3270eConformance OBJECT IDENTIFIER ::= { tn3270eMIB 3 } 538 -- MIB Objects 540 tn3270eSrvrConfTable OBJECT-TYPE 541 SYNTAX SEQUENCE OF Tn3270eSrvrConfEntry 542 MAX-ACCESS not-accessible 543 STATUS current 544 DESCRIPTION 545 "This table defines the configuration elements for 546 TN3270E Servers. The number of entries in this table 547 is expected to vary depending on the location of the 548 table. A particular TN3270E server is expected to 549 have a single entry. Modeling of the configuration 550 elements as a table allows multiple 551 TN3270E Servers to exist at the same host." 552 ::= { tn3270eObjects 1 } 554 tn3270eSrvrConfEntry OBJECT-TYPE 556 Expires May 1998 [Page 11]~ 558 White TN3270E Management Information Base (TN3270E-MIB) 20 November 1997 560 SYNTAX Tn3270eSrvrConfEntry 561 MAX-ACCESS not-accessible 562 STATUS current 563 DESCRIPTION 564 "Definition of the configuration elements for a single 565 TN3270E server." 566 INDEX { tn3270eSrvrConfIndex } 567 ::= { tn3270eSrvrConfTable 1 } 569 Tn3270eSrvrConfEntry ::= SEQUENCE { 570 tn3270eSrvrConfIndex Unsigned32, 571 tn3270eSrvrConfInactivityTimeout Unsigned32, 572 tn3270eSrvrConfActivityCheck INTEGER, 573 tn3270eSrvrConfActivityTimeout Unsigned32, 574 tn3270eSrvrConfActivityInterval Unsigned32, 575 tn3270eSrvrFunctionsSupported Tn3270Functions, 576 tn3270eSrvrConfAdminStatus INTEGER, 577 tn3270eSrvrConfOperStatus INTEGER, 578 tn3270eSrvrConfSessionTermState INTEGER, 579 tn3270eSrvrConfSrvrType INTEGER, 580 tn3270eSrvrConfContact Utf8String, 581 tn3270eSrvrConfRowStatus RowStatus 582 } 584 tn3270eSrvrConfIndex OBJECT-TYPE 585 SYNTAX Unsigned32 586 MAX-ACCESS not-accessible 587 STATUS current 588 DESCRIPTION 589 "Indicates the instance of a TN3270E server that 590 exists at an IP Host. Assignments of tn3270eSrvrConfIndex 591 values need not be continuous and is implementation 592 dependent. Within a host, assignment of 593 tn3270eSrvrConfIndex values must be unique." 594 ::= { tn3270eSrvrConfEntry 1 } 596 tn3270eSrvrConfInactivityTimeout OBJECT-TYPE 597 SYNTAX Unsigned32 (0..99999999) 598 UNITS "seconds" 599 MAX-ACCESS read-create 600 STATUS current 601 DESCRIPTION 602 "The inactivity time-out specified in seconds. When a 603 connection has been inactive for the number of seconds 604 specified by this object it is closed. The default of 605 0 means no inactivity time-out." 606 DEFVAL { 0 } 607 ::= { tn3270eSrvrConfEntry 2 } 609 Expires May 1998 [Page 12]~ 611 White TN3270E Management Information Base (TN3270E-MIB) 20 November 1997 613 tn3270eSrvrConfActivityCheck OBJECT-TYPE 614 SYNTAX INTEGER { 615 noCheck(0), 616 timeMark(1), 617 nop(2) 618 } 619 MAX-ACCESS read-create 620 STATUS current 621 DESCRIPTION 622 "This object is intended to enable either timemark or 623 nop processing." 624 DEFVAL { noCheck } 625 ::= { tn3270eSrvrConfEntry 3 } 627 tn3270eSrvrConfActivityTimeout OBJECT-TYPE 628 SYNTAX Unsigned32 (1..99999999) 629 UNITS "seconds" 630 MAX-ACCESS read-create 631 STATUS current 632 DESCRIPTION 633 "The TIMEMARK or NOP processing time-out specified in seconds. 634 Note that a value of 0 is not allowed for this object since 635 the function that uses this object relies on 636 tn3270eSrvrConfActivityCheck for function enablement." 637 DEFVAL { 600 } -- 10 minutes 638 ::= { tn3270eSrvrConfEntry 4 } 640 tn3270eSrvrConfActivityInterval OBJECT-TYPE 641 SYNTAX Unsigned32 (1..99999999) 642 UNITS "seconds" 643 MAX-ACCESS read-create 644 STATUS current 645 DESCRIPTION 646 "The scan interval to be used by a TN3270E server. 647 TIMEMARK or NOP processing scans the Telnet sessions 648 on the interval provided by this object looking for 649 sessions that have been idle for more than the value 650 provided by tn3270eSrvrConfActivityTimeout. 651 Note that a value of 0 is not allowed for this object since 652 the function that uses this object relies on 653 tn3270eSrvrConfActivityCheck for function enablement." 654 DEFVAL { 120 } -- 2 minutes 655 ::= { tn3270eSrvrConfEntry 5 } 657 tn3270eSrvrFunctionsSupported OBJECT-TYPE 658 SYNTAX Tn3270Functions 659 MAX-ACCESS read-only 660 STATUS current 662 Expires May 1998 [Page 13]~ 664 White TN3270E Management Information Base (TN3270E-MIB) 20 November 1997 666 DESCRIPTION 667 "This object indicates the functions supported by a 668 TN3270E server." 669 DEFVAL { { scsCtlCodes, dataStreamCtl, 670 responses, bindImage, sysreq } } 671 ::= { tn3270eSrvrConfEntry 6 } 673 tn3270eSrvrConfAdminStatus OBJECT-TYPE 674 SYNTAX INTEGER { 675 up(1), 676 down(2), 677 stopImmediate(3) 678 } 679 MAX-ACCESS read-create 680 STATUS current 681 DESCRIPTION 682 "The desired state of the TN3270E server: 684 up(1) - Activate a TN3270E server. 685 down(2) - Informs the associating TN3270E server 686 to gracefully terminate its processing. 687 stopImmediate(3) - Informs the associating TN3270E server 688 to terminate immediately. 690 Implementation as to the exact semantics of either down(2) 691 or stopImmediate(3) processing is left as implementation 692 dependent. A TN3270E server that does not distinguish 693 between down or stopImmediate transitions should not 694 support stopImmediate." 695 ::= { tn3270eSrvrConfEntry 7 } 697 tn3270eSrvrConfOperStatus OBJECT-TYPE 698 SYNTAX INTEGER { 699 up(1), 700 down(2) 701 } 702 MAX-ACCESS read-only 703 STATUS current 704 DESCRIPTION 705 "The current operational state of a TN3270E server: 707 up(1) - The corresponding TN3270E server is active. 708 down(2) - The corresponding TN3270E server is inactive." 709 ::= { tn3270eSrvrConfEntry 8 } 711 tn3270eSrvrConfSessionTermState OBJECT-TYPE 712 SYNTAX INTEGER { 713 terminate(1), 715 Expires May 1998 [Page 14]~ 717 White TN3270E Management Information Base (TN3270E-MIB) 20 November 1997 719 luSessionPend(2), 720 queueSession(3) 721 } 722 MAX-ACCESS read-create 723 STATUS current 724 DESCRIPTION 725 "The current state for determining what a TN3270E server 726 should do when a TN3270 Session terminates: 728 terminate(1) => Terminate TCP connection. 729 luSessionPend(2) => Do not drop the TCP Connection 730 associated with a client when their 731 TN3270 Session ends. Processing should 732 redrive session initialization as if the 733 client was first connecting. 734 queueSession(3) => QUEUESESSION deals with CLSDST-Pass. 735 An example is the easiest explanation. 736 Assume APPL1 does a CLSDST-Pass 737 to APPL2. Then the client logs off APPL 738 Without QUEUESESSION the connection 739 would now be broken. With QUEUESESSION 740 the TN3270E server keeps the LU around 741 after getting the APPL2 unbind waiting 742 for a bind from APPL1." 743 DEFVAL { terminate } 744 ::= { tn3270eSrvrConfEntry 9 } 746 tn3270eSrvrConfSrvrType OBJECT-TYPE 747 SYNTAX INTEGER { 748 unknown(0), 749 host(1), 750 gateway(2) 751 } 752 MAX-ACCESS read-only 753 STATUS current 754 DESCRIPTION 755 "This object indicates the type of TN3270E server. 756 The existence of MIB tables and objects that will be 757 defined by follow-on MIBs may be predicated on whether the 758 TN3270E server can be local to the same host as a 759 Target Application (host(1)) or will always be remote 760 (gateway(2))." 761 ::= { tn3270eSrvrConfEntry 10 } 763 tn3270eSrvrConfContact OBJECT-TYPE 764 SYNTAX Utf8String (SIZE(0..255)) 765 MAX-ACCESS read-create 766 STATUS current 768 Expires May 1998 [Page 15]~ 770 White TN3270E Management Information Base (TN3270E-MIB) 20 November 1997 772 DESCRIPTION 773 "This object provides a scratch pad for a TN3270E server 774 administrator for storing information for later retrieval." 775 ::= { tn3270eSrvrConfEntry 11 } 777 tn3270eSrvrConfRowStatus OBJECT-TYPE 778 SYNTAX RowStatus 779 MAX-ACCESS read-create 780 STATUS current 781 DESCRIPTION 782 "This object allows entries to be created and deleted in the 783 tn3270eSrvrConfTable. 785 An entry in this table is deleted by setting this object 786 to destroy(6)." 787 REFERENCE 788 "RFC 1903, 'Textual Conventions for version 2 of the Simple 789 Network Management Protocol (SNMPv2).'" 790 ::= { tn3270eSrvrConfEntry 12 } 792 tn3270eSrvrPortTable OBJECT-TYPE 793 SYNTAX SEQUENCE OF Tn3270eSrvrPortEntry 794 MAX-ACCESS not-accessible 795 STATUS current 796 DESCRIPTION 797 "This table defines the TCP ports associated with TN3270E 798 Servers." 799 ::= { tn3270eObjects 2 } 801 tn3270eSrvrPortEntry OBJECT-TYPE 802 SYNTAX Tn3270eSrvrPortEntry 803 MAX-ACCESS not-accessible 804 STATUS current 805 DESCRIPTION 806 "Definition of a single TCP port assignment to a 807 TN3270E server." 808 INDEX { 809 tn3270eSrvrConfIndex, 810 tn3270eSrvrPort, 811 tn3270eSrvrPortAddrType, 812 tn3270eSrvrPortAddress 813 } 814 ::= { tn3270eSrvrPortTable 1 } 816 Tn3270eSrvrPortEntry ::= SEQUENCE { 817 tn3270eSrvrPort Unsigned32, 818 tn3270eSrvrPortAddrType Tn3270eAddrType, 819 tn3270eSrvrPortAddress Tn3270eTAddress, 821 Expires May 1998 [Page 16]~ 823 White TN3270E Management Information Base (TN3270E-MIB) 20 November 1997 825 tn3270eSrvrPortRowStatus RowStatus 826 } 828 tn3270eSrvrPort OBJECT-TYPE 829 SYNTAX Unsigned32 (0..65535) 830 MAX-ACCESS not-accessible 831 STATUS current 832 DESCRIPTION 833 "Indicates a port assigned to a server." 834 ::= { tn3270eSrvrPortEntry 1 } 836 tn3270eSrvrPortAddrType OBJECT-TYPE 837 SYNTAX Tn3270eAddrType 838 MAX-ACCESS not-accessible 839 STATUS current 840 DESCRIPTION 841 "Indicates the type of the Client Address represented in 842 tn3270eSrvrPortAddress." 843 ::= { tn3270eSrvrPortEntry 2 } 845 tn3270eSrvrPortAddress OBJECT-TYPE 846 SYNTAX Tn3270eTAddress 847 MAX-ACCESS not-accessible 848 STATUS current 849 DESCRIPTION 850 "The Client Address associated with a TN3270E server port. 851 tn3270eClientGroupAddrType indicates the address type 852 (ipv4 or ipv6 for example)." 853 ::= { tn3270eSrvrPortEntry 3 } 855 tn3270eSrvrPortRowStatus OBJECT-TYPE 856 SYNTAX RowStatus 857 MAX-ACCESS read-create 858 STATUS current 859 DESCRIPTION 860 "This object allows entries to be created and deleted in the 861 tn3270eSrvrPortTable. 863 An entry in this table is deleted by setting this object 864 to destroy(6)." 865 REFERENCE 866 "RFC 1903, 'Textual Conventions for version 2 of the Simple 867 Network Management Protocol (SNMPv2).'" 868 ::= { tn3270eSrvrPortEntry 4 } 870 tn3270eSrvrStatsTable OBJECT-TYPE 871 SYNTAX SEQUENCE OF Tn3270eSrvrStatsEntry 872 MAX-ACCESS not-accessible 874 Expires May 1998 [Page 17]~ 876 White TN3270E Management Information Base (TN3270E-MIB) 20 November 1997 878 STATUS current 879 DESCRIPTION 880 "This table defines a set of statistics concerning 881 global TN3270E server performance." 882 ::= { tn3270eObjects 3 } 884 tn3270eSrvrStatsEntry OBJECT-TYPE 885 SYNTAX Tn3270eSrvrStatsEntry 886 MAX-ACCESS not-accessible 887 STATUS current 888 DESCRIPTION 889 "Collection of a set of statistic objects for a single 890 TN3270 server. An entry can be global with respect to 891 a single TN3270E server or be specified at a port level. 892 Refer to the text description for tn3270eSrvrStatsPort. 894 It is possible that a TN3270E server implementation may 895 not be structured to support resource usage on a port basis 896 but provide statistics via an entry in this table for 897 each port. The recommended approach for this is to 898 provide a global entry (a value of 0 for 899 tn3270eSrvrStatsPort) with: 901 tn3270eSrvrStatsMaxLus 902 tn3270eSrvrStatsMaxLus 903 tn3270eSrvrStatsLusInUse 904 tn3270eSrvrStatsSpareLus 905 tn3270eSrvrStatsMaxPtrs 906 tn3270eSrvrStatsPtrsInUse 907 tn3270eSrvrStatsSparePtrs 909 set at this layer but set to zero at the port layer." 910 INDEX { tn3270eSrvrConfIndex, tn3270eSrvrStatsPort } 911 ::= { tn3270eSrvrStatsTable 1 } 913 Tn3270eSrvrStatsEntry ::= SEQUENCE { 914 tn3270eSrvrStatsPort Unsigned32, 915 tn3270eSrvrStatsUpTime TimeTicks, 916 tn3270eSrvrStatsMaxLus Unsigned32, 917 tn3270eSrvrStatsLusInUse Gauge32, 918 tn3270eSrvrStatsSpareLus Gauge32, 919 tn3270eSrvrStatsMaxPtrs Unsigned32, 920 tn3270eSrvrStatsPtrsInUse Gauge32, 921 tn3270eSrvrStatsSparePtrs Gauge32, 922 tn3270eSrvrStatsConnectsIn Counter32, 923 tn3270eSrvrStatsConnRejects Counter32, 924 tn3270eSrvrStatsDisconnects Counter32, 925 tn3270eSrvrStatsOctetsIn Counter64, 927 Expires May 1998 [Page 18]~ 929 White TN3270E Management Information Base (TN3270E-MIB) 20 November 1997 931 tn3270eSrvrStatsOctetsInLow Counter32, 932 tn3270eSrvrStatsOctetsOut Counter64, 933 tn3270eSrvrStatsOctetsOutLow Counter32 934 } 936 tn3270eSrvrStatsPort OBJECT-TYPE 937 SYNTAX Unsigned32 (0..65535) 938 MAX-ACCESS not-accessible 939 STATUS current 940 DESCRIPTION 941 "Indicates the port that the corresponding statistics are 942 for. Implementation of collection of these statistics 943 on a port basis is not mandatory. An implementation may 944 limit itself to keeping this data on a global basis by 945 using a value of 0." 946 ::= { tn3270eSrvrStatsEntry 1 } 948 tn3270eSrvrStatsUpTime OBJECT-TYPE 949 SYNTAX TimeTicks 950 MAX-ACCESS read-only 951 STATUS current 952 DESCRIPTION 953 "Indicates when either usage of a associating port becomes 954 active (tn3270eSrvrStatsPort non-zero) or if the entry 955 is being kept on a global basis the time that the TN3270E 956 server becomes active. The value of this object does not 957 get reset based on port usage status changes or changes 958 to tn3270eSrvrConfOperStatus." 959 ::= { tn3270eSrvrStatsEntry 2 } 961 tn3270eSrvrStatsMaxLus OBJECT-TYPE 962 SYNTAX Unsigned32 963 MAX-ACCESS read-only 964 STATUS current 965 DESCRIPTION 966 "Indicates the maximum number of LUs for use by a 967 TN3270E server. The granularity of this data can be 968 either global (corresponding tn3270eSrvrStatsPort index 969 equal to 0) or on a port basis." 970 ::= { tn3270eSrvrStatsEntry 3 } 972 tn3270eSrvrStatsLusInUse OBJECT-TYPE 973 SYNTAX Gauge32 974 MAX-ACCESS read-only 975 STATUS current 976 DESCRIPTION 977 "Indicates the current number of LUs in use by a 978 TN3270E server. The granularity of this data can be 980 Expires May 1998 [Page 19]~ 982 White TN3270E Management Information Base (TN3270E-MIB) 20 November 1997 984 either global (corresponding tn3270eSrvrStatsPort index 985 equal to 0) or on a port basis." 986 ::= { tn3270eSrvrStatsEntry 4 } 988 tn3270eSrvrStatsSpareLus OBJECT-TYPE 989 SYNTAX Gauge32 990 MAX-ACCESS read-only 991 STATUS current 992 DESCRIPTION 993 "Indicates the number of free LUs for a particular TN3270E 994 server. It is possible that the difference between 995 tn3270eSrvrStatsMaxLus and tn3270eSrvrStatsLusInUse does 996 not equal tn3270eSrvrStatsSpareLus. An LU may exist 997 but not be useable by an client connection. 998 The granularity of this data can be 999 either global (corresponding tn3270eSrvrStatsPort index 1000 equal to 0) or on a port basis." 1001 ::= { tn3270eSrvrStatsEntry 5 } 1003 tn3270eSrvrStatsMaxPtrs OBJECT-TYPE 1004 SYNTAX Unsigned32 1005 MAX-ACCESS read-only 1006 STATUS current 1007 DESCRIPTION 1008 "Indicates the maximum number of Printer Resources for 1009 use by a TN3270E server. The granularity of this data 1010 can be either global (corresponding tn3270eSrvrStatsPort 1011 index equal to 0) or on a port basis." 1012 ::= { tn3270eSrvrStatsEntry 6 } 1014 tn3270eSrvrStatsPtrsInUse OBJECT-TYPE 1015 SYNTAX Gauge32 1016 MAX-ACCESS read-only 1017 STATUS current 1018 DESCRIPTION 1019 "Indicates the current number of Printer Resources in 1020 use by a TN3270E server. The granularity of this data 1021 can be either global (corresponding tn3270eSrvrStatsPort 1022 index equal to 0) or on a port basis." 1023 ::= { tn3270eSrvrStatsEntry 7 } 1025 tn3270eSrvrStatsSparePtrs OBJECT-TYPE 1026 SYNTAX Gauge32 1027 MAX-ACCESS read-only 1028 STATUS current 1029 DESCRIPTION 1030 "Indicates the number of free Printer Resources for a 1031 particular TN3270E server. It is possible that the 1033 Expires May 1998 [Page 20]~ 1035 White TN3270E Management Information Base (TN3270E-MIB) 20 November 1997 1037 difference between tn3270eSrvrStatsMaxPtrs and 1038 tn3270eSrvrStatsPtrsInUse does not equal 1039 tn3270eSrvrStatsSparePtrs. A Printer resource may 1040 exist but not be useable by an client connection. 1041 The granularity of this data 1042 can be either global (corresponding tn3270eSrvrStatsPort 1043 index equal to 0) or on a port basis." 1044 ::= { tn3270eSrvrStatsEntry 8 } 1046 tn3270eSrvrStatsConnectsIn OBJECT-TYPE 1047 SYNTAX Counter32 1048 MAX-ACCESS read-only 1049 STATUS current 1050 DESCRIPTION 1051 "Indicates the number of client connections received by a 1052 TN3270E server. The granularity of this data 1053 can be either global (corresponding tn3270eSrvrStatsPort 1054 index equal to 0) or on a port basis." 1055 ::= { tn3270eSrvrStatsEntry 9 } 1057 tn3270eSrvrStatsConnRejects OBJECT-TYPE 1058 SYNTAX Counter32 1059 MAX-ACCESS read-only 1060 STATUS current 1061 DESCRIPTION 1062 "Indicates the number of client connections rejected during 1063 connection setup. An example of this is when no LU or 1064 Printer resource is available to associate with the 1065 TCP Connection of an client. The granularity of this data 1066 can be either global (corresponding tn3270eSrvrStatsPort 1067 index equal to 0) or on a port basis." 1068 ::= { tn3270eSrvrStatsEntry 10 } 1070 tn3270eSrvrStatsDisconnects OBJECT-TYPE 1071 SYNTAX Counter32 1072 MAX-ACCESS read-only 1073 STATUS current 1074 DESCRIPTION 1075 "Indicates the number of client connections disconnected by a 1076 TN3270E server. The granularity of this data 1077 can be either global (corresponding tn3270eSrvrStatsPort 1078 index equal to 0) or on a port basis." 1079 ::= { tn3270eSrvrStatsEntry 11 } 1081 tn3270eSrvrStatsOctetsIn OBJECT-TYPE 1082 SYNTAX Counter64 1083 MAX-ACCESS read-only 1084 STATUS current 1086 Expires May 1998 [Page 21]~ 1088 White TN3270E Management Information Base (TN3270E-MIB) 20 November 1997 1090 DESCRIPTION 1091 "Indicates the number of octets received from TN3270 1092 and TN3270E Clients. The granularity 1093 of this data can be either global (corresponding 1094 tn3270eSrvrStatsPort index equal to 0) or on a port basis." 1095 ::= { tn3270eSrvrStatsEntry 12 } 1097 tn3270eSrvrStatsOctetsInLow OBJECT-TYPE 1098 SYNTAX Counter32 1099 MAX-ACCESS read-only 1100 STATUS current 1101 DESCRIPTION 1102 "Low order 32 bits of tn3270eSrvrStatsOctetsIn." 1103 ::= { tn3270eSrvrStatsEntry 13 } 1105 tn3270eSrvrStatsOctetsOut OBJECT-TYPE 1106 SYNTAX Counter64 1107 MAX-ACCESS read-only 1108 STATUS current 1109 DESCRIPTION 1110 "Indicates the number of octets sent to TN3270 1111 and TN3270E Clients. The granularity 1112 of this data can be either global (corresponding 1113 tn3270eSrvrStatsPort index equal to 0) or on a port basis." 1114 ::= { tn3270eSrvrStatsEntry 14 } 1116 tn3270eSrvrStatsOctetsOutLow OBJECT-TYPE 1117 SYNTAX Counter32 1118 MAX-ACCESS read-only 1119 STATUS current 1120 DESCRIPTION 1121 "Low order 32 bits of tn3270eSrvrStatsOctetsOut." 1122 ::= { tn3270eSrvrStatsEntry 15 } 1124 tn3270eClientGroupTable OBJECT-TYPE 1125 SYNTAX SEQUENCE OF Tn3270eClientGroupEntry 1126 MAX-ACCESS not-accessible 1127 STATUS current 1128 DESCRIPTION 1129 "This table defines client address groupings for use by a 1130 TN3270E server." 1131 ::= { tn3270eObjects 4 } 1133 tn3270eClientGroupEntry OBJECT-TYPE 1134 SYNTAX Tn3270eClientGroupEntry 1135 MAX-ACCESS not-accessible 1136 STATUS current 1137 DESCRIPTION 1139 Expires May 1998 [Page 22]~ 1141 White TN3270E Management Information Base (TN3270E-MIB) 20 November 1997 1143 "Definition of a single client address entry. All entries with 1144 the same first two indexes, tn3270eSrvrConfIndex and 1145 tn3270eClientGroupName, are considered to be in the same 1146 client group." 1147 INDEX { tn3270eSrvrConfIndex, 1148 tn3270eClientGroupName, 1149 tn3270eClientGroupAddrType, 1150 tn3270eClientGroupAddress } 1151 ::= { tn3270eClientGroupTable 1 } 1153 Tn3270eClientGroupEntry ::= SEQUENCE { 1154 tn3270eClientGroupName Utf8String, 1155 tn3270eClientGroupAddrType Tn3270eAddrType, 1156 tn3270eClientGroupAddress Tn3270eTAddress, 1157 tn3270eClientGroupSubnetMask IpAddress, 1158 tn3270eClientGroupPfxLength Unsigned32, 1159 tn3270eClientGroupRowStatus RowStatus } 1161 tn3270eClientGroupName OBJECT-TYPE 1162 SYNTAX Utf8String (SIZE(1..24)) 1163 MAX-ACCESS not-accessible 1164 STATUS current 1165 DESCRIPTION 1166 "The name of a client group." 1167 ::= { tn3270eClientGroupEntry 1 } 1169 tn3270eClientGroupAddrType OBJECT-TYPE 1170 SYNTAX Tn3270eAddrType 1171 MAX-ACCESS not-accessible 1172 STATUS current 1173 DESCRIPTION 1174 "Indicates the type of the address represented in 1175 tn3270eClientGroupAddress." 1176 ::= { tn3270eClientGroupEntry 2 } 1178 tn3270eClientGroupAddress OBJECT-TYPE 1179 SYNTAX Tn3270eTAddress 1180 MAX-ACCESS not-accessible 1181 STATUS current 1182 DESCRIPTION 1183 "The client address of a member of a client group. The value 1184 of tn3270eClientGroupAddrType indicates the address 1185 type (ipv4 or ipv6 for example)." 1186 ::= { tn3270eClientGroupEntry 3 } 1188 tn3270eClientGroupSubnetMask OBJECT-TYPE 1189 SYNTAX IpAddress 1190 MAX-ACCESS read-create 1192 Expires May 1998 [Page 23]~ 1194 White TN3270E Management Information Base (TN3270E-MIB) 20 November 1997 1196 STATUS current 1197 DESCRIPTION 1198 "The corresponding subnet mask associated with 1199 tn3270eClientGroupAddress. A single IP Address is 1200 represented by having this object contain the value 1201 of 255.255.255.255. This object is valid only if 1202 tn3270eClientGroupAddrType has a value of ipv4(1)." 1203 DEFVAL { 'FFFFFFFF'H } 1204 ::= { tn3270eClientGroupEntry 4 } 1206 tn3270eClientGroupPfxLength OBJECT-TYPE 1207 SYNTAX Unsigned32 (0..128) 1208 MAX-ACCESS read-create 1209 STATUS current 1210 DESCRIPTION 1211 "The corresponding IPv6 network prefix length. This 1212 object is valid only if tn3270eClientGroupAddrType 1213 has a value of ipv6(2)." 1214 DEFVAL { 0 } 1215 ::= { tn3270eClientGroupEntry 5 } 1217 tn3270eClientGroupRowStatus OBJECT-TYPE 1218 SYNTAX RowStatus 1219 MAX-ACCESS read-create 1220 STATUS current 1221 DESCRIPTION 1222 "This object allows entries to be created and deleted in the 1223 tn3270eClientGroupTable. 1225 An entry in this table is deleted by setting this object 1226 to destroy(6)." 1227 REFERENCE 1228 "RFC 1903, 'Textual Conventions for version 2 of the Simple 1229 Network Management Protocol (SNMPv2).'" 1230 ::= { tn3270eClientGroupEntry 6 } 1232 tn3270eResPoolTable OBJECT-TYPE 1233 SYNTAX SEQUENCE OF Tn3270eResPoolEntry 1234 MAX-ACCESS not-accessible 1235 STATUS current 1236 DESCRIPTION 1237 "This table defines resource groupings; the term 1238 'pool' is used as it is defined by RFC 1647." 1239 ::= { tn3270eObjects 5 } 1241 tn3270eResPoolEntry OBJECT-TYPE 1242 SYNTAX Tn3270eResPoolEntry 1243 MAX-ACCESS not-accessible 1245 Expires May 1998 [Page 24]~ 1247 White TN3270E Management Information Base (TN3270E-MIB) 20 November 1997 1249 STATUS current 1250 DESCRIPTION 1251 "Definition of a single resource pool member. All entries 1252 with the same first two indexes, tn3270eSrvrConfIndex and 1253 tn3270eResPoolName, are considered to be in the same pool." 1254 INDEX { tn3270eSrvrConfIndex, 1255 tn3270eResPoolName, 1256 tn3270eResPoolElementName } 1257 ::= { tn3270eResPoolTable 1 } 1259 Tn3270eResPoolEntry ::= SEQUENCE { 1260 tn3270eResPoolName Utf8String, 1261 tn3270eResPoolElementName SnaResourceName, 1262 tn3270eResPoolElementType Tn3270ResourceType, 1263 tn3270eResPoolRowStatus RowStatus } 1265 tn3270eResPoolName OBJECT-TYPE 1266 SYNTAX Utf8String (SIZE(1..24)) 1267 MAX-ACCESS not-accessible 1268 STATUS current 1269 DESCRIPTION 1270 "The name of a resource pool.." 1271 ::= { tn3270eResPoolEntry 1 } 1273 tn3270eResPoolElementName OBJECT-TYPE 1274 SYNTAX SnaResourceName 1275 MAX-ACCESS not-accessible 1276 STATUS current 1277 DESCRIPTION 1278 "The name of a member of a resource pool." 1279 ::= { tn3270eResPoolEntry 2 } 1281 tn3270eResPoolElementType OBJECT-TYPE 1282 SYNTAX Tn3270ResourceType 1283 MAX-ACCESS read-create 1284 STATUS current 1285 DESCRIPTION 1286 "The type of the entity in a resource pool." 1287 ::= { tn3270eResPoolEntry 3 } 1289 tn3270eResPoolRowStatus OBJECT-TYPE 1290 SYNTAX RowStatus 1291 MAX-ACCESS read-create 1292 STATUS current 1293 DESCRIPTION 1294 "This object allows entries to be created and deleted in the 1295 tn3270eResPoolTable. 1297 Expires May 1998 [Page 25]~ 1299 White TN3270E Management Information Base (TN3270E-MIB) 20 November 1997 1301 An entry in this table is deleted by setting this object 1302 to destroy(6)." 1303 REFERENCE 1304 "RFC 1903, 'Textual Conventions for version 2 of the Simple 1305 Network Management Protocol (SNMPv2).'" 1306 ::= { tn3270eResPoolEntry 4 } 1308 tn3270eSnaMapTable OBJECT-TYPE 1309 SYNTAX SEQUENCE OF Tn3270eSnaMapEntry 1310 MAX-ACCESS not-accessible 1311 STATUS current 1312 DESCRIPTION 1313 "This table provide a mapping from the name by which 1314 a secondary LU is known in the SNA network to the 1315 name by which it is known locally at the TN3270e 1316 server. This latter name serves as an index into 1317 the tn3270eResPoolTable and the tn3270eResMapTable." 1318 ::= { tn3270eObjects 6 } 1320 tn3270eSnaMapEntry OBJECT-TYPE 1321 SYNTAX Tn3270eSnaMapEntry 1322 MAX-ACCESS not-accessible 1323 STATUS current 1324 DESCRIPTION 1325 "Definition of a single mapping from an SSCP-supplied 1326 SLU name to a local SLU name." 1327 INDEX { tn3270eSrvrConfIndex, 1328 tn3270eSnaMapSscpSuppliedName } 1329 ::= { tn3270eSnaMapTable 1 } 1331 Tn3270eSnaMapEntry ::= SEQUENCE { 1332 tn3270eSnaMapSscpSuppliedName SnaResourceName, 1333 tn3270eSnaMapLocalName SnaResourceName, 1334 tn3270eSnaMapPrimaryLuName SnaResourceName } 1336 tn3270eSnaMapSscpSuppliedName OBJECT-TYPE 1337 SYNTAX SnaResourceName 1338 MAX-ACCESS not-accessible 1339 STATUS current 1340 DESCRIPTION 1341 "The name of the secondary LU (SLU) as it is known in the 1342 SNA network. This name is sent by the SSCP on the 1343 Activate Logical Unit (ACTLU) request." 1344 ::= { tn3270eSnaMapEntry 1 } 1346 tn3270eSnaMapLocalName OBJECT-TYPE 1347 SYNTAX SnaResourceName 1348 MAX-ACCESS read-only 1350 Expires May 1998 [Page 26]~ 1352 White TN3270E Management Information Base (TN3270E-MIB) 20 November 1997 1354 STATUS current 1355 DESCRIPTION 1356 "The local name of the secondary LU (SLU)." 1357 ::= { tn3270eSnaMapEntry 2 } 1359 tn3270eSnaMapPrimaryLuName OBJECT-TYPE 1360 SYNTAX SnaResourceName 1361 MAX-ACCESS read-only 1362 STATUS current 1363 DESCRIPTION 1364 "When there is a currently active LU-LU session for this 1365 connection, this object returns the primary LU (PLU) name 1366 from the BIND. When there is no active LU-LU session, or 1367 when the PLU name is unavailable for some other reason, 1368 this object returns the empty string." 1369 ::= { tn3270eSnaMapEntry 3 } 1371 tn3270eClientResMapTable OBJECT-TYPE 1372 SYNTAX SEQUENCE OF Tn3270eClientResMapEntry 1373 MAX-ACCESS not-accessible 1374 STATUS current 1375 DESCRIPTION 1376 "This table defines resource pool to client group mappings. 1377 Since both the resource pool name and client group name 1378 are included in the index clause of this table, multiple 1379 resource pools can be assigned to the same client group. This 1380 enables use of multiple resource pools for use in client to 1381 resource mapping. Assigning multiple client Groups to the 1382 same resource pool is also allowed, but is not the primary 1383 purpose for how the indexing is structured. 1385 Assignment of a resource pool to client group can be 1386 restricted based on TCP port. An index value of 0 for 1387 tn3270eClientResMapClientPort disables restriction of 1388 resource assignment based on client target port selection." 1389 ::= { tn3270eObjects 7 } 1391 tn3270eClientResMapEntry OBJECT-TYPE 1392 SYNTAX Tn3270eClientResMapEntry 1393 MAX-ACCESS not-accessible 1394 STATUS current 1395 DESCRIPTION 1396 "Definition of a single resource pool to client group 1397 mapping." 1398 INDEX { tn3270eSrvrConfIndex, 1399 tn3270eClientResMapPoolName, 1400 tn3270eClientResMapClientGroupName, 1401 tn3270eClientResMapClientPort } 1403 Expires May 1998 [Page 27]~ 1405 White TN3270E Management Information Base (TN3270E-MIB) 20 November 1997 1407 ::= { tn3270eClientResMapTable 1 } 1409 Tn3270eClientResMapEntry ::= SEQUENCE { 1410 tn3270eClientResMapPoolName Utf8String, 1411 tn3270eClientResMapClientGroupName Utf8String, 1412 tn3270eClientResMapClientPort Unsigned32, 1413 tn3270eClientResMapRowStatus RowStatus } 1415 tn3270eClientResMapPoolName OBJECT-TYPE 1416 SYNTAX Utf8String (SIZE(1..24)) 1417 MAX-ACCESS not-accessible 1418 STATUS current 1419 DESCRIPTION 1420 "The name of a resource pool." 1421 ::= { tn3270eClientResMapEntry 1 } 1423 tn3270eClientResMapClientGroupName OBJECT-TYPE 1424 SYNTAX Utf8String (SIZE(1..24)) 1425 MAX-ACCESS not-accessible 1426 STATUS current 1427 DESCRIPTION 1428 "The name of the client group that is mapped to a 1429 resource pool." 1430 ::= { tn3270eClientResMapEntry 2 } 1432 tn3270eClientResMapClientPort OBJECT-TYPE 1433 SYNTAX Unsigned32 (0..65535) 1434 MAX-ACCESS not-accessible 1435 STATUS current 1436 DESCRIPTION 1437 "The port to restrict a resource pool to a client group 1438 mapping. A value of 0 for this objects implies that 1439 the mapping is not restricted." 1440 ::= { tn3270eClientResMapEntry 3 } 1442 tn3270eClientResMapRowStatus OBJECT-TYPE 1443 SYNTAX RowStatus 1444 MAX-ACCESS read-create 1445 STATUS current 1446 DESCRIPTION 1447 "This object allows entries to be created and deleted in the 1448 tn3270eClientResMapTable. 1450 An entry in this table is deleted by setting this object 1451 to destroy(6)." 1452 REFERENCE 1453 "RFC 1903, 'Textual Conventions for version 2 of the Simple 1454 Network Management Protocol (SNMPv2).'" 1456 Expires May 1998 [Page 28]~ 1458 White TN3270E Management Information Base (TN3270E-MIB) 20 November 1997 1460 ::= { tn3270eClientResMapEntry 4 } 1462 tn3270eResMapTable OBJECT-TYPE 1463 SYNTAX SEQUENCE OF Tn3270eResMapEntry 1464 MAX-ACCESS not-accessible 1465 STATUS current 1466 DESCRIPTION 1467 "This table defines the actual mapping of a resource to 1468 a client Address." 1469 ::= { tn3270eObjects 8 } 1471 tn3270eResMapEntry OBJECT-TYPE 1472 SYNTAX Tn3270eResMapEntry 1473 MAX-ACCESS not-accessible 1474 STATUS current 1475 DESCRIPTION 1476 "Definition of the mapping of a Resource Element to 1477 a client Address." 1478 INDEX { tn3270eSrvrConfIndex, 1479 tn3270eResMapElementName } 1480 ::= { tn3270eResMapTable 1 } 1482 Tn3270eResMapEntry ::= SEQUENCE { 1483 tn3270eResMapElementName SnaResourceName, 1484 tn3270eResMapAddrType Tn3270eAddrType, 1485 tn3270eResMapAddress Tn3270eTAddress, 1486 tn3270eResMapPort Unsigned32, 1487 tn3270eResMapElementType Tn3270ResourceType, 1488 tn3270eResMapSscpSuppliedName SnaResourceName } 1490 tn3270eResMapElementName OBJECT-TYPE 1491 SYNTAX SnaResourceName 1492 MAX-ACCESS not-accessible 1493 STATUS current 1494 DESCRIPTION 1495 "The name of a resource element. This is the name by 1496 which the server implementing this table knows the 1497 resource. It may be different from the name by which 1498 the resource is known in the SNA network. In this case 1499 the name by which the resource is known in the SNA 1500 network is returned in the tn3270eResMapSscpSuppliedName 1501 object." 1502 ::= { tn3270eResMapEntry 1 } 1504 tn3270eResMapAddrType OBJECT-TYPE 1505 SYNTAX Tn3270eAddrType 1506 MAX-ACCESS read-only 1507 STATUS current 1509 Expires May 1998 [Page 29]~ 1511 White TN3270E Management Information Base (TN3270E-MIB) 20 November 1997 1513 DESCRIPTION 1514 "Indicates the type of the client Address represented in 1515 tn3270eResMapAddress." 1516 ::= { tn3270eResMapEntry 2 } 1518 tn3270eResMapAddress OBJECT-TYPE 1519 SYNTAX Tn3270eTAddress 1520 MAX-ACCESS read-only 1521 STATUS current 1522 DESCRIPTION 1523 "A client address." 1524 ::= { tn3270eResMapEntry 3 } 1526 tn3270eResMapPort OBJECT-TYPE 1527 SYNTAX Unsigned32 (0..65535) 1528 MAX-ACCESS read-only 1529 STATUS current 1530 DESCRIPTION 1531 "A client Port." 1532 ::= { tn3270eResMapEntry 4 } 1534 tn3270eResMapElementType OBJECT-TYPE 1535 SYNTAX Tn3270ResourceType 1536 MAX-ACCESS read-only 1537 STATUS current 1538 DESCRIPTION 1539 "The type of the associating resource element." 1540 ::= { tn3270eResMapEntry 5 } 1542 tn3270eResMapSscpSuppliedName OBJECT-TYPE 1543 SYNTAX SnaResourceName 1544 MAX-ACCESS read-only 1545 STATUS current 1546 DESCRIPTION 1547 "The name of the secondary LU (SLU) as it is known in the 1548 SNA network. This name is sent by the SSCP on the 1549 Activate Logical Unit (ACTLU) request. The value of this 1550 object is the empty string if the tn3270eResMapElementName 1551 is the same as the SSCP-supplied name." 1552 ::= { tn3270eResMapEntry 6 } 1554 -- Define the set of objects to add to the Tcp Connection Table 1556 tn3270eTcpConnTable OBJECT-TYPE 1557 SYNTAX SEQUENCE OF Tn3270eTcpConnEntry 1558 MAX-ACCESS not-accessible 1559 STATUS current 1560 DESCRIPTION 1562 Expires May 1998 [Page 30]~ 1564 White TN3270E Management Information Base (TN3270E-MIB) 20 November 1997 1566 "Provides a table that has an entry for each TN3270(E) 1567 client connection that is active at a TN3270E server. 1568 The table was originally modeled after the tcpConnTable 1569 but was changed to support different client Address types 1570 and to be indexed first by the remote address and port 1571 as oppose to local address and port. This is to enable 1572 use of a SNMP GET-NEXT operation using only the remote 1573 address and port." 1574 ::= { tn3270eObjects 9 } 1576 tn3270eTcpConnEntry OBJECT-TYPE 1577 SYNTAX Tn3270eTcpConnEntry 1578 MAX-ACCESS not-accessible 1579 STATUS current 1580 DESCRIPTION 1581 "Provides in formation about a single TN3270/TN3270E 1582 session. Note: a tn3270eSrvrConfIndex is not needed 1583 in this table since the combination of both remote 1584 local addresses and ports is sufficient to 1585 guarantee uniqueness between TN3270E Servers on the 1586 same or actually different hosts." 1587 INDEX { tn3270eTcpConnRemAddrType, 1588 tn3270eTcpConnRemAddress, 1589 tn3270eTcpConnRemPort, 1590 tn3270eTcpConnLocalAddrType, 1591 tn3270eTcpConnLocalAddress, 1592 tn3270eTcpConnLocalPort 1593 } 1594 ::= { tn3270eTcpConnTable 1 } 1596 Tn3270eTcpConnEntry ::= 1597 SEQUENCE 1598 { 1599 tn3270eTcpConnRemAddrType Tn3270eAddrType, 1600 tn3270eTcpConnRemAddress Tn3270eTAddress, 1601 tn3270eTcpConnRemPort Unsigned32, 1602 tn3270eTcpConnLocalAddrType Tn3270eAddrType, 1603 tn3270eTcpConnLocalAddress Tn3270eTAddress, 1604 tn3270eTcpConnLocalPort Unsigned32, 1605 tn3270eTcpConnLastActivity TimeTicks, 1606 tn3270eTcpConnBytesIn Counter32, 1607 tn3270eTcpConnBytesOut Counter32, 1608 tn3270eTcpConnResourceElement SnaResourceName, 1609 tn3270eTcpConnResourceType Tn3270ResourceType, 1610 tn3270eTcpConnDeviceType Tn3270DeviceTypes, 1611 tn3270eTcpConnFunctions Tn3270Functions, 1612 tn3270eTcpConnId Unsigned32, 1613 tn3270eTcpConnClientIdFormat INTEGER, 1615 Expires May 1998 [Page 31]~ 1617 White TN3270E Management Information Base (TN3270E-MIB) 20 November 1997 1619 tn3270eTcpConnClientId OCTET STRING, 1620 tn3270eTcpConnMiscInfoFormat BITS, 1621 tn3270eTcpConnMiscInfo OCTET STRING, 1622 tn3270eTcpConnLuLuBindImage OCTET STRING, 1623 tn3270eTcpConnSnaState INTEGER 1624 } 1626 tn3270eTcpConnRemAddrType OBJECT-TYPE 1627 SYNTAX Tn3270eAddrType 1628 MAX-ACCESS not-accessible 1629 STATUS current 1630 DESCRIPTION 1631 "Indicates the type of the value of the 1632 tn3270eTcpConnRemAddress object. For example, 1633 ipv4(1) or ipv6(2)." 1634 ::= { tn3270eTcpConnEntry 1 } 1636 tn3270eTcpConnRemAddress OBJECT-TYPE 1637 SYNTAX Tn3270eTAddress 1638 MAX-ACCESS not-accessible 1639 STATUS current 1640 DESCRIPTION 1641 "The remote address associated with a TN3270E client. 1642 tn3270eTcpConnRemAddrType indicates the address type 1643 (ipv4 or ipv6 for example). 1645 If a TN3270(E) client is connected to its 1646 server via a proxy client the address represented by 1647 the value of this object should be the remote client's 1648 address, not the proxy client's address." 1649 ::= { tn3270eTcpConnEntry 2 } 1651 tn3270eTcpConnRemPort OBJECT-TYPE 1652 SYNTAX Unsigned32 (0..65535) 1653 MAX-ACCESS not-accessible 1654 STATUS current 1655 DESCRIPTION 1656 "The remote port associated with a TN3270E client. 1658 If a TN3270(E) client is connected to its 1659 server via a proxy client the port represented by 1660 the value of this object should be the remote client's 1661 port, not the proxy client's port." 1662 ::= { tn3270eTcpConnEntry 3 } 1664 tn3270eTcpConnLocalAddrType OBJECT-TYPE 1665 SYNTAX Tn3270eAddrType 1666 MAX-ACCESS not-accessible 1668 Expires May 1998 [Page 32]~ 1670 White TN3270E Management Information Base (TN3270E-MIB) 20 November 1997 1672 STATUS current 1673 DESCRIPTION 1674 "Indicates the type of the value of the 1675 tn3270eTcpConnLocalAddress object. For example, 1676 ipv4(1) or ipv6(2)." 1677 ::= { tn3270eTcpConnEntry 4 } 1679 tn3270eTcpConnLocalAddress OBJECT-TYPE 1680 SYNTAX Tn3270eTAddress 1681 MAX-ACCESS not-accessible 1682 STATUS current 1683 DESCRIPTION 1684 "The local address associated with a TN3270E client. 1685 tn3270eTcpConnRemAddrType indicates the address type 1686 (ipv4 or ipv6 for example)." 1687 ::= { tn3270eTcpConnEntry 5 } 1689 tn3270eTcpConnLocalPort OBJECT-TYPE 1690 SYNTAX Unsigned32 (0..65535) 1691 MAX-ACCESS not-accessible 1692 STATUS current 1693 DESCRIPTION 1694 "The remote port associated with a TN3270E client." 1695 ::= { tn3270eTcpConnEntry 6 } 1697 tn3270eTcpConnLastActivity OBJECT-TYPE 1698 SYNTAX TimeTicks 1699 MAX-ACCESS read-only 1700 STATUS current 1701 DESCRIPTION 1702 "The number of 100ths of seconds since any data was 1703 transferred for the associating TCP Connection." 1704 DEFVAL { 0 } 1705 ::= { tn3270eTcpConnEntry 7 } 1707 tn3270eTcpConnBytesIn OBJECT-TYPE 1708 SYNTAX Counter32 1709 UNITS "octets" 1710 MAX-ACCESS read-only 1711 STATUS current 1712 DESCRIPTION 1713 "The number of bytes received by the server from TCP 1714 for this connection." 1715 ::= { tn3270eTcpConnEntry 8 } 1717 tn3270eTcpConnBytesOut OBJECT-TYPE 1718 SYNTAX Counter32 1719 UNITS "octets" 1721 Expires May 1998 [Page 33]~ 1723 White TN3270E Management Information Base (TN3270E-MIB) 20 November 1997 1725 MAX-ACCESS read-only 1726 STATUS current 1727 DESCRIPTION 1728 "The number of bytes sent to TCP for this connection." 1729 ::= { tn3270eTcpConnEntry 9 } 1731 tn3270eTcpConnResourceElement OBJECT-TYPE 1732 SYNTAX SnaResourceName 1733 MAX-ACCESS read-only 1734 STATUS current 1735 DESCRIPTION 1736 "LU/Print secondary name for connecting an client 1737 into an SNA network." 1738 ::= { tn3270eTcpConnEntry 10 } 1740 tn3270eTcpConnResourceType OBJECT-TYPE 1741 SYNTAX Tn3270ResourceType 1742 MAX-ACCESS read-only 1743 STATUS current 1744 DESCRIPTION 1745 "Indicates the type of resource identified by 1746 tn3270eTcpConnResourceElement." 1747 ::= { tn3270eTcpConnEntry 11 } 1749 tn3270eTcpConnDeviceType OBJECT-TYPE 1750 SYNTAX Tn3270DeviceTypes 1751 MAX-ACCESS read-only 1752 STATUS current 1753 DESCRIPTION 1754 "Indicates the device type if negotiated with client. 1755 This object is also known as logmode." 1756 ::= { tn3270eTcpConnEntry 12 } 1758 tn3270eTcpConnFunctions OBJECT-TYPE 1759 SYNTAX Tn3270Functions 1760 MAX-ACCESS read-only 1761 STATUS current 1762 DESCRIPTION 1763 "This object will indicates which of the TN3270 and TN3270E 1764 functions that are supported by the server was negioted 1765 with a client. Refer to tn3270eSrvrFunctionsSupported." 1766 ::= { tn3270eTcpConnEntry 13 } 1768 tn3270eTcpConnId OBJECT-TYPE 1769 SYNTAX Unsigned32 1770 MAX-ACCESS read-only 1771 STATUS current 1772 DESCRIPTION 1774 Expires May 1998 [Page 34]~ 1776 White TN3270E Management Information Base (TN3270E-MIB) 20 November 1997 1778 "The connection identifier associated with a TN3270 or 1779 a TN3270E session's TCP connection." 1780 ::= { tn3270eTcpConnEntry 14 } 1782 tn3270eTcpConnClientIdFormat OBJECT-TYPE 1783 SYNTAX INTEGER { 1784 unknown(0) 1785 } 1787 MAX-ACCESS read-only 1788 STATUS current 1789 DESCRIPTION 1790 "The format of the corresponding tn3270eTcpConnClientId 1791 object: 1793 ENUMERATION OCTETs DESCRIPTION 1794 unknown(0) 0" 1795 ::= { tn3270eTcpConnEntry 15 } 1797 tn3270eTcpConnClientId OBJECT-TYPE 1798 SYNTAX OCTET STRING (SIZE (0..512)) 1799 MAX-ACCESS read-only 1800 STATUS current 1801 DESCRIPTION 1802 "Additional client identification information whose 1803 content is defined by the corresponding value of 1804 tn3270eTcpConnClientIdFormat." 1805 ::= { tn3270eTcpConnEntry 16 } 1807 tn3270eTcpConnMiscInfoFormat OBJECT-TYPE 1808 SYNTAX BITS { 1809 none(0), 1810 unknown(1), 1811 proxyIpv4(2), 1812 proxyIpv6(3) 1813 } 1814 MAX-ACCESS read-only 1815 STATUS current 1816 DESCRIPTION 1817 "This object defines the content of a corresponding 1818 tn3270eTcpConnMiscInfo object. This object is defined 1819 using the BITS SYNTAX in order to enable the presents 1820 of multiple elements. The order of occurance of the 1821 selected elements in a tn3270eTcpConnMiscInfo must 1822 follow the precedence of the associating BIT definition 1823 with the exception of unknown(1) which must be last 1824 if selected: 1826 Expires May 1998 [Page 35]~ 1828 White TN3270E Management Information Base (TN3270E-MIB) 20 November 1997 1830 ENUMERATION OCTETs DESCRIPTION 1831 none(0) 0 1832 unknown(1) 0..512 A variable length generic field. 1833 proxyIpv4(2) 4 The actual client is connected 1834 via a proxy client whose address 1835 is stored in tn3270eTcpConnClientId. 1836 proxyIpv6(3) 16 The actual client is connected 1837 via a proxy client whose address 1838 is stored in tn3270eTcpConnClientId. 1840 For example, selection of unknown(1), proxyIpv4(2) and 1841 proxyIpv6(3) would result in the corresponding 1842 tn3270eTcpConnMiscInfo containing a proxyIpv6 value 1843 followed by a proxyIpv4 value and ended with a variable 1844 length unknown value." 1845 ::= { tn3270eTcpConnEntry 17 } 1847 tn3270eTcpConnMiscInfo OBJECT-TYPE 1848 SYNTAX OCTET STRING (SIZE (0..512)) 1849 MAX-ACCESS read-only 1850 STATUS current 1851 DESCRIPTION 1852 "Additional client information. The contents of this 1853 object is defined by the corresponding object 1854 tn3270eTcpConnMiscInfoFormat." 1855 ::= { tn3270eTcpConnEntry 18 } 1857 tn3270eTcpConnLuLuBindImage OBJECT-TYPE 1858 SYNTAX OCTET STRING (SIZE (0..256)) 1859 MAX-ACCESS read-only 1860 STATUS current 1861 DESCRIPTION 1862 "When there is a currently active LU-LU session for 1863 this connection, this object returns the BIND Image 1864 (defined to be bytes 1-p of the complete BIND Request 1865 Unit) that was received from the PLU during session 1866 activation. When there is no active LU-LU session, 1867 or when a BIND image is unavailable for some other 1868 reason, this object returns the empty string." 1869 ::= { tn3270eTcpConnEntry 19 } 1871 tn3270eTcpConnSnaState OBJECT-TYPE 1872 SYNTAX INTEGER { 1873 unknown(0), 1874 noSluSession(1), 1875 sscpLuSession(2), -- but no LU-LU session 1876 luLuSession(3) 1877 } 1879 Expires May 1998 [Page 36]~ 1881 White TN3270E Management Information Base (TN3270E-MIB) 20 November 1997 1883 MAX-ACCESS read-only 1884 STATUS current 1885 DESCRIPTION 1886 "The current state of the SNA side of the end-to-end 1887 TN3270 connection. The following states are defined: 1889 unknown(0) - The true state is not known. 1890 noSluSession(1) - The SLU has neither an SSCP-LU 1891 nor an LU-LU session active. 1892 sscpLuSession(2) - The SSCP-LU session for the SLU 1893 is active, but the SLU is not 1894 currently in session with a PLU. 1895 luLuSession(3) - The SLU currently has an active 1896 session with a PLU." 1897 ::= { tn3270eTcpConnEntry 20 } 1899 -- Conformance Definitions 1901 tn3270eGroups OBJECT IDENTIFIER ::= { tn3270eConformance 1 } 1902 tn3270eCompliances OBJECT IDENTIFIER ::= { tn3270eConformance 2 } 1904 -- compliance statements 1906 tn3270eCompliance MODULE-COMPLIANCE 1907 STATUS current 1908 DESCRIPTION 1909 "The compliance statement for agents that support the 1910 TN3270E-MIB." 1911 MODULE -- this module 1912 MANDATORY-GROUPS { tn3270eBasicGroup, 1913 tn3270eSessionGroup 1914 } 1915 GROUP tn3270eResMapGroup 1916 DESCRIPTION 1917 "This group is optional and provides a method of 1918 performing tn3270eClientGroup to tn3270eResPool 1919 mapping." 1920 OBJECT tn3270eSrvrConfActivityCheck 1921 MIN-ACCESS read-only 1922 DESCRIPTION 1923 "The agent is not required to support a set to this 1924 object if the associating TN3270E server doesn't 1925 support either TIMEMARK or NOP processing. In 1926 this case an agent should return noCheck on 1927 retrieval." 1928 OBJECT tn3270eSrvrConfActivityTimeout 1929 MIN-ACCESS read-only 1930 DESCRIPTION 1932 Expires May 1998 [Page 37]~ 1934 White TN3270E Management Information Base (TN3270E-MIB) 20 November 1997 1936 "The agent is not required to support a set to this 1937 object if the functions enabled by 1938 tn3270eSrvrConfActivityCheck are not supported. 1939 An agent in this case should return a value of 0." 1940 OBJECT tn3270eSrvrConfActivityInterval 1941 MIN-ACCESS read-only 1942 DESCRIPTION 1943 "The agent is not required to support a set to this 1944 object if the functions enabled by 1945 tn3270eSrvrConfActivityCheck are not supported. 1946 An agent in this case should return a value of 0." 1947 OBJECT tn3270eSrvrConfAdminStatus 1948 DESCRIPTION 1949 "A TN3270E server is not required to support a 1950 stopImmediate state transition." 1951 ::= { tn3270eCompliances 1 } 1953 -- units of conformance 1955 tn3270eBasicGroup OBJECT-GROUP 1956 OBJECTS { 1957 tn3270eSrvrConfInactivityTimeout, 1958 tn3270eSrvrConfActivityCheck, 1959 tn3270eSrvrConfActivityTimeout, 1960 tn3270eSrvrConfActivityInterval, 1961 tn3270eSrvrFunctionsSupported, 1962 tn3270eSrvrConfAdminStatus, 1963 tn3270eSrvrConfOperStatus, 1964 tn3270eSrvrConfSessionTermState, 1965 tn3270eSrvrConfSrvrType, 1966 tn3270eSrvrConfContact, 1967 tn3270eSrvrConfRowStatus, 1968 tn3270eSrvrPortRowStatus, 1969 tn3270eSrvrStatsUpTime, 1970 tn3270eSrvrStatsMaxLus, 1971 tn3270eSrvrStatsLusInUse, 1972 tn3270eSrvrStatsSpareLus, 1973 tn3270eSrvrStatsMaxPtrs, 1974 tn3270eSrvrStatsPtrsInUse, 1975 tn3270eSrvrStatsSparePtrs, 1976 tn3270eSrvrStatsConnectsIn, 1977 tn3270eSrvrStatsConnRejects, 1978 tn3270eSrvrStatsDisconnects, 1979 tn3270eSrvrStatsOctetsIn, 1980 tn3270eSrvrStatsOctetsInLow, 1981 tn3270eSrvrStatsOctetsOut, 1982 tn3270eSrvrStatsOctetsOutLow, 1983 tn3270eClientGroupSubnetMask, 1985 Expires May 1998 [Page 38]~ 1987 White TN3270E Management Information Base (TN3270E-MIB) 20 November 1997 1989 tn3270eClientGroupPfxLength, 1990 tn3270eClientGroupRowStatus, 1991 tn3270eSnaMapLocalName, 1992 tn3270eSnaMapPrimaryLuName 1993 } 1994 STATUS current 1995 DESCRIPTION 1996 "This group is mandatory for all hosts supporting the 1997 TN3270E-MIB." 1998 ::= { tn3270eGroups 1 } 2000 tn3270eSessionGroup OBJECT-GROUP 2001 OBJECTS { 2002 tn3270eResMapAddrType, 2003 tn3270eResMapAddress, 2004 tn3270eResMapPort, 2005 tn3270eResMapElementType, 2006 tn3270eResMapSscpSuppliedName, 2007 tn3270eTcpConnLastActivity, 2008 tn3270eTcpConnBytesIn, 2009 tn3270eTcpConnBytesOut, 2010 tn3270eTcpConnResourceElement, 2011 tn3270eTcpConnResourceType, 2012 tn3270eTcpConnDeviceType, 2013 tn3270eTcpConnFunctions 2014 } 2015 STATUS current 2016 DESCRIPTION 2017 "This group is mandatory for all hosts supporting the 2018 TN3270E-MIB." 2019 ::= { tn3270eGroups 2 } 2021 tn3270eResMapGroup OBJECT-GROUP 2022 OBJECTS { 2023 tn3270eResPoolElementType, 2024 tn3270eResPoolRowStatus, 2025 tn3270eClientResMapRowStatus, 2026 tn3270eTcpConnId, 2027 tn3270eTcpConnClientIdFormat, 2028 tn3270eTcpConnClientId, 2029 tn3270eTcpConnMiscInfoFormat, 2030 tn3270eTcpConnMiscInfo, 2031 tn3270eTcpConnLuLuBindImage, 2032 tn3270eTcpConnSnaState 2033 } 2034 STATUS current 2035 DESCRIPTION 2036 "This group is optional for all hosts supporting the 2038 Expires May 1998 [Page 39]~ 2040 White TN3270E Management Information Base (TN3270E-MIB) 20 November 1997 2042 TN3270E-MIB." 2043 ::= { tn3270eGroups 3 } 2045 END 2047 5. Security Considerations 2049 Certain management information defined in this MIB may be considered 2050 sensitive in some network environments. Therefore, authentication of 2051 received SNMP requests and controlled access to management information 2052 should be employed in such environments. The method for this 2053 authentication is a function of the SNMP Administrative Framework, and 2054 has not been expanded by this MIB. 2056 Several objects in this MIB allow write access or provide for remote 2057 creation. Allowing this support in a non-secure environment can have a 2058 negative effect on network operations. It is recommended that 2059 implementers seriously consider whether set operations should be 2060 allowed without providing, at a minimum, authentication of request 2061 origin. It it recommended that without such support that the following 2062 objects be implemented as read-only: 2064 o tn3270eSrvrConfInactivityTimout 2065 o tn3270eSrvrConfActivityCheck 2066 o tn3270eSrvrConfActivityTimeout 2067 o tn3270eSrvrConfActivityInterval 2068 o tn3270eSrvrConfAdminStatus 2069 o tn3270eSrvrConfSessionTermState 2070 o tn3270eSrvrConfContact 2071 o tn3270eClientGroupSubnetMask 2072 o tn3270eResPoolElementType 2074 The following objects should either be implemented as read-only or not 2075 implemented when security is an issue as previously discussed: 2077 o tn3270eSrvrConfRowStatus 2078 o tn3270eSrvrPortRowStatus 2079 o tn3270eClientGroupRowStatus 2080 o tn3270eResPoolRowStatus 2081 o tn3270eResMapRowStatus 2083 6. Acknowledgments 2085 This document is a product of the TN3270E Working Group. 2087 Expires May 1998 [Page 40]~ 2089 White TN3270E Management Information Base (TN3270E-MIB) 20 November 1997 2091 7. References 2093 [1] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 2094 Waldbusser S., "Structure of Management Information for version 2 2095 of the Simple Network Management Protocol (SNMPv2)", RFC 1902, 2096 January 1996. 2098 [2] Network Working Group, Postel, J., and Reynolds, J., "Telnet 2099 Protocol Specification", RFC 854, May 1983. 2101 [3] Network Working Group, Postel, J., and Reynolds, J., "Telnet Timing 2102 Mark Option", RFC 860, May 1983. 2104 [4] Network Working Group and Rekhter J., "Telnet 3270 Regime Option", 2105 RFC 1041, January 1988. 2107 [5] McCloghrie, K., and M. Rose, Editors, "Management Information Base 2108 for Network Management of TCP/IP-based internets: MIB-II", STD 17, 2109 RFC 1213, Hughes LAN Systems, Performance Systems International, 2110 March 1991. 2112 [6] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. 2113 Waldbusser, "Textual Conventions for version 2 of the Simple 2114 Network Management Protocol (SNMPv2)", RFC 1903, January 1996. 2116 [7] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. 2117 Waldbusser, "Protocol Operations for version 2 of the Simple 2118 Network Management Protocol (SNMPv2)", RFC 1905, January 1996. 2120 [8] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. 2121 Waldbusser, "Conformance Statements for version 2 of the Simple 2122 Network Management Protocol (SNMPv2)", RFC 1904, January 1996. 2124 [9] Case, J., M. Fedor, M. Schoffstall, J. Davin, "Simple Network 2125 Management Protocol", RFC 1157, SNMP Research, Performance Systems 2126 International, MIT Laboratory for Computer Science, May 1990. 2128 [10] IETF SNMPv2 Working Group and McCloghrie, K., "TCP-MIB 2130 Expires May 1998 [Page 41]~ 2132 White TN3270E Management Information Base (TN3270E-MIB) 20 November 1997 2134 Definitions", November 1994. 2136 [11] Hinden, R., Deering, S., "IP Version 6 Addressing Architecture", 2137 , July 16, 1997 2139 [12] Krupczak, Cheryl, Saperia, Jonathan, "Definitions of System-Level 2140 Managed Objects for Applications", April 15, 1997. 2142 8. Authors' Address 2144 Kenneth D. White 2145 Dept. G80/Bldg 501 2146 IBM Corporation 2147 Research Triangle Park, NC 27709, USA 2148 E-mail: kennethw@vnet.ibm.com 2150 Expires May 1998 [Page 42]~