draft-ietf-hubmib-etherif-mib-v2-01.txt   draft-ietf-hubmib-etherif-mib-v2-02.txt 
Hub MIB Working Group J. Flick Hub MIB Working Group J. Flick
INTERNET DRAFT Hewlett-Packard Company INTERNET DRAFT Hewlett-Packard Company
J. Johnson J. Johnson
RedBack Networks RedBack Networks
November 1998 January 1999
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-v2-01.txt> <draft-ietf-hubmib-etherif-mib-v2-02.txt>
Status of this Memo Status of this Memo
This document is an Internet-Draft. Internet-Drafts are working This document is an Internet-Draft. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas, documents of the Internet Engineering Task Force (IETF), its areas,
and its working groups. Note that other groups may also distribute and its working groups. Note that other groups may also distribute
working documents as Internet-Drafts. working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet- Drafts as reference time. It is inappropriate to use Internet- Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
To view the entire list of current Internet-Drafts, please check the To view the list Internet-Draft Shadow Directories, see
"1id-abstracts.txt" listing contained in the Internet-Drafts Shadow http://www.ietf.org/shadow.html.
Directories on ftp.is.co.za (Africa), ftp.nordu.net (Northern
Europe), ftp.nis.garr.it (Southern Europe), munnari.oz.au (Pacific
Rim), ftp.ietf.org (US East Coast), or ftp.isi.edu (US West Coast).
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (1998). All Rights Reserved. Copyright (C) The Internet Society (1999). 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 2358 ''Definitions of Managed Objects for the This memo obsoletes RFC 2358 ''Definitions of Managed Objects for the
Ethernet-like Interface Types''. This memo extends that Ethernet-like Interface Types''. This memo extends that
specification by including management information useful for the specification by including management information useful for the
management of 1000 Mb/s and full-duplex Ethernet interfaces. management of 1000 Mb/s and full-duplex Ethernet interfaces.
skipping to change at page 2, line 25 skipping to change at page 2, line 22
1. Introduction ................................................ 2 1. Introduction ................................................ 2
2. The SNMP Management Framework .............................. 3 2. The SNMP Management Framework .............................. 3
3. Overview ................................................... 4 3. Overview ................................................... 4
3.1. Relation to MIB-2 ........................................ 4 3.1. Relation to MIB-2 ........................................ 4
3.2. Relation to the Interfaces MIB ........................... 5 3.2. Relation to the Interfaces MIB ........................... 5
3.2.1. Layering Model ......................................... 5 3.2.1. Layering Model ......................................... 5
3.2.2. Virtual Circuits ....................................... 5 3.2.2. Virtual Circuits ....................................... 5
3.2.3. ifTestTable ............................................ 5 3.2.3. ifTestTable ............................................ 5
3.2.4. ifRcvAddressTable ...................................... 6 3.2.4. ifRcvAddressTable ...................................... 6
3.2.5. ifPhysAddress .......................................... 6 3.2.5. ifPhysAddress .......................................... 6
3.2.6. ifType ................................................. 7 3.2.6. ifType ................................................. 6
3.2.7. Specific Interface MIB Objects ......................... 7 3.2.7. Specific Interface MIB Objects ......................... 7
3.3. Relation to the 802.3 MAU MIB ............................ 11 3.3. Relation to the 802.3 MAU MIB ............................ 10
3.4. dot3StatsEtherChipSet .................................... 11 3.4. dot3StatsEtherChipSet .................................... 11
3.5. Mapping of IEEE 802.3 Managed Objects .................... 11 3.5. Mapping of IEEE 802.3 Managed Objects .................... 11
4. Definitions ................................................ 14 4. Definitions ................................................ 14
5. Intellectual Property ...................................... 35 5. Intellectual Property ...................................... 36
6. Acknowledgements ........................................... 36 6. Acknowledgements ........................................... 36
7. References ................................................. 37 7. References ................................................. 37
8. Security Considerations .................................... 40 8. Security Considerations .................................... 40
9. Author's Addresses ......................................... 40 9. Author's Addresses ......................................... 41
A. Change Log ................................................. 41 A. Change Log ................................................. 41
A.1. Changes since RFC 2358 ................................... 41 A.1. Changes since RFC 2358 ................................... 41
A.2. Changes between RFC 1650 and RFC 2358 .................... 42 A.2. Changes between RFC 1650 and RFC 2358 .................... 42
B. Full Copyright Statement ................................... 43 B. Full Copyright Statement ................................... 43
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
skipping to change at page 11, line 25 skipping to change at page 11, line 18
of the interface. of the interface.
3.4. dot3StatsEtherChipSet 3.4. dot3StatsEtherChipSet
This document defines an object called dot3StatsEtherChipSet, which This document defines an object called dot3StatsEtherChipSet, which
is used to identify the MAC hardware used to communicate on an is used to identify the MAC hardware used to communicate on an
interface. Previous versions of this document contained a number of interface. Previous versions of this document contained a number of
OID assignments for some existing Ethernet chipsets. Maintaining OID assignments for some existing Ethernet chipsets. Maintaining
that list as part of this document has proven to be problematic, so that list as part of this document has proven to be problematic, so
the OID assignments contained in prevous versions of this document the OID assignments contained in prevous versions of this document
have now been moved to a separate document [28]. That document also have now been moved to a separate document [28].
contains information on future management of chipset OID assignments.
The dot3StatsEtherChipSet object has now been deprecated.
Implementation feedback indicates that this object is much more
useful in theory than in practice. The object's utility in debugging
network problems in the field appears to be limited. In those cases
where it may be useful, it is not sufficient, since it identifies
only the MAC chip, and not the PHY, PMD, or driver. The
administrative overhead involved in maintaining a central registry of
chipset OIDs cannot be justified for an object whose usefulness is
questionable at best.
Implementations which continue to support this object for the purpose
of backwards compatability may continue to use the values defined in
[28]. For chipsets not listed in [28], implementors should assign
OBJECT IDENTIFIERS within that part of the registration tree
delegated to individual enterprises.
3.5. Mapping of IEEE 802.3 Managed Objects 3.5. Mapping of IEEE 802.3 Managed Objects
IEEE 802.3 Managed Object Corresponding SNMP Object IEEE 802.3 Managed Object Corresponding SNMP Object
oMacEntity oMacEntity
.aMACID dot3StatsIndex or .aMACID dot3StatsIndex or
IF-MIB - ifIndex IF-MIB - ifIndex
.aFramesTransmittedOK IF-MIB - ifOutUCastPkts + .aFramesTransmittedOK IF-MIB - ifOutUCastPkts +
ifOutMulticastPkts + ifOutMulticastPkts +
skipping to change at page 14, line 25 skipping to change at page 14, line 32
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY, MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY,
Counter32, Unsigned32, mib-2, transmission Counter32, Unsigned32, mib-2, transmission
FROM SNMPv2-SMI FROM SNMPv2-SMI
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
ifIndex, InterfaceIndex ifIndex, InterfaceIndex
FROM IF-MIB; FROM IF-MIB;
etherMIB MODULE-IDENTITY etherMIB MODULE-IDENTITY
LAST-UPDATED "9811172346Z" -- November 17, 1998 LAST-UPDATED "9901280031Z" -- January 28, 1999
ORGANIZATION "IETF 802.3 Hub MIB Working Group" ORGANIZATION "IETF Ethernet Interfaces and Hub MIB
Working Group"
CONTACT-INFO CONTACT-INFO
"WG E-mail: hubmib@hprnd.rose.hp.com "WG E-mail: hubmib@hprnd.rose.hp.com
To subscribe: hubmib-request@hprnd.rose.hp.com To subscribe: hubmib-request@hprnd.rose.hp.com
Chair: Dan Romascanu Chair: Dan Romascanu
Postal: LANNET Ltd. Postal: Lucent Technologies
Atidum Technology Park, Bldg. 3 Atidum Technology Park, Bldg. 3
Tel Aviv 61131 Tel Aviv 61131
Israel Israel
Tel: +972 3 645 8414 Tel: +972 3 645 8414
E-mail: dromasca@lannet.com E-mail: dromasca@lucent.com
Editor: John Flick Editor: John Flick
Postal: Hewlett-Packard Company Postal: Hewlett-Packard Company
8000 Foothills Blvd. M/S 5556 8000 Foothills Blvd. M/S 5557
Roseville, CA 95747-5556 Roseville, CA 95747-5557
USA USA
Tel: +1 916 785 4018 Tel: +1 916 785 4018
Fax: +1 916 785 3583 Fax: +1 916 785 1199
E-mail: johnf@rose.hp.com E-mail: johnf@rose.hp.com
Editor: Jeffrey Johnson Editor: Jeffrey Johnson
Postal: RedBack Networks Postal: RedBack Networks
2570 North First Street, Suite 410 2570 North First Street, Suite 410
San Jose, CA, 95131 San Jose, CA, 95131
USA USA
Tel: +1 408 571 2699 Tel: +1 408 571 2699
Fax: +1 408 571 2698 Fax: +1 408 571 2698
E-Mail: jeff@redbacknetworks.com" E-Mail: jeff@redbacknetworks.com"
skipping to change at page 15, line 29 skipping to change at page 15, line 37
Local and metropolitan area networks - Local and metropolitan area networks -
Specific requirements - Part 3: Carrier Specific requirements - Part 3: Carrier
sense multiple access with collision sense multiple access with collision
detection (CSMA/CD) access method and detection (CSMA/CD) access method and
physical layer specifications', physical layer specifications',
September 1998. September 1998.
Of particular interest is Clause 30, '10Mb/s, Of particular interest is Clause 30, '10Mb/s,
100Mb/s and 1000Mb/s Management'." 100Mb/s and 1000Mb/s Management'."
REVISION "9811172346Z" -- November 17, 1998 REVISION "9901280031Z" -- January 28, 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."
REVISION "9806032150Z" -- June 3, 1998 REVISION "9806032150Z" -- June 3, 1998
DESCRIPTION "Updated to include support for 100 Mb/sec DESCRIPTION "Updated to include support for 100 Mb/sec
interfaces. Published as RFC 2358." interfaces. Published as RFC 2358."
REVISION "9402030400Z" -- February 3, 1994 REVISION "9402030400Z" -- February 3, 1994
DESCRIPTION "Version published as RFC 1650." DESCRIPTION "Version published as RFC 1650."
::= { mib-2 35 } ::= { mib-2 35 }
skipping to change at page 22, line 22 skipping to change at page 22, line 27
object may represent a count of receive errors object may represent a count of receive errors
on a particular interface that are not on a particular interface that are not
otherwise counted." otherwise counted."
REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.15, REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.15,
aFramesLostDueToIntMACRcvError." aFramesLostDueToIntMACRcvError."
::= { dot3StatsEntry 16 } ::= { dot3StatsEntry 16 }
dot3StatsEtherChipSet OBJECT-TYPE dot3StatsEtherChipSet OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER SYNTAX OBJECT IDENTIFIER
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS deprecated
DESCRIPTION "This object contains an OBJECT IDENTIFIER DESCRIPTION "******** THIS OBJECT IS DEPRECATED ********
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
skipping to change at page 34, line 37 skipping to change at page 34, line 44
dot3StatsAlignmentErrors, dot3StatsAlignmentErrors,
dot3StatsFCSErrors, dot3StatsFCSErrors,
dot3StatsSingleCollisionFrames, dot3StatsSingleCollisionFrames,
dot3StatsMultipleCollisionFrames, dot3StatsMultipleCollisionFrames,
dot3StatsDeferredTransmissions, dot3StatsDeferredTransmissions,
dot3StatsLateCollisions, dot3StatsLateCollisions,
dot3StatsExcessiveCollisions, dot3StatsExcessiveCollisions,
dot3StatsInternalMacTransmitErrors, dot3StatsInternalMacTransmitErrors,
dot3StatsCarrierSenseErrors, dot3StatsCarrierSenseErrors,
dot3StatsFrameTooLongs, dot3StatsFrameTooLongs,
dot3StatsInternalMacReceiveErrors, dot3StatsInternalMacReceiveErrors
dot3StatsEtherChipSet
} }
STATUS current STATUS current
DESCRIPTION "A collection of objects providing information DESCRIPTION "A collection of objects providing information
applicable to all ethernet-like network applicable to all ethernet-like network
interfaces." interfaces."
::= { 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 }
etherStatsHighSpeedGroup OBJECT-GROUP etherStatsHighSpeedGroup OBJECT-GROUP
skipping to change at page 40, line 5 skipping to change at page 40, line 11
[25] McCloghrie, K., and F. Kastenholz, "The Interfaces Group MIB [25] McCloghrie, K., and F. Kastenholz, "The Interfaces Group MIB
using SMIv2", RFC 2233, Cisco Systems, FTP Software, using SMIv2", RFC 2233, Cisco Systems, FTP Software,
November 1997. November 1997.
[26] Bradner, S., "Key words for use in RFCs to Indicate [26] Bradner, S., "Key words for use in RFCs to Indicate
Requirements Levels", BCP 14, RFC 2119, March 1997. Requirements Levels", BCP 14, RFC 2119, March 1997.
[27] Smith, A., Flick, J., deGraaf, K., Romascanu, D., McMaster, [27] Smith, A., Flick, J., deGraaf, K., Romascanu, D., McMaster,
D., McCloghrie, K., and S. Roberts, "Definitions of Managed D., McCloghrie, K., and S. Roberts, "Definitions of Managed
Objects for IEEE 802.3 Medium Attachment Units (MAUs) using Objects for IEEE 802.3 Medium Attachment Units (MAUs) using
SMIv2", work in progress, draft-ietf-hubmib-mau-mib-v2-01.txt, SMIv2", work in progress, draft-ietf-hubmib-mau-mib-v2-02.txt,
Extreme Networks, Inc., Hewlett-Packard Company, Argon Networks, Extreme Networks, Inc., Hewlett-Packard Company, Argon Networks,
LANNET Ltd., Cisco Systems, Inc., Cisco Systems Inc., Farallon LANNET Ltd., Cisco Systems, Inc., Cisco Systems Inc., Farallon
Computing Inc., November 1998. Computing Inc., January 1999.
[28] "Ethernet Interface Chipset Registrations", work in progress. [28] Flick, J., "Definitions of Object Identifiers for Identifying
Ethernet Chip Sets", work in progress,
draft-ietf-hubmib-ether-chipsets-00.txt, Hewlett-Packard
Company, January 1999.
8. Security Considerations 8. Security Considerations
There are two management objects defined in this MIB that have a There are two management objects defined in this MIB that have a
MAX-ACCESS clause of read-write. Such objects may be considered MAX-ACCESS clause of read-write. Such objects may be considered
sensitive or vulnerable in some network environments. The support sensitive or vulnerable in some network environments. The support
for SET operations in a non-secure environment without proper for SET operations in a non-secure environment without proper
protection can have a negative effect on network operations. protection can have a negative effect on network operations.
There are a number of managed objects in this MIB that may be There are a number of managed objects in this MIB that may be
considered to contain sensitive information. In particular, the considered to contain sensitive information. 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. 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.
Therefore, it may be important in some environments to control read Therefore, it may be important in some environments to control read
access to these objects and possibly to even encrypt the values of access to these objects and possibly to even encrypt the values of
these object when sending them over the network via SNMP. Not all these objects when sending them over the network via SNMP. Not all
versions of SNMP provide features for such a secure environment. versions of SNMP provide features for such a secure environment.
SNMPv1 by itself is such an insecure environment. Even if the SNMPv1 by itself is such an insecure environment. Even if the
network itself is secure (for example by using IPSec), even then, 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 there is no control as to who on the secure network is allowed to
access and GET (read) the objects in this MIB. access and GET (read) the objects in this MIB.
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. Specifically, the use
of the User-based Security Model RFC 2274 [12] and the View-based of the User-based Security Model RFC 2274 [12] and the View-based
skipping to change at page 41, line 4 skipping to change at page 41, line 14
It is then a customer/user responsibility to ensure that the SNMP It is then a customer/user responsibility to ensure that the SNMP
entity giving access to an instance of this MIB, is properly entity giving access to an instance of this MIB, is properly
configured to give access to those objects only to those principals configured to give access to those objects only to those principals
(users) that have legitimate rights to access them. (users) that have legitimate rights to access them.
9. Author's Addresses 9. Author's Addresses
John Flick John Flick
Hewlett-Packard Company Hewlett-Packard Company
8000 Foothills Blvd. M/S 5556 8000 Foothills Blvd. M/S 5557
Roseville, CA 95747-5556 Roseville, CA 95747-5557
Phone: +1 916 785 4018 Phone: +1 916 785 4018
Email: johnf@rose.hp.com Email: johnf@rose.hp.com
Jeffrey Johnson Jeffrey Johnson
RedBack Networks RedBack Networks
2570 North First Street, Suite 410 2570 North First Street, Suite 410
San Jose, CA, 95131, USA San Jose, CA, 95131, USA
Phone: +1 408 571 2699 Phone: +1 408 571 2699
skipping to change at page 42, line 13 skipping to change at page 42, line 23
dot3StatsFCSErrors, dot3StatsSQETestErrors, dot3StatsFCSErrors, dot3StatsSQETestErrors,
dot3StatsLateCollisions, dot3StatsSymbolErrors. dot3StatsLateCollisions, dot3StatsSymbolErrors.
(7) Two new tables, dot3ControlTable and dot3PauseTable, (7) Two new tables, dot3ControlTable and dot3PauseTable,
have been added. have been added.
(8) A new object, dot3StatsDuplexStatus, has been added. (8) A new object, dot3StatsDuplexStatus, has been added.
(9) The object groups and compliances have been restructured. (9) The object groups and compliances have been restructured.
(10) The dot3ChipSets have been moved to a separate document. (10) The dot3StatsEtherChipSet object has been deprecated.
(11) The dot3ChipSets have been moved to a separate document.
A.2. Changes between RFC 1650 and RFC 2358 A.2. Changes between RFC 1650 and RFC 2358
This section enumerates changes made to RFC 1650 to produce RFC 2358. This section enumerates changes made to RFC 1650 to produce RFC 2358.
(1) The MODULE-IDENTITY has been updated to reflect the changes (1) The MODULE-IDENTITY has been updated to reflect the changes
in the MIB. in the MIB.
(2) A new object, dot3StatsSymbolErrors, has been added. (2) A new object, dot3StatsSymbolErrors, has been added.
 End of changes. 

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