idnits 2.17.1 draft-ietf-snanau-appntrapmib-00.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 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. ** 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 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 10 instances of too long lines in the document, the longest one being 1 character in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (May 14, 1998) is 9478 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: '12' is defined on line 940, but no explicit reference was found in the text ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. '1') ** Obsolete normative reference: RFC 1902 (ref. '3') (Obsoleted by RFC 2578) ** Obsolete normative reference: RFC 1903 (ref. '4') (Obsoleted by RFC 2579) ** Obsolete normative reference: RFC 1904 (ref. '5') (Obsoleted by RFC 2580) ** Obsolete normative reference: RFC 1905 (ref. '6') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2271 (ref. '7') (Obsoleted by RFC 2571) ** Obsolete normative reference: RFC 2272 (ref. '8') (Obsoleted by RFC 2572) ** Obsolete normative reference: RFC 2273 (ref. '9') (Obsoleted by RFC 2573) ** Obsolete normative reference: RFC 2274 (ref. '10') (Obsoleted by RFC 2574) ** Obsolete normative reference: RFC 2275 (ref. '11') (Obsoleted by RFC 2575) ** Obsolete normative reference: RFC 2028 (ref. '12') (Obsoleted by RFC 9281) ** Obsolete normative reference: RFC 2155 (ref. '14') (Obsoleted by RFC 2455) Summary: 22 errors (**), 0 flaws (~~), 3 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Definitions of Managed Objects 3 for APPN TRAPS 5 May 14, 1998 7 Bob Clouston (editor) 8 Cisco Systems 9 clouston@cisco.com 11 Bob Moore (editor) 12 IBM Corporation 13 remoore@us.ibm.com 15 17 Status of this Memo 19 This document is an Internet Draft. Internet Drafts are working 20 documents of the Internet Engineering Task Force (IETF), its Areas, and 21 its Working Groups. Note that other groups may also distribute working 22 documents as Internet Drafts. 24 Internet Drafts are draft documents valid for a maximum of six months. 25 Internet Drafts may be updated, replaced, or obsoleted by other 26 documents at any time. It is not appropriate to use Internet Drafts as 27 reference material or to cite them other than as a "working draft" or 28 "work in progress." 30 Please check the I-D abstract listing contained in each Internet Draft 31 directory to learn the current status of this or any Internet Draft. 32 Distribution of this document is unlimited. 34 Copyright Notice 36 Copyright (C) The Internet Society (1998). All Rights Reserved. 38 Abstract 40 This memo defines a portion of the Management Information Base (MIB) for 41 use with network management protocols in the Internet community. In 42 particular, it defines objects for receiving notifications from network 43 devices with APPN (Advanced Peer-to-Peer Network) and DLUR (Dependent LU 44 Requester) capabilities. This memo identifies notifications for the 45 APPN and DLUR architecture. 47 This memo does not specify a standard for the Internet community. 49 1. Introduction 51 This document is a product of the SNA NAU Services MIB Working Group. 52 It defines a MIB module for notifications for devices with Advanced 53 Peer-to-Peer Networking (APPN) and Dependent LU Requester (DLUR) 54 capabilities. 56 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 57 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 58 document are to be interpreted as described in RFC 2119 [13]. 60 2. The SNMP Network Management Framework 62 The SNMP Network Management Framework presently consists of six major 63 components. They are: 65 o the overall architecture, described in RFC 2271 [7]. 67 o the SMI, described in RFC 1902 [3], - the mechanisms used for 68 describing and naming objects for the purpose of management. 70 o the MIB-II, STD 17, RFC 1213 [2], - the core set of managed objects 71 for the Internet suite of protocols. 73 o the protocol, RFC 1157 [1] and/or RFC 1905 [6] and/or RFC 2272 [8] 74 -- the protocol for accessing managed information. 76 o the user-based security model defined in RFC 2274 [10]. 78 o the view-based access control model defined in RFC 2275 [11]. 80 Textual conventions are defined in RFC 1903 [4], and conformance 81 statements are defined in RFC 1904 [5]. Common applications are defined 82 in RFC 2273 [9]. 84 The Framework permits new objects to be defined for the purpose of 85 experimentation and evaluation. 87 This memo specifies a MIB module that is compliant to the SMIv2. A MIB 88 conforming to the SMIv1 can be produced through the appropriate 89 translation. 91 3. Overview 93 This document identifies the set of objects for reporting the status of 94 devices with APPN and DLUR capabilities via notifications. See the 95 SNANAU APPN MIB [14] and SNANAU DLUR MIB [15] for the objects for 96 monitoring the configuration and active characteristics of the devices 97 with APPN and DLUR capabilities. 99 The SNANAU APPN MIB allows a management station to collect the network 100 topology of an APPN network (the network nodes (NNs) in the network and 101 all of transmission groups (TGs) between the network nodes) from an APPN 102 device. It also allows the management station to collect the local 103 topology (TGs to end stations, and locally defined ports and link 104 stations) from an APPN device. While the SNANAU APPN MIB has an 105 efficient way to poll the APPN device for updates to the network 106 topology, using flow reduction sequence numbers (FRSNs) as a table 107 index; it does not have a mechanism to poll the local topology tables 108 (appnLocalTgTable, appnPortTable, and appnLsTable) for updates. To 109 learn about updates, deletions, and additions to the local topology, the 110 management station must retrieve the complete tables and examine them. 112 This MIB provides a mechanism for an APPN device to send notifications 113 to inform the management station of updates, deletions, and additions to 114 these tables. A notification is defined for each of these tables. 116 Each notification always contains an object which is a count of the 117 number of times this table has changed since the APPN node was last 118 reinitialized. This enables a management station to detect that it has 119 missed a notification, if it does not get the notifications in numerical 120 sequence. If the notifications are not in sequence, the management 121 station should retrieve the entire table to get the correct status for 122 all rows. 124 Each notification also contains an object indicating whether the 125 notification is reporting an addition, deletion, or modification of the 126 row. If the notification is an addition, all of the objects listed in 127 the notification. If it is a deletion, it only returns one of the 128 objects so that the management station can use the row index to 129 determine which row was deleted. If it is a modifcation, only those 130 objects in the row that were modified are included in the notification. 132 Similarly, the SNANAU DLUR MIB provides a mechanism for retrieving the 133 configuration and status of dependent LU server (DLUS) sessions on a 134 device with DLUR capabilities. This MIB defines a notification for the 135 addition, deletion, or modification of a row in the dlurDlusTable, in 136 the manner described above. 138 The SNANAU APPN MIB also provides a mechanism for a management station 139 to collect traffic statistics on intermediate sessions, primarily for 140 accounting purposes. However, when the session is terminated, all 141 statistics from the last poll until the session termination time are 142 lost, since the row for that session is deleted from the appnIsInTable. 143 This MIB defines a notification so that the session's final statistics 144 can be sent to a management station. 146 Highlights of the management functions supported by the APPN TRAP MIB 147 module include the following: 149 o A notification for the addition, deletion, or modification of an 150 APPN local TG. 152 o A notification for the addition, deletion, or modification of an 153 APPN port. 155 o A notification for the addition, deletion, or modification of an 156 APPN link station. 158 o A notification for the addition, deletion, or modification of a 159 DLUR-DLUS sesion. 161 o A notification for reporting final APPN intermediate session 162 statistics. 164 This MIB module does not support: 166 o Objects to query the configuration or status of APPN nodes on 167 demand. 169 3.1. APPN TRAP MIB Structure 171 The APPN TRAP MIB module contains a group of notifications, and a group 172 of supporting objects. 174 The group of notifications consists of the following notifications: 176 1) appnIsrAccountingDataTrap 178 This notification is generated by an APPN device when an intermediate 179 session is terminating, to report the final accounting statistics of the 180 session. 182 2) appnLocalTgTopoChangeTrap 184 This notification identifies an addition, deletion, or modification to a 185 row of the SNANAU APPN MIB appnLocalTgTable. 187 3) appnPortChangeTrap 189 This notification identifies an addition, deletion, or modification to a 190 row of the SNANAU APPN MIB appnPortTable. 192 4) appnLsChangeTrap 194 This notification identifies an addition, deletion, or modification to a 195 row of the SNANAU APPN MIB appnLsTable. 197 5) dlurDlusChangeTrap 199 This notification identifies an addition, deletion, or modification to a 200 row of the SNANAU DLUR MIB dlurDlusTable. 202 The group of supporting objects contains the appnTrapControl object, 203 which controls whether the APPN device generates each type of 204 notification. Note that generation of the appnIsrAccountingDataTrap is 205 not controlled by this object; instead it is controlled by the 206 appnIsInGlobalCtrAdminStatus object in the SNANAU APPN MIB. 208 Although APPN notification generation could be controlled solely by 209 entries in the snmpNotificationMIB, RFC 2273 [9], the appnTrapControl 210 object exists in this MIB so that implementations are not required to 211 implement SNMPv3 to control generation of APPN notifications. If 212 appnTrapControl enables APPN notifications, snmpNotificationMIB entries 213 could disable them. 215 Also contained in this group are objects for the TG, port, link, and 216 DLUR-DLUS session notifications to indicate the number of times each of 217 the tables has changed since the APPN node was last reinitialized, and 218 to indicate whether a particular notification is reporting an addition, 219 deletion, or modification of a row in the table. 221 4. Definitions 223 APPN-TRAP-MIB DEFINITIONS ::= BEGIN 225 IMPORTS 227 Counter32, OBJECT-TYPE, MODULE-IDENTITY, 228 NOTIFICATION-TYPE 229 FROM SNMPv2-SMI 231 TEXTUAL-CONVENTION 232 FROM SNMPv2-TC 234 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 235 FROM SNMPv2-CONF 237 appnMIB, appnIsInP2SFmdPius, appnIsInS2PFmdPius, 238 appnIsInP2SNonFmdPius, appnIsInS2PNonFmdPius, 239 appnIsInP2SFmdBytes, appnIsInS2PFmdBytes, 240 appnIsInP2SNonFmdBytes, appnIsInS2PNonFmdBytes, 241 appnIsInSessUpTime, appnObjects, 242 appnLocalTgDestVirtual, appnLocalTgDlcData, 243 appnLocalTgPortName, appnLocalTgQuiescing, 244 appnLocalTgOperational, appnLocalTgCpCpSession, 245 appnLocalTgEffCap, appnLocalTgConnCost, 246 appnLocalTgByteCost, appnLocalTgSecurity, 247 appnLocalTgDelay, appnLocalTgUsr1, 248 appnLocalTgUsr2, appnLocalTgUsr3, 249 appnLocalTgHprSup, appnLocalTgIntersubnet, 250 appnLocalTgMltgLinkType, appnLocalTgBranchLinkType, 251 appnPortOperState, appnPortDlcType, 252 appnPortPortType, appnPortSIMRIM, 253 appnPortLsRole, appnPortNegotLs, 254 appnPortDynamicLinkSupport, appnPortMaxRcvBtuSize, 255 appnPortMaxIframeWindow, appnPortSpecific, 256 appnPortDlcLocalAddr, appnPortCounterDisconTime, 257 appnLsOperState, appnLsPortName, 258 appnLsDlcType, appnLsDynamic, 259 appnLsAdjCpName, appnLsAdjNodeType, 260 appnLsTgNum, appnLsLimResource, 261 appnLsActOnDemand, appnLsMigration, 262 appnLsPartnerNodeId, appnLsCpCpSessionSupport, 263 appnLsMaxSendBtuSize, appnLsSpecific, 264 appnLsHprSup, appnLsErrRecoSup, 265 appnLsForAnrLabel, appnLsRevAnrLabel, 266 appnLsCpCpNceId, appnLsRouteNceId, 267 appnLsBfNceId, appnLsLocalAddr, 269 appnLsRemoteAddr, appnLsRemoteLsName, 270 appnLsCounterDisconTime, appnCompliances, appnGroups 271 FROM APPN-MIB 273 dlurDlusSessnStatus 274 FROM APPN-DLUR-MIB; 276 appnTrapMIB MODULE-IDENTITY 277 LAST-UPDATED "9805130000Z" -- May 13, 1998 278 ORGANIZATION "IETF SNA NAU MIB WG / AIW APPN MIBs SIG" 279 CONTACT-INFO 281 " 282 Bob Clouston 283 Cisco Systems 284 7025 Kit Creek Road 285 P.O. Box 14987 286 Research Triangle Park, NC 27709, USA 287 Tel: 1 919 472 2333 288 E-mail: clouston@cisco.com 290 Bob Moore 291 IBM Corporation 292 4205 S. Miami Boulevard 293 BRQA/501 294 P.O. Box 12195 295 Research Triangle Park, NC 27709, USA 296 Tel: 1 919 254 4436 297 E-mail: remoore@us.ibm.com 298 " 299 DESCRIPTION 300 "This MIB module defines notifications to be generated by 301 network devices with APPN capabilities. It presupposes 302 support for the APPN MIB (RFC 2155). It also presupposes 303 support for the DLUR MIB (RFC 2232) for implementations 304 that support the DLUR-related groups." 306 ::= { appnMIB 0 } 308 -- ********************************************************************* 309 -- Textual Conventions 310 -- ********************************************************************* 311 AppnLastChangeType ::= TEXTUAL-CONVENTION 312 STATUS current 313 DESCRIPTION 314 "A value reporting the type of the last change made to 315 a specified table. Defined values are: 317 addition(1) - a new row was added to the table 318 deletion(2) - an existing row was removed from 319 the table 320 modification(3) - the value of one or more objects 321 in an existing row of the table 322 changed. Changes to objects with 323 the syntax counter32 or counter64 324 are not considered modifications. 325 Changes to other objects may also 326 be excluded in the definition of 327 an object having this syntax." 329 SYNTAX INTEGER { addition(1), 330 deletion(2), 331 modification(3) 332 } 333 -- ********************************************************************* 334 -- Notifications 335 -- ********************************************************************* 337 appnIsrAccountingDataTrap NOTIFICATION-TYPE 338 OBJECTS { 339 appnIsInP2SFmdPius, 340 appnIsInS2PFmdPius, 341 appnIsInP2SNonFmdPius, 342 appnIsInS2PNonFmdPius, 343 appnIsInP2SFmdBytes, 344 appnIsInS2PFmdBytes, 345 appnIsInP2SNonFmdBytes, 346 appnIsInS2PNonFmdBytes, 347 appnIsInSessUpTime 348 } 349 STATUS current 350 DESCRIPTION 351 "When it has been enabled, this notification is generated by an 352 APPN node whenever an ISR session passing through the node is 353 taken down, regardless of whether the session went down 354 normally or abnormally. Its purpose is to allow a management 355 application (primarily an accounting application) that is 356 monitoring the ISR counts to receive the final values of these 357 counts, so that the application can properly account for the 358 amounts the counts were incremented since the last time the 359 application polled them. The appnIsInSessUpTime object 360 provides the total amount of time that the session was active. 362 This notification is not a substitute for polling the ISR 363 counts. In particular, the count values reported in this 364 notification cannot be assumed to be the complete totals for 365 the life of the session, since they may have wrapped while the 366 session was up. 368 The session to which the objects in this notification apply is 369 identified by the fully qualified CP name and PCID that make up 370 the table index. An instance of this notification will contain 371 exactly one instance of each of its objects, and these objects 372 will all belong to the same conceptual row of the 373 appnIsInTable. 375 Generation of this notification is controlled by the same 376 object in the APPN MIB, appnIsInGlobeCtrAdminStatus, that 377 controls whether the count objects themselves are being 378 incremented." 380 ::= { appnTrapMIB 1 } 382 appnLocalTgTopoChangeTrap NOTIFICATION-TYPE 383 OBJECTS { 384 appnLocalTgTableChanges, 385 appnLocalTgTableLastChangeType, 386 appnLocalTgDestVirtual, 387 appnLocalTgDlcData, 388 appnLocalTgPortName, 389 appnLocalTgQuiescing, 390 appnLocalTgOperational, 391 appnLocalTgCpCpSession, 392 appnLocalTgEffCap, 393 appnLocalTgConnCost, 394 appnLocalTgByteCost, 395 appnLocalTgSecurity, 396 appnLocalTgDelay, 397 appnLocalTgUsr1, 398 appnLocalTgUsr2, 399 appnLocalTgUsr3, 400 appnLocalTgHprSup, 401 appnLocalTgIntersubnet, 402 appnLocalTgMltgLinkType, 403 appnLocalTgBranchLinkType 404 } 405 STATUS current 406 DESCRIPTION 407 "When it has been enabled, this notification makes it possible 408 for an APPN topology application to get asynchronous 409 notifications of local topology changes, and thus to reduce the 410 frequency with which it polls for these changes. The 411 notification is more than a simple 'poll me now' indication. 412 It carries both a count of local TG topology changes, and the 413 updated objects themselves. The count of changes allows an 414 application to detect lost notifications, either when polling 415 or upon receiving a subsequent notification, at which point it 416 knows it must retrieve the entire appnLocalTgTable again. 418 An instance of this notification reports a change (addition, 419 deletion, or modification) to a single row in the 420 appnLocalTgTable. It contains the two global objects 421 appnLocalTgTableChanges and appnLocalTgTableLastChangeType, 422 plus one or more objects from the affected row, as follows: 424 - For an addition to the table, all the objects in the 425 new row; 426 - For a deletion, the appnLocalTgDestVirtual object; 427 - For a modification, all the objects whose values 428 changed. 430 The choice of appnLocalTgDestVirtual as the object to include 431 in the deletion case was totally arbitrary. All the receiving 432 application needs is some object from the deleted row, so it 433 can determine the index of the row. 435 Generation of this notification is controlled by the 436 appnTrapControl object." 438 ::= { appnTrapMIB 2 } 440 appnPortChangeTrap NOTIFICATION-TYPE 441 OBJECTS { 442 appnPortTableChanges, 443 appnPortTableLastChangeType, 444 appnPortOperState, 445 appnPortDlcType, 446 appnPortPortType, 447 appnPortSIMRIM, 448 appnPortLsRole, 449 appnPortNegotLs, 450 appnPortDynamicLinkSupport, 451 appnPortMaxRcvBtuSize, 452 appnPortMaxIframeWindow, 453 appnPortSpecific, 454 appnPortDlcLocalAddr, 455 appnPortCounterDisconTime 456 } 457 STATUS current 458 DESCRIPTION 459 "When it has been enabled, this notification makes it possible 460 for an APPN topology application to get asynchronous 461 notifications of port table changes, and thus to reduce the 462 frequency with which it polls for these changes. The 463 notification is more than a simple 'poll me now' indication. 464 It carries both a count of port table changes, and the updated 465 objects themselves. The count of changes allows an application 466 to detect lost notifications, either when polling or upon 467 receiving a subsequent notification, at which point it knows it 468 must retrieve the entire appnPortTable again. 470 An instance of this notification reports a change (addition, 471 deletion, or modification) to a single row in the 472 appnPortTable. It contains the two global objects 473 appnPortTableChanges and appnPortTableLastChangeType, plus one 474 or more objects from the affected row, as follows: 476 - For an addition to the table, all the objects listed 477 here in the new row; 478 - For a deletion, only the appnPortDlcType object; 479 - For a modification, all the objects listed here 480 whose values changed. 482 Note that the counter objects in the appnPortTable are not 483 included here, since notifications should not be issued as they 484 are incremented. 486 The choice of appnPortDlcType as the object to include in the 487 deletion case was totally arbitrary. All the receiving 488 application needs is some object from the deleted row, so it 489 can determine the index of the row. 491 Generation of this notification is controlled by the 492 appnTrapControl object." 494 ::= { appnTrapMIB 3 } 496 appnLsChangeTrap NOTIFICATION-TYPE 497 OBJECTS { 498 appnLsTableChanges, 499 appnLsTableLastChangeType, 500 appnLsOperState, 501 appnLsPortName, 502 appnLsDlcType, 503 appnLsDynamic, 504 appnLsAdjCpName, 505 appnLsAdjNodeType, 506 appnLsTgNum, 507 appnLsLimResource, 508 appnLsActOnDemand, 509 appnLsMigration, 510 appnLsPartnerNodeId, 511 appnLsCpCpSessionSupport, 512 appnLsMaxSendBtuSize, 513 appnLsSpecific, 514 appnLsHprSup, 515 appnLsErrRecoSup, 516 appnLsForAnrLabel, 517 appnLsRevAnrLabel, 518 appnLsCpCpNceId, 519 appnLsRouteNceId, 520 appnLsBfNceId, 521 appnLsLocalAddr, 522 appnLsRemoteAddr, 523 appnLsRemoteLsName, 524 appnLsCounterDisconTime 525 } 526 STATUS current 527 DESCRIPTION 528 "When it has been enabled, this notification makes it possible 529 for an APPN topology application to get asynchronous 530 notifications of link station table changes, and thus to reduce 531 the frequency with which it polls for these changes. The 532 notification is more than a simple 'poll me now' indication. 533 It carries both a count of link station table changes, and the 534 updated objects themselves. The count of changes allows an 535 application to detect lost notifications, either when polling 536 or upon receiving a subsequent notification, at which point it 537 knows it must retrieve the entire appnLsTable again. 539 An instance of this notification reports a change (addition, 540 deletion, or modification) to a single row in the appnLsTable. 541 It contains the two global objects appnLsTableChanges and 542 appnLsTableLastChangeType, plus one or more objects from the 543 affected row, as follows: 545 - For an addition to the table, all the objects 546 listed here in the new row; 547 - For a deletion, only the appnLsPortName object; 548 - For a modification, all the objects listed here 549 whose values changed. 551 Note that the counter and gauge objects in the appnLsTable are 552 not included here, since notifications should not be issued as 553 their values change. 555 The choice of appnLsPortName as the object to include in the 556 deletion case was totally arbitrary. All the receiving 557 application needs is some object from the deleted row, so it 558 can determine the index of the row. 560 Generation of this notification is controlled by the 561 appnTrapControl object." 563 ::= { appnTrapMIB 4 } 565 dlurDlusChangeTrap NOTIFICATION-TYPE 566 OBJECTS { 567 dlurDlusTableChanges, 568 dlurDlusTableLastChangeType, 569 dlurDlusSessnStatus 570 } 571 STATUS current 572 DESCRIPTION 573 "When it has been enabled, this notification makes it possible 574 for an APPN topology application to get asynchronous 575 notifications of DLUR-DLUS table changes, and thus to reduce 576 the frequency with which it polls for these changes. The 577 notification is more than a simple 'poll me now' indication. 578 It carries both a count of DLUR-DLUS table changes, and the 579 updated objects themselves. The count of changes allows an 580 application to detect lost notifications, either when polling 581 or upon receiving a subsequent notification, at which point it 582 knows it must retrieve the entire dlurDlusTable again. 584 An instance of this notification reports a change (addition, 585 deletion, or modification) to a single row in the 586 dlurDlusTable. It contains the two global objects 587 dlurDlusTableChanges and dlurDlusTableLastChangeType, plus 588 the table's one accessible object: dlurDlusSessnStatus. 590 Generation of this notification is controlled by the 591 appnTrapControl object." 593 ::= { appnTrapMIB 5 } 595 -- ********************************************************************* 596 -- Supporting Objects 597 -- ********************************************************************* 599 appnTrapObjects OBJECT IDENTIFIER ::= { appnObjects 7 } 601 appnTrapControl OBJECT-TYPE 603 SYNTAX BITS { 604 appnLocalTgTopoChangeTrap(0), 605 appnPortChangeTrap(1), 606 appnLsChangeTrap(2), 607 dlurDlusChangeTrap(3) 608 -- add other notification types here 609 } 610 MAX-ACCESS read-write 611 STATUS current 612 DESCRIPTION 613 "An object to turn APPN notification generation on and off. 614 Setting a notification type's bit to 1 enables generation of 615 notifications of that type, subject to further filtering 616 resulting from entries in the snmpNotificationMIB. Setting 617 this bit to 0 disables generation of notifications of that 618 type. 620 Note that generation of the appnIsrAccountingDataTrap is 621 controlled by the appnIsInGlobeCtrAdminStatus object in 622 the APPN MIB: if counts of intermediate session traffic 623 are being kept at all, then the notification is also enabled." 625 ::= { appnTrapObjects 1 } 627 appnLocalTgTableChanges OBJECT-TYPE 628 SYNTAX Counter32 629 MAX-ACCESS read-only 630 STATUS current 631 DESCRIPTION 632 "A count of the number of times the appnLocalTgTable has 633 changed since the APPN node was last reinitialized. 634 Addition, deletion, or modification of a row in the table 635 counts as a single change." 637 ::= { appnTrapObjects 2 } 639 appnLocalTgTableLastChangeType OBJECT-TYPE 640 SYNTAX AppnLastChangeType 641 MAX-ACCESS read-only 642 STATUS current 643 DESCRIPTION 644 "An object reporting the type of the last change made 645 to the appnLocalTgTable." 647 ::= { appnTrapObjects 3 } 649 appnPortTableChanges OBJECT-TYPE 650 SYNTAX Counter32 651 MAX-ACCESS read-only 652 STATUS current 653 DESCRIPTION 654 "A count of the number of times the appnPortTable has 655 changed since the APPN node was last reinitialized. 656 Addition, deletion, or modification of a row in the table 657 counts as a single change." 659 ::= { appnTrapObjects 4 } 661 appnPortTableLastChangeType OBJECT-TYPE 662 SYNTAX AppnLastChangeType 663 MAX-ACCESS read-only 664 STATUS current 665 DESCRIPTION 666 "An object reporting the type of the last change made 667 to the appnPortTable." 669 ::= { appnTrapObjects 5 } 671 appnLsTableChanges OBJECT-TYPE 672 SYNTAX Counter32 673 MAX-ACCESS read-only 674 STATUS current 675 DESCRIPTION 676 "A count of the number of times the appnLsTable has 677 changed since the APPN node was last reinitialized. 678 Addition, deletion, or modification of a row in the table 679 counts as a single change." 681 ::= { appnTrapObjects 6 } 683 appnLsTableLastChangeType OBJECT-TYPE 684 SYNTAX AppnLastChangeType 685 MAX-ACCESS read-only 686 STATUS current 687 DESCRIPTION 688 "An object reporting the type of the last change made 689 to the appnLsTable." 691 ::= { appnTrapObjects 7 } 693 dlurDlusTableChanges OBJECT-TYPE 694 SYNTAX Counter32 695 MAX-ACCESS read-only 696 STATUS current 697 DESCRIPTION 698 "A count of the number of times the dlurDlusTable has 699 changed since the APPN node was last reinitialized. 700 Addition, deletion, or modification of a row in the table 701 counts as a single change." 703 ::= { appnTrapObjects 8 } 705 dlurDlusTableLastChangeType OBJECT-TYPE 706 SYNTAX AppnLastChangeType 707 MAX-ACCESS read-only 708 STATUS current 709 DESCRIPTION 711 "An object reporting the type of the last change made 712 to the dlurDlusTable." 714 ::= { appnTrapObjects 9 } 716 -- ********************************************************************* 717 -- Conformance information 718 -- ********************************************************************* 720 -- Tie into the conformance structure in the APPN MIB: 721 -- appnConformance OBJECT IDENTIFIER ::= {appnMIB 3 } 722 -- 723 -- appnCompliances OBJECT IDENTIFIER ::= {appnConformance 1 } 724 -- appnGroups OBJECT IDENTIFIER ::= {appnConformance 2 } 726 -- Compliance statement 727 appnTrapMibCompliance MODULE-COMPLIANCE 728 STATUS current 729 DESCRIPTION 730 "The compliance statement for the SNMP entities that 731 implement the APPN-TRAP-MIB." 733 MODULE -- this module 735 -- Conditionally mandatory groups 736 GROUP appnTrapMibIsrNotifGroup 737 DESCRIPTION 738 "This group is mandatory for APPN nodes supporting 739 reporting of final ISR counter values via notifications." 741 GROUP appnTrapMibTopoConfGroup 742 DESCRIPTION 743 "This group is mandatory for APPN nodes supporting 744 polling reduction for local topology." 746 GROUP appnTrapMibTopoNotifGroup 747 DESCRIPTION 748 "This group is mandatory for APPN nodes supporting 749 polling reduction for local topology." 751 GROUP appnTrapMibDlurConfGroup 752 DESCRIPTION 753 "This group is mandatory for APPN nodes supporting 754 polling reduction for the dlurDlusTable." 756 GROUP appnTrapMibDlurNotifGroup 757 DESCRIPTION 758 "This group is mandatory for APPN nodes supporting 759 polling reduction for the dlurDlusTable." 761 OBJECT appnTrapControl 762 MIN-ACCESS read-only 763 DESCRIPTION 764 "An agent is not required to support a set to 765 this object." 767 ::= {appnCompliances 2 } 769 -- Units of conformance 770 appnTrapMibIsrNotifGroup NOTIFICATION-GROUP 771 NOTIFICATIONS { 772 appnIsrAccountingDataTrap 773 } 774 STATUS current 775 DESCRIPTION 776 "A notification for reporting the final values of the 777 APPN MIB's ISR counters." 779 ::= { appnGroups 21 } 781 appnTrapMibTopoConfGroup OBJECT-GROUP 782 OBJECTS { 783 appnTrapControl, 784 appnLocalTgTableChanges, 785 appnLocalTgTableLastChangeType, 786 appnPortTableChanges, 787 appnPortTableLastChangeType, 788 appnLsTableChanges, 789 appnLsTableLastChangeType 790 } 791 STATUS current 792 DESCRIPTION 793 "A collection of objects for reducing the polling 794 associated with the local topology tables in the 795 APPN MIB. Nodes that implement this group SHALL 796 also implement the appnTrapMibTopoNotifGroup." 798 ::= { appnGroups 22 } 800 appnTrapMibTopoNotifGroup NOTIFICATION-GROUP 801 NOTIFICATIONS { 802 appnLocalTgTopoChangeTrap, 803 appnPortChangeTrap, 804 appnLsChangeTrap 805 } 806 STATUS current 807 DESCRIPTION 808 "A collection of notifications for reducing the polling 809 associated with the local topology tables in the 810 APPN MIB. Nodes that implement this group SHALL 811 also implement the appnTrapMibTopoConfGroup." 813 ::= { appnGroups 23 } 815 appnTrapMibDlurConfGroup OBJECT-GROUP 816 OBJECTS { 817 appnTrapControl, 818 dlurDlusTableChanges, 819 dlurDlusTableLastChangeType 820 } 821 STATUS current 822 DESCRIPTION 823 "A collection of objects for reducing the polling 824 associated with the dlurDlusTable in the DLUR 825 MIB. Nodes that implement this group SHALL also 826 implement the appnTrapMibDlurNotifGroup." 828 ::= { appnGroups 24 } 830 appnTrapMibDlurNotifGroup NOTIFICATION-GROUP 831 NOTIFICATIONS { 832 dlurDlusChangeTrap 833 } 834 STATUS current 835 DESCRIPTION 836 "A notification for reducing the polling associated 837 with the dlurDlusTable in the DLUR MIB. Nodes that 838 implement this group SHALL also implement the 839 appnTrapMibDlurConfGroup." 841 ::= { appnGroups 25 } 843 END 844 5. Security Considerations 846 Certain management information defined in this MIB may be considered 847 sensitive in some network environments. Therefore, authentication of 848 received SNMP requests and controlled access to management information 849 SHOULD be employed in such environments. An authentication protocol is 850 defined in [10]. A protocol for access control is defined in [11]. 852 None of the read-only objects in the APPN TRAP MIB reports a password, 853 user data, or anything else that is particularly sensitive. Some 854 enterprises view their network configuration itself, as well as 855 information about network usage and performance, as corporate assets; 856 such enterprises may wish to restrict SNMP access to most of the objects 857 in the MIB. 859 There is one read-write object in the APPN TRAP MIB, appnTrapControl. 860 This object controls the generation of the notifications defined in the 861 APPN TRAP MIB. 863 6. Intellectual Property 865 The IETF takes no position regarding the validity or scope of any 866 intellectual property or other rights that might be claimed to pertain 867 to the implementation or use of the technology described in this 868 document or the extent to which any license under such rights might or 869 might not be available; neither does it represent that it has made any 870 effort to identify any such rights. Information on the IETF's 871 procedures with respect to rights in standards-track and standards- 872 related documentation can be found in BCP-11 [12]. Copies of claims of 873 rights made available for publication and any assurances of licenses to 874 be made available, or the result of an attempt made to obtain a general 875 license or permission for the use of such proprietary rights by 876 implementers or users of this specification can be obtained from the 877 IETF Secretariat. 879 The IETF invites any interested party to bring to its attention any 880 copyrights, patents or patent applications, or other proprietary rights 881 which may cover technology that may be required to practice this 882 standard. Please address the information to the IETF Executive 883 Director. 885 7. Acknowledgments 887 This MIB module is the product of the IETF SNA NAU MIB WG and the AIW 888 APPN/HPR MIBs SIG. 890 8. References 892 [1] Case, J., M. Fedor, M. Schoffstall, J. Davin, "Simple Network 893 Management Protocol", RFC 1157, SNMP Research, Performance Systems 894 International, MIT Laboratory for Computer Science, May 1990. 896 [2] McCloghrie, K., and M. Rose, Editors, "Management Information Base 897 for Network Management of TCP/IP-based internets: MIB-II", STD 17, 898 RFC 1213, Hughes LAN Systems, Performance Systems International, 899 March 1991. 901 [3] Case, J., McCloghrie, K., Rose, M., and Waldbusser S., "Structure 902 of Management Information for Version 2 of the Simple Network 903 Management Protocol (SNMPv2)", RFC 1902, January 1996. 905 [4] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Textual 906 Conventions for Version 2 of the Simple Network Management Protocol 907 (SNMPv2)", RFC 1903, January 1996. 909 [5] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., 910 "Conformance Statements for Version 2 of the Simple Network 911 Management Protocol (SNMPv2)", RFC 1904, January 1996. 913 [6] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Protocol 914 Operations for Version 2 of the Simple Network Management Protocol 915 (SNMPv2)", RFC 1905, January 1996. 917 [7] Harrington D., Presuhn, R., Wijnen, B., "An Architecture for 918 Describing SNMP Management Frameworks", RFC 2271, Cabletron 919 Systems, BMC Software, Inc., IBM T.J. Watson Research, January 920 1998. 922 [8] Harrington D., Presuhn, R., Wijnen, B., "Message Processing and 923 Dispatching for the Simple Network Management Protocol (SNMP)", RFC 924 2272, Cabletron Systems, BMC Software, Inc., IBM T.J. Watson 925 Research, January 1998. 927 [9] Levi D., Meyer P., Stewart, B., "SNMPv3 Applications", RFC 2273, 928 SNMP Research, Inc., Secure Computing Corporation, Cisco Systems, 929 January 1998. 931 [10] Blumenthal, U., Wijnen, B., "User-based Security Model (USM) for 932 version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 933 2274, IBM T. J. Watson Research, January 1998 935 [11] Wijnen, B., Presuhn, R., McCloghrie, K., "View-based Access Control 936 Model (VACM) for the Simple Network Management Protocol (SNMP)", 937 RFC 2275, IBM T.J. Watson Research, BMC Software, Inc., Cisco 938 Systems, Inc., January 1998. 940 [12] Hovey, R., and S. Bradner, "The Organizations Involved in the IETF 941 Standards Process", BCP 11, RFC 2028, October 1996. 943 [13] Bradner, S., "Key words for use in RFCs to Indicate Requirement 944 Levels", BCP 14, RFC 2119, March 1997. 946 [14] Clouston, B., and B. Moore, "Definition of Managed Objects for APPN 947 using SMIv2", RFC 2155, June 1997. 949 [15] Clouston, B., and B. Moore, "Definitions of Managed Objects for 950 DLUR", RFC 2232, November 1997. 952 9. Authors' Addresses 954 Bob Clouston 955 Cisco Systems 956 7025 Kit Creek Road 957 P.O. Box 14987 958 Research Triangle Park, NC 27709, USA 960 Tel: 1 919 472 2333 961 E-mail: clouston@cisco.com 963 Robert Moore 964 Dept. BRQA/Bldg. 501/G114 965 IBM Corporation 966 P.O.Box 12195 967 3039 Cornwallis 968 Research Triangle Park, NC 27709, USA 970 Phone: +1-919-254-4436 971 E-mail: remoore@us.ibm.com 973 10. Full Copyright Statement 975 Copyright (C) The Internet Society (1998). All Rights Reserved. 977 This document and translations of it may be copied and furnished to 978 others, and derivative works that comment on or otherwise explain it or 979 assist in its implementation may be prepared, copied, published and 980 distributed, in whole or in part, without restriction of any kind, 981 provided that the above copyright notice and this paragraph are included 982 on all such copies and derivative works. However, this document itself 983 may not be modified in any way, such as by removing the copyright notice 984 or references to the Internet Society or other Internet organizations, 985 except as needed for the purpose of developing Internet standards in 986 which case the procedures for copyrights defined in the Internet 987 Standards process must be followed, or as required to translate it into 988 languages other than English. 990 The limited permissions granted above are perpetual and will not be 991 revoked by the Internet Society or its successors or assigns. 993 This document and the information contained herein is provided on an "AS 994 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK 995 FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT 996 LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT 997 INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR 998 FITNESS FOR A PARTICULAR PURPOSE. 1000 Table of Contents 1002 1. Introduction ........................................... 2 1003 2. The SNMP Network Management Framework .................. 2 1004 3. Overview ............................................... 3 1005 3.1 APPN TRAP MIB structure .............................. 4 1006 4. Definitions ............................................ 6 1007 5. Security Considerations ................................ 20 1008 5. Intellectual Property .................................. 20 1009 7. Acknowledgments ........................................ 20 1010 8. References ............................................. 21 1011 9. Authors' Addresses ..................................... 22 1012 10. Full Copyright Statement ............................... 22