replaced by etherStatsBaseGroup and
etherStatsHighSpeedGroup."
::= { etherGroups 3 }
etherStatsBaseGroup OBJECT-GROUP
OBJECTS { dot3StatsIndex,
dot3StatsAlignmentErrors,
dot3StatsFCSErrors,
dot3StatsSingleCollisionFrames,
dot3StatsMultipleCollisionFrames,
dot3StatsDeferredTransmissions,
dot3StatsLateCollisions,
dot3StatsExcessiveCollisions,
dot3StatsInternalMacTransmitErrors,
dot3StatsCarrierSenseErrors,
dot3StatsFrameTooLongs,
dot3StatsInternalMacReceiveErrors
}
STATUS deprecated
DESCRIPTION "********* THIS GROUP IS DEPRECATED **********
A collection of objects providing information
applicable to all ethernet-like network
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 }
etherStatsLowSpeedGroup OBJECT-GROUP
OBJECTS { dot3StatsSQETestErrors }
STATUS current
DESCRIPTION "A collection of objects providing information
applicable to ethernet-like network interfaces
capable of operating at 10 Mb/s or slower in
half-duplex mode."
::= { etherGroups 5 }
etherStatsHighSpeedGroup OBJECT-GROUP
OBJECTS { dot3StatsSymbolErrors }
STATUS current
DESCRIPTION "A collection of objects providing information
applicable to ethernet-like network interfaces
capable of operating at 100 Mb/s or faster."
::= { etherGroups 6 }
etherDuplexGroup OBJECT-GROUP
OBJECTS { dot3StatsDuplexStatus }
STATUS current
DESCRIPTION "A collection of objects providing information
about the duplex mode of an ethernet-like
network interface."
::= { etherGroups 7 }
etherControlGroup OBJECT-GROUP
OBJECTS { dot3ControlFunctionsSupported,
dot3ControlInUnknownOpcodes
}
STATUS current
DESCRIPTION "A collection of objects providing information
about the MAC Control sublayer on ethernet-like
network interfaces."
::= { etherGroups 8 }
etherControlPauseGroup OBJECT-GROUP
OBJECTS { dot3PauseAdminMode,
dot3PauseOperMode,
dot3InPauseFrames,
dot3OutPauseFrames
}
STATUS current
DESCRIPTION "A collection of objects providing information
about and control of the MAC Control PAUSE
function on ethernet-like network interfaces."
::= { etherGroups 9 }
etherStatsBaseGroup2 OBJECT-GROUP
OBJECTS { dot3StatsIndex,
dot3StatsAlignmentErrors,
dot3StatsFCSErrors,
dot3StatsInternalMacTransmitErrors,
dot3StatsFrameTooLongs,
dot3StatsInternalMacReceiveErrors
}
STATUS current
DESCRIPTION "A collection of objects providing information
applicable to all ethernet-like network
interfaces."
::= { etherGroups 10 }
etherStatsHalfDuplexGroup OBJECT-GROUP
OBJECTS { dot3StatsSingleCollisionFrames,
dot3StatsMultipleCollisionFrames,
dot3StatsDeferredTransmissions,
dot3StatsLateCollisions,
dot3StatsExcessiveCollisions,
dot3StatsCarrierSenseErrors
}
STATUS current
DESCRIPTION "A collection of objects providing information
applicable only to half-duplex ethernet-like
network interfaces."
::= { etherGroups 11 }
etherHCStatsGroup OBJECT-GROUP
OBJECTS { dot3HCStatsAlignmentErrors,
dot3HCStatsFCSErrors,
dot3HCStatsInternalMacTransmitErrors,
dot3HCStatsFrameTooLongs,
dot3HCStatsInternalMacReceiveErrors,
dot3HCStatsSymbolErrors
}
STATUS current
DESCRIPTION "A collection of objects providing high-capacity
statistics applicable to higher-speed
ethernet-like network interfaces."
::= { etherGroups 12 }
etherHCControlGroup OBJECT-GROUP
OBJECTS { dot3HCControlInUnknownOpcodes }
STATUS current
DESCRIPTION "A collection of objects providing high-capacity
statistics for the MAC Control sublayer on
higher-speed ethernet-like network interfaces."
::= { etherGroups 13 }
etherHCControlPauseGroup OBJECT-GROUP
OBJECTS { dot3HCInPauseFrames,
dot3HCOutPauseFrames
}
STATUS current
DESCRIPTION "A collection of objects providing high-capacity
statistics for the MAC Control PAUSE function on
higher-speed ethernet-like network interfaces."
::= { etherGroups 14 }
etherRateControlGroup OBJECT-GROUP
OBJECTS { dot3StatsRateControlAbility,
dot3StatsRateControlStatus
}
STATUS current
DESCRIPTION "A collection of objects providing information
about the Rate Control function on ethernet-like
interfaces."
::= { etherGroups 15 }
END
5. Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to
pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights
might or might not be available; neither does it represent that it
has made any effort to identify any such rights. Information on the
IETF’s procedures with respect to rights in standards-track and
standards-related documentation can be found in BCP-11. Copies of
claims of rights made available for publication and any assurances of
licenses to be made available, or the result of an attempt made to
obtain a general license or permission for the use of such
proprietary rights by implementors or users of this specification can
be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive
Director.
6. Acknowledgements
This document was produced by the IETF Ethernet Interfaces and Hub
MIB Working Group, whose efforts were greatly advanced by the
contributions of the following people:
Ran Atkinson
Mike Ayers
Mike Heard
Jeffrey Johnson
Lynn Kubinec
Kam Lam
Kerry McDonald
Steve McRobert
K.C. Norseth
Dan Romascanu
Randy Presuhn
Andrew Smith
Kaj Tesink
Geoff Thompson
This document is based on the Proposed Standard Ethernet MIB, RFC
2665 [RFC2665], edited by John Flick of Hewlett-Packard and Jeffrey
Johnson of RedBack Networks and produced by the Ethernet Interfaces
and Hub MIB Working Group. It extends that document by providing
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 2358 [RFC2358], edited by John Flick of Hewlett-Packard and
Jeffrey Johnson of RedBack Networks and produced by the 802.3 Hub MIB
Working Group. It extends that document by providing support for
full-duplex Ethernet interfaces and 1000 Mb/sec Ethernet interfaces
as outlined in [IEEE802.3].
RFC 2358, in turn, is almost completely based on both the Standard
Ethernet MIB, RFC 1643 [RFC1643], and the Proposed Standard Ethernet
MIB using the SNMPv2 SMI, RFC 1650 [RFC1650], both of which were
edited by Frank Kastenholz of FTP Software and produced by the
Interfaces MIB Working Group. RFC 2358 extends those documents by
providing support for 100 Mb/sec ethernet interfaces.
RFC 1643 and RFC 1650, in turn, are based on the Draft Standard
Ethernet MIB, RFC 1398 [RFC1398], also edited by Frank Kastenholz and
produced by the Ethernet MIB Working Group.
RFC 1398, in turn, is based on the Proposed Standard Ethernet MIB,
RFC 1284 [RFC1284], which was edited by John Cook of Chipcom and
produced by the Transmission MIB Working Group. The Ethernet MIB
Working Group gathered implementation experience of the variables
specified in RFC 1284, documented that experience in RFC 1369
[RFC1369], and used that information to develop this revised MIB.
RFC 1284, in turn, is based on a document written by Frank
Kastenholz, then of Interlan, entitled IEEE 802.3 Layer Management
Draft M compatible MIB for TCP/IP Networks [KASTEN]. This document
was modestly reworked, initially by the SNMP Working Group, and then
by the Transmission Working Group, to reflect the current conventions
for defining objects for MIB interfaces. James Davin, of the MIT
Laboratory for Computer Science, and Keith McCloghrie of Hughes LAN
Systems, contributed to later drafts of this memo. Marshall Rose of
Performance Systems International, Inc. converted the document into
RFC 1212 [RFC1212] concise format. Anil Rijsinghani of DEC
contributed text that more adequately describes the TDR test. Thanks
to Frank Kastenholz of Interlan and Louis Steinberg of IBM for their
experimentation.
7. 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,
J., Rose, M. and S. Waldbusser, "Structure of
Management Information Version 2 (SMIv2)", STD 58, RFC
2578, April 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
J., Rose, M. and S. Waldbusser, "Textual Conventions
for SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,
J., Rose, M. and S. Waldbusser, "Conformance Statements
for SMIv2", STD 58, RFC 2580, April 1999.
[RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group
MIB using SMIv2", RFC 2863, June 2000.
[IEEE802.3] IEEE, IEEE Std 802.3, 2002 Edition: "Carrier Sense
Multiple Access with Collision Detection (CSMA/CD)
Access Method and Physical Layer Specifications", March
2002.
[IEEE802.3ae] IEEE, IEEE Std 802.3ae-2002, "Amendment: Media Access
Control (MAC) Parameters, Physical Layers, and
Management Parameters for 10 Gb/s Operation", August,
2002.
[RFC3636] Flick, J., "Definitions of Managed Objects for IEEE
802.3 Medium Attachment Units (MAUs) using SMIv2", RFC
3636, September 2003.
8. Informative References
[RFC1212] Rose, M. and K. McCloghrie, Editors, "Concise MIB
Definitions", STD 16, RFC 1212, March 1991.
[RFC1213] McCloghrie, K. and M. Rose, Editors, "Management
Information Base for Network Management of TCP/IP-based
internets: MIB-II", STD 17, RFC 1213, March 1991.
[RFC1284] Cook, J., "Definitions of Managed Objects for
Ethernet-Like Interface Types", RFC 1284, December
1991.
[RFC1369] Kastenholz, F., "Implementation Notes and Experience
for The Internet Ethernet MIB", RFC 1369, October 1992.
[RFC1398] Kastenholz, F., "Definitions of Managed Objects for the
Ethernet-like Interface Types", RFC 1398, January 1993.
[RFC1643] Kastenholz, F., "Definitions of Managed Objects for the
Ethernet-like Interface Types", STD 50, RFC 1643, July
1994.
[RFC1650] Kastenholz, F., "Definitions of Managed Objects for the
Ethernet-like Interface Types using SMIv2", RFC 1650,
August 1994.
[RFC2358] Flick, J. and J. Johnson, "Definitions of Managed
Objects for the Ethernet-like Interface Types", RFC
2358, June 1998.
[RFC2665] Flick, J. and J. Johnson, "Definitions of Managed
Objects for the Ethernet-like Interface Types", RFC
2665, August 1999.
[RFC2666] Flick, J., "Definitions of Object Identifiers for
Identifying Ethernet Chip Sets", RFC 2666, August 1999.
[RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart,
"Introduction and Applicability Statements for
Internet-Standard Network Management Framework", RFC
3410, December 2002.
[CASE] Case, J., and C. Partridge, "Case Diagrams: A First
Step to Diagrammed Management Information Bases",
Computer Communications Review, 19(1):13-16, January
1989.
[RFC3637] Heard, C., "Definitions of Managed Objects for the
Ethernet WAN Interface Sublayer", RFC 3637, September
2003.
[KASTEN] Kastenholz, F., "IEEE 802.3 Layer Management Draft
compatible MIB for TCP/IP Networks", electronic mail
message to mib-wg@nnsc.nsf.net, 9 June 1989.
9. Security Considerations
There is one management object defined in this MIB that has a MAX-
ACCESS clause of read-write. That object, dot3PauseAdminMode, may be
used to change the flow control configuration on a network interface,
which may result in dropped packets, or sending flow control packets
on links where the link partner will not understand them. Either
action could be detrimental to network performance.
Such objects may be considered sensitive or vulnerable in some
network environments. The support for SET operations in a non-secure
environment without proper protection can have a negative effect on
network operations.
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
environments, since it would allow an intruder to obtain information
about which vendor’s equipment is in use on the network. Note that
this object has been deprecated. However, some implementors may
still choose to implement it for backwards compatability.
Most of the objects in this MIB module contain statistical
information about particular network links. In some network
environments, this information may be considered sensitive.
It is thus important to control even GET and/or NOTIFY access to
these objects and possibly to even encrypt the values of these
objects when sending them over the network via SNMP.
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
features as provided by the SNMPv3 framework (see [RFC3410], section
8), including full support for the SNMPv3 cryptographic mechanisms
(for authentication and privacy).
Furthermore, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them.
10. IANA Considerations
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 have had an ASN.1 comment added by IANA stating
that they have been deprecated:
- iso88032Csmacd(7)
- starLan(11)
In addition, the following enumerated values have had an ASN.1
comment added by IANA stating that they are obsolete:
- fastEther(62)
- fastEtherFX(69)
- gigabitEthernet(117)
In all of the above cases, the ASN.1 comment indicates that
ethernetCsmacd(6) should be used instead of these values.
A. Change Log
A.1. Changes since RFC 2665
This section enumerates changes made to RFC 2665 to produce this
document.
(1) Updated references to the IEEE 802.3 standard to
refer to the 2002 edition.
(2) Added reference to IEEE 802.3ae-2002.
(3) Updated WG e-mail address.
(4) The following DESCRIPTION clauses have been updated
to reflect behaviour on 10 Gb/s interfaces:
dot3StatsAlignmentErrors and dot3StatsSymbolErrors.
(5) The following objects have been added for management
of the Rate Control function in WAN applications of
ethernet: dot3StatsRateControlAbility and
dot3StatsRateControlStatus.
(6) The following 64-bit counters have been added to
support operation on high-speed ethernet interfaces:
dot3HCControlInUnknownOpcodes, dot3HCInPauseFrames,
dot3HCOutPauseFrames, dot3HCStatsAlignmentErrors,
dot3HCStatsFCSErrors, dot3HCStatsFrameTooLongs,
dot3HCStatsInternalMacTransmitErrors,
dot3HCStatsInternalMacReceiveErrors,
dot3HCStatsSymbolErrors
(7) Object groups and compliances have been added to
contain the new objects.