draft-ietf-hubmib-etherif-mib-02.txt   draft-ietf-hubmib-etherif-mib-03.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
F. Kastenholz F. Kastenholz
FTP Software, Inc. FTP Software, Inc.
November 1997 February 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-02.txt> <draft-ietf-hubmib-etherif-mib-03.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
skipping to change at page 1, line 36 skipping to change at page 1, line 36
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 learn the current status of any Internet-Draft, 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), nic.nordu.net (Europe),
munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or munnari.oz.au (Pacific Rim), ds.internic.net (US East Coast), or
ftp.isi.edu (US West Coast). ftp.isi.edu (US West Coast).
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (1997). 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 is an extension to the SNMP MIB. It specifies an IAB
standards track protocol for the Internet community, and requests standards track protocol for the Internet community, and requests
discussion and suggestions for improvements. The origin of this memo discussion and suggestions for improvements. The origin of this memo
is from RFC 1650 ''Definitions of Managed Objects for the Ethernet- is from RFC 1650 "Definitions of Managed Objects for the Ethernet-
like Interface Types using SMIv2.'' This memo extends that like Interface Types using SMIv2." This memo extends that
specification by including management information useful for the specification by including management information useful for the
management of 100BaseT 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.
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.
skipping to change at page 3, line 30 skipping to change at page 3, line 30
(8) A section on mapping of Interfaces MIB objects has (8) A section on mapping of Interfaces MIB objects has
been added. been added.
(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) Comverted 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) An intellectual property notice and copyright notice (12) Added to the The list of registered dot3ChipSets.
(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]:
ethernetCsmacd(6) ethernetCsmacd(6)
skipping to change at page 7, line 18 skipping to change at page 7, line 18
NOT use the fastEther(62) or fastEtherFX(69) ifTypes. NOT use the fastEther(62) or fastEtherFX(69) ifTypes.
Interfaces with any of the supported ifType values map to the Interfaces with any of the supported ifType values map to the
EtherLike-MIB in the same manner. Which compliance statement an EtherLike-MIB in the same manner. Which compliance statement an
interface should implement is dependent on the maximum speed interface should implement is dependent on the maximum speed
supported on the interface. The EtherLike-MIB etherCompliance supported on the interface. The EtherLike-MIB etherCompliance
compliance statement applies to all Ethernet-like interfaces whose compliance statement applies to all Ethernet-like interfaces whose
maximum supported speed is 10 Mbit/sec or less. There are no maximum supported speed is 10 Mbit/sec or less. There are no
implementation differences. Similarly, the EtherLike-MIB implementation differences. Similarly, the EtherLike-MIB
ether100MbsCompliance compliance statement applies to all Ethernet- ether100MbsCompliance compliance statement applies to all Ethernet-
like interfaces whose maximum supported speed of 100Mbit/sec. like interfaces whose maximum supported speed is 100Mbit/sec.
An interface that is capable of operating at 100Mbit/sec MUST An interface that is capable of operating at 100Mbit/sec MUST
implement the ether100MbsCompliance compliance statement, even if it implement the ether100MbsCompliance compliance statement, even if it
is currently operating at a lower speed. Counters in the is currently operating at a lower speed. Counters in the
ether100MbsCompliance compliance statement that only apply to 100 ether100MbsCompliance compliance statement that only apply to 100
Mbit interfaces would simply not increment when the interface is Mbit interfaces would simply not increment when the interface is
operating at a lower speed. operating at a lower speed.
4.2.7. Specific Interface MIB Objects 4.2.7. Specific Interface MIB Objects
skipping to change at page 13, line 19 skipping to change at page 13, line 19
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 "9711102157Z" -- November 10, 1997 LAST-UPDATED "9802172351Z" -- February 17, 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
Chair: Dan Romascanu Chair: Dan Romascanu
Postal: Madge Networks Postal: Madge Networks
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
skipping to change at page 14, line 6 skipping to change at page 14, line 6
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"
DESCRIPTION "The MIB module to describe generic objects for DESCRIPTION "The MIB module to describe generic objects for
Ethernet-like network interfaces. This MIB is an Ethernet-like network interfaces. This MIB is an
updated version of the Ethernet-like MIB in RFC updated version of the Ethernet-like MIB in RFC
1650." 1650."
REVISION "9711102157Z" REVISION "9802172351Z"
DESCRIPTION "Updated to include support for 100 Mb/sec DESCRIPTION "Updated to include support for 100 Mb/sec
interfaces." interfaces."
REVISION "9402030400Z" REVISION "9402030400Z"
DESCRIPTION "Version published as RFC 1650." DESCRIPTION "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 }
skipping to change at page 22, line 39 skipping to change at page 22, line 39
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)."
::= { dot3Tests 1 } ::= { dot3Tests 1 }
-- Loopback Test -- Loopback Test
dot3TestLoopBack OBJECT-IDENTITY dot3TestLoopBack OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "This test configures the MAC chip and executes DESCRIPTION "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.
skipping to change at page 23, line 31 skipping to change at page 23, line 31
STATUS current STATUS current
DESCRIPTION "Expected data not received (or not received DESCRIPTION "Expected data not received (or not received
correctly) in loopback test." correctly) in loopback test."
::= { dot3Errors 2 } ::= { dot3Errors 2 }
-- 802.3 Hardware Chipsets -- 802.3 Hardware Chipsets
-- The object dot3StatsEtherChipSet is provided to -- The object dot3StatsEtherChipSet is provided to
-- identify the MAC hardware used to communicate on an -- identify the MAC hardware used to communicate on an
-- interface. The following hardware chipsets are -- interface. The following hardware chipsets are
-- provided: -- registered:
dot3ChipSets OBJECT IDENTIFIER ::= { dot3 8 } dot3ChipSets OBJECT IDENTIFIER ::= { dot3 8 }
dot3ChipSetAMD OBJECT IDENTIFIER ::= { dot3ChipSets 1 } dot3ChipSetAMD OBJECT IDENTIFIER ::= { dot3ChipSets 1 }
dot3ChipSetAMD7990 OBJECT-IDENTITY dot3ChipSetAMD7990 OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "The authoritative identifier for the Advanced DESCRIPTION "The authoritative identifier for the Advanced
Micro Devices Am7990 Local Area Network Micro Devices Am7990 Local Area Network
Controller for Ethernet (LANCE)." Controller for Ethernet (LANCE)."
skipping to change at page 24, line 6 skipping to change at page 24, line 6
dot3ChipSetAMD79900 OBJECT-IDENTITY dot3ChipSetAMD79900 OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "The authoritative identifier for the Advanced DESCRIPTION "The authoritative identifier for the Advanced
Micro Devices Am79900 chip." Micro Devices Am79900 chip."
::= { dot3ChipSetAMD 2 } ::= { dot3ChipSetAMD 2 }
dot3ChipSetAMD79C940 OBJECT-IDENTITY dot3ChipSetAMD79C940 OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "The authoritative identifier for the Advanced DESCRIPTION "The authoritative identifier for the Advanced
Micro Devices am79C940 Media Access Controller Micro Devices Am79C940 Media Access Controller
for Ethernet (MACE)." for Ethernet (MACE)."
::= { dot3ChipSetAMD 3 } ::= { dot3ChipSetAMD 3 }
dot3ChipSetAMD79C90 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Advanced
Micro Devices Am79C90 CMOS Local Area Network
Controller for Ethernet (C-LANCE)."
::= { dot3ChipSetAMD 4 }
dot3ChipSetAMD79C960 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Advanced
Micro Devices Am79C960 PCnet-ISA Single Chip
Ethernet Controller for ISA."
::= { dot3ChipSetAMD 5 }
dot3ChipSetAMD79C961 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Advanced
Micro Devices Am79C961 PCnet-ISA+ Single Chip
Plug & Play Full-Duplex Ethernet Controller
for ISA."
::= { dot3ChipSetAMD 6 }
dot3ChipSetAMD79C961A OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Advanced
Micro Devices Am79C961A PCnet-ISA II Single Chip
Plug & Play Full-Duplex Ethernet Controller
for ISA."
::= { dot3ChipSetAMD 7 }
dot3ChipSetAMD79C965 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Advanced
Micro Devices Am79C965 PCnet-32 Single Chip
Ethernet Controller for PCI."
::= { dot3ChipSetAMD 8 }
dot3ChipSetAMD79C970 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Advanced
Micro Devices Am79C970 PCnet PCI Single Chip
Ethernet Controller for PCI Local Bus."
::= { dot3ChipSetAMD 9 }
dot3ChipSetAMD79C970A OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Advanced
Micro Devices AM79C970A PCnet PCI II Single Chip
Full-Duplex Ethernet Controller for PCI Local
Bus."
::= { dot3ChipSetAMD 10 }
dot3ChipSetAMD79C971 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Advanced
Micro Devices Am79C971 PCnet-FAST Single Chip
Full-Duplex 10/100 Mbps Ethernet Controller for
PCI Local Bus."
::= { dot3ChipSetAMD 11 }
dot3ChipSetAMD79C972 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Advanced
Micro Devices Am79C972 PCnet-FAST+ Enhanced
10/100 Mbps PCI Ethernet Controller with OnNow
Support."
::= { dot3ChipSetAMD 12 }
dot3ChipSetIntel OBJECT IDENTIFIER ::= { dot3ChipSets 2 } dot3ChipSetIntel OBJECT IDENTIFIER ::= { dot3ChipSets 2 }
dot3ChipSetIntel82586 OBJECT-IDENTITY dot3ChipSetIntel82586 OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "The authoritative identifier for the Intel DESCRIPTION "The authoritative identifier for the Intel
82586 IEEE 802.3 Ethernet LAN Coprocessor." 82586 IEEE 802.3 Ethernet LAN Coprocessor."
::= { dot3ChipSetIntel 1 } ::= { dot3ChipSetIntel 1 }
dot3ChipSetIntel82596 OBJECT-IDENTITY dot3ChipSetIntel82596 OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "The authoritative identifier for the Intel DESCRIPTION "The authoritative identifier for the Intel
82596 High-Performance 32-Bit Local Area Network 82596 High-Performance 32-Bit Local Area Network
Coprocessor." Coprocessor."
::= { dot3ChipSetIntel 2 } ::= { dot3ChipSetIntel 2 }
dot3ChipSetIntel82595 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Intel
82595 High Integration Ethernet Controller."
::= { dot3ChipSetIntel 3 }
dot3ChipSetIntel82557 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Intel
82557 Fast Ethernet PCI Bus Lan Controller."
::= { dot3ChipSetIntel 4 }
dot3ChipSetIntel82558 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Intel
82558 Fast Ethernet PCI Bus LAN Controller with
Integrated PHY."
::= { dot3ChipSetIntel 5 }
dot3ChipSetSeeq OBJECT IDENTIFIER ::= { dot3ChipSets 3 } dot3ChipSetSeeq OBJECT IDENTIFIER ::= { dot3ChipSets 3 }
dot3ChipSetSeeq8003 OBJECT-IDENTITY dot3ChipSetSeeq8003 OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "The authoritative identifier for the SEEQ DESCRIPTION "The authoritative identifier for the SEEQ
8003 chip set." 8003 chip set."
::= { dot3ChipSetSeeq 1 } ::= { dot3ChipSetSeeq 1 }
dot3ChipSetSeeq80C03 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the SEEQ
80C03 Full-Duplex CMOS Ethernet Data Link
Controller (MAC)."
::= { dot3ChipSetSeeq 2 }
dot3ChipSetSeeq84C30 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the SEEQ
4-Port 84C30 Full-Duplex CMOS Ethernet 10
MBit/Sec Data Link Controller (MAC)."
::= { dot3ChipSetSeeq 3 }
dot3ChipSetSeeq8431 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the SEEQ
4-Port 8431 Full-Duplex CMOS Ethernet 10
MBit/Sec Data Link Controller (MAC)."
::= { dot3ChipSetSeeq 4 }
dot3ChipSetSeeq80C300 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the SEEQ
80C300 Full-Duplex CMOS Ethernet 10/100
Mbit/Sec Data Link Controller (MAC)."
::= { dot3ChipSetSeeq 5 }
dot3ChipSetSeeq84C300 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the SEEQ
4-Port 84C300 Fast Ethernet Controller (MAC)."
::= { dot3ChipSetSeeq 6 }
dot3ChipSetSeeq84301 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the SEEQ
4-Port 84301 Fast Ethernet Controller (MAC)."
::= { dot3ChipSetSeeq 7 }
dot3ChipSetSeeq84302 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the SEEQ
4-Port 84302 Fast Ethernet Controller (MAC)."
::= { dot3ChipSetSeeq 8 }
dot3ChipSetSeeq8100 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the SEEQ
8100 Gigabit Ethernet Controller (MAC & PCS)."
::= { dot3ChipSetSeeq 9 }
dot3ChipSetNational OBJECT IDENTIFIER ::= { dot3ChipSets 4 } dot3ChipSetNational OBJECT IDENTIFIER ::= { dot3ChipSets 4 }
dot3ChipSetNational8390 OBJECT-IDENTITY dot3ChipSetNational8390 OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "The authoritative identifier for the National DESCRIPTION "The authoritative identifier for the National
Semiconductor DP8390 Network Interface Semiconductor DP8390 Network Interface
Controller." Controller."
::= { dot3ChipSetNational 1 } ::= { dot3ChipSetNational 1 }
dot3ChipSetNationalSonic OBJECT-IDENTITY dot3ChipSetNationalSonic OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "The authoritative identifier for the National DESCRIPTION "The authoritative identifier for the National
Semiconductor DP83932 Systems-Oriented Network Semiconductor DP83932 Systems-Oriented Network
Interface Controller (SONIC)." Interface Controller (SONIC)."
::= { dot3ChipSetNational 2 } ::= { dot3ChipSetNational 2 }
dot3ChipSetNational83901 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the National
Semiconductor DP83901 Serial Network Interface
Controller (SNIC)."
::= { dot3ChipSetNational 3 }
dot3ChipSetNational83902 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the National
Semiconductor DP83902 Serial Network Interface
Controller for Twisted Pair (ST-NIC)."
::= { dot3ChipSetNational 4 }
dot3ChipSetNational83905 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the National
Semiconductor DP83905 AT Local Area Network
Twisted-Pair Interface (AT/LANTIC)."
::= { dot3ChipSetNational 5 }
dot3ChipSetNational83907 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the National
Semiconductor DP83907 AT Twisted-Pair Enhanced
Coaxial Network Interface Controller
(AT/LANTIC II)."
::= { dot3ChipSetNational 6 }
dot3ChipSetNational83916 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the National
Semiconductor DP83916 Systems-Oriented Network
Interface Controller (SONIC-16)."
::= { dot3ChipSetNational 7 }
dot3ChipSetNational83934 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the National
Semiconductor DP83934 Systems-Oriented Network
Interface Controller with Twisted Pair Interface
(SONIC-T)."
::= { dot3ChipSetNational 8 }
dot3ChipSetNational83936 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the National
Semiconductor DP83936AVUL Full-Duplex Systems-
Oriented Network Interface Controller with
Twisted Pair Interface (SONIC-T)."
::= { dot3ChipSetNational 9 }
dot3ChipSetFujitsu OBJECT IDENTIFIER ::= { dot3ChipSets 5 } dot3ChipSetFujitsu OBJECT IDENTIFIER ::= { dot3ChipSets 5 }
dot3ChipSetFujitsu86950 OBJECT-IDENTITY dot3ChipSetFujitsu86950 OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "The authoritative identifier for the Fujitsu DESCRIPTION "The authoritative identifier for the Fujitsu
86950 chip." 86950 chip."
::= { dot3ChipSetFujitsu 1 } ::= { dot3ChipSetFujitsu 1 }
dot3ChipSetFujitsu86960 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Fujitsu
MB86960 Network Interface Controller with
Encoder/Decoder (NICE)."
::= { dot3ChipSetFujitsu 2 }
dot3ChipSetFujitsu86964 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Fujitsu
MB86964 Ethernet Controller with 10BASE-T
Tranceiver."
::= { dot3ChipSetFujitsu 3 }
dot3ChipSetFujitsu86965A OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Fujitsu
MB86965A EtherCoupler Single-Chip Ethernet
Controller."
::= { dot3ChipSetFujitsu 4 }
dot3ChipSetFujitsu86965B OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Fujitsu
MB86965B EtherCoupler Single-Chip Ethernet
Controller (supports full-duplex)."
::= { dot3ChipSetFujitsu 5 }
dot3ChipSetDigital OBJECT IDENTIFIER ::= { dot3ChipSets 6 } dot3ChipSetDigital OBJECT IDENTIFIER ::= { dot3ChipSets 6 }
dot3ChipSetDigitalDC21040 OBJECT-IDENTITY dot3ChipSetDigitalDC21040 OBJECT-IDENTITY
STATUS current STATUS current
DESCRIPTION "The authoritative identifier for the Digital DESCRIPTION "The authoritative identifier for the Digital
DC21040 chip." Semiconductor DC21040 chip."
::= { dot3ChipSetDigital 1 } ::= { dot3ChipSetDigital 1 }
dot3ChipSetDigital21041 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Digital
Semiconductor 21041 PCI Ethernet LAN
Controller."
::= { dot3ChipSetDigital 2 }
dot3ChipSetDigital21140 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Digital
Semiconductor 21140 PCI Fast Ethernet LAN
Controller."
::= { dot3ChipSetDigital 3 }
dot3ChipSetDigital21143 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Digital
Semiconductor 21143 PCI/CardBus 10/100-Mb/s
Ethernet LAN Controller."
::= { dot3ChipSetDigital 4 }
dot3ChipSetDigital21340 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Digital
Semiconductor 21340 10/100-MB/s managed buffered
port switch."
::= { dot3ChipSetDigital 5 }
dot3ChipSetDigital21440 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Digital
Semiconductor 21440 Multiport 10/100Mbps
Ethernet Controller."
::= { dot3ChipSetDigital 6 }
dot3ChipSetDigital21540 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Digital
Semiconductor 21540 PCI/CardBus Ethernet LAN
Controller with Modem Interface."
::= { dot3ChipSetDigital 7 }
dot3ChipSetTI OBJECT IDENTIFIER ::= { dot3ChipSets 7 }
dot3ChipSetTIE100 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Texas
Instruments TNETE100 ThunderLAN PCI Fast
Ethernet Controller."
::= { dot3ChipSetTI 1 }
dot3ChipSetTIE110 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Texas
Instruments TNETE110 ThunderLAN PCI 10BASE-T
Ethernet Adapter."
::= { dot3ChipSetTI 2 }
dot3ChipSetTIX3100 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Texas
Instruments TNETX3100 Desktop ThunderSWITCH
8/2."
::= { dot3ChipSetTI 3 }
dot3ChipSetTIX3150 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Texas
Instruments TNETX3150 ThunderSWITCH 12/3."
::= { dot3ChipSetTI 4 }
dot3ChipSetTIX3270 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Texas
Instruments TNETX3270 ThunderSWITCH 24/3."
::= { dot3ChipSetTI 5 }
dot3ChipSetToshiba OBJECT IDENTIFIER ::= { dot3ChipSets 8 }
dot3ChipSetToshibaTC35815F OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Toshiba
TC35815F PCI-Based 100/10Mbps Ethernet
Controller."
::= { dot3ChipSetToshiba 1 }
dot3ChipSetLucent OBJECT IDENTIFIER ::= { dot3ChipSets 9 }
dot3ChipSetLucentATT1MX10 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Lucent
Technologies ATT1MX10 (Spinnaker) Quad MAC and
Tranceiver for Ethernet Frame Switching."
::= { dot3ChipSetLucent 1 }
dot3ChipSetLucentLUC3M08 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Lucent
Technologies LUC3M08 Eight Ethernet MACs for
10/100 Mbits/s Frame Switching."
::= { dot3ChipSetLucent 2 }
dot3ChipSetGalileo OBJECT IDENTIFIER ::= { dot3ChipSets 10 }
dot3ChipSetGalileoGT48001 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Galileo
Technology GT-48001A Switched Ethernet
Controller."
::= { dot3ChipSetGalileo 1 }
dot3ChipSetGalileoGT48002 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Galileo
Technology GT-48002A Switched Fast Ethernet
Controller."
::= { dot3ChipSetGalileo 2 }
dot3ChipSetGalileoGT48004 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Galileo
Technology GT-48004A Four Port Fast Ethernet
Switch for Multiport 10/100BASE-X Systems."
::= { dot3ChipSetGalileo 3 }
dot3ChipSetGalileoGT48207 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Galileo
Technology GT-48207 Low-Cost 10 Port Switched
Ethernet Controller for 10+10/100BASE-X."
::= { dot3ChipSetGalileo 4 }
dot3ChipSetGalileoGT48208 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Galileo
Technology GT-48208 Advanced 10 Port Switched
Ethernet Controller for 10+10/100BASE-X."
::= { dot3ChipSetGalileo 5 }
dot3ChipSetGalileoGT48212 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Galileo
Technology GT-48212 Advanced 14 Port Switched
Ethernet Controller for 10+10/100BASE-X."
::= { dot3ChipSetGalileo 6 }
dot3ChipSetJato OBJECT IDENTIFIER ::= { dot3ChipSets 11 }
dot3ChipSetJatoJT1001 OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the Jato
Technologies JT1001 GigEMAC Server
10/100/1000Mbps Ethernet Controller with PCI
interface."
::= { dot3ChipSetJato 1 }
dot3ChipSetXaQti OBJECT IDENTIFIER ::= { dot3ChipSets 12 }
dot3ChipSetXaQtiXQ11800FP OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the XaQTI
XQ11800FP XMAC II Gigabit Ethernet Media Access
Controller."
::= { dot3ChipSetXaQti 1 }
dot3ChipSetXaQtiXQ18110FP OBJECT-IDENTITY
STATUS current
DESCRIPTION "The authoritative identifier for the XaQTI
XQ18110FP GigaPower Protocol Accelerator."
::= { 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
-- deletaged to individual enterprises (see RFC1155). -- delegated to individual enterprises (see RFC1155).
-- 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 30, line 13 skipping to change at page 38, line 13
January 1993. January 1993.
[10] Kastenholz, F., "Definitions of Managed Objects for the [10] Kastenholz, F., "Definitions of Managed Objects for the
Ethernet-like Interface Types", RFC 1623, FTP Software, Inc., Ethernet-like Interface Types", RFC 1623, FTP Software, Inc.,
May 1994. May 1994.
[11] Kastenholz, F., "Definitions of Managed Objects for the [11] Kastenholz, F., "Definitions of Managed Objects for the
Ethernet-like Interface Types using SMIv2", RFC 1650, Ethernet-like Interface Types using SMIv2", RFC 1650,
FTP Software, Inc., August 1994. FTP Software, Inc., August 1994.
[12] McCloghrie, K., and F. Kastenholz, "Evolution of the Interfaces [12] McCloghrie, K., and F. Kastenholz, "The Interfaces Group MIB
Group of MIB-II", RFC 1573, Hughes LAN Systems, FTP Software, using SMIv2", RFC 2233, Cisco Systems, FTP Software,
January 1994. November 1997.
[13] Bradner, S., "Key words for use in RFCs to Indicate [13] 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.
[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", RFCXXXX, 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., October 1997. Inc., Cisco Systems Inc., Farallon Computing Inc., November
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 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
skipping to change at page 32, line 24 skipping to change at page 40, line 24
4.2.1. Layering Model ......................................... 5 4.2.1. Layering Model ......................................... 5
4.2.2. Virtual Circuits ....................................... 5 4.2.2. Virtual Circuits ....................................... 5
4.2.3. ifTestTable ............................................ 5 4.2.3. ifTestTable ............................................ 5
4.2.4. ifRcvAddressTable ...................................... 5 4.2.4. ifRcvAddressTable ...................................... 5
4.2.5. ifPhysAddress .......................................... 6 4.2.5. ifPhysAddress .......................................... 6
4.2.6. ifType ................................................. 6 4.2.6. ifType ................................................. 6
4.2.7. Specific Interface MIB Objects ......................... 7 4.2.7. Specific Interface MIB Objects ......................... 7
4.3. Relation to the 802.3 MAU MIB ............................ 10 4.3. Relation to the 802.3 MAU MIB ............................ 10
4.4. Mapping of IEEE 802.3 Managed Objects .................... 10 4.4. Mapping of IEEE 802.3 Managed Objects .................... 10
5. Definitions ................................................ 13 5. Definitions ................................................ 13
6. Intellectual Property ...................................... 28 6. Intellectual Property ...................................... 36
7. Acknowledgements ........................................... 28 7. Acknowledgements ........................................... 36
8. References ................................................. 29 8. References ................................................. 37
9. Security Considerations .................................... 30 9. Security Considerations .................................... 38
10. Author's Addresses ........................................ 30 10. Author's Addresses ........................................ 38
11. Full Copyright Statement .................................. 31 11. Full Copyright Statement .................................. 39
 End of changes. 

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