draft-ietf-hubmib-etherif-mib-v2-00.txt | draft-ietf-hubmib-etherif-mib-v2-01.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 | |||
August 1998 | November 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-v2-00.txt> | <draft-ietf-hubmib-etherif-mib-v2-01.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 2, line 4 | skipping to change at page 2, line 4 | |||
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. | |||
Ethernet technology, as defined by the 802.3 Working Group of the | Ethernet technology, as defined by the 802.3 Working Group of the | |||
IEEE, continues to evolve, with scalable increases in speed, new | IEEE, continues to evolve, with scalable increases in speed, new | |||
types of cabling and interfaces, and new features. This evolution | types of cabling and interfaces, and new features. This evolution | |||
may require changes in the managed objects in order to reflect this | may require changes in the managed objects in order to reflect this | |||
new functionality. This document, as with other documents issued by | new functionality. This document, as with other documents issued by | |||
this working group, reflect a certain stage in the evolution of | this working group, reflects a certain stage in the evolution of | |||
Ethernet technology. In the future, this document might be revised, | Ethernet technology. In the future, this document might be revised, | |||
or new documents might be issued by the Ethernet Interfaces and Hub | or new documents might be issued by the Ethernet Interfaces and Hub | |||
MIB Working Group, in order to reflect the evolution of Ethernet | MIB Working Group, in order to reflect the evolution of Ethernet | |||
technology. | technology. | |||
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 | |||
skipping to change at page 2, line 28 | skipping to change at page 2, line 28 | |||
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 ................................................. 7 | |||
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 ............................ 11 | |||
3.4. Mapping of IEEE 802.3 Managed Objects .................... 11 | 3.4. dot3StatsEtherChipSet .................................... 11 | |||
4. Definitions ................................................ 12 | 3.5. Mapping of IEEE 802.3 Managed Objects .................... 11 | |||
5. Intellectual Property ...................................... 40 | 4. Definitions ................................................ 14 | |||
6. Acknowledgements ........................................... 41 | 5. Intellectual Property ...................................... 35 | |||
7. References ................................................. 42 | 6. Acknowledgements ........................................... 36 | |||
8. Security Considerations .................................... 45 | 7. References ................................................. 37 | |||
9. Author's Addresses ......................................... 45 | 8. Security Considerations .................................... 40 | |||
A. Change Log ................................................. 46 | 9. Author's Addresses ......................................... 40 | |||
A.1. Changes since RFC 2358 ................................... 46 | A. Change Log ................................................. 41 | |||
A.2. Changes between RFC 1650 and RFC 2358 .................... 47 | A.1. Changes since RFC 2358 ................................... 41 | |||
B. Full Copyright Statement ................................... 47 | A.2. Changes between RFC 1650 and RFC 2358 .................... 42 | |||
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 | |||
interfaces. | interfaces. | |||
This memo also includes a MIB module. This MIB module extends the | This memo also includes a MIB module. This MIB module extends 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: | |||
RFC2358 [26]. | ||||
RFC 2358 [23]. | ||||
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 [29]. | document are to be interpreted as described in [26]. | |||
2. The SNMP Management Framework | 2. The SNMP Management Framework | |||
The SNMP Management Framework presently consists of five major | The SNMP Management Framework presently consists of five major | |||
components: | components: | |||
o An overall architecture, described in RFC 2271 [1]. | o An overall architecture, described in RFC 2271 [1]. | |||
o Mechanisms for describing and naming objects and events for the | o Mechanisms for describing and naming objects and events for the | |||
purpose of management. The first version of this Structure of | purpose of management. The first version of this Structure of | |||
skipping to change at page 4, line 11 | skipping to change at page 4, line 13 | |||
information in SMIv2 will be converted into textual descriptions in | information in SMIv2 will be converted into textual descriptions in | |||
SMIv1 during the translation process. However, this loss of machine | SMIv1 during the translation process. However, this loss of machine | |||
readable information is not considered to change the semantics of the | readable information is not considered to change the semantics of the | |||
MIB. | 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 following values of the ifType object in | media are identified by the following values of the ifType object in | |||
the Interfaces MIB [28]: | the Interfaces MIB [25]: | |||
ethernetCsmacd(6) | ethernetCsmacd(6) | |||
iso88023Csmacd(7) | iso88023Csmacd(7) | |||
starLan(11) | starLan(11) | |||
The definitions presented here are based on IEEE Draft 802.3z/D4.2, | The definitions presented here are based on Section 30, "10 Mb/s, 100 | |||
Section 30 [19], as originally interpreted by Frank Kastenholz then | Mb/s and 1000 Mb/s Management", and Annex 30A, "GDMO Specification | |||
of Interlan in [20]. Implementors of these MIB objects should note | for 802.3 managed object classes" of IEEE Std. 802.3, 1998 Edition | |||
that IEEE Std. 802.3 ([16], [17], and [18]) and IEEE Draft 802.3z | [16], as originally interpreted by Frank Kastenholz then of Interlan | |||
[19] explicitly describe (in the form of Pascal pseudocode) when, | in [17]. Implementors of these MIB objects should note that IEEE | |||
where, and how various MAC attributes are measured. The IEEE | Std. 802.3 [16] explicitly describes (in the form of Pascal | |||
documents also describe the effects of MAC actions that may be | pseudocode) when, where, and how various MAC attributes are measured. | |||
invoked by manipulating instances of the MIB objects defined here. | The IEEE document also describes the effects of MAC actions that may | |||
be invoked by manipulating instances of the MIB objects defined here. | ||||
To the extent that some of the attributes defined in [19] are | To the extent that some of the attributes defined in [16] are | |||
represented by previously defined objects in MIB-2 [27] or in the | represented by previously defined objects in MIB-2 [24] or in the | |||
Interfaces MIB [28], such attributes are not redundantly represented | Interfaces MIB [25], such attributes are not redundantly represented | |||
by objects defined in this memo. Among the attributes represented by | by objects defined in this memo. Among the attributes represented by | |||
objects defined in other memos are the number of octets transmitted | objects defined in other memos are the number of octets transmitted | |||
or received on a particular interface, the number of frames | or received on a particular interface, the number of frames | |||
transmitted or received on a particular interface, the promiscuous | transmitted or received on a particular interface, the promiscuous | |||
status of an interface, the MAC address of an interface, and | status of an interface, the MAC address of an interface, and | |||
multicast information associated with an interface. | multicast information associated with an interface. | |||
3.1. Relation to MIB-2 | 3.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) [27] interface group. | the "old" (RFC 1213) [24] 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 MIB-2 is one-to-one. As such, the value of an | |||
the value of an ifIndex object instance can be directly used to | ifIndex object instance can be directly used to identify | |||
identify corresponding instances of the objects defined herein. | 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: | |||
dot3 OBJECT IDENTIFER ::= { transmission 7 } | dot3 OBJECT IDENTIFER ::= { transmission 7 } | |||
3.2. Relation to the Interfaces MIB | 3.2. Relation to the Interfaces MIB | |||
The Interface MIB [28] requires that any MIB which is an adjunct of | The Interface MIB [25] requires that any MIB which is an adjunct of | |||
the Interface MIB clarify specific areas within the Interface MIB. | the Interface MIB clarify specific areas within the Interface MIB. | |||
These areas were intentionally left vague in the Interface MIB to | These areas were intentionally left vague in the Interface MIB to | |||
avoid over constraining the MIB, thereby precluding management of | avoid over constraining the MIB, thereby precluding management of | |||
certain media-types. | certain media-types. | |||
Section 3.3 of [28] enumerates several areas which a media-specific | Section 3.3 of [25] enumerates several areas which a media-specific | |||
MIB must clarify. Each of these areas is addressed in a following | MIB must clarify. Each of these areas is addressed in a following | |||
subsection. The implementor is referred to [28] in order to | subsection. The implementor is referred to [25] in order to | |||
understand the general intent of these areas. | understand the general intent of these areas. | |||
3.2.1. Layering Model | 3.2.1. Layering Model | |||
This MIB does not provide for layering. There are no sublayers. | This MIB does not provide for layering. There are no sublayers. | |||
EDITOR'S NOTE: | EDITOR'S NOTE: | |||
One could foresee the development of an 802.2 and enet-transceiver | One could foresee the development of an 802.2 and enet-transceiver | |||
MIB. They could be higher and lower sublayers, respectively. All | MIB. They could be higher and lower sublayers, respectively. All | |||
skipping to change at page 7, line 20 | skipping to change at page 7, line 21 | |||
ethernetCsmacd(6) | ethernetCsmacd(6) | |||
iso88023Csmacd(7) | iso88023Csmacd(7) | |||
starLan(11) | starLan(11) | |||
It is RECOMMENDED that all Ethernet-like interfaces use an ifType of | It is RECOMMENDED that all Ethernet-like interfaces use an ifType of | |||
ethernetCsmacd(6) regardless of the speed that the interface is | ethernetCsmacd(6) regardless of the speed that the interface is | |||
running or the link-layer encapsulation in use. iso88023Csmacd(7) | running or the link-layer encapsulation in use. iso88023Csmacd(7) | |||
and starLan(11) are supported for backwards compatability. | and starLan(11) are supported for backwards compatability. | |||
There are three other interface types defined in the IANAifType-MIB | There are three other interface types defined in the IANAifType-MIB | |||
for 100 Mbit Ethernet. They are fastEther(62), fastEtherFX(69), and | for Ethernet. They are fastEther(62), fastEtherFX(69), and | |||
gigabitEthernet(117). This document takes the position that an | gigabitEthernet(117). This document takes the position that an | |||
Ethernet is an Ethernet, and Ethernet interfaces SHOULD always have | Ethernet is an Ethernet, and Ethernet interfaces SHOULD always have | |||
the same value of ifType. Information on the particular flavor of | the same value of ifType. Information on the particular flavor of | |||
Ethernet that an interface is running is available from ifSpeed in | Ethernet that an interface is running is available from ifSpeed in | |||
the Interfaces MIB, and ifMauType in the 802.3 MAU MIB. An | the Interfaces MIB, and ifMauType in the 802.3 MAU MIB. An | |||
Ethernet-like interface SHOULD NOT use the fastEther(62), | Ethernet-like interface SHOULD NOT use the fastEther(62), | |||
fastEtherFX(69), or gigabitEthernet(117) ifTypes. | fastEtherFX(69), or gigabitEthernet(117) 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. There are no implementation | |||
interface should implement is dependent on the maximum speed | differences. | |||
supported on the interface. The EtherLike-MIB etherCompliance | ||||
compliance statement applies to all Ethernet-like interfaces whose | ||||
maximum supported speed is 10 Mbit/sec or less. There are no | ||||
implementation differences. Similarly, the EtherLike-MIB | ||||
ether100MbsCompliance compliance statement applies to all Ethernet- | ||||
like interfaces whose maximum supported speed is 100Mbit/sec. | ||||
An interface that is capable of operating at 100Mbit/sec MUST | ||||
implement the ether100MbsCompliance compliance statement, even if it | ||||
is currently operating at a lower speed. Counters in the | ||||
ether100MbsCompliance compliance statement that only apply to 100 | ||||
Mbit interfaces would simply not increment when the interface is | ||||
operating at a lower speed. | ||||
3.2.7. Specific Interface MIB Objects | 3.2.7. Specific Interface MIB Objects | |||
The following table provides specific implementation guidelines for | The following table provides specific implementation guidelines for | |||
applying the interface group objects to ethernet-like media. | applying the interface group objects to ethernet-like media. | |||
Object | Object | |||
ifIndex Each ethernet-like interface is | ifIndex Each ethernet-like interface is | |||
represented by an ifEntry. The | represented by an ifEntry. The | |||
dot3StatsTable in this MIB module is | dot3StatsTable in this MIB module is | |||
indexed by dot3StatsIndex. The interface | indexed by dot3StatsIndex. The interface | |||
identified by a particular value of | identified by a particular value of | |||
dot3StatsIndex is the same interface as | dot3StatsIndex is the same interface as | |||
identified by the same value of ifIndex. | identified by the same value of ifIndex. | |||
ifDescr Refer to [28]. | ifDescr Refer to [25]. | |||
ifType Refer to section 3.2.6. | ifType Refer to section 3.2.6. | |||
ifMtu 1500 octets. NOTE: This is the MTU as | ifMtu 1500 octets. NOTE: This is the MTU as | |||
seen by the MAC client. When a higher | seen by the MAC client. When a higher | |||
layer protocol, like IP, is running over | layer protocol, like IP, is running over | |||
Ethernet, this is the MTU that will be | Ethernet, this is the MTU that will be | |||
seen by that higher layer protocol. | seen by that higher layer protocol. | |||
However, when using the IEEE 802.2 LLC | However, when using the IEEE 802.2 LLC | |||
protocol, higher layer protocols will | protocol, higher layer protocols will | |||
skipping to change at page 8, line 46 | skipping to change at page 8, line 37 | |||
auto-negotiation, auto-negotiation is | auto-negotiation, auto-negotiation is | |||
enabled for this interface, and the | enabled for this interface, and the | |||
interface has not yet negotiated to an | interface has not yet negotiated to an | |||
operational speed, this object SHOULD | operational speed, this object SHOULD | |||
reflect the maximum speed supported by | reflect the maximum speed supported by | |||
the interface. Note that this object | the interface. Note that this object | |||
MUST NOT indicate a doubled value when | MUST NOT indicate a doubled value when | |||
operating in full-duplex mode. It MUST | operating in full-duplex mode. It MUST | |||
indicate the correct line speed | indicate the correct line speed | |||
regardless of the current duplex mode. | regardless of the current duplex mode. | |||
The correct object to use to determine | The duplex mode of the interface may | |||
the duplex mode of the interface is the | be determined by examining either the | |||
ifMauType object in the 802.3 MAU MIB. | dot3StatsDuplexStatus object in this | |||
MIBmodule, or the ifMauType object in | ||||
the 802.3 MAU MIB. | ||||
ifPhysAddress Refer to section 3.2.5. | ifPhysAddress Refer to section 3.2.5. | |||
ifAdminStatus Write access is not required. Support | ifAdminStatus Write access is not required. Support | |||
for 'testing' is not required. | for 'testing' is not required. | |||
ifOperStatus The operational state of the interface. | ifOperStatus The operational state of the interface. | |||
Support for 'testing' is not required. | Support for 'testing' is not required. | |||
The value 'dormant' has no meaning for | The value 'dormant' has no meaning for | |||
an ethernet-like interface. | an ethernet-like interface. | |||
ifLastChange Refer to [28]. | ifLastChange Refer to [25]. | |||
ifInOctets The number of octets in valid MAC frames | ifInOctets The number of octets in valid MAC frames | |||
received on this interface, including | received on this interface, including | |||
the MAC header and FCS. | the MAC header and FCS. | |||
ifInUcastPkts Refer to [28]. | ifInUcastPkts Refer to [25]. | |||
ifInDiscards Refer to [28]. | ifInDiscards Refer to [25]. | |||
ifInErrors The sum for this interface of | ifInErrors The sum for this interface of | |||
dot3StatsAlignmentErrors, | dot3StatsAlignmentErrors, | |||
dot3StatsFCSErrors, | dot3StatsFCSErrors, | |||
dot3StatsFrameTooLongs, | dot3StatsFrameTooLongs, | |||
dot3StatsInternalMacReceiveErrors and | dot3StatsInternalMacReceiveErrors and | |||
dot3StatsSymbolErrors. | dot3StatsSymbolErrors. | |||
ifInUnknownProtos Refer to [28]. | ifInUnknownProtos Refer to [25]. | |||
ifOutOctets The number of octets transmitted in | ifOutOctets The number of octets transmitted in | |||
valid MAC frames on this interface, | valid MAC frames on this interface, | |||
including the MAC header and FCS. | including the MAC header and FCS. | |||
ifOutUcastPkts Refer to [28]. | ifOutUcastPkts Refer to [25]. | |||
ifOutDiscards Refer to [28]. | ifOutDiscards Refer to [25]. | |||
ifOutErrors The sum for this interface of: | ifOutErrors The sum for this interface of: | |||
dot3StatsSQETestErrors, | dot3StatsSQETestErrors, | |||
dot3StatsLateCollisions, | dot3StatsLateCollisions, | |||
dot3StatsExcessiveCollisions, | dot3StatsExcessiveCollisions, | |||
dot3StatsInternalMacTransmitErrors and | dot3StatsInternalMacTransmitErrors and | |||
dot3StatsCarrierSenseErrors. | dot3StatsCarrierSenseErrors. | |||
ifName Locally-significant textual name for the | ifName Locally-significant textual name for the | |||
interface (e.g. lan0). | interface (e.g. lan0). | |||
ifInMulticastPkts Refer to [28]. | ifInMulticastPkts Refer to [25]. | |||
ifInBroadcastPkts Refer to [28]. | ifInBroadcastPkts Refer to [25]. | |||
ifOutMulticastPkts Refer to [28]. | ifOutMulticastPkts Refer to [25]. | |||
ifOutBroadcastPkts Refer to [28]. | ifOutBroadcastPkts Refer to [25]. | |||
ifHCInOctets 64-bit versions of counters. Required | ifHCInOctets 64-bit versions of counters. Required | |||
ifHCOutOctets for ethernet-like interfaces that are | ifHCOutOctets for ethernet-like interfaces that are | |||
capable of operating at 20Mbit/sec or | capable of operating at 20Mbit/sec or | |||
faster, even if the interface is | faster, even if the interface is | |||
currently operating at less than | currently operating at less than | |||
20Mbit/sec. | 20Mbit/sec. | |||
ifHCInUcastPkts 64-bit versions of packet counters. | ifHCInUcastPkts 64-bit versions of packet counters. | |||
ifHCInMulticastPkts Support for these counters is not | ifHCInMulticastPkts Required for ethernet-like interfaces | |||
ifHCInBroadcastPkts required for the interface types | ifHCInBroadcastPkts that are capable of operating at | |||
ifHCOutUcastPkts supported by this MIB. They are only | ifHCOutUcastPkts 640Mbit/sec or faster, even if the | |||
ifHCOutMulticastPkts required for interfaces capable of | ifHCOutMulticastPkts interface is currently operating at | |||
ifHCOutBroadcastPkts operating at 640Mbit/sec or faster. | ifHCOutBroadcastPkts less than 640Mbit/sec. | |||
Note that a future revision of this | ||||
document may support faster interfaces, | ||||
and therefore may require support for | ||||
these counters. | ||||
ifLinkUpDownTrapEnable Refer to [28]. Default is 'enabled' | ifLinkUpDownTrapEnable Refer to [25]. Default is 'enabled' | |||
ifHighSpeed The current operational speed of the | ifHighSpeed The current operational speed of the | |||
interface in millions of bits per | interface in millions of bits per | |||
second. For current ethernet-like | second. For current ethernet-like | |||
interfaces, this will be equal to 1, 10, | interfaces, this will be equal to 1, 10, | |||
100, or 1,000. If the interface | 100, or 1,000. If the interface | |||
implements auto-negotiation, | implements auto-negotiation, | |||
auto-negotiation is enabled for this | auto-negotiation is enabled for this | |||
interface, and the interface has not yet | interface, and the interface has not yet | |||
negotiated to an operational speed, this | negotiated to an operational speed, this | |||
object SHOULD reflect the maximum speed | object SHOULD reflect the maximum speed | |||
supported by the interface. Note that | supported by the interface. Note that | |||
this object MUST NOT indicate a doubled | this object MUST NOT indicate a doubled | |||
value when operating in full-duplex | value when operating in full-duplex | |||
mode. It MUST indicate the correct line | mode. It MUST indicate the correct line | |||
speed regardless of the current duplex | speed regardless of the current duplex | |||
mode. The correct object to use to | mode. The duplex mode of the interface | |||
determine the duplex mode of the | may be determined by examining either | |||
interface is the ifMauType object in the | the dot3StatsDuplexStatus object in this | |||
802.3 MAU MIB. | MIB module, or the ifMauType object in | |||
the 802.3 MAU MIB. | ||||
ifPromiscuousMode Refer to [28]. | ifPromiscuousMode Refer to [25]. | |||
ifConnectorPresent This will normally be 'true'. | ifConnectorPresent This will normally be 'true'. | |||
ifAlias Refer to [28]. | ifAlias Refer to [25]. | |||
ifCounterDiscontinuityTime Refer to [28]. | ifCounterDiscontinuityTime Refer to [25]. | |||
ifStackHigherLayer Refer to section 3.2.1. | ifStackHigherLayer Refer to section 3.2.1. | |||
ifStackLowerLayer | ifStackLowerLayer | |||
ifStackStatus | ifStackStatus | |||
ifRcvAddressAddress Refer to section 3.2.4. | ifRcvAddressAddress Refer to section 3.2.4. | |||
ifRcvAddressStatus | ifRcvAddressStatus | |||
ifRcvAddressType | ifRcvAddressType | |||
3.3. Relation to the 802.3 MAU MIB | 3.3. Relation to the 802.3 MAU MIB | |||
Support for the mauModIfCompl compliance statement of the MAU-MIB | Support for the mauModIfCompl2 compliance statement of the MAU-MIB | |||
[30] is REQUIRED for Ethernet-like interfaces. This MIB is needed in | [27] is REQUIRED for Ethernet-like interfaces. This MIB is needed in | |||
order to allow applications to determine the current MAU type in use | order to allow applications to determine the current MAU type in use | |||
by the interface. The MAU type indicates not only the media type in | by the interface, and to control autonegotiation and duplex mode for | |||
use, but also indicates whether the interface is operating in half- | the interface. Implementing this MIB module without implementing the | |||
duplex or full-duplex mode. Implementing this MIB module without | MAU-MIB would leave applications with no standard way to determine | |||
implementing the MAU-MIB would leave applications with no standard | the media type in use, and no standard way to control the duplex mode | |||
way to determine the duplex mode of the interface. | of the interface. | |||
3.4. Mapping of IEEE 802.3 Managed Objects | 3.4. dot3StatsEtherChipSet | |||
This document defines an object called dot3StatsEtherChipSet, which | ||||
is used to identify the MAC hardware used to communicate on an | ||||
interface. Previous versions of this document contained a number of | ||||
OID assignments for some existing Ethernet chipsets. Maintaining | ||||
that list as part of this document has proven to be problematic, so | ||||
the OID assignments contained in prevous versions of this document | ||||
have now been moved to a separate document [28]. That document also | ||||
contains information on future management of chipset OID assignments. | ||||
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 + | |||
ifOutBroadcastPkts | ifOutBroadcastPkts | |||
.aSingleCollisionFrames dot3StatsSingleCollisionFrames | .aSingleCollisionFrames dot3StatsSingleCollisionFrames | |||
skipping to change at page 12, line 15 | skipping to change at page 12, line 17 | |||
.aFramesLostDueToIntMACRcvError dot3StatsInternalMacReceiveErrors | .aFramesLostDueToIntMACRcvError dot3StatsInternalMacReceiveErrors | |||
.aPromiscuousStatus IF-MIB - ifPromiscuousMode | .aPromiscuousStatus IF-MIB - ifPromiscuousMode | |||
.aReadMulticastAddressList IF-MIB - ifRcvAddressTable | .aReadMulticastAddressList IF-MIB - ifRcvAddressTable | |||
.aMulticastFramesXmittedOK IF-MIB - ifOutMulticastPkts | .aMulticastFramesXmittedOK IF-MIB - ifOutMulticastPkts | |||
.aBroadcastFramesXmittedOK IF-MIB - ifOutBroadcastPkts | .aBroadcastFramesXmittedOK IF-MIB - ifOutBroadcastPkts | |||
.aMulticastFramesReceivedOK IF-MIB - ifInMulticastPkts | .aMulticastFramesReceivedOK IF-MIB - ifInMulticastPkts | |||
.aBroadcastFramesReceivedOK IF-MIB - ifInBroadcastPkts | .aBroadcastFramesReceivedOK IF-MIB - ifInBroadcastPkts | |||
.aFrameTooLongErrors dot3StatsFrameTooLongs | .aFrameTooLongErrors dot3StatsFrameTooLongs | |||
.aReadWriteMACAddress IF-MIB - ifPhysAddress | .aReadWriteMACAddress IF-MIB - ifPhysAddress | |||
.aCollisionFrames dot3CollFrequencies | .aCollisionFrames dot3CollFrequencies | |||
.aDuplexStatus dot3StatsDuplexStatus | ||||
.acAddGroupAddress IF-MIB - ifRcvAddressTable | .acAddGroupAddress IF-MIB - ifRcvAddressTable | |||
.acDeleteGroupAddress IF-MIB - ifRcvAddressTable | .acDeleteGroupAddress IF-MIB - ifRcvAddressTable | |||
.acExecuteSelfTest dot3TestLoopBack | .acExecuteSelfTest dot3TestLoopBack | |||
oPHYEntity | oPHYEntity | |||
.aPHYID dot3StatsIndex or | ||||
IF-MIB - ifIndex | ||||
.aSQETestErrors dot3StatsSQETestErrors | .aSQETestErrors dot3StatsSQETestErrors | |||
.aSymbolErrorDuringCarrier dot3StatsSymbolErrors | .aSymbolErrorDuringCarrier dot3StatsSymbolErrors | |||
oMACControlEntity | ||||
.aMACControlID dot3StatsIndex or | ||||
IF-MIB - ifIndex | ||||
.aMACControlFunctionsSupported dot3ControlFunctionsSupported and | ||||
dot3ControlFunctionsEnabled | ||||
.aUnsupportedOpcodesReceived dot3ControlInUnknownOpcodes | ||||
oPAUSEEntity | ||||
.aPAUSELinkDelayAllowance dot3PauseLinkDelayAllowance | ||||
.aPAUSEMACCtrlFramesTransmitted dot3OutPauseFrames | ||||
.aPAUSEMACCtrlFramesReceived dot3InPauseFrames | ||||
* Note that the octet counters in IF-MIB do not exactly match the | * Note that the octet counters in IF-MIB do not exactly match the | |||
definition of the octet counters in IEEE 802.3. aOctetsTransmittedOK | definition of the octet counters in IEEE 802.3. aOctetsTransmittedOK | |||
and aOctetsReceivedOK count only the octets in the clientData and Pad | and aOctetsReceivedOK count only the octets in the clientData and Pad | |||
fields, whereas ifInOctets and ifOutOctets include the entire MAC | fields, whereas ifInOctets and ifOutOctets include the entire MAC | |||
frame, including MAC header and FCS. However, the IF-MIB counters | frame, including MAC header and FCS. However, the IF-MIB counters | |||
can be derived from the IEEE 802.3 counters as follows: | can be derived from the IEEE 802.3 counters as follows: | |||
ifInOctets = aOctetsReceivedOK + (18 * aFramesReceivedOK) | ifInOctets = aOctetsReceivedOK + (18 * aFramesReceivedOK) | |||
ifOutOctets = aOctetsTransmittedOK + (18 * aFramesTransmittedOK) | ifOutOctets = aOctetsTransmittedOK + (18 * aFramesTransmittedOK) | |||
skipping to change at page 12, line 45 | skipping to change at page 13, line 15 | |||
oMacEntity | oMacEntity | |||
.aFramesWithExcessiveDeferral | .aFramesWithExcessiveDeferral | |||
.aInRangeLengthErrors | .aInRangeLengthErrors | |||
.aOutOfRangeLengthField | .aOutOfRangeLengthField | |||
.aMACEnableStatus | .aMACEnableStatus | |||
.aTransmitEnableStatus | .aTransmitEnableStatus | |||
.aMulticastReceiveStatus | .aMulticastReceiveStatus | |||
.acInitializeMAC | .acInitializeMAC | |||
Please see [22] for the detailed reasoning on why these objects were | Please see [19] for the detailed reasoning on why these objects were | |||
removed. | removed. | |||
In addition, the following IEEE 802.3 managed objects have not been | ||||
included in this MIB for the following reasons. | ||||
IEEE 802.3 Managed Object Disposition | ||||
oMACEntity | ||||
.aMACCapabilities Can be derived from | ||||
MAU-MIB - ifMauTypeListBits | ||||
oPHYEntity | ||||
.aPhyType Can be derived from | ||||
MAU-MIB - ifMauType | ||||
.aPhyTypeList Can be derived from | ||||
MAU-MIB - ifMauTypeListBits | ||||
.aMIIDetect Not considered useful. | ||||
.aPhyAdminState Can already obtain interface | ||||
state from IF-MIB - ifOperStatus | ||||
and MAU state from MAU-MIB - | ||||
ifMauStatus. Providing an | ||||
additional state for the PHY | ||||
was not considered useful. | ||||
.acPhyAdminControl Can already control interface | ||||
state from IF-MIB - ifAdminStatus | ||||
and MAU state from MAU-MIB - | ||||
ifMauStatus. Providing separate | ||||
admin control of the PHY was not | ||||
considered useful. | ||||
oMACControlEntity | ||||
.aMACControlFramesTransmitted Can be determined by summing the | ||||
OutFrames counters for the | ||||
individual control functions | ||||
.aMACControlFramesReceived Can be determined by summing the | ||||
InFrames counters for the | ||||
individual control functions | ||||
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, 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; | |||
skipping to change at page 13, line 16 | skipping to change at page 14, line 25 | |||
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 "9808042227Z" -- August 4, 1998 | LAST-UPDATED "9811172346Z" -- November 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 | |||
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: LANNET Ltd. | |||
Atidum Technology Park, Bldg. 3 | Atidum Technology Park, Bldg. 3 | |||
Tel Aviv 61131 | Tel Aviv 61131 | |||
Israel | Israel | |||
skipping to change at page 14, line 7 | skipping to change at page 15, line 16 | |||
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. | 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: | |||
ISO/IEC 8802-3: 1996(E), (ANSI/IEEE | IEEE Std 802.3, 1998 Edition: 'Information | |||
Std 802.3, 1996 Edition), 'Information | ||||
technology - Telecommunications and | technology - Telecommunications and | |||
information exchange between systems - Local | information exchange between systems - | |||
and metropolitan area networks - Specific | Local and metropolitan area networks - | |||
requirements - Part 3: Carrier sense | Specific requirements - Part 3: Carrier | |||
multiple access with collision detection | sense multiple access with collision | |||
(CSMA/CD) access method and physical layer | detection (CSMA/CD) access method and | |||
specifications', July 1996. | physical layer specifications', | |||
September 1998. | ||||
as ammended by the following supplements: | ||||
IEEE Std 802.3u-1995, 'Media Access Control | ||||
(MAC) Parameters, Physical Layer, Medium | ||||
Attachment Units, and Repeater for 100Mb/s | ||||
Operation, Type 100BASE-T', October 1995. | ||||
IEEE Std 802.3x-1997 and IEEE Std | ||||
802.3y-1997, 'Specification for 802.3 Full | ||||
Duplex Operation and Physical Layer | ||||
Specification for 100Mbit/s Operation on Two | ||||
Pairs of Category 3 or Better Balanced | ||||
Twisted Pair Cable (100BASE-T2)', November | ||||
1997. | ||||
IEEE Draft 802.3z/D4.2, 'Media Access | ||||
Control (MAC) Parameters, Physical Layer, | ||||
Repeater and Management Parameters for 1000 | ||||
Mb/s Operation', March 1998. | ||||
Of particular interest is Clause 30, '10Mb/s, | Of particular interest is Clause 30, '10Mb/s, | |||
100Mb/s and 1000Mb/s Management', which is | 100Mb/s and 1000Mb/s Management'." | |||
specified in IEEE Draft 802.3z/D4.2." | ||||
REVISION "9808042227Z" | REVISION "9811172346Z" -- November 17, 1998 | |||
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" | 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" | REVISION "9402030400Z" -- February 3, 1994 | |||
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 } | |||
-- the Ethernet-like Statistics group | -- the Ethernet-like Statistics group | |||
dot3StatsTable OBJECT-TYPE | dot3StatsTable OBJECT-TYPE | |||
SYNTAX SEQUENCE OF Dot3StatsEntry | SYNTAX SEQUENCE OF Dot3StatsEntry | |||
MAX-ACCESS not-accessible | MAX-ACCESS not-accessible | |||
STATUS current | STATUS current | |||
skipping to change at page 15, line 43 | skipping to change at page 16, line 32 | |||
dot3StatsMultipleCollisionFrames Counter32, | dot3StatsMultipleCollisionFrames Counter32, | |||
dot3StatsSQETestErrors Counter32, | dot3StatsSQETestErrors Counter32, | |||
dot3StatsDeferredTransmissions Counter32, | dot3StatsDeferredTransmissions Counter32, | |||
dot3StatsLateCollisions Counter32, | dot3StatsLateCollisions Counter32, | |||
dot3StatsExcessiveCollisions Counter32, | dot3StatsExcessiveCollisions Counter32, | |||
dot3StatsInternalMacTransmitErrors Counter32, | dot3StatsInternalMacTransmitErrors Counter32, | |||
dot3StatsCarrierSenseErrors Counter32, | dot3StatsCarrierSenseErrors Counter32, | |||
dot3StatsFrameTooLongs Counter32, | dot3StatsFrameTooLongs Counter32, | |||
dot3StatsInternalMacReceiveErrors Counter32, | dot3StatsInternalMacReceiveErrors Counter32, | |||
dot3StatsEtherChipSet OBJECT IDENTIFIER, | dot3StatsEtherChipSet OBJECT IDENTIFIER, | |||
dot3StatsSymbolErrors Counter32 | dot3StatsSymbolErrors Counter32, | |||
dot3StatsDuplexStatus INTEGER | ||||
} | } | |||
dot3StatsIndex OBJECT-TYPE | dot3StatsIndex OBJECT-TYPE | |||
SYNTAX InterfaceIndex | SYNTAX InterfaceIndex | |||
MAX-ACCESS read-only | MAX-ACCESS read-only | |||
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 | |||
skipping to change at page 18, line 18 | skipping to change at page 19, line 9 | |||
dot3StatsSQETestErrors OBJECT-TYPE | dot3StatsSQETestErrors OBJECT-TYPE | |||
SYNTAX Counter32 | SYNTAX Counter32 | |||
MAX-ACCESS read-only | MAX-ACCESS read-only | |||
STATUS current | STATUS current | |||
DESCRIPTION "A count of times that the SQE TEST ERROR | DESCRIPTION "A count of times that the SQE TEST ERROR | |||
message is generated by the PLS sublayer for a | message is generated by the PLS sublayer for a | |||
particular interface. The SQE TEST ERROR | particular interface. The SQE TEST ERROR | |||
is set in accordance with the rules for | is set in accordance with the rules for | |||
verification of the SQE detection mechanism in | verification of the SQE detection mechanism in | |||
the PLS Carrier Sense Function as described in | the PLS Carrier Sense Function as described in | |||
ANSI/IEEE 802.3-1996, section 7.2.4.6. | IEEE Std. 802.3, 1998 Edition, section 7.2.4.6. | |||
This counter does not increment on interfaces | This counter does not increment on interfaces | |||
operating at speeds greater than 10 Mb/s, or on | operating at speeds greater than 10 Mb/s, or on | |||
interfaces operating in full-duplex mode." | interfaces operating in full-duplex mode." | |||
REFERENCE "[IEEE 802.3 Std.], 7.2.4.6, also 30.3.2.1.4, | REFERENCE "[IEEE 802.3 Std.], 7.2.4.6, also 30.3.2.1.4, | |||
aSQETestErrors." | aSQETestErrors." | |||
::= { dot3StatsEntry 6 } | ::= { dot3StatsEntry 6 } | |||
dot3StatsDeferredTransmissions OBJECT-TYPE | dot3StatsDeferredTransmissions OBJECT-TYPE | |||
SYNTAX Counter32 | SYNTAX Counter32 | |||
skipping to change at page 22, line 40 | skipping to change at page 23, line 31 | |||
The count represented by an instance of this | The count represented by an instance of this | |||
object is incremented at most once per carrier | object is incremented at most once per carrier | |||
event, even if multiple symbol errors occur | event, even if multiple symbol errors occur | |||
during the carrier event. This count does | during the carrier event. This count does | |||
not increment if a collision is present." | not increment if a collision is present." | |||
REFERENCE "[IEEE 802.3 Std.], 30.3.2.1.5, | REFERENCE "[IEEE 802.3 Std.], 30.3.2.1.5, | |||
aSymbolErrorDuringCarrier." | aSymbolErrorDuringCarrier." | |||
::= { dot3StatsEntry 18 } | ::= { dot3StatsEntry 18 } | |||
dot3StatsDuplexStatus OBJECT-TYPE | ||||
SYNTAX INTEGER { | ||||
unknown(1), | ||||
halfDuplex(2), | ||||
fullDuplex(3) | ||||
} | ||||
MAX-ACCESS read-only | ||||
STATUS current | ||||
DESCRIPTION "The current mode of operation of the MAC | ||||
entity. 'unknown' indicates that the current | ||||
duplex mode could not be determined. | ||||
Management control of the duplex mode is | ||||
accomplished through the MAU MIB. When | ||||
an interface does not support autonegotiation, | ||||
or when autonegotiation is not enabled, the | ||||
duplex mode is controlled using | ||||
ifMauDefaultType. When autonegotiation is | ||||
supported and enabled, duplex mode is controlled | ||||
using ifMauAutoNegAdvertisedBits. In either | ||||
case, the currently operating duplex mode is | ||||
reflected both in this object and in ifMauType." | ||||
REFERENCE "[IEEE 802.3 Std.], 30.3.1.1.32, | ||||
aDuplexStatus." | ||||
::= { dot3StatsEntry 19 } | ||||
-- the Ethernet-like Collision Statistics group | -- the Ethernet-like Collision Statistics group | |||
-- Implementation of this group is optional; it is appropriate | -- Implementation of this group is optional; it is appropriate | |||
-- for all systems which have the necessary metering | -- for all systems which have the necessary metering | |||
dot3CollTable OBJECT-TYPE | dot3CollTable OBJECT-TYPE | |||
SYNTAX SEQUENCE OF Dot3CollEntry | SYNTAX SEQUENCE OF Dot3CollEntry | |||
MAX-ACCESS not-accessible | MAX-ACCESS not-accessible | |||
STATUS current | STATUS current | |||
DESCRIPTION "A collection of collision histograms for a | DESCRIPTION "A collection of collision histograms for a | |||
skipping to change at page 24, line 35 | skipping to change at page 26, line 4 | |||
dot3ControlEntry OBJECT-TYPE | dot3ControlEntry OBJECT-TYPE | |||
SYNTAX Dot3ControlEntry | SYNTAX Dot3ControlEntry | |||
MAX-ACCESS not-accessible | MAX-ACCESS not-accessible | |||
STATUS current | STATUS current | |||
DESCRIPTION "An entry in the table, containing information | DESCRIPTION "An entry in the table, containing information | |||
about the MAC Control sublayer on a single | about the MAC Control sublayer on a single | |||
ethernet-like interface." | ethernet-like interface." | |||
INDEX { dot3StatsIndex } | INDEX { dot3StatsIndex } | |||
::= { dot3ControlTable 1 } | ::= { dot3ControlTable 1 } | |||
Dot3ControlEntry ::= | Dot3ControlEntry ::= | |||
SEQUENCE { | SEQUENCE { | |||
dot3ControlFunctionsSupported BITS, | dot3ControlFunctionsSupported BITS, | |||
dot3ControlInUnknownOpcodes Counter32, | dot3ControlInUnknownOpcodes Counter32 | |||
dot3ControlPauseMode INTEGER, | ||||
dot3ControlPauseLinkDelayAllowance Unsigned32, | ||||
dot3ControlInPauseFrames Counter32, | ||||
dot3ControlOutPauseFrames Counter32 | ||||
} | } | |||
dot3ControlFunctionsSupported OBJECT-TYPE | dot3ControlFunctionsSupported OBJECT-TYPE | |||
SYNTAX BITS { | SYNTAX BITS { | |||
pause(0) | pause(0) | |||
} | } | |||
MAX-ACCESS read-write | MAX-ACCESS read-only | |||
STATUS current | STATUS current | |||
DESCRIPTION "A list of the possible MAC Control functions | DESCRIPTION "A list of the possible MAC Control functions | |||
implemented for this interface." | implemented for this interface." | |||
REFERENCE "[IEEE 802.3 Std.], 30.3.3.2, | REFERENCE "[IEEE 802.3 Std.], 30.3.3.2, | |||
aMACControlFunctionsSupported." | aMACControlFunctionsSupported." | |||
::= { dot3ControlEntry 1 } | ::= { dot3ControlEntry 1 } | |||
dot3ControlInUnknownOpcodes OBJECT-TYPE | dot3ControlInUnknownOpcodes OBJECT-TYPE | |||
SYNTAX Counter32 | SYNTAX Counter32 | |||
MAX-ACCESS read-only | MAX-ACCESS read-only | |||
STATUS current | STATUS current | |||
DESCRIPTION "A count of MAC Control frames received on this | DESCRIPTION "A count of MAC Control frames received on this | |||
interface that contain an opcode that is not | interface that contain an opcode that is not | |||
supported by this device." | supported by this device." | |||
REFERENCE "[IEEE 802.3 Std.], 30.3.3.5, | REFERENCE "[IEEE 802.3 Std.], 30.3.3.5, | |||
aUnsupportedOpcodesReceived" | aUnsupportedOpcodesReceived" | |||
::= { dot3ControlEntry 2 } | ::= { dot3ControlEntry 2 } | |||
dot3ControlPauseMode OBJECT-TYPE | dot3PauseTable OBJECT-TYPE | |||
SYNTAX SEQUENCE OF Dot3PauseEntry | ||||
MAX-ACCESS not-accessible | ||||
STATUS current | ||||
DESCRIPTION "A table of descriptive and status information | ||||
about the MAC Control PAUSE function on the | ||||
ethernet-like interfaces attached to a | ||||
particular system." | ||||
::= { dot3 10 } | ||||
dot3PauseEntry OBJECT-TYPE | ||||
SYNTAX Dot3PauseEntry | ||||
MAX-ACCESS not-accessible | ||||
STATUS current | ||||
DESCRIPTION "An entry in the table, containing information | ||||
about the MAC Control PAUSE function on a single | ||||
ethernet-like interface." | ||||
INDEX { dot3StatsIndex } | ||||
::= { dot3PauseTable 1 } | ||||
Dot3PauseEntry ::= | ||||
SEQUENCE { | ||||
dot3PauseAdminMode INTEGER, | ||||
dot3PauseOperMode INTEGER, | ||||
dot3PauseLinkDelayAllowance Unsigned32, | ||||
dot3InPauseFrames Counter32, | ||||
dot3OutPauseFrames Counter32 | ||||
} | ||||
dot3PauseAdminMode OBJECT-TYPE | ||||
SYNTAX INTEGER { | ||||
disabled(1), | ||||
enabledXmit(2), | ||||
enabledRcv(3), | ||||
enabledXmitAndRcv(4) | ||||
} | ||||
MAX-ACCESS read-write | ||||
STATUS current | ||||
DESCRIPTION "This object is used to configure the default | ||||
administrative PAUSE mode for this interface. | ||||
This object represents the | ||||
administratively-configured PAUSE mode for this | ||||
interface. If auto-negotiation is not enabled | ||||
or is not implemented for the active MAU | ||||
attached to this interface, the value of this | ||||
object determines the operational PAUSE mode | ||||
of the interface whenever it is operating in | ||||
full-duplex mode. In this case, a set to this | ||||
object will force the interface into the | ||||
specified mode. | ||||
If auto-negotiation is implemented and enabled | ||||
for the MAU attached to this interface, the | ||||
PAUSE mode for this interface is determined by | ||||
auto-negotiation, and the value of this object | ||||
denotes the mode to which the interface will | ||||
automatically revert if/when auto-negotiation is | ||||
later disabled. Note that when auto-negotiation | ||||
is running, administrative control of the PAUSE | ||||
mode may be accomplished using the | ||||
ifMauAutoNegCapAdvertisedBits object in the | ||||
MAU-MIB. | ||||
Note that the value of this object is ignored | ||||
when the interface is not operating in | ||||
full-duplex mode. | ||||
An attempt to set this object to | ||||
'enabledXmit(2)' or 'enabledRcv(3)' will fail | ||||
on interfaces that do not support operation | ||||
at greater than 100 Mb/s." | ||||
::= { dot3PauseEntry 1 } | ||||
dot3PauseOperMode OBJECT-TYPE | ||||
SYNTAX INTEGER { | SYNTAX INTEGER { | |||
disabled(1), | disabled(1), | |||
enabledXmit(2), | enabledXmit(2), | |||
enabledRcv(3), | enabledRcv(3), | |||
enabledXmitAndRcv(4) | enabledXmitAndRcv(4) | |||
} | } | |||
MAX-ACCESS read-only | MAX-ACCESS read-only | |||
STATUS current | STATUS current | |||
DESCRIPTION "This object reflects the PAUSE mode currently | DESCRIPTION "This object reflects the PAUSE mode currently | |||
in use on this interface. Interfaces operating | in use on this interface, as determined by | |||
at less than 1000 Mb/s will never return | either (1) the result of the auto-negotiation | |||
function or (2) if auto-negotiation is not | ||||
enabled or is not implemented for the active MAU | ||||
attached to this interface, by the value of | ||||
dot3PauseAdminMode. Interfaces operating at | ||||
100 Mb/s or less will never return | ||||
'enabledXmit(2)' or 'enabledRcv(3)'. Interfaces | 'enabledXmit(2)' or 'enabledRcv(3)'. Interfaces | |||
which have not yet completed auto-negotiation | operating in half-duplex mode will always return | |||
should return the value 'disabled(1)'." | 'disabled(1)'. Interfaces on which | |||
::= { dot3ControlEntry 3 } | auto-negotiation is enabled but not yet | |||
completed should return the value | ||||
'disabled(1)'." | ||||
::= { dot3PauseEntry 2 } | ||||
dot3ControlPauseLinkDelayAllowance OBJECT-TYPE | dot3PauseLinkDelayAllowance OBJECT-TYPE | |||
SYNTAX Unsigned32 (0..4294967295) | SYNTAX Unsigned32 (0..4294967295) | |||
MAX-ACCESS read-write | MAX-ACCESS read-write | |||
STATUS current | STATUS current | |||
DESCRIPTION "The allowance, in bit times, made by the PAUSE | DESCRIPTION "The allowance, in bit times, made by the PAUSE | |||
MAC Control entity for round-trip propagation | MAC Control entity for round-trip propagation | |||
delay of the full-duplex link." | delay of the full-duplex link." | |||
REFERENCE "[IEEE 802.3 Std.], 30.3.4.1, | REFERENCE "[IEEE 802.3 Std.], 30.3.4.1, | |||
aPAUSELinkDelayAllowance." | aPAUSELinkDelayAllowance." | |||
::= { dot3ControlEntry 4 } | ::= { dot3PauseEntry 3 } | |||
dot3ControlInPauseFrames OBJECT-TYPE | dot3InPauseFrames OBJECT-TYPE | |||
SYNTAX Counter32 | SYNTAX Counter32 | |||
MAX-ACCESS read-only | MAX-ACCESS read-only | |||
STATUS current | STATUS current | |||
DESCRIPTION "A count of MAC Control frames received on this | DESCRIPTION "A count of MAC Control frames received on this | |||
interface with an opcode indicating the PAUSE | interface with an opcode indicating the PAUSE | |||
operation. | operation. | |||
This counter does not increment when the | This counter does not increment when the | |||
interface is operating in half-duplex mode." | interface is operating in half-duplex mode." | |||
REFERENCE "[IEEE 802.3 Std.], 30.3.4.3, | REFERENCE "[IEEE 802.3 Std.], 30.3.4.3, | |||
aPAUSEMACCtrlFramesReceived." | aPAUSEMACCtrlFramesReceived." | |||
::= { dot3ControlEntry 5 } | ::= { dot3PauseEntry 4 } | |||
dot3ControlOutPauseFrames OBJECT-TYPE | dot3OutPauseFrames OBJECT-TYPE | |||
SYNTAX Counter32 | SYNTAX Counter32 | |||
MAX-ACCESS read-only | MAX-ACCESS read-only | |||
STATUS current | STATUS current | |||
DESCRIPTION "A count of MAC Control frames transmitted on | DESCRIPTION "A count of MAC Control frames transmitted on | |||
this interface with an opcode indicating the | this interface with an opcode indicating the | |||
PAUSE operation. | PAUSE operation. | |||
This counter does not increment when the | This counter does not increment when the | |||
interface is operating in half-duplex mode." | interface is operating in half-duplex mode." | |||
REFERENCE "[IEEE 802.3 Std.], 30.3.4.2, | REFERENCE "[IEEE 802.3 Std.], 30.3.4.2, | |||
aPAUSEMACCtrlFramesTransmitted." | aPAUSEMACCtrlFramesTransmitted." | |||
::= { dot3ControlEntry 6 } | ::= { dot3PauseEntry 5 } | |||
-- 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 | |||
skipping to change at page 27, line 48 | skipping to change at page 30, line 47 | |||
STATUS current | STATUS current | |||
DESCRIPTION "Couldn't initialize MAC chip for test." | DESCRIPTION "Couldn't initialize MAC chip for test." | |||
::= { dot3Errors 1 } | ::= { dot3Errors 1 } | |||
dot3ErrorLoopbackError OBJECT-IDENTITY | dot3ErrorLoopbackError OBJECT-IDENTITY | |||
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 | ||||
-- The object dot3StatsEtherChipSet is provided to | ||||
-- identify the MAC hardware used to communicate on an | ||||
-- interface. The following hardware chipsets are | ||||
-- registered: | ||||
dot3ChipSets OBJECT IDENTIFIER ::= { dot3 8 } | ||||
dot3ChipSetAMD OBJECT IDENTIFIER ::= { dot3ChipSets 1 } | ||||
dot3ChipSetAMD7990 OBJECT-IDENTITY | ||||
STATUS current | ||||
DESCRIPTION "The authoritative identifier for the Advanced | ||||
Micro Devices Am7990 Local Area Network | ||||
Controller for Ethernet (LANCE)." | ||||
::= { dot3ChipSetAMD 1 } | ||||
dot3ChipSetAMD79900 OBJECT-IDENTITY | ||||
STATUS current | ||||
DESCRIPTION "The authoritative identifier for the Advanced | ||||
Micro Devices Am79900 chip." | ||||
::= { dot3ChipSetAMD 2 } | ||||
dot3ChipSetAMD79C940 OBJECT-IDENTITY | ||||
STATUS current | ||||
DESCRIPTION "The authoritative identifier for the Advanced | ||||
Micro Devices Am79C940 Media Access Controller | ||||
for Ethernet (MACE)." | ||||
::= { 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 } | ||||
dot3ChipSetIntel82586 OBJECT-IDENTITY | ||||
STATUS current | ||||
DESCRIPTION "The authoritative identifier for the Intel | ||||
82586 IEEE 802.3 Ethernet LAN Coprocessor." | ||||
::= { dot3ChipSetIntel 1 } | ||||
dot3ChipSetIntel82596 OBJECT-IDENTITY | ||||
STATUS current | ||||
DESCRIPTION "The authoritative identifier for the Intel | ||||
82596 High-Performance 32-Bit Local Area Network | ||||
Coprocessor." | ||||
::= { 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 } | ||||
dot3ChipSetSeeq8003 OBJECT-IDENTITY | ||||
STATUS current | ||||
DESCRIPTION "The authoritative identifier for the SEEQ | ||||
8003 chip set." | ||||
::= { 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 } | ||||
dot3ChipSetNational8390 OBJECT-IDENTITY | ||||
STATUS current | ||||
DESCRIPTION "The authoritative identifier for the National | ||||
Semiconductor DP8390 Network Interface | ||||
Controller." | ||||
::= { dot3ChipSetNational 1 } | ||||
dot3ChipSetNationalSonic OBJECT-IDENTITY | ||||
STATUS current | ||||
DESCRIPTION "The authoritative identifier for the National | ||||
Semiconductor DP83932 Systems-Oriented Network | ||||
Interface Controller (SONIC)." | ||||
::= { 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 } | ||||
dot3ChipSetFujitsu86950 OBJECT-IDENTITY | ||||
STATUS current | ||||
DESCRIPTION "The authoritative identifier for the Fujitsu | ||||
86950 chip." | ||||
::= { 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 } | ||||
dot3ChipSetDigitalDC21040 OBJECT-IDENTITY | ||||
STATUS current | ||||
DESCRIPTION "The authoritative identifier for the Digital | ||||
Semiconductor DC21040 chip." | ||||
::= { 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 | ||||
-- assignment is required in other documentation, e.g., | ||||
-- assignment within that part of the registration tree | ||||
-- delegated to individual enterprises (see RFC 1155 and | ||||
-- RFC 1902). | ||||
-- | ||||
-- In the future, management of chipset registrations may be | ||||
-- delegated to the Internet Assigned Numbers Authority (IANA). | ||||
-- 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 | |||
etherCompliance MODULE-COMPLIANCE | etherCompliance MODULE-COMPLIANCE | |||
STATUS current | STATUS deprecated | |||
DESCRIPTION "The compliance statement for managed network | DESCRIPTION "******** THIS COMPLIANCE IS DEPRECATED ******** | |||
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 | ||||
dot3Compliance." | ||||
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 deprecated | |||
DESCRIPTION "The compliance statement for managed network | DESCRIPTION "******** THIS COMPLIANCE IS DEPRECATED ******** | |||
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. | |||
This compliance is deprecated and replaced by | ||||
dot3Compliance." | ||||
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 } | |||
dot3Compliance MODULE-COMPLIANCE | ||||
STATUS current | ||||
DESCRIPTION "The compliance statement for managed network | ||||
entities which have ethernet-like network | ||||
interfaces." | ||||
MODULE -- this module | ||||
MANDATORY-GROUPS { etherStatsBaseGroup } | ||||
GROUP etherDuplexGroup | ||||
DESCRIPTION "This group is mandatory for all | ||||
ethernet-like network interfaces which are | ||||
capable of operating in full-duplex mode. | ||||
It is highly recommended for all | ||||
ethernet-like network interfaces." | ||||
GROUP etherStatsLowSpeedGroup | ||||
DESCRIPTION "This group is mandatory for all | ||||
ethernet-like network interfaces which are | ||||
capable of operating at 10 Mb/s or slower in | ||||
half-duplex mode." | ||||
GROUP etherStatsHighSpeedGroup | ||||
DESCRIPTION "This group is mandatory for all | ||||
ethernet-like network interfaces which are | ||||
capable of operating at 100 Mb/s or faster." | ||||
GROUP etherControlGroup | ||||
DESCRIPTION "This group is mandatory for all | ||||
ethernet-like network interfaces that | ||||
support the MAC Control sublayer." | ||||
GROUP etherControlPauseGroup | ||||
DESCRIPTION "This group is mandatory for all | ||||
ethernet-like network interfaces that | ||||
support the MAC Control PAUSE function." | ||||
OBJECT dot3PauseLinkDelayAllowance | ||||
MIN-ACCESS read-only | ||||
DESCRIPTION "Write access is not required." | ||||
GROUP etherCollisionTableGroup | ||||
DESCRIPTION "This group is optional. It is appropriate | ||||
for all ethernet-like network interfaces | ||||
which are capable of operating in | ||||
half-duplex mode and have the necessary | ||||
metering. Implementation in systems with | ||||
such interfaces is highly recommended." | ||||
::= { etherCompliances 3 } | ||||
-- units of conformance | -- units of conformance | |||
etherStatsGroup OBJECT-GROUP | etherStatsGroup OBJECT-GROUP | |||
OBJECTS { dot3StatsIndex, | OBJECTS { dot3StatsIndex, | |||
dot3StatsAlignmentErrors, | dot3StatsAlignmentErrors, | |||
dot3StatsFCSErrors, | dot3StatsFCSErrors, | |||
dot3StatsSingleCollisionFrames, | dot3StatsSingleCollisionFrames, | |||
dot3StatsMultipleCollisionFrames, | dot3StatsMultipleCollisionFrames, | |||
dot3StatsSQETestErrors, | dot3StatsSQETestErrors, | |||
dot3StatsDeferredTransmissions, | dot3StatsDeferredTransmissions, | |||
dot3StatsLateCollisions, | dot3StatsLateCollisions, | |||
dot3StatsExcessiveCollisions, | dot3StatsExcessiveCollisions, | |||
dot3StatsInternalMacTransmitErrors, | dot3StatsInternalMacTransmitErrors, | |||
dot3StatsCarrierSenseErrors, | dot3StatsCarrierSenseErrors, | |||
dot3StatsFrameTooLongs, | dot3StatsFrameTooLongs, | |||
dot3StatsInternalMacReceiveErrors, | dot3StatsInternalMacReceiveErrors, | |||
dot3StatsEtherChipSet | dot3StatsEtherChipSet | |||
} | } | |||
STATUS current | STATUS deprecated | |||
DESCRIPTION "A collection of objects providing information | DESCRIPTION "********* THIS GROUP IS DEPRECATED ********** | |||
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 etherStatsBaseGroup and | ||||
etherStatsLowSpeedGroup." | ||||
::= { etherGroups 1 } | ::= { etherGroups 1 } | |||
etherCollisionTableGroup OBJECT-GROUP | etherCollisionTableGroup OBJECT-GROUP | |||
OBJECTS { dot3CollFrequencies | OBJECTS { dot3CollFrequencies | |||
} | } | |||
STATUS current | STATUS current | |||
DESCRIPTION "A collection of objects providing a histogram | DESCRIPTION "A collection of objects providing a histogram | |||
of packets successfully transmitted after | of packets successfully transmitted after | |||
experiencing exactly N collisions." | experiencing exactly N collisions." | |||
::= { etherGroups 2 } | ::= { etherGroups 2 } | |||
skipping to change at page 39, line 47 | skipping to change at page 34, line 13 | |||
dot3StatsDeferredTransmissions, | dot3StatsDeferredTransmissions, | |||
dot3StatsLateCollisions, | dot3StatsLateCollisions, | |||
dot3StatsExcessiveCollisions, | dot3StatsExcessiveCollisions, | |||
dot3StatsInternalMacTransmitErrors, | dot3StatsInternalMacTransmitErrors, | |||
dot3StatsCarrierSenseErrors, | dot3StatsCarrierSenseErrors, | |||
dot3StatsFrameTooLongs, | dot3StatsFrameTooLongs, | |||
dot3StatsInternalMacReceiveErrors, | dot3StatsInternalMacReceiveErrors, | |||
dot3StatsEtherChipSet, | dot3StatsEtherChipSet, | |||
dot3StatsSymbolErrors | dot3StatsSymbolErrors | |||
} | } | |||
STATUS deprecated | ||||
DESCRIPTION "********* THIS GROUP IS DEPRECATED ********** | ||||
A collection of objects providing information | ||||
applicable to 100 Mb/sec ethernet-like network | ||||
interfaces. | ||||
This object group has been deprecated and | ||||
replaced by etherStatsBaseGroup and | ||||
etherStatsHighSpeedGroup." | ||||
::= { etherGroups 3 } | ||||
etherStatsBaseGroup OBJECT-GROUP | ||||
OBJECTS { dot3StatsIndex, | ||||
dot3StatsAlignmentErrors, | ||||
dot3StatsFCSErrors, | ||||
dot3StatsSingleCollisionFrames, | ||||
dot3StatsMultipleCollisionFrames, | ||||
dot3StatsDeferredTransmissions, | ||||
dot3StatsLateCollisions, | ||||
dot3StatsExcessiveCollisions, | ||||
dot3StatsInternalMacTransmitErrors, | ||||
dot3StatsCarrierSenseErrors, | ||||
dot3StatsFrameTooLongs, | ||||
dot3StatsInternalMacReceiveErrors, | ||||
dot3StatsEtherChipSet | ||||
} | ||||
STATUS current | STATUS current | |||
DESCRIPTION "A collection of objects providing information | DESCRIPTION "A collection of objects providing information | |||
applicable to 100 Mb/sec ethernet-like network | applicable to all ethernet-like network | |||
interfaces." | interfaces." | |||
::= { etherGroups 3 } | ::= { 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 | etherControlGroup OBJECT-GROUP | |||
OBJECTS { dot3ControlFunctionsSupported, | OBJECTS { dot3ControlFunctionsSupported, | |||
dot3ControlInUnknownOpcodes | dot3ControlInUnknownOpcodes | |||
} | } | |||
STATUS current | STATUS current | |||
DESCRIPTION "A collection of objects providing information | DESCRIPTION "A collection of objects providing information | |||
about the MAC Control sublayer on ethernet-like | about the MAC Control sublayer on ethernet-like | |||
network interfaces." | network interfaces." | |||
::= { etherGroups 4 } | ::= { etherGroups 8 } | |||
etherControlPauseGroup OBJECT-GROUP | etherControlPauseGroup OBJECT-GROUP | |||
OBJECTS { dot3ControlPauseMode, | OBJECTS { dot3PauseAdminMode, | |||
dot3ControlPauseLinkDelayAllowance, | dot3PauseOperMode, | |||
dot3ControlInPauseFrames, | dot3PauseLinkDelayAllowance, | |||
dot3ControlOutPauseFrames | dot3InPauseFrames, | |||
dot3OutPauseFrames | ||||
} | } | |||
STATUS current | STATUS current | |||
DESCRIPTION "A collection of objects providing information | DESCRIPTION "A collection of objects providing information | |||
about the MAC Control PAUSE function on | about and control of the MAC Control PAUSE | |||
ethernet-like network interfaces." | function on ethernet-like network interfaces." | |||
::= { etherGroups 5 } | ::= { etherGroups 9 } | |||
END | END | |||
5. Intellectual Property | 5. Intellectual Property | |||
The IETF takes no position regarding the validity or scope of any | The IETF takes no position regarding the validity or scope of any | |||
intellectual property or other rights that might be claimed to | intellectual property or other rights that might be claimed to | |||
pertain to the implementation or use of the technology described in | pertain to the implementation or use of the technology described in | |||
this document or the extent to which any license under such rights | this document or the extent to which any license under such rights | |||
might or might not be available; neither does it represent that it | might or might not be available; neither does it represent that it | |||
skipping to change at page 41, line 9 | skipping to change at page 36, line 25 | |||
be obtained from the IETF Secretariat. | be obtained from the IETF Secretariat. | |||
The IETF invites any interested party to bring to its attention any | The IETF invites any interested party to bring to its attention any | |||
copyrights, patents or patent applications, or other proprietary | copyrights, patents or patent applications, or other proprietary | |||
rights which may cover technology that may be required to practice | rights which may cover technology that may be required to practice | |||
this standard. Please address the information to the IETF Executive | this standard. Please address the information to the IETF Executive | |||
Director. | Director. | |||
6. Acknowledgements | 6. Acknowledgements | |||
This document was produced by the 802.3 Hub MIB Working Group. | This document was produced by the Ethernet Interfaces and Hub MIB | |||
Working Group. | ||||
This document is based on the Proposed Standard Ethernet MIB, RFC | This document is based on the Proposed Standard Ethernet MIB, RFC | |||
2358 [26], edited by John Flick of Hewlett-Packard and Jeffrey | 2358 [23], 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 802.3 Hub MIB Working | |||
and Hub MIB Working Group. It extends that document by providing | Group. It extends that document by providing support for full-duplex | |||
support for full-duplex Ethernet interfaces as outlined in [18] and | Ethernet interfaces and 1000 Mb/sec Ethernet interfaces as outlined | |||
1000 Mb/sec Ethernet interfaces as outlined in [19]. | in [16]. | |||
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 [24], and the Proposed Standard Ethernet MIB | Ethernet MIB, RFC 1643 [21], and the Proposed Standard Ethernet MIB | |||
using the SNMPv2 SMI, RFC 1650 [25], both of which were edited by | using the SNMPv2 SMI, RFC 1650 [22], both of which were edited by | |||
Frank Kastenholz of FTP Software and produced by the Ethernet MIB | Frank Kastenholz of FTP Software and produced by the Interfaces MIB | |||
Working Group. RFC 2358 extends those documents by providing support | Working Group. RFC 2358 extends those documents by providing support | |||
for 100 Mb/sec ethernet interfaces as outlined in [17]. | for 100 Mb/sec ethernet interfaces. | |||
RFC 1643 and RFC 1650, in turn, are based on the Draft Standard | RFC 1643 and RFC 1650, in turn, are based on the Draft Standard | |||
Ethernet MIB, RFC 1398 [23], also edited by Frank Kastenholz and | Ethernet MIB, RFC 1398 [20], also edited by Frank Kastenholz and | |||
produced by the Ethernet MIB Working Group. | produced by the Ethernet MIB Working Group. | |||
RFC 1398, in turn, is based on the Proposed Standard Ethernet MIB, | RFC 1398, in turn, is based on the Proposed Standard Ethernet MIB, | |||
RFC 1284 [21], which was edited by John Cook of Chipcom and produced | RFC 1284 [18], which was edited by John Cook of Chipcom and produced | |||
by the Transmission MIB Working Group. The Ethernet MIB Working | by the Transmission MIB Working Group. The Ethernet MIB Working | |||
Group gathered implementation experience of the variables specified | Group gathered implementation experience of the variables specified | |||
in RFC 1284, documented that experience in RFC 1369 [22], and used | in RFC 1284, documented that experience in RFC 1369 [19], and used | |||
that information to develop this revised MIB. | that information to develop this revised MIB. | |||
RFC 1284, in turn, is based on a document written by Frank | RFC 1284, in turn, is based on a document written by Frank | |||
Kastenholz, then of Interlan, entitled IEEE 802.3 Layer Management | Kastenholz, then of Interlan, entitled IEEE 802.3 Layer Management | |||
Draft M compatible MIB for TCP/IP Networks [20]. This document was | Draft M compatible MIB for TCP/IP Networks [17]. This document was | |||
modestly reworked, initially by the SNMP Working Group, and then by | modestly reworked, initially by the SNMP Working Group, and then by | |||
the Transmission Working Group, to reflect the current conventions | 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 [3] concise format. Anil Rijsinghani of DEC contributed text | RFC 1212 [3] concise format. Anil Rijsinghani of DEC contributed | |||
that more adequately describes the TDR test. Thanks to Frank | text that more adequately describes the TDR test. Thanks to Frank | |||
Kastenholz of Interlan and Louis Steinberg of IBM for their | Kastenholz of Interlan and Louis Steinberg of IBM for their | |||
experimentation. | experimentation. | |||
7. References | 7. References | |||
[1] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for | [1] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for | |||
Describing SNMP Management Frameworks", RFC 2271, Cabletron | Describing SNMP Management Frameworks", RFC 2271, Cabletron | |||
Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, | Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, | |||
January 1998 | January 1998 | |||
skipping to change at page 43, line 34 | skipping to change at page 38, line 52 | |||
[14] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC | [14] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC | |||
2273, SNMP Research, Inc., Secure Computing Corporation, Cisco | 2273, SNMP Research, Inc., Secure Computing Corporation, Cisco | |||
Systems, January 1998 | Systems, January 1998 | |||
[15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access | [15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access | |||
Control Model (VACM) for the Simple Network Management Protocol | Control Model (VACM) for the Simple Network Management Protocol | |||
(SNMP)", RFC 2275, IBM T. J. Watson Research, BMC Software, | (SNMP)", RFC 2275, IBM T. J. Watson Research, BMC Software, | |||
Inc., Cisco Systems, Inc., January 1998 | Inc., Cisco Systems, Inc., January 1998 | |||
[16] International Standard ISO/IEC 8802-3: 1996(E), (ANSI/IEEE Std | [16] IEEE, IEEE Std 802.3, 1998 Edition: "Information technology - | |||
802.3, 1996 Edition), "Information technology - | ||||
Telecommunications and information exchange between systems - | Telecommunications and information exchange between systems - | |||
Local and metropolitan area networks - Specific requirements - | Local and metropolitan area networks - Specific requirements - | |||
Part 3: Carrier sense multiple access with collision detection | Part 3: Carrier sense multiple access with collision detection | |||
(CSMA/CD) access method and physical layer specifications", July | (CSMA/CD) access method and physical layer specifications" | |||
1996. | (incorporating ANSI/IEEE Std. 802.3, 1996 Edition, IEEE Std. | |||
802.3r-1996, 802.3u-1995, 802.3x&y-1997, 802.3z-1998, and | ||||
[17] IEEE, IEEE Std 802.3u-1995, "Media Access Control (MAC) | 802.3aa-1998), September 1998. | |||
Parameters, Physical Layer, Medium Attachment Units, and | ||||
Repeater for 100Mb/s Operation, Type 100BASE-T", Supplement to | ||||
ISO/IEC 8802-3: 1993 (ANSI/IEEE Std 802.3, 1993 Edition), | ||||
October 1995. | ||||
[18] IEEE, IEEE Std 802.3x-1997 and IEEE Std 802.3y-1997, | ||||
"Specification for 802.3 Full Duplex Operation and Physical | ||||
Layer Specification for 100Mbit/s Operation on Two Pairs of | ||||
Category 3 or Better Balanced Twisted Pair Cable (100BASE-T2)", | ||||
Supplement to ISO/IEC 8802-3: 1996 (ANSI/IEEE Std 802.3, 1996 | ||||
Edition), November 1997. | ||||
[19] IEEE, IEEE Draft 802.3z/D4.2, "Media Access Control (MAC) | ||||
Parameters, Physical Layer, Repeater and Management Parameters | ||||
for 1000 Mb/s Operation", Supplement to ISO/IEC 8802-3: 1996 | ||||
(ANSI/IEEE Std 802.3, 1996 Edition), March 1998. | ||||
[20] Kastenholz, F., "IEEE 802.3 Layer Management Draft compatible | [17] Kastenholz, F., "IEEE 802.3 Layer Management Draft compatible | |||
MIB for TCP/IP Networks", electronic mail message to mib- | MIB for TCP/IP Networks", electronic mail message to mib- | |||
wg@nnsc.nsf.net, 9 June 1989. | wg@nnsc.nsf.net, 9 June 1989. | |||
[21] Cook, J., "Definitions of Managed Objects for Ethernet-Like | [18] Cook, J., "Definitions of Managed Objects for Ethernet-Like | |||
Interface Types", RFC 1284, Chipcom Corporation, December 1991. | Interface Types", RFC 1284, Chipcom Corporation, December 1991. | |||
[22] Kastenholz, F., "Implementation Notes and Experience for The | [19] 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. | |||
[23] Kastenholz, F., "Definitions of Managed Objects for the | [20] Kastenholz, F., "Definitions of Managed Objects for the | |||
Ethernet-like Interface Types", RFC 1398, FTP Software, Inc., | Ethernet-like Interface Types", RFC 1398, FTP Software, Inc., | |||
January 1993. | January 1993. | |||
[24] Kastenholz, F., "Definitions of Managed Objects for the | [21] Kastenholz, F., "Definitions of Managed Objects for the | |||
Ethernet-like Interface Types", STD 50, RFC 1643, FTP Software, | Ethernet-like Interface Types", STD 50, RFC 1643, FTP Software, | |||
Inc., July 1994. | Inc., July 1994. | |||
[25] Kastenholz, F., "Definitions of Managed Objects for the | [22] 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. | |||
[26] Flick, J., and J. Johnson, "Definitions of Managed Objects | [23] Flick, J., and J. Johnson, "Definitions of Managed Objects | |||
for the Ethernet-like Interface Types", RFC 2358, | for the Ethernet-like Interface Types", RFC 2358, | |||
Hewlett-Packard Company, RedBack Networks, June 1998. | Hewlett-Packard Company, RedBack Networks, June 1998. | |||
[27] McCloghrie, K., and M. Rose, Editors, "Management Information | [24] McCloghrie, K., and M. Rose, Editors, "Management Information | |||
Base for Network Management of TCP/IP-based internets: MIB-II", | Base for Network Management of TCP/IP-based internets: MIB-II", | |||
STD 17, RFC 1213, March 1991. | STD 17, RFC 1213, Hughes LAN Systems, Performance Systems | |||
International, March 1991. | ||||
[28] 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. | |||
[29] 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. | |||
[30] deGraaf, K., Romascanu, D., McMaster, D., McCloghrie, K., and | [27] Smith, A., Flick, J., deGraaf, K., Romascanu, D., McMaster, | |||
S. Roberts, "Definitions of Managed Objects for IEEE 802.3 | D., McCloghrie, K., and S. Roberts, "Definitions of Managed | |||
Medium Attachment Units (MAUs) using SMIv2", RFC 2239, | Objects for IEEE 802.3 Medium Attachment Units (MAUs) using | |||
3Com Corporation, Madge Networks (Israel) Ltd., Cisco Systems | SMIv2", work in progress, draft-ietf-hubmib-mau-mib-v2-01.txt, | |||
Inc., Cisco Systems Inc., Farallon Computing Inc., November | Extreme Networks, Inc., Hewlett-Packard Company, Argon Networks, | |||
1997. | LANNET Ltd., Cisco Systems, Inc., Cisco Systems Inc., Farallon | |||
Computing Inc., November 1998. | ||||
[28] "Ethernet Interface Chipset Registrations", work in progress. | ||||
8. Security Considerations | 8. Security Considerations | |||
There are no management objects defined in this MIB that have a MAX- | There are two management objects defined in this MIB that have a | |||
ACCESS clause of read-write and/or read-create. So, if this MIB is | MAX-ACCESS clause of read-write. Such objects may be considered | |||
implemented correctly, then there is no risk that an intruder can | sensitive or vulnerable in some network environments. The support | |||
alter or create any management objects of this MIB via direct SNMP | for SET operations in a non-secure environment without proper | |||
SET 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. | |||
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 object when sending them over the network via SNMP. Not all | |||
skipping to change at page 46, line 47 | skipping to change at page 42, line 6 | |||
dot3StatsDeferredTransmissions, dot3StatsLateCollisions, | dot3StatsDeferredTransmissions, dot3StatsLateCollisions, | |||
dot3StatsExcessiveCollisions, dot3StatsCarrierSenseErrors, | dot3StatsExcessiveCollisions, dot3StatsCarrierSenseErrors, | |||
dot3CollFrequencies. | dot3CollFrequencies. | |||
(6) The following object DESCRIPTION clauses have been | (6) The following object DESCRIPTION clauses have been | |||
updated to reflect behaviour on full-duplex and | updated to reflect behaviour on full-duplex and | |||
1000 Mb/s interfaces: dot3StatsAlignmentErrors, | 1000 Mb/s interfaces: dot3StatsAlignmentErrors, | |||
dot3StatsFCSErrors, dot3StatsSQETestErrors, | dot3StatsFCSErrors, dot3StatsSQETestErrors, | |||
dot3StatsLateCollisions, dot3StatsSymbolErrors. | dot3StatsLateCollisions, dot3StatsSymbolErrors. | |||
(7) A new table, dot3ControlTable, has been added. | (7) Two new tables, dot3ControlTable and dot3PauseTable, | |||
have been added. | ||||
(8) Two new conformance groups, etherControlGroup and | (8) A new object, dot3StatsDuplexStatus, has been added. | |||
etherControlPauseGroup, have been added. | ||||
(9) The object groups and compliances have been restructured. | ||||
(10) 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/ |