draft-ietf-hubmib-etherif-mib-v3-02.txt   draft-ietf-hubmib-etherif-mib-v3-03.txt 
Ethernet Interfaces and Hub MIB Working Group Editor of this version: Ethernet Interfaces and Hub MIB Working Group J. Flick
INTERNET DRAFT J. Flick INTERNET DRAFT Hewlett-Packard Company
Hewlett-Packard Company March 2003
Editors of previous versions:
J. Flick
Hewlett-Packard Company
J. Johnson
RedBack Networks
F. Kastenholz
Unisphere Networks
May 2002
Definitions of Managed Objects for Definitions of Managed Objects for
the Ethernet-like Interface Types the Ethernet-like Interface Types
<draft-ietf-hubmib-etherif-mib-v3-02.txt> <draft-ietf-hubmib-etherif-mib-v3-03.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. all provisions of Section 10 of 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 1, line 44 skipping to change at page 1, line 35
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
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.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2002). All Rights Reserved. Copyright (C) The Internet Society (2003). All Rights Reserved.
Abstract Abstract
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
This memo obsoletes RFC 2665 ''Definitions of Managed Objects for the In particular, it defines objects for managing Ethernet-like
Ethernet-like Interface Types''. This memo updates that interfaces.
specification by including management information useful for the
management of 10 Gigabit per second (Gb/s) Ethernet interfaces.
Ethernet technology, as defined by the 802.3 Working Group of the This memo obsoletes RFC 2665. It updates that specification by
IEEE, continues to evolve, with scalable increases in speed, new including management information useful for the management of 10
types of cabling and interfaces, and new features. This evolution Gigabit per second (Gb/s) Ethernet interfaces.
may require changes in the managed objects in order to reflect this
new functionality. This document, as with other documents issued by
this working group, reflects a certain stage in the evolution of
Ethernet technology. In the future, this document might be revised,
or new documents might be issued by the Ethernet Interfaces and Hub
MIB Working Group, in order to reflect the evolution of Ethernet
technology.
Distribution of this memo is unlimited. Please forward comments to Distribution of this memo is unlimited. Please forward comments to
hubmib@ietf.org. hubmib@ietf.org.
Table of Contents Table of Contents
1. Introduction ................................................ 3 1. Introduction ................................................ 2
2. The SNMP Management Framework .............................. 3 2. The Internet-Standard Management Framework ................. 3
3. Overview ................................................... 4 3. Overview ................................................... 3
3.1. Relation to MIB-2 ........................................ 5 3.1. Relation to MIB-2 ........................................ 4
3.2. Relation to the Interfaces MIB ........................... 5 3.2. Relation to the Interfaces MIB ........................... 4
3.2.1. Layering Model ......................................... 5 3.2.1. Layering Model ......................................... 5
3.2.2. Virtual Circuits ....................................... 6 3.2.2. Virtual Circuits ....................................... 5
3.2.3. ifRcvAddressTable ...................................... 6 3.2.3. ifRcvAddressTable ...................................... 5
3.2.4. ifType ................................................. 6 3.2.4. ifType ................................................. 5
3.2.5. ifXxxOctets ............................................ 7 3.2.5. ifXxxOctets ............................................ 6
3.2.6. ifXxxXcastPkts ......................................... 8 3.2.6. ifXxxXcastPkts ......................................... 7
3.2.7. ifMtu .................................................. 9 3.2.7. ifMtu .................................................. 8
3.2.8. ifSpeed and ifHighSpeed ................................ 10 3.2.8. ifSpeed and ifHighSpeed ................................ 9
3.2.9. ifPhysAddress .......................................... 10 3.2.9. ifPhysAddress .......................................... 9
3.2.10. Specific Interface MIB Objects ........................ 11 3.2.10. Specific Interface MIB Objects ........................ 10
3.3. Relation to the 802.3 MAU MIB ............................ 14 3.3. Relation to the 802.3 MAU MIB ............................ 13
3.4. dot3StatsEtherChipSet .................................... 14 3.4. dot3StatsEtherChipSet .................................... 13
3.5. Mapping of IEEE 802.3 Managed Objects .................... 15 3.5. Mapping of IEEE 802.3 Managed Objects .................... 14
4. Definitions ................................................ 18 4. Definitions ................................................ 17
5. Intellectual Property ...................................... 54 5. Intellectual Property ...................................... 55
6. Acknowledgements ........................................... 55 6. Acknowledgements ........................................... 56
7. References ................................................. 56 7. Normative References ....................................... 57
8. Security Considerations .................................... 59 8. Informative References ..................................... 58
9. Author's Address ........................................... 60 9. Security Considerations .................................... 59
A. Change Log ................................................. 60 10. IANA Considerations ....................................... 60
A.1. Changes since RFC 2665 ................................... 60 11. Author's Address .......................................... 60
A.2. Changes between RFC 2358 and RFC 2665 .................... 61 A. Change Log ................................................. 61
A.3. Changes between RFC 1650 and RFC 2358 .................... 62 A.1. Changes since RFC 2665 ................................... 61
A.2. Changes between RFC 2358 and RFC 2665 .................... 62
A.3. Changes between RFC 1650 and RFC 2358 .................... 63
B. Full Copyright Statement ................................... 63 B. Full Copyright Statement ................................... 63
1. Introduction 1. Introduction
This memo defines a portion of the Management Information Base (MIB) This memo defines a portion of the Management Information Base (MIB)
for use with network management protocols in the Internet community. for use with network management protocols in the Internet community.
In particular, it defines objects for managing Ethernet-like In particular, it defines objects for managing Ethernet-like
interfaces. interfaces.
This memo also includes a MIB module. This MIB module updates the This memo also includes a MIB module. This MIB module updates the
list of managed objects specified in the earlier version of this MIB, list of managed objects specified in the earlier version of this MIB,
RFC 2665 [RFC2665]. module, RFC 2665 [RFC2665].
Ethernet technology, as defined by the 802.3 Working Group of the
IEEE, continues to evolve, with scalable increases in speed, new
types of cabling and interfaces, and new features. This evolution
may require changes in the managed objects in order to reflect this
new functionality. This document, as with other documents issued by
this working group, reflects a certain stage in the evolution of
Ethernet technology. In the future, this document might be revised,
or new documents might be issued by the Ethernet Interfaces and Hub
MIB Working Group, in order to reflect the evolution of Ethernet
technology.
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", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
2. The SNMP Management Framework 2. The Internet-Standard Management Framework
The SNMP Management Framework presently consists of five major
components:
o An overall architecture, described in RFC 2571 [RFC2571].
o Mechanisms for describing and naming objects and events for the
purpose of management. The first version of this Structure of
Management Information (SMI) is called SMIv1 and described in
STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC
1215 [RFC1215]. The second version, called SMIv2, is described
in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and
STD 58, RFC 2580 [RFC2580].
o Message protocols for transferring management information. The
first version of the SNMP message protocol is called SNMPv1 and
described in STD 15, RFC 1157 [RFC1157]. A second version of
the SNMP message protocol, which is not an Internet standards
track protocol, is called SNMPv2c and described in RFC 1901
[RFC1901] and RFC 1906 [RFC1906]. The third version of the
message protocol is called SNMPv3 and described in RFC 1906
[RFC1906], RFC 2572 [RFC2572] and RFC 2574 [RFC2574].
o Protocol operations for accessing management information. The
first set of protocol operations and associated PDU formats is
described in STD 15, RFC 1157 [RFC1157]. A second set of
protocol operations and associated PDU formats is described in
RFC 1905 [RFC1905].
o A set of fundamental applications described in RFC 2573
[RFC2573] and the view-based access control mechanism described
in RFC 2575 [RFC2575].
A more detailed introduction to the current SNMP Management Framework For a detailed overview of the documents that describe the current
can be found in RFC 2570 [RFC2570]. Internet-Standard Management Framework, please refer to section 7 of
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. Objects in the MIB are the Management Information Base or MIB. MIB objects are generally
defined using the mechanisms defined in the SMI. accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the
This memo specifies a MIB module that is compliant to the SMIv2. A Structure of Management Information (SMI). This memo specifies a MIB
MIB conforming to the SMIv1 can be produced through the appropriate module that is compliant to the SMIv2, which is described in STD 58,
translations. The resulting translated MIB must be semantically RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
equivalent, except where objects or events are omitted because no [RFC2580].
translation is possible (use of Counter64). Some machine readable
information in SMIv2 will be converted into textual descriptions in
SMIv1 during the translation process. However, this loss of machine
readable information is not considered to change the semantics of the
MIB.
3. Overview 3. Overview
Instances of these object types represent attributes of an interface Instances of these object types represent attributes of an interface
to an ethernet-like communications medium. At present, ethernet-like to an ethernet-like communications medium. At present, ethernet-like
media are identified by the value ethernetCsmacd(6) of the ifType media are identified by the value ethernetCsmacd(6) of the ifType
object in the Interfaces MIB [RFC2863]. Some older implementations object in the Interfaces MIB [RFC2863]. Some older implementations
may return the values iso88023Csmacd(7) or starLan(11) for ifType for may return the values iso88023Csmacd(7) or starLan(11) for ifType for
ethernet-like media. ethernet-like media.
The definitions presented here are based on Section 30, "10 Mb/s, 100 The definitions presented here are based on Section 30, "10 Mb/s, 100
Mb/s 1000 Mb/s and 10 Gb/s Management", and Annex 30A, "GDMO Mb/s 1000 Mb/s and 10 Gb/s Management", and Annex 30A, "GDMO
Specification for 802.3 managed object classes" of IEEE Std. 802.3, Specification for 802.3 managed object classes" of IEEE Std. 802.3,
2000 Edition [IEEE802.3], amended by IEEE Draft P802.3ae/D4.3 2002 Edition [IEEE802.3], amended by IEEE Std. 802.3ae-2002
[P802.3ae], as originally interpreted by Frank Kastenholz, then of [IEEE802.3ae], as originally interpreted by Frank Kastenholz, then of
Interlan in [KASTEN]. Implementors of these MIB objects should note Interlan in [KASTEN]. Implementors of these MIB objects should note
that IEEE Std. 802.3 [IEEE802.3] explicitly describes (in the form of that IEEE Std. 802.3 [IEEE802.3] explicitly describes (in the form of
Pascal pseudocode) when, where, and how various MAC attributes are Pascal pseudocode) when, where, and how various MAC attributes are
measured. The IEEE document also describes the effects of MAC actions measured. The IEEE document also describes the effects of MAC actions
that may be invoked by manipulating instances of the MIB objects that may be invoked by manipulating instances of the MIB objects
defined here. defined here.
To the extent that some of the attributes defined in [IEEE802.3] are To the extent that some of the attributes defined in [IEEE802.3] are
represented by previously defined objects in MIB-2 [RFC1213] or in represented by previously defined objects in MIB-2 [RFC1213] or in
the Interfaces MIB [RFC2863], such attributes are not redundantly the Interfaces MIB [RFC2863], such attributes are not redundantly
skipping to change at page 18, line 11 skipping to change at page 17, line 19
oPAUSEEntity oPAUSEEntity
.aPAUSELinkDelayAllowance Not considered useful. .aPAUSELinkDelayAllowance Not considered useful.
4. Definitions 4. Definitions
EtherLike-MIB DEFINITIONS ::= BEGIN EtherLike-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY, MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY,
Counter32, Counter64, mib-2, transmission Integer32, Counter32, Counter64, mib-2, transmission
FROM SNMPv2-SMI FROM SNMPv2-SMI
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
TruthValue TruthValue
FROM SNMPv2-TC FROM SNMPv2-TC
ifIndex, InterfaceIndex ifIndex, InterfaceIndex
FROM IF-MIB; FROM IF-MIB;
etherMIB MODULE-IDENTITY etherMIB MODULE-IDENTITY
LAST-UPDATED "200205100000Z" -- May 10, 2002 LAST-UPDATED "200302280000Z" -- February 28, 2003
ORGANIZATION "IETF Ethernet Interfaces and Hub MIB ORGANIZATION "IETF Ethernet Interfaces and Hub MIB
Working Group" Working Group"
CONTACT-INFO CONTACT-INFO
"WG E-mail: hubmib@ietf.org "WG E-mail: hubmib@ietf.org
To subscribe: hubmib-request@ietf.org To subscribe: hubmib-request@ietf.org
Chair: Dan Romascanu Chair: Dan Romascanu
Postal: Avaya Inc. Postal: Avaya Inc.
Atidum Technology Park, Bldg. 3 Atidum Technology Park, Bldg. 3
Tel Aviv 61131 Tel Aviv 61131
skipping to change at page 18, line 52 skipping to change at page 18, line 13
Fax: +1 916 785 1199 Fax: +1 916 785 1199
E-mail: johnf@rose.hp.com" E-mail: johnf@rose.hp.com"
DESCRIPTION "The MIB module to describe generic objects for DESCRIPTION "The MIB module to describe generic objects for
ethernet-like network interfaces. ethernet-like network interfaces.
The following reference is used throughout this The following reference is used throughout this
MIB module: MIB module:
[IEEE 802.3 Std] refers to: [IEEE 802.3 Std] refers to:
IEEE Std 802.3, 2000 Edition: 'IEEE Standard IEEE Std 802.3, 2002 Edition: 'IEEE Standard
for Information technology - for Information technology -
Telecommunications and information exchange Telecommunications and information exchange
between systems - Local and metropolitan between systems - Local and metropolitan
area networks - Specific requirements - area networks - Specific requirements -
Part 3: Carrier sense multiple access with Part 3: Carrier sense multiple access with
collision detection (CSMA/CD) access method collision detection (CSMA/CD) access method
and physical layer specifications', as and physical layer specifications', as
amended by IEEE Draft P802.3ae/D4.3: amended by IEEE Std 802.3ae-2002:
'Supplement to Carrier Sense Multiple Access 'Amendment: Media Access Control (MAC)
with Collision Detection (CSMA/CD) Access Parameters, Physical Layer, and Management
Method & Physical Layer Specifications - Parameters for 10 Gb/s Operation', August,
Media Access Control (MAC) Parameters, 2002.
Physical Layer, and Management Parameters
for 10 Gb/s Operation', April, 2002.
Of particular interest is Clause 30, '10 Mb/s, Of particular interest is Clause 30, '10 Mb/s,
100 Mb/s, 1000 Mb/s, and 10 Gb/s Management'." 100 Mb/s, 1000 Mb/s, and 10 Gb/s Management'.
REVISION "200205100000Z" -- May 10, 2002 Copyright (C) The Internet Society (2003). This
version of this MIB module is part of RFC XXXX;
see the RFC itself for full legal notices."
-- RFC Ed.: Replace XXXX with the actual RFC number & remove
-- this note
REVISION "200302280000Z" -- February 28, 2003
DESCRIPTION "Updated to include support for 10 Gb/sec DESCRIPTION "Updated to include support for 10 Gb/sec
interfaces. interfaces. This resulted in the following
revisions:
- Updated dot3StatsAlignmentErrors and
dot3StatsSymbolErrors DESCRIPTIONs to
reflect behaviour at 10 Gb/s
- Added dot3StatsRateControlAbility and
dot3RateControlStatus for management
of the Rate Control function in 10 Gb/s
WAN applications
- Added 64-bit versions of all counters
that are used on high-speed ethernet
interfaces
- Added object groups to contain the new
objects
- Deprecated etherStatsBaseGroup and
split into etherStatsBaseGroup2 and
etherStatsHalfDuplexGroup, so that
interfaces which can only operate at
full-duplex do not need to implement
half-duplex-only statistics
- Deprecated dot3Compliance and replaced
it with dot3Compliance2, which includes
the compliance information for the new
object groups
In addition, the dot3Tests and dot3Errors
object identities have been deprecated,
since there is no longer a standard method
for using them.
This version published as RFC XXXX." This version published as RFC XXXX."
-- RFC Ed.: Replace XXXX with the actual RFC number & remove
-- this note
REVISION "9908240400Z" -- August 24, 1999 REVISION "199908240400Z" -- August 24, 1999
DESCRIPTION "Updated to include support for 1000 Mb/sec DESCRIPTION "Updated to include support for 1000 Mb/sec
interfaces and full-duplex interfaces. interfaces and full-duplex interfaces.
This version published as RFC 2665." This version published as RFC 2665."
REVISION "9806032150Z" -- June 3, 1998 REVISION "199806032150Z" -- June 3, 1998
DESCRIPTION "Updated to include support for 100 Mb/sec DESCRIPTION "Updated to include support for 100 Mb/sec
interfaces. interfaces.
This version published as RFC 2358." This version published as RFC 2358."
REVISION "9402030400Z" -- February 3, 1994 REVISION "199402030400Z" -- February 3, 1994
DESCRIPTION "Initial version, published as RFC 1650." DESCRIPTION "Initial version, published as RFC 1650."
::= { mib-2 35 } ::= { mib-2 35 }
etherMIBObjects OBJECT IDENTIFIER ::= { etherMIB 1 } etherMIBObjects OBJECT IDENTIFIER ::= { etherMIB 1 }
dot3 OBJECT IDENTIFIER ::= { transmission 7 } dot3 OBJECT IDENTIFIER ::= { transmission 7 }
-- the Ethernet-like Statistics group -- the Ethernet-like Statistics group
dot3StatsTable OBJECT-TYPE dot3StatsTable OBJECT-TYPE
skipping to change at page 20, line 42 skipping to change at page 20, line 40
dot3StatsInternalMacReceiveErrors Counter32, dot3StatsInternalMacReceiveErrors Counter32,
dot3StatsEtherChipSet OBJECT IDENTIFIER, dot3StatsEtherChipSet OBJECT IDENTIFIER,
dot3StatsSymbolErrors Counter32, dot3StatsSymbolErrors Counter32,
dot3StatsDuplexStatus INTEGER, dot3StatsDuplexStatus INTEGER,
dot3StatsRateControlAbility TruthValue, dot3StatsRateControlAbility TruthValue,
dot3StatsRateControlStatus INTEGER dot3StatsRateControlStatus INTEGER
} }
dot3StatsIndex OBJECT-TYPE dot3StatsIndex OBJECT-TYPE
SYNTAX InterfaceIndex SYNTAX InterfaceIndex
MAX-ACCESS read-only MAX-ACCESS read-only -- read-only since originally an
-- SMIv1 index
STATUS current STATUS current
DESCRIPTION "An index value that uniquely identifies an DESCRIPTION "An index value that uniquely identifies an
interface to an ethernet-like medium. The interface to an ethernet-like medium. The
interface identified by a particular value of interface identified by a particular value of
this index is the same interface as identified this index is the same interface as identified
by the same value of ifIndex." by the same value of ifIndex."
REFERENCE "RFC 2863, ifIndex" REFERENCE "RFC 2863, ifIndex"
::= { dot3StatsEntry 1 } ::= { dot3StatsEntry 1 }
dot3StatsAlignmentErrors OBJECT-TYPE dot3StatsAlignmentErrors OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "A count of frames received on a particular DESCRIPTION "A count of frames received on a particular
interface that are not an integral number of interface that are not an integral number of
octets in length and do not pass the FCS check. octets in length and do not pass the FCS check.
The count represented by an instance of this The count represented by an instance of this
object is incremented when the alignmentError object is incremented when the alignmentError
skipping to change at page 29, line 4 skipping to change at page 28, line 48
This object contains an OBJECT IDENTIFIER This object contains an OBJECT IDENTIFIER
which identifies the chipset used to which identifies the chipset used to
realize the interface. Ethernet-like realize the interface. Ethernet-like
interfaces are typically built out of interfaces are typically built out of
several different chips. The MIB implementor several different chips. The MIB implementor
is presented with a decision of which chip is presented with a decision of which chip
to identify via this object. The implementor to identify via this object. The implementor
should identify the chip which is usually should identify the chip which is usually
called the Medium Access Control chip. called the Medium Access Control chip.
If no such chip is easily identifiable, If no such chip is easily identifiable,
the implementor should identify the chip the implementor should identify the chip
which actually gathers the transmit which actually gathers the transmit
and receive statistics and error and receive statistics and error
indications. This would allow a indications. This would allow a
manager station to correlate the manager station to correlate the
statistics and the chip generating statistics and the chip generating
them, giving it the ability to take them, giving it the ability to take
into account any known anomalies into account any known anomalies
in the chip." in the chip.
This object has been deprecated. Implementation
feedback indicates that it is of limited use for
debugging network problems in the field, and
the administrative overhead involved in
maintaining a registry of chipset OIDs is not
justified."
::= { dot3StatsEntry 17 } ::= { dot3StatsEntry 17 }
dot3StatsSymbolErrors OBJECT-TYPE dot3StatsSymbolErrors OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "For an interface operating at 100 Mb/s, the DESCRIPTION "For an interface operating at 100 Mb/s, the
number of times there was an invalid data symbol number of times there was an invalid data symbol
when a valid carrier was present. when a valid carrier was present.
skipping to change at page 32, line 26 skipping to change at page 32, line 29
instance of this object represents the instance of this object represents the
frequency of individual MAC frames for which frequency of individual MAC frames for which
the transmission (successful or otherwise) on a the transmission (successful or otherwise) on a
particular interface is accompanied by a particular interface is accompanied by a
particular number of media collisions." particular number of media collisions."
INDEX { ifIndex, dot3CollCount } INDEX { ifIndex, dot3CollCount }
::= { dot3CollTable 1 } ::= { dot3CollTable 1 }
Dot3CollEntry ::= Dot3CollEntry ::=
SEQUENCE { SEQUENCE {
dot3CollCount INTEGER, dot3CollCount Integer32,
dot3CollFrequencies Counter32 dot3CollFrequencies Counter32
} }
-- { dot3CollEntry 1 } is no longer in use -- { dot3CollEntry 1 } is no longer in use
dot3CollCount OBJECT-TYPE dot3CollCount OBJECT-TYPE
SYNTAX INTEGER (1..16) SYNTAX Integer32 (1..16)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION "The number of per-frame media collisions for DESCRIPTION "The number of per-frame media collisions for
which a particular collision histogram cell which a particular collision histogram cell
represents the frequency on a particular represents the frequency on a particular
interface." interface."
::= { dot3CollEntry 2 } ::= { dot3CollEntry 2 }
dot3CollFrequencies OBJECT-TYPE dot3CollFrequencies OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
skipping to change at page 45, line 23 skipping to change at page 45, line 23
-- 802.3 Tests -- 802.3 Tests
dot3Tests OBJECT IDENTIFIER ::= { dot3 6 } dot3Tests OBJECT IDENTIFIER ::= { dot3 6 }
dot3Errors OBJECT IDENTIFIER ::= { dot3 7 } dot3Errors OBJECT IDENTIFIER ::= { dot3 7 }
-- TDR Test -- TDR Test
dot3TestTdr OBJECT-IDENTITY dot3TestTdr OBJECT-IDENTITY
STATUS deprecated STATUS deprecated
DESCRIPTION "The Time-Domain Reflectometry (TDR) test is DESCRIPTION "******** THIS IDENTITY IS DEPRECATED *******
The Time-Domain Reflectometry (TDR) test is
specific to ethernet-like interfaces of type specific to ethernet-like interfaces of type
10Base5 and 10Base2. The TDR value may be 10Base5 and 10Base2. The TDR value may be
useful in determining the approximate distance useful in determining the approximate distance
to a cable fault. It is advisable to repeat to a cable fault. It is advisable to repeat
this test to check for a consistent resulting this test to check for a consistent resulting
TDR value, to verify that there is a fault. TDR value, to verify that there is a fault.
A TDR test returns as its result the time A TDR test returns as its result the time
interval, measured in 10 MHz ticks or 100 nsec interval, measured in 10 MHz ticks or 100 nsec
units, between the start of TDR test units, between the start of TDR test
transmission and the subsequent detection of a transmission and the subsequent detection of a
collision or deassertion of carrier. On collision or deassertion of carrier. On
successful completion of a TDR test, the result successful completion of a TDR test, the result
is stored as the value of an appropriate is stored as the value of an appropriate
instance of an appropriate vendor specific MIB instance of an appropriate vendor specific MIB
object, and the OBJECT IDENTIFIER of that object, and the OBJECT IDENTIFIER of that
instance is stored in the appropriate instance instance is stored in the appropriate instance
of the appropriate test result code object of the appropriate test result code object
(thereby indicating where the result has been (thereby indicating where the result has been
stored)." stored).
This object identity has been deprecated, since
the ifTestTable in the IF-MIB was deprecated,
and there is no longer a standard mechanism for
initiating an interface test. This left no
standard way of using this object identity."
::= { dot3Tests 1 } ::= { dot3Tests 1 }
-- Loopback Test -- Loopback Test
dot3TestLoopBack OBJECT-IDENTITY dot3TestLoopBack OBJECT-IDENTITY
STATUS deprecated STATUS deprecated
DESCRIPTION "This test configures the MAC chip and executes DESCRIPTION "******** THIS IDENTITY IS DEPRECATED *******
This test configures the MAC chip and executes
an internal loopback test of memory, data paths, an internal loopback test of memory, data paths,
and the MAC chip logic. This loopback test can and the MAC chip logic. This loopback test can
only be executed if the interface is offline. only be executed if the interface is offline.
Once the test has completed, the MAC chip should Once the test has completed, the MAC chip should
be reinitialized for network operation, but it be reinitialized for network operation, but it
should remain offline. should remain offline.
If an error occurs during a test, the If an error occurs during a test, the
appropriate test result object will be set appropriate test result object will be set
to indicate a failure. The two OBJECT to indicate a failure. The two OBJECT
IDENTIFIER values dot3ErrorInitError and IDENTIFIER values dot3ErrorInitError and
dot3ErrorLoopbackError may be used to provided dot3ErrorLoopbackError may be used to provided
more information as values for an appropriate more information as values for an appropriate
test result code object." test result code object.
This object identity has been deprecated, since
the ifTestTable in the IF-MIB was deprecated,
and there is no longer a standard mechanism for
initiating an interface test. This left no
standard way of using this object identity."
::= { dot3Tests 2 } ::= { dot3Tests 2 }
dot3ErrorInitError OBJECT-IDENTITY dot3ErrorInitError OBJECT-IDENTITY
STATUS deprecated STATUS deprecated
DESCRIPTION "Couldn't initialize MAC chip for test." DESCRIPTION "******** THIS IDENTITY IS DEPRECATED *******
Couldn't initialize MAC chip for test.
This object identity has been deprecated, since
the ifTestTable in the IF-MIB was deprecated,
and there is no longer a standard mechanism for
initiating an interface test. This left no
standard way of using this object identity."
::= { dot3Errors 1 } ::= { dot3Errors 1 }
dot3ErrorLoopbackError OBJECT-IDENTITY dot3ErrorLoopbackError OBJECT-IDENTITY
STATUS deprecated STATUS deprecated
DESCRIPTION "Expected data not received (or not received DESCRIPTION "******** THIS IDENTITY IS DEPRECATED *******
correctly) in loopback test." Expected data not received (or not received
correctly) in loopback test.
This object identity has been deprecated, since
the ifTestTable in the IF-MIB was deprecated,
and there is no longer a standard mechanism for
initiating an interface test. This left no
standard way of using this object identity."
::= { dot3Errors 2 } ::= { dot3Errors 2 }
-- { dot3 8 }, the dot3ChipSets tree, is defined in [31] -- { dot3 8 }, the dot3ChipSets tree, is defined in [RFC2666]
-- conformance information -- conformance information
etherConformance OBJECT IDENTIFIER ::= { etherMIB 2 } etherConformance OBJECT IDENTIFIER ::= { etherMIB 2 }
etherGroups OBJECT IDENTIFIER ::= { etherConformance 1 } etherGroups OBJECT IDENTIFIER ::= { etherConformance 1 }
etherCompliances OBJECT IDENTIFIER ::= { etherConformance 2 } etherCompliances OBJECT IDENTIFIER ::= { etherConformance 2 }
-- compliance statements -- compliance statements
skipping to change at page 47, line 45 skipping to change at page 48, line 27
metering. Implementation in such systems is metering. Implementation in such systems is
highly recommended." highly recommended."
::= { etherCompliances 2 } ::= { etherCompliances 2 }
dot3Compliance MODULE-COMPLIANCE dot3Compliance MODULE-COMPLIANCE
STATUS deprecated STATUS deprecated
DESCRIPTION "******** THIS COMPLIANCE IS DEPRECATED ******** DESCRIPTION "******** THIS COMPLIANCE IS DEPRECATED ********
The compliance statement for managed network The compliance statement for managed network
entities which have ethernet-like network entities which have ethernet-like network
interfaces." interfaces.
This compliance is deprecated and replaced by
dot3Compliance2."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { etherStatsBaseGroup } MANDATORY-GROUPS { etherStatsBaseGroup }
GROUP etherDuplexGroup GROUP etherDuplexGroup
DESCRIPTION "This group is mandatory for all DESCRIPTION "This group is mandatory for all
ethernet-like network interfaces which are ethernet-like network interfaces which are
capable of operating in full-duplex mode. capable of operating in full-duplex mode.
It is highly recommended for all It is highly recommended for all
ethernet-like network interfaces." ethernet-like network interfaces."
skipping to change at page 48, line 42 skipping to change at page 49, line 27
which are capable of operating in which are capable of operating in
half-duplex mode and have the necessary half-duplex mode and have the necessary
metering. Implementation in systems with metering. Implementation in systems with
such interfaces is highly recommended." such interfaces is highly recommended."
::= { etherCompliances 3 } ::= { etherCompliances 3 }
dot3Compliance2 MODULE-COMPLIANCE dot3Compliance2 MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION "The compliance statement for managed network DESCRIPTION "The compliance statement for managed network
entities which have ethernet-like network entities which have ethernet-like network
interfaces." interfaces.
Note that compliance with this MIB module
requires compliance with the ifCompliance3
MODULE-COMPLIANCE statement of the IF-MIB
[RFC2863]. In addition, compliance with this
MIB module requires compliance with the
mauModIfCompl3 MODULE-COMPLIANCE statement of
the MAU-MIB [MAU-MIB]."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { etherStatsBaseGroup2 } MANDATORY-GROUPS { etherStatsBaseGroup2 }
GROUP etherDuplexGroup GROUP etherDuplexGroup
DESCRIPTION "This group is mandatory for all DESCRIPTION "This group is mandatory for all
ethernet-like network interfaces which are ethernet-like network interfaces which are
capable of operating in full-duplex mode. capable of operating in full-duplex mode.
It is highly recommended for all It is highly recommended for all
ethernet-like network interfaces." ethernet-like network interfaces."
skipping to change at page 52, line 10 skipping to change at page 52, line 51
dot3StatsInternalMacTransmitErrors, dot3StatsInternalMacTransmitErrors,
dot3StatsCarrierSenseErrors, dot3StatsCarrierSenseErrors,
dot3StatsFrameTooLongs, dot3StatsFrameTooLongs,
dot3StatsInternalMacReceiveErrors dot3StatsInternalMacReceiveErrors
} }
STATUS deprecated STATUS deprecated
DESCRIPTION "********* THIS GROUP IS DEPRECATED ********** DESCRIPTION "********* THIS GROUP IS DEPRECATED **********
A collection of objects providing information A collection of objects providing information
applicable to all ethernet-like network applicable to all ethernet-like network
interfaces." interfaces.
This object group has been deprecated and
replaced by etherStatsBaseGroup2 and
etherStatsHalfDuplexGroup, to separate
objects which must be implemented by all
ethernet-like network interfaces from
objects that need only be implemented on
ethernet-like network interfaces that are
capable of half-duplex operation."
::= { etherGroups 4 } ::= { etherGroups 4 }
etherStatsLowSpeedGroup OBJECT-GROUP etherStatsLowSpeedGroup OBJECT-GROUP
OBJECTS { dot3StatsSQETestErrors } OBJECTS { dot3StatsSQETestErrors }
STATUS current STATUS current
DESCRIPTION "A collection of objects providing information DESCRIPTION "A collection of objects providing information
applicable to ethernet-like network interfaces applicable to ethernet-like network interfaces
capable of operating at 10 Mb/s or slower in capable of operating at 10 Mb/s or slower in
half-duplex mode." half-duplex mode."
::= { etherGroups 5 } ::= { etherGroups 5 }
skipping to change at page 55, line 20 skipping to change at page 56, line 21
6. Acknowledgements 6. Acknowledgements
This document was produced by the IETF Ethernet Interfaces and Hub This document was produced by the IETF Ethernet Interfaces and Hub
MIB Working Group, whose efforts were greatly advanced by the MIB Working Group, whose efforts were greatly advanced by the
contributions of the following people: contributions of the following people:
Ran Atkinson Ran Atkinson
Mike Ayers Mike Ayers
Mike Heard Mike Heard
Jeffrey Johnson
Lynn Kubinec Lynn Kubinec
Kam Lam Kam Lam
Kerry McDonald Kerry McDonald
Steve McRobert Steve McRobert
K.C. Norseth K.C. Norseth
Dan Romascanu Dan Romascanu
Randy Presuhn Randy Presuhn
Andrew Smith Andrew Smith
Kaj Tesink Kaj Tesink
Geoff Thompson Geoff Thompson
This document is based on the Proposed Standard Ethernet MIB, RFC This document is based on the Proposed Standard Ethernet MIB, RFC
2665 [RFC2665], edited by John Flick of Hewlett-Packard and Jeffrey 2665 [RFC2665], edited by John Flick of Hewlett-Packard and Jeffrey
Johnson of RedBack Networks and produced by the Ethernet Interfaces Johnson of RedBack Networks and produced by the Ethernet Interfaces
and Hub MIB Working Group. It extends that document by providing and Hub MIB Working Group. It extends that document by providing
support for 10 Gb/s Ethernet interfaces as defined in [P802.3ae]. support for 10 Gb/s Ethernet interfaces as defined in [IEEE802.3ae].
RFC 2665, in turn, is based on the Proposed Standard Ethernet MIB, RFC 2665, in turn, is based on the Proposed Standard Ethernet MIB,
RFC 2358 [RFC2358], edited by John Flick of Hewlett-Packard and RFC 2358 [RFC2358], edited by John Flick of Hewlett-Packard and
Jeffrey Johnson of RedBack Networks and produced by the 802.3 Hub MIB Jeffrey Johnson of RedBack Networks and produced by the 802.3 Hub MIB
Working Group. It extends that document by providing support for Working Group. It extends that document by providing support for
full-duplex Ethernet interfaces and 1000 Mb/sec Ethernet interfaces full-duplex Ethernet interfaces and 1000 Mb/sec Ethernet interfaces
as outlined in [IEEE802.3]. as outlined in [IEEE802.3].
RFC 2358, in turn, is almost completely based on both the Standard RFC 2358, in turn, is almost completely based on both the Standard
Ethernet MIB, RFC 1643 [RFC1643], and the Proposed Standard Ethernet Ethernet MIB, RFC 1643 [RFC1643], and the Proposed Standard Ethernet
skipping to change at page 56, line 28 skipping to change at page 57, line 31
by the Transmission Working Group, to reflect the current conventions by the Transmission Working Group, to reflect the current conventions
for defining objects for MIB interfaces. James Davin, of the MIT for defining objects for MIB interfaces. James Davin, of the MIT
Laboratory for Computer Science, and Keith McCloghrie of Hughes LAN Laboratory for Computer Science, and Keith McCloghrie of Hughes LAN
Systems, contributed to later drafts of this memo. Marshall Rose of Systems, contributed to later drafts of this memo. Marshall Rose of
Performance Systems International, Inc. converted the document into Performance Systems International, Inc. converted the document into
RFC 1212 [RFC1212] concise format. Anil Rijsinghani of DEC RFC 1212 [RFC1212] concise format. Anil Rijsinghani of DEC
contributed text that more adequately describes the TDR test. Thanks contributed text that more adequately describes the TDR test. Thanks
to Frank Kastenholz of Interlan and Louis Steinberg of IBM for their to Frank Kastenholz of Interlan and Louis Steinberg of IBM for their
experimentation. experimentation.
7. References 7. Normative References
Normative References [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirements Levels", BCP 14, RFC 2119, March 1997.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
J., Rose, M. and S. Waldbusser, "Structure of Management J., Rose, M. and S. Waldbusser, "Structure of
Information Version 2 (SMIv2)", STD 58, RFC 2578, April Management Information Version 2 (SMIv2)", STD 58, RFC
1999. 2578, April 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
J., Rose, M. and S. Waldbusser, "Textual Conventions for J., Rose, M. and S. Waldbusser, "Textual Conventions
SMIv2", STD 58, RFC 2579, April 1999. for SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
J., Rose, M. and S. Waldbusser, "Conformance Statements J., Rose, M. and S. Waldbusser, "Conformance Statements
for SMIv2", STD 58, RFC 2580, April 1999. for SMIv2", STD 58, RFC 2580, April 1999.
[IEEE802.3] IEEE, IEEE Std 802.3, 2000 Edition: "Information [IEEE802.3] IEEE, IEEE Std 802.3, 2002 Edition: "Carrier Sense
technology - Telecommunications and information exchange Multiple Access with Collision Detection (CSMA/CD)
between systems - Local and metropolitan area networks - Access Method and Physical Layer Specifications",
Specific requirements - Part 3: Carrier sense multiple March 2002.
access with collision detection (CSMA/CD) access method
and physical layer specifications", (Adopted by ISO/IEC
and redesignated as ISO/IEC 8802-3:2000(E), 2000.
[P802.3ae] Law, D., Editor, Draft Supplement to IEEE Std. 802.3, [IEEE802.3ae] IEEE, IEEE Std 802.3ae-2002, "Amendment: Media
IEEE Draft P802.3ae/D4.3, April 2002, work in Access Control (MAC) Parameters, Physical Layers,
progress. and Management Parameters for 10 Gb/s Operation",
August, 2002.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces
MIB using SMIv2", RFC 2863, June 2000. Group MIB using SMIv2", RFC 2863, June 2000.
[MAU-MIB] Flick, J., "Definitions of Managed Objects for IEEE [MAU-MIB] Flick, J., "Definitions of Managed Objects for IEEE
802.3 Medium Attachment Units (MAUs) using SMIv2", work 802.3 Medium Attachment Units (MAUs) using SMIv2", work
in progress, draft-ietf-hubmib-mau-mib-v3-02.txt, in progress, draft-ietf-hubmib-mau-mib-v3-03.txt,
May 2002. March 2003.
Non-Normative References
[RFC2571] Harrington, D., Presuhn, R. and B. Wijnen, "An
Architecture for Describing SNMP Management Frameworks",
RFC 2571, April 1999.
[RFC1155] Rose, M. and K. McCloghrie, "Structure and
Identification of Management Information for
TCP/IP-based Internets", STD 16, RFC 1155, May 1990.
[RFC1212] Rose, M. and K. McCloghrie, "Concise MIB Definitions",
STD 16, RFC 1212, March 1991.
[RFC1215] Rose, M., "A Convention for Defining Traps for use with
the SNMP", RFC 1215, March 1991.
[RFC1157] Case, J., Fedor, M., Schoffstall, M. and J. Davin,
"Simple Network Management Protocol", STD 15, RFC 1157,
May 1990.
[RFC1901] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser,
"Introduction to Community-based SNMPv2", RFC 1901,
January 1996.
[RFC1906] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser,
"Transport Mappings for Version 2 of the Simple Network
Management Protocol (SNMPv2)", RFC 1906, January 1996.
[RFC2572] Case, J., Harrington, D., Presuhn R. and B. Wijnen,
"Message Processing and Dispatching for the Simple
Network Management Protocol (SNMP)", RFC 2572, May 1999.
[RFC2574] Blumenthal, U. and B. Wijnen, "User-based Security Model
(USM) for version 3 of the Simple Network Management
Protocol (SNMPv3)", RFC 2574, May 1999.
[RFC1905] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser,
"Protocol Operations for Version 2 of the Simple Network
Management Protocol (SNMPv2)", RFC 1905, January 1996.
[RFC2573] Levi, D., Meyer, P. and B. Stewart, "SNMPv3
Applications", RFC 2573, May 1999.
[RFC2575] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based 8. Informative References
Access Control Model (VACM) for the Simple Network
Management Protocol (SNMP)", RFC 2575, May 1999.
[RFC2570] Case, J., Mundy, R., Partain, D. and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart,
"Introduction to Version 3 of the Internet-Standard "Introduction and Applicability Statements for
Network Management Framework", RFC 2570, April 1999. Internet-Standard Network Management Framework",
RFC 3410, December 2002.
[KASTEN] Kastenholz, F., "IEEE 802.3 Layer Management Draft [KASTEN] Kastenholz, F., "IEEE 802.3 Layer Management Draft
compatible MIB for TCP/IP Networks", electronic mail compatible MIB for TCP/IP Networks", electronic mail
message to mib-wg@nnsc.nsf.net, 9 June 1989. message to mib-wg@nnsc.nsf.net, 9 June 1989.
[RFC1284] Cook, J., "Definitions of Managed Objects for [RFC1284] Cook, J., "Definitions of Managed Objects for
Ethernet-Like Interface Types", RFC 1284, December 1991. Ethernet-Like Interface Types", RFC 1284, December 1991.
[RFC1369] Kastenholz, F., "Implementation Notes and Experience for [RFC1369] Kastenholz, F., "Implementation Notes and Experience for
The Internet Ethernet MIB", RFC 1369, October 1992. The Internet Ethernet MIB", RFC 1369, October 1992.
skipping to change at page 60, line ? skipping to change at page 59, line 13
2358, June 1998. 2358, June 1998.
[RFC2665] Flick, J., and J. Johnson, "Definitions of Managed [RFC2665] Flick, J., and J. Johnson, "Definitions of Managed
Objects for the Ethernet-like Interface Types", RFC Objects for the Ethernet-like Interface Types", RFC
2665, August 1999. 2665, August 1999.
[RFC1213] McCloghrie, K. and M. Rose, Editors, "Management [RFC1213] McCloghrie, K. and M. Rose, Editors, "Management
Information Base for Network Management of TCP/IP-based Information Base for Network Management of TCP/IP-based
internets: MIB-II", STD 17, RFC 1213, March 1991. internets: MIB-II", STD 17, RFC 1213, March 1991.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirements Levels", BCP 14, RFC 2119, March 1997.
[RFC2666] Flick, J., "Definitions of Object Identifiers for [RFC2666] Flick, J., "Definitions of Object Identifiers for
Identifying Ethernet Chip Sets", RFC 2666, August 1999. Identifying Ethernet Chip Sets", RFC 2666, August 1999.
[ETHERWIS] Ayers, M., Flick, J., Heard, C. M., Lam, K., McDonald, [ETHERWIS] Heard, C. M., "Definitions of Managed Objects for the
K., Norseth, K. C., and K. Tesink, "Definitions of Ethernet WAN Interface Sublayer", work in progress,
Managed Objects for the Ethernet WAN Interface draft-ietf-hubmib-wis-mib-06.txt, January 2003.
Sublayer", work in progress,
draft-ietf-hubmib-wis-mib-04.txt, May 2002.
[CASE] Case, J., and C. Partridge, "Case Diagrams: A First Step [CASE] Case, J., and C. Partridge, "Case Diagrams: A First Step
to Diagrammed Management Information Bases", Computer to Diagrammed Management Information Bases", Computer
Communications Review, 19(1):13-16, January 1989. Communications Review, 19(1):13-16, January 1989.
8. Security Considerations 9. Security Considerations
There are two management objects defined in this MIB that have a There is one management object defined in this MIB that has a MAX-
MAX-ACCESS clause of read-write. Such objects may be considered ACCESS clause of read-write. That object, dot3PauseAdminMode, may be
sensitive or vulnerable in some network environments. The support used to change the flow control configuration on a network interface,
for SET operations in a non-secure environment without proper which may result in dropped packets, or sending flow control packets
protection can have a negative effect on network operations. on links where the link partner will not understand them. Either
action could be detrimental to network performance.
There are a number of managed objects in this MIB that may be Such objects may be considered sensitive or vulnerable in some
considered to contain sensitive information. In particular, the network environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on
network operations.
Some of the readable objects in this MIB module (i.e., objects with a
MAX-ACCESS other than not-accessible) may be considered sensitive or
vulnerable in some network environments. In particular, the
dot3StatsEtherChipSet object may be considered sensitive in many dot3StatsEtherChipSet object may be considered sensitive in many
environments, since it would allow an intruder to obtain information environments, since it would allow an intruder to obtain information
about which vendor's equipment is in use on the network. Note that about which vendor's equipment is in use on the network. Note that
this object has been deprecated. However, some implementors may this object has been deprecated. However, some implementors may
still choose to implement it for backwards compatability. still choose to implement it for backwards compatability.
Therefore, it may be important in some environments to control read Most of the objects in this MIB module contain statistical
access to these objects and possibly to even encrypt the values of information about particular network links. In some network
these objects when sending them over the network via SNMP. Not all environments, this information may be considered sensitive.
versions of SNMP provide features for such a secure environment.
SNMPv1 by itself is such an insecure environment. Even if the It is thus important to control even GET and/or NOTIFY access to
network itself is secure (for example by using IPSec), even then, these objects and possibly to even encrypt the values of these
there is no control as to who on the secure network is allowed to objects when sending them over the network via SNMP.
access and GET (read) the objects in this MIB.
SNMP versions prior to SNMPv3 did not include adequate security.
Even if the network itself is secure (for example by using IPSec),
even then, 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.
It is recommended that the implementors consider the security It is recommended that the implementors consider the security
features as provided by the SNMPv3 framework. Specifically, the use features as provided by the SNMPv3 framework (see [RFC3410], section
of the User-based Security Model RFC 2574 [RFC2574] and the View- 8), including full support for the SNMPv3 cryptographic mechanisms
(for authentication and privacy).
Flick Expires November 2002 [Page 59]e Furthermore, deployment of SNMP versions prior to SNMPv3 is NOT
based Access Control Model RFC 2575 [RFC2575] is recommended. 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.
It is then a customer/user responsibility to ensure that the SNMP 10. IANA Considerations
entity giving access to an instance of this MIB, is properly
configured to give access to those objects only to those principals
(users) that have legitimate rights to access them.
9. Author's Address This document does not define any new name space to be administered
by IANA. However, section 3.2.4 does specify that some of the
defined values in a current IANA-maintained name space are to be
marked as deprecated or obsolete. In particular, the following
enumerated values in the IANAifType TEXTUAL-CONVENTION in the
IANAifType-MIB module need to have an ASN.1 comment added stating
that they have been deprecated:
- iso88032Csmacd(7)
- starLan(11)
In addition, the following enumerated values need to have an ASN.1
comment added stating that they are obsolete:
- fastEther(62)
- fastEtherFX(69)
- gigabitEthernet(117)
In all of the above cases, the ASN.1 comment should indicate that
ethernetCsmacd(6) should be used instead of these values.
11. Author's Address
John Flick John Flick
Hewlett-Packard Company Hewlett-Packard Company
8000 Foothills Blvd. M/S 5557 8000 Foothills Blvd. M/S 5557
Roseville, CA 95747-5557 Roseville, CA 95747-5557
Phone: +1 916 785 4018 Phone: +1 916 785 4018
Email: johnf@rose.hp.com Email: johnf@rose.hp.com
A. Change Log A. Change Log
A.1. Changes since RFC 2665 A.1. Changes since RFC 2665
This section enumerates changes made to RFC 2665 to produce this This section enumerates changes made to RFC 2665 to produce this
document. document.
(1) Updated references to the IEEE 802.3 standard to (1) Updated references to the IEEE 802.3 standard to
refer to the 2000 edition. refer to the 2002 edition.
(2) Added reference to 802.3ae. (2) Added reference to IEEE 802.3ae-2002.
(3) Updated WG e-mail address. (3) Updated WG e-mail address.
(4) The following DESCRIPTION clauses have been updated (4) The following DESCRIPTION clauses have been updated
to reflect behaviour on 10 Gb/s interfaces: to reflect behaviour on 10 Gb/s interfaces:
dot3StatsAlignmentErrors and dot3StatsSymbolErrors. dot3StatsAlignmentErrors and dot3StatsSymbolErrors.
(5) The following objects have been added for management (5) The following objects have been added for management
of the Rate Control function in WAN applications of of the Rate Control function in WAN applications of
ethernet: dot3StatsRateControlAbility and ethernet: dot3StatsRateControlAbility and
dot3StatsRateControlStatus. dot3StatsRateControlStatus.
(6) The following 64-bit counters have been added to (6) The following 64-bit counters have been added to
support operation on high-speed ethernet interfaces: support operation on high-speed ethernet interfaces:
dot3HCControlInUnknownOpcodes, dot3HCInPauseFrames, dot3HCControlInUnknownOpcodes, dot3HCInPauseFrames,
dot3HCOutPauseFrames, dot3HCStatsAlignmentErrors, dot3HCOutPauseFrames, dot3HCStatsAlignmentErrors,
dot3HCStatsFCSErrors, dot3HCStatsFrameTooLongs, dot3HCStatsFCSErrors, dot3HCStatsFrameTooLongs,
dot3HCStatsInternalMacTransmitErrors, dot3HCStatsInternalMacTransmitErrors,
dot3HCStatsInternalMacReceiveErrors, dot3HCStatsInternalMacReceiveErrors,
dot3StatsSymbolErrors dot3HCStatsSymbolErrors
(7) Object groups and compliances have been added to (7) Object groups and compliances have been added to
contain the new objects. contain the new objects.
(8) The MODULE-IDENTITY clause has been updated to (8) The MODULE-IDENTITY clause has been updated to
reflect the changes in the MIB module. reflect the changes in the MIB module.
(9) Use of the various ifType values for ethernet has (9) Use of the various ifType values for ethernet has
been clarified to emphasize that all ethernet-like been clarified to emphasize that all ethernet-like
interfaces must use the ethernetCsmacd ifType. interfaces must use the ethernetCsmacd ifType.
skipping to change at page 63, line 12 skipping to change at page 64, line 4
(11) Converted the dot3Tests, dot3Errors, and dot3ChipSets (11) Converted the dot3Tests, dot3Errors, and dot3ChipSets
OIDs to use the OBJECT-IDENTITY macro. OIDs to use the OBJECT-IDENTITY macro.
(12) Added to the list of registered dot3ChipSets. (12) Added to the list of registered dot3ChipSets.
(13) An intellectual property notice and copyright notice (13) An intellectual property notice and copyright notice
were added, as required by RFC 2026. were added, as required by RFC 2026.
B. Full Copyright Statement B. Full Copyright Statement
Copyright (C) The Internet Society (2002). All Rights Reserved. Copyright (C) The Internet Society (2002). 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 others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published and or assist in its implementation may be prepared, copied, published
distributed, in whole or in part, without restriction of any kind, and distributed, in whole or in part, without restriction of any
provided that the above copyright notice and this paragraph are kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than followed, or as required to translate it into languages other than
English. English.
The limited permissions granted above are perpetual and will not be The limited permissions granted above are perpetual and will not be
 End of changes. 

This html diff was produced by rfcdiff 1.25, available from http://www.levkowetz.com/ietf/tools/rfcdiff/