idnits 2.17.1 draft-ietf-rsvp-mib-04.txt: ** The Abstract section seems to be numbered 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 expiration date. The document expiration date should appear on the first and last page. ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity. ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts. ** The document seems to lack a 1id_guidelines paragraph about the list of Shadow Directories. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an Introduction 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 an Authors' Addresses Section. ** There are 388 instances of weird spacing in the document. Is it really formatted ragged-right, rather than justified? ** There are 6 instances of too long lines in the document, the longest one being 8 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 190 has weird spacing: '...ds that are ...' == Line 192 has weird spacing: '...d Path or r...' == Line 215 has weird spacing: '...ns seen by a...' == Line 248 has weird spacing: '...ndexing purpo...' == Line 257 has weird spacing: '...6 with flow...' == (383 more instances...) -- 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 1996) is 10023 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) -- Missing reference section? '1' on line 2741 looks like a reference -- Missing reference section? '2' on line 2747 looks like a reference -- Missing reference section? '3' on line 2753 looks like a reference Summary: 13 errors (**), 0 flaws (~~), 7 warnings (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Internet Draft RSVP MIB November 1996 4 RSVP Management Information Base 5 draft-ietf-rsvp-mib-04.txt 7 Thu Nov 21 16:08:20 PST 1996 9 Fred Baker 11 Cisco Systems 12 519 Lado Drive 13 Santa Barbara, California 93111 15 fred@cisco.com 17 John Krawczyk 19 Bay Networks, Inc 20 2 Federal Street 21 Billerica, Massachusetts 01821 23 jj@BayNetworks.com 25 1. Status of this Memo 27 This document is an Internet Draft. Internet Drafts are 28 working documents of the Internet Engineering Task Force 29 (IETF), its Areas, and its Working Groups. Note that other 30 groups may also distribute working documents as Internet 31 Drafts. 33 Internet Drafts are draft documents valid for a maximum of six 34 months. Internet Drafts may be updated, replaced, or obsoleted 35 by other documents at any time. It is not appropriate to use 36 Internet Drafts as reference material or to cite them other 37 than as a "working draft" or "work in progress." 39 Please check the I-D abstract listing contained in each 40 Internet Draft directory to learn the current status of this 41 or any other Internet Draft. 43 2. Abstract 45 This memo defines a portion of the Management Information Base 46 (MIB) for use with network management protocols in TCP/IP- 47 based internets. In particular, it defines objects for 48 managing the Resource Reservation Protocol (RSVP) within the 49 interface attributes defined in the Integrated Services Model. 50 Thus, the Integrated Services MIB is directly relevant to and 51 cross-referenced by this MIB. Comments should be made to the 52 RSVP Working Group, rsvp@isi.edu. 54 This memo does not, in its draft form, specify a standard for 55 the Internet community. 57 3. The SNMPv2 Network Management Framework 59 The SNMPv2 Network Management Framework consists of four major 60 components. They are: 62 o RFC 1441 which defines the SMI, the mechanisms used for 63 describing and naming objects for the purpose of 64 management. 66 o RFC 1213 defines MIB-II, the core set of managed objects 67 for the Internet suite of protocols. 69 o RFC 1445 which defines the administrative and other 70 architectural aspects of the framework. 72 o RFC 1448 which defines the protocol used for network 73 access to managed objects. 75 The Framework permits new objects to be defined for the 76 purpose of experimentation and evaluation. 78 3.1. Object Definitions 80 Managed objects are accessed via a virtual information store, 81 termed the Management Information Base or MIB. Objects in the 82 MIB are defined using the subset of Abstract Syntax Notation 83 One (ASN.1) defined in the SMI. In particular, each object 84 type is named by an OBJECT IDENTIFIER, an administratively 85 assigned name. The object type together with an object 86 instance serves to uniquely identify a specific instantiation 87 of the object. For human convenience, we often use a textual 88 string, termed the descriptor, to refer to the object type. 90 4. Overview 92 4.1. Textual Conventions 94 Several new data types are introduced as a textual convention 95 in this MIB document. These textual conventions enhance the 96 readability of the specification and can ease comparison with 97 other specifications if appropriate. It should be noted that 98 the introduction of the these textual conventions has no 99 effect on either the syntax nor the semantics of any managed 100 objects. The use of these is merely an artifact of the 101 explanatory method used. Objects defined in terms of one of 102 these methods are always encoded by means of the rules that 103 define the primitive type. Hence, no changes to the SMI or 104 the SNMP are necessary to accommodate these textual 105 conventions which are adopted merely for the convenience of 106 readers and writers in pursuit of the elusive goal of clear, 107 concise, and unambiguous MIB documents. 109 4.2. Structure of MIB 111 The MIB is composed of the following sections: 112 General Objects 113 Session Statistics Table 114 Session Sender Table 115 Reservation Requests Received Table 116 Reservation Requests Forwarded Table 117 RSVP Interface Attributes Table 118 RSVP Neighbor Table 120 As a general rule, it is difficult in SNMP to describe 121 arbitrarily long of complex messages; this MIB therefore seeks 122 to describe the Path State Database and the Reservation State 123 Database as though each flow and filter description received 124 in an aggregate message had been received in a separate 125 reservation message. 127 Thus, if a RESV message is received for session 128 224.1.2.3+UDP+4455 with two filter/flow spec groups describing 129 a sender 1.2.3.4 and another sender 1.2.7.8, these two will 130 show in the MIB as two separate rows: one for 131 224.1.2.3+UDP+4455 from 1.2.3.4 and the other for 132 224.1.2.3+UDP+4455 from 1.2.7.8. 134 5. Definitions 136 RSVP-MIB DEFINITIONS ::= BEGIN 138 IMPORTS 139 MODULE-IDENTITY, OBJECT-TYPE, Gauge32, 140 Integer32, experimental FROM SNMPv2-SMI 142 TEXTUAL-CONVENTION, TruthValue, RowStatus, TimeStamp, 143 TestAndIncr, TimeInterval FROM SNMPv2-TC 145 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF 146 Port, SessionNumber, SessionType, Protocol, 147 MessageSize, BitRate, BurstSize FROM INTEGRATED-SERVICES-MIB 148 ifIndex, InterfaceIndex FROM IF-MIB; 150 rsvp MODULE-IDENTITY 151 LAST-UPDATED "9611211608Z" -- Thu Nov 21 16:08:20 PST 1996 152 ORGANIZATION "IETF RSVP Working Group" 153 CONTACT-INFO 154 " Fred Baker 155 Postal: Cisco Systems 156 519 Lado Drive 157 Santa Barbara, California 93111 158 Tel: +1 805 681 0115 159 E-Mail: fred@cisco.com 161 John Krawczyk 162 Postal: Bay Networks, Inc 163 2 Federal Street 164 Billerica, Massachusetts 01821 165 Tel: +1 508 916 3811 166 E-Mail: jj@BayNetworks.com" 167 DESCRIPTION 168 "The MIB module to describe the RSVP Protocol" 169 ::= { experimental 71 } 171 rsvpObjects OBJECT IDENTIFIER ::= { rsvp 1 } -- tables 172 rsvpGenObjects OBJECT IDENTIFIER ::= { rsvp 2 } -- global objects 173 rsvpNotifications OBJECT IDENTIFIER ::= { rsvp 3 } -- traps 174 rsvpConformance OBJECT IDENTIFIER ::= { rsvp 4 } -- conformance 175 RsvpEncapsulation ::= TEXTUAL-CONVENTION 176 STATUS current 177 DESCRIPTION 178 "This indicates the encapsulation that an RSVP 179 Neighbor is perceived to be using." 180 SYNTAX INTEGER { 181 ip (1), -- IP Protocol 46 182 udp (2), -- UDP Encapsulation 183 both (3) -- neighbor is using both encapsulations 184 } 186 RefreshInterval ::= TEXTUAL-CONVENTION 187 DISPLAY-HINT "d" 188 STATUS current 189 DESCRIPTION 190 "The number of milliseconds that are expected 191 to elapse between refreshes of path or reserva- 192 tion state. Unrefreshed Path or reservation 193 state is removed after a small multiple of this 194 period." 195 SYNTAX INTEGER (0..'7FFFFFFF'h) 197 QosService ::= TEXTUAL-CONVENTION 198 STATUS current 199 DESCRIPTION 200 "The class of service in use by a flow." 201 SYNTAX INTEGER { 202 guaranteedDelay (2), -- Guaranteed Delay 203 controlledLoad (5) -- Controlled Load 204 } 206 -- The RSVP Session Statistics Database displays statistics 207 -- relating to the number of senders and receivers in each 208 -- session. 210 rsvpSessionTable OBJECT-TYPE 211 SYNTAX SEQUENCE OF RsvpSessionEntry 212 MAX-ACCESS not-accessible 213 STATUS current 214 DESCRIPTION 215 "Statistics concerning the sessions seen by a 216 given system." 217 ::= { rsvpObjects 1 } 219 rsvpSessionEntry OBJECT-TYPE 220 SYNTAX RsvpSessionEntry 221 MAX-ACCESS not-accessible 222 STATUS current 223 DESCRIPTION 224 "Statistics concerning a single RSVP session 225 seen by a given system." 226 INDEX { rsvpSessionNumber } 227 ::= { rsvpSessionTable 1 } 229 RsvpSessionEntry ::= 230 SEQUENCE { 231 rsvpSessionNumber SessionNumber, 232 rsvpSessionType SessionType, 233 rsvpSessionDestAddr OCTET STRING, 234 rsvpSessionDestAddrLength INTEGER, 235 rsvpSessionProtocol Protocol, 236 rsvpSessionPort Port, 237 rsvpSessionSenders Gauge32, 238 rsvpSessionReceivers Gauge32, 239 rsvpSessionRequests Gauge32 240 } 242 rsvpSessionNumber OBJECT-TYPE 243 SYNTAX SessionNumber 244 MAX-ACCESS not-accessible 245 STATUS current 246 DESCRIPTION 247 "The number of this session. This is for SNMP 248 Indexing purposes only and has no relation to 249 any protocol value." 250 ::= { rsvpSessionEntry 1 } 252 rsvpSessionType OBJECT-TYPE 253 SYNTAX SessionType 254 MAX-ACCESS read-only 255 STATUS current 256 DESCRIPTION 257 "The type of session (IP4, IP6, IP6 with flow 258 information, etc)." 259 ::= { rsvpSessionEntry 2 } 261 rsvpSessionDestAddr OBJECT-TYPE 262 SYNTAX OCTET STRING (SIZE(4..16)) 263 MAX-ACCESS read-only 264 STATUS current 265 DESCRIPTION 266 "The destination address used by all senders in 267 this session. This object may not be changed 268 when the value of the RowStatus object is 269 'valid'." 270 ::= { rsvpSessionEntry 3 } 272 rsvpSessionDestAddrLength OBJECT-TYPE 273 SYNTAX INTEGER(0..128) 274 MAX-ACCESS read-only 275 STATUS current 276 DESCRIPTION 277 "The CIDR prefix length of the session address, 278 which is 32 for IP4 host and multicast ad- 279 dresses. This object may not be changed when 280 the value of the RowStatus object is 'valid'." 281 ::= { rsvpSessionEntry 4 } 283 rsvpSessionProtocol OBJECT-TYPE 284 SYNTAX Protocol 285 MAX-ACCESS read-only 286 STATUS current 287 DESCRIPTION 288 "The IP Protocol used by this session. This 289 object may not be changed when the value of the 290 RowStatus object is 'valid'." 291 ::= { rsvpSessionEntry 5 } 293 rsvpSessionPort OBJECT-TYPE 294 SYNTAX Port 295 MAX-ACCESS read-only 296 STATUS current 297 DESCRIPTION 298 "The UDP or TCP port number used as a destina- 299 tion port for all senders in this session. If 300 the IP protocol in use, specified by rsvpSen- 301 derProtocol, is 50 (ESP) or 51 (AH), this 302 represents a virtual destination port number. 303 A value of zero indicates that the IP protocol 304 in use does not have ports. This object may 305 not be changed when the value of the RowStatus 306 object is 'valid'." 307 ::= { rsvpSessionEntry 6 } 309 rsvpSessionSenders OBJECT-TYPE 310 SYNTAX Gauge32 311 MAX-ACCESS read-only 312 STATUS current 313 DESCRIPTION 314 "The number of senders currently known to be 315 part of this session." 316 ::= { rsvpSessionEntry 7 } 318 rsvpSessionReceivers OBJECT-TYPE 319 SYNTAX Gauge32 320 MAX-ACCESS read-only 321 STATUS current 322 DESCRIPTION 323 "The number of reservations being requested of 324 this system for this session." 325 ::= { rsvpSessionEntry 8 } 327 rsvpSessionRequests OBJECT-TYPE 328 SYNTAX Gauge32 329 MAX-ACCESS read-only 330 STATUS current 331 DESCRIPTION 332 "The number of reservation requests this system 333 is sending upstream for this session." 334 ::= { rsvpSessionEntry 9 } 336 -- The RSVP Session Sender Database contains the information 337 -- displayed by senders regarding their potential contribution 338 -- to session data content. It is in essence a list of the 339 -- valid PATH messages that the RSVP Router or Host is receiving. 341 rsvpSenderNewIndex OBJECT-TYPE 342 SYNTAX TestAndIncr 343 MAX-ACCESS read-write 344 STATUS current 345 DESCRIPTION 346 "This object is used to assign values to 347 rsvpSenderNumber as described in 'Textual Con- 348 ventions for SNMPv2'. The network manager 349 reads the object, and then writes the value 350 back in the SET that creates a new instance of 351 rsvpSenderEntry. If the SET fails with the 352 code 'inconsistentValue', then the process must 353 be repeated; If the SET succeeds, then the ob- 354 ject is incremented, and the new instance is 355 created according to the manager's directions." 356 ::= { rsvpGenObjects 2 } 358 rsvpSenderTable OBJECT-TYPE 359 SYNTAX SEQUENCE OF RsvpSenderEntry 360 MAX-ACCESS not-accessible 361 STATUS current 362 DESCRIPTION 363 "Information describing the state information 364 displayed by senders in PATH messages." 365 ::= { rsvpObjects 2 } 367 rsvpSenderEntry OBJECT-TYPE 368 SYNTAX RsvpSenderEntry 369 MAX-ACCESS not-accessible 370 STATUS current 371 DESCRIPTION 372 "Information describing the state information 373 displayed by a single sender's PATH message." 374 INDEX { rsvpSessionNumber, rsvpSenderNumber } 375 ::= { rsvpSenderTable 1 } 377 RsvpSenderEntry ::= 378 SEQUENCE { 379 rsvpSenderNumber SessionNumber, 380 rsvpSenderType SessionType, 381 rsvpSenderDestAddr OCTET STRING, 382 rsvpSenderAddr OCTET STRING, 383 rsvpSenderDestAddrLength INTEGER, 384 rsvpSenderAddrLength INTEGER, 385 rsvpSenderProtocol Protocol, 386 rsvpSenderDestPort Port, 387 rsvpSenderPort Port, 388 rsvpSenderHopAddr OCTET STRING, 389 rsvpSenderHopLih Integer32, 390 rsvpSenderInterface InterfaceIndex, 391 rsvpSenderTSpecRate BitRate, 392 rsvpSenderTSpecPeakRate BitRate, 393 rsvpSenderTSpecBurst BurstSize, 394 rsvpSenderTSpecMinTU MessageSize, 395 rsvpSenderTSpecMaxTU MessageSize, 396 rsvpSenderInterval RefreshInterval, 397 rsvpSenderRSVPHop TruthValue, 398 rsvpSenderLastChange TimeStamp, 399 rsvpSenderPolicy OCTET STRING, 400 rsvpSenderAdspecBreak TruthValue, 401 rsvpSenderAdspecHopCount INTEGER, 402 rsvpSenderAdspecPathBw BitRate, 403 rsvpSenderAdspecMinLatency Integer32, 404 rsvpSenderAdspecMtu INTEGER, 405 rsvpSenderAdspecGuaranteedSvc TruthValue, 406 rsvpSenderAdspecGuaranteedBreak TruthValue, 407 rsvpSenderAdspecGuaranteedCtot Integer32, 408 rsvpSenderAdspecGuaranteedDtot Integer32, 409 rsvpSenderAdspecGuaranteedCsum Integer32, 410 rsvpSenderAdspecGuaranteedDsum Integer32, 411 rsvpSenderAdspecGuaranteedHopCount INTEGER, 412 rsvpSenderAdspecGuaranteedPathBw BitRate, 413 rsvpSenderAdspecGuaranteedMinLatency Integer32, 414 rsvpSenderAdspecGuaranteedMtu INTEGER, 415 rsvpSenderAdspecCtrlLoadSvc TruthValue, 416 rsvpSenderAdspecCtrlLoadBreak TruthValue, 417 rsvpSenderAdspecCtrlLoadHopCount INTEGER, 418 rsvpSenderAdspecCtrlLoadPathBw BitRate, 419 rsvpSenderAdspecCtrlLoadMinLatency Integer32, 420 rsvpSenderAdspecCtrlLoadMtu INTEGER, 421 rsvpSenderStatus RowStatus 422 } 423 rsvpSenderNumber OBJECT-TYPE 424 SYNTAX SessionNumber 425 MAX-ACCESS not-accessible 426 STATUS current 427 DESCRIPTION 428 "The number of this sender. This is for SNMP 429 Indexing purposes only and has no relation to 430 any protocol vaalue." 431 ::= { rsvpSenderEntry 1 } 433 rsvpSenderType OBJECT-TYPE 434 SYNTAX SessionType 435 MAX-ACCESS read-create 436 STATUS current 437 DESCRIPTION 438 "The type of session (IP4, IP6, IP6 with flow 439 information, etc)." 440 ::= { rsvpSenderEntry 2 } 442 rsvpSenderDestAddr OBJECT-TYPE 443 SYNTAX OCTET STRING (SIZE(4..16)) 444 MAX-ACCESS read-create 445 STATUS current 446 DESCRIPTION 447 "The destination address used by all senders in 448 this session. This object may not be changed 449 when the value of the RowStatus object is 450 'valid'." 451 ::= { rsvpSenderEntry 3 } 453 rsvpSenderAddr OBJECT-TYPE 454 SYNTAX OCTET STRING (SIZE(4..16)) 455 MAX-ACCESS read-create 456 STATUS current 457 DESCRIPTION 458 "The source address used by this sender in this 459 session. This object may not be changed when 460 the value of the RowStatus object is 'valid'." 461 ::= { rsvpSenderEntry 4 } 463 rsvpSenderDestAddrLength OBJECT-TYPE 464 SYNTAX INTEGER(0..128) 465 MAX-ACCESS read-create 466 STATUS current 467 DESCRIPTION 468 "The length of the destination address in bits. 469 This is the CIDR Prefix Length, which for IP4 470 hosts and multicast addresses is 32 bits. This 471 object may not be changed when the value of the 472 RowStatus object is 'valid'." 473 ::= { rsvpSenderEntry 5 } 475 rsvpSenderAddrLength OBJECT-TYPE 476 SYNTAX INTEGER(0..128) 477 MAX-ACCESS read-create 478 STATUS current 479 DESCRIPTION 480 "The length of the sender's address in bits. 481 This is the CIDR Prefix Length, which for IP4 482 hosts and multicast addresses is 32 bits. This 483 object may not be changed when the value of the 484 RowStatus object is 'valid'." 485 ::= { rsvpSenderEntry 6 } 487 rsvpSenderProtocol OBJECT-TYPE 488 SYNTAX Protocol 489 MAX-ACCESS read-create 490 STATUS current 491 DESCRIPTION 492 "The IP Protocol used by this session. This 493 object may not be changed when the value of the 494 RowStatus object is 'valid'." 495 ::= { rsvpSenderEntry 7 } 497 rsvpSenderDestPort OBJECT-TYPE 498 SYNTAX Port 499 MAX-ACCESS read-create 500 STATUS current 501 DESCRIPTION 502 "The UDP or TCP port number used as a destina- 503 tion port for all senders in this session. If 504 the IP protocol in use, specified by rsvpSen- 505 derProtocol, is 50 (ESP) or 51 (AH), this 506 represents a virtual destination port number. 507 A value of zero indicates that the IP protocol 508 in use does not have ports. This object may 509 not be changed when the value of the RowStatus 510 object is 'valid'." 511 ::= { rsvpSenderEntry 8 } 513 rsvpSenderPort OBJECT-TYPE 514 SYNTAX Port 515 MAX-ACCESS read-create 516 STATUS current 517 DESCRIPTION 518 "The UDP or TCP port number used as a source 519 port for this sender in this session. If the 520 IP protocol in use, specified by rsvpSenderPro- 521 tocol is 50 (ESP) or 51 (AH), this represents a 522 generalized port identifier (GPI). A value of 523 zero indicates that the IP protocol in use does 524 not have ports. This object may not be changed 525 when the value of the RowStatus object is 526 'valid'." 527 ::= { rsvpSenderEntry 9 } 529 rsvpSenderHopAddr OBJECT-TYPE 530 SYNTAX OCTET STRING (SIZE(4..16)) 531 MAX-ACCESS read-create 532 STATUS current 533 DESCRIPTION 534 "The address used by the previous RSVP hop 535 (which may be the original sender)." 536 ::= { rsvpSenderEntry 10 } 538 rsvpSenderHopLih OBJECT-TYPE 539 SYNTAX Integer32 540 MAX-ACCESS read-create 541 STATUS current 542 DESCRIPTION 543 "The Logical Interface Handle used by the pre- 544 vious RSVP hop (which may be the original 545 sender)." 546 ::= { rsvpSenderEntry 11 } 548 rsvpSenderInterface OBJECT-TYPE 549 SYNTAX InterfaceIndex 550 MAX-ACCESS read-create 551 STATUS current 552 DESCRIPTION 553 "The ifIndex value of the interface on which 554 this PATH message was most recently received." 555 ::= { rsvpSenderEntry 12 } 557 rsvpSenderTSpecRate OBJECT-TYPE 558 SYNTAX BitRate 559 UNITS "bits per second" 560 MAX-ACCESS read-create 561 STATUS current 562 DESCRIPTION 563 "The Average Bit Rate of the sender's data 564 stream. Within a transmission burst, the ar- 565 rival rate may be as fast as rsvpSenderTSpec- 566 PeakRate (if supported by the service model); 567 however, averaged across two or more burst in- 568 tervals, the rate should not exceed rsvpSen- 569 derTSpecRate. 571 Note that this is a prediction, often based on 572 the general capability of a type of codec or 573 particular encoding; the measured average rate 574 may be significantly lower." 575 ::= { rsvpSenderEntry 13 } 577 rsvpSenderTSpecPeakRate OBJECT-TYPE 578 SYNTAX BitRate 579 UNITS "bits per second" 580 MAX-ACCESS read-create 581 STATUS current 582 DESCRIPTION 583 "The Peak Bit Rate of the sender's data stream. 584 Traffic arrival is not expected to exceed this 585 rate at any time, apart from the effects of 586 jitter in the network. If not specified in the 587 TSpec, this returns zero or noSuchValue." 588 ::= { rsvpSenderEntry 14 } 590 rsvpSenderTSpecBurst OBJECT-TYPE 591 SYNTAX BurstSize 592 UNITS "bytes" 593 MAX-ACCESS read-create 594 STATUS current 595 DESCRIPTION 596 "The size of the largest burst expected from 597 the sender at a time." 598 ::= { rsvpSenderEntry 15 } 600 rsvpSenderTSpecMinTU OBJECT-TYPE 601 SYNTAX MessageSize 602 MAX-ACCESS read-create 603 STATUS current 604 DESCRIPTION 605 "The minimum message size for this flow. The 606 policing algorithm will treat smaller messages 607 as though they are this size." 608 ::= { rsvpSenderEntry 16 } 610 rsvpSenderTSpecMaxTU OBJECT-TYPE 611 SYNTAX MessageSize 612 MAX-ACCESS read-create 613 STATUS current 614 DESCRIPTION 615 "The maximum message size for this flow. The 616 admission algorithm will reject TSpecs whose 617 Maximum Transmission Unit, plus the interface 618 headers, exceed the interface MTU." 619 ::= { rsvpSenderEntry 17 } 621 rsvpSenderInterval OBJECT-TYPE 622 SYNTAX RefreshInterval 623 MAX-ACCESS read-create 624 STATUS current 625 DESCRIPTION 626 "The interval between refresh messages as ad- 627 vertised by the Previous Hop." 628 ::= { rsvpSenderEntry 18 } 630 rsvpSenderRSVPHop OBJECT-TYPE 631 SYNTAX TruthValue 632 MAX-ACCESS read-create 633 STATUS current 634 DESCRIPTION 635 "If TRUE, the node believes that the previous 636 IP hop is an RSVP hop. If FALSE, the node be- 637 lieves that the previous IP hop may not be an 638 RSVP hop." 639 ::= { rsvpSenderEntry 19 } 641 rsvpSenderLastChange OBJECT-TYPE 642 SYNTAX TimeStamp 643 MAX-ACCESS read-only 644 STATUS current 645 DESCRIPTION 646 "The time of the last change in this PATH mes- 647 sage; This is either the first time it was re- 648 ceived or the time of the most recent change in 649 parameters." 650 ::= { rsvpSenderEntry 20 } 652 rsvpSenderPolicy OBJECT-TYPE 653 SYNTAX OCTET STRING (SIZE(4..65536)) 654 MAX-ACCESS read-create 655 STATUS current 656 DESCRIPTION 657 "The contents of the policy object, displayed 658 as an uninterpreted string of octets, including 659 the object header. In the absence of such an 660 object, this should be of zero length." 661 ::= { rsvpSenderEntry 21 } 663 rsvpSenderAdspecBreak OBJECT-TYPE 664 SYNTAX TruthValue 665 MAX-ACCESS read-create 666 STATUS current 667 DESCRIPTION 668 "The global break bit general characterization 669 parameter from the ADSPEC. If TRUE, at least 670 one non-IS hop was detected in the path. If 671 FALSE, no non-IS hops were detected." 672 ::= { rsvpSenderEntry 22 } 674 rsvpSenderAdspecHopCount OBJECT-TYPE 675 SYNTAX INTEGER (0..65535) 676 MAX-ACCESS read-create 677 STATUS current 678 DESCRIPTION 679 "The hop count general characterization parame- 680 ter from the ADSPEC. A return of zero or 681 noSuchValue indicates one of the following con- 682 ditions: 684 the invalid bit was set 685 the parameter was not present" 686 ::= { rsvpSenderEntry 23 } 688 rsvpSenderAdspecPathBw OBJECT-TYPE 689 SYNTAX BitRate 690 UNITS "bits per second" 691 MAX-ACCESS read-create 692 STATUS current 693 DESCRIPTION 694 "The path bandwidth estimate general character- 695 ization parameter from the ADSPEC. A return of 696 zero or noSuchValue indicates one of the fol- 697 lowing conditions: 699 the invalid bit was set 700 the parameter was not present" 701 ::= { rsvpSenderEntry 24 } 703 rsvpSenderAdspecMinLatency OBJECT-TYPE 704 SYNTAX Integer32 705 UNITS "microseconds" 706 MAX-ACCESS read-create 707 STATUS current 708 DESCRIPTION 709 "The minimum path latency general characteriza- 710 tion parameter from the ADSPEC. A return of 711 zero or noSuchValue indicates one of the fol- 712 lowing conditions: 714 the invalid bit was set 715 the parameter was not present" 716 ::= { rsvpSenderEntry 25 } 718 rsvpSenderAdspecMtu OBJECT-TYPE 719 SYNTAX INTEGER (0..65535) 720 UNITS "bytes" 721 MAX-ACCESS read-create 722 STATUS current 723 DESCRIPTION 724 "The composed Maximum Transmission Unit general 725 characterization parameter from the ADSPEC. A 726 return of zero or noSuchValue indicates one of 727 the following conditions: 729 the invalid bit was set 730 the parameter was not present" 731 ::= { rsvpSenderEntry 26 } 733 rsvpSenderAdspecGuaranteedSvc OBJECT-TYPE 734 SYNTAX TruthValue 735 MAX-ACCESS read-create 736 STATUS current 737 DESCRIPTION 738 "If TRUE, the ADSPEC contains a Guaranteed Ser- 739 vice fragment. If FALSE, the ADSPEC does not 740 contain a Guaranteed Service fragment." 741 ::= { rsvpSenderEntry 27 } 743 rsvpSenderAdspecGuaranteedBreak OBJECT-TYPE 744 SYNTAX TruthValue 745 MAX-ACCESS read-create 746 STATUS current 747 DESCRIPTION 748 "If TRUE, the Guaranteed Service fragment has 749 its 'break' bit set, indicating that one or 750 more nodes along the path do not support the 751 guaranteed service. If FALSE, and rsvpSen- 752 derAdspecGuaranteedSvc is TRUE, the 'break' bit 753 is not set. 755 If rsvpSenderAdspecGuaranteedSvc is FALSE, this 756 returns FALSE or noSuchValue." 757 ::= { rsvpSenderEntry 28 } 759 rsvpSenderAdspecGuaranteedCtot OBJECT-TYPE 760 SYNTAX Integer32 761 UNITS "bytes" 762 MAX-ACCESS read-create 763 STATUS current 764 DESCRIPTION 766 "If rsvpSenderAdspecGuaranteedSvc is TRUE, this 767 is the end-to-end composed value for the 768 guaranteed service 'C' parameter. A return of 769 zero or noSuchValue indicates one of the fol- 770 lowing conditions: 772 the invalid bit was set 773 the parameter was not present 775 If rsvpSenderAdspecGuaranteedSvc is FALSE, this 776 returns zero or noSuchValue." 777 ::= { rsvpSenderEntry 29 } 779 rsvpSenderAdspecGuaranteedDtot OBJECT-TYPE 780 SYNTAX Integer32 781 UNITS "microseconds" 782 MAX-ACCESS read-create 783 STATUS current 784 DESCRIPTION 785 "If rsvpSenderAdspecGuaranteedSvc is TRUE, this 786 is the end-to-end composed value for the 787 guaranteed service 'D' parameter. A return of 788 zero or noSuchValue indicates one of the fol- 789 lowing conditions: 791 the invalid bit was set 792 the parameter was not present 794 If rsvpSenderAdspecGuaranteedSvc is FALSE, this 795 returns zero or noSuchValue." 796 ::= { rsvpSenderEntry 30 } 798 rsvpSenderAdspecGuaranteedCsum OBJECT-TYPE 799 SYNTAX Integer32 800 UNITS "bytes" 801 MAX-ACCESS read-create 802 STATUS current 803 DESCRIPTION 804 "If rsvpSenderAdspecGuaranteedSvc is TRUE, this 805 is the composed value for the guaranteed ser- 806 vice 'C' parameter since the last reshaping 807 point. A return of zero or noSuchValue indi- 808 cates one of the following conditions: 810 the invalid bit was set 811 the parameter was not present 813 If rsvpSenderAdspecGuaranteedSvc is FALSE, this 814 returns zero or noSuchValue." 815 ::= { rsvpSenderEntry 31 } 817 rsvpSenderAdspecGuaranteedDsum OBJECT-TYPE 818 SYNTAX Integer32 819 UNITS "microseconds" 820 MAX-ACCESS read-create 821 STATUS current 822 DESCRIPTION 823 "If rsvpSenderAdspecGuaranteedSvc is TRUE, this 824 is the composed value for the guaranteed ser- 825 vice 'D' parameter since the last reshaping 826 point. A return of zero or noSuchValue indi- 827 cates one of the following conditions: 829 the invalid bit was set 830 the parameter was not present 832 If rsvpSenderAdspecGuaranteedSvc is FALSE, this 833 returns zero or noSuchValue." 834 ::= { rsvpSenderEntry 32 } 836 rsvpSenderAdspecGuaranteedHopCount OBJECT-TYPE 837 SYNTAX INTEGER (0..65535) 838 MAX-ACCESS read-create 839 STATUS current 840 DESCRIPTION 842 "If rsvpSenderAdspecGuaranteedSvc is TRUE, this 843 is the service-specific override of the hop 844 count general characterization parameter from 845 the ADSPEC. A return of zero or noSuchValue 846 indicates one of the following conditions: 848 the invalid bit was set 849 the parameter was not present 851 If rsvpSenderAdspecGuaranteedSvc is FALSE, this 852 returns zero or noSuchValue." 853 ::= { rsvpSenderEntry 33 } 855 rsvpSenderAdspecGuaranteedPathBw OBJECT-TYPE 856 SYNTAX BitRate 857 UNITS "bits per second" 858 MAX-ACCESS read-create 859 STATUS current 860 DESCRIPTION 861 "If rsvpSenderAdspecGuaranteedSvc is TRUE, this 862 is the service-specific override of the path 863 bandwidth estimate general characterization 864 parameter from the ADSPEC. A return of zero or 865 noSuchValue indicates one of the following con- 866 ditions: 868 the invalid bit was set 869 the parameter was not present 871 If rsvpSenderAdspecGuaranteedSvc is FALSE, this 872 returns zero or noSuchValue." 873 ::= { rsvpSenderEntry 34 } 875 rsvpSenderAdspecGuaranteedMinLatency OBJECT-TYPE 876 SYNTAX Integer32 877 UNITS "microseconds" 878 MAX-ACCESS read-create 879 STATUS current 880 DESCRIPTION 881 "If rsvpSenderAdspecGuaranteedSvc is TRUE, this 882 is the service-specific override of the minimum 883 path latency general characterization parameter 884 from the ADSPEC. A return of zero or noSuch- 885 Value indicates one of the following condi- 886 tions: 888 the invalid bit was set 889 the parameter was not present 891 If rsvpSenderAdspecGuaranteedSvc is FALSE, this 892 returns zero or noSuchValue." 893 ::= { rsvpSenderEntry 35 } 895 rsvpSenderAdspecGuaranteedMtu OBJECT-TYPE 896 SYNTAX INTEGER (0..65535) 897 UNITS "bytes" 898 MAX-ACCESS read-create 899 STATUS current 900 DESCRIPTION 901 "If rsvpSenderAdspecGuaranteedSvc is TRUE, this 902 is the service-specific override of the com- 903 posed Maximum Transmission Unit general charac- 904 terization parameter from the ADSPEC. A return 905 of zero or noSuchValue indicates one of the 906 following conditions: 908 the invalid bit was set 909 the parameter was not present 911 If rsvpSenderAdspecGuaranteedSvc is FALSE, this 912 returns zero or noSuchValue." 913 ::= { rsvpSenderEntry 36 } 915 rsvpSenderAdspecCtrlLoadSvc OBJECT-TYPE 916 SYNTAX TruthValue 917 MAX-ACCESS read-create 918 STATUS current 919 DESCRIPTION 920 "If TRUE, the ADSPEC contains a Controlled Load 921 Service fragment. If FALSE, the ADSPEC does 922 not contain a Controlled Load Service frag- 923 ment." 924 ::= { rsvpSenderEntry 37 } 926 rsvpSenderAdspecCtrlLoadBreak OBJECT-TYPE 927 SYNTAX TruthValue 928 MAX-ACCESS read-create 929 STATUS current 930 DESCRIPTION 931 "If TRUE, the Controlled Load Service fragment 932 has its 'break' bit set, indicating that one or 933 more nodes along the path do not support the 934 controlled load service. If FALSE, and 935 rsvpSenderAdspecCtrlLoadSvc is TRUE, the 936 'break' bit is not set. 938 If rsvpSenderAdspecCtrlLoadSvc is FALSE, this 939 returns FALSE or noSuchValue." 940 ::= { rsvpSenderEntry 38 } 942 rsvpSenderAdspecCtrlLoadHopCount OBJECT-TYPE 943 SYNTAX INTEGER (0..65535) 944 MAX-ACCESS read-create 945 STATUS current 946 DESCRIPTION 948 "If rsvpSenderAdspecCtrlLoadSvc is TRUE, this 949 is the service-specific override of the hop 950 count general characterization parameter from 951 the ADSPEC. A return of zero or noSuchValue 952 indicates one of the following conditions: 954 the invalid bit was set 955 the parameter was not present 957 If rsvpSenderAdspecCtrlLoadSvc is FALSE, this 958 returns zero or noSuchValue." 959 ::= { rsvpSenderEntry 39 } 961 rsvpSenderAdspecCtrlLoadPathBw OBJECT-TYPE 962 SYNTAX BitRate 963 UNITS "bits per second" 964 MAX-ACCESS read-create 965 STATUS current 966 DESCRIPTION 967 "If rsvpSenderAdspecCtrlLoadSvc is TRUE, this 968 is the service-specific override of the path 969 bandwidth estimate general characterization 970 parameter from the ADSPEC. A return of zero or 971 noSuchValue indicates one of the following con- 972 ditions: 974 the invalid bit was set 975 the parameter was not present 977 If rsvpSenderAdspecCtrlLoadSvc is FALSE, this 978 returns zero or noSuchValue." 979 ::= { rsvpSenderEntry 40 } 981 rsvpSenderAdspecCtrlLoadMinLatency OBJECT-TYPE 982 SYNTAX Integer32 983 UNITS "microseconds" 984 MAX-ACCESS read-create 985 STATUS current 986 DESCRIPTION 987 "If rsvpSenderAdspecCtrlLoadSvc is TRUE, this 988 is the service-specific override of the minimum 989 path latency general characterization parameter 990 from the ADSPEC. A return of zero or noSuch- 991 Value indicates one of the following condi- 992 tions: 994 the invalid bit was set 995 the parameter was not present 997 If rsvpSenderAdspecCtrlLoadSvc is FALSE, this 998 returns zero or noSuchValue." 999 ::= { rsvpSenderEntry 41 } 1001 rsvpSenderAdspecCtrlLoadMtu OBJECT-TYPE 1002 SYNTAX INTEGER (0..65535) 1003 UNITS "bytes" 1004 MAX-ACCESS read-create 1005 STATUS current 1006 DESCRIPTION 1007 "If rsvpSenderAdspecCtrlLoadSvc is TRUE, this 1008 is the service-specific override of the com- 1009 posed Maximum Transmission Unit general charac- 1010 terization parameter from the ADSPEC. A return 1011 of zero or noSuchValue indicates one of the 1012 following conditions: 1014 the invalid bit was set 1015 the parameter was not present 1017 If rsvpSenderAdspecCtrlLoadSvc is FALSE, this 1018 returns zero or noSuchValue." 1019 ::= { rsvpSenderEntry 42 } 1021 rsvpSenderStatus OBJECT-TYPE 1022 SYNTAX RowStatus 1023 MAX-ACCESS read-create 1024 STATUS current 1025 DESCRIPTION 1026 "'valid' for all active PATH messages. This 1027 object may be used to install static PATH in- 1028 formation or delete PATH information." 1029 ::= { rsvpSenderEntry 43 } 1031 -- The RSVP Reservation Requests Received Table contains the 1032 -- information displayed by receivers regarding their needs with 1033 -- respect to sessions and senders. It is in essence a list of the 1034 -- valid RESV messages that the RSVP Router or Host is receiving. 1036 rsvpResvNewIndex OBJECT-TYPE 1037 SYNTAX TestAndIncr 1038 MAX-ACCESS read-write 1039 STATUS current 1040 DESCRIPTION 1041 "This object is used to assign values to 1042 rsvpResvNumber as described in 'Textual Conven- 1043 tions for SNMPv2'. The network manager reads 1044 the object, and then writes the value back in 1045 the SET that creates a new instance of 1046 rsvpResvEntry. If the SET fails with the code 1047 'inconsistentValue', then the process must be 1048 repeated; If the SET succeeds, then the object 1049 is incremented, and the new instance is created 1050 according to the manager's directions." 1051 ::= { rsvpGenObjects 3 } 1053 rsvpResvTable OBJECT-TYPE 1054 SYNTAX SEQUENCE OF RsvpResvEntry 1055 MAX-ACCESS not-accessible 1056 STATUS current 1057 DESCRIPTION 1058 "Information describing the state information 1059 displayed by receivers in RESV messages." 1060 ::= { rsvpObjects 3 } 1062 rsvpResvEntry OBJECT-TYPE 1063 SYNTAX RsvpResvEntry 1064 MAX-ACCESS not-accessible 1065 STATUS current 1066 DESCRIPTION 1067 "Information describing the state information 1068 displayed by a single receiver's RESV message 1069 concerning a single sender." 1070 INDEX { rsvpSessionNumber, rsvpResvNumber } 1071 ::= { rsvpResvTable 1 } 1073 RsvpResvEntry ::= 1074 SEQUENCE { 1075 rsvpResvNumber SessionNumber, 1076 rsvpResvType SessionType, 1077 rsvpResvDestAddr OCTET STRING, 1078 rsvpResvSenderAddr OCTET STRING, 1079 rsvpResvDestAddrLength INTEGER, 1080 rsvpResvSenderAddrLength INTEGER, 1081 rsvpResvProtocol Protocol, 1082 rsvpResvDestPort Port, 1083 rsvpResvPort Port, 1084 rsvpResvHopAddr OCTET STRING, 1085 rsvpResvHopLih Integer32, 1086 rsvpResvInterface InterfaceIndex, 1087 rsvpResvService QosService, 1088 rsvpResvTSpecRate BitRate, 1089 rsvpResvTSpecPeakRate BitRate, 1090 rsvpResvTSpecBurst BurstSize, 1091 rsvpResvTSpecMinTU MessageSize, 1092 rsvpResvTSpecMaxTU MessageSize, 1093 rsvpResvRSpecRate BitRate, 1094 rsvpResvRSpecSlack Integer32, 1095 rsvpResvInterval RefreshInterval, 1096 rsvpResvScope OCTET STRING, 1097 rsvpResvShared TruthValue, 1098 rsvpResvExplicit TruthValue, 1099 rsvpResvRSVPHop TruthValue, 1100 rsvpResvLastChange TimeStamp, 1101 rsvpResvPolicy OCTET STRING, 1102 rsvpResvStatus RowStatus 1103 } 1105 rsvpResvNumber OBJECT-TYPE 1106 SYNTAX SessionNumber 1107 MAX-ACCESS not-accessible 1108 STATUS current 1109 DESCRIPTION 1110 "The number of this reservation request. This 1111 is for SNMP Indexing purposes only and has no 1112 relation to any protocol value." 1113 ::= { rsvpResvEntry 1 } 1115 rsvpResvType OBJECT-TYPE 1116 SYNTAX SessionType 1117 MAX-ACCESS read-create 1118 STATUS current 1119 DESCRIPTION 1120 "The type of session (IP4, IP6, IP6 with flow 1121 information, etc)." 1122 ::= { rsvpResvEntry 2 } 1124 rsvpResvDestAddr OBJECT-TYPE 1125 SYNTAX OCTET STRING (SIZE(4..16)) 1126 MAX-ACCESS read-create 1127 STATUS current 1128 DESCRIPTION 1129 "The destination address used by all senders in 1130 this session. This object may not be changed 1131 when the value of the RowStatus object is 1132 'valid'." 1133 ::= { rsvpResvEntry 3 } 1135 rsvpResvSenderAddr OBJECT-TYPE 1136 SYNTAX OCTET STRING (SIZE(4..16)) 1137 MAX-ACCESS read-create 1138 STATUS current 1139 DESCRIPTION 1140 "The source address of the sender selected by 1141 this reservation. The value of all zeroes in- 1142 dicates 'all senders'. This object may not be 1143 changed when the value of the RowStatus object 1144 is 'valid'." 1145 ::= { rsvpResvEntry 4 } 1147 rsvpResvDestAddrLength OBJECT-TYPE 1148 SYNTAX INTEGER(0..128) 1149 MAX-ACCESS read-create 1150 STATUS current 1151 DESCRIPTION 1152 "The length of the destination address in bits. 1153 This is the CIDR Prefix Length, which for IP4 1154 hosts and multicast addresses is 32 bits. This 1155 object may not be changed when the value of the 1156 RowStatus object is 'valid'." 1157 ::= { rsvpResvEntry 5 } 1159 rsvpResvSenderAddrLength OBJECT-TYPE 1160 SYNTAX INTEGER(0..128) 1161 MAX-ACCESS read-create 1162 STATUS current 1163 DESCRIPTION 1164 "The length of the sender's address in bits. 1165 This is the CIDR Prefix Length, which for IP4 1166 hosts and multicast addresses is 32 bits. This 1167 object may not be changed when the value of the 1168 RowStatus object is 'valid'." 1169 ::= { rsvpResvEntry 6 } 1171 rsvpResvProtocol OBJECT-TYPE 1172 SYNTAX Protocol 1173 MAX-ACCESS read-create 1174 STATUS current 1175 DESCRIPTION 1176 "The IP Protocol used by this session. This 1177 object may not be changed when the value of the 1178 RowStatus object is 'valid'." 1179 ::= { rsvpResvEntry 7 } 1181 rsvpResvDestPort OBJECT-TYPE 1182 SYNTAX Port 1183 MAX-ACCESS read-create 1184 STATUS current 1185 DESCRIPTION 1186 "The UDP or TCP port number used as a destina- 1187 tion port for all senders in this session. If 1188 the IP protocol in use, specified by 1189 rsvpResvProtocol, is 50 (ESP) or 51 (AH), this 1190 represents a virtual destination port number. 1191 A value of zero indicates that the IP protocol 1192 in use does not have ports. This object may 1193 not be changed when the value of the RowStatus 1194 object is 'valid'." 1195 ::= { rsvpResvEntry 8 } 1197 rsvpResvPort OBJECT-TYPE 1198 SYNTAX Port 1199 MAX-ACCESS read-create 1200 STATUS current 1201 DESCRIPTION 1202 "The UDP or TCP port number used as a source 1203 port for this sender in this session. If the 1204 IP protocol in use, specified by rsvpResvProto- 1205 col is 50 (ESP) or 51 (AH), this represents a 1206 generalized port identifier (GPI). A value of 1207 zero indicates that the IP protocol in use does 1208 not have ports. This object may not be changed 1209 when the value of the RowStatus object is 1210 'valid'." 1211 ::= { rsvpResvEntry 9 } 1213 rsvpResvHopAddr OBJECT-TYPE 1214 SYNTAX OCTET STRING (SIZE(4..16)) 1215 MAX-ACCESS read-create 1216 STATUS current 1217 DESCRIPTION 1218 "The address used by the next RSVP hop (which 1219 may be the ultimate receiver)." 1220 ::= { rsvpResvEntry 10 } 1222 rsvpResvHopLih OBJECT-TYPE 1223 SYNTAX Integer32 1224 MAX-ACCESS read-create 1225 STATUS current 1226 DESCRIPTION 1227 "The Logical Interface Handle received from the 1228 previous RSVP hop (which may be the ultimate 1229 receiver)." 1230 ::= { rsvpResvEntry 11 } 1232 rsvpResvInterface OBJECT-TYPE 1233 SYNTAX InterfaceIndex 1234 MAX-ACCESS read-create 1235 STATUS current 1236 DESCRIPTION 1237 "The ifIndex value of the interface on which 1238 this RESV message was most recently received." 1239 ::= { rsvpResvEntry 12 } 1241 rsvpResvService OBJECT-TYPE 1242 SYNTAX QosService 1243 MAX-ACCESS read-create 1244 STATUS current 1245 DESCRIPTION 1246 "The QoS Service classification requested by 1247 the receiver." 1248 ::= { rsvpResvEntry 13 } 1250 rsvpResvTSpecRate OBJECT-TYPE 1251 SYNTAX BitRate 1252 UNITS "bits per second" 1253 MAX-ACCESS read-create 1254 STATUS current 1255 DESCRIPTION 1256 "The Average Bit Rate of the sender's data 1257 stream. Within a transmission burst, the ar- 1258 rival rate may be as fast as rsvpResvTSpec- 1259 PeakRate (if supported by the service model); 1260 however, averaged across two or more burst in- 1261 tervals, the rate should not exceed 1262 rsvpResvTSpecRate. 1264 Note that this is a prediction, often based on 1265 the general capability of a type of codec or 1266 particular encoding; the measured average rate 1267 may be significantly lower." 1268 ::= { rsvpResvEntry 14 } 1270 rsvpResvTSpecPeakRate OBJECT-TYPE 1271 SYNTAX BitRate 1272 UNITS "bits per second" 1273 MAX-ACCESS read-create 1274 STATUS current 1275 DESCRIPTION 1276 "The Peak Bit Rate of the sender's data stream. 1277 Traffic arrival is not expected to exceed this 1278 rate at any time, apart from the effects of 1279 jitter in the network. If not specified in the 1280 TSpec, this returns zero or noSuchValue." 1281 ::= { rsvpResvEntry 15 } 1283 rsvpResvTSpecBurst OBJECT-TYPE 1284 SYNTAX BurstSize 1285 UNITS "bytes" 1286 MAX-ACCESS read-create 1287 STATUS current 1288 DESCRIPTION 1289 "The size of the largest burst expected from 1290 the sender at a time. 1292 If this is less than the sender's advertised 1293 burst size, the receiver is asking the network 1294 to provide flow pacing beyond what would be 1295 provided under normal circumstances. Such pac- 1296 ing is at the network's option." 1297 ::= { rsvpResvEntry 16 } 1299 rsvpResvTSpecMinTU OBJECT-TYPE 1300 SYNTAX MessageSize 1301 MAX-ACCESS read-create 1302 STATUS current 1303 DESCRIPTION 1304 "The minimum message size for this flow. The 1305 policing algorithm will treat smaller messages 1306 as though they are this size." 1307 ::= { rsvpResvEntry 17 } 1309 rsvpResvTSpecMaxTU OBJECT-TYPE 1310 SYNTAX MessageSize 1311 MAX-ACCESS read-create 1312 STATUS current 1313 DESCRIPTION 1314 "The maximum message size for this flow. The 1315 admission algorithm will reject TSpecs whose 1316 Maximum Transmission Unit, plus the interface 1317 headers, exceed the interface MTU." 1318 ::= { rsvpResvEntry 18 } 1320 rsvpResvRSpecRate OBJECT-TYPE 1321 SYNTAX BitRate 1322 UNITS "bits per second" 1323 MAX-ACCESS read-create 1324 STATUS current 1325 DESCRIPTION 1326 "If the requested service is Guaranteed, as 1327 specified by rsvpResvService, this is the 1328 clearing rate that is being requested. Other- 1329 wise, it is zero, or the agent may return 1330 noSuchValue." 1331 ::= { rsvpResvEntry 19 } 1333 rsvpResvRSpecSlack OBJECT-TYPE 1334 SYNTAX Integer32 1335 UNITS "microseconds" 1336 MAX-ACCESS read-create 1337 STATUS current 1338 DESCRIPTION 1339 "If the requested service is Guaranteed, as 1340 specified by rsvpResvService, this is the delay 1341 slack. Otherwise, it is zero, or the agent may 1342 return noSuchValue." 1343 ::= { rsvpResvEntry 20 } 1345 rsvpResvInterval OBJECT-TYPE 1346 SYNTAX RefreshInterval 1347 MAX-ACCESS read-create 1348 STATUS current 1349 DESCRIPTION 1350 "The interval between refresh messages as ad- 1351 vertised by the Next Hop." 1352 ::= { rsvpResvEntry 21 } 1354 rsvpResvScope OBJECT-TYPE 1355 SYNTAX OCTET STRING (SIZE(0..65536)) 1356 MAX-ACCESS read-create 1357 STATUS current 1358 DESCRIPTION 1360 "The contents of the scope object, displayed as 1361 an uninterpreted string of octets, including 1362 the object header. In the absence of such an 1363 object, this should be of zero length. 1365 If the length is non-zero, this contains a 1366 series of IP4 or IP6 addresses." 1367 ::= { rsvpResvEntry 22 } 1369 rsvpResvShared OBJECT-TYPE 1370 SYNTAX TruthValue 1371 MAX-ACCESS read-create 1372 STATUS current 1373 DESCRIPTION 1374 "If TRUE, a reservation shared among senders is 1375 requested. If FALSE, a reservation specific to 1376 this sender is requested." 1377 ::= { rsvpResvEntry 23 } 1379 rsvpResvExplicit OBJECT-TYPE 1380 SYNTAX TruthValue 1381 MAX-ACCESS read-create 1382 STATUS current 1383 DESCRIPTION 1384 "If TRUE, individual senders are listed using 1385 Filter Specifications. If FALSE, all senders 1386 are implicitly selected. The Scope Object will 1387 contain a list of senders that need to receive 1388 this reservation request for the purpose of 1389 routing the RESV message." 1390 ::= { rsvpResvEntry 24 } 1392 rsvpResvRSVPHop OBJECT-TYPE 1393 SYNTAX TruthValue 1394 MAX-ACCESS read-create 1395 STATUS current 1396 DESCRIPTION 1397 "If TRUE, the node believes that the previous 1398 IP hop is an RSVP hop. If FALSE, the node be- 1399 lieves that the previous IP hop may not be an 1400 RSVP hop." 1401 ::= { rsvpResvEntry 25 } 1403 rsvpResvLastChange OBJECT-TYPE 1404 SYNTAX TimeStamp 1405 MAX-ACCESS read-only 1406 STATUS current 1407 DESCRIPTION 1408 "The time of the last change in this reserva- 1409 tion request; This is either the first time it 1410 was received or the time of the most recent 1411 change in parameters." 1412 ::= { rsvpResvEntry 26 } 1414 rsvpResvPolicy OBJECT-TYPE 1415 SYNTAX OCTET STRING (SIZE(0..65536)) 1416 MAX-ACCESS read-create 1417 STATUS current 1418 DESCRIPTION 1419 "The contents of the policy object, displayed 1420 as an uninterpreted string of octets, including 1421 the object header. In the absence of such an 1422 object, this should be of zero length." 1423 ::= { rsvpResvEntry 27 } 1425 rsvpResvStatus OBJECT-TYPE 1426 SYNTAX RowStatus 1427 MAX-ACCESS read-create 1428 STATUS current 1429 DESCRIPTION 1430 "'valid' for all active RESV messages. This 1431 object may be used to install static RESV in- 1432 formation or delete RESV information." 1433 ::= { rsvpResvEntry 28 } 1435 -- The RSVP Reservation Requests Forwarded Table contains the 1436 -- information displayed by receivers regarding their needs with 1437 -- respect to sessions and senders. It is in essence a list of the 1438 -- valid RESV messages that the RSVP Router or Host is sending 1439 -- to its upstream neighbors. 1441 rsvpResvFwdNewIndex OBJECT-TYPE 1442 SYNTAX TestAndIncr 1443 MAX-ACCESS read-write 1444 STATUS current 1445 DESCRIPTION 1446 "This object is used to assign values to 1447 rsvpResvFwdNumber as described in 'Textual Con- 1448 ventions for SNMPv2'. The network manager 1449 reads the object, and then writes the value 1450 back in the SET that creates a new instance of 1451 rsvpResvFwdEntry. If the SET fails with the 1452 code 'inconsistentValue', then the process must 1453 be repeated; If the SET succeeds, then the ob- 1454 ject is incremented, and the new instance is 1455 created according to the manager's directions." 1456 ::= { rsvpGenObjects 4 } 1458 rsvpResvFwdTable OBJECT-TYPE 1459 SYNTAX SEQUENCE OF RsvpResvFwdEntry 1460 MAX-ACCESS not-accessible 1461 STATUS current 1462 DESCRIPTION 1463 "Information describing the state information 1464 displayed upstream in RESV messages." 1465 ::= { rsvpObjects 4 } 1467 rsvpResvFwdEntry OBJECT-TYPE 1468 SYNTAX RsvpResvFwdEntry 1469 MAX-ACCESS not-accessible 1470 STATUS current 1471 DESCRIPTION 1472 "Information describing the state information 1473 displayed upstream in an RESV message concern- 1474 ing a single sender." 1475 INDEX { rsvpSessionNumber, rsvpResvFwdNumber } 1476 ::= { rsvpResvFwdTable 1 } 1478 RsvpResvFwdEntry ::= 1479 SEQUENCE { 1480 rsvpResvFwdNumber SessionNumber, 1481 rsvpResvFwdType SessionType, 1482 rsvpResvFwdDestAddr OCTET STRING, 1483 rsvpResvFwdSenderAddr OCTET STRING, 1484 rsvpResvFwdDestAddrLength INTEGER, 1485 rsvpResvFwdSenderAddrLength INTEGER, 1486 rsvpResvFwdProtocol Protocol, 1487 rsvpResvFwdDestPort Port, 1488 rsvpResvFwdPort Port, 1489 rsvpResvFwdHopAddr OCTET STRING, 1490 rsvpResvFwdHopLih Integer32, 1491 rsvpResvFwdInterface InterfaceIndex, 1492 rsvpResvFwdService QosService, 1493 rsvpResvFwdTSpecRate BitRate, 1494 rsvpResvFwdTSpecPeakRate BitRate, 1495 rsvpResvFwdTSpecBurst BurstSize, 1496 rsvpResvFwdTSpecMinTU MessageSize, 1497 rsvpResvFwdTSpecMaxTU MessageSize, 1498 rsvpResvFwdRSpecRate BitRate, 1499 rsvpResvFwdRSpecSlack Integer32, 1500 rsvpResvFwdInterval RefreshInterval, 1501 rsvpResvFwdScope OCTET STRING, 1502 rsvpResvFwdShared TruthValue, 1503 rsvpResvFwdExplicit TruthValue, 1504 rsvpResvFwdRSVPHop TruthValue, 1505 rsvpResvFwdLastChange TimeStamp, 1506 rsvpResvFwdPolicy OCTET STRING, 1507 rsvpResvFwdStatus RowStatus 1508 } 1510 rsvpResvFwdNumber OBJECT-TYPE 1511 SYNTAX SessionNumber 1512 MAX-ACCESS not-accessible 1513 STATUS current 1514 DESCRIPTION 1515 "The number of this reservation request. This 1516 is for SNMP Indexing purposes only and has no 1517 relation to any protocol vaalue." 1518 ::= { rsvpResvFwdEntry 1 } 1520 rsvpResvFwdType OBJECT-TYPE 1521 SYNTAX SessionType 1522 MAX-ACCESS read-create 1523 STATUS current 1524 DESCRIPTION 1525 "The type of session (IP4, IP6, IP6 with flow 1526 information, etc)." 1527 ::= { rsvpResvFwdEntry 2 } 1529 rsvpResvFwdDestAddr OBJECT-TYPE 1530 SYNTAX OCTET STRING (SIZE(4..16)) 1531 MAX-ACCESS read-create 1532 STATUS current 1533 DESCRIPTION 1534 "The destination address used by all senders in 1535 this session. This object may not be changed 1536 when the value of the RowStatus object is 1537 'valid'." 1538 ::= { rsvpResvFwdEntry 3 } 1540 rsvpResvFwdSenderAddr OBJECT-TYPE 1541 SYNTAX OCTET STRING (SIZE(4..16)) 1542 MAX-ACCESS read-create 1543 STATUS current 1544 DESCRIPTION 1545 "The source address of the sender selected by 1546 this reservation. The value of all zeroes in- 1547 dicates 'all senders'. This object may not be 1548 changed when the value of the RowStatus object 1549 is 'valid'." 1550 ::= { rsvpResvFwdEntry 4 } 1552 rsvpResvFwdDestAddrLength OBJECT-TYPE 1553 SYNTAX INTEGER(0..128) 1554 MAX-ACCESS read-create 1555 STATUS current 1556 DESCRIPTION 1557 "The length of the destination address in bits. 1558 This is the CIDR Prefix Length, which for IP4 1559 hosts and multicast addresses is 32 bits. This 1560 object may not be changed when the value of the 1561 RowStatus object is 'valid'." 1562 ::= { rsvpResvFwdEntry 5 } 1564 rsvpResvFwdSenderAddrLength OBJECT-TYPE 1565 SYNTAX INTEGER(0..128) 1566 MAX-ACCESS read-create 1567 STATUS current 1568 DESCRIPTION 1569 "The length of the sender's address in bits. 1570 This is the CIDR Prefix Length, which for IP4 1571 hosts and multicast addresses is 32 bits. This 1572 object may not be changed when the value of the 1573 RowStatus object is 'valid'." 1574 ::= { rsvpResvFwdEntry 6 } 1576 rsvpResvFwdProtocol OBJECT-TYPE 1577 SYNTAX Protocol 1578 MAX-ACCESS read-create 1579 STATUS current 1580 DESCRIPTION 1581 "The IP Protocol used by a session. for secure 1582 sessions, this indicates IP Security. This ob- 1583 ject may not be changed when the value of the 1584 RowStatus object is 'valid'." 1585 ::= { rsvpResvFwdEntry 7 } 1587 rsvpResvFwdDestPort OBJECT-TYPE 1588 SYNTAX Port 1589 MAX-ACCESS read-create 1590 STATUS current 1591 DESCRIPTION 1592 "The UDP or TCP port number used as a destina- 1593 tion port for all senders in this session. If 1594 the IP protocol in use, specified by 1595 rsvpResvFwdProtocol, is 50 (ESP) or 51 (AH), 1596 this represents a virtual destination port 1597 number. A value of zero indicates that the IP 1598 protocol in use does not have ports. This ob- 1599 ject may not be changed when the value of the 1600 RowStatus object is 'valid'." 1601 ::= { rsvpResvFwdEntry 8 } 1603 rsvpResvFwdPort OBJECT-TYPE 1604 SYNTAX Port 1605 MAX-ACCESS read-create 1606 STATUS current 1607 DESCRIPTION 1608 "The UDP or TCP port number used as a source 1609 port for this sender in this session. If the 1610 IP protocol in use, specified by 1611 rsvpResvFwdProtocol is 50 (ESP) or 51 (AH), 1612 this represents a generalized port identifier 1613 (GPI). A value of zero indicates that the IP 1614 protocol in use does not have ports. This ob- 1615 ject may not be changed when the value of the 1616 RowStatus object is 'valid'." 1617 ::= { rsvpResvFwdEntry 9 } 1619 rsvpResvFwdHopAddr OBJECT-TYPE 1620 SYNTAX OCTET STRING (SIZE(4..16)) 1621 MAX-ACCESS read-create 1622 STATUS current 1623 DESCRIPTION 1624 "The address of the (previous) RSVP that will 1625 receive this message." 1626 ::= { rsvpResvFwdEntry 10 } 1628 rsvpResvFwdHopLih OBJECT-TYPE 1629 SYNTAX Integer32 1630 MAX-ACCESS read-create 1631 STATUS current 1632 DESCRIPTION 1633 "The Logical Interface Handle sent to the (pre- 1634 vious) RSVP that will receive this message." 1635 ::= { rsvpResvFwdEntry 11 } 1637 rsvpResvFwdInterface OBJECT-TYPE 1638 SYNTAX InterfaceIndex 1639 MAX-ACCESS read-create 1640 STATUS current 1641 DESCRIPTION 1642 "The ifIndex value of the interface on which 1643 this RESV message was most recently sent." 1644 ::= { rsvpResvFwdEntry 12 } 1646 rsvpResvFwdService OBJECT-TYPE 1647 SYNTAX QosService 1648 MAX-ACCESS read-create 1649 STATUS current 1650 DESCRIPTION 1651 "The QoS Service classification requested." 1652 ::= { rsvpResvFwdEntry 13 } 1654 rsvpResvFwdTSpecRate OBJECT-TYPE 1655 SYNTAX BitRate 1656 UNITS "bits per second" 1657 MAX-ACCESS read-create 1658 STATUS current 1659 DESCRIPTION 1660 "The Average Bit Rate of the sender's data 1661 stream. Within a transmission burst, the ar- 1662 rival rate may be as fast as rsvpResvFwdTSpec- 1663 PeakRate (if supported by the service model); 1664 however, averaged across two or more burst in- 1665 tervals, the rate should not exceed 1666 rsvpResvFwdTSpecRate. 1668 Note that this is a prediction, often based on 1669 the general capability of a type of codec or 1670 particular encoding; the measured average rate 1671 may be significantly lower." 1672 ::= { rsvpResvFwdEntry 14 } 1674 rsvpResvFwdTSpecPeakRate OBJECT-TYPE 1675 SYNTAX BitRate 1676 UNITS "bits per second" 1677 MAX-ACCESS read-create 1678 STATUS current 1679 DESCRIPTION 1680 "The Peak Bit Rate of the sender's data stream 1681 Traffic arrival is not expected to exceed this 1682 rate at any time, apart from the effects of 1683 jitter in the network. If not specified in the 1684 TSpec, this returns zero or noSuchValue." 1685 ::= { rsvpResvFwdEntry 15 } 1687 rsvpResvFwdTSpecBurst OBJECT-TYPE 1688 SYNTAX BurstSize 1689 UNITS "bytes" 1690 MAX-ACCESS read-create 1691 STATUS current 1692 DESCRIPTION 1693 "The size of the largest burst expected from 1694 the sender at a time. 1696 If this is less than the sender's advertised 1697 burst size, the receiver is asking the network 1698 to provide flow pacing beyond what would be 1699 provided under normal circumstances. Such pac- 1700 ing is at the network's option." 1701 ::= { rsvpResvFwdEntry 16 } 1703 rsvpResvFwdTSpecMinTU OBJECT-TYPE 1704 SYNTAX MessageSize 1705 MAX-ACCESS read-create 1706 STATUS current 1707 DESCRIPTION 1708 "The minimum message size for this flow. The 1709 policing algorithm will treat smaller messages 1710 as though they are this size." 1711 ::= { rsvpResvFwdEntry 17 } 1713 rsvpResvFwdTSpecMaxTU OBJECT-TYPE 1714 SYNTAX MessageSize 1715 MAX-ACCESS read-create 1716 STATUS current 1717 DESCRIPTION 1718 "The maximum message size for this flow. The 1719 admission algorithm will reject TSpecs whose 1720 Maximum Transmission Unit, plus the interface 1721 headers, exceed the interface MTU." 1722 ::= { rsvpResvFwdEntry 18 } 1724 rsvpResvFwdRSpecRate OBJECT-TYPE 1725 SYNTAX BitRate 1726 UNITS "bytes per second" 1727 MAX-ACCESS read-create 1728 STATUS current 1729 DESCRIPTION 1730 "If the requested service is Guaranteed, as 1731 specified by rsvpResvService, this is the 1732 clearing rate that is being requested. Other- 1733 wise, it is zero, or the agent may return 1734 noSuchValue." 1735 ::= { rsvpResvFwdEntry 19 } 1737 rsvpResvFwdRSpecSlack OBJECT-TYPE 1738 SYNTAX Integer32 1739 UNITS "microseconds" 1740 MAX-ACCESS read-create 1741 STATUS current 1742 DESCRIPTION 1743 "If the requested service is Guaranteed, as 1744 specified by rsvpResvService, this is the delay 1745 slack. Otherwise, it is zero, or the agent may 1746 return noSuchValue." 1747 ::= { rsvpResvFwdEntry 20 } 1749 rsvpResvFwdInterval OBJECT-TYPE 1750 SYNTAX RefreshInterval 1751 MAX-ACCESS read-create 1752 STATUS current 1753 DESCRIPTION 1754 "The interval between refresh messages adver- 1755 tised to the Previous Hop." 1756 ::= { rsvpResvFwdEntry 21 } 1758 rsvpResvFwdScope OBJECT-TYPE 1759 SYNTAX OCTET STRING (SIZE(0..65536)) 1760 MAX-ACCESS read-create 1761 STATUS current 1762 DESCRIPTION 1763 "The contents of the scope object, displayed as 1764 an uninterpreted string of octets, including 1765 the object header. In the absence of such an 1766 object, this should be of zero length." 1767 ::= { rsvpResvFwdEntry 22 } 1769 rsvpResvFwdShared OBJECT-TYPE 1770 SYNTAX TruthValue 1771 MAX-ACCESS read-create 1772 STATUS current 1773 DESCRIPTION 1774 "If TRUE, a reservation shared among senders is 1775 requested. If FALSE, a reservation specific to 1776 this sender is requested." 1777 ::= { rsvpResvFwdEntry 23 } 1779 rsvpResvFwdExplicit OBJECT-TYPE 1780 SYNTAX TruthValue 1781 MAX-ACCESS read-create 1782 STATUS current 1783 DESCRIPTION 1784 "If TRUE, individual senders are listed using 1785 Filter Specifications. If FALSE, all senders 1786 are implicitly selected. The Scope Object will 1787 contain a list of senders that need to receive 1788 this reservation request for the purpose of 1789 routing the RESV message." 1790 ::= { rsvpResvFwdEntry 24 } 1792 rsvpResvFwdRSVPHop OBJECT-TYPE 1793 SYNTAX TruthValue 1794 MAX-ACCESS read-create 1795 STATUS current 1796 DESCRIPTION 1797 "If TRUE, the node believes that the next IP 1798 hop is an RSVP hop. If FALSE, the node be- 1799 lieves that the next IP hop may not be an RSVP 1800 hop." 1801 ::= { rsvpResvFwdEntry 25 } 1803 rsvpResvFwdLastChange OBJECT-TYPE 1804 SYNTAX TimeStamp 1805 MAX-ACCESS read-only 1806 STATUS current 1807 DESCRIPTION 1808 "The time of the last change in this request; 1809 This is either the first time it was sent or 1810 the time of the most recent change in parame- 1811 ters." 1812 ::= { rsvpResvFwdEntry 26 } 1814 rsvpResvFwdPolicy OBJECT-TYPE 1815 SYNTAX OCTET STRING (SIZE(0..65536)) 1816 MAX-ACCESS read-create 1817 STATUS current 1818 DESCRIPTION 1819 "The contents of the policy object, displayed 1820 as an uninterpreted string of octets, including 1821 the object header. In the absence of such an 1822 object, this should be of zero length." 1823 ::= { rsvpResvFwdEntry 27 } 1825 rsvpResvFwdStatus OBJECT-TYPE 1826 SYNTAX RowStatus 1827 MAX-ACCESS read-create 1828 STATUS current 1829 DESCRIPTION 1830 "'valid' for all active RESV messages. This 1831 object may be used to install static RESV in- 1832 formation or delete RESV information." 1833 ::= { rsvpResvFwdEntry 28 } 1835 -- The RSVP Interface Attributes Database contains the 1836 -- RSVP-specific information for an interface. Information 1837 -- that is shared with other reservation procedures such 1838 -- as ST-II is in the Integrated Interface Attributes 1839 -- Database. 1841 rsvpIfTable OBJECT-TYPE 1842 SYNTAX SEQUENCE OF RsvpIfEntry 1843 MAX-ACCESS not-accessible 1844 STATUS current 1845 DESCRIPTION 1846 "The RSVP-specific attributes of the system's 1847 interfaces." 1848 ::= { rsvpObjects 6 } 1850 rsvpIfEntry OBJECT-TYPE 1851 SYNTAX RsvpIfEntry 1852 MAX-ACCESS not-accessible 1853 STATUS current 1854 DESCRIPTION 1855 "The RSVP-specific attributes of the a given 1856 interface." 1857 INDEX { ifIndex } 1858 ::= { rsvpIfTable 1 } 1860 RsvpIfEntry ::= 1861 SEQUENCE { 1862 rsvpIfUdpNbrs Gauge32, 1863 rsvpIfIpNbrs Gauge32, 1864 rsvpIfNbrs Gauge32, 1865 rsvpIfEnabled TruthValue, 1866 rsvpIfUdpRequired TruthValue, 1867 rsvpIfRefreshBlockadeMultiple INTEGER, 1868 rsvpIfRefreshMultiple INTEGER, 1869 rsvpIfTTL INTEGER, 1870 rsvpIfRefreshInterval TimeInterval, 1871 rsvpIfRouteDelay TimeInterval, 1872 rsvpIfStatus RowStatus 1873 } 1874 rsvpIfUdpNbrs OBJECT-TYPE 1875 SYNTAX Gauge32 1876 MAX-ACCESS read-only 1877 STATUS current 1878 DESCRIPTION 1879 "The number of neighbors perceived to be using 1880 only the RSVP UDP Encapsulation." 1881 ::= { rsvpIfEntry 1 } 1883 rsvpIfIpNbrs OBJECT-TYPE 1884 SYNTAX Gauge32 1885 MAX-ACCESS read-only 1886 STATUS current 1887 DESCRIPTION 1888 "The number of neighbors perceived to be using 1889 only the RSVP IP Encapsulation." 1890 ::= { rsvpIfEntry 2 } 1892 rsvpIfNbrs OBJECT-TYPE 1893 SYNTAX Gauge32 1894 MAX-ACCESS read-only 1895 STATUS current 1896 DESCRIPTION 1897 "The number of neighbors currently perceived; 1898 this will exceed rsvpIfIpNbrs + rsvpIfUdpNbrs 1899 by the number of neighbors using both encapsu- 1900 lations." 1901 ::= { rsvpIfEntry 3 } 1903 rsvpIfRefreshBlockadeMultiple OBJECT-TYPE 1904 SYNTAX INTEGER (1..65536) 1905 MAX-ACCESS read-create 1906 STATUS current 1907 DESCRIPTION 1908 "The value of the RSVP value 'Kb', Which is the 1909 minimum number of refresh intervals that 1910 blockade state will last once entered." 1911 DEFVAL { 4 } 1912 ::= { rsvpIfEntry 4 } 1914 rsvpIfRefreshMultiple OBJECT-TYPE 1915 SYNTAX INTEGER (1..65536) 1916 MAX-ACCESS read-create 1917 STATUS current 1918 DESCRIPTION 1919 "The value of the RSVP value 'K', which is the 1920 number of refresh intervals which must elapse 1921 (minimum) before a PATH or RESV message which 1922 is not being refreshed will be aged out." 1923 DEFVAL { 3 } 1924 ::= { rsvpIfEntry 5 } 1926 rsvpIfTTL OBJECT-TYPE 1927 SYNTAX INTEGER (0..255) 1928 MAX-ACCESS read-create 1929 STATUS current 1930 DESCRIPTION 1931 "The value of SEND_TTL used on this interface 1932 for messages this node originates. If set to 1933 zero, the node determines the TTL via other 1934 means." 1935 DEFVAL { 0 } -- which is to say, no override 1936 ::= { rsvpIfEntry 6 } 1938 rsvpIfRefreshInterval OBJECT-TYPE 1939 SYNTAX TimeInterval 1940 UNITS "hundredths of a second" 1941 MAX-ACCESS read-create 1942 STATUS current 1943 DESCRIPTION 1944 "The value of the RSVP value 'R', which is the 1945 minimum period between refresh transmissions of 1946 a given PATH or RESV message on an interface." 1947 DEFVAL { 3000 } -- 30 seconds 1948 ::= { rsvpIfEntry 7 } 1950 rsvpIfRouteDelay OBJECT-TYPE 1951 SYNTAX TimeInterval 1952 UNITS "hundredths of a second" 1953 MAX-ACCESS read-create 1954 STATUS current 1955 DESCRIPTION 1956 "The approximate period from the time a route 1957 is changed to the time a resulting message ap- 1958 pears on the interface." 1959 DEFVAL { 200 } -- 2 seconds 1960 ::= { rsvpIfEntry 8 } 1962 rsvpIfEnabled OBJECT-TYPE 1963 SYNTAX TruthValue 1964 MAX-ACCESS read-create 1965 STATUS current 1966 DESCRIPTION 1967 "If TRUE, RSVP is enabled on this Interface. 1968 If FALSE, RSVP is not enabled on this inter- 1969 face." 1970 ::= { rsvpIfEntry 9 } 1972 rsvpIfUdpRequired OBJECT-TYPE 1973 SYNTAX TruthValue 1974 MAX-ACCESS read-create 1975 STATUS current 1976 DESCRIPTION 1977 "If TRUE, manual configuration forces the use 1978 of UDP encapsulation on the interface. If 1979 FALSE, UDP encapsulation is only used if rsvpI- 1980 fUdpNbrs is not zero." 1982 ::= { rsvpIfEntry 10 } 1984 rsvpIfStatus OBJECT-TYPE 1985 SYNTAX RowStatus 1986 MAX-ACCESS read-create 1987 STATUS current 1988 DESCRIPTION 1989 "'valid' on interfaces that are configured for 1990 RSVP." 1991 ::= { rsvpIfEntry 11 } 1993 -- The RSVP Neighbor Database lists the neighbors the RSVP 1994 -- process currently is receiving messages from. 1996 rsvpNbrTable OBJECT-TYPE 1997 SYNTAX SEQUENCE OF RsvpNbrEntry 1998 MAX-ACCESS not-accessible 1999 STATUS current 2000 DESCRIPTION 2001 "Information describing the Neighbors of an 2002 RSVP system." 2003 ::= { rsvpObjects 7 } 2005 rsvpNbrEntry OBJECT-TYPE 2006 SYNTAX RsvpNbrEntry 2007 MAX-ACCESS not-accessible 2008 STATUS current 2009 DESCRIPTION 2010 "Information describing a single RSVP Neigh- 2011 bor." 2012 INDEX { ifIndex, rsvpNbrAddress } 2013 ::= { rsvpNbrTable 1 } 2015 RsvpNbrEntry ::= 2016 SEQUENCE { 2017 rsvpNbrAddress OCTET STRING, 2018 rsvpNbrProtocol RsvpEncapsulation, 2019 rsvpNbrStatus RowStatus 2020 } 2022 rsvpNbrAddress OBJECT-TYPE 2023 SYNTAX OCTET STRING (SIZE(4..16)) 2024 MAX-ACCESS not-accessible 2025 STATUS current 2026 DESCRIPTION 2027 "The IP4 or IP6 Address used by this neighbor. 2028 This object may not be changed when the value 2029 of the RowStatus object is 'valid'." 2030 ::= { rsvpNbrEntry 1 } 2032 rsvpNbrProtocol OBJECT-TYPE 2033 SYNTAX RsvpEncapsulation 2034 MAX-ACCESS read-create 2035 STATUS current 2036 DESCRIPTION 2037 "The encapsulation being used by this neigh- 2038 bor." 2039 ::= { rsvpNbrEntry 2 } 2041 rsvpNbrStatus OBJECT-TYPE 2042 SYNTAX RowStatus 2043 MAX-ACCESS read-create 2044 STATUS current 2045 DESCRIPTION 2046 "'valid' for all neighbors. This object may be 2047 used to configure neighbors. In the presence 2048 of configured neighbors, the implementation may 2049 (but is not required to) limit the set of valid 2050 neighbors to those configured." 2051 ::= { rsvpNbrEntry 3 } 2053 -- conformance information 2055 rsvpGroups OBJECT IDENTIFIER ::= { rsvpConformance 1 } 2056 rsvpCompliances OBJECT IDENTIFIER ::= { rsvpConformance 2 } 2058 -- compliance statements 2059 rsvpCompliance MODULE-COMPLIANCE 2060 STATUS current 2061 DESCRIPTION 2062 "The compliance statement. Note that the im- 2063 plementation of this module requires implemen- 2064 tation of the Integrated Services MIB as well." 2065 MODULE -- this module 2066 MANDATORY-GROUPS { 2067 rsvpSessionGroup, rsvpSenderGroup, rsvpResvGroup, 2068 rsvpResvFwdGroup, rsvpIfGroup, 2069 rsvpNbrGroup 2070 } 2072 OBJECT rsvpSenderType 2073 MIN-ACCESS read-only 2074 DESCRIPTION 2075 "read-create access is not required. This may be 2076 read-only." 2078 OBJECT rsvpSenderDestAddr 2079 MIN-ACCESS read-only 2080 DESCRIPTION 2081 "read-create access is not required. This may be 2082 read-only." 2084 OBJECT rsvpSenderAddr 2085 MIN-ACCESS read-only 2086 DESCRIPTION 2087 "read-create access is not required. This may be 2088 read-only." 2090 OBJECT rsvpSenderDestAddrLength 2091 MIN-ACCESS read-only 2092 DESCRIPTION 2093 "read-create access is not required. This may be 2094 read-only." 2096 OBJECT rsvpSenderAddrLength 2097 MIN-ACCESS read-only 2098 DESCRIPTION 2099 "read-create access is not required. This may be 2100 read-only." 2102 OBJECT rsvpSenderProtocol 2103 MIN-ACCESS read-only 2104 DESCRIPTION 2105 "read-create access is not required. This may be 2106 read-only." 2108 OBJECT rsvpSenderDestPort 2109 MIN-ACCESS read-only 2110 DESCRIPTION 2111 "read-create access is not required. This may be 2112 read-only." 2114 OBJECT rsvpSenderPort 2115 MIN-ACCESS read-only 2116 DESCRIPTION 2117 "read-create access is not required. This may be 2118 read-only." 2120 OBJECT rsvpSenderHopAddr 2121 MIN-ACCESS read-only 2122 DESCRIPTION 2123 "read-create access is not required. This may be 2124 read-only." 2126 OBJECT rsvpSenderHopLih 2127 MIN-ACCESS read-only 2128 DESCRIPTION 2129 "read-create access is not required. This may be 2130 read-only." 2132 OBJECT rsvpSenderInterface 2133 MIN-ACCESS read-only 2134 DESCRIPTION 2135 "read-create access is not required. This may be 2136 read-only." 2138 OBJECT rsvpSenderTSpecRate 2139 MIN-ACCESS read-only 2140 DESCRIPTION 2141 "read-create access is not required. This may be 2142 read-only." 2144 OBJECT rsvpSenderTSpecPeakRate 2145 MIN-ACCESS read-only 2146 DESCRIPTION 2147 "read-create access is not required. This may be 2148 read-only." 2150 OBJECT rsvpSenderTSpecBurst 2151 MIN-ACCESS read-only 2152 DESCRIPTION 2153 "read-create access is not required. This may be 2154 read-only." 2156 OBJECT rsvpSenderTSpecMinTU 2157 MIN-ACCESS read-only 2158 DESCRIPTION 2159 "read-create access is not required. This may be 2160 read-only." 2162 OBJECT rsvpSenderTSpecMaxTU 2163 MIN-ACCESS read-only 2164 DESCRIPTION 2165 "read-create access is not required. This may be 2166 read-only." 2168 OBJECT rsvpSenderInterval 2169 MIN-ACCESS read-only 2170 DESCRIPTION 2171 "read-create access is not required. This may be 2172 read-only." 2174 OBJECT rsvpSenderRSVPHop 2175 MIN-ACCESS read-only 2176 DESCRIPTION 2177 "read-create access is not required. This may be 2178 read-only." 2180 OBJECT rsvpSenderPolicy 2181 MIN-ACCESS read-only 2182 DESCRIPTION 2183 "read-create access is not required. This may be 2184 read-only." 2186 OBJECT rsvpSenderAdspecBreak 2187 MIN-ACCESS read-only 2188 DESCRIPTION 2189 "read-create access is not required. This may be 2190 read-only." 2192 OBJECT rsvpSenderAdspecHopCount 2193 MIN-ACCESS read-only 2194 DESCRIPTION 2195 "read-create access is not required. This may be 2196 read-only." 2198 OBJECT rsvpSenderAdspecPathBw 2199 MIN-ACCESS read-only 2200 DESCRIPTION 2201 "read-create access is not required. This may be 2202 read-only." 2204 OBJECT rsvpSenderAdspecMinLatency 2205 MIN-ACCESS read-only 2206 DESCRIPTION 2207 "read-create access is not required. This may be 2208 read-only." 2210 OBJECT rsvpSenderAdspecMtu 2211 MIN-ACCESS read-only 2212 DESCRIPTION 2213 "read-create access is not required. This may be 2214 read-only." 2216 OBJECT rsvpSenderAdspecGuaranteedSvc 2217 MIN-ACCESS read-only 2218 DESCRIPTION 2219 "read-create access is not required. This may be 2220 read-only." 2222 OBJECT rsvpSenderAdspecGuaranteedBreak 2223 MIN-ACCESS read-only 2224 DESCRIPTION 2225 "read-create access is not required. This may be 2226 read-only." 2228 OBJECT rsvpSenderAdspecGuaranteedCtot 2229 MIN-ACCESS read-only 2230 DESCRIPTION 2231 "read-create access is not required. This may be 2232 read-only." 2234 OBJECT rsvpSenderAdspecGuaranteedDtot 2235 MIN-ACCESS read-only 2236 DESCRIPTION 2237 "read-create access is not required. This may be 2238 read-only." 2240 OBJECT rsvpSenderAdspecGuaranteedCsum 2241 MIN-ACCESS read-only 2242 DESCRIPTION 2243 "read-create access is not required. This may be 2244 read-only." 2246 OBJECT rsvpSenderAdspecGuaranteedDsum 2247 MIN-ACCESS read-only 2248 DESCRIPTION 2249 "read-create access is not required. This may be 2250 read-only." 2252 OBJECT rsvpSenderAdspecGuaranteedHopCount 2253 MIN-ACCESS read-only 2254 DESCRIPTION 2255 "read-create access is not required. This may be 2256 read-only." 2258 OBJECT rsvpSenderAdspecGuaranteedPathBw 2259 MIN-ACCESS read-only 2260 DESCRIPTION 2261 "read-create access is not required. This may be 2262 read-only." 2264 OBJECT rsvpSenderAdspecGuaranteedMinLatency 2265 MIN-ACCESS read-only 2266 DESCRIPTION 2267 "read-create access is not required. This may be 2268 read-only." 2270 OBJECT rsvpSenderAdspecGuaranteedMtu 2271 MIN-ACCESS read-only 2272 DESCRIPTION 2273 "read-create access is not required. This may be 2274 read-only." 2276 OBJECT rsvpSenderAdspecCtrlLoadSvc 2277 MIN-ACCESS read-only 2278 DESCRIPTION 2279 "read-create access is not required. This may be 2280 read-only." 2282 OBJECT rsvpSenderAdspecCtrlLoadBreak 2283 MIN-ACCESS read-only 2284 DESCRIPTION 2285 "read-create access is not required. This may be 2286 read-only." 2288 OBJECT rsvpSenderAdspecCtrlLoadHopCount 2289 MIN-ACCESS read-only 2290 DESCRIPTION 2291 "read-create access is not required. This may be 2292 read-only." 2294 OBJECT rsvpSenderAdspecCtrlLoadPathBw 2295 MIN-ACCESS read-only 2296 DESCRIPTION 2297 "read-create access is not required. This may be 2298 read-only." 2300 OBJECT rsvpSenderAdspecCtrlLoadMinLatency 2301 MIN-ACCESS read-only 2302 DESCRIPTION 2303 "read-create access is not required. This may be 2304 read-only." 2306 OBJECT rsvpSenderAdspecCtrlLoadMtu 2307 MIN-ACCESS read-only 2308 DESCRIPTION 2309 "read-create access is not required. This may be 2310 read-only." 2312 OBJECT rsvpSenderStatus 2313 MIN-ACCESS read-only 2314 DESCRIPTION 2315 "read-create access is not required. This may be 2316 read-only." 2318 OBJECT rsvpResvType 2319 MIN-ACCESS read-only 2320 DESCRIPTION 2321 "read-create access is not required. This may be 2322 read-only." 2324 OBJECT rsvpResvDestAddr 2325 MIN-ACCESS read-only 2326 DESCRIPTION 2327 "read-create access is not required. This may be 2328 read-only." 2330 OBJECT rsvpResvSenderAddr 2331 MIN-ACCESS read-only 2332 DESCRIPTION 2333 "read-create access is not required. This may be 2334 read-only." 2336 OBJECT rsvpResvDestAddrLength 2337 MIN-ACCESS read-only 2338 DESCRIPTION 2339 "read-create access is not required. This may be 2340 read-only." 2342 OBJECT rsvpResvSenderAddrLength 2343 MIN-ACCESS read-only 2344 DESCRIPTION 2345 "read-create access is not required. This may be 2346 read-only." 2348 OBJECT rsvpResvProtocol 2349 MIN-ACCESS read-only 2350 DESCRIPTION 2351 "read-create access is not required. This may be 2352 read-only." 2354 OBJECT rsvpResvDestPort 2355 MIN-ACCESS read-only 2356 DESCRIPTION 2357 "read-create access is not required. This may be 2358 read-only." 2360 OBJECT rsvpResvPort 2361 MIN-ACCESS read-only 2362 DESCRIPTION 2363 "read-create access is not required. This may be 2364 read-only." 2366 OBJECT rsvpResvHopAddr 2367 MIN-ACCESS read-only 2368 DESCRIPTION 2369 "read-create access is not required. This may be 2370 read-only." 2372 OBJECT rsvpResvHopLih 2373 MIN-ACCESS read-only 2374 DESCRIPTION 2375 "read-create access is not required. This may be 2376 read-only." 2378 OBJECT rsvpResvInterface 2379 MIN-ACCESS read-only 2380 DESCRIPTION 2381 "read-create access is not required. This may be 2382 read-only." 2384 OBJECT rsvpResvService 2385 MIN-ACCESS read-only 2386 DESCRIPTION 2387 "read-create access is not required. This may be 2388 read-only." 2390 OBJECT rsvpResvTSpecRate 2391 MIN-ACCESS read-only 2392 DESCRIPTION 2393 "read-create access is not required. This may be 2394 read-only." 2396 OBJECT rsvpResvTSpecPeakRate 2397 MIN-ACCESS read-only 2398 DESCRIPTION 2399 "read-create access is not required. This may be 2400 read-only." 2402 OBJECT rsvpResvTSpecBurst 2403 MIN-ACCESS read-only 2404 DESCRIPTION 2405 "read-create access is not required. This may be 2406 read-only." 2408 OBJECT rsvpResvTSpecMinTU 2409 MIN-ACCESS read-only 2410 DESCRIPTION 2411 "read-create access is not required. This may be 2412 read-only." 2414 OBJECT rsvpResvTSpecMaxTU 2415 MIN-ACCESS read-only 2416 DESCRIPTION 2417 "read-create access is not required. This may be 2418 read-only." 2420 OBJECT rsvpResvRSpecRate 2421 MIN-ACCESS read-only 2422 DESCRIPTION 2423 "read-create access is not required. This may be 2424 read-only." 2426 OBJECT rsvpResvRSpecSlack 2427 MIN-ACCESS read-only 2428 DESCRIPTION 2429 "read-create access is not required. This may be 2430 read-only." 2432 OBJECT rsvpResvInterval 2433 MIN-ACCESS read-only 2434 DESCRIPTION 2435 "read-create access is not required. This may be 2436 read-only." 2438 OBJECT rsvpResvScope 2439 MIN-ACCESS read-only 2440 DESCRIPTION 2441 "read-create access is not required. This may be 2442 read-only." 2444 OBJECT rsvpResvShared 2445 MIN-ACCESS read-only 2446 DESCRIPTION 2447 "read-create access is not required. This may be 2448 read-only." 2450 OBJECT rsvpResvExplicit 2451 MIN-ACCESS read-only 2452 DESCRIPTION 2453 "read-create access is not required. This may be 2454 read-only." 2456 OBJECT rsvpResvRSVPHop 2457 MIN-ACCESS read-only 2458 DESCRIPTION 2459 "read-create access is not required. This may be 2460 read-only." 2462 OBJECT rsvpResvPolicy 2463 MIN-ACCESS read-only 2464 DESCRIPTION 2465 "read-create access is not required. This may be 2466 read-only." 2468 OBJECT rsvpResvStatus 2469 MIN-ACCESS read-only 2470 DESCRIPTION 2471 "read-create access is not required. This may be 2472 read-only." 2474 OBJECT rsvpResvFwdType 2475 MIN-ACCESS read-only 2476 DESCRIPTION 2477 "read-create access is not required. This may be 2478 read-only." 2480 OBJECT rsvpResvFwdDestAddr 2481 MIN-ACCESS read-only 2482 DESCRIPTION 2483 "read-create access is not required. This may be 2484 read-only." 2486 OBJECT rsvpResvFwdSenderAddr 2487 MIN-ACCESS read-only 2488 DESCRIPTION 2489 "read-create access is not required. This may be 2490 read-only." 2492 OBJECT rsvpResvFwdDestAddrLength 2493 MIN-ACCESS read-only 2494 DESCRIPTION 2495 "read-create access is not required. This may be 2496 read-only." 2498 OBJECT rsvpResvFwdSenderAddrLength 2499 MIN-ACCESS read-only 2500 DESCRIPTION 2501 "read-create access is not required. This may be 2502 read-only." 2504 OBJECT rsvpResvFwdProtocol 2505 MIN-ACCESS read-only 2506 DESCRIPTION 2507 "read-create access is not required. This may be 2508 read-only." 2510 OBJECT rsvpResvFwdDestPort 2511 MIN-ACCESS read-only 2512 DESCRIPTION 2513 "read-create access is not required. This may be 2514 read-only." 2516 OBJECT rsvpResvFwdPort 2517 MIN-ACCESS read-only 2518 DESCRIPTION 2519 "read-create access is not required. This may be 2520 read-only." 2522 OBJECT rsvpResvFwdHopAddr 2523 MIN-ACCESS read-only 2524 DESCRIPTION 2525 "read-create access is not required. This may be 2526 read-only." 2528 OBJECT rsvpResvFwdHopLih 2529 MIN-ACCESS read-only 2530 DESCRIPTION 2531 "read-create access is not required. This may be 2532 read-only." 2534 OBJECT rsvpResvFwdInterface 2535 MIN-ACCESS read-only 2536 DESCRIPTION 2537 "read-create access is not required. This may be 2538 read-only." 2540 OBJECT rsvpResvFwdService 2541 MIN-ACCESS read-only 2542 DESCRIPTION 2543 "read-create access is not required. This may be 2544 read-only." 2546 OBJECT rsvpResvFwdTSpecRate 2547 MIN-ACCESS read-only 2548 DESCRIPTION 2549 "read-create access is not required. This may be 2550 read-only." 2552 OBJECT rsvpResvFwdTSpecPeakRate 2553 MIN-ACCESS read-only 2554 DESCRIPTION 2555 "read-create access is not required. This may be 2556 read-only." 2558 OBJECT rsvpResvFwdTSpecBurst 2559 MIN-ACCESS read-only 2560 DESCRIPTION 2561 "read-create access is not required. This may be 2562 read-only." 2564 OBJECT rsvpResvFwdTSpecMinTU 2565 MIN-ACCESS read-only 2566 DESCRIPTION 2567 "read-create access is not required. This may be 2568 read-only." 2570 OBJECT rsvpResvFwdTSpecMaxTU 2571 MIN-ACCESS read-only 2572 DESCRIPTION 2573 "read-create access is not required. This may be 2574 read-only." 2576 OBJECT rsvpResvFwdRSpecRate 2577 MIN-ACCESS read-only 2578 DESCRIPTION 2579 "read-create access is not required. This may be 2580 read-only." 2582 OBJECT rsvpResvFwdRSpecSlack 2583 MIN-ACCESS read-only 2584 DESCRIPTION 2585 "read-create access is not required. This may be 2586 read-only." 2588 OBJECT rsvpResvFwdInterval 2589 MIN-ACCESS read-only 2590 DESCRIPTION 2591 "read-create access is not required. This may be 2592 read-only." 2594 OBJECT rsvpResvFwdScope 2595 MIN-ACCESS read-only 2596 DESCRIPTION 2597 "read-create access is not required. This may be 2598 read-only." 2600 OBJECT rsvpResvFwdShared 2601 MIN-ACCESS read-only 2602 DESCRIPTION 2603 "read-create access is not required. This may be 2604 read-only." 2606 OBJECT rsvpResvFwdExplicit 2607 MIN-ACCESS read-only 2608 DESCRIPTION 2609 "read-create access is not required. This may be 2610 read-only." 2612 OBJECT rsvpResvFwdRSVPHop 2613 MIN-ACCESS read-only 2614 DESCRIPTION 2615 "read-create access is not required. This may be 2616 read-only." 2618 OBJECT rsvpResvFwdPolicy 2619 MIN-ACCESS read-only 2620 DESCRIPTION 2621 "read-create access is not required. This may be 2622 read-only." 2624 OBJECT rsvpResvFwdStatus 2625 MIN-ACCESS read-only 2626 DESCRIPTION 2627 "read-create access is not required. This may be 2628 read-only." 2630 ::= { rsvpCompliances 1 } 2632 rsvpSessionGroup OBJECT-GROUP 2633 OBJECTS { 2634 rsvpSessionType, rsvpSessionDestAddr, 2635 rsvpSessionDestAddrLength, rsvpSessionProtocol, 2636 rsvpSessionPort, rsvpSessionSenders, rsvpSessionReceivers, 2637 rsvpSessionRequests 2638 } 2639 STATUS current 2640 DESCRIPTION 2641 "These objects are required for RSVP Systems." 2642 ::= { rsvpGroups 1 } 2644 rsvpSenderGroup OBJECT-GROUP 2645 OBJECTS { 2646 rsvpSenderType, rsvpSenderDestAddr, rsvpSenderAddr, 2647 rsvpSenderDestAddrLength, rsvpSenderAddrLength, 2648 rsvpSenderProtocol, rsvpSenderDestPort, rsvpSenderPort, 2649 rsvpSenderHopAddr, rsvpSenderHopLih, rsvpSenderInterface, 2650 rsvpSenderTSpecRate, rsvpSenderTSpecPeakRate, 2651 rsvpSenderTSpecBurst, rsvpSenderTSpecMinTU, 2652 rsvpSenderTSpecMaxTU, rsvpSenderInterval, rsvpSenderLastChange, 2653 rsvpSenderStatus, rsvpSenderRSVPHop, rsvpSenderPolicy, 2654 rsvpSenderAdspecBreak, rsvpSenderAdspecHopCount, 2655 rsvpSenderAdspecPathBw, rsvpSenderAdspecMinLatency, 2656 rsvpSenderAdspecMtu, rsvpSenderAdspecGuaranteedSvc, 2657 rsvpSenderAdspecGuaranteedBreak, 2658 rsvpSenderAdspecGuaranteedCtot, rsvpSenderAdspecGuaranteedDtot, 2659 rsvpSenderAdspecGuaranteedCsum, rsvpSenderAdspecGuaranteedDsum, 2660 rsvpSenderAdspecGuaranteedHopCount, 2661 rsvpSenderAdspecGuaranteedPathBw, 2662 rsvpSenderAdspecGuaranteedMinLatency, 2663 rsvpSenderAdspecGuaranteedMtu, rsvpSenderAdspecCtrlLoadSvc, 2664 rsvpSenderAdspecCtrlLoadBreak, 2665 rsvpSenderAdspecCtrlLoadHopCount, 2666 rsvpSenderAdspecCtrlLoadPathBw, 2667 rsvpSenderAdspecCtrlLoadMinLatency, 2668 rsvpSenderAdspecCtrlLoadMtu, rsvpSenderNewIndex 2669 } 2670 STATUS current 2671 DESCRIPTION 2672 "These objects are required for RSVP Systems." 2673 ::= { rsvpGroups 2 } 2675 rsvpResvGroup OBJECT-GROUP 2676 OBJECTS { 2677 rsvpResvType, rsvpResvDestAddr, rsvpResvSenderAddr, 2678 rsvpResvDestAddrLength, rsvpResvSenderAddrLength, 2679 rsvpResvProtocol, rsvpResvDestPort, rsvpResvPort, 2680 rsvpResvHopAddr, rsvpResvHopLih, rsvpResvInterface, 2681 rsvpResvService, rsvpResvTSpecRate, rsvpResvTSpecBurst, 2682 rsvpResvTSpecPeakRate, rsvpResvTSpecMinTU, rsvpResvTSpecMaxTU, 2683 rsvpResvRSpecRate, rsvpResvRSpecSlack, rsvpResvInterval, 2684 rsvpResvScope, rsvpResvShared, rsvpResvExplicit, 2685 rsvpResvRSVPHop, rsvpResvLastChange, rsvpResvPolicy, 2686 rsvpResvStatus, rsvpResvNewIndex 2687 } 2688 STATUS current 2689 DESCRIPTION 2690 "These objects are required for RSVP Systems." 2691 ::= { rsvpGroups 3 } 2693 rsvpResvFwdGroup OBJECT-GROUP 2694 OBJECTS { 2695 rsvpResvFwdType, rsvpResvFwdDestAddr, rsvpResvFwdSenderAddr, 2696 rsvpResvFwdDestAddrLength, rsvpResvFwdSenderAddrLength, 2697 rsvpResvFwdProtocol, rsvpResvFwdDestPort, rsvpResvFwdPort, 2698 rsvpResvFwdHopAddr, rsvpResvFwdHopLih, rsvpResvFwdInterface, 2699 rsvpResvFwdNewIndex, rsvpResvFwdService, 2700 rsvpResvFwdTSpecPeakRate, rsvpResvFwdTSpecMinTU, 2701 rsvpResvFwdTSpecMaxTU, rsvpResvFwdTSpecRate, 2702 rsvpResvFwdTSpecBurst, rsvpResvFwdRSpecRate, 2703 rsvpResvFwdRSpecSlack, rsvpResvFwdInterval, rsvpResvFwdScope, 2704 rsvpResvFwdShared, rsvpResvFwdExplicit, rsvpResvFwdRSVPHop, 2705 rsvpResvFwdLastChange, rsvpResvFwdPolicy, rsvpResvFwdStatus 2706 } 2707 STATUS current 2708 DESCRIPTION 2709 "These objects are optional, used for some RSVP 2710 Systems." 2711 ::= { rsvpGroups 4 } 2713 rsvpIfGroup OBJECT-GROUP 2714 OBJECTS { 2715 rsvpIfUdpNbrs, rsvpIfIpNbrs, rsvpIfNbrs, rsvpIfEnabled, 2716 rsvpIfUdpRequired, rsvpIfRefreshBlockadeMultiple, 2717 rsvpIfRefreshMultiple, rsvpIfRefreshInterval, rsvpIfTTL, 2718 rsvpIfRouteDelay, rsvpIfStatus 2719 } 2720 STATUS current 2721 DESCRIPTION 2722 "These objects are required for RSVP Systems." 2723 ::= { rsvpGroups 6 } 2725 rsvpNbrGroup OBJECT-GROUP 2726 OBJECTS { 2727 rsvpNbrProtocol, rsvpNbrStatus 2728 } 2729 STATUS current 2730 DESCRIPTION 2731 "These objects are required for RSVP Systems." 2732 ::= { rsvpGroups 7 } 2734 END 2735 6. Acknowledgements 2737 This document was produced by the RSVP Working Group. 2739 7. References 2741 [1] M.T. Rose (editor), Management Information Base for 2742 Network Management of TCP/IP-based internets, Internet 2743 Working Group Request for Comments 1213. Network 2744 Information Center, SRI International, Menlo Park, 2745 California, (May, 1990). 2747 [2] Information processing systems - Open Systems 2748 Interconnection - Specification of Abstract Syntax 2749 Notation One (ASN.1), International Organization for 2750 Standardization. International Standard 8824, (December, 2751 1987). 2753 [3] Information processing systems - Open Systems 2754 Interconnection - Specification of Basic Encoding Rules 2755 for Abstract Notation One (ASN.1), International 2756 Organization for Standardization. International Standard 2757 8825, (December, 1987). 2759 Table of Contents 2761 1 Status of this Memo ................................... 1 2762 2 Abstract .............................................. 2 2763 3 The SNMPv2 Network Management Framework ............... 3 2764 3.1 Object Definitions .................................. 3 2765 4 Overview .............................................. 3 2766 4.1 Textual Conventions ................................. 3 2767 4.2 Structure of MIB .................................... 4 2768 5 Definitions ........................................... 5 2769 5.1 RSVP Session Statistics Database .................... 6 2770 5.1 RSVP Session Sender Database ........................ 10 2771 5.2 RSVP Reservations Requested Database ................ 29 2772 5.3 RSVP Reservation Requests Database .................. 41 2773 5.4 RSVP Interface Attributes Database .................. 53 2774 5.5 RSVP Neighbor Database .............................. 58 2775 6 Acknowledgements ...................................... 78 2776 7 References ............................................ 79