Definitions of Managed Objects for the Virtual Router Redundancy Protocol
RFC 2787

Document Type RFC - Proposed Standard (March 2000; No errata)
Obsoleted by RFC 6527
Last updated 2013-03-02
Stream IETF
Formats plain text pdf html bibtex
Stream WG state (None)
Document shepherd No shepherd assigned
IESG IESG state RFC 2787 (Proposed Standard)
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                           B. Jewell
Request for Comments: 2787                 Copper Mountain Networks, Inc.
Category: Standards Track                                       D. Chuang
                                                    CoSine Communications
                                                               March 2000

                 Definitions of Managed Objects for the
                   Virtual Router Redundancy Protocol

Status of this Memo

   This document specifies an Internet standards track protocol for the
   Internet community, and requests discussion and suggestions for
   improvements.  Please refer to the current edition of the "Internet
   Official Protocol Standards" (STD 1) for the standardization state
   and status of this protocol.  Distribution of this memo is unlimited.

Copyright Notice

   Copyright (C) The Internet Society (2000).  All Rights Reserved.

Abstract

   This specification defines an extension to the Management Information
   Base (MIB) for use with SNMP-based network management.  In
   particular, it defines objects for configuring, monitoring, and
   controlling routers that employ the Virtual Router Redundancy
   Protocol (VRRP) [17].

   This memo specifies a MIB module in a manner that is compliant with
   SMIv2 [5], and semantically identical to the SMIv1 definitions [2].

Jewell & Chuang             Standards Track                     [Page 1]
RFC 2787              VRRP MIB Management Objects             March 2000

Table of Contents

   1  The SNMP Network Management Framework .................    2
   2  Overview ..............................................    3
   2.1  VRRP MIB Structure ..................................    3
   2.2  Virtual Router Redundancy Protocol ..................    4
   2.3  VRRP MIB Table Design ...............................    4
   2.3.1  Relation to Interface Group .......................    5
   2.4  VRRP Scenarios ......................................    5
   2.4.1  Scenario #1 .......................................    5
   2.4.2  Scenario #2 .......................................    8
   3  Definitions ...........................................   11
   4  Security Considerations ...............................   27
   5  Acknowledgements ......................................   28
   6  References ............................................   28
   7  Authors' Addresses ....................................   30
   8  Intellectual Property Statement........................   30
   9  Full Copyright Statement...............................   31

1.  The SNMP Management Framework

   The SNMP Management Framework presently consists of five major
   components:

   o An overall architecture, described in RFC 2571 [1].

   o Mechanisms for describing and naming objects and events for the
     purpose of management. The first version of this Structure of
     Management Information (SMI) is called SMIv1 and described in STD
     16, RFC 1155 [2], STD 16, RFC 1212 [3] and RFC 1215 [4]. The second
     version, called SMIv2, is described in STD 58, RFC 2578 [5], STD
     58, RFC 2579 [6] and STD 58, RFC 2580 [7].

   o Message protocols for transferring management information. The
     first version of the SNMP message protocol is called SNMPv1 and
     described in STD 15, RFC 1157 [8]. A second version of the SNMP
     message protocol, which is not an Internet standards track
     protocol, is called SNMPv2c and described in RFC 1901 [9] and RFC
     1906 [10].  The third version of the message protocol is called
     SNMPv3 and described in RFC 1906 [10], RFC 2572 [11] and RFC 2574
     [12].

   o Protocol operations for accessing management information. The first
     set of protocol operations and associated PDU formats is described
     in STD 15, RFC 1157 [8]. A second set of protocol operations and
     associated PDU formats is described in RFC 1905 [13].

Jewell & Chuang             Standards Track                     [Page 2]
RFC 2787              VRRP MIB Management Objects             March 2000

   o A set of fundamental applications described in RFC 2573 [14] and
     the view-based access control mechanism described in RFC 2575 [15].

   A more detailed introduction to the current SNMP Management Framework
   can be found in RFC 2570 [16].

   Managed objects are accessed via a virtual information store, termed
   the Management Information Base or MIB.  Objects in the MIB are
   defined using the mechanisms defined in the SMI.

   This memo specifies a MIB module that is compliant to the SMIv2. A
   MIB conforming to the SMIv1 can be produced through the appropriate
   translations. The resulting translated MIB must be semantically
   equivalent, except where objects or events are omitted because no
   translation is possible (use of Counter64). Some machine readable
   information in SMIv2 will be converted into textual descriptions in
Show full document text