idnits 2.17.1 draft-ietf-tn3270e-tn3270-mib-09.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 are 2 instances 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 1109 has weird spacing: '...ddrType unkn...' == Line 1110 has weird spacing: '...Address zer...' == Line 1116 has weird spacing: '...ddrType unkn...' == Line 1117 has weird spacing: '...Address zer...' == Line 1123 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 (June 1998) is 9437 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 2588, but no explicit reference was found in the text == Unused Reference: '19' is defined on line 2594, 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: December, 1998 Robert Moore 4 IBM Corp. 5 June 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 . . . . . . . . . . . . . . . . . . . 46 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 . . . . . . . . . . . . . . . . . . 49 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 tn3270eSrvrConfConnectivityChk 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 tn3270eSrvrConfConnectivityChk 237 allows a Management Station to select either a NOP command or a 238 TIMING-MARK command. Sending a NOP command results in less overhead 239 then a 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 "9806050000Z" -- June 5, 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 implementation-dependent where the 'initial part of 616 a PDU' starts. For SNA data, however, the starting point 617 SHOULD be the first byte of the TH. For IP data the 618 starting point SHOULD be the first byte of the IP header. 620 It is left to implementations to determine how much of 621 each PDU to return in a trace element. 623 The zero-length string indicates that no trace 624 data is available." 625 SYNTAX OCTET STRING (SIZE (0 | 3..4096)) 627 -- Top-level structure of the MIB 629 tn3270eNotifications OBJECT IDENTIFIER ::= { tn3270eMIB 0 } 630 tn3270eObjects OBJECT IDENTIFIER ::= { tn3270eMIB 1 } 631 tn3270eConformance OBJECT IDENTIFIER ::= { tn3270eMIB 3 } 633 -- MIB Objects 635 tn3270eSrvrConfTable OBJECT-TYPE 636 SYNTAX SEQUENCE OF Tn3270eSrvrConfEntry 637 MAX-ACCESS not-accessible 638 STATUS current 639 DESCRIPTION 640 "This table defines the configuration elements for 641 TN3270E servers. The number of entries in this table 642 is expected to vary depending on the location of the 643 table. A particular TN3270E server is expected to 644 have a single entry. Modeling of the configuration 645 elements as a table allows multiple TN3270E 646 servers to be serviced by the same SNMP agent. 648 An implementation SHOULD NOT retain an SNMP-created 649 entry in this table across re-IPLs (Initial Program 650 Loads) of the corresponding TN3270E server." 652 ::= { tn3270eObjects 1 } 654 tn3270eSrvrConfEntry OBJECT-TYPE 655 SYNTAX Tn3270eSrvrConfEntry 656 MAX-ACCESS not-accessible 657 STATUS current 658 DESCRIPTION 659 "Definition of the configuration elements for a single 660 TN3270E server." 661 INDEX { tn3270eSrvrConfIndex } 662 ::= { tn3270eSrvrConfTable 1 } 664 Tn3270eSrvrConfEntry ::= SEQUENCE { 665 tn3270eSrvrConfIndex Unsigned32, 666 tn3270eSrvrConfInactivityTimeout Unsigned32, 667 tn3270eSrvrConfConnectivityChk INTEGER, 668 tn3270eSrvrConfTmNopInactTime Unsigned32, 669 tn3270eSrvrConfTmNopInterval Unsigned32, 670 tn3270eSrvrFunctionsSupported IANATn3270Functions, 671 tn3270eSrvrConfAdminStatus INTEGER, 672 tn3270eSrvrConfOperStatus INTEGER, 673 tn3270eSrvrConfSessionTermState INTEGER, 674 tn3270eSrvrConfSrvrType INTEGER, 675 tn3270eSrvrConfContact SnmpAdminString, 676 tn3270eSrvrConfRowStatus RowStatus, 677 tn3270eSrvrConfLastActTime DateAndTime, 678 tn3270eSrvrConfTmTimeout Unsigned32 679 } 681 tn3270eSrvrConfIndex OBJECT-TYPE 682 SYNTAX Unsigned32 (1..4294967295) 683 MAX-ACCESS not-accessible 684 STATUS current 685 DESCRIPTION 686 "Identifier for a single TN3270E server. 688 tn3270eSrvrConfIndex values need not be 689 contiguous." 690 ::= { tn3270eSrvrConfEntry 1 } 692 tn3270eSrvrConfInactivityTimeout OBJECT-TYPE 693 SYNTAX Unsigned32 (0..99999999) 694 UNITS "seconds" 695 MAX-ACCESS read-create 696 STATUS current 697 DESCRIPTION 698 "The inactivity time-out specified in seconds. When a 699 connection has been inactive for the number of seconds 700 specified by this object it is closed. Only user traffic 701 is considered when determining whether there has been 702 activity on a connection. 704 The default value 0 means that no inactivity time-out is 705 in effect." 706 DEFVAL { 0 } 707 ::= { tn3270eSrvrConfEntry 2 } 709 tn3270eSrvrConfConnectivityChk OBJECT-TYPE 710 SYNTAX INTEGER { 711 noCheck(0), 712 timingMark(1), 713 nop(2) 714 } 715 MAX-ACCESS read-create 716 STATUS current 717 DESCRIPTION 718 "This object enables TIMING-MARK processing, NOP 719 processing, or neither for a TN3270E server." 720 DEFVAL { noCheck } 721 ::= { tn3270eSrvrConfEntry 3 } 723 tn3270eSrvrConfTmNopInactTime OBJECT-TYPE 724 SYNTAX Unsigned32 (1..86400) -- 1 second to 24 hours 725 UNITS "seconds" 726 MAX-ACCESS read-create 727 STATUS current 728 DESCRIPTION 729 "The amount of time a connection must have had no 730 traffic on it in order for a TIMING-MARK or NOP request 731 to be sent on the connection. This value applies only 732 when connections are being examined for recent activity 733 on a scan interval controlled by the value of the 734 tn3270eSrvrConfTmNopInterval object." 735 DEFVAL { 600 } -- 10 minutes 736 ::= { tn3270eSrvrConfEntry 4 } 738 tn3270eSrvrConfTmNopInterval OBJECT-TYPE 739 SYNTAX Unsigned32 (1..86400) -- 1 second to 24 hours 740 UNITS "seconds" 741 MAX-ACCESS read-create 742 STATUS current 743 DESCRIPTION 744 "The scan interval to be used by a TN3270E server when 745 it examines its Telnet connections for recent activity. 746 The server scans its Telnet connections on the interval 747 provided by this object, looking for ones that have been 748 idle for more than the value provided by the 749 tn3270eSrvrConfTmNopInactTime object. A TIMING-MARK or 750 NOP request is sent for each connection that has 751 exhibited no activity for this period of time." 752 DEFVAL { 120 } -- 2 minutes 753 ::= { tn3270eSrvrConfEntry 5 } 755 tn3270eSrvrFunctionsSupported OBJECT-TYPE 756 SYNTAX IANATn3270Functions 757 MAX-ACCESS read-only 758 STATUS current 759 DESCRIPTION 760 "This object indicates the functions supported by a 761 TN3270E server." 762 DEFVAL { { scsCtlCodes, dataStreamCtl, 763 responses, bindImage, sysreq } } 764 ::= { tn3270eSrvrConfEntry 6 } 766 tn3270eSrvrConfAdminStatus OBJECT-TYPE 767 SYNTAX INTEGER { 768 up(1), 769 down(2), 770 stopImmediate(3) 771 } 772 MAX-ACCESS read-create 773 STATUS current 774 DESCRIPTION 775 "The desired state of the TN3270E server represented 776 by this entry in the table: 778 up(1) - Activate this TN3270E server. 779 down(2) - Informs the associated TN3270E 780 server to gracefully terminate 781 its processing. 782 stopImmediate(3) - Informs the associated TN3270E 783 server to terminate itself 784 immediately. 786 When a managed system creates an entry in this table, 787 tn3270eSrvrConfAdminStatus and tn3270eSrvrConfOperStatus 788 are initialized as up(1) by default. 790 The exact behavior of a server in response to a down(2) 791 or stopImmediate(3) command is left implementation- 792 dependent. A TN3270E server that is capable of it 793 SHOULD close all of its TN3270 and TN3270E sessions 794 during a graceful termination. 796 Often the function enabled via stopImmediate(3) is used 797 as a last resort by a system administrator, to attempt 798 to either bring down a hung TN3270E server or free up 799 its resources immediately to aid in general system 800 availability, or to shut down a TN3270E server that is 801 not recognizing a down(2) request. 803 A TN3270E server that does not distinguish between 804 down(2) or stopImmediate(3) transitions should not 805 support stopImmediate(3)." 807 DEFVAL { up } 808 ::= { tn3270eSrvrConfEntry 7 } 810 tn3270eSrvrConfOperStatus OBJECT-TYPE 811 SYNTAX INTEGER { 812 up(1), 813 down(2), 814 busy(3), 815 shuttingDown(4) 816 } 817 MAX-ACCESS read-only 818 STATUS current 819 DESCRIPTION 820 "The current operational state of a TN3270E server. 821 The following values are defined: 823 up(1) - the server is active and accepting 824 new client connections 825 down(2) - the server is not active 826 busy(3) - the server is active, but is not 827 accepting new client connections 828 because it lacks the resources to 829 do so 830 shuttingDown(4) - the server is active, but is not 831 accepting new client connections 832 because it is in the process of 833 performing a graceful shutdown." 834 DEFVAL { up } 835 ::= { tn3270eSrvrConfEntry 8 } 837 tn3270eSrvrConfSessionTermState OBJECT-TYPE 838 SYNTAX INTEGER { 839 terminate(1), 840 luSessionPend(2), 841 queueSession(3) 842 } 843 MAX-ACCESS read-create 844 STATUS current 845 DESCRIPTION 846 "This object determines what a TN3270E server 847 should do when a TN3270 Session terminates: 849 terminate(1) => Terminate the TCP connection. 850 luSessionPend(2) => Do not drop the TCP connection 851 associated with a client when its 852 TN3270 session ends. Processing 853 should redrive session initialization 854 as if the client were first connecting. 855 queueSession(3) => This value relates to the Close 856 Destination PASS (CLSDST PASS) operation 857 in VTAM. An example provides the 858 easiest explanation. Suppose a TN3270E 859 client is in session with APPL1, and 860 APPL1 does a CLSDST PASS of the client's 861 session to APPL2. queueSession(3) 862 specifies that the TN3270E server must 863 keep the TCP connection with the client 864 active after it receives the UNBIND from 865 APPL1, waiting for the BIND from APPL2." 866 DEFVAL { terminate } 867 ::= { tn3270eSrvrConfEntry 9 } 869 tn3270eSrvrConfSrvrType OBJECT-TYPE 870 SYNTAX INTEGER { 871 host(1), 872 gateway(2) 873 } 874 MAX-ACCESS read-only 875 STATUS current 876 DESCRIPTION 877 "This object indicates the type of TN3270E server. 878 The existence of MIB tables and objects that will be 879 defined by follow-on MIBs may be predicated on whether 880 the TN3270E server can be local to the same host as a 881 target application (host(1)) or will always be remote 882 (gateway(2)). 884 A host TN3270E server refers to an implementation where 885 the TN3270E server is collocated with the Systems 886 Network Architecture (SNA) System Services Control Point 887 (SSCP) for the dependent Secondary Logical Units (SLUs) 888 that the server makes available to its clients for 889 connecting into an SNA network. 891 A gateway TN3270E server resides on an SNA node other 892 than an SSCP, either an SNA type 2.0 node or an APPN node 893 acting in the role of a Dependent LU Requester (DLUR). 895 Host and gateway TN3270E server implementations typically 896 differ greatly as to their internal implementation and 897 system definition (SYSDEF) requirements." 898 ::= { tn3270eSrvrConfEntry 10 } 900 tn3270eSrvrConfContact OBJECT-TYPE 901 SYNTAX SnmpAdminString 902 MAX-ACCESS read-create 903 STATUS current 904 DESCRIPTION 905 "This object provides a scratch pad for a TN3270E 906 server administrator for storing information for 907 later retrieval." 908 DEFVAL { ''H } -- the empty string 909 ::= { tn3270eSrvrConfEntry 11 } 911 tn3270eSrvrConfRowStatus OBJECT-TYPE 912 SYNTAX RowStatus 913 MAX-ACCESS read-create 914 STATUS current 915 DESCRIPTION 916 "This object allows entries to be created and deleted 917 in the tn3270eSrvrConfTable. Entries may also be 918 created and deleted as a result of implementation- 919 dependent operations. 921 With the exception of tn3270eSrvrConfSrvrType, which 922 an implementation can easily fill in for itself, all 923 the columnar objects in this table have DEFVALs 924 associated with them. Consequently, a Management 925 Station can create a conceptual row via a SET 926 operation that specifies a value only for this object. 928 When a tn3270eSrvrConfEntry is deleted (by setting 929 this object to destroy(6)), this has the side-effect 930 of removing all the associated entries (i.e., those 931 having the same tn3270eSrvrConfIndex) from the 932 tn3270eSrvrPortTable, the tn3270eSrvrStatsTable, the 933 tn3270eClientGroupTable, the tn3270eResPoolTable, 934 the tn3270eSnaMapTable, the tn3270eClientResMapTable, 935 and the tn3270eResMapTable. All entries in the 936 tn3270eTcpConnTable that belong to a TN3270E server 937 that has been deleted MUST also be removed. 939 In other words, a tn3270eSrvrConfEntry must exist for 940 a TN3270E server in order for it to have entries in 941 any of the other tables defined by this MIB." 942 REFERENCE 943 "RFC 1903, 'Textual Conventions for version 2 of the 944 Simple Network Management Protocol (SNMPv2).'" 945 ::= { tn3270eSrvrConfEntry 12 } 947 tn3270eSrvrConfLastActTime OBJECT-TYPE 948 SYNTAX DateAndTime 949 MAX-ACCESS read-only 950 STATUS current 951 DESCRIPTION 952 "This object reports the DateAndTime when a TN3270E 953 server was most recently activated. 955 The special value of all '00'Hs indicates that the 956 server has never been active, i.e., that the value of 957 tn3270eSrvrOperStatus has never been anything other 958 than down(2)." 959 DEFVAL { '0000000000000000'H } 960 ::= { tn3270eSrvrConfEntry 13 } 962 tn3270eSrvrConfTmTimeout OBJECT-TYPE 963 SYNTAX Unsigned32 (1..600) -- 1 second to 10 minutes 964 UNITS "seconds" 965 MAX-ACCESS read-create 966 STATUS current 967 DESCRIPTION 968 "The TIMING-MARK time-out, specified in seconds." 969 DEFVAL { 5 } -- 5 seconds 970 ::= { tn3270eSrvrConfEntry 14 } 972 tn3270eSrvrPortTable OBJECT-TYPE 973 SYNTAX SEQUENCE OF Tn3270eSrvrPortEntry 974 MAX-ACCESS not-accessible 975 STATUS current 976 DESCRIPTION 977 "This table defines the TCP ports associated with 978 TN3270E servers. No entry in this table shall exist 979 without a corresponding (same tn3270eSrvrConfIndex) 980 entry in the tn3270eSrvrConfTable existing. 982 An implementation SHOULD NOT retain SNMP-created 983 entries in this table across re-IPLs (Initial Program 984 Loads) of the corresponding TN3270E server." 985 ::= { tn3270eObjects 2 } 987 tn3270eSrvrPortEntry OBJECT-TYPE 988 SYNTAX Tn3270eSrvrPortEntry 989 MAX-ACCESS not-accessible 990 STATUS current 991 DESCRIPTION 992 "Definition of a single TCP port assignment to a 993 TN3270E server. Assignment of a port on a local 994 address basis is enabled though use of 995 tn3270eSrvrPortAddrType and tn3270eSrvrPortAddress. 997 A TCP port assignment that is not restricted to 998 a local address SHALL specify a tn3270eSrvrPortAddrType 999 of unknown(0), and SHALL use a zero-length octet string 1000 for the tn3270eSrvrPortAddress." 1001 INDEX { 1002 tn3270eSrvrConfIndex, 1003 tn3270eSrvrPort, 1004 tn3270eSrvrPortAddrType, 1005 tn3270eSrvrPortAddress 1006 } 1007 ::= { tn3270eSrvrPortTable 1 } 1009 Tn3270eSrvrPortEntry ::= SEQUENCE { 1010 tn3270eSrvrPort Unsigned32, 1011 tn3270eSrvrPortAddrType IANATn3270eAddrType, 1012 tn3270eSrvrPortAddress Tn3270eTAddress, 1013 tn3270eSrvrPortRowStatus RowStatus 1014 } 1016 tn3270eSrvrPort OBJECT-TYPE 1017 SYNTAX Unsigned32 (0..65535) 1018 MAX-ACCESS not-accessible 1019 STATUS current 1020 DESCRIPTION 1021 "Indicates a port assigned to a server." 1022 ::= { tn3270eSrvrPortEntry 1 } 1024 tn3270eSrvrPortAddrType OBJECT-TYPE 1025 SYNTAX IANATn3270eAddrType 1026 MAX-ACCESS not-accessible 1027 STATUS current 1028 DESCRIPTION 1029 "Indicates the type of an address local to the host on 1030 which the TN3270E server resides that is represented 1031 in tn3270eSrvrPortAddress. A value of unknown(0) 1032 SHALL be used for this object when the port is not 1033 to be restricted to a local address." 1034 ::= { tn3270eSrvrPortEntry 2 } 1036 tn3270eSrvrPortAddress OBJECT-TYPE 1037 SYNTAX Tn3270eTAddress 1038 MAX-ACCESS not-accessible 1039 STATUS current 1040 DESCRIPTION 1041 "A local address on the host that a TN3270E server 1042 resides on that is associated with a TCP port that 1043 is to be used or is in use by a TN3270E server. 1044 tn3270eClientGroupAddrType indicates the 1045 address type (IPv4 or IPv6, for example). 1047 A zero-length octet string SHALL be used as the 1048 value of this object when a local address isn't 1049 being specified." 1050 ::= { tn3270eSrvrPortEntry 3 } 1052 tn3270eSrvrPortRowStatus OBJECT-TYPE 1053 SYNTAX RowStatus 1054 MAX-ACCESS read-create 1055 STATUS current 1056 DESCRIPTION 1057 "This object allows entries to be created and deleted 1058 in the tn3270eSrvrPortTable. Entries may also be 1059 created and deleted as a result of implementation- 1060 dependent operations. 1062 Since this is the only accessible object in this table, 1063 a Management Station can create a conceptual row via a SET 1064 operation that specifies a value only for this object. 1066 An entry in this table is deleted by setting this object 1067 to destroy(6). Deletion of a tn3270eSrvrPortEntry has 1068 no effect on any other table entry defined by this MIB." 1069 REFERENCE 1070 "RFC 1903, 'Textual Conventions for version 2 of the 1071 Simple Network Management Protocol (SNMPv2).'" 1072 ::= { tn3270eSrvrPortEntry 4 } 1074 tn3270eSrvrStatsTable OBJECT-TYPE 1075 SYNTAX SEQUENCE OF Tn3270eSrvrStatsEntry 1076 MAX-ACCESS not-accessible 1077 STATUS current 1078 DESCRIPTION 1079 "This table defines a set of statistics concerning 1080 TN3270E server performance. 1082 No entry in this table shall exist without 1083 a corresponding (same tn3270eSrvrConfIndex) entry in 1084 the tn3270eSrvrConfTable existing." 1085 ::= { tn3270eObjects 3 } 1087 tn3270eSrvrStatsEntry OBJECT-TYPE 1088 SYNTAX Tn3270eSrvrStatsEntry 1089 MAX-ACCESS not-accessible 1090 STATUS current 1091 DESCRIPTION 1092 "A collection of statistical and maximum usage objects 1093 for a single TN3270 server. An entry can represent the total 1094 activity of the server, or it can represent the activity 1095 occurring at the server on either a port or a 1096 port-and-local-address basis. 1098 Collection of the statistics represented by the objects 1099 in this table is not mandatory. An implementation 1100 of this table MUST use only one of the three levels of 1101 refinement that this table supports for the entries 1102 associated with each TN3270E server. 1104 The indexing for a row that represents total server 1105 statistics is as follows: 1107 tn3270eSrvrConfIndex value identifying the server 1108 tn3270eSrvrPort 0 1109 tn3270eSrvrPortAddrType unknown(0) 1110 tn3270eSrvrPortAddress zero-length octet string. 1112 On a port basis: 1114 tn3270eSrvrConfIndex value identifying the server 1115 tn3270eSrvrPort > 0 1116 tn3270eSrvrPortAddrType unknown(0) 1117 tn3270eSrvrPortAddress zero-length octet string. 1119 On a port-and-local-address basis: 1121 tn3270eSrvrConfIndex value identifying the server 1122 tn3270eSrvrPort > 0 1123 tn3270eSrvrPortAddrType valid value other than unknown(0) 1124 tn3270eSrvrPortAddress non-zero-length octet string. 1126 " 1127 INDEX { 1128 tn3270eSrvrConfIndex, 1129 tn3270eSrvrPort, 1130 tn3270eSrvrPortAddrType, 1131 tn3270eSrvrPortAddress 1132 } 1133 ::= { tn3270eSrvrStatsTable 1 } 1135 Tn3270eSrvrStatsEntry ::= SEQUENCE { 1136 tn3270eSrvrStatsUpTime TimeStamp, 1137 tn3270eSrvrStatsMaxTerms Unsigned32, 1138 tn3270eSrvrStatsInUseTerms Gauge32, 1139 tn3270eSrvrStatsSpareTerms Gauge32, 1140 tn3270eSrvrStatsMaxPtrs Unsigned32, 1141 tn3270eSrvrStatsInUsePtrs Gauge32, 1142 tn3270eSrvrStatsSparePtrs Gauge32, 1143 tn3270eSrvrStatsInConnects Counter32, 1144 tn3270eSrvrStatsConnResrceRejs Counter32, 1145 tn3270eSrvrStatsDisconnects Counter32, 1146 tn3270eSrvrStatsHCInOctets Counter64, 1147 tn3270eSrvrStatsInOctets Counter32, 1148 tn3270eSrvrStatsHCOutOctets Counter64, 1149 tn3270eSrvrStatsOutOctets Counter32, 1150 tn3270eSrvrStatsConnErrorRejs Counter32 1151 } 1153 tn3270eSrvrStatsUpTime OBJECT-TYPE 1154 SYNTAX TimeStamp 1155 MAX-ACCESS read-only 1156 STATUS current 1157 DESCRIPTION 1158 "The value of the sysUpTime object the last time 1159 the TN3270E server was re-initialized. 1161 Server re-initialization is the only discontinuity 1162 event for the counters in this table. Even if table 1163 entries are on a port or port-and-local-address 1164 basis, port deactivation and reactivation do not 1165 result in counter discontinuities." 1166 ::= { tn3270eSrvrStatsEntry 2 } 1168 tn3270eSrvrStatsMaxTerms OBJECT-TYPE 1169 SYNTAX Unsigned32 1170 UNITS "LUs" 1171 MAX-ACCESS read-only 1172 STATUS current 1173 DESCRIPTION 1174 "Indicates the maximum number of terminal LUs available 1175 for use at a TN3270E server for the granularity of this 1176 conceptual row (server-wide, port, or 1177 port-and-local-address)." 1178 ::= { tn3270eSrvrStatsEntry 3 } 1180 tn3270eSrvrStatsInUseTerms OBJECT-TYPE 1181 SYNTAX Gauge32 1182 UNITS "LUs" 1183 MAX-ACCESS read-only 1184 STATUS current 1185 DESCRIPTION 1186 "Indicates the number of terminal LUs currently in 1187 use at a TN3270E server for the granularity of this 1188 conceptual row (server-wide, port, or 1189 port-and-local-address)." 1190 ::= { tn3270eSrvrStatsEntry 4 } 1192 tn3270eSrvrStatsSpareTerms OBJECT-TYPE 1193 SYNTAX Gauge32 1194 UNITS "LUs" 1195 MAX-ACCESS read-only 1196 STATUS current 1197 DESCRIPTION 1198 "Indicates the number of free terminal LUs at a TN3270E 1199 server for the granularity of this conceptual row 1200 (server-wide, port, or port-and-local-address). 1202 It is possible that the difference between 1203 tn3270eSrvrStatsMaxTerms and tn3270eSrvrStatsInUseTerms 1204 in a conceptual row does not equal the value of 1205 tn3270eSrvrStatsSpareTerms in that row: an LU may 1206 exist but not be usable by a client connection. 1208 Alternatively, the administrative ceiling represented 1209 by tn3270eSrvrStatsMaxTerms may have been lowered to 1210 a point where it is less than the current value of 1211 tn3270eSrvrStatsInUseTerms. In this case 1212 tn3270eSrvrStatsSpareTerms returns the value 0." 1214 ::= { tn3270eSrvrStatsEntry 5 } 1216 tn3270eSrvrStatsMaxPtrs OBJECT-TYPE 1217 SYNTAX Unsigned32 1218 UNITS "Printer Resources" 1219 MAX-ACCESS read-only 1220 STATUS current 1221 DESCRIPTION 1222 "Indicates the maximum number of printer resources 1223 available for use by a TN3270E server for the 1224 granularity of this conceptual row (server-wide, 1225 port, or port-and-local-address)." 1226 ::= { tn3270eSrvrStatsEntry 6 } 1228 tn3270eSrvrStatsInUsePtrs OBJECT-TYPE 1229 SYNTAX Gauge32 1230 UNITS "Printer Resources" 1231 MAX-ACCESS read-only 1232 STATUS current 1233 DESCRIPTION 1234 "Indicates the number of printer resources 1235 currently in use by a TN3270E server for the 1236 granularity of this conceptual row (server-wide, 1237 port, or port-and-local-address)." 1238 ::= { tn3270eSrvrStatsEntry 7 } 1240 tn3270eSrvrStatsSparePtrs OBJECT-TYPE 1241 SYNTAX Gauge32 1242 UNITS "Spare Printer Resources" 1243 MAX-ACCESS read-only 1244 STATUS current 1245 DESCRIPTION 1246 "Indicates the number of free printer resources at 1247 a TN3270E server for the granularity of this conceptual 1248 row (server-wide, port, or port-and-local-address). 1250 It is possible that the difference between 1251 tn3270eSrvrStatsMaxPtrs and tn3270eSrvrStatsInUsePtrs 1252 in a conceptual row does not equal the value of 1253 tn3270eSrvrStatsSparePtrs in that row: a printer 1254 resource may exist but not be usable by a client 1255 connection. 1257 Alternatively, the administrative ceiling represented 1258 by tn3270eSrvrStatsMaxPtrs may have been lowered to 1259 a point where it is less than the current value of 1260 tn3270eSrvrStatsInUsePtrs. In this case 1261 tn3270eSrvrStatsSparePtrs returns the value 0." 1262 ::= { tn3270eSrvrStatsEntry 8 } 1264 tn3270eSrvrStatsInConnects OBJECT-TYPE 1265 SYNTAX Counter32 1266 UNITS "connections" 1267 MAX-ACCESS read-only 1268 STATUS current 1269 DESCRIPTION 1270 "Indicates the number of client (TCP) connections 1271 that succeeded at a TN3270E server for the 1272 granularity of this conceptual row (server-wide, 1273 port, or port-and-local-address). 1275 The tn3270eSrvrStatsConnResrceRejs and 1276 tn3270eSrvrStatsConnErrorRejs objects provide a count 1277 of failed connection attempts. 1279 A Management Station can detect discontinuities in 1280 this counter by monitoring the tn3270eSrvrStatsUpTime 1281 object." 1282 ::= { tn3270eSrvrStatsEntry 9 } 1284 tn3270eSrvrStatsConnResrceRejs OBJECT-TYPE 1285 SYNTAX Counter32 1286 UNITS "connection attempts" 1287 MAX-ACCESS read-only 1288 STATUS current 1289 DESCRIPTION 1290 "Indicates the number of (TCP) connections rejected 1291 during connection setup at a TN3270E server for the 1292 granularity of this conceptual row (server-wide, 1293 port, or port-and-local-address) due to a lack of 1294 resources at the server. An example of when this 1295 counter would be incremented is when no terminal 1296 or printer resource is available to associate with a 1297 client's TCP connection. 1299 A Management Station can detect discontinuities in 1300 this counter by monitoring the tn3270eSrvrStatsUpTime 1301 object." 1303 ::= { tn3270eSrvrStatsEntry 10 } 1305 tn3270eSrvrStatsDisconnects OBJECT-TYPE 1306 SYNTAX Counter32 1307 UNITS "disconnections" 1308 MAX-ACCESS read-only 1309 STATUS current 1310 DESCRIPTION 1311 "Indicates the number of (TCP) connections that were 1312 disconnected at a TN3270E server for the 1313 granularity of this conceptual row (server-wide, 1314 port, or port-and-local-address). 1316 A Management Station can detect discontinuities in 1317 this counter by monitoring the tn3270eSrvrStatsUpTime 1318 object." 1319 ::= { tn3270eSrvrStatsEntry 11 } 1321 tn3270eSrvrStatsHCInOctets OBJECT-TYPE 1322 SYNTAX Counter64 1323 UNITS "octets" 1324 MAX-ACCESS read-only 1325 STATUS current 1326 DESCRIPTION 1327 "Indicates the number of octets received from TN3270 1328 and TN3270E clients for the granularity of this 1329 conceptual row (server-wide, port, or 1330 port-and-local-address). 1332 A Management Station can detect discontinuities in 1333 this counter by monitoring the tn3270eSrvrStatsUpTime 1334 object." 1335 ::= { tn3270eSrvrStatsEntry 12 } 1337 tn3270eSrvrStatsInOctets OBJECT-TYPE 1338 SYNTAX Counter32 1339 UNITS "octets" 1340 MAX-ACCESS read-only 1341 STATUS current 1342 DESCRIPTION 1343 "Low-order 32 bits of tn3270eSrvrStatsHCInOctets for 1344 this conceptual row. 1346 A Management Station can detect discontinuities in 1347 this counter by monitoring the tn3270eSrvrStatsUpTime 1348 object." 1349 ::= { tn3270eSrvrStatsEntry 13 } 1351 tn3270eSrvrStatsHCOutOctets OBJECT-TYPE 1352 SYNTAX Counter64 1353 UNITS "octets" 1354 MAX-ACCESS read-only 1355 STATUS current 1356 DESCRIPTION 1357 "Indicates the number of octets sent to TN3270 1358 and TN3270E clients for the granularity of this 1359 conceptual row (server-wide, port, or 1360 port-and-local-address). 1362 A Management Station can detect discontinuities in 1363 this counter by monitoring the tn3270eSrvrStatsUpTime 1364 object." 1365 ::= { tn3270eSrvrStatsEntry 14 } 1367 tn3270eSrvrStatsOutOctets OBJECT-TYPE 1368 SYNTAX Counter32 1369 UNITS "octets" 1370 MAX-ACCESS read-only 1371 STATUS current 1372 DESCRIPTION 1373 "Low-order 32 bits of tn3270eSrvrStatsHCOutOctets for 1374 this conceptual row. 1376 A Management Station can detect discontinuities in 1377 this counter by monitoring the tn3270eSrvrStatsUpTime 1378 object." 1379 ::= { tn3270eSrvrStatsEntry 15 } 1381 tn3270eSrvrStatsConnErrorRejs OBJECT-TYPE 1382 SYNTAX Counter32 1383 UNITS "connection attempts" 1384 MAX-ACCESS read-only 1385 STATUS current 1386 DESCRIPTION 1387 "Indicates the number of (TCP) connections rejected 1388 during connection setup at a TN3270E server for the 1389 granularity of this conceptual row (server-wide, 1390 port, or port-and-local-address) due to an error 1391 of some type. An example of when this counter would 1392 be incremented is when the client and the server 1393 cannot agree on a common set of TN3270E functions for 1394 the connection. 1396 A Management Station can detect discontinuities in 1397 this counter by monitoring the tn3270eSrvrStatsUpTime 1398 object." 1399 ::= { tn3270eSrvrStatsEntry 16 } 1401 tn3270eClientGroupTable OBJECT-TYPE 1402 SYNTAX SEQUENCE OF Tn3270eClientGroupEntry 1403 MAX-ACCESS not-accessible 1404 STATUS current 1405 DESCRIPTION 1406 "This table defines client address groupings for use 1407 by a TN3270E server. 1409 No entry in this table shall exist without 1410 a corresponding (same tn3270eSrvrConfIndex) entry in 1411 the tn3270eSrvrConfTable existing. 1413 An implementation SHOULD NOT retain SNMP-created 1414 entries in this table across re-IPLs (Initial Program 1415 Loads) of the corresponding TN3270E server." 1416 ::= { tn3270eObjects 4 } 1418 tn3270eClientGroupEntry OBJECT-TYPE 1419 SYNTAX Tn3270eClientGroupEntry 1420 MAX-ACCESS not-accessible 1421 STATUS current 1422 DESCRIPTION 1423 "Definition of a single client address entry. All 1424 entries with the same first two indexes, 1425 tn3270eSrvrConfIndex and tn3270eClientGroupName, are 1426 considered to be in the same client group." 1427 INDEX { tn3270eSrvrConfIndex, 1428 tn3270eClientGroupName, 1429 tn3270eClientGroupAddrType, 1430 tn3270eClientGroupAddress } 1431 ::= { tn3270eClientGroupTable 1 } 1433 Tn3270eClientGroupEntry ::= SEQUENCE { 1434 tn3270eClientGroupName Utf8String, 1435 tn3270eClientGroupAddrType IANATn3270eAddrType, 1436 tn3270eClientGroupAddress Tn3270eTAddress, 1437 tn3270eClientGroupSubnetMask IpAddress, 1438 tn3270eClientGroupPfxLength Unsigned32, 1439 tn3270eClientGroupRowStatus RowStatus 1440 } 1442 tn3270eClientGroupName OBJECT-TYPE 1443 SYNTAX Utf8String (SIZE(1..24)) 1444 MAX-ACCESS not-accessible 1445 STATUS current 1446 DESCRIPTION 1447 "The name of a client group. Note: client group 1448 names are required to be unique only with respect 1449 to a single TN3270E server." 1450 ::= { tn3270eClientGroupEntry 1 } 1452 tn3270eClientGroupAddrType OBJECT-TYPE 1453 SYNTAX IANATn3270eAddrType 1454 MAX-ACCESS not-accessible 1455 STATUS current 1456 DESCRIPTION 1457 "Indicates the type of the address represented in 1458 tn3270eClientGroupAddress." 1459 ::= { tn3270eClientGroupEntry 2 } 1461 tn3270eClientGroupAddress OBJECT-TYPE 1462 SYNTAX Tn3270eTAddress 1463 MAX-ACCESS not-accessible 1464 STATUS current 1465 DESCRIPTION 1466 "The client address of a member of a client group. 1467 The value of tn3270eClientGroupAddrType indicates 1468 the address type (IPv4 or IPv6, for example)." 1469 ::= { tn3270eClientGroupEntry 3 } 1471 tn3270eClientGroupSubnetMask OBJECT-TYPE 1472 SYNTAX IpAddress 1473 MAX-ACCESS read-create 1474 STATUS current 1475 DESCRIPTION 1476 "The corresponding subnet mask associated with 1477 tn3270eClientGroupAddress. A single IP address is 1478 represented by having this object contain the value 1479 of 255.255.255.255. 1481 This object's value is meaningful only if 1482 tn3270eClientGroupAddrType has a value of ipv4(1)." 1483 DEFVAL { 'FFFFFFFF'H } 1484 ::= { tn3270eClientGroupEntry 4 } 1486 tn3270eClientGroupPfxLength OBJECT-TYPE 1487 SYNTAX Unsigned32 (0..128) 1488 UNITS "bits" 1489 MAX-ACCESS read-create 1490 STATUS current 1491 DESCRIPTION 1492 "The corresponding IPv6 network prefix length. 1494 This object's value is meaningful only if 1495 tn3270eClientGroupAddrType has a value of ipv6(2)." 1496 DEFVAL { 0 } 1497 ::= { tn3270eClientGroupEntry 5 } 1499 tn3270eClientGroupRowStatus OBJECT-TYPE 1500 SYNTAX RowStatus 1501 MAX-ACCESS read-create 1502 STATUS current 1503 DESCRIPTION 1504 "This object allows entries to be created and deleted 1505 in the tn3270eClientGroupTable. Entries may also be 1506 created and deleted as a result of implementation- 1507 dependent operations. 1509 An entry in this table is deleted by setting this object 1510 to destroy(6). When the number of entries in this table 1511 for a given client group becomes 0, this has the side- 1512 effect of removing any entries for the group in the 1513 tn3270eClientResMapTable." 1514 REFERENCE 1515 "RFC 1903, 'Textual Conventions for version 2 of the 1516 Simple Network Management Protocol (SNMPv2).'" 1517 ::= { tn3270eClientGroupEntry 6 } 1519 tn3270eResPoolTable OBJECT-TYPE 1520 SYNTAX SEQUENCE OF Tn3270eResPoolEntry 1521 MAX-ACCESS not-accessible 1522 STATUS current 1523 DESCRIPTION 1524 "This table defines resource groupings; the term 1525 'pool' is used as it is defined by RFC 1647. 1527 No entry in this table shall exist without 1528 a corresponding (same tn3270eSrvrConfIndex) entry in 1529 the tn3270eSrvrConfTable existing. 1531 An implementation SHOULD NOT retain SNMP-created 1532 entries in this table across re-IPLs (Initial Program 1533 Loads) of the corresponding TN3270E server." 1534 ::= { tn3270eObjects 5 } 1536 tn3270eResPoolEntry OBJECT-TYPE 1537 SYNTAX Tn3270eResPoolEntry 1538 MAX-ACCESS not-accessible 1539 STATUS current 1540 DESCRIPTION 1541 "Definition of a single resource pool member. All entries 1542 with the same first two indexes, tn3270eSrvrConfIndex and 1543 tn3270eResPoolName, are considered to be in the same pool." 1544 INDEX { tn3270eSrvrConfIndex, 1545 tn3270eResPoolName, 1546 tn3270eResPoolElementName } 1547 ::= { tn3270eResPoolTable 1 } 1549 Tn3270eResPoolEntry ::= SEQUENCE { 1550 tn3270eResPoolName Utf8String, 1551 tn3270eResPoolElementName SnaResourceName, 1552 tn3270eResPoolElementType Tn3270ResourceType, 1553 tn3270eResPoolRowStatus RowStatus 1554 } 1556 tn3270eResPoolName OBJECT-TYPE 1557 SYNTAX Utf8String (SIZE(1..24)) 1558 MAX-ACCESS not-accessible 1559 STATUS current 1560 DESCRIPTION 1561 "The name of a resource pool." 1562 ::= { tn3270eResPoolEntry 1 } 1564 tn3270eResPoolElementName OBJECT-TYPE 1565 SYNTAX SnaResourceName 1566 MAX-ACCESS not-accessible 1567 STATUS current 1568 DESCRIPTION 1569 "The name of a member of a resource pool." 1570 ::= { tn3270eResPoolEntry 2 } 1572 tn3270eResPoolElementType OBJECT-TYPE 1573 SYNTAX Tn3270ResourceType 1574 MAX-ACCESS read-create 1575 STATUS current 1576 DESCRIPTION 1577 "The type of the entity in a resource pool." 1579 ::= { tn3270eResPoolEntry 3 } 1581 tn3270eResPoolRowStatus OBJECT-TYPE 1582 SYNTAX RowStatus 1583 MAX-ACCESS read-create 1584 STATUS current 1585 DESCRIPTION 1586 "This object allows entries to be created and deleted 1587 in the tn3270eResPoolTable. Entries may also be 1588 created and deleted as a result of implementation- 1589 dependent operations. 1591 An entry in this table is deleted by setting this object 1592 to destroy(6). When all entries in this table associated 1593 with the same tn3270eResPoolElementName have been removed, 1594 then any associated (tn3270eResPoolElementName matching 1595 tn3270eClientResMapPoolName with same tn3270eSrvrConfIndex 1596 values) entries in the tn3270eClientResMapTable SHALL 1597 also be removed." 1598 REFERENCE 1599 "RFC 1903, 'Textual Conventions for version 2 of the 1600 Simple Network Management Protocol (SNMPv2).'" 1601 ::= { tn3270eResPoolEntry 4 } 1603 tn3270eSnaMapTable OBJECT-TYPE 1604 SYNTAX SEQUENCE OF Tn3270eSnaMapEntry 1605 MAX-ACCESS not-accessible 1606 STATUS current 1607 DESCRIPTION 1608 "This table provide a mapping from the name by which 1609 a secondary LU is known in the SNA network to the 1610 name by which it is known locally at the TN3270e 1611 server. This latter name serves as an index into 1612 the tn3270eResPoolTable and the tn3270eResMapTable. 1614 No entry in this table shall exist without 1615 a corresponding (same tn3270eSrvrConfIndex) entry in 1616 the tn3270eSrvrConfTable existing." 1617 ::= { tn3270eObjects 6 } 1619 tn3270eSnaMapEntry OBJECT-TYPE 1620 SYNTAX Tn3270eSnaMapEntry 1621 MAX-ACCESS not-accessible 1622 STATUS current 1623 DESCRIPTION 1624 "Definition of a single mapping from an SSCP-supplied 1625 SLU name to a local SLU name. 1627 Note: In certain pathological cases, it is possible 1628 that an SSCP will send on an ACTLU for a local LU an 1629 SLU name currently represented by an entry in this 1630 table that associates it with a different local LU. 1631 In these cases the association from the newer ACTLU 1632 SHOULD be the one represented in this table." 1633 INDEX { tn3270eSrvrConfIndex, 1634 tn3270eSnaMapSscpSuppliedName } 1635 ::= { tn3270eSnaMapTable 1 } 1637 Tn3270eSnaMapEntry ::= SEQUENCE { 1638 tn3270eSnaMapSscpSuppliedName SnaResourceName, 1639 tn3270eSnaMapLocalName SnaResourceName, 1640 tn3270eSnaMapPrimaryLuName SnaResourceName 1641 } 1643 tn3270eSnaMapSscpSuppliedName OBJECT-TYPE 1644 SYNTAX SnaResourceName 1645 MAX-ACCESS not-accessible 1646 STATUS current 1647 DESCRIPTION 1648 "The name of the secondary LU (SLU) as it is known in 1649 the SNA network. This name is sent by the SSCP on 1650 the Activate Logical Unit (ACTLU) request." 1651 ::= { tn3270eSnaMapEntry 1 } 1653 tn3270eSnaMapLocalName OBJECT-TYPE 1654 SYNTAX SnaResourceName 1655 MAX-ACCESS read-only 1656 STATUS current 1657 DESCRIPTION 1658 "The local name of the secondary LU (SLU)." 1659 ::= { tn3270eSnaMapEntry 2 } 1661 tn3270eSnaMapPrimaryLuName OBJECT-TYPE 1662 SYNTAX SnaResourceName 1663 MAX-ACCESS read-only 1664 STATUS current 1665 DESCRIPTION 1666 "When there is a currently active LU-LU session for 1667 this connection, this object returns the primary LU 1668 (PLU) name from the BIND. When there is no active 1669 LU-LU session, or when the PLU name is unavailable 1670 for some other reason, this object returns a 1671 zero-length octet string." 1672 ::= { tn3270eSnaMapEntry 3 } 1674 tn3270eClientResMapTable OBJECT-TYPE 1675 SYNTAX SEQUENCE OF Tn3270eClientResMapEntry 1676 MAX-ACCESS not-accessible 1677 STATUS current 1678 DESCRIPTION 1679 "This table defines resource-pool to client-group 1680 mappings. Since both the resource pool name and client 1681 group name are included in the index clause of this 1682 table, multiple resource pools can be assigned to the 1683 same client group. This enables use of multiple 1684 resource pools for use in client to resource mapping. 1685 Assigning multiple client groups to the same resource 1686 pool is also allowed, but is not the primary purpose 1687 for how the indexing is structured. 1689 Assignment of a resource pool to client group can be 1690 restricted based on TCP port. An index value of 0 for 1691 tn3270eClientResMapClientPort disables restriction of 1692 resource assignment based on client target port 1693 selection. 1695 No entry in this table shall exist without 1696 a corresponding (same tn3270eSrvrConfIndex) entry in 1697 the tn3270eSrvrConfTable existing. 1699 An implementation SHOULD NOT retain SNMP-created 1700 entries in this table across re-IPLs (Initial Program 1701 Loads) of the corresponding TN3270E server." 1702 ::= { tn3270eObjects 7 } 1704 tn3270eClientResMapEntry OBJECT-TYPE 1705 SYNTAX Tn3270eClientResMapEntry 1706 MAX-ACCESS not-accessible 1707 STATUS current 1708 DESCRIPTION 1709 "Definition of a single resource pool to client group 1710 mapping." 1711 INDEX { tn3270eSrvrConfIndex, 1712 tn3270eClientResMapPoolName, 1713 tn3270eClientResMapClientGroupName, 1714 tn3270eClientResMapClientPort } 1715 ::= { tn3270eClientResMapTable 1 } 1717 Tn3270eClientResMapEntry ::= SEQUENCE { 1718 tn3270eClientResMapPoolName Utf8String, 1719 tn3270eClientResMapClientGroupName Utf8String, 1720 tn3270eClientResMapClientPort Unsigned32, 1721 tn3270eClientResMapRowStatus RowStatus 1722 } 1724 tn3270eClientResMapPoolName OBJECT-TYPE 1725 SYNTAX Utf8String (SIZE(1..24)) 1726 MAX-ACCESS not-accessible 1727 STATUS current 1728 DESCRIPTION 1729 "The name of a resource pool." 1730 ::= { tn3270eClientResMapEntry 1 } 1732 tn3270eClientResMapClientGroupName OBJECT-TYPE 1733 SYNTAX Utf8String (SIZE(1..24)) 1734 MAX-ACCESS not-accessible 1735 STATUS current 1736 DESCRIPTION 1737 "The name of the client group that is mapped to a 1738 resource pool." 1739 ::= { tn3270eClientResMapEntry 2 } 1741 tn3270eClientResMapClientPort OBJECT-TYPE 1742 SYNTAX Unsigned32 (0..65535) 1743 MAX-ACCESS not-accessible 1744 STATUS current 1745 DESCRIPTION 1746 "A port number restricting the scope of a mapping 1747 from a resource pool to a client group. The 1748 value 0 for this object indicates that the scope 1749 of the mapping is not restricted." 1750 ::= { tn3270eClientResMapEntry 3 } 1752 tn3270eClientResMapRowStatus OBJECT-TYPE 1753 SYNTAX RowStatus 1754 MAX-ACCESS read-create 1755 STATUS current 1756 DESCRIPTION 1757 "This object allows entries to be created and deleted 1758 in the tn3270eClientResMapTable. Entries may also be 1759 created and deleted as a result of implementation- 1760 dependent operations. 1762 An entry in this table is deleted by setting this object 1763 to destroy(6). Removing an entry from this table doesn't 1764 affect any other table entry defined in this MIB." 1765 REFERENCE 1766 "RFC 1903, 'Textual Conventions for version 2 of the 1767 Simple Network Management Protocol (SNMPv2).'" 1768 ::= { tn3270eClientResMapEntry 4 } 1770 tn3270eResMapTable OBJECT-TYPE 1771 SYNTAX SEQUENCE OF Tn3270eResMapEntry 1772 MAX-ACCESS not-accessible 1773 STATUS current 1774 DESCRIPTION 1775 "This table defines the actual mapping of a resource 1776 to a client address. 1778 No entry in this table shall exist without 1779 a corresponding (same tn3270eSrvrConfIndex) entry in 1780 the tn3270eSrvrConfTable existing." 1781 ::= { tn3270eObjects 8 } 1783 tn3270eResMapEntry OBJECT-TYPE 1784 SYNTAX Tn3270eResMapEntry 1785 MAX-ACCESS not-accessible 1786 STATUS current 1787 DESCRIPTION 1788 "Definition of the mapping of a Resource Element to 1789 a client address." 1790 INDEX { tn3270eSrvrConfIndex, 1791 tn3270eResMapElementName } 1792 ::= { tn3270eResMapTable 1 } 1794 Tn3270eResMapEntry ::= SEQUENCE { 1795 tn3270eResMapElementName SnaResourceName, 1796 tn3270eResMapAddrType IANATn3270eAddrType, 1797 tn3270eResMapAddress Tn3270eTAddress, 1798 tn3270eResMapPort Unsigned32, 1799 tn3270eResMapElementType Tn3270ResourceType, 1800 tn3270eResMapSscpSuppliedName SnaResourceName 1801 } 1803 tn3270eResMapElementName OBJECT-TYPE 1804 SYNTAX SnaResourceName 1805 MAX-ACCESS not-accessible 1806 STATUS current 1807 DESCRIPTION 1808 "The name of a resource element. This is the name by 1809 which the server implementing this table knows the 1810 resource. It may be different from the name by which 1811 the resource is known in the SNA network. This latter 1812 name is returned in the tn3270eResMapSscpSuppliedName 1813 object." 1814 ::= { tn3270eResMapEntry 1 } 1816 tn3270eResMapAddrType OBJECT-TYPE 1817 SYNTAX IANATn3270eAddrType 1818 MAX-ACCESS read-only 1819 STATUS current 1820 DESCRIPTION 1821 "Indicates the type of the client address represented 1822 in tn3270eResMapAddress." 1823 ::= { tn3270eResMapEntry 2 } 1825 tn3270eResMapAddress OBJECT-TYPE 1826 SYNTAX Tn3270eTAddress 1827 MAX-ACCESS read-only 1828 STATUS current 1829 DESCRIPTION 1830 "A client address." 1831 ::= { tn3270eResMapEntry 3 } 1833 tn3270eResMapPort OBJECT-TYPE 1834 SYNTAX Unsigned32 (0..65535) 1835 MAX-ACCESS read-only 1836 STATUS current 1837 DESCRIPTION 1838 "A client port." 1839 ::= { tn3270eResMapEntry 4 } 1841 tn3270eResMapElementType OBJECT-TYPE 1842 SYNTAX Tn3270ResourceType 1843 MAX-ACCESS read-only 1844 STATUS current 1845 DESCRIPTION 1846 "The type of the associated resource element." 1847 ::= { tn3270eResMapEntry 5 } 1849 tn3270eResMapSscpSuppliedName OBJECT-TYPE 1850 SYNTAX SnaResourceName 1851 MAX-ACCESS read-only 1852 STATUS current 1853 DESCRIPTION 1854 "The name of the secondary LU (SLU) as it is known 1855 in a SNA network. This name is sent by the SSCP on 1856 the Activate Logical Unit (ACTLU) request. If this 1857 name is not known, this object returns a zero-length 1858 octet string." 1859 ::= { tn3270eResMapEntry 6 } 1861 -- Define the set of objects to supplement the TCP Connection Table 1863 tn3270eTcpConnTable OBJECT-TYPE 1864 SYNTAX SEQUENCE OF Tn3270eTcpConnEntry 1865 MAX-ACCESS not-accessible 1866 STATUS current 1867 DESCRIPTION 1868 "This table has an entry for each TN3270(E) client 1869 connection that is currently active at a TN3270E server. 1870 An implementation MAY retain entries for connections 1871 that have been terminated, but which entries are 1872 retained, how many entries are retained, and how long 1873 they are retained is entirely implementation-dependent. 1875 The indexing for this table is designed to support the 1876 use of an SNMP GET-NEXT operation using only the remote 1877 address type, remote address, and remote port, as a way 1878 for a Management Station to retrieve the table entries 1879 related to a particular TN3270(E) client." 1880 ::= { tn3270eObjects 9 } 1882 tn3270eTcpConnEntry OBJECT-TYPE 1883 SYNTAX Tn3270eTcpConnEntry 1884 MAX-ACCESS not-accessible 1885 STATUS current 1886 DESCRIPTION 1887 "Provides information about a single TN3270/TN3270E 1888 session. Note: a tn3270eSrvrConfIndex is not needed 1889 in this table, since the combination of remote and 1890 local addresses and ports is sufficient to 1891 guarantee uniqueness across the TN3270E servers 1892 serviced by an SNMP agent. Because of this indexing 1893 structure, however, this table does not support 1894 view-based access control policies that provide 1895 access to table rows on a per-server basis." 1896 INDEX { tn3270eTcpConnRemAddrType, 1897 tn3270eTcpConnRemAddress, 1898 tn3270eTcpConnRemPort, 1899 tn3270eTcpConnLocalAddrType, 1900 tn3270eTcpConnLocalAddress, 1901 tn3270eTcpConnLocalPort 1902 } 1903 ::= { tn3270eTcpConnTable 1 } 1905 Tn3270eTcpConnEntry ::= 1906 SEQUENCE 1907 { 1908 tn3270eTcpConnRemAddrType IANATn3270eAddrType, 1909 tn3270eTcpConnRemAddress Tn3270eTAddress, 1910 tn3270eTcpConnRemPort Unsigned32, 1911 tn3270eTcpConnLocalAddrType IANATn3270eAddrType, 1912 tn3270eTcpConnLocalAddress Tn3270eTAddress, 1913 tn3270eTcpConnLocalPort Unsigned32, 1914 tn3270eTcpConnLastActivity TimeTicks, 1915 tn3270eTcpConnBytesIn Counter32, 1916 tn3270eTcpConnBytesOut Counter32, 1917 tn3270eTcpConnResourceElement SnaResourceName, 1918 tn3270eTcpConnResourceType Tn3270ResourceType, 1919 tn3270eTcpConnDeviceType Tn3270DeviceTypes, 1920 tn3270eTcpConnFunctions IANATn3270Functions, 1921 tn3270eTcpConnId Unsigned32, 1922 tn3270eTcpConnClientIdFormat IANATn3270eClientType, 1923 tn3270eTcpConnClientId OCTET STRING, 1924 tn3270eTcpConnTraceData Tn3270eTraceData, 1925 tn3270eTcpConnLogInfo IANATn3270eLogData, 1926 tn3270eTcpConnLuLuBindImage OCTET STRING, 1927 tn3270eTcpConnSnaState INTEGER, 1928 tn3270eTcpConnStateLastDiscReason INTEGER, 1929 tn3270eTcpConnSrvrConfIndex Unsigned32, 1930 tn3270eTcpConnActivationTime TimeStamp 1931 } 1933 tn3270eTcpConnRemAddrType OBJECT-TYPE 1934 SYNTAX IANATn3270eAddrType 1935 MAX-ACCESS not-accessible 1936 STATUS current 1937 DESCRIPTION 1938 "Indicates the type of the value of the 1939 tn3270eTcpConnRemAddress object. For example, 1940 ipv4(1) or ipv6(2)." 1941 ::= { tn3270eTcpConnEntry 1 } 1943 tn3270eTcpConnRemAddress OBJECT-TYPE 1944 SYNTAX Tn3270eTAddress 1945 MAX-ACCESS not-accessible 1946 STATUS current 1947 DESCRIPTION 1948 "The remote address associated with a TN3270E client. 1949 tn3270eTcpConnRemAddrType indicates the address type 1950 (IPv4 or IPv6, for example). 1952 If a TN3270(E) client is connected to its 1953 server via a proxy client the address represented by 1954 the value of this object shall be the remote client's 1955 address, not the proxy client's address." 1956 ::= { tn3270eTcpConnEntry 2 } 1958 tn3270eTcpConnRemPort OBJECT-TYPE 1959 SYNTAX Unsigned32 (0..65535) 1960 MAX-ACCESS not-accessible 1961 STATUS current 1962 DESCRIPTION 1963 "The remote port associated with a TN3270E client. The value 0 1964 is used if the tn3270eTcpConnRemAddrType identifies an address 1965 type that does not support ports. 1967 If a TN3270(E) client is connected to its server via a proxy 1968 client, the port represented by the value of this object shall 1969 be the remote client's port, not the proxy client's port." 1970 ::= { tn3270eTcpConnEntry 3 } 1972 tn3270eTcpConnLocalAddrType OBJECT-TYPE 1973 SYNTAX IANATn3270eAddrType 1974 MAX-ACCESS not-accessible 1975 STATUS current 1976 DESCRIPTION 1977 "Indicates the type of the value of the 1978 tn3270eTcpConnLocalAddress object. For example, 1979 ipv4(1) or ipv6(2)." 1980 ::= { tn3270eTcpConnEntry 4 } 1982 tn3270eTcpConnLocalAddress OBJECT-TYPE 1983 SYNTAX Tn3270eTAddress 1984 MAX-ACCESS not-accessible 1985 STATUS current 1986 DESCRIPTION 1987 "The local address associated with a TN3270E client. 1988 tn3270eTcpConnRemAddrType indicates the address type 1989 (IPv4 or IPv6, for example)." 1990 ::= { tn3270eTcpConnEntry 5 } 1992 tn3270eTcpConnLocalPort OBJECT-TYPE 1993 SYNTAX Unsigned32 (1..65535) 1994 MAX-ACCESS not-accessible 1995 STATUS current 1996 DESCRIPTION 1997 "The remote port associated with a TN3270E client." 1998 ::= { tn3270eTcpConnEntry 6 } 2000 tn3270eTcpConnLastActivity OBJECT-TYPE 2001 SYNTAX TimeTicks 2002 MAX-ACCESS read-only 2003 STATUS current 2004 DESCRIPTION 2005 "The number of 100ths of seconds since any data was 2006 transferred for the associated TCP Connection." 2007 DEFVAL { 0 } 2008 ::= { tn3270eTcpConnEntry 7 } 2010 tn3270eTcpConnBytesIn OBJECT-TYPE 2011 SYNTAX Counter32 2012 UNITS "octets" 2013 MAX-ACCESS read-only 2014 STATUS current 2015 DESCRIPTION 2016 "The number of bytes received by the server from TCP 2017 for this connection. 2019 A Management Station can detect discontinuities in 2020 this counter by monitoring the 2021 tn3270eTcpConnActivationTime object." 2022 ::= { tn3270eTcpConnEntry 8 } 2024 tn3270eTcpConnBytesOut OBJECT-TYPE 2025 SYNTAX Counter32 2026 UNITS "octets" 2027 MAX-ACCESS read-only 2028 STATUS current 2029 DESCRIPTION 2030 "The number of bytes sent to TCP for this connection. 2032 A Management Station can detect discontinuities in 2033 this counter by monitoring the 2034 tn3270eTcpConnActivationTime object." 2035 ::= { tn3270eTcpConnEntry 9 } 2037 tn3270eTcpConnResourceElement OBJECT-TYPE 2038 SYNTAX SnaResourceName 2039 MAX-ACCESS read-only 2040 STATUS current 2041 DESCRIPTION 2042 "LU/Print secondary name for connecting an client 2043 into an SNA network." 2044 ::= { tn3270eTcpConnEntry 10 } 2046 tn3270eTcpConnResourceType OBJECT-TYPE 2047 SYNTAX Tn3270ResourceType 2048 MAX-ACCESS read-only 2049 STATUS current 2050 DESCRIPTION 2051 "Indicates the type of resource identified by 2052 tn3270eTcpConnResourceElement." 2053 ::= { tn3270eTcpConnEntry 11 } 2055 tn3270eTcpConnDeviceType OBJECT-TYPE 2056 SYNTAX Tn3270DeviceTypes 2057 MAX-ACCESS read-only 2058 STATUS current 2059 DESCRIPTION 2060 "Indicates the device type if negotiated with the 2061 client. A value of unknown(0) should be used as the 2062 value of this object when a device type is not 2063 negotiated. Refer to RFC 1647 for how device types 2064 can be negotiated." 2065 ::= { tn3270eTcpConnEntry 12 } 2067 tn3270eTcpConnFunctions OBJECT-TYPE 2068 SYNTAX IANATn3270Functions 2069 MAX-ACCESS read-only 2070 STATUS current 2071 DESCRIPTION 2072 "This object indicates which of the TN3270 and TN3270E 2073 functions were negotiated by the server and the client 2074 for this TCP connection. 2076 Refer to tn3270eSrvrFunctionsSupported for the list of 2077 these functions supported by the server." 2078 ::= { tn3270eTcpConnEntry 13 } 2080 tn3270eTcpConnId OBJECT-TYPE 2081 SYNTAX Unsigned32 2082 MAX-ACCESS read-only 2083 STATUS current 2084 DESCRIPTION 2085 "The connection identifier associated with a TN3270 or 2086 a TN3270E session's TCP connection. TCP implementations 2087 often assign a unique (with respect to itself) unsigned 2088 integer as an identifier for a TCP connection. 2090 The value 0 indicates that a connection does not have 2091 a valid connection identifier." 2092 ::= { tn3270eTcpConnEntry 14 } 2094 tn3270eTcpConnClientIdFormat OBJECT-TYPE 2095 SYNTAX IANATn3270eClientType 2096 MAX-ACCESS read-only 2097 STATUS current 2098 DESCRIPTION 2099 "The format of a corresponding tn3270eTcpConnClientId 2100 object as defined by the IANSTn3270eClientType 2101 textual convention imported from the 2102 IANATn3270eTC-MIB." 2103 ::= { tn3270eTcpConnEntry 15 } 2105 tn3270eTcpConnClientId OBJECT-TYPE 2106 SYNTAX OCTET STRING (SIZE (0..512)) 2107 MAX-ACCESS read-only 2108 STATUS current 2109 DESCRIPTION 2110 "Additional client identification information. The 2111 type of this information is indicated by the value of 2112 the corresponding tn3270eTcpConnClientIdFormat object. 2113 All values are returned in network-byte order. 2115 The purpose of this object is to provide an alternate 2116 means of identifying a client, other than though the 2117 remote address returned in tn3270eTcpConnRemAddress." 2118 ::= { tn3270eTcpConnEntry 16 } 2120 tn3270eTcpConnTraceData OBJECT-TYPE 2121 SYNTAX Tn3270eTraceData 2122 MAX-ACCESS read-only 2123 STATUS current 2124 DESCRIPTION 2125 "Trace data for this session." 2126 ::= { tn3270eTcpConnEntry 17 } 2128 tn3270eTcpConnLogInfo OBJECT-TYPE 2129 SYNTAX IANATn3270eLogData 2130 MAX-ACCESS read-only 2131 STATUS current 2132 DESCRIPTION 2133 "Log information, encoded as specified in the 2134 IANATn3270eLogData textual convention from the 2135 IANAtn3270eTC-MIB." 2136 ::= { tn3270eTcpConnEntry 18 } 2138 tn3270eTcpConnLuLuBindImage OBJECT-TYPE 2139 SYNTAX OCTET STRING (SIZE (0..256)) 2140 MAX-ACCESS read-only 2141 STATUS current 2142 DESCRIPTION 2143 "When there is a currently active LU-LU session for 2144 this connection, this object returns the BIND Image 2145 (defined to be bytes 1-p of the complete BIND Request 2146 Unit -- see 'SNA Formats' for more information) 2147 that was received from the PLU during session 2148 activation. When there is no active LU-LU session, 2149 or when a BIND image is unavailable for some other 2150 reason, this object returns a zero-length octet 2151 string." 2152 REFERENCE 2153 "'Systems Network Architecture Formats', IBM 2154 Publication GA27-3136." 2155 ::= { tn3270eTcpConnEntry 19 } 2157 tn3270eTcpConnSnaState OBJECT-TYPE 2158 SYNTAX INTEGER { 2159 unknown(0), 2160 noSluSession(1), 2161 sscpLuSession(2), -- but no LU-LU session 2162 luLuSession(3), -- but no SSCP-LU session 2163 sscpLuSessionAndLuLuSession(4) 2164 } 2165 MAX-ACCESS read-only 2166 STATUS current 2167 DESCRIPTION 2168 "The current state of the SNA side of the end-to-end 2169 TN3270 connection. The following states are defined: 2171 unknown(0) - The true state is not known. 2172 noSluSession(1) - The SLU has neither an SSCP-LU 2173 nor an LU-LU session active. 2174 sscpLuSession(2) - The SSCP-LU session for the SLU 2175 is active, but the SLU is not 2176 currently in session with a PLU. 2177 luLuSession(3) - The SLU is currently in session 2178 with a PLU, but the SSCP-LU 2179 session for the LU is not active. 2180 sscpLuSessionAndLuLuSession(4) - The SLU currently has 2181 an active session with a PLU, 2182 and the SSCP-LU session for the 2183 SLU is active." 2185 ::= { tn3270eTcpConnEntry 20 } 2187 tn3270eTcpConnStateLastDiscReason OBJECT-TYPE 2188 SYNTAX INTEGER { 2189 unknown(0), 2190 hostSendsUnbind(1), 2191 hostDontAcceptConnection(2), 2192 outOfResource(3), 2193 clientProtocolError(4), 2194 invalidDeviceName(5), 2195 deviceInUse(6), 2196 inactivityTimeout(7), 2197 hostNotResponding(8), 2198 clientNotResponding(9), 2199 serverClose(10), 2200 sysreqLogoff(11), 2201 serverSpecificHexCode(12) 2202 } 2203 MAX-ACCESS read-only 2204 STATUS current 2205 DESCRIPTION 2206 "The last disconnect reason. A session that has not 2207 experienced a disconnect shall use the value unknown(0) 2208 for this object. Depending on when an implementation 2209 removes entries from this table, certain states may 2210 never be returned." 2211 ::= { tn3270eTcpConnEntry 21 } 2213 tn3270eTcpConnSrvrConfIndex OBJECT-TYPE 2214 SYNTAX Unsigned32 (1..4294967295) 2215 MAX-ACCESS read-only 2216 STATUS current 2217 DESCRIPTION 2218 "tn3270eSrvrConfIndex of the tn3270eSrvrConfEntry 2219 belonging to the TN3270E server to which this entry 2220 belongs." 2221 ::= { tn3270eTcpConnEntry 22 } 2223 tn3270eTcpConnActivationTime OBJECT-TYPE 2224 SYNTAX TimeStamp 2225 MAX-ACCESS read-only 2226 STATUS current 2227 DESCRIPTION 2228 "The value of the sysUpTime object the last time 2229 this TCP connection became active." 2230 ::= { tn3270eTcpConnEntry 23 } 2232 tn3270eConfSpinLock OBJECT-TYPE 2233 SYNTAX TestAndIncr 2234 MAX-ACCESS read-write 2235 STATUS current 2236 DESCRIPTION 2237 "An advisory lock used to allow cooperating 2238 TN3270E-MIB applications to coordinate their use 2239 of the tn3270eSrvrConfTable, the tn3270eSrvrPortTable, 2240 the tn3270eClientGroupTable, the tn3270eResPoolTable, 2241 and the tn3270eClientResMapTable. 2243 When creating a new entry or altering an existing entry 2244 in the any of the tables mentioned above, an application 2245 should make use of tn3270eRtSpinLock to serialize 2246 application changes or additions. 2248 Since this is an advisory lock, the use of this lock is 2249 not enforced." 2250 ::= { tn3270eObjects 10 } 2252 -- Conformance Definitions 2254 tn3270eGroups OBJECT IDENTIFIER ::= { tn3270eConformance 1 } 2256 tn3270eCompliances OBJECT IDENTIFIER ::= { tn3270eConformance 2 } 2258 -- compliance statements 2260 tn3270eCompliance MODULE-COMPLIANCE 2261 STATUS current 2262 DESCRIPTION 2263 "The compliance statement for agents that support the 2264 TN3270E-MIB." 2265 MODULE -- this module 2266 MANDATORY-GROUPS { tn3270eBasicGroup, 2267 tn3270eSessionGroup 2268 } 2269 GROUP tn3270eResMapGroup 2270 DESCRIPTION 2271 "This group is optional and provides a method of 2272 performing tn3270eClientGroup to tn3270eResPool 2273 mapping." 2275 GROUP tn3270eHiCapacityGroup 2276 DESCRIPTION 2277 "This group is optional and provides for support 2278 of high capacity counters." 2280 OBJECT tn3270eSrvrConfConnectivityChk 2281 MIN-ACCESS read-only 2282 DESCRIPTION 2283 "The agent is not required to support a set to this 2284 object if the associated TN3270E server doesn't 2285 support either TIMING-MARK or NOP processing. In 2286 this case an agent should return noCheck on 2287 retrieval." 2289 OBJECT tn3270eSrvrConfTmNopInactTime 2290 MIN-ACCESS read-only 2291 DESCRIPTION 2292 "The agent is not required to support a set to this 2293 object if the functions enabled by 2294 tn3270eSrvrConfConnectivityChk are not supported. 2295 An agent in this case should return a value of 0." 2297 OBJECT tn3270eSrvrConfTmNopInterval 2298 MIN-ACCESS read-only 2299 DESCRIPTION 2300 "The agent is not required to support a set to this 2301 object if the functions enabled by 2302 tn3270eSrvrConfConnectivityChk are not supported. 2303 An agent in this case should return a value of 0." 2305 OBJECT tn3270eSrvrConfAdminStatus 2306 DESCRIPTION 2307 "A TN3270E server is not required to support a 2308 stopImmediate state transition." 2310 OBJECT tn3270eSrvrConfRowStatus 2311 MIN-ACCESS read-only 2312 DESCRIPTION 2313 "Write access is not required." 2315 OBJECT tn3270eSrvrConfTmTimeout 2316 MIN-ACCESS read-only 2317 DESCRIPTION 2318 "The agent is not required to support a set to this 2319 object if the functions enabled by 2320 tn3270eSrvrConfConnectivityChk are not supported. 2321 An agent in this case should return a value of 0." 2323 OBJECT tn3270eSrvrPortRowStatus 2324 MIN-ACCESS read-only 2325 DESCRIPTION 2326 "Write access is not required." 2328 OBJECT tn3270eClientGroupRowStatus 2329 MIN-ACCESS read-only 2330 DESCRIPTION 2331 "Write access is not required." 2333 OBJECT tn3270eResPoolRowStatus 2334 MIN-ACCESS read-only 2335 DESCRIPTION 2336 "Write access is not required." 2338 OBJECT tn3270eClientResMapRowStatus 2339 MIN-ACCESS read-only 2340 DESCRIPTION 2341 "Write access is not required." 2343 ::= { tn3270eCompliances 1 } 2345 -- units of conformance 2347 tn3270eBasicGroup OBJECT-GROUP 2348 OBJECTS { 2349 tn3270eSrvrConfInactivityTimeout, 2350 tn3270eSrvrConfConnectivityChk, 2351 tn3270eSrvrConfTmNopInactTime, 2352 tn3270eSrvrConfTmNopInterval, 2353 tn3270eSrvrFunctionsSupported, 2354 tn3270eSrvrConfAdminStatus, 2355 tn3270eSrvrConfOperStatus, 2356 tn3270eSrvrConfSessionTermState, 2357 tn3270eSrvrConfSrvrType, 2358 tn3270eSrvrConfContact, 2359 tn3270eSrvrConfRowStatus, 2360 tn3270eSrvrConfLastActTime, 2361 tn3270eSrvrConfTmTimeout, 2362 tn3270eSrvrPortRowStatus, 2363 tn3270eSrvrStatsUpTime, 2364 tn3270eSrvrStatsMaxTerms, 2365 tn3270eSrvrStatsInUseTerms, 2366 tn3270eSrvrStatsSpareTerms, 2367 tn3270eSrvrStatsMaxPtrs, 2368 tn3270eSrvrStatsInUsePtrs, 2369 tn3270eSrvrStatsSparePtrs, 2370 tn3270eSrvrStatsInConnects, 2371 tn3270eSrvrStatsConnResrceRejs, 2372 tn3270eSrvrStatsDisconnects, 2373 tn3270eSrvrStatsInOctets, 2374 tn3270eSrvrStatsOutOctets, 2375 tn3270eSrvrStatsConnErrorRejs, 2376 tn3270eClientGroupSubnetMask, 2377 tn3270eClientGroupPfxLength, 2378 tn3270eClientGroupRowStatus, 2379 tn3270eSnaMapLocalName, 2380 tn3270eSnaMapPrimaryLuName, 2381 tn3270eConfSpinLock 2382 } 2383 STATUS current 2384 DESCRIPTION 2385 "This group is mandatory for all hosts supporting the 2386 TN3270E-MIB." 2387 ::= { tn3270eGroups 1 } 2389 tn3270eSessionGroup OBJECT-GROUP 2390 OBJECTS { 2391 tn3270eResMapAddrType, 2392 tn3270eResMapAddress, 2393 tn3270eResMapPort, 2394 tn3270eResMapElementType, 2395 tn3270eResMapSscpSuppliedName, 2396 tn3270eTcpConnLastActivity, 2397 tn3270eTcpConnBytesIn, 2398 tn3270eTcpConnBytesOut, 2399 tn3270eTcpConnResourceElement, 2400 tn3270eTcpConnResourceType, 2401 tn3270eTcpConnDeviceType, 2402 tn3270eTcpConnFunctions, 2403 tn3270eTcpConnSrvrConfIndex, 2404 tn3270eTcpConnActivationTime 2405 } 2406 STATUS current 2407 DESCRIPTION 2408 "This group is mandatory for all hosts supporting the 2409 TN3270E-MIB." 2410 ::= { tn3270eGroups 2 } 2412 tn3270eResMapGroup OBJECT-GROUP 2413 OBJECTS { 2414 tn3270eResPoolElementType, 2415 tn3270eResPoolRowStatus, 2416 tn3270eClientResMapRowStatus, 2417 tn3270eTcpConnId, 2418 tn3270eTcpConnClientIdFormat, 2419 tn3270eTcpConnClientId, 2420 tn3270eTcpConnTraceData, 2421 tn3270eTcpConnLogInfo, 2422 tn3270eTcpConnLuLuBindImage, 2423 tn3270eTcpConnSnaState, 2424 tn3270eTcpConnStateLastDiscReason 2425 } 2426 STATUS current 2427 DESCRIPTION 2428 "This group is optional for all hosts supporting the 2429 TN3270E-MIB." 2430 ::= { tn3270eGroups 3 } 2432 tn3270eHiCapacityGroup OBJECT-GROUP 2433 OBJECTS { 2434 tn3270eSrvrStatsHCInOctets, 2435 tn3270eSrvrStatsHCOutOctets 2436 } 2437 STATUS current 2438 DESCRIPTION 2439 "Support of these objects is REQUIRED when the 2440 Counter32 versions can potentially wrap too 2441 frequently. This group is optional for all other 2442 hosts supporting the TN3270E-MIB. 2444 The IF-MIB (RFC 2233) requires that the 64-bit 2445 versions of its counters be implemented when an 2446 interface can support rates of around 20 million 2447 bits per second or greater. This implies a minimum 2448 wrap rate of just over 28 minutes. It is recommended 2449 that this same guideline be used for determining 2450 whether an implementation implements these objects. 2452 This group contains two objects with the syntax 2453 Counter64. An implementation that doesn't support 2454 these objects should return noSuchObject, since 2455 returning a zero is misleading." 2457 ::= { tn3270eGroups 4 } 2459 END 2461 5.0 Security Considerations 2463 Certain management information defined in this MIB may be considered 2464 sensitive in some network environments. Therefore, authentication of 2465 received SNMP requests and controlled access to management information 2466 SHOULD be employed in such environments. An authentication protocol is 2467 defined in [10]. A protocol for access control is defined in [11]. 2469 Several objects in this MIB allow write access or provide for row 2470 creation. Allowing this support in a non-secure environment can have a 2471 negative effect on network operations. It is RECOMMENDED that 2472 implementers seriously consider whether set operations or row creation 2473 should be allowed without providing, at a minimum, authentication of 2474 request origin. It is RECOMMENDED that without such support, the 2475 following objects be implemented as read-only: 2477 o tn3270eSrvrConfInactivityTimout 2478 o tn3270eSrvrConfConnectivityChk 2479 o tn3270eSrvrConfActivityTimeout 2480 o tn3270eSrvrConfActivityInterval 2481 o tn3270eSrvrConfAdminStatus 2482 o tn3270eSrvrConfSessionTermState 2483 o tn3270eSrvrConfContact 2484 o tn3270eClientGroupSubnetMask 2485 o tn3270eResPoolElementType 2486 o tn3270eSrvrConfRowStatus 2487 o tn3270eSrvrPortRowStatus 2488 o tn3270eClientGroupRowStatus 2489 o tn3270eResPoolRowStatus 2490 o tn3270eResMapRowStatus 2492 For all tables in the MIB except the tn3270eTcpConnTable, the first 2493 index identifies an individual TN3270E server. This makes it easy to 2494 implement an access control policy under which different principals have 2495 access to objects related to different servers. Implementation of such 2496 a policy is not possible for the entries in the tn3270eTcpConTable. 2498 6.0 Intellectual Property 2500 The IETF takes no position regarding the validity or scope of any 2501 intellectual property or other rights that might be claimed to pertain 2502 to the implementation or use of the technology described in this 2503 document or the extent to which any license under such rights might or 2504 might not be available; neither does it represent that it has made any 2505 effort to identify any such rights. Information on the IETF's 2506 procedures with respect to rights in standards-track and 2507 standards-related documentation can be found in BCP-11. Copies of 2508 claims of rights made available for publication and any assurances of 2509 licenses to be made available, or the result of an attempt made to 2510 obtain a general license or permission for the use of such proprietary 2511 rights by implementers or users of this specification can be obtained 2512 from the IETF Secretariat. 2514 The IETF invites any interested party to bring to its attention any 2515 copyrights, patents or patent applications, or other proprietary rights 2516 which may cover technology that may be required to practice this 2517 standard. Please address the information to the IETF Executive 2518 Director. 2520 7.0 Acknowledgments 2522 This document is a product of the TN3270E Working Group. Thanks to 2523 Randy Presuhn of BMC Software for his valuable review comments on 2524 several versions of the document. 2526 8.0 References 2528 [1] Case, J., M. Fedor, M. Schoffstall, J. Davin, "Simple Network 2529 Management Protocol", RFC 1157, SNMP Research, Performance Systems 2530 International, MIT Laboratory for Computer Science, May 1990. 2532 [2] McCloghrie, K., and M. Rose, Editors, "Management Information Base 2533 for Network Management of TCP/IP-based internets: MIB-II", STD 17, 2534 RFC 1213, Hughes LAN Systems, Performance Systems International, 2535 March 1991. 2537 [3] Case, J., McCloghrie, K., Rose, M., and Waldbusser S., "Structure 2538 of Management Information for Version 2 of the Simple Network 2539 Management Protocol (SNMPv2)", RFC 1902, January 1996. 2541 [4] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Textual 2542 Conventions for Version 2 of the Simple Network Management Protocol 2543 (SNMPv2)", RFC 1903, January 1996. 2545 [5] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., 2546 "Conformance Statements for Version 2 of the Simple Network 2547 Management Protocol (SNMPv2)", RFC 1904, January 1996. 2549 [6] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Protocol 2550 Operations for Version 2 of the Simple Network Management Protocol 2551 (SNMPv2)", RFC 1905, January 1996. 2553 [7] Harrington D., Presuhn, R., Wijnen, B., "An Architecture for 2554 Describing SNMP Management Frameworks", RFC 2271, Cabletron 2555 Systems, BMC Software, Inc., IBM T.J. Watson Research, January 2556 1998. 2558 [8] Harrington D., Presuhn, R., Wijnen, B., "Message Processing and 2559 Dispatching for the Simple Network Management Protocol (SNMP)", RFC 2560 2272, Cabletron Systems, BMC Software, Inc., IBM T.J. Watson 2561 Research, January 1998. 2563 [9] Levi D., Meyer P., Stewart, B., "SNMPv3 Applications", RFC 2273, 2564 SNMP Research, Inc., Secure Computing Corporation, Cisco Systems, 2565 January 1998. 2567 [10] Blumenthal, U., Wijnen, B., "User-based Security Model (USM) for 2568 version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 2569 2274, IBM T. J. Watson Research, January 1998. 2571 [11] Wijnen, B., Presuhn, R., McCloghrie, K., "View-based Access Control 2572 Model (VACM) for the Simple Network Management Protocol (SNMP)", 2573 RFC 2275, IBM T.J. Watson Research, BMC Software, Inc., Cisco 2574 Systems, Inc., January 1998. 2576 [12] Postel, J., and Reynolds, J., "Telnet Protocol Specification", RFC 2577 854, May 1983. 2579 [13] Postel, J., and Reynolds, J., "Telnet Timing Mark Option", RFC 860, 2580 May 1983. 2582 [14] Rekhter, J., "Telnet 3270 Regime Option", RFC 1041, January 1988. 2584 [15] Kelly, B., "TN3270 Enhancements", RFC 1647, July 1994. 2586 [16] McCloghrie, K., "TCP-MIB Definitions", RFC 2012, November 1996. 2588 [17] Hovey, R., and S. Bradner, "The Organizations Involved in the IETF 2589 Standards Process", BCP 11, RFC 2028, October 1996. 2591 [18] Bradner, S., "Key words for use in RFCs to Indicate Requirement 2592 Levels", BCP 14, RFC 2119, March 1997. 2594 [19] Hinden, R., Deering, S., "IP Version 6 Addressing Architecture", 2595 , July 16, 1997. 2597 [20] Krupczak, Cheryl, Saperia, Jonathan, "Definitions of System-Level 2598 Managed Objects for Applications", RFC 2287, February 1998. 2600 9.0 Authors' Addresses 2602 Kenneth D. White 2603 Dept. BRQA/Bldg. 501/G114 2604 IBM Corporation 2605 P.O.Box 12195 2606 3039 Cornwallis 2607 Research Triangle Park, NC 27709, USA 2608 E-mail: kennethw@vnet.ibm.com 2610 Robert Moore 2611 Dept. BRQA/Bldg. 501/G114 2612 IBM Corporation 2613 P.O.Box 12195 2614 3039 Cornwallis 2615 Research Triangle Park, NC 27709, USA 2616 Phone: +1-919-254-4436 2617 E-mail: remoore@us.ibm.com 2619 10.0 Full Copyright Statement 2621 Copyright (C) The Internet Society (1997). All Rights Reserved. 2623 This document and translations of it may be copied and furnished to 2624 others, and derivative works that comment on or otherwise explain it or 2625 assist in its implementation may be prepared, copied, published and 2626 distributed, in whole or in part, without restriction of any kind, 2627 provided that the above copyright notice and this paragraph are included 2628 on all such copies and derivative works. However, this document itself 2629 may not be modified in any way, such as by removing the copyright notice 2630 or references to the Internet Society or other Internet organizations, 2631 except as needed for the purpose of developing Internet standards in 2632 which case the procedures for copyrights defined in the Internet 2633 Standards process must be followed, or as required to translate it into 2634 languages other than English. 2636 The limited permissions granted above are perpetual and will not be 2637 revoked by the Internet Society or its successors or assigns. 2639 This document and the information contained herein is provided on an "AS 2640 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK 2641 FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT 2642 LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT 2643 INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR 2644 FITNESS FOR A PARTICULAR PURPOSE. 2646 Appendix A. IANATn3270eTC-MIB 2648 This appendix defines the current content of the IANATn3270eTC-MIB. 2649 This section should be removed from this document prior to its approval, 2650 at which time this MIB will be administered by IANA. 2652 IANATn3270eTC-MIB DEFINITIONS ::= BEGIN 2654 IMPORTS 2655 MODULE-IDENTITY, experimental 2656 FROM SNMPv2-SMI 2657 TEXTUAL-CONVENTION 2658 FROM SNMPv2-TC; 2660 ianaTn3270eTcMib MODULE-IDENTITY 2661 LAST-UPDATED "9802020000Z" -- February 2, 1998 2662 ORGANIZATION "IANA" 2663 CONTACT-INFO 2664 "Internet Assigned Numbers Authority 2666 Postal: USC/Information Sciences Institute 2667 4676 Admiralty Way, Marina del Rey, CA 90292 2669 Tel: +1 310 822 1511 2670 E-Mail: iana@isi.edu" 2671 DESCRIPTION 2672 "This module defines a set of textual conventions 2673 for use by the TN3270E-MIB and the TN3270E-RT-MIB. 2675 Any additions or changes to the contents of this 2676 MIB module must first be discussed on the tn3270e 2677 working group list at: tn3270e@list.nih.gov 2678 and approved by one of the following TN3270E 2679 working group contacts: 2681 Ed Bailey (co-chair) - elbailey@us.ibm.com 2682 Michael Boe (co-chair) - mboe@cisco.com 2683 Ken White - kennethw@vnet.ibm.com 2684 Robert Moore - remoore@us.ibm.com 2686 The above list of contacts can be altered with 2687 the approval of the two co-chairs. 2689 The Textual Conventions defined within this MIB have 2690 no security issues associated with them unless 2691 explicitly stated in their corresponding 2692 DESCRIPTION clause." 2693 -- IANA will assign a real OID when they take over this module. 2694 ::= { experimental 2001 } 2696 -- Textual Conventions 2698 IANATn3270eAddrType ::= TEXTUAL-CONVENTION 2699 STATUS current 2700 DESCRIPTION 2701 "The textual convention for defining the type of a 2702 client address. The enumeration value unknown(0) is 2703 usually used to indicate that no actual address is 2704 present." 2705 SYNTAX INTEGER { 2706 unknown(0), 2707 ipv4(1), 2708 ipv6(2) 2709 } 2711 IANATn3270Functions ::= TEXTUAL-CONVENTION 2712 STATUS current 2713 DESCRIPTION 2714 "This textual convention reflects the current set of 2715 TN3270 and TN3270E functions that can be negotiated 2716 between a server and its client: 2718 RFC856 2719 transmitBinary The sender of this command REQUESTS 2720 permission to begin transmitting, or 2721 confirms that it will now begin 2722 transmitting characters which are to 2723 be interpreted as 8 bits of binary 2724 data by the receiver of the data. 2725 RFC860 2726 timingMark The sender of this command REQUESTS 2727 that the receiver of this command 2728 return a WILL TIMING-MARK in the data 2729 stream at the 'appropriate place'. 2730 RFC885 2731 endOfRecord The sender of this command requests 2732 permission to begin transmission of 2733 the Telnet END-OF-RECORD (EOR) code 2734 when transmitting data characters, or 2735 the sender of this command confirms it 2736 will now begin transmission of EORs 2737 with transmitted data characters. 2738 RFC1091 2739 terminalType Sender is willing to send terminal 2740 type information in a subsequent 2741 sub-negotiation. 2742 RFC1041 2743 tn3270Regime Sender is willing to send list of 2744 supported 3270 Regimes in a 2745 subsequent sub-negotiation. 2746 RFC1647 2747 scsCtlCodes (Printer sessions only). Allows the 2748 use of the SNA Character Stream (SCS) 2749 and SCS control codes on the session. 2750 SCS is used with LU type 1 SNA sessions. 2751 dataStreamCtl (Printer sessions only). Allows the use 2752 of the standard 3270 data stream. This 2753 corresponds to LU type 3 SNA sessions. 2755 responses Provides support for positive and 2756 negative response handling. Allows the 2757 server to reflect to the client any and 2758 all definite, exception, and no response 2759 requests sent by the host application. 2760 bindImage Allows the server to send the SNA Bind 2761 image and Unbind notification to the 2762 client. 2763 sysreq Allows the client and server to emulate 2764 some (or all, depending on the server) of 2765 the functions of the SYSREQ key in an SNA 2766 environment." 2767 SYNTAX BITS { 2768 transmitBinary(0),-- rfc856 2769 timemark(1), -- rfc860 2770 endOfRecord(2), -- rfc885 2771 terminalType(3), -- rfc1091 2772 tn3270Regime(4), -- rfc1041 2773 scsCtlCodes(5), -- rfc1647 2774 dataStreamCtl(6), -- rfc1647 2775 responses(7), -- rfc1647 2776 bindImage(8), -- rfc1647 2777 sysreq(9) -- rfc1647 2778 } 2780 IANATn3270eClientType ::= TEXTUAL-CONVENTION 2781 STATUS current 2782 DESCRIPTION 2783 "The textual convention for defining the set of 2784 enumerations used by tn3270eTcpConnClientIdFormat 2785 in the TN3270E-MIB: 2787 ENUMERATION OCTETs DESCRIPTION 2789 none(0) 0 Not specified 2790 other(1) 1..512 Implementation specific 2791 ipv4(2) 6 4-octet IP Address plus 2792 2-octet TCP Port 2793 ipv6(3) 18 16-octet IPv6 Address 2794 plus 2-octet TCP Port 2795 domainName(4) 1..512 The DNS name of a 2796 client. 2797 truncDomainName(5) 1..512 The (truncated) DNS name 2798 of a client. 2799 string(6) 1..512 Unknown Utf8String 2800 certificate(7) 1..512 certificate 2801 userId(8) 1..8 Client's userid 2802 x509dn(9) 1..512 X.509 Distinguished Name 2804 Representation of a certificate(7) may be lead to 2805 a security exposure and is NOT RECOMMENDED without 2806 adequate security." 2807 SYNTAX INTEGER { 2808 none(0), 2809 other(1), 2810 ipv4(2), 2811 ipv6(3), 2812 domainName(4), 2813 truncDomainName(5), 2814 string(6), 2815 certificate(7), 2816 userId(8), 2817 x509dn(9) 2818 } 2820 IANATn3270eLogData ::= TEXTUAL-CONVENTION 2821 STATUS current 2822 DESCRIPTION 2823 "An octet string representing log data as pertaining to 2824 either a TN3270 or TN3270E Session as reported from a 2825 TN3270E Server. Log data is stored in an octet string 2826 in time order (from earliest to latest). 2828 Each log element has the following form: 2830 +------+----+---------+------------+ 2831 !length!type!TimeStamp! data ! 2832 +------+----+---------+------------+ 2834 where 2836 length = one-octet length of the data portion of the 2837 trace element, not including the length, 2838 type, and TimeStamp fields 2839 type = one-octet code point characterizing the data. 2840 TimeStamp = A 4-octet field representing the number of 2841 TimeTicks since the TN3270E server was last 2842 activated. The server's last activation time 2843 is available in the tn3270eSrvrConfLastActTime 2844 object in the TN3270E MIB, which has the 2845 syntax DateAndTime. 2846 data = initial part of a PDU. 2848 length type 2850 0-255 x'00' - unknown 2851 0 x'01' - inactivity timer expired 2852 0 x'02' - dynamic timer expired 2853 0 x'03' - actlu req 2854 0 x'04' - bind req 2855 0 x'05' - clear req 2856 0 x'06' - dactlu req 2857 0 x'07' - warm actpu req 2858 0 x'08' - sdt req 2859 0 x'09' - unbind req 2860 0 x'0A' - notify resp 2861 0 x'0B' - reply PSID neg rsp 2862 0 x'0C' - reply PSID pos rsp 2863 0 x'0D' - unbind rsp 2864 0 x'0E' - hierarchical reset 2865 0 x'0F' - client connect req 2866 0 x'10' - client disconnect req 2867 0 x'11' - timingmark received 2868 0 x'12' - flowControl timer expired 2869 0 x'13' - neg rsp to host 2870 0 x'14' - neg rsp from host 2871 0 x'15' - data contention 2872 0 x'16' - no buffer to send SNA data 2873 0 x'17' - receive response while inbound 2874 0 x'18' - client protocol error 2875 0 x'19' - badClientSequenceReceived 2876 1-255 x'1A' - utf8String 2877 2 x'1B' - hexCode, implementation dependent 2879 log event entries have a minimum length of 6 octets. 2880 The zero-length string indicates that no log data is 2881 available." 2882 SYNTAX OCTET STRING (SIZE (0 | 6..2048)) 2884 END