idnits 2.17.1 draft-ietf-tn3270e-tn3270-mib-07.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. 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 53 longer pages, the longest (page 2) being 59 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There is 1 instance of too long lines in the document, the longest one being 2 characters in excess of 72. ** The abstract seems to contain references ([15], [3], [12], [13], [14]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 1103 has weird spacing: '...ddrType unkn...' == Line 1104 has weird spacing: '...Address zer...' == Line 1110 has weird spacing: '...ddrType unkn...' == Line 1111 has weird spacing: '...Address zer...' == Line 1117 has weird spacing: '...ddrType vali...' == (3 more instances...) == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. -- 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 (May 1998) is 9472 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: '17' is defined on line 2572, but no explicit reference was found in the text == Unused Reference: '19' is defined on line 2578, but no explicit reference was found in the text ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. '1') ** Obsolete normative reference: RFC 1902 (ref. '3') (Obsoleted by RFC 2578) ** Obsolete normative reference: RFC 1903 (ref. '4') (Obsoleted by RFC 2579) ** Obsolete normative reference: RFC 1904 (ref. '5') (Obsoleted by RFC 2580) ** Obsolete normative reference: RFC 1905 (ref. '6') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2271 (ref. '7') (Obsoleted by RFC 2571) ** Obsolete normative reference: RFC 2272 (ref. '8') (Obsoleted by RFC 2572) ** Obsolete normative reference: RFC 2273 (ref. '9') (Obsoleted by RFC 2573) ** Obsolete normative reference: RFC 2274 (ref. '10') (Obsoleted by RFC 2574) ** Obsolete normative reference: RFC 2275 (ref. '11') (Obsoleted by RFC 2575) ** Downref: Normative reference to an Historic RFC: RFC 1041 (ref. '14') ** Obsolete normative reference: RFC 1647 (ref. '15') (Obsoleted by RFC 2355) ** Obsolete normative reference: RFC 2012 (ref. '16') (Obsoleted by RFC 4022) ** Obsolete normative reference: RFC 2028 (ref. '17') (Obsoleted by RFC 9281) -- Possible downref: Non-RFC (?) normative reference: ref. '19' Summary: 23 errors (**), 0 flaws (~~), 12 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 TN3270E Working Group Kenneth White 2 INTERNET DRAFT: IBM Corp. 3 Expiration Date: November, 1998 Robert Moore 4 IBM Corp. 5 May 1998 7 Base Definitions of Managed Objects for 8 TN3270E Using SMIv2 9 11 Status of this Memo 13 This document is an Internet Draft. Internet Drafts are working 14 documents of the Internet Engineering Task Force (IETF), its Areas, and 15 its Working Groups. Note that other groups may also distribute working 16 documents as Internet Drafts. 18 Internet Drafts are draft documents valid for a maximum of six months. 19 Internet Drafts may be updated, replaced, or obsoleted by other 20 documents at any time. It is not appropriate to use Internet Drafts as 21 reference material or to cite them other than as a "working draft" or 22 "work in progress." 24 Please check the I-D abstract listing contained in each Internet Draft 25 directory to learn the current status of this or any Internet Draft. 26 Distribution of this document is unlimited. 28 Copyright Notice 30 Copyright (C) The Internet Society (1998). All Rights Reserved. 32 Abstract 34 This memo defines a Management Information Base (MIB) for configuring 35 and managing TN3270E servers. TN3270E, defined by RFC 1647 [15], refers 36 to the enhancements made to the Telnet 3270 (TN3270) terminal emulation 37 practices. Refer to RFC 1041 [14], RFC 854 [12], and RFC 860 [13] for a 38 sample of what is meant by TN3270 practices. 40 The MIB defined by this memo provides generic support for both host and 41 gateway TN3270E server implementations. A TN3270E server connects a 42 Telnet client performing 3270 emulation to a target SNA host over both a 43 client-side network (client to TN3270E server) and an SNA Network 44 (TN3270E server to target SNA host). The client-side network is 45 typically TCP/IP, but it need not be. 47 A host TN3270E server refers to an implementation where the TN3270E 48 server is collocated with the Systems Network Architecture (SNA) System 49 Services Control Point (SSCP) for the dependent Secondary Logical Units 50 (SLUs) that the server makes available to its clients for connecting 51 into a SNA network. A gateway TN3270E server resides on an SNA node 52 other than an SSCP, either an SNA type 2.0 node, a 53 boundary-function-attached type 2.1 node, or an APPN node acting in the 54 role of a Dependent LU Requester (DLUR). Host and gateway TN3270E 55 server implementations typically differ greatly as to their internal 56 implementation and system definition (SYSDEF) methods. 58 It is the intent that the MIB defined herein be extended by subsequent 59 memos. For example, one such extension enables collection of TN3270E 60 response time data. The specification of this MIB uses the Structure of 61 Management Information (SMI) for Version 2 of the Simple Network 62 Management Protocol (refer to RFC1902 [3]). 64 Table of Contents 66 1.0 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 68 2.0 The SNMP Network Management Framework . . . . . . . . . . . . 3 70 3.0 Structure of the MIB . . . . . . . . . . . . . . . . . . . . . 3 71 3.1 TN3270E Server Control . . . . . . . . . . . . . . . . . . . . 4 72 3.1.1 tn3270eSrvrConfTable . . . . . . . . . . . . . . . . . . . 5 73 3.1.2 tn3270eSrvrPortTable . . . . . . . . . . . . . . . . . . . 6 74 3.1.3 tn3270eSrvrStatsTable . . . . . . . . . . . . . . . . . . 6 75 3.2 TN3270E Server Resource Configuration . . . . . . . . . . . . 6 76 3.3 Resource Name / Client Address Mappings . . . . . . . . . . . 7 77 3.3.1 tn3270eSnaMapTable . . . . . . . . . . . . . . . . . . . . 7 78 3.3.2 tn3270eResMapTable . . . . . . . . . . . . . . . . . . . . 7 79 3.3.3 tn3270eTcpConnTable . . . . . . . . . . . . . . . . . . . 8 80 3.4 Advisory Spin Lock Usage . . . . . . . . . . . . . . . . . . . 8 81 3.5 Row Persistence . . . . . . . . . . . . . . . . . . . . . . . 8 82 3.6 IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9 84 4.0 Definitions . . . . . . . . . . . . . . . . . . . . . . . . . 9 86 5.0 Security Considerations . . . . . . . . . . . . . . . . . . . 45 88 6.0 Intellectual Property . . . . . . . . . . . . . . . . . . . . 46 90 7.0 Acknowledgments . . . . . . . . . . . . . . . . . . . . . . . 47 92 8.0 References . . . . . . . . . . . . . . . . . . . . . . . . . . 47 94 9.0 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . 48 96 10.0 Full Copyright Statement . . . . . . . . . . . . . . . . . . 48 97 1.0 Introduction 99 This document is a product of the TN3270E Working Group. Its purpose is 100 to define a MIB module for support by a TCP/IP implementation for 101 configuration and management of TN3270E servers. 103 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 104 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 105 document are to be interpreted as described in RFC 2119, reference [18]. 107 2.0 The SNMP Network Management Framework 109 The SNMP Network Management Framework presently consists of six major 110 components. They are: 112 o the overall architecture, described in RFC 2271 [7]. 114 o the SMI, described in RFC 1902 [3], - the mechanisms used for 115 describing and naming objects for the purpose of management. 117 o the MIB-II, STD 17, RFC 1213 [2], - the core set of managed objects 118 for the Internet suite of protocols. 120 o the protocol, RFC 1157 [1] and/or RFC 1905 [6] and/or RFC 2272 [8] 121 -- the protocol for accessing managed information. 123 o the user-based security model defined in RFC 2274 [10]. 125 o the view-based access control model defined in RFC 2275 [11]. 127 Textual conventions are defined in RFC 1903 [4], and conformance 128 statements are defined in RFC 1904 [5]. Common applications are defined 129 in RFC 2273 [9]. 131 The Framework permits new objects to be defined for the purpose of 132 experimentation and evaluation. 134 This memo specifies a MIB module that is compliant to the SMIv2. A MIB 135 conforming to the SMIv1 can be produced through the appropriate 136 translation. 138 3.0 Structure of the MIB 140 The TN3270E-MIB is split into the following components: 142 o TN3270E Server Control 143 o TN3270E Server Resource Configuration 144 o Resource/Client Address Mappings 146 There are three additional sections to address: 148 o Advisory Spin Lock Usage 149 o Row Persistence 150 o IANA Considerations 152 The TN3270E-MIB is defined primarily for TN3270E servers. This memo 153 does not explicitly address use of the MIB by TN3270 servers that do not 154 support the TN3270E protocol. Even though a significant number of the 155 objects in the MIB do apply in the TN3270-only case, the case was not 156 addressed, since it is unlikely that a TN3270-only server would 157 implement this MIB. 159 The SYSAPPL-MIB, reference [20], contains the Utf8String textual 160 convention (TC) that the TN3270E-MIB imports. This TC, which is used 161 for some MIB objects containing textual information, enables 162 internationalization of text strings, whereas the DisplayString TC does 163 not. The SNMP-FRAMEWORK-MIB, reference [7], contains the 164 SnmpAdminString TC that the TN3270E-MIB also imports. Like the 165 Utf8String TC, this TC also enables internationalization of text 166 strings; in addition, it provides some guidelines on the length and 167 content of the strings. 169 It is important to note that implementation of the SYSAPPL-MIB is not 170 actually a prerequisite for implementing the TN3270E-MIB. On the other 171 hand, implementation of the TN3270E-MIB does not preclude implementing 172 the SYSAPPL-MIB as well. When both MIBs are implemented, the primary 173 index into most of the TN3270E-MIB tables, tn3270eSrvrConfIndex, SHOULD 174 equal one of the SYSAPPL-MIB's sysApplElmtRunIndex values. In this case 175 the entry in the sysApplElmtRunTable provides additional information on 176 a TN3270E server. 178 The MIB defined by this memo supports use of both IPv4 and IPv6 179 addressing. Two textual conventions, IANATn3270eAddrType and 180 Tn3270eTAddress, are defined for this purpose. IANATn3270eTAddress is 181 essentially equivalent to the TAddress TC, defined by RFC 1903. The 182 difference between the two is that IANATn3270eTAddress allows a 183 zero-length octet string, while TAddress doesn't. It is important that 184 IANATn3270eTAddress allow for the absence of an address, because some 185 objects with this syntax are used as table indexes, and have special 186 meanings when they contain zero-length strings. 188 The IANATn3270eAddrType textual convention is used rather than the 189 TDomain TC (defined by RFC 1903) for identifying the contents of a 190 tn3270eTAddress object. TDomain uses an OID to characterize the 191 contents of an associated TAddress object. IANATn3270eAddrType was 192 chosen over TDomain because, with a SYNTAX of Unsigned32 (enumeration 193 type), it is much simpler to use as a component in an instance 194 identifier. It was placed in the IANA-administered module to allow for 195 the addition of values to cover cases (such as proxy servers) not 196 covered by the TN3270E-MIB itself. 198 3.1 TN3270E Server Control 200 This group of objects provides for TN3270E server configuration and 201 control. It consists of three tables: 203 o tn3270eSrvrConfTable 204 o tn3270eSrvrPortTable 205 o tn3270eSrvrStatsTable 207 The tn3270eSrvrConfTable is the primary table within the entire 208 TN3270E-MIB. As section 3.1.1 indicates, each TN3270E server is 209 represented by an entry in this table, indexed by tn3270eSrvrConfIndex. 210 Most of the other tables defined by the TN3270E-MIB have 211 tn3270eSrvrConfIndex as their primary index. Entries in these tables 212 MUST NOT exist for a TN3270E server when it does not have a 213 tn3270eSrvrConfigEntry. 215 3.1.1 tn3270eSrvrConfTable 217 The tn3270eSrvrConfTable contains a set of objects primarily used for 218 configuring and managing TN3270E servers. As with most of the other 219 tables in the TN3270E-MIB, this table is indexed by an unsigned integer, 220 tn3270eSrvrConfIndex. This primary index element enables support of 221 multiple TN3270E servers by a single SNMP agent. Within the set of MIB 222 objects returned by one SNMP agent, tn3270eSrvrConfIndex values MUST be 223 unique, and need not be contiguous. 225 The tn3270eSrvrConfInactivityTimer object defines the inactivity period 226 for user traffic on TN3270 and TN3270E sessions. 228 The four objects: 230 o tn3270eSrvrConfActivityCheck 231 o tn3270eSrvrConfTmNopInterval 232 o tn3270eSrvrConfTmNopInactTime 233 o tn3270eSrvrConfTmTimeout 235 define the parameters for performing the "Telnet Timing Mark Option" as 236 defined by RFC 860 [13]. The object tn3270eSrvrConfActivityCheck allows 237 a Management Station to select either a NOP command or a TIMING-MARK 238 command. Sending a NOP command results in less overhead then a 239 TIMING-MARK command, since a client doesn't send a reply. 241 The objects tn3270eSrvrConfAdminStatus and tn3270eSrvrConfOperStatus 242 enable remote starting and stopping of a TN3270E server, and report the 243 current state of the server. The object 244 tn3270eSrvrConfFunctionsSupported indicates which of the TN3270 and 245 TN3270E options a server supports. The object 246 tn3270eSrvrConfSessionTermState defines as a TN3270E server-wide option 247 what SHOULD occur when the SNA portion of a TN3270 or TN3270E session 248 terminates with respect to the associated TCP connection. The object 249 tn3270eSrvrConfSrvrType indicates whether the TN3270E server represented 250 by a tn3270eSrvrConfEntry is a host or a gateway server. The object 251 tn3270eSrvrConfContact provides a scratch pad area for a TN3270E server 252 administrator to store information for later retrieval. The object 253 tn3270eSrvrConfLastActTime reports the DateAndTime when the server was 254 most recently activated. The special value of all '00'Hs indicates that 255 the server has never been active. 257 The object tn3270eSrvrConfRowStatus provides the capability to perform 258 row creation and deletion operations on this table. 260 3.1.2 tn3270eSrvrPortTable 262 The tn3270eSrvrPortTable represents the local TCP ports associated with 263 a TN3270E server. This information is important because some TN3270E 264 server implementations support usage of multiple local ports. A 265 tn3270eSrvrPortEntry is indexed by: 267 o tn3270eSrvrConfIndex 268 o tn3270eSrvrConfPort 269 o tn3270eSrvrConfPortAddrType 270 o tn3270eSrvrConfPortAddress 272 Certain TN3270E server implementations restrict a local TCP port to a 273 particular local IP address, instead of allowing connections for any 274 local IP address to occur via the port. tn3270eSrvrConfPortAddrType and 275 tn3270eSrvrConfPortAddress allow this restriction to be represented in 276 the MIB. A TN3270E server that doesn't restrict connections over a port 277 to a local IP Address SHALL use the value unknown(0) for 278 tn3270eSrvrConfPortAddrType, and a zero-length octet string for 279 tn3270eSrvrConfPortAddress. 281 3.1.3 tn3270eSrvrStatsTable 283 The tn3270eSrvrStatsTable defines a series of objects that provide 284 general usage statistics for a TN3270E server. An entry can represent 285 the total activity for a server, or it can represent the activity 286 occurring at the server on either a port or a port-and-local-address 287 basis. 289 An implementation of this table MUST use only one of the three levels of 290 refinement that the indexing of this table supports for the entries 291 associated with a single TN3270E server. 293 The objects in this table reporting maximum, in-use, and spare LUs for 294 terminals and printers presuppose an implementation where terminal 295 resources and printer resources come from disjoint, dedicated pools. An 296 implementation where resources for the two types of LUs come from a 297 single shared pool should return the following values: 299 o maximum: maximum size of the shared pool 300 o in-use: number currently in use as this type of LU 301 o spare: maximum - (terminal in-use + printer in-use) 303 3.2 TN3270E Server Resource Configuration 305 The following three tables provide for configuration of resources at a 306 TN3270E server: 308 o tn3270eClientGroupTable 309 o tn3270eResPoolTable 310 o tn3270eClientResMapTable 312 tn3270eClientGroupTable and tn3270eResPoolTable enable implementations 313 to define groupings of both client addresses and resource pools for 314 mapping client addresses to resources. The tn3270eClientResMapTable 315 provides a mapping from a client group to a resource pool. 317 3.3 Resource Name / Client Address Mappings 319 The TN3270E-MIB contains three tables for mapping resource names to 320 client addresses, and client addresses to resource names: 322 o tn3270eSnaMapTable 323 o tn3270eResMapTable 324 o tn3270eTcpConnTable 326 3.3.1 tn3270eSnaMapTable 328 The tn3270eSnaMapTable is a read-only table that maps a secondary LU's 329 SNA network name to the name by which it is known locally at the TN3270E 330 server. For correlation with data from the SNA network, the name of the 331 associated primary LU also appears in a tn3270eSnaMapEntry. An entry in 332 this table is created when the Activate LU (ACTLU) request carrying the 333 SNA network name of the SLU is received from the SSCP. The entry is 334 deleted when the SLU is deactivated. 336 A TN3270E server provides a client with access to an SNA application by 337 associating a TCP connection from the client with an SNA secondary LU 338 (SLU) at the server. This SLU in turn has an SNA session with a primary 339 LU (PLU) running on an SNA host. This PLU represents the application 340 with which the client is communicating. The TN3270E-MIB includes two 341 tables for mapping back and forth among the SNA name identifying the 342 PLU, the SNA name identifying the SLU, and the TCP connection with the 343 client. 345 In order to understand how these name mappings work, it is necessary to 346 understand a subtlety involving the names of the SLUs at the TN3270E 347 server: these names are often different from the names by which the 348 SLUs are known in the rest of the SNA network. In the TN3270E-MIB, 349 these two types of SLU names are termed "local names" and "SSCP-supplied 350 names"; the latter term indicates that the name by which the SLU is 351 known in the SNA network comes to the TN3270E server from the SNA System 352 Services Control Point. 354 SSCPs don't always send SLU names down to secondary LUs; in some cases 355 this capability must be turned on. In the case of SLUs served by a 356 Dependent LU Requester (DLUR), an SSCP always sends SLU names to the 357 DLUR. It is necessary, however, to enable the DLUR's PU/LU Network Name 358 Forwarding function, so that it forwards the SLU names it receives from 359 the SSCP down to the PUs that it serves. 361 For SLUs associated with an SNA type 2.0 node (or with a 362 boundary-function-attached type 2.1 node) not served by a DLUR, 363 inclusion of SLU names on ACTLU must be enabled explicitly at the SSCP 364 via local configuration. 366 3.3.2 tn3270eResMapTable 367 The tn3270eResMapTable is a read-only table that maps a resource name to 368 a client's address. An entry in this table is created when a TCP 369 connection is received by a TN3270E server and mapped to a resource. 370 The entry is deleted when the resource-to-address association is no 371 longer valid. 373 3.3.3 tn3270eTcpConnTable 375 The TCP Connection Table is currently defined by RFC 2012 (Refer to 376 reference [16], TCP-MIB Definitions). It contains the following 377 objects: 379 o tcpConnState (INTEGER) 380 o tcpConnLocalAddress (IpAddress) 381 o tcpConnLocalPort (INTEGER) 382 o tcpConnRemAddress (IpAddress) 383 o tcpConnRemPort (INTEGER) 385 It is indexed by: tcpConnLocalAddress, tcpConnLocalPort, 386 tcpConnRemAddress, and tcpConnRemPort. 388 The tn3270eTcpConnTable contains objects for keeping a list of the 389 current set of TN3270 and TN3270E sessions at a TN3270E server. The 390 relationship between the tcpConnTable and the Tn3270eTcpConnTable is not 391 one-to-one, since the tn3270eTcpConnTable contains information 392 pertaining only to TN3270(E) sessions. 394 The tn3270eTcpConnTable has a different indexing structure from that of 395 the tcpConnTable. Instead of using IpAddress objects, Tn3270eTAddress 396 and IANATn3270eAddrType object pairs are used to specify client 397 addresses (both local and remote). This enables support of IPv6 398 addresses. In addition, the remote address pair precedes the local 399 address pair in the index clause, in order to enable a GET-NEXT 400 operation using only the remote address pair. 402 3.4 Advisory Spin Lock Usage 404 Within the TN3270E-MIB, tn3270eConfSpinLock is defined as an advisory 405 lock that allows cooperating TN3270E-MIB applications to coordinate 406 their use of the tn3270eSrvrConfTable, the tn3270eSrvrPortTable, the 407 tn3270eClientGroupTable, the tn3270eResPoolTable, and the 408 tn3270eClientResMapTable. When creating a new entry or altering an 409 existing entry in any of these tables, an application SHOULD make use of 410 tn3270eConfSpinLock to serialize application changes or additions. 411 Since this is an advisory lock, its use by management applications SHALL 412 NOT be enforced by agents. Agents MUST, however, implement the 413 tn3270eConfSpinLock object. 415 3.5 Row Persistence 417 The following tables enable remote creation of their entries by 418 including RowStatus objects: 420 o tn3270eSrvrConfTable 421 o tn3270eSrvrPortTable 422 o tn3270eClientGroupTable 423 o tn3270eResPoolTable 424 o tn3270eClientResMapTable 426 An implementation SHOULD NOT retain SNMP-created entries in these tables 427 across reIPLs (Initial Program Loads) of the corresponding TN3270E 428 server, since management applications need to see consistent behavior 429 with respect to the persistence of the table entries that they create. 431 It is expected that local, implementation-dependent configuration 432 information will be used to define the initial and persistent 433 configurations for TN3270E server usage. Thus it is not necessary to 434 enable persistence of table entries by adding StorageType (refer to RFC 435 1903 [4]) objects to these tables. 437 3.6 IANA Considerations 439 The tn3270eSrvrFunctionsSupported, tn3270eTcpConnFunctions, 440 tn3270eTcpConnClientIdFormat, and tn3270eTcpConnLogInfo objects, as well 441 as a number of objects identifying the types of various addresses, use 442 textual conventions imported from the IANATn3270eTC-MIB. The purpose of 443 defining these textual conventions in a separate MIB module is to allow 444 additional values to be defined without having to issue a new version of 445 this document. The Internet Assigned Number Authority (IANA) is 446 responsible for the assignment of all Internet numbers, including 447 various SNMP-related numbers; it will administer the values associated 448 with these textual conventions. 450 The rules for additions or changes to the IANATn3270eTC-MIB are outlined 451 in the DESCRIPTION clause associated with its MODULE-IDENTITY statement. 453 The current version of the IANATn3270eTC-MIB can be accessed from the 454 IANA home page at: "http://www.iana.org/iana/". 456 4.0 Definitions 458 TN3270E-MIB DEFINITIONS ::= BEGIN 460 IMPORTS 461 MODULE-IDENTITY, OBJECT-TYPE, Unsigned32, TimeTicks, 462 IpAddress, Counter32, Gauge32, Counter64 463 FROM SNMPv2-SMI 464 TEXTUAL-CONVENTION, RowStatus, TestAndIncr, DateAndTime, 465 TimeStamp 466 FROM SNMPv2-TC 467 MODULE-COMPLIANCE, OBJECT-GROUP 468 FROM SNMPv2-CONF 469 snanauMIB 470 FROM SNA-NAU-MIB 471 Utf8String 472 FROM SYSAPPL-MIB 473 SnmpAdminString 474 FROM SNMP-FRAMEWORK-MIB 475 IANATn3270eAddrType, IANATn3270eClientType, 476 IANATn3270eLogData, IANATn3270Functions 477 FROM IANATn3270eTC-MIB; 479 tn3270eMIB MODULE-IDENTITY 480 LAST-UPDATED "9805120000Z" -- May 12, 1998 481 ORGANIZATION "TN3270E Working Group" 482 CONTACT-INFO 483 "Kenneth White (kennethw@vnet.ibm.com) 484 IBM Corp. - Dept. BRQA/Bldg. 501/G114 485 P.O. Box 12195 486 3039 Cornwallis 487 RTP, NC 27709-2195 488 USA 490 Robert Moore (remoore@us.ibm.com) 491 IBM Corp. - Dept. BRQA/Bldg. 501/G114 492 P.O. Box 12195 493 3039 Cornwallis 494 RTP, NC 27709-2195 495 USA 496 +1-919-254-4436" 497 DESCRIPTION 498 "This module defines a portion of the management 499 information base (MIB) for managing TN3270E servers." 500 ::= { snanauMIB 8 } 502 -- Textual Conventions 504 SnaResourceName ::= TEXTUAL-CONVENTION 505 STATUS current 506 DESCRIPTION 507 "The textual convention for defining an SNA resource 508 name. A fully qualified SNA resource name, consisting 509 of a 1 to 8 character network identifier (NetId), a 510 period ('.'), and a 1 to 8 character resource name 511 (ResName). 513 The NetId and ResName are constructed from the 514 uppercase letters 'A' - 'Z' and the numerics '0' - '9', 515 all encoded in ASCII, with the restriction that the 516 first character of each must be a letter. Blanks are 517 not allowed. 519 Earlier versions of SNA permitted three additional 520 characters in NetIds and ResNames: '#', '@', and '$'. 521 While this use of these characters has been retired, 522 a Management Station should still accept them for 523 backward compatibility. 525 Note: This Textual Convention is not subject to 526 internationalization, and does not use the character 527 encodings used by the Utf8String Textual Convention." 528 SYNTAX OCTET STRING (SIZE(0..17)) 530 Tn3270ResourceType ::= TEXTUAL-CONVENTION 531 STATUS current 532 DESCRIPTION 533 "The type of resource defined by a resource pool. Refer 534 to tn3270eResPoolTable." 535 SYNTAX INTEGER { 536 other(0), 537 terminal(1), 538 printer(2), 539 terminalOrPrinter(3) 540 } 542 Tn3270eTAddress ::= TEXTUAL-CONVENTION 543 STATUS current 544 DESCRIPTION 545 "Denotes a client address. The type of client 546 address is determined by use of the IANATn3270eAddrType 547 textual convention. The length in octets of a 548 Tn3270eTAddress object is: 550 IANATn3270eAddrType Address Length 551 unknown(0) not specified or unknown; 552 the actual length of the 553 Tn3270eTAddress octet string 554 indicates if an address 555 is present 556 ipv4(1) 4 OCTETS 557 ipv6(2) 16 OCTETS 559 This textual convention is similar to the TAddress 560 TC defined by RFC1903 except that it allows a 561 zero-length octet string and is not a full transport 562 layer address." 563 SYNTAX OCTET STRING (SIZE (0..255)) 565 Tn3270DeviceTypes ::= TEXTUAL-CONVENTION 566 STATUS current 567 DESCRIPTION 568 "This textual convention defines the list of device 569 types that can be set, as defined by RFC 1647." 570 SYNTAX INTEGER { -- terminals 571 unknown(0), 572 ibm3278d2(1), -- (24 row x 80 col display) 573 ibm3278d2E(2), -- (24 row x 80 col display) 574 ibm3278d3(3), -- (32 row x 80 col display) 575 ibm3278d3E(4), -- (32 row x 80 col display) 576 ibm3278d4(5), -- (43 row x 80 col display) 577 ibm3278d4E(6), -- (43 row x 80 col display) 578 ibm3278d5(7), -- (27 row x 132 col display) 579 ibm3278d5E(8), -- (27 row x 132 col display) 580 ibmDynamic(9), -- (no pre-defined display size) 581 ibm3287d1(10) -- printers 582 } 584 Tn3270eTraceData ::= TEXTUAL-CONVENTION 585 STATUS current 586 DESCRIPTION 587 "An octet string representing trace data from the 588 Telnet half of a TN3270E session, from the SNA half, 589 or from both. The octet string contains a sequence 590 of trace elements, with the trace elements in the 591 string ordered from earliest to latest. 593 Each trace element has the following form: 595 +---+---+----+----------------------+ 596 !length !type!data ! 597 +---+---+----+----------------------+ 599 where: 601 length = two-octet length of the data portion of the 602 trace element, not including the length and 603 type octets 605 type = one-octet code point characterizing the data; 606 defined values are: 608 X'01' telnet PDU from the server to the client 609 X'02' telnet PDU from the client to the server 610 X'03' SNA data from the server to the SNA host 611 X'04' SNA data from the SNA host to the server 613 data = initial part of a PDU. 615 It is left to implementations to determine how 616 much of each PDU to return in a trace element. 618 The zero-length string indicates that no trace 619 data is available." 620 SYNTAX OCTET STRING (SIZE (0 | 3..4096)) 622 -- Top-level structure of the MIB 624 tn3270eNotifications OBJECT IDENTIFIER ::= { tn3270eMIB 0 } 625 tn3270eObjects OBJECT IDENTIFIER ::= { tn3270eMIB 1 } 626 tn3270eConformance OBJECT IDENTIFIER ::= { tn3270eMIB 3 } 628 -- MIB Objects 630 tn3270eSrvrConfTable OBJECT-TYPE 631 SYNTAX SEQUENCE OF Tn3270eSrvrConfEntry 632 MAX-ACCESS not-accessible 633 STATUS current 634 DESCRIPTION 635 "This table defines the configuration elements for 636 TN3270E servers. The number of entries in this table 637 is expected to vary depending on the location of the 638 table. A particular TN3270E server is expected to 639 have a single entry. Modeling of the configuration 640 elements as a table allows multiple TN3270E 641 servers to be serviced by the same SNMP agent. 643 An implementation SHOULD NOT retain an SNMP-created 644 entry in this table across re-IPLs (Initial Program 645 Loads) of the corresponding TN3270E server." 647 ::= { tn3270eObjects 1 } 649 tn3270eSrvrConfEntry OBJECT-TYPE 650 SYNTAX Tn3270eSrvrConfEntry 651 MAX-ACCESS not-accessible 652 STATUS current 653 DESCRIPTION 654 "Definition of the configuration elements for a single 655 TN3270E server." 656 INDEX { tn3270eSrvrConfIndex } 657 ::= { tn3270eSrvrConfTable 1 } 659 Tn3270eSrvrConfEntry ::= SEQUENCE { 660 tn3270eSrvrConfIndex Unsigned32, 661 tn3270eSrvrConfInactivityTimeout Unsigned32, 662 tn3270eSrvrConfActivityCheck INTEGER, 663 tn3270eSrvrConfTmNopInactTime Unsigned32, 664 tn3270eSrvrConfTmNopInterval Unsigned32, 665 tn3270eSrvrFunctionsSupported IANATn3270Functions, 666 tn3270eSrvrConfAdminStatus INTEGER, 667 tn3270eSrvrConfOperStatus INTEGER, 668 tn3270eSrvrConfSessionTermState INTEGER, 669 tn3270eSrvrConfSrvrType INTEGER, 670 tn3270eSrvrConfContact SnmpAdminString, 671 tn3270eSrvrConfRowStatus RowStatus, 672 tn3270eSrvrConfLastActTime DateAndTime, 673 tn3270eSrvrConfTmTimeout Unsigned32 674 } 676 tn3270eSrvrConfIndex OBJECT-TYPE 677 SYNTAX Unsigned32 (1..4294967295) 678 MAX-ACCESS not-accessible 679 STATUS current 680 DESCRIPTION 681 "Identifier for a single TN3270E server. 683 tn3270eSrvrConfIndex values need not be 684 contiguous." 685 ::= { tn3270eSrvrConfEntry 1 } 687 tn3270eSrvrConfInactivityTimeout OBJECT-TYPE 688 SYNTAX Unsigned32 (0..99999999) 689 UNITS "seconds" 690 MAX-ACCESS read-create 691 STATUS current 692 DESCRIPTION 693 "The inactivity time-out specified in seconds. When a 694 connection has been inactive for the number of seconds 695 specified by this object it is closed. Only user traffic 696 is considered when determining whether there has been 697 activity on a connection. 699 The default value 0 means that no inactivity time-out is 700 in effect." 701 DEFVAL { 0 } 702 ::= { tn3270eSrvrConfEntry 2 } 704 tn3270eSrvrConfActivityCheck OBJECT-TYPE 705 SYNTAX INTEGER { 706 noCheck(0), 707 timingMark(1), 708 nop(2) 709 } 710 MAX-ACCESS read-create 711 STATUS current 712 DESCRIPTION 713 "This object enables TIMING-MARK processing, NOP 714 processing, or neither for a TN3270E server." 715 DEFVAL { noCheck } 716 ::= { tn3270eSrvrConfEntry 3 } 718 tn3270eSrvrConfTmNopInactTime OBJECT-TYPE 719 SYNTAX Unsigned32 (1..86400) -- 1 second to 24 hours 720 UNITS "seconds" 721 MAX-ACCESS read-create 722 STATUS current 723 DESCRIPTION 724 "The amount of time a connection must have had no 725 traffic on it in order for a TIMING-MARK or NOP request 726 to be sent on the connection. This value applies only 727 when connections are being examined for recent activity 728 on a scan interval controlled by the value of the 729 tn3270eSrvrConfTmNopInterval object." 730 DEFVAL { 600 } -- 10 minutes 731 ::= { tn3270eSrvrConfEntry 4 } 733 tn3270eSrvrConfTmNopInterval OBJECT-TYPE 734 SYNTAX Unsigned32 (1..86400) -- 1 second to 24 hours 735 UNITS "seconds" 736 MAX-ACCESS read-create 737 STATUS current 738 DESCRIPTION 739 "The scan interval to be used by a TN3270E server when 740 it examines its Telnet connections for recent activity. 741 The server scans its Telnet connections on the interval 742 provided by this object, looking for ones that have been 743 idle for more than the value provided by the 744 tn3270eSrvrConfTmNopInactTime object. A TIMING-MARK or 745 NOP request is sent for each connection that has 746 exhibited no activity for this period of time." 747 DEFVAL { 120 } -- 2 minutes 748 ::= { tn3270eSrvrConfEntry 5 } 750 tn3270eSrvrFunctionsSupported OBJECT-TYPE 751 SYNTAX IANATn3270Functions 752 MAX-ACCESS read-only 753 STATUS current 754 DESCRIPTION 755 "This object indicates the functions supported by a 756 TN3270E server." 757 DEFVAL { { scsCtlCodes, dataStreamCtl, 758 responses, bindImage, sysreq } } 759 ::= { tn3270eSrvrConfEntry 6 } 761 tn3270eSrvrConfAdminStatus OBJECT-TYPE 762 SYNTAX INTEGER { 763 up(1), 764 down(2), 765 stopImmediate(3) 766 } 767 MAX-ACCESS read-create 768 STATUS current 769 DESCRIPTION 770 "The desired state of the TN3270E server represented 771 by this entry in the table: 773 up(1) - Activate this TN3270E server. 774 down(2) - Informs the associated TN3270E 775 server to gracefully terminate 776 its processing. 777 stopImmediate(3) - Informs the associated TN3270E 778 server to terminate itself 779 immediately. 781 When a managed system creates an entry in this table, 782 tn3270eSrvrConfAdminStatus and tn3270eSrvrConfOperStatus 783 are initialized as up(1) by default. 785 The exact behavior of a server in response to a down(2) 786 or stopImmediate(3) command is left implementation- 787 dependent. A TN3270E server that is capable of it 788 SHOULD close all of its TN3270 and TN3270E sessions 789 during a graceful termination. 791 Often the function enabled via stopImmediate(3) is used 792 as a last resort by a system administrator, to attempt 793 to either bring down a hung TN3270E server or free up 794 its resources immediately to aid in general system 795 availability, or to shut down a TN3270E server that is 796 not recognizing a down(2) request. 798 A TN3270E server that does not distinguish between 799 down(2) or stopImmediate(3) transitions should not 800 support stopImmediate(3)." 801 DEFVAL { up } 802 ::= { tn3270eSrvrConfEntry 7 } 804 tn3270eSrvrConfOperStatus OBJECT-TYPE 805 SYNTAX INTEGER { 806 up(1), 807 down(2), 808 busy(3), 809 shuttingDown(4) 810 } 811 MAX-ACCESS read-only 812 STATUS current 813 DESCRIPTION 814 "The current operational state of a TN3270E server. 815 The following values are defined: 817 up(1) - the server is active and accepting 818 new client connections 819 down(2) - the server is not active 820 busy(3) - the server is active, but is not 821 accepting new client connections 822 because it lacks the resources to 823 do so 824 shuttingDown(4) - the server is active, but is not 825 accepting new client connections 826 because it is in the process of 827 performing a graceful shutdown." 828 DEFVAL { up } 829 ::= { tn3270eSrvrConfEntry 8 } 831 tn3270eSrvrConfSessionTermState OBJECT-TYPE 832 SYNTAX INTEGER { 833 terminate(1), 834 luSessionPend(2), 835 queueSession(3) 836 } 837 MAX-ACCESS read-create 838 STATUS current 839 DESCRIPTION 840 "This object determines what a TN3270E server 841 should do when a TN3270 Session terminates: 843 terminate(1) => Terminate the TCP connection. 844 luSessionPend(2) => Do not drop the TCP connection 845 associated with a client when its 846 TN3270 session ends. Processing 847 should redrive session initialization 848 as if the client were first connecting. 849 queueSession(3) => This value relates to the Close 850 Destination PASS (CLSDST PASS) operation 851 in VTAM. An example provides the 852 easiest explanation. Suppose a TN3270E 853 client is in session with APPL1, and 854 APPL1 does a CLSDST PASS of the client's 855 session to APPL2. queueSession(3) 856 specifies that the TN3270E server must 857 keep the TCP connection with the client 858 active after it receives the UNBIND from 859 APPL1, waiting for the BIND from APPL2." 860 DEFVAL { terminate } 861 ::= { tn3270eSrvrConfEntry 9 } 863 tn3270eSrvrConfSrvrType OBJECT-TYPE 864 SYNTAX INTEGER { 865 host(1), 866 gateway(2) 867 } 868 MAX-ACCESS read-only 869 STATUS current 870 DESCRIPTION 871 "This object indicates the type of TN3270E server. 872 The existence of MIB tables and objects that will be 873 defined by follow-on MIBs may be predicated on whether 874 the TN3270E server can be local to the same host as a 875 target application (host(1)) or will always be remote 876 (gateway(2)). 878 A host TN3270E server refers to an implementation where 879 the TN3270E server is collocated with the Systems 880 Network Architecture (SNA) System Services Control Point 881 (SSCP) for the dependent Secondary Logical Units (SLUs) 882 that the server makes available to its clients for 883 connecting into an SNA network. 885 A gateway TN3270E server resides on an SNA node other 886 than an SSCP, either an SNA type 2.0 node or an APPN node 887 acting in the role of a Dependent LU Requester (DLUR). 889 Host and gateway TN3270E server implementations typically 890 differ greatly as to their internal implementation and 891 system definition (SYSDEF) requirements." 892 ::= { tn3270eSrvrConfEntry 10 } 894 tn3270eSrvrConfContact OBJECT-TYPE 895 SYNTAX SnmpAdminString 896 MAX-ACCESS read-create 897 STATUS current 898 DESCRIPTION 899 "This object provides a scratch pad for a TN3270E 900 server administrator for storing information for 901 later retrieval." 902 DEFVAL { ''H } -- the empty string 903 ::= { tn3270eSrvrConfEntry 11 } 905 tn3270eSrvrConfRowStatus OBJECT-TYPE 906 SYNTAX RowStatus 907 MAX-ACCESS read-create 908 STATUS current 909 DESCRIPTION 910 "This object allows entries to be created and deleted 911 in the tn3270eSrvrConfTable. Entries may also be 912 created and deleted as a result of implementation- 913 dependent operations. 915 With the exception of tn3270eSrvrConfSrvrType, which 916 an implementation can easily fill in for itself, all 917 the columnar objects in this table have DEFVALs 918 associated with them. Consequently, a Management 919 Station can create a conceptual row via a SET 920 operation that specifies a value only for this object. 922 When a tn3270eSrvrConfEntry is deleted (by setting 923 this object to destroy(6)), this has the side-effect 924 of removing all the associated entries (i.e., those 925 having the same tn3270eSrvrConfIndex) from the 926 tn3270eSrvrPortTable, the tn3270eSrvrStatsTable, the 927 tn3270eClientGroupTable, the tn3270eResPoolTable, 928 the tn3270eSnaMapTable, the tn3270eClientResMapTable, 929 and the tn3270eResMapTable. All entries in the 930 tn3270eTcpConnTable that belong to a TN3270E server 931 that has been deleted MUST also be removed. 933 In other words, a tn3270eSrvrConfEntry must exist for 934 a TN3270E server in order for it to have entries in 935 any of the other tables defined by this MIB." 936 REFERENCE 937 "RFC 1903, 'Textual Conventions for version 2 of the 938 Simple Network Management Protocol (SNMPv2).'" 939 ::= { tn3270eSrvrConfEntry 12 } 941 tn3270eSrvrConfLastActTime OBJECT-TYPE 942 SYNTAX DateAndTime 943 MAX-ACCESS read-only 944 STATUS current 945 DESCRIPTION 946 "This object reports the DateAndTime when a TN3270E 947 server was most recently activated. 949 The special value of all '00'Hs indicates that the 950 server has never been active, i.e., that the value of 951 tn3270eSrvrOperStatus has never been anything other 952 than down(2)." 953 DEFVAL { '0000000000000000'H } 954 ::= { tn3270eSrvrConfEntry 13 } 956 tn3270eSrvrConfTmTimeout OBJECT-TYPE 957 SYNTAX Unsigned32 (1..600) -- 1 second to 10 minutes 958 UNITS "seconds" 959 MAX-ACCESS read-create 960 STATUS current 961 DESCRIPTION 962 "The TIMING-MARK time-out, specified in seconds." 963 DEFVAL { 5 } -- 5 seconds 964 ::= { tn3270eSrvrConfEntry 14 } 966 tn3270eSrvrPortTable OBJECT-TYPE 967 SYNTAX SEQUENCE OF Tn3270eSrvrPortEntry 968 MAX-ACCESS not-accessible 969 STATUS current 970 DESCRIPTION 971 "This table defines the TCP ports associated with 972 TN3270E servers. No entry in this table shall exist 973 without a corresponding (same tn3270eSrvrConfIndex) 974 entry in the tn3270eSrvrConfTable existing. 976 An implementation SHOULD NOT retain SNMP-created 977 entries in this table across re-IPLs (Initial Program 978 Loads) of the corresponding TN3270E server." 979 ::= { tn3270eObjects 2 } 981 tn3270eSrvrPortEntry OBJECT-TYPE 982 SYNTAX Tn3270eSrvrPortEntry 983 MAX-ACCESS not-accessible 984 STATUS current 985 DESCRIPTION 986 "Definition of a single TCP port assignment to a 987 TN3270E server. Assignment of a port on a local 988 address basis is enabled though use of 989 tn3270eSrvrPortAddrType and tn3270eSrvrPortAddress. 991 A TCP port assignment that is not restricted to 992 a local address SHALL specify a tn3270eSrvrPortAddrType 993 of unknown(0), and SHALL use a zero-length octet string 994 for the tn3270eSrvrPortAddress." 995 INDEX { 996 tn3270eSrvrConfIndex, 997 tn3270eSrvrPort, 998 tn3270eSrvrPortAddrType, 999 tn3270eSrvrPortAddress 1000 } 1001 ::= { tn3270eSrvrPortTable 1 } 1003 Tn3270eSrvrPortEntry ::= SEQUENCE { 1004 tn3270eSrvrPort Unsigned32, 1005 tn3270eSrvrPortAddrType IANATn3270eAddrType, 1006 tn3270eSrvrPortAddress Tn3270eTAddress, 1007 tn3270eSrvrPortRowStatus RowStatus 1008 } 1010 tn3270eSrvrPort OBJECT-TYPE 1011 SYNTAX Unsigned32 (0..65535) 1012 MAX-ACCESS not-accessible 1013 STATUS current 1014 DESCRIPTION 1015 "Indicates a port assigned to a server." 1016 ::= { tn3270eSrvrPortEntry 1 } 1018 tn3270eSrvrPortAddrType OBJECT-TYPE 1019 SYNTAX IANATn3270eAddrType 1020 MAX-ACCESS not-accessible 1021 STATUS current 1022 DESCRIPTION 1023 "Indicates the type of an address local to the host on 1024 which the TN3270E server resides that is represented 1025 in tn3270eSrvrPortAddress. A value of unknown(0) 1026 SHALL be used for this object when the port is not 1027 to be restricted to a local address." 1028 ::= { tn3270eSrvrPortEntry 2 } 1030 tn3270eSrvrPortAddress OBJECT-TYPE 1031 SYNTAX Tn3270eTAddress 1032 MAX-ACCESS not-accessible 1033 STATUS current 1034 DESCRIPTION 1035 "A local address on the host that a TN3270E server 1036 resides on that is associated with a TCP port that 1037 is to be used or is in use by a TN3270E server. 1038 tn3270eClientGroupAddrType indicates the 1039 address type (IPv4 or IPv6, for example). 1041 A zero-length octet string SHALL be used as the 1042 value of this object when a local address isn't 1043 being specified." 1044 ::= { tn3270eSrvrPortEntry 3 } 1046 tn3270eSrvrPortRowStatus OBJECT-TYPE 1047 SYNTAX RowStatus 1048 MAX-ACCESS read-create 1049 STATUS current 1050 DESCRIPTION 1051 "This object allows entries to be created and deleted 1052 in the tn3270eSrvrPortTable. Entries may also be 1053 created and deleted as a result of implementation- 1054 dependent operations. 1056 Since this is the only accessible object in this table, 1057 a Management Station can create a conceptual row via a SET 1058 operation that specifies a value only for this object. 1060 An entry in this table is deleted by setting this object 1061 to destroy(6). Deletion of a tn3270eSrvrPortEntry has 1062 no effect on any other table entry defined by this MIB." 1063 REFERENCE 1064 "RFC 1903, 'Textual Conventions for version 2 of the 1065 Simple Network Management Protocol (SNMPv2).'" 1066 ::= { tn3270eSrvrPortEntry 4 } 1068 tn3270eSrvrStatsTable OBJECT-TYPE 1069 SYNTAX SEQUENCE OF Tn3270eSrvrStatsEntry 1070 MAX-ACCESS not-accessible 1071 STATUS current 1072 DESCRIPTION 1073 "This table defines a set of statistics concerning 1074 TN3270E server performance. 1076 No entry in this table shall exist without 1077 a corresponding (same tn3270eSrvrConfIndex) entry in 1078 the tn3270eSrvrConfTable existing." 1079 ::= { tn3270eObjects 3 } 1081 tn3270eSrvrStatsEntry OBJECT-TYPE 1082 SYNTAX Tn3270eSrvrStatsEntry 1083 MAX-ACCESS not-accessible 1084 STATUS current 1085 DESCRIPTION 1086 "A collection of statistical and maximum usage objects 1087 for a single TN3270 server. An entry can represent the total 1088 activity of the server, or it can represent the activity 1089 occurring at the server on either a port or a 1090 port-and-local-address basis. 1092 Collection of the statistics represented by the objects 1093 in this table is not mandatory. An implementation 1094 of this table MUST use only one of the three levels of 1095 refinement that this table supports for the entries 1096 associated with each TN3270E server. 1098 The indexing for a row that represents total server 1099 statistics is as follows: 1101 tn3270eSrvrConfIndex value identifying the server 1102 tn3270eSrvrPort 0 1103 tn3270eSrvrPortAddrType unknown(0) 1104 tn3270eSrvrPortAddress zero-length octet string. 1106 On a port basis: 1108 tn3270eSrvrConfIndex value identifying the server 1109 tn3270eSrvrPort > 0 1110 tn3270eSrvrPortAddrType unknown(0) 1111 tn3270eSrvrPortAddress zero-length octet string. 1113 On a port-and-local-address basis: 1115 tn3270eSrvrConfIndex value identifying the server 1116 tn3270eSrvrPort > 0 1117 tn3270eSrvrPortAddrType valid value other than unknown(0) 1118 tn3270eSrvrPortAddress non-zero-length octet string. 1120 " 1121 INDEX { 1122 tn3270eSrvrConfIndex, 1123 tn3270eSrvrPort, 1124 tn3270eSrvrPortAddrType, 1125 tn3270eSrvrPortAddress 1126 } 1127 ::= { tn3270eSrvrStatsTable 1 } 1129 Tn3270eSrvrStatsEntry ::= SEQUENCE { 1130 tn3270eSrvrStatsUpTime TimeStamp, 1131 tn3270eSrvrStatsMaxTerms Unsigned32, 1132 tn3270eSrvrStatsInUseTerms Gauge32, 1133 tn3270eSrvrStatsSpareTerms Gauge32, 1134 tn3270eSrvrStatsMaxPtrs Unsigned32, 1135 tn3270eSrvrStatsInUsePtrs Gauge32, 1136 tn3270eSrvrStatsSparePtrs Gauge32, 1137 tn3270eSrvrStatsInConnects Counter32, 1138 tn3270eSrvrStatsConnResrceRejs Counter32, 1139 tn3270eSrvrStatsDisconnects Counter32, 1140 tn3270eSrvrStatsHCInOctets Counter64, 1141 tn3270eSrvrStatsInOctets Counter32, 1142 tn3270eSrvrStatsHCOutOctets Counter64, 1143 tn3270eSrvrStatsOutOctets Counter32, 1144 tn3270eSrvrStatsConnErrorRejs Counter32 1145 } 1147 tn3270eSrvrStatsUpTime OBJECT-TYPE 1148 SYNTAX TimeStamp 1149 MAX-ACCESS read-only 1150 STATUS current 1151 DESCRIPTION 1152 "The value of the sysUpTime object the last time 1153 the TN3270E server was re-initialized. 1155 Server re-initialization is the only discontinuity 1156 event for the counters in this table. Even if table 1157 entries are on a port or port-and-local-address 1158 basis, port deactivation and reactivation do not 1159 result in counter discontinuities." 1160 ::= { tn3270eSrvrStatsEntry 2 } 1162 tn3270eSrvrStatsMaxTerms OBJECT-TYPE 1163 SYNTAX Unsigned32 1164 UNITS "LUs" 1165 MAX-ACCESS read-only 1166 STATUS current 1167 DESCRIPTION 1168 "Indicates the maximum number of terminal LUs available 1169 for use at a TN3270E server for the granularity of this 1170 conceptual row (server-wide, port, or 1171 port-and-local-address)." 1172 ::= { tn3270eSrvrStatsEntry 3 } 1174 tn3270eSrvrStatsInUseTerms OBJECT-TYPE 1175 SYNTAX Gauge32 1176 UNITS "LUs" 1177 MAX-ACCESS read-only 1178 STATUS current 1179 DESCRIPTION 1180 "Indicates the number of terminal LUs currently in 1181 use at a TN3270E server for the granularity of this 1182 conceptual row (server-wide, port, or 1183 port-and-local-address)." 1184 ::= { tn3270eSrvrStatsEntry 4 } 1186 tn3270eSrvrStatsSpareTerms OBJECT-TYPE 1187 SYNTAX Gauge32 1188 UNITS "LUs" 1189 MAX-ACCESS read-only 1190 STATUS current 1191 DESCRIPTION 1192 "Indicates the number of free terminal LUs at a TN3270E 1193 server for the granularity of this conceptual row 1194 (server-wide, port, or port-and-local-address). 1196 It is possible that the difference between 1197 tn3270eSrvrStatsMaxTerms and tn3270eSrvrStatsInUseTerms 1198 in a conceptual row does not equal the value of 1199 tn3270eSrvrStatsSpareTerms in that row: an LU may 1200 exist but not be usable by a client connection. 1202 Alternatively, the administrative ceiling represented 1203 by tn3270eSrvrStatsMaxTerms may have been lowered to 1204 a point where it is less than the current value of 1205 tn3270eSrvrStatsInUseTerms. In this case 1206 tn3270eSrvrStatsSpareTerms returns the value 0." 1208 ::= { tn3270eSrvrStatsEntry 5 } 1210 tn3270eSrvrStatsMaxPtrs OBJECT-TYPE 1211 SYNTAX Unsigned32 1212 UNITS "Printer Resources" 1213 MAX-ACCESS read-only 1214 STATUS current 1215 DESCRIPTION 1216 "Indicates the maximum number of printer resources 1217 available for use by a TN3270E server for the 1218 granularity of this conceptual row (server-wide, 1219 port, or port-and-local-address)." 1220 ::= { tn3270eSrvrStatsEntry 6 } 1222 tn3270eSrvrStatsInUsePtrs OBJECT-TYPE 1223 SYNTAX Gauge32 1224 UNITS "Printer Resources" 1225 MAX-ACCESS read-only 1226 STATUS current 1227 DESCRIPTION 1228 "Indicates the number of printer resources 1229 currently in use by a TN3270E server for the 1230 granularity of this conceptual row (server-wide, 1231 port, or port-and-local-address)." 1232 ::= { tn3270eSrvrStatsEntry 7 } 1234 tn3270eSrvrStatsSparePtrs OBJECT-TYPE 1235 SYNTAX Gauge32 1236 UNITS "Spare Printer Resources" 1237 MAX-ACCESS read-only 1238 STATUS current 1239 DESCRIPTION 1240 "Indicates the number of free printer resources at 1241 a TN3270E server for the granularity of this conceptual 1242 row (server-wide, port, or port-and-local-address). 1244 It is possible that the difference between 1245 tn3270eSrvrStatsMaxPtrs and tn3270eSrvrStatsInUsePtrs 1246 in a conceptual row does not equal the value of 1247 tn3270eSrvrStatsSparePtrs in that row: a printer 1248 resource may exist but not be usable by a client 1249 connection. 1251 Alternatively, the administrative ceiling represented 1252 by tn3270eSrvrStatsMaxPtrs may have been lowered to 1253 a point where it is less than the current value of 1254 tn3270eSrvrStatsInUsePtrs. In this case 1255 tn3270eSrvrStatsSparePtrs returns the value 0." 1256 ::= { tn3270eSrvrStatsEntry 8 } 1258 tn3270eSrvrStatsInConnects OBJECT-TYPE 1259 SYNTAX Counter32 1260 UNITS "connections" 1261 MAX-ACCESS read-only 1262 STATUS current 1263 DESCRIPTION 1264 "Indicates the number of client (TCP) connections 1265 that succeeded at a TN3270E server for the 1266 granularity of this conceptual row (server-wide, 1267 port, or port-and-local-address). 1269 The tn3270eSrvrStatsConnResrceRejs and 1270 tn3270eSrvrStatsConnErrorRejs objects provide a count 1271 of failed connection attempts. 1273 A Management Station can detect discontinuities in 1274 this counter by monitoring the tn3270eSrvrStatsUpTime 1275 object." 1276 ::= { tn3270eSrvrStatsEntry 9 } 1278 tn3270eSrvrStatsConnResrceRejs OBJECT-TYPE 1279 SYNTAX Counter32 1280 UNITS "connection attempts" 1281 MAX-ACCESS read-only 1282 STATUS current 1283 DESCRIPTION 1284 "Indicates the number of (TCP) connections rejected 1285 during connection setup at a TN3270E server for the 1286 granularity of this conceptual row (server-wide, 1287 port, or port-and-local-address) due to a lack of 1288 resources at the server. An example of when this 1289 counter would be incremented is when no terminal 1290 or printer resource is available to associate with a 1291 client's TCP connection. 1293 A Management Station can detect discontinuities in 1294 this counter by monitoring the tn3270eSrvrStatsUpTime 1295 object." 1296 ::= { tn3270eSrvrStatsEntry 10 } 1298 tn3270eSrvrStatsDisconnects OBJECT-TYPE 1299 SYNTAX Counter32 1300 UNITS "disconnections" 1301 MAX-ACCESS read-only 1302 STATUS current 1303 DESCRIPTION 1304 "Indicates the number of (TCP) connections that were 1305 disconnected at a TN3270E server for the 1306 granularity of this conceptual row (server-wide, 1307 port, or port-and-local-address). 1309 A Management Station can detect discontinuities in 1310 this counter by monitoring the tn3270eSrvrStatsUpTime 1311 object." 1312 ::= { tn3270eSrvrStatsEntry 11 } 1314 tn3270eSrvrStatsHCInOctets OBJECT-TYPE 1315 SYNTAX Counter64 1316 UNITS "octets" 1317 MAX-ACCESS read-only 1318 STATUS current 1319 DESCRIPTION 1320 "Indicates the number of octets received from TN3270 1321 and TN3270E clients for the granularity of this 1322 conceptual row (server-wide, port, or 1323 port-and-local-address). 1325 A Management Station can detect discontinuities in 1326 this counter by monitoring the tn3270eSrvrStatsUpTime 1327 object." 1328 ::= { tn3270eSrvrStatsEntry 12 } 1330 tn3270eSrvrStatsInOctets OBJECT-TYPE 1331 SYNTAX Counter32 1332 UNITS "octets" 1333 MAX-ACCESS read-only 1334 STATUS current 1335 DESCRIPTION 1336 "Low-order 32 bits of tn3270eSrvrStatsHCInOctets for 1337 this conceptual row. 1339 A Management Station can detect discontinuities in 1340 this counter by monitoring the tn3270eSrvrStatsUpTime 1341 object." 1342 ::= { tn3270eSrvrStatsEntry 13 } 1344 tn3270eSrvrStatsHCOutOctets OBJECT-TYPE 1345 SYNTAX Counter64 1346 UNITS "octets" 1347 MAX-ACCESS read-only 1348 STATUS current 1349 DESCRIPTION 1350 "Indicates the number of octets sent to TN3270 1351 and TN3270E clients for the granularity of this 1352 conceptual row (server-wide, port, or 1353 port-and-local-address). 1355 A Management Station can detect discontinuities in 1356 this counter by monitoring the tn3270eSrvrStatsUpTime 1357 object." 1358 ::= { tn3270eSrvrStatsEntry 14 } 1360 tn3270eSrvrStatsOutOctets OBJECT-TYPE 1361 SYNTAX Counter32 1362 UNITS "octets" 1363 MAX-ACCESS read-only 1364 STATUS current 1365 DESCRIPTION 1366 "Low-order 32 bits of tn3270eSrvrStatsHCOutOctets for 1367 this conceptual row. 1369 A Management Station can detect discontinuities in 1370 this counter by monitoring the tn3270eSrvrStatsUpTime 1371 object." 1372 ::= { tn3270eSrvrStatsEntry 15 } 1374 tn3270eSrvrStatsConnErrorRejs OBJECT-TYPE 1375 SYNTAX Counter32 1376 UNITS "connection attempts" 1377 MAX-ACCESS read-only 1378 STATUS current 1379 DESCRIPTION 1380 "Indicates the number of (TCP) connections rejected 1381 during connection setup at a TN3270E server for the 1382 granularity of this conceptual row (server-wide, 1383 port, or port-and-local-address) due to an error 1384 of some type. An example of when this counter would 1385 be incremented is when the client and the server 1386 cannot agree on a common set of TN3270E functions for 1387 the connection. 1389 A Management Station can detect discontinuities in 1390 this counter by monitoring the tn3270eSrvrStatsUpTime 1391 object." 1392 ::= { tn3270eSrvrStatsEntry 16 } 1394 tn3270eClientGroupTable OBJECT-TYPE 1395 SYNTAX SEQUENCE OF Tn3270eClientGroupEntry 1396 MAX-ACCESS not-accessible 1397 STATUS current 1398 DESCRIPTION 1399 "This table defines client address groupings for use 1400 by a TN3270E server. 1402 No entry in this table shall exist without 1403 a corresponding (same tn3270eSrvrConfIndex) entry in 1404 the tn3270eSrvrConfTable existing. 1406 An implementation SHOULD NOT retain SNMP-created 1407 entries in this table across re-IPLs (Initial Program 1408 Loads) of the corresponding TN3270E server." 1409 ::= { tn3270eObjects 4 } 1411 tn3270eClientGroupEntry OBJECT-TYPE 1412 SYNTAX Tn3270eClientGroupEntry 1413 MAX-ACCESS not-accessible 1414 STATUS current 1415 DESCRIPTION 1416 "Definition of a single client address entry. All 1417 entries with the same first two indexes, 1418 tn3270eSrvrConfIndex and tn3270eClientGroupName, are 1419 considered to be in the same client group." 1420 INDEX { tn3270eSrvrConfIndex, 1421 tn3270eClientGroupName, 1422 tn3270eClientGroupAddrType, 1423 tn3270eClientGroupAddress } 1424 ::= { tn3270eClientGroupTable 1 } 1426 Tn3270eClientGroupEntry ::= SEQUENCE { 1427 tn3270eClientGroupName Utf8String, 1428 tn3270eClientGroupAddrType IANATn3270eAddrType, 1429 tn3270eClientGroupAddress Tn3270eTAddress, 1430 tn3270eClientGroupSubnetMask IpAddress, 1431 tn3270eClientGroupPfxLength Unsigned32, 1432 tn3270eClientGroupRowStatus RowStatus 1433 } 1435 tn3270eClientGroupName OBJECT-TYPE 1436 SYNTAX Utf8String (SIZE(1..24)) 1437 MAX-ACCESS not-accessible 1438 STATUS current 1439 DESCRIPTION 1440 "The name of a client group. Note: client group 1441 names are required to be unique only with respect 1442 to a single TN3270E server." 1443 ::= { tn3270eClientGroupEntry 1 } 1445 tn3270eClientGroupAddrType OBJECT-TYPE 1446 SYNTAX IANATn3270eAddrType 1447 MAX-ACCESS not-accessible 1448 STATUS current 1449 DESCRIPTION 1450 "Indicates the type of the address represented in 1451 tn3270eClientGroupAddress." 1452 ::= { tn3270eClientGroupEntry 2 } 1454 tn3270eClientGroupAddress OBJECT-TYPE 1455 SYNTAX Tn3270eTAddress 1456 MAX-ACCESS not-accessible 1457 STATUS current 1458 DESCRIPTION 1459 "The client address of a member of a client group. 1460 The value of tn3270eClientGroupAddrType indicates 1461 the address type (IPv4 or IPv6, for example)." 1462 ::= { tn3270eClientGroupEntry 3 } 1464 tn3270eClientGroupSubnetMask OBJECT-TYPE 1465 SYNTAX IpAddress 1466 MAX-ACCESS read-create 1467 STATUS current 1468 DESCRIPTION 1469 "The corresponding subnet mask associated with 1470 tn3270eClientGroupAddress. A single IP address is 1471 represented by having this object contain the value 1472 of 255.255.255.255. 1474 This object's value is meaningful only if 1475 tn3270eClientGroupAddrType has a value of ipv4(1)." 1476 DEFVAL { 'FFFFFFFF'H } 1477 ::= { tn3270eClientGroupEntry 4 } 1479 tn3270eClientGroupPfxLength OBJECT-TYPE 1480 SYNTAX Unsigned32 (0..128) 1481 UNITS "bits" 1482 MAX-ACCESS read-create 1483 STATUS current 1484 DESCRIPTION 1485 "The corresponding IPv6 network prefix length. 1487 This object's value is meaningful only if 1488 tn3270eClientGroupAddrType has a value of ipv6(2)." 1489 DEFVAL { 0 } 1490 ::= { tn3270eClientGroupEntry 5 } 1492 tn3270eClientGroupRowStatus OBJECT-TYPE 1493 SYNTAX RowStatus 1494 MAX-ACCESS read-create 1495 STATUS current 1496 DESCRIPTION 1497 "This object allows entries to be created and deleted 1498 in the tn3270eClientGroupTable. Entries may also be 1499 created and deleted as a result of implementation- 1500 dependent operations. 1502 An entry in this table is deleted by setting this object 1503 to destroy(6). When the number of entries in this table 1504 for a given client group becomes 0, this has the side- 1505 effect of removing any entries for the group in the 1506 tn3270eClientResMapTable." 1507 REFERENCE 1508 "RFC 1903, 'Textual Conventions for version 2 of the 1509 Simple Network Management Protocol (SNMPv2).'" 1510 ::= { tn3270eClientGroupEntry 6 } 1512 tn3270eResPoolTable OBJECT-TYPE 1513 SYNTAX SEQUENCE OF Tn3270eResPoolEntry 1514 MAX-ACCESS not-accessible 1515 STATUS current 1516 DESCRIPTION 1517 "This table defines resource groupings; the term 1518 'pool' is used as it is defined by RFC 1647. 1520 No entry in this table shall exist without 1521 a corresponding (same tn3270eSrvrConfIndex) entry in 1522 the tn3270eSrvrConfTable existing. 1524 An implementation SHOULD NOT retain SNMP-created 1525 entries in this table across re-IPLs (Initial Program 1526 Loads) of the corresponding TN3270E server." 1527 ::= { tn3270eObjects 5 } 1529 tn3270eResPoolEntry OBJECT-TYPE 1530 SYNTAX Tn3270eResPoolEntry 1531 MAX-ACCESS not-accessible 1532 STATUS current 1533 DESCRIPTION 1534 "Definition of a single resource pool member. All entries 1535 with the same first two indexes, tn3270eSrvrConfIndex and 1536 tn3270eResPoolName, are considered to be in the same pool." 1537 INDEX { tn3270eSrvrConfIndex, 1538 tn3270eResPoolName, 1539 tn3270eResPoolElementName } 1540 ::= { tn3270eResPoolTable 1 } 1542 Tn3270eResPoolEntry ::= SEQUENCE { 1543 tn3270eResPoolName Utf8String, 1544 tn3270eResPoolElementName SnaResourceName, 1545 tn3270eResPoolElementType Tn3270ResourceType, 1546 tn3270eResPoolRowStatus RowStatus 1547 } 1549 tn3270eResPoolName OBJECT-TYPE 1550 SYNTAX Utf8String (SIZE(1..24)) 1551 MAX-ACCESS not-accessible 1552 STATUS current 1553 DESCRIPTION 1554 "The name of a resource pool." 1555 ::= { tn3270eResPoolEntry 1 } 1557 tn3270eResPoolElementName OBJECT-TYPE 1558 SYNTAX SnaResourceName 1559 MAX-ACCESS not-accessible 1560 STATUS current 1561 DESCRIPTION 1562 "The name of a member of a resource pool." 1563 ::= { tn3270eResPoolEntry 2 } 1565 tn3270eResPoolElementType OBJECT-TYPE 1566 SYNTAX Tn3270ResourceType 1567 MAX-ACCESS read-create 1568 STATUS current 1569 DESCRIPTION 1570 "The type of the entity in a resource pool." 1571 ::= { tn3270eResPoolEntry 3 } 1573 tn3270eResPoolRowStatus OBJECT-TYPE 1574 SYNTAX RowStatus 1575 MAX-ACCESS read-create 1576 STATUS current 1577 DESCRIPTION 1578 "This object allows entries to be created and deleted 1579 in the tn3270eResPoolTable. Entries may also be 1580 created and deleted as a result of implementation- 1581 dependent operations. 1583 An entry in this table is deleted by setting this object 1584 to destroy(6). When all entries in this table associated 1585 with the same tn3270eResPoolElementName have been removed, 1586 then any associated (tn3270eResPoolElementName matching 1587 tn3270eClientResMapPoolName with same tn3270eSrvrConfIndex 1588 values) entries in the tn3270eClientResMapTable SHALL 1589 also be removed." 1590 REFERENCE 1591 "RFC 1903, 'Textual Conventions for version 2 of the 1592 Simple Network Management Protocol (SNMPv2).'" 1593 ::= { tn3270eResPoolEntry 4 } 1595 tn3270eSnaMapTable OBJECT-TYPE 1596 SYNTAX SEQUENCE OF Tn3270eSnaMapEntry 1597 MAX-ACCESS not-accessible 1598 STATUS current 1599 DESCRIPTION 1600 "This table provide a mapping from the name by which 1601 a secondary LU is known in the SNA network to the 1602 name by which it is known locally at the TN3270e 1603 server. This latter name serves as an index into 1604 the tn3270eResPoolTable and the tn3270eResMapTable. 1606 No entry in this table shall exist without 1607 a corresponding (same tn3270eSrvrConfIndex) entry in 1608 the tn3270eSrvrConfTable existing." 1609 ::= { tn3270eObjects 6 } 1611 tn3270eSnaMapEntry OBJECT-TYPE 1612 SYNTAX Tn3270eSnaMapEntry 1613 MAX-ACCESS not-accessible 1614 STATUS current 1615 DESCRIPTION 1616 "Definition of a single mapping from an SSCP-supplied 1617 SLU name to a local SLU name." 1618 INDEX { tn3270eSrvrConfIndex, 1619 tn3270eSnaMapSscpSuppliedName } 1620 ::= { tn3270eSnaMapTable 1 } 1622 Tn3270eSnaMapEntry ::= SEQUENCE { 1623 tn3270eSnaMapSscpSuppliedName SnaResourceName, 1624 tn3270eSnaMapLocalName SnaResourceName, 1625 tn3270eSnaMapPrimaryLuName SnaResourceName 1626 } 1628 tn3270eSnaMapSscpSuppliedName OBJECT-TYPE 1629 SYNTAX SnaResourceName 1630 MAX-ACCESS not-accessible 1631 STATUS current 1632 DESCRIPTION 1633 "The name of the secondary LU (SLU) as it is known in 1634 the SNA network. This name is sent by the SSCP on 1635 the Activate Logical Unit (ACTLU) request." 1636 ::= { tn3270eSnaMapEntry 1 } 1638 tn3270eSnaMapLocalName OBJECT-TYPE 1639 SYNTAX SnaResourceName 1640 MAX-ACCESS read-only 1641 STATUS current 1642 DESCRIPTION 1643 "The local name of the secondary LU (SLU)." 1644 ::= { tn3270eSnaMapEntry 2 } 1646 tn3270eSnaMapPrimaryLuName OBJECT-TYPE 1647 SYNTAX SnaResourceName 1648 MAX-ACCESS read-only 1649 STATUS current 1650 DESCRIPTION 1651 "When there is a currently active LU-LU session for 1652 this connection, this object returns the primary LU 1653 (PLU) name from the BIND. When there is no active 1654 LU-LU session, or when the PLU name is unavailable 1655 for some other reason, this object returns a 1656 zero-length octet string." 1657 ::= { tn3270eSnaMapEntry 3 } 1659 tn3270eClientResMapTable OBJECT-TYPE 1660 SYNTAX SEQUENCE OF Tn3270eClientResMapEntry 1661 MAX-ACCESS not-accessible 1662 STATUS current 1663 DESCRIPTION 1664 "This table defines resource-pool to client-group 1665 mappings. Since both the resource pool name and client 1666 group name are included in the index clause of this 1667 table, multiple resource pools can be assigned to the 1668 same client group. This enables use of multiple 1669 resource pools for use in client to resource mapping. 1670 Assigning multiple client groups to the same resource 1671 pool is also allowed, but is not the primary purpose 1672 for how the indexing is structured. 1674 Assignment of a resource pool to client group can be 1675 restricted based on TCP port. An index value of 0 for 1676 tn3270eClientResMapClientPort disables restriction of 1677 resource assignment based on client target port 1678 selection. 1680 No entry in this table shall exist without 1681 a corresponding (same tn3270eSrvrConfIndex) entry in 1682 the tn3270eSrvrConfTable existing. 1684 An implementation SHOULD NOT retain SNMP-created 1685 entries in this table across re-IPLs (Initial Program 1686 Loads) of the corresponding TN3270E server." 1687 ::= { tn3270eObjects 7 } 1689 tn3270eClientResMapEntry OBJECT-TYPE 1690 SYNTAX Tn3270eClientResMapEntry 1691 MAX-ACCESS not-accessible 1692 STATUS current 1693 DESCRIPTION 1694 "Definition of a single resource pool to client group 1695 mapping." 1696 INDEX { tn3270eSrvrConfIndex, 1697 tn3270eClientResMapPoolName, 1698 tn3270eClientResMapClientGroupName, 1699 tn3270eClientResMapClientPort } 1700 ::= { tn3270eClientResMapTable 1 } 1702 Tn3270eClientResMapEntry ::= SEQUENCE { 1703 tn3270eClientResMapPoolName Utf8String, 1704 tn3270eClientResMapClientGroupName Utf8String, 1705 tn3270eClientResMapClientPort Unsigned32, 1706 tn3270eClientResMapRowStatus RowStatus 1707 } 1709 tn3270eClientResMapPoolName OBJECT-TYPE 1710 SYNTAX Utf8String (SIZE(1..24)) 1711 MAX-ACCESS not-accessible 1712 STATUS current 1713 DESCRIPTION 1714 "The name of a resource pool." 1715 ::= { tn3270eClientResMapEntry 1 } 1717 tn3270eClientResMapClientGroupName OBJECT-TYPE 1718 SYNTAX Utf8String (SIZE(1..24)) 1719 MAX-ACCESS not-accessible 1720 STATUS current 1721 DESCRIPTION 1722 "The name of the client group that is mapped to a 1723 resource pool." 1724 ::= { tn3270eClientResMapEntry 2 } 1726 tn3270eClientResMapClientPort OBJECT-TYPE 1727 SYNTAX Unsigned32 (0..65535) 1728 MAX-ACCESS not-accessible 1729 STATUS current 1730 DESCRIPTION 1731 "A port number restricting the scope of a mapping 1732 from a resource pool to a client group. The 1733 value 0 for this object indicates that the scope 1734 of the mapping is not restricted." 1735 ::= { tn3270eClientResMapEntry 3 } 1737 tn3270eClientResMapRowStatus OBJECT-TYPE 1738 SYNTAX RowStatus 1739 MAX-ACCESS read-create 1740 STATUS current 1741 DESCRIPTION 1742 "This object allows entries to be created and deleted 1743 in the tn3270eClientResMapTable. Entries may also be 1744 created and deleted as a result of implementation- 1745 dependent operations. 1747 An entry in this table is deleted by setting this object 1748 to destroy(6). Removing an entry from this table doesn't 1749 affect any other table entry defined in this MIB." 1750 REFERENCE 1751 "RFC 1903, 'Textual Conventions for version 2 of the 1752 Simple Network Management Protocol (SNMPv2).'" 1753 ::= { tn3270eClientResMapEntry 4 } 1755 tn3270eResMapTable OBJECT-TYPE 1756 SYNTAX SEQUENCE OF Tn3270eResMapEntry 1757 MAX-ACCESS not-accessible 1758 STATUS current 1759 DESCRIPTION 1760 "This table defines the actual mapping of a resource 1761 to a client address. 1763 No entry in this table shall exist without 1764 a corresponding (same tn3270eSrvrConfIndex) entry in 1765 the tn3270eSrvrConfTable existing." 1766 ::= { tn3270eObjects 8 } 1768 tn3270eResMapEntry OBJECT-TYPE 1769 SYNTAX Tn3270eResMapEntry 1770 MAX-ACCESS not-accessible 1771 STATUS current 1772 DESCRIPTION 1773 "Definition of the mapping of a Resource Element to 1774 a client address." 1775 INDEX { tn3270eSrvrConfIndex, 1776 tn3270eResMapElementName } 1777 ::= { tn3270eResMapTable 1 } 1779 Tn3270eResMapEntry ::= SEQUENCE { 1780 tn3270eResMapElementName SnaResourceName, 1781 tn3270eResMapAddrType IANATn3270eAddrType, 1782 tn3270eResMapAddress Tn3270eTAddress, 1783 tn3270eResMapPort Unsigned32, 1784 tn3270eResMapElementType Tn3270ResourceType, 1785 tn3270eResMapSscpSuppliedName SnaResourceName 1786 } 1788 tn3270eResMapElementName OBJECT-TYPE 1789 SYNTAX SnaResourceName 1790 MAX-ACCESS not-accessible 1791 STATUS current 1792 DESCRIPTION 1793 "The name of a resource element. This is the name by 1794 which the server implementing this table knows the 1795 resource. It may be different from the name by which 1796 the resource is known in the SNA network. This latter 1797 name is returned in the tn3270eResMapSscpSuppliedName 1798 object." 1799 ::= { tn3270eResMapEntry 1 } 1801 tn3270eResMapAddrType OBJECT-TYPE 1802 SYNTAX IANATn3270eAddrType 1803 MAX-ACCESS read-only 1804 STATUS current 1805 DESCRIPTION 1806 "Indicates the type of the client address represented 1807 in tn3270eResMapAddress." 1808 ::= { tn3270eResMapEntry 2 } 1810 tn3270eResMapAddress OBJECT-TYPE 1811 SYNTAX Tn3270eTAddress 1812 MAX-ACCESS read-only 1813 STATUS current 1814 DESCRIPTION 1815 "A client address." 1816 ::= { tn3270eResMapEntry 3 } 1818 tn3270eResMapPort OBJECT-TYPE 1819 SYNTAX Unsigned32 (0..65535) 1820 MAX-ACCESS read-only 1821 STATUS current 1822 DESCRIPTION 1823 "A client port." 1824 ::= { tn3270eResMapEntry 4 } 1826 tn3270eResMapElementType OBJECT-TYPE 1827 SYNTAX Tn3270ResourceType 1828 MAX-ACCESS read-only 1829 STATUS current 1830 DESCRIPTION 1831 "The type of the associated resource element." 1832 ::= { tn3270eResMapEntry 5 } 1834 tn3270eResMapSscpSuppliedName OBJECT-TYPE 1835 SYNTAX SnaResourceName 1836 MAX-ACCESS read-only 1837 STATUS current 1838 DESCRIPTION 1839 "The name of the secondary LU (SLU) as it is known 1840 in a SNA network. This name is sent by the SSCP on 1841 the Activate Logical Unit (ACTLU) request. If this 1842 name is not known, this object returns a zero-length 1843 octet string." 1844 ::= { tn3270eResMapEntry 6 } 1846 -- Define the set of objects to supplement the TCP Connection Table 1848 tn3270eTcpConnTable OBJECT-TYPE 1849 SYNTAX SEQUENCE OF Tn3270eTcpConnEntry 1850 MAX-ACCESS not-accessible 1851 STATUS current 1852 DESCRIPTION 1853 "This table has an entry for each TN3270(E) client 1854 connection that is currently active at a TN3270E server. 1855 An implementation MAY retain entries for connections 1856 that have been terminated, but which entries are 1857 retained, how many entries are retained, and how long 1858 they are retained is entirely implementation-dependent. 1860 The indexing for this table is designed to support the 1861 use of an SNMP GET-NEXT operation using only the remote 1862 address type, remote address, and remote port, as a way 1863 for a Management Station to retrieve the table entries 1864 related to a particular TN3270(E) client." 1865 ::= { tn3270eObjects 9 } 1867 tn3270eTcpConnEntry OBJECT-TYPE 1868 SYNTAX Tn3270eTcpConnEntry 1869 MAX-ACCESS not-accessible 1870 STATUS current 1871 DESCRIPTION 1872 "Provides information about a single TN3270/TN3270E 1873 session. Note: a tn3270eSrvrConfIndex is not needed 1874 in this table, since the combination of remote and 1875 local addresses and ports is sufficient to 1876 guarantee uniqueness across the TN3270E servers 1877 serviced by an SNMP agent. Because of this indexing 1878 structure, however, this table does not support 1879 view-based access control policies that provide 1880 access to table rows on a per-server basis." 1881 INDEX { tn3270eTcpConnRemAddrType, 1882 tn3270eTcpConnRemAddress, 1883 tn3270eTcpConnRemPort, 1884 tn3270eTcpConnLocalAddrType, 1885 tn3270eTcpConnLocalAddress, 1886 tn3270eTcpConnLocalPort 1887 } 1888 ::= { tn3270eTcpConnTable 1 } 1890 Tn3270eTcpConnEntry ::= 1891 SEQUENCE 1892 { 1893 tn3270eTcpConnRemAddrType IANATn3270eAddrType, 1894 tn3270eTcpConnRemAddress Tn3270eTAddress, 1895 tn3270eTcpConnRemPort Unsigned32, 1896 tn3270eTcpConnLocalAddrType IANATn3270eAddrType, 1897 tn3270eTcpConnLocalAddress Tn3270eTAddress, 1898 tn3270eTcpConnLocalPort Unsigned32, 1899 tn3270eTcpConnLastActivity TimeTicks, 1900 tn3270eTcpConnBytesIn Counter32, 1901 tn3270eTcpConnBytesOut Counter32, 1902 tn3270eTcpConnResourceElement SnaResourceName, 1903 tn3270eTcpConnResourceType Tn3270ResourceType, 1904 tn3270eTcpConnDeviceType Tn3270DeviceTypes, 1905 tn3270eTcpConnFunctions IANATn3270Functions, 1906 tn3270eTcpConnId Unsigned32, 1907 tn3270eTcpConnClientIdFormat IANATn3270eClientType, 1908 tn3270eTcpConnClientId OCTET STRING, 1909 tn3270eTcpConnTraceData Tn3270eTraceData, 1910 tn3270eTcpConnLogInfo IANATn3270eLogData, 1911 tn3270eTcpConnLuLuBindImage OCTET STRING, 1912 tn3270eTcpConnSnaState INTEGER, 1913 tn3270eTcpConnStateLastDiscReason INTEGER, 1914 tn3270eTcpConnSrvrConfIndex Unsigned32, 1915 tn3270eTcpConnActivationTime TimeStamp 1916 } 1918 tn3270eTcpConnRemAddrType OBJECT-TYPE 1919 SYNTAX IANATn3270eAddrType 1920 MAX-ACCESS not-accessible 1921 STATUS current 1922 DESCRIPTION 1923 "Indicates the type of the value of the 1924 tn3270eTcpConnRemAddress object. For example, 1925 ipv4(1) or ipv6(2)." 1926 ::= { tn3270eTcpConnEntry 1 } 1928 tn3270eTcpConnRemAddress OBJECT-TYPE 1929 SYNTAX Tn3270eTAddress 1930 MAX-ACCESS not-accessible 1931 STATUS current 1932 DESCRIPTION 1933 "The remote address associated with a TN3270E client. 1934 tn3270eTcpConnRemAddrType indicates the address type 1935 (IPv4 or IPv6, for example). 1937 If a TN3270(E) client is connected to its 1938 server via a proxy client the address represented by 1939 the value of this object shall be the remote client's 1940 address, not the proxy client's address." 1941 ::= { tn3270eTcpConnEntry 2 } 1943 tn3270eTcpConnRemPort OBJECT-TYPE 1944 SYNTAX Unsigned32 (1..65535) 1945 MAX-ACCESS not-accessible 1946 STATUS current 1947 DESCRIPTION 1948 "The remote port associated with a TN3270E client. 1950 If a TN3270(E) client is connected to its 1951 server via a proxy client the port represented by 1952 the value of this object shall be the remote client's 1953 port, not the proxy client's port." 1954 ::= { tn3270eTcpConnEntry 3 } 1956 tn3270eTcpConnLocalAddrType OBJECT-TYPE 1957 SYNTAX IANATn3270eAddrType 1958 MAX-ACCESS not-accessible 1959 STATUS current 1960 DESCRIPTION 1961 "Indicates the type of the value of the 1962 tn3270eTcpConnLocalAddress object. For example, 1963 ipv4(1) or ipv6(2)." 1964 ::= { tn3270eTcpConnEntry 4 } 1966 tn3270eTcpConnLocalAddress OBJECT-TYPE 1967 SYNTAX Tn3270eTAddress 1968 MAX-ACCESS not-accessible 1969 STATUS current 1970 DESCRIPTION 1971 "The local address associated with a TN3270E client. 1972 tn3270eTcpConnRemAddrType indicates the address type 1973 (IPv4 or IPv6, for example)." 1974 ::= { tn3270eTcpConnEntry 5 } 1976 tn3270eTcpConnLocalPort OBJECT-TYPE 1977 SYNTAX Unsigned32 (1..65535) 1978 MAX-ACCESS not-accessible 1979 STATUS current 1980 DESCRIPTION 1981 "The remote port associated with a TN3270E client." 1982 ::= { tn3270eTcpConnEntry 6 } 1984 tn3270eTcpConnLastActivity OBJECT-TYPE 1985 SYNTAX TimeTicks 1986 MAX-ACCESS read-only 1987 STATUS current 1988 DESCRIPTION 1989 "The number of 100ths of seconds since any data was 1990 transferred for the associated TCP Connection." 1991 DEFVAL { 0 } 1992 ::= { tn3270eTcpConnEntry 7 } 1994 tn3270eTcpConnBytesIn OBJECT-TYPE 1995 SYNTAX Counter32 1996 UNITS "octets" 1997 MAX-ACCESS read-only 1998 STATUS current 1999 DESCRIPTION 2000 "The number of bytes received by the server from TCP 2001 for this connection. 2003 A Management Station can detect discontinuities in 2004 this counter by monitoring the 2005 tn3270eTcpConnActivationTime object." 2006 ::= { tn3270eTcpConnEntry 8 } 2008 tn3270eTcpConnBytesOut OBJECT-TYPE 2009 SYNTAX Counter32 2010 UNITS "octets" 2011 MAX-ACCESS read-only 2012 STATUS current 2013 DESCRIPTION 2014 "The number of bytes sent to TCP for this connection. 2016 A Management Station can detect discontinuities in 2017 this counter by monitoring the 2018 tn3270eTcpConnActivationTime object." 2019 ::= { tn3270eTcpConnEntry 9 } 2021 tn3270eTcpConnResourceElement OBJECT-TYPE 2022 SYNTAX SnaResourceName 2023 MAX-ACCESS read-only 2024 STATUS current 2025 DESCRIPTION 2026 "LU/Print secondary name for connecting an client 2027 into an SNA network." 2028 ::= { tn3270eTcpConnEntry 10 } 2030 tn3270eTcpConnResourceType OBJECT-TYPE 2031 SYNTAX Tn3270ResourceType 2032 MAX-ACCESS read-only 2033 STATUS current 2034 DESCRIPTION 2035 "Indicates the type of resource identified by 2036 tn3270eTcpConnResourceElement." 2037 ::= { tn3270eTcpConnEntry 11 } 2039 tn3270eTcpConnDeviceType OBJECT-TYPE 2040 SYNTAX Tn3270DeviceTypes 2041 MAX-ACCESS read-only 2042 STATUS current 2043 DESCRIPTION 2044 "Indicates the device type if negotiated with the 2045 client. A value of unknown(0) should be used as the 2046 value of this object when a device type is not 2047 negotiated. Refer to RFC 1647 for how device types 2048 can be negotiated." 2049 ::= { tn3270eTcpConnEntry 12 } 2051 tn3270eTcpConnFunctions OBJECT-TYPE 2052 SYNTAX IANATn3270Functions 2053 MAX-ACCESS read-only 2054 STATUS current 2055 DESCRIPTION 2056 "This object indicates which of the TN3270 and TN3270E 2057 functions were negotiated by the server and the client 2058 for this TCP connection. 2060 Refer to tn3270eSrvrFunctionsSupported for the list of 2061 these functions supported by the server." 2062 ::= { tn3270eTcpConnEntry 13 } 2064 tn3270eTcpConnId OBJECT-TYPE 2065 SYNTAX Unsigned32 2066 MAX-ACCESS read-only 2067 STATUS current 2068 DESCRIPTION 2069 "The connection identifier associated with a TN3270 or 2070 a TN3270E session's TCP connection. TCP implementations 2071 often assign a unique (with respect to itself) unsigned 2072 integer as an identifier for a TCP connection. 2074 The value 0 indicates that a connection does not have 2075 a valid connection identifier." 2076 ::= { tn3270eTcpConnEntry 14 } 2078 tn3270eTcpConnClientIdFormat OBJECT-TYPE 2079 SYNTAX IANATn3270eClientType 2080 MAX-ACCESS read-only 2081 STATUS current 2082 DESCRIPTION 2083 "The format of a corresponding tn3270eTcpConnClientId 2084 object as defined by the IANSTn3270eClientType 2085 textual convention imported from the 2086 IANATn3270eTC-MIB." 2087 ::= { tn3270eTcpConnEntry 15 } 2089 tn3270eTcpConnClientId OBJECT-TYPE 2090 SYNTAX OCTET STRING (SIZE (0..512)) 2091 MAX-ACCESS read-only 2092 STATUS current 2093 DESCRIPTION 2094 "Additional client identification information. The 2095 type of this information is indicated by the value of 2096 the corresponding tn3270eTcpConnClientIdFormat object. 2097 All values are returned in network-byte order. 2099 The purpose of this object is to provide an alternate 2100 means of identifying a client, other than though the 2101 remote address returned in tn3270eTcpConnRemAddress." 2102 ::= { tn3270eTcpConnEntry 16 } 2104 tn3270eTcpConnTraceData OBJECT-TYPE 2105 SYNTAX Tn3270eTraceData 2106 MAX-ACCESS read-only 2107 STATUS current 2108 DESCRIPTION 2109 "Trace data for this session." 2110 ::= { tn3270eTcpConnEntry 17 } 2112 tn3270eTcpConnLogInfo OBJECT-TYPE 2113 SYNTAX IANATn3270eLogData 2114 MAX-ACCESS read-only 2115 STATUS current 2116 DESCRIPTION 2117 "Log information, encoded as specified in the 2118 IANATn3270eLogData textual convention from the 2119 IANAtn3270eTC-MIB." 2120 ::= { tn3270eTcpConnEntry 18 } 2122 tn3270eTcpConnLuLuBindImage OBJECT-TYPE 2123 SYNTAX OCTET STRING (SIZE (0..256)) 2124 MAX-ACCESS read-only 2125 STATUS current 2126 DESCRIPTION 2127 "When there is a currently active LU-LU session for 2128 this connection, this object returns the BIND Image 2129 (defined to be bytes 1-p of the complete BIND Request 2130 Unit -- see 'SNA Formats' for more information) 2131 that was received from the PLU during session 2132 activation. When there is no active LU-LU session, 2133 or when a BIND image is unavailable for some other 2134 reason, this object returns a zero-length octet 2135 string." 2136 REFERENCE 2137 "'Systems Network Architecture Formats', IBM 2138 Publication GA27-3136." 2139 ::= { tn3270eTcpConnEntry 19 } 2141 tn3270eTcpConnSnaState OBJECT-TYPE 2142 SYNTAX INTEGER { 2143 unknown(0), 2144 noSluSession(1), 2145 sscpLuSession(2), -- but no LU-LU session 2146 luLuSession(3), -- but no SSCP-LU session 2147 sscpLuSessionAndLuLuSession(4) 2148 } 2149 MAX-ACCESS read-only 2150 STATUS current 2151 DESCRIPTION 2152 "The current state of the SNA side of the end-to-end 2153 TN3270 connection. The following states are defined: 2155 unknown(0) - The true state is not known. 2156 noSluSession(1) - The SLU has neither an SSCP-LU 2157 nor an LU-LU session active. 2158 sscpLuSession(2) - The SSCP-LU session for the SLU 2159 is active, but the SLU is not 2160 currently in session with a PLU. 2161 luLuSession(3) - The SLU is currently in session 2162 with a PLU, but the SSCP-LU 2163 session for the LU is not active. 2164 sscpLuSessionAndLuLuSession(4) - The SLU currently has 2165 an active session with a PLU, 2166 and the SSCP-LU session for the 2167 SLU is active." 2169 ::= { tn3270eTcpConnEntry 20 } 2171 tn3270eTcpConnStateLastDiscReason OBJECT-TYPE 2172 SYNTAX INTEGER { 2173 unknown(0), 2174 hostSendsUnbind(1), 2175 hostDontAcceptConnection(2), 2176 outOfResource(3), 2177 clientProtocolError(4), 2178 invalidDeviceName(5), 2179 deviceInUse(6), 2180 inactivityTimeout(7), 2181 hostNotResponding(8), 2182 clientNotResponding(9), 2183 serverClose(10), 2184 sysreqLogoff(11), 2185 serverSpecificHexCode(12) 2186 } 2187 MAX-ACCESS read-only 2188 STATUS current 2189 DESCRIPTION 2190 "The last disconnect reason. A session that has not 2191 experienced a disconnect shall use the value unknown(0) 2192 for this object. Depending on when an implementation 2193 removes entries from this table, certain states may 2194 never be returned." 2195 ::= { tn3270eTcpConnEntry 21 } 2197 tn3270eTcpConnSrvrConfIndex OBJECT-TYPE 2198 SYNTAX Unsigned32 (1..4294967295) 2199 MAX-ACCESS read-only 2200 STATUS current 2201 DESCRIPTION 2202 "tn3270eSrvrConfIndex of the tn3270eSrvrConfEntry 2203 belonging to the TN3270E server to which this entry 2204 belongs." 2205 ::= { tn3270eTcpConnEntry 22 } 2207 tn3270eTcpConnActivationTime OBJECT-TYPE 2208 SYNTAX TimeStamp 2209 MAX-ACCESS read-only 2210 STATUS current 2211 DESCRIPTION 2212 "The value of the sysUpTime object the last time 2213 this TCP connection became active." 2214 ::= { tn3270eTcpConnEntry 23 } 2216 tn3270eConfSpinLock OBJECT-TYPE 2217 SYNTAX TestAndIncr 2218 MAX-ACCESS read-write 2219 STATUS current 2220 DESCRIPTION 2221 "An advisory lock used to allow cooperating 2222 TN3270E-MIB applications to coordinate their use 2223 of the tn3270eSrvrConfTable, the tn3270eSrvrPortTable, 2224 the tn3270eClientGroupTable, the tn3270eResPoolTable, 2225 and the tn3270eClientResMapTable. 2227 When creating a new entry or altering an existing entry 2228 in the any of the tables mentioned above, an application 2229 should make use of tn3270eRtSpinLock to serialize 2230 application changes or additions. 2232 Since this is an advisory lock, the use of this lock is 2233 not enforced." 2234 ::= { tn3270eObjects 10 } 2236 -- Conformance Definitions 2238 tn3270eGroups OBJECT IDENTIFIER ::= { tn3270eConformance 1 } 2240 tn3270eCompliances OBJECT IDENTIFIER ::= { tn3270eConformance 2 } 2242 -- compliance statements 2244 tn3270eCompliance MODULE-COMPLIANCE 2245 STATUS current 2246 DESCRIPTION 2247 "The compliance statement for agents that support the 2248 TN3270E-MIB." 2249 MODULE -- this module 2250 MANDATORY-GROUPS { tn3270eBasicGroup, 2251 tn3270eSessionGroup 2252 } 2253 GROUP tn3270eResMapGroup 2254 DESCRIPTION 2255 "This group is optional and provides a method of 2256 performing tn3270eClientGroup to tn3270eResPool 2257 mapping." 2259 GROUP tn3270eHiCapacityGroup 2260 DESCRIPTION 2261 "This group is optional and provides for support 2262 of high capacity counters." 2264 OBJECT tn3270eSrvrConfActivityCheck 2265 MIN-ACCESS read-only 2266 DESCRIPTION 2267 "The agent is not required to support a set to this 2268 object if the associated TN3270E server doesn't 2269 support either TIMING-MARK or NOP processing. In 2270 this case an agent should return noCheck on 2271 retrieval." 2273 OBJECT tn3270eSrvrConfTmNopInactTime 2274 MIN-ACCESS read-only 2275 DESCRIPTION 2276 "The agent is not required to support a set to this 2277 object if the functions enabled by 2278 tn3270eSrvrConfActivityCheck are not supported. 2279 An agent in this case should return a value of 0." 2281 OBJECT tn3270eSrvrConfTmNopInterval 2282 MIN-ACCESS read-only 2283 DESCRIPTION 2284 "The agent is not required to support a set to this 2285 object if the functions enabled by 2286 tn3270eSrvrConfActivityCheck are not supported. 2287 An agent in this case should return a value of 0." 2289 OBJECT tn3270eSrvrConfAdminStatus 2290 DESCRIPTION 2291 "A TN3270E server is not required to support a 2292 stopImmediate state transition." 2294 OBJECT tn3270eSrvrConfRowStatus 2295 MIN-ACCESS read-only 2296 DESCRIPTION 2297 "Write access is not required." 2299 OBJECT tn3270eSrvrConfTmTimeout 2300 MIN-ACCESS read-only 2301 DESCRIPTION 2302 "The agent is not required to support a set to this 2303 object if the functions enabled by 2304 tn3270eSrvrConfActivityCheck are not supported. 2305 An agent in this case should return a value of 0." 2307 OBJECT tn3270eSrvrPortRowStatus 2308 MIN-ACCESS read-only 2309 DESCRIPTION 2310 "Write access is not required." 2312 OBJECT tn3270eClientGroupRowStatus 2313 MIN-ACCESS read-only 2314 DESCRIPTION 2315 "Write access is not required." 2317 OBJECT tn3270eResPoolRowStatus 2318 MIN-ACCESS read-only 2319 DESCRIPTION 2320 "Write access is not required." 2322 OBJECT tn3270eClientResMapRowStatus 2323 MIN-ACCESS read-only 2324 DESCRIPTION 2325 "Write access is not required." 2327 ::= { tn3270eCompliances 1 } 2329 -- units of conformance 2331 tn3270eBasicGroup OBJECT-GROUP 2332 OBJECTS { 2333 tn3270eSrvrConfInactivityTimeout, 2334 tn3270eSrvrConfActivityCheck, 2335 tn3270eSrvrConfTmNopInactTime, 2336 tn3270eSrvrConfTmNopInterval, 2337 tn3270eSrvrFunctionsSupported, 2338 tn3270eSrvrConfAdminStatus, 2339 tn3270eSrvrConfOperStatus, 2340 tn3270eSrvrConfSessionTermState, 2341 tn3270eSrvrConfSrvrType, 2342 tn3270eSrvrConfContact, 2343 tn3270eSrvrConfRowStatus, 2344 tn3270eSrvrConfLastActTime, 2345 tn3270eSrvrConfTmTimeout, 2346 tn3270eSrvrPortRowStatus, 2347 tn3270eSrvrStatsUpTime, 2348 tn3270eSrvrStatsMaxTerms, 2349 tn3270eSrvrStatsInUseTerms, 2350 tn3270eSrvrStatsSpareTerms, 2351 tn3270eSrvrStatsMaxPtrs, 2352 tn3270eSrvrStatsInUsePtrs, 2353 tn3270eSrvrStatsSparePtrs, 2354 tn3270eSrvrStatsInConnects, 2355 tn3270eSrvrStatsConnResrceRejs, 2356 tn3270eSrvrStatsDisconnects, 2357 tn3270eSrvrStatsInOctets, 2358 tn3270eSrvrStatsOutOctets, 2359 tn3270eSrvrStatsConnErrorRejs, 2360 tn3270eClientGroupSubnetMask, 2361 tn3270eClientGroupPfxLength, 2362 tn3270eClientGroupRowStatus, 2363 tn3270eSnaMapLocalName, 2364 tn3270eSnaMapPrimaryLuName, 2365 tn3270eConfSpinLock 2366 } 2367 STATUS current 2368 DESCRIPTION 2369 "This group is mandatory for all hosts supporting the 2370 TN3270E-MIB." 2371 ::= { tn3270eGroups 1 } 2373 tn3270eSessionGroup OBJECT-GROUP 2374 OBJECTS { 2375 tn3270eResMapAddrType, 2376 tn3270eResMapAddress, 2377 tn3270eResMapPort, 2378 tn3270eResMapElementType, 2379 tn3270eResMapSscpSuppliedName, 2380 tn3270eTcpConnLastActivity, 2381 tn3270eTcpConnBytesIn, 2382 tn3270eTcpConnBytesOut, 2383 tn3270eTcpConnResourceElement, 2384 tn3270eTcpConnResourceType, 2385 tn3270eTcpConnDeviceType, 2386 tn3270eTcpConnFunctions, 2387 tn3270eTcpConnSrvrConfIndex, 2388 tn3270eTcpConnActivationTime 2389 } 2390 STATUS current 2391 DESCRIPTION 2392 "This group is mandatory for all hosts supporting the 2393 TN3270E-MIB." 2394 ::= { tn3270eGroups 2 } 2396 tn3270eResMapGroup OBJECT-GROUP 2397 OBJECTS { 2398 tn3270eResPoolElementType, 2399 tn3270eResPoolRowStatus, 2400 tn3270eClientResMapRowStatus, 2401 tn3270eTcpConnId, 2402 tn3270eTcpConnClientIdFormat, 2403 tn3270eTcpConnClientId, 2404 tn3270eTcpConnTraceData, 2405 tn3270eTcpConnLogInfo, 2406 tn3270eTcpConnLuLuBindImage, 2407 tn3270eTcpConnSnaState, 2408 tn3270eTcpConnStateLastDiscReason 2409 } 2410 STATUS current 2411 DESCRIPTION 2412 "This group is optional for all hosts supporting the 2413 TN3270E-MIB." 2414 ::= { tn3270eGroups 3 } 2416 tn3270eHiCapacityGroup OBJECT-GROUP 2417 OBJECTS { 2418 tn3270eSrvrStatsHCInOctets, 2419 tn3270eSrvrStatsHCOutOctets 2420 } 2421 STATUS current 2422 DESCRIPTION 2423 "Support of these objects is REQUIRED when the 2424 Counter32 versions can potentially wrap too 2425 frequently. This group is optional for all other 2426 hosts supporting the TN3270E-MIB. 2428 The IF-MIB (RFC 2233) requires that the 64-bit 2429 versions of its counters be implemented when an 2430 interface can support rates of around 20 million 2431 bits per second or greater. This implies a minimum 2432 wrap rate of just over 28 minutes. It is recommended 2433 that this same guideline be used for determining 2434 whether an implementation implements these objects. 2436 This group contains two objects with the syntax 2437 Counter64. An implementation that doesn't support 2438 these objects should return noSuchObject, since 2439 returning a zero is misleading." 2441 ::= { tn3270eGroups 4 } 2443 END 2445 5.0 Security Considerations 2447 Certain management information defined in this MIB may be considered 2448 sensitive in some network environments. Therefore, authentication of 2449 received SNMP requests and controlled access to management information 2450 SHOULD be employed in such environments. An authentication protocol is 2451 defined in [10]. A protocol for access control is defined in [11]. 2453 Several objects in this MIB allow write access or provide for row 2454 creation. Allowing this support in a non-secure environment can have a 2455 negative effect on network operations. It is RECOMMENDED that 2456 implementers seriously consider whether set operations or row creation 2457 should be allowed without providing, at a minimum, authentication of 2458 request origin. It is RECOMMENDED that without such support, the 2459 following objects be implemented as read-only: 2461 o tn3270eSrvrConfInactivityTimout 2462 o tn3270eSrvrConfActivityCheck 2463 o tn3270eSrvrConfActivityTimeout 2464 o tn3270eSrvrConfActivityInterval 2465 o tn3270eSrvrConfAdminStatus 2466 o tn3270eSrvrConfSessionTermState 2467 o tn3270eSrvrConfContact 2468 o tn3270eClientGroupSubnetMask 2469 o tn3270eResPoolElementType 2470 o tn3270eSrvrConfRowStatus 2471 o tn3270eSrvrPortRowStatus 2472 o tn3270eClientGroupRowStatus 2473 o tn3270eResPoolRowStatus 2474 o tn3270eResMapRowStatus 2476 For all tables in the MIB except the tn3270eTcpConnTable, the first 2477 index identifies an individual TN3270E server. This makes it easy to 2478 implement an access control policy under which different principals have 2479 access to objects related to different servers. Implementation of such 2480 a policy is not possible for the entries in the tn3270eTcpConTable. 2482 6.0 Intellectual Property 2484 The IETF takes no position regarding the validity or scope of any 2485 intellectual property or other rights that might be claimed to pertain 2486 to the implementation or use of the technology described in this 2487 document or the extent to which any license under such rights might or 2488 might not be available; neither does it represent that it has made any 2489 effort to identify any such rights. Information on the IETF's 2490 procedures with respect to rights in standards-track and 2491 standards-related documentation can be found in BCP-11. Copies of 2492 claims of rights made available for publication and any assurances of 2493 licenses to be made available, or the result of an attempt made to 2494 obtain a general license or permission for the use of such proprietary 2495 rights by implementers or users of this specification can be obtained 2496 from the IETF Secretariat. 2498 The IETF invites any interested party to bring to its attention any 2499 copyrights, patents or patent applications, or other proprietary rights 2500 which may cover technology that may be required to practice this 2501 standard. Please address the information to the IETF Executive 2502 Director. 2504 7.0 Acknowledgments 2506 This document is a product of the TN3270E Working Group. Thanks to 2507 Randy Presuhn of BMC Software for his valuable review comments on 2508 several versions of the document. 2510 8.0 References 2512 [1] Case, J., M. Fedor, M. Schoffstall, J. Davin, "Simple Network 2513 Management Protocol", RFC 1157, SNMP Research, Performance Systems 2514 International, MIT Laboratory for Computer Science, May 1990. 2516 [2] McCloghrie, K., and M. Rose, Editors, "Management Information Base 2517 for Network Management of TCP/IP-based internets: MIB-II", STD 17, 2518 RFC 1213, Hughes LAN Systems, Performance Systems International, 2519 March 1991. 2521 [3] Case, J., McCloghrie, K., Rose, M., and Waldbusser S., "Structure 2522 of Management Information for Version 2 of the Simple Network 2523 Management Protocol (SNMPv2)", RFC 1902, January 1996. 2525 [4] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Textual 2526 Conventions for Version 2 of the Simple Network Management Protocol 2527 (SNMPv2)", RFC 1903, January 1996. 2529 [5] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., 2530 "Conformance Statements for Version 2 of the Simple Network 2531 Management Protocol (SNMPv2)", RFC 1904, January 1996. 2533 [6] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Protocol 2534 Operations for Version 2 of the Simple Network Management Protocol 2535 (SNMPv2)", RFC 1905, January 1996. 2537 [7] Harrington D., Presuhn, R., Wijnen, B., "An Architecture for 2538 Describing SNMP Management Frameworks", RFC 2271, Cabletron 2539 Systems, BMC Software, Inc., IBM T.J. Watson Research, January 2540 1998. 2542 [8] Harrington D., Presuhn, R., Wijnen, B., "Message Processing and 2543 Dispatching for the Simple Network Management Protocol (SNMP)", RFC 2544 2272, Cabletron Systems, BMC Software, Inc., IBM T.J. Watson 2545 Research, January 1998. 2547 [9] Levi D., Meyer P., Stewart, B., "SNMPv3 Applications", RFC 2273, 2548 SNMP Research, Inc., Secure Computing Corporation, Cisco Systems, 2549 January 1998. 2551 [10] Blumenthal, U., Wijnen, B., "User-based Security Model (USM) for 2552 version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 2553 2274, IBM T. J. Watson Research, January 1998. 2555 [11] Wijnen, B., Presuhn, R., McCloghrie, K., "View-based Access Control 2556 Model (VACM) for the Simple Network Management Protocol (SNMP)", 2557 RFC 2275, IBM T.J. Watson Research, BMC Software, Inc., Cisco 2558 Systems, Inc., January 1998. 2560 [12] Postel, J., and Reynolds, J., "Telnet Protocol Specification", RFC 2561 854, May 1983. 2563 [13] Postel, J., and Reynolds, J., "Telnet Timing Mark Option", RFC 860, 2564 May 1983. 2566 [14] Rekhter, J., "Telnet 3270 Regime Option", RFC 1041, January 1988. 2568 [15] Kelly, B., "TN3270 Enhancements", RFC 1647, July 1994. 2570 [16] McCloghrie, K., "TCP-MIB Definitions", RFC 2012, November 1996. 2572 [17] Hovey, R., and S. Bradner, "The Organizations Involved in the IETF 2573 Standards Process", BCP 11, RFC 2028, October 1996. 2575 [18] Bradner, S., "Key words for use in RFCs to Indicate Requirement 2576 Levels", BCP 14, RFC 2119, March 1997. 2578 [19] Hinden, R., Deering, S., "IP Version 6 Addressing Architecture", 2579 , July 16, 1997. 2581 [20] Krupczak, Cheryl, Saperia, Jonathan, "Definitions of System-Level 2582 Managed Objects for Applications", RFC 2287, February 1998. 2584 9.0 Authors' Addresses 2586 Kenneth D. White 2587 Dept. BRQA/Bldg. 501/G114 2588 IBM Corporation 2589 P.O.Box 12195 2590 3039 Cornwallis 2591 Research Triangle Park, NC 27709, USA 2592 E-mail: kennethw@vnet.ibm.com 2594 Robert Moore 2595 Dept. BRQA/Bldg. 501/G114 2596 IBM Corporation 2597 P.O.Box 12195 2598 3039 Cornwallis 2599 Research Triangle Park, NC 27709, USA 2600 Phone: +1-919-254-4436 2601 E-mail: remoore@us.ibm.com 2603 10.0 Full Copyright Statement 2605 Copyright (C) The Internet Society (1997). All Rights Reserved. 2607 This document and translations of it may be copied and furnished to 2608 others, and derivative works that comment on or otherwise explain it or 2609 assist in its implementation may be prepared, copied, published and 2610 distributed, in whole or in part, without restriction of any kind, 2611 provided that the above copyright notice and this paragraph are included 2612 on all such copies and derivative works. However, this document itself 2613 may not be modified in any way, such as by removing the copyright notice 2614 or references to the Internet Society or other Internet organizations, 2615 except as needed for the purpose of developing Internet standards in 2616 which case the procedures for copyrights defined in the Internet 2617 Standards process must be followed, or as required to translate it into 2618 languages other than English. 2620 The limited permissions granted above are perpetual and will not be 2621 revoked by the Internet Society or its successors or assigns. 2623 This document and the information contained herein is provided on an "AS 2624 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK 2625 FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT 2626 LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT 2627 INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR 2628 FITNESS FOR A PARTICULAR PURPOSE. 2630 Appendix A. IANATn3270eTC-MIB 2632 This appendix defines the current content of the IANATn3270eTC-MIB. 2633 This section should be removed from this document prior to its approval, 2634 at which time this MIB will be administered by IANA. 2636 IANATn3270eTC-MIB DEFINITIONS ::= BEGIN 2638 IMPORTS 2639 MODULE-IDENTITY, experimental 2640 FROM SNMPv2-SMI 2641 TEXTUAL-CONVENTION 2642 FROM SNMPv2-TC; 2644 ianaTn3270eTcMib MODULE-IDENTITY 2645 LAST-UPDATED "9802020000Z" -- February 2, 1998 2646 ORGANIZATION "IANA" 2647 CONTACT-INFO 2648 "Internet Assigned Numbers Authority 2650 Postal: USC/Information Sciences Institute 2651 4676 Admiralty Way, Marina del Rey, CA 90292 2653 Tel: +1 310 822 1511 2654 E-Mail: iana@isi.edu" 2655 DESCRIPTION 2656 "This module defines a set of textual conventions 2657 for use by the TN3270E-MIB and the TN3270E-RT-MIB. 2659 Any additions or changes to the contents of this 2660 MIB module must first be discussed on the tn3270e 2661 working group list at: tn3270e@list.nih.gov 2662 and approved by one of the following TN3270E 2663 working group contacts: 2665 Ed Bailey (co-chair) - elbailey@us.ibm.com 2666 Michael Boe (co-chair) - mboe@cisco.com 2667 Ken White - kennethw@vnet.ibm.com 2668 Robert Moore - remoore@us.ibm.com 2670 The above list of contacts can be altered with 2671 the approval of the two co-chairs. 2673 The Textual Conventions defined within this MIB have 2674 no security issues associated with them unless 2675 explicitly stated in their corresponding 2676 DESCRIPTION clause." 2677 -- IANA will assign a real OID when they take over this module. 2678 ::= { experimental 2001 } 2680 -- Textual Conventions 2682 IANATn3270eAddrType ::= TEXTUAL-CONVENTION 2683 STATUS current 2684 DESCRIPTION 2685 "The textual convention for defining the type of a 2686 client address. The enumeration value unknown(0) is 2687 usually used to indicate that no actual address is 2688 present." 2689 SYNTAX INTEGER { 2690 unknown(0), 2691 ipv4(1), 2692 ipv6(2) 2693 } 2695 IANATn3270Functions ::= TEXTUAL-CONVENTION 2696 STATUS current 2697 DESCRIPTION 2698 "This textual convention reflects the current set of 2699 TN3270 and TN3270E functions that can be negotiated 2700 between a server and its client: 2702 RFC856 2703 transmitBinary The sender of this command REQUESTS 2704 permission to begin transmitting, or 2705 confirms that it will now begin 2706 transmitting characters which are to 2707 be interpreted as 8 bits of binary 2708 data by the receiver of the data. 2709 RFC860 2710 timingMark The sender of this command REQUESTS 2711 that the receiver of this command 2712 return a WILL TIMING-MARK in the data 2713 stream at the 'appropriate place'. 2714 RFC885 2715 endOfRecord The sender of this command requests 2716 permission to begin transmission of 2717 the Telnet END-OF-RECORD (EOR) code 2718 when transmitting data characters, or 2719 the sender of this command confirms it 2720 will now begin transmission of EORs 2721 with transmitted data characters. 2722 RFC1091 2723 terminalType Sender is willing to send terminal 2724 type information in a subsequent 2725 sub-negotiation. 2726 RFC1041 2727 tn3270Regime Sender is willing to send list of 2728 supported 3270 Regimes in a 2729 subsequent sub-negotiation. 2730 RFC1647 2731 scsCtlCodes (Printer sessions only). Allows the 2732 use of the SNA Character Stream (SCS) 2733 and SCS control codes on the session. 2734 SCS is used with LU type 1 SNA sessions. 2735 dataStreamCtl (Printer sessions only). Allows the use 2736 of the standard 3270 data stream. This 2737 corresponds to LU type 3 SNA sessions. 2739 responses Provides support for positive and 2740 negative response handling. Allows the 2741 server to reflect to the client any and 2742 all definite, exception, and no response 2743 requests sent by the host application. 2744 bindImage Allows the server to send the SNA Bind 2745 image and Unbind notification to the 2746 client. 2747 sysreq Allows the client and server to emulate 2748 some (or all, depending on the server) of 2749 the functions of the SYSREQ key in an SNA 2750 environment." 2751 SYNTAX BITS { 2752 transmitBinary(0),-- rfc856 2753 timemark(1), -- rfc860 2754 endOfRecord(2), -- rfc885 2755 terminalType(3), -- rfc1091 2756 tn3270Regime(4), -- rfc1041 2757 scsCtlCodes(5), -- rfc1647 2758 dataStreamCtl(6), -- rfc1647 2759 responses(7), -- rfc1647 2760 bindImage(8), -- rfc1647 2761 sysreq(9) -- rfc1647 2762 } 2764 IANATn3270eClientType ::= TEXTUAL-CONVENTION 2765 STATUS current 2766 DESCRIPTION 2767 "The textual convention for defining the set of 2768 enumerations used by tn3270eTcpConnClientIdFormat 2769 in the TN3270E-MIB: 2771 ENUMERATION OCTETs DESCRIPTION 2773 none(0) 0 Not specified 2774 other(1) 1..512 Implementation specific 2775 ipv4(2) 6 4-octet IP Address plus 2776 2-octet TCP Port 2777 ipv6(3) 18 16-octet IPv6 Address 2778 plus 2-octet TCP Port 2779 domainName(4) 1..512 The DNS name of a 2780 client. 2781 truncDomainName(5) 1..512 The (truncated) DNS name 2782 of a client. 2783 string(6) 1..512 Unknown Utf8String 2784 certificate(7) 1..512 certificate 2785 userId(8) 1..8 Client's userid 2786 x509dn(9) 1..512 X.509 Distinguished Name 2788 Representation of a certificate(7) may be lead to 2789 a security exposure and is NOT RECOMMENDED without 2790 adequate security." 2791 SYNTAX INTEGER { 2792 none(0), 2793 other(1), 2794 ipv4(2), 2795 ipv6(3), 2796 domainName(4), 2797 truncDomainName(5), 2798 string(6), 2799 certificate(7), 2800 userId(8), 2801 x509dn(9) 2802 } 2804 IANATn3270eLogData ::= TEXTUAL-CONVENTION 2805 STATUS current 2806 DESCRIPTION 2807 "An octet string representing log data as pertaining to 2808 either a TN3270 or TN3270E Session as reported from a 2809 TN3270E Server. Log data is stored in an octet string 2810 in time order (from earliest to latest). 2812 Each log element has the following form: 2814 +------+----+---------+------------+ 2815 !length!type!TimeStamp! data ! 2816 +------+----+---------+------------+ 2818 where 2820 length = one-octet length of the data portion of the 2821 trace element, not including the length, 2822 type, and TimeStamp fields 2823 type = one-octet code point characterizing the data. 2824 TimeStamp = A 4-octet field representing the number of 2825 TimeTicks since the TN3270E server was last 2826 activated. The server's last activation time 2827 is available in the tn3270eSrvrConfLastActTime 2828 object in the TN3270E MIB, which has the 2829 syntax DateAndTime. 2830 data = initial part of a PDU. 2832 length type 2834 0-255 x'00' - unknown 2835 0 x'01' - inactivity timer expired 2836 0 x'02' - dynamic timer expired 2837 0 x'03' - actlu req 2838 0 x'04' - bind req 2839 0 x'05' - clear req 2840 0 x'06' - dactlu req 2841 0 x'07' - warm actpu req 2842 0 x'08' - sdt req 2843 0 x'09' - unbind req 2844 0 x'0A' - notify resp 2845 0 x'0B' - reply PSID neg rsp 2846 0 x'0C' - reply PSID pos rsp 2847 0 x'0D' - unbind rsp 2848 0 x'0E' - hierarchical reset 2849 0 x'0F' - client connect req 2850 0 x'10' - client disconnect req 2851 0 x'11' - timingmark received 2852 0 x'12' - flowControl timer expired 2853 0 x'13' - neg rsp to host 2854 0 x'14' - neg rsp from host 2855 0 x'15' - data contention 2856 0 x'16' - no buffer to send SNA data 2857 0 x'17' - receive response while inbound 2858 0 x'18' - client protocol error 2859 0 x'19' - badClientSequenceReceived 2860 1-255 x'1A' - utf8String 2861 2 x'1B' - hexCode, implementation dependent 2863 log event entries have a minimum length of 6 octets. 2864 The zero-length string indicates that no log data is 2865 available." 2866 SYNTAX OCTET STRING (SIZE (0 | 6..2048)) 2868 END