idnits 2.17.1 draft-ietf-snanau-naumib-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-24) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing document type: Expected "INTERNET-DRAFT" in the upper left hand corner of the first page ** 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 -- however, there's a paragraph with a matching beginning. Boilerplate error? ** 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 Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Abstract section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 59 instances of too long lines in the document, the longest one being 1 character in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 1975 has weird spacing: '...tActive colle...' == Line 1993 has weird spacing: '...tActive colle...' -- 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 (March 06, 1996) is 10276 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) -- Possible downref: Non-RFC (?) normative reference: ref. '1' ** Obsolete normative reference: RFC 1902 (ref. '2') (Obsoleted by RFC 2578) ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. '4') ** Obsolete normative reference: RFC 1905 (ref. '5') (Obsoleted by RFC 3416) Summary: 14 errors (**), 0 flaws (~~), 3 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Definitions of Managed Objects 3 for SNA NAUs 5 March 06, 1996 7 Bob Clouston 8 Cisco Systems 9 clouston@cisco.com 11 Zbigniew Kielczewski 12 Cisco Systems 13 zkielcze@cisco.com 15 Kitty Shih 16 Novell 17 kmshih@novell.com 19 Bob Moore 20 IBM Corporation 21 remoore@ralvm6.vnet.ibm.com 23 25 1. Status of this Memo 27 This document is an Internet-Draft. Internet-Drafts are working 28 documents of the Internet Engineering Task Force (IETF), its areas, and 29 its working groups. Note that other groups may also distribute working 30 documents as Internet-Drafts. 32 Internet-Drafts are draft documents valid for a maximum of six months. 33 Internet-Drafts may be updated, replaced, or obsoleted by other 34 documents at any time. It is not appropriate to use Internet-Drafts as 35 reference material or to cite them other than as a working draft or work 36 in progress. 38 To learn the current status of any Internet-Draft, please check the 39 1id-abstracts.txt listing contained in the Internet-Drafts Shadow 40 Directories on ds.internic.net, nic.nordu.net, ftp.isi.edu, or 41 munnari.oz.au. 43 2. Introduction 45 This memo defines a portion of the Management Information Base (MIB) for 46 use with network management protocols in the Internet community. In 47 particular, it defines objects for managing the configuration, 48 monitoring and control of Physical Units (PUs) and Logical Units (LUs) 49 in an SNA environment. PUs and LUs are two types of Network Addressable 50 Units (NAUs) in the logical structure of an SNA network. NAUs are the 51 origination or destination points for SNA data streams. This memo 52 identifies managed objects for PU Type 1.0, 2.0 and Type 2.1 and LU Type 53 0, 1, 2, 3, 4, 7. The generic objects defined here can also be used to 54 manage LU 6.2 and any LU-LU session. The SNA terms and overall 55 architecture are documented in [1]. 57 This memo does not specify a standard for the Internet community. 59 3. The SNMPv2 Network Management Framework 61 The Internet-standard Network Management Framework presently consists of 62 three major components. They are: 64 o RFC 1902 [2] which defines the SMI, the mechanisms used for 65 describing and naming objects for the purpose of management. 67 o STD 17, RFC 1213 [3] which defines MIB-II, the core set of managed 68 objects for the Internet suite of protocols. 70 o RFC 1157 [4] and/or RFC 1905 [5] which defines the protocol used 71 for network access to managed objects. 73 The Framework permits new objects to be defined for the purpose of 74 experimentation and evaluation. 76 4. Overview 78 This document identifies the proposed set of objects for managing the 79 configuration, monitoring and control of Physical Units (PUs) and 80 Logical Units (LUs) in an SNA environment. In this document, the name 81 "Node" is used to describe SNA Node Type 1.0, 2.0 and Type 2.1 and the 82 name "LU" is used to describe Logical Unit of Type 0, 1, 2, 3, 4, 7 and 83 6.2. Note however that only objects common to all PU and LU types are 84 covered here and LU 6.2 specific objects are not included in this MIB 85 module. 87 Highlights of the management functions supported by the SNANAU MIB 88 module include the following: 90 o Activation/Deactivation of Nodes via the AdminState object in the 91 snaNodeTable 93 o Deactivation of sessions via the OperState object in the 94 snaLuActSessnTable 96 o Monitoring and modification of parameters related to Nodes, LUs, 97 and Node/link associations 99 o Monitoring of session operational parameters 101 o PU2.0 operational statistics 103 o Session operational statistics 105 o RTM statistics 107 o Traps for: 108 + Node state change 109 + Node activation failure 110 + LU session BIND failure 112 This MIB module does not support: 114 o creation of objects, 116 o activation or deactivation of LUs, nor 118 o activation of sessions. 120 4.1. SNANUAU MIB Structure 122 The SNANAU MIB module contains three groups of objects: 124 o snaNode - objects related to Node configuration, monitoring and 125 control. 127 o snaLu - objects related to LU definition, monitoring and control. 129 o snaMgtTools - objects related to specific management tools well 130 known in SNA environment. 132 These groups are described below in more detail. 134 Many objects are organized into two types of tables: the Admin and Oper 135 tables. 137 The "Admin" table contains read-only objects which contain default or 138 expected configuration values. This MIB does not create or modify 139 configuration values. The "Oper" table contains objects which provide 140 current operational values, such as state values or negotiated 141 parameters, for dynamic or configured objects. Dynamic objects are 142 created by the Agent system using one of the templates provided in the 143 "Admin" table. Configured objects usually have a one-to-one 144 relationship between "Admin" and "Oper" entries. However, some "Admin" 145 values may have changed since the object became operational, such that 146 the "Oper" values may no longer be based on the "Admin" values. The 147 "Admin" entry could even be deleted. For example, some implementations 148 may allow a link station definition (snaNodeLinkAdminEntry) to be 149 deleted even while the link station is active (snaNodeLinkOperEntry 150 still exists). Where appropriate, the "Oper" table may include initial 151 starting values for objects that can be reconfigured while operational. 152 How the "Admin" values are changed or deleted is outside the scope of 153 this MIB. 155 4.1.1. snaNode group 157 This table contains objects which describe runtime and operational state 158 variables for a Node, and an object to change the state of the node. 159 This table is indexed by the node name. 161 The snaNodeAdminState object describes the desired operational state of 162 a Node and is used to change the operational state of a Node. 164 How an Agent or a Management Station obtains the initial value of each 165 object at creation time is an implementation specific issue not 166 addressed in this memo. 168 Link-specific configuration objects are contained in a separate MIB 169 module (e.g., the SNA DLC MIB module) corresponding to link type. 171 2) snaPu20Table 173 Each row contains statistics variables and operational variables about a 174 PU type 2.0. 176 3) snaNodeLinkAdminTable 178 This table contains all references to link-specific tables. If a Node 179 is configured with multiple links, then it will have multiple entries in 180 this table. The entries in this table can be generated initially, after 181 startup of SNA service, by the Agent which uses information from Node 182 configuration file. Subsequent modifications of parameters, creation of 183 new Node link entries and deletion of entries is possible. The 184 modifications to this table can be saved in the Node configuration file 185 for the next startup (i.e., restart or next initialization) of SNA 186 service, but the mechanism for this function is not defined in this 187 memo. Each entry contains the configuration information that associates 188 a Node instance to one link instance. The table indices are the node 189 name and the link name. 191 4) snaNodeLinkOperTable 193 This table contains all references to link- specific tables for 194 operational parameters. If the Node is configured for multiple links, 195 then it will have multiple entries in this table. The table indices are 196 the node name and the link name. 198 5) snaNodeTraps 200 Two traps are defined for Nodes. The snaNodeStateChangeTrap indicates 201 that the operational state of a Node has changed. The 202 snaNodeActFailTrap indicates the failure of ACTPU received from host. 204 4.1.2. snaLu group 206 The snaLu group consists of the following tables: 208 1) snaLuAdminTable 210 Table containing LU configuration information. The rows in this table 211 cannot be created and deleted by a Management Station. Only objects 212 which are common to all types of LUs are included in this table. The 213 entries are indexed by node name and LU name. 215 2) snaLuOperTable 217 Table containing dynamic runtime information and control variables 218 relating to LUs. Only objects which are common to all types of LUs are 219 included in this table. This table is indexed by node name and LU name. 221 3) snaLuActSessnTable 223 This is a table containing objects which describe the operational state 224 of LU-LU sessions. Only objects which are common to all types of LU-LU 225 sessions are included in this table. When a session is started, an 226 entry in the session table is created by the Agent. When a session has 227 ended, the entry for that session is removed from the session table by 228 the Agent. Entries are indexed by node name, local LU name, and a 229 unique session index assigned by the agent. 231 4) snaLuHistSessTable 233 This table contains historical information about abnormally terminated 234 sessions. The table is indexed by an integer which will eventually 235 wrap. 237 5)snaLuSessStats 239 This group has objects that indicate and control gathering of 240 statistics, as well as the snaLuSessnStatsTable, which is a table 241 containing dynamic statistics information relating to LU-LU sessions. 243 5) snaLuTraps 245 The snaLuActSessBindFailTrap indicates the failure of a BIND request. 247 4.1.3. snaMgtTools group 249 This is an optional group. The snaMgtTools group consists of the 250 following table: 252 1) snaLuRtmTable 254 Each row contains Response Time Monitor (RTM) variables for an LU. The 255 table is indexed by Node and LU indices. Entries correspond to LU 2 256 entries in the snaLuAdminTable. A Management Station can read 257 collection of RTM statistics for a given LU. 259 4.1.4. Conformance statement 261 Compliance of the SNMPv2 management entity to the SNANAU MIB is defined 262 in terms of following conformance units called groups. 264 Unconditionally mandatory groups: snaNodeGroup, snaLuGroup, 265 snaSessionGroup. 267 Conditionally mandatory groups: snaPu20Group - mandatory only for those 268 entities which implement PU type 2.0. The snaMgtToolsRtmGroup - 269 mandatory only for those entities which implement LU type 2 and RTM. 271 5. Definitions 273 SNA-NAU-MIB DEFINITIONS ::= BEGIN 275 -- This MIB module contains objects necessary for management of the 276 -- following SNA devices: node types 1.0, 2.0, 2.1 and LU types 0, 1, 277 -- 2, 3, 4, 7. It also contains generic objects which can be used to 278 -- manage LU 6.2. 280 -- Naming conventions in this document: 281 -- The following names are used in object descriptors according to 282 -- SNA conventions. The name 'PU' or 'node' is used to describe nodes 283 -- type 1.0, 2.0 or 2.1. The name 'LU' is used to describe logical units 284 -- of type 0, 1, 2, 3, 4, 7 or 6.2. 286 IMPORTS 287 DisplayString, RowPointer, DateAndTime, TEXTUAL-CONVENTION 288 FROM SNMPv2-TC 290 Counter32, Gauge32, Integer32, TimeTicks, 291 OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE 292 FROM SNMPv2-SMI 294 MODULE-COMPLIANCE, OBJECT-GROUP 295 FROM SNMPv2-CONF; 297 snanauMIB MODULE-IDENTITY 298 LAST-UPDATED "9603061800Z" 299 ORGANIZATION "IETF SNA NAU MIB Working Group" 300 CONTACT-INFO 301 " Zbigniew Kielczewski 302 Cisco Systems 303 7025 Kit Creek Road 304 P.O. Box 14987 305 Research Triangle Park, NC 27709, USA 306 Tel: 1 919 472 2326 307 E-mail: zkielcze@cisco.com 309 Kitty Shih 310 Novell 311 890 Ross Drive 312 Sunnyvale, CA 94089 313 Tel: 1 408 747 4305 314 E-mail: kmshih@novell.com 315 Bob Moore (editor) 316 IBM Corporation 317 800 Park Offices Drive 318 CNMA/664 319 P.O. Box 12195 320 Research Triangle Park, NC 27709, USA 321 Tel: 1 919 254 4436 322 E-mail: remoore@ralvm6.vnet.ibm.com 323 " 325 DESCRIPTION 326 "This is the MIB module for objects used to 327 manage SNA devices." 328 ::= { mib-2 34 } 330 -- ******************************************************************** 331 -- Textual Convention 332 -- --------------------------------------------------------------------- 333 SnaSenseData ::= TEXTUAL-CONVENTION 334 STATUS current 335 DESCRIPTION 336 "To facilitate their display by a Management Station, sense 337 data objects in the MIB are represented as DisplayStrings of 338 size 8. Eight '0' characters indicates that no sense data 339 identifying an SNA error condition is available." 341 SYNTAX DisplayString (SIZE (8)) 343 -- ******************************************************************** 344 -- The SNANAU MIB module contains an objects part and a conformance part. 345 -- Objects are organized into the following groups: 346 -- (1)snaNode group, 347 -- (2)snaLu group, 348 -- (3)snaMgtTools group. 350 snanauObjects OBJECT IDENTIFIER ::= { snanauMIB 1 } 352 snaNode OBJECT IDENTIFIER ::= { snanauObjects 1 } 353 snaLu OBJECT IDENTIFIER ::= { snanauObjects 2 } 354 snaMgtTools OBJECT IDENTIFIER ::= { snanauObjects 3} 356 -- ******************************************************************** 357 -- snaNode group 358 -- 359 -- This group contains Managed Objects related to all node types, 360 -- plus some specific objects for type 2.0 nodes. 361 -- ******************************************************************** 363 -- ******************************************************************** 364 -- With the exception of snaNodeAdminState, objects in this table 365 -- contain current operational values, such as state values or 366 -- negotiated parameters, for SNA nodes. snaNodeAdminState provides 367 -- a Management Station with the ability to activate and deactivate 368 -- an SNA node. 369 -- ******************************************************************** 371 snaNodeTable OBJECT-TYPE 372 SYNTAX SEQUENCE OF SnaNodeEntry 373 MAX-ACCESS not-accessible 374 STATUS current 375 DESCRIPTION 376 "This table contains dynamic node parameters, which have read- 377 only access. These objects reflect the actual status of the 378 node. It also contains an object that a Management Station can 379 set to activate or deactivate an SNA node." 381 ::= { snaNode 3 } 383 snaNodeEntry OBJECT-TYPE 384 SYNTAX SnaNodeEntry 385 MAX-ACCESS not-accessible 386 STATUS current 387 DESCRIPTION 388 "The entry contains parameters that describe the state of one 389 node. The entries are created by the Agent. They have read- 390 only access." 392 INDEX { snaNodeName } 394 ::= { snaNodeTable 1 } 396 SnaNodeEntry ::= SEQUENCE { 397 snaNodeName DisplayString, 398 snaNodeAdminState INTEGER, 399 snaNodeOperState INTEGER, 400 snaNodeSscpSuppliedName DisplayString, 401 snaNodeType INTEGER, 402 snaNodeXidFormat INTEGER, 403 snaNodeId DisplayString, 404 snaNodeEnablingMethod INTEGER, 405 snaNodeLuTermDefault INTEGER, 406 snaNodeMaxLu Integer32, 407 snaNodeStopMethod INTEGER, 408 snaNodeStartTime DateAndTime, 409 snaNodeLastStateChange DateAndTime, 410 snaNodeActFailureReason INTEGER 411 } 413 snaNodeName OBJECT-TYPE 414 SYNTAX DisplayString (SIZE(1..17)) 415 MAX-ACCESS not-accessible 416 STATUS current 417 DESCRIPTION 418 "The value indicates the locally-defined name of the node. In 419 a type 2.1 node, this is a fully qualified name, meaning that 420 the node name is preceded by the NetId (if present) with a 421 period as the delimiter." 423 ::= { snaNodeEntry 1 } 425 snaNodeAdminState OBJECT-TYPE 426 SYNTAX INTEGER { 427 inactive(1), 428 active(3), 429 ready(5) 430 } 431 MAX-ACCESS read-write 432 STATUS current 433 DESCRIPTION 434 "Object by which a Management Station can activate or 435 deactivate a node, by setting the value to active(3) or 436 inactive(1), respectively. The value ready(5) has no meaning 437 on a set operation; it is returned in response to a get 438 operation when no set directed to this object has been 439 processed by the agent. 441 If the current value in snaNodeState is 'active(3)', then 442 setting this object to 'inactive(1)' will initiate the node 443 shutdown process using the method indicated by 444 snaNodeStopMethod. 446 If the current value in snaNodeState is 'inactive(1)', then 447 setting this object to 'active(3)' will initiate the node's 448 activation. 450 A Management Station can always set this object to 'active (3)' 451 irrespective of the value in the snaNodeEnablingMethod." 453 ::= { snaNodeEntry 2 } 455 snaNodeOperState OBJECT-TYPE 456 SYNTAX INTEGER { 457 inactive(1), 458 active(2), 459 waiting(3), 460 stopping(4) 461 } 462 MAX-ACCESS read-only 463 STATUS current 464 DESCRIPTION 465 "The current state of the node. The values have the following 466 meanings: 468 inactive(1) - the node is ready for activation -or- 469 an active node has been stopped -or- 470 a waiting node has returned to the 471 inactive state. 472 active(2) - the node is ready and operating. 473 waiting(3) - a request to have the node activated 474 has been issued, and the node 475 is pending activation. 476 stopping(4) - a request to stop the node has been 477 issued while the StopMethod normal 478 or immediate is used." 480 ::= { snaNodeEntry 3 } 482 snaNodeSscpSuppliedName OBJECT-TYPE 483 SYNTAX DisplayString (SIZE(0..17)) 484 MAX-ACCESS read-only 485 STATUS current 486 DESCRIPTION 487 "The value identifies the SNA name of the node. This name is 488 supplied to a PU by the SSCP that activated it. If a value was 489 not supplied, a zero-length string is returned. In a type 2.1 490 node, this is a fully qualified name, meaning that the node 491 name is preceded by the NetId (if present) with a period as the 492 delimiter." 494 ::= { snaNodeEntry 4 } 496 snaNodeType OBJECT-TYPE 497 SYNTAX INTEGER { 498 other(1), 499 pu10(2), 500 pu20(3), 501 t21LEN(4), 502 endNode(5), 503 networkNode(6) 504 } 505 MAX-ACCESS read-only 506 STATUS current 507 DESCRIPTION 508 "The value identifies the current type of the node." 510 ::= { snaNodeEntry 5 } 512 snaNodeXidFormat OBJECT-TYPE 513 SYNTAX INTEGER { 514 format0(1), 515 format1(2), 516 format3(3) 517 } 518 MAX-ACCESS read-only 519 STATUS current 520 DESCRIPTION 521 "The value identifies the type of XID format currently used for 522 this node. Note that there is no format type 2." 524 ::= { snaNodeEntry 6 } 526 snaNodeId OBJECT-TYPE 527 SYNTAX DisplayString (SIZE(8)) 528 MAX-ACCESS read-only 529 STATUS current 530 DESCRIPTION 531 "The value indicates the node id for this node instance. The 532 node id consists of two parts: 534 The block number is the first three digits of the 535 node id. These 3 hexadecimal digits identify the 536 product. 538 The ID number is the last 5 digits of the node id. 539 These 5 hexadecimal digits are administratively 540 defined and combined with the 3-digit block number 541 form the node id. This node_id is used to identify 542 the local node and is included in XIDs. A unique 543 value is required for connections to SNA subarea. 544 In some implementations, the value of 'bbb00000' 545 (where 'bbb' represents a 3-digit block number) is 546 returned to mean that the ID number is not unique on 547 this node." 549 ::= { snaNodeEntry 7 } 551 snaNodeEnablingMethod OBJECT-TYPE 552 SYNTAX INTEGER { 553 other(1), 554 startup(2), 555 demand(3), 556 onlyMS(4) 557 } 558 MAX-ACCESS read-only 559 STATUS current 560 DESCRIPTION 561 "The value indicates how the node is activated for the first 562 time. The values have the following meanings: 564 other(1) - not at boot time, LU activation 565 or by a Management Station; 566 startup(2) - at SNA services' initialization 567 time (this is the default); 568 demand(3) - only when LU is requested by 569 application; 570 onlyMS(4) - by a network Management Station only." 572 ::= { snaNodeEntry 8 } 574 snaNodeLuTermDefault OBJECT-TYPE 575 SYNTAX INTEGER { 576 unbind(1), 577 termself(2), 578 rshutd(3), 579 poweroff(4) 580 } 581 MAX-ACCESS read-only 582 STATUS current 583 DESCRIPTION 584 "The value identifies the default method used to deactivate LUs 585 for this node. 587 For LU6.2s, 'unbind(1)' is the only valid value. 589 unbind(1) - terminate the LU-LU session by sending 590 an SNA UNBIND request. 591 termself(2) - terminate the LU-LU session by sending 592 an SNA TERM-SELF (Terminate Self) 593 request on the SSCP-LU session. The 594 SSCP will inform the remote session LU 595 partner to send an UNBIND request to 596 terminate the session. 597 rshutd(3) - terminate the LU-LU session by sending 598 an SNA RSHUTD (Request ShutDown) request 599 to the remote session LU partner. 600 The remote LU will then send an UNBIND 601 request to terminate the session. 602 poweroff(4) - terminate the LU-LU session by sending 603 either an SNA LUSTAT (LU Status) request 604 on the LU-LU session or an SNA NOTIFY 605 request on the SSCP-LU session indicating 606 that the LU has been powered off. Sending 607 both is also acceptable. The result 608 should be that the remote session LU 609 partner will send an UNBIND to terminate 610 the session. 612 This object describes the default behavior for this node; 613 however, it is possible that for a specific LU the behavior 614 indicated by the snaLuOperTerm object is different." 616 ::= { snaNodeEntry 9 } 618 snaNodeMaxLu OBJECT-TYPE 619 SYNTAX Integer32 620 MAX-ACCESS read-only 621 STATUS current 622 DESCRIPTION 623 "This value identifies the current, maximum number of LUs that 624 can be activated for this node. For type 2.1 nodes, this 625 object refers to the number of dependent LUs." 627 ::= { snaNodeEntry 10 } 629 snaNodeStopMethod OBJECT-TYPE 630 SYNTAX INTEGER { 631 other(1), 632 normal(2), 633 immed(3), 634 force(4) 635 } 636 MAX-ACCESS read-only 637 STATUS current 638 DESCRIPTION 639 "This value identifies the current node shutdown method to be 640 used by the Agent to stop the node. When the Agent changes the 641 node's state to 'inactive (1)', the Agent must use the shutdown 642 method indicated by this object. 644 The values have the following meaning: 646 other(1) - proprietary method not listed in this 647 enumeration 648 normal(2) - deactivate only when there is no more 649 activity on this node (i.e., all data 650 flows have been completed and all 651 sessions have been terminated). 652 immed(3) - deactivate immediately regardless of 653 current activities on this node. Wait 654 for deactivation responses (from remote 655 node) before changing the node state to 656 inactive. 657 force(4) - deactivate immediately regardless of 658 current activities on this node. Do not 659 wait for deactivation responses (from 660 remote node) before changing the node 661 state to inactive." 663 ::= { snaNodeEntry 11 } 665 snaNodeStartTime OBJECT-TYPE 666 SYNTAX DateAndTime 667 MAX-ACCESS read-only 668 STATUS current 669 DESCRIPTION 670 "The time of node activation." 672 ::= { snaNodeEntry 12 } 674 snaNodeLastStateChange OBJECT-TYPE 675 SYNTAX DateAndTime 676 MAX-ACCESS read-only 677 STATUS current 678 DESCRIPTION 679 "The time of the last state change of the node." 681 ::= { snaNodeEntry 13 } 683 snaNodeActFailureReason OBJECT-TYPE 684 SYNTAX INTEGER { 685 other(1), 686 linkFailure(2), 687 noResources(3), 688 badConfiguration(4), 689 internalError(5), 690 unknown(255) 691 } 692 MAX-ACCESS read-only 693 STATUS current 694 DESCRIPTION 695 "The value indicates the reason for an activation failure. The 696 value 'other(1)' indicates a reason not listed in the 697 enumeration. The value 'unknown(255)' indicates that a reason 698 for the failure cannot be determined. 700 This object is sent in the trap snaNodeActFailTrap." 702 ::= { snaNodeEntry 14 } 704 -- ******************************************************************** 705 -- The following object is updated when there is a change to the value 706 -- of an object in any row of snaNodeTable, or when a row is added to 707 -- or deleted from the table. 708 -- ******************************************************************** 710 snaNodeTableLastChange OBJECT-TYPE 711 SYNTAX DateAndTime 712 MAX-ACCESS read-only 713 STATUS current 714 DESCRIPTION 715 "The time of at the last change made to any object in the 716 snaNodeTable, including row deletions/additions. 718 This object can be used to reduce frequent retrievals of the 719 snaNodeTable by a Management Station. It is expected that a 720 Management Station will periodically poll this object and 721 compare its current value with the previous one. A difference 722 indicates that some node operational information has been 723 changed. Only then will the Management Station retrieve the 724 entire table." 726 ::= { snaNode 4 } 728 -- ******************************************************************** 729 -- The following table contains information for type 2.0 nodes. 730 -- ******************************************************************** 732 snaPu20Table OBJECT-TYPE 733 SYNTAX SEQUENCE OF SnaPu20Entry 734 MAX-ACCESS not-accessible 735 STATUS current 736 DESCRIPTION 737 "This table contains dynamic parameters that have read-only 738 access. The entries in this table correspond to the type 2.0 739 node entries in the snaNodeTable." 741 ::= { snaNode 5 } 743 snaPu20Entry OBJECT-TYPE 744 SYNTAX SnaPu20Entry 745 MAX-ACCESS not-accessible 746 STATUS current 747 DESCRIPTION 748 "The entry contains information related to one type 2.0 node. 749 Counters represent traffic for all kinds of sessions: LU-LU, 750 SSCP-PU, and SSCP-LU." 752 INDEX { snaPu20Name } 754 ::= { snaPu20Table 1 } 756 SnaPu20Entry ::= SEQUENCE { 757 snaPu20Name DisplayString, 758 snaPu20SentBytes Counter32, 759 snaPu20ReceivedBytes Counter32, 760 snaPu20SentPius Counter32, 761 snaPu20ReceivedPius Counter32, 762 snaPu20SentNegRsps Counter32, 763 snaPu20ReceivedNegRsps Counter32, 764 snaPu20ActLus Gauge32, 765 snaPu20InActLus Gauge32, 766 snaPu20BindLus Gauge32, 767 snaPu20HostSscpId OCTET STRING, 768 snaPu20HostDescription DisplayString, 769 snaPu20SscpName OCTET STRING, 770 snaPu20PuName OCTET STRING 771 } 773 snaPu20Name OBJECT-TYPE 774 SYNTAX DisplayString (SIZE(1..17)) 775 MAX-ACCESS not-accessible 776 STATUS current 777 DESCRIPTION 778 "The locally defined name of the type 2.0 node." 780 ::= { snaPu20Entry 1 } 782 snaPu20SentBytes OBJECT-TYPE 783 SYNTAX Counter32 784 MAX-ACCESS read-only 785 STATUS current 786 DESCRIPTION 787 "The number of bytes sent by this node." 789 ::= { snaPu20Entry 2 } 791 snaPu20ReceivedBytes OBJECT-TYPE 792 SYNTAX Counter32 793 MAX-ACCESS read-only 794 STATUS current 795 DESCRIPTION 796 "The number of bytes received by this node." 798 ::= { snaPu20Entry 3 } 800 snaPu20SentPius OBJECT-TYPE 801 SYNTAX Counter32 802 MAX-ACCESS read-only 803 STATUS current 804 DESCRIPTION 805 "The number of PIUs sent by this node." 807 ::= { snaPu20Entry 4 } 809 snaPu20ReceivedPius OBJECT-TYPE 810 SYNTAX Counter32 811 MAX-ACCESS read-only 812 STATUS current 813 DESCRIPTION 814 "The number of PIUs received by this node." 816 ::= { snaPu20Entry 5 } 818 snaPu20SentNegRsps OBJECT-TYPE 819 SYNTAX Counter32 820 MAX-ACCESS read-only 821 STATUS current 822 DESCRIPTION 823 "The number of negative responses sent by this node." 825 ::= { snaPu20Entry 6 } 827 snaPu20ReceivedNegRsps OBJECT-TYPE 828 SYNTAX Counter32 829 MAX-ACCESS read-only 830 STATUS current 831 DESCRIPTION 832 "The number of negative responses received by this node." 834 ::= { snaPu20Entry 7 } 836 snaPu20ActLus OBJECT-TYPE 837 SYNTAX Gauge32 838 MAX-ACCESS read-only 839 STATUS current 840 DESCRIPTION 841 "The number of LUs on this PU that have received and responded 842 to ACTLU from the host." 844 ::= { snaPu20Entry 8 } 846 snaPu20InActLus OBJECT-TYPE 847 SYNTAX Gauge32 848 MAX-ACCESS read-only 849 STATUS current 850 DESCRIPTION 851 "The number of LUs on this PU that have not received an ACTLU 852 from the host. This is possible if the number of configured 853 LUs exceeds that on the host." 855 ::= { snaPu20Entry 9 } 857 snaPu20BindLus OBJECT-TYPE 858 SYNTAX Gauge32 859 MAX-ACCESS read-only 860 STATUS current 861 DESCRIPTION 862 "The number of LUs on this PU that have received and 863 acknowledged a BIND request from the host." 865 ::= { snaPu20Entry 10 } 867 snaPu20HostSscpId OBJECT-TYPE 868 SYNTAX OCTET STRING (SIZE(6)) 869 MAX-ACCESS read-only 870 STATUS current 871 DESCRIPTION 872 "This value identifies the current SSCP Id associated with the 873 node. It corresponds to bytes 3-8 of ACTPU." 875 ::= { snaPu20Entry 11 } 877 snaPu20HostDescription OBJECT-TYPE 878 SYNTAX DisplayString (SIZE(0..128)) 879 MAX-ACCESS read-only 880 STATUS current 881 DESCRIPTION 882 "The value identifies the remote host associated with this 883 node. Since SSCP Id's may not be unique across hosts, the host 884 description is required to uniquely identify the SSCP. 886 If the remote host is unknown, then the value is the null 887 string." 889 ::= { snaPu20Entry 12 } 891 snaPu20SscpName OBJECT-TYPE 892 SYNTAX OCTET STRING (SIZE(0 | 3..17)) 893 MAX-ACCESS read-only 894 STATUS current 895 DESCRIPTION 896 "The name of the SSCP that activated this 2.0 node. If an 897 ACTPU has not been received, a zero-length string is returned." 899 ::= { snaPu20Entry 13 } 901 snaPu20PuName OBJECT-TYPE 902 SYNTAX OCTET STRING (SIZE(0..17)) 903 MAX-ACCESS read-only 904 STATUS current 905 DESCRIPTION 906 "The name for this node received from the SSCP. If an ACTPU 907 has not been received, a zero-length string is returned." 909 ::= { snaPu20Entry 14 } 911 -- ******************************************************************** 912 -- The following table associates an SNA node with its link stations. 913 -- It represents configured information. 914 -- ******************************************************************** 916 snaNodeLinkAdminTable OBJECT-TYPE 917 SYNTAX SEQUENCE OF SnaNodeLinkAdminEntry 918 MAX-ACCESS not-accessible 919 STATUS current 920 DESCRIPTION 921 "This table associates an SNA node with its link stations, and 922 contains references to link-specific tables. If a node is 923 configured for multiple links, then the node will have multiple 924 entries in this table." 926 ::= { snaNode 6 } 928 snaNodeLinkAdminEntry OBJECT-TYPE 929 SYNTAX SnaNodeLinkAdminEntry 930 MAX-ACCESS not-accessible 931 STATUS current 932 DESCRIPTION 933 "Each entry contains configuration information associating 934 an SNA node with one of its link stations." 936 INDEX { snaNodeLinkAdminNodeName, 937 snaNodeLinkAdminLsName } 939 ::= { snaNodeLinkAdminTable 1 } 941 SnaNodeLinkAdminEntry ::= SEQUENCE { 942 snaNodeLinkAdminNodeName DisplayString, 943 snaNodeLinkAdminLsName DisplayString, 944 snaNodeLinkAdminSpecific RowPointer, 945 snaNodeLinkAdminMaxPiu Integer32 946 } 948 snaNodeLinkAdminNodeName OBJECT-TYPE 949 SYNTAX DisplayString (SIZE(1..17)) 950 MAX-ACCESS not-accessible 951 STATUS current 952 DESCRIPTION 953 "Locally-defined name of the node. In a type 2.1 node, this is 954 a fully qualified name, meaning that the node name is preceded 955 by the NetId (if present) with a period as the delimiter. 957 If this object has the same value as snaNodeName, then the two 958 entries being indexed apply to the same SNA node." 960 ::= { snaNodeLinkAdminEntry 1 } 962 snaNodeLinkAdminLsName OBJECT-TYPE 963 SYNTAX DisplayString (SIZE(1..10)) 964 MAX-ACCESS not-accessible 965 STATUS current 966 DESCRIPTION 967 "Administratively assigned name for the link station." 969 ::= { snaNodeLinkAdminEntry 2 } 971 snaNodeLinkAdminSpecific OBJECT-TYPE 972 SYNTAX RowPointer 973 MAX-ACCESS read-only 974 STATUS current 975 DESCRIPTION 976 "This value points to a row in a table containing configuration 977 information for the link instance associated with this node and 978 link station. It may, for example, point to a row in the 979 sdlcLSAdminTable defined in the SNA DLC MIB module." 981 ::= { snaNodeLinkAdminEntry 3 } 983 snaNodeLinkAdminMaxPiu OBJECT-TYPE 984 SYNTAX Integer32 985 MAX-ACCESS read-only 986 STATUS current 987 DESCRIPTION 988 "This value identifies the maximum number of octets that can be 989 exchanged in one Path Information Unit (PIU) by this node 990 through this link station. This is a configured value, which 991 the node will use the next time this link is established." 993 ::= { snaNodeLinkAdminEntry 4 } 995 -- ******************************************************************** 996 -- The following object is updated when there is a change to the value 997 -- of any object in the snaNodeLinkAdminTable. 998 -- ******************************************************************** 999 snaNodeLinkAdminTableLastChg OBJECT-TYPE 1000 SYNTAX DateAndTime 1001 MAX-ACCESS read-only 1002 STATUS current 1003 DESCRIPTION 1004 "The time of the last change made to any object in the 1005 snaNodeLinkAdminTable, including row deletions/additions. 1007 This object can be used to reduce frequent retrievals of the 1008 snaNodeLinkAdminTable by a Management Station. It is expected 1009 that a Management Station will periodically poll this object 1010 and compare its current value with the previous one. A 1011 difference indicates that some node configuration information 1012 has been changed. Only then will the Management Station 1013 retrieve the entire table." 1015 ::= { snaNode 7 } 1017 -- ******************************************************************** 1018 -- The following table associates an SNA node with its link stations. 1019 -- It represents current operational information. 1020 -- ******************************************************************** 1022 snaNodeLinkOperTable OBJECT-TYPE 1023 SYNTAX SEQUENCE OF SnaNodeLinkOperEntry 1024 MAX-ACCESS not-accessible 1025 STATUS current 1026 DESCRIPTION 1027 "This table associates an SNA node with its link stations, and 1028 contains references to link-specific tables. If a node has 1029 multiple links, then the node will have multiple entries in 1030 this table." 1032 ::= { snaNode 8 } 1034 snaNodeLinkOperEntry OBJECT-TYPE 1035 SYNTAX SnaNodeLinkOperEntry 1036 MAX-ACCESS not-accessible 1037 STATUS current 1038 DESCRIPTION 1039 "Each entry contains operational information associating an SNA 1040 node with one of its link stations." 1042 INDEX { snaNodeLinkOperNodeName, 1043 snaNodeLinkOperLsName } 1045 ::= { snaNodeLinkOperTable 1 } 1047 SnaNodeLinkOperEntry ::= SEQUENCE { 1048 snaNodeLinkOperNodeName DisplayString, 1049 snaNodeLinkOperLsName DisplayString, 1050 snaNodeLinkOperSpecific RowPointer, 1051 snaNodeLinkOperMaxPiu Integer32 1052 } 1054 snaNodeLinkOperNodeName OBJECT-TYPE 1055 SYNTAX DisplayString (SIZE(1..17)) 1056 MAX-ACCESS not-accessible 1057 STATUS current 1058 DESCRIPTION 1059 "Locally-defined name of the node. In a type 2.1 node, this is 1060 a fully qualified name, meaning that the node name is preceded 1061 by the NetId (if present) with a period as the delimiter. 1063 If this object has the same value as snaNodeName, then the two 1064 entries being indexed apply to the same SNA node." 1066 ::= { snaNodeLinkOperEntry 1 } 1068 snaNodeLinkOperLsName OBJECT-TYPE 1069 SYNTAX DisplayString (SIZE(1..10)) 1070 MAX-ACCESS not-accessible 1071 STATUS current 1072 DESCRIPTION 1073 "Administratively assigned name for the link station." 1075 ::= { snaNodeLinkOperEntry 2 } 1077 snaNodeLinkOperSpecific OBJECT-TYPE 1078 SYNTAX RowPointer 1079 MAX-ACCESS read-only 1080 STATUS current 1081 DESCRIPTION 1082 "This value points to a row in a table containing operational 1083 information for the link instance associated with this node and 1084 link station. It may, for example, point to a row in the 1085 sdlcLSOperTable defined in the SNA DLC MIB module." 1087 ::= { snaNodeLinkOperEntry 3 } 1089 snaNodeLinkOperMaxPiu OBJECT-TYPE 1090 SYNTAX Integer32 1091 MAX-ACCESS read-only 1092 STATUS current 1093 DESCRIPTION 1094 "This value identifies the maximum number of octets that can be 1095 exchanged in one Path Information Unit (PIU) by this node 1096 through this link station. This is the current operational 1097 value." 1099 ::= { snaNodeLinkOperEntry 4 } 1101 -- ******************************************************************** 1102 -- The following object is updated when there is a change to the value 1103 -- of any object in the snaNodeLinkOperTable. 1104 -- ******************************************************************** 1105 snaNodeLinkOperTableLastChg OBJECT-TYPE 1106 SYNTAX DateAndTime 1107 MAX-ACCESS read-only 1108 STATUS current 1109 DESCRIPTION 1110 "The time of the last change made to any object in the 1111 snaNodeLinkOperTable, including row deletions/additions. 1113 This object can be used to reduce frequent retrievals of the 1114 snaNodeLinkOperTable by a Management Station. It is expected 1115 that a Management Station will periodically poll this object 1116 and compare its current value with the previous one. A 1117 difference indicates that some node operational information has 1118 been changed. Only then will the Management Station retrieve 1119 the entire table." 1121 ::= { snaNode 9 } 1123 -- ******************************************************************** 1124 -- Traps 1125 -- ******************************************************************** 1127 snaNodeTraps OBJECT IDENTIFIER ::= { snaNode 10 } 1129 snaNodeStateChangeTrap NOTIFICATION-TYPE 1130 OBJECTS { snaNodeName, 1131 snaNodeOperState } 1132 STATUS current 1133 DESCRIPTION 1134 "This trap indicates that the operational state (i.e., the 1135 value of the snaNodeOperState object) of a node has changed. 1136 The following variables are returned: 1138 snaNodeName - name of the node being reported upon 1140 snaNodeOperState - state of the node after the change." 1142 ::= { snaNodeTraps 1 } 1144 snaNodeActFailTrap NOTIFICATION-TYPE 1145 OBJECTS { snaNodeName, 1146 snaNodeOperState, 1147 snaNodeActFailureReason } 1148 STATUS current 1149 DESCRIPTION 1150 "This trap indicates a node activation failure. The value of 1151 snaNodeOperState indicates the state of the node after the 1152 activation attempt. The value of snaNodeActFailureReason 1153 indicates the reason for the failure." 1155 ::= { snaNodeTraps 2 } 1157 -- ******************************************************************** 1158 -- snaLu group 1159 -- 1160 -- This group contains Managed Objects related to all dependent LUs, 1161 -- plus some specific objects for LUs of type 0, 1, 2, 3. 1162 -- 1163 -- An implementation having both dependent and independent LU 6.2s, or 1164 -- one having only independent LU 6.2s, reports on these LUs via the 1165 -- APPC MIB. An implementation having only dependent LU 6.2s reports on 1166 -- them via this MIB. 1167 -- ******************************************************************** 1169 -- ******************************************************************** 1170 -- snaLuAdminTable 1171 -- Objects in this table contain default or expected configuration 1172 -- values for local dependent LUs of types 0, 1, 2, 3, 4, 6.2, and 7. 1173 -- ******************************************************************** 1175 snaLuAdminTable OBJECT-TYPE 1176 SYNTAX SEQUENCE OF SnaLuAdminEntry 1177 MAX-ACCESS not-accessible 1178 STATUS current 1179 DESCRIPTION 1180 "This table contains LU configuration information." 1182 ::= { snaLu 1 } 1184 snaLuAdminEntry OBJECT-TYPE 1185 SYNTAX SnaLuAdminEntry 1186 MAX-ACCESS not-accessible 1187 STATUS current 1188 DESCRIPTION 1189 "Contains configuration variables for an LU." 1191 INDEX { snaLuAdminNodeName, 1192 snaLuAdminLuName } 1194 ::= { snaLuAdminTable 1 } 1196 SnaLuAdminEntry ::= SEQUENCE { 1197 snaLuAdminNodeName DisplayString, 1198 snaLuAdminLuName DisplayString, 1199 snaLuAdminUserLuName DisplayString, 1200 snaLuAdminType INTEGER, 1201 snaLuAdminLocalAddress OCTET STRING, 1202 snaLuAdminDisplayModel INTEGER, 1203 snaLuAdminTerm INTEGER 1204 } 1206 snaLuAdminNodeName OBJECT-TYPE 1207 SYNTAX DisplayString 1208 MAX-ACCESS not-accessible 1209 STATUS current 1210 DESCRIPTION 1211 "The value indicates the locally-defined name of the node 1212 through which the LU is to be activated. In a type 2.1 node, 1213 this is a fully qualified name, meaning that the node name is 1214 preceded by the NetId (if present) with a period as the 1215 delimiter. 1217 If this object has the same value as snaNodeName, then the two 1218 entries being indexed apply to the same SNA node." 1220 ::= { snaLuAdminEntry 1 } 1222 snaLuAdminLuName OBJECT-TYPE 1223 SYNTAX DisplayString (SIZE(1..17)) 1224 MAX-ACCESS not-accessible 1225 STATUS current 1226 DESCRIPTION 1227 "This value identifies the locally-defined SNA LU name used in 1228 exchange of SNA data." 1230 ::= { snaLuAdminEntry 2 } 1232 snaLuAdminUserLuName OBJECT-TYPE 1233 SYNTAX DisplayString (SIZE(0..48)) 1234 MAX-ACCESS read-only 1235 STATUS current 1236 DESCRIPTION 1237 "This value identifies the user configurable name for this LU. 1238 If a name is not assigned to the LU, then this object contains 1239 a zero length string." 1241 ::= { snaLuAdminEntry 3 } 1243 snaLuAdminType OBJECT-TYPE 1244 SYNTAX INTEGER { 1245 other(1), 1246 lu0(2), 1247 lu1(3), 1248 lu2(4), 1249 lu3(5), 1250 lu4(6), 1251 lu62(7), -- dependent only 1252 lu7(8), 1253 unknown(255) 1254 } 1255 MAX-ACCESS read-only 1256 STATUS current 1257 DESCRIPTION 1258 "This value identifies the LU type." 1260 ::= { snaLuAdminEntry 4 } 1262 snaLuAdminLocalAddress OBJECT-TYPE 1263 SYNTAX OCTET STRING (SIZE(1)) 1264 MAX-ACCESS read-only 1265 STATUS current 1266 DESCRIPTION 1267 "The local address for this LU is a byte with a value ranging 1268 from 1 to 254." 1270 ::= { snaLuAdminEntry 5 } 1272 snaLuAdminDisplayModel OBJECT-TYPE 1273 SYNTAX INTEGER { 1274 invalid(1), 1275 model2A(2), 1276 model2B(3), 1277 model3A(4), 1278 model3B(5), 1279 model4A(6), 1280 model4B(7), 1281 model5A(8), 1282 model5B(9), 1283 dynamic(10) 1284 } 1285 MAX-ACCESS read-only 1286 STATUS current 1287 DESCRIPTION 1288 "The value of this object identifies the model type and screen 1289 size of the terminal connected to the host. This is only valid 1290 for LU Type 2. The values have the following meaning: 1292 model2A(2) - Model 2 (24 rows x 80 columns) with base 1293 attributes 1294 model2B(3) - Model 2 (24 rows x 80 columns) with extended 1295 attributes 1296 model3A(4) - Model 3 (32 rows x 80 columns) with base 1297 attributes 1298 model3B(5) - Model 3 (32 rows x 80 columns) with extended 1299 attributes 1300 model4A(6) - Model 4 (43 rows x 80 columns) with base 1301 attributes 1302 model4B(7) - Model 4 (43 rows x 80 columns) with extended 1303 attributes 1304 model5A(8) - Model 5 (27 rows x 132 columns) with base 1305 attributes 1306 model5B(9) - Model 5 (27 rows x 132 columns) with extended 1307 attributes 1308 dynamic(10)- Screen size determine with BIND and Read 1309 Partition Query. 1311 In case this LU is not Type 2, then this object contains the 1312 invalid(1) value." 1314 ::= { snaLuAdminEntry 6 } 1316 snaLuAdminTerm OBJECT-TYPE 1317 SYNTAX INTEGER { 1318 unbind(1), 1319 termself(2), 1320 rshutd(3), 1321 poweroff(4) 1322 } 1323 MAX-ACCESS read-only 1324 STATUS current 1325 DESCRIPTION 1326 "This value identifies the desired method for deactivation of 1327 this LU. This value overrides the default method 1328 (snaNodeLuTermDefault) for this node. 1330 For LU6.2s, 'unbind(1)' is the only valid value. 1332 unbind(1) - terminate the LU-LU session by sending 1333 an SNA UNBIND request. 1334 termself(2) - terminate the LU-LU session by sending 1335 an SNA TERM-SELF (Terminate Self) 1336 request on the SSCP-LU session. The 1337 SSCP will inform the remote session LU 1338 partner to send an UNBIND request to 1339 terminate the session. 1340 rshutd(3) - terminate the LU-LU session by sending 1341 an SNA RSHUTD (Request ShutDown) request 1342 to the remote session LU partner. 1343 The remote LU will then send an UNBIND 1344 request to terminate the session. 1345 poweroff(4) - terminate the LU-LU session by sending 1346 either an SNA LUSTAT (LU Status) request 1347 on the LU-LU session or an SNA NOTIFY 1348 request on the SSCP-LU session indicating 1349 that the LU has been powered off. Sending 1350 both is also acceptable. The result 1351 should be that the remote session LU 1352 partner will send an UNBIND to terminate 1353 the session." 1355 ::= { snaLuAdminEntry 7 } 1357 -- ******************************************************************** 1358 -- snaLuOperTable 1359 -- Objects in this table contain current operational values, such as 1360 -- state values or negotiated parameters, for local dependent LUs of 1361 -- types 0, 1, 2, 3, 4, 6.2, and 7. 1362 -- ******************************************************************** 1364 snaLuOperTable OBJECT-TYPE 1365 SYNTAX SEQUENCE OF SnaLuOperEntry 1366 MAX-ACCESS not-accessible 1367 STATUS current 1368 DESCRIPTION 1369 "This table contains dynamic run-time information and control 1370 variables relating to LUs. Only objects which are common to 1371 all types of LUs are included in this table." 1373 ::= { snaLu 2 } 1375 snaLuOperEntry OBJECT-TYPE 1376 SYNTAX SnaLuOperEntry 1377 MAX-ACCESS not-accessible 1378 STATUS current 1379 DESCRIPTION 1380 "Contains objects reflecting current information for an LU. 1381 Each entry is created by the Agent. All entries have read-only 1382 access." 1384 INDEX { snaLuOperNodeName, 1385 snaLuOperLuName } 1387 ::= { snaLuOperTable 1 } 1389 SnaLuOperEntry ::= SEQUENCE { 1390 snaLuOperNodeName DisplayString, 1391 snaLuOperLuName DisplayString, 1392 snaLuOperUserLuName DisplayString, 1393 snaLuOperSscpSuppliedName DisplayString, 1394 snaLuOperType INTEGER, 1395 snaLuOperLocalAddress OCTET STRING, 1396 snaLuOperDisplayModel INTEGER, 1397 snaLuOperTerm INTEGER, 1398 snaLuOperState INTEGER 1399 } 1401 snaLuOperNodeName OBJECT-TYPE 1402 SYNTAX DisplayString (SIZE(1..17)) 1403 MAX-ACCESS not-accessible 1404 STATUS current 1405 DESCRIPTION 1406 "The value indicates the locally-defined name of the node 1407 through which the LU was activated. In a type 2.1 node, this 1408 is a fully qualified name, meaning that the node name is 1409 preceded by the NetId (if present) with a period as the 1410 delimiter. 1412 If this object has the same value as snaNodeName, then the two 1413 entries being indexed apply to the same SNA node." 1415 ::= { snaLuOperEntry 1 } 1417 snaLuOperLuName OBJECT-TYPE 1418 SYNTAX DisplayString (SIZE(1..17)) 1419 MAX-ACCESS not-accessible 1420 STATUS current 1421 DESCRIPTION 1422 "This value identifies the locally-defined SNA LU name used in 1423 exchanging SNA data. 1425 If this object has the same value as snaLuAdminLuName, then the 1426 two entries being indexed apply to the same LU." 1428 ::= { snaLuOperEntry 2 } 1430 snaLuOperUserLuName OBJECT-TYPE 1431 SYNTAX DisplayString (SIZE(0..48)) 1432 MAX-ACCESS read-only 1433 STATUS current 1434 DESCRIPTION 1435 "User configurable name for this LU. If a name is not 1436 assigned, then this object contains a zero-length string." 1438 ::= { snaLuOperEntry 3 } 1440 snaLuOperSscpSuppliedName OBJECT-TYPE 1441 SYNTAX DisplayString (SIZE(0..17)) 1442 MAX-ACCESS read-only 1443 STATUS current 1444 DESCRIPTION 1445 "The value identifies the SNA name of the LU. This name is 1446 supplied to a dependent LU by the SSCP that activated it. If a 1447 value was not supplied, a zero-length string is returned." 1449 ::= { snaLuOperEntry 4 } 1451 snaLuOperType OBJECT-TYPE 1452 SYNTAX INTEGER { 1453 other(1), 1454 lu0(2), 1455 lu1(3), 1456 lu2(4), 1457 lu3(5), 1458 lu4(6), 1459 lu62(7), 1460 lu7(8) 1461 } 1462 MAX-ACCESS read-only 1463 STATUS current 1464 DESCRIPTION 1465 "The value identifies the current LU type." 1467 ::= { snaLuOperEntry 5 } 1469 snaLuOperLocalAddress OBJECT-TYPE 1470 SYNTAX OCTET STRING (SIZE(1)) 1471 MAX-ACCESS read-only 1472 STATUS current 1473 DESCRIPTION 1474 "The local address for this LU is a byte with a value ranging 1475 from 1 to 254." 1477 ::= { snaLuOperEntry 6 } 1479 snaLuOperDisplayModel OBJECT-TYPE 1480 SYNTAX INTEGER { 1481 invalid(1), 1482 model2A(2), 1483 model2B(3), 1484 model3A(4), 1485 model3B(5), 1486 model4A(6), 1487 model4B(7), 1488 model5A(8), 1489 model5B(9), 1490 dynamic(10) 1491 } 1492 MAX-ACCESS read-only 1493 STATUS current 1494 DESCRIPTION 1495 "The value of this object identifies the model type and screen 1496 size of the terminal connected to the host. This is only valid 1497 for LU Type 2. The values have the following meaning: 1499 model2A(2) - Model 2 (24 rows x 80 columns) with base 1500 attributes 1501 model2B(3) - Model 2 (24 rows x 80 columns) with extended 1502 attributes 1503 model3A(4) - Model 3 (32 rows x 80 columns) with base 1504 attributes 1506 model3B(5) - Model 3 (32 rows x 80 columns) with extended 1507 attributes 1508 model4A(6) - Model 4 (43 rows x 80 columns) with base 1509 attributes 1510 model4B(7) - Model 4 (43 rows x 80 columns) with extended 1511 attributes 1512 model5A(8) - Model 5 (27 rows x 132 columns) with base 1513 attributes 1514 model5B(9) - Model 5 (27 rows x 132 columns) with extended 1515 attributes 1516 dynamic(10)- Screen size determine with BIND and Read 1517 Partition Query. 1519 In case this LU is not Type 2, then this object contains the 1520 invalid(1) value." 1522 ::= { snaLuOperEntry 7 } 1524 snaLuOperTerm OBJECT-TYPE 1525 SYNTAX INTEGER { 1526 unbind(1), 1527 termself(2), 1528 rshutd(3), 1529 poweroff(4) 1530 } 1531 MAX-ACCESS read-only 1532 STATUS current 1533 DESCRIPTION 1534 "The value identifies the current method for deactivation of 1535 this LU. This value overrides the default method 1536 (snaNodeLuTermDefault) for this node. 1538 For LU6.2s, 'unbind(1)' is the only valid value. 1540 unbind(1) - terminate the LU-LU session by sending 1541 an SNA UNBIND request. 1542 termself(2) - terminate the LU-LU session by sending 1543 an SNA TERM-SELF (Terminate Self) 1544 request on the SSCP-LU session. The 1545 SSCP will inform the remote session LU 1546 partner to send an UNBIND request to 1547 terminate the session. 1548 rshutd(3) - terminate the LU-LU session by sending 1549 an SNA RSHUTD (Request ShutDown) request 1550 to the remote session LU partner. 1551 The remote LU will then send an UNBIND 1552 request to terminate the session. 1553 poweroff(4) - terminate the LU-LU session by sending 1554 either an SNA LUSTAT (LU Status) request 1555 on the LU-LU session or an SNA NOTIFY 1556 request on the SSCP-LU session indicating 1557 that the LU has been powered off. Sending 1558 both is also acceptable. The result 1559 should be that the remote session LU 1560 partner will send an UNBIND to terminate 1561 the session." 1563 ::= { snaLuOperEntry 8 } 1565 snaLuOperState OBJECT-TYPE 1566 SYNTAX INTEGER { 1567 inactive(1), 1568 active(2) 1569 } 1570 MAX-ACCESS read-only 1571 STATUS current 1572 DESCRIPTION 1573 "The value identifies the current operational state of this LU. 1574 The values indicate the following: 1576 inactive(1) - LU didn't receive an ACTLU, or it received a 1577 DACTLU, or it received an ACTLU and returned a 1578 negative response 1580 active(2) - LU received an ACTLU and returned a positive 1581 response." 1583 ::= { snaLuOperEntry 9 } 1585 -- ******************************************************************** 1586 -- The following table contains information for active LU-LU sessions. 1587 -- ******************************************************************** 1589 snaLuActSessTable OBJECT-TYPE 1590 SYNTAX SEQUENCE OF SnaLuActSessEntry 1591 MAX-ACCESS not-accessible 1592 STATUS current 1593 DESCRIPTION 1594 "This table contains objects that describe the operational 1595 state of LU-LU sessions. Only objects common to all types of 1596 LUs are included in this table. 1598 When a session's snaLuActSessOperState value changes to 1599 'pendingBind(2)', then the corresponding entry in this table is 1600 created by the Agent. 1602 When a session's snaLuActSessOperState value changes to 1603 'unbound(1)', then the entry for the session is removed from 1604 this table by the Agent." 1606 ::= { snaLu 3 } 1608 snaLuActSessEntry OBJECT-TYPE 1609 SYNTAX SnaLuActSessEntry 1610 MAX-ACCESS not-accessible 1611 STATUS current 1612 DESCRIPTION 1613 "An entry contains dynamic parameters for an LU-LU session. 1614 The indices identify the node, local LU, and remote LU for this 1615 session." 1617 INDEX { snaLuActSessNodeName, 1618 snaLuActSessLocLuName, 1619 snaLuActSessIndex } 1620 ::= { snaLuActSessTable 1 } 1622 SnaLuActSessEntry ::= SEQUENCE { 1623 snaLuActSessNodeName DisplayString, 1624 snaLuActSessLocLuName DisplayString, 1625 snaLuActSessIndex Integer32, 1626 snaLuActSessOperState INTEGER, 1627 snaLuActSessParLuIndex RowPointer, 1628 snaLuActSessLocalApplName DisplayString, 1629 snaLuActSessParLuName DisplayString, 1630 snaLuActSessMaxSndRuSize INTEGER, 1631 snaLuActSessMaxRcvRuSize INTEGER, 1632 snaLuActSessSndPacingSize INTEGER, 1633 snaLuActSessRcvPacingSize INTEGER, 1634 snaLuActSessUpTime TimeTicks, 1635 snaLuActSessLinkIndex RowPointer 1636 } 1638 snaLuActSessNodeName OBJECT-TYPE 1639 SYNTAX DisplayString (SIZE(1..17)) 1640 MAX-ACCESS not-accessible 1641 STATUS current 1642 DESCRIPTION 1643 "The value indicates the locally-defined name of the node 1644 through which the LU for this session was activated. In a type 1645 2.1 node, this is a fully qualified name, meaning that the node 1646 name is preceded by the NetId (if present) with a period as the 1647 delimiter. 1649 If this object has the same value as snaNodeName, then the two 1650 entries being indexed apply to the same SNA node." 1652 ::= { snaLuActSessEntry 1 } 1654 snaLuActSessLocLuName OBJECT-TYPE 1655 SYNTAX DisplayString (SIZE(1..17)) 1656 MAX-ACCESS not-accessible 1657 STATUS current 1658 DESCRIPTION 1659 "This value identifies the locally-defined SNA LU name for the 1660 session's local LU. 1662 If this object has the same value as snaLuAdminLuName, then the 1663 two entries being indexed apply to the same LU." 1665 ::= { snaLuActSessEntry 2 } 1667 snaLuActSessIndex OBJECT-TYPE 1668 SYNTAX Integer32 1669 MAX-ACCESS not-accessible 1670 STATUS current 1671 DESCRIPTION 1672 "This value identifies the unique index of the session. It is 1673 recommended that an Agent should not reuse the index of a 1674 deactivated session for a significant period of time (e.g., one 1675 week)." 1677 ::= { snaLuActSessEntry 3 } 1679 snaLuActSessOperState OBJECT-TYPE 1680 SYNTAX INTEGER { 1681 unbound(1), 1682 pendingBind(2), 1683 bound(3), 1684 pendingUnbind(4) 1685 } 1686 MAX-ACCESS read-write 1687 STATUS current 1688 DESCRIPTION 1689 "The value indicates the current operational state of the 1690 session. 1692 'unbound(1)' - session has been unbound; when a 1693 session enters this state, the Agent 1694 removes its entry from this table 1696 'pendingBind(2)' - waiting for a BIND from the host; when 1697 a session enters this state, the Agent 1698 creates an entry for it in this table 1700 'bound(3)' - session has been successfully bound. 1702 'pendingUnbind(4)' - session is in this state between the 1703 time when an UNBIND is sent and that 1704 when the rsp(UNBIND) is received. 1706 Session deactivation: 1708 If a session is in the operational state 'bound(3)' then 1709 setting the value of this object to 'unbound(1)' will 1710 initiate the session shutdown. 1712 If a session is in the operational state 'pendingBind(2)' 1713 then setting the value of this object to 'unbound(1)' will 1714 initiate the session shutdown. 1716 If a session is in the operational state 'pendingUnbind(4)' 1717 for an abnormally long period of time (e.g., three minutes) 1718 then setting the value of this object to 'unbound(1)' will 1719 change the session operational state to 'unbound(1)'." 1721 ::= { snaLuActSessEntry 4 } 1723 snaLuActSessParLuIndex OBJECT-TYPE 1724 SYNTAX RowPointer 1725 MAX-ACCESS read-only 1726 STATUS current 1727 DESCRIPTION 1728 "This value may be used to identify information about the 1729 session partner LU in a table of information about remote LUs. 1730 Such a table is not defined in this document. 1732 If a table of remote LU information is not implemented, or if 1733 the table is implemented but it does not contain information 1734 about the partner LU for a particular session, then this object 1735 shall have the value zeroDotZero defined in SNMPv2-SMI." 1737 ::= { snaLuActSessEntry 5 } 1739 snaLuActSessLocalApplName OBJECT-TYPE 1740 SYNTAX DisplayString (SIZE(0..48)) 1741 MAX-ACCESS read-only 1742 STATUS current 1743 DESCRIPTION 1744 "The name of the local application using this LU. If the local 1745 application is unknown, then this object contains a zero-length 1746 string." 1747 ::= { snaLuActSessEntry 6 } 1749 snaLuActSessParLuName OBJECT-TYPE 1750 SYNTAX DisplayString (SIZE(0..17)) 1751 MAX-ACCESS read-only 1752 STATUS current 1753 DESCRIPTION 1754 "The name of the partner LU for the session. If the partner's 1755 LU name is unknown, then this object contains a zero-length 1756 string." 1758 ::= { snaLuActSessEntry 7 } 1760 snaLuActSessMaxSndRuSize OBJECT-TYPE 1761 SYNTAX INTEGER (1..8192) 1762 UNITS "bytes" 1763 MAX-ACCESS read-only 1764 STATUS current 1765 DESCRIPTION 1766 "The maximum RU size used on this session for sending RUs." 1768 ::= { snaLuActSessEntry 8 } 1770 snaLuActSessMaxRcvRuSize OBJECT-TYPE 1771 SYNTAX INTEGER (1..8192) 1772 UNITS "bytes" 1773 MAX-ACCESS read-only 1774 STATUS current 1775 DESCRIPTION 1776 "The maximum RU size used on this session for receiving RUs." 1778 ::= { snaLuActSessEntry 9 } 1780 snaLuActSessSndPacingSize OBJECT-TYPE 1781 SYNTAX INTEGER (1..63) 1782 MAX-ACCESS read-only 1783 STATUS current 1784 DESCRIPTION 1785 "The size of the send pacing window on this session." 1787 ::= { snaLuActSessEntry 10 } 1789 snaLuActSessRcvPacingSize OBJECT-TYPE 1790 SYNTAX INTEGER (1..63) 1791 MAX-ACCESS read-only 1792 STATUS current 1793 DESCRIPTION 1794 "The size of the receive pacing window on this session." 1796 ::= { snaLuActSessEntry 11 } 1798 snaLuActSessUpTime OBJECT-TYPE 1799 SYNTAX TimeTicks 1800 UNITS "hundredths of a second" 1801 MAX-ACCESS read-only 1802 STATUS current 1803 DESCRIPTION 1804 "The length of time the session has been active, measured in 1805 hundredths of a second." 1807 ::= { snaLuActSessEntry 12 } 1809 snaLuActSessLinkIndex OBJECT-TYPE 1810 SYNTAX RowPointer 1811 MAX-ACCESS read-only 1812 STATUS current 1813 DESCRIPTION 1814 "This value identifies the link over which the session passes. 1815 It is an index into snaNodeLinkAdminTable. If the index value 1816 is not known, this object shall have the value zeroDotZero 1817 defined in SNMPv2-SMI." 1819 ::= { snaLuActSessEntry 13 } 1821 -- ********************************************************************* 1822 -- SNA LU Historical Session Table 1823 -- --------------------------------------------------------------------- 1824 -- This table contains historical information about LU-LU sessions that 1825 -- terminated abnormally. It is an implementation choice how long to 1826 -- retain information on a given session. 1827 -- ********************************************************************* 1828 snaLuHistSessTable OBJECT-TYPE 1829 SYNTAX SEQUENCE OF SnaLuHistSessEntry 1830 MAX-ACCESS not-accessible 1831 STATUS current 1832 DESCRIPTION 1833 "Table of historical information about LU-LU sessions that 1834 terminated abnormally. It is an implementation choice how long 1835 to retain information about a given session." 1837 ::= { snaLu 4 } 1839 snaLuHistSessEntry OBJECT-TYPE 1840 SYNTAX SnaLuHistSessEntry 1841 MAX-ACCESS not-accessible 1842 STATUS current 1843 DESCRIPTION 1844 "Entry of SNA LU Session History Table. This table is indexed 1845 by an integer which is continuously incremented until it 1846 eventually wraps." 1848 INDEX 1849 { snaLuHistSessIndex } 1851 ::= { snaLuHistSessTable 1 } 1853 SnaLuHistSessEntry ::= SEQUENCE { 1854 snaLuHistSessIndex INTEGER, 1855 snaLuHistSessNodeName DisplayString, 1856 snaLuHistSessLocLuName DisplayString, 1857 snaLuHistSessParLuName DisplayString, 1858 snaLuHistSessTime DateAndTime, 1859 snaLuHistSessSenseData SnaSenseData, 1860 snaLuHistSessTerminationRu INTEGER, 1861 snaLuHistSessUnbindType OCTET STRING 1862 } 1864 snaLuHistSessIndex OBJECT-TYPE 1865 SYNTAX INTEGER (0..2147483647) 1866 MAX-ACCESS not-accessible 1867 STATUS current 1868 DESCRIPTION 1869 "Table index. The value of the index begins at zero 1870 and is incremented up to a maximum value of 2**31-1 1871 (2,147,483,647) before wrapping." 1873 ::= { snaLuHistSessEntry 1 } 1875 snaLuHistSessNodeName OBJECT-TYPE 1876 SYNTAX DisplayString (SIZE(1..17)) 1877 MAX-ACCESS read-only 1878 STATUS current 1879 DESCRIPTION 1880 "The value indicates the locally-defined name of the node 1881 through which the LU for this session was activated. In a type 1882 2.1 node, this is a fully qualified name, meaning that the node 1883 name is preceded by the NetId (if present) with a period as the 1884 delimiter. 1886 If this object has the same value as snaNodeName, then the two 1887 entries being indexed apply to the same SNA node." 1889 ::= { snaLuHistSessEntry 2 } 1891 snaLuHistSessLocLuName OBJECT-TYPE 1892 SYNTAX DisplayString (SIZE(1..17)) 1893 MAX-ACCESS read-only 1894 STATUS current 1895 DESCRIPTION 1896 "This value identifies the locally-defined SNA LU name for the 1897 session's local LU. 1899 If this object has the same value as snaLuAdminLuName, then the 1900 two entries being indexed apply to the same LU." 1902 ::= { snaLuHistSessEntry 3 } 1904 snaLuHistSessParLuName OBJECT-TYPE 1905 SYNTAX DisplayString (SIZE(0..17)) 1906 MAX-ACCESS read-only 1907 STATUS current 1908 DESCRIPTION 1909 "The name of the partner LU for the session. If the partner's 1910 LU name is unknown, then this object contains a zero-length 1911 string." 1913 ::= { snaLuHistSessEntry 4 } 1915 snaLuHistSessTime OBJECT-TYPE 1916 SYNTAX DateAndTime 1917 MAX-ACCESS read-only 1918 STATUS current 1919 DESCRIPTION 1920 "The time at which the session was either terminated or 1921 failed to be established." 1923 ::= { snaLuHistSessEntry 5 } 1925 snaLuHistSessSenseData OBJECT-TYPE 1926 SYNTAX SnaSenseData 1927 MAX-ACCESS read-only 1928 STATUS current 1929 DESCRIPTION 1930 "The value identifies the sense data when there is a BIND 1931 failure. It is taken from the negative BIND response or UNBIND 1932 request." 1934 ::= { snaLuHistSessEntry 6 } 1936 snaLuHistSessTerminationRu OBJECT-TYPE 1937 SYNTAX INTEGER { 1938 other(1), 1939 bindFailure(2), 1940 unbind(3) 1941 } 1942 MAX-ACCESS read-only 1943 STATUS current 1944 DESCRIPTION 1945 "The value identifies the SNA RU that terminated the session." 1947 ::= { snaLuHistSessEntry 7 } 1949 snaLuHistSessUnbindType OBJECT-TYPE 1950 SYNTAX OCTET STRING (SIZE(0..1)) 1951 MAX-ACCESS read-only 1952 STATUS current 1953 DESCRIPTION 1954 "If the session was terminated by an UNBIND, then this object 1955 contains the UNBIND type value (byte 1 of the UNBIND RU); 1956 otherwise the string is null." 1958 ::= { snaLuHistSessEntry 8 } 1960 -- ******************************************************************** 1961 -- The following group covers statistics collection for LU-Lu sessions. 1962 -- ******************************************************************** 1963 snaLuSessStats OBJECT IDENTIFIER ::= {snaLu 5 } 1965 snaLuSessCntrlOperStat OBJECT-TYPE 1966 SYNTAX INTEGER { 1967 notActive(1), 1968 active(2) 1969 } 1970 MAX-ACCESS read-only 1971 STATUS current 1972 DESCRIPTION 1973 "Indicates the current collection option in effect: 1975 notActive collection of session statistics is not active. 1976 active collection of session statistics is active. 1978 Statistical entries are present in the snaLuSessStatsTable 1979 only when the value of this object is 'active'." 1981 ::= { snaLuSessStats 1 } 1983 snaLuSessCntrlAdminStat OBJECT-TYPE 1984 SYNTAX INTEGER { 1985 notActive(1), 1986 active(2) 1987 } 1988 MAX-ACCESS read-write 1989 STATUS current 1990 DESCRIPTION 1991 "Indicates the desired state of statistics collection: 1993 notActive collection of session statistics is not active. 1994 active collection of session statistics is active. 1996 When this object is set to notActive, all of the entries are 1997 removed from the snaLuSessStatsTable." 1999 ::= { snaLuSessStats 2 } 2001 -- ******************************************************************** 2002 -- The following table contains session statistics for LU-LU sessions. 2003 -- ******************************************************************** 2005 snaLuSessStatsTable OBJECT-TYPE 2006 SYNTAX SEQUENCE OF SnaLuSessStatsEntry 2007 MAX-ACCESS not-accessible 2008 STATUS current 2009 DESCRIPTION 2010 "This table contains dynamic statistics information relating to 2011 active LU-LU sessions. The entries in this table cannot be 2012 created by a Management Station." 2014 ::= { snaLuSessStats 3 } 2016 snaLuSessStatsEntry OBJECT-TYPE 2017 SYNTAX SnaLuSessStatsEntry 2018 MAX-ACCESS not-accessible 2019 STATUS current 2020 DESCRIPTION 2021 "Contains statistics information for LU-LU sessions. Each 2022 entry is created by the Agent. Objects in this table have 2023 read-only access. Each session from snaLuActSessTable has one 2024 entry in this table." 2026 INDEX { snaLuSessStatsNodeName, 2027 snaLuSessStatsLuName, 2028 snaLuSessStatsParLuName, 2029 snaLuSessStatsSessIndex } 2031 ::= { snaLuSessStatsTable 1 } 2033 SnaLuSessStatsEntry ::= SEQUENCE { 2034 snaLuSessStatsNodeName DisplayString, 2035 snaLuSessStatsLuName DisplayString, 2036 snaLuSessStatsParLuName DisplayString, 2037 snaLuSessStatsSessIndex Integer32, 2038 snaLuSessStatsSentFmdBytes Counter32, 2039 snaLuSessStatsSentNonFmdBytes Counter32, 2040 snaLuSessStatsRcvdFmdBytes Counter32, 2041 snaLuSessStatsRcvdNonFmdBytes Counter32, 2042 snaLuSessStatsSentFmdRus Counter32, 2043 snaLuSessStatsSentNonFmdRus Counter32, 2044 snaLuSessStatsRcvdFmdRus Counter32, 2045 snaLuSessStatsRcvdNonFmdRus Counter32, 2046 snaLuSessStatsSentNegRsps Counter32, 2047 snaLuSessStatsRcvdNegRsps Counter32 2048 } 2050 snaLuSessStatsNodeName OBJECT-TYPE 2051 SYNTAX DisplayString (SIZE (1..17)) 2052 MAX-ACCESS not-accessible 2053 STATUS current 2054 DESCRIPTION 2055 "Locally-defined name of the node through which the local LU 2056 for this session was activated. In a type 2.1 node, this is a 2057 fully qualified name, meaning that the node name is preceded by 2058 the NetId (if present) with a period as the delimiter. 2060 If this object has the same value as snaNodeName, then the two 2061 entries being indexed apply to the same SNA node." 2063 ::= { snaLuSessStatsEntry 1 } 2065 snaLuSessStatsLuName OBJECT-TYPE 2066 SYNTAX DisplayString (SIZE (1..17)) 2067 MAX-ACCESS not-accessible 2068 STATUS current 2069 DESCRIPTION 2070 "Specifies the name of the local LU for the session. This 2071 field is from 1 to 17 characters in length, including a period 2072 (.) which separates the NetId from the NAU name if the NetId is 2073 present. 2075 If this object has the same value as snaLuOperLuName, then the 2076 two entries being indexed apply to the same resource 2077 (specifically, to the same local LU)." 2079 ::= { snaLuSessStatsEntry 2 } 2081 snaLuSessStatsParLuName OBJECT-TYPE 2082 SYNTAX DisplayString (SIZE (1..17)) 2083 MAX-ACCESS not-accessible 2084 STATUS current 2085 DESCRIPTION 2086 "Specifies the name of the partner LU for the session. This 2087 field is from 1 to 17 characters in length, including a period 2088 (.) which separates the NetId from the NAU name if the NetId is 2089 present. 2091 If this object has the same value as snaLuActSessParLuName, 2092 then the two entries being indexed apply to the same resource 2093 (specifically, to the same partner LU)." 2095 ::= { snaLuSessStatsEntry 3 } 2097 snaLuSessStatsSessIndex OBJECT-TYPE 2098 SYNTAX Integer32 2099 MAX-ACCESS not-accessible 2100 STATUS current 2101 DESCRIPTION 2102 "This value identifies the index of the session, which is 2103 unique for this LU pair. It is recommended that an Agent not 2104 reuse the index of a deactivated session for a significant 2105 period of time (e.g., one week). 2107 If this object has the same value as snaLuActSessIndex for the 2108 same LU pair, then the two entries being indexed apply to the 2109 same resource (specifically, to the same session)." 2111 ::= { snaLuSessStatsEntry 4 } 2113 snaLuSessStatsSentFmdBytes OBJECT-TYPE 2114 SYNTAX Counter32 2115 MAX-ACCESS read-only 2116 STATUS current 2117 DESCRIPTION 2118 "The number of function management data (FMD) bytes sent by the 2119 local LU." 2121 ::= { snaLuSessStatsEntry 5 } 2123 snaLuSessStatsSentNonFmdBytes OBJECT-TYPE 2124 SYNTAX Counter32 2125 MAX-ACCESS read-only 2126 STATUS current 2127 DESCRIPTION 2128 "The number of non-function management data (non-FMD) bytes 2129 sent by the local LU." 2131 ::= { snaLuSessStatsEntry 6 } 2133 snaLuSessStatsRcvdFmdBytes OBJECT-TYPE 2134 SYNTAX Counter32 2135 MAX-ACCESS read-only 2136 STATUS current 2137 DESCRIPTION 2138 "The number of function management data (FMD) bytes received by 2139 the local LU." 2141 ::= { snaLuSessStatsEntry 7 } 2143 snaLuSessStatsRcvdNonFmdBytes OBJECT-TYPE 2144 SYNTAX Counter32 2145 MAX-ACCESS read-only 2146 STATUS current 2147 DESCRIPTION 2148 "The number of non-function management data (non-FMD) bytes 2149 received by the local LU." 2151 ::= { snaLuSessStatsEntry 8 } 2153 snaLuSessStatsSentFmdRus OBJECT-TYPE 2154 SYNTAX Counter32 2155 MAX-ACCESS read-only 2156 STATUS current 2157 DESCRIPTION 2158 "The number of function management data (FMD) RUs sent by the 2159 local LU." 2161 ::= { snaLuSessStatsEntry 9 } 2163 snaLuSessStatsSentNonFmdRus OBJECT-TYPE 2164 SYNTAX Counter32 2165 MAX-ACCESS read-only 2166 STATUS current 2167 DESCRIPTION 2168 "The number of non-function management data (non-FMD) RUs sent 2169 by the local LU." 2171 ::= { snaLuSessStatsEntry 10 } 2173 snaLuSessStatsRcvdFmdRus OBJECT-TYPE 2174 SYNTAX Counter32 2175 MAX-ACCESS read-only 2176 STATUS current 2177 DESCRIPTION 2178 "The number of function management data (FMD) RUs received by 2179 the local LU." 2181 ::= { snaLuSessStatsEntry 11 } 2183 snaLuSessStatsRcvdNonFmdRus OBJECT-TYPE 2184 SYNTAX Counter32 2185 MAX-ACCESS read-only 2186 STATUS current 2187 DESCRIPTION 2188 "The number of non-function management data (non-FMD) RUs 2189 received by the local LU." 2191 ::= { snaLuSessStatsEntry 12 } 2193 snaLuSessStatsSentNegRsps OBJECT-TYPE 2194 SYNTAX Counter32 2195 MAX-ACCESS read-only 2196 STATUS current 2197 DESCRIPTION 2198 "The number of negative responses sent by the local LU." 2200 ::= { snaLuSessStatsEntry 13 } 2202 snaLuSessStatsRcvdNegRsps OBJECT-TYPE 2203 SYNTAX Counter32 2204 MAX-ACCESS read-only 2205 STATUS current 2206 DESCRIPTION 2207 "The number of negative responses received by the local LU." 2209 ::= { snaLuSessStatsEntry 14 } 2211 -- ******************************************************************** 2212 -- Traps 2213 -- ******************************************************************** 2215 snaLuTraps OBJECT IDENTIFIER ::= { snaLu 6 } 2217 snaLuActSessBindFailTrap NOTIFICATION-TYPE 2218 OBJECTS { snaLuActSessLocalApplName, 2219 snaLuActSessParLuName, 2220 snaLuActSessOperState, 2221 snaLuHistSessSenseData } 2222 STATUS current 2223 DESCRIPTION 2224 "This trap indicates the failure of a BIND. The value of 2225 snaLuActSessLocalApplName indicates the local application name. 2226 The value of snaLuActSessParLuName indicates the partner name. 2227 The value of snaLuActSessOperState indicates the current state 2228 after change. The value of snaLuHistSessSenseData indicates 2229 the failure reason. 2231 The Agent should not generate more than 1 trap of this type per 2232 minute to minimize the level of management traffic on the 2233 network." 2235 ::= { snaLuTraps 1 } 2237 -- ******************************************************************** 2238 -- snaMgtTools group 2239 -- 2240 -- Currently this group contains only one table. 2242 -- ******************************************************************** 2244 -- ******************************************************************** 2245 -- The following table contains Response Time Monitoring (RTM) 2246 -- configuration information and statistics for LU Type 2s. 2247 -- RTM supports the capability to measure and report end-user 2248 -- response times for dependent LUs. When the RTM state of an LU 2249 -- is 'on', response times for each LU transaction are monitored. 2250 -- A set of ranges is defined (e.g., Range 1 includes the number of 2251 -- transactions with response times less than 1 second) using the 2252 -- "boundary" definitions (e.g., boundary #2 is defined as 3 seconds). 2253 -- A set of counters (one per range) identifies 2254 -- the number of transactions within each response-time range. 2255 -- ******************************************************************** 2257 snaLuRtmTable OBJECT-TYPE 2258 SYNTAX SEQUENCE OF SnaLuRtmEntry 2259 MAX-ACCESS not-accessible 2260 STATUS current 2261 DESCRIPTION 2262 "This table contains Response Time Monitoring (RTM) information 2263 relating to an LU (Type 2). Each entry corresponds to an LU 2 2264 entry in snaLuAdminTable." 2266 ::= { snaMgtTools 1 } 2268 snaLuRtmEntry OBJECT-TYPE 2269 SYNTAX SnaLuRtmEntry 2270 MAX-ACCESS not-accessible 2271 STATUS current 2272 DESCRIPTION 2273 "Contains RTM information for an LU (Type 2). Each entry is 2274 created by the Agent." 2276 INDEX { snaLuRtmPuName, 2277 snaLuRtmLuName } 2279 ::= { snaLuRtmTable 1 } 2281 SnaLuRtmEntry ::= SEQUENCE { 2282 snaLuRtmPuName DisplayString, 2283 snaLuRtmLuName DisplayString, 2284 snaLuRtmCorrelator OCTET STRING, 2285 snaLuRtmState INTEGER, 2286 snaLuRtmStateTime DateAndTime, 2287 snaLuRtmDef INTEGER, 2288 snaLuRtmBoundary1 Integer32, 2289 snaLuRtmBoundary2 Integer32, 2290 snaLuRtmBoundary3 Integer32, 2291 snaLuRtmBoundary4 Integer32, 2292 snaLuRtmCounter1 Counter32, 2293 snaLuRtmCounter2 Counter32, 2294 snaLuRtmCounter3 Counter32, 2295 snaLuRtmCounter4 Counter32, 2296 snaLuRtmOverflows Counter32, 2297 snaLuRtmTotalTime Integer32, 2298 snaLuRtmLastRspTime Integer32 2299 } 2301 snaLuRtmPuName OBJECT-TYPE 2302 SYNTAX DisplayString (SIZE(1..17)) 2303 MAX-ACCESS not-accessible 2304 STATUS current 2305 DESCRIPTION 2306 "The locally defined name of the type 2.0 node with which this 2307 LU is associated. 2309 If this object has the same value as snaPu20Name, then the two 2310 entries being indexed apply to the same PU." 2312 ::= { snaLuRtmEntry 1 } 2314 snaLuRtmLuName OBJECT-TYPE 2315 SYNTAX DisplayString 2316 MAX-ACCESS not-accessible 2317 STATUS current 2318 DESCRIPTION 2319 "The name of the LU to which the RTM data applies. 2321 If this object has the same value as snaLuAdminLuName, then the 2322 two entries being indexed apply to the same LU." 2324 ::= { snaLuRtmEntry 2 } 2326 snaLuRtmCorrelator OBJECT-TYPE 2327 SYNTAX OCTET STRING (SIZE (2)) 2328 MAX-ACCESS read-only 2329 STATUS current 2330 DESCRIPTION 2331 "A value that uniquely identifies an LU-LU session. By 2332 examining this value, a Management Station can determine 2333 whether RTM that it retrieves is for the same session as 2334 data that it had retrieved previously. 2336 This object corresponds to bytes 7-8 of the X'91' RTM MS 2337 subvector." 2339 ::= { snaLuRtmEntry 3 } 2341 snaLuRtmState OBJECT-TYPE 2342 SYNTAX INTEGER { 2343 off(1), 2344 on(2) 2345 } 2346 MAX-ACCESS read-only 2347 STATUS current 2348 DESCRIPTION 2349 "The value indicates the current RTM state of an LU. 2351 This object corresponds to bytes 5-6, bit 0 of the X'91' 2352 RTM MS subvector." 2354 ::= { snaLuRtmEntry 4 } 2356 snaLuRtmStateTime OBJECT-TYPE 2357 SYNTAX DateAndTime 2358 MAX-ACCESS read-only 2359 STATUS current 2360 DESCRIPTION 2361 "The time when the RTM state for this LU last changed." 2363 ::= { snaLuRtmEntry 5 } 2365 snaLuRtmDef OBJECT-TYPE 2366 SYNTAX INTEGER { 2367 firstChar(1), 2368 kb(2), 2369 cdeb(3) 2370 } 2371 MAX-ACCESS read-only 2372 STATUS current 2373 DESCRIPTION 2374 "The value indicates the mode of measurement for this RTM 2375 request. The values have following meaning: 2377 firstChar(1) - measured from the Attention or Action key 2378 depression to the arrival back at the LU of 2379 the first character that can alter the 2380 presentation space 2381 kb(2) - measured from the Attention or Action key 2382 depression until the LU is ready to accept 2383 input from the end user 2384 cdeb(3) - measured from the Attention or Action key 2385 depression to the receipt and processing 2386 back at the LU of Change Direction (CD) or 2387 End Bracket (EB) 2389 This object corresponds to byte 2 of the X'93' RTM MS 2390 subvector." 2392 ::= { snaLuRtmEntry 6 } 2394 snaLuRtmBoundary1 OBJECT-TYPE 2395 SYNTAX Integer32 2396 UNITS "tenths of a second" 2397 MAX-ACCESS read-only 2398 STATUS current 2399 DESCRIPTION 2400 "This object contains the value of the first boundary in units 2401 of 1/10th of a second. 2403 This object corresponds to bytes 9-10 of the X'93' RTM MS 2404 subvector." 2406 ::= { snaLuRtmEntry 7 } 2408 snaLuRtmBoundary2 OBJECT-TYPE 2409 SYNTAX Integer32 2410 UNITS "tenths of a second" 2411 MAX-ACCESS read-only 2412 STATUS current 2413 DESCRIPTION 2414 "This object contains the value of the second boundary in units 2415 of 1/10th of a second. 2417 This object corresponds to bytes 11-12 of the X'93' RTM MS 2418 subvector." 2420 ::= { snaLuRtmEntry 8 } 2422 snaLuRtmBoundary3 OBJECT-TYPE 2423 SYNTAX Integer32 2424 UNITS "tenths of a second" 2425 MAX-ACCESS read-only 2426 STATUS current 2427 DESCRIPTION 2428 "This object contains the value of the third boundary in units 2429 of 1/10th of a second. 2431 This object corresponds to bytes 13-14 of the X'93' RTM MS 2432 subvector." 2434 ::= { snaLuRtmEntry 9 } 2436 snaLuRtmBoundary4 OBJECT-TYPE 2437 SYNTAX Integer32 2438 UNITS "tenths of a second" 2439 MAX-ACCESS read-only 2440 STATUS current 2441 DESCRIPTION 2442 "This object contains the value of the fourth boundary in units 2443 of 1/10th of a second. 2445 This object corresponds to bytes 15-16 of the X'93' RTM MS 2446 subvector." 2448 ::= { snaLuRtmEntry 10 } 2450 snaLuRtmCounter1 OBJECT-TYPE 2451 SYNTAX Counter32 2452 MAX-ACCESS read-only 2453 STATUS current 2454 DESCRIPTION 2455 "Number of exchanges in the range (0, boundary1). 2457 This object corresponds to bytes p+1 - p+2 of the X'93' RTM MS 2458 subvector." 2460 ::= { snaLuRtmEntry 11 } 2462 snaLuRtmCounter2 OBJECT-TYPE 2463 SYNTAX Counter32 2464 MAX-ACCESS read-only 2465 STATUS current 2466 DESCRIPTION 2467 "Number of exchanges in the range (boundary1 + 1, boundary2). 2469 This object corresponds to bytes p+3 - p+4 of the X'93' RTM MS 2470 subvector." 2472 ::= { snaLuRtmEntry 12 } 2474 snaLuRtmCounter3 OBJECT-TYPE 2475 SYNTAX Counter32 2476 MAX-ACCESS read-only 2477 STATUS current 2478 DESCRIPTION 2479 "Number of exchanges in the range (boundary2 + 1, boundary3). 2481 This object corresponds to bytes p+5 - p+6 of the X'93' RTM MS 2482 subvector." 2484 ::= { snaLuRtmEntry 13 } 2486 snaLuRtmCounter4 OBJECT-TYPE 2487 SYNTAX Counter32 2488 MAX-ACCESS read-only 2489 STATUS current 2490 DESCRIPTION 2491 "Number of exchanges in the range (boundary3 + 1, boundary4). 2493 This object corresponds to bytes p+7 - p+8 of the X'93' RTM MS 2494 subvector." 2496 ::= { snaLuRtmEntry 14 } 2498 snaLuRtmOverflows OBJECT-TYPE 2499 SYNTAX Counter32 2500 MAX-ACCESS read-only 2501 STATUS current 2502 DESCRIPTION 2503 "The number of exchange durations greater than the maximum 2504 boundary specified. 2506 This object corresponds to bytes q+1 - q+2 of the X'93' RTM MS 2507 subvector." 2509 ::= { snaLuRtmEntry 15 } 2511 snaLuRtmTotalTime OBJECT-TYPE 2512 SYNTAX Integer32 2513 UNITS "tenths of a second" 2514 MAX-ACCESS read-only 2515 STATUS current 2516 DESCRIPTION 2517 "The total of all individual times for all exchanges measured 2518 and reported by this table row, including overflows, in units 2519 of 1/10 of a second. 2521 This object corresponds to bytes q+3 - q+6 of the X'93' RTM MS 2522 subvector." 2524 ::= { snaLuRtmEntry 16 } 2526 snaLuRtmLastRspTime OBJECT-TYPE 2527 SYNTAX Integer32 2528 UNITS "tenths of a second" 2529 MAX-ACCESS read-only 2530 STATUS current 2531 DESCRIPTION 2532 "This value indicates the response time for the last 2533 transaction in units of 1/10th of a second." 2535 ::= { snaLuRtmEntry 17 } 2537 -- ******************************************************************** 2538 -- Conformance information 2539 -- ******************************************************************** 2541 snanauConformance OBJECT IDENTIFIER ::= { snanauMIB 2 } 2543 snanauCompliances OBJECT IDENTIFIER ::= {snanauConformance 1 } 2544 snanauGroups OBJECT IDENTIFIER ::= {snanauConformance 2 } 2546 -- Compliance statements 2547 snanauCompliance MODULE-COMPLIANCE 2548 STATUS current 2549 DESCRIPTION 2550 "The compliance statement for the SNMPv2 entities which 2551 implement the SNANAU MIB." MODULE -- this module 2553 -- Unconditionally mandatory groups 2554 MANDATORY-GROUPS { snaNodeGroup, 2555 snaLuGroup, 2556 snaSessionGroup } 2558 -- Conditionally mandatory groups 2559 GROUP snaPu20Group 2560 DESCRIPTION 2561 "The snaPu20Group is mandatory only for those 2562 entities which implement PU type 2.0" 2564 GROUP snaMgtToolsRtmGroup 2565 DESCRIPTION 2566 "The snaMgtToolsGroup is mandatory only for those 2567 entities which implement LU type 2 and RTM." 2569 OBJECT snaNodeAdminState 2570 MIN-ACCESS read-only 2571 DESCRIPTION 2572 "An Agent is not required to support node 2573 deactivation via this object." 2575 ::= { snanauCompliances 1 } 2577 -- Units of conformance 2579 snaNodeGroup OBJECT-GROUP 2580 OBJECTS { snaNodeAdminState, 2581 snaNodeOperState, 2582 snaNodeSscpSuppliedName, 2583 snaNodeType, 2584 snaNodeXidFormat, 2585 snaNodeId, 2586 snaNodeEnablingMethod, 2587 snaNodeLuTermDefault, 2588 snaNodeMaxLu, 2589 snaNodeStopMethod, 2590 snaNodeStartTime, 2591 snaNodeLastStateChange, 2592 snaNodeActFailureReason, 2593 snaNodeTableLastChange, 2594 snaNodeLinkAdminSpecific, 2595 snaNodeLinkAdminMaxPiu, 2596 snaNodeLinkAdminTableLastChg, 2597 snaNodeLinkOperSpecific, 2598 snaNodeLinkOperMaxPiu, 2599 snaNodeLinkOperTableLastChg } 2600 STATUS current 2601 DESCRIPTION 2602 "A collection of objects providing the instrumentation for SNA 2603 nodes." 2605 ::= { snanauGroups 1 } 2607 snaLuGroup OBJECT-GROUP 2608 OBJECTS { snaLuAdminUserLuName, 2609 snaLuAdminType, 2610 snaLuAdminLocalAddress, 2611 snaLuAdminDisplayModel, 2612 snaLuAdminTerm, 2613 snaLuOperUserLuName, 2614 snaLuOperSscpSuppliedName, 2615 snaLuOperType, 2616 snaLuOperLocalAddress, 2617 snaLuOperDisplayModel, 2618 snaLuOperTerm, 2619 snaLuOperState } 2620 STATUS current 2621 DESCRIPTION 2622 "A collection of objects providing the instrumentation for 2623 dependent SNA LUs." 2625 ::= { snanauGroups 2 } 2627 snaSessionGroup OBJECT-GROUP 2628 OBJECTS { snaLuActSessOperState, 2629 snaLuActSessParLuIndex, 2630 snaLuActSessLocalApplName, 2631 snaLuActSessParLuName, 2632 snaLuActSessMaxSndRuSize, 2633 snaLuActSessMaxRcvRuSize, 2634 snaLuActSessSndPacingSize, 2635 snaLuActSessRcvPacingSize, 2636 snaLuActSessUpTime, 2637 snaLuActSessLinkIndex, 2638 snaLuHistSessNodeName, 2639 snaLuHistSessLocLuName, 2640 snaLuHistSessParLuName, 2641 snaLuHistSessTime, 2642 snaLuHistSessSenseData, 2643 snaLuHistSessTerminationRu, 2644 snaLuHistSessUnbindType, 2645 snaLuSessCntrlOperStat, 2646 snaLuSessCntrlAdminStat, 2647 snaLuSessStatsSentFmdBytes, 2648 snaLuSessStatsSentNonFmdBytes, 2649 snaLuSessStatsRcvdFmdBytes, 2650 snaLuSessStatsRcvdNonFmdBytes, 2651 snaLuSessStatsSentFmdRus, 2652 snaLuSessStatsSentNonFmdRus, 2653 snaLuSessStatsRcvdFmdRus, 2654 snaLuSessStatsRcvdNonFmdRus, 2655 snaLuSessStatsSentNegRsps, 2656 snaLuSessStatsRcvdNegRsps } 2657 STATUS current 2658 DESCRIPTION 2659 "A collection of objects providing the instrumentation for SNA 2660 sessions involving dependent LUs." 2662 ::= { snanauGroups 3 } 2664 snaPu20Group OBJECT-GROUP 2665 OBJECTS { snaPu20SentBytes, 2666 snaPu20ReceivedBytes, 2667 snaPu20SentPius, 2668 snaPu20ReceivedPius, 2669 snaPu20SentNegRsps, 2670 snaPu20ReceivedNegRsps, 2671 snaPu20ActLus, 2672 snaPu20InActLus, 2673 snaPu20BindLus, 2674 snaPu20HostSscpId, 2675 snaPu20HostDescription, 2676 snaPu20SscpName, 2677 snaPu20PuName } 2678 STATUS current 2679 DESCRIPTION 2680 "A collection of objects providing the instrumentation for type 2681 2.0 nodes." 2683 ::= { snanauGroups 4 } 2685 snaMgtToolsRtmGroup OBJECT-GROUP 2686 OBJECTS { snaLuRtmCorrelator, 2687 snaLuRtmState, 2688 snaLuRtmStateTime, 2689 snaLuRtmDef, 2690 snaLuRtmBoundary1, 2691 snaLuRtmBoundary2, 2692 snaLuRtmBoundary3, 2693 snaLuRtmBoundary4, 2694 snaLuRtmCounter1, 2695 snaLuRtmCounter2, 2696 snaLuRtmCounter3, 2697 snaLuRtmCounter4, 2698 snaLuRtmOverflows, 2699 snaLuRtmTotalTime, 2700 snaLuRtmLastRspTime } 2702 STATUS current 2703 DESCRIPTION 2704 "A collection of objects providing the instrumentation of RTM 2705 for SNA LU 2.0." 2707 ::= { snanauGroups 5 } 2709 -- end of conformance statement 2711 END 2712 6. Acknowledgments 2714 This MIB module is the product of the SNA NAU MIB Working Group. 2716 7. References 2718 [1] IBM, Systems Network Architecture Technical Overview, GC30-3073-3, 2719 March, 1991. 2721 [2] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. 2722 Waldbusser, "Structure of Management Information for version 2 of 2723 the Simple Network Management Protocol (SNMPv2)", RFC 1902, January 2724 1996. 2726 [3] McCloghrie, K., and M. Rose, Editors, "Management Information Base 2727 for Network Management of TCP/IP-based internets: MIB-II", STD 17, 2728 RFC 1213, March 1991. 2730 [4] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network 2731 Management Protocol", RFC 1157, May 1990. 2733 [5] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. 2734 Waldbusser, "Protocol Operations for version 2 of the Simple 2735 Network Management Protocol (SNMPv2)", RFC 1905, January 1996. 2737 8. Security Considerations 2739 Security issues are not discussed in this memo. 2741 9. Authors' Addresses 2743 Zbigniew Kielczewski 2744 Cisco Systems 2745 7025 Kit Creek Road 2746 P.O. Box 14987 2747 Research Triangle Park, NC 27709, USA 2749 Tel: 1 919 472 2326 2750 E-mail: zkielcze@cisco.com 2752 Kitty Shih 2753 Novell 2754 890 Ross Drive 2755 Sunnyvale, CA 94089 2757 Tel: 1 408 747 4305 2758 E-mail: kmshih@novell.com 2760 Bob Moore 2761 IBM Corporation 2762 800 Park Offices Drive 2763 CNMA/664 2764 P.O. Box 12195 2765 Research Triangle Park, NC 27709, USA 2767 Tel: 1 919 254 4436 2768 E-mail: remoore@ralvm6.vnet.ibm.com 2770 10. Table of Contents 2772 1. Status of this Memo .................................... 1 2773 2. Introduction ........................................... 2 2774 3. The SNMPv2 Network Management Framework ................ 2 2775 4. Overview ............................................... 2 2776 4.1 SNANAU MIB structure .................................. 3 2777 5. Definitions ............................................ 8 2778 6. Acknowledgments ........................................ 62 2779 7. References ............................................. 62 2780 8. Security Considerations ................................ 63 2781 9. Author's Addresses ...................................... 63