idnits 2.17.1 draft-ietf-tn3270e-tn3270-mib-02.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-19) 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 28 longer pages, the longest (page 2) being 60 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 29 pages 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. ** 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: ---------------------------------------------------------------------------- -- 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 (July 1997) is 9775 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 1360, but no explicit reference was found in the text == Unused Reference: '4' is defined on line 1366, but no explicit reference was found in the text == Unused Reference: '10' is defined on line 1390, 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' Summary: 15 errors (**), 0 flaws (~~), 6 warnings (==), 3 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: January, 1998 5 IBM Corp. 7 July 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 White TN3270E Management Information Base (TN3270E-MIB)28 July 1997 52 1.0 Introduction............................................. 2 53 2.0 The SNMPv2 Network Management Framework.................. 2 54 2.1 Object Definitions....................................... 3 55 3.0 Structure of the MIB..................................... 3 56 3.1 TN3270E Server Control................................... 3 57 3.1.1 tn3270eSrvrConfTable................................... 4 58 3.1.2 tn3270eSrvrPortTable................................... 4 59 3.1.3 tn3270eSrvrStatsTable.................................. 5 60 3.2 TN3270E Server Resource Configuration.................... 5 61 3.3 Resource/IP Address Mappings............................. 5 62 3.3.1 tn3270eResMapTable..................................... 5 63 3.3.2 TCP Connection Table Additions......................... 5 64 4.0 Definitions.............................................. 6 65 5.0 Security Considerations..................................27 66 6.0 Acknowledgments..........................................27 67 7.0 References...............................................28 68 8.0 Authors' Address.........................................29 70 1. Introduction 72 This document is a product of the TN3270E Working Group. Its purpose 73 is to define a MIB module for extending the traditional MIBs supported 74 by a TCP/IP implementation for configuration and management of TN3270E 75 Servers. 77 This memo considers IPv6 addressability to be out of scope with 78 respect to the MIB module defined herein. It is the intent of the 79 author of this document to address IPv6 addressing in an additional 80 submission. 82 2. The SNMPv2 Network Management Framework 84 The SNMP Network Management Framework presently consists of three 85 major components. They are: 87 o the SMI, described in RFC 1902 [1], - the mechanisms used for 88 describing and naming objects for the purpose of management. 90 o the MIB-II, STD 17, RFC 1213 [5], - the core set of managed 91 objects for the Internet suite of protocols. 93 o the protocol, RFC 1157 [9] and/or RFC 1905 [7] - the protocol 94 for accessing managed information. 96 Textual conventions are defined in RFC 1903 [6], and conformance 98 White TN3270E Management Information Base (TN3270E-MIB)28 July 1997 100 statements are defined in RFC 1904 [8]. 102 The Framework permits new objects to be defined for the purpose of 103 experimentation and evaluation. 105 This memo specifies a MIB module that is compliant to the SNMPv2 SMI. 106 A semantically identical MIB conforming to the SNMPv1 SMI can be 107 produced through the appropriate translation. 109 2.1. Object Definitions 111 Managed objects are accessed via a virtual information store, termed 112 the Management Information Base or MIB. Objects in the MIB are 113 defined using the subset of Abstract Syntax Notation One (ASN.1) 114 defined in the SMI. In particular, each object object type is named 115 by an OBJECT IDENTIFIER, an administratively assigned name. The 116 object type together with an object instance serves to uniquely 117 identify a specific instantiation of the object. For human 118 convenience, we often use a textual string, termed the descriptor, to 119 refer to the object type. 121 3. Structure of the MIB 123 The TN3270E-MIB is split into the following components: 125 o TN3270E Server Control 126 o TN3270E Server Resource Configuration 127 o Resource/IP Address Mappings 129 The TN3270E-MIB is defined for support primarily by TN3270E Servers. 130 Use of this MIB by TN3270 Servers that do not support the TN3270E 131 protocol is not explicitly addressed by this memo. A significant 132 portion of the objects do apply in the TN3270 only case. Addressing 133 the TN3270 only case was not done since it is unlikely that this MIB 134 would be implemented by TN3270 only servers. 136 3.1. TN3270E Server Control 138 This group of objects provides for TN3270E Server configuration and 139 consists of: 141 o tn3270eSrvrConfTable 142 o tn3270eSrvrPortTable 143 o tn3270eSrvrStatsTable 145 White TN3270E Management Information Base (TN3270E-MIB)28 July 1997 147 3.1.1. tn3270eSrvrConfTable 149 The tn3270eSrvrConfTable contains a set of objects primarily for 150 configuring and managing a TN3270E Server. This table, as well most of 151 the tables in the TN3270E-MIB, are structured to be indexed by a 152 unsigned integer, tn3270eSrvrConfIndex. The primary index element, 153 tn3270eSrvrConfigIndex, enables support of multiple TN3270E Servers on 154 the same host. 156 An earlier version of this memo had used the local IP Address 157 associated with a TN3270E Server along with tn3270eSrvrConfIndex as 158 the primary indexes into most of its tables. Use of a local IP 159 Address was thought to enable representation of these tables by 160 management applications. This approach was dropped since it 161 introduces a level of complexity with respect to MIB table indexing 162 for little actually benefit. 164 tn3270eSrvrConfInactivityTimer defines the inactivity period for 165 TN3270 and TN3270E Sessions. tn3270eSrvrConfSessionTermState defines 166 how a session should be terminated. The three objects: 168 o tn3270eSrvrConfActivityCheck 169 o tn3270eSrvrConfActivityTimeout 170 o tn3270eSrvrConfActivityInterval 172 defines the parameters for performing the "Telnet Timing Mark Option" 173 as defined by RFC 860 [3]. The object tn3270eSrvrConfActivityCheck is 174 defined to enable selection of either a NOP command or a TIMEMARK 175 command. Sending a NOP command results in less overhead then a 176 TIMEMARK command since a client doesn't send a reply. 178 The objects tn3270eSrvrConfAdminStatus and tn3270eSrvrConfOperStatus 179 exists in order to enable remote starting and stopping of a TN3270E 180 Server. tn3270eSrvrConfFunctionsSupported indicates which of the 181 TN3270 and TN3270E options that a server supports. The object 182 tn3270eSrvrConfSessionTermState defines as a global option what 183 processing steps that a TN3270E Server should perform when a TN3270E 184 Session terminates with respect to the associating TCP Connection. 185 The object tn3270eSrvrConfSrvrType indicates the implementation type 186 of TN3270E Server that the tn3270eSrvrConfEntry represents. The 187 object tn3270eSrvrConfRowStatus provides the capability to perform 188 remote creation and deletion operations on this table. 190 3.1.2. tn3270eSrvrPortTable 192 The tn3270eSrvrPortTable exists in order to assign and retrieve the 193 local ports associated with a TN3270E Server. Some TN3270E Server 195 White TN3270E Management Information Base (TN3270E-MIB)28 July 1997 197 implementations support multiple local port usage. 199 3.1.3. tn3270eSrvrStatsTable 201 The tn3270eSrvrStatsTable defines a series of objects used to provide 202 general statistics on the use of a TN3270E Server. 204 3.2. TN3270E Server Resource Configuration 206 The TN3270E Server Resource Configuration collection of objects consists 207 of three tables: 209 o tn3270eIpGroupTable 210 o tn3270eResPoolTable 211 o tn3270eIpResMapTable 213 The tn3270eIpGroupTable and tn3270eResPoolTable enable 214 implementations to define groupings of both IP Addresses and Resource 215 Pools for mapping IP Addresses to resources. The mapping of a IP Group 216 to a Resource Pool is enabled via the tn3270eIpResMapTable. 218 3.3. Resource/IP Address Mappings 220 Two tables are defined by this memo to enable mapping of Resource Name 221 to IP Address and IP Address to Resource Name: 223 o tn3270eResMapTable 224 o TCP Connection Table Additions 226 3.3.1. tn3270eResMapTable 228 The tn3270eResMapTable is a read-only table that provides for mapping a 229 resource name to a IP Client's IP Address. An entry in this table is 230 added when a TCP Connection is received by a TN3270E Server and mapped 231 to a resource. The entry is deleted with the resource to IP Address 232 association is no longer valid. 234 3.3.2. TCP Connection Table Additions 236 The TCP Connection Table is defined by RFC 2012 (Refer to reference 237 10, TCP-MIB Definitions). Traditionally, the contents of the TCP 239 White TN3270E Management Information Base (TN3270E-MIB)28 July 1997 241 Connection Table has been implementation dependent. Its formal 242 definition consists of the following objects: 244 o tcpConnState (INTEGER) 245 o tcpConnLocalAddress (IpAddress) 246 o tcpConnLocalPort (INTEGER) 247 o tcpConnRemAddress (IpAddress) 248 o tcpConnRemPort (INTEGER) 250 and is indexed by: tcpConnLocalAddress, tcpConnLocalPort, 251 tcpConnRemAddress and tcpConnRemPort. The tn3270eTcpConnTableGroup 252 contains the objects defined by the tn3270eTcpConnTable for keeping a 253 list of the current set of TN3270 and TN3270E sessions at a TN3270E 254 Server. The tn3270eTcpConnTable has the same index elements as the 255 tcpConnTable but doesn't AUGMENT it since the relationship is not 256 one-to-one. 258 4. Definitions 260 TN3270E-MIB DEFINITIONS ::= BEGIN 262 IMPORTS 263 MODULE-IDENTITY, OBJECT-TYPE, BITS, Unsigned32, 264 experimental, IpAddress, TimeTicks, 265 Counter32, Gauge32 266 FROM SNMPv2-SMI 267 TEXTUAL-CONVENTION, RowStatus, DisplayString 268 FROM SNMPv2-TC 269 MODULE-COMPLIANCE, OBJECT-GROUP 270 FROM SNMPv2-CONF 271 tcpConnLocalAddress, tcpConnLocalPort, 272 tcpConnRemAddress, tcpConnRemPort 273 FROM TCP-MIB 274 ; 276 tn3270eMIB MODULE-IDENTITY 277 LAST-UPDATED "9707280000Z" -- July 28, 1997 278 ORGANIZATION "TN3270E Working Group" 279 CONTACT-INFO 280 "Kenneth White (kennethw@vnet.ibm.com) 281 IBM Corp." 282 DESCRIPTION 283 "This module defines a portion of the management 284 information base (MIB) for managing TN3270E Servers" 285 -- Need an experimental OID from IANA 286 ::= { experimental 2001 } 288 White TN3270E Management Information Base (TN3270E-MIB)28 July 1997 290 -- Textual Conventions 292 Tn3270ResourceType ::= TEXTUAL-CONVENTION 293 STATUS current 294 DESCRIPTION 295 "The type of resource defined by a Resource Pool. Refer 296 to tn3270eResPoolTable." 297 SYNTAX INTEGER { 298 other(0), 299 lu(1), 300 printer(2) 301 } 303 Tn3270Functions ::= TEXTUAL-CONVENTION 304 STATUS current 305 DESCRIPTION 306 "This textual convention is intended to reflect the 307 current set of TN3270 and TN3270E functions that can 308 be negotiated between a server and its client: 310 RFC856 311 transmitBinary The sender of this command REQUESTS 312 permission to begin transmitting, or 313 confirms that it will now begin transmitting 314 characters which are to be interpreted 315 as 8 bits of binary data by 316 the receiver of the data. 317 RFC820 318 timeMark The sender of this command REQUESTS that 319 the receiver of this command return a WILL 320 TIMING-MARK in the data stream at the 321 'appropriate place' ... 322 RFC885 323 endOfRecord The sender of this command requests 324 permission to begin transmission of the 325 Telnet END-OF-RECORD (EOR) code when 326 transmitting data characters, or 327 the sender of this command confirms it will 328 now begin transmission of EORs with 329 transmitted data characters. 330 RFC1091 331 terminalType Sender is willing to send terminal type 332 information in a subsequent sub-negotiation. 333 RFC1041 334 tn3270Regime Sender is willing to send list of supported 335 3270 Regimes in a subsequent sub-negotiation. 336 RFC1647 337 scsCtlCodes (Printer sessions only). Allows the use 339 White TN3270E Management Information Base (TN3270E-MIB)28 July 1997 341 of the SNA Character Stream (SCS) and SCS 342 control codes on the session. SCS is 343 used with LU type 1 SNA sessions. 344 dataStreamCtl (Printer sessions only). Allows the use 345 of the standard 3270 data stream. This 346 corresponds to LU type 3 SNA sessions. 347 responses Provides support for positive and 348 negative response handling. Allows the 349 server to reflect to the client any and 350 all definite, exception, and no response 351 requests sent by the host application. 352 bindImage Allows the server to send the SNA Bind 353 image and Unbind notification to the 354 client. 355 sysreq Allows the client and server to emulate 356 some (or all, depending on the server) of 357 the functions of the SYSREQ key in an SNA 358 environment." 359 SYNTAX BITS { 360 transmitBinary(0),-- rfc856 361 timemark(1), -- rfc860 362 endOfRecord(2), -- rfc885 363 terminalType(3), -- rfc1091 364 tn3270Regime(4), -- rfc1041 365 scsCtlCodes(5), -- rfc1647 366 dataStreamCtl(6), -- rfc1647 367 responses(7), -- rfc1647 368 bindImage(8), -- rfc1647 369 sysreq(9) -- rfc1647 370 } 372 Tn3270DeviceTypes ::= TEXTUAL-CONVENTION 373 STATUS current 374 DESCRIPTION 375 "This textual convention defines the list of device types 376 that can be set as defined by RFC 1647." 377 SYNTAX INTEGER { -- terminals 378 unknown(0), 379 ibm3278d2(1), -- (24 row x 80 col display) 380 ibm3278d2E(2), -- (24 row x 80 col display) 381 ibm3278d3(3), -- (32 row x 80 col display) 382 ibm3278d3E(4), -- (32 row x 80 col display) 383 ibm3278d4(5), -- (43 row x 80 col display) 384 ibm3278d4E(6), -- (43 row x 80 col display) 385 ibm3278d5(7), -- (27 row x 132 col display) 386 ibm3278d5E(8), -- (27 row x 132 col display) 387 ibmDynamic(9), -- (no pre-defined display size) 388 ibm3287d1(10) -- printers 390 White TN3270E Management Information Base (TN3270E-MIB)28 July 1997 392 } 394 -- Top-level structure of the MIB 396 tn3270eNotifications OBJECT IDENTIFIER ::= { tn3270eMIB 0 } 397 tn3270eObjects OBJECT IDENTIFIER ::= { tn3270eMIB 1 } 398 tn3270eConformance OBJECT IDENTIFIER ::= { tn3270eMIB 3 } 400 -- MIB Objects 402 tn3270eSrvrConfTable OBJECT-TYPE 403 SYNTAX SEQUENCE OF Tn3270eSrvrConfEntry 404 MAX-ACCESS not-accessible 405 STATUS current 406 DESCRIPTION 407 "This table defines the configuration elements for 408 TN3270E Servers. The number of entries in this table 409 is expected to vary depending on the location of the 410 table. A particular TN3270E Server is expected to 411 have a single entry. Modeling of the configuration 412 elements as a table allows multiple 413 TN3270E Servers to exist at the same host." 414 ::= { tn3270eObjects 1 } 416 tn3270eSrvrConfEntry OBJECT-TYPE 417 SYNTAX Tn3270eSrvrConfEntry 418 MAX-ACCESS not-accessible 419 STATUS current 420 DESCRIPTION 421 "Definition of the configuration elements for a single 422 TN3270E Server." 423 INDEX { tn3270eSrvrConfIndex } 424 ::= { tn3270eSrvrConfTable 1 } 426 Tn3270eSrvrConfEntry ::= SEQUENCE { 427 tn3270eSrvrConfIndex Unsigned32, 428 tn3270eSrvrConfInactivityTimeout Unsigned32, 429 tn3270eSrvrConfActivityCheck INTEGER, 430 tn3270eSrvrConfActivityTimeout Unsigned32, 431 tn3270eSrvrConfActivityInterval Unsigned32, 432 tn3270eSrvrFunctionsSupported Tn3270Functions, 433 tn3270eSrvrConfAdminStatus INTEGER, 434 tn3270eSrvrConfOperStatus INTEGER, 435 tn3270eSrvrConfSessionTermState INTEGER, 436 tn3270eSrvrConfSrvrType INTEGER, 437 tn3270eSrvrConfRowStatus RowStatus 438 } 440 White TN3270E Management Information Base (TN3270E-MIB)28 July 1997 442 tn3270eSrvrConfIndex OBJECT-TYPE 443 SYNTAX Unsigned32 444 MAX-ACCESS not-accessible 445 STATUS current 446 DESCRIPTION 447 "Indicates the instance of a TN3270E Server that 448 exists at a IP Host." 449 ::= { tn3270eSrvrConfEntry 1 } 451 tn3270eSrvrConfInactivityTimeout OBJECT-TYPE 452 SYNTAX Unsigned32 (0..99999999) 453 UNITS "seconds" 454 MAX-ACCESS read-create 455 STATUS current 456 DESCRIPTION 457 "The inactivity time-out specified in seconds. When a 458 connection has been inactive for the number of seconds 459 specified by this object it is closed. The default of 460 0 means no inactivity time-out." 461 DEFVAL { 0 } 462 ::= { tn3270eSrvrConfEntry 2 } 464 tn3270eSrvrConfActivityCheck OBJECT-TYPE 465 SYNTAX INTEGER { 466 noCheck(0), 467 timeMark(1), 468 nop(2) 469 } 470 MAX-ACCESS read-create 471 STATUS current 472 DESCRIPTION 473 "This object is intended to enable either timemark or 474 nop processing." 475 DEFVAL { noCheck } 476 ::= { tn3270eSrvrConfEntry 3 } 478 tn3270eSrvrConfActivityTimeout OBJECT-TYPE 479 SYNTAX Unsigned32 (1..99999999) 480 UNITS "seconds" 481 MAX-ACCESS read-create 482 STATUS current 483 DESCRIPTION 484 "The TIMEMARK or NOP processing time-out specified in seconds. 485 Note that a value of 0 is not allowed for this object since 486 the function that uses this object relies on 487 tn3270eSrvrConfActivityCheck for function enablement." 488 DEFVAL { 600 } -- 10 minutes 489 ::= { tn3270eSrvrConfEntry 4 } 491 White TN3270E Management Information Base (TN3270E-MIB)28 July 1997 493 tn3270eSrvrConfActivityInterval OBJECT-TYPE 494 SYNTAX Unsigned32 (1..99999999) 495 UNITS "seconds" 496 MAX-ACCESS read-create 497 STATUS current 498 DESCRIPTION 499 "The scan interval to be used by a TN3270E Server. 500 TIMEMARK or NOP processing scans the Telnet sessions 501 on the interval provided by this object looking for 502 sessions that have been idle for more than the value 503 provided by tn3270eSrvrConfActivityTimeout. 504 Note that a value of 0 is not allowed for this object since 505 the function that uses this object relies on 506 tn3270eSrvrConfActivityCheck for function enablement." 507 DEFVAL { 120 } -- 2 minutes 508 ::= { tn3270eSrvrConfEntry 5 } 510 tn3270eSrvrFunctionsSupported OBJECT-TYPE 511 SYNTAX Tn3270Functions 512 MAX-ACCESS read-only 513 STATUS current 514 DESCRIPTION 515 "This object indicates the functions supported by a 516 TN3270E Server." 517 DEFVAL { { scsCtlCodes, dataStreamCtl, 518 responses, bindImage, sysreq } } 519 ::= { tn3270eSrvrConfEntry 6 } 521 tn3270eSrvrConfAdminStatus OBJECT-TYPE 522 SYNTAX INTEGER { 523 up(1), 524 down(2), 525 stopImmediate(3) 526 } 527 MAX-ACCESS read-create 528 STATUS current 529 DESCRIPTION 530 "The desired state of the TN3270E Server: 532 up(1) - Activate a TN3270E Server. 533 down(2) - Informs the associating TN3270E Server 534 to gracefully terminate its processing. 535 stopImmediate(3) - Informs the associating TN3270E Server 536 to terminate immediately. 538 Implementation as to the exact symantics of either down(2) 539 or stopImmediate(3) processing is left as implementation 540 dependent. A TN3270E Server that does not distinquish 542 White TN3270E Management Information Base (TN3270E-MIB)28 July 1997 544 between down or stopImmediate transitions should not 545 support stopImmediate." 546 ::= { tn3270eSrvrConfEntry 7 } 548 tn3270eSrvrConfOperStatus OBJECT-TYPE 549 SYNTAX INTEGER { 550 up(1), 551 down(2) 552 } 553 MAX-ACCESS read-only 554 STATUS current 555 DESCRIPTION 556 "The current operational state of a TN3270E Server: 558 up(1) - The corresponding TN3270E Server is active. 559 down(2) - The corresponding TN3270E Server is inactive." 560 ::= { tn3270eSrvrConfEntry 8 } 562 tn3270eSrvrConfSessionTermState OBJECT-TYPE 563 SYNTAX INTEGER { 564 terminate(1), 565 luSessionPend(2), 566 queueSession(3) 567 } 568 MAX-ACCESS read-create 569 STATUS current 570 DESCRIPTION 571 "The current state for determining what a TN3270E Server 572 should do when a TN3270 Session terminates: 574 terminate(1) => Terminate TCP connection. 575 luSessionPend(2) => Do not drop the TCP Connection 576 associated with a IP Client when their 577 TN3270 Session ends. Processing should 578 redrive session initialization as if the 579 client was first connecting. 580 queueSession(3) => QUEUESESSION deals with CLSDST-Pass. 581 An example is the easiest explanation. 582 Assume APPL1 does a CLSDST-Pass 583 to APPL2. Then the client logs off APPL 584 Without QUEUESESSION the connection 585 would now be broken. With QUEUESESSION 586 the TN3270E Server keeps the LU around 587 after getting the APPL2 unbind waiting 588 for a bind from APPL1." 589 DEFVAL { terminate } 590 ::= { tn3270eSrvrConfEntry 9 } 592 White TN3270E Management Information Base (TN3270E-MIB)28 July 1997 594 tn3270eSrvrConfSrvrType OBJECT-TYPE 595 SYNTAX INTEGER { 596 unknown(0), 597 host(1), 598 gateway(2) 599 } 600 MAX-ACCESS read-only 601 STATUS current 602 DESCRIPTION 603 "This object indicates the type of TN3270E Server. 604 The existence of MIB tables and objects that will be 605 defined by follow-on MIBs may be predicated on whether the 606 TN3270E Server can be local to the same host as a 607 Target Application (host(1)) or will always be remote 608 (gateway(2))." 609 ::= { tn3270eSrvrConfEntry 10 } 611 tn3270eSrvrConfRowStatus OBJECT-TYPE 612 SYNTAX RowStatus 613 MAX-ACCESS read-create 614 STATUS current 615 DESCRIPTION 616 "This object allows entries to be created and deleted in the 617 tn3270eSrvrConfTable. 619 An entry in this table is deleted by setting this object 620 to destroy(6)." 621 REFERENCE 622 "RFC 1903, 'Textual Conventions for version 2 of the Simple 623 Network Management Protocol (SNMPv2).'" 624 ::= { tn3270eSrvrConfEntry 11 } 626 tn3270eSrvrPortTable OBJECT-TYPE 627 SYNTAX SEQUENCE OF Tn3270eSrvrPortEntry 628 MAX-ACCESS not-accessible 629 STATUS current 630 DESCRIPTION 631 "This table defines the TCP ports associated with TN3270E 632 Servers." 633 ::= { tn3270eObjects 2 } 635 tn3270eSrvrPortEntry OBJECT-TYPE 636 SYNTAX Tn3270eSrvrPortEntry 637 MAX-ACCESS not-accessible 638 STATUS current 639 DESCRIPTION 640 "Definition of a single TCP port assignment to a 641 TN3270E Server." 643 White TN3270E Management Information Base (TN3270E-MIB)28 July 1997 645 INDEX { tn3270eSrvrConfIndex, tn3270eSrvrPort } 646 ::= { tn3270eSrvrPortTable 1 } 648 Tn3270eSrvrPortEntry ::= SEQUENCE { 649 tn3270eSrvrPort Unsigned32, 650 tn3270eSrvrPortRowStatus RowStatus 651 } 653 tn3270eSrvrPort OBJECT-TYPE 654 SYNTAX Unsigned32 (0..65535) 655 MAX-ACCESS not-accessible 656 STATUS current 657 DESCRIPTION 658 "Indicates a port assigned to a server." 659 ::= { tn3270eSrvrPortEntry 1 } 661 tn3270eSrvrPortRowStatus OBJECT-TYPE 662 SYNTAX RowStatus 663 MAX-ACCESS read-create 664 STATUS current 665 DESCRIPTION 666 "This object allows entries to be created and deleted in the 667 tn3270eSrvrPortTable. 669 An entry in this table is deleted by setting this object 670 to destroy(6)." 671 REFERENCE 672 "RFC 1903, 'Textual Conventions for version 2 of the Simple 673 Network Management Protocol (SNMPv2).'" 674 ::= { tn3270eSrvrPortEntry 2 } 676 tn3270eSrvrStatsTable OBJECT-TYPE 677 SYNTAX SEQUENCE OF Tn3270eSrvrStatsEntry 678 MAX-ACCESS not-accessible 679 STATUS current 680 DESCRIPTION 681 "This table defines a set of statistics concerning 682 global TN3270E Server performance." 683 ::= { tn3270eObjects 3 } 685 tn3270eSrvrStatsEntry OBJECT-TYPE 686 SYNTAX Tn3270eSrvrStatsEntry 687 MAX-ACCESS not-accessible 688 STATUS current 689 DESCRIPTION 690 "Collection of a set of statistic objects for a single 691 TN3270 Server." 692 INDEX { tn3270eSrvrConfIndex } 694 White TN3270E Management Information Base (TN3270E-MIB)28 July 1997 696 ::= { tn3270eSrvrStatsTable 1 } 698 Tn3270eSrvrStatsEntry ::= SEQUENCE { 699 tn3270eSrvrStatsUpTime TimeTicks, 700 tn3270eSrvrStatsMaxLus Unsigned32, 701 tn3270eSrvrStatsLusInUse Gauge32, 702 tn3270eSrvrStatsSpareLus Gauge32, 703 tn3270eSrvrStatsMaxPtrs Unsigned32, 704 tn3270eSrvrStatsPtrsInUse Gauge32, 705 tn3270eSrvrStatsSparePtrs Gauge32, 706 tn3270eSrvrStatsConnectsIn Counter32, 707 tn3270eSrvrStatsConnRejects Counter32, 708 tn3270eSrvrStatsDisconnects Counter32 709 } 711 tn3270eSrvrStatsUpTime OBJECT-TYPE 712 SYNTAX TimeTicks 713 MAX-ACCESS read-only 714 STATUS current 715 DESCRIPTION 716 "Indicates the amount of time that a particular TN3270E 717 has be active. This is total time since the server was 718 started and is not reset on tn3270eSrvrConfOperStatus." 719 ::= { tn3270eSrvrStatsEntry 1 } 721 tn3270eSrvrStatsMaxLus OBJECT-TYPE 722 SYNTAX Unsigned32 723 MAX-ACCESS read-only 724 STATUS current 725 DESCRIPTION 726 "Indicates the maximum number of LUs for use by a 727 TN3270E Server." 728 ::= { tn3270eSrvrStatsEntry 2 } 730 tn3270eSrvrStatsLusInUse OBJECT-TYPE 731 SYNTAX Gauge32 732 MAX-ACCESS read-only 733 STATUS current 734 DESCRIPTION 735 "Indicates the current number of LUs in use by a 736 TN3270E Server." 737 ::= { tn3270eSrvrStatsEntry 3 } 739 tn3270eSrvrStatsSpareLus OBJECT-TYPE 740 SYNTAX Gauge32 741 MAX-ACCESS read-only 742 STATUS current 743 DESCRIPTION 745 White TN3270E Management Information Base (TN3270E-MIB)28 July 1997 747 "Indicates the number of free LUs for a particular TN3270E 748 Server. It is possible that the difference between 749 tn3270eSrvrStatsMaxLus and tn3270eSrvrStatsLusInUse does 750 not equal tn3270eSrvrStatsSpareLus. An LU may exist 751 but not be useable by a IP Client connection." 752 ::= { tn3270eSrvrStatsEntry 4 } 754 tn3270eSrvrStatsMaxPtrs OBJECT-TYPE 755 SYNTAX Unsigned32 756 MAX-ACCESS read-only 757 STATUS current 758 DESCRIPTION 759 "Indicates the maximum number of Printer Resources for use by a 760 TN3270E Server." 761 ::= { tn3270eSrvrStatsEntry 5 } 763 tn3270eSrvrStatsPtrsInUse OBJECT-TYPE 764 SYNTAX Gauge32 765 MAX-ACCESS read-only 766 STATUS current 767 DESCRIPTION 768 "Indicates the current number of Printer Resources in use by a 769 TN3270E Server." 770 ::= { tn3270eSrvrStatsEntry 6 } 772 tn3270eSrvrStatsSparePtrs OBJECT-TYPE 773 SYNTAX Gauge32 774 MAX-ACCESS read-only 775 STATUS current 776 DESCRIPTION 777 "Indicates the number of free Printer Resources for a 778 particular TN3270E Server. It is possible that the 779 difference between tn3270eSrvrStatsMaxPtrs and 780 tn3270eSrvrStatsPtrsInUse does not equal 781 tn3270eSrvrStatsSparePtrs. A Printer resource may 782 exist but not be useable by a IP Client connection." 783 ::= { tn3270eSrvrStatsEntry 7 } 785 tn3270eSrvrStatsConnectsIn OBJECT-TYPE 786 SYNTAX Counter32 787 MAX-ACCESS read-only 788 STATUS current 789 DESCRIPTION 790 "Indicates the number of client connections received by a 791 TN3270E Server." 792 ::= { tn3270eSrvrStatsEntry 8 } 794 tn3270eSrvrStatsConnRejects OBJECT-TYPE 796 White TN3270E Management Information Base (TN3270E-MIB)28 July 1997 798 SYNTAX Counter32 799 MAX-ACCESS read-only 800 STATUS current 801 DESCRIPTION 802 "Indicates the number of client connections rejected during 803 connection setup. An example of this is when no LU or 804 Printer resource is available to associate with the 805 TCP Connection of a IP Client." 806 ::= { tn3270eSrvrStatsEntry 9 } 808 tn3270eSrvrStatsDisconnects OBJECT-TYPE 809 SYNTAX Counter32 810 MAX-ACCESS read-only 811 STATUS current 812 DESCRIPTION 813 "Indicates the number of client connections disconnected by a 814 TN3270E Server." 815 ::= { tn3270eSrvrStatsEntry 10 } 817 tn3270eIpGroupTable OBJECT-TYPE 818 SYNTAX SEQUENCE OF Tn3270eIpGroupEntry 819 MAX-ACCESS not-accessible 820 STATUS current 821 DESCRIPTION 822 "This table defines IP Address groupings for use by a 823 TN3270E Server." 824 ::= { tn3270eObjects 4 } 826 tn3270eIpGroupEntry OBJECT-TYPE 827 SYNTAX Tn3270eIpGroupEntry 828 MAX-ACCESS not-accessible 829 STATUS current 830 DESCRIPTION 831 "Definition of a single IP Address entry. All entries with 832 the same first two indexes, tn3270eSrvrConfIndex and 833 tn3270eIpGroupName, are considered to be in the same 834 IP Group." 835 INDEX { tn3270eSrvrConfIndex, 836 tn3270eIpGroupName, 837 tn3270eIpGroupIpAddress } 838 ::= { tn3270eIpGroupTable 1 } 840 Tn3270eIpGroupEntry ::= SEQUENCE { 841 tn3270eIpGroupName DisplayString, 842 tn3270eIpGroupIpAddress IpAddress, 843 tn3270eIpGroupSubnetMask IpAddress, 844 tn3270eIpGroupRowStatus RowStatus } 846 White TN3270E Management Information Base (TN3270E-MIB)28 July 1997 848 tn3270eIpGroupName OBJECT-TYPE 849 SYNTAX DisplayString (SIZE(1..24)) 850 MAX-ACCESS not-accessible 851 STATUS current 852 DESCRIPTION 853 "The name of a IP Group." 854 ::= { tn3270eIpGroupEntry 1 } 856 tn3270eIpGroupIpAddress OBJECT-TYPE 857 SYNTAX IpAddress 858 MAX-ACCESS not-accessible 859 STATUS current 860 DESCRIPTION 861 "The IP Address of a member of a IP Group." 862 ::= { tn3270eIpGroupEntry 2 } 864 tn3270eIpGroupSubnetMask OBJECT-TYPE 865 SYNTAX IpAddress 866 MAX-ACCESS read-create 867 STATUS current 868 DESCRIPTION 869 "The corresponding subnet mask associated with 870 tn3270eIpGroupIpAddress. A single IP Address 871 is represented by having this object contain 872 the value of 255.255.255.255." 873 DEFVAL { 'FFFFFFFF'H } 874 ::= { tn3270eIpGroupEntry 3 } 876 tn3270eIpGroupRowStatus OBJECT-TYPE 877 SYNTAX RowStatus 878 MAX-ACCESS read-create 879 STATUS current 880 DESCRIPTION 881 "This object allows entries to be created and deleted in the 882 tn3270eIpGroupTable. 884 An entry in this table is deleted by setting this object 885 to destroy(6)." 886 REFERENCE 887 "RFC 1903, 'Textual Conventions for version 2 of the Simple 888 Network Management Protocol (SNMPv2).'" 889 ::= { tn3270eIpGroupEntry 4 } 891 tn3270eResPoolTable OBJECT-TYPE 892 SYNTAX SEQUENCE OF Tn3270eResPoolEntry 893 MAX-ACCESS not-accessible 894 STATUS current 895 DESCRIPTION 897 White TN3270E Management Information Base (TN3270E-MIB)28 July 1997 899 "This table defines Resource groupings and using the term 900 pool as defined by RFC 1647." 901 ::= { tn3270eObjects 5 } 903 tn3270eResPoolEntry OBJECT-TYPE 904 SYNTAX Tn3270eResPoolEntry 905 MAX-ACCESS not-accessible 906 STATUS current 907 DESCRIPTION 908 "Definition of a single Resource Pool member. All entries 909 with the same first two indexes, tn3270eSrvrConfIndex and 910 tn3270eResPoolName, are considered to be in the same Pool." 911 INDEX { tn3270eSrvrConfIndex, 912 tn3270eResPoolName, 913 tn3270eResPoolElementName } 914 ::= { tn3270eResPoolTable 1 } 916 Tn3270eResPoolEntry ::= SEQUENCE { 917 tn3270eResPoolName DisplayString, 918 tn3270eResPoolElementName DisplayString, 919 tn3270eResPoolElementType Tn3270ResourceType, 920 tn3270eResPoolRowStatus RowStatus } 922 tn3270eResPoolName OBJECT-TYPE 923 SYNTAX DisplayString (SIZE(1..24)) 924 MAX-ACCESS not-accessible 925 STATUS current 926 DESCRIPTION 927 "The name of a Resource Pool.." 928 ::= { tn3270eResPoolEntry 1 } 930 tn3270eResPoolElementName OBJECT-TYPE 931 SYNTAX DisplayString (SIZE(1..8)) 932 MAX-ACCESS not-accessible 933 STATUS current 934 DESCRIPTION 935 "The Name of a member of a Resource Pool." 936 ::= { tn3270eResPoolEntry 2 } 938 tn3270eResPoolElementType OBJECT-TYPE 939 SYNTAX Tn3270ResourceType 940 MAX-ACCESS read-create 941 STATUS current 942 DESCRIPTION 943 "The type of the entity in a Resource Pool." 944 ::= { tn3270eResPoolEntry 3 } 946 tn3270eResPoolRowStatus OBJECT-TYPE 948 White TN3270E Management Information Base (TN3270E-MIB)28 July 1997 950 SYNTAX RowStatus 951 MAX-ACCESS read-create 952 STATUS current 953 DESCRIPTION 954 "This object allows entries to be created and deleted in the 955 tn3270eResPoolTable. 957 An entry in this table is deleted by setting this object 958 to destroy(6)." 959 REFERENCE 960 "RFC 1903, 'Textual Conventions for version 2 of the Simple 961 Network Management Protocol (SNMPv2).'" 962 ::= { tn3270eResPoolEntry 4 } 964 tn3270eIpResMapTable OBJECT-TYPE 965 SYNTAX SEQUENCE OF Tn3270eIpResMapEntry 966 MAX-ACCESS not-accessible 967 STATUS current 968 DESCRIPTION 969 "This table defines Resource Pool to IP Group mappings. 970 Since both the Resource Pool Name and IP Group Name 971 are included in the index clause of this table multiple 972 Resource Pools can be assigned to the same IP Group. This 973 enables use of multiple Resource Pools for use in IP to 974 resource mapping. Assigning multiple IP Groups to the 975 same Resource Pool is also allowed but is not the primary 976 purpose for how the indexing is structured. 978 Assignment of Resource Pool to IP Group can be restricted 979 based on TCP Port. A index value of 0 for 980 tn3270eIpResMapClientPort disables restriction of resource 981 assignment based on IP Client target port selection." 982 ::= { tn3270eObjects 6 } 984 tn3270eIpResMapEntry OBJECT-TYPE 985 SYNTAX Tn3270eIpResMapEntry 986 MAX-ACCESS not-accessible 987 STATUS current 988 DESCRIPTION 989 "Definition of a single Resource Pool to IP Group mapping." 990 INDEX { tn3270eSrvrConfIndex, 991 tn3270eIpResMapPoolName, 992 tn3270eIpResMapIpGroupName, 993 tn3270eIpResMapClientPort } 994 ::= { tn3270eIpResMapTable 1 } 996 Tn3270eIpResMapEntry ::= SEQUENCE { 997 tn3270eIpResMapPoolName DisplayString, 999 White TN3270E Management Information Base (TN3270E-MIB)28 July 1997 1001 tn3270eIpResMapIpGroupName DisplayString, 1002 tn3270eIpResMapClientPort Unsigned32, 1003 tn3270eIpResMapRowStatus RowStatus } 1005 tn3270eIpResMapPoolName OBJECT-TYPE 1006 SYNTAX DisplayString (SIZE(1..24)) 1007 MAX-ACCESS not-accessible 1008 STATUS current 1009 DESCRIPTION 1010 "The name of a Resource Pool." 1011 ::= { tn3270eIpResMapEntry 1 } 1013 tn3270eIpResMapIpGroupName OBJECT-TYPE 1014 SYNTAX DisplayString (SIZE(1..24)) 1015 MAX-ACCESS not-accessible 1016 STATUS current 1017 DESCRIPTION 1018 "The name of the IP Group that is mapped to a 1019 Resource Pool." 1020 ::= { tn3270eIpResMapEntry 2 } 1022 tn3270eIpResMapClientPort OBJECT-TYPE 1023 SYNTAX Unsigned32 (0..65535) 1024 MAX-ACCESS not-accessible 1025 STATUS current 1026 DESCRIPTION 1027 "The port to restrict a Resource Pool to a IP Group 1028 mapping. A value of 0 for this objects implies that 1029 the mapping is not restricted." 1030 ::= { tn3270eIpResMapEntry 3 } 1032 tn3270eIpResMapRowStatus OBJECT-TYPE 1033 SYNTAX RowStatus 1034 MAX-ACCESS read-create 1035 STATUS current 1036 DESCRIPTION 1037 "This object allows entries to be created and deleted in the 1038 tn3270eIpResMapTable. 1040 An entry in this table is deleted by setting this object 1041 to destroy(6)." 1042 REFERENCE 1043 "RFC 1903, 'Textual Conventions for version 2 of the Simple 1044 Network Management Protocol (SNMPv2).'" 1045 ::= { tn3270eIpResMapEntry 4 } 1047 tn3270eResMapTable OBJECT-TYPE 1048 SYNTAX SEQUENCE OF Tn3270eResMapEntry 1050 White TN3270E Management Information Base (TN3270E-MIB)28 July 1997 1052 MAX-ACCESS not-accessible 1053 STATUS current 1054 DESCRIPTION 1055 "This table defines the actual mapping of a resource to 1056 a IP Address." 1057 ::= { tn3270eObjects 7 } 1059 tn3270eResMapEntry OBJECT-TYPE 1060 SYNTAX Tn3270eResMapEntry 1061 MAX-ACCESS not-accessible 1062 STATUS current 1063 DESCRIPTION 1064 "Definition of the mapping of a Resource Element to 1065 a IP Address." 1066 INDEX { tn3270eSrvrConfIndex, 1067 tn3270eResMapElementName, 1068 tn3270eResMapIpAddress } 1069 ::= { tn3270eResMapTable 1 } 1071 Tn3270eResMapEntry ::= SEQUENCE { 1072 tn3270eResMapElementName DisplayString, 1073 tn3270eResMapIpAddress IpAddress, 1074 tn3270eResMapElementType Tn3270ResourceType } 1076 tn3270eResMapElementName OBJECT-TYPE 1077 SYNTAX DisplayString (SIZE(1..8)) 1078 MAX-ACCESS not-accessible 1079 STATUS current 1080 DESCRIPTION 1081 "The Name of a resource element." 1082 ::= { tn3270eResMapEntry 1 } 1084 tn3270eResMapIpAddress OBJECT-TYPE 1085 SYNTAX IpAddress 1086 MAX-ACCESS not-accessible 1087 STATUS current 1088 DESCRIPTION 1089 "A client IP Address." 1090 ::= { tn3270eResMapEntry 2 } 1092 tn3270eResMapElementType OBJECT-TYPE 1093 SYNTAX Tn3270ResourceType 1094 MAX-ACCESS read-only 1095 STATUS current 1096 DESCRIPTION 1097 "The type of the associating resource element/" 1098 ::= { tn3270eResMapEntry 3 } 1100 White TN3270E Management Information Base (TN3270E-MIB)28 July 1997 1102 -- Define the set of objects to add to the Tcp Connection Table 1104 tn3270eTcpConnTable OBJECT-TYPE 1105 SYNTAX SEQUENCE OF Tn3270eTcpConnEntry 1106 MAX-ACCESS not-accessible 1107 STATUS current 1108 DESCRIPTION 1109 "Extends tcpConnTable to support TN3270 and TN3270E 1110 performance monitoring." 1111 ::= { tn3270eObjects 8 } 1113 tn3270eTcpConnEntry OBJECT-TYPE 1114 SYNTAX Tn3270eTcpConnEntry 1115 MAX-ACCESS not-accessible 1116 STATUS current 1117 DESCRIPTION 1118 "Provides in formation about a single TN3270/TN3270E 1119 session." 1120 INDEX { tcpConnLocalAddress, tcpConnLocalPort, 1121 tcpConnRemAddress, tcpConnRemPort } 1122 ::= { tn3270eTcpConnTable 1 } 1124 Tn3270eTcpConnEntry ::= 1125 SEQUENCE 1126 { 1127 tn3270eTcpConnLastActivity TimeTicks, 1128 tn3270eTcpConnBytesIn Counter32, 1129 tn3270eTcpConnBytesOut Counter32, 1130 tn3270eTcpConnResourceName DisplayString, 1131 tn3270eTcpConnResourceType Tn3270ResourceType, 1132 tn3270eTcpConnDeviceType Tn3270DeviceTypes, 1133 tn3270eTcpConnFunctions Tn3270Functions 1134 } 1136 tn3270eTcpConnLastActivity OBJECT-TYPE 1137 SYNTAX TimeTicks 1138 MAX-ACCESS read-only 1139 STATUS current 1140 DESCRIPTION 1141 "The number of 100ths of seconds since any data was 1142 transferred for the associating TCP Connection." 1143 DEFVAL { 0 } 1144 ::= { tn3270eTcpConnEntry 1 } 1146 tn3270eTcpConnBytesIn OBJECT-TYPE 1147 SYNTAX Counter32 1148 UNITS "octets" 1149 MAX-ACCESS read-only 1151 White TN3270E Management Information Base (TN3270E-MIB)28 July 1997 1153 STATUS current 1154 DESCRIPTION 1155 "The number of bytes received by the Server from TCP 1156 for this connection." 1157 ::= { tn3270eTcpConnEntry 2 } 1159 tn3270eTcpConnBytesOut OBJECT-TYPE 1160 SYNTAX Counter32 1161 UNITS "octets" 1162 MAX-ACCESS read-only 1163 STATUS current 1164 DESCRIPTION 1165 "The number of bytes sent to TCP for this connection." 1166 ::= { tn3270eTcpConnEntry 3 } 1168 tn3270eTcpConnResourceName OBJECT-TYPE 1169 SYNTAX DisplayString (SIZE(0..8)) 1170 MAX-ACCESS read-only 1171 STATUS current 1172 DESCRIPTION 1173 "LU/Print secondary name for connecting a IP Client 1174 into a SNA network." 1175 ::= { tn3270eTcpConnEntry 4 } 1177 tn3270eTcpConnResourceType OBJECT-TYPE 1178 SYNTAX Tn3270ResourceType 1179 MAX-ACCESS read-only 1180 STATUS current 1181 DESCRIPTION 1182 "Indicates the type of resource identified by 1183 tn3270eTcpConnResourceName." 1184 ::= { tn3270eTcpConnEntry 5 } 1186 tn3270eTcpConnDeviceType OBJECT-TYPE 1187 SYNTAX Tn3270DeviceTypes 1188 MAX-ACCESS read-only 1189 STATUS current 1190 DESCRIPTION 1191 "Indicates the device type if negiotiated with client. 1192 This object is also known as logmode." 1193 ::= { tn3270eTcpConnEntry 6 } 1195 tn3270eTcpConnFunctions OBJECT-TYPE 1196 SYNTAX Tn3270Functions 1197 MAX-ACCESS read-only 1198 STATUS current 1199 DESCRIPTION 1200 "This object will indicates which of the TN3270 and TN3270E 1202 White TN3270E Management Information Base (TN3270E-MIB)28 July 1997 1204 functions that are supported by the Server was negioted 1205 with a client. Refer to tn3270eSrvrFunctionsSupported." 1206 ::= { tn3270eTcpConnEntry 7 } 1208 -- Conformance Definitions 1210 tn3270eGroups OBJECT IDENTIFIER ::= { tn3270eConformance 1 } 1211 tn3270eCompliances OBJECT IDENTIFIER ::= { tn3270eConformance 2 } 1213 -- compliance statements 1214 tn3270eCompliance MODULE-COMPLIANCE 1215 STATUS current 1216 DESCRIPTION 1217 "The compliance statement for agents that support the 1218 TN3270E-MIB." 1219 MODULE -- this module 1220 MANDATORY-GROUPS { tn3270eBasicGroup, 1221 tn3270eSessionGroup 1222 } 1223 OBJECT tn3270eSrvrConfActivityCheck 1224 MIN-ACCESS read-only 1225 DESCRIPTION 1226 "The agent is not required to support a set to this 1227 object if the associating TN3270E Server doesn't 1228 support either TIMEMARK or NOP processing. In 1229 this case an agent should return noCheck on 1230 retrieval." 1231 OBJECT tn3270eSrvrConfActivityTimeout 1232 MIN-ACCESS read-only 1233 DESCRIPTION 1234 "The agent is not required to support a set to this 1235 object if the functions enabled by 1236 tn3270eSrvrConfActivityCheck are not supported. 1237 An agent in this case should return a value of 0." 1238 OBJECT tn3270eSrvrConfActivityInterval 1239 MIN-ACCESS read-only 1240 DESCRIPTION 1241 "The agent is not required to support a set to this 1242 object if the functions enabled by 1243 tn3270eSrvrConfActivityCheck are not supported. 1244 An agent in this case should return a value of 0." 1245 OBJECT tn3270eSrvrConfAdminStatus 1246 DESCRIPTION 1247 "A TN3270E Server is not required to support a 1248 stopImmediate state transition." 1249 ::= { tn3270eCompliances 1 } 1251 -- units of conformance 1253 White TN3270E Management Information Base (TN3270E-MIB)28 July 1997 1255 tn3270eBasicGroup OBJECT-GROUP 1256 OBJECTS { 1257 tn3270eSrvrConfInactivityTimeout, 1258 tn3270eSrvrConfActivityCheck, 1259 tn3270eSrvrConfActivityTimeout, 1260 tn3270eSrvrConfActivityInterval, 1261 tn3270eSrvrFunctionsSupported, 1262 tn3270eSrvrConfAdminStatus, 1263 tn3270eSrvrConfOperStatus, 1264 tn3270eSrvrConfSessionTermState, 1265 tn3270eSrvrConfSrvrType, 1266 tn3270eSrvrConfRowStatus, 1267 tn3270eSrvrPortRowStatus, 1268 tn3270eSrvrStatsUpTime, 1269 tn3270eSrvrStatsMaxLus, 1270 tn3270eSrvrStatsLusInUse, 1271 tn3270eSrvrStatsSpareLus, 1272 tn3270eSrvrStatsMaxPtrs, 1273 tn3270eSrvrStatsPtrsInUse, 1274 tn3270eSrvrStatsSparePtrs, 1275 tn3270eSrvrStatsConnectsIn, 1276 tn3270eSrvrStatsConnRejects, 1277 tn3270eSrvrStatsDisconnects, 1278 tn3270eIpGroupSubnetMask, 1279 tn3270eIpGroupRowStatus, 1280 tn3270eResPoolElementType, 1281 tn3270eResPoolRowStatus, 1282 tn3270eIpResMapRowStatus 1283 } 1284 STATUS current 1285 DESCRIPTION 1286 "This group is mandatory for all hosts supporting the 1287 TN3270E-MIB." 1288 ::= { tn3270eGroups 1 } 1290 tn3270eSessionGroup OBJECT-GROUP 1291 OBJECTS { 1292 tn3270eResMapElementType, 1293 tn3270eTcpConnLastActivity, 1294 tn3270eTcpConnBytesIn, 1295 tn3270eTcpConnBytesOut, 1296 tn3270eTcpConnResourceName, 1297 tn3270eTcpConnResourceType, 1298 tn3270eTcpConnDeviceType, 1299 tn3270eTcpConnFunctions 1300 } 1301 STATUS current 1302 DESCRIPTION 1304 White TN3270E Management Information Base (TN3270E-MIB)28 July 1997 1306 "This group is mandatory for all hosts supporting the 1307 TN3270E-MIB." 1308 ::= { tn3270eGroups 2 } 1310 END 1312 5. Security Considerations 1314 Certain management information defined in this MIB may be considered 1315 sensitive in some network environments. Therefore, authentication of 1316 received SNMP requests and controlled access to management information 1317 should be employed in such environments. The method for this 1318 authentication is a function of the SNMP Administrative Framework, and 1319 has not been expanded by this MIB. 1321 Several objects in this MIB allow write access or provide for remote 1322 creation. Allowing this support in a non-secure environment can have a 1323 negative effect on network operations. It is recommended that 1324 implementers seriously consider whether set operations should be 1325 allowed without providing, at a minimum, authentication of request 1326 origin. It it recommended that without such support that the following 1327 objects be implemented as read-only: 1329 o tn3270eSrvrConfInactivityTimout 1330 o tn3270eSrvrConfActivityCheck 1331 o tn3270eSrvrConfActivityTimeout 1332 o tn3270eSrvrConfActivityInterval 1333 o tn3270eSrvrConfAdminStatus 1334 o tn3270eSrvrConfSessionTermState 1335 o tn3270eIpGroupSubnetMask 1336 o tn3270eResPoolElementType 1338 The following objects should either be implemented as read-only or not 1339 implemented when security is an issue as previously discussed: 1341 o tn3270eSrvrConfRowStatus 1342 o tn3270eSrvrPortRowStatus 1343 o tn3270eIpGroupRowStatus 1344 o tn3270eResPoolRowStatus 1345 o tn3270eResMapRowStatus 1347 6. Acknowledgments 1349 This document is a product of the TN3270E Working Group. 1351 White TN3270E Management Information Base (TN3270E-MIB)28 July 1997 1353 7. References 1355 [1] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 1356 Waldbusser S., "Structure of Management Information for version 2 1357 of the Simple Network Management Protocol (SNMPv2)", RFC 1902, 1358 January 1996. 1360 [2] Network Working Group, Postel, J., and Reynolds, J., "Telnet 1361 Protocol Specification", RFC 854, May 1983. 1363 [3] Network Working Group, Postel, J., and Reynolds, J., "Telnet Timing 1364 Mark Option", RFC 860, May 1983. 1366 [4] Network Working Group and Rekhter J., "Telnet 3270 Regime Option", 1367 RFC 1041, January 1988. 1369 [5] McCloghrie, K., and M. Rose, Editors, "Management Information Base 1370 for Network Management of TCP/IP-based internets: MIB-II", STD 17, 1371 RFC 1213, Hughes LAN Systems, Performance Systems International, 1372 March 1991. 1374 [6] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. 1375 Waldbusser, "Textual Conventions for version 2 of the Simple 1376 Network Management Protocol (SNMPv2)", RFC 1903, January 1996. 1378 [7] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. 1379 Waldbusser, "Protocol Operations for version 2 of the Simple 1380 Network Management Protocol (SNMPv2)", RFC 1905, January 1996. 1382 [8] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. 1383 Waldbusser, "Conformance Statements for version 2 of the Simple 1384 Network Management Protocol (SNMPv2)", RFC 1904, January 1996. 1386 [9] Case, J., M. Fedor, M. Schoffstall, J. Davin, "Simple Network 1387 Management Protocol", RFC 1157, SNMP Research, Performance Systems 1388 International, MIT Laboratory for Computer Science, May 1990. 1390 [10] IETF SNMPv2 Working Group and McCloghrie, K., "TCP-MIB 1392 White TN3270E Management Information Base (TN3270E-MIB)28 July 1997 1394 Definitions", November 1994. 1396 8. Authors' Address 1398 Kenneth D. White 1399 Dept. G80/Bldg 503 1400 IBM Corporation 1401 Research Triangle Park, NC 27709, USA 1402 E-mail: kennethw@vnet.ibm.com