< draft-ietf-ifmib-ifmib2-01.txt   draft-ietf-ifmib-ifmib2-02.txt >
Network Working Group Keith McCloghrie Network Working Group Keith McCloghrie
Internet Draft Cisco Systems Internet Draft Cisco Systems
Obsoletes: 1573, 2233 Frank Kastenholz Obsoletes: 1573, 2233 Frank Kastenholz
Argon Networks Argon Networks
11 October 1999 11 January 2000
The Interfaces Group MIB The Interfaces Group MIB
draft-ietf-ifmib-ifmib2-01.txt draft-ietf-ifmib-ifmib2-02.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026 [RFC2026]. all provisions of Section 10 of RFC2026 [RFC2026].
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as Internet- other groups may also distribute working documents as Internet-
Drafts. Drafts.
skipping to change at page 2, line ? skipping to change at page 2, line ?
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
Distribution of this document is unlimited. Please send comments Distribution of this document is unlimited. Please send comments
to the Interfaces MIB Working Group at if-mib@vnd.tek.com. to the Interfaces MIB Working Group at if-mib@vnd.tek.com.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (1999). All Rights Reserved. Copyright (C) The Internet Society (2000). All Rights Reserved.
1. Introduction 1. Introduction
This memo defines a portion of the Management Information Base This memo defines a portion of the Management Information Base
(MIB) for use with network management protocols in the Internet (MIB) for use with network management protocols in the Internet
community. In particular, it describes managed objects used for community. In particular, it describes managed objects used for
managing Network Interfaces. This memo discusses the 'interfaces' managing Network Interfaces. This memo discusses the 'interfaces'
group of MIB-II [17], especially the experience gained from the group of MIB-II [17], especially the experience gained from the
definition of numerous media-specific MIB modules for use in definition of numerous media-specific MIB modules for use in
conjunction with the 'interfaces' group for managing various sub- conjunction with the 'interfaces' group for managing various sub-
skipping to change at page 16, line 17 skipping to change at page 16, line 17
be incremented. Traffic would then appear to be very bursty, leading to be incremented. Traffic would then appear to be very bursty, leading to
incorrect conclusions of the network's performance. incorrect conclusions of the network's performance.
Instead, this memo adopts expanded, 64 bit, counters. These counters Instead, this memo adopts expanded, 64 bit, counters. These counters
are provided in new "high capacity" groups. The old, 32-bit, counters are provided in new "high capacity" groups. The old, 32-bit, counters
have not been deprecated. The 64-bit counters are to be used only when have not been deprecated. The 64-bit counters are to be used only when
the 32-bit counters do not provide enough capacity; that is, when the 32 the 32-bit counters do not provide enough capacity; that is, when the 32
bit counters could wrap too fast. bit counters could wrap too fast.
For interfaces that operate at 20,000,000 (20 million) bits per second For interfaces that operate at 20,000,000 (20 million) bits per second
or less, 32-bit byte and packet counters MUST be used. For interfaces or less, 32-bit byte and packet counters MUST be supported. For
that operate faster than 20,000,000 bits/second, and slower than interfaces that operate faster than 20,000,000 bits/second, and slower
650,000,000 bits/second, 32-bit packet counters MUST be used and 64-bit than 650,000,000 bits/second, 32-bit packet counters MUST be supported
octet counters MUST be used. For interfaces that operate at 650,000,000 and 64-bit octet counters MUST be supported. For interfaces that
bits/second or faster, 64-bit packet counters AND 64-bit octet counters operate at 650,000,000 bits/second or faster, 64-bit packet counters AND
MUST be used. 64-bit octet counters MUST be supported.
These speed thresholds were chosen as reasonable compromises based on These speed thresholds were chosen as reasonable compromises based on
the following: the following:
(1) The cost of maintaining 64-bit counters is relatively high, so (1) The cost of maintaining 64-bit counters is relatively high, so
minimizing the number of agents which must support them is minimizing the number of agents which must support them is
desirable. Common interfaces (such as 10Mbs Ethernet) should not desirable. Common interfaces (such as 10Mbs Ethernet) should not
require them. require them.
(2) 64-bit counters are a new feature, introduced in SNMPv2. It is (2) 64-bit counters are a new feature, introduced in SNMPv2. It is
skipping to change at page 23, line 43 skipping to change at page 23, line 43
consistent with current usage and interpretation of these traps by consistent with current usage and interpretation of these traps by
manager stations. manager stations.
Transitions to/from the notPresent state are concerned with the Transitions to/from the notPresent state are concerned with the
insertion and removal of hardware, and are outside the scope of these insertion and removal of hardware, and are outside the scope of these
traps. traps.
Therefore, this memo defines that LinkUp and linkDown traps are Therefore, this memo defines that LinkUp and linkDown traps are
generated just after ifOperStatus leaves, or just before it enters, the generated just after ifOperStatus leaves, or just before it enters, the
down state, respectively; except that LinkUp and linkDown traps are down state, respectively; except that LinkUp and linkDown traps are
never generated on transitions to/from the notPresent state. never generated on transitions to/from the notPresent state. For the
purpose of deciding when these traps occur, the lowerLayerDown state and
the down state are considered to be equivalent, i.e., there is no trap
on transition from lowerLayerDown into down, and there is a trap on
transition from any other state except down (and notPresent) into
lowerLayerDown.
Note that this definition allows a node with only one interface to Note that this definition allows a node with only one interface to
transmit a linkDown trap before that interface goes down. (Of course, transmit a linkDown trap before that interface goes down. (Of course,
when the interface is going down because of a failure condition, the when the interface is going down because of a failure condition, the
linkDown trap probably cannot be successfully transmitted anyway.) linkDown trap probably cannot be successfully transmitted anyway.)
Some interfaces perform a link "training" function when trying to bring Some interfaces perform a link "training" function when trying to bring
the interface up. In the event that such an interface were defective, the interface up. In the event that such an interface were defective,
then the training function would fail and the interface would remain then the training function would fail and the interface would remain
down, and the training function might be repeated at appropriate down, and the training function might be repeated at appropriate
intervals. If the interface, while performing this training function, intervals. If the interface, while performing this training function,
were considered to the in the testing state, then linkUp and linkDown were considered to the in the testing state, then linkUp and linkDown
traps would be generated for each start and end of the training traps would be generated for each start and end of the training
function. This is not the intent of the linkUp and linkDown traps, and function. This is not the intent of the linkUp and linkDown traps, and
therefore, while performing such a training function, the interface's therefore, while performing such a training function, the interface's
state should be represented as down. state should be represented as down.
skipping to change at page 56, line 22 skipping to change at page 56, line 22
-- compliance statements -- compliance statements
ifCompliance3 MODULE-COMPLIANCE ifCompliance3 MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for SNMP entities which have "The compliance statement for SNMP entities which have
network interfaces." network interfaces."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { ifGeneralInformationGroup, MANDATORY-GROUPS { ifGeneralInformationGroup,
linkUpDownNotificationsGroup, linkUpDownNotificationsGroup }
ifCounterDiscontinuityGroup }
-- The groups: -- The groups:
-- ifFixedLengthGroup -- ifFixedLengthGroup
-- ifHCFixedLengthGroup -- ifHCFixedLengthGroup
-- ifPacketGroup -- ifPacketGroup
-- ifHCPacketGroup -- ifHCPacketGroup
-- ifVHCPacketGroup -- ifVHCPacketGroup
-- are mutually exclusive; at most one of these groups is implemented -- are mutually exclusive; at most one of these groups is implemented
-- for a particular interface. When any of these groups is implemented
-- for a particular interface, then ifCounterDiscontinuityGroup must
-- also be implemented for that interface.
GROUP ifFixedLengthGroup GROUP ifFixedLengthGroup
DESCRIPTION DESCRIPTION
"This group is mandatory for those network interfaces which "This group is mandatory for those network interfaces which
are character-oriented or transmit data in fixed-length are character-oriented or transmit data in fixed-length
transmission units, and for which the value of the transmission units, and for which the value of the
corresponding instance of ifSpeed is less than or equal to corresponding instance of ifSpeed is less than or equal to
20,000,000 bits/second." 20,000,000 bits/second."
GROUP ifHCFixedLengthGroup GROUP ifHCFixedLengthGroup
skipping to change at page 57, line 27 skipping to change at page 57, line 29
bits/second but less than or equal to 650,000,000 bits/second but less than or equal to 650,000,000
bits/second." bits/second."
GROUP ifVHCPacketGroup GROUP ifVHCPacketGroup
DESCRIPTION DESCRIPTION
"This group is mandatory only for those network interfaces "This group is mandatory only for those network interfaces
which are packet-oriented and for which the value of the which are packet-oriented and for which the value of the
corresponding instance of ifSpeed is greater than corresponding instance of ifSpeed is greater than
650,000,000 bits/second." 650,000,000 bits/second."
GROUP ifCounterDiscontinuityGroup
DESCRIPTION
"This group is mandatory for those network interfaces that
are required to maintain counters (i.e., those for which one
of the ifFixedLengthGroup, ifHCFixedLengthGroup,
ifPacketGroup, ifHCPacketGroup, or ifVHCPacketGroup is
mandatory)."
GROUP ifRcvAddressGroup GROUP ifRcvAddressGroup
DESCRIPTION DESCRIPTION
"The applicability of this group MUST be defined by the "The applicability of this group MUST be defined by the
media-specific MIBs. Media-specific MIBs must define the media-specific MIBs. Media-specific MIBs must define the
exact meaning, use, and semantics of the addresses in this exact meaning, use, and semantics of the addresses in this
group." group."
OBJECT ifLinkUpDownTrapEnable OBJECT ifLinkUpDownTrapEnable
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
skipping to change at page 79, line 29 skipping to change at page 79, line 29
IETF Secretariat. IETF Secretariat.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary rights copyrights, patents or patent applications, or other proprietary rights
which may cover technology that may be required to practice this which may cover technology that may be required to practice this
standard. Please address the information to the IETF Executive standard. Please address the information to the IETF Executive
Director. Director.
13. Full Copyright Statement 13. Full Copyright Statement
Copyright (C) The Internet Society (1999). All Rights Reserved. Copyright (C) The Internet Society (2000). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it or others, and derivative works that comment on or otherwise explain it or
assist in its implmentation may be prepared, copied, published and assist in its implmentation may be prepared, copied, published and
distributed, in whole or in part, without restriction of any kind, distributed, in whole or in part, without restriction of any kind,
provided that the above copyright notice and this paragraph are included provided that the above copyright notice and this paragraph are included
on all such copies and derivative works. However, this document itself on all such copies and derivative works. However, this document itself
may not be modified in any way, such as by removing the copyright notice may not be modified in any way, such as by removing the copyright notice
or references to the Internet Society or other Internet organizations, or references to the Internet Society or other Internet organizations,
except as needed for the purpose of developing Internet standards in except as needed for the purpose of developing Internet standards in
skipping to change at page 81, line 26 skipping to change at page 81, line 26
3.1.7 Interface Speed ............................................. 17 3.1.7 Interface Speed ............................................. 17
3.1.8 Multicast/Broadcast Counters ................................ 18 3.1.8 Multicast/Broadcast Counters ................................ 18
3.1.9 Trap Enable ................................................. 19 3.1.9 Trap Enable ................................................. 19
3.1.10 Addition of New ifType values .............................. 19 3.1.10 Addition of New ifType values .............................. 19
3.1.11 InterfaceIndex Textual Convention .......................... 19 3.1.11 InterfaceIndex Textual Convention .......................... 19
3.1.12 New states for IfOperStatus ................................ 20 3.1.12 New states for IfOperStatus ................................ 20
3.1.13 IfAdminStatus and IfOperStatus ............................. 21 3.1.13 IfAdminStatus and IfOperStatus ............................. 21
3.1.14 IfOperStatus in an Interface Stack ......................... 22 3.1.14 IfOperStatus in an Interface Stack ......................... 22
3.1.15 Traps ...................................................... 22 3.1.15 Traps ...................................................... 22
3.1.16 ifSpecific ................................................. 24 3.1.16 ifSpecific ................................................. 24
3.1.17 Creation/Deletion of Interfaces ............................ 24 3.1.17 Creation/Deletion of Interfaces ............................ 25
3.1.18 All Values Must be Known ................................... 25 3.1.18 All Values Must be Known ................................... 25
4 Media-Specific MIB Applicability ................................ 27 4 Media-Specific MIB Applicability ................................ 27
5 Overview ........................................................ 28 5 Overview ........................................................ 28
6 Interfaces Group Definitions .................................... 29 6 Interfaces Group Definitions .................................... 29
7 Acknowledgements ................................................ 73 7 Acknowledgements ................................................ 73
8 References ...................................................... 73 8 References ...................................................... 73
9 Security Considerations ......................................... 76 9 Security Considerations ......................................... 76
10 Authors' Addresses ............................................. 76 10 Authors' Addresses ............................................. 76
11 Changes from RFC 2233 .......................................... 78 11 Changes from RFC 2233 .......................................... 78
12 Notice on Intellectual Property ................................ 79 12 Notice on Intellectual Property ................................ 79
 End of changes. 11 change blocks. 
14 lines changed or deleted 30 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/