idnits 2.17.1 draft-ietf-vrrp-mib-08.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** Missing expiration date. The document expiration date should appear on the first and last page. ** 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? == No 'Intended status' indicated for this document; assuming Proposed Standard == It seems as if not all pages are separated by form feeds - found 0 form feeds but 39 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 48 instances of too long lines in the document, the longest one being 5 characters in excess of 72. ** The abstract seems to contain references ([2], [17], [19]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 642 has weird spacing: '...nsition to be...' == Line 815 has weird spacing: '...virtual route...' -- 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) -- Looks like a reference, but probably isn't: 'RFC2574' on line 1254 -- Looks like a reference, but probably isn't: 'RFC2575' on line 1255 == Unused Reference: '22' is defined on line 1373, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2571 (ref. '1') (Obsoleted by RFC 3411) ** Downref: Normative reference to an Informational RFC: RFC 1215 (ref. '4') ** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. '8') ** Downref: Normative reference to an Historic RFC: RFC 1901 (ref. '9') ** Obsolete normative reference: RFC 1906 (ref. '10') (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2572 (ref. '11') (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2574 (ref. '12') (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 1905 (ref. '13') (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2573 (ref. '14') (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2575 (ref. '15') (Obsoleted by RFC 3415) ** Obsolete normative reference: RFC 2570 (ref. '16') (Obsoleted by RFC 3410) ** Obsolete normative reference: RFC 2338 (ref. '17') (Obsoleted by RFC 3768) ** Obsolete normative reference: RFC 1902 (ref. '19') (Obsoleted by RFC 2578) ** Obsolete normative reference: RFC 1903 (ref. '20') (Obsoleted by RFC 2579) ** Obsolete normative reference: RFC 1904 (ref. '21') (Obsoleted by RFC 2580) ** Obsolete normative reference: RFC 2223 (ref. '22') (Obsoleted by RFC 7322) ** Obsolete normative reference: RFC 2233 (ref. '23') (Obsoleted by RFC 2863) Summary: 24 errors (**), 0 flaws (~~), 5 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 INTERNET-DRAFT B. Jewell 2 June 24, 1999 D. Chuang 3 3Com, Inc. 5 Definitions of Managed Objects for the 6 Virtual Router Redundancy Protocol 8 10 Status of this Memo 12 This document is an Internet-Draft and is in full conformance with 13 all provisions of Section 10 of RFC2026. 15 Internet-Drafts are working documents of the Internet Engineering 16 Task Force (IETF), its areas, and its working groups. Note that 17 other groups may also distribute working documents as Internet- 18 Drafts. 20 Internet-Drafts are draft documents valid for a maximum of six months 21 and may be updated, replaced, or obsoleted by other documents at any 22 time. It is inappropriate to use Internet- Drafts as reference 23 material or to cite them other than as "work in progress." 25 The list of current Internet-Drafts can be accessed at 26 http://www.ietf.org/ietf/1id-abstracts.txt 28 The list of Internet-Draft Shadow Directories can be accessed at 29 http://www.ietf.org/shadow.html. 31 This internet draft expires on December 4, 1999. 33 Abstract 35 This specification defines an extension to the Management Information 36 Base (MIB) for use with SNMP-based network management. In 37 particular, it defines objects for configuring, monitoring, and 38 controlling routers that employ the Virtual Router Redundancy 39 Protocol (VRRP) [17]. 41 This memo specifies a MIB module in a manner that is compliant with 42 both the SNMPv2 SMI [19], and semantically identical to the SNMPv1 43 definitions [2]. 45 Table of Contents 47 1 The SNMPv2 Network Management Framework ............... 3 49 2 Overview .............................................. 4 51 2.1 VRRP MIB Structure .................................. 4 53 2.2 Virtual Router Redundancy Protocol .................. 4 55 2.3 VRRP MIB Table Design ............................... 5 57 2.3.1 Relation to Interface Group ....................... 5 59 2.4 VRRP Scenarios ...................................... 5 61 2.4.1 Scenario #1 ....................................... 6 63 2.4.2 Scenario #2 ....................................... 8 65 3 Definitions ........................................... 11 67 4 Security Considerations ............................... 31 69 5 Acknowledgements ...................................... 32 71 6 References ............................................ 32 73 7 Authors' Addresses .................................... 34 75 1. The SNMP Management Framework 77 The SNMP Management Framework presently consists of five major 78 components: 80 o An overall architecture, described in RFC 2571 [1]. 82 o Mechanisms for describing and naming objects and events for the 83 purpose of management. The first version of this Structure of 84 Management Information (SMI) is called SMIv1 and described in RFC 85 1155 [2], RFC 1212 [3] and RFC 1215 [4]. The second version, 86 called SMIv2, is described in RFC 2578 [5], RFC 2579 [6] and RFC 87 2580 [7]. 89 o Message protocols for transferring management information. The 90 first version of the SNMP message protocol is called SNMPv1 and 91 described in RFC 1157 [8]. A second version of the SNMP message 92 protocol, which is not an Internet standards track protocol, is 93 called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10]. 94 The third version of the message protocol is called SNMPv3 and 95 described in RFC 1906 [10], RFC 2572 [11] and RFC 2574 [12]. 97 o Protocol operations for accessing management information. The 98 first set of protocol operations and associated PDU formats is 99 described in RFC 1157 [8]. A second set of protocol operations and 100 associated PDU formats is described in RFC 1905 [13]. 102 o A set of fundamental applications described in RFC 2573 [14] and 103 the view-based access control mechanism described in RFC 2575 104 [15]. 106 A more detailed introduction to the current SNMP Management Framework 107 can be found in RFC 2570 [16]. 109 Managed objects are accessed via a virtual information store, termed 110 the Management Information Base or MIB. Objects in the MIB are 111 defined using the mechanisms defined in the SMI. 113 This memo specifies a MIB module that is compliant to the SMIv2. A 114 MIB conforming to the SMIv1 can be produced through the appropriate 115 translations. The resulting translated MIB must be semantically 116 equivalent, except where objects or events are omitted because no 117 translation is possible (use of Counter64). Some machine readable 118 information in SMIv2 will be converted into textual descriptions in 119 SMIv1 during the translation process. However, this loss of machine 120 readable information is not considered to change the semantics of the 121 MIB. 123 2. Overview 125 This memo identifies the set of objects for configuring, monitoring, 126 and controlling the Virtual Router Redundancy Protocol (VRRP), as 127 defined in RFC 2338 [17]. 129 VRRP specifies an election protocol that will allow one or more 130 associated IP addresses to be assumed by another router in the event 131 of a failure of the IP address(es) owner. Thus, IP traffic from a 132 host using a failed router as a default gateway is transparently 133 fowarded by the VRRP router that has assumed control. VRRP provides 134 redundancy in routed networks without requiring configuration of 135 dynamic routing or router discovery protocols on every end-host. 137 2.1. VRRP MIB Structure 139 The VRRP MIB contains three conformance groups: 141 - vrrpOperations Group: Objects related to VRRP router's 142 configuration and control. 144 - vrrpStatistics Group: Objects containing information useful in 145 monitoring the operation of VRRP routers. 147 - vrrpNotifications Group: Consists of objects and definitions for 148 use in SNMP traps sent by VRRP routers. 150 Tables in the MIB include the following: 152 (1) The vrrpOperTable, which contains objects that define the 153 operational characteristics of a VRRP router. Rows in this table 154 correspond to instances of virtual routers. 156 (2) The vrrpAssoIpAddrTable, which contains the addresses of the 157 virtual router(s) that a given VRRP router is backing up. 159 (3) The vrrpRouterStatsTable which contains the operating statistics 160 for a VRRP router. 162 2.2. Virtual Router Redundancy Protocol 164 This MIB is based on the following characteristics of VRRP as defined 165 in the VRRP specification [17]. 167 - A "VRRP router" is one that is configured to run the VRRP protocol 168 in conjunction with one or more other VRRP routers attached to a 169 LAN. 171 - A VRRP router can be running one or more instances of a virtual 172 router. 174 - A "virtual router" is an abstraction which consists of two or more 175 physical routers associated by a Virtual Router Identifier (VRID). 177 - An instance of a virtual router (on a physical VRRP router), can 178 be uniquely identified by a combination of the 'IF Index' [18] and 179 "Virtual Router Identifier" (VRID). 181 - For each VRID there is a set of one or more "associated IP 182 addresses" that are backed-up by the virtual router. 184 2.3. VRRP MIB Table Design 186 The tables in the VRRP MIB are structured with the assumption that a 187 VRRP network management application would likely be designed to 188 display information or provide configuration about a VRRP router on a 189 "per-virtual-router basis". Thus, the tables defined in the MIB 190 consist of conceptual rows which are grouped in a manner to present a 191 view of individual virtual routers with a minimal number of SNMP 192 operations. 194 2.3.1. Relation to Interface Group (RFC 2233) [23]. 196 Since a router can be participating in VRRP on one or more physical 197 interfaces, "ifIndex" is used as an index into the tables defined in 198 the VRRP MIB. 200 2.4. VRRP Scenarios 202 The following section provides examples of how some of the objects in 203 this MIB are instantiated for two different VRRP scenarios. 205 KEY: 206 ---- 208 The labels in the following tables and diagrams correspond to the 209 actual MIB objects as follows: 211 if = vrrpOperIfIndex 212 VrId = vrrpOperVrId 213 State = vrrpOperState 214 Prior = vrrpOperPriority 215 AddrCnt = vrrpOperIpAddrCount 216 IpAddr = vrrpOperMasterIpAddr 217 RowStat = vrrpOperRowStatus 219 2.4.1. VRRP Scenario #1 221 The following figure shows a simple network with two VRRP routers 222 configured with two virtual routers. This sample topology is taken 223 from the VRRP specification [17]. Addresses in '()' indicate the IP 224 address of the default gateway for a given host, H1 - H4. In the 225 diagram, "Interface" is used in the context defined in MIB-II [4]. 227 VRID=1 VRID=2 228 +-----+ +-----+ 229 | MR1 | | MR2 | 230 | & | | & | 231 | BR2 | | BR1 | 232 +-----+ +-----+ 233 IP A ---------->* *<---------- IP B 234 Interface=I1 | | Interface=I2 235 | | 236 | | 237 ------------------+------------+-----+--------+--------+--------+-- 238 ^ ^ ^ ^ 239 | | | | 240 (IP A) (IP A) (IP A) (IP A) 241 | | | | 242 +--+--+ +--+--+ +--+--+ +--+--+ 243 | H1 | | H2 | | H3 | | H4 | 244 +-----+ +-----+ +--+--+ +--+--+ 246 ----- MIB Tables For VRRP Router "IP A": ----- 248 vrrpOperTable 249 ------------- 251 | if | VrId | State | Prior | AddrCnt | IpAddr | ... | RowStat | 252 +----+------+-------+-------+---------+--------+-( )-+---------+ 253 | | | | | | | | | 254 | I1 | 01 | M | 255 | 1 | A | | active | 255 | | | | | | | | | 256 +----+------+-------+-------+---------+--------+-( )-+---------+ 257 | | | | | | | | | 258 | I1 | 02 | B | 1-254 | 1 | B | | active | 259 | | | | | | | | | 260 +----+------+-------+-------+---------+--------+-( )-+---------+ 262 vrrpAssoIpAddrTable 263 ------------------- 265 | if | VrId | IP | RowStat | 266 +----+------+-------+---------+ 267 | | | | | 268 | I1 | 01 | A | active | 269 | | | | | 270 +----+------+-------+---------+ 271 | | | | | 272 | I1 | 02 | B | active | 273 | | | | | 274 +----+------+-------+---------+ 276 ----- MIB Tables For VRRP Router "IP B": ----- 278 vrrpOperTable 279 ------------- 281 | if | VrId | State | Prior | AddrCnt | IpAddr | ... | RowStat | 282 +----+------+-------+-------+---------+--------+-( )-+---------+ 283 | | | | | | | | | 284 | I2 | 01 | B | 1-254 | 1 | A | | active | 285 | | | | | | | | | 286 +----+------+-------+-------+---------+--------+-( )-+---------+ 287 | | | | | | | | | 288 | I2 | 02 | M | 255 | 1 | B | | active | 289 | | | | | | | | | 290 +----+------+-------+-------+---------+--------+-( )-+---------+ 292 vrrpAssoIpAddrTable 293 ------------------- 295 | if | VrId | IP | RowStat | 296 +----+------+-------+---------+ 297 | | | | | 298 | I2 | 01 | A | active | 299 | | | | | 300 +----+------+-------+---------+ 301 | | | | | 302 | I2 | 02 | B | active | 303 | | | | | 304 +----+------+-------+---------+ 306 NOTES: 308 1) "I1" and "I2" are used to designate IF indices on each 309 respective router. 311 2) For "State": M = Master; B = Backup. 313 3) In the vrrpOperTable, a "priority" of 255 indicates that the 314 respective router owns the IP address, e.g., this IP address is 315 native to the router (i.e., "the IP Address Owner" [17]). 317 2.4.2. VRRP Scenario #2 319 The following figure shows a simple network with two virtual routers. 320 Here, a single interface has been configured with two IP addresses. 321 Again, addresses in () indicate the IP address of the default gateway 322 for a given host, H1 - H2. 324 VRID=1 VRID=2 325 +-----+ +-----+ 326 | MR1 | | MR2 | 327 | & | | & | 328 | BR2 | | BR1 | 329 +-----+ +-----+ 330 IP A ---------->* *<---------- IP B 331 IP C | | Interface=I2 332 Interface=I1 | | 333 | | 334 | | 335 ------------------+------------+-----+--------+ 336 ^ ^ 337 | | 338 (IP A) (IP B) 339 | | 340 +--+--+ +--+--+ 341 | H1 | | H2 | 342 +-----+ +-----+ 344 ----- MIB Tables For VRRP Router "IP A": ----- 346 vrrpOperTable 347 ------------- 349 | if | VrId | State | Prior | AddrCnt | IpAddr | ... | RowStat | 350 +----+------+-------+-------+---------+--------+-( )-+---------+ 351 | | | | | | | | | 352 | I1 | 01 | M | 255 | 2 | A | | active | 353 | | | | | | | | | 354 +----+------+-------+-------+---------+--------+-( )-+---------+ 355 | | | | | | | | | 356 | I1 | 02 | B | 1-254 | 1 | B | | active | 357 | | | | | | | | | 358 +----+------+-------+-------+---------+--------+-( )-+---------+ 360 vrrpAssoIpAddrTable 361 ------------------- 363 | if | VrId | IP | RowStat | 364 +----+------+-------+---------+ 365 | | | | | 366 | I1 | 01 | A | active | 367 | | | | | 368 +----+------+-------+---------+ 369 | | | | | 370 | I1 | 01 | C | active | 371 | | | | | 372 +----+------+-------+---------+ 373 | | | | | 374 | I1 | 02 | B | active | 375 | | | | | 376 +----+------+-------+---------+ 377 ----- MIB Tables For VRRP Router "IP B": ----- 379 vrrpOperTable 380 ------------- 382 | if | VrId | State | Prior | AddrCnt | IpAddr | ... | RowStat | 383 +----+------+-------+-------+---------+--------+-( )-+---------+ 384 | | | | | | | | | 385 | I2 | 01 | B | 1-254 | 2 | A | | active | 386 | | | | | | | | | 387 +----+------+-------+-------+---------+--------+-( )-+---------+ 388 | | | | | | | | | 389 | I2 | 02 | M | 255 | 1 | B | | active | 390 | | | | | | | | | 391 +----+------+-------+-------+---------+--------+-( )-+---------+ 393 vrrpAssoIpAddrTable 394 ------------------- 396 | if | VrId | IP | RowStat | 397 +----+------+-------+---------+ 398 | | | | | 399 | I2 | 01 | A | active | 400 | | | | | 401 +----+------+-------+---------+ 402 | | | | | 403 | I2 | 01 | C | active | 404 | | | | | 405 +----+------+-------+---------+ 406 | | | | | 407 | I2 | 02 | B | active | 408 | | | | | 409 +----+------+-------+---------+ 411 3. Definitions 413 VRRP-MIB DEFINITIONS ::= BEGIN 415 IMPORTS 416 MODULE-IDENTITY, OBJECT-TYPE, 417 NOTIFICATION-TYPE, Counter32, 418 Integer32, IpAddress, mib-2 FROM SNMPv2-SMI -- RFC 1902[19] 419 TEXTUAL-CONVENTION, RowStatus, 420 MacAddress, TruthValue, TimeStamp FROM SNMPv2-TC -- RFC 1903[20] 421 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF -- RFC 1904[21] 422 ifIndex FROM IF-MIB; -- RFC 2233 424 vrrp MODULE-IDENTITY 425 LAST-UPDATED "9906240900Z" 426 ORGANIZATION "IETF VRRP Working Group" 427 CONTACT-INFO 428 "Brian R. Jewell 429 Postal: 3Com Corporation 430 5400 BayFront Plaza 431 Santa Clara, California 95052 432 Tel: +1 408 326 6173 433 E-Mail: bjewell@3com.com" 435 DESCRIPTION 436 "The MIB module to describe the VRRP Version 2 Protocol." 437 ::= { mib-2 68 } 439 vrrpMIB OBJECT IDENTIFIER ::= { vrrp 1 } 441 -- ******************************************************************* 442 -- Textual Conventions 443 -- ******************************************************************* 445 VrId ::= TEXTUAL-CONVENTION 446 STATUS current 447 DESCRIPTION 448 "A number which, along with an interface index (ifIndex), 449 serves to uniquely identify a virtual router on a given VRRP 450 router. A set of one or more associated addresses is assigned 451 to a VRID." 452 SYNTAX Integer32 (1..255) 454 -- ******************************************************************* 455 -- VRRP MIB Groups 456 -- ******************************************************************* 458 vrrpOperations OBJECT IDENTIFIER ::= { vrrpMIB 1 } 459 vrrpStatistics OBJECT IDENTIFIER ::= { vrrpMIB 2 } 460 vrrpNotifications OBJECT IDENTIFIER ::= { vrrpMIB 3 } 461 vrrpConformance OBJECT IDENTIFIER ::= { vrrpMIB 4 } 463 -- ******************************************************************* 464 -- Start of MIB objects 465 -- ******************************************************************* 467 vrrpNodeVersion OBJECT-TYPE 468 SYNTAX Integer32 469 MAX-ACCESS read-only 470 STATUS current 471 DESCRIPTION 472 "This value identifies the particular version of the VRRP 473 supported by this node." 474 REFERENCE 475 "Virtual Router Redundancy Protocol, RFC 2338" 476 DEFVAL { 2 } 477 ::= { vrrpOperations 1 } 479 vrrpTrapCntl OBJECT-TYPE 480 SYNTAX INTEGER { 481 enabled (1), 482 disabled (2) 483 } 484 MAX-ACCESS read-write 485 STATUS current 486 DESCRIPTION 487 "Indicates whether the VRRP-enabled router will generate 488 SNMP traps for events defined in this MIB. 'Enabled' 489 results in SNMP traps; 'disabled', no traps are sent." 490 DEFVAL { enabled } 491 ::= { vrrpOperations 2 } 493 -- ******************************************************************* 494 -- VRRP Operations Table 495 -- ******************************************************************* 497 vrrpOperTable OBJECT-TYPE 498 SYNTAX SEQUENCE OF VrrpOperEntry 499 MAX-ACCESS not-accessible 500 STATUS current 501 DESCRIPTION 502 "Operations table for a VRRP router which consists of a 503 sequence (i.e., one or more conceptual rows) of 504 'vrrpOperEntry' items." 505 ::= { vrrpOperations 3 } 507 vrrpOperEntry OBJECT-TYPE 508 SYNTAX VrrpOperEntry 509 MAX-ACCESS not-accessible 510 STATUS current 511 DESCRIPTION 512 "An entry in the vrrpOperTable containing the operational 513 characteristics of a virtual router. On a VRRP router, 514 a given virtual router is identified by a combination 515 of the IF index and VRID. 517 Rows in the table cannot be modified unless the value 518 of `vrrpOperAdminState' is `disabled' and the 519 `vrrpOperState' has transitioned to `initialize'." 521 INDEX { ifIndex, vrrpOperVrId } 522 ::= { vrrpOperTable 1 } 524 VrrpOperEntry ::= 525 SEQUENCE { 526 vrrpOperVrId 527 VrId, 528 vrrpOperVirtualMacAddr 529 MacAddress, 530 vrrpOperState 531 INTEGER, 532 vrrpOperAdminState 533 INTEGER, 534 vrrpOperPriority 535 Integer32, 536 vrrpOperIpAddrCount 537 Integer32, 538 vrrpOperMasterIpAddr 539 IpAddress, 540 vrrpOperPrimaryIpAddr 541 IpAddress, 542 vrrpOperAuthType 543 INTEGER, 544 vrrpOperAuthKey 545 OCTET STRING, 546 vrrpOperAdvertisementInterval 547 Integer32, 548 vrrpOperPreemptMode 549 TruthValue, 550 vrrpOperVirtualRouterUpTime 551 TimeStamp, 552 vrrpOperProtocol 553 INTEGER, 554 vrrpOperRowStatus 555 RowStatus 556 } 558 vrrpOperVrId OBJECT-TYPE 559 SYNTAX VrId 560 MAX-ACCESS not-accessible 561 STATUS current 562 DESCRIPTION 563 "This object contains the Virtual Router Identifier (VRID)." 564 ::= { vrrpOperEntry 1 } 566 vrrpOperVirtualMacAddr OBJECT-TYPE 567 SYNTAX MacAddress 568 MAX-ACCESS read-only 569 STATUS current 570 DESCRIPTION 571 "The virtual MAC address of the virtual router. Although this 572 object can be derived from the 'vrrpOperVrId' object, it is 573 defined so that it is easily obtainable by a management 574 application and can be included in VRRP-related SNMP traps." 575 ::= { vrrpOperEntry 2 } 577 vrrpOperState OBJECT-TYPE 578 SYNTAX INTEGER { 579 initialize(1), 580 backup(2), 581 master(3) 582 } 583 MAX-ACCESS read-only 584 STATUS current 586 DESCRIPTION 587 "The current state of the virtual router. This object has 588 three defined values: 590 - `initialize', which indicates that all the 591 virtual router is waiting for a startup event. 593 - `backup', which indicates the virtual router is 594 monitoring the availability of the master router. 596 - `master', which indicates that the virtual router 597 is forwarding packets for IP addresses that are 598 associated with this router. 600 Setting the `vrrpOperAdminState' object (below) initiates 601 transitions in the value of this object." 603 ::= { vrrpOperEntry 3 } 605 vrrpOperAdminState OBJECT-TYPE 606 SYNTAX INTEGER { 607 up(1), 608 down(2) 609 } 610 MAX-ACCESS read-create 611 STATUS current 612 DESCRIPTION 613 "This object will enable/disable the virtual router 614 function. Setting the value to 'up', will transition 615 the state of the virtual router from `initialize' to `backup' 616 or `master'; setting the value to `down', will transition 617 the router from `master' or `backup' to `initialize'. State 618 transitions may not be immediate; they sometimes depend on 619 other factors, such as the interface (IF) state. 621 The `vrrpOperAdminState' object must be set to `down' prior 622 to modifying the other read-create objects in the conceptual 623 row. The value of the `vrrpOperRowStatus' object (below) 624 must be `active', signifying that the conceptual row 625 is valid (i.e., the objects are correctly set), 626 in order for this object to be set to `up'." 627 DEFVAL { down } 628 ::= { vrrpOperEntry 4 } 630 vrrpOperPriority OBJECT-TYPE 631 SYNTAX Integer32 (0..255) 632 MAX-ACCESS read-create 633 STATUS current 634 DESCRIPTION 635 "This object specifies the priority to be used for the 636 virtual router master election process. Higher values imply 637 higher priority. 639 A priority of '0', although not settable, is sent by 640 the master router to indicate that this router has ceased 641 to particpate in VRRP and a backup virtual router should 642 transition to become a new master. 644 A priority of 255 is used for the router that owns the 645 associated IP address(es)." 646 DEFVAL { 100 } 647 ::= { vrrpOperEntry 5 } 649 vrrpOperIpAddrCount OBJECT-TYPE 650 SYNTAX Integer32 (0..255) 651 MAX-ACCESS read-only 652 STATUS current 653 DESCRIPTION 654 "The number of IP addresses that are associated with this 655 virtual router. This number is equal to the number of rows 656 in the vrrpAssoIpAddrTable that correspond to a given IF 657 index/VRID pair." 658 ::= { vrrpOperEntry 6 } 660 vrrpOperMasterIpAddr OBJECT-TYPE 661 SYNTAX IpAddress 662 MAX-ACCESS read-only 663 STATUS current 664 DESCRIPTION 665 "The master router's real (primary) IP address. This is 666 the IP address listed as the source in VRRP advertisement 667 last received by this virtual router." 668 ::= { vrrpOperEntry 7 } 670 vrrpOperPrimaryIpAddr OBJECT-TYPE 671 SYNTAX IpAddress 672 MAX-ACCESS read-create 673 STATUS current 674 DESCRIPTION 675 "In the case where there is more than one IP address for 676 a given `ifIndex', this object is used to specify the IP 677 address that will become the `vrrpOperMasterIpAddr', should 678 the virtual router transition from backup to master. If 679 this object is set to 0.0.0.0, the IP address which is 680 numerically lowest will be selected." 681 DEFVAL { '00000000'H } -- 0.0.0.0 682 ::= { vrrpOperEntry 8 } 684 vrrpOperAuthType OBJECT-TYPE 685 SYNTAX INTEGER { 686 noAuthentication(1), -- VRRP protocol exchanges are not 687 -- authenticated. 688 simpleTextPassword(2), -- Exchanges are authenticated by a 689 -- clear text password. 690 ipAuthenticationHeader(3) -- Exchanges are authenticated using 691 -- the IP authentication header. 692 } 693 MAX-ACCESS read-create 694 STATUS current 695 DESCRIPTION 696 "Authentication type used for VRRP protocol exchanges between 697 virtual routers. This value of this object is the same for a 698 given ifIndex." 699 DEFVAL { noAuthentication } 700 ::= { vrrpOperEntry 9 } 702 vrrpOperAuthKey OBJECT-TYPE 703 SYNTAX OCTET STRING (SIZE (0..16)) 704 MAX-ACCESS read-create 705 STATUS current 706 DESCRIPTION 707 "The Authentication Key. This object is set according to 708 the value of the 'vrrpOperAuthType' object 709 ('simpleTextPassword' or 'ipAuthenticationHeader'). If the 710 length of the value is less than 16 octets, the agent will 711 left adjust and zero fill to 16 octets. The value of this 712 object is the same for a given ifIndex. 714 When read, vrrpOperAuthKey always returns an Octet String 715 of length zero." 716 ::= { vrrpOperEntry 10 } 718 vrrpOperAdvertisementInterval OBJECT-TYPE 719 SYNTAX Integer32 (1..255) 720 MAX-ACCESS read-create 721 STATUS current 722 DESCRIPTION 723 "The time interval, in seconds, between sending 724 advertisement messages. Only the master router sends 725 VRRP advertisements." 726 DEFVAL { 1 } 727 ::= { vrrpOperEntry 11 } 729 vrrpOperPreemptMode OBJECT-TYPE 730 SYNTAX TruthValue 731 MAX-ACCESS read-create 732 STATUS current 733 DESCRIPTION 734 "Controls whether a higher priority virtual router will 735 preempt a lower priority master." 736 DEFVAL { true } 737 ::= { vrrpOperEntry 12 } 739 vrrpOperVirtualRouterUpTime OBJECT-TYPE 740 SYNTAX TimeStamp 741 MAX-ACCESS read-only 742 STATUS current 743 DESCRIPTION 744 "This is the value of the `sysUpTime' object when this 745 virtual router (i.e., the `vrrpOperState') transitioned 746 out of `initialized'." 747 ::= { vrrpOperEntry 13 } 749 vrrpOperProtocol OBJECT-TYPE 750 SYNTAX INTEGER { 751 ip (1), 752 bridge (2), 753 decnet (3), 754 other (4) 755 } 756 MAX-ACCESS read-create 757 STATUS current 758 DESCRIPTION 759 "The particular protocol being controlled by this Virtual 760 Router." 761 DEFVAL { ip } 762 ::= { vrrpOperEntry 14 } 764 vrrpOperRowStatus OBJECT-TYPE 765 SYNTAX RowStatus 766 MAX-ACCESS read-create 767 STATUS current 768 DESCRIPTION 769 "The row status variable, used in accordance to installation 770 and removal conventions for conceptual rows. In the text 771 that follows, the characteristics (i.e., whether readable, 772 settable or both) of each value are indicated in parenthesis. 774 The state that this object transitions to when it is set 775 is based on a determination of whether the read-create 776 objects in the row have been correctly initialized for 777 virtual router operation. A row in which not all of the 778 objects are correctly set is considered `incomplete'. 780 The rowstatus of a currently active row in the vrrpOperTable 781 is also constrained by the operational state of the 782 corresponding virtual router. Prior to setting this object 783 from `active' to a different value, the `vrrpOperAdminState' 784 object must be set to `down', and the `vrrpOperState' object 785 be transitioned to `initialize'. 787 The rowstatus column has six defined values: 789 - `active' (read/set). When this value is read, it 790 indicates that all the read-create objects (in the row) 791 required for virtual router operation have been 792 correctly initialized such that the respective virtual 793 router can be made operational by setting the 794 `vrrpOperAdminState' to `up'. When set to `active', 795 no other objects in the conceptual row, with the 796 exception of `vrrpOperAdminState', can be modified. 798 When set, the agent will transition the value of 799 rowstatus to `notReady' if the row is incomplete. 801 - `notInService' (read/set), which when set, allows the 802 objects in the row to be modified by a management station, 803 thus changing the operational characteristics of the 804 corresponding virtual router. 806 - `notReady' (read). The agent sets the object to this 807 state to indicate that the conceptual row exists, 808 but is lacking initialization of one or more objects 809 required for virtual router operation. 811 - `createAndGo' (set), which is set by a management 812 station wishing to create a new instance of a 813 virtual router and to have its status automatically 814 set to `active', making it available for use by a 815 virtual router. Upon receiving a request to set the 816 rowstatus to this value, the agent transitions the 817 rowstatus to `active' if the other settable objects 818 in the row have been correctly initialized. If the 819 row is incomplete, the agent transitions the state to 820 `notReady'. 822 - `createAndWait' (set), which is set by a management 823 station wishing to create a new instance of a 824 virtual router but not make it available for use. 825 When this value is set, rowstatus transitions to 826 `notInService' if the row has been correctly 827 initialized; if the row is incomplete, rowstatus will 828 become `notReady'. 830 - `destroy' (set), which deletes the conceptual row, 831 and hence, the corresponding instance of a virtual 832 router." 834 ::= { vrrpOperEntry 15 } 836 -- ******************************************************************* 837 -- VRRP Associated IP Address Table 838 -- ******************************************************************* 840 vrrpAssoIpAddrTable OBJECT-TYPE 841 SYNTAX SEQUENCE OF VrrpAssoIpAddrEntry 842 MAX-ACCESS not-accessible 843 STATUS current 844 DESCRIPTION 845 "The table of addresses associated with this virtual router." 846 ::= { vrrpOperations 4 } 848 vrrpAssoIpAddrEntry OBJECT-TYPE 849 SYNTAX VrrpAssoIpAddrEntry 850 MAX-ACCESS not-accessible 851 STATUS current 852 DESCRIPTION 853 "An entry in the table contains an IP address that is 854 associated with a virtual router. The number of rows for 855 a given ifIndex and VrId will equal the number of IP 856 addresses associated (e.g., backed up) by the virtual 857 router (equivalent to 'vrrpOperIpAddrCount'). 859 Rows in the table cannot be modified unless the value 860 of `vrrpOperAdminState' is `disabled' and the 861 `vrrpOperState' has transitioned to `initialize'." 863 INDEX { ifIndex, vrrpOperVrId, vrrpAssoIpAddr } 864 ::= { vrrpAssoIpAddrTable 1 } 866 VrrpAssoIpAddrEntry ::= 867 SEQUENCE { 868 vrrpAssoIpAddr 869 IpAddress, 870 vrrpAssoIpAddrRowStatus 871 RowStatus 872 } 874 vrrpAssoIpAddr OBJECT-TYPE 875 SYNTAX IpAddress 876 MAX-ACCESS not-accessible 877 STATUS current 878 DESCRIPTION 879 "The assigned IP addresses that a virtual router is 880 responsible for backing up." 881 ::= { vrrpAssoIpAddrEntry 1 } 883 vrrpAssoIpAddrRowStatus OBJECT-TYPE 884 SYNTAX RowStatus 885 MAX-ACCESS read-create 886 STATUS current 887 DESCRIPTION 888 "The row status variable, used according to installation 889 and removal conventions for conceptual rows. Setting this 890 object to `active' or 'createAndGo' results in the addition 891 of an associated address for a virtual router. Destroying 892 the entry or setting it to 'notInService' removes the 893 associated address from the virtual router. The use of 894 other values is implementation-dependent." 895 ::= { vrrpAssoIpAddrEntry 2 } 897 -- ******************************************************************* 898 -- VRRP Router Statistics 899 -- ******************************************************************* 901 vrrpRouterChecksumErrors OBJECT-TYPE 902 SYNTAX Counter32 903 MAX-ACCESS read-only 904 STATUS current 905 DESCRIPTION 906 "The total number of VRRP packets received with an invalid 907 VRRP checksum value." 908 ::= { vrrpStatistics 1 } 910 vrrpRouterVersionErrors OBJECT-TYPE 911 SYNTAX Counter32 912 MAX-ACCESS read-only 913 STATUS current 914 DESCRIPTION 915 "The total number of VRRP packets received with an unknown 916 or unsupported version number." 917 ::= { vrrpStatistics 2 } 919 vrrpRouterVrIdErrors OBJECT-TYPE 920 SYNTAX Counter32 921 MAX-ACCESS read-only 922 STATUS current 923 DESCRIPTION 924 "The total number of VRRP packets received with an invalid 925 VRID for this virtual router." 926 ::= { vrrpStatistics 3 } 928 -- ******************************************************************* 929 -- VRRP Router Statistics Table 930 -- ******************************************************************* 932 vrrpRouterStatsTable OBJECT-TYPE 933 SYNTAX SEQUENCE OF VrrpRouterStatsEntry 934 MAX-ACCESS not-accessible 935 STATUS current 936 DESCRIPTION 937 "Table of virtual router statistics." 938 ::= { vrrpStatistics 4 } 940 vrrpRouterStatsEntry OBJECT-TYPE 941 SYNTAX VrrpRouterStatsEntry 942 MAX-ACCESS not-accessible 943 STATUS current 944 DESCRIPTION 945 "An entry in the table, containing statistics information 946 about a given virtual router." 947 AUGMENTS { vrrpOperEntry } 948 ::= { vrrpRouterStatsTable 1 } 950 VrrpRouterStatsEntry ::= 951 SEQUENCE { 952 vrrpStatsBecomeMaster 953 Counter32, 954 vrrpStatsAdvertiseRcvd 955 Counter32, 956 vrrpStatsAdvertiseIntervalErrors 957 Counter32, 958 vrrpStatsAuthFailures 959 Counter32, 960 vrrpStatsIpTtlErrors 961 Counter32, 962 vrrpStatsPriorityZeroPktsRcvd 963 Counter32, 964 vrrpStatsPriorityZeroPktsSent 965 Counter32, 966 vrrpStatsInvalidTypePktsRcvd 967 Counter32, 968 vrrpStatsAddressListErrors 969 Counter32, 970 vrrpStatsInvalidAuthType 971 Counter32, 972 vrrpStatsAuthTypeMismatch 973 Counter32, 974 vrrpStatsPacketLengthErrors 975 Counter32 976 } 978 vrrpStatsBecomeMaster OBJECT-TYPE 979 SYNTAX Counter32 980 MAX-ACCESS read-only 981 STATUS current 982 DESCRIPTION 983 "The total number of times that this virtual router's state 984 has transitioned to MASTER." 985 ::= { vrrpRouterStatsEntry 1 } 987 vrrpStatsAdvertiseRcvd OBJECT-TYPE 988 SYNTAX Counter32 989 MAX-ACCESS read-only 990 STATUS current 991 DESCRIPTION 992 "The total number of VRRP advertisements received by this 993 virtual router." 994 ::= { vrrpRouterStatsEntry 2 } 996 vrrpStatsAdvertiseIntervalErrors OBJECT-TYPE 997 SYNTAX Counter32 998 MAX-ACCESS read-only 999 STATUS current 1000 DESCRIPTION 1001 "The total number of VRRP advertisement packets received 1002 for which the advertisement interval is different than the 1003 one configured for the local virtual router." 1004 ::= { vrrpRouterStatsEntry 3 } 1006 vrrpStatsAuthFailures OBJECT-TYPE 1007 SYNTAX Counter32 1008 MAX-ACCESS read-only 1009 STATUS current 1010 DESCRIPTION 1011 "The total number of VRRP packets received that do not pass 1012 the authentication check." 1013 ::= { vrrpRouterStatsEntry 4 } 1015 vrrpStatsIpTtlErrors OBJECT-TYPE 1016 SYNTAX Counter32 1017 MAX-ACCESS read-only 1018 STATUS current 1019 DESCRIPTION 1020 "The total number of VRRP packets received by the virtual 1021 router with IP TTL (Time-To-Live) not equal to 255." 1022 ::= { vrrpRouterStatsEntry 5 } 1024 vrrpStatsPriorityZeroPktsRcvd OBJECT-TYPE 1025 SYNTAX Counter32 1026 MAX-ACCESS read-only 1027 STATUS current 1028 DESCRIPTION 1029 "The total number of VRRP packets received by the virtual 1030 router with a priority of '0'." 1031 ::= { vrrpRouterStatsEntry 6 } 1033 vrrpStatsPriorityZeroPktsSent OBJECT-TYPE 1034 SYNTAX Counter32 1035 MAX-ACCESS read-only 1036 STATUS current 1037 DESCRIPTION 1038 "The total number of VRRP packets sent by the virtual router 1039 with a priority of '0'." 1040 ::= { vrrpRouterStatsEntry 7 } 1042 vrrpStatsInvalidTypePktsRcvd OBJECT-TYPE 1043 SYNTAX Counter32 1044 MAX-ACCESS read-only 1045 STATUS current 1046 DESCRIPTION 1047 "The number of VRRP packets received by the virtual router 1048 with an invalid value in the 'type' field." 1049 ::= { vrrpRouterStatsEntry 8 } 1051 vrrpStatsAddressListErrors OBJECT-TYPE 1052 SYNTAX Counter32 1053 MAX-ACCESS read-only 1054 STATUS current 1055 DESCRIPTION 1056 "The total number of packets received for which the address 1057 list does not match the locally configured list for the 1058 virtual router." 1059 ::= { vrrpRouterStatsEntry 9 } 1061 vrrpStatsInvalidAuthType OBJECT-TYPE 1062 SYNTAX Counter32 1063 MAX-ACCESS read-only 1064 STATUS current 1065 DESCRIPTION 1066 "The total number of packets received with an unknown 1067 authentication type." 1068 ::= { vrrpRouterStatsEntry 10 } 1070 vrrpStatsAuthTypeMismatch OBJECT-TYPE 1071 SYNTAX Counter32 1072 MAX-ACCESS read-only 1073 STATUS current 1074 DESCRIPTION 1075 "The total number of packets received with 'Auth Type' not 1076 equal to the locally configured authentication method 1077 (`vrrpOperAuthType')." 1078 ::= { vrrpRouterStatsEntry 11 } 1080 vrrpStatsPacketLengthErrors OBJECT-TYPE 1081 SYNTAX Counter32 1082 MAX-ACCESS read-only 1083 STATUS current 1084 DESCRIPTION 1085 "The total number of packets received with a packet length 1086 less than the length of the VRRP header." 1087 ::= { vrrpRouterStatsEntry 12 } 1089 -- ******************************************************************* 1090 -- Trap Definitions 1091 -- ******************************************************************* 1093 vrrpTraps OBJECT IDENTIFIER ::= { vrrpNotifications 1 } 1095 vrrpTrapPacketSrc OBJECT-TYPE 1096 SYNTAX IpAddress 1097 MAX-ACCESS accessible-for-notify 1098 STATUS current 1099 DESCRIPTION 1100 "The IP address of an inbound VRRP packet. Used by 1101 vrrpTrapAuthFailure trap." 1102 ::= { vrrpTraps 1 } 1104 vrrpTrapAuthErrorType OBJECT-TYPE 1105 SYNTAX INTEGER { 1106 invalidAuthType (1), 1107 authTypeMismatch (2), 1108 authFailure (3) 1109 } 1110 MAX-ACCESS accessible-for-notify 1111 STATUS current 1112 DESCRIPTION 1113 "Potential types of configuration conflicts. 1114 Used by vrrpAuthFailure trap." 1115 ::= { vrrpTraps 2 } 1117 vrrpTrapNewMaster NOTIFICATION-TYPE 1118 OBJECTS { ifIndex, 1119 vrrpOperVrId 1120 } 1121 STATUS current 1122 DESCRIPTION 1123 "The newMaster trap indicates that the sending agent 1124 has transitioned from 'Backup' state to 'Master' state." 1125 ::= { vrrpTraps 3 } 1127 vrrpTrapAuthFailure NOTIFICATION-TYPE 1128 OBJECTS { ifIndex, 1129 vrrpOperVrId, 1130 vrrpTrapPacketSrc, 1131 vrrpTrapAuthErrorType 1132 } 1133 STATUS current 1134 DESCRIPTION 1135 "A vrrpAuthFailure trap signifies that a packet has 1136 been received from a router whose authentication key 1137 or authentication type conflicts with this router's 1138 authentication key or authentication type. Implementation 1139 of this trap is optional." 1140 ::= { vrrpTraps 4 } 1142 -- ******************************************************************* 1143 -- Conformance Information 1144 -- ******************************************************************* 1146 vrrpMIBCompliances OBJECT IDENTIFIER ::= { vrrpConformance 1 } 1147 vrrpMIBGroups OBJECT IDENTIFIER ::= { vrrpConformance 2 } 1149 -- ................................................................... 1150 -- Compliance Statements 1151 -- ................................................................... 1153 vrrpMIBCompliance MODULE-COMPLIANCE 1154 STATUS current 1155 DESCRIPTION 1156 "The core compliance statement for all VRRP implementations." 1157 MODULE -- this module 1158 MANDATORY-GROUPS { 1159 vrrpOperGroup , 1160 vrrpStatsGroup 1161 } 1162 ::= { vrrpMIBCompliances 1 } 1164 -- ................................................................... 1165 -- Conformance Groups 1166 -- ................................................................... 1168 vrrpOperGroup OBJECT-GROUP 1169 OBJECTS { 1170 vrrpNodeVersion, 1171 vrrpTrapCntl, 1172 vrrpOperVrId, 1173 vrrpOperVirtualMacAddr, 1174 vrrpOperState, 1175 vrrpOperAdminState, 1176 vrrpOperPriority, 1177 vrrpOperIpAddrCount, 1178 vrrpOperMasterIpAddr, 1179 vrrpOperPrimaryIpAddr, 1180 vrrpOperAuthType, 1181 vrrpOperAuthKey, 1182 vrrpOperAdvertisementInterval, 1183 vrrpOperPreemptMode, 1184 vrrpOperVirtualRouterUpTime, 1185 vrrpOperProtocol, 1186 vrrpOperRowStatus, 1187 vrrpAssoIpAddr, 1188 vrrpAssoIpAddrRowStatus 1189 } 1190 STATUS current 1191 DESCRIPTION 1192 "Conformance group for VRRP operations." 1193 ::= { vrrpMIBGroups 1 } 1195 vrrpStatsGroup OBJECT-GROUP 1196 OBJECTS { 1197 vrrpRouterChecksumErrors, 1198 vrrpRouterVersionErrors, 1199 vrrpRouterVrIdErrors, 1200 vrrpStatsBecomeMaster, 1201 vrrpStatsAdvertiseRcvd, 1202 vrrpStatsAdvertiseIntervalErrors, 1203 vrrpStatsAuthFailures, 1204 vrrpStatsIpTtlErrors, 1205 vrrpStatsPriorityZeroPktsRcvd, 1206 vrrpStatsPriorityZeroPktsSent, 1207 vrrpStatsInvalidTypePktsRcvd, 1208 vrrpStatsAddressListErrors, 1209 vrrpStatsInvalidAuthType, 1210 vrrpStatsAuthTypeMismatch, 1211 vrrpStatsPacketLengthErrors 1212 } 1213 STATUS current 1214 DESCRIPTION 1215 "Conformance group for VRRP statistics." 1216 ::= { vrrpMIBGroups 2 } 1217 END 1219 4. Security Considerations 1221 There are a number of management objects defined in this MIB that 1222 have a MAX-ACCESS clause of read-write or read-create. Such objects 1223 may be considered sensitive or vulnerable to security attacks in some 1224 networking environments. The support for SET operations in a non- 1225 secure environment without proper protection can have a negative 1226 effect on VRRP router operations. 1228 A number of objects in the vrrpOperTable possess the read-create 1229 attribute. Manipulation of these objects is capable of affecting the 1230 operation of a virtual router. 1232 Specific examples of this include, but are not limited to: 1234 o The vrrpOperAdminState object which could be used to disable a 1235 virtual router. 1237 o The vrrpOperPrimaryIpAddr object which, if compromised, could 1238 allow assignment of an invalid IP address to a master router. 1240 o The authentication type/key related objects which could 1241 potentially render the VRRP security mechanisms ineffective. 1243 Of additional concern is the ability to disable the transmission of 1244 traps. This would nullify the capability of a virtual router to 1245 provide notification in the event of an authentication failure. 1247 SNMPv1 by itself is not a secure environment. Even if the network 1248 itself is secure (for example by using IPSec), even then, there is no 1249 control as to who on the secure network is allowed to access and 1250 GET/SET (read/change/create/delete) the objects in this MIB. 1252 It is recommended that the implementers consider the security 1253 features as provided by the SNMPv3 framework. Specifically, the use 1254 of the User-based Security Model RFC 2574 [RFC2574] and the View- 1255 based Access Control Model RFC 2575 [RFC2575] is recommended. 1257 It is then a customer/user responsibility to ensure that the SNMP 1258 entity giving access to an instance of this MIB, is properly 1259 configured to give access to the objects only to those principals 1260 (users) that have legitimate rights to indeed GET or SET 1261 (change/create/delete) them. 1263 5. Acknowledgements 1265 The authors would like to thank Danny Mitzel, Venkat Prasad, Al Pham, 1266 Robert Hinden, Venkat Prasad, Barbera Denny, Fred Baker, Jeff Case, 1267 Flavio Fernandes, Acee Lindem and Scott Barvick for their comments 1268 and suggestions. 1270 6. References 1272 [1] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for 1273 Describing SNMP Management Frameworks", RFC 2571, Cabletron 1274 Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, 1275 April 1999 1277 [2] Rose, M., and K. McCloghrie, "Structure and Identification of 1278 Management Information for TCP/IP-based Internets", RFC 1155, STD 1279 16, Performance Systems International, Hughes LAN Systems, May 1280 1990 1282 [3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", RFC 1212, 1283 STD 16, Performance Systems International, Hughes LAN Systems, 1284 March 1991 1286 [4] M. Rose, "A Convention for Defining Traps for use with the SNMP", 1287 RFC 1215, Performance Systems International, March 1991 1289 [5] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, 1290 M., and S. Waldbusser, "Structure of Management Information 1291 Version 2 (SMIv2)", RFC 2578, STD 58, Cisco Systems, SNMPinfo, TU 1292 Braunschweig, SNMP Research, First Virtual Holdings, International 1293 Network Services, April 1999 1295 [6] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, 1296 M., and S. Waldbusser, "Textual Conventions for SMIv2", RFC 2579, 1297 STD 58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP Research, 1298 First Virtual Holdings, International Network Services, April 1999 1300 [7] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, 1301 M., and S. Waldbusser, "Conformance Statements for SMIv2", RFC 1302 2580, STD 58, Cisco Systems, SNMPinfo, TU Braunschweig, SNMP 1303 Research, First Virtual Holdings, International Network Services, 1304 April 1999 1306 [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple 1307 Network Management Protocol", RFC 1157, STD 15, SNMP Research, 1308 Performance Systems International, Performance Systems 1309 International, MIT Laboratory for Computer Science, May 1990. 1311 [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1312 "Introduction to Community-based SNMPv2", RFC 1901, SNMP Research, 1313 Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., 1314 International Network Services, January 1996. 1316 [10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport 1317 Mappings for Version 2 of the Simple Network Management Protocol 1318 (SNMPv2)", RFC 1906, SNMP Research, Inc., Cisco Systems, Inc., 1319 Dover Beach Consulting, Inc., International Network Services, 1320 January 1996. 1322 [11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 1323 Processing and Dispatching for the Simple Network Management 1324 Protocol (SNMP)", RFC 2572, SNMP Research, Inc., Cabletron 1325 Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, 1326 April 1999 1328 [12] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) 1329 for version 3 of the Simple Network Management Protocol (SNMPv3)", 1330 RFC 2574, IBM T. J. Watson Research, April 1999 1332 [13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol 1333 Operations for Version 2 of the Simple Network Management Protocol 1334 (SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco Systems, Inc., 1335 Dover Beach Consulting, Inc., International Network Services, 1336 January 1996. 1338 [14] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC 1339 2573, SNMP Research, Inc., Secure Computing Corporation, Cisco 1340 Systems, April 1999 1342 [15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access 1343 Control Model (VACM) for the Simple Network Management Protocol 1344 (SNMP)", RFC 2575, IBM T. J. Watson Research, BMC Software, Inc., 1345 Cisco Systems, Inc., April 1999 1347 [16] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction to 1348 Version 3 of the Internet-standard Network Management Framework", 1349 RFC 2570, SNMP Research, Inc., TIS Labs at Network Associates, 1350 Inc., Ericsson, Cisco Systems, April 1999 1352 [17] Knight, S., Weaver, D., Whipple, D., Hinden, R., Mitzel, D., Hunt, 1353 P., Higginson, P., Shand, M., Lindem, A., "Virtual Router 1354 Redundancy Protocol", RFC 2338. 1356 [18] McCloghrie, K., and M. Rose, "Management Information Base for 1357 Network Management of TCP/IP-based internets - MIB-II", STD 17, 1358 RFC 1213, March 1991. 1360 [19] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and S. 1361 Waldbusser, "Structure of Management Information for version 2 of 1362 the Simple Network Management Protocol (SNMPv2)", RFC 1902, 1363 January 1996. 1365 [20] SNMPv2 Working Group, J. Case, K. McCloghrie, M. Rose, and S. 1366 Waldbusser, "Textual Conventions for version 2 of the Simple 1367 Network Management Protocol (SNMPv2)", RFC 1903, January 1996. 1369 [21] SNMPv2 Working Group, J. Case, K. McCloghrie, M. Rose, and S. 1370 Waldbusser, "Conformance Statements for version 2 of the Simple 1371 Network Management Protocol (SNMPv2)", RFC 1904, January 1996. 1373 [22] Postel, J., Reynolds, J., "Instructions to RFC Authors", RFC 2223, 1374 October 1997. 1376 [23] McCloghrie, K., and F. Kastenholz, "The Interfaces Group MIB using 1377 SMIv2", RFC 2233, Cisco Systems, November 1997. 1379 7. Authors' Addresses 1381 Brian R. Jewell 1382 3Com, Inc. 1383 5400 Bayfront Plaza 1384 Santa Clara, CA 95052 1385 US 1387 Phone: +1 326 764 6173 1388 EMail: bjewell@3com.com 1390 David Chuang 1391 3Com, Inc. 1392 5400 Bayfront Plaza 1393 Santa Clara, CA 95052 1394 US 1396 Phone: +1 408 326 6610 1397 EMail: david_chuang@3com.com 1398 -- ------------------------------------------------------------------- 1399 -- Change Log 1400 -- ------------------------------------------------------------------- 1401 This section tracks changes made during revisions of this document. It 1402 will be deleted when the document is published as an RFC. 1404 * June 1999: Changes in 8th revision (draft-ietf-vrrp-mib-08.txt): 1406 - Changed inport of "ifIndex" from RFC 1213 to IF-MIB. 1407 - Added new IANA assigned MIB OID (68). 1409 * June 1999: Changes in 7th revision (draft-ietf-vrrp-mib-07.txt): 1411 - Added MIB Boilerplate for "The SNMP Management Framework" section. 1412 - Added "Security Considerations" section 1413 - Removed references to "SNMPv2" in header and footers. 1415 * May, 1999: Changes in 6th revision (draft-ietf-vrrp-mib-06.txt): 1417 - Removed description of how "vrrpOperVirtualMacAddr" is specifed 1418 as per changes to the VRRP Spec (addition of Token Ring). 1419 - Added citiations for RFC 1903 and RFC 1904 in references. 1420 - Modifed reference to RFC 1573, which has been obsoleted by RFC 1421 2233. 1423 * March, 1999: Changes in 5th revision (draft-ietf-vrrp-mib-05.txt): 1425 - Objects under "vrrpRouterStatsEntry" were renumbered. OID's 1426 became out-of-sequence due to changes made in the last revision 1427 (04). 1428 - Format of section numbers was changed ('.' added) to be consistant 1429 with other RFC's. 1430 - Changed the type of "vrrpNodeVersion" from INTEGER to Integer32. 1431 Also made DEFVAL (for this object) a decimal number. 1432 - A few spelling and typographical corrections were made. 1433 - Revisions were made to the format of some of the references to 1434 make then more concise and consistant. 1435 - Reworded the Overview section to attempt to make the description 1436 of VRRP more in-line with the VRRP RFC. 1438 * January, 1999: Changes in 4th revision (draft-ietf-vrrp-mib-04.txt): 1440 - "vrrpNodeVersion" SYNTAX changed from OCTET STRING to INTEGER. 1441 - Removed the REFERENCE clause from "vrrpOperVirtualMacAddr", as it 1442 was deemed redundant. 1443 - The range of vrrpOperAddrCount was changed from (1..255) to 1444 (0..255). This reflects the fact that a row might be created 1445 in the vrrpOperTable *prior* to creating a row in the 1446 vrrpAssoIpAddrTable. 1447 - Removed DEFVAL clause from "vrrpOperAuthKey" as unnecessary. 1448 - Moved the following objects out of the "vrrpRouterStatsTable" 1449 to become "global" VRRP router objects: "vrrpStatsChecksunErrors", 1450 "vrrpStatsVersionErrors", "vrrpStatsVrIdErrors". Each of these 1451 was renamed "vrrpRouter*", accordingly (since they are no longer 1452 members of the vrrpRouterStatsTable. The reason for this change 1453 is that, when any of these events occur, attempting to map the 1454 packet, with possible corruption of the VRID (or other fields), 1455 into a row of the vrrpRouterStatsTable would be risky, at best. 1456 - Removed "vrrpOperVirtualMacAddr" from the "vrrpTrapNewMaster". 1457 Since the virtual MAC can be derived from the VR ID, this was 1458 extra payload in the trap. 1459 - removed "vrrpTrapConfigErrorType" and "vrrpTrapPacketSrc" 1460 from conformance groups, as these are not mandatory objects. 1461 - Added new object, "vrrpOperPrimaryIpAddr" to vrrpOperTable. 1462 This object allows for designation of the vrrp IP primary 1463 address on an interface with multiple IP addresses, should this 1464 virtual router transition from backup to master. 1465 - Changed vrrpRouterStatsEntry to AUGMENT the vrrpOperEntry, since 1466 there is a one-to-one correspondence between these two objects 1467 and they are indexed with identical parmeters. 1468 - Addded new object, vrrpStatsPacketLengthErrors, to the statistics 1469 table. 1470 - Changed the description for "vrrpStatsSecurityViolations" to apply 1471 to *all* types of authentication failures, as opposed to 1472 cleartext auth failures only, which it previously stated. 1473 - Renamed "vrrpTrapConfigErrorType" object to "vrrpTrapAuthErrorType" 1474 and added a new enumeration for "authentication failures". 1475 - Renamed "vrrpStatsAuthTypeErrors" to "vrrpStatsAuthTypeMismatch". 1476 - Renamed "vrrpStatsSecurityViolations" to " vrrpStats- 1477 AuthenticationFailures" 1479 * November, 1998: Changes in 3rd revision (draft-ietf-vrrp-mib-03.txt): 1481 - Changed name of "vrrpAssoIpAddrStatus" object to 1482 "vrrpAssoIpAddrRowStatus" for consistancy with similar object 1483 in vrrpOperTable. 1484 - Changed name of "vrrpOperControl" object to "vrrpOperAdminState" 1485 and enhanced description clause. 1486 - Renumbered the objects in both the vrrpOperTable and 1487 vrrpAssoIpAddrTable. The first objects in the tables started 1488 with an OID of '2', when they should have started with '1'. 1490 - Changed the name of "vrrpStatsUnknownAuthType" to 1491 "vrrpStatsInvalidAuthType" as per suggestion that it was 1492 more concise. 1493 - Rewrote the descriptions for the table Entry objects and the 1494 rowstatus objects to make the process of row creation and 1495 deletion more clear. Each enumeration of the rowstatus 1496 object in the "vrrpOperTable" is now clearly explained. 1497 - Changed MAX-ACCESS to "read-create" on the "vrrpOperAuthType" 1498 and "vrrpOperAuthKey" objects. This was done with the 1499 assumption the the VRRP RFC will change to make these 1500 attributes defined on a "per-virtual-router-basis" as 1501 was proposed at the August (1998) IETF Meeting. 1503 * July, 1998: Changes in 2nd revision (draft-ietf-vrrp-mib-02.txt): 1505 - A number of changes were made to the textual content of the 1506 draft as per feedback received at the last WG meeting. These 1507 changes were too numerous to document individually in this 1508 section. 1509 - The size of the "vrrpNodeVersion" object has been changed from 1510 2 octets to 1 octet. 1511 - References to obsoleted RFC's have been replaced by references 1512 to later documents. Notably, references to RFC's 1442, 1443 and 1513 1444 have been replaced by RFC 1902, RFC 1903 and RFC 1904, 1514 respectively. 1515 - The description for the "vrrpOperControl" was changed to 1516 reflect the fact that a virtual router does not necessarily 1517 transition directly from initialize state -> backup state. 1518 The description for the "vrrpStatsBecomeMaster" was also 1519 changed to more accurately convey this fact. 1520 - The SYNTAX of the "vrrpOperIpAddrCount" was changed to 1521 reflect the fact that a virtual router can support only up 1522 to 255 backup IP addresses. 1523 - Descriptions for vrrpOperAuthType and vrrpOperAuthKey expanded 1524 to indicate the per-interface assignment. 1525 - SYNTAX of vrrpOperPreemptMode object changed from INTEGER 1526 to 'truthValue' 1527 - The OIDs for the VRRP traps were fixed; incorrect ident- 1528 ifiers ('vrrpOperations') had been used in OID assignments. 1529 - The SYNTAX for the 'vrrpOperPriority' object was corrected 1530 to indicate that this can have a value of '0'. 1531 - The vrrpOperHMACMD5Key object was deleted. It was combined 1532 with the vrrpOperAuthKey object, whose SYNTAX was adjusted 1533 accordingly. 1534 - OID for 'vrrpTraps' changed to '{ vrrpNotifications 1 }' 1535 - The 'vrrpStatsPasswdSecurityViolations' and 'vrrpStatsHmac- 1536 SecurityViolations' objects have been combined into a 1537 single 'vrrpStatsSecurityViolations' object; this was 1538 suggested to avoid redundancy. 1539 - As per the last WG meeting, the 'vrrpAssoIpAddrIndex' object 1540 has been deleted from the 'vrrpAssoIpAddrTable'and replaced 1541 by 'vrrpAssoIpAddr'. 1542 - Removed references to 'vrrpAssoIpAddrIndex' in samples. 1543 - Added new object 'vrrpOperProtocol' to 'VrrpOperEntry'. 1544 - MAX-ACCESS for the 'vrrpOperVrId' object changed to 1545 'not-accessible', as per RFC1902 (auxilary objects). 1546 - SYNTAX for 'vrrpOperVirtualRouterUpTime' changed to 1547 'TimeStamp'. 1548 - Added importation of 'TruthValue'and 'TimeStamp' to accomodate 1549 changes listed above. Deleted importation of 'TimeTicks'. 1550 - Changed MAX-ACCESS to 'accessible-for-notify' for 1551 'vrrpTrapPacketSrc' and 'vrrpTrapConfigErrorType' objects. 1552 - In the sample tables, the "if" values were incorrect for 1553 the sample tables for "IP B" (they used to read "I1"). 1554 - MAX-ACCESS for 'vrrpOperAuthType' and 'vrrpOperAuthKey' 1555 changed to 'read-only', since these objects are defined on 1556 a per-interface basis. 1557 - Overall review and editing of Section 5.0 (References) with 1558 deletion of references not used in this document. Also, added 1559 reference '9'. 1561 Concerns: 1562 --------- 1563 - Keep the 'vrrpTrapAuthFailure' trap? 1564 - Remove 'vrrpTrapPacketSrc' and 'vrrpTrapConfigErrorType' from 1565 compliances? Only used for 'vrrpTrapAuthFailure' trap. 1567 * 3/4/1998: Changes in 1st revision (draft-ietf-vrrp-mib-01.txt): 1569 - Overall review and editing of document text and object 1570 descriptions from feedback received at December 1997 IETF meeting. 1571 More specifically the changes made along these lines include 1572 the following: 1574 -- Cleaned up Section 5.0 ("References") and validated. 1575 -- Modifed diagram for VRRP Scenario #2 (Section 2.4.2). 1576 -- VRRP Overview (Section 2.0) rewritten to be more in-line with 1577 latest revision (05) of VRRP RFC Draft. 1578 -- Description of "VrId" Textual convention rewritten. 1580 - MAX-ACCESS of vrrpTrapCntl object changed to "read-write". 1581 - Changed SYNTAX of "vrrpOperVirtualMacAddr" object from 1582 "PhyAddress" to "MacAddress". 1583 - Changed the syntax of the "vrrpOperPriority" object so upper 1584 value can be 255. 1585 - Change MAX-ACCESS for "vrrpOperAuthType" object from 1586 read-only to read-create. 1587 - Added three new objects to "vrrpRouterStatsTable": 1588 "vrrpStatsAddressListErrors", "vrrpStatsUnknownAuthType" 1589 and "vrrpStatsAuthTypeErrors". 1590 - Removed "vrrpStatsUnknownPacketType" object, as it was 1591 redundant (with "vrrpStatsInvalidPacketType"). 1592 - Removed the "vrrpOperIfIndex" object to use "ifIndex" (which is 1593 actually equivalent) instead. 1595 * 11/19/97 (vft-ietf-vrrp-mib-00.txt) - Initial Draft