[要約] この文書は、IPv4およびIPv6ネットワークで動作するVRRPv3(Virtual Router Redundancy Protocol version 3)を管理するための管理情報ベース(MIB)を定義しています。VRRPルータの設定、状態監視、および統計情報の取得を可能にするオブジェクトを規定し、ネットワークの冗長構成を標準的なSNMPツールで管理できるようにします。

Internet Engineering Task Force (IETF)                           K. Tata
Request for Comments: 6527                                         Nokia
Obsoletes: 2787                                               March 2012
Category: Standards Track
ISSN: 2070-1721
        

Definitions of Managed Objects for the Virtual Router Redundancy Protocol Version 3 (VRRPv3)

仮想ルーター冗長性プロトコルバージョン3(VRRPV3)の管理されたオブジェクトの定義

Abstract

概要

This specification defines a portion of the Management Information Base (MIB) for use with network management based on the Simple Network Management Protocol (SNMP). In particular, it defines objects for configuring, monitoring, and controlling routers that employ the Virtual Router Redundancy Protocol Version 3 (VRRPv3) for both IPv4 and IPv6 as defined in RFC 5798. This memo obsoletes RFC 2787.

この仕様では、単純なネットワーク管理プロトコル(SNMP)に基づいて、ネットワーク管理で使用する管理情報ベース(MIB)の一部を定義します。特に、RFC 5798で定義されているように、IPv4とIPv6の両方の仮想ルーター冗長プロトコルバージョン3(VRRPV3)を使用するルーターを構成、監視、制御するオブジェクトを定義します。

Status of This Memo

本文書の状態

This is an Internet Standards Track document.

これは、インターネット標準トラックドキュメントです。

This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section 2 of RFC 5741.

このドキュメントは、インターネットエンジニアリングタスクフォース(IETF)の製品です。IETFコミュニティのコンセンサスを表しています。公開レビューを受けており、インターネットエンジニアリングステアリンググループ(IESG)からの出版が承認されています。インターネット標準の詳細については、RFC 5741のセクション2で入手できます。

Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc6527.

このドキュメントの現在のステータス、任意のERRATA、およびそのフィードバックを提供する方法に関する情報は、http://www.rfc-editor.org/info/rfc6527で取得できます。

Copyright Notice

著作権表示

Copyright (c) 2012 IETF Trust and the persons identified as the document authors. All rights reserved.

Copyright(c)2012 IETF Trustおよび文書著者として特定された人。全著作権所有。

This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://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.

このドキュメントは、BCP 78およびIETFドキュメント(http://trustee.ietf.org/license-info)に関連するIETF Trustの法的規定の対象となります。この文書に関するあなたの権利と制限を説明するので、これらの文書を注意深く確認してください。このドキュメントから抽出されたコードコンポーネントには、セクション4.Eで説明されている法的規定のセクション4.Eで説明されており、単純化されたBSDライセンスで説明されているように保証なしで提供される簡略化されたBSDライセンステキストを含める必要があります。

This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of such material outside the IETF Standards Process. Without obtaining an adequate license from the person(s) controlling the copyright in such materials, this document may not be modified outside the IETF Standards Process, and derivative works of it may not be created outside the IETF Standards Process, except to format it for publication as an RFC or to translate it into languages other than English.

この文書には、2008年11月10日より前に公開された、または一般に利用可能になったIETF文書またはIETFコントリビューションの素材が含まれている場合があります。この素材の一部について著作権を管理する者は、IETF標準プロセスの外でその素材を変更することを許可する権利をIETFトラストに付与していない可能性があります。そのような素材の著作権を管理する者から適切なライセンスを取得しない限り、IETF標準プロセスの外でこの文書を変更することはできません。また、RFCとして発行するために書式を整える場合と英語以外の言語に翻訳する場合を除き、IETF標準プロセスの外でこの文書の派生物を作成することはできません。

Table of Contents

目次

   1. The Internet-Standard Management Framework ......................2
   1. インターネット標準の管理フレームワーク ..........................2
   2. Introduction ....................................................3
   2. はじめに ........................................................3
   3. Terminology .....................................................3
   3. 用語 ............................................................3
   4. Relationship to RFC 2787 ........................................3
   4. RFC 2787との関係 ................................................3
   5. Relation to Interface Group (IF-MIB) ............................3
   5. インターフェイスグループとの関係(IF-MIB) ......................3
   6. Multi-Stack Implementations .....................................3
   6. マルチスタックの実装 ............................................3
   7. Interpretation of RFC 5798 ......................................3
   7. RFC 5798の解釈 ..................................................3
   8. VRRP MIB Structure and Design ...................................4
   8. VRRP MIB構造と設計 ..............................................4
   9. VRRP Multi-Stack Scenario .......................................4
   9. VRRPマルチスタックシナリオ ......................................4
   10. Definitions ....................................................7
   10. 定義 ...........................................................7
   11. Security Considerations .......................................27
   11. セキュリティに関する考慮事項 ..................................27
   12. IANA Considerations ...........................................29
   12. IANAの考慮事項 ................................................29
   13. Normative References ..........................................29
   13. 引用文献 ......................................................29
   14. Informative References ........................................30
   14. 参考引用 ......................................................30
   15. Acknowledgments ...............................................31
   15. 謝辞 ..........................................................31

1. The Internet-Standard Management Framework

1. インターネット標準の管理フレームワーク

For a detailed overview of the documents that describe the current Internet-Standard Management Framework, please refer to section 7 of RFC 3410 [RFC3410].

現在のインターネット標準管理フレームワークを説明するドキュメントの詳細な概要については、RFC 3410 [RFC3410]のセクション7を参照してください。

Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. MIB objects are generally accessed through the Simple Network Management Protocol (SNMP). Objects in the MIB are defined using the mechanisms defined in the Structure of Management Information (SMI). This memo specifies a MIB module that is compliant to the SMIv2, which is described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580].

管理されたオブジェクトは、管理情報ベースまたはMIBと呼ばれる仮想情報ストアからアクセスされます。MIBオブジェクトは通常、単純なネットワーク管理プロトコル(SNMP)からアクセスされます。MIBのオブジェクトは、管理情報の構造(SMI)で定義されたメカニズムを使用して定義されます。このメモは、STD 58、RFC 2578 [RFC2578]、STD 58、RFC 2579 [RFC2579]およびSTD 58、RFC 2580 [RFC2580]に記載されているSMIV2に準拠したMIBモジュールを指定します。

2. Introduction

2. はじめに

This specification defines a portion of the 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 Version 3 (VRRPv3) for both IPv4 and IPv6 as defined in RFC 5798 [RFC5798].

この仕様は、SNMPベースのネットワーク管理で使用するMIBの一部を定義します。特に、RFC 5798 [RFC5798]で定義されているように、IPv4とIPv6の両方の仮想ルーター冗長プロトコルバージョン3(VRRPV3)を使用するルーターを構成、監視、制御するオブジェクトを定義します。

3. Terminology

3. 用語

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119].

このドキュメントのキーワード "MUST"、"MUST NOT"、"REQUIRED"、"SHALL"、"SHALL NOT"、"SHOULD"、"SHOULD NOT"、"RECOMMENDED"、"NOT RECOMMENDED"、"MAY"、および "OPTIONAL" は、RFC 2119 [RFC2119] で説明されているように解釈されるものとします。

4. Relationship to RFC 2787

4. RFC 2787との関係

This document obsoletes RFC 2787 [RFC2787]. The major changes in this document reflect changes in the VRRP protocol between RFC 2338 [RFC2338] and RFC 5798 [RFC5798]. This document is also updated to conform to current MIB conventions.

この文書は、RFC 2787 [RFC2787]を廃止します。このドキュメントの主要な変更は、RFC 2338 [RFC2338]とRFC 5798 [RFC5798]の間のVRRPプロトコルの変化を反映しています。このドキュメントは、現在のMIB規則に準拠するために更新されます。

5. Relation to Interface Group (IF-MIB)

5. インターフェイスグループとの関係(IF-MIB)

Since a router can be participating in VRRP on one or more interfaces, "ifIndex" is used as an index into the tables defined in the VRRP MIB. This MIB module imports ifIndex from the IF-MIB. At this time, the latest version of the IF-MIB is from RFC 2863 [RFC2863].

