draft-ietf-hubmib-etherif-mib-04.txt   draft-ietf-hubmib-etherif-mib-05.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
March 1998 May 1998
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-04.txt> <draft-ietf-hubmib-etherif-mib-05.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 learn the current status of any Internet-Draft, please check the To view the entire list of current Internet-Drafts, please check the
``1id-abstracts.txt'' listing contained in the Internet-Drafts Shadow "1id-abstracts.txt" listing contained in the Internet-Drafts Shadow
Directories on ftp.is.co.za (Africa), nic.nordu.net (Europe), Directories on ftp.is.co.za (Africa), ftp.nordu.net (Northern
munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or Europe), ftp.nis.garr.it (Southern Europe), munnari.oz.au (Pacific
ftp.isi.edu (US West Coast). 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 (1998). All Rights Reserved.
Abstract Abstract
This memo is an extension to the SNMP MIB. It specifies an IAB This memo defines a portion of the Management Information Base (MIB)
standards track protocol for the Internet community, and requests for use with network management protocols in the Internet community.
discussion and suggestions for improvements. The origin of this memo The origin of this memo is from RFC 1650 ''Definitions of Managed
is from RFC 1650 ''Definitions of Managed Objects for the Ethernet- Objects for the Ethernet-like Interface Types using SMIv2.'' This
like Interface Types using SMIv2.'' This memo extends that memo extends that specification by including management information
specification by including management information useful for the useful for the management of 100 Mb/s Ethernet interfaces.
management of 100BaseT ethernet interfaces.
Distribution of this memo is unlimited. Please forward comments to Distribution of this memo is unlimited. Please forward comments to
hubmib@hprnd.rose.hp.com. hubmib@hprnd.rose.hp.com.
Table of Contents Table of Contents
1. Introduction ................................................ 2 1. Introduction ................................................ 2
2. The SNMP Network Management Framework ...................... 2 2. The SNMP Network Management Framework ...................... 2
2.1. Object Definitions ....................................... 3 2.1. Object Definitions ....................................... 3
3. Change Log ................................................. 3 3. Change Log ................................................. 3
skipping to change at page 4, line 12 skipping to change at page 4, line 12
(9) A section defining the relationship of this MIB to (9) A section defining the relationship of this MIB to
the MAU MIB has been added. the MAU MIB has been added.
(10) A section on the mapping of IEEE 802.3 managed objects (10) A section on the mapping of IEEE 802.3 managed objects
to this MIB and the Interfaces MIB has been added. to this MIB and the Interfaces MIB has been added.
(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 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.
4. Overview 4. 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 following values of the ifType object in media are identified by the following values of the ifType object in
the Interfaces MIB [12]: the Interfaces MIB [12]:
skipping to change at page 4, line 38 skipping to change at page 4, line 38
The definitions presented here are based on the IEEE 802.3 Layer The definitions presented here are based on the IEEE 802.3 Layer
Management Specification [5], as originally interpreted by Frank Management Specification [5], as originally interpreted by Frank
Kastenholz then of Interlan in [7]. Implementors of these MIB Kastenholz then of Interlan in [7]. Implementors of these MIB
objects should note that the IEEE document explicitly describes (in objects should note that the IEEE document explicitly describes (in
the form of Pascal pseudocode) when, where, and how various MAC the form of Pascal pseudocode) when, where, and how various MAC
attributes are measured. The IEEE document also describes the attributes are measured. The IEEE document also describes the
effects of MAC actions that may be invoked by manipulating instances effects of MAC actions that may be invoked by manipulating instances
of the MIB objects defined here. of the MIB objects defined here.
To the extent that some of the attributes defined in [5] are To the extent that some of the attributes defined in [5] are
represented by previously defined objects in the Internet-standard represented by previously defined objects in MIB-2 [16] or in the
MIB or in the Interfaces Group Evolution MIB [12], such attributes Interfaces MIB [12], such attributes are not redundantly represented
are not redundantly represented by objects defined in this memo. by objects defined in this memo. Among the attributes represented by
Among the attributes represented by objects defined in other memos objects defined in other memos are the number of octets transmitted
are the number of octets transmitted or received on a particular or received on a particular interface, the number of frames
interface, the number of frames transmitted or received on a transmitted or received on a particular interface, the promiscuous
particular interface, the promiscuous status of an interface, the MAC status of an interface, the MAC address of an interface, and
address of an interface, and multicast information associated with an multicast information associated with an interface.
interface.
4.1. Relation to MIB-2 4.1. Relation to MIB-2
This section applies only when this MIB is used in conjunction with This section applies only when this MIB is used in conjunction with
the "old" (RFC 1213) interface group. the "old" (RFC 1213) [16] interface group.
The relationship between an ethernet-like interface and an interface The relationship between an ethernet-like interface and an interface
in the context of the Internet-standard MIB is one-to-one. As such, in the context of the Internet-standard MIB is one-to-one. As such,
the value of an ifIndex object instance can be directly used to the value of an ifIndex object instance can be directly used to
identify corresponding instances of the objects defined herein. identify corresponding instances of the objects defined herein.
For agents which implement the (now deprecated) ifSpecific object, an For agents which implement the (now deprecated) ifSpecific object, an
instance of that object that is associated with an ethernet-like instance of that object that is associated with an ethernet-like
interface has the OBJECT IDENTIFIER value: interface has the OBJECT IDENTIFIER value:
skipping to change at page 13, line 4 skipping to change at page 13, line 4
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY, MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY,
Counter32, mib-2, transmission Counter32, 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 "9802260008Z" -- February 26, 1998 LAST-UPDATED "9805122107Z" -- May 12, 1998
ORGANIZATION "IETF 802.3 Hub MIB Working Group" ORGANIZATION "IETF 802.3 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
Chair: Dan Romascanu Chair: Dan Romascanu
Postal: LANNET Ltd. Postal: LANNET Ltd.
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@lannet.com
Editor: John Flick Editor: John Flick
skipping to change at page 33, line 11 skipping to change at page 33, line 11
dot3ChipSetXaQtiXQ18110FP OBJECT-IDENTITY dot3ChipSetXaQtiXQ18110FP OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "The authoritative identifier for the XaQTI DESCRIPTION "The authoritative identifier for the XaQTI
XQ18110FP GigaPower Protocol Accelerator." XQ18110FP GigaPower Protocol Accelerator."
::= { dot3ChipSetXaQti 2 } ::= { dot3ChipSetXaQti 2 }
-- For those chipsets not represented above, OBJECT IDENTIFIER -- For those chipsets not represented above, OBJECT IDENTIFIER
-- assignment is required in other documentation, e.g., -- assignment is required in other documentation, e.g.,
-- assignment within that part of the registration tree -- assignment within that part of the registration tree
-- delegated to individual enterprises (see RFC1155). -- delegated to individual enterprises (see RFC 1155 and
-- RFC 1902).
-- 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 33, line 34 skipping to change at page 33, line 35
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."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { etherStatsGroup } MANDATORY-GROUPS { etherStatsGroup }
GROUP etherCollisionTableGroup GROUP etherCollisionTableGroup
DESCRIPTION "This group is optional. It is appropriate DESCRIPTION "This group is optional. It is appropriate
for all systems which have the necessary for all systems which have the necessary
metering Implementation in such systems is metering. Implementation in such systems is
highly recommended." highly recommended."
::= { etherCompliances 1 } ::= { etherCompliances 1 }
ether100MbsCompliance MODULE-COMPLIANCE ether100MbsCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION "The compliance statement for managed network DESCRIPTION "The compliance statement for managed network
entities which have 100 Mb/sec ethernet-like entities which have 100 Mb/sec ethernet-like
network interfaces." network interfaces."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { etherStats100MbsGroup } MANDATORY-GROUPS { etherStats100MbsGroup }
GROUP etherCollisionTableGroup GROUP etherCollisionTableGroup
DESCRIPTION "This group is optional. It is appropriate DESCRIPTION "This group is optional. It is appropriate
for all systems which have the necessary for all systems which have the necessary
metering Implementation in such systems is metering. Implementation in such systems is
highly recommended." highly recommended."
::= { etherCompliances 2 } ::= { etherCompliances 2 }
-- units of conformance -- units of conformance
etherStatsGroup OBJECT-GROUP etherStatsGroup OBJECT-GROUP
OBJECTS { dot3StatsIndex, OBJECTS { dot3StatsIndex,
dot3StatsAlignmentErrors, dot3StatsAlignmentErrors,
dot3StatsFCSErrors, dot3StatsFCSErrors,
dot3StatsSingleCollisionFrames, dot3StatsSingleCollisionFrames,
skipping to change at page 37, line 46 skipping to change at page 37, line 46
[14] deGraaf, K., Romascanu, D., McMaster, D., McCloghrie, K., and [14] deGraaf, K., Romascanu, D., McMaster, D., McCloghrie, K., and
S. Roberts, "Definitions of Managed Objects for IEEE 802.3 S. Roberts, "Definitions of Managed Objects for IEEE 802.3
Medium Attachment Units (MAUs) using SMIv2", RFC 2239, Medium Attachment Units (MAUs) using SMIv2", RFC 2239,
3Com Corporation, Madge Networks (Israel) Ltd., Cisco Systems 3Com Corporation, Madge Networks (Israel) Ltd., Cisco Systems
Inc., Cisco Systems Inc., Farallon Computing Inc., November Inc., Cisco Systems Inc., Farallon Computing Inc., November
1997. 1997.
[15] Kastenholz, F., "Implementation Notes and Experience for The [15] Kastenholz, F., "Implementation Notes and Experience for The
Internet Ethernet MIB", RFC 1369, FTP Software, October 1992. Internet Ethernet MIB", RFC 1369, FTP Software, October 1992.
9. Security Considerations [16] McCloghrie, K., and M. Rose, Editors, "Management Information
Base for Network Management of TCP/IP-based internets: MIB-II",
STD 17, RFC 1213, Hughes LAN Systems, Performance Systems
International, March 1991.
9. Security Considerations
Certain management information defined in this MIB may be considered Certain management information defined in this MIB may be considered
sensitive in some network environments. Therefore, authentication of sensitive in some network environments. Therefore, authentication of
received SNMP requests and controlled access to management received SNMP requests and controlled access to management
information should be employed in such environments. The method for information should be employed in such environments. The method for
this authentication is a function of the SNMP Administrative this authentication is a function of the SNMP Administrative
Framework, and has not been expanded by this MIB. Framework, and has not been expanded by this MIB.
10. Author's Addresses 10. Author's Addresses
John Flick John Flick
 End of changes. 

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