idnits 2.17.1 draft-ietf-vrrp-mib-02.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-23) 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 -- 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 == The page length should not exceed 58 lines per page, but there was 1 longer page, the longest (page 1) being 121 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** 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 28 instances of too long lines in the document, the longest one being 4 characters in excess of 72. ** There is 1 instance of lines with control characters in the document. ** The abstract seems to contain references ([2], [5], [1]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 606 has weird spacing: '...nsition to be...' -- 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.) -- Couldn't find a document date in the document -- date freshness check skipped. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: '7' is defined on line 1134, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2338 (ref. '1') (Obsoleted by RFC 3768) ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. '3') ** Obsolete normative reference: RFC 1902 (ref. '5') (Obsoleted by RFC 2578) ** Obsolete normative reference: RFC 1905 (ref. '6') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2223 (ref. '7') (Obsoleted by RFC 7322) ** Obsolete normative reference: RFC 1573 (ref. '8') (Obsoleted by RFC 2233) -- Possible downref: Non-RFC (?) normative reference: ref. '9' Summary: 18 errors (**), 0 flaws (~~), 4 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 INTERNET-DRAFT B. Jewell 2 July 23, 1998 D. Chuang 3 3Com, Inc. 5 Definitions of Managed Objects for the Virtual Router Redundancy Protocol 6 using SNMPv2 8 10 Status of this Memo 12 This document is an Internet-Draft. Internet-Drafts are working 13 documents of the Internet Engineering Task Force (IETF), its areas, 14 and its working groups. Note that other groups may also distribute 15 working documents as Internet-Drafts. 17 Internet-Drafts are draft documents valid for a maximum of six months 18 and may be updated, replaced, or obsoleted by other documents at any 19 time. It is inappropriate to use Internet-Drafts as reference 20 material or to cite them other than as ``work in progress.'' 22 To view the entire list of current Internet-Drafts, please check 23 the "1id-abstracts.txt" listing contained in the Internet-Drafts 24 Shadow Directories on ftp.is.co.za (Africa), ftp.nordu.net 25 (Northern Europe), ftp.nis.garr.it (Southern Europe), munnari.oz.au 26 (Pacific Rim), ftp.ietf.org (US East Coast), or ftp.isi.edu 27 (US West Coast). 29 Abstract 31 This specification defines an extension to the Management Information 32 Base (MIB) for use with SNMP-based network management. In 33 particular, it defines objects for configuring, monitoring, and 34 controlling routers that employ the Virtual Router Redundancy 35 Protocol (VRRP) [1]. 37 This memo specifies a MIB module in a manner that is compliant 38 with both the SNMPv2 SMI [5], and semantically identical to the SNMPv1 39 definitions [2]. 41 Table of Contents 43 1.0 The SNMP Network Management Framework ................ 3 44 1.1 Object Definitions ................................... 3 45 2.0 Overview ............................................ 4 46 2.1 MIB Structure ........................................ 4 47 2.2 Virtual Router Redundancy Protocol ................... 5 48 2.3 VRRP MIB Table Design ................................ 5 49 2.3.1 Relation to Interface Group ....................... 5 50 2.4 VRRP Scenarios ....................................... 6 51 2.4.1 Scenario #1 ....................................... 6 52 2.4.2 Scenario #2 ....................................... 8 53 3.0 Definitions ........................................... 11 54 4.0 Acknowledgements ...................................... 26 55 5.0 References ............................................ 26 56 6.0 Author's Address ...................................... 27 57 7.0 Change Log ............................................ 28 59 1. The SNMPv2 Network Management Framework 61 The SNMP Network Management Framework presently consists of three 62 major components. They are: 64 o the SMI, described in RFC 1902 [5] - the mechanisms used for 65 describing and naming objects for the purpose of management. 67 o the MIB-II, STD 17, RFC 1213 [4] - the core set of managed 68 objects for the Internet suite of protocols. 70 o the protocol, STD 15, RFC 1157 [3] and/or RFC 1905 [6], - the 71 protocol for accessing managed objects. 73 The Framework permits new objects to be defined for the purpose of 74 experimentation and evaluation. 76 1.1 Object Definitions 78 Managed objects are accessed via a virtual information store, termed 79 the Management Information Base or MIB. Objects in the MIB are 80 defined using the subset of Abstract Syntax Notation One (ASN.1) 81 defined in the SMI. In particular, each object type is named by an 82 OBJECT IDENTIFIER, an administratively assigned name. The object 83 type together with an object instance serves to uniquely identify a 84 specific instantiation of the object. For human convenience, we 85 often use a textual string, termed the descriptor, to also refer to 86 the object type. 88 The syntax of an object type defines the abstract data structure 89 corresponding to that object type. The ASN.1 language is used for 90 this purpose. However, the SMI [5] purposely restricts the ASN.1 91 constructs which may be used. These restrictions are explicitly made 92 for simplicity. 94 The encoding of an object type is simply how that object type is 95 represented using the object type's syntax. Implicitly tied to the 96 notion of an object type's syntax and encoding is how the object type 97 is represented when being transmitted on the network. 99 The SMI specifies the use of the basic encoding rules of ASN.1 [9], 100 subject to the additional requirements imposed by the SNMP. 102 2.0 Overview 104 This memo identifies the set of objects for configuring, monitoring, 105 and controlling the Virtual Router Redundancy Protocol (VRRP), as 106 defined in RFC 2338 [1]. 108 VRRP specifies an election protocol that dynamically allows a set of 109 routers running VRRP to backup each other on a LAN. The VRRP router 110 controlling one or more IP addresses is called the "master router" and 111 forwards packets sent to these IP addresses. In the event that the 112 master router fails, a backup VRRP router assumes the packet fowarding 113 responsibilities of the failed router. Thus, IP packets with the 114 destination address of the failed router will be fowarded by another 115 VRRP router that has assumed control. Hence, VRRP provides redundancy 116 in routed networks without requiring configuration of dynamic 117 routing or router discovery protocols on every end-host. 119 2.1 VRRP MIB Structure 121 The VRRP MIB contains three conformance groups: 123 - vrrpOperations Group: Objects related to VRRP router's configuration 124 and control. 126 - vrrpStatistics Group: Objects containing information useful in 127 monitoring the operation of VRRP routers. 129 - vrrpNotifications Group: Consists of objects and definitions for 130 use in SNMP traps sent by VRRP routers. 132 Tables in the MIB include the following: 134 (1) The vrrpOperTable, which contains objects that define the operational 135 characteristics of a VRRP router. Rows in this table correspond to 136 instances of virtual routers. 138 (2) The vrrpAssoIpAddrTable, which contains the addresses of the 139 virtual router(s) that a given VRRP router is backing up. 141 (3) The vrrpRouterStatsTable which contains the operating statistics 142 for a VRRP router. 144 2.2 Virtual Router Redundancy Protocol 146 This MIB is based on the following characteristics of VRRP as defined 147 in the VRRP specification [1]. 149 - A "VRRP router" is one that is configured to run the VRRP protocol 150 in conjunction with one or more other VRRP routers attached to a LAN. 152 - A VRRP router can be running one or more instances of a virtual 153 router. 155 - A "virtual router" is an abstraction which consists of two 156 or more physical routers. A virtual router essentially identifies 157 a pool of physical routers that are capable of providing routing 158 services for one or more associated IP addresses in the event of 159 a failure of a router that is a member of the virtual router group. 161 - An instance of a virtual router (on a physical VRRP router), can be 162 uniquely identified by a combination of the 'IF Index' [4] and 163 "Virtual Router Identifier" (VRID). 165 - For each VRID there is a set of one or more "associated IP addresses" 166 that are backed-up by the virtual router. 168 2.3 VRRP MIB Table Design 170 The tables in the VRRP MIB are structured with the assumption that 171 a VRRP network management application would likely be designed to 172 display information or provide configuration about a VRRP router on a 173 "per-virtual-router basis". Thus, the tables defined in the MIB 174 consist of conceptual rows which are grouped in a manner to present 175 a view of individual virtual routers with a minimal number of SNMP 176 operations. 178 2.3.1 Relation to Interface Group (RFC 1573) [8]. 180 Since a router can be participating in VRRP on one or more physical 181 interfaces, "ifIndex" is used as an index into the tables defined in 182 the VRRP MIB. 184 2.4 VRRP Scenarios 186 The following section provides examples of how some of the objects 187 in this MIB are instantiated for two different VRRP scenarios. 189 KEY: 190 ---- 191 The labels in the following table diagrams correspond to the actual 192 MIB objects as follows: 194 if = vrrpOperIfIndex 195 VrId = vrrpOperVrId 196 State = vrrpOperState 197 Prior = vrrpOperPriority 198 AddrCnt = vrrpOperIpAddrCount 199 IpAddr = vrrpOperMasterIpAddr 200 RowStat = vrrpOperRowStatus 202 2.4.1 VRRP Scenario #1 204 The following figure shows a simple network with two VRRP routers 205 configured with two virtual routers. This sample topology is taken 206 from the VRRP specification [1]. Addresses in '()' indicate the IP 207 address of the default gateway for a given host, H1 - H4. In the 208 diagram, "Interface" is used in the context defined in MIB-II [4]. 210 VRID=1 VRID=2 211 +-----+ +-----+ 212 | MR1 | | MR2 | 213 | & | | & | 214 | BR2 | | BR1 | 215 +-----+ +-----+ 216 IP A ---------->* *<---------- IP B 217 Interface=I1 | | Interface=I2 218 | | 219 | | 220 ------------------+------------+-----+--------+--------+--------+-- 221 ^ ^ ^ ^ 222 | | | | 223 (IP A) (IP A) (IP A) (IP A) 224 | | | | 225 +--+--+ +--+--+ +--+--+ +--+--+ 226 | H1 | | H2 | | H3 | | H4 | 227 +-----+ +-----+ +--+--+ +--+--+ 229 ----- MIB Tables For VRRP Router "IP A": ----- 231 vrrpOperTable 232 ------------- 234 | if | VrId | State | Prior | AddrCnt | IpAddr | ... | RowStat | 235 +----+------+-------+-------+---------+--------+-( )-+---------+ 236 | | | | | | | | | 237 | I1 | 01 | M | 255 | 1 | A | | active | 238 | | | | | | | | | 239 +----+------+-------+-------+---------+--------+-( )-+---------+ 240 | | | | | | | | | 241 | I1 | 02 | B | 1-254 | 1 | B | | active | 242 | | | | | | | | | 243 +----+------+-------+-------+---------+--------+-( )-+---------+ 245 vrrpAssoIpAddrTable 246 ------------------- 248 | if | VrId | IP | RowStat | 249 +----+------+-------+---------+ 250 | | | | | 251 | I1 | 01 | A | active | 252 | | | | | 253 +----+------+-------+---------+ 254 | | | | | 255 | I1 | 02 | B | active | 256 | | | | | 257 +----+------+-------+---------+ 259 ----- MIB Tables For VRRP Router "IP B": ----- 261 vrrpOperTable 262 ------------- 264 | if | VrId | State | Prior | AddrCnt | IpAddr | ... | RowStat | 265 +----+------+-------+-------+---------+--------+-( )-+---------+ 266 | | | | | | | | | 267 | I2 | 01 | B | 1-254 | 1 | A | | active | 268 | | | | | | | | | 269 +----+------+-------+-------+---------+--------+-( )-+---------+ 270 | | | | | | | | | 271 | I2 | 02 | M | 255 | 1 | B | | active | 272 | | | | | | | | | 273 +----+------+-------+-------+---------+--------+-( )-+---------+ 274 vrrpAssoIpAddrTable 275 ------------------- 277 | if | VrId | IP | RowStat | 278 +----+------+-------+---------+ 279 | | | | | 280 | I2 | 01 | A | active | 281 | | | | | 282 +----+------+-------+---------+ 283 | | | | | 284 | I2 | 02 | B | active | 285 | | | | | 286 +----+------+-------+---------+ 288 NOTES: 290 1) "I1" and "I2" are used to designate IF indices on each respective 291 router. 293 2) For "State": M = Master; B = Backup. 295 3) In the vrrpOperTable, a "priority" of 255 indicates that the 296 respective router owns the IP address, e.g., this IP address is 297 native to the router (i.e., "the IP Address Owner" [1]). 299 2.4.2 VRRP Scenario #2 301 The following figure shows a simple network with two virtual routers. 302 Here, a single interface has been configured with two IP addresses. 303 Again, addresses in () indicate the IP address of the default gateway 304 for a given host, H1 - H2. 306 VRID=1 VRID=2 307 +-----+ +-----+ 308 | MR1 | | MR2 | 309 | & | | & | 310 | BR2 | | BR1 | 311 +-----+ +-----+ 312 IP A ---------->* *<---------- IP B 313 IP C | | Interface=I2 314 Interface=I1 | | 315 | | 316 | | 317 ------------------+------------+-----+--------+ 318 ^ ^ 319 | | 320 (IP A) (IP B) 321 | | 322 +--+--+ +--+--+ 323 | H1 | | H2 | 324 +-----+ +-----+ 326 ----- MIB Tables For VRRP Router "IP A": ----- 328 vrrpOperTable 329 ------------- 331 | if | VrId | State | Prior | AddrCnt | IpAddr | ... | RowStat | 332 +----+------+-------+-------+---------+--------+-( )-+---------+ 333 | | | | | | | | | 334 | I1 | 01 | M | 255 | 2 | A | | active | 335 | | | | | | | | | 336 +----+------+-------+-------+---------+--------+-( )-+---------+ 337 | | | | | | | | | 338 | I1 | 02 | B | 1-254 | 1 | B | | active | 339 | | | | | | | | | 340 +----+------+-------+-------+---------+--------+-( )-+---------+ 342 vrrpAssoIpAddrTable 343 ------------------- 345 | if | VrId | IP | RowStat | 346 +----+------+-------+---------+ 347 | | | | | 348 | I1 | 01 | A | active | 349 | | | | | 350 +----+------+-------+---------+ 351 | | | | | 352 | I1 | 01 | C | active | 353 | | | | | 354 +----+------+-------+---------+ 355 | | | | | 356 | I1 | 02 | B | active | 357 | | | | | 358 +----+------+-------+---------+ 360 ----- MIB Tables For VRRP Router "IP B": ----- 362 vrrpOperTable 363 ------------- 365 | if | VrId | State | Prior | AddrCnt | IpAddr | ... | RowStat | 366 +----+------+-------+-------+---------+--------+-( )-+---------+ 367 | | | | | | | | | 368 | I2 | 01 | B | 1-254 | 2 | A | | active | 369 | | | | | | | | | 370 +----+------+-------+-------+---------+--------+-( )-+---------+ 371 | | | | | | | | | 372 | I2 | 02 | M | 255 | 1 | B | | active | 373 | | | | | | | | | 374 +----+------+-------+-------+---------+--------+-( )-+---------+ 375 vrrpAssoIpAddrTable 376 ------------------- 378 | if | VrId | IP | RowStat | 379 +----+------+-------+---------+ 380 | | | | | 381 | I2 | 01 | A | active | 382 | | | | | 383 +----+------+-------+---------+ 384 | | | | | 385 | I2 | 01 | C | active | 386 | | | | | 387 +----+------+-------+---------+ 388 | | | | | 389 | I2 | 02 | B | active | 390 | | | | | 391 +----+------+-------+---------+ 393 3. Definitions 395 VRRP-MIB DEFINITIONS ::= BEGIN 397 IMPORTS 398 MODULE-IDENTITY, OBJECT-TYPE, 399 NOTIFICATION-TYPE, Counter32, 400 Integer32, IpAddress FROM SNMPv2-SMI -- RFC 1902 401 TEXTUAL-CONVENTION, RowStatus, 402 MacAddress, TruthValue, TimeStamp FROM SNMPv2-TC -- RFC 1903 403 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF -- RFC 1904 404 mib-2, ifIndex FROM RFC1213-MIB; 406 vrrp MODULE-IDENTITY 407 LAST-UPDATED "9807230900Z" 408 ORGANIZATION "IETF VRRP Working Group" 409 CONTACT-INFO 410 "Brian R. Jewell 411 Postal: 3Com Corporation 412 5400 BayFront Plaza 413 Santa Clara, California 95052 414 Tel: +1 408 326 6173 415 E-Mail: bjewell@3com.com" 417 DESCRIPTION 418 "The MIB module to describe the VRRP Version 2 Protocol." 419 ::= { mib-2 46 } -- Temporary until assigned. 421 vrrpMIB OBJECT IDENTIFIER ::= { vrrp 1 } 423 -- ******************************************************************* 424 -- Textual Conventions 425 -- ******************************************************************* 427 VrId ::= TEXTUAL-CONVENTION 428 STATUS current 429 DESCRIPTION 430 "A number which, along with an interface index (ifIndex), 431 serves to uniquely identify a virtual router on a given VRRP 432 router. A set of one or more associated addresses is assigned 433 to a VRID." 434 SYNTAX Integer32 (1..255) 436 -- ******************************************************************* 437 -- VRRP MIB Groups 438 -- ******************************************************************* 440 vrrpOperations OBJECT IDENTIFIER ::= { vrrpMIB 1 } 441 vrrpStatistics OBJECT IDENTIFIER ::= { vrrpMIB 2 } 442 vrrpNotifications OBJECT IDENTIFIER ::= { vrrpMIB 3 } 443 vrrpConformance OBJECT IDENTIFIER ::= { vrrpMIB 4 } 445 -- ******************************************************************* 446 -- Start of MIB objects 447 -- ******************************************************************* 449 vrrpNodeVersion OBJECT-TYPE 450 SYNTAX OCTET STRING (SIZE (1)) 451 MAX-ACCESS read-only 452 STATUS current 453 DESCRIPTION 454 "This value identifies the particular version of the VRRP 455 supported by this node. The current value is '02'." 456 REFERENCE 457 "Virtual Router Redundancy Protocol, RFC 2338" 458 DEFVAL { '02'H } 459 ::= { vrrpOperations 1 } 461 vrrpTrapCntl OBJECT-TYPE 462 SYNTAX INTEGER { 463 enabled (1), 464 disabled (2) 465 } 466 MAX-ACCESS read-write 467 STATUS current 468 DESCRIPTION 469 "Indicates whether the VRRP-enabled router will generate 470 SNMP traps for events defined in this MIB. 'Enabled' 471 results in SNMP traps; 'disabled', no traps are sent." 472 DEFVAL { enabled } 473 ::= { vrrpOperations 2 } 475 -- ******************************************************************* 476 -- VRRP Operations Table 477 -- ******************************************************************* 479 vrrpOperTable OBJECT-TYPE 480 SYNTAX SEQUENCE OF VrrpOperEntry 481 MAX-ACCESS not-accessible 482 STATUS current 483 DESCRIPTION 484 "Operations table for a VRRP router which consists of a 485 sequence (i.e., one or more conceptual rows) of 486 'vrrpOperEntry' items." 487 ::= { vrrpOperations 3 } 489 vrrpOperEntry OBJECT-TYPE 490 SYNTAX VrrpOperEntry 491 MAX-ACCESS not-accessible 492 STATUS current 493 DESCRIPTION 494 "An entry in the vrrpOperTable containing the operational 495 characteristics of a virtual router. On a VRRP router, 496 a given virtual router is identified by a combination 497 of the IF index and VRID." 498 INDEX { ifIndex, vrrpOperVrId } 499 ::= { vrrpOperTable 1 } 501 VrrpOperEntry ::= 502 SEQUENCE { 503 vrrpOperVrId 504 VrId, 505 vrrpOperVirtualMacAddr 506 MacAddress, 507 vrrpOperState 508 INTEGER, 509 vrrpOperControl 510 INTEGER, 511 vrrpOperPriority 512 Integer32, 513 vrrpOperIpAddrCount 514 Integer32, 515 vrrpOperMasterIpAddr 516 IpAddress, 517 vrrpOperAuthType 518 INTEGER, 519 vrrpOperAuthKey 520 OCTET STRING, 521 vrrpOperAdvertisementInterval 522 Integer32, 524 vrrpOperPreemptMode 525 TruthValue, 526 vrrpOperVirtualRouterUpTime 527 TimeStamp, 528 vrrpOperProtocol 529 INTEGER, 530 vrrpOperRowStatus 531 RowStatus 532 } 534 vrrpOperVrId OBJECT-TYPE 535 SYNTAX VrId 536 MAX-ACCESS not-accessible 537 STATUS current 538 DESCRIPTION 539 "This object contains the Virtual Router Identifier (VRID)." 540 ::= { vrrpOperEntry 2 } 542 vrrpOperVirtualMacAddr OBJECT-TYPE 543 SYNTAX MacAddress 544 MAX-ACCESS read-only 545 STATUS current 546 DESCRIPTION 547 "The virtual MAC address of the virtual router. This is derived 548 as follows: 00-00-5E-00-01-. 550 Where the first three octets consist of the IANA's OUI; The 551 next two octets indicate the address block of the VRRP protocol; 552 and the remaining octets consist of the VRID. 554 Although this object can be derived from the 'vrrpOperVrId' 555 object, it is included here, for completeness, so that it 556 is easily obtainable by a management application and can be 557 included in VRRP-related SNMP traps." 558 REFERENCE 559 "rfc1903 - MacAddress" 560 ::= { vrrpOperEntry 3 } 562 vrrpOperState OBJECT-TYPE 563 SYNTAX INTEGER { 564 initialize(1), -- Waiting for a startup event 565 backup(2), -- Monitoring the state/availability of 566 -- master router 567 master(3) -- Forwarding IP addresses associated with 568 -- this virtual router. 569 } 570 MAX-ACCESS read-only 571 STATUS current 572 DESCRIPTION 573 "The current state of the virtual router." 574 ::= { vrrpOperEntry 4 } 576 vrrpOperControl OBJECT-TYPE 577 SYNTAX INTEGER { 578 enabled(1), 579 disabled(2) 580 } 581 MAX-ACCESS read-create 582 STATUS current 583 DESCRIPTION 584 "This object will enable/disable the virtual router 585 function. Setting the value to 'enabled', will transition 586 the state of the router from 'initialize to 'backup' or 587 'master'. Setting the value to 'disabled', will transition 588 the router from 'master' or 'backup' to 'initialize'. State 589 transitions may not be immediate; they sometimes depend on 590 other factors, such as the interface state." 591 DEFVAL { enabled } 592 ::= { vrrpOperEntry 5 } 594 vrrpOperPriority OBJECT-TYPE 595 SYNTAX Integer32 (0..255) 596 MAX-ACCESS read-create 597 STATUS current 598 DESCRIPTION 599 "This object specifies the priority to be used for the 600 virtual router master election process. Higher values imply 601 higher priority. 603 A priority of '0', although not settable, is sent by 604 the master router to indicate that this router has ceased 605 to particpate in VRRP and a backup virtual router should 606 transition to become a new master. 608 A priority of 255 is used for the router that owns the 609 associated IP address(es)." 610 DEFVAL { 100 } 611 ::= { vrrpOperEntry 6 } 613 vrrpOperIpAddrCount OBJECT-TYPE 614 SYNTAX Integer32 (1..255) 615 MAX-ACCESS read-only 616 STATUS current 617 DESCRIPTION 618 "The number of IP addresses that are associated with this 619 virtual router. This number is equal to the number of rows 620 in the vrrpAssoIpAddrTable that correspond to a given IF 621 index/VRID pair." 622 ::= { vrrpOperEntry 7 } 624 vrrpOperMasterIpAddr OBJECT-TYPE 625 SYNTAX IpAddress 626 MAX-ACCESS read-only 627 STATUS current 628 DESCRIPTION 629 "The master router's real (primary) IP address. This is 630 the IP address listed as the source in VRRP advertisement 631 last received by this virtual router" 632 ::= { vrrpOperEntry 8 } 634 vrrpOperAuthType OBJECT-TYPE 635 SYNTAX INTEGER { 636 noAuthentication(1), -- VRRP protocol exchanges are not 637 -- authenticated. 638 simpleTextPassword(2), -- Exchanges are authenticated by a 639 -- clear text password. 640 ipAuthenticationHeader(3) -- Exchanges are authenticated using 641 -- the IP authentication header. 642 } 643 MAX-ACCESS read-only 644 STATUS current 645 DESCRIPTION 646 "Authentication type used for VRRP protocol exchanges between 647 virtual routers. This value of this object is the same for a 648 given ifIndex." 649 ::= { vrrpOperEntry 9 } 651 vrrpOperAuthKey OBJECT-TYPE 652 SYNTAX OCTET STRING (SIZE (0..16)) 653 MAX-ACCESS read-only 654 STATUS current 655 DESCRIPTION 656 "The Authentication Key. This object is set according to 657 the value of the 'vrrpOperAuthType' object 658 ('simpleTextPassword' or 'ipAuthenticationHeader'). If the 659 length of the value is less than 16 octets, the agent will 660 left adjust and zero fill to 16 octets. The value of this 661 object is the same for a given ifIndex. 663 When read, vrrpOperAuthKey always returns an Octet String 664 of length zero." 665 DEFVAL { '00000000000000000000000000000000'H } 666 -- 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0 667 ::= { vrrpOperEntry 10 } 669 vrrpOperAdvertisementInterval OBJECT-TYPE 670 SYNTAX Integer32 (1..255) 671 MAX-ACCESS read-create 672 STATUS current 673 DESCRIPTION 674 "The time interval, in seconds, between sending 675 advertisement messages. Only the master router sends 676 VRRP advertisements." 677 DEFVAL { 1 } 678 ::= { vrrpOperEntry 11 } 680 vrrpOperPreemptMode OBJECT-TYPE 681 SYNTAX TruthValue 682 MAX-ACCESS read-create 683 STATUS current 684 DESCRIPTION 685 "Controls whether a higher priority virtual router will 686 preempt a lower priority master." 687 DEFVAL { true } 688 ::= { vrrpOperEntry 12 } 690 vrrpOperVirtualRouterUpTime OBJECT-TYPE 691 SYNTAX TimeStamp 692 MAX-ACCESS read-only 693 STATUS current 694 DESCRIPTION 695 "This is the time interval (in hundredths of a second) 696 since this virtual router was initialized." 697 ::= { vrrpOperEntry 13 } 699 vrrpOperProtocol OBJECT-TYPE 700 SYNTAX INTEGER { 701 ip (1), 702 bridge (2), 703 decnet (3), 704 other (4) 705 } 706 MAX-ACCESS read-create 707 STATUS current 708 DESCRIPTION 709 "The particular protocol being controlled by this Virtual 710 Router." 711 DEFVAL { ip } 712 ::= { vrrpOperEntry 14 } 714 vrrpOperRowStatus OBJECT-TYPE 715 SYNTAX RowStatus 716 MAX-ACCESS read-create 717 STATUS current 718 DESCRIPTION 719 "The row status variable, used according to installation 720 and removal conventions for conceptual rows. Setting this 721 object to 'createAndGo' results in enabling the VRRP 722 protocol for this virtual router. The information required 723 to actually create the conceptual row may be included in 724 the SET primitive or may be initialized by the agent on 725 the virtual router. Destroying the entry or setting it to 726 'notInService' disables VRRP on this virtual router." 727 ::= { vrrpOperEntry 15 } 729 -- ******************************************************************* 730 -- VRRP Associated IP Address Table 731 -- ******************************************************************* 733 vrrpAssoIpAddrTable OBJECT-TYPE 734 SYNTAX SEQUENCE OF VrrpAssoIpAddrEntry 735 MAX-ACCESS not-accessible 736 STATUS current 737 DESCRIPTION 738 "The table of addresses associated with this virtual router." 739 ::= { vrrpOperations 4 } 741 vrrpAssoIpAddrEntry OBJECT-TYPE 742 SYNTAX VrrpAssoIpAddrEntry 743 MAX-ACCESS not-accessible 744 STATUS current 745 DESCRIPTION 746 "An entry in the table contains an IP address that is 747 associated with a virtual router. The number of rows for 748 a given ifIndex and VrId will equal the number of IP 749 addresses associated (e.g., backed up) by the virtual 750 router (equivalent to 'vrrpOperIpAddrCount')." 751 INDEX { ifIndex, vrrpOperVrId, vrrpAssoIpAddr } 752 ::= { vrrpAssoIpAddrTable 1 } 754 VrrpAssoIpAddrEntry ::= 755 SEQUENCE { 756 vrrpAssoIpAddr 757 IpAddress, 758 vrrpAssoIpAddrStatus 759 RowStatus 760 } 761 vrrpAssoIpAddr OBJECT-TYPE 762 SYNTAX IpAddress 763 MAX-ACCESS not-accessible 764 STATUS current 765 DESCRIPTION 766 "The assigned IP addresses that a virtual router is responsible 767 for backing up." 768 ::= { vrrpAssoIpAddrEntry 2 } 770 vrrpAssoIpAddrStatus OBJECT-TYPE 771 SYNTAX RowStatus 772 MAX-ACCESS read-create 773 STATUS current 774 DESCRIPTION 775 "The row status variable, used according to installation 776 and removal conventions for conceptual rows. Setting this 777 object to 'createAndGo' results in the addition of an 778 associated address for a virtual router. The information 779 required to actually create the conceptual may be included 780 in the SET primitive or may be initialized by the agent on 781 the VRRP router. Destroying the entry or setting it to 782 'notInService' removes the associated address from the 783 virtual router." 784 ::= { vrrpAssoIpAddrEntry 3 } 786 -- ******************************************************************* 787 -- VRRP Router Statistics Table 788 -- ******************************************************************* 790 vrrpRouterStatsTable OBJECT-TYPE 791 SYNTAX SEQUENCE OF VrrpRouterStatsEntry 792 MAX-ACCESS not-accessible 793 STATUS current 794 DESCRIPTION 795 "Table of virtual router statistics." 796 ::= { vrrpStatistics 1 } 798 vrrpRouterStatsEntry OBJECT-TYPE 799 SYNTAX VrrpRouterStatsEntry 800 MAX-ACCESS not-accessible 801 STATUS current 802 DESCRIPTION 803 "An entry in the table, containing statistics information 804 about a given virtual router." 805 INDEX { ifIndex, vrrpOperVrId } 806 ::= { vrrpRouterStatsTable 1 } 808 VrrpRouterStatsEntry ::= 809 SEQUENCE { 810 vrrpStatsBecomeMaster 811 Counter32, 812 vrrpStatsAdvertiseRcvd 813 Counter32, 814 vrrpStatsChecksumErrors 815 Counter32, 816 vrrpStatsVersionErrors 817 Counter32, 818 vrrpStatsVrIdErrors 819 Counter32, 820 vrrpStatsAdvertiseIntervalErrors 821 Counter32, 822 vrrpStatsSecurityViolations 823 Counter32, 824 vrrpStatsIpTtlErrors 825 Counter32, 826 vrrpStatsPriorityZeroPktsRcvd 827 Counter32, 828 vrrpStatsPriorityZeroPktsSent 829 Counter32, 830 vrrpStatsInvalidTypePktsRcvd 831 Counter32, 832 vrrpStatsAddressListErrors 833 Counter32, 834 vrrpStatsUnknownAuthType 835 Counter32, 836 vrrpStatsAuthTypeErrors 837 Counter32 838 } 840 vrrpStatsBecomeMaster OBJECT-TYPE 841 SYNTAX Counter32 842 MAX-ACCESS read-only 843 STATUS current 844 DESCRIPTION 845 "The total number of times that this virtual router's state 846 has transitioned to MASTER." 847 ::= { vrrpRouterStatsEntry 1 } 849 vrrpStatsAdvertiseRcvd OBJECT-TYPE 850 SYNTAX Counter32 851 MAX-ACCESS read-only 852 STATUS current 853 DESCRIPTION 854 "The total number of VRRP advertisements received by this 855 virtual router." 856 ::= { vrrpRouterStatsEntry 2 } 858 vrrpStatsChecksumErrors OBJECT-TYPE 859 SYNTAX Counter32 860 MAX-ACCESS read-only 861 STATUS current 862 DESCRIPTION 863 "The total number of VRRP packets received with an invalid 864 VRRP checksum value." 865 ::= { vrrpRouterStatsEntry 3 } 867 vrrpStatsVersionErrors OBJECT-TYPE 868 SYNTAX Counter32 869 MAX-ACCESS read-only 870 STATUS current 871 DESCRIPTION 872 "The total number of VRRP packets received with an unknown 873 or unsupported version number." 874 ::= { vrrpRouterStatsEntry 4 } 876 vrrpStatsVrIdErrors OBJECT-TYPE 877 SYNTAX Counter32 878 MAX-ACCESS read-only 879 STATUS current 880 DESCRIPTION 881 "The total number of VRRP packets received with an invalid 882 VRID for this virtual router." 883 ::= { vrrpRouterStatsEntry 5 } 885 vrrpStatsAdvertiseIntervalErrors OBJECT-TYPE 886 SYNTAX Counter32 887 MAX-ACCESS read-only 888 STATUS current 889 DESCRIPTION 890 "The total number of VRRP advertisement packets received 891 for which the advertisement interval is different than the 892 one configured for the local virtual router." 893 ::= { vrrpRouterStatsEntry 6 } 895 vrrpStatsSecurityViolations OBJECT-TYPE 896 SYNTAX Counter32 897 MAX-ACCESS read-only 898 STATUS current 899 DESCRIPTION 900 "The total number of VRRP packets received that do not pass 901 the simple text password authentication check." 902 ::= { vrrpRouterStatsEntry 7 } 904 vrrpStatsIpTtlErrors OBJECT-TYPE 905 SYNTAX Counter32 906 MAX-ACCESS read-only 907 STATUS current 908 DESCRIPTION 909 "The total number of VRRP packets received by the virtual 910 router with IP TTL (Time-To-Live) not equal to 255." 911 ::= { vrrpRouterStatsEntry 8 } 913 vrrpStatsPriorityZeroPktsRcvd OBJECT-TYPE 914 SYNTAX Counter32 915 MAX-ACCESS read-only 916 STATUS current 917 DESCRIPTION 918 "The total number of VRRP packets received by the virtual 919 router with a priority of '0'." 920 ::= { vrrpRouterStatsEntry 9 } 922 vrrpStatsPriorityZeroPktsSent OBJECT-TYPE 923 SYNTAX Counter32 924 MAX-ACCESS read-only 925 STATUS current 926 DESCRIPTION 927 "The total number of VRRP packets sent by the virtual router 928 with a priority of '0'." 929 ::= { vrrpRouterStatsEntry 10 } 931 vrrpStatsInvalidTypePktsRcvd OBJECT-TYPE 932 SYNTAX Counter32 933 MAX-ACCESS read-only 934 STATUS current 935 DESCRIPTION 936 "The number of VRRP packets received by the virtual router 937 with an invalid value in the 'type' field." 938 ::= { vrrpRouterStatsEntry 11 } 940 vrrpStatsAddressListErrors OBJECT-TYPE 941 SYNTAX Counter32 942 MAX-ACCESS read-only 943 STATUS current 944 DESCRIPTION 945 "The total number of packets received for which the address 946 list does not match the locally configured list for the 947 virtual router." 948 ::= { vrrpRouterStatsEntry 12 } 950 vrrpStatsUnknownAuthType OBJECT-TYPE 951 SYNTAX Counter32 952 MAX-ACCESS read-only 953 STATUS current 954 DESCRIPTION 955 "The total number of packets received with an unknown 956 authentication type." 957 ::= { vrrpRouterStatsEntry 13 } 959 vrrpStatsAuthTypeErrors OBJECT-TYPE 960 SYNTAX Counter32 961 MAX-ACCESS read-only 962 STATUS current 963 DESCRIPTION 964 "The total number of packets received with 'Auth Type' not 965 equal to the locally configured authentication method 966 ('vrrpOperAuthType')." 967 ::= { vrrpRouterStatsEntry 14 } 969 -- ******************************************************************* 970 -- Trap Definitions 971 -- ******************************************************************* 973 vrrpTraps OBJECT IDENTIFIER ::= { vrrpNotifications 1 } 975 vrrpTrapPacketSrc OBJECT-TYPE 976 SYNTAX IpAddress 977 MAX-ACCESS accessible-for-notify 978 STATUS current 979 DESCRIPTION 980 "The IP address of an inbound VRRP packet. Used by 981 vrrpTrapAuthFailure trap." 982 ::= { vrrpTraps 1 } 984 vrrpTrapConfigErrorType OBJECT-TYPE 985 SYNTAX INTEGER { 986 authTypeMismatch (1), 987 authFailure (2) 988 } 989 MAX-ACCESS accessible-for-notify 990 STATUS current 991 DESCRIPTION 992 "Potential types of configuration conflicts. 993 Used by vrrpAuthFailure trap." 994 ::= { vrrpTraps 2 } 996 vrrpTrapNewMaster NOTIFICATION-TYPE 997 OBJECTS { ifIndex, 998 vrrpOperVrId, 999 vrrpOperVirtualMacAddr 1000 } 1001 STATUS current 1002 DESCRIPTION 1003 "The newMaster trap indicates that the sending agent 1004 has transitioned from 'Backup' state to 'Master' state." 1005 ::= { vrrpTraps 3 } 1007 vrrpTrapAuthFailure NOTIFICATION-TYPE 1008 OBJECTS { ifIndex, 1009 vrrpOperVrId, 1010 vrrpTrapPacketSrc, 1011 vrrpTrapConfigErrorType 1012 } 1013 STATUS current 1014 DESCRIPTION 1015 "A vrrpAuthFailure trap signifies that a packet has 1016 been received from a router whose authentication key 1017 or authentication type conflicts with this router's 1018 authentication key or authentication type. Implementation 1019 of this trap is optional." 1020 ::= { vrrpTraps 4 } 1022 -- ******************************************************************* 1023 -- Conformance Information 1024 -- ******************************************************************* 1026 vrrpMIBCompliances OBJECT IDENTIFIER ::= { vrrpConformance 1 } 1027 vrrpMIBGroups OBJECT IDENTIFIER ::= { vrrpConformance 2 } 1029 -- ................................................................... 1030 -- Compliance Statements 1031 -- ................................................................... 1033 vrrpMIBCompliance MODULE-COMPLIANCE 1034 STATUS current 1035 DESCRIPTION 1036 "The core compliance statement for all VRRP implementations." 1037 MODULE -- this module 1038 MANDATORY-GROUPS { 1039 vrrpOperGroup , 1040 vrrpStatsGroup 1041 } 1042 ::= { vrrpMIBCompliances 1 } 1044 -- ................................................................... 1045 -- Conformance Groups 1046 -- ................................................................... 1048 vrrpOperGroup OBJECT-GROUP 1049 OBJECTS { 1050 vrrpNodeVersion, 1051 vrrpTrapCntl, 1052 vrrpOperVrId, 1053 vrrpOperVirtualMacAddr, 1054 vrrpOperState, 1055 vrrpOperControl, 1056 vrrpOperPriority, 1057 vrrpOperIpAddrCount, 1058 vrrpOperMasterIpAddr, 1059 vrrpOperAuthType, 1060 vrrpOperAuthKey, 1061 vrrpOperAdvertisementInterval, 1062 vrrpOperPreemptMode, 1063 vrrpOperVirtualRouterUpTime, 1064 vrrpOperProtocol, 1065 vrrpOperRowStatus, 1066 vrrpTrapPacketSrc, 1067 vrrpTrapConfigErrorType, 1068 vrrpAssoIpAddr, 1069 vrrpAssoIpAddrStatus 1070 } 1071 STATUS current 1072 DESCRIPTION 1073 "Conformance group for VRRP operations." 1074 ::= { vrrpMIBGroups 1 } 1076 vrrpStatsGroup OBJECT-GROUP 1077 OBJECTS { 1078 vrrpStatsBecomeMaster, 1079 vrrpStatsAdvertiseRcvd, 1080 vrrpStatsChecksumErrors, 1081 vrrpStatsVersionErrors, 1082 vrrpStatsVrIdErrors, 1083 vrrpStatsAdvertiseIntervalErrors, 1084 vrrpStatsSecurityViolations, 1085 vrrpStatsIpTtlErrors, 1086 vrrpStatsPriorityZeroPktsRcvd, 1087 vrrpStatsPriorityZeroPktsSent, 1088 vrrpStatsInvalidTypePktsRcvd, 1089 vrrpStatsAddressListErrors, 1090 vrrpStatsUnknownAuthType, 1091 vrrpStatsAuthTypeErrors 1092 } 1093 STATUS current 1094 DESCRIPTION 1095 "Conformance group for VRRP statistics." 1096 ::= { vrrpMIBGroups 2 } 1098 END 1099 4.0 Acknowledgements 1101 The authors would like to thank Venkat Prasad, Barbera Denny, Al Pham, 1102 Robert Hinden, Danny Mitzel and Fred Baker for their comments and 1103 suggestions. 1105 5.0 References 1107 [1] Knight, S., Weaver, D., Whipple, D., Hinden, R., Mitzel, D., 1108 Hunt, P., Higginson, P., Shand, M., Lindem, A., 1109 "Virtual Router Redunancy Protocol", RFC 2338. 1111 [2] Rose, M., and K. McCloghrie, "Structure and Identification of 1112 Management Information for TCP/IP-based Internets", STD 16, RFC 1113 1155, May 1990. 1115 [3] Case, J., Fedor, M., Schoffstall, M., Davin, J., 1116 "Simple Network Management Protocol (SNMP)", STD 15, RFC 1157, 1117 May 1990. 1119 [4] McCloghrie, K., and M. Rose, "Management Information Base for 1120 Network Management of TCP/IP-based internets - MIB-II", STD 17, 1121 RFC 1213, March 1991. 1123 [5] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. 1124 Waldbusser, "Structure of Management Information for version 2 of 1125 the Simple Network Management Protocol (SNMPv2)", RFC 1902, January 1126 1996. 1128 [6] Case, J., McCloghrie, K., Rose, M., Waldbusser, S., 1129 Protocol Operations for Version 2 of the Simple Network Management 1130 Protocol (SNMPv2)", RFC 1905, SNMP Research Inc., Cisco Systems 1131 Inc., Dover Beach Consulting, Inc., International Network Services, 1132 January 1996. 1134 [7] Postel, J., Reynolds, J., 1135 "Instructions to RFC Authors", RFC 2223, 1136 SNMP Research, Inc., Hughes LAN Systems, Dover Beach 1137 Consulting, Inc., Carnegie Mellon University, October 1997. 1139 [8] McCloghrie K., and F. Kastenholz, "Evolution of the Interfaces 1140 Group of MIB-II", RFC 1573, Hughes LAN Syst, FTP Software, 1141 January 1994. 1143 [9] Information processing systems - Open Systems Interconnection, 1144 "Specification of Basic Encoding Rules for Abstract Notation One 1145 (ASN.1)", International Organization for Standardization, 1146 International Standard 8825, December 1987. 1148 6.0 Authors' Addresses 1150 Brian R. Jewell 1151 3Com, Inc. 1152 5400 Bayfront Plaza 1153 Santa Clara, CA 95052 1154 US 1156 Phone: +1 326 764 6173 1157 EMail: bjewell@3com.com 1159 David Chuang 1160 3Com, Inc. 1161 5400 Bayfront Plaza 1162 Santa Clara, CA 95052 1163 US 1165 Phone: +1 408 326 6610 1166 EMail: david_chuang@3com.com 1168 -- ------------------------------------------------------------------- 1169 -- Change Log 1170 -- ------------------------------------------------------------------- 1172 This section tracks changes made during revisions of this document. It 1173 will be deleted when the document is published as an RFC. 1175 * July, 1998: Changes in 2nd revision (draft-ietf-vrrp-mib-02.txt): 1177 - A number of changes were made to the textual content of the 1178 draft as per feedback received at the last WG meeting. These 1179 changes were too numerous to document individually in this 1180 section. 1181 - The size of the "vrrpNodeVersion" object has been changed from 1182 2 octets to 1 octet. 1183 - References to obsoleted RFC's have been replaced by references 1184 to later documents. Notably, references to RFC's 1442, 1443 and 1185 1444 have been replaced by RFC 1902, RFC 1903 and RFC 1904, 1186 respectively. 1187 - The description for the "vrrpOperControl" was changed to 1188 reflect the fact that a virtual router does not necessarily 1189 transition directly from initialize state -> backup state. 1190 The description for the "vrrpStatsBecomeMaster" was also 1191 changed to more accurately convey this fact. 1192 - The SYNTAX of the "vrrpOperIpAddrCount" was changed to 1193 reflect the fact that a virtual router can support only up 1194 to 255 backup IP addresses. 1195 - Descriptions for vrrpOperAuthType and vrrpOperAuthKey expanded 1196 to indicate the per-interface assignment. 1197 - SYNTAX of vrrpOperPreemptMode object changed from INTEGER 1198 to 'truthValue' 1199 - The OIDs for the VRRP traps were fixed; incorrect ident- 1200 ifiers ('vrrpOperations') had been used in OID assignments. 1201 - The SYNTAX for the 'vrrpOperPriority' object was corrected 1202 to indicate that this can have a value of '0'. 1203 - The vrrpOperHMACMD5Key object was deleted. It was combined 1204 with the vrrpOperAuthKey object, whose SYNTAX was adjusted 1205 accordingly. 1206 - OID for 'vrrpTraps' changed to '{ vrrpNotifications 1 }' 1207 - The 'vrrpStatsPasswdSecurityViolations' and 'vrrpStatsHmac- 1208 SecurityViolations' objects have been combined into a 1209 single 'vrrpStatsSecurityViolations' object; this was 1210 suggested to avoid redundancy. 1211 - As per the last WG meeting, the 'vrrpAssoIpAddrIndex' object 1212 has been deleted from the 'vrrpAssoIpAddrTable'and replaced 1213 by 'vrrpAssoIpAddr'. 1214 - Removed references to 'vrrpAssoIpAddrIndex' in samples. 1215 - Added new object 'vrrpOperProtocol' to 'VrrpOperEntry'. 1216 - MAX-ACCESS for the 'vrrpOperVrId' object changed to 1217 'not-accessible', as per RFC1902 (auxilary objects). 1218 - SYNTAX for 'vrrpOperVirtualRouterUpTime' changed to 1219 'TimeStamp'. 1220 - Added importation of 'TruthValue'and 'TimeStamp' to accomodate 1221 changes listed above. Deleted importation of 'TimeTicks'. 1222 - Changed MAX-ACCESS to 'accessible-for-notify' for 1223 'vrrpTrapPacketSrc' and 'vrrpTrapConfigErrorType' objects. 1224 - In the sample tables, the "if" values were incorrect for 1225 the sample tables for "IP B" (they used to read "I1"). 1226 - MAX-ACCESS for 'vrrpOperAuthType' and 'vrrpOperAuthKey' 1227 changed to 'read-only', since these objects are defined on 1228 a per-interface basis. 1229 - Overall review and editing of Section 5.0 (References) with 1230 deletion of references not used in this document. Also, added 1231 reference '9'. 1233 Concerns: 1234 --------- 1235 - Keep the 'vrrpTrapAuthFailure' trap? 1236 - Remove 'vrrpTrapPacketSrc' and 'vrrpTrapConfigErrorType' from 1237 compliances? Only used for 'vrrpTrapAuthFailure' trap. 1239 * 3/4/1998: Changes in 1st revision (draft-ietf-vrrp-mib-01.txt): 1241 - Overall review and editing of document text and object 1242 descriptions from feedback received at December 1997 IETF meeting. 1243 More specifically the changes made along these lines include 1244 the following: 1246 -- Cleaned up Section 5.0 ("References") and validated. 1247 -- Modifed diagram for VRRP Scenario #2 (Section 2.4.2). 1248 -- VRRP Overview (Section 2.0) rewritten to be more in-line with 1249 latest revision (05) of VRRP RFC Draft. 1250 -- Description of "VrId" Textual convention rewritten. 1252 - MAX-ACCESS of vrrpTrapCntl object changed to "read-write". 1253 - Changed SYNTAX of "vrrpOperVirtualMacAddr" object from 1254 "PhyAddress" to "MacAddress". 1255 - Changed the syntax of the "vrrpOperPriority" object so upper 1256 value can be 255. 1257 - Change MAX-ACCESS for "vrrpOperAuthType" object from 1258 read-only to read-create. 1259 - Added three new objects to "vrrpRouterStatsTable": 1260 "vrrpStatsAddressListErrors", "vrrpStatsUnknownAuthType" 1261 and "vrrpStatsAuthTypeErrors". 1262 - Removed "vrrpStatsUnknownPacketType" object, as it was 1263 redundant (with "vrrpStatsInvalidPacketType"). 1264 - Removed the "vrrpOperIfIndex" object to use "ifIndex" (which is 1265 actually equivalent) instead. 1267 * 11/19/97 (vft-ietf-vrrp-mib-00.txt) - Initial Draft