ルーターは1つ以上のインターフェイスでVRRPに参加できるため、「ifIndex」はVRRP MIBで定義されたテーブルのインデックスとして使用されます。このMIBモジュールは、if-mibからifIndexをインポートします。この時点で、IF-MIBの最新バージョンはRFC 2863 [RFC2863]からです。

6. Multi-Stack Implementations

6. マルチスタックの実装

This MIB module is designed to support multi-stack implementations that run VRRP over IPv4 and IPv6. The IP version, Virtual Router Identifier (VRID), and ifIndex are used to uniquely identify rows in a multi-stack implementation.

このMIBモジュールは、IPv4およびIPv6を介してVRRPを実行するマルチスタック実装をサポートするように設計されています。IPバージョン、仮想ルーター識別子(VRID)、およびifIndexは、マルチスタックの実装で行を一意に識別するために使用されます。

7. Interpretation of RFC 5798

7. RFC 5798の解釈

During the review of this document, it emerged that there are different possible interpretations of [RFC5798]. The authors of that document and the VRRP working group were unable to reach consensus as to which interpretation is correct. This document makes the following assumption:

この文書のレビュー中に、[RFC5798]の異なる可能な解釈があることが明らかになりました。その文書の著者とVRRPワーキンググループは、どの解釈が正しいかについてコンセンサスに達することができませんでした。このドキュメントは、次の仮定を作成します。

IPv4 and IPv6 virtual routers are treated as two separate logical entities and represented as two separate entries in the vrrpv3OperationsTable. This is required due to the undefined behavior of the protocol in [RFC5798] in a multi-stack scenario.

IPv4およびIPv6仮想ルーターは、2つの別々の論理エンティティとして扱われ、vrrpv3OperationsTableの2つの別々のエントリとして表されます。これは、マルチスタックシナリオで[RFC5798]のプロトコルの未定義の動作のために必要です。

8. VRRP MIB Structure and Design

8. VRRP MIB構造と設計

This MIB module contains three tables:

このMIBモジュールには3つのテーブルが含まれています。

(1) The vrrpv3OperationsTable contains objects that define the operational characteristics of a VRRP router. Rows in this table correspond to instances of virtual routers.

(1) vrrpv3OperationsTableには、VRRPルーターの動作特性を定義するオブジェクトが含まれています。この表の行は、仮想ルーターのインスタンスに対応しています。

(2) The vrrpv3StatisticsTable contains the operating statistics for a VRRP router.

(2) vrrpv3StatisticsTableには、VRRPルーターの動作統計が含まれています。

(3) The vrrpv3AssociatedIpAddrTable contains the addresses of the virtual router(s) that a given VRRP router is backing up.

(3) VRRPV3ASSITEDIPADDRTABLEには、特定のVRRPルーターがバックアップしている仮想ルーターのアドレスが含まれています。

Tables are indexed on ifIndex, VRID, and the IP version to uniquely identify a VRRP router.

テーブルは、VRRPルーターを一意に識別するために、ifIndex、VRID、およびIPバージョンでインデックス付けされています。

Notifications in this MIB module are controlled using the mechanisms defined in [RFC3413].

このMIBモジュールの通知は、[RFC3413]で定義されたメカニズムを使用して制御されます。

9. VRRP Multi-Stack Scenario

9. VRRPマルチスタックシナリオ

The following section provides examples of how some of the objects in this MIB are instantiated.

次のセクションでは、このMIBの一部のオブジェクトがどのようにインスタンス化されているかの例を示します。

   KEY:
   ----
   The labels in the following tables and diagrams correspond to the
   actual MIB objects as follows:
        
   if      = IfIndex
   AddrType= vrrpv3OperationsInetAddrType
   VrId    = vrrpv3OperationsVrId
   State   = vrrpv3OperationsStatus
   Prior   = vrrpv3OperationsPriority
   IpAddr  = vrrpv3OperationsMasterIpAddr
        

The following figure shows a hypothetical network with two VRRP routers, VR1 & VR2, configured with two virtual routers. Addresses in '()' indicate the address of the default gateway for a given host; H1 to H4 are IPv4 hosts, and H5 to H8 are IPv6 hosts. A, B, and C are IPv4 addresses, and X, Y, and Z are IPv6 addresses. In the diagram, "Interface" is used in the context defined in IF-MIB.

次の図は、2つの仮想ルーターで構成された2つのVRRPルーター、VR1とVR2を備えた仮想ネットワークを示しています。'()'のアドレスは、特定のホストのデフォルトゲートウェイのアドレスを示します。H1〜H4はIPv4ホストであり、H5からH8はIPv6ホストです。A、B、およびCはIPv4アドレスであり、x、y、zはIPv6アドレスです。図では、「インターフェイス」は、if-mibで定義されたコンテキストで使用されます。

                 +------+                      +------+
                 | VR1  |                      |  VR2 |
                 |      |                      |      |
                 +------+                      +------+
                     |                            |
                Intf = I1                    Intf = I2
       IP A          |   IP X         IP B        |    IP Y
       IP C          |                            |    IP Z
       VRID = 1      |   VRID=2       VRID=2      |    VRID = 1
                     |                            |
   ----+------+------+-+-------+--------+--------++------+--------+---
       ^      ^        ^       ^        ^        ^       ^        ^
       |      |        |       |        |        |       |        |
    (IP A)  (IP A)   (IP B)  (IP B)   (IP X)   (IP X)  (IP Y)   (IP Y)
       |      |        |       |        |        |       |        |
    +----+  +----+  +----+  +----+    +----+   +----+  +----+  +----+
    | H1 |  | H2 |  | H3 |  | H4 |    | H5 |   | H6 |  | H7 |  | H8 |
    +----+  +----+  +----+  +----+    +----+   +----+  +----+  +----+
        
           -----   MIB Tables For VRRP Router "VR1":   -----
        
   vrrpv3OperationsTable
   -------------------
        
   | if | VrId |AddrType| State | Prior |IpAddr|        |
   +----+------+--------+-------+-------+------+--(..)--+
   | I1 |  01  |    1   |   M   |  255  |   A  |        |
   +----+------+--------+-------+-------+------+--(..)--+
   | I1 |  01  |    2   |   B   | 1-254 |   Y  |        |
   +----+------+--------+-------+-------+------+--(..)--+
   | I1 |  02  |    1   |   B   | 1-254 |   B  |        |
   +----+------+--------+-------+-------+------+--(..)--+
   | I1 |  02  |    2   |   M   |  255  |   X  |        |
   +----+------+--------+-------+-------+------+--------+
   vrrpv3AssociatedIpAddrTable
   -------------------------
        
   | if | VrId | AddrType | IP   | RowStat |
   +----+------+----------+------+---------+
   | I1 |  01  |    1     |  A   | active  |
   +----+------+----------+------+---------+
   | I1 |  01  |    1     |  C   | active  |
   +----+------+----------+------+---------+
   | I1 |  01  |    2     |  Y   | active  |
   +----+------+----------+------+---------+
   | I1 |  01  |    2     |  Z   | active  |
   +----+------+----------+------+---------+
   | I1 |  02  |    1     |  B   | active  |
   +----+------+----------+------+---------+
   | I1 |  02  |    2     |  X   | active  |
   +----+------+----------+------+---------+
        
           -----   MIB Tables For VRRP Router "VR2":   -----
        
   vrrpv3OperationsTable
   -------------------
        
   | if | VrId |AddrType| State | Prior |IpAddr|        |
   +----+------+--------+-------+-------+------+--(..)--+
   | I2 |  01  |    1   |   B   | 1-254 |   A  |        |
   +----+------+--------+-------+-------|------+--(..)--+
   | I2 |  01  |    2   |   M   | 255   |   Y  |        |
   +----+------+--------+-------+-------+------+--(..)--+
   | I2 |  02  |    1   |   M   |  255  |   B  |        |
   +----+------+--------+-------+-------+------+--(..)--+
   | I2 |  02  |    2   |   B   | 1-254 |   X  |        |
   +----+------+--------+-------+-------+------+--------+
   vrrpv3AssociatedIpAddrTable
   -------------------------
        
   | if | VrId |AddrType| IP   | RowStat |
   +----+------+--------+------+---------+
   | I2 |  01  |   1    |  A   | active  |
   +----+------+--------+------+---------+
   | I2 |  01  |   1    |  C   | active  |
   +----+------+--------+------+---------+
   | I2 |  01  |   2    |  Y   | active  |
   +----+------+--------+------+---------+
   | I2 |  01  |   2    |  Z   | active  |
   +----+------+--------+------+---------+
   | I2 |  02  |   1    |  B   | active  |
   +----+------+--------+------+---------+
   | I2 |  02  |   2    |  X   | active  |
   +----+------+--------+------+---------+
        

