idnits 2.16.02
/tmp/draft-ietf-vrrp-mib-08.txt:
Checking boilerplate required by RFC 5378 and the IETF Trust (see
https://trustee.ietf.org/license-info):
----------------------------------------------------------------------------
** Looks like you're using RFC 2026 boilerplate. This must be updated to
follow RFC 3978/3979, as updated by RFC 4748.
Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt:
----------------------------------------------------------------------------
** Missing expiration date. The document expiration date should appear on
the first and last page.
** The document seems to lack a 1id_guidelines paragraph about 6 months
document validity -- however, there's a paragraph with a matching
beginning. Boilerplate error?
== No 'Intended status' indicated for this document; assuming Proposed
Standard
== It seems as if not all pages are separated by form feeds - found 0 form
feeds but 39 pages
Checking nits according to https://www.ietf.org/id-info/checklist :
----------------------------------------------------------------------------
** The document seems to lack an IANA Considerations section. (See Section
2.2 of https://www.ietf.org/id-info/checklist for how to handle the case
when there are no actions for IANA.)
** The document seems to lack separate sections for Informative/Normative
References. All references will be assumed normative when checking for
downward references.
** There are 48 instances of too long lines in the document, the longest
one being 5 characters in excess of 72.
** The abstract seems to contain references ([2], [17], [19]), which it
shouldn't. Please replace those with straight textual mentions of the
documents in question.
Miscellaneous warnings:
----------------------------------------------------------------------------
== Line 642 has weird spacing: '...nsition to be...'
== Line 815 has weird spacing: '...virtual route...'
== Couldn't figure out when the document was first submitted -- there may
comments or warnings related to the use of a disclaimer for pre-RFC5378
work that could not be issued because of this. Please check the Legal
Provisions document at https://trustee.ietf.org/license-info to determine
if you need the pre-RFC5378 disclaimer.
-- Couldn't find a document date in the document -- date freshness check
skipped.
Checking references for intended status: Proposed Standard
----------------------------------------------------------------------------
(See RFCs 3967 and 4897 for information about using normative references
to lower-maturity documents in RFCs)
-- Looks like a reference, but probably isn't: 'RFC2574' on line 1254
-- Looks like a reference, but probably isn't: 'RFC2575' on line 1255
== Unused Reference: '22' is defined on line 1373, but no explicit
reference was found in the text
** Obsolete normative reference: RFC 2571 (ref. '1') (Obsoleted by RFC 3411)
** Downref: Normative reference to an Informational RFC: RFC 1215 (ref. '4')
** Downref: Normative reference to an Historic RFC: RFC 1157 (ref. '8')
** Downref: Normative reference to an Historic RFC: RFC 1901 (ref. '9')
** Obsolete normative reference: RFC 1906 (ref. '10') (Obsoleted by RFC
3417)
** Obsolete normative reference: RFC 2572 (ref. '11') (Obsoleted by RFC
3412)
** Obsolete normative reference: RFC 2574 (ref. '12') (Obsoleted by RFC
3414)
** Obsolete normative reference: RFC 1905 (ref. '13') (Obsoleted by RFC
3416)
** Obsolete normative reference: RFC 2573 (ref. '14') (Obsoleted by RFC
3413)
** Obsolete normative reference: RFC 2575 (ref. '15') (Obsoleted by RFC
3415)
** Obsolete normative reference: RFC 2570 (ref. '16') (Obsoleted by RFC
3410)
** Obsolete normative reference: RFC 2338 (ref. '17') (Obsoleted by RFC
3768)
** Obsolete normative reference: RFC 1902 (ref. '19') (Obsoleted by RFC
2578)
** Obsolete normative reference: RFC 1903 (ref. '20') (Obsoleted by RFC
2579)
** Obsolete normative reference: RFC 1904 (ref. '21') (Obsoleted by RFC
2580)
** Obsolete normative reference: RFC 2223 (ref. '22') (Obsoleted by RFC
7322)
** Obsolete normative reference: RFC 2233 (ref. '23') (Obsoleted by RFC
2863)
Summary: 24 errors (**), 0 flaws (~~), 6 warnings (==), 3 comments (--).
Run idnits with the --verbose option for more detailed information about
the items above.
--------------------------------------------------------------------------------
1 INTERNET-DRAFT B. Jewell
2 June 24, 1999 D. Chuang
3 3Com, Inc.
5 Definitions of Managed Objects for the
6 Virtual Router Redundancy Protocol
8
10 Status of this Memo
12 This document is an Internet-Draft and is in full conformance with
13 all provisions of Section 10 of RFC2026.
15 Internet-Drafts are working documents of the Internet Engineering
16 Task Force (IETF), its areas, and its working groups. Note that
17 other groups may also distribute working documents as Internet-
18 Drafts.
20 Internet-Drafts are draft documents valid for a maximum of six months
21 and may be updated, replaced, or obsoleted by other documents at any
22 time. It is inappropriate to use Internet- Drafts as reference
23 material or to cite them other than as "work in progress."
25 The list of current Internet-Drafts can be accessed at
26 http://www.ietf.org/ietf/1id-abstracts.txt
28 The list of Internet-Draft Shadow Directories can be accessed at
29 http://www.ietf.org/shadow.html.
31 This internet draft expires on December 4, 1999.
33 Abstract
35 This specification defines an extension to the Management Information
36 Base (MIB) for use with SNMP-based network management. In
37 particular, it defines objects for configuring, monitoring, and
38 controlling routers that employ the Virtual Router Redundancy
39 Protocol (VRRP) [17].
41 This memo specifies a MIB module in a manner that is compliant with
42 both the SNMPv2 SMI [19], and semantically identical to the SNMPv1
43 definitions [2].
45 Table of Contents
47 1 The SNMPv2 Network Management Framework ............... 3
49 2 Overview .............................................. 4
51 2.1 VRRP MIB Structure .................................. 4
53 2.2 Virtual Router Redundancy Protocol .................. 4
55 2.3 VRRP MIB Table Design ............................... 5
57 2.3.1 Relation to Interface Group ....................... 5
59 2.4 VRRP Scenarios ...................................... 5
61 2.4.1 Scenario #1 ....................................... 6
63 2.4.2 Scenario #2 ....................................... 8
65 3 Definitions ........................................... 11
67 4 Security Considerations ............................... 31
69 5 Acknowledgements ...................................... 32
71 6 References ............................................ 32
73 7 Authors' Addresses .................................... 34
75 1. The SNMP Management Framework
77 The SNMP Management Framework presently consists of five major
78 components:
80 o An overall architecture, described in RFC 2571 [1].
82 o Mechanisms for describing and naming objects and events for the
83 purpose of management. The first version of this Structure of
84 Management Information (SMI) is called SMIv1 and described in RFC
85 1155 [2], RFC 1212 [3] and RFC 1215 [4]. The second version,
86 called SMIv2, is described in RFC 2578 [5], RFC 2579 [6] and RFC
87 2580 [7].
89 o Message protocols for transferring management information. The
90 first version of the SNMP message protocol is called SNMPv1 and
91 described in RFC 1157 [8]. A second version of the SNMP message
92 protocol, which is not an Internet standards track protocol, is
93 called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10].
94 The third version of the message protocol is called SNMPv3 and
95 described in RFC 1906 [10], RFC 2572 [11] and RFC 2574 [12].
97 o Protocol operations for accessing management information. The
98 first set of protocol operations and associated PDU formats is
99 described in RFC 1157 [8]. A second set of protocol operations and
100 associated PDU formats is described in RFC 1905 [13].
102 o A set of fundamental applications described in RFC 2573 [14] and
103 the view-based access control mechanism described in RFC 2575
104 [15].
106 A more detailed introduction to the current SNMP Management Framework
107 can be found in RFC 2570 [16].
109 Managed objects are accessed via a virtual information store, termed
110 the Management Information Base or MIB. Objects in the MIB are
111 defined using the mechanisms defined in the SMI.
113 This memo specifies a MIB module that is compliant to the SMIv2. A
114 MIB conforming to the SMIv1 can be produced through the appropriate
115 translations. The resulting translated MIB must be semantically
116 equivalent, except where objects or events are omitted because no
117 translation is possible (use of Counter64). Some machine readable
118 information in SMIv2 will be converted into textual descriptions in
119 SMIv1 during the translation process. However, this loss of machine
120 readable information is not considered to change the semantics of the
121 MIB.
123 2. Overview
125 This memo identifies the set of objects for configuring, monitoring,
126 and controlling the Virtual Router Redundancy Protocol (VRRP), as
127 defined in RFC 2338 [17].
129 VRRP specifies an election protocol that will allow one or more
130 associated IP addresses to be assumed by another router in the event
131 of a failure of the IP address(es) owner. Thus, IP traffic from a
132 host using a failed router as a default gateway is transparently
133 fowarded by the VRRP router that has assumed control. VRRP provides
134 redundancy in routed networks without requiring configuration of
135 dynamic routing or router discovery protocols on every end-host.
137 2.1. VRRP MIB Structure
139 The VRRP MIB contains three conformance groups:
141 - vrrpOperations Group: Objects related to VRRP router's
142 configuration and control.
144 - vrrpStatistics Group: Objects containing information useful in
145 monitoring the operation of VRRP routers.
147 - vrrpNotifications Group: Consists of objects and definitions for
148 use in SNMP traps sent by VRRP routers.
150 Tables in the MIB include the following:
152 (1) The vrrpOperTable, which contains objects that define the
153 operational characteristics of a VRRP router. Rows in this table
154 correspond to instances of virtual routers.
156 (2) The vrrpAssoIpAddrTable, which contains the addresses of the
157 virtual router(s) that a given VRRP router is backing up.
159 (3) The vrrpRouterStatsTable which contains the operating statistics
160 for a VRRP router.
162 2.2. Virtual Router Redundancy Protocol
164 This MIB is based on the following characteristics of VRRP as defined
165 in the VRRP specification [17].
167 - A "VRRP router" is one that is configured to run the VRRP protocol
168 in conjunction with one or more other VRRP routers attached to a
169 LAN.
171 - A VRRP router can be running one or more instances of a virtual
172 router.
174 - A "virtual router" is an abstraction which consists of two or more
175 physical routers associated by a Virtual Router Identifier (VRID).
177 - An instance of a virtual router (on a physical VRRP router), can
178 be uniquely identified by a combination of the 'IF Index' [18] and
179 "Virtual Router Identifier" (VRID).
181 - For each VRID there is a set of one or more "associated IP
182 addresses" that are backed-up by the virtual router.
184 2.3. VRRP MIB Table Design
186 The tables in the VRRP MIB are structured with the assumption that a
187 VRRP network management application would likely be designed to
188 display information or provide configuration about a VRRP router on a
189 "per-virtual-router basis". Thus, the tables defined in the MIB
190 consist of conceptual rows which are grouped in a manner to present a
191 view of individual virtual routers with a minimal number of SNMP
192 operations.
194 2.3.1. Relation to Interface Group (RFC 2233) [23].
196 Since a router can be participating in VRRP on one or more physical
197 interfaces, "ifIndex" is used as an index into the tables defined in
198 the VRRP MIB.
200 2.4. VRRP Scenarios
202 The following section provides examples of how some of the objects in
203 this MIB are instantiated for two different VRRP scenarios.
205 KEY:
206 ----
208 The labels in the following tables and diagrams correspond to the
209 actual MIB objects as follows:
211 if = vrrpOperIfIndex
212 VrId = vrrpOperVrId
213 State = vrrpOperState
214 Prior = vrrpOperPriority
215 AddrCnt = vrrpOperIpAddrCount
216 IpAddr = vrrpOperMasterIpAddr
217 RowStat = vrrpOperRowStatus
219 2.4.1. VRRP Scenario #1
221 The following figure shows a simple network with two VRRP routers
222 configured with two virtual routers. This sample topology is taken
223 from the VRRP specification [17]. Addresses in '()' indicate the IP
224 address of the default gateway for a given host, H1 - H4. In the
225 diagram, "Interface" is used in the context defined in MIB-II [4].
227 VRID=1 VRID=2
228 +-----+ +-----+
229 | MR1 | | MR2 |
230 | & | | & |
231 | BR2 | | BR1 |
232 +-----+ +-----+
233 IP A ---------->* ** * backup state.
1518 The description for the "vrrpStatsBecomeMaster" was also
1519 changed to more accurately convey this fact.
1520 - The SYNTAX of the "vrrpOperIpAddrCount" was changed to
1521 reflect the fact that a virtual router can support only up
1522 to 255 backup IP addresses.
1523 - Descriptions for vrrpOperAuthType and vrrpOperAuthKey expanded
1524 to indicate the per-interface assignment.
1525 - SYNTAX of vrrpOperPreemptMode object changed from INTEGER
1526 to 'truthValue'
1527 - The OIDs for the VRRP traps were fixed; incorrect ident-
1528 ifiers ('vrrpOperations') had been used in OID assignments.
1529 - The SYNTAX for the 'vrrpOperPriority' object was corrected
1530 to indicate that this can have a value of '0'.
1531 - The vrrpOperHMACMD5Key object was deleted. It was combined
1532 with the vrrpOperAuthKey object, whose SYNTAX was adjusted
1533 accordingly.
1534 - OID for 'vrrpTraps' changed to '{ vrrpNotifications 1 }'
1535 - The 'vrrpStatsPasswdSecurityViolations' and 'vrrpStatsHmac-
1536 SecurityViolations' objects have been combined into a
1537 single 'vrrpStatsSecurityViolations' object; this was
1538 suggested to avoid redundancy.
1539 - As per the last WG meeting, the 'vrrpAssoIpAddrIndex' object
1540 has been deleted from the 'vrrpAssoIpAddrTable'and replaced
1541 by 'vrrpAssoIpAddr'.
1542 - Removed references to 'vrrpAssoIpAddrIndex' in samples.
1543 - Added new object 'vrrpOperProtocol' to 'VrrpOperEntry'.
1544 - MAX-ACCESS for the 'vrrpOperVrId' object changed to
1545 'not-accessible', as per RFC1902 (auxilary objects).
1546 - SYNTAX for 'vrrpOperVirtualRouterUpTime' changed to
1547 'TimeStamp'.
1548 - Added importation of 'TruthValue'and 'TimeStamp' to accomodate
1549 changes listed above. Deleted importation of 'TimeTicks'.
1550 - Changed MAX-ACCESS to 'accessible-for-notify' for
1551 'vrrpTrapPacketSrc' and 'vrrpTrapConfigErrorType' objects.
1552 - In the sample tables, the "if" values were incorrect for
1553 the sample tables for "IP B" (they used to read "I1").
1554 - MAX-ACCESS for 'vrrpOperAuthType' and 'vrrpOperAuthKey'
1555 changed to 'read-only', since these objects are defined on
1556 a per-interface basis.
1557 - Overall review and editing of Section 5.0 (References) with
1558 deletion of references not used in this document. Also, added
1559 reference '9'.
1561 Concerns:
1562 ---------
1563 - Keep the 'vrrpTrapAuthFailure' trap?
1564 - Remove 'vrrpTrapPacketSrc' and 'vrrpTrapConfigErrorType' from
1565 compliances? Only used for 'vrrpTrapAuthFailure' trap.
1567 * 3/4/1998: Changes in 1st revision (draft-ietf-vrrp-mib-01.txt):
1569 - Overall review and editing of document text and object
1570 descriptions from feedback received at December 1997 IETF meeting.
1571 More specifically the changes made along these lines include
1572 the following:
1574 -- Cleaned up Section 5.0 ("References") and validated.
1575 -- Modifed diagram for VRRP Scenario #2 (Section 2.4.2).
1576 -- VRRP Overview (Section 2.0) rewritten to be more in-line with
1577 latest revision (05) of VRRP RFC Draft.
1578 -- Description of "VrId" Textual convention rewritten.
1580 - MAX-ACCESS of vrrpTrapCntl object changed to "read-write".
1581 - Changed SYNTAX of "vrrpOperVirtualMacAddr" object from
1582 "PhyAddress" to "MacAddress".
1583 - Changed the syntax of the "vrrpOperPriority" object so upper
1584 value can be 255.
1585 - Change MAX-ACCESS for "vrrpOperAuthType" object from
1586 read-only to read-create.
1587 - Added three new objects to "vrrpRouterStatsTable":
1588 "vrrpStatsAddressListErrors", "vrrpStatsUnknownAuthType"
1589 and "vrrpStatsAuthTypeErrors".
1590 - Removed "vrrpStatsUnknownPacketType" object, as it was
1591 redundant (with "vrrpStatsInvalidPacketType").
1592 - Removed the "vrrpOperIfIndex" object to use "ifIndex" (which is
1593 actually equivalent) instead.
1595 * 11/19/97 (vft-ietf-vrrp-mib-00.txt) - Initial Draft