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