idnits 2.17.1 draft-ietf-tn3270e-tn3270-mib-03.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-25) 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 37 longer pages, the longest (page 2) being 61 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 38 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. ** There are 37 instances of too long lines in the document, the longest one being 10 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 1040 has weird spacing: '...is data can b...' == Line 1062 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 (September 1997) is 9719 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 1816, but no explicit reference was found in the text == Unused Reference: '4' is defined on line 1822, but no explicit reference was found in the text == Unused Reference: '10' is defined on line 1846, but no explicit reference was found in the text == Unused Reference: '11' is defined on line 1852, 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 (~~), 9 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: March, 1998 5 IBM Corp. 7 September 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) 13 September 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................................... 4 57 3.1.1 tn3270eSrvrConfTable................................... 4 58 3.1.2 tn3270eSrvrPortTable................................... 5 59 3.1.3 tn3270eSrvrStatsTable.................................. 5 60 3.2 TN3270E Server Resource Configuration.................... 6 61 3.3 Resource/Client Address Mappings......................... 6 62 3.3.1 tn3270eSnaMapTable..................................... 6 63 3.3.2 tn3270eResMapTable..................................... 6 64 3.3.3 TCP Connection Table Additions......................... 6 65 4.0 Definitions.............................................. 7 66 5.0 Security Considerations..................................36 67 6.0 Acknowledgments..........................................36 68 7.0 References...............................................37 69 8.0 Authors' Address.........................................38 71 1. Introduction 73 This document is a product of the TN3270E Working Group. Its purpose 74 is to define a MIB module for extending the traditional MIBs supported 75 by a TCP/IP implementation for configuration and management of TN3270E 76 servers. 78 2. The SNMPv2 Network Management Framework 80 The SNMP Network Management Framework presently consists of three 81 major components. They are: 83 o the SMI, described in RFC 1902 [1], - the mechanisms used for 84 describing and naming objects for the purpose of management. 86 o the MIB-II, STD 17, RFC 1213 [5], - the core set of managed 87 objects for the Internet suite of protocols. 89 o the protocol, RFC 1157 [9] and/or RFC 1905 [7] - the protocol 90 for accessing managed information. 92 Textual conventions are defined in RFC 1903 [6], and conformance 93 statements are defined in RFC 1904 [8]. 95 The Framework permits new objects to be defined for the purpose of 96 experimentation and evaluation. 98 White TN3270E Management Information Base (TN3270E-MIB) 13 September 1997 100 This memo specifies a MIB module that is compliant to the SNMPv2 SMI. 101 A semantically identical MIB conforming to the SNMPv1 SMI can be 102 produced through the appropriate translation. 104 2.1. Object Definitions 106 Managed objects are accessed via a virtual information store, termed 107 the Management Information Base or MIB. Objects in the MIB are 108 defined using the subset of Abstract Syntax Notation One (ASN.1) 109 defined in the SMI. In particular, each object object type is named 110 by an OBJECT IDENTIFIER, an administratively assigned name. The 111 object type together with an object instance serves to uniquely 112 identify a specific instantiation of the object. For human 113 convenience, we often use a textual string, termed the descriptor, to 114 refer to the object type. 116 3. Structure of the MIB 118 The TN3270E-MIB is split into the following components: 120 o TN3270E Server Control 121 o TN3270E Server Resource Configuration 122 o Resource/Client Address Mappings 124 The TN3270E-MIB is defined primarily for TN3270E servers. This memo 125 does not explicitly address use of the MIB by TN3270 servers that do 126 not support the TN3270E protocol. Although a significant number of 127 the objects do apply in the TN3270-only case, the case was not 128 addressed since it is unlikely that a TN3270-only server would 129 implement this MIB. 131 The SYSAPPL-MIB, reference [12], is a prerequisite for the TN3270E- 132 MIB, so that the Utf8String Textual Convention (TC) can be imported. 133 This TC, which is used for some MIB objects containing textual 134 information, enables internationalization of text strings, whereas the 135 DisplayString TC does not. 137 The MIB defined by this memo handles both IPv4 and IPv6 addressing. 138 Two Textual Conventions, Tn3270eAddrType and Tn3270eTAddress, are 139 defined for this purpose. Tn3270eTAddress is essentially equivalent 140 to TAddress, defined by RFC 1903. The difference is that 141 Tn3270eTAddress allows a null-length octet string, while TAddress 142 doesn't. Allowing a null IP Address is important, since in places 143 Tn3270eTAddress object values are used as a component of an object 144 instance, and need not actually contain an IP Address. In general, use 146 White TN3270E Management Information Base (TN3270E-MIB) 13 September 1997 148 of Tn3270eTAddress replaces the prior use of IpAddress to represent IP 149 Addresses. 151 Tn3270eAddrType is functionally equivalent to the TDomain TC, also 152 defined by RFC 1903. TDomain uses an OID to identify the contents of 153 a TAddress object. Tn3270eAddrType was chosen over TDomain because, 154 with a SYNTAX of Unsigned32 (enumeration type), it is much simpler 155 than an OID to specify in an instance identifier. 157 3.1. TN3270E Server Control 159 This group of objects provides for TN3270E server configuration, and 160 consists of: 162 o tn3270eSrvrConfTable 163 o tn3270eSrvrPortTable 164 o tn3270eSrvrStatsTable 166 3.1.1. tn3270eSrvrConfTable 168 The tn3270eSrvrConfTable contains a set of objects primarily for 169 configuring and managing a TN3270E server. As with most of the other 170 tables in the TN3270E-MIB, this table is indexed by an unsigned 171 integer, tn3270eSrvrConfIndex. This primary index element enables 172 support of multiple TN3270E servers on the same host. Within a host, 173 tn3270eSrvrConfIndex values must be unique, and need not be 174 contiguous; otherwise these values are implementation-dependent. 176 An earlier version of this memo had used the local IP Address 177 associated with a TN3270E server along with tn3270eSrvrConfIndex as 178 the primary indexes into most of its tables. Use of a local IP 179 Address was thought to enable use of these tables by management 180 applications. This approach was dropped, since it introduces a level 181 of complexity into MIB table indexing for little actual benefit. 183 tn3270eSrvrConfInactivityTimer defines the inactivity period for 184 TN3270 and TN3270E Sessions. tn3270eSrvrConfSessionTermState defines 185 how a session should be terminated. The three objects: 187 o tn3270eSrvrConfActivityCheck 188 o tn3270eSrvrConfActivityTimeout 189 o tn3270eSrvrConfActivityInterval 191 define the parameters for performing the "Telnet Timing Mark Option" 192 as defined by RFC 860 [3]. The object tn3270eSrvrConfActivityCheck is 193 defined to enable selection of either a NOP command or a TIMEMARK 195 White TN3270E Management Information Base (TN3270E-MIB) 13 September 1997 197 command. Sending a NOP command results in less overhead then a 198 TIMEMARK command, since a client doesn't send a reply. 200 The objects tn3270eSrvrConfAdminStatus and tn3270eSrvrConfOperStatus 201 enable remote starting and stopping of a TN3270E server. 202 tn3270eSrvrConfFunctionsSupported indicates which of the TN3270 and 203 TN3270E options a server supports. The object 204 tn3270eSrvrConfSessionTermState defines as a global option the 205 processing steps that a TN3270E server should perform when a TN3270E 206 session terminates with respect to the associated TCP connection. The 207 object tn3270eSrvrConfSrvrType indicates whether the TN3270E server 208 represented by the tn3270eSrvrConfEntry is a host or a gateway server. 209 The object tn3270eSrvrConfContact provides a scratch pad area for a 210 TN3270E server administrator to store information for later retrieval. 211 The object tn3270eSrvrConfRowStatus provides the capability to perform 212 remote creation and deletion operations on this table. 214 3.1.2. tn3270eSrvrPortTable 216 The tn3270eSrvrPortTable exists in order to assign and retrieve the 217 local TCP ports associated with a TN3270E server, since some TN3270E 218 server implementations support multiple local ports. A 219 tn3270eSrvrPortEntry is indexed by: 221 o tn3270eSrvrConfIndex 222 o tn3270eSrvrConfPort 223 o tn3270eSrvrConfPortAddrType 224 o tn3270eSrvrConfPortAddress 226 Certain TN3270E server implementations retrict a local TCP port to a 227 particular local IP Address, instead of allowing connections for any 228 local IP Address to occur via the port. tn3270eSrvrConfPortAddrType 229 and tn3270eSrvrConfPortAddress allow this restriction to be 230 represented in the MIB. A TN3270E server that doesn't restrict 231 connections over a port to a local IP Address should use the value 232 'unknown(0)' for tn3270eSrvrConfPortAddrType, and a null octet string 233 for tn3270eSrvrConfPortAddress. 235 3.1.3. tn3270eSrvrStatsTable 237 The tn3270eSrvrStatsTable defines a series of objects used to provide 238 general statistics on the use of a TN3270E server. 240 White TN3270E Management Information Base (TN3270E-MIB) 13 September 1997 242 3.2. TN3270E Server Resource Configuration 244 The TN3270E Server Resource Configuration collection of objects consists 245 of three tables: 247 o tn3270eClientGroupTable 248 o tn3270eResPoolTable 249 o tn3270eClientResMapTable 251 tn3270eClientGroupTable and tn3270eResPoolTable enable implementations 252 to define groupings of both client addresses and resource pools for 253 mapping client addresses to resources. The mapping of a client group to 254 a resource pool is enabled via the tn3270eClientResMapTable. 256 3.3. Resource/Client Address Mappings 258 Three tables are defined by this memo to enable mapping of resource 259 names to client addresses, and client addresses to resource names: 261 o tn3270eSnaMapTable 262 o tn3270eResMapTable 263 o TCP Connection Table Additions 265 3.3.1. tn3270eSnaMapTable 267 The tn3270eSnaMapTable is a read-only table that maps a secondary LU's 268 SNA network name to the name by which it is known locally at the TN3270e 269 server. An entry in this table is created when the Activate LU (ACTLU) 270 request carrying the SNA network name of the SLU is received from the 271 SSCP. The entry is deleted when the SLU is deactivated. 273 3.3.2. tn3270eResMapTable 275 The tn3270eResMapTable is a read-only table that maps a resource name to 276 a client's address. An entry in this table is created when a TCP 277 connection is received by a TN3270E server and mapped to a resource. The 278 entry is deleted when the resource-to-address association is no longer 279 valid. 281 3.3.3. TCP Connection Table Additions 283 The TCP Connection Table is defined by RFC 2012 (Refer to reference 10, 285 White TN3270E Management Information Base (TN3270E-MIB) 13 September 1997 287 TCP-MIB Definitions). Traditionally, the contents of the TCP Connection 288 Table have been implementation-dependent. Its formal definition 289 consists of the following objects: 291 o tcpConnState (INTEGER) 292 o tcpConnLocalAddress (IpAddress) 293 o tcpConnLocalPort (INTEGER) 294 o tcpConnRemAddress (IpAddress) 295 o tcpConnRemPort (INTEGER) 297 It is indexed by: tcpConnLocalAddress, tcpConnLocalPort, 298 tcpConnRemAddress, and tcpConnRemPort. 300 The tn3270eTcpConnTable contains objects for keeping a list of the 301 current set of TN3270 and TN3270E sessions at a TN3270E server. The 302 relationship between the tcpConnTable and the Tn3270eTcpConnTable is not 303 one-to-one, since the tn3270eTcpConnTable contains information 304 pertaining only to TN3270(E) sessions. 306 The tn3270eTcpConnTable has a different indexing structure from that of 307 the tcpConnTable. Instead of using IpAddress objects, Tn3270eTAddress 308 and Tn3270eAddrType object pairs are used to specify client addresses 309 (both local and remote). This enables support of IPv6 addresses. In 310 addition, the remote address pair precedes the local address pair in the 311 index clause, in order to enable a GET-NEXT operation using only the 312 remote address pair. 314 4. Definitions 316 TN3270E-MIB DEFINITIONS ::= BEGIN 318 IMPORTS 319 MODULE-IDENTITY, OBJECT-TYPE, BITS, Unsigned32, 320 experimental, TimeTicks, IpAddress, 321 Counter32, Gauge32, Counter64 322 FROM SNMPv2-SMI 323 TEXTUAL-CONVENTION, RowStatus 324 FROM SNMPv2-TC 325 MODULE-COMPLIANCE, OBJECT-GROUP 326 FROM SNMPv2-CONF 327 Utf8String 328 FROM SYSAPPL-MIB; 330 tn3270eMIB MODULE-IDENTITY 331 LAST-UPDATED "9709130000Z" -- September 13, 1997 332 ORGANIZATION "TN3270E Working Group" 333 CONTACT-INFO 335 White TN3270E Management Information Base (TN3270E-MIB) 13 September 1997 337 "Kenneth White (kennethw@vnet.ibm.com) 338 IBM Corp." 339 DESCRIPTION 340 "This module defines a portion of the management 341 information base (MIB) for managing TN3270E servers" 342 ::= { experimental 80 } 344 -- Textual Conventions 346 SnaResourceName ::= TEXTUAL-CONVENTION 347 STATUS current 348 DESCRIPTION 349 "The textual convention for defining an SNA resource 350 name. A fully qualified SNA resource name, consisting of 351 a 1 to 8 character network identifier (NetId), a 352 period ('.'), and a 1 to 8 character resource name 353 (ResName). 355 The NetId and ResName are constructed from the uppercase 356 letter 'A' - 'Z' and the numerics '0' - '9', all encoded 357 in ASCII, with the restriction that the first character 358 of each must be a letter. Trailing blanks are not allowed. 360 Earlier versions of SNA permitted three additional 361 characters in NetIds and ResNames: '#', '@', and '$'. 362 While this use of these characters has been retired, 363 a Management Station should still accept them for 364 backward compatibility. 366 Note: This Textual Convention is not subject to 367 internationalization, and does not use the character 368 encodings used by the Utf8String Textual Convention." 369 SYNTAX OCTET STRING (SIZE(0..17)) 371 Tn3270eAddrType ::= TEXTUAL-CONVENTION 372 STATUS current 373 DESCRIPTION 374 "The textual convention for defining the type of an IP 375 Address." 376 SYNTAX INTEGER { 377 unknown(0), 378 ipv4(1), 379 ipv6(2) 380 } 382 Tn3270ResourceType ::= TEXTUAL-CONVENTION 383 STATUS current 385 White TN3270E Management Information Base (TN3270E-MIB) 13 September 1997 387 DESCRIPTION 388 "The type of resource defined by a resource pool. Refer 389 to tn3270eResPoolTable." 390 SYNTAX INTEGER { 391 other(0), 392 lu(1), 393 printer(2) 394 } 396 Tn3270eTAddress ::= TEXTUAL-CONVENTION 397 STATUS current 398 DESCRIPTION 399 "Denotes an IP Address. The type of IP Address is determined 400 by use of the Tn3270eAddrType Textual Convention. 401 The length in octets of a Tn3270eTAddress object is: 403 Tn3270eAddrType ENUM 404 unknown(0) not known, must look at the 405 actual length of the 406 Tn3270eTAddress OCTET STRING. 407 ipv4(1) 4 OCTETS 408 ipv6(2) 16 OCTETS 410 This textual convention is similar to the TAddress TC 411 defined by RFC1903 except that it allows a zero length 412 OCTET STRING and is not a full transport layer address." 413 SYNTAX OCTET STRING (SIZE (0..255)) 415 Tn3270Functions ::= TEXTUAL-CONVENTION 416 STATUS current 417 DESCRIPTION 418 "This textual convention is intended to reflect the 419 current set of TN3270 and TN3270E functions that can 420 be negotiated between a server and its client: 422 RFC856 423 transmitBinary The sender of this command REQUESTS 424 permission to begin transmitting, or 425 confirms that it will now begin transmitting 426 characters which are to be interpreted 427 as 8 bits of binary data by 428 the receiver of the data. 429 RFC820 430 timeMark The sender of this command REQUESTS that 431 the receiver of this command return a WILL 432 TIMING-MARK in the data stream at the 433 'appropriate place' ... 434 RFC885 436 White TN3270E Management Information Base (TN3270E-MIB) 13 September 1997 438 endOfRecord The sender of this command requests 439 permission to begin transmission of the 440 Telnet END-OF-RECORD (EOR) code when 441 transmitting data characters, or 442 the sender of this command confirms it will 443 now begin transmission of EORs with 444 transmitted data characters. 445 RFC1091 446 terminalType Sender is willing to send terminal type 447 information in a subsequent sub-negotiation. 448 RFC1041 449 tn3270Regime Sender is willing to send list of supported 450 3270 Regimes in a subsequent sub-negotiation. 451 RFC1647 452 scsCtlCodes (Printer sessions only). Allows the use 453 of the SNA Character Stream (SCS) and SCS 454 control codes on the session. SCS is 455 used with LU type 1 SNA sessions. 456 dataStreamCtl (Printer sessions only). Allows the use 457 of the standard 3270 data stream. This 458 corresponds to LU type 3 SNA sessions. 459 responses Provides support for positive and 460 negative response handling. Allows the 461 server to reflect to the client any and 462 all definite, exception, and no response 463 requests sent by the host application. 464 bindImage Allows the server to send the SNA Bind 465 image and Unbind notification to the 466 client. 467 sysreq Allows the client and server to emulate 468 some (or all, depending on the server) of 469 the functions of the SYSREQ key in an SNA 470 environment." 471 SYNTAX BITS { 472 transmitBinary(0),-- rfc856 473 timemark(1), -- rfc860 474 endOfRecord(2), -- rfc885 475 terminalType(3), -- rfc1091 476 tn3270Regime(4), -- rfc1041 477 scsCtlCodes(5), -- rfc1647 478 dataStreamCtl(6), -- rfc1647 479 responses(7), -- rfc1647 480 bindImage(8), -- rfc1647 481 sysreq(9) -- rfc1647 482 } 484 Tn3270DeviceTypes ::= TEXTUAL-CONVENTION 485 STATUS current 487 White TN3270E Management Information Base (TN3270E-MIB) 13 September 1997 489 DESCRIPTION 490 "This textual convention defines the list of device types 491 that can be set as defined by RFC 1647." 492 SYNTAX INTEGER { -- terminals 493 unknown(0), 494 ibm3278d2(1), -- (24 row x 80 col display) 495 ibm3278d2E(2), -- (24 row x 80 col display) 496 ibm3278d3(3), -- (32 row x 80 col display) 497 ibm3278d3E(4), -- (32 row x 80 col display) 498 ibm3278d4(5), -- (43 row x 80 col display) 499 ibm3278d4E(6), -- (43 row x 80 col display) 500 ibm3278d5(7), -- (27 row x 132 col display) 501 ibm3278d5E(8), -- (27 row x 132 col display) 502 ibmDynamic(9), -- (no pre-defined display size) 503 ibm3287d1(10) -- printers 504 } 506 -- Top-level structure of the MIB 508 tn3270eNotifications OBJECT IDENTIFIER ::= { tn3270eMIB 0 } 509 tn3270eObjects OBJECT IDENTIFIER ::= { tn3270eMIB 1 } 510 tn3270eConformance OBJECT IDENTIFIER ::= { tn3270eMIB 3 } 512 -- MIB Objects 514 tn3270eSrvrConfTable OBJECT-TYPE 515 SYNTAX SEQUENCE OF Tn3270eSrvrConfEntry 516 MAX-ACCESS not-accessible 517 STATUS current 518 DESCRIPTION 519 "This table defines the configuration elements for 520 TN3270E Servers. The number of entries in this table 521 is expected to vary depending on the location of the 522 table. A particular TN3270E server is expected to 523 have a single entry. Modeling of the configuration 524 elements as a table allows multiple 525 TN3270E Servers to exist at the same host." 526 ::= { tn3270eObjects 1 } 528 tn3270eSrvrConfEntry OBJECT-TYPE 529 SYNTAX Tn3270eSrvrConfEntry 530 MAX-ACCESS not-accessible 531 STATUS current 532 DESCRIPTION 533 "Definition of the configuration elements for a single 534 TN3270E server." 535 INDEX { tn3270eSrvrConfIndex } 536 ::= { tn3270eSrvrConfTable 1 } 538 White TN3270E Management Information Base (TN3270E-MIB) 13 September 1997 540 Tn3270eSrvrConfEntry ::= SEQUENCE { 541 tn3270eSrvrConfIndex Unsigned32, 542 tn3270eSrvrConfInactivityTimeout Unsigned32, 543 tn3270eSrvrConfActivityCheck INTEGER, 544 tn3270eSrvrConfActivityTimeout Unsigned32, 545 tn3270eSrvrConfActivityInterval Unsigned32, 546 tn3270eSrvrFunctionsSupported Tn3270Functions, 547 tn3270eSrvrConfAdminStatus INTEGER, 548 tn3270eSrvrConfOperStatus INTEGER, 549 tn3270eSrvrConfSessionTermState INTEGER, 550 tn3270eSrvrConfSrvrType INTEGER, 551 tn3270eSrvrConfContact Utf8String, 552 tn3270eSrvrConfRowStatus RowStatus 553 } 555 tn3270eSrvrConfIndex OBJECT-TYPE 556 SYNTAX Unsigned32 557 MAX-ACCESS not-accessible 558 STATUS current 559 DESCRIPTION 560 "Indicates the instance of a TN3270E server that 561 exists at an IP Host. Assignments of tn3270eSrvrConfIndex 562 values need not be continuous and is implementation 563 dependent. Within a host, assignment of 564 tn3270eSrvrConfIndex values must be unique." 565 ::= { tn3270eSrvrConfEntry 1 } 567 tn3270eSrvrConfInactivityTimeout OBJECT-TYPE 568 SYNTAX Unsigned32 (0..99999999) 569 UNITS "seconds" 570 MAX-ACCESS read-create 571 STATUS current 572 DESCRIPTION 573 "The inactivity time-out specified in seconds. When a 574 connection has been inactive for the number of seconds 575 specified by this object it is closed. The default of 576 0 means no inactivity time-out." 577 DEFVAL { 0 } 578 ::= { tn3270eSrvrConfEntry 2 } 580 tn3270eSrvrConfActivityCheck OBJECT-TYPE 581 SYNTAX INTEGER { 582 noCheck(0), 583 timeMark(1), 584 nop(2) 585 } 586 MAX-ACCESS read-create 587 STATUS current 589 White TN3270E Management Information Base (TN3270E-MIB) 13 September 1997 591 DESCRIPTION 592 "This object is intended to enable either timemark or 593 nop processing." 594 DEFVAL { noCheck } 595 ::= { tn3270eSrvrConfEntry 3 } 597 tn3270eSrvrConfActivityTimeout OBJECT-TYPE 598 SYNTAX Unsigned32 (1..99999999) 599 UNITS "seconds" 600 MAX-ACCESS read-create 601 STATUS current 602 DESCRIPTION 603 "The TIMEMARK or NOP processing time-out specified in seconds. 604 Note that a value of 0 is not allowed for this object since 605 the function that uses this object relies on 606 tn3270eSrvrConfActivityCheck for function enablement." 607 DEFVAL { 600 } -- 10 minutes 608 ::= { tn3270eSrvrConfEntry 4 } 610 tn3270eSrvrConfActivityInterval OBJECT-TYPE 611 SYNTAX Unsigned32 (1..99999999) 612 UNITS "seconds" 613 MAX-ACCESS read-create 614 STATUS current 615 DESCRIPTION 616 "The scan interval to be used by a TN3270E server. 617 TIMEMARK or NOP processing scans the Telnet sessions 618 on the interval provided by this object looking for 619 sessions that have been idle for more than the value 620 provided by tn3270eSrvrConfActivityTimeout. 621 Note that a value of 0 is not allowed for this object since 622 the function that uses this object relies on 623 tn3270eSrvrConfActivityCheck for function enablement." 624 DEFVAL { 120 } -- 2 minutes 625 ::= { tn3270eSrvrConfEntry 5 } 627 tn3270eSrvrFunctionsSupported OBJECT-TYPE 628 SYNTAX Tn3270Functions 629 MAX-ACCESS read-only 630 STATUS current 631 DESCRIPTION 632 "This object indicates the functions supported by a 633 TN3270E server." 634 DEFVAL { { scsCtlCodes, dataStreamCtl, 635 responses, bindImage, sysreq } } 636 ::= { tn3270eSrvrConfEntry 6 } 638 tn3270eSrvrConfAdminStatus OBJECT-TYPE 640 White TN3270E Management Information Base (TN3270E-MIB) 13 September 1997 642 SYNTAX INTEGER { 643 up(1), 644 down(2), 645 stopImmediate(3) 646 } 647 MAX-ACCESS read-create 648 STATUS current 649 DESCRIPTION 650 "The desired state of the TN3270E server: 652 up(1) - Activate a TN3270E server. 653 down(2) - Informs the associating TN3270E server 654 to gracefully terminate its processing. 655 stopImmediate(3) - Informs the associating TN3270E server 656 to terminate immediately. 658 Implementation as to the exact semantics of either down(2) 659 or stopImmediate(3) processing is left as implementation 660 dependent. A TN3270E server that does not distinguish 661 between down or stopImmediate transitions should not 662 support stopImmediate." 663 ::= { tn3270eSrvrConfEntry 7 } 665 tn3270eSrvrConfOperStatus OBJECT-TYPE 666 SYNTAX INTEGER { 667 up(1), 668 down(2) 669 } 670 MAX-ACCESS read-only 671 STATUS current 672 DESCRIPTION 673 "The current operational state of a TN3270E server: 675 up(1) - The corresponding TN3270E server is active. 676 down(2) - The corresponding TN3270E server is inactive." 677 ::= { tn3270eSrvrConfEntry 8 } 679 tn3270eSrvrConfSessionTermState OBJECT-TYPE 680 SYNTAX INTEGER { 681 terminate(1), 682 luSessionPend(2), 683 queueSession(3) 684 } 685 MAX-ACCESS read-create 686 STATUS current 687 DESCRIPTION 688 "The current state for determining what a TN3270E server 689 should do when a TN3270 Session terminates: 691 White TN3270E Management Information Base (TN3270E-MIB) 13 September 1997 693 terminate(1) => Terminate TCP connection. 694 luSessionPend(2) => Do not drop the TCP Connection 695 associated with an IP client when their 696 TN3270 Session ends. Processing should 697 redrive session initialization as if the 698 client was first connecting. 699 queueSession(3) => QUEUESESSION deals with CLSDST-Pass. 700 An example is the easiest explanation. 701 Assume APPL1 does a CLSDST-Pass 702 to APPL2. Then the client logs off APPL 703 Without QUEUESESSION the connection 704 would now be broken. With QUEUESESSION 705 the TN3270E server keeps the LU around 706 after getting the APPL2 unbind waiting 707 for a bind from APPL1." 708 DEFVAL { terminate } 709 ::= { tn3270eSrvrConfEntry 9 } 711 tn3270eSrvrConfSrvrType OBJECT-TYPE 712 SYNTAX INTEGER { 713 unknown(0), 714 host(1), 715 gateway(2) 716 } 717 MAX-ACCESS read-only 718 STATUS current 719 DESCRIPTION 720 "This object indicates the type of TN3270E server. 721 The existence of MIB tables and objects that will be 722 defined by follow-on MIBs may be predicated on whether the 723 TN3270E server can be local to the same host as a 724 Target Application (host(1)) or will always be remote 725 (gateway(2))." 726 ::= { tn3270eSrvrConfEntry 10 } 728 tn3270eSrvrConfContact OBJECT-TYPE 729 SYNTAX Utf8String (SIZE(0..255)) 730 MAX-ACCESS read-create 731 STATUS current 732 DESCRIPTION 733 "This object provides a scratch pad for a TN3270E server 734 administrator for storing information for later retrieval." 735 ::= { tn3270eSrvrConfEntry 11 } 737 tn3270eSrvrConfRowStatus OBJECT-TYPE 738 SYNTAX RowStatus 739 MAX-ACCESS read-create 740 STATUS current 742 White TN3270E Management Information Base (TN3270E-MIB) 13 September 1997 744 DESCRIPTION 745 "This object allows entries to be created and deleted in the 746 tn3270eSrvrConfTable. 748 An entry in this table is deleted by setting this object 749 to destroy(6)." 750 REFERENCE 751 "RFC 1903, 'Textual Conventions for version 2 of the Simple 752 Network Management Protocol (SNMPv2).'" 753 ::= { tn3270eSrvrConfEntry 12 } 755 tn3270eSrvrPortTable OBJECT-TYPE 756 SYNTAX SEQUENCE OF Tn3270eSrvrPortEntry 757 MAX-ACCESS not-accessible 758 STATUS current 759 DESCRIPTION 760 "This table defines the TCP ports associated with TN3270E 761 Servers." 762 ::= { tn3270eObjects 2 } 764 tn3270eSrvrPortEntry OBJECT-TYPE 765 SYNTAX Tn3270eSrvrPortEntry 766 MAX-ACCESS not-accessible 767 STATUS current 768 DESCRIPTION 769 "Definition of a single TCP port assignment to a 770 TN3270E server." 771 INDEX { 772 tn3270eSrvrConfIndex, 773 tn3270eSrvrPort, 774 tn3270eSrvrPortAddrType, 775 tn3270eSrvrPortAddress 776 } 777 ::= { tn3270eSrvrPortTable 1 } 779 Tn3270eSrvrPortEntry ::= SEQUENCE { 780 tn3270eSrvrPort Unsigned32, 781 tn3270eSrvrPortAddrType Tn3270eAddrType, 782 tn3270eSrvrPortAddress Tn3270eTAddress, 783 tn3270eSrvrPortRowStatus RowStatus 784 } 786 tn3270eSrvrPort OBJECT-TYPE 787 SYNTAX Unsigned32 (0..65535) 788 MAX-ACCESS not-accessible 789 STATUS current 790 DESCRIPTION 791 "Indicates a port assigned to a server." 793 White TN3270E Management Information Base (TN3270E-MIB) 13 September 1997 795 ::= { tn3270eSrvrPortEntry 1 } 797 tn3270eSrvrPortAddrType OBJECT-TYPE 798 SYNTAX Tn3270eAddrType 799 MAX-ACCESS not-accessible 800 STATUS current 801 DESCRIPTION 802 "Indicates the type of the IP Address represented in 803 tn3270eSrvrPortAddress." 804 ::= { tn3270eSrvrPortEntry 2 } 806 tn3270eSrvrPortAddress OBJECT-TYPE 807 SYNTAX Tn3270eTAddress 808 MAX-ACCESS not-accessible 809 STATUS current 810 DESCRIPTION 811 "The IP Address associated with a TN3270E server port. 812 tn3270eClientGroupAddrType indicates the address type 813 (ipv4 or ipv6 for example)." 814 ::= { tn3270eSrvrPortEntry 3 } 816 tn3270eSrvrPortRowStatus OBJECT-TYPE 817 SYNTAX RowStatus 818 MAX-ACCESS read-create 819 STATUS current 820 DESCRIPTION 821 "This object allows entries to be created and deleted in the 822 tn3270eSrvrPortTable. 824 An entry in this table is deleted by setting this object 825 to destroy(6)." 826 REFERENCE 827 "RFC 1903, 'Textual Conventions for version 2 of the Simple 828 Network Management Protocol (SNMPv2).'" 829 ::= { tn3270eSrvrPortEntry 4 } 831 tn3270eSrvrStatsTable OBJECT-TYPE 832 SYNTAX SEQUENCE OF Tn3270eSrvrStatsEntry 833 MAX-ACCESS not-accessible 834 STATUS current 835 DESCRIPTION 836 "This table defines a set of statistics concerning 837 global TN3270E server performance." 838 ::= { tn3270eObjects 3 } 840 tn3270eSrvrStatsEntry OBJECT-TYPE 841 SYNTAX Tn3270eSrvrStatsEntry 842 MAX-ACCESS not-accessible 844 White TN3270E Management Information Base (TN3270E-MIB) 13 September 1997 846 STATUS current 847 DESCRIPTION 848 "Collection of a set of statistic objects for a single 849 TN3270 server. An entry can be global with respect to 850 a single TN3270E server or be specified at a port level. 851 Refer to the text description for tn3270eSrvrStatsPort. 853 It is possible that a TN3270E server implementation may 854 not be structured to support resource usage on a port basis 855 but provide statistics via an entry in this table for 856 each port. The recommended approach for this is to 857 provide a global entry (a value of 0 for 858 tn3270eSrvrStatsPort) with: 860 tn3270eSrvrStatsMaxLus 861 tn3270eSrvrStatsMaxLus 862 tn3270eSrvrStatsLusInUse 863 tn3270eSrvrStatsSpareLus 864 tn3270eSrvrStatsMaxPtrs 865 tn3270eSrvrStatsPtrsInUse 866 tn3270eSrvrStatsSparePtrs 868 set at this layer but set to zero at the port layer." 869 INDEX { tn3270eSrvrConfIndex, tn3270eSrvrStatsPort } 870 ::= { tn3270eSrvrStatsTable 1 } 872 Tn3270eSrvrStatsEntry ::= SEQUENCE { 873 tn3270eSrvrStatsPort Unsigned32, 874 tn3270eSrvrStatsUpTime TimeTicks, 875 tn3270eSrvrStatsMaxLus Unsigned32, 876 tn3270eSrvrStatsLusInUse Gauge32, 877 tn3270eSrvrStatsSpareLus Gauge32, 878 tn3270eSrvrStatsMaxPtrs Unsigned32, 879 tn3270eSrvrStatsPtrsInUse Gauge32, 880 tn3270eSrvrStatsSparePtrs Gauge32, 881 tn3270eSrvrStatsConnectsIn Counter32, 882 tn3270eSrvrStatsConnRejects Counter32, 883 tn3270eSrvrStatsDisconnects Counter32, 884 tn3270eSrvrStatsOctetsIn Counter64, 885 tn3270eSrvrStatsOctetsInLow Counter32, 886 tn3270eSrvrStatsOctetsOut Counter64, 887 tn3270eSrvrStatsOctetsOutLow Counter32 888 } 890 tn3270eSrvrStatsPort OBJECT-TYPE 891 SYNTAX Unsigned32 (0..65535) 892 MAX-ACCESS not-accessible 893 STATUS current 895 White TN3270E Management Information Base (TN3270E-MIB) 13 September 1997 897 DESCRIPTION 898 "Indicates the port that the corresponding statistics are 899 for. Implementation of collection of these statistics 900 on a port basis is not mandatory. An implementation may 901 limit itself to keeping this data on a global basis by 902 using a value of 0." 903 ::= { tn3270eSrvrStatsEntry 1 } 905 tn3270eSrvrStatsUpTime OBJECT-TYPE 906 SYNTAX TimeTicks 907 MAX-ACCESS read-only 908 STATUS current 909 DESCRIPTION 910 "Indicates when either usage of a associating port becomes 911 active (tn3270eSrvrStatsPort non-zero) or if the entry 912 is being kept on a global basis the time that the TN3270E 913 server becomes active. The value of this object does not 914 get reset based on port usage status changes or changes 915 to tn3270eSrvrConfOperStatus." 916 ::= { tn3270eSrvrStatsEntry 2 } 918 tn3270eSrvrStatsMaxLus OBJECT-TYPE 919 SYNTAX Unsigned32 920 MAX-ACCESS read-only 921 STATUS current 922 DESCRIPTION 923 "Indicates the maximum number of LUs for use by a 924 TN3270E server. The granularity of this data can be 925 either global (corresponding tn3270eSrvrStatsPort index 926 equal to 0) or on a port basis." 927 ::= { tn3270eSrvrStatsEntry 3 } 929 tn3270eSrvrStatsLusInUse OBJECT-TYPE 930 SYNTAX Gauge32 931 MAX-ACCESS read-only 932 STATUS current 933 DESCRIPTION 934 "Indicates the current number of LUs in use by a 935 TN3270E server. The granularity of this data can be 936 either global (corresponding tn3270eSrvrStatsPort index 937 equal to 0) or on a port basis." 938 ::= { tn3270eSrvrStatsEntry 4 } 940 tn3270eSrvrStatsSpareLus OBJECT-TYPE 941 SYNTAX Gauge32 942 MAX-ACCESS read-only 943 STATUS current 944 DESCRIPTION 946 White TN3270E Management Information Base (TN3270E-MIB) 13 September 1997 948 "Indicates the number of free LUs for a particular TN3270E 949 server. It is possible that the difference between 950 tn3270eSrvrStatsMaxLus and tn3270eSrvrStatsLusInUse does 951 not equal tn3270eSrvrStatsSpareLus. An LU may exist 952 but not be useable by an IP client connection. 953 The granularity of this data can be 954 either global (corresponding tn3270eSrvrStatsPort index 955 equal to 0) or on a port basis." 956 ::= { tn3270eSrvrStatsEntry 5 } 958 tn3270eSrvrStatsMaxPtrs OBJECT-TYPE 959 SYNTAX Unsigned32 960 MAX-ACCESS read-only 961 STATUS current 962 DESCRIPTION 963 "Indicates the maximum number of Printer Resources for 964 use by a TN3270E server. The granularity of this data 965 can be either global (corresponding tn3270eSrvrStatsPort 966 index equal to 0) or on a port basis." 967 ::= { tn3270eSrvrStatsEntry 6 } 969 tn3270eSrvrStatsPtrsInUse OBJECT-TYPE 970 SYNTAX Gauge32 971 MAX-ACCESS read-only 972 STATUS current 973 DESCRIPTION 974 "Indicates the current number of Printer Resources in 975 use by a TN3270E server. The granularity of this data 976 can be either global (corresponding tn3270eSrvrStatsPort 977 index equal to 0) or on a port basis." 978 ::= { tn3270eSrvrStatsEntry 7 } 980 tn3270eSrvrStatsSparePtrs OBJECT-TYPE 981 SYNTAX Gauge32 982 MAX-ACCESS read-only 983 STATUS current 984 DESCRIPTION 985 "Indicates the number of free Printer Resources for a 986 particular TN3270E server. It is possible that the 987 difference between tn3270eSrvrStatsMaxPtrs and 988 tn3270eSrvrStatsPtrsInUse does not equal 989 tn3270eSrvrStatsSparePtrs. A Printer resource may 990 exist but not be useable by an IP client connection. 991 The granularity of this data 992 can be either global (corresponding tn3270eSrvrStatsPort 993 index equal to 0) or on a port basis." 994 ::= { tn3270eSrvrStatsEntry 8 } 996 White TN3270E Management Information Base (TN3270E-MIB) 13 September 1997 998 tn3270eSrvrStatsConnectsIn OBJECT-TYPE 999 SYNTAX Counter32 1000 MAX-ACCESS read-only 1001 STATUS current 1002 DESCRIPTION 1003 "Indicates the number of client connections received by a 1004 TN3270E server. The granularity of this data 1005 can be either global (corresponding tn3270eSrvrStatsPort 1006 index equal to 0) or on a port basis." 1007 ::= { tn3270eSrvrStatsEntry 9 } 1009 tn3270eSrvrStatsConnRejects OBJECT-TYPE 1010 SYNTAX Counter32 1011 MAX-ACCESS read-only 1012 STATUS current 1013 DESCRIPTION 1014 "Indicates the number of client connections rejected during 1015 connection setup. An example of this is when no LU or 1016 Printer resource is available to associate with the 1017 TCP Connection of an IP client. The granularity of this data 1018 can be either global (corresponding tn3270eSrvrStatsPort 1019 index equal to 0) or on a port basis." 1020 ::= { tn3270eSrvrStatsEntry 10 } 1022 tn3270eSrvrStatsDisconnects OBJECT-TYPE 1023 SYNTAX Counter32 1024 MAX-ACCESS read-only 1025 STATUS current 1026 DESCRIPTION 1027 "Indicates the number of client connections disconnected by a 1028 TN3270E server. The granularity of this data 1029 can be either global (corresponding tn3270eSrvrStatsPort 1030 index equal to 0) or on a port basis." 1031 ::= { tn3270eSrvrStatsEntry 11 } 1033 tn3270eSrvrStatsOctetsIn OBJECT-TYPE 1034 SYNTAX Counter64 1035 MAX-ACCESS read-only 1036 STATUS current 1037 DESCRIPTION 1038 "Indicates the number of octets received from TN3270 1039 and TN3270E Clients. The granularity 1040 of this data can be either global (corresponding 1041 tn3270eSrvrStatsPort index equal to 0) or on a port basis." 1042 ::= { tn3270eSrvrStatsEntry 12 } 1044 tn3270eSrvrStatsOctetsInLow OBJECT-TYPE 1045 SYNTAX Counter32 1047 White TN3270E Management Information Base (TN3270E-MIB) 13 September 1997 1049 MAX-ACCESS read-only 1050 STATUS current 1051 DESCRIPTION 1052 "Low order 32 bits of tn3270eSrvrStatsOctetsIn." 1053 ::= { tn3270eSrvrStatsEntry 13 } 1055 tn3270eSrvrStatsOctetsOut OBJECT-TYPE 1056 SYNTAX Counter64 1057 MAX-ACCESS read-only 1058 STATUS current 1059 DESCRIPTION 1060 "Indicates the number of octets sent to TN3270 1061 and TN3270E Clients. The granularity 1062 of this data can be either global (corresponding 1063 tn3270eSrvrStatsPort index equal to 0) or on a port basis." 1064 ::= { tn3270eSrvrStatsEntry 14 } 1066 tn3270eSrvrStatsOctetsOutLow OBJECT-TYPE 1067 SYNTAX Counter32 1068 MAX-ACCESS read-only 1069 STATUS current 1070 DESCRIPTION 1071 "Low order 32 bits of tn3270eSrvrStatsOctetsOut." 1072 ::= { tn3270eSrvrStatsEntry 15 } 1074 tn3270eClientGroupTable OBJECT-TYPE 1075 SYNTAX SEQUENCE OF Tn3270eClientGroupEntry 1076 MAX-ACCESS not-accessible 1077 STATUS current 1078 DESCRIPTION 1079 "This table defines client address groupings for use by a 1080 TN3270E server." 1081 ::= { tn3270eObjects 4 } 1083 tn3270eClientGroupEntry OBJECT-TYPE 1084 SYNTAX Tn3270eClientGroupEntry 1085 MAX-ACCESS not-accessible 1086 STATUS current 1087 DESCRIPTION 1088 "Definition of a single client address entry. All entries with 1089 the same first two indexes, tn3270eSrvrConfIndex and 1090 tn3270eClientGroupName, are considered to be in the same 1091 client group." 1092 INDEX { tn3270eSrvrConfIndex, 1093 tn3270eClientGroupName, 1094 tn3270eClientGroupAddrType, 1095 tn3270eClientGroupAddress } 1096 ::= { tn3270eClientGroupTable 1 } 1098 White TN3270E Management Information Base (TN3270E-MIB) 13 September 1997 1100 Tn3270eClientGroupEntry ::= SEQUENCE { 1101 tn3270eClientGroupName Utf8String, 1102 tn3270eClientGroupAddrType Tn3270eAddrType, 1103 tn3270eClientGroupAddress Tn3270eTAddress, 1104 tn3270eClientGroupSubnetMask IpAddress, 1105 tn3270eClientGroupPfxLength Unsigned32, 1106 tn3270eClientGroupRowStatus RowStatus } 1108 tn3270eClientGroupName OBJECT-TYPE 1109 SYNTAX Utf8String (SIZE(1..24)) 1110 MAX-ACCESS not-accessible 1111 STATUS current 1112 DESCRIPTION 1113 "The name of a client group." 1114 ::= { tn3270eClientGroupEntry 1 } 1116 tn3270eClientGroupAddrType OBJECT-TYPE 1117 SYNTAX Tn3270eAddrType 1118 MAX-ACCESS not-accessible 1119 STATUS current 1120 DESCRIPTION 1121 "Indicates the type of the address represented in 1122 tn3270eClientGroupAddress." 1123 ::= { tn3270eClientGroupEntry 2 } 1125 tn3270eClientGroupAddress OBJECT-TYPE 1126 SYNTAX Tn3270eTAddress 1127 MAX-ACCESS not-accessible 1128 STATUS current 1129 DESCRIPTION 1130 "The client address of a member of a client group. The value 1131 of tn3270eClientGroupAddrType indicates the address 1132 type (ipv4 or ipv6 for example)." 1133 ::= { tn3270eClientGroupEntry 3 } 1135 tn3270eClientGroupSubnetMask OBJECT-TYPE 1136 SYNTAX IpAddress 1137 MAX-ACCESS read-create 1138 STATUS current 1139 DESCRIPTION 1140 "The corresponding subnet mask associated with 1141 tn3270eClientGroupAddress. A single IP Address is 1142 represented by having this object contain the value 1143 of 255.255.255.255. This object is valid only if 1144 tn3270eClientGroupAddrType has a value of ipv4(1)." 1145 DEFVAL { 'FFFFFFFF'H } 1146 ::= { tn3270eClientGroupEntry 4 } 1148 White TN3270E Management Information Base (TN3270E-MIB) 13 September 1997 1150 tn3270eClientGroupPfxLength OBJECT-TYPE 1151 SYNTAX Unsigned32 (0..128) 1152 MAX-ACCESS read-create 1153 STATUS current 1154 DESCRIPTION 1155 "The corresponding IPv6 network prefix length. This 1156 object is valid only if tn3270eClientGroupAddrType 1157 has a value of ipv6(2)." 1158 DEFVAL { 0 } 1159 ::= { tn3270eClientGroupEntry 5 } 1161 tn3270eClientGroupRowStatus OBJECT-TYPE 1162 SYNTAX RowStatus 1163 MAX-ACCESS read-create 1164 STATUS current 1165 DESCRIPTION 1166 "This object allows entries to be created and deleted in the 1167 tn3270eClientGroupTable. 1169 An entry in this table is deleted by setting this object 1170 to destroy(6)." 1171 REFERENCE 1172 "RFC 1903, 'Textual Conventions for version 2 of the Simple 1173 Network Management Protocol (SNMPv2).'" 1174 ::= { tn3270eClientGroupEntry 6 } 1176 tn3270eResPoolTable OBJECT-TYPE 1177 SYNTAX SEQUENCE OF Tn3270eResPoolEntry 1178 MAX-ACCESS not-accessible 1179 STATUS current 1180 DESCRIPTION 1181 "This table defines resource groupings; the term 1182 'pool' is used as it is defined by RFC 1647." 1183 ::= { tn3270eObjects 5 } 1185 tn3270eResPoolEntry OBJECT-TYPE 1186 SYNTAX Tn3270eResPoolEntry 1187 MAX-ACCESS not-accessible 1188 STATUS current 1189 DESCRIPTION 1190 "Definition of a single resource pool member. All entries 1191 with the same first two indexes, tn3270eSrvrConfIndex and 1192 tn3270eResPoolName, are considered to be in the same pool." 1193 INDEX { tn3270eSrvrConfIndex, 1194 tn3270eResPoolName, 1195 tn3270eResPoolElementName } 1196 ::= { tn3270eResPoolTable 1 } 1198 White TN3270E Management Information Base (TN3270E-MIB) 13 September 1997 1200 Tn3270eResPoolEntry ::= SEQUENCE { 1201 tn3270eResPoolName Utf8String, 1202 tn3270eResPoolElementName SnaResourceName, 1203 tn3270eResPoolElementType Tn3270ResourceType, 1204 tn3270eResPoolRowStatus RowStatus } 1206 tn3270eResPoolName OBJECT-TYPE 1207 SYNTAX Utf8String (SIZE(1..24)) 1208 MAX-ACCESS not-accessible 1209 STATUS current 1210 DESCRIPTION 1211 "The name of a resource pool.." 1212 ::= { tn3270eResPoolEntry 1 } 1214 tn3270eResPoolElementName OBJECT-TYPE 1215 SYNTAX SnaResourceName 1216 MAX-ACCESS not-accessible 1217 STATUS current 1218 DESCRIPTION 1219 "The name of a member of a resource pool." 1220 ::= { tn3270eResPoolEntry 2 } 1222 tn3270eResPoolElementType OBJECT-TYPE 1223 SYNTAX Tn3270ResourceType 1224 MAX-ACCESS read-create 1225 STATUS current 1226 DESCRIPTION 1227 "The type of the entity in a resource pool." 1228 ::= { tn3270eResPoolEntry 3 } 1230 tn3270eResPoolRowStatus OBJECT-TYPE 1231 SYNTAX RowStatus 1232 MAX-ACCESS read-create 1233 STATUS current 1234 DESCRIPTION 1235 "This object allows entries to be created and deleted in the 1236 tn3270eResPoolTable. 1238 An entry in this table is deleted by setting this object 1239 to destroy(6)." 1240 REFERENCE 1241 "RFC 1903, 'Textual Conventions for version 2 of the Simple 1242 Network Management Protocol (SNMPv2).'" 1243 ::= { tn3270eResPoolEntry 4 } 1245 tn3270eSnaMapTable OBJECT-TYPE 1246 SYNTAX SEQUENCE OF Tn3270eSnaMapEntry 1247 MAX-ACCESS not-accessible 1249 White TN3270E Management Information Base (TN3270E-MIB) 13 September 1997 1251 STATUS current 1252 DESCRIPTION 1253 "This table provide a mapping from the name by which 1254 a secondary LU is known in the SNA network to the 1255 name by which it is known locally at the TN3270e 1256 server. This latter name serves as an index into 1257 the tn3270eResPoolTable and the tn3270eResMapTable." 1258 ::= { tn3270eObjects 6 } 1260 tn3270eSnaMapEntry OBJECT-TYPE 1261 SYNTAX Tn3270eSnaMapEntry 1262 MAX-ACCESS not-accessible 1263 STATUS current 1264 DESCRIPTION 1265 "Definition of a single mapping from an SSCP-supplied 1266 SLU name to a local SLU name." 1267 INDEX { tn3270eSrvrConfIndex, 1268 tn3270eSnaMapSscpSuppliedName } 1269 ::= { tn3270eSnaMapTable 1 } 1271 Tn3270eSnaMapEntry ::= SEQUENCE { 1272 tn3270eSnaMapSscpSuppliedName SnaResourceName, 1273 tn3270eSnaMapLocalName SnaResourceName } 1275 tn3270eSnaMapSscpSuppliedName OBJECT-TYPE 1276 SYNTAX SnaResourceName 1277 MAX-ACCESS not-accessible 1278 STATUS current 1279 DESCRIPTION 1280 "The name of the secondary LU (SLU) as it is known in the 1281 SNA network. This name is sent by the SSCP on the 1282 Activate Logical Unit (ACTLU) request." 1283 ::= { tn3270eSnaMapEntry 1 } 1285 tn3270eSnaMapLocalName OBJECT-TYPE 1286 SYNTAX SnaResourceName 1287 MAX-ACCESS read-only 1288 STATUS current 1289 DESCRIPTION 1290 "The local name of the secondary LU (SLU)." 1291 ::= { tn3270eSnaMapEntry 2 } 1293 tn3270eClientResMapTable OBJECT-TYPE 1294 SYNTAX SEQUENCE OF Tn3270eClientResMapEntry 1295 MAX-ACCESS not-accessible 1296 STATUS current 1297 DESCRIPTION 1298 "This table defines resource pool to client group mappings. 1300 White TN3270E Management Information Base (TN3270E-MIB) 13 September 1997 1302 Since both the resource pool name and client group name 1303 are included in the index clause of this table, multiple 1304 resource pools can be assigned to the same client group. This 1305 enables use of multiple resource pools for use in client to 1306 resource mapping. Assigning multiple client Groups to the 1307 same resource pool is also allowed, but is not the primary 1308 purpose for how the indexing is structured. 1310 Assignment of a resource pool to client group can be 1311 restricted based on TCP port. An index value of 0 for 1312 tn3270eClientResMapClientPort disables restriction of 1313 resource assignment based on client target port selection." 1314 ::= { tn3270eObjects 7 } 1316 tn3270eClientResMapEntry OBJECT-TYPE 1317 SYNTAX Tn3270eClientResMapEntry 1318 MAX-ACCESS not-accessible 1319 STATUS current 1320 DESCRIPTION 1321 "Definition of a single resource pool to client group 1322 mapping." 1323 INDEX { tn3270eSrvrConfIndex, 1324 tn3270eClientResMapPoolName, 1325 tn3270eClientResMapClientGroupName, 1326 tn3270eClientResMapClientPort } 1327 ::= { tn3270eClientResMapTable 1 } 1329 Tn3270eClientResMapEntry ::= SEQUENCE { 1330 tn3270eClientResMapPoolName Utf8String, 1331 tn3270eClientResMapClientGroupName Utf8String, 1332 tn3270eClientResMapClientPort Unsigned32, 1333 tn3270eClientResMapRowStatus RowStatus } 1335 tn3270eClientResMapPoolName OBJECT-TYPE 1336 SYNTAX Utf8String (SIZE(1..24)) 1337 MAX-ACCESS not-accessible 1338 STATUS current 1339 DESCRIPTION 1340 "The name of a resource pool." 1341 ::= { tn3270eClientResMapEntry 1 } 1343 tn3270eClientResMapClientGroupName OBJECT-TYPE 1344 SYNTAX Utf8String (SIZE(1..24)) 1345 MAX-ACCESS not-accessible 1346 STATUS current 1347 DESCRIPTION 1348 "The name of the client group that is mapped to a 1349 resource pool." 1351 White TN3270E Management Information Base (TN3270E-MIB) 13 September 1997 1353 ::= { tn3270eClientResMapEntry 2 } 1355 tn3270eClientResMapClientPort OBJECT-TYPE 1356 SYNTAX Unsigned32 (0..65535) 1357 MAX-ACCESS not-accessible 1358 STATUS current 1359 DESCRIPTION 1360 "The port to restrict a resource pool to a client group 1361 mapping. A value of 0 for this objects implies that 1362 the mapping is not restricted." 1363 ::= { tn3270eClientResMapEntry 3 } 1365 tn3270eClientResMapRowStatus OBJECT-TYPE 1366 SYNTAX RowStatus 1367 MAX-ACCESS read-create 1368 STATUS current 1369 DESCRIPTION 1370 "This object allows entries to be created and deleted in the 1371 tn3270eClientResMapTable. 1373 An entry in this table is deleted by setting this object 1374 to destroy(6)." 1375 REFERENCE 1376 "RFC 1903, 'Textual Conventions for version 2 of the Simple 1377 Network Management Protocol (SNMPv2).'" 1378 ::= { tn3270eClientResMapEntry 4 } 1380 tn3270eResMapTable OBJECT-TYPE 1381 SYNTAX SEQUENCE OF Tn3270eResMapEntry 1382 MAX-ACCESS not-accessible 1383 STATUS current 1384 DESCRIPTION 1385 "This table defines the actual mapping of a resource to 1386 a client Address." 1387 ::= { tn3270eObjects 8 } 1389 tn3270eResMapEntry OBJECT-TYPE 1390 SYNTAX Tn3270eResMapEntry 1391 MAX-ACCESS not-accessible 1392 STATUS current 1393 DESCRIPTION 1394 "Definition of the mapping of a Resource Element to 1395 a client Address." 1396 INDEX { tn3270eSrvrConfIndex, 1397 tn3270eResMapElementName } 1398 ::= { tn3270eResMapTable 1 } 1400 Tn3270eResMapEntry ::= SEQUENCE { 1402 White TN3270E Management Information Base (TN3270E-MIB) 13 September 1997 1404 tn3270eResMapElementName SnaResourceName, 1405 tn3270eResMapAddrType Tn3270eAddrType, 1406 tn3270eResMapAddress Tn3270eTAddress, 1407 tn3270eResMapPort Unsigned32, 1408 tn3270eResMapElementType Tn3270ResourceType } 1410 tn3270eResMapElementName OBJECT-TYPE 1411 SYNTAX SnaResourceName 1412 MAX-ACCESS not-accessible 1413 STATUS current 1414 DESCRIPTION 1415 "The name of a resource element." 1416 ::= { tn3270eResMapEntry 1 } 1418 tn3270eResMapAddrType OBJECT-TYPE 1419 SYNTAX Tn3270eAddrType 1420 MAX-ACCESS read-only 1421 STATUS current 1422 DESCRIPTION 1423 "Indicates the type of the client Address represented in 1424 tn3270eResMapAddress." 1425 ::= { tn3270eResMapEntry 2 } 1427 tn3270eResMapAddress OBJECT-TYPE 1428 SYNTAX Tn3270eTAddress 1429 MAX-ACCESS read-only 1430 STATUS current 1431 DESCRIPTION 1432 "A client address." 1433 ::= { tn3270eResMapEntry 3 } 1435 tn3270eResMapPort OBJECT-TYPE 1436 SYNTAX Unsigned32 (0..65535) 1437 MAX-ACCESS read-only 1438 STATUS current 1439 DESCRIPTION 1440 "A client Port." 1441 ::= { tn3270eResMapEntry 4 } 1443 tn3270eResMapElementType OBJECT-TYPE 1444 SYNTAX Tn3270ResourceType 1445 MAX-ACCESS read-only 1446 STATUS current 1447 DESCRIPTION 1448 "The type of the associating resource element." 1449 ::= { tn3270eResMapEntry 5 } 1451 -- Define the set of objects to add to the Tcp Connection Table 1453 White TN3270E Management Information Base (TN3270E-MIB) 13 September 1997 1455 tn3270eTcpConnTable OBJECT-TYPE 1456 SYNTAX SEQUENCE OF Tn3270eTcpConnEntry 1457 MAX-ACCESS not-accessible 1458 STATUS current 1459 DESCRIPTION 1460 "Provides a table that has an entry for each TN3270(E) 1461 client connection that is active at a TN3270E server. 1462 The table was originally modeled after the tcpConnTable 1463 but was changed to support different client Address types 1464 and to be indexed first by the remote address and port 1465 as oppose to local address and port. This is to enable 1466 use of a SNMP GET-NEXT operation using only the remote 1467 address and port." 1468 ::= { tn3270eObjects 9 } 1470 tn3270eTcpConnEntry OBJECT-TYPE 1471 SYNTAX Tn3270eTcpConnEntry 1472 MAX-ACCESS not-accessible 1473 STATUS current 1474 DESCRIPTION 1475 "Provides in formation about a single TN3270/TN3270E 1476 session. Note: a tn3270eSrvrConfIndex is not needed 1477 in this table since the combination of both remote 1478 local addresses and ports is sufficient to 1479 guarantee uniqueness between TN3270E Servers on the 1480 same or actually different hosts." 1481 INDEX { tn3270eTcpConnRemAddress, 1482 tn3270eTcpConnRemPort, 1483 tn3270eTcpConnRemAddrType, 1484 tn3270eTcpConnLocalAddress, 1485 tn3270eTcpConnLocalPort, 1486 tn3270eTcpConnLocalAddrType 1487 } 1488 ::= { tn3270eTcpConnTable 1 } 1490 Tn3270eTcpConnEntry ::= 1491 SEQUENCE 1492 { 1493 tn3270eTcpConnRemAddress Tn3270eTAddress, 1494 tn3270eTcpConnRemPort Unsigned32, 1495 tn3270eTcpConnRemAddrType Tn3270eAddrType, 1496 tn3270eTcpConnLocalAddress Tn3270eTAddress, 1497 tn3270eTcpConnLocalPort Unsigned32, 1498 tn3270eTcpConnLocalAddrType Tn3270eAddrType, 1499 tn3270eTcpConnLastActivity TimeTicks, 1500 tn3270eTcpConnBytesIn Counter32, 1501 tn3270eTcpConnBytesOut Counter32, 1502 tn3270eTcpConnResourceElement SnaResourceName, 1504 White TN3270E Management Information Base (TN3270E-MIB) 13 September 1997 1506 tn3270eTcpConnResourceType Tn3270ResourceType, 1507 tn3270eTcpConnDeviceType Tn3270DeviceTypes, 1508 tn3270eTcpConnFunctions Tn3270Functions 1509 } 1511 tn3270eTcpConnRemAddress OBJECT-TYPE 1512 SYNTAX Tn3270eTAddress 1513 MAX-ACCESS not-accessible 1514 STATUS current 1515 DESCRIPTION 1516 "The remote address associated with a TN3270E client. 1517 tn3270eTcpConnRemAddrType indicates the address type 1518 (ipv4 or ipv6 for example)." 1519 ::= { tn3270eTcpConnEntry 1 } 1521 tn3270eTcpConnRemPort OBJECT-TYPE 1522 SYNTAX Unsigned32 (0..65535) 1523 MAX-ACCESS not-accessible 1524 STATUS current 1525 DESCRIPTION 1526 "The remote port associated with a TN3270E client." 1527 ::= { tn3270eTcpConnEntry 2 } 1529 tn3270eTcpConnRemAddrType OBJECT-TYPE 1530 SYNTAX Tn3270eAddrType 1531 MAX-ACCESS not-accessible 1532 STATUS current 1533 DESCRIPTION 1534 "Indicates whether the index element tcpConnRemAddress 1535 is a ipv4(1) or a ipv6(2) address." 1536 ::= { tn3270eTcpConnEntry 3 } 1538 tn3270eTcpConnLocalAddress OBJECT-TYPE 1539 SYNTAX Tn3270eTAddress 1540 MAX-ACCESS not-accessible 1541 STATUS current 1542 DESCRIPTION 1543 "The local address associated with a TN3270E client. 1544 tn3270eTcpConnRemAddrType indicates the address type 1545 (ipv4 or ipv6 for example)." 1546 ::= { tn3270eTcpConnEntry 4 } 1548 tn3270eTcpConnLocalPort OBJECT-TYPE 1549 SYNTAX Unsigned32 (0..65535) 1550 MAX-ACCESS not-accessible 1551 STATUS current 1552 DESCRIPTION 1553 "The remote port associated with a TN3270E client." 1555 White TN3270E Management Information Base (TN3270E-MIB) 13 September 1997 1557 ::= { tn3270eTcpConnEntry 5 } 1559 tn3270eTcpConnLocalAddrType OBJECT-TYPE 1560 SYNTAX Tn3270eAddrType 1561 MAX-ACCESS not-accessible 1562 STATUS current 1563 DESCRIPTION 1564 "Indicates whether the index element tcpConnLocalAddress 1565 is a ipv4(1) or a ipv6(2) address." 1566 ::= { tn3270eTcpConnEntry 6 } 1568 tn3270eTcpConnLastActivity OBJECT-TYPE 1569 SYNTAX TimeTicks 1570 MAX-ACCESS read-only 1571 STATUS current 1572 DESCRIPTION 1573 "The number of 100ths of seconds since any data was 1574 transferred for the associating TCP Connection." 1575 DEFVAL { 0 } 1576 ::= { tn3270eTcpConnEntry 7 } 1578 tn3270eTcpConnBytesIn OBJECT-TYPE 1579 SYNTAX Counter32 1580 UNITS "octets" 1581 MAX-ACCESS read-only 1582 STATUS current 1583 DESCRIPTION 1584 "The number of bytes received by the server from TCP 1585 for this connection." 1586 ::= { tn3270eTcpConnEntry 8 } 1588 tn3270eTcpConnBytesOut OBJECT-TYPE 1589 SYNTAX Counter32 1590 UNITS "octets" 1591 MAX-ACCESS read-only 1592 STATUS current 1593 DESCRIPTION 1594 "The number of bytes sent to TCP for this connection." 1595 ::= { tn3270eTcpConnEntry 9 } 1597 tn3270eTcpConnResourceElement OBJECT-TYPE 1598 SYNTAX SnaResourceName 1599 MAX-ACCESS read-only 1600 STATUS current 1601 DESCRIPTION 1602 "LU/Print secondary name for connecting an IP client 1603 into an SNA network." 1604 ::= { tn3270eTcpConnEntry 10 } 1606 White TN3270E Management Information Base (TN3270E-MIB) 13 September 1997 1608 tn3270eTcpConnResourceType OBJECT-TYPE 1609 SYNTAX Tn3270ResourceType 1610 MAX-ACCESS read-only 1611 STATUS current 1612 DESCRIPTION 1613 "Indicates the type of resource identified by 1614 tn3270eTcpConnResourceElement." 1615 ::= { tn3270eTcpConnEntry 11 } 1617 tn3270eTcpConnDeviceType OBJECT-TYPE 1618 SYNTAX Tn3270DeviceTypes 1619 MAX-ACCESS read-only 1620 STATUS current 1621 DESCRIPTION 1622 "Indicates the device type if negotiated with client. 1623 This object is also known as logmode." 1624 ::= { tn3270eTcpConnEntry 12 } 1626 tn3270eTcpConnFunctions OBJECT-TYPE 1627 SYNTAX Tn3270Functions 1628 MAX-ACCESS read-only 1629 STATUS current 1630 DESCRIPTION 1631 "This object will indicates which of the TN3270 and TN3270E 1632 functions that are supported by the server was negioted 1633 with a client. Refer to tn3270eSrvrFunctionsSupported." 1634 ::= { tn3270eTcpConnEntry 13 } 1636 -- Conformance Definitions 1638 tn3270eGroups OBJECT IDENTIFIER ::= { tn3270eConformance 1 } 1639 tn3270eCompliances OBJECT IDENTIFIER ::= { tn3270eConformance 2 } 1641 -- compliance statements 1643 tn3270eCompliance MODULE-COMPLIANCE 1644 STATUS current 1645 DESCRIPTION 1646 "The compliance statement for agents that support the 1647 TN3270E-MIB." 1648 MODULE -- this module 1649 MANDATORY-GROUPS { tn3270eBasicGroup, 1650 tn3270eSessionGroup 1651 } 1652 GROUP tn3270eResMapGroup 1653 DESCRIPTION 1654 "This group is optional and provides a method of 1656 White TN3270E Management Information Base (TN3270E-MIB) 13 September 1997 1658 performing tn3270eClientGroup to tn3270eResPool 1659 mapping." 1660 OBJECT tn3270eSrvrConfActivityCheck 1661 MIN-ACCESS read-only 1662 DESCRIPTION 1663 "The agent is not required to support a set to this 1664 object if the associating TN3270E server doesn't 1665 support either TIMEMARK or NOP processing. In 1666 this case an agent should return noCheck on 1667 retrieval." 1668 OBJECT tn3270eSrvrConfActivityTimeout 1669 MIN-ACCESS read-only 1670 DESCRIPTION 1671 "The agent is not required to support a set to this 1672 object if the functions enabled by 1673 tn3270eSrvrConfActivityCheck are not supported. 1674 An agent in this case should return a value of 0." 1675 OBJECT tn3270eSrvrConfActivityInterval 1676 MIN-ACCESS read-only 1677 DESCRIPTION 1678 "The agent is not required to support a set to this 1679 object if the functions enabled by 1680 tn3270eSrvrConfActivityCheck are not supported. 1681 An agent in this case should return a value of 0." 1682 OBJECT tn3270eSrvrConfAdminStatus 1683 DESCRIPTION 1684 "A TN3270E server is not required to support a 1685 stopImmediate state transition." 1686 ::= { tn3270eCompliances 1 } 1688 -- units of conformance 1690 tn3270eBasicGroup OBJECT-GROUP 1691 OBJECTS { 1692 tn3270eSrvrConfInactivityTimeout, 1693 tn3270eSrvrConfActivityCheck, 1694 tn3270eSrvrConfActivityTimeout, 1695 tn3270eSrvrConfActivityInterval, 1696 tn3270eSrvrFunctionsSupported, 1697 tn3270eSrvrConfAdminStatus, 1698 tn3270eSrvrConfOperStatus, 1699 tn3270eSrvrConfSessionTermState, 1700 tn3270eSrvrConfSrvrType, 1701 tn3270eSrvrConfContact, 1702 tn3270eSrvrConfRowStatus, 1703 tn3270eSrvrPortRowStatus, 1704 tn3270eSrvrStatsUpTime, 1705 tn3270eSrvrStatsMaxLus, 1707 White TN3270E Management Information Base (TN3270E-MIB) 13 September 1997 1709 tn3270eSrvrStatsLusInUse, 1710 tn3270eSrvrStatsSpareLus, 1711 tn3270eSrvrStatsMaxPtrs, 1712 tn3270eSrvrStatsPtrsInUse, 1713 tn3270eSrvrStatsSparePtrs, 1714 tn3270eSrvrStatsConnectsIn, 1715 tn3270eSrvrStatsConnRejects, 1716 tn3270eSrvrStatsDisconnects, 1717 tn3270eSrvrStatsOctetsIn, 1718 tn3270eSrvrStatsOctetsInLow, 1719 tn3270eSrvrStatsOctetsOut, 1720 tn3270eSrvrStatsOctetsOutLow, 1721 tn3270eClientGroupSubnetMask, 1722 tn3270eClientGroupPfxLength, 1723 tn3270eClientGroupRowStatus, 1724 tn3270eSnaMapLocalName 1725 } 1726 STATUS current 1727 DESCRIPTION 1728 "This group is mandatory for all hosts supporting the 1729 TN3270E-MIB." 1730 ::= { tn3270eGroups 1 } 1732 tn3270eSessionGroup OBJECT-GROUP 1733 OBJECTS { 1734 tn3270eResMapAddrType, 1735 tn3270eResMapAddress, 1736 tn3270eResMapPort, 1737 tn3270eResMapElementType, 1738 tn3270eTcpConnLastActivity, 1739 tn3270eTcpConnBytesIn, 1740 tn3270eTcpConnBytesOut, 1741 tn3270eTcpConnResourceElement, 1742 tn3270eTcpConnResourceType, 1743 tn3270eTcpConnDeviceType, 1744 tn3270eTcpConnFunctions 1745 } 1746 STATUS current 1747 DESCRIPTION 1748 "This group is mandatory for all hosts supporting the 1749 TN3270E-MIB." 1750 ::= { tn3270eGroups 2 } 1752 tn3270eResMapGroup OBJECT-GROUP 1753 OBJECTS { 1754 tn3270eResPoolElementType, 1755 tn3270eResPoolRowStatus, 1756 tn3270eClientResMapRowStatus 1758 White TN3270E Management Information Base (TN3270E-MIB) 13 September 1997 1760 } 1761 STATUS current 1762 DESCRIPTION 1763 "This group is optional for all hosts supporting the 1764 TN3270E-MIB." 1765 ::= { tn3270eGroups 3 } END 1767 5. Security Considerations 1769 Certain management information defined in this MIB may be considered 1770 sensitive in some network environments. Therefore, authentication of 1771 received SNMP requests and controlled access to management information 1772 should be employed in such environments. The method for this 1773 authentication is a function of the SNMP Administrative Framework, and 1774 has not been expanded by this MIB. 1776 Several objects in this MIB allow write access or provide for remote 1777 creation. Allowing this support in a non-secure environment can have a 1778 negative effect on network operations. It is recommended that 1779 implementers seriously consider whether set operations should be 1780 allowed without providing, at a minimum, authentication of request 1781 origin. It it recommended that without such support that the following 1782 objects be implemented as read-only: 1784 o tn3270eSrvrConfInactivityTimout 1785 o tn3270eSrvrConfActivityCheck 1786 o tn3270eSrvrConfActivityTimeout 1787 o tn3270eSrvrConfActivityInterval 1788 o tn3270eSrvrConfAdminStatus 1789 o tn3270eSrvrConfSessionTermState 1790 o tn3270eSrvrConfContact 1791 o tn3270eClientGroupSubnetMask 1792 o tn3270eResPoolElementType 1794 The following objects should either be implemented as read-only or not 1795 implemented when security is an issue as previously discussed: 1797 o tn3270eSrvrConfRowStatus 1798 o tn3270eSrvrPortRowStatus 1799 o tn3270eClientGroupRowStatus 1800 o tn3270eResPoolRowStatus 1801 o tn3270eResMapRowStatus 1803 6. Acknowledgments 1805 This document is a product of the TN3270E Working Group. 1807 White TN3270E Management Information Base (TN3270E-MIB) 13 September 1997 1809 7. References 1811 [1] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and 1812 Waldbusser S., "Structure of Management Information for version 2 1813 of the Simple Network Management Protocol (SNMPv2)", RFC 1902, 1814 January 1996. 1816 [2] Network Working Group, Postel, J., and Reynolds, J., "Telnet 1817 Protocol Specification", RFC 854, May 1983. 1819 [3] Network Working Group, Postel, J., and Reynolds, J., "Telnet Timing 1820 Mark Option", RFC 860, May 1983. 1822 [4] Network Working Group and Rekhter J., "Telnet 3270 Regime Option", 1823 RFC 1041, January 1988. 1825 [5] McCloghrie, K., and M. Rose, Editors, "Management Information Base 1826 for Network Management of TCP/IP-based internets: MIB-II", STD 17, 1827 RFC 1213, Hughes LAN Systems, Performance Systems International, 1828 March 1991. 1830 [6] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. 1831 Waldbusser, "Textual Conventions for version 2 of the Simple 1832 Network Management Protocol (SNMPv2)", RFC 1903, January 1996. 1834 [7] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. 1835 Waldbusser, "Protocol Operations for version 2 of the Simple 1836 Network Management Protocol (SNMPv2)", RFC 1905, January 1996. 1838 [8] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. 1839 Waldbusser, "Conformance Statements for version 2 of the Simple 1840 Network Management Protocol (SNMPv2)", RFC 1904, January 1996. 1842 [9] Case, J., M. Fedor, M. Schoffstall, J. Davin, "Simple Network 1843 Management Protocol", RFC 1157, SNMP Research, Performance Systems 1844 International, MIT Laboratory for Computer Science, May 1990. 1846 [10] IETF SNMPv2 Working Group and McCloghrie, K., "TCP-MIB 1848 White TN3270E Management Information Base (TN3270E-MIB) 13 September 1997 1850 Definitions", November 1994. 1852 [11] Hinden, R., Deering, S., "IP Version 6 Addressing Architecture", 1853 , July 16, 1997 1855 [12] Krupczak, Cheryl, Saperia, Jonathan, "Definitions of System-Level 1856 Managed Objects for Applications", April 15, 1997. 1858 8. Authors' Address 1860 Kenneth D. White 1861 Dept. G80/Bldg 503 1862 IBM Corporation 1863 Research Triangle Park, NC 27709, USA 1864 E-mail: kennethw@vnet.ibm.com