idnits 2.17.1 draft-ietf-snanau-appntrapmib-01.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 24 instances of too long lines in the document, the longest one being 5 characters 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 22, 1998) is 9464 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 841, 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 22, 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 status changes. 110 This MIB provides a mechanism for an APPN device to send notifications 111 to inform the management station of status changes to rows of these 112 tables. Status changes include operational state changes, and for TGs 113 also include control-point to control-point (CP-CP) session state 114 changes. A notification is defined for each type of status change for 115 each table. 117 The port and link operational state objects have intermediate states. 118 Notifications are only sent for transition to active or inactive state. 120 Notifications are only sent for row creation if the state is active or 121 operational. This is done to avoid sending a notification as the row is 122 created with an inactive initial state, followed by another notification 123 as the resource is activated. 125 Notifications are only sent for row deletion if the last state was 126 active or operational. In most cases, a resource must be deactivated 127 before it can be deleted, and the deactivation will cause a notification 128 to be sent. There is no need for a second notification to be sent for 129 the row deletion, except for the case where the deletion occurred 130 without deactivation. In this case, the state of the object in the 131 notification will indicate an inactve state, since a deleted resource 132 can no longer be active. 134 The purpose of the appnLocalTgCpCpStateChangeTrap notification is to 135 identify the loss or recovery of CP-CP sessions on a TG while the TG 136 remains operational. Thus this notification is only sent if there is a 137 change to an appnLocalTgCpCpSession object, but not a change to the 138 appnLocalTgOperational object. This notification is never sent for the 139 creation or deletion of a row in the appnLocalTgTable. 141 Each notification always contains an object which is a count of the 142 number of times the status of a row in table has changed since the APPN 143 node was last reinitialized. This enables a management station to 144 detect that it has missed a notification, if it does not get the 145 notifications in numerical sequence. If the notifications are not in 146 sequence, the management station should retrieve the entire table to get 147 the correct status for all rows. 149 Similarly, the SNANAU DLUR MIB provides a mechanism for retrieving the 150 configuration and status of dependent LU server (DLUS) sessions on a 151 device with DLUR capabilities. This MIB defines a notification for a 152 DLUR-DLUS session state change of a row in the dlurDlusTable, in the 153 manner described above. A notification is only sent for a session state 154 transition to active or inactive. As with the above notifications, it 155 is only sent on row creation if the initial state is active; and on row 156 deletion is the last state was active, in which case the notification 157 indicates that the state is now inactive. 159 The SNANAU APPN MIB also provides a mechanism for a management station 160 to collect traffic statistics on intermediate sessions, primarily for 161 accounting purposes. However, when the session is terminated, all 162 statistics from the last poll until the session termination time are 163 lost, since the row for that session is deleted from the appnIsInTable. 164 This MIB defines a notification so that the session's final statistics 165 can be sent to a management station. 167 Highlights of the management functions supported by the APPN TRAP MIB 168 module include the following: 170 o A notification for an APPN local TG operational state change. 172 o A notification for an APPN local TG CP-CP session state change. 174 o A notification for an APPN port operational state change. 176 o A notification for an APPN link station operational state change. 178 o A notification for a DLUR-DLUS session state change. 180 o A notification for reporting final APPN intermediate session 181 statistics. 183 This MIB module does not support: 185 o Objects to query the configuration or status of APPN nodes on 186 demand. 188 o Notifications for changes to local topology tables not related to 189 status. 191 3.1. APPN TRAP MIB Structure 193 The APPN TRAP MIB module contains a group of notifications, and a group 194 of supporting objects. 196 The group of notifications consists of the following notifications: 198 1) appnIsrAccountingDataTrap 200 This notification is generated by an APPN device when an intermediate 201 session is terminating, to report the final accounting statistics of the 202 session. 204 2) appnLocalTgOperStateChangeTrap 206 This notification identifies a change to the appnLocalTgOperational 207 object in a row of the SNANAU APPN MIB appnLocalTgTable. 209 3) appnLocalTgCpCpStateChangeTrap 211 This notification identifies a change to the appnLocalTgCpCpSession 212 object in a row of the SNANAU APPN MIB appnLocalTgTable. 214 4) appnPortOperStateChangeTrap 216 This notification identifies a change to the appnPortOperState object in 217 a row of the SNANAU APPN MIB appnPortTable. 219 5) appnLsOperStateChangeTrap 221 This notification identifies a change to the appnLsOperState object in a 222 row of the SNANAU APPN MIB appnLsTable. 224 6) dlurDlusStateChangeTrap 226 This notification identifies a change to the dlurDlusSessnStatus object 227 in a row of the SNANAU DLUR MIB dlurDlusTable. 229 The group of supporting objects contains the appnTrapControl object, 230 which controls whether the APPN device generates each type of 231 notification. Note that generation of the appnIsrAccountingDataTrap is 232 not controlled by this object; instead it is controlled by the 233 appnIsInGlobalCtrAdminStatus object in the SNANAU APPN MIB. 235 Although APPN notification generation could be controlled solely by 236 entries in the snmpNotificationMIB, RFC 2273 [9], the appnTrapControl 237 object exists in this MIB so that implementations are not required to 238 implement SNMPv3 to control generation of APPN notifications. If 239 appnTrapControl enables APPN notifications, snmpNotificationMIB entries 240 could disable them. 242 Also contained in this group are objects for the TG, port, link, and 243 DLUR-DLUS session notifications to indicate the number of times each of 244 the tables has had a status change of a row since the APPN node was last 245 reinitialized. 247 4. Definitions 249 APPN-TRAP-MIB DEFINITIONS ::= BEGIN 251 IMPORTS 253 Counter32, OBJECT-TYPE, MODULE-IDENTITY, 254 NOTIFICATION-TYPE 255 FROM SNMPv2-SMI 257 MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP 258 FROM SNMPv2-CONF 260 appnMIB, appnIsInP2SFmdPius, appnIsInS2PFmdPius, 261 appnIsInP2SNonFmdPius, appnIsInS2PNonFmdPius, 262 appnIsInP2SFmdBytes, appnIsInS2PFmdBytes, 263 appnIsInP2SNonFmdBytes, appnIsInS2PNonFmdBytes, 264 appnIsInSessUpTime, appnObjects, 265 appnLocalTgOperational, appnLocalTgCpCpSession, 266 appnPortOperState, appnLsOperState, 267 appnCompliances, appnGroups 268 FROM APPN-MIB 270 dlurDlusSessnStatus 271 FROM APPN-DLUR-MIB; 273 appnTrapMIB MODULE-IDENTITY 274 LAST-UPDATED "9805220000Z" -- May 22, 1998 275 ORGANIZATION "IETF SNA NAU MIB WG / AIW APPN MIBs SIG" 276 CONTACT-INFO 278 " 279 Bob Clouston 280 Cisco Systems 281 7025 Kit Creek Road 282 P.O. Box 14987 283 Research Triangle Park, NC 27709, USA 284 Tel: 1 919 472 2333 285 E-mail: clouston@cisco.com 287 Bob Moore 288 IBM Corporation 289 4205 S. Miami Boulevard 290 BRQA/501 291 P.O. Box 12195 292 Research Triangle Park, NC 27709, USA 293 Tel: 1 919 254 4436 294 E-mail: remoore@us.ibm.com 295 " 296 DESCRIPTION 297 "This MIB module defines notifications to be generated by 298 network devices with APPN capabilities. It presupposes 299 support for the APPN MIB (RFC 2155). It also presupposes 300 support for the DLUR MIB (RFC 2232) for implementations 301 that support the DLUR-related groups." 303 ::= { appnMIB 0 } 305 -- ********************************************************************* 306 -- Notifications 307 -- ********************************************************************* 309 appnIsrAccountingDataTrap NOTIFICATION-TYPE 310 OBJECTS { 311 appnIsInP2SFmdPius, 312 appnIsInS2PFmdPius, 313 appnIsInP2SNonFmdPius, 314 appnIsInS2PNonFmdPius, 315 appnIsInP2SFmdBytes, 316 appnIsInS2PFmdBytes, 317 appnIsInP2SNonFmdBytes, 318 appnIsInS2PNonFmdBytes, 319 appnIsInSessUpTime 320 } 321 STATUS current 322 DESCRIPTION 323 "When it has been enabled, this notification is generated by an 324 APPN node whenever an ISR session passing through the node is 325 taken down, regardless of whether the session went down 326 normally or abnormally. Its purpose is to allow a management 327 application (primarily an accounting application) that is 328 monitoring the ISR counts to receive the final values of these 329 counts, so that the application can properly account for the 330 amounts the counts were incremented since the last time the 331 application polled them. The appnIsInSessUpTime object 332 provides the total amount of time that the session was active. 334 This notification is not a substitute for polling the ISR 335 counts. In particular, the count values reported in this 336 notification cannot be assumed to be the complete totals for 337 the life of the session, since they may have wrapped while the 338 session was up. 340 The session to which the objects in this notification apply is 341 identified by the fully qualified CP name and PCID that make up 342 the table index. An instance of this notification will contain 343 exactly one instance of each of its objects, and these objects 344 will all belong to the same conceptual row of the 345 appnIsInTable. 347 Generation of this notification is controlled by the same 348 object in the APPN MIB, appnIsInGlobeCtrAdminStatus, that 349 controls whether the count objects themselves are being 350 incremented." 352 ::= { appnTrapMIB 1 } 354 appnLocalTgOperStateChangeTrap NOTIFICATION-TYPE 355 OBJECTS { 356 appnLocalTgTableChanges, 357 appnLocalTgOperational 358 } 359 STATUS current 360 DESCRIPTION 361 "When it has been enabled, this notification makes it possible 362 for an APPN topology application to get asynchronous 363 notifications of local TG operational state changes, 364 and thus to reduce the frequency with which it polls 365 for these changes. 367 This notification is sent whenever there is a change to 368 the appnLocalTgOperational object in a row of the 369 appnLocalTgTable. This notification is only sent for row 370 creation if the row is created with a value of 'true' for 371 appnLocalTgOperational. This notification is only sent for 372 row deletion if the last value of appnLocalTgOperational was 373 'true'. In this case, the value of appnLocalTgOperational 374 in the notification shall be 'false', since the deletion of 375 a row indicates that the TG is no longer operational. 377 The notification is more than a simple 'poll me now' indication. 378 It carries both a count of local TG topology changes, and the 379 current operational state itself. The count of changes allows an 380 application to detect lost notifications, either when polling 381 or upon receiving a subsequent notification, at which point it 382 knows it must retrieve the entire appnLocalTgTable again. 383 This is the same count as used in the appnLocalCpCpStateChangeTrap. 384 A lost notification could indicate a local TG CP-CP session state 385 change or an operational state change. 387 Generation of this notification is controlled by the 388 appnTrapControl object." 390 ::= { appnTrapMIB 2 } 392 appnLocalTgCpCpChangeTrap NOTIFICATION-TYPE 393 OBJECTS { 394 appnLocalTgTableChanges, 395 appnLocalTgCpCpSession 396 } 397 STATUS current 398 DESCRIPTION 399 "When it has been enabled, this notification makes it possible 400 for an APPN topology application to get asynchronous 401 notifications of local TG control-point to control-point (CP-CP) 402 session state changes, and thus to reduce the 403 frequency with which it polls for these changes. 405 This notification is sent whenever there is a change to 406 the appnLocalTgCpCpSession object but NOT the 407 appnLocalTgOperational object in a row of the appnLocalTgTable. 408 This notification is never sent for appnLocalTgTable row 409 creation or deletion. 411 The notification is more than a simple 'poll me now' indication. 412 It carries both a count of local TG topology changes, and the 413 current CP-CP session state itself. The count of changes allows 414 an 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. This 417 is the same count as used in the appnLocalTgOperStateChangeTrap. 418 A lost notification could indicate a local TG CP-CP session 419 state change or an operational state change. 421 Generation of this notification is controlled by the 422 appnTrapControl object." 424 ::= { appnTrapMIB 3 } 426 appnPortOperStateChangeTrap NOTIFICATION-TYPE 427 OBJECTS { 428 appnPortTableChanges, 429 appnPortOperState 430 } 432 STATUS current 433 DESCRIPTION 434 "When it has been enabled, this notification makes it possible 435 for an APPN topology application to get asynchronous 436 notifications of port operational state changes, and thus to 437 reduce the frequency with which it polls for these changes. 438 This notification is only sent when a appnPortOperState has 439 transitioned to a value of 'active' or 'inactive'. 441 This notification is sent whenever there is a appnPortOperState 442 object transition to 'inactive' or 'active' state in the 443 appnPortTable. This notification is only sent for row creation 444 if the row is created with a value of 'active' for 445 appnPortOperState. This notification is only sent for 446 row deletion if the last value of appnPortOperState was 447 'active'. In this case, the value of appnPortOperState 448 in the notification shall be 'inactive', since the deletion of 449 a row indicates that the port is no longer active. 451 The notification is more than a simple 'poll me now' indication. 452 It carries both a count of port table changes, and the 453 operational state itself. The count of changes allows an 454 application to detect lost notifications, either when polling 455 or upon receiving a subsequent notification, at which point 456 it knows it must retrieve the entire appnPortTable again. 458 Generation of this notification is controlled by the 459 appnTrapControl object." 461 ::= { appnTrapMIB 4 } 463 appnLsOperStateChangeTrap NOTIFICATION-TYPE 464 OBJECTS { 465 appnLsTableChanges, 466 appnLsOperState 467 } 468 STATUS current 469 DESCRIPTION 470 "When it has been enabled, this notification makes it possible 471 for an APPN topology application to get asynchronous 472 notifications of link station operational state changes, and 473 thus to reduce the frequency with which it polls for these 474 changes. This notification is only sent when a appnLsOperState 475 has transitioned to a value of 'active' or 'inactive'. 477 This notification is sent whenever there is a appnLsOperState 478 object transition to 'inactive' or 'active' state in the 479 appnLsTable. This notification is only sent for row creation 480 if the row is created with a value of 'active' for 481 appnLsOperState. This notification is only sent for 482 row deletion if the last value of appnLsOperState was 483 'active'. In this case, the value of appnLsOperState 484 in the notification shall be 'inactive', since the deletion of 485 a row indicates that the link station is no longer active. 487 The notification is more than a simple 'poll me now' indication. 488 It carries both a count of link station table changes, and the 489 operational state itself. The count of changes allows an 490 application to detect lost notifications, either when polling 491 or upon receiving a subsequent notification, at which point it 492 knows it must retrieve the entire appnLsTable again. 494 Generation of this notification is controlled by the 495 appnTrapControl object." 497 ::= { appnTrapMIB 5 } 499 dlurDlusStateChangeTrap NOTIFICATION-TYPE 500 OBJECTS { 501 dlurDlusTableChanges, 502 dlurDlusSessnStatus 503 } 504 STATUS current 505 DESCRIPTION 506 "When it has been enabled, this notification makes it possible 507 for an APPN topology application to get asynchronous 508 notifications of DLUR-DLUS session changes, and thus to reduce 509 the frequency with which it polls for these changes. 511 This notification is sent whenever there is a dlurDlusSessnStatus 512 object transition to 'inactive' or 'active' state in the 513 dlurDlusTable. This notification is only sent for row creation 514 if the row is created with a value of 'active' for 515 dlurDlusSessnStatus. This notification is only sent for 516 row deletion if the last value of dlurDlusSessnStatus was 517 'active'. In this case, the value of dlurDlusSessnStatus 518 in the notification shall be 'inactive', since the deletion of 519 a row indicates that the session is no longer active. 521 The notification is more than a simple 'poll me now' indication. 522 It carries both a count of DLUR-DLUS table changes, and the 523 session status itself. The count of changes allows an 524 application to detect lost notifications, either when polling 525 or upon receiving a subsequent notification, at which point it 526 knows it must retrieve the entire dlurDlusTable again. 528 Generation of this notification is controlled by the 529 appnTrapControl object." 531 ::= { appnTrapMIB 6 } 533 -- ********************************************************************* 534 -- Supporting Objects 535 -- ********************************************************************* 537 appnTrapObjects OBJECT IDENTIFIER ::= { appnObjects 7 } 539 appnTrapControl OBJECT-TYPE 541 SYNTAX BITS { 542 appnLocalTgOperStateChangeTrap(0), 543 appnLocalTgCpCpChangeTrap(1), 544 appnPortOperStateChangeTrap(2), 545 appnLsOperStateChangeTrap(3), 546 dlurDlusStateChangeTrap(4) 547 -- add other notification types here 548 } 549 MAX-ACCESS read-write 550 STATUS current 551 DESCRIPTION 552 "An object to turn APPN notification generation on and off. 553 Setting a notification type's bit to 1 enables generation of 554 notifications of that type, subject to further filtering 555 resulting from entries in the snmpNotificationMIB. Setting 556 this bit to 0 disables generation of notifications of that 557 type. 559 Note that generation of the appnIsrAccountingDataTrap is 560 controlled by the appnIsInGlobeCtrAdminStatus object in 561 the APPN MIB: if counts of intermediate session traffic 562 are being kept at all, then the notification is also enabled." 564 ::= { appnTrapObjects 1 } 566 appnLocalTgTableChanges OBJECT-TYPE 567 SYNTAX Counter32 568 MAX-ACCESS read-only 569 STATUS current 570 DESCRIPTION 571 "A count of the number of times a row in the appnLocalTgTable 572 has changed status since the APPN node was last reinitialized. 573 This counter is incremented whenever a condition is detected 574 that would cause a appnLocalTgOperStateChangeTrap or 575 appnLocalTgCpCpChangeTrap notification to be sent, whether 576 or not those notifications are enabled." 578 ::= { appnTrapObjects 2 } 580 appnPortTableChanges OBJECT-TYPE 581 SYNTAX Counter32 582 MAX-ACCESS read-only 583 STATUS current 584 DESCRIPTION 585 "A count of the number of times a row in the appnPortTable 586 has changed status since the APPN node was last reinitialized. 587 This counter is incremented whenever a condition is detected 588 that would cause a appnPortOperStateChangeTrap notification 589 to be sent, whether or not this notification is enabled." 591 ::= { appnTrapObjects 3 } 593 appnLsTableChanges OBJECT-TYPE 594 SYNTAX Counter32 595 MAX-ACCESS read-only 596 STATUS current 597 DESCRIPTION 598 "A count of the number of times a row in the appnLsTable 599 has changed status since the APPN node was last reinitialized. 600 This counter is incremented whenever a condition is detected 601 that would cause a appnLsOperStateChangeTrap notification 602 to be sent, whether or not this notification is enabled." 604 ::= { appnTrapObjects 4 } 606 dlurDlusTableChanges OBJECT-TYPE 607 SYNTAX Counter32 608 MAX-ACCESS read-only 609 STATUS current 610 DESCRIPTION 611 "A count of the number of times a row in the dlurDlusTable 612 has changed status since the APPN node was last reinitialized. 613 This counter is incremented whenever a condition is detected 614 that would cause a dlurDlusStateChangeTrap notification 615 to be sent, whether or not this notification is enabled." 617 ::= { appnTrapObjects 5 } 619 -- ********************************************************************* 620 -- Conformance information 621 -- ********************************************************************* 623 -- Tie into the conformance structure in the APPN MIB: 624 -- appnConformance OBJECT IDENTIFIER ::= {appnMIB 3 } 625 -- 626 -- appnCompliances OBJECT IDENTIFIER ::= {appnConformance 1 } 627 -- appnGroups OBJECT IDENTIFIER ::= {appnConformance 2 } 629 -- Compliance statement 630 appnTrapMibCompliance MODULE-COMPLIANCE 631 STATUS current 632 DESCRIPTION 633 "The compliance statement for the SNMP entities that 634 implement the APPN-TRAP-MIB." 636 MODULE -- this module 638 -- Conditionally mandatory groups 639 GROUP appnTrapMibIsrNotifGroup 640 DESCRIPTION 641 "This group is mandatory for APPN nodes supporting 642 reporting of final ISR counter values via notifications." 644 GROUP appnTrapMibTopoConfGroup 645 DESCRIPTION 646 "This group is mandatory for APPN nodes supporting 647 polling reduction for local topology." 649 GROUP appnTrapMibTopoNotifGroup 650 DESCRIPTION 651 "This group is mandatory for APPN nodes supporting 652 polling reduction for local topology." 654 GROUP appnTrapMibDlurConfGroup 655 DESCRIPTION 656 "This group is mandatory for APPN nodes supporting 657 polling reduction for the dlurDlusTable." 659 GROUP appnTrapMibDlurNotifGroup 660 DESCRIPTION 661 "This group is mandatory for APPN nodes supporting 662 polling reduction for the dlurDlusTable." 664 OBJECT appnTrapControl 665 MIN-ACCESS read-only 666 DESCRIPTION 667 "An agent is not required to support a set to 668 this object." 670 ::= {appnCompliances 2 } 672 -- Units of conformance 673 appnTrapMibIsrNotifGroup NOTIFICATION-GROUP 674 NOTIFICATIONS { 675 appnIsrAccountingDataTrap 676 } 677 STATUS current 678 DESCRIPTION 679 "A notification for reporting the final values of the 680 APPN MIB's ISR counters." 682 ::= { appnGroups 21 } 684 appnTrapMibTopoConfGroup OBJECT-GROUP 685 OBJECTS { 686 appnTrapControl, 687 appnLocalTgTableChanges, 688 appnPortTableChanges, 689 appnLsTableChanges 690 } 691 STATUS current 692 DESCRIPTION 693 "A collection of objects for reducing the polling 694 associated with the local topology tables in the 695 APPN MIB. Nodes that implement this group SHALL 696 also implement the appnTrapMibTopoNotifGroup." 698 ::= { appnGroups 22 } 700 appnTrapMibTopoNotifGroup NOTIFICATION-GROUP 701 NOTIFICATIONS { 702 appnLocalTgOperStateChangeTrap, 703 appnLocalTgCpCpChangeTrap, 704 appnPortOperStateChangeTrap, 705 appnLsOperStateChangeTrap 707 } 708 STATUS current 709 DESCRIPTION 710 "A collection of notifications for reducing the polling 711 associated with the local topology tables in the 712 APPN MIB. Nodes that implement this group SHALL 713 also implement the appnTrapMibTopoConfGroup." 715 ::= { appnGroups 23 } 717 appnTrapMibDlurConfGroup OBJECT-GROUP 718 OBJECTS { 719 appnTrapControl, 720 dlurDlusTableChanges 721 } 722 STATUS current 723 DESCRIPTION 724 "A collection of objects for reducing the polling 725 associated with the dlurDlusTable in the DLUR 726 MIB. Nodes that implement this group SHALL also 727 implement the appnTrapMibDlurNotifGroup." 729 ::= { appnGroups 24 } 731 appnTrapMibDlurNotifGroup NOTIFICATION-GROUP 732 NOTIFICATIONS { 733 dlurDlusStateChangeTrap 734 } 735 STATUS current 736 DESCRIPTION 737 "A notification for reducing the polling associated 738 with the dlurDlusTable in the DLUR MIB. Nodes that 739 implement this group SHALL also implement the 740 appnTrapMibDlurConfGroup." 742 ::= { appnGroups 25 } 744 END 745 5. Security Considerations 747 Certain management information defined in this MIB may be considered 748 sensitive in some network environments. Therefore, authentication of 749 received SNMP requests and controlled access to management information 750 SHOULD be employed in such environments. An authentication protocol is 751 defined in [10]. A protocol for access control is defined in [11]. 753 None of the read-only objects in the APPN TRAP MIB reports a password, 754 user data, or anything else that is particularly sensitive. Some 755 enterprises view their network configuration itself, as well as 756 information about network usage and performance, as corporate assets; 757 such enterprises may wish to restrict SNMP access to most of the objects 758 in the MIB. 760 There is one read-write object in the APPN TRAP MIB, appnTrapControl. 761 This object controls the generation of the notifications defined in the 762 APPN TRAP MIB. 764 6. Intellectual Property 766 The IETF takes no position regarding the validity or scope of any 767 intellectual property or other rights that might be claimed to pertain 768 to the implementation or use of the technology described in this 769 document or the extent to which any license under such rights might or 770 might not be available; neither does it represent that it has made any 771 effort to identify any such rights. Information on the IETF's 772 procedures with respect to rights in standards-track and standards- 773 related documentation can be found in BCP-11 [12]. Copies of claims of 774 rights made available for publication and any assurances of licenses to 775 be made available, or the result of an attempt made to obtain a general 776 license or permission for the use of such proprietary rights by 777 implementers or users of this specification can be obtained from the 778 IETF Secretariat. 780 The IETF invites any interested party to bring to its attention any 781 copyrights, patents or patent applications, or other proprietary rights 782 which may cover technology that may be required to practice this 783 standard. Please address the information to the IETF Executive 784 Director. 786 7. Acknowledgments 788 This MIB module is the product of the IETF SNA NAU MIB WG and the AIW 789 APPN/HPR MIBs SIG. 791 8. References 793 [1] Case, J., M. Fedor, M. Schoffstall, J. Davin, "Simple Network 794 Management Protocol", RFC 1157, SNMP Research, Performance Systems 795 International, MIT Laboratory for Computer Science, May 1990. 797 [2] McCloghrie, K., and M. Rose, Editors, "Management Information Base 798 for Network Management of TCP/IP-based internets: MIB-II", STD 17, 799 RFC 1213, Hughes LAN Systems, Performance Systems International, 800 March 1991. 802 [3] Case, J., McCloghrie, K., Rose, M., and Waldbusser S., "Structure 803 of Management Information for Version 2 of the Simple Network 804 Management Protocol (SNMPv2)", RFC 1902, January 1996. 806 [4] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Textual 807 Conventions for Version 2 of the Simple Network Management Protocol 808 (SNMPv2)", RFC 1903, January 1996. 810 [5] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., 811 "Conformance Statements for Version 2 of the Simple Network 812 Management Protocol (SNMPv2)", RFC 1904, January 1996. 814 [6] Case, J., McCloghrie, K., Rose, M., and Waldbusser, S., "Protocol 815 Operations for Version 2 of the Simple Network Management Protocol 816 (SNMPv2)", RFC 1905, January 1996. 818 [7] Harrington D., Presuhn, R., Wijnen, B., "An Architecture for 819 Describing SNMP Management Frameworks", RFC 2271, Cabletron 820 Systems, BMC Software, Inc., IBM T.J. Watson Research, January 821 1998. 823 [8] Harrington D., Presuhn, R., Wijnen, B., "Message Processing and 824 Dispatching for the Simple Network Management Protocol (SNMP)", RFC 825 2272, Cabletron Systems, BMC Software, Inc., IBM T.J. Watson 826 Research, January 1998. 828 [9] Levi D., Meyer P., Stewart, B., "SNMPv3 Applications", RFC 2273, 829 SNMP Research, Inc., Secure Computing Corporation, Cisco Systems, 830 January 1998. 832 [10] Blumenthal, U., Wijnen, B., "User-based Security Model (USM) for 833 version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 834 2274, IBM T. J. Watson Research, January 1998 836 [11] Wijnen, B., Presuhn, R., McCloghrie, K., "View-based Access Control 837 Model (VACM) for the Simple Network Management Protocol (SNMP)", 838 RFC 2275, IBM T.J. Watson Research, BMC Software, Inc., Cisco 839 Systems, Inc., January 1998. 841 [12] Hovey, R., and S. Bradner, "The Organizations Involved in the IETF 842 Standards Process", BCP 11, RFC 2028, October 1996. 844 [13] Bradner, S., "Key words for use in RFCs to Indicate Requirement 845 Levels", BCP 14, RFC 2119, March 1997. 847 [14] Clouston, B., and B. Moore, "Definition of Managed Objects for APPN 848 using SMIv2", RFC 2155, June 1997. 850 [15] Clouston, B., and B. Moore, "Definitions of Managed Objects for 851 DLUR", RFC 2232, November 1997. 853 9. Authors' Addresses 855 Bob Clouston 856 Cisco Systems 857 7025 Kit Creek Road 858 P.O. Box 14987 859 Research Triangle Park, NC 27709, USA 861 Tel: 1 919 472 2333 862 E-mail: clouston@cisco.com 864 Robert Moore 865 Dept. BRQA/Bldg. 501/G114 866 IBM Corporation 867 P.O.Box 12195 868 3039 Cornwallis 869 Research Triangle Park, NC 27709, USA 871 Phone: +1-919-254-4436 872 E-mail: remoore@us.ibm.com 874 10. Full Copyright Statement 876 Copyright (C) The Internet Society (1998). All Rights Reserved. 878 This document and translations of it may be copied and furnished to 879 others, and derivative works that comment on or otherwise explain it or 880 assist in its implementation may be prepared, copied, published and 881 distributed, in whole or in part, without restriction of any kind, 882 provided that the above copyright notice and this paragraph are included 883 on all such copies and derivative works. However, this document itself 884 may not be modified in any way, such as by removing the copyright notice 885 or references to the Internet Society or other Internet organizations, 886 except as needed for the purpose of developing Internet standards in 887 which case the procedures for copyrights defined in the Internet 888 Standards process must be followed, or as required to translate it into 889 languages other than English. 891 The limited permissions granted above are perpetual and will not be 892 revoked by the Internet Society or its successors or assigns. 894 This document and the information contained herein is provided on an "AS 895 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK 896 FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT 897 LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT 898 INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR 899 FITNESS FOR A PARTICULAR PURPOSE. 901 Table of Contents 903 1. Introduction ........................................... 2 904 2. The SNMP Network Management Framework .................. 2 905 3. Overview ............................................... 3 906 3.1 APPN TRAP MIB structure .............................. 5 907 4. Definitions ............................................ 7 908 5. Security Considerations ................................ 18 909 5. Intellectual Property .................................. 18 910 7. Acknowledgments ........................................ 18 911 8. References ............................................. 19 912 9. Author's Addresses ..................................... 20 913 10. Full Copyright Statement ............................... 20