idnits 2.17.1 draft-ietf-snanau-hprmib-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Cannot find the required boilerplate sections (Copyright, IPR, etc.) in this document. Expected boilerplate is as follows today (2024-04-25) 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 46 instances of too long lines in the document, the longest one being 3 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 735 has weird spacing: '... -- ok err p...' == Line 737 has weird spacing: '... -- ok op p...' == Line 738 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 (November 19, 1996) is 10019 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' Summary: 15 errors (**), 0 flaws (~~), 4 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Definitions of Managed Objects 3 for HPR 5 November 19, 1996 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 the proposed set of objects for monitoring the 59 configuration and active characteristics of devices with HPR 60 capabilities. HPR is an enhancement to the Advanced Peer-to-Peer 61 Network (APPN) architecture that provides fast data routing and improved 62 session reliability. APPN is one of the protocols that can use the HPR 63 transport mechanism. See the SNANAU APPN MIB [4] for management of APPN 64 and APPN use of the HPR transport. 66 Automatic Network Routing (ANR) is a fast low-level routing technique. 67 Each node assigns a unique (within that node) ANR label for each out- 68 bound link as it is activated. The label size is defined by the ANR 69 node, and nodes only need to know how to interpret their own labels. 70 The ANR string is a group of ANR labels encoded in a header in front of 71 the message being sent. At each hop the node strips off its own ANR 72 label and forwards the message onto the link with that label. The last 73 label in the string is the Network Connection Endpoint (NCE), which 74 identifies the component within the destination node that is to receive 75 the message. 77 Rapid Transport Protocol (RTP) is an end-to-end full duplex transport 78 connection (pipe). It provides for high-speed transport of data using 79 ANR. RTP is connection-oriented, and delivers data in correct order 80 reliably. Error recovery is done efficiently with selective 81 retransmission of data. An RTP path can be switched without disrupting 82 the sessions using it. An RTP path switch may be done automatically if 83 a link in the path fails and another RTP path is available, or on demand 84 to restore the optimal path. 86 RTP performs flow/congestion control with the Adaptive Rate-Based (ARB) 87 algorithm. ARB is done only at the endpoints of the RTP pipe, so 88 intermediate hops are not involved. ARB regulates the flow of data over 89 an RTP connection by adaptively changing the sender's rate based on 90 feedback on the receiver's rate. It is designed to prevent congestion 91 rather than react to it. 93 In this document, we describe HPR managed objects. 95 The HPR terms and overall architecture are available from the 96 networking.raleigh.ibm.com ftp site [5]. 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 supporting the HPR 106 Transport Tower. 108 o Ability to trigger an RTP path switch 110 o Historical information about RTP path switch attempts 112 This MIB module does not support: 114 o Configuration of HPR nodes. 116 o Protocol-specific uses of HPR (such as APPN) 118 o Traps. The APPN MIB contains a trap for Alert conditions that may 119 affect HPR resources. 121 4.1. HPR MIB Structure 123 The HPR MIB module contains the following groups of objects: 125 o hprGlobal - general HPR objects. 127 o hprAnrRouting - objects related to the ANR routing table. 129 o hprTransportUser - objects related to users of the HPR transport. 131 o hprRtp - objects related to the HPR Transport Tower. 133 These groups are described below in more detail. 135 4.1.1. hprGlobal group 137 The hprGlobal group consists of general objects such as the APPN CP name 138 of the HPR node and the level of support for operator-requested path 139 switches. 141 4.1.2. hprAnrRouting group 143 The hprAnrRouting group consists objects to monitor and control the 144 counting of ANR packets received and the following table: 146 1) hprAnrRoutingTable 148 This table correlates incoming ANR labels to the outbound transmission 149 group (TG) or local NCE to which incoming packet will be forwarded. An 150 entry defines the label type as identifying a local NCE or a TG, 151 identifies the NCE or TG, and counts the number of packets received with 152 the entry's ANR label. 154 4.1.3. hprTransportUser group 156 The hprTransportUser group consists of the following table: 158 1) hprNceTable 160 This table identifies network connection endpoints and their function 161 types. The function type can be any combination of a control point 162 (CP), logical unit (LU), boundary function, and route setup. 164 4.1.4. hprRtp group 166 The hprRtp group consists of the following objects and tables: 168 1) hprRtpGlobe 170 These objects contain information about the number of RTP connection 171 setups, and control of RTP counters. 173 2) hprRtpTable 175 This table contains one entry for each RTP connection. The information 176 includes local and remote NCE IDs and TCIDs, timers, send rates, and 177 statistics. A path switch can be triggered by the 178 hprRptPathSwitchTrigger object if the agent node supports it; however, a 179 new path cannot be specified. 181 3) hprRtpStatusTable 183 This table contains statistics and historical information for RTP path 184 switches attempts, including old and new ANR strings and Route Selection 185 Control Vectors (RSCVs), why the path switch was initiated, and the 186 result (successful or reason for failure). 188 5. Definitions 190 HPR-MIB DEFINITIONS ::= BEGIN 192 IMPORTS 193 DisplayString, DateAndTime, TimeStamp, TEXTUAL-CONVENTION 194 FROM SNMPv2-TC 196 Counter32, Gauge32, Unsigned32, TimeTicks, 197 OBJECT-TYPE, MODULE-IDENTITY 198 FROM SNMPv2-SMI 200 MODULE-COMPLIANCE, OBJECT-GROUP 201 FROM SNMPv2-CONF 203 snanauMIB 204 FROM SNA-NAU-MIB 206 SnaControlPointName 207 FROM APPN-MIB; 208 hprMIB MODULE-IDENTITY 209 LAST-UPDATED "961119000000Z" 210 ORGANIZATION "AIW APPN / HPR MIB SIG" 211 CONTACT-INFO 213 " 215 Bob Clouston 216 Cisco Systems 217 7025 Kit Creek Road 218 P.O. Box 14987 219 Research Triangle Park, NC 27709, USA 220 Tel: 1 919 472 2333 221 E-mail: clouston@cisco.com 223 Bob Moore 224 IBM Corporation 225 800 Park Offices Drive 226 RHJA/664 227 P.O. Box 12195 228 Research Triangle Park, NC 27709, USA 229 Tel: 1 919 254 4436 230 E-mail: remoore@ralvm6.vnet.ibm.com 231 " 232 DESCRIPTION 233 "This is the MIB module for objects used to 234 manage network devices with HPR capabilities." 235 ::= { snanauMIB 6 } 236 -- snanauMIB ::= { mib-2 34 } 238 -- ********************************************************************* 239 -- Textual Conventions 240 -- --------------------------------------------------------------------- 242 -- SnaControlPointName is imported from the APPN MIB 244 HprRtpCounter ::= TEXTUAL-CONVENTION 245 STATUS current 246 DESCRIPTION 247 "An object providing statistics for an RTP connection. A 248 Management Station can detect discontinuities in this counter 249 by monitoring the hprRtpCounterDisconTime object." 251 SYNTAX Counter32 253 -- ********************************************************************* 254 hprObjects OBJECT IDENTIFIER ::= { hprMIB 1 } 255 -- ********************************************************************* 257 -- ********************************************************************* 258 hprGlobal OBJECT IDENTIFIER ::= { hprObjects 1 } 259 -- ********************************************************************** 260 -- The hprGlobal group applies to both intermediate and end nodes. 261 -- ********************************************************************** 263 hprNodeCpName OBJECT-TYPE 264 SYNTAX SnaControlPointName 265 MAX-ACCESS read-only 266 STATUS current 267 DESCRIPTION 268 "Administratively assigned network name for the APPN node where 269 this HPR implementation resides. This object corresponds to 270 the appnNodeCpName object in the APPN MIB." 272 ::= { hprGlobal 1 } 274 hprUpTime OBJECT-TYPE 275 SYNTAX TimeTicks 276 MAX-ACCESS read-only 277 STATUS current 278 DESCRIPTION 279 "Time (in hundredths of a second) since this HPR component 280 was last re-initialized." 282 ::= { hprGlobal 2 } 284 hprOperatorPathSwitchSupport OBJECT-TYPE 285 SYNTAX INTEGER { 286 notSupported(1), 287 switchTriggerSupported(2), 288 switchToPathSupported(3) 289 } 290 MAX-ACCESS read-only 291 STATUS current 292 DESCRIPTION 293 "This object indicates an implementation's level of support for 294 an operator-requested path switch. 296 notSupported(1) - the agent does not support 297 operator-requested path switches 298 switchTriggerSupported(2) - the agent supports a 'switch 299 path now' command from an 300 operator, but not a command to 301 switch to a specified path 302 switchToPathSupported(3) - the agent supports both a 303 'switch path now' command and a 304 command to switch to a specified 305 path." 307 ::= { hprGlobal 3 } 309 -- ********************************************************************** 310 hprAnrRouting OBJECT IDENTIFIER ::= { hprObjects 2 } 311 -- ********************************************************************** 313 hprAnrsAssigned OBJECT-TYPE 314 SYNTAX Counter32 315 MAX-ACCESS read-only 316 STATUS current 317 DESCRIPTION 318 "The total number of ANRs assigned by this node since it was 319 last re-initialized. A Management Station can detect 320 discontinuities in this counter by monitoring the 321 appnNodeCounterDisconTime object in the APPN MIB." 323 ::= { hprAnrRouting 1 } 325 hprAnrCounterState OBJECT-TYPE 326 SYNTAX INTEGER { 327 notActive(1), 328 active(2) 329 } 330 MAX-ACCESS read-write 331 STATUS current 332 DESCRIPTION 333 "This object is used for a network management station to turn 334 on/off the counting of ANR packets in the hprAnrRoutingTable. 335 The initial value of this object is an implementation choice. 337 notActive(1) - this counter is not being incremented; 338 its value is always zero 339 active(2) - this counter is being incremented" 341 ::= { hprAnrRouting 2 } 343 hprAnrCounterStateTime OBJECT-TYPE 344 SYNTAX DateAndTime 345 MAX-ACCESS read-only 346 STATUS current 347 DESCRIPTION 348 "The time when the hprAnrCounterState object last changed its 349 value." 351 ::= { hprAnrRouting 3 } 353 hprAnrRoutingTable OBJECT-TYPE 354 SYNTAX SEQUENCE OF HprAnrRoutingEntry 355 MAX-ACCESS not-accessible 356 STATUS current 357 DESCRIPTION 358 "The ANR Routing table provides a means of correlating an 359 incoming ANR label (i.e., one assigned by this node) with the 360 TG over which a packet containing the label will be forwarded. 361 When the ANR label identifies a local NCE, the TG information 362 objects have no meaning. The table also contains an object to 363 count the number of packets received with a given ANR label." 365 ::= { hprAnrRouting 4 } 367 hprAnrRoutingEntry OBJECT-TYPE 368 SYNTAX HprAnrRoutingEntry 369 MAX-ACCESS not-accessible 370 STATUS current 371 DESCRIPTION 372 "The ANR label is used to index this table." 374 INDEX { hprAnrLabel } 376 ::= { hprAnrRoutingTable 1 } 378 HprAnrRoutingEntry ::= SEQUENCE { 379 hprAnrLabel OCTET STRING, 380 hprAnrType INTEGER, 381 hprAnrOutTgDest DisplayString, 382 hprAnrOutTgNum INTEGER, 383 hprAnrPacketsReceived Counter32, 384 hprAnrCounterDisconTime TimeStamp 385 } 387 hprAnrLabel OBJECT-TYPE 388 SYNTAX OCTET STRING (SIZE (1..8)) 389 MAX-ACCESS not-accessible 390 STATUS current 391 DESCRIPTION 392 "The first ANR label in an incoming packet." 394 ::= { hprAnrRoutingEntry 1 } 396 hprAnrType OBJECT-TYPE 397 SYNTAX INTEGER { 398 nce(1), 399 tg(2) 400 } 401 MAX-ACCESS read-only 402 STATUS current 403 DESCRIPTION 404 "An object indicating whether an ANR label assigned by this 405 node identifies a local NCE or a TG on which outgoing packets 406 are forwarded. 408 nce(1) - the ANR label identifies a local NCE. In this 409 case the hprAnrOutTgDest and hprAnrOutTgNum 410 objects have no meaning. 411 tg(2) - the ANR label identifies a TG." 413 ::= { hprAnrRoutingEntry 2 } 415 hprAnrOutTgDest OBJECT-TYPE 416 SYNTAX DisplayString (SIZE (0 | 3..17)) 417 MAX-ACCESS read-only 418 STATUS current 419 DESCRIPTION 420 "Destination node for the TG over which packets with this ANR 421 label are forwarded. This is the fully qualified name of an 422 APPN network node or end node, formatted according to the 423 SnaControlPointName textual convention. If the ANR label 424 identifies a local NCE, then this object returns a zero-length 425 string. 427 This object corresponds to the appnLocalTgDest object in the 428 APPN MIB." 430 ::= { hprAnrRoutingEntry 3 } 432 hprAnrOutTgNum OBJECT-TYPE 433 SYNTAX INTEGER (0..255) 434 MAX-ACCESS read-only 435 STATUS current 436 DESCRIPTION 437 "Number of the TG over which packets with this ANR label are 438 forwarded. If the ANR label identifies a local NCE, then this 439 object returns the value 0. 441 This object corresponds to the appnLocalTgNum object in the 442 APPN MIB." 444 ::= { hprAnrRoutingEntry 4 } 446 hprAnrPacketsReceived OBJECT-TYPE 447 SYNTAX Counter32 448 MAX-ACCESS read-only 449 STATUS current 450 DESCRIPTION 451 "The total number of packets received with this ANR label as 452 their first label. 454 A Management Station can detect discontinuities in this counter 455 by monitoring the hprAnrCounterDisconTime object." 457 ::= { hprAnrRoutingEntry 5 } 459 hprAnrCounterDisconTime OBJECT-TYPE 460 SYNTAX TimeStamp 461 MAX-ACCESS read-only 462 STATUS current 463 DESCRIPTION 464 "The value of the sysUpTime object when the 465 hprAnrPacketsReceived counter for this ANR label last 466 experienced a discontinuity. This will be the later of two 467 times: the time at which the ANR label was associated with 468 either an outgoing TG or a local NCE, or the time at which the 469 ANR counters were last turned on." 471 ::= { hprAnrRoutingEntry 6 } 473 -- ********************************************************************** 474 hprTransportUser OBJECT IDENTIFIER ::= { hprObjects 3 } 475 -- ********************************************************************** 476 -- Transport Service User (TU) Table: (RTP Connection Users) 477 -- 478 -- There will be several users of the HPR transport and each HPR node 479 -- shall maintain a table of these users. 480 -- ********************************************************************** 482 hprNceTable OBJECT-TYPE 483 SYNTAX SEQUENCE OF HprNceEntry 484 MAX-ACCESS not-accessible 485 STATUS current 486 DESCRIPTION 487 "The Network Connection Endpoint (NCE) table." 489 ::= { hprTransportUser 1 } 491 hprNceEntry OBJECT-TYPE 492 SYNTAX HprNceEntry 493 MAX-ACCESS not-accessible 494 STATUS current 495 DESCRIPTION 496 "The NCE ID is used to index this table." 498 INDEX { hprNceId } 500 ::= { hprNceTable 1 } 502 HprNceEntry ::= SEQUENCE { 503 hprNceId OCTET STRING, 504 hprNceType INTEGER, 505 hprNceDefault INTEGER, 506 hprNceInstanceId OCTET STRING 507 } 509 hprNceId OBJECT-TYPE 510 SYNTAX OCTET STRING (SIZE (1..8)) 511 MAX-ACCESS not-accessible 512 STATUS current 513 DESCRIPTION 514 "The Network Connection Endpoint (NCE) id. NCEs identify 515 Control Points (Cp), Logical Units (Lu), HPR Boundary 516 Functions (Bf) and Route Setup (Rs) Functions." 518 ::= { hprNceEntry 1 } 520 hprNceType OBJECT-TYPE 521 SYNTAX INTEGER { 522 cp(1), 523 lu(2), 524 luCp(3), 525 bf(4), 526 bfCp(5), 527 bfLu(6), 528 bfLuCp(7), 529 rs(8), 530 rsCp(9), 531 rsLu(10), 532 rsLuCp(11), 533 rsBf(12), 534 rsBfCp(13), 535 rsBfLu(14), 536 rsBfLuCp(15) 537 } 538 MAX-ACCESS read-only 539 STATUS current 540 DESCRIPTION 541 "The Network Connection Endpoint (NCE) may provide one or more 542 function types. These function types are encoded such that a 543 bit is set to '1' if the corresponding function type is 544 supported by this NCE: 546 bit 0: Control Point Functions (Cp) 547 bit 1: Logical Unit Functions (Lu) 548 bit 2: Boundary Functions (Bf) 549 bit 3: Route Setup Functions (Rs) 550 bit 4-31: reserved, always '0' 551 " 553 ::= { hprNceEntry 2 } 555 hprNceDefault OBJECT-TYPE 556 SYNTAX INTEGER { 557 cp(1), 558 lu(2), 559 luCp(3), 560 bf(4), 561 bfCp(5), 562 bfLu(6), 563 bfLuCp(7), 564 rs(8), 565 rsCp(9), 566 rsLu(10), 567 rsLuCp(11), 568 rsBf(12), 569 rsBfCp(13), 570 rsBfLu(14), 571 rsBfLuCp(15), 572 noDefault(32768) 573 } 574 MAX-ACCESS read-only 575 STATUS current 576 DESCRIPTION 577 "Indicates whether or not this NCE is the default for one or 578 more function types. While default NCEs are not explicitly 579 defined in the architecture, some implementations provide them; 580 for such implementations, it is useful to make this information 581 available to a Management Station. 583 The function types are encoded such that a bit is set to '1' if 584 the corresponding function type uses this NCE as the default. 585 Turning on only bit 15 indicates that the NCE is not a default 586 for any function type; an implementation that does not support 587 default NCEs returns this value for every NCE. 589 bit 0: Control Point Functions (Cp) 590 bit 1: Logical Unit Functions (Lu) 591 bit 2: Boundary Functions (Bf) 592 bit 3: Route Setup Functions (Rs) 593 bit 4-14: reserved, always '0' 594 bit 15: not a default for any function type 595 bit 16-31: reserved, always '0' 596 " 598 ::= { hprNceEntry 3 } 600 hprNceInstanceId OBJECT-TYPE 601 SYNTAX OCTET STRING (SIZE (4)) 602 MAX-ACCESS read-only 603 STATUS current 604 DESCRIPTION 605 "The NCE instance identifier (NCEII) identifying the current 606 instance of this NCE." 608 ::= { hprNceEntry 4 } 610 -- ********************************************************************** 611 hprRtp OBJECT IDENTIFIER ::= { hprObjects 4 } 612 -- ********************************************************************** 613 -- ********************************************************************** 614 -- 615 -- The RTP group is implemented by all managed nodes supporting the 616 -- HPR Transport Tower. The group contains several scalars (simple 617 -- objects) and a table. 618 -- ********************************************************************** 620 -- ********************************************************************** 621 hprRtpGlobe OBJECT IDENTIFIER ::= { hprRtp 1} 622 -- ********************************************************************** 623 hprRtpGlobeConnSetups OBJECT-TYPE 624 SYNTAX Counter32 625 MAX-ACCESS read-only 626 STATUS current 627 DESCRIPTION 628 "The total number of RTP connection setups in which this node 629 has participated, as either sender or receiver, since it was 630 last re-initialized. Retries of a setup attempt do not cause 631 the counter to be incremented. 633 A Management Station can detect discontinuities in this counter 634 by monitoring the appnNodeCounterDisconTime object in the APPN 635 MIB." 637 ::= { hprRtpGlobe 1 } 639 hprRtpGlobeCtrState OBJECT-TYPE 640 SYNTAX INTEGER { 641 notActive(1), 642 active(2) 643 } 644 MAX-ACCESS read-write 645 STATUS current 646 DESCRIPTION 647 "This object allows a network management station to turn the 648 counters in the hprRtpTable on and off. The initial value of 649 this object is an implementation choice. 651 notActive(1) - these counters are not being incremented; 652 their values are always zero 653 active(2) - these counters are being incremented" 655 ::= { hprRtpGlobe 2 } 657 hprRtpGlobeCtrStateTime OBJECT-TYPE 658 SYNTAX DateAndTime 659 MAX-ACCESS read-only 660 STATUS current 661 DESCRIPTION 662 "The time when the value of the hprRtpGlobeCtrState object last 663 changed. This time can be used to identify when this change 664 occurred in relation to other events in the agent, such as the 665 last time the APPN node was re-initialized, and thus it can be 666 of use in determining how to interpret the values of the 667 counter objects." 669 ::= { hprRtpGlobe 3 } 671 -- ********************************************************************** 672 -- The RTP Connection Table 673 -- There may be many RTP connections on a node supporting the 674 -- HPR Transport Tower. Each tower node shall maintain a table 675 -- of these RTP connections. 676 -- ********************************************************************** 678 hprRtpTable OBJECT-TYPE 679 SYNTAX SEQUENCE OF HprRtpEntry 680 MAX-ACCESS not-accessible 681 STATUS current 682 DESCRIPTION 683 "The RTP Connection table" 685 ::= { hprRtp 2 } 687 hprRtpEntry OBJECT-TYPE 688 SYNTAX HprRtpEntry 689 MAX-ACCESS not-accessible 690 STATUS current 691 DESCRIPTION 692 "The local NCE ID and local TCID are used to index this table." 694 INDEX 695 { hprRtpLocNceId, 696 hprRtpLocTcid } 698 ::= { hprRtpTable 1 } 700 HprRtpEntry ::= SEQUENCE { 701 hprRtpLocNceId OCTET STRING, -- local nce id 702 hprRtpLocTcid OCTET STRING, -- local tcid 703 hprRtpRemCpName SnaControlPointName,-- remote cp name 704 hprRtpRemNceId OCTET STRING, -- remote nce id 705 hprRtpRemTcid OCTET STRING, -- remote tcid 706 hprRtpPathSwitchTrigger INTEGER, -- trigger (read-write) 707 hprRtpRscv OCTET STRING, -- rscv 708 hprRtpTopic DisplayString, -- topic (cos) 709 hprRtpState INTEGER, -- state 710 hprRtpUpTime TimeTicks, -- up time 712 hprRtpLivenessTimer Unsigned32, -- liveness timer 713 hprRtpShortReqTimer Unsigned32, -- short request timer 714 hprRtpPathSwTimer Unsigned32, -- path switch timer 716 hprRtpLivenessTimeouts HprRtpCounter, -- liveness timeouts 717 hprRtpShortReqTimeouts HprRtpCounter, -- short req timeouts 719 hprRtpMaxSendRate Gauge32, -- maximum send rate 720 hprRtpMinSendRate Gauge32, -- minimum send rate 721 hprRtpCurSendRate Gauge32, -- current send rate 723 hprRtpSmRdTripDelay Gauge32, -- smooth rnd trip delay 725 hprRtpRecvPackets HprRtpCounter, -- total packets recv 726 hprRtpSendPackets HprRtpCounter, -- total packets sent 727 hprRtpRecvBytes HprRtpCounter, -- total bytes recv 728 hprRtpSendBytes HprRtpCounter, -- total bytes sent 730 hprRtpRetrPackets HprRtpCounter, -- total pkts re-xmitted 731 hprRtpPacketsDiscarded HprRtpCounter, -- total pkts discarded 732 hprRtpDetectGaps HprRtpCounter, -- total gaps detected 733 hprRtpRateReqSends HprRtpCounter, -- total rate req send 735 hprRtpOkErrPathSws HprRtpCounter, -- ok err path sws 736 hprRtpBadErrPathSws HprRtpCounter, -- bad err path sws 737 hprRtpOkOpPathSws HprRtpCounter, -- ok op path sws 738 hprRtpBadOpPathSws HprRtpCounter, -- bad op path sws 739 hprRtpCounterDisconTime TimeStamp -- discontinuity ind 740 } 742 hprRtpLocNceId OBJECT-TYPE 743 SYNTAX OCTET STRING (SIZE (1..8)) 744 MAX-ACCESS not-accessible 745 STATUS current 746 DESCRIPTION 747 "The local Network Connection Endpoint (NCE) of this RTP 748 connection. NCEs identify CPs, LUs, Boundary Functions (BFs), 749 and Route Setup (RS) components." 751 ::= { hprRtpEntry 1 } 753 hprRtpLocTcid OBJECT-TYPE 754 SYNTAX OCTET STRING (SIZE (8)) 755 MAX-ACCESS not-accessible 756 STATUS current 757 DESCRIPTION 758 "The local TCID of this RTP connection." 760 ::= { hprRtpEntry 2 } 762 hprRtpRemCpName OBJECT-TYPE 763 SYNTAX SnaControlPointName 764 MAX-ACCESS read-only 765 STATUS current 766 DESCRIPTION 767 "Administratively assigned network name for the remote node of 768 this RTP connection." 770 ::= { hprRtpEntry 3 } 772 hprRtpRemNceId OBJECT-TYPE 773 SYNTAX OCTET STRING (SIZE (1..8)) 774 MAX-ACCESS read-only 775 STATUS current 776 DESCRIPTION 777 "The remote Network Connection Endpoint (NCE) of this RTP 778 connection. NCEs identify CPs, LUs, Boundary Functions (BFs), 779 and Route Setup (RS) components." 781 ::= { hprRtpEntry 4 } 783 hprRtpRemTcid OBJECT-TYPE 784 SYNTAX OCTET STRING (SIZE (8)) 785 MAX-ACCESS read-only 786 STATUS current 787 DESCRIPTION 788 "The remote TCID of this RTP connection." 790 ::= { hprRtpEntry 5 } 792 hprRtpPathSwitchTrigger OBJECT-TYPE 793 SYNTAX INTEGER { 794 ready(1), 795 switchPathNow(2) 796 } 797 MAX-ACCESS read-write 798 STATUS current 799 DESCRIPTION 800 "Object by which a Management Station can trigger an operator- 801 requested path switch, by setting the value to 802 switchPathNow(2). Setting this object to switchPathNow(2) 803 triggers a path switch even if its previous value was already 804 switchPathNow(2). 806 The value ready(1) is returned on GET operations until a SET 807 has been processed; after that the value received on the most 808 recent SET is returned. 810 Setting this object to switchPathNow(2) has no effect if the 811 agent does not support operator-requested path switches (i.e., 812 if the value of the hprOperatorPathSwitchSupport object is 813 notSupported(1)). 815 This MIB module provides no support for an operator-requested 816 switch to a specified path." 818 ::= { hprRtpEntry 6 } 820 hprRtpRscv OBJECT-TYPE 821 SYNTAX OCTET STRING (SIZE (0..255)) 822 MAX-ACCESS read-only 823 STATUS current 824 DESCRIPTION 825 "The forward Route Selection Control Vector for this RTP 826 connection. The format of this vector is described in SNA 827 Formats. 829 The value returned in this object during a path switch is 830 implementation-dependent: it may be the old path, the new 831 path, a zero-length string, or some other valid RSCV string." 833 ::= { hprRtpEntry 7 } 835 hprRtpTopic OBJECT-TYPE 836 SYNTAX DisplayString (SIZE(8)) 837 MAX-ACCESS read-only 838 STATUS current 839 DESCRIPTION 840 "The topic for this RTP connection. This is used to indicate 841 the Class of Service." 843 ::= { hprRtpEntry 8 } 845 hprRtpState OBJECT-TYPE 846 SYNTAX INTEGER { 847 rtpListening(1), 848 rtpCalling(2), 849 rtpConnected(3), 850 rtpPathSwitching(4), 851 rtpDisconnecting(5), 852 other(99) 853 } 854 MAX-ACCESS read-only 855 STATUS current 856 DESCRIPTION 857 "The state of the RTP connection, from the perspective of the 858 local RTP protocol machine: 860 rtpListening - connection open; waiting for other end 861 to call in 862 rtpCalling - connection opened, attempting to call 863 out, have not yet received any data 864 from other end 865 rtpConnected - connection is active; responded to a 866 call-in or received other end's TCID 867 from a call-out attempt 868 rtpPathSwitching - the path switch timer is running; 869 attempting to find a new path for this 870 connection. 871 rtpDisconnecting - no sessions are using this connection; 872 in process of bringing it down 873 other - the connection is not in any of the 874 states listed above." 876 ::= { hprRtpEntry 9 } 878 hprRtpUpTime OBJECT-TYPE 879 SYNTAX TimeTicks 880 MAX-ACCESS read-only 881 STATUS current 882 DESCRIPTION 883 "The length of time the RTP connection has been up, measured in 884 1/100ths of a second." 886 ::= { hprRtpEntry 10 } 888 hprRtpLivenessTimer OBJECT-TYPE 889 SYNTAX Unsigned32 890 UNITS "1/100ths of a second" 891 MAX-ACCESS read-only 892 STATUS current 893 DESCRIPTION 894 "The value of the liveness (ALIVE) timer of this RTP 895 connection, in units of 1/100th of a second. When this timer 896 expires and no packet has arrived from the partner since it was 897 last set, packets with Status Request indicators will be sent 898 to see if the RTP connection is still alive." 900 ::= { hprRtpEntry 11 } 902 hprRtpShortReqTimer OBJECT-TYPE 903 SYNTAX Unsigned32 904 UNITS "1/100ths of a second" 905 MAX-ACCESS read-only 906 STATUS current 907 DESCRIPTION 908 "The value of the RTP SHORT_REQ timer, in units of 1/100 of a 909 second. This timer represents the maximum time that a sender 910 waits for a reply from a receiver." 912 ::= { hprRtpEntry 12 } 914 hprRtpPathSwTimer OBJECT-TYPE 915 SYNTAX Unsigned32 916 UNITS "1/100ths of a second" 917 MAX-ACCESS read-only 918 STATUS current 919 DESCRIPTION 920 "The length of time that RTP should attempt a path switch for a 921 connection, in units of 1/100th of a second." 923 ::= { hprRtpEntry 13 } 925 hprRtpLivenessTimeouts OBJECT-TYPE 926 SYNTAX HprRtpCounter 927 MAX-ACCESS read-only 928 STATUS current 929 DESCRIPTION 930 "The total number of liveness timeouts for this RTP 931 connection." 933 ::= { hprRtpEntry 14 } 935 hprRtpShortReqTimeouts OBJECT-TYPE 936 SYNTAX HprRtpCounter 937 MAX-ACCESS read-only 938 STATUS current 939 DESCRIPTION 940 "The total number of short request timeouts for this RTP 941 connection." 943 ::= { hprRtpEntry 15 } 945 hprRtpMaxSendRate OBJECT-TYPE 946 SYNTAX Gauge32 947 MAX-ACCESS read-only 948 STATUS current 949 DESCRIPTION 950 "The high-water mark for this RTP connection's send rate, in 951 units of bytes per second. This is the high-water mark for the 952 entire life of the connection, not just the high-water mark for 953 the connection's current path." 955 ::= { hprRtpEntry 16 } 957 hprRtpMinSendRate OBJECT-TYPE 958 SYNTAX Gauge32 959 MAX-ACCESS read-only 960 STATUS current 961 DESCRIPTION 962 "The low-water mark for this RTP connection's send rate, in 963 units of bytes per second. This is the low-water mark for the 964 entire life of the connection, not just the low-water mark for 965 the connection's current path." 967 ::= { hprRtpEntry 17 } 969 hprRtpCurSendRate OBJECT-TYPE 970 SYNTAX Gauge32 971 MAX-ACCESS read-only 972 STATUS current 973 DESCRIPTION 974 "The current send rate for this RTP connection, in units of 975 bytes per second." 977 ::= { hprRtpEntry 18 } 979 hprRtpSmRdTripDelay OBJECT-TYPE 980 SYNTAX Gauge32 981 UNITS "1/1000ths of a second" 982 MAX-ACCESS read-only 983 STATUS current 984 DESCRIPTION 985 "The smoothed round trip delay for this RTP connection, in 986 units of 1/1000th of a second (ms)." 988 ::= { hprRtpEntry 19 } 990 hprRtpSendPackets OBJECT-TYPE 991 SYNTAX HprRtpCounter 992 MAX-ACCESS read-only 993 STATUS current 994 DESCRIPTION 995 "The total number of packets successfully sent on this RTP 996 connection." 998 ::= { hprRtpEntry 20 } 1000 hprRtpRecvPackets OBJECT-TYPE 1001 SYNTAX HprRtpCounter 1002 MAX-ACCESS read-only 1003 STATUS current 1004 DESCRIPTION 1005 "The total number of packets received on this RTP connection. 1006 The counter is incremented only once if duplicate copies of a 1007 packet are received." 1009 ::= { hprRtpEntry 21 } 1011 hprRtpSendBytes OBJECT-TYPE 1012 SYNTAX HprRtpCounter 1013 MAX-ACCESS read-only 1014 STATUS current 1015 DESCRIPTION 1016 "The total number of bytes sent on this RTP connection. Both 1017 RTP Transport Header (THDR) bytes and data bytes are included 1018 in this count." 1020 ::= { hprRtpEntry 22 } 1022 hprRtpRecvBytes OBJECT-TYPE 1023 SYNTAX HprRtpCounter 1024 MAX-ACCESS read-only 1025 STATUS current 1026 DESCRIPTION 1027 "The total number of bytes received on this RTP connection. 1028 Both RTP Transport Header (THDR) bytes and data bytes are 1029 included in this count." 1031 ::= { hprRtpEntry 23 } 1033 hprRtpRetrPackets OBJECT-TYPE 1034 SYNTAX HprRtpCounter 1035 MAX-ACCESS read-only 1036 STATUS current 1037 DESCRIPTION 1038 "The total number of packets retransmitted on this RTP 1039 connection." 1041 ::= { hprRtpEntry 24 } 1043 hprRtpPacketsDiscarded OBJECT-TYPE 1044 SYNTAX HprRtpCounter 1045 MAX-ACCESS read-only 1046 STATUS current 1047 DESCRIPTION 1048 "The total number of packets received on this RTP connection 1049 and then discarded. A packet may be discarded because it is 1050 determined to be a duplicate, or for other reasons." 1052 ::= { hprRtpEntry 25 } 1054 hprRtpDetectGaps OBJECT-TYPE 1055 SYNTAX HprRtpCounter 1056 MAX-ACCESS read-only 1057 STATUS current 1058 DESCRIPTION 1059 "The total number of gaps detected on this RTP connection." 1061 ::= { hprRtpEntry 26 } 1063 hprRtpRateReqSends OBJECT-TYPE 1064 SYNTAX HprRtpCounter 1065 MAX-ACCESS read-only 1066 STATUS current 1067 DESCRIPTION 1068 "The total number of Rate Requests sent on this RTP 1069 connection." 1071 ::= { hprRtpEntry 27 } 1073 hprRtpOkErrPathSws OBJECT-TYPE 1074 SYNTAX HprRtpCounter 1075 MAX-ACCESS read-only 1076 STATUS current 1077 DESCRIPTION 1078 "The total number of successful path switch attempts for this 1079 RTP connection due to errors." 1081 ::= { hprRtpEntry 28 } 1083 hprRtpBadErrPathSws OBJECT-TYPE 1084 SYNTAX HprRtpCounter 1085 MAX-ACCESS read-only 1086 STATUS current 1087 DESCRIPTION 1088 "The total number of unsuccessful path switches for this RTP 1089 connection due to errors." 1091 ::= { hprRtpEntry 29 } 1093 hprRtpOkOpPathSws OBJECT-TYPE 1094 SYNTAX HprRtpCounter 1095 MAX-ACCESS read-only 1096 STATUS current 1097 DESCRIPTION 1098 "The total number of successful path switches for this RTP 1099 connection due to operator requests." 1101 ::= { hprRtpEntry 30 } 1103 hprRtpBadOpPathSws OBJECT-TYPE 1104 SYNTAX HprRtpCounter 1105 MAX-ACCESS read-only 1106 STATUS current 1107 DESCRIPTION 1108 "The total number of unsuccessful path switches for this RTP 1109 connection due to operator requests. This counter is not 1110 incremented by an implementation that does not support 1111 operator-requested path switches, even if a Management Station 1112 requests such a path switch by setting the 1113 hprRtpPathSwitchTrigger object." 1115 ::= { hprRtpEntry 31 } 1117 hprRtpCounterDisconTime OBJECT-TYPE 1118 SYNTAX TimeStamp 1119 MAX-ACCESS read-only 1120 STATUS current 1121 DESCRIPTION 1122 "The value of the sysUpTime object when the counters for this 1123 RTP connection last experienced a discontinuity. This will be 1124 the later of two times: the time at which the connection was 1125 established or the time at which the HPR counters were last 1126 turned on." 1128 ::= { hprRtpEntry 32 } 1130 -- ********************************************************************** 1131 -- The RTP Connection Status Table 1132 -- This table contains statistics and historical information related to 1133 -- both successful and unsuccessful RTP path switches. This information 1134 -- can be important for both trend analysis and problem determination. 1135 -- 1136 -- Note the terminology here: when RTP is triggered to find a new path 1137 -- for a connection, this initiates a 'path switch,' which will end up 1138 -- being either successful or unsuccessful. During this path switch, 1139 -- RTP will make one or more 'path switch attempts,' which are attempts 1140 -- to find a new path for the connection and switch the connection to 1141 -- it. This 'new' path may be the same path that the connection was 1142 -- using before the path switch. 1143 -- 1144 -- It is an implementation option how many entries to keep in this 1145 -- table, and how long to retain any individual entry. 1146 -- ********************************************************************** 1147 hprRtpStatusTable OBJECT-TYPE 1148 SYNTAX SEQUENCE OF HprRtpStatusEntry 1149 MAX-ACCESS not-accessible 1150 STATUS current 1151 DESCRIPTION 1152 "RTP Connection Status Table: This table contains historical 1153 information on RTP connections. An entry is created in this 1154 table when a path switch is completed, either successfully or 1155 unsuccessfully." 1157 ::= { hprRtp 3 } 1159 hprRtpStatusEntry OBJECT-TYPE 1160 SYNTAX HprRtpStatusEntry 1161 MAX-ACCESS not-accessible 1162 STATUS current 1163 DESCRIPTION 1164 "This table is indexed by local NCE ID, local TCID, and 1165 an integer hprRtpStatusIndex." 1167 INDEX 1168 { hprRtpStatusLocNceId, 1169 hprRtpStatusLocTcid, 1170 hprRtpStatusIndex } 1172 ::= { hprRtpStatusTable 1 } 1174 HprRtpStatusEntry ::= SEQUENCE { 1175 hprRtpStatusLocNceId OCTET STRING, -- local nce id 1176 hprRtpStatusLocTcid OCTET STRING, -- local tcid 1177 hprRtpStatusIndex Unsigned32, -- index 1178 hprRtpStatusStartTime DateAndTime, -- time stamp 1179 hprRtpStatusEndTime DateAndTime, -- time stamp 1180 hprRtpStatusRemNceId OCTET STRING, -- remote nce id 1181 hprRtpStatusRemTcid OCTET STRING, -- remote tcid 1182 hprRtpStatusRemCpName SnaControlPointName,-- remote cp name 1183 hprRtpStatusNewRscv OCTET STRING, -- new rscv 1184 hprRtpStatusOldRscv OCTET STRING, -- old rscv 1185 hprRtpStatusCause INTEGER, -- cause 1186 hprRtpStatusLastAttemptResult INTEGER -- result of last 1187 } 1189 hprRtpStatusLocNceId OBJECT-TYPE 1190 SYNTAX OCTET STRING (SIZE (1..8)) 1191 MAX-ACCESS not-accessible 1192 STATUS current 1193 DESCRIPTION 1194 "The local Network Connection Endpoint (NCE) of this RTP 1195 connection. NCEs identify CPs, LUs, Boundary Functions (BFs), 1196 and Route Setup (RS) components." 1198 ::= { hprRtpStatusEntry 1 } 1200 hprRtpStatusLocTcid OBJECT-TYPE 1201 SYNTAX OCTET STRING (SIZE (8)) 1202 MAX-ACCESS not-accessible 1203 STATUS current 1204 DESCRIPTION 1205 "The local TCID of this RTP connection." 1207 ::= { hprRtpStatusEntry 2 } 1209 hprRtpStatusIndex OBJECT-TYPE 1210 SYNTAX Unsigned32 1211 MAX-ACCESS not-accessible 1212 STATUS current 1213 DESCRIPTION 1214 "Table index. This value begins at zero and is incremented 1215 when a new entry is added to the table." 1217 ::= { hprRtpStatusEntry 3 } 1219 hprRtpStatusStartTime OBJECT-TYPE 1220 SYNTAX DateAndTime 1221 MAX-ACCESS read-only 1222 STATUS current 1223 DESCRIPTION 1224 "The time when the path switch began." 1226 ::= { hprRtpStatusEntry 4 } 1228 hprRtpStatusEndTime OBJECT-TYPE 1229 SYNTAX DateAndTime 1230 MAX-ACCESS read-only 1231 STATUS current 1232 DESCRIPTION 1233 "The time when the path switch was ended, either successfully 1234 or unsuccessfully." 1236 ::= { hprRtpStatusEntry 5 } 1238 hprRtpStatusRemCpName OBJECT-TYPE 1239 SYNTAX SnaControlPointName 1240 MAX-ACCESS read-only 1241 STATUS current 1242 DESCRIPTION 1243 "Administratively assigned network name for the remote node of 1244 this RTP connection." 1246 ::= { hprRtpStatusEntry 6 } 1248 hprRtpStatusRemNceId OBJECT-TYPE 1249 SYNTAX OCTET STRING (SIZE (1..8)) 1250 MAX-ACCESS read-only 1251 STATUS current 1252 DESCRIPTION 1253 "The remote Network Connection Endpoint (NCE) of this RTP 1254 connection. NCEs identify CPs, LUs, Boundary Functions (BFs), 1255 and Route Setup (RS) components." 1257 ::= { hprRtpStatusEntry 7 } 1259 hprRtpStatusRemTcid OBJECT-TYPE 1260 SYNTAX OCTET STRING (SIZE (8)) 1261 MAX-ACCESS read-only 1262 STATUS current 1263 DESCRIPTION 1264 "The remote TCID of this RTP connection." 1266 ::= { hprRtpStatusEntry 8 } 1268 hprRtpStatusNewRscv OBJECT-TYPE 1269 SYNTAX OCTET STRING (SIZE (0..255)) 1270 MAX-ACCESS read-only 1271 STATUS current 1272 DESCRIPTION 1273 "The new Route Selection Control Vector for this RTP 1274 connection." 1276 ::= { hprRtpStatusEntry 9 } 1278 hprRtpStatusOldRscv OBJECT-TYPE 1279 SYNTAX OCTET STRING (SIZE (0..255)) 1280 MAX-ACCESS read-only 1281 STATUS current 1282 DESCRIPTION 1283 "The old Route Selection Control Vector for this RTP 1284 connection." 1286 ::= { hprRtpStatusEntry 10 } 1288 hprRtpStatusCause OBJECT-TYPE 1289 SYNTAX INTEGER { 1290 other(1), 1291 rtpConnFail(2), 1292 locLinkFail(3), 1293 remLinkFail(4), 1294 operRequest(5) 1295 } 1296 MAX-ACCESS read-only 1297 STATUS current 1298 DESCRIPTION 1299 "The reason for the path switch: 1301 other(1) - Reason other than those listed below, 1302 rtpConnFail(2) - RTP connection failure detected, 1303 locLinkFail(3) - Local link failure, 1304 remLinkFail(4) - Remote link failure (learned from TDUs), 1305 operRequest(5) - Operator requested path switch. " 1307 ::= { hprRtpStatusEntry 11 } 1309 hprRtpStatusLastAttemptResult OBJECT-TYPE 1310 SYNTAX INTEGER { successful(1), 1311 initiatorMoving(2), 1312 directorySearchFailed(3), 1313 rscvCalculationFailed(4), 1314 negativeRouteSetupReply(5), 1315 backoutRouteSetupReply(6), 1316 timeoutDuringFirstAttempt(7), 1317 otherUnsuccessful(8) 1318 } 1319 MAX-ACCESS read-only 1320 STATUS current 1321 DESCRIPTION 1322 "The result of the last completed path switch attempt. If the 1323 path switch is aborted in the middle of a path switch attempt 1324 because the path switch timer expires, the result of the 1325 previous path swtich attempt is reported. 1327 The values are defined as follows: 1329 successful(1) - The final path switch attempt 1330 was successful. 1331 initiatorMoving(2) - The final path switch attempt 1332 failed because the initiator 1333 is mobile, and there was no 1334 active link out of this node. 1335 directorySearchFailed(3) - The final path switch attempt 1336 failed because a directory 1337 search for the destination 1338 node's CP name failed. 1339 rscvCalculationFailed(4) - The final path switch attempt 1340 failed because an RSCV to the 1341 node containing the remote 1342 RTP endpoint could not be 1343 calculated. 1344 negativeRouteSetupReply(5) - The final path switch attempt 1345 failed because route setup 1346 failed for the new path. 1347 backoutRouteSetupReply(6) - The final path switch attempt 1348 failed because the remote RTP 1349 endpoint refused to continue 1350 the RTP connection. 1351 timeoutDuringFirstAttempt(7) - The path switch timer expired 1352 during the first path switch 1353 attempt. 1354 otherUnsuccessful(8) - The final path switch attempt 1355 failed for a reason other 1356 than those listed above." 1358 ::= { hprRtpStatusEntry 12 } 1360 -- *************************************************************** 1361 -- Conformance information 1362 -- *************************************************************** 1364 hprConformance OBJECT IDENTIFIER ::= { hprMIB 2 } 1366 hprCompliances OBJECT IDENTIFIER ::= { hprConformance 1 } 1367 hprGroups OBJECT IDENTIFIER ::= { hprConformance 2 } 1369 -- Compliance statements 1371 hprCompliance MODULE-COMPLIANCE 1372 STATUS current 1373 DESCRIPTION 1374 "The compliance statement for the SNMPv2 entities that 1375 implement the HPR MIB." 1377 MODULE -- this module 1379 -- Unconditionally mandatory groups 1380 MANDATORY-GROUPS { 1381 hprGlobalConfGroup, 1382 hprAnrRoutingConfGroup, 1383 hprTransportUserConfGroup 1384 } 1386 -- Conditionally mandatory groups 1387 GROUP hprRtpConfGroup 1388 DESCRIPTION 1389 "The hprRtpConfGroup is mandatory for HPR implementations 1390 supporting the HPR transport tower." 1392 ::= { hprCompliances 1 } 1394 -- Units of conformance 1395 hprGlobalConfGroup OBJECT-GROUP 1396 OBJECTS { 1397 hprNodeCpName, 1398 hprUpTime, 1399 hprOperatorPathSwitchSupport 1400 } 1401 STATUS current 1402 DESCRIPTION 1403 "A collection of objects providing the instrumentation of HPR 1404 general information and capabilities." 1406 ::= { hprGroups 1 } 1408 hprAnrRoutingConfGroup OBJECT-GROUP 1409 OBJECTS { 1410 hprAnrsAssigned, 1411 hprAnrCounterState, 1412 hprAnrCounterStateTime, 1413 hprAnrType, 1414 hprAnrOutTgDest, 1415 hprAnrOutTgNum, 1416 hprAnrPacketsReceived, 1417 hprAnrCounterDisconTime 1418 } 1419 STATUS current 1420 DESCRIPTION 1421 "A collection of objects providing instrumentation for the 1422 node's ANR routing." 1424 ::= { hprGroups 2 } 1426 hprTransportUserConfGroup OBJECT-GROUP 1427 OBJECTS { 1428 hprNceType, 1429 hprNceDefault, 1430 hprNceInstanceId 1431 } 1432 STATUS current 1433 DESCRIPTION 1434 "A collection of objects providing information on the users of 1435 the HPR transport known to the node." 1437 ::= { hprGroups 3 } 1439 hprRtpConfGroup OBJECT-GROUP 1440 OBJECTS { 1441 hprRtpGlobeConnSetups, 1442 hprRtpGlobeCtrState, 1443 hprRtpGlobeCtrStateTime, 1444 hprRtpRemCpName, 1445 hprRtpRemNceId, 1446 hprRtpRemTcid, 1447 hprRtpPathSwitchTrigger, 1448 hprRtpRscv, 1449 hprRtpTopic, 1450 hprRtpState, 1451 hprRtpUpTime, 1452 hprRtpLivenessTimer, 1453 hprRtpShortReqTimer, 1454 hprRtpPathSwTimer, 1455 hprRtpLivenessTimeouts, 1456 hprRtpShortReqTimeouts, 1458 hprRtpMaxSendRate, 1459 hprRtpMinSendRate, 1460 hprRtpCurSendRate, 1462 hprRtpSmRdTripDelay, 1464 hprRtpRecvPackets, 1465 hprRtpSendPackets, 1466 hprRtpRecvBytes, 1467 hprRtpSendBytes, 1469 hprRtpRetrPackets, 1470 hprRtpPacketsDiscarded, 1471 hprRtpDetectGaps, 1472 hprRtpRateReqSends, 1474 hprRtpOkErrPathSws, 1475 hprRtpBadErrPathSws, 1476 hprRtpOkOpPathSws, 1477 hprRtpBadOpPathSws, 1478 hprRtpCounterDisconTime, 1480 hprRtpStatusStartTime, 1481 hprRtpStatusEndTime, 1482 hprRtpStatusRemNceId, 1483 hprRtpStatusRemTcid, 1484 hprRtpStatusRemCpName, 1485 hprRtpStatusNewRscv, 1486 hprRtpStatusOldRscv, 1487 hprRtpStatusCause, 1488 hprRtpStatusLastAttemptResult 1490 } 1491 STATUS current 1492 DESCRIPTION 1493 "A collection of objects providing the instrumentation for RTP 1494 connection end points." 1496 ::= { hprGroups 4 } 1498 -- end of conformance statement 1500 END 1501 6. Acknowledgments 1503 This MIB module is the product of the IETF SNA NAU MIB WG and the AIW 1504 APPN/HPR MIBs SIG. Thanks to Ray Bird, IBM Corporation; Jim Cobban, 1505 Nortel; and Laura Petrie, IBM Corporation, for their contributions and 1506 review. 1508 7. References 1510 [1] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. 1511 Waldbusser, "Structure of Management Information for version 2 of 1512 the Simple Network Management Protocol (SNMPv2)", RFC 1902, January 1513 1996. 1515 [2] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. 1516 Waldbusser, "Textual Conventions for Version 2 of the Simple 1517 Network Management Protocol (SNMPv2)", RFC 1903, January 1996. 1519 [3] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. 1520 Waldbusser, "Conformance Statements for Version 2 of the Simple 1521 Network Management Protocol (SNMPv2)", RFC 1904, January 1996. 1523 [4] Clouston, B., and B. Moore, "Definition of Managed Objects for 1524 APPN", Cisco Systems, IBM Corporation, November 1996. 1526 [5] ftp://networking.raleigh.ibm.com/pub/standards/aiw/appn/hpr/hpr6.psbin 1527 8. Security Considerations 1529 Security issues are not discussed in this memo. 1531 9. Authors' Addresses 1533 Bob Clouston 1534 Cisco Systems 1535 7025 Kit Creek Road 1536 P.O. Box 14987 1537 Research Triangle Park, NC 27709, USA 1539 Tel: 1 919 472 2333 1540 E-mail: clouston@cisco.com 1542 Bob Moore 1543 IBM Corporation 1544 800 Park Offices Drive 1545 CNMA/664 1546 P.O. Box 12195 1547 Research Triangle Park, NC 27709, USA 1549 Tel: 1 919 254 4436 1550 E-mail: remoore@ralvm6.vnet.ibm.com 1551 10. Table of Contents 1553 1. Status of this Memo .................................... 1 1554 2. Introduction ........................................... 1 1555 3. The SNMP Network Management Framework .................. 2 1556 4. Overview ............................................... 2 1557 4.1 HPR MIB structure ..................................... 3 1558 5. Definitions ............................................ 6 1559 6. Acknowledgments ........................................ 35 1560 7. References ............................................. 35 1561 8. Security Considerations ................................ 36 1562 9. Author's Addresses ..................................... 36