NOTES:

ノート:

1) For "State": M = Master; B = Backup. In the vrrpv3OperationsTable, a "priority" of 255 indicates that the respective router owns the IP address, e.g., this IP address is native to the router (i.e., "the IP Address Owner").

1) 「状態」の場合:m = master;b =バックアップ。vrrpv3OperationsTableでは、255の「優先度」は、それぞれのルーターがIPアドレスを所有していることを示しています。

10. Definitions

10. 定義

This MIB module makes reference to the following documents [RFC2578], [RFC2579], [RFC2580], [RFC2863], and [RFC4001].

このMIBモジュールは、次のドキュメント[RFC2578]、[RFC2579]、[RFC2580]、[RFC2863]、および[RFC4001]を参照しています。

   VRRPV3-MIB DEFINITIONS ::= BEGIN
        
       IMPORTS
           MODULE-IDENTITY, OBJECT-TYPE,
           NOTIFICATION-TYPE, Counter32,
           Integer32, mib-2, Unsigned32,
           Counter64, TimeTicks
               FROM SNMPv2-SMI                 -- RFC2578
        
           TEXTUAL-CONVENTION, RowStatus,
           MacAddress, TruthValue, TimeStamp,
           TimeInterval
               FROM SNMPv2-TC                  -- RFC2579
        
           MODULE-COMPLIANCE, OBJECT-GROUP,
           NOTIFICATION-GROUP
               FROM SNMPv2-CONF                -- RFC2580
        
           ifIndex
               FROM IF-MIB                     -- RFC2863
           InetAddressType, InetAddress
        
               FROM INET-ADDRESS-MIB;          -- RFC4001
        
      vrrpv3MIB  MODULE-IDENTITY
           LAST-UPDATED "201202130000Z"         -- Feb 13, 2012
           ORGANIZATION "IETF VRRP Working Group"
           CONTACT-INFO
                  "WG E-Mail: vrrp@ietf.org
        
                   Editor:    Kalyan Tata
                              Nokia
                              313 Fairchild Dr,
                              Mountain View, CA 94043
                              Tata_kalyan@yahoo.com"
        
           DESCRIPTION
               "This MIB describes objects used for managing Virtual
                Router Redundancy Protocol version 3 (VRRPv3).
        
                Copyright (c) 2012 IETF Trust and the persons
                identified as authors of the code.  All rights
                reserved.
        
                Redistribution and use in source and binary forms,
                with or without modification, is permitted pursuant
                to, and subject to the license terms contained in,
                the Simplified BSD License set forth in Section
                4.c of the IETF Trust's Legal Provisions Relating
                to IETF Documents
                (http://trustee.ietf.org/license-info).
        
                This version of the MIB module is part of RFC 6527.
                Please see the RFC for full legal notices."
        
           REVISION "201202120000Z"    -- Feb 13, 2012
           DESCRIPTION "Initial version as published in RFC 6527."
        
           ::= { mib-2 207 }
        
   -- Textual Conventions
        
      Vrrpv3VrIdTC ::= TEXTUAL-CONVENTION
           DISPLAY-HINT "d"
           STATUS       current
           DESCRIPTION
        
               "The value of the Virtual Router Identifier noted as
               (VRID) in RFC 5798.  This, along with interface index
               (ifIndex) and IP version, serves to uniquely identify
               a virtual router on a given VRRP router."
           REFERENCE "RFC 5798 (Sections 3 and 5.2.3)"
           SYNTAX      Integer32 (1..255)
        
   --  VRRPv3 MIB Groups
        
      vrrpv3Notifications   OBJECT IDENTIFIER ::= { vrrpv3MIB 0 }
      vrrpv3Objects         OBJECT IDENTIFIER ::= { vrrpv3MIB 1 }
      vrrpv3Conformance     OBJECT IDENTIFIER ::= { vrrpv3MIB 2 }
        
   -- VRRPv3 MIB Objects
        
      vrrpv3Operations      OBJECT IDENTIFIER ::= { vrrpv3Objects 1 }
      vrrpv3Statistics      OBJECT IDENTIFIER ::= { vrrpv3Objects 2 }
        
   --  VRRPv3 Operations Table
        
       vrrpv3OperationsTable OBJECT-TYPE
           SYNTAX       SEQUENCE OF Vrrpv3OperationsEntry
           MAX-ACCESS   not-accessible
           STATUS       current
           DESCRIPTION
               "Unified Operations table for a VRRP router that
                consists of a sequence (i.e., one or more conceptual
                rows) of 'vrrpv3OperationsEntry' items each of which
                describe the operational characteristics of a virtual
                router."
        
           ::= { vrrpv3Operations 1 }
        
       vrrpv3OperationsEntry OBJECT-TYPE
           SYNTAX       Vrrpv3OperationsEntry
           MAX-ACCESS   not-accessible
           STATUS       current
           DESCRIPTION
               "An entry in the vrrpv3OperationsTable containing the
                operational characteristics of a virtual router.
                On a VRRP router, a given virtual router is
                identified by a combination of ifIndex, VRID, and
                the IP version.  ifIndex represents an interface of
                the router.
        
                A row must be created with vrrpv3OperationsStatus
                set to initialize(1) and cannot transition to
                backup(2) or master(3) until
        
                vrrpv3OperationsRowStatus is transitioned to
                active(1).
        
                The information in this table is persistent and when
                written the entity SHOULD save the change to non-
                volatile storage."
        
           INDEX    { ifIndex, vrrpv3OperationsVrId,
                      vrrpv3OperationsInetAddrType
                     }
           ::= { vrrpv3OperationsTable 1 }
        
       Vrrpv3OperationsEntry ::=
        
           SEQUENCE {
               vrrpv3OperationsVrId
                   Vrrpv3VrIdTC,
               vrrpv3OperationsInetAddrType
                   InetAddressType,
               vrrpv3OperationsMasterIpAddr
                   InetAddress,
               vrrpv3OperationsPrimaryIpAddr
                   InetAddress,
               vrrpv3OperationsVirtualMacAddr
                   MacAddress,
               vrrpv3OperationsStatus
                   INTEGER,
               vrrpv3OperationsPriority
                   Unsigned32,
               vrrpv3OperationsAddrCount
                   Integer32,
               vrrpv3OperationsAdvInterval
                   TimeInterval,
               vrrpv3OperationsPreemptMode
                   TruthValue,
               vrrpv3OperationsAcceptMode
                   TruthValue,
               vrrpv3OperationsUpTime
                   TimeTicks,
               vrrpv3OperationsRowStatus
                   RowStatus
       }
       vrrpv3OperationsVrId OBJECT-TYPE
           SYNTAX       Vrrpv3VrIdTC
           MAX-ACCESS   not-accessible
           STATUS       current
           DESCRIPTION
        
               "This object contains the Virtual Router Identifier
                (VRID)."
           REFERENCE "RFC 4001"
           ::= { vrrpv3OperationsEntry 1 }
        
       vrrpv3OperationsInetAddrType OBJECT-TYPE
           SYNTAX       InetAddressType
           MAX-ACCESS   not-accessible
           STATUS       current
           DESCRIPTION
              "The IP address type of Vrrpv3OperationsEntry and
               Vrrpv3AssociatedIpAddrEntry.  This value determines
               the type for vrrpv3OperationsMasterIpAddr,
               vrrpv3OperationsPrimaryIpAddr, and
               vrrpv3AssociatedIpAddrAddress.
        
                ipv4(1) and ipv6(2) are the only two values supported
                in this MIB module."
           REFERENCE "RFC 4001"
           ::= { vrrpv3OperationsEntry 2 }
        
       vrrpv3OperationsMasterIpAddr OBJECT-TYPE
           SYNTAX       InetAddress
           MAX-ACCESS   read-only
           STATUS       current
           DESCRIPTION
             "The master router's real IP address.  The master router
             would set this address to vrrpv3OperationsPrimaryIpAddr
             while transitioning to master state.  For backup
             routers, this is the IP address listed as the source in
             the VRRP advertisement last received by this virtual
             router."
           REFERENCE "RFC 5798"
           ::= { vrrpv3OperationsEntry 3 }
        
       vrrpv3OperationsPrimaryIpAddr OBJECT-TYPE
           SYNTAX       InetAddress
           MAX-ACCESS   read-create
           STATUS       current
           DESCRIPTION
               "In the case where there is more than one IP
               Address (associated IP addresses) for a given
               'ifIndex', this object is used to specify the IP
               address that will become the
               vrrpv3OperationsMasterIpAddr', should the virtual
               router transition from backup state to master."
           ::= { vrrpv3OperationsEntry 4 }
        
       vrrpv3OperationsVirtualMacAddr OBJECT-TYPE
           SYNTAX       MacAddress
           MAX-ACCESS   read-only
           STATUS       current
           DESCRIPTION
              "The virtual MAC address of the virtual router.
              Although this object can be derived from the
              'vrrpv3OperationsVrId' object, it is defined so that it
              is easily obtainable by a management application and
              can be included in VRRP-related SNMP notifications."
           ::= { vrrpv3OperationsEntry 5 }
        
       vrrpv3OperationsStatus OBJECT-TYPE
           SYNTAX       INTEGER {
               initialize(1),
               backup(2),
               master(3)
           }
           MAX-ACCESS   read-only
           STATUS       current
        
           DESCRIPTION
               "The current state of the virtual router.  This object
               has three defined values:
        
               - 'initialize', which indicates that the
                  virtual router is waiting for a startup event.
        
               - 'backup', which indicates that the virtual router is
                  monitoring the availability of the master router.
        
               - 'master', which indicates that the virtual router
                  is forwarding packets for IP addresses that are
                  associated with this router."
           REFERENCE "RFC 5798"
           ::= { vrrpv3OperationsEntry 6 }
        
       vrrpv3OperationsPriority OBJECT-TYPE
           SYNTAX       Unsigned32 (0..255)
           MAX-ACCESS   read-create
           STATUS       current
           DESCRIPTION
             "This object specifies the priority to be used for the
             virtual router master election process; higher values
             imply higher priority.
        
             A priority of '0', although not settable, is sent by
             the master router to indicate that this router has
        
             ceased to participate in VRRP, and a backup virtual
             router should transition to become a new master.
        
             A priority of 255 is used for the router that owns the
             associated IP address(es) for VRRP over IPv4 and hence
             is not settable.
        
             Setting the values of this object to 0 or 255 should be
             rejected by the agents implementing this MIB module.
             For example, an SNMP agent would return 'badValue(3)'
             when a user tries to set the values 0 or 255 for this
             object."
        
           REFERENCE "RFC 5798, Section 6.1"
           DEFVAL       { 100 }
           ::= { vrrpv3OperationsEntry 7 }
        
       vrrpv3OperationsAddrCount OBJECT-TYPE
           SYNTAX       Integer32 (0..255)
           MAX-ACCESS   read-only
           STATUS       current
           DESCRIPTION
               "The number of IP addresses that are associated with
               this virtual router.  This number is equal to the
               number of rows in the vrrpv3AssociatedAddrTable that
               correspond to a given ifIndex/VRID/IP version."
           REFERENCE "RFC 5798, Section 6.1"
           ::= { vrrpv3OperationsEntry 8 }
        
       vrrpv3OperationsAdvInterval OBJECT-TYPE
           SYNTAX       TimeInterval (1..4095)
           UNITS        "centiseconds"
           MAX-ACCESS   read-create
           STATUS       current
           DESCRIPTION
               "The time interval, in centiseconds, between sending
               advertisement messages.  Only the master router sends
               VRRP advertisements."
           REFERENCE "RFC 5798, Section 6.1"
           DEFVAL       { 100}
           ::= { vrrpv3OperationsEntry 9 }
        
       vrrpv3OperationsPreemptMode OBJECT-TYPE
           SYNTAX       TruthValue
           MAX-ACCESS   read-create
           STATUS       current
           DESCRIPTION
        
             "Controls whether a higher priority virtual router will
             preempt a lower priority master."
           REFERENCE "RFC 5798, Section 6.1"
           DEFVAL       { true }
           ::= { vrrpv3OperationsEntry 10 }
        
       vrrpv3OperationsAcceptMode OBJECT-TYPE
           SYNTAX       TruthValue
           MAX-ACCESS   read-create
           STATUS       current
           DESCRIPTION
              "Controls whether a virtual router in master state
              will accept packets addressed to the address owner's
              IPv6 address as its own if it is not the IPv6 address
              owner.  Default is false(2).
              This object is not relevant for rows representing VRRP
              over IPv4 and should be set to false(2)."
           DEFVAL       { false }
           ::= { vrrpv3OperationsEntry 11 }
        
       vrrpv3OperationsUpTime OBJECT-TYPE
           SYNTAX       TimeTicks
           MAX-ACCESS   read-only
           STATUS       current
           DESCRIPTION
               "This value represents the amount of time, in
               TimeTicks (hundredth of a second), since this virtual
               router (i.e., the 'vrrpv3OperationsStatus')
               transitioned out of 'initialize'."
           REFERENCE "RFC 5798, Section 6.1"
           ::= { vrrpv3OperationsEntry 12 }
        
       vrrpv3OperationsRowStatus OBJECT-TYPE
           SYNTAX       RowStatus
           MAX-ACCESS   read-create
           STATUS       current
           DESCRIPTION
             "The RowStatus variable should be used in accordance to
              installation and removal conventions for conceptual
              rows.
        
              To create a row in this table, a manager sets this
              object to either createAndGo(4) or createAndWait(5).
              Until instances of all corresponding columns are
              appropriately configured, the value of the
              corresponding instance of the
              'vrrpv3OperationsRowStatus' column will be read as
              notReady(3).
        
              In particular, a newly created row cannot be made
              active(1) until (minimally) the corresponding instance
              of vrrpv3OperationsInetAddrType, vrrpv3OperationsVrId,
              and vrrpv3OperationsPrimaryIpAddr has been set, and
              there is at least one active row in the
              'vrrpv3AssociatedIpAddrTable' defining an associated
              IP address.
        
              notInService(2) should be used to administratively
              bring the row down.
        
              A typical order of operation to add a row is:
              1. Create a row in vrrpv3OperationsTable with
              createAndWait(5).
              2. Create one or more corresponding rows in
              vrrpv3AssociatedIpAddrTable.
              3. Populate the vrrpv3OperationsEntry.
              4. Set vrrpv3OperationsRowStatus to active(1).
        
              A typical order of operation to delete an entry is:
              1. Set vrrpv3OperationsRowStatus to notInService(2).
              2. Set the corresponding rows in
              vrrpv3AssociatedIpAddrTable to destroy(6) to delete
              the entry.
              3. Set vrrpv3OperationsRowStatus to destroy(6) to
              delete the entry."
           ::= { vrrpv3OperationsEntry 13 }
        
   --  VRRP Associated Address Table
        
       vrrpv3AssociatedIpAddrTable OBJECT-TYPE
           SYNTAX       SEQUENCE OF Vrrpv3AssociatedIpAddrEntry
           MAX-ACCESS   not-accessible
           STATUS       current
           DESCRIPTION
               "The table of addresses associated with each virtual
                router."
           ::= { vrrpv3Operations 2 }
        
       vrrpv3AssociatedIpAddrEntry OBJECT-TYPE
           SYNTAX       Vrrpv3AssociatedIpAddrEntry
           MAX-ACCESS   not-accessible
           STATUS       current
           DESCRIPTION
              "An entry in the table contains an IP address that is
              associated with a virtual router.  The number of rows
              for a given IP version, VrID, and ifIndex will equal
              the number of IP addresses associated (e.g., backed up)
        
              by the virtual router (equivalent to
              'vrrpv3OperationsIpAddrCount').
        
              Rows in the table cannot be modified unless the value
              of 'vrrpv3OperationsStatus' for the corresponding entry
              in the vrrpv3OperationsTable has transitioned to
              initialize(1).
        
              The information in this table is persistent and when
              written the entity SHOULD save the change to non-
              volatile storage."
        
           INDEX    { ifIndex, vrrpv3OperationsVrId,
                      vrrpv3OperationsInetAddrType,
                      vrrpv3AssociatedIpAddrAddress }
        
           ::= { vrrpv3AssociatedIpAddrTable 1 }
        
       Vrrpv3AssociatedIpAddrEntry ::=
           SEQUENCE {
               vrrpv3AssociatedIpAddrAddress
        
                   InetAddress,
               vrrpv3AssociatedIpAddrRowStatus
                   RowStatus
       }
        
       vrrpv3AssociatedIpAddrAddress OBJECT-TYPE
           SYNTAX       InetAddress (SIZE (0|4|16))
           MAX-ACCESS   not-accessible
           STATUS       current
           DESCRIPTION
               "The assigned IP addresses that a virtual router is
               responsible for backing up.
        
               The IP address type is determined by the value of
               vrrpv3OperationsInetAddrType in the index of this
               row."
           REFERENCE "RFC 5798"
           ::= { vrrpv3AssociatedIpAddrEntry 1 }
        
       vrrpv3AssociatedIpAddrRowStatus OBJECT-TYPE
           SYNTAX       RowStatus
           MAX-ACCESS   read-create
           STATUS       current
           DESCRIPTION
             "The row status variable, used according to
             installation and removal conventions for conceptual
        
             rows.  To create a row in this table, a manager sets
             this object to either createAndGo(4) or
             createAndWait(5).  Setting this object to active(1)
             results in the addition of an associated address for a
             virtual router.  Setting this object to notInService(2)
             results in administratively bringing down the row.
        
             Destroying the entry or setting it to destroy(6)
             removes the associated address from the virtual router.
             The use of other values is implementation-dependent.
        
             Implementations should not allow deletion of the last
             row corresponding to an active row in
             vrrpv3OperationsTable.
        
             Refer to the description of vrrpv3OperationsRowStatus
             for typical row creation and deletion scenarios."
           ::= { vrrpv3AssociatedIpAddrEntry 2 }
        
   --  VRRP Router Statistics
        
       vrrpv3RouterChecksumErrors OBJECT-TYPE
           SYNTAX       Counter64
           MAX-ACCESS   read-only
           STATUS       current
           DESCRIPTION
               "The total number of VRRP packets received with an
               invalid VRRP checksum value.
        
               Discontinuities in the value of this counter can occur
               at re-initialization of the management system, and at
               other times as indicated by the value of
               vrrpv3GlobalStatisticsDiscontinuityTime."
        
           REFERENCE "RFC 5798, Section 5.2.8"
           ::= { vrrpv3Statistics 1 }
        
       vrrpv3RouterVersionErrors OBJECT-TYPE
           SYNTAX       Counter64
           MAX-ACCESS   read-only
           STATUS       current
           DESCRIPTION
               "The total number of VRRP packets received with an
               unknown or unsupported version number.
        
               Discontinuities in the value of this counter can occur
               at re-initialization of the management system, and at
        
               other times as indicated by the value of
               vrrpv3GlobalStatisticsDiscontinuityTime."
        
           REFERENCE "RFC 5798, Section 5.2.1"
           ::= { vrrpv3Statistics 2 }
        
       vrrpv3RouterVrIdErrors OBJECT-TYPE
           SYNTAX       Counter64
           MAX-ACCESS   read-only
          STATUS       current
           DESCRIPTION
               "The total number of VRRP packets received with a
                VRID that is not valid for any virtual router on this
                router.
        
               Discontinuities in the value of this counter can occur
               at re-initialization of the management system, and at
               other times as indicated by the value of
               vrrpv3GlobalStatisticsDiscontinuityTime."
        
           REFERENCE "RFC 5798, Section 5.2.3"
           ::= { vrrpv3Statistics 3 }
        
      vrrpv3GlobalStatisticsDiscontinuityTime OBJECT-TYPE
          SYNTAX     TimeStamp
          MAX-ACCESS read-only
          STATUS     current
          DESCRIPTION
            "The value of sysUpTime on the most recent occasion at
             which one of vrrpv3RouterChecksumErrors,
             vrrpv3RouterVersionErrors, and vrrpv3RouterVrIdErrors
             suffered a discontinuity.
        
             If no such discontinuities have occurred since the last
             re-initialization of the local management subsystem,
             then this object contains a zero value."
        
          ::= { vrrpv3Statistics 4 }
        
   --  VRRP Router Statistics Table
        
       vrrpv3StatisticsTable OBJECT-TYPE
           SYNTAX       SEQUENCE OF Vrrpv3StatisticsEntry
           MAX-ACCESS   not-accessible
           STATUS       current
           DESCRIPTION
               "Table of virtual router statistics."
           ::= { vrrpv3Statistics 5 }
        
       vrrpv3StatisticsEntry OBJECT-TYPE
           SYNTAX       Vrrpv3StatisticsEntry
           MAX-ACCESS   not-accessible
           STATUS       current
           DESCRIPTION
               "An entry in the table containing statistics
               information about a given virtual router."
           AUGMENTS    { vrrpv3OperationsEntry }
           ::= { vrrpv3StatisticsTable 1 }
        
       Vrrpv3StatisticsEntry ::=
           SEQUENCE {
               vrrpv3StatisticsMasterTransitions
                   Counter32,
               vrrpv3StatisticsNewMasterReason
                   INTEGER,
               vrrpv3StatisticsRcvdAdvertisements
                   Counter64,
               vrrpv3StatisticsAdvIntervalErrors
                   Counter64,
               vrrpv3StatisticsIpTtlErrors
                   Counter64,
               vrrpv3StatisticsProtoErrReason
                   INTEGER,
               vrrpv3StatisticsRcvdPriZeroPackets
                   Counter64,
               vrrpv3StatisticsSentPriZeroPackets
                   Counter64,
               vrrpv3StatisticsRcvdInvalidTypePackets
                   Counter64,
               vrrpv3StatisticsAddressListErrors
                   Counter64,
               vrrpv3StatisticsPacketLengthErrors
                   Counter64,
               vrrpv3StatisticsRowDiscontinuityTime
                    TimeStamp,
               vrrpv3StatisticsRefreshRate
                    Unsigned32
           }
        
       vrrpv3StatisticsMasterTransitions OBJECT-TYPE
           SYNTAX       Counter32
           MAX-ACCESS   read-only
           STATUS       current
           DESCRIPTION
               "The total number of times that this virtual router's
               state has transitioned to master state.
        
               Discontinuities in the value of this counter can occur
               at re-initialization of the management system, and at
               other times as indicated by the value of
               vrrpv3StatisticsRowDiscontinuityTime."
           ::= { vrrpv3StatisticsEntry 1 }
        
      vrrpv3StatisticsNewMasterReason OBJECT-TYPE
           SYNTAX        INTEGER {
               notMaster (0),
               priority  (1),
               preempted (2),
               masterNoResponse (3)
           }
           MAX-ACCESS   read-only
           STATUS       current
           DESCRIPTION
              "This indicates the reason for the virtual router to
              transition to master state.  If the virtual router
              never transitioned to master state, the value of this
              object is notMaster(0).  Otherwise, this indicates the
              reason this virtual router transitioned to master
              state the last time.  Used by vrrpv3NewMaster
              notification."
           ::= { vrrpv3StatisticsEntry 2 }
        
       vrrpv3StatisticsRcvdAdvertisements OBJECT-TYPE
           SYNTAX       Counter64
           MAX-ACCESS   read-only
           STATUS       current
           DESCRIPTION
               "The total number of VRRP advertisements received by
               this virtual router.
        
               Discontinuities in the value of this counter can occur
               at re-initialization of the management system, and at
               other times as indicated by the value of
               vrrpv3StatisticsRowDiscontinuityTime."
        
           ::= { vrrpv3StatisticsEntry 3 }
        
       vrrpv3StatisticsAdvIntervalErrors OBJECT-TYPE
           SYNTAX       Counter64
           MAX-ACCESS   read-only
           STATUS       current
           DESCRIPTION
               "The total number of VRRP advertisement packets
               received for which the advertisement interval is
        
               different from the vrrpv3OperationsAdvInterval
               configured on this virtual router.
        
               Discontinuities in the value of this counter can occur
               at re-initialization of the management system, and at
               other times as indicated by the value of
               vrrpv3StatisticsRowDiscontinuityTime."
        
           ::= { vrrpv3StatisticsEntry 4 }
        
       vrrpv3StatisticsIpTtlErrors OBJECT-TYPE
           SYNTAX       Counter64
           MAX-ACCESS   read-only
           STATUS       current
           DESCRIPTION
               "The total number of VRRP packets received by the
               virtual router with IPv4 TTL (for VRRP over IPv4) or
               IPv6 Hop Limit (for VRRP over IPv6) not equal to 255.
        
               Discontinuities in the value of this counter can occur
               at re-initialization of the management system, and at
               other times as indicated by the value of
               vrrpv3StatisticsRowDiscontinuityTime."
           REFERENCE "RFC 5798, Section 5.1.1.3"
           ::= { vrrpv3StatisticsEntry 5 }
        
      vrrpv3StatisticsProtoErrReason OBJECT-TYPE
           SYNTAX        INTEGER {
               noError (0),
               ipTtlError (1),
               versionError  (2),
               checksumError (3),
               vrIdError(4)
           }
           MAX-ACCESS   read-only
           STATUS       current
           DESCRIPTION
               "This indicates the reason for the last protocol
               error.  This SHOULD be set to noError(0) when no
               protocol errors are encountered.  Used by
               vrrpv3ProtoError notification."
           ::= { vrrpv3StatisticsEntry 6 }
        
       vrrpv3StatisticsRcvdPriZeroPackets OBJECT-TYPE
           SYNTAX       Counter64
           MAX-ACCESS   read-only
           STATUS       current
           DESCRIPTION
        
               "The total number of VRRP packets received by the
               virtual router with a priority of '0'.
        
               Discontinuities in the value of this counter can occur
               at re-initialization of the management system, and at
               other times as indicated by the value of
               vrrpv3StatisticsRowDiscontinuityTime."
           REFERENCE "RFC 5798, Section 5.2.4"
           ::= { vrrpv3StatisticsEntry 7 }
        
       vrrpv3StatisticsSentPriZeroPackets OBJECT-TYPE
           SYNTAX       Counter64
           MAX-ACCESS   read-only
           STATUS       current
           DESCRIPTION
               "The total number of VRRP packets sent by the virtual
               router with a priority of '0'.
        
               Discontinuities in the value of this counter can occur
               at re-initialization of the management system, and at
               other times as indicated by the value of
               vrrpv3StatisticsRowDiscontinuityTime."
           REFERENCE "RFC 5798, Section 5.2.4"
           ::= { vrrpv3StatisticsEntry 8 }
        
       vrrpv3StatisticsRcvdInvalidTypePackets OBJECT-TYPE
           SYNTAX       Counter64
           MAX-ACCESS   read-only
           STATUS       current
           DESCRIPTION
               "The number of VRRP packets received by the virtual
               router with an invalid value in the 'type' field.
        
               Discontinuities in the value of this counter can occur
               at re-initialization of the management system, and at
               other times as indicated by the value of
               vrrpv3StatisticsRowDiscontinuityTime."
           ::= { vrrpv3StatisticsEntry 9 }
        
       vrrpv3StatisticsAddressListErrors OBJECT-TYPE
           SYNTAX       Counter64
           MAX-ACCESS   read-only
           STATUS       current
           DESCRIPTION
               "The total number of packets received for which the
               address list does not match the locally configured
               list for the virtual router.
        
               Discontinuities in the value of this counter can occur
               at re-initialization of the management system, and at
               other times as indicated by the value of
               vrrpv3StatisticsRowDiscontinuityTime."
           ::= { vrrpv3StatisticsEntry 10 }
        
       vrrpv3StatisticsPacketLengthErrors OBJECT-TYPE
           SYNTAX       Counter64
           MAX-ACCESS   read-only
           STATUS       current
           DESCRIPTION
               "The total number of packets received with a packet
               length less than the length of the VRRP header.
        
               Discontinuities in the value of this counter can occur
               at re-initialization of the management system, and at
               other times as indicated by the value of
               vrrpv3StatisticsRowDiscontinuityTime."
           ::= { vrrpv3StatisticsEntry 11 }
        
      vrrpv3StatisticsRowDiscontinuityTime OBJECT-TYPE
          SYNTAX     TimeStamp
          MAX-ACCESS read-only
          STATUS     current
          DESCRIPTION
             "The value of sysUpTime on the most recent occasion at
             which any one or more of this entry's counters
             suffered a discontinuity.
        
             If no such discontinuities have occurred since the last
             re-initialization of the local management subsystem,
             then this object contains a zero value."
          ::= { vrrpv3StatisticsEntry 12 }
        
      vrrpv3StatisticsRefreshRate OBJECT-TYPE
          SYNTAX     Unsigned32
          UNITS "milliseconds"
          MAX-ACCESS read-only
          STATUS     current
          DESCRIPTION
            "The minimum reasonable polling interval for this entry.
             This object provides an indication of the minimum
             amount of time required to update the counters in this
             entry."
          ::= { vrrpv3StatisticsEntry 13 }
        
   --   Notification Definitions
   --   Notifications may be controlled using SNMP-NOTIFICATION-MIB
        
       vrrpv3NewMaster NOTIFICATION-TYPE
           OBJECTS      {
                          vrrpv3OperationsMasterIpAddr,
                          vrrpv3StatisticsNewMasterReason
                        }
           STATUS       current
           DESCRIPTION
               "The newMaster notification indicates that the sending
               agent has transitioned to master state."
           ::= { vrrpv3Notifications 1 }
        
       vrrpv3ProtoError NOTIFICATION-TYPE
           OBJECTS      {
                          vrrpv3StatisticsProtoErrReason
                        }
           STATUS       current
           DESCRIPTION
               "The notification indicates that the sending agent has
               encountered the protocol error indicated by
               vrrpv3StatisticsProtoErrReason."
           ::= { vrrpv3Notifications 2 }
        
   --  Conformance Information
        
    vrrpv3Compliances  OBJECT IDENTIFIER ::= { vrrpv3Conformance 1 }
    vrrpv3Groups       OBJECT IDENTIFIER ::= { vrrpv3Conformance 2 }
        
   -- Compliance Statements
        
       vrrpv3FullCompliance MODULE-COMPLIANCE
           STATUS current
           DESCRIPTION
              "The compliance statement"
           MODULE -- this module
           MANDATORY-GROUPS  {
               vrrpv3OperationsGroup,
               vrrpv3StatisticsGroup,
               vrrpv3InfoGroup,
               vrrpv3NotificationsGroup
           }
           OBJECT        vrrpv3OperationsPriority
           WRITE-SYNTAX  Unsigned32 (1..254)
           DESCRIPTION  "Setable values are from 1 to 254."
           ::= { vrrpv3Compliances 1 }
        
       vrrpv3ReadOnlyCompliance MODULE-COMPLIANCE
           STATUS current
           DESCRIPTION
        
              "When this MIB module is implemented without support
              for read-create (i.e., in read-only mode), then such
              an implementation can claim read-only compliance.
              Such a device can then be monitored, but cannot be
              configured with this MIB."
        
           MODULE -- this module
           MANDATORY-GROUPS  {
               vrrpv3OperationsGroup,
               vrrpv3StatisticsGroup,
               vrrpv3StatisticsDiscontinuityGroup,
               vrrpv3InfoGroup,
               vrrpv3NotificationsGroup
           }
        
           OBJECT        vrrpv3OperationsPriority
           MIN-ACCESS    read-only
           DESCRIPTION  "Write access is not required."
        
           OBJECT        vrrpv3OperationsPrimaryIpAddr
           MIN-ACCESS    read-only
           DESCRIPTION  "Write access is not required."
           OBJECT        vrrpv3OperationsAdvInterval
           MIN-ACCESS    read-only
           DESCRIPTION  "Write access is not required."
        
           OBJECT        vrrpv3OperationsPreemptMode
           MIN-ACCESS    read-only
           DESCRIPTION  "Write access is not required."
        
           OBJECT        vrrpv3OperationsAcceptMode
           MIN-ACCESS    read-only
           DESCRIPTION  "Write access is not required."
        
           OBJECT        vrrpv3OperationsRowStatus
           MIN-ACCESS    read-only
           DESCRIPTION  "Write access is not required."
        
           OBJECT        vrrpv3AssociatedIpAddrRowStatus
           MIN-ACCESS    read-only
           DESCRIPTION  "Write access is not required."
        
           ::= { vrrpv3Compliances 2 }
        
   -- Conformance Groups
        
       vrrpv3OperationsGroup   OBJECT-GROUP
           OBJECTS  {
        
               vrrpv3OperationsVirtualMacAddr,
               vrrpv3OperationsStatus,
               vrrpv3OperationsPriority,
               vrrpv3OperationsMasterIpAddr,
               vrrpv3OperationsAdvInterval,
               vrrpv3OperationsPreemptMode,
               vrrpv3OperationsAcceptMode,
               vrrpv3OperationsUpTime,
               vrrpv3OperationsRowStatus,
               vrrpv3OperationsAddrCount,
               vrrpv3OperationsPrimaryIpAddr,
               vrrpv3AssociatedIpAddrRowStatus
               }
           STATUS current
           DESCRIPTION
              "Conformance group for VRRPv3 operations."
           ::= { vrrpv3Groups 1 }
        
       vrrpv3StatisticsGroup  OBJECT-GROUP
           OBJECTS  {
               vrrpv3RouterChecksumErrors,
               vrrpv3RouterVersionErrors,
               vrrpv3RouterVrIdErrors,
               vrrpv3StatisticsMasterTransitions,
               vrrpv3StatisticsNewMasterReason,
               vrrpv3StatisticsRcvdAdvertisements,
               vrrpv3StatisticsAdvIntervalErrors,
               vrrpv3StatisticsRcvdPriZeroPackets,
               vrrpv3StatisticsSentPriZeroPackets,
               vrrpv3StatisticsRcvdInvalidTypePackets,
               vrrpv3StatisticsIpTtlErrors,
               vrrpv3StatisticsProtoErrReason,
               vrrpv3StatisticsAddressListErrors,
               vrrpv3StatisticsPacketLengthErrors,
               vrrpv3StatisticsRowDiscontinuityTime,
               vrrpv3StatisticsRefreshRate
               }
           STATUS current
           DESCRIPTION
              "Conformance group for VRRPv3 statistics."
           ::= { vrrpv3Groups 2 }
        
       vrrpv3StatisticsDiscontinuityGroup  OBJECT-GROUP
           OBJECTS  {
               vrrpv3GlobalStatisticsDiscontinuityTime
               }
           STATUS current
           DESCRIPTION
        
              "Objects providing information about counter
               discontinuities."
           ::= { vrrpv3Groups 3 }
        
       vrrpv3InfoGroup  OBJECT-GROUP
           OBJECTS  {
               vrrpv3StatisticsProtoErrReason,
               vrrpv3StatisticsNewMasterReason
               }
           STATUS current
           DESCRIPTION
              "Conformance group for objects contained in VRRPv3
               notifications."
           ::= { vrrpv3Groups 4 }
        
       vrrpv3NotificationsGroup NOTIFICATION-GROUP
           NOTIFICATIONS {
               vrrpv3NewMaster,
               vrrpv3ProtoError
               }
           STATUS current
           DESCRIPTION
              "The VRRP MIB Notification Group."
           ::= { vrrpv3Groups 5 }
        
   END
        

11. Security Considerations

11. セキュリティに関する考慮事項

There are a number of management objects defined in this MIB module with a MAX-ACCESS clause of read-write and/or read-create. Such objects may be considered sensitive or vulnerable in some network environments. The support for SET operations in a non-secure environment without proper protection can have a negative effect on network operations. These are the tables and objects and their sensitivity/vulnerability:

このMIBモジュールには、読み取りワイトおよび/またはread-Createの最大アクセス句を持つ多くの管理オブジェクトが定義されています。このようなオブジェクトは、一部のネットワーク環境で敏感または脆弱と見なされる場合があります。適切な保護なしの非セクター環境でのセット操作のサポートは、ネットワーク操作に悪影響を与える可能性があります。これらはテーブルとオブジェクトであり、その感度/脆弱性です。

The objects vrrpv3OperationsPriority, vrrpv3OperationsPrimaryIpAddr, vrrpv3OperationsAdvInterval, vrrpv3OperationsPreemptMode, vrrpv3OperationsAcceptMode, vrrpv3OperationsRowStatus, and vrrpv3AssociatedIpAddrRowStatus possess the read-create attribute. Manipulation of these objects is capable of affecting the operation of a virtual router.

オブジェクトvrrpv3OperationsPriority、vrrpv3OperationsPrimaryIpAddr、vrrpv3OperationsAdvInterval、vrrpv3OperationsPreemptMode、vrrpv3OperationsAcceptMode、vrrpv3OperationsRowStatus、およびvrpv3associateideiatedipaddrowstatusのvrrpv3associetieated-ceptmode。これらのオブジェクトの操作は、仮想ルーターの動作に影響を与えることができます。

Examples of how these objects could adversely affect the operation of a virtual router include:

これらのオブジェクトが仮想ルーターの動作に悪影響を与える可能性のある例は、次のものを次のとおりです。

o An unauthorized change to vrrpv3OperationsPriority can affect the priority used in master election, resulting in this router either becoming master when it should not, or in some other router being elected by preference. While this will disrupt the operator's plans, it will only replicate the unfortunate failure of multiple routers, and any router that does become master will be capable of filling that role.

o vrrpv3OperationsPriorityの不正な変更は、マスター選挙で使用される優先度に影響を与える可能性があり、このルーターは、そうでない場合にマスターになるか、好みによって選出される他のルーターのいずれかになります。これはオペレーターの計画を混乱させますが、複数のルーターの不幸な障害のみを複製するだけで、マスターになるルーターはその役割を埋めることができます。

o Modification of vrrpv3OperationsPrimaryIpAddr would cause the configured router to take on an incorrect IP address if it becomes master, which would be potentially very disruptive to the network operation.

o vrrpv3OperationsPrimaryIpAddrの変更により、構成されたルーターがマスターになった場合、誤ったIPアドレスを採用します。これは、ネットワーク操作を非常に破壊する可能性があります。

o A malicious change to vrrpv3OperationsAdvInterval could either result in the configured router flooding the network with advertisements when it becomes master, or the new master not advertising frequently enough such that some routers do not learn about the new master.

o VRRPV3OPERATIONADVINTERVALの悪意のある変更により、構成されたルーターがマスターになったときにネットワークに広告をあふれさせるか、新しいマスターが新しいマスターについて学習しないように頻繁に広告しないようにする可能性があります。

o vrrpv3OperationsPreemptMode controls whether this router will preempt another master router. Setting it inappropriately will at worse cause one router to be master against the operator's plans, but that router will still be qualified to operate as a master.

o vrrpv3OperationsPreemptModeこのルーターが別のマスタールーターを先取りするかどうかを制御します。不適切に設定すると、1つのルーターがオペレーターの計画に反対するマスターになりますが、そのルーターはマスターとして動作する資格があります。

o Setting the vrrpv3OperationsAcceptMode could prevent an IPv6-capable VRRP router from accepting packets addressed to the address owner's IPv6 address as its own even if it is not the IPv6 address owner. Although the default for this object is false(2), unauthorized setting of this object to false might restrict the function of some parts of the network.

o vrrpv3OperationsAcceptModeを設定すると、IPv6対応のVRRPルーターが、IPv6アドレスの所有者でなくても、アドレス所有者のIPv6アドレスにアドレス指定されたパケットを独自のものとして受け入れることができなくなります。このオブジェクトのデフォルトはfalse(2)ですが、このオブジェクトの不正な設定がfalseになると、ネットワークの一部の機能が制限される場合があります。

o The vrrpv3OperationsRowStatus object that could be used to disable a virtual router. While there are other columns that, if changed, could disrupt operations, they cannot be changed without first changing the RowStatus object.

o 仮想ルーターの無効化に使用できるvrrpv3OperationsRowStatusオブジェクト。変更された場合、操作を混乱させる可能性のある他の列がありますが、最初にRowStatusオブジェクトを変更せずに変更することはできません。

SNMP versions prior to SNMPv3 did not include adequate security. Even if the network itself is secure (for example by using IPsec), there is no control as to who on the secure network is allowed to access and GET/SET (read/change/create/delete) the objects in this MIB module.

SNMPV3以前のSNMPバージョンには、適切なセキュリティが含まれていませんでした。ネットワーク自体が(たとえば、IPSECを使用して)安全である場合でも、このMIBモジュールのオブジェクトにセキュアネットワークのアクセスと取得/設定(読み取り/変更/作成/削除)が許可されている人については制御できません。

Implementations MUST provide the security features described by the SNMPv3 framework (see [RFC3410]), including full support for authentication and privacy via the User-based Security Model (USM) [RFC3414] with the AES cipher algorithm [RFC3826]. Implementations MAY also provide support for the Transport Security Model (TSM)

実装は、AES暗号アルゴリズム[RFC3826]を使用して、ユーザーベースのセキュリティモデル(USM)[RFC3414]を介した認証とプライバシーの完全なサポートを含む、SNMPV3フレームワーク([RFC3410]を参照)で説明されているセキュリティ機能を提供しなければなりません (MUST)。実装は、輸送セキュリティモデル(TSM)のサポートも提供する場合があります (MAY)

[RFC5591] in combination with a secure transport such as SSH [RFC5592] or TLS/DTLS [RFC6353].

[RFC5591] SSH [RFC5592]やTLS/DTLS [RFC6353]などの安全な輸送と組み合わせて。

Further, deployment of SNMP versions prior to SNMPv3 is NOT RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to enable cryptographic security. It is then a customer/operator responsibility to ensure that the SNMP entity giving access to an instance of this MIB module is properly configured to give access to the objects only to those principals (users) that have legitimate rights to indeed GET or SET (change/create/delete) them.

さらに、SNMPv3より前のSNMPバージョンは導入することは推奨されません (NOT RECOMMENDED)。SNMPv3を導入し、暗号によるセキュリティ機能を有効にすることが推奨されます (RECOMMENDED)。このMIBモジュールのインスタンスへのアクセスを提供するSNMPエンティティを適切に設定し、オブジェクトをGETまたはSET(変更、作成、削除)する正当な権限を持つプリンシパル(ユーザー)だけにアクセスを許可することは、顧客または運用者の責任です。

12. IANA Considerations

12. IANAの考慮事項

The MIB module in this document uses the following IANA-assigned OBJECT IDENTIFIER values recorded in the SMI Numbers registry:

このドキュメントのMIBモジュールは、SMI番号レジストリに記録された次のIANAによって割り当てられたオブジェクト識別子値を使用します。

        Descriptor        OBJECT IDENTIFIER value
        ----------        -----------------------
        

vrrpv3MIB { mib-2 207 vrrpv3MIB VRRPV3-MIB }

vrrpv3MIB {mib-2 207 vrrpv3MIB vrrpv3-mib}

This document obsoletes RFC 2787. Therefore, IANA has deprecated value 68 under 'mib-2', which is assigned to VRRP-MIB.

このドキュメントはRFC 2787を廃止します。したがって、IANAはvrrp-mibに割り当てられている「MIB-2」の下で値68を非推奨68にしています。

13. Normative References

13. 引用文献

[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997.

[RFC2119] Bradner, S.、「要件レベルを示すためにRFCで使用するためのキーワード」、BCP 14、RFC 2119、1997年3月。

[RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Structure of Management Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.

[RFC2578] McCloghrie, K., Perkins, D., and J. Schoenwaelder、「管理情報の構造バージョン2(SMIV2)」、STD 58、RFC 2578、1999年4月。

[RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999.

[RFC2579] McCloghrie, K., Perkins, D., and J. Schoenwaelder、「SMIV2のテキストコンベンション」、STD 58、RFC 2579、1999年4月。

[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999.

[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder、「SMIV2の適合ステートメント」、STD 58、RFC 2580、1999年4月。

[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB", RFC 2863, June 2000.

[RFC2863] McCloghrie, K. and F. Kastenholz、「The Interfaces Group MIB」、RFC 2863、2000年6月。

[RFC3413] Levi, D., Meyer, P., and B. Stewart, "Simple Network Management Protocol (SNMP) Applications", STD 62, RFC 3413, December 2002.

[RFC3413] Levi, D., Meyer, P., and B. Stewart、「Simple Network Management Protocol(SNMP)アプリケーション」、STD 62、RFC 3413、2002年12月。

[RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. Schoenwaelder, "Textual Conventions for Internet Network Addresses", RFC 4001, February 2005.

[RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. Schoenwaelder、「インターネットネットワークアドレスのテキストコンベンション」、RFC 4001、2005年2月。

[RFC5798] Nadas, S., Ed., "Virtual Router Redundancy Protocol (VRRP) Version 3 for IPv4 and IPv6", RFC 5798, March 2010.

[RFC5798] Nadas, S., Ed.、「IPv4およびIPv6用の仮想ルーター冗長プロトコル(VRRP)バージョン3」、RFC 5798、2010年3月。

14. Informative References

14. 参考引用

[RFC2338] Knight, S., Weaver, D., Whipple, D., Hinden, R., Mitzel, D., Hunt, P., Higginson, P., Shand, M., and A. Lindem, "Virtual Router Redundancy Protocol", RFC 2338, April 1998.

[RFC2338] Knight, S., Weaver, D., Whipple, D., Hinden, R., Mitzel, D., Hunt, P., Higginson, P., Shand, M., and A. Lindem, "Virtualルーター冗長プロトコル」、RFC 2338、1998年4月。

[RFC2787] Jewell, B. and D. Chuang, "Definitions of Managed Objects for the Virtual Router Redundancy Protocol", RFC 2787, March 2000.

[RFC2787] Jewell, B. and D. Chuang、「仮想ルーター冗長プロトコルの管理されたオブジェクトの定義」、RFC 2787、2000年3月。

[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction and Applicability Statements for Internet-Standard Management Framework", RFC 3410, December 2002.

[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart、「インターネット標準管理フレームワークの紹介と適用声明」、RFC 3410、2002年12月。

[RFC3414] Blumenthal, U. and B. Wijnen, "User-based Security Model (USM) for version 3 of the Simple Network Management Protocol (SNMPv3)", STD 62, RFC 3414, December 2002.

[RFC3414] Blumenthal, U. and B. Wijnen、「Simple Network Management Protocol(SNMPV3)のバージョン3のユーザーベースのセキュリティモデル(USM)」、STD 62、RFC 3414、2002年12月。

[RFC3826] Blumenthal, U., Maino, F., and K. McCloghrie, "The Advanced Encryption Standard (AES) Cipher Algorithm in the SNMP User-based Security Model", RFC 3826, June 2004.

[RFC3826] Blumenthal, U., Maino, F., and K. McCloghrie、「SNMPユーザーベースのセキュリティモデルにおける高度な暗号化標準(AES)暗号アルゴリズム」、RFC 3826、2004年6月。

[RFC5591] Harrington, D. and W. Hardaker, "Transport Security Model for the Simple Network Management Protocol (SNMP)", RFC 5591, June 2009.

[RFC5591] Harrington, D. and W. Hardaker、「Simple Network Management Protocol(SNMP)の輸送セキュリティモデル」、RFC 5591、2009年6月。

[RFC5592] Harrington, D., Salowey, J., and W. Hardaker, "Secure Shell Transport Model for the Simple Network Management Protocol (SNMP)", RFC 5592, June 2009.

[RFC5592] Harrington, D., Salowey, J., and W. Hardaker、「Secure Shell Transport Model for the Simple Network Management Protocol(SNMP)」、RFC 5592、2009年6月。

[RFC6353] Hardaker, W., "Transport Layer Security (TLS) Transport Model for the Simple Network Management Protocol (SNMP)", RFC 6353, July 2011.

[RFC6353] Hardaker, W.、「シンプルネットワーク管理プロトコル(SNMP)の輸送層セキュリティ(TLS)輸送モデル」、RFC 6353、2011年7月。

15. Acknowledgments

15. 謝辞

Kripakaran Karlekar and Brain Jewell helped in design and initial drafts of this specification. This specification is based on RFC 2787. The authors of RFC 2787 are Brian Jewell and David Chuang. The author would also like to thank Bert Wijnen, Dave Thaler, Joan Cucchiara, Mukesh Gupta, Steve Bates, Adrian Farrel, Ben Campbell and Joel M. Halpern for taking time to review the document and provide valuable guidance.

Kripakaran KarlekarとBrain Jewellは、この仕様の設計と初期ドラフトを支援しました。この仕様はRFC 2787に基づいています。RFC2787の著者は、ブライアンジュエルとデビッドチュアンです。著者はまた、Bert Wijnen、Dave Thaler、Joan Cucchiara、Mukesh Gupta、Steve Bates、Adrian Farrel、Ben Campbell、Joel M. Halpernに時間を割いて、貴重なガイダンスを提供してくれたことにも感謝したいと思います。

Author's Address

著者の連絡先

Srinivas Kalyan Tata Nokia 313 Fairchild Dr. Mountain View, CA 94043 EMail: Tata_kalyan@yahoo.com

Srinivas Kalyan Tata Nokia 313 Fairchild Dr. Mountain View、CA 94043メール:tata_kalyan@yahoo.com