idnits 2.17.1 draft-ietf-snanau-hprmib-01.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-24) according to https://trustee.ietf.org/license-info : IETF Trust Legal Provisions of 28-dec-2009, Section 6.a: This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 2: Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved. IETF Trust Legal Provisions of 28-dec-2009, Section 6.b(i), paragraph 3: This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing document type: Expected "INTERNET-DRAFT" in the upper left hand corner of the first page ** Missing expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Abstract section. ** The document seems to lack a Security Considerations section. ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 50 instances of too long lines in the document, the longest one being 2 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 704 has weird spacing: '... -- ok err p...' == Line 706 has weird spacing: '... -- ok op p...' == Line 707 has weird spacing: '... bad op path ...' -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (March 31, 1997) is 9886 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) ** Obsolete normative reference: RFC 1902 (ref. '1') (Obsoleted by RFC 2578) ** Obsolete normative reference: RFC 1903 (ref. '2') (Obsoleted by RFC 2579) ** Obsolete normative reference: RFC 1904 (ref. '3') (Obsoleted by RFC 2580) -- Possible downref: Non-RFC (?) normative reference: ref. '4' -- Possible downref: Non-RFC (?) normative reference: ref. '5' -- Possible downref: Non-RFC (?) normative reference: ref. '6' Summary: 15 errors (**), 0 flaws (~~), 4 warnings (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Definitions of Managed Objects 3 for HPR 5 March 31, 1997 7 Bob Clouston (editor) 8 Cisco Systems 9 clouston@cisco.com 11 Bob Moore (editor) 12 IBM Corporation 13 remoore@ralvm6.vnet.ibm.com 15 17 1. 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 work 28 in progress. 30 To learn the current status of any Internet-Draft, please check the 31 1id-abstracts.txt listing contained in the Internet-Drafts Shadow 32 Directories on ds.internic.net, nic.nordu.net, ftp.isi.edu, or 33 munnari.oz.au. 35 2. Introduction 37 This memo defines a portion of the Management Information Base (MIB) for 38 use with network management protocols in the Internet community. In 39 particular, it defines objects for monitoring and controlling network 40 devices with HPR (High Performance Routing) capabilities. This memo 41 identifies managed objects for the HPR protocol. 43 This memo does not specify a standard for the Internet community. 45 3. The SNMP Network Management Framework 47 The SNMP Network Management Framework consists of several components. 48 For the purpose of this specification, the applicable components of the 49 Framework are the SMI and related documents [1, 2, 3], which define the 50 mechanisms used for describing and naming objects for the purpose of 51 management. 53 The Framework permits new objects to be defined for the purpose of 54 experimentation and evaluation. 56 4. Overview 58 This document identifies objects for monitoring the configuration and 59 active characteristics of devices with HPR capabilities. HPR is an 60 enhancement to the Advanced Peer-to-Peer Network (APPN) architecture 61 that provides fast data routing and improved session reliability. APPN 62 is one of the protocols that can use the HPR transport mechanism. See 63 the SNANAU APPN MIB [4] for management of APPN and APPN use of the HPR 64 transport. 66 The HPR terms and overall architecture [5] are available at 67 http://www.networking.ibm.com/app/aiwdoc/aiwsrc.htm. 69 Automatic Network Routing (ANR) is a fast low-level routing technique. 70 Each node assigns a unique (within that node) ANR label for each out- 71 bound link as it is activated. The label size is defined by the ANR 72 node, and nodes only need to know how to interpret their own labels. 73 The ANR string is a group of ANR labels encoded in a header in front of 74 the message being sent. At each hop the node strips off its own ANR 75 label and forwards the message onto the link with that label. The last 76 label in the string is the Network Connection Endpoint (NCE), which 77 identifies the component within the destination node that is to receive 78 the message. 80 Rapid Transport Protocol (RTP) is an end-to-end full duplex transport 81 connection (pipe). It provides for high-speed transport of data using 82 ANR. RTP is connection-oriented, and delivers data in correct order 83 reliably. Error recovery is done efficiently with selective 84 retransmission of data. An RTP path can be switched without disrupting 85 the sessions using it. An RTP path switch may be done automatically if 86 a link in the path fails and another RTP path is available, or on demand 87 to attempt to restore the optimal path. 89 RTP performs flow/congestion control with the Adaptive Rate-Based (ARB) 90 algorithm, described in [5]. ARB is done only at the endpoints of the 91 RTP pipe, so intermediate hops are not involved. ARB regulates the flow 92 of data over an RTP connection by adaptively changing the sender's rate 93 based on feedback on the receiver's rate. It is designed to prevent 94 congestion rather than react to it. 96 In this document, we describe HPR managed objects. 98 Highlights of the management functions supported by the HPR MIB module 99 include the following: 101 o Identifying network connection endpoints (NCEs). 103 o Identifying how incoming packets are routed based on ANR labels. 105 o Monitoring the RTP connections between nodes. Tower. 107 o Ability to trigger an RTP path switch. The MIB only supports a 108 path switch with no specified path. Some implementations may have 109 a product-specific option to specify a new path. The 110 hprOperatorPathSwitchSupport object identifies this support. 112 o Historical information about RTP path switch attempts 114 This MIB module does not support: 116 o Configuration of HPR nodes. 118 o Protocol-specific uses of HPR (such as APPN) 120 o Traps. The APPN MIB contains a trap for Alert conditions that may 121 affect HPR resources. The value for the affectedObject object 122 contained in the alertTrap is determined by the implementation. It 123 may contain a VariablePointer from the HPR MIB. The APPN/HPR 124 Alerts are defined in [6]. 126 4.1. HPR MIB Structure 128 Although HPR is an extension to APPN, the HPR MIB relies very little 129 upon the APPN MIB. The appnNodeCounterDisconTime object in the APPN MIB 130 is used to detect discontinuities in HPR MIB counters. The 131 hprNodeCpName object in this MIB has the same value as the 132 appnNodeCpName object in the APPN MIB. 134 The HPR MIB module contains the following collections of objects: 136 o hprGlobal - general HPR objects. 138 o hprAnrRouting - objects related to the ANR routing table. 140 o hprTransportUser - objects related to users of the HPR transport. 142 o hprRtp - objects related to the HPR Transport Tower. 144 These are described below in more detail. 146 4.1.1. hprGlobal group 148 The hprGlobal group consists of general objects such as the APPN CP 149 (control point) name of the HPR node and the level of support for 150 operator-requested path switches. 152 4.1.2. hprAnrRouting group 154 The hprAnrRouting group consists objects to monitor and control the 155 counting of ANR packets received and the following table: 157 The hprAnrRoutingTable correlates incoming ANR labels to the outbound 158 transmission group (TG) or local NCE to which incoming packet will be 159 forwarded. An entry defines the label type as identifying a local NCE 160 or a TG, identifies the NCE or TG, and counts the number of packets 161 received with the entry's ANR label. 163 4.1.3. hprTransportUser group 165 The hprTransportUser group consists of the following table: 167 The hprNceTable identifies network connection endpoints and their 168 function types. The function type can be any combination of a CP, 169 logical unit (LU), boundary function, and route setup. 171 4.1.4. hprRtp group 173 The hprRtp group consists of the following objects and tables: 175 1) hprRtpGlobe 177 These objects contain information about the number of RTP connection 178 setups, and control of RTP counters. 180 2) hprRtpTable 182 This table contains one entry for each RTP connection. The information 183 includes local and remote NCE IDs and TCIDs (transport connection 184 identifiers), timers, send rates, and statistics. A path switch can be 185 triggered by the hprRptPathSwitchTrigger object if the agent node 186 supports it; however, a new path cannot be specified. 188 3) hprRtpStatusTable 190 This table contains statistics and historical information for RTP path 191 switches attempts, including old and new ANR strings and Route Selection 192 Control Vectors (RSCVs), why the path switch was initiated, and the 193 result (successful or reason for failure). 195 5. Definitions 197 HPR-MIB DEFINITIONS ::= BEGIN 199 IMPORTS 200 DisplayString, DateAndTime, TimeStamp, TEXTUAL-CONVENTION 201 FROM SNMPv2-TC 203 Counter32, Gauge32, Unsigned32, TimeTicks, BITS, 204 OBJECT-TYPE, MODULE-IDENTITY 205 FROM SNMPv2-SMI 207 MODULE-COMPLIANCE, OBJECT-GROUP 208 FROM SNMPv2-CONF 210 snanauMIB 211 FROM SNA-NAU-MIB 213 SnaControlPointName 214 FROM APPN-MIB; 216 hprMIB MODULE-IDENTITY 217 LAST-UPDATED "970331000000Z" 218 ORGANIZATION "AIW APPN / HPR MIB SIG" 219 CONTACT-INFO 221 " 223 Bob Clouston 224 Cisco Systems 225 7025 Kit Creek Road 226 P.O. Box 14987 227 Research Triangle Park, NC 27709, USA 228 Tel: 1 919 472 2333 229 E-mail: clouston@cisco.com 231 Bob Moore 232 IBM Corporation 233 800 Park Offices Drive 234 RHJA/664 235 P.O. Box 12195 236 Research Triangle Park, NC 27709, USA 237 Tel: 1 919 254 4436 238 E-mail: remoore@ralvm6.vnet.ibm.com 239 " 240 DESCRIPTION 241 "This is the MIB module for objects used to 242 manage network devices with HPR capabilities." 243 ::= { snanauMIB 6 } 244 -- snanauMIB ::= { mib-2 34 } 246 -- ********************************************************************* 247 -- Textual Conventions 248 -- ********************************************************************* 249 -- SnaControlPointName is imported from the APPN MIB 251 HprNceTypes ::= TEXTUAL-CONVENTION 252 STATUS current 253 DESCRIPTION 254 "A bit string identifying the set of functions provided by a 255 network connection endpoint (NCE)." 257 SYNTAX BITS { controlPoint(0), 258 logicalUnit(1), 259 boundaryFunction(2), 260 routeSetup(3) } 262 HprRtpCounter ::= TEXTUAL-CONVENTION 263 STATUS current 264 DESCRIPTION 265 "An object providing statistics for an RTP connection. A 266 Management Station can detect discontinuities in this counter 267 by monitoring the correspondingly indexed 268 hprRtpCounterDisconTime object." 270 SYNTAX Counter32 272 -- ********************************************************************* 273 hprObjects OBJECT IDENTIFIER ::= { hprMIB 1 } 274 -- ********************************************************************* 276 -- ********************************************************************* 277 hprGlobal OBJECT IDENTIFIER ::= { hprObjects 1 } 278 -- ********************************************************************** 279 -- The hprGlobal group applies to both intermediate and end nodes. 280 -- ********************************************************************** 282 hprNodeCpName OBJECT-TYPE 283 SYNTAX SnaControlPointName 284 MAX-ACCESS read-only 285 STATUS current 286 DESCRIPTION 287 "Administratively assigned network name for the APPN node where 288 this HPR implementation resides. If this object has the same 289 value as the appnNodeCpName object in the APPN MIB, then the 290 two objects are referring to the same APPN node." 292 ::= { hprGlobal 1 } 294 hprOperatorPathSwitchSupport OBJECT-TYPE 295 SYNTAX INTEGER { 296 notSupported(1), 297 switchTriggerSupported(2), 298 switchToPathSupported(3) 299 } 300 MAX-ACCESS read-only 301 STATUS current 302 DESCRIPTION 303 "This object indicates an implementation's level of support for 304 an operator-requested path switch. 306 notSupported(1) - the agent does not support 307 operator-requested path switches 308 switchTriggerSupported(2) - the agent supports a 'switch 309 path now' command from an 310 operator, but not a command to 311 switch to a specified path 312 switchToPathSupported(3) - the agent supports both a 313 'switch path now' command and a 314 command to switch to a specified 315 path. Note that the latter 316 command is not available via this 317 MIB; a system that supports it 318 must do so via other means, such 319 as a local operator interface." 321 ::= { hprGlobal 2 } 323 -- ********************************************************************** 324 hprAnrRouting OBJECT IDENTIFIER ::= { hprObjects 2 } 325 -- ********************************************************************** 327 hprAnrsAssigned OBJECT-TYPE 328 SYNTAX Counter32 329 UNITS "ANR labels" 330 MAX-ACCESS read-only 331 STATUS current 332 DESCRIPTION 333 "The count of ANR labels assigned by this node since it was 334 last re-initialized. A Management Station can detect 335 discontinuities in this counter by monitoring the 336 appnNodeCounterDisconTime object in the APPN MIB." 338 ::= { hprAnrRouting 1 } 340 hprAnrCounterState OBJECT-TYPE 341 SYNTAX INTEGER { 342 notActive(1), 343 active(2) 344 } 345 MAX-ACCESS read-write 346 STATUS current 347 DESCRIPTION 348 "This object is used for a network management station to turn 349 on/off the counting of ANR packets in the hprAnrRoutingTable. 350 The initial value of this object is an implementation choice. 352 notActive(1) - the counter hprAnrPacketsReceived 353 returns no meaningful value 354 active(2) - the counter hprAnrPacketsReceived is 355 being incremented and is returning 356 meaningful values" 358 ::= { hprAnrRouting 2 } 360 hprAnrCounterStateTime OBJECT-TYPE 361 SYNTAX DateAndTime 362 MAX-ACCESS read-only 363 STATUS current 364 DESCRIPTION 365 "The time when the hprAnrCounterState object last changed its 366 value. The initial value returned by this object is the time 367 at which the APPN node instrumented with this MIB was last 368 brought up." 370 ::= { hprAnrRouting 3 } 372 hprAnrRoutingTable OBJECT-TYPE 373 SYNTAX SEQUENCE OF HprAnrRoutingEntry 374 MAX-ACCESS not-accessible 375 STATUS current 376 DESCRIPTION 377 "The ANR Routing table provides a means of correlating an 378 incoming ANR label (i.e., one assigned by this node) with the 379 TG over which a packet containing the label will be forwarded. 380 When the ANR label identifies a local NCE, the hprAnrOutTgDest 381 and hprAnrOutTgNum objects have no meaning. The table also 382 contains an object to count the number of packets received with 383 a given ANR label." 385 ::= { hprAnrRouting 4 } 387 hprAnrRoutingEntry OBJECT-TYPE 388 SYNTAX HprAnrRoutingEntry 389 MAX-ACCESS not-accessible 390 STATUS current 391 DESCRIPTION 392 "The ANR label is used to index this table." 394 INDEX { hprAnrLabel } 396 ::= { hprAnrRoutingTable 1 } 398 HprAnrRoutingEntry ::= SEQUENCE { 399 hprAnrLabel OCTET STRING, 400 hprAnrType INTEGER, 401 hprAnrOutTgDest DisplayString, 402 hprAnrOutTgNum INTEGER, 403 hprAnrPacketsReceived Counter32, 404 hprAnrCounterDisconTime TimeStamp 405 } 407 hprAnrLabel OBJECT-TYPE 408 SYNTAX OCTET STRING (SIZE (1..8)) 409 MAX-ACCESS not-accessible 410 STATUS current 411 DESCRIPTION 412 "The first ANR label in an incoming packet." 414 ::= { hprAnrRoutingEntry 1 } 416 hprAnrType OBJECT-TYPE 417 SYNTAX INTEGER { 418 nce(1), 419 tg(2) 420 } 421 MAX-ACCESS read-only 422 STATUS current 423 DESCRIPTION 424 "An object indicating whether an ANR label assigned by this 425 node identifies a local NCE or a TG on which outgoing packets 426 are forwarded. 428 nce(1) - the ANR label identifies a local NCE. In this 429 case the hprAnrOutTgDest and hprAnrOutTgNum 430 objects have no meaning. 431 tg(2) - the ANR label identifies a TG." 433 ::= { hprAnrRoutingEntry 2 } 435 hprAnrOutTgDest OBJECT-TYPE 436 SYNTAX DisplayString (SIZE (0 | 3..17)) 437 MAX-ACCESS read-only 438 STATUS current 439 DESCRIPTION 440 "Destination node for the TG over which packets with this ANR 441 label are forwarded. This is the fully qualified name of an 442 APPN network node or end node, formatted according to the 443 SnaControlPointName textual convention. If the ANR label 444 identifies a local NCE, then this object returns a zero-length 445 string. 447 This object corresponds to the appnLocalTgDest object in the 448 APPN MIB." 450 ::= { hprAnrRoutingEntry 3 } 452 hprAnrOutTgNum OBJECT-TYPE 453 SYNTAX INTEGER (0..255) 454 MAX-ACCESS read-only 455 STATUS current 456 DESCRIPTION 457 "Number of the TG over which packets with this ANR label are 458 forwarded. If the ANR label identifies a local NCE, then this 459 object returns the value 0, since 0 is not a valid TG number 460 for a TG that supports HPR. 462 This object corresponds to the appnLocalTgNum object in the 463 APPN MIB." 465 ::= { hprAnrRoutingEntry 4 } 467 hprAnrPacketsReceived OBJECT-TYPE 468 SYNTAX Counter32 469 UNITS "ANR packets" 470 MAX-ACCESS read-only 471 STATUS current 472 DESCRIPTION 473 "The count of packets received with this ANR label as their 474 first label. 476 A Management Station can detect discontinuities in this counter 477 by monitoring the hprAnrCounterDisconTime object in the same 478 row." 480 ::= { hprAnrRoutingEntry 5 } 482 hprAnrCounterDisconTime OBJECT-TYPE 483 SYNTAX TimeStamp 484 MAX-ACCESS read-only 485 STATUS current 486 DESCRIPTION 487 "The value of the sysUpTime object when the 488 hprAnrPacketsReceived counter for this ANR label last 489 experienced a discontinuity. This will be the more recent of 490 two times: the time at which the ANR label was associated with 491 either an outgoing TG or a local NCE, or the time at which the 492 ANR counters were last turned on or off." 494 ::= { hprAnrRoutingEntry 6 } 496 -- ********************************************************************** 497 hprTransportUser OBJECT IDENTIFIER ::= { hprObjects 3 } 498 -- ********************************************************************** 499 -- Transport Service User (TU) Table: (RTP Connection Users) 500 -- 501 -- There will be several users of the HPR transport and each HPR node 502 -- shall maintain a table of these users. 503 -- ********************************************************************** 505 hprNceTable OBJECT-TYPE 506 SYNTAX SEQUENCE OF HprNceEntry 507 MAX-ACCESS not-accessible 508 STATUS current 509 DESCRIPTION 510 "The Network Connection Endpoint (NCE) table." 512 ::= { hprTransportUser 1 } 514 hprNceEntry OBJECT-TYPE 515 SYNTAX HprNceEntry 516 MAX-ACCESS not-accessible 517 STATUS current 518 DESCRIPTION 519 "The NCE ID is used to index this table." 521 INDEX { hprNceId } 523 ::= { hprNceTable 1 } 525 HprNceEntry ::= SEQUENCE { 526 hprNceId OCTET STRING, 527 hprNceType HprNceTypes, 528 hprNceDefault HprNceTypes, 529 hprNceInstanceId OCTET STRING 530 } 532 hprNceId OBJECT-TYPE 533 SYNTAX OCTET STRING (SIZE (1..8)) 534 MAX-ACCESS not-accessible 535 STATUS current 536 DESCRIPTION 537 "The Network Connection Endpoint (NCE) id. NCEs identify 538 Control Points (Cp), Logical Units (Lu), HPR Boundary Functions 539 (Bf) and Route Setup (Rs) Functions. A value for this object 540 can be retrieved from any of several *NceId objects in the APPN 541 MIB; in each case this value identifies a row in this table 542 containing information related to that in the APPN MIB." 544 ::= { hprNceEntry 1 } 546 hprNceType OBJECT-TYPE 547 SYNTAX HprNceTypes 548 MAX-ACCESS read-only 549 STATUS current 550 DESCRIPTION 551 "A bit string identifying the function types provided by this 552 Network Connection Endpoint (NCE)." 554 ::= { hprNceEntry 2 } 556 hprNceDefault OBJECT-TYPE 557 SYNTAX HprNceTypes 558 MAX-ACCESS read-only 559 STATUS current 560 DESCRIPTION 561 "A bit string identifying the function types for which this 562 Network Connection Endpoint (NCE) is the default NCE. While 563 default NCEs are not explicitly defined in the architecture, 564 some implementations provide them; for such implementations, it 565 is useful to make this information available to a Management 566 Station." 568 ::= { hprNceEntry 3 } 570 hprNceInstanceId OBJECT-TYPE 571 SYNTAX OCTET STRING (SIZE (4)) 572 MAX-ACCESS read-only 573 STATUS current 574 DESCRIPTION 575 "The NCE instance identifier (NCEII) identifying the current 576 instance of this NCE." 578 ::= { hprNceEntry 4 } 580 -- ********************************************************************** 581 hprRtp OBJECT IDENTIFIER ::= { hprObjects 4 } 582 -- ********************************************************************** 583 -- ********************************************************************** 584 -- 585 -- The RTP group is implemented by all managed nodes supporting the 586 -- HPR Transport Tower. The group contains several scalars (simple 587 -- objects) and a table. 588 -- ********************************************************************** 590 -- ********************************************************************** 591 hprRtpGlobe OBJECT IDENTIFIER ::= { hprRtp 1} 592 -- ********************************************************************** 593 hprRtpGlobeConnSetups OBJECT-TYPE 594 SYNTAX Counter32 595 UNITS "RTP connection setups" 596 MAX-ACCESS read-only 597 STATUS current 598 DESCRIPTION 599 "The count of RTP connection setups in which this node has 600 participated, as either sender or receiver, since it was last 601 re-initialized. Retries of a setup attempt do not cause the 602 counter to be incremented. 604 A Management Station can detect discontinuities in this counter 605 by monitoring the appnNodeCounterDisconTime object in the APPN 606 MIB." 608 ::= { hprRtpGlobe 1 } 610 hprRtpGlobeCtrState OBJECT-TYPE 611 SYNTAX INTEGER { 612 notActive(1), 613 active(2) 614 } 615 MAX-ACCESS read-write 616 STATUS current 617 DESCRIPTION 618 "This object allows a network management station to turn the 619 counters in the hprRtpTable on and off. The initial value of 620 this object is an implementation choice. 622 notActive(1) - the counters in the hprRtpTable are 623 returning no meaningful values 624 active(2) - the counters in the hprRtpTable are 625 being incremented and are returning 626 meaningful values" 628 ::= { hprRtpGlobe 2 } 630 hprRtpGlobeCtrStateTime OBJECT-TYPE 631 SYNTAX DateAndTime 632 MAX-ACCESS read-only 633 STATUS current 634 DESCRIPTION 635 "The time when the value of the hprRtpGlobeCtrState object last 636 changed." 638 ::= { hprRtpGlobe 3 } 640 -- ********************************************************************** 641 -- The RTP Connection Table 642 -- There may be many RTP connections on a node supporting the functions 643 -- specified in the RTP option set. Each node implementing this option 644 -- set shall maintain a table of these RTP connections. 645 -- ********************************************************************** 647 hprRtpTable OBJECT-TYPE 648 SYNTAX SEQUENCE OF HprRtpEntry 649 MAX-ACCESS not-accessible 650 STATUS current 651 DESCRIPTION 652 "The RTP Connection table" 654 ::= { hprRtp 2 } 656 hprRtpEntry OBJECT-TYPE 657 SYNTAX HprRtpEntry 658 MAX-ACCESS not-accessible 659 STATUS current 660 DESCRIPTION 661 "The local NCE ID and local TCID are used to index this table." 663 INDEX 664 { hprRtpLocNceId, 665 hprRtpLocTcid } 667 ::= { hprRtpTable 1 } 669 HprRtpEntry ::= SEQUENCE { 670 hprRtpLocNceId OCTET STRING, -- local nce id 671 hprRtpLocTcid OCTET STRING, -- local tcid 672 hprRtpRemCpName SnaControlPointName,-- remote cp name 673 hprRtpRemNceId OCTET STRING, -- remote nce id 674 hprRtpRemTcid OCTET STRING, -- remote tcid 675 hprRtpPathSwitchTrigger INTEGER, -- trigger (read-write) 676 hprRtpRscv OCTET STRING, -- rscv 677 hprRtpTopic DisplayString, -- topic (cos) 678 hprRtpState INTEGER, -- state 679 hprRtpUpTime TimeTicks, -- up time 681 hprRtpLivenessTimer Unsigned32, -- liveness timer 682 hprRtpShortReqTimer Unsigned32, -- short request timer 683 hprRtpPathSwTimer Unsigned32, -- path switch timer 685 hprRtpLivenessTimeouts HprRtpCounter, -- liveness timeouts 686 hprRtpShortReqTimeouts HprRtpCounter, -- short req timeouts 688 hprRtpMaxSendRate Gauge32, -- maximum send rate 689 hprRtpMinSendRate Gauge32, -- minimum send rate 690 hprRtpCurSendRate Gauge32, -- current send rate 692 hprRtpSmRdTripDelay Gauge32, -- smooth rnd trip delay 694 hprRtpSendPackets HprRtpCounter, -- packets sent 695 hprRtpRecvPackets HprRtpCounter, -- packets received 696 hprRtpSendBytes HprRtpCounter, -- bytes sent 697 hprRtpRecvBytes HprRtpCounter, -- bytes received 699 hprRtpRetrPackets HprRtpCounter, -- pkts re-xmitted 700 hprRtpPacketsDiscarded HprRtpCounter, -- pkts discarded 701 hprRtpDetectGaps HprRtpCounter, -- gaps detected 702 hprRtpRateReqSends HprRtpCounter, -- rate req send 704 hprRtpOkErrPathSws HprRtpCounter, -- ok err path sws 705 hprRtpBadErrPathSws HprRtpCounter, -- bad err path sws 706 hprRtpOkOpPathSws HprRtpCounter, -- ok op path sws 707 hprRtpBadOpPathSws HprRtpCounter, -- bad op path sws 709 hprRtpCounterDisconTime TimeStamp -- discontinuity ind 710 } 712 hprRtpLocNceId OBJECT-TYPE 713 SYNTAX OCTET STRING (SIZE (1..8)) 714 MAX-ACCESS not-accessible 715 STATUS current 716 DESCRIPTION 717 "The local Network Connection Endpoint (NCE) ID of this RTP 718 connection. NCEs identify CPs, LUs, Boundary Functions (BFs), 719 and Route Setup (RS) components. A value for this object can 720 be retrieved from any of several *NceId objects in the APPN 721 MIB; in each case this value identifies a row in this table 722 containing information related to that in the APPN MIB." 724 ::= { hprRtpEntry 1 } 726 hprRtpLocTcid OBJECT-TYPE 727 SYNTAX OCTET STRING (SIZE (8)) 728 MAX-ACCESS not-accessible 729 STATUS current 730 DESCRIPTION 731 "The local TCID of this RTP connection. A value for this 732 object can be retrieved from any of several *Tcid objects in 733 the APPN MIB; in each case this value identifies a row in this 734 table containing information related to that in the APPN MIB." 736 ::= { hprRtpEntry 2 } 738 hprRtpRemCpName OBJECT-TYPE 739 SYNTAX SnaControlPointName 740 MAX-ACCESS read-only 741 STATUS current 742 DESCRIPTION 743 "Administratively assigned network name for the remote node of 744 this RTP connection." 746 ::= { hprRtpEntry 3 } 748 hprRtpRemNceId OBJECT-TYPE 749 SYNTAX OCTET STRING (SIZE (1..8)) 750 MAX-ACCESS read-only 751 STATUS current 752 DESCRIPTION 753 "The remote Network Connection Endpoint (NCE) of this RTP 754 connection. NCEs identify CPs, LUs, Boundary Functions (BFs), 755 and Route Setup (RS) components." 757 ::= { hprRtpEntry 4 } 759 hprRtpRemTcid OBJECT-TYPE 760 SYNTAX OCTET STRING (SIZE (8)) 761 MAX-ACCESS read-only 762 STATUS current 763 DESCRIPTION 764 "The remote TCID of this RTP connection." 766 ::= { hprRtpEntry 5 } 768 hprRtpPathSwitchTrigger OBJECT-TYPE 769 SYNTAX INTEGER { 770 ready(1), 771 switchPathNow(2) 772 } 773 MAX-ACCESS read-write 774 STATUS current 775 DESCRIPTION 776 "Object by which a Management Station can trigger an operator- 777 requested path switch, by setting the value to 778 switchPathNow(2). Setting this object to switchPathNow(2) 779 triggers a path switch even if its previous value was already 780 switchPathNow(2). 782 The value ready(1) is returned on GET operations until a SET 783 has been processed; after that the value received on the most 784 recent SET is returned. 786 This MIB module provides no support for an operator-requested 787 switch to a specified path." 789 ::= { hprRtpEntry 6 } 791 hprRtpRscv OBJECT-TYPE 792 SYNTAX OCTET STRING (SIZE (0..255)) 793 MAX-ACCESS read-only 794 STATUS current 795 DESCRIPTION 796 "The forward Route Selection Control Vector for this RTP 797 connection. The format of this vector is described in SNA 798 Formats. 800 The value returned in this object during a path switch is 801 implementation-dependent: it may be the old path, the new 802 path, a zero-length string, or some other valid RSCV string." 804 ::= { hprRtpEntry 7 } 806 hprRtpTopic OBJECT-TYPE 807 SYNTAX DisplayString (SIZE(8)) 808 MAX-ACCESS read-only 809 STATUS current 810 DESCRIPTION 811 "The topic for this RTP connection. This is used to indicate 812 the Class of Service." 814 ::= { hprRtpEntry 8 } 816 hprRtpState OBJECT-TYPE 817 SYNTAX INTEGER { 818 rtpListening(1), 819 rtpCalling(2), 820 rtpConnected(3), 821 rtpPathSwitching(4), 822 rtpDisconnecting(5), 823 other(99) 824 } 825 MAX-ACCESS read-only 826 STATUS current 827 DESCRIPTION 828 "The state of the RTP connection, from the perspective of the 829 local RTP protocol machine: 831 rtpListening - connection open; waiting for other end 832 to call in 833 rtpCalling - connection opened, attempting to call 834 out, have not yet received any data 835 from other end 836 rtpConnected - connection is active; responded to a 837 call-in or received other end's TCID 838 from a call-out attempt 839 rtpPathSwitching - the path switch timer is running; 840 attempting to find a new path for this 841 connection. 842 rtpDisconnecting - no sessions are using this connection; 843 in process of bringing it down 844 other - the connection is not in any of the 845 states listed above." 847 ::= { hprRtpEntry 9 } 849 hprRtpUpTime OBJECT-TYPE 850 SYNTAX TimeTicks 851 MAX-ACCESS read-only 852 STATUS current 853 DESCRIPTION 854 "The length of time the RTP connection has been up, measured in 855 1/100ths of a second." 857 ::= { hprRtpEntry 10 } 859 hprRtpLivenessTimer OBJECT-TYPE 860 SYNTAX Unsigned32 861 UNITS "1/100ths of a second" 862 MAX-ACCESS read-only 863 STATUS current 864 DESCRIPTION 865 "The value of the liveness (ALIVE) timer of this RTP 866 connection, in units of 1/100th of a second. When this timer 867 expires and no packet has arrived from the partner since it was 868 last set, packets with Status Request indicators will be sent 869 to see if the RTP connection is still alive." 871 ::= { hprRtpEntry 11 } 873 hprRtpShortReqTimer OBJECT-TYPE 874 SYNTAX Unsigned32 875 UNITS "1/100ths of a second" 876 MAX-ACCESS read-only 877 STATUS current 878 DESCRIPTION 879 "The value of the RTP SHORT_REQ timer, in units of 1/100 of a 880 second. This timer represents the maximum time that a sender 881 waits for a reply from a receiver." 883 ::= { hprRtpEntry 12 } 885 hprRtpPathSwTimer OBJECT-TYPE 886 SYNTAX Unsigned32 887 UNITS "1/100ths of a second" 888 MAX-ACCESS read-only 889 STATUS current 890 DESCRIPTION 891 "The length of time that RTP should attempt a path switch for a 892 connection, in units of 1/100th of a second." 894 ::= { hprRtpEntry 13 } 896 hprRtpLivenessTimeouts OBJECT-TYPE 897 SYNTAX HprRtpCounter 898 UNITS "liveness timeouts" 899 MAX-ACCESS read-only 900 STATUS current 901 DESCRIPTION 902 "The count of liveness timeouts for this RTP connection." 904 ::= { hprRtpEntry 14 } 906 hprRtpShortReqTimeouts OBJECT-TYPE 907 SYNTAX HprRtpCounter 908 UNITS "short request timeouts" 909 MAX-ACCESS read-only 910 STATUS current 911 DESCRIPTION 912 "The count of short request timeouts for this RTP connection." 914 ::= { hprRtpEntry 15 } 916 hprRtpMaxSendRate OBJECT-TYPE 917 SYNTAX Gauge32 918 UNITS "bytes per second" 919 MAX-ACCESS read-only 920 STATUS current 921 DESCRIPTION 922 "The high-water mark for this RTP connection's send rate, in 923 units of bytes per second. This is the high-water mark for the 924 entire life of the connection, not just the high-water mark for 925 the connection's current path. 927 For more details on this and other parameters related to HPR, 928 see the High Performance Routing Architecture Reference." 930 ::= { hprRtpEntry 16 } 932 hprRtpMinSendRate OBJECT-TYPE 933 SYNTAX Gauge32 934 UNITS "bytes per second" 935 MAX-ACCESS read-only 936 STATUS current 937 DESCRIPTION 938 "The low-water mark for this RTP connection's send rate, in 939 units of bytes per second. This is the low-water mark for the 940 entire life of the connection, not just the low-water mark for 941 the connection's current path. 943 For more details on this and other parameters related to HPR, 944 see the High Performance Routing Architecture Reference." 946 ::= { hprRtpEntry 17 } 948 hprRtpCurSendRate OBJECT-TYPE 949 SYNTAX Gauge32 950 UNITS "bytes per second" 951 MAX-ACCESS read-only 952 STATUS current 953 DESCRIPTION 954 "The current send rate for this RTP connection, in units of 955 bytes per second. 957 For more details on this and other parameters related to HPR, 958 see the High Performance Routing Architecture Reference." 960 ::= { hprRtpEntry 18 } 962 hprRtpSmRdTripDelay OBJECT-TYPE 963 SYNTAX Gauge32 964 UNITS "1/1000ths of a second" 965 MAX-ACCESS read-only 966 STATUS current 967 DESCRIPTION 968 "The smoothed round trip delay for this RTP connection, in 969 units of 1/1000th of a second (ms). 971 For more details on this and other parameters related to HPR, 972 see the High Performance Routing Architecture Reference." 974 ::= { hprRtpEntry 19 } 976 hprRtpSendPackets OBJECT-TYPE 977 SYNTAX HprRtpCounter 978 UNITS "RTP packets" 979 MAX-ACCESS read-only 980 STATUS current 981 DESCRIPTION 982 "The count of packets successfully sent on this RTP 983 connection." 985 ::= { hprRtpEntry 20 } 987 hprRtpRecvPackets OBJECT-TYPE 988 SYNTAX HprRtpCounter 989 UNITS "RTP packets" 990 MAX-ACCESS read-only 991 STATUS current 992 DESCRIPTION 993 "The count of packets received on this RTP connection. The 994 counter is incremented only once if duplicate copies of a 995 packet are received." 997 ::= { hprRtpEntry 21 } 999 hprRtpSendBytes OBJECT-TYPE 1000 SYNTAX HprRtpCounter 1001 UNITS "bytes" 1002 MAX-ACCESS read-only 1003 STATUS current 1004 DESCRIPTION 1005 "The count of bytes sent on this RTP connection. Both RTP 1006 Transport Header (THDR) bytes and data bytes are included in 1007 this count." 1009 ::= { hprRtpEntry 22 } 1011 hprRtpRecvBytes OBJECT-TYPE 1012 SYNTAX HprRtpCounter 1013 UNITS "bytes" 1014 MAX-ACCESS read-only 1015 STATUS current 1016 DESCRIPTION 1017 "The count of bytes received on this RTP connection. Both RTP 1018 Transport Header (THDR) bytes and data bytes are included in 1019 this count." 1021 ::= { hprRtpEntry 23 } 1023 hprRtpRetrPackets OBJECT-TYPE 1024 SYNTAX HprRtpCounter 1025 UNITS "RTP packets" 1026 MAX-ACCESS read-only 1027 STATUS current 1028 DESCRIPTION 1029 "The count of packets retransmitted on this RTP connection." 1031 ::= { hprRtpEntry 24 } 1033 hprRtpPacketsDiscarded OBJECT-TYPE 1034 SYNTAX HprRtpCounter 1035 UNITS "RTP packets" 1036 MAX-ACCESS read-only 1037 STATUS current 1038 DESCRIPTION 1039 "The count of packets received on this RTP connection and then 1040 discarded. A packet may be discarded because it is determined 1041 to be a duplicate, or for other reasons." 1043 ::= { hprRtpEntry 25 } 1045 hprRtpDetectGaps OBJECT-TYPE 1046 SYNTAX HprRtpCounter 1047 UNITS "gaps" 1048 MAX-ACCESS read-only 1049 STATUS current 1050 DESCRIPTION 1051 "The count of gaps detected on this RTP connection." 1053 ::= { hprRtpEntry 26 } 1055 hprRtpRateReqSends OBJECT-TYPE 1056 SYNTAX HprRtpCounter 1057 UNITS "rate requests" 1058 MAX-ACCESS read-only 1059 STATUS current 1060 DESCRIPTION 1061 "The count of Rate Requests sent on this RTP connection." 1063 ::= { hprRtpEntry 27 } 1065 hprRtpOkErrPathSws OBJECT-TYPE 1066 SYNTAX HprRtpCounter 1067 UNITS "path switch attempts" 1068 MAX-ACCESS read-only 1069 STATUS current 1070 DESCRIPTION 1071 "The count of successful path switch attempts for this RTP 1072 connection due to errors." 1074 ::= { hprRtpEntry 28 } 1076 hprRtpBadErrPathSws OBJECT-TYPE 1077 SYNTAX HprRtpCounter 1078 UNITS "path switch attempts" 1079 MAX-ACCESS read-only 1080 STATUS current 1081 DESCRIPTION 1082 "The count of unsuccessful path switches for this RTP 1083 connection due to errors." 1085 ::= { hprRtpEntry 29 } 1087 hprRtpOkOpPathSws OBJECT-TYPE 1088 SYNTAX HprRtpCounter 1089 UNITS "path switches" 1090 MAX-ACCESS read-only 1091 STATUS current 1092 DESCRIPTION 1093 "The count of successful path switches for this RTP connection 1094 due to operator requests." 1096 ::= { hprRtpEntry 30 } 1098 hprRtpBadOpPathSws OBJECT-TYPE 1099 SYNTAX HprRtpCounter 1100 UNITS "path switches" 1101 MAX-ACCESS read-only 1102 STATUS current 1103 DESCRIPTION 1104 "The count of unsuccessful path switches for this RTP 1105 connection due to operator requests. This counter is not 1106 incremented by an implementation that does not support 1107 operator-requested path switches, even if a Management Station 1108 requests such a path switch by setting the 1109 hprRtpPathSwitchTrigger object." 1111 ::= { hprRtpEntry 31 } 1113 hprRtpCounterDisconTime OBJECT-TYPE 1114 SYNTAX TimeStamp 1115 MAX-ACCESS read-only 1116 STATUS current 1117 DESCRIPTION 1118 "The value of the sysUpTime object when the counters for this 1119 RTP connection last experienced a discontinuity. This will be 1120 the more recent of two times: the time at which the connection 1121 was established or the time at which the HPR counters were last 1122 turned on or off." 1124 ::= { hprRtpEntry 32 } 1126 -- ********************************************************************** 1127 -- The RTP Connection Status Table 1128 -- This table contains statistics and historical information related to 1129 -- both successful and unsuccessful RTP path switches. This information 1130 -- can be important for both trend analysis and problem determination. 1131 -- 1132 -- Note the terminology here: when RTP is triggered to find a new path 1133 -- for a connection, this initiates a 'path switch,' which will end up 1134 -- being either successful or unsuccessful. During this path switch, 1135 -- RTP will make one or more 'path switch attempts,' which are attempts 1136 -- to find a new path for the connection and switch the connection to 1137 -- it. This 'new' path may be the same path that the connection was 1138 -- using before the path switch. 1139 -- 1140 -- It is an implementation option how many entries to keep in this 1141 -- table, and how long to retain any individual entry. 1142 -- ********************************************************************** 1143 hprRtpStatusTable OBJECT-TYPE 1144 SYNTAX SEQUENCE OF HprRtpStatusEntry 1145 MAX-ACCESS not-accessible 1146 STATUS current 1147 DESCRIPTION 1148 "RTP Connection Status Table: This table contains historical 1149 information on RTP connections. An entry is created in this 1150 table when a path switch is completed, either successfully or 1151 unsuccessfully." 1153 ::= { hprRtp 3 } 1155 hprRtpStatusEntry OBJECT-TYPE 1156 SYNTAX HprRtpStatusEntry 1157 MAX-ACCESS not-accessible 1158 STATUS current 1159 DESCRIPTION 1160 "This table is indexed by local NCE ID, local TCID, and an 1161 integer hprRtpStatusIndex. Thus the primary grouping of table 1162 rows is by RTP connection, with the multiple entries for a 1163 given RTP connection ordered by time." 1165 INDEX 1166 { hprRtpStatusLocNceId, 1167 hprRtpStatusLocTcid, 1168 hprRtpStatusIndex } 1170 ::= { hprRtpStatusTable 1 } 1172 HprRtpStatusEntry ::= SEQUENCE { 1173 hprRtpStatusLocNceId OCTET STRING, -- local nce id 1174 hprRtpStatusLocTcid OCTET STRING, -- local tcid 1175 hprRtpStatusIndex Unsigned32, -- index 1176 hprRtpStatusStartTime DateAndTime, -- time stamp 1177 hprRtpStatusEndTime DateAndTime, -- time stamp 1178 hprRtpStatusRemNceId OCTET STRING, -- remote nce id 1179 hprRtpStatusRemTcid OCTET STRING, -- remote tcid 1180 hprRtpStatusRemCpName SnaControlPointName,-- remote cp name 1181 hprRtpStatusNewRscv OCTET STRING, -- new rscv 1182 hprRtpStatusOldRscv OCTET STRING, -- old rscv 1183 hprRtpStatusCause INTEGER, -- cause 1184 hprRtpStatusLastAttemptResult INTEGER -- result of last 1185 } 1187 hprRtpStatusLocNceId OBJECT-TYPE 1188 SYNTAX OCTET STRING (SIZE (1..8)) 1189 MAX-ACCESS not-accessible 1190 STATUS current 1191 DESCRIPTION 1192 "The local Network Connection Endpoint (NCE) of this RTP 1193 connection. NCEs identify CPs, LUs, Boundary Functions (BFs), 1194 and Route Setup (RS) components." 1196 ::= { hprRtpStatusEntry 1 } 1198 hprRtpStatusLocTcid OBJECT-TYPE 1199 SYNTAX OCTET STRING (SIZE (8)) 1200 MAX-ACCESS not-accessible 1201 STATUS current 1202 DESCRIPTION 1203 "The local TCID of this RTP connection." 1205 ::= { hprRtpStatusEntry 2 } 1207 hprRtpStatusIndex OBJECT-TYPE 1208 SYNTAX Unsigned32 1209 MAX-ACCESS not-accessible 1210 STATUS current 1211 DESCRIPTION 1212 "Table index. This value begins at one and is incremented 1213 when a new entry is added to the table. It is an implementation 1214 choice whether to run a single counter for all entries in the 1215 table, or to run a separate counter for the entries for each 1216 RTP connection. In the unlikely event of a wrap, it is 1217 assumed that Management Stations will have the ability to 1218 order table entries correctly." 1220 ::= { hprRtpStatusEntry 3 } 1222 hprRtpStatusStartTime OBJECT-TYPE 1223 SYNTAX DateAndTime 1224 MAX-ACCESS read-only 1225 STATUS current 1226 DESCRIPTION 1227 "The time when the path switch began." 1229 ::= { hprRtpStatusEntry 4 } 1231 hprRtpStatusEndTime OBJECT-TYPE 1232 SYNTAX DateAndTime 1233 MAX-ACCESS read-only 1234 STATUS current 1235 DESCRIPTION 1236 "The time when the path switch was ended, either successfully 1237 or unsuccessfully." 1239 ::= { hprRtpStatusEntry 5 } 1241 hprRtpStatusRemCpName OBJECT-TYPE 1242 SYNTAX SnaControlPointName 1243 MAX-ACCESS read-only 1244 STATUS current 1245 DESCRIPTION 1246 "Administratively assigned network name for the remote node of 1247 this RTP connection." 1249 ::= { hprRtpStatusEntry 6 } 1251 hprRtpStatusRemNceId OBJECT-TYPE 1252 SYNTAX OCTET STRING (SIZE (1..8)) 1253 MAX-ACCESS read-only 1254 STATUS current 1255 DESCRIPTION 1256 "The remote Network Connection Endpoint (NCE) of this RTP 1257 connection. NCEs identify CPs, LUs, Boundary Functions (BFs), 1258 and Route Setup (RS) components." 1260 ::= { hprRtpStatusEntry 7 } 1262 hprRtpStatusRemTcid OBJECT-TYPE 1263 SYNTAX OCTET STRING (SIZE (8)) 1264 MAX-ACCESS read-only 1265 STATUS current 1266 DESCRIPTION 1267 "The remote TCID of this RTP connection." 1269 ::= { hprRtpStatusEntry 8 } 1271 hprRtpStatusNewRscv OBJECT-TYPE 1272 SYNTAX OCTET STRING (SIZE (0..255)) 1273 MAX-ACCESS read-only 1274 STATUS current 1275 DESCRIPTION 1276 "The new Route Selection Control Vector for this RTP 1277 connection. A zero-length string indicates that no value is 1278 available, perhaps because the implementation does not save 1279 RSCVs." 1281 ::= { hprRtpStatusEntry 9 } 1283 hprRtpStatusOldRscv OBJECT-TYPE 1284 SYNTAX OCTET STRING (SIZE (0..255)) 1285 MAX-ACCESS read-only 1286 STATUS current 1287 DESCRIPTION 1288 "The old Route Selection Control Vector for this RTP 1289 connection. A zero-length string indicates that no value is 1290 available, perhaps because the implementation does not save 1291 RSCVs." 1293 ::= { hprRtpStatusEntry 10 } 1295 hprRtpStatusCause OBJECT-TYPE 1296 SYNTAX INTEGER { 1297 other(1), 1298 rtpConnFail(2), 1299 locLinkFail(3), 1300 remLinkFail(4), 1301 operRequest(5) 1302 } 1303 MAX-ACCESS read-only 1304 STATUS current 1305 DESCRIPTION 1306 "The reason for the path switch: 1308 other(1) - Reason other than those listed below, 1309 rtpConnFail(2) - RTP connection failure detected, 1310 locLinkFail(3) - Local link failure, 1311 remLinkFail(4) - Remote link failure (learned from TDUs), 1312 operRequest(5) - Operator requested path switch. " 1314 ::= { hprRtpStatusEntry 11 } 1316 hprRtpStatusLastAttemptResult OBJECT-TYPE 1317 SYNTAX INTEGER { successful(1), 1318 initiatorMoving(2), 1319 directorySearchFailed(3), 1320 rscvCalculationFailed(4), 1321 negativeRouteSetupReply(5), 1322 backoutRouteSetupReply(6), 1323 timeoutDuringFirstAttempt(7), 1324 otherUnsuccessful(8) 1325 } 1326 MAX-ACCESS read-only 1327 STATUS current 1328 DESCRIPTION 1329 "The result of the last completed path switch attempt. If the 1330 path switch is aborted in the middle of a path switch attempt 1331 because the path switch timer expires, the result of the 1332 previous path switch attempt is reported. 1334 The values are defined as follows: 1336 successful(1) - The final path switch attempt 1337 was successful. 1338 initiatorMoving(2) - The final path switch attempt 1339 failed because the initiator 1340 is mobile, and there was no 1341 active link out of this node. 1342 directorySearchFailed(3) - The final path switch attempt 1343 failed because a directory 1344 search for the destination 1345 node's CP name failed. 1347 rscvCalculationFailed(4) - The final path switch attempt 1348 failed because an RSCV to the 1349 node containing the remote 1350 RTP endpoint could not be 1351 calculated. 1352 negativeRouteSetupReply(5) - The final path switch attempt 1353 failed because route setup 1354 failed for the new path. 1355 backoutRouteSetupReply(6) - The final path switch attempt 1356 failed because the remote RTP 1357 endpoint refused to continue 1358 the RTP connection. 1359 timeoutDuringFirstAttempt(7) - The path switch timer expired 1360 during the first path switch 1361 attempt. 1362 otherUnsuccessful(8) - The final path switch attempt 1363 failed for a reason other 1364 than those listed above." 1366 ::= { hprRtpStatusEntry 12 } 1368 -- *************************************************************** 1369 -- Conformance information 1370 -- *************************************************************** 1372 hprConformance OBJECT IDENTIFIER ::= { hprMIB 2 } 1374 hprCompliances OBJECT IDENTIFIER ::= { hprConformance 1 } 1375 hprGroups OBJECT IDENTIFIER ::= { hprConformance 2 } 1377 -- Compliance statements 1379 hprCompliance MODULE-COMPLIANCE 1380 STATUS current 1381 DESCRIPTION 1382 "The compliance statement for the SNMPv2 entities that 1383 implement the HPR MIB." 1385 MODULE -- this module 1387 -- Unconditionally mandatory groups 1388 MANDATORY-GROUPS { 1389 hprGlobalConfGroup, 1390 hprAnrRoutingConfGroup, 1391 hprTransportUserConfGroup 1392 } 1394 -- Conditionally mandatory groups 1395 GROUP hprRtpConfGroup 1396 DESCRIPTION 1397 "The hprRtpConfGroup is mandatory for HPR implementations 1398 supporting the HPR transport tower." 1400 ::= { hprCompliances 1 } 1402 -- Units of conformance 1403 hprGlobalConfGroup OBJECT-GROUP 1404 OBJECTS { 1405 hprNodeCpName, 1406 hprOperatorPathSwitchSupport 1407 } 1408 STATUS current 1409 DESCRIPTION 1410 "A collection of objects providing the instrumentation of HPR 1411 general information and capabilities." 1413 ::= { hprGroups 1 } 1415 hprAnrRoutingConfGroup OBJECT-GROUP 1416 OBJECTS { 1417 hprAnrsAssigned, 1418 hprAnrCounterState, 1419 hprAnrCounterStateTime, 1420 hprAnrType, 1421 hprAnrOutTgDest, 1422 hprAnrOutTgNum, 1423 hprAnrPacketsReceived, 1424 hprAnrCounterDisconTime 1425 } 1426 STATUS current 1427 DESCRIPTION 1428 "A collection of objects providing instrumentation for the 1429 node's ANR routing." 1431 ::= { hprGroups 2 } 1433 hprTransportUserConfGroup OBJECT-GROUP 1434 OBJECTS { 1435 hprNceType, 1436 hprNceDefault, 1437 hprNceInstanceId 1438 } 1439 STATUS current 1440 DESCRIPTION 1441 "A collection of objects providing information on the users of 1442 the HPR transport known to the node." 1444 ::= { hprGroups 3 } 1446 hprRtpConfGroup OBJECT-GROUP 1447 OBJECTS { 1448 hprRtpGlobeConnSetups, 1449 hprRtpGlobeCtrState, 1450 hprRtpGlobeCtrStateTime, 1451 hprRtpRemCpName, 1452 hprRtpRemNceId, 1453 hprRtpRemTcid, 1454 hprRtpPathSwitchTrigger, 1455 hprRtpRscv, 1456 hprRtpTopic, 1457 hprRtpState, 1458 hprRtpUpTime, 1459 hprRtpLivenessTimer, 1460 hprRtpShortReqTimer, 1461 hprRtpPathSwTimer, 1462 hprRtpLivenessTimeouts, 1463 hprRtpShortReqTimeouts, 1465 hprRtpMaxSendRate, 1466 hprRtpMinSendRate, 1467 hprRtpCurSendRate, 1469 hprRtpSmRdTripDelay, 1471 hprRtpSendPackets, 1472 hprRtpRecvPackets, 1473 hprRtpSendBytes, 1474 hprRtpRecvBytes, 1476 hprRtpRetrPackets, 1477 hprRtpPacketsDiscarded, 1478 hprRtpDetectGaps, 1479 hprRtpRateReqSends, 1481 hprRtpOkErrPathSws, 1482 hprRtpBadErrPathSws, 1483 hprRtpOkOpPathSws, 1484 hprRtpBadOpPathSws, 1485 hprRtpCounterDisconTime, 1487 hprRtpStatusStartTime, 1488 hprRtpStatusEndTime, 1489 hprRtpStatusRemNceId, 1490 hprRtpStatusRemTcid, 1491 hprRtpStatusRemCpName, 1492 hprRtpStatusNewRscv, 1493 hprRtpStatusOldRscv, 1494 hprRtpStatusCause, 1495 hprRtpStatusLastAttemptResult 1497 } 1498 STATUS current 1499 DESCRIPTION 1500 "A collection of objects providing the instrumentation for RTP 1501 connection end points." 1503 ::= { hprGroups 4 } 1505 -- end of conformance statement 1507 END 1508 6. Acknowledgments 1510 This MIB module is the product of the IETF SNA NAU MIB WG and the AIW 1511 APPN/HPR MIBs SIG. Thanks to Ray Bird, IBM Corporation; Jim Cobban, 1512 Nortel; and Laura Petrie, IBM Corporation, for their contributions and 1513 review. 1515 7. References 1517 [1] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. 1518 Waldbusser, "Structure of Management Information for version 2 of 1519 the Simple Network Management Protocol (SNMPv2)", RFC 1902, January 1520 1996. 1522 [2] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. 1523 Waldbusser, "Textual Conventions for Version 2 of the Simple 1524 Network Management Protocol (SNMPv2)", RFC 1903, January 1996. 1526 [3] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. 1527 Waldbusser, "Conformance Statements for Version 2 of the Simple 1528 Network Management Protocol (SNMPv2)", RFC 1904, January 1996. 1530 [4] Clouston, B., and B. Moore, "Definition of Managed Objects for 1531 APPN", Cisco Systems, IBM Corporation, November 1996. 1533 [5] IBM, APPN High Performance Routing Architecture Reference, SV40- 1534 1018-00. 1536 [6] IBM, SNA/MS Formats, GC31-8302-00 1537 8. Security Considerations 1539 In most cases, MIBs are not themselves security risks; if SNMP security 1540 is operating as intended, the use of a MIB to view information about a 1541 system, or to change some parameter at the system, is a tool, not a 1542 threat. 1544 None of the read-only objects in the HPR MIB reports a password, user 1545 data, or anything else that is particularly sensitive. Some enterprises 1546 view their network configuration itself, as well as information about 1547 network usage and performance, as corporate assets; such enterprises may 1548 wish to restrict SNMP access to most of the objects in the MIB. 1550 One read-write object in the MIB can affect network operations: 1552 o hprRtpPathSwitchTrigger: Setting this object to 'switchPathNow' 1553 triggers an immediate path switch attempt. An HPR path switch does 1554 not itself disrupt the SNA sessions using the RTP connection 1555 undergoing the path switch. However, frequent path switches for 1556 many RTP connections can have an adverse impact on overall network 1557 performance. 1559 It is recommended that SNMP access to this object be restricted. 1561 Other read-write objects control the gathering of network 1562 management data; controlling access to these objects is less 1563 critical. 1565 9. Authors' Addresses 1567 Bob Clouston 1568 Cisco Systems 1569 7025 Kit Creek Road 1570 P.O. Box 14987 1571 Research Triangle Park, NC 27709, USA 1573 Tel: 1 919 472 2333 1574 E-mail: clouston@cisco.com 1576 Bob Moore 1577 IBM Corporation 1578 800 Park Offices Drive 1579 CNMA/664 1580 P.O. Box 12195 1581 Research Triangle Park, NC 27709, USA 1583 Tel: 1 919 254 4436 1584 E-mail: remoore@ralvm6.vnet.ibm.com 1585 10. Table of Contents 1587 1. Status of this Memo .................................... 1 1588 2. Introduction ........................................... 1 1589 3. The SNMP Network Management Framework .................. 2 1590 4. Overview ............................................... 2 1591 4.1 HPR MIB structure ..................................... 4 1592 5. Definitions ............................................ 6 1593 6. Acknowledgments ........................................ 35 1594 7. References ............................................. 35 1595 8. Security Considerations ................................ 36 1596 9. Author's Addresses ..................................... 36