idnits 2.17.1 draft-ietf-snanau-hpripmib-02.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 7 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 doesn't use any RFC 2119 keywords, yet seems to have RFC 2119 boilerplate text. -- 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 (October 14, 1998) is 9327 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: '16' is defined on line 888, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2271 (ref. '1') (Obsoleted by RFC 2571) ** Downref: Normative reference to an Informational RFC: RFC 1215 (ref. '4') ** Obsolete normative reference: RFC 1902 (ref. '5') (Obsoleted by RFC 2578) ** Obsolete normative reference: RFC 1903 (ref. '6') (Obsoleted by RFC 2579) ** Obsolete normative reference: RFC 1904 (ref. '7') (Obsoleted by RFC 2580) ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. '8') ** Downref: Normative reference to an Historic RFC: RFC 1901 (ref. '9') ** Obsolete normative reference: RFC 1906 (ref. '10') (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2272 (ref. '11') (Obsoleted by RFC 2572) ** Obsolete normative reference: RFC 2274 (ref. '12') (Obsoleted by RFC 2574) ** Obsolete normative reference: RFC 1905 (ref. '13') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2273 (ref. '14') (Obsoleted by RFC 2573) ** Obsolete normative reference: RFC 2275 (ref. '15') (Obsoleted by RFC 2575) ** Obsolete normative reference: RFC 2028 (ref. '16') (Obsoleted by RFC 9281) ** Downref: Normative reference to an Informational RFC: RFC 2353 (ref. '18') -- Possible downref: Non-RFC (?) normative reference: ref. '19' Summary: 25 errors (**), 0 flaws (~~), 4 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Definitions of Managed Objects 3 for APPN/HPR in IP Networks 5 October 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 39 This memo defines a portion of the Management Information Base (MIB) for 40 use with network management protocols in the Internet community. In 41 particular, it defines objects for monitoring and controlling HPR (High 42 Performance Routing) network devices which have the capability to 43 communicate in IP (Internet Protocol) networks. This memo identifies 44 managed objects for the HPR in IP network communications. 46 1. Introduction 48 This document is a product of the SNA NAU Services MIB Working Group. 49 It defines a MIB module for managing devices with HPR in IP networks 50 capabilities. 52 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 53 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 54 document are to be interpreted as described in RFC 2119 [17]. 56 This memo does not specify a standard for the Internet community. 58 2. The SNMP Network Management Framework 60 The SNMP Management Framework presently consists of five major 61 components: 63 o An overall architecture, described in RFC 2271 [1]. 65 o Mechanisms for describing and naming objects and events for the 66 purpose of management. The first version of this Structure of 67 Management Information (SMI) is called SMIv1 and described in RFC 68 1155 [2], RFC 1212 [3] and RFC 1215 [4]. The second version, called 69 SMIv2, is described in RFC 1902 [5], RFC 1903 [6] and RFC 1904 [7]. 71 o Message protocols for transferring management information. The 72 first version of the SNMP message protocol is called SNMPv1 and 73 described in RFC 1157 [8]. A second version of the SNMP message 74 protocol, which is not an Internet standards track protocol, is 75 called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10]. The 76 third version of the message protocol is called SNMPv3 and 77 described in RFC 1906 [10], RFC 2272 [11] and RFC 2274 [12]. 79 o Protocol operations for accessing management information. The first 80 set of protocol operations and associated PDU formats is described 81 in RFC 1157 [8]. A second set of protocol operations and associated 82 PDU formats is described in RFC 1905 [13]. 84 o A set of fundamental applications described in RFC 2273 [14] and 85 the view-based access control mechanism described in RFC 2275 [15]. 87 Managed objects are accessed via a virtual information store, termed the 88 Management Information Base or MIB. Objects in the MIB are defined 89 using the mechanisms defined in the SMI. 91 This memo specifies a MIB module that is compliant to the SMIv2. A MIB 92 conforming to the SMIv1 can be produced through the appropriate 93 translations. The resulting translated MIB must be semantically 94 equivalent, except where objects or events are omitted because no 95 translation is possible (use of Counter64). Some machine readable 96 information in SMIv2 will be converted into textual descriptions in 97 SMIv1 during the translation process. However, this loss of machine 98 readable information is not considered to change the semantics of the 99 MIB. 101 3. Overview 103 This document identifies a set of objects for monitoring the 104 configuration and active characteristics of devices with HPR in IP 105 network capabilities. HPR is an enhancement to the Advanced Peer-to- 106 Peer Network (APPN) architecture that provides fast data routing and 107 improved session reliability. APPN is the aspect of Systems Network 108 Architecture (SNA) that supports peer-to-peer networking. APPN/HPR in IP 109 Networks is a further enhancement to the APPN/HPR architecture, 110 described in RFC 2353 [18]. It provides a method with which APPN/HPR 111 nodes can communicate in IP networks. 113 APPN management information is defined by the APPN MIB [19]. HPR 114 management information is defined by the HPR MIB, RFC 2238 [20]. 116 Highlights of the management functions supported by the APPN/HPR in IP 117 Networks MIB module include the following: 119 o A count of UDP packets sent with each type of APPN traffic on 120 HPR/IP links. 122 o Monitoring and setting configuration parameters for the mappings 123 between APPN traffic types on Type of Service (TOS) Precedence 124 settings in the IP header. 126 This MIB module does not support: 128 o Configuration of IP addresses used for APPN ports or link stations. 130 3.1. HPR/IP Values for Objects in the APPN MIB 132 Ports and link stations are the APPN device's interface to the data link 133 control (DLC), which provides the physical transport, or to another 134 protocol, such as IP. The APPN MIB identifies ports and link stations 135 using IP as the transport with the following objects: 137 o appnPortDlcType 139 o appnLsDlcType 141 o appnLsStatusDlcType 143 These objects all have the syntax IANAifType, and the value 126, defined 144 as "IP (for APPN HPR in IP networks)" shall be returned when they 145 identify an HPR/IP port or link station. 147 The IP address used for the port or link station is returned in the 148 following objects: 150 o appnPortDlcLocalAddr 152 o appnLsLocalAddr 154 o appnLsRemoteAddr 156 o appnLsStatusLocalAddr 158 o appnLsStatusRemoteAddr 160 These objects have the syntax DisplayableDlcAddress, defined in the APPN 161 MIB as a textual convention to represent the address as an octet string 162 of ASCII characters. 164 The following two objects return object identifiers that tie port and 165 link table entries in the APPN MIB to lower-layer MIB entries: 167 o appnPortSpecific 168 o appnLsSpecific 170 Both objects should return a RowPointer to the ifEntry in the agent's 171 ifTable for the physical interface associated with the local IP address 172 for the port. If the agent implements the IP-MIB (RFC 2011), this 173 association between the IP address and the physical interface will be 174 represented in the ipNetToMediaTable. 176 3.2. APPN/HPR in IP Networks MIB Structure 178 The APPN/HPR in IP Networks MIB module contains two groups of objects: 180 o hprIpMonitoringGroup - an object for counting outgoing HPR/IP 181 traffic for each APPN traffic type 183 o hprIpConfigurationGroup - objects to represent TOS Precedence to 184 APPN traffic type mappings 186 These groups are described below in more detail. 188 3.2.1. hprIpMonitoringGroup 190 The hprIpMonitoringGroup group consists of the hprIpActiveLsTable. This 191 table is indexed by the link station name and traffic type, and contains 192 a counter for the number of UDP packets sent on a link station for that 193 traffic type. 195 3.2.2. hprIpConfigurationGroup 197 The hprIpMonitoringGroup group consists of the following objects and 198 tables: 200 1) hprIpAppnPortTable 202 This table supports reading and setting the default mapping between APPN 203 traffic types and TOS Precedence settings for all link stations using a 204 port. This mapping may be overridden for individual link stations or 205 individual connection networks. 207 2) hprIpLsTable 208 This table supports reading and setting the mappings between APPN 209 traffic types and TOS Precedence settings for an individual link station 210 and APPN traffic type. If there is no entry in this table for a given 211 link station and traffic type, then that link station inherits its 212 mapping from its port. 214 3) hprIpCnTable 216 This table supports reading and setting the mapping between APPN traffic 217 types and TOS Precedence settings for an individual connection network 218 and traffic type. If there is no entry in this table for a given 219 connection network and traffic type, then that connection network 220 inherits its mapping from its port. 222 4. Definitions 224 HPR-IP-MIB DEFINITIONS ::= BEGIN 226 IMPORTS 227 MODULE-IDENTITY,OBJECT-TYPE, Counter32 228 FROM SNMPv2-SMI 229 DisplayString, RowStatus, TEXTUAL-CONVENTION 230 FROM SNMPv2-TC 231 MODULE-COMPLIANCE, OBJECT-GROUP 232 FROM SNMPv2-CONF 233 SnaControlPointName 234 FROM APPN-MIB 235 hprObjects, hprCompliances, hprGroups 236 FROM HPR-MIB ; 238 hprIp MODULE-IDENTITY 239 LAST-UPDATED "9809240000Z" -- September 24, 1998 240 ORGANIZATION "IBM" 241 CONTACT-INFO 242 " 243 Bob Clouston 244 Cisco Systems 245 7025 Kit Creek Road 246 P.O. Box 14987 247 Research Triangle Park, NC 27709, USA 248 Tel: 1 919 472 2333 249 E-mail: clouston@cisco.com 251 Bob Moore 252 IBM Corporation 253 4205 S. Miami Boulevard 254 BRQA/501 255 P.O. Box 12195 256 Research Triangle Park, NC 27709, USA 257 Tel: 1 919 254 4436 258 E-mail: remoore@us.ibm.com 259 " 260 DESCRIPTION 261 "The MIB module for HPR over IP. This module contains two 262 groups: 264 - the HPR over IP Monitoring Group provides a count of the UDP 265 packets sent by a link station for each APPN traffic type. 267 - the HPR over IP Configuration Group provides for reading and 268 setting the mappings between APPN traffic types and TOS 269 Precedence settings in the IP header. These mappings are 270 configured at the APPN port level, and are inherited by the 271 APPN connection networks and link stations associated with an 272 APPN port. A port-level mapping can, however, be overridden 273 for a particular connection network or link station." 274 REVISION "9809240000Z" -- September 24, 1998 275 DESCRIPTION 276 "RFC nnnn (Proposed Standard)" -- RFC Editor to fill in number 278 ::= { hprObjects 5 } 280 -- ********************************************************************* 281 -- Textual Conventions 282 -- ********************************************************************* 283 AppnTrafficType ::= TEXTUAL-CONVENTION 284 STATUS current 285 DESCRIPTION 286 "APPN traffic type. The first four values correspond 287 to APPN transmission priorities (network, high, medium and 288 low), while the fifth is used for both LLC commands (XID, 289 TEST, DISC, and DM) and function-routed NLPs (XID_DONE_RQ 290 and XID_DONE_RSP)." 292 SYNTAX INTEGER { low (1), 293 medium (2), 294 high (3), 295 network (4), 296 llcAndFnRoutedNlp (5) } 298 AppnTOSPrecedence ::= TEXTUAL-CONVENTION 299 STATUS current 300 DESCRIPTION 301 "A DisplayString representing the setting of the three TOS 302 Precedence bits in the IP Type of Service field for this APPN 303 traffic type. The HPR over IP architecture specifies the 304 following default mapping: 306 APPN traffic type IP TOS Precedence bits 307 ------------------ ---------------------- 308 Network 110 309 High 100 310 Medium 010 311 Low 001 312 LLC commands, etc. 110 313 " 315 SYNTAX DisplayString (SIZE(3)) 317 -- ******************************************************************* 318 -- hprObjects OBJECT IDENTIFIER ::= { hprMIB 1 } 319 -- ******************************************************************* 321 -- ******************************************************************* 322 -- HPR over IP Monitoring Group 323 -- 324 -- This group contains a single table, the hprIsActiveLsTable, 325 -- providing a count of UDP packets sent with each type of 326 -- APPN traffic on each active link supporting HPR over IP. 327 -- ******************************************************************* 328 hprIpActiveLsTable OBJECT-TYPE 329 SYNTAX SEQUENCE OF HprIpActiveLsEntry 330 MAX-ACCESS not-accessible 331 STATUS current 332 DESCRIPTION 333 "The HPR/IP active link station table. This table provides 334 counts of the number of UDP packets sent for each APPN 335 traffic type." 337 ::= { hprIp 1 } 339 hprIpActiveLsEntry OBJECT-TYPE 340 SYNTAX HprIpActiveLsEntry 341 MAX-ACCESS not-accessible 342 STATUS current 343 DESCRIPTION 344 "Entry of the HPR/IP link station table." 346 INDEX { hprIpActiveLsLsName, 347 hprIpActiveLsAppnTrafficType } 349 ::= { hprIpActiveLsTable 1 } 351 HprIpActiveLsEntry ::= SEQUENCE { 352 hprIpActiveLsLsName DisplayString, 353 hprIpActiveLsAppnTrafficType AppnTrafficType, 354 hprIpActiveLsUdpPackets Counter32 } 356 hprIpActiveLsLsName OBJECT-TYPE 357 SYNTAX DisplayString (SIZE (1..10)) 358 MAX-ACCESS not-accessible 359 STATUS current 360 DESCRIPTION 361 "Administratively assigned name for the link station. If this 362 object has the same value as the appnLsName in the APPN MIB, 363 then the two objects are referring to the same APPN link 364 station." 366 ::= { hprIpActiveLsEntry 1 } 368 hprIpActiveLsAppnTrafficType OBJECT-TYPE 369 SYNTAX AppnTrafficType 370 MAX-ACCESS not-accessible 371 STATUS current 372 DESCRIPTION 373 "APPN traffic type being sent through the link station." 375 ::= { hprIpActiveLsEntry 2 } 377 hprIpActiveLsUdpPackets OBJECT-TYPE 378 SYNTAX Counter32 379 MAX-ACCESS read-only 380 STATUS current 381 DESCRIPTION 382 "The count of outgoing UDP packets carrying this type of APPN 383 traffic. A discontinuity in the counter is indicated by the 384 appnLsCounterDisconTime object in the APPN MIB." 386 ::= { hprIpActiveLsEntry 3 } 388 -- ******************************************************************* 389 -- HPR over IP Configuration Group 390 -- 391 -- This group contains three tables for reading and setting the 392 -- mapping between APPN traffic types and values for the TOS 393 -- Precedence bits in the IP header. hprIpAppnPortTOSPrecedence 394 -- represents the APPN port-level mapping. This mapping can be 395 -- overridden for an individual link station or an individual 396 -- connection network via, respectively, the hprIpLsTOSPrecedence 397 -- and the hprIpCnTOSPrecedence objects. 398 -- ******************************************************************* 400 hprIpAppnPortTable OBJECT-TYPE 401 SYNTAX SEQUENCE OF HprIpAppnPortEntry 402 MAX-ACCESS not-accessible 403 STATUS current 404 DESCRIPTION 405 "The HPR/IP APPN port table. This table supports reading and 406 setting the mapping between APPN traffic types and TOS 407 Precedence settings for all the link stations at this APPN 408 port. This mapping can be overridden for an individual link 409 station or an individual connection network via, respectively, 410 the hprIpLsTOSPrecedence and the hprIpCnTOSPrecedence objects." 412 ::= { hprIp 2 } 414 hprIpAppnPortEntry OBJECT-TYPE 415 SYNTAX HprIpAppnPortEntry 416 MAX-ACCESS not-accessible 417 STATUS current 418 DESCRIPTION 419 "Entry of the HPR/IP APPN port table. Entries exist for 420 every APPN port defined to support HPR over IP." 422 INDEX { hprIpAppnPortName, 423 hprIpAppnPortAppnTrafficType } 425 ::= { hprIpAppnPortTable 1 } 427 HprIpAppnPortEntry ::= SEQUENCE { 428 hprIpAppnPortName DisplayString, 429 hprIpAppnPortAppnTrafficType AppnTrafficType, 430 hprIpAppnPortTOSPrecedence AppnTOSPrecedence } 432 hprIpAppnPortName OBJECT-TYPE 433 SYNTAX DisplayString (SIZE (1..10)) 434 MAX-ACCESS not-accessible 435 STATUS current 436 DESCRIPTION 437 "Administratively assigned name for this APPN port. If this 438 object has the same value as the appnPortName in the APPN MIB, 439 then the two objects are referring to the same APPN port." 441 ::= { hprIpAppnPortEntry 1 } 443 hprIpAppnPortAppnTrafficType OBJECT-TYPE 444 SYNTAX AppnTrafficType 445 MAX-ACCESS not-accessible 446 STATUS current 447 DESCRIPTION 448 "APPN traffic type sent through the port." 450 ::= { hprIpAppnPortEntry 2 } 452 hprIpAppnPortTOSPrecedence OBJECT-TYPE 453 SYNTAX AppnTOSPrecedence 454 MAX-ACCESS read-write 455 STATUS current 456 DESCRIPTION 457 "A setting for the three TOS Precedence bits in the IP Type of 458 Service field for this APPN traffic type. 460 When this value is changed via a Set operation, the new setting 461 for the TOS Precedence bits takes effect immediately, rather 462 than waiting for some event such as reinitialization of the 463 port or of the APPN node itself." 465 ::= { hprIpAppnPortEntry 3 } 467 -- ******************************************************************* 468 hprIpLsTable OBJECT-TYPE 469 SYNTAX SEQUENCE OF HprIpLsEntry 470 MAX-ACCESS not-accessible 471 STATUS current 472 DESCRIPTION 473 "The HPR/IP link station table. Values for TOS Precedence at 474 the link station level override those at the level of the 475 containing port. If there is no entry in this table for a 476 given link station, then that link station inherits its TOS 477 Precedence values from its port." 479 ::= { hprIp 3 } 481 hprIpLsEntry OBJECT-TYPE 482 SYNTAX HprIpLsEntry 483 MAX-ACCESS not-accessible 484 STATUS current 485 DESCRIPTION 486 "Entry of the HPR/IP link station table." 488 INDEX { hprIpLsLsName, 489 hprIpLsAppnTrafficType } 491 ::= { hprIpLsTable 1 } 493 HprIpLsEntry ::= SEQUENCE { 494 hprIpLsLsName DisplayString, 495 hprIpLsAppnTrafficType AppnTrafficType, 496 hprIpLsTOSPrecedence AppnTOSPrecedence, 497 hprIpLsRowStatus RowStatus } 499 hprIpLsLsName OBJECT-TYPE 500 SYNTAX DisplayString (SIZE (1..10)) 501 MAX-ACCESS not-accessible 502 STATUS current 503 DESCRIPTION 504 "Administratively assigned name for the link station. If this 505 object has the same value as the appnLsName in the APPN MIB, 506 then the two objects are referring to the same APPN link 507 station." 509 ::= { hprIpLsEntry 1 } 511 hprIpLsAppnTrafficType OBJECT-TYPE 512 SYNTAX AppnTrafficType 513 MAX-ACCESS not-accessible 514 STATUS current 515 DESCRIPTION 516 "APPN traffic type sent through the link station." 518 ::= { hprIpLsEntry 2 } 520 hprIpLsTOSPrecedence OBJECT-TYPE 521 SYNTAX AppnTOSPrecedence 522 MAX-ACCESS read-create 523 STATUS current 524 DESCRIPTION 525 "A setting for the three TOS Precedence bits in the IP Type of 526 Service field for this APPN traffic type. 528 When this value is changed via a Set operation, the new setting 529 for the TOS Precedence bits takes effect immediately, rather 530 than waiting for some event such as reinitialization of the 531 port or of the APPN node itself." 533 ::= { hprIpLsEntry 3 } 535 hprIpLsRowStatus OBJECT-TYPE 536 SYNTAX RowStatus 537 MAX-ACCESS read-create 538 STATUS current 539 DESCRIPTION 540 "This object allows entries to be created and deleted in the 541 hprIpLsTable. As soon as an entry becomes active, the mapping 542 between APPN traffic types and TOS Precedence settings that it 543 specifies becomes effective. 545 The value of the other accessible object in this entry, 546 hprIpLsTOSPrecedence, can be changed via a Set operation when 547 this object's value is active(1). 549 An entry in this table is deleted by setting this object to 550 destroy(6). Deleting an entry in this table causes the 551 link station to revert to the default TOS Precedence 552 mapping for its port." 554 ::= { hprIpLsEntry 4 } 556 -- ******************************************************************* 557 hprIpCnTable OBJECT-TYPE 558 SYNTAX SEQUENCE OF HprIpCnEntry 559 MAX-ACCESS not-accessible 560 STATUS current 561 DESCRIPTION 562 "The HPR/IP connection network table. Values for TOS 563 Precedence at the connection network level override those at 564 the level of the containing port. If there is no entry in 565 this table for a given connection network, then that 566 connection network inherits its TOS Precedence values from 567 its port. 569 A node may have connections to a given connection network 570 through multiple ports. There is no provision in the HPR-IP 571 architecture for variations in TOS Precedence values for 572 a single connection network based on the port through which 573 traffic is flowing to the connection network. Thus an entry 574 in this table overrides the port-level settings for all the 575 ports through which the node can reach the connection 576 network." 578 ::= { hprIp 4 } 580 hprIpCnEntry OBJECT-TYPE 581 SYNTAX HprIpCnEntry 582 MAX-ACCESS not-accessible 583 STATUS current 584 DESCRIPTION 585 "Entry of the HPR/IP connection network table." 587 INDEX { hprIpCnVrnName, 588 hprIpCnAppnTrafficType } 590 ::= { hprIpCnTable 1 } 592 HprIpCnEntry ::= SEQUENCE { 593 hprIpCnVrnName SnaControlPointName, 594 hprIpCnAppnTrafficType AppnTrafficType, 595 hprIpCnTOSPrecedence AppnTOSPrecedence, 596 hprIpCnRowStatus RowStatus } 598 hprIpCnVrnName OBJECT-TYPE 599 SYNTAX SnaControlPointName 600 MAX-ACCESS not-accessible 601 STATUS current 602 DESCRIPTION 603 "SNA control point name of the virtual routing node (VRN) that 604 identifies the connection network in the APPN topology 605 database. If this object has the same value as the appnVrnName 606 in the APPN MIB, then the two objects are referring 607 to the same APPN VRN." 609 ::= { hprIpCnEntry 1 } 611 hprIpCnAppnTrafficType OBJECT-TYPE 612 SYNTAX AppnTrafficType 613 MAX-ACCESS not-accessible 614 STATUS current 615 DESCRIPTION 616 "APPN traffic type sent to this connection network." 618 ::= { hprIpCnEntry 2 } 620 hprIpCnTOSPrecedence OBJECT-TYPE 621 SYNTAX AppnTOSPrecedence 622 MAX-ACCESS read-create 623 STATUS current 624 DESCRIPTION 625 "A setting for the three TOS Precedence bits in the IP Type of 626 Service field for this APPN traffic type. This setting applies 627 to all traffic sent to this connection network by this node, 628 regardless of the port through which the traffic is sent. 630 When this value is changed via a Set operation, the new setting 631 for the TOS Precedence bits takes effect immediately, rather 632 than waiting for some event such as reinitialization of a 633 port or of the APPN node itself." 635 ::= { hprIpCnEntry 3 } 637 hprIpCnRowStatus OBJECT-TYPE 638 SYNTAX RowStatus 639 MAX-ACCESS read-create 640 STATUS current 641 DESCRIPTION 642 "This object allows entries to be created and deleted in the 643 hprIpCnTable. As soon as an entry becomes active, the mapping 644 between APPN traffic types and TOS Precedence settings that it 645 specifies becomes effective. 647 The value of the other accessible object in this entry, 648 hprIpCnTOSPrecedence, can be changed via a Set operation when 649 this object's value is active(1). 651 An entry in this table is deleted by setting this object to 652 destroy(6). Deleting an entry in this table causes the 653 connection network to revert to the default TOS Precedence 654 mapping for each port through which it is accessed." 656 ::= { hprIpCnEntry 4 } 658 -- ******************************************************************* 659 -- Conformance Statement 660 -- ******************************************************************* 661 -- Definitions imported from the HPR MIB: 662 -- hprConformance OBJECT IDENTIFIER ::= { hprMIB 2 } 663 -- hprCompliances OBJECT IDENTIFIER ::= { hprConformance 1 } 664 -- hprGroups OBJECT IDENTIFIER ::= { hprConformance 2 } 666 -- Compliance statements 667 hprIpCompliance MODULE-COMPLIANCE 668 STATUS current 669 DESCRIPTION 670 "Compliance statement for the HPR over IP MIB module." 671 MODULE -- this module 673 -- Conditionally mandatory groups 674 GROUP hprIpMonitoringGroup 675 DESCRIPTION 676 "The hprIpMonitoringGroup is mandatory for APPN implementations 677 supporting HPR over IP." 679 GROUP hprIpConfigurationGroup 680 DESCRIPTION 681 "The hprIpConfigurationGroup is mandatory for APPN 682 implementations supporting HPR over IP. It may, however, 683 be implemented as a collection of read-only objects." 685 OBJECT hprIpAppnPortTOSPrecedence 686 MIN-ACCESS read-only 687 DESCRIPTION 688 "Write access is not required." 690 OBJECT hprIpLsTOSPrecedence 691 MIN-ACCESS read-only 692 DESCRIPTION 693 "Write access is not required." 695 OBJECT hprIpLsRowStatus 696 MIN-ACCESS read-only 697 DESCRIPTION 698 "Write access is not required." 700 OBJECT hprIpCnTOSPrecedence 701 MIN-ACCESS read-only 702 DESCRIPTION 703 "Write access is not required." 705 OBJECT hprIpCnRowStatus 706 MIN-ACCESS read-only 707 DESCRIPTION 708 "Write access is not required." 710 ::= { hprCompliances 2 } 712 -- Group definitions 714 hprIpMonitoringGroup OBJECT-GROUP 715 OBJECTS { hprIpActiveLsUdpPackets } 716 STATUS current 717 DESCRIPTION 718 "An object for counting outgoing HPR/IP traffic for each APPN 719 traffic type." 721 ::= { hprGroups 5 } 723 hprIpConfigurationGroup OBJECT-GROUP 724 OBJECTS { hprIpAppnPortTOSPrecedence, 725 hprIpLsTOSPrecedence, 726 hprIpLsRowStatus, 727 hprIpCnTOSPrecedence, 728 hprIpCnRowStatus } 729 STATUS current 730 DESCRIPTION 731 "A collection of HPR/IP objects representing the mappings 732 between APPN traffic types and TOS Precedence bits at the APPN 733 port, APPN link station, and APPN connection network levels." 735 ::= { hprGroups 6 } 737 END 738 5. Security Considerations 740 Certain management information defined in this MIB may be considered 741 sensitive in some network environments. Therefore, authentication of 742 received SNMP requests and controlled access to management information 743 SHOULD be employed in such environments. An authentication protocol is 744 defined in [12]. A protocol for access control is defined in [15]. It 745 is a customer responsibility to properly set up access control for MIB 746 access. 748 None of the read-only objects in this MIB reports a password, user data, 749 or anything else that is particularly sensitive. Some enterprises view 750 their network configuration itself, as well as information about network 751 usage and performance, as corporate assets; such enterprises may wish to 752 restrict SNMP access to most of the objects in the MIB. 754 The one read-write and four read-create objects in the MIB can affect 755 network operations; it is recommended that SNMP access to these objects 756 be restricted. The five objects are: 758 o hprIpPortTOSPrecedence: Setting this object immediately changes 759 the mapping for all link stations using this port which do not have 760 an entry to override the port value. Improper mappings may cause 761 delays or disruptions in the network. For example, if APPN traffic 762 type 'High' is mapped to IP TOS Precedence bits '001', network 763 control traffic will have the same TOS precedence as bulk data 764 traffic. This may cause delays with session initializations, and 765 timeouts on control sessions that could cause network outages. 767 o hprIpLsTOSPrecedence: Setting this object has the potential for 768 delay or disruption for this link station as described above with 769 hprIpPortTOSPrecedence. 771 o hprIpLsRowStatus: Setting this object to delete(6) causes this 772 link station to revert to the default TOS Precedence mapping for 773 its port. The customized mapping for this link station will no 774 longer be in effect. 776 o hprIpCnTOSPrecedence: Setting this object has the potential for 777 delay or disruption for this links created for this connection 778 network as described above with hprIpPortTOSPrecedence. 780 o hprIpCnRowStatus: Setting this object to delete(6) causes links 781 created for this connection network to revert to the default TOS 782 Precedence mapping for its port. The customized mapping for this 783 connection network will no longer be in effect. 785 6. Intellectual Property 787 The IETF takes no position regarding the validity or scope of any 788 intellectual property or other rights that might be claimed to pertain 789 to the implementation or use of the technology described in this 790 document or the extent to which any license under such rights might or 791 might not be available; neither does it represent that it has made any 792 effort to identify any such rights. Information on the IETF's 793 procedures with respect to rights in standards-track and standards- 794 related documentation can be found in BCP-11 [16]. Copies of claims of 795 rights made available for publication and any assurances of licenses to 796 be made available, or the result of an attempt made to obtain a general 797 license or permission for the use of such proprietary rights by 798 implementers or users of this specification can be obtained from the 799 IETF Secretariat. 801 The IETF invites any interested party to bring to its attention any 802 copyrights, patents or patent applications, or other proprietary rights 803 which may cover technology that may be required to practice this 804 standard. Please address the information to the IETF Executive 805 Director. 807 7. Acknowledgments 809 This MIB module is the product of the IETF SNA NAU MIB WG and the AIW 810 APPN/HPR MIBs SIG. The editors would like to thank Katie Lee, IBM 811 Corporation, for her work in creating the original version of this MIB. 813 8. References 815 [1] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for 816 Describing SNMP Management Frameworks", RFC 2271, Cabletron 817 Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, 818 January 1998 820 [2] Rose, M., and K. McCloghrie, "Structure and Identification of 821 Management Information for TCP/IP-based Internets", RFC 1155, 822 Performance Systems International, Hughes LAN Systems, May 1990 824 [3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", RFC 1212, 825 Performance Systems International, Hughes LAN Systems, March 1991 827 [4] M. Rose, "A Convention for Defining Traps for use with the SNMP", 828 RFC 1215, Performance Systems International, March 1991 830 [5] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Structure 831 of Management Information for Version 2 of the Simple Network 832 Management Protocol (SNMPv2)", RFC 1902, SNMP Research,Inc., Cisco 833 Systems, Inc., Dover Beach Consulting, Inc., International Network 834 Services, January 1996. 836 [6] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Textual 837 Conventions for Version 2 of the Simple Network Management Protocol 838 (SNMPv2)", RFC 1903, SNMP Research, Inc., Cisco Systems, Inc., 839 Dover Beach Consulting, Inc., International Network Services, 840 January 1996. 842 [7] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Conformance 843 Statements for Version 2 of the Simple Network Management Protocol 844 (SNMPv2)", RFC 1904, SNMP Research, Inc., Cisco Systems, Inc., 845 Dover Beach Consulting, Inc., International Network Services, 846 January 1996. 848 [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network 849 Management Protocol", RFC 1157, SNMP Research, Performance Systems 850 International, Performance Systems International, MIT Laboratory 851 for Computer Science, May 1990. 853 [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 854 "Introduction to Community-based SNMPv2", RFC 1901, SNMP Research, 855 Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., 856 International Network Services, January 1996. 858 [10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport 859 Mappings for Version 2 of the Simple Network Management Protocol 860 (SNMPv2)", RFC 1906, SNMP Research, Inc., Cisco Systems, Inc., 861 Dover Beach Consulting, Inc., International Network Services, 862 January 1996. 864 [11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 865 Processing and Dispatching for the Simple Network Management 866 Protocol (SNMP)", RFC 2272, SNMP Research, Inc., Cabletron Systems, 867 Inc., BMC Software, Inc., IBM T. J. Watson Research, January 1998. 869 [12] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for 870 version 3 of the Simple Network Management Protocol (SNMPv3)", RFC 871 2274, IBM T. J. Watson Research, January 1998. 873 [13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol 874 Operations for Version 2 of the Simple Network Management Protocol 875 (SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco Systems, Inc., 876 Dover Beach Consulting, Inc., International Network Services, 877 January 1996. 879 [14] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC 880 2273, SNMP Research, Inc., Secure Computing Corporation, Cisco 881 Systems, January 1998 883 [15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access 884 Control Model (VACM) for the Simple Network Management Protocol 885 (SNMP)", RFC 2275, IBM T. J. Watson Research, BMC Software, Inc., 886 Cisco Systems, Inc., January 1998 888 [16] Hovey, R., and S. Bradner, "The Organizations Involved in the IETF 889 Standards Process", BCP 11, RFC 2028, October 1996. 891 [17] Bradner, S., "Key words for use in RFCs to Indicate Requirement 892 Levels", BCP 14, RFC 2119, March 1997. 894 [18] Dudley, G, "APPN/HPR in IP Networks", RFC 2353, IBM, May 1998. 896 [19] Clouston, B., and B. Moore, "Definition of Managed Objects for 897 APPN", Cisco Systems, IBM Corporation, July 1998. 899 [20] Clouston, B., and B. Moore, "Definitions of Managed Objects for 900 HPR", RFC 2238, May 1997. 902 9. Authors' Addresses 904 Bob Clouston 905 Cisco Systems 906 7025 Kit Creek Road 907 P.O. Box 14987 908 Research Triangle Park, NC 27709, USA 910 Tel: 1 919 472 2333 911 E-mail: clouston@cisco.com 913 Robert Moore 914 Dept. BRQA/Bldg. 501/G114 915 IBM Corporation 916 P.O.Box 12195 917 3039 Cornwallis 918 Research Triangle Park, NC 27709, USA 920 Tel: 1 919 254 4436 921 E-mail: remoore@us.ibm.com 923 10. Full Copyright Statement 925 Copyright (C) The Internet Society (1998). All Rights Reserved. 927 This document and translations of it may be copied and furnished to 928 others, and derivative works that comment on or otherwise explain it or 929 assist in its implementation may be prepared, copied, published and 930 distributed, in whole or in part, without restriction of any kind, 931 provided that the above copyright notice and this paragraph are included 932 on all such copies and derivative works. However, this document itself 933 may not be modified in any way, such as by removing the copyright notice 934 or references to the Internet Society or other Internet organizations, 935 except as needed for the purpose of developing Internet standards in 936 which case the procedures for copyrights defined in the Internet 937 Standards process must be followed, or as required to translate it into 938 languages other than English. 940 The limited permissions granted above are perpetual and will not be 941 revoked by the Internet Society or its successors or assigns. 943 This document and the information contained herein is provided on an "AS 944 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK 945 FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT 946 LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT 947 INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR 948 FITNESS FOR A PARTICULAR PURPOSE. 950 11. Table of Contents 952 1. Introduction ........................................... 2 953 2. The SNMPv2 Network Management Framework ................ 2 954 3. Overview ............................................... 3 955 3.1 HPR/IP Values for Objects in the APPN MIB ............. 4 956 3.2 APPN/HPR in IP Networks MIB structure ................. 5 957 3.2.1 hprIpMonitoringGroup ................................ 5 958 3.2.2 hprIpConfigurationGroup ............................. 5 959 4. Definitions ............................................ 7 960 5. Security Considerations ................................ 19 961 6. Intellectual Property .................................. 20 962 7. Acknowledgments ........................................ 20 963 8. References ............................................. 20 964 9. Author's Addresses ..................................... 23 965 10. Full Copyright Statement ............................... 23