< draft-ietf-vrrp-unified-mib-09.txt   draft-ietf-vrrp-unified-mib-10.txt >
Network Working Group Kalyan Tata Network Working Group Kalyan Tata
Internet Draft Check Point Software Internet Draft Check Point Software
Document: draft-ietf-vrrp-unified-mib-09.txt April 2011 Document: draft-ietf-vrrp-unified-mib-10.txt September 2011
Obsoletes: 2787 (if approved) Obsoletes: 2787 (if approved)
Intended Status: Proposed Standard Intended Status: Proposed Standard
Expires: Oct 2011 Expires: March 2012
Definitions of Managed Objects for VRRPv3 Definitions of Managed Objects for VRRPv3
<draft-ietf-vrrp-unified-mib-09.txt> <draft-ietf-vrrp-unified-mib-10.txt>
Abstract Abstract
This specification defines a portion of the Management Information This specification defines a portion of the Management Information
Base (MIB) for use with SNMP-based network management. In Base (MIB) for use with SNMP-based network management. In
particular, it defines objects for configuring, monitoring, and particular, it defines objects for configuring, monitoring, and
controlling routers that employ the Virtual Router Redundancy controlling routers that employ the Virtual Router Redundancy
Protocol Version 3 for both IPv4 and IPv6 as defined in RFC 5798. Protocol Version 3 for both IPv4 and IPv6 as defined in RFC 5798.
This memo obsoletes RFC 2787. This memo obsoletes RFC 2787.
skipping to change at page 2, line 26 skipping to change at page 2, line 26
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) (http://trustee.ietf.org/license-info)
in effect on the date of publication of this document. Please in effect on the date of publication of this document. Please
review these documents carefully, as they describe your rights and review these documents carefully, as they describe your rights and
restrictions with respect to this document. Code Components restrictions with respect to this document. Code Components
extracted from this document must include Simplified BSD License extracted from this document must include Simplified BSD License
text as described in Section 4.e of the Trust Legal Provisions and text as described in Section 4.e of the Trust Legal Provisions and
are provided without warranty as described in the Simplified BSD are provided without warranty as described in the Simplified BSD
License. License.
Conventions used in this document
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
RFC2119 [RFC2119].
Table of Contents Table of Contents
1. The Internet-Standard Management Framework.....................3 1. The Internet-Standard Management Framework.....................3
2. Introduction...................................................3 2. Introduction...................................................3
3. Terminology....................................................3 3. Terminology....................................................3
4. Relationship to RFC 2787.......................................3 4. Relationship to RFC 2787.......................................3
5. Relation to Interface Group (IF-MIB)...........................3 5. Relation to Interface Group (IF-MIB)...........................3
6. Multi-Stack Implementations....................................3 6. Multi-Stack Implementations....................................3
7. VRRP MIB Structure and Design..................................4 7. Interpretation of RFC5798......................................4
8. VRRP Multistack Scenario.......................................4 8. VRRP MIB Structure and Design..................................4
9. Definitions....................................................7 9. VRRP Multistack Scenario.......................................4
10. Security Considerations......................................26 10. Definitions...................................................7
11. IANA Considerations..........................................27 11. Security Considerations......................................27
12. Normative References.........................................28 12. IANA Considerations..........................................28
13. Informative References.......................................28 13. Normative References.........................................28
14. Acknowledgments..............................................28 14. Informative References.......................................29
15. Author's Address.............................................29 15. Acknowledgments..............................................29
16. Author's Address.............................................29
1. The Internet-Standard Management Framework 1. The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410]. RFC 3410 [RFC3410].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. MIB objects are generally the Management Information Base or MIB. MIB objects are generally
accessed through the Simple Network Management Protocol (SNMP). accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the Objects in the MIB are defined using the mechanisms defined in the
Structure of Management Information (SMI). This memo specifies a MIB Structure of Management Information (SMI). This memo specifies a MIB
module that is compliant to the SMIv2, which is described in STD 58, 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 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
[RFC2580]. [RFC2580].
2. Introduction 2. Introduction
This specification defines a portion of the Management Information This specification defines a portion of the Management Information
Base (MIB) for use with SNMP-based network management. In Base (MIB) for use with SNMP-based network management. In
particular, it defines objects for configuring, monitoring, and particular, it defines objects for configuring, monitoring, and
controlling routers that employ the Virtual Router Redundancy controlling routers that employ the Virtual Router Redundancy
Protocol Version 3 for both IPv4 and IPv6 as defined in RFC 5798 Protocol Version 3 for both IPv4 and IPv6 as defined in RFC 5798
[RFC5798]. [RFC5798].
3. Terminology 3. Terminology
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
document are to be interpreted as described in RFC 2119 [RFC2119]. "OPTIONAL" in this document are to be interpreted as described in
RFC 2119 [RFC2119].
4. Relationship to RFC 2787 4. Relationship to RFC 2787
This document obsoletes RFC2787 [RFC2787]. The major changes in this This document obsoletes RFC2787 [RFC2787]. The major changes in this
document reflect changes in VRRP protocol between RFC 2338 [RFC2338] document reflect changes in VRRP protocol between RFC 2338 [RFC2338]
and RFC 5798 [RFC5798]. This document is also updated to conform to and RFC 5798 [RFC5798]. This document is also updated to conform to
current MIB conventions. current MIB conventions.
5. Relation to Interface Group (IF-MIB) 5. Relation to Interface Group (IF-MIB)
Since a router can be participating in VRRP on one or more Since a router can be participating in VRRP on one or more
interfaces, "ifIndex" is used as an index into the tables defined in 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 the VRRP MIB. This MIB module imports ifIndex from the IF-MIB. At
this time, the latest version of IF-MIB is from RFC2863 [RFC2863]. this time, the latest version of IF-MIB is from RFC2863 [RFC2863].
6. Multi-Stack Implementations 6. Multi-Stack Implementations
This MIB module is designed to support Multi-Stack implementations This MIB module is designed to support Multi-Stack implementations
that run VRRP over IPv4 and IPv6. IP version, VRID and ifIndex are that run VRRP over IPv4 and IPv6. IP version, VRID and ifIndex are
used to uniquely identify rows in a multi stack implementation. used to uniquely identify rows in a multi stack implementation.
7. VRRP MIB Structure and Design 7. Interpretation of RFC5798
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 on
which interpretation is correct. This document makes the following
assumption.
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.
8. VRRP MIB Structure and Design
This MIB module contains three tables: This MIB module contains three tables:
(1) The vrrpv3OperationsTable, which contains objects that define (1) The vrrpv3OperationsTable, which contains objects that define
the operational characteristics of a VRRP router. Rows in this the operational characteristics of a VRRP router. Rows in this
table correspond to instances of virtual routers. table correspond to instances of virtual routers.
(2) The vrrpv3StatisticsTable which contains the operating (2) The vrrpv3StatisticsTable which contains the operating
statistics for a VRRP router. statistics for a VRRP router.
(3) The vrrpv3AssociatedIpAddrTable, contains the addresses of the (3) The vrrpv3AssociatedIpAddrTable, contains the addresses of the
virtual router(s) that a given VRRP router is backing up. virtual router(s) that a given VRRP router is backing up.
Tables are indexed on ifIndex, VRID and the IP version to uniquely Tables are indexed on ifIndex, VRID and the IP version to uniquely
identify a VRRP router. identify a VRRP router.
Notifications in this MIB module are controlled using the mechanisms Notifications in this MIB module are controlled using the mechanisms
defined in [RFC3413]. defined in [RFC3413].
8. VRRP Multistack Scenario 9. VRRP Multistack Scenario
The following section provides examples of how some of the objects in The following section provides examples of how some of the objects in
this MIB are instantiated. this MIB are instantiated.
KEY: KEY:
---- ----
The labels in the following tables and diagrams correspond to the The labels in the following tables and diagrams correspond to the
actual MIB objects as follows: actual MIB objects as follows:
if = IfIndex if = IfIndex
AddrType= vrrpv3OperationsInetAddrType AddrType= vrrpv3OperationsInetAddrType
VrId = vrrpv3OperationsVrId VrId = vrrpv3OperationsVrId
State = vrrpv3OperationsStatus State = vrrpv3OperationsStatus
Prior = vrrpOpeartionsPriority Prior = vrrpOpeartionsPriority
IpAddr = vrrpv3OperationsMasterIpAddr IpAddr = vrrpv3OperationsMasterIpAddr
skipping to change at page 7, line 4 skipping to change at page 7, line 18
| I2 | 01 | 1 | C | active | | I2 | 01 | 1 | C | active |
+----+------+--------+------+---------+ +----+------+--------+------+---------+
| I2 | 01 | 2 | Y | active | | I2 | 01 | 2 | Y | active |
+----+------+--------+------+---------+ +----+------+--------+------+---------+
| I2 | 01 | 2 | Z | active | | I2 | 01 | 2 | Z | active |
+----+------+--------+------+---------+ +----+------+--------+------+---------+
| I2 | 02 | 1 | B | active | | I2 | 02 | 1 | B | active |
+----+------+--------+------+---------+ +----+------+--------+------+---------+
| I2 | 02 | 2 | X | active | | I2 | 02 | 2 | X | active |
+----+------+--------+------+---------+ +----+------+--------+------+---------+
NOTES: NOTES:
1) For "State": M = Master; B = Backup. 1) For "State": M = Master; B = Backup.
In the vrrpv3OperationsTable, a "priority" of 255 indicates that the In the vrrpv3OperationsTable, a "priority" of 255 indicates that the
respective router owns the IP address, e.g., this IP address is respective router owns the IP address, e.g., this IP address is
native to the router (i.e., "the IP Address Owner"). native to the router (i.e., "the IP Address Owner").
9. Definitions 10. Definitions
This MIB module makes reference to the following documents [RFC2578], This MIB module makes reference to the following documents [RFC2578],
[RFC2579], [RFC2580], [RFC2863], and [RFC4001]. [RFC2579], [RFC2580], [RFC2863], and [RFC4001].
VRRPV3-MIB DEFINITIONS ::= BEGIN VRRPV3-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, MODULE-IDENTITY, OBJECT-TYPE,
NOTIFICATION-TYPE, Counter32, NOTIFICATION-TYPE, Counter32,
Integer32, mib-2, Unsigned32, Integer32, mib-2, Unsigned32,
skipping to change at page 13, line 43 skipping to change at page 14, line 10
This object is not relevant for rows representing VRRP This object is not relevant for rows representing VRRP
over IPv4 and should be set to false(2)." over IPv4 and should be set to false(2)."
DEFVAL { false } DEFVAL { false }
::= { vrrpv3OperationsEntry 11 } ::= { vrrpv3OperationsEntry 11 }
vrrpv3OperationsUpTime OBJECT-TYPE vrrpv3OperationsUpTime OBJECT-TYPE
SYNTAX TimeTicks SYNTAX TimeTicks
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This value represents the amount of time since this "This value represents the amount of time, in
virtual router (i.e., the ` vrrpv3OperationsStatus') TimeTicks (hundredth of a second), since this virtual
router (i.e., the ` vrrpv3OperationsStatus')
transitioned out of `initialize'." transitioned out of `initialize'."
REFERENCE " RFC 5798 section 6.1" REFERENCE " RFC 5798 section 6.1"
::= { vrrpv3OperationsEntry 12 } ::= { vrrpv3OperationsEntry 12 }
vrrpv3OperationsRowStatus OBJECT-TYPE vrrpv3OperationsRowStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The RowStatus variable should be used in accordance to "The RowStatus variable should be used in accordance to
skipping to change at page 26, line 45 skipping to change at page 27, line 13
vrrpv3NewMaster, vrrpv3NewMaster,
vrrpv3ProtoError vrrpv3ProtoError
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The VRRP MIB Notification Group." "The VRRP MIB Notification Group."
::= { vrrpv3Groups 5 } ::= { vrrpv3Groups 5 }
END END
10. Security Considerations 11. Security Considerations
There are a number of management objects defined in this MIB module 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 with a MAX-ACCESS clause of read-write and/or read-create. Such
objects may be considered sensitive or vulnerable in some network objects may be considered sensitive or vulnerable in some network
environments. The support for SET operations in a non-secure environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on environment without proper protection can have a negative effect on
network operations. These are the tables and objects and their network operations. These are the tables and objects and their
sensitivity/vulnerability: sensitivity/vulnerability:
The objects vrrpv3OperationsPriority, vrrpv3OperationsPrimaryIpAddr, The objects vrrpv3OperationsPriority, vrrpv3OperationsPrimaryIpAddr,
skipping to change at page 27, line 41 skipping to change at page 28, line 9
authentication and privacy). authentication and privacy).
Further, deployment of SNMP versions prior to SNMPv3 is NOT Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them. rights to indeed GET or SET (change/create/delete) them.
11. IANA Considerations 12. IANA Considerations
The MIB module in this document uses the following IANA-assigned The MIB module in this document uses the following IANA-assigned
OBJECT IDENTIFIER values recorded in the SMI Numbers registry: OBJECT IDENTIFIER values recorded in the SMI Numbers registry:
Descriptor OBJECT IDENTIFIER value Descriptor OBJECT IDENTIFIER value
---------- ----------------------- ---------- -----------------------
vrrpv3MIB { mib-2 ZZZ } vrrpv3MIB { mib-2 ZZZ }
[Editor's Note (to be removed prior to publication): The IANA is [Editor's Note (to be removed prior to publication): The IANA is
requested to assign a value for "ZZZ" under the 'mib-2' subtree requested to assign a value for "ZZZ" under the 'mib-2' subtree
and to record the assignment in the SMI Numbers registry. When and to record the assignment in the SMI Numbers registry. When
the assignment has been made, the RFC Editor is asked to replace the assignment has been made, the RFC Editor is asked to replace
"ZZZ" (here and in the MIB module) with the assigned value. "ZZZ" (here and in the MIB module) with the assigned value.
This document obsoletes RFC 2787 and the IANA is requested to This document obsoletes RFC 2787 and the IANA is requested to
deprecate the value 68 under 'mib-2' assigned to VRRP-MIB.] deprecate the value 68 under 'mib-2' assigned to VRRP-MIB.]
12. Normative References 13. Normative References
[RFC2119] Bradner S., "Key words for use in RFCs to Indicate [RFC2119] Bradner S., "Key words for use in RFCs to Indicate
Requirement Levels", RFC 2119, March 1997. Requirement Levels", RFC 2119, March 1997.
[RFC2578] McCloghrie, K., D. Perkins, J. Schoenwaelder, J. Case, M. [RFC2578] McCloghrie, K., D. Perkins, J. Schoenwaelder, J. Case, M.
Rose, S. Waldbusser, "Structure of Management Information Rose, S. Waldbusser, "Structure of Management Information
Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[RFC2579] McCloghrie, K., D. Perkins, J. Schoenwaelder, J. Case, M. [RFC2579] McCloghrie, K., D. Perkins, J. Schoenwaelder, J. Case, M.
Rose, S. Waldbusser, "Textual Conventions for SMIv2", STD Rose, S. Waldbusser, "Textual Conventions for SMIv2", STD
58, RFC 2579, April 1999. 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., D. Perkins, J. Schoenwaelder, J. Case, M. [RFC2580] McCloghrie, K., D. Perkins, J. Schoenwaelder, J. Case, M.
Rose, S. Waldbusser, "Conformance Statements for SMIv2", Rose, S. Waldbusser, "Conformance Statements for SMIv2",
STD 58, RFC 2580, April 1999. STD 58, RFC 2580, April 1999.
[RFC2338] S.Knight, D.Weaver, D.Whipple, R.Hinden, D.Mitzel, P.Hunt, [RFC5798] S. Nadas, Ed., "Virtual Router Redundancy Protocol
P.Higginson, M.Shand, A.Lindem, "Virtual Router Redundancy
Protocol", RFC 2338, April 1998.
[RFC5798] S. Nadas, Ed., "Virtual Router Redundancy Protocol
Version 3 for IPv4 and IPv6 ", RFC 5798, Mar 2010. Version 3 for IPv4 and IPv6 ", RFC 5798, Mar 2010.
[RFC2787] Jewell, B., D. Chuang, "Definitions of Managed Objects for [RFC2787] Jewell, B., D. Chuang, "Definitions of Managed Objects for
the Virtual Router Redundancy Protocol", RFC 2787, March the Virtual Router Redundancy Protocol", RFC 2787, March
2000. 2000.
[RFC2863] McCloghrie, K., Kastenholz, F., "The Interfaces Group [RFC2863] McCloghrie, K., Kastenholz, F., "The Interfaces Group
MIB" RFC2863, June 2000. MIB" RFC2863, June 2000.
[RFC4001] Daniele, M., Haberman, B., Routhier, S., and J. [RFC4001] Daniele, M., Haberman, B., Routhier, S., and J.
Schoenwaelder, "Textual Conventions for Internet Schoenwaelder, "Textual Conventions for Internet
Network Addresses", RFC 4001, February 2005. Network Addresses", RFC 4001, February 2005.
[RFC3413] Levi, D., Meyer, P., Stewart, B., "SNMP Applications", [RFC3413] Levi, D., Meyer, P., Stewart, B., "SNMP Applications",
RFC 3413, December 2002. RFC 3413, December 2002.
13. Informative References 14. Informative References
[RFC3410] Case, J., R. Mundy, D. Partain, B. Stewart, "Introduction [RFC3410] Case, J., R. Mundy, D. Partain, B. Stewart, "Introduction
and Applicability Statements for Internet-Standard and Applicability Statements for Internet-Standard
Management Framework", RFC 3410, December 2002. Management Framework", RFC 3410, December 2002.
[RFC2338] S.Knight, D.Weaver, D.Whipple, R.Hinden, D.Mitzel, P.Hunt,
P.Higginson, M.Shand, A.Lindem, "Virtual Router Redundancy
Protocol", RFC 2338, April 1998.
14. Acknowledgments 15. Acknowledgments
Kripakaran Karlekar and Brain Jewell helped in design and initial Kripakaran Karlekar and Brain Jewell helped in design and initial
drafts of this specification. This specification is based on RFC drafts of this specification. This specification is based on RFC
2787. The authors of RFC2787 are Brian Jewell and David Chuang. The 2787. The authors of RFC2787 are Brian Jewell and David Chuang. The
author would also like to thank Bert Wijnen, Dave Thaler, Joan author would also like to thank Bert Wijnen, Dave Thaler, Joan
Cucchiara, Mukesh Gupta, Steve Bates and Adrian Farrel, for taking Cucchiara, Mukesh Gupta, Steve Bates, Adrian Farrel, Ben Campbell and
time to review the document and provide valuable guidance. Joel M. Halpern for taking time to review the document and provide
valuable guidance.
15. Author's Address 16. Author's Address
Srinivas Kalyan Tata Srinivas Kalyan Tata
Check Point Software Check Point Software
800 Bridge Parkway 800 Bridge Parkway
Redwood City, CA 94065 Redwood City, CA 94065
Phone: +1-408-505-0542 Phone: +1-408-505-0542
EMail: tata_kalyan@yahoo.com EMail: tata_kalyan@yahoo.com
 End of changes. 30 change blocks. 
47 lines changed or deleted 60 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/