Internet Engineering Task Force (IETF) K. Tata
Request for Comments: 6527 Nokia
Obsoletes: 2787 March 2012
Category: Standards Track
ISSN: 2070-1721
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.
本规范定义了管理信息库（MIB）的一部分，用于基于简单网络管理协议（SNMP）的网络管理。特别是，它定义了用于配置、监视和控制路由器的对象，这些路由器采用RFC 5798中定义的IPv4和IPv6虚拟路由器冗余协议版本3（VRRPv3）。本备忘录废除RFC 2787。
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.
有关本文件当前状态、任何勘误表以及如何提供反馈的信息，请访问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.
版权所有（c）2012 IETF信托基金和确定为文件作者的人员。版权所有。
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信托有关IETF文件的法律规定的约束(http://trustee.ietf.org/license-info)自本文件出版之日起生效。请仔细阅读这些文件，因为它们描述了您对本文件的权利和限制。从本文件中提取的代码组件必须包括信托法律条款第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标准流程之外修改本文件，也不得在IETF标准流程之外创建其衍生作品，除了将其格式化以RFC形式发布或将其翻译成英语以外的其他语言。
Table of Contents
目录
1. The Internet-Standard Management Framework ......................2
2. Introduction ....................................................3
3. Terminology .....................................................3
4. Relationship to RFC 2787 ........................................3
5. Relation to Interface Group (IF-MIB) ............................3
6. Multi-Stack Implementations .....................................3
7. Interpretation of RFC 5798 ......................................3
8. VRRP MIB Structure and Design ...................................4
9. VRRP Multi-Stack Scenario .......................................4
10. Definitions ....................................................7
11. Security Considerations .......................................27
12. IANA Considerations ...........................................29
13. Normative References ..........................................29
14. Informative References ........................................30
15. Acknowledgments ...............................................31
1. The Internet-Standard Management Framework ......................2
2. Introduction ....................................................3
3. Terminology .....................................................3
4. Relationship to RFC 2787 ........................................3
5. Relation to Interface Group (IF-MIB) ............................3
6. Multi-Stack Implementations .....................................3
7. Interpretation of RFC 5798 ......................................3
8. VRRP MIB Structure and Design ...................................4
9. VRRP Multi-Stack Scenario .......................................4
10. Definitions ....................................................7
11. Security Considerations .......................................27
12. IANA Considerations ...........................................29
13. Normative References ..........................................29
14. Informative References ........................................30
15. Acknowledgments ...............................................31
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）中定义的机制定义的。本备忘录规定了符合SMIv2的MIB模块，如STD 58、RFC 2578[RFC2578]、STD 58、RFC 2579[RFC2579]和STD 58、RFC 2580[RFC2580]所述。
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].
本规范定义了MIB的一部分，用于基于SNMP的网络管理。特别是，它定义了用于配置、监视和控制路由器的对象，这些路由器采用RFC 5798[RFC5798]中定义的IPv4和IPv6虚拟路由器冗余协议版本3（VRRPv3）。
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].
本文件中的关键词“必须”、“不得”、“必需”、“应”、“不应”、“建议”、“不建议”、“可”和“可选”应按照RFC 2119[RFC2119]中的说明进行解释。
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约定。
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].
由于路由器可以在一个或多个接口上参与VRRP，“ifIndex”用作VRRP MIB中定义的表的索引。此MIB模块从IF-MIB导入ifIndex。目前，IF-MIB的最新版本来自RFC 2863[RFC2863]。
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用于唯一标识多堆栈实现中的行。
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虚拟路由器被视为两个独立的逻辑实体，并在vrrpv3OperationsTable中表示为两个独立的条目。这是因为[RFC5798]中的协议在多堆栈场景中的行为未定义。
This MIB module contains three tables:
此MIB模块包含三个表：
(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) VRRPV3统计表包含VRRP路由器的操作统计信息。
(3) The vrrpv3AssociatedIpAddrTable contains the addresses of the virtual router(s) that a given VRRP router is backing up.
(3) VRRPV3AssociatedIPAddressTable包含给定VRRP路由器正在备份的虚拟路由器的地址。
Tables are indexed on ifIndex, VRID, and the IP version to uniquely identify a VRRP router.
表在ifIndex、VRID和IP版本上建立索引，以唯一标识VRRP路由器。
Notifications in this MIB module are controlled using the mechanisms defined in [RFC3413].
此MIB模块中的通知使用[RFC3413]中定义的机制进行控制。
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:
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
if=IfIndex AddrType=VRRPV3操作INETADDRTYPE VrId=VRRPV3操作VrId状态=VRRPV3操作状态优先级=VRRPV3操作优先级IpAddr=VRRPV3操作主IpAddr
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.
下图显示了一个具有两个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 |
+----+ +----+ +----+ +----+ +----+ +----+ +----+ +----+
+------+ +------+
| 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": -----
----- MIB Tables For VRRP Router "VR1": -----
vrrpv3OperationsTable
-------------------
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 | |
+----+------+--------+-------+-------+------+--------+
| 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
-------------------------
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 |
+----+------+----------+------+---------+
| 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": -----
----- MIB Tables For VRRP Router "VR2": -----
vrrpv3OperationsTable
-------------------
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 | |
+----+------+--------+-------+-------+------+--------+
| 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
-------------------------
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 |
+----+------+--------+------+---------+
| 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=主；B=备份。在vrrpv3OperationsTable中，“优先级”为255表示各路由器拥有IP地址，例如，该IP地址是路由器的本机地址（即“IP地址所有者”）。
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
VRRPV3-MIB DEFINITIONS ::= BEGIN
IMPORTS MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, Counter32, Integer32, mib-2, Unsigned32, Counter64, TimeTicks FROM SNMPv2-SMI -- RFC2578
从SNMPv2 SMI--RFC2578导入模块标识、对象类型、通知类型、计数器32、整数32、mib-2、无符号32、计数器64、时间刻度
TEXTUAL-CONVENTION, RowStatus, MacAddress, TruthValue, TimeStamp, TimeInterval FROM SNMPv2-TC -- RFC2579
文本约定、行状态、MacAddress、TruthValue、时间戳、SNMPv2 TC的时间间隔——RFC2579
MODULE-COMPLIANCE, OBJECT-GROUP, NOTIFICATION-GROUP FROM SNMPv2-CONF -- RFC2580
来自SNMPv2 CONF的MODULE-COMPLIANCE、OBJECT-GROUP、NOTIFICATION-GROUP——RFC2580
ifIndex FROM IF-MIB -- RFC2863 InetAddressType, InetAddress
来自IF-MIB的ifIndex——RFC2863 InetAddressType，InetAddress
FROM INET-ADDRESS-MIB; -- RFC4001
从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
vrrpv3MIB模块标识最后一次更新“201202130000Z”--2012年2月13日组织“IETF VRRP工作组”联系方式工作组电子邮件：vrrp@ietf.org
Editor: Kalyan Tata Nokia 313 Fairchild Dr, Mountain View, CA 94043 Tata_kalyan@yahoo.com"
编辑：Kalyan Tata诺基亚313 Fairchild博士，加利福尼亚州山景城，塔塔94043_kalyan@yahoo.com"
DESCRIPTION "This MIB describes objects used for managing Virtual Router Redundancy Protocol version 3 (VRRPv3).
DESCRIPTION“此MIB描述用于管理虚拟路由器冗余协议版本3（VRRPv3）的对象。
Copyright (c) 2012 IETF Trust and the persons identified as authors of the code. All rights reserved.
版权所有（c）2012 IETF信托基金和被确定为代码作者的人员。版权所有。
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).
根据IETF信托有关IETF文件的法律规定第4.c节规定的简化BSD许可证中包含的许可条款，允许以源代码和二进制格式重新分发和使用，无论是否修改(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."
此版本的MIB模块是RFC 6527的一部分。有关完整的法律通知，请参见RFC。”
REVISION "201202120000Z" -- Feb 13, 2012 DESCRIPTION "Initial version as published in RFC 6527."
修订版“201202120000Z”-2012年2月13日描述“RFC 6527中发布的初始版本”
::= { mib-2 207 }
::= { mib-2 207 }
-- Textual Conventions
--文本约定
Vrrpv3VrIdTC ::= TEXTUAL-CONVENTION
DISPLAY-HINT "d"
STATUS current
DESCRIPTION
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)
RFC 5798中注明为（VRID）的虚拟路由器标识符的值。该值与接口索引（ifIndex）和IP版本一起，用于唯一标识给定VRRP路由器上的虚拟路由器。参考“RFC 5798（第3节和第5.2.3节）”语法整数32（1..255）
-- VRRPv3 MIB Groups
--VRRPv3 MIB组
vrrpv3Notifications OBJECT IDENTIFIER ::= { vrrpv3MIB 0 }
vrrpv3Objects OBJECT IDENTIFIER ::= { vrrpv3MIB 1 }
vrrpv3Conformance OBJECT IDENTIFIER ::= { vrrpv3MIB 2 }
vrrpv3Notifications OBJECT IDENTIFIER ::= { vrrpv3MIB 0 }
vrrpv3Objects OBJECT IDENTIFIER ::= { vrrpv3MIB 1 }
vrrpv3Conformance OBJECT IDENTIFIER ::= { vrrpv3MIB 2 }
-- VRRPv3 MIB Objects
--VRRPv3 MIB对象
vrrpv3Operations OBJECT IDENTIFIER ::= { vrrpv3Objects 1 }
vrrpv3Statistics OBJECT IDENTIFIER ::= { vrrpv3Objects 2 }
vrrpv3Operations OBJECT IDENTIFIER ::= { vrrpv3Objects 1 }
vrrpv3Statistics OBJECT IDENTIFIER ::= { vrrpv3Objects 2 }
-- VRRPv3 Operations Table
--VRRPv3操作表
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."
vrrpv3OperationsTable Vrrpv3OperationsEntry的对象类型语法序列MAX-ACCESS不可访问状态当前描述“VRRP路由器的统一操作表，该表由“Vrrpv3OperationsEntry”项的序列（即一个或多个概念行）组成，每个项描述虚拟路由器的操作特性。”
::= { vrrpv3Operations 1 }
::= { 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.
vrrpv3OperationsEntry对象类型语法vrrpv3OperationsEntry MAX-ACCESS不可访问状态当前描述“vrrpv3OperationsTable中的一个条目，包含虚拟路由器的操作特性。在VRRP路由器上，给定的虚拟路由器由ifIndex、VRID和IP版本的组合标识。iIndex表示路由器的接口。
A row must be created with vrrpv3OperationsStatus set to initialize(1) and cannot transition to backup(2) or master(3) until
必须在vrrpv3OperationsStatus设置为initialize（1）的情况下创建一行，并且在以下情况下才能转换为backup（2）或master（3）
vrrpv3OperationsRowStatus is transitioned to active(1).
VRRPV3操作箭头状态转换为活动（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 }
INDEX { ifIndex, vrrpv3OperationsVrId,
vrrpv3OperationsInetAddrType
}
::= { vrrpv3OperationsTable 1 }
Vrrpv3OperationsEntry ::=
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
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 }
"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.
vrrpv3OperationsInetAddrType对象类型语法InetAddressType MAX-ACCESS不可访问状态当前描述“Vrrpv3OperationsEntry和Vrrpv3AssociatedIpAddrEntry的IP地址类型。此值确定vrrpv3OperationsMasterIpAddr、VRRPV3OperationsPrimaryPaddr和vrrpv3AssociatedIpAddrAddress的类型。
ipv4(1) and ipv6(2) are the only two values supported
in this MIB module."
REFERENCE "RFC 4001"
::= { vrrpv3OperationsEntry 2 }
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 }
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 }
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 }
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
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:
DESCRIPTION“虚拟路由器的当前状态。此对象有三个定义值：
- '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 }
- '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.
vrrpv3OperationsPriority对象类型语法Unsigned32（0..255）MAX-ACCESS read create STATUS current DESCRIPTION“此对象指定用于虚拟路由器主选择过程的优先级；值越高表示优先级越高。
A priority of '0', although not settable, is sent by the master router to indicate that this router has
“0”的优先级虽然不可设置，但由主路由器发送，以指示此路由器具有
ceased to participate in VRRP, and a backup virtual router should transition to become a new master.
停止参与VRRP，备份虚拟路由器应过渡为新主机。
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.
在IPv4上拥有VRRP相关IP地址的路由器使用255优先级，因此不可设置。
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."
实现此MIB模块的代理应拒绝将此对象的值设置为0或255。例如，当用户尝试为此对象设置值0或255时，SNMP代理将返回“badValue（3）”
REFERENCE "RFC 5798, Section 6.1"
DEFVAL { 100 }
::= { vrrpv3OperationsEntry 7 }
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 }
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 }
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
vrrpv3OperationsPreemptMode对象类型语法TruthValue MAX-ACCESS读取创建状态当前描述
"Controls whether a higher priority virtual router will
preempt a lower priority master."
REFERENCE "RFC 5798, Section 6.1"
DEFVAL { true }
::= { vrrpv3OperationsEntry 10 }
"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 }
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 }
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.
VRRPV3操作RowStatus对象类型语法RowStatus MAX-ACCESS read create STATUS current DESCRIPTION“应根据概念行的安装和删除约定使用RowStatus变量。
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).
要在此表中创建行，管理器将此对象设置为createAndGo（4）或createAndWait（5）。在正确配置所有相应列的实例之前，“vrrpv3OperationsRowStatus”列的相应实例的值将被读取为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.
特别是，在（至少）设置了vrrpv3OperationsInetAddrType、vrrpv3OperationsVrId和VRRPV3OperationsPrimaryPaddr的对应实例，并且“VRRPV3AssociatedIPAddressable”中至少有一个活动行定义了关联的IP地址之前，新创建的行不能被激活（1）。
notInService(2) should be used to administratively bring the row down.
notInService（2）应用于管理性地降低行。
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).
添加行的典型操作顺序为：1。使用createAndWait（5）在vrrpv3OperationsTable中创建一行。2.在VRRPV3AssociatedIPAddressTable中创建一个或多个对应行。3.填充vrrpv3OperationsEntry。4.将VRRPV3操作箭头状态设置为激活（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 }
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
--VRRP关联地址表
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 }
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)
VRRPV3AssociatedIPAddressEntry对象类型语法VRRPV3AssociatedIPAddressEntry MAX-ACCESS不可访问状态当前描述“表中的条目包含与虚拟路由器关联的IP地址。给定IP版本、VrID和ifIndex的行数将等于关联（例如备份）的IP地址数
by the virtual router (equivalent to 'vrrpv3OperationsIpAddrCount').
通过虚拟路由器（相当于“VRRPV3OperationsIPAddressCount”）。
Rows in the table cannot be modified unless the value of 'vrrpv3OperationsStatus' for the corresponding entry in the vrrpv3OperationsTable has transitioned to initialize(1).
除非vrrpv3OperationsTable中相应条目的“vrrpv3OperationsStatus”值已转换为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 }
索引{ifIndex，VRRPV3操作VRID，VRRPV3操作INETADDRTYPE，VRRPV3关联IP地址}
::= { vrrpv3AssociatedIpAddrTable 1 }
::= { vrrpv3AssociatedIpAddrTable 1 }
Vrrpv3AssociatedIpAddrEntry ::=
SEQUENCE {
vrrpv3AssociatedIpAddrAddress
Vrrpv3AssociatedIpAddrEntry ::=
SEQUENCE {
vrrpv3AssociatedIpAddrAddress
InetAddress, vrrpv3AssociatedIpAddrRowStatus RowStatus }
InetAddress，VRRPV3关联IPAddressRowStatus 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.
VRRPV3AssociatedIPAddress对象类型语法InetAddress（大小（0 | 4 | 16））MAX-ACCESS不可访问状态当前描述“虚拟路由器负责备份的分配IP地址。
The IP address type is determined by the value of
vrrpv3OperationsInetAddrType in the index of this
row."
REFERENCE "RFC 5798"
::= { vrrpv3AssociatedIpAddrEntry 1 }
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
VRRPV3AssociatedIPADDROWSTATUS对象类型语法RowStatus MAX-ACCESS read create STATUS current DESCRIPTION“行状态变量，根据安装和删除约定用于
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.
排。要在此表中创建行，管理器将此对象设置为createAndGo（4）或createAndWait（5）。将此对象设置为活动（1）将导致添加虚拟路由器的关联地址。将此对象设置为notInService（2）将导致以管理方式关闭该行。
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.
销毁条目或将其设置为销毁（6）会从虚拟路由器中删除关联的地址。其他值的使用取决于实现。
Implementations should not allow deletion of the last row corresponding to an active row in vrrpv3OperationsTable.
实现不应允许删除与vrrpv3OperationsTable中活动行相对应的最后一行。
Refer to the description of vrrpv3OperationsRowStatus
for typical row creation and deletion scenarios."
::= { vrrpv3AssociatedIpAddrEntry 2 }
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.
VRRPV3RouterCheckSumerors对象类型语法计数器64 MAX-ACCESS只读状态当前描述“接收到的具有无效VRRP校验和值的VRRP数据包总数。
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."
在管理系统重新初始化时，以及在VRRPV3GlobalStatisticsInjunctionTime值指示的其他时间，此计数器的值可能会出现不连续。”
REFERENCE "RFC 5798, Section 5.2.8"
::= { vrrpv3Statistics 1 }
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.
VRRPV3RouteServersOnErrors对象类型语法计数器64 MAX-ACCESS只读状态当前描述“接收到的版本号未知或不受支持的VRRP数据包总数。
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."
VRRPV3GlobalStatisticsIntercontinurationTime值指示的其他时间。”
REFERENCE "RFC 5798, Section 5.2.1"
::= { vrrpv3Statistics 2 }
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.
vrrpv3RouterVrIdErrors对象类型语法计数器64 MAX-ACCESS只读状态当前描述“接收到的VRRP数据包总数，其VRID对此路由器上的任何虚拟路由器无效。
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."
在管理系统重新初始化时，以及在VRRPV3GlobalStatisticsInjunctionTime值指示的其他时间，此计数器的值可能会出现不连续。”
REFERENCE "RFC 5798, Section 5.2.3"
::= { vrrpv3Statistics 3 }
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.
VRRPV3GlobalStatisticsInterruptyTime对象类型语法时间戳MAX-ACCESS只读状态当前描述“最近vrrpv3RouterChecksumErrors、VRRPV3RouterServersOnErrors和VRRPV3RouterRidErrors之一发生中断时的系统正常运行时间值。
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 }
::= { vrrpv3Statistics 4 }
-- VRRP Router Statistics Table
--VRRP路由器统计表
vrrpv3StatisticsTable OBJECT-TYPE
SYNTAX SEQUENCE OF Vrrpv3StatisticsEntry
MAX-ACCESS not-accessible
STATUS current
DESCRIPTION
"Table of virtual router statistics."
::= { vrrpv3Statistics 5 }
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 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
}
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.
vrrpv3StatisticsMasterTransitions对象类型语法计数器32 MAX-ACCESS只读状态当前描述“此虚拟路由器状态转换为主状态的总次数。
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 }
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 }
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.
VRRPV3StatisticsRCVDAdvertisions对象类型语法计数器64 MAX-ACCESS只读状态当前描述“此虚拟路由器接收的VRRP播发总数。
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."
在管理系统重新初始化时，以及在VRRPV3StatisticsRowIntercontinuctionTime值指示的其他时间，该计数器的值可能会出现不连续。”
::= { vrrpv3StatisticsEntry 3 }
::= { 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
vrrpv3StatisticsAdvIntervalErrors对象类型语法计数器64 MAX-ACCESS只读状态当前描述“接收的VRRP播发数据包总数，播发间隔为
different from the vrrpv3OperationsAdvInterval configured on this virtual router.
与此虚拟路由器上配置的vrrpv3OperationsAdvInterval不同。
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."
在管理系统重新初始化时，以及在VRRPV3StatisticsRowIntercontinuctionTime值指示的其他时间，该计数器的值可能会出现不连续。”
::= { vrrpv3StatisticsEntry 4 }
::= { 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.
VRRPV3StatisticsIPTTErrors对象类型语法计数器64最大访问只读状态当前描述“虚拟路由器接收的VRRP数据包总数，其中IPv4 TTL（对于IPv4上的VRRP）或IPv6跃点限制（对于IPv6上的VRRP）不等于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 }
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 }
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
vrrpv3StatisticsRcvdPriZeroPackets对象类型语法计数器64最大访问只读状态当前说明
"The total number of VRRP packets received by the virtual router with a priority of '0'.
“由优先级为“0”的虚拟路由器接收的VRRP数据包总数。
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 }
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'.
VRRPV3StatisticsEntpriZeroPackets对象类型语法计数器64 MAX-ACCESS只读状态当前描述“由优先级为“0”的虚拟路由器发送的VRRP数据包总数”。
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 }
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.
vrrpv3StatisticsRcvdInvalidTypePackets对象类型语法计数器64 MAX-ACCESS只读状态当前描述“虚拟路由器接收的VRRP数据包数量，在“类型”字段中具有无效值。
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 }
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.
vrrpv3StatisticsAddressListErrors对象类型语法计数器64 MAX-ACCESS只读状态当前描述“收到的地址列表与虚拟路由器本地配置的列表不匹配的数据包总数。
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 }
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.
vrrpv3StatisticsPacketLengthErrors对象类型语法计数器64 MAX-ACCESS只读状态当前描述“数据包长度小于VRRP标头长度时接收的数据包总数。
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 }
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.
VRRPV3StatisticsRowInteractionyTime对象类型语法时间戳MAX-ACCESS只读状态当前描述“此项的任何一个或多个计数器最近发生中断时的sysUpTime值。
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 }
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 }
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
-- 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 }
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 }
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 }
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 }
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
VRRPV3只读符合性模块-符合性状态当前说明
"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."
当此MIB模块在不支持读创建的情况下实现时（即，在只读模式下），这样的实现可以声明只读符合性。这样的设备可以被监视，但不能用此MIB配置
MODULE -- this module
MANDATORY-GROUPS {
vrrpv3OperationsGroup,
vrrpv3StatisticsGroup,
vrrpv3StatisticsDiscontinuityGroup,
vrrpv3InfoGroup,
vrrpv3NotificationsGroup
}
MODULE -- this module
MANDATORY-GROUPS {
vrrpv3OperationsGroup,
vrrpv3StatisticsGroup,
vrrpv3StatisticsDiscontinuityGroup,
vrrpv3InfoGroup,
vrrpv3NotificationsGroup
}
OBJECT vrrpv3OperationsPriority MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象VRRPV3操作优先级最小访问只读描述“不需要写访问。”
OBJECT vrrpv3OperationsPrimaryIpAddr MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT vrrpv3OperationsAdvInterval MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象VRRPV3OperationsPrimaryPaddr最小访问只读描述“不需要写访问”。对象vrrpv3OperationsAdvInterval最小访问只读描述“不需要写访问”
OBJECT vrrpv3OperationsPreemptMode MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象vrrpv3OperationsPreemptMode最小访问只读描述“不需要写访问。”
OBJECT vrrpv3OperationsAcceptMode MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象vrrpv3OperationsAcceptMode最小访问只读描述“不需要写访问。”
OBJECT vrrpv3OperationsRowStatus MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象vrrpv3OperationsRowStatus最小访问只读描述“不需要写入访问权限。”
OBJECT vrrpv3AssociatedIpAddrRowStatus MIN-ACCESS read-only DESCRIPTION "Write access is not required."
对象VRRPV3关联的IPAddressRowStatus最小访问只读说明“不需要写入访问。”
::= { vrrpv3Compliances 2 }
::= { vrrpv3Compliances 2 }
-- Conformance Groups
--一致性组
vrrpv3OperationsGroup OBJECT-GROUP OBJECTS {
VRRPV3操作组对象-组对象{
vrrpv3OperationsVirtualMacAddr,
vrrpv3OperationsStatus,
vrrpv3OperationsPriority,
vrrpv3OperationsMasterIpAddr,
vrrpv3OperationsAdvInterval,
vrrpv3OperationsPreemptMode,
vrrpv3OperationsAcceptMode,
vrrpv3OperationsUpTime,
vrrpv3OperationsRowStatus,
vrrpv3OperationsAddrCount,
vrrpv3OperationsPrimaryIpAddr,
vrrpv3AssociatedIpAddrRowStatus
}
STATUS current
DESCRIPTION
"Conformance group for VRRPv3 operations."
::= { vrrpv3Groups 1 }
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 }
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
vrrpv3StatisticsDiscontinuityGroup OBJECT-GROUP
OBJECTS {
vrrpv3GlobalStatisticsDiscontinuityTime
}
STATUS current
DESCRIPTION
"Objects providing information about counter
discontinuities."
::= { vrrpv3Groups 3 }
"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 }
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 }
vrrpv3NotificationsGroup NOTIFICATION-GROUP
NOTIFICATIONS {
vrrpv3NewMaster,
vrrpv3ProtoError
}
STATUS current
DESCRIPTION
"The VRRP MIB Notification Group."
::= { vrrpv3Groups 5 }
END
终止
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模块中定义了许多管理对象，其MAX-ACCESS子句为read-write和/或read-create。在某些网络环境中，此类对象可能被视为敏感或易受攻击。在没有适当保护的非安全环境中支持SET操作可能会对网络操作产生负面影响。以下是表和对象及其敏感度/漏洞：
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、VRRPV3OperationsPrimaryPaddr、vrrpv3OperationsAdvInterval、vrrpv3OperationsPreemptMode、vrrpv3OperationsAcceptMode、vrrpv3OperationsRowStatus和VRRPV3AssociatedIPAddressRowStatus具有读取-创建属性。对这些对象的操作可能会影响虚拟路由器的操作。
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 修改VRRPV3OperationsPrimaryPaddr会导致配置的路由器在成为主路由器时使用不正确的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 对vrrpv3OperationsAdvInterval的恶意更改可能会导致配置的路由器在成为主控时向网络发送大量广告，或者新主控未频繁发送广告，从而导致某些路由器无法了解新主控。
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 VRRPV3操作抢占模式控制此路由器是否抢占另一个主路由器。设置不当将导致一台路由器违反运营商的计划成为主路由器，但该路由器仍有资格作为主路由器运行。
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)
实现必须提供SNMPv3框架（参见[RFC3410]）描述的安全功能，包括通过基于用户的安全模型（USM）[RFC3414]和AES密码算法[RFC3826]对身份验证和隐私的完全支持。实现还可以提供对传输安全模型（TSM）的支持
[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版本。相反，建议部署SNMPv3并启用加密安全性。然后，客户/运营商应负责确保授予访问此MIB模块实例权限的SNMP实体已正确配置为仅授予那些拥有确实获取或设置（更改/创建/删除）对象的合法权限的主体（用户）访问对象。
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
---------- -----------------------
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。
[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.，和J.Schoenwaeld，“管理信息的结构版本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.，和J.Schoenwaeld，“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.，和J.Schoenwaeld，“SMIv2的一致性声明”，STD 58，RFC 25801999年4月。
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group MIB", RFC 2863, June 2000.
[RFC2863]McCloghrie，K.和F.Kastenholz，“接口组MIB”，RFC 28632000年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.，和B.Stewart，“简单网络管理协议（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.，和J.Schoenwaeld，“互联网网络地址的文本约定”，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.，编辑，“IPv4和IPv6的虚拟路由器冗余协议（VRRP）第3版”，RFC 5798，2010年3月。
[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]奈特，S.，韦弗，D.，惠普尔，D.，辛登，R.，米特泽尔，D.，亨特，P.，希金森，P.，尚德，M.，和A.林登，“虚拟路由器冗余协议”，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.和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.，和B.Stewart，“互联网标准管理框架的介绍和适用性声明”，RFC 34102002年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.和B.Wijnen，“简单网络管理协议（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.，和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.和W.Hardaker，“简单网络管理协议（SNMP）的传输安全模型”，RFC 55912009年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.，和W.Hardaker，“简单网络管理协议（SNMP）的安全外壳传输模型”，RFC 55922009年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 63532011年7月。
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的作者是Brian Jewell和David Chuang。作者还要感谢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诺基亚313飞兆儿童加利福尼亚州山景城博士94043电子邮件：Tata_kalyan@yahoo.com