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