< draft-ietf-snmp-ethernetmib-04.txt   draft-ietf-snmp-ethernetmib-05.txt >
Internet Draft ETHERNET-LIKE OBJECTS March 1991 Internet Draft ETHERNET-LIKE OBJECTS April 1991
Definitions of Managed Objects Definitions of Managed Objects
for the Ethernet-like Interface Types for the Ethernet-like Interface Types
18 March 20:45:00 1991 7 April 1991
Transmission MIB Working Group Transmission MIB Working Group
J. Cook (editor) J. Cook (editor)
Chipcom Corporation Chipcom Corporation
118 Turnpike Road 118 Turnpike Road
Southborough, MA 01772 Southborough, MA 01772
cook@chipcom.com cook@chipcom.com
skipping to change at page 5, line 17 skipping to change at page 5, line 17
Instances of these object types represent attributes of an Instances of these object types represent attributes of an
interface to an ethernet-like communications medium. At interface to an ethernet-like communications medium. At
present, ethernet-like media are identified by three values of present, ethernet-like media are identified by three values of
the ifType object in the Internet-standard MIB: the ifType object in the Internet-standard MIB:
ethernet-csmacd(6) ethernet-csmacd(6)
iso88023-csmacd(7) iso88023-csmacd(7)
starLan(11) starLan(11)
For these interfaces, the value of the ifSpecific variable in For these interfaces, the value of the ifSpecific variable in
the MIB-II [3] has the OBJECT IDENTIFIER value: the MIB-II [6] has the OBJECT IDENTIFIER value:
dot3 OBJECT IDENTIFER ::= { experimental 3 } dot3 OBJECT IDENTIFER ::= { experimental 3 }
The definitions presented here are based on the IEEE 802.3 The definitions presented here are based on the IEEE 802.3
Layer Management Specification [9], as originally interpreted Layer Management Specification [9], as originally interpreted
by Frank Kastenholz of Interlan in [10]. Implementors of by Frank Kastenholz of Interlan in [10]. Implementors of
these MIB objects should note that the IEEE document these MIB objects should note that the IEEE document
explicitly describes (in the form of Pascal pseudocode) when, explicitly describes (in the form of Pascal pseudocode) when,
where, and how various MAC attributes are measured. The IEEE where, and how various MAC attributes are measured. The IEEE
document also describes the effects of MAC actions that may be document also describes the effects of MAC actions that may be
skipping to change at page 6, line 10 skipping to change at page 6, line 10
interface in the context of the Internet-standard MIB is one- interface in the context of the Internet-standard MIB is one-
to-one. As such, the value of an ifIndex object instance can to-one. As such, the value of an ifIndex object instance can
be directly used to identify corresponding instances of the be directly used to identify corresponding instances of the
objects defined herein. objects defined herein.
6. Definitions 6. Definitions
RFCxxxx-MIB DEFINITIONS ::= BEGIN RFCxxxx-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
experimental, Counter experimental, Counter, Gauge
FROM RFC1155-SMI FROM RFC1155-SMI
OBJECT-TYPE OBJECT-TYPE
FROM RFC-oooo; FROM RFC-oooo;
-- This MIB module uses the extended OBJECT-TYPE macro as -- This MIB module uses the extended OBJECT-TYPE macro as
-- defined in [13] -- defined in [13]
-- this is the MIB module for ethernet-like objects -- this is the MIB module for ethernet-like objects
dot3 OBJECT IDENTIFIER ::= { experimental 3 } dot3 OBJECT IDENTIFIER ::= { experimental 3 }
skipping to change at page 22, line 20 skipping to change at page 22, line 20
-- At this time, one well known test (testFullDuplexLoopBack) is -- At this time, one well known test (testFullDuplexLoopBack) is
-- defined in [11]. For ethernet-like interfaces, this test -- defined in [11]. For ethernet-like interfaces, this test
-- configures the MAC chip and executes an internal loopback -- configures the MAC chip and executes an internal loopback
-- test of memory and the MAC chip logic. This loopback test can -- test of memory and the MAC chip logic. This loopback test can
-- only be executed if the interface is offline. Once the test -- only be executed if the interface is offline. Once the test
-- has completed, the MAC chip should be reinitialized for network -- has completed, the MAC chip should be reinitialized for network
-- operation, but it should remain offline. -- operation, but it should remain offline.
-- If an error occurs during a test, the object ifExtnsTestResult -- If an error occurs during a test, the object ifExtnsTestResult
-- (defined in [11]) will be set to failed (7). The following two -- (defined in [11]) will be set to failed(7). The following two
-- OBJECT IDENTIFIERs may be used to provided more information as -- OBJECT IDENTIFIERs may be used to provided more information as
-- values for the object ifExtnsTestCode in [11]: -- values for the object ifExtnsTestCode in [11]:
dot3Errors OBJECT IDENTIFIER ::= { dot3 7 } dot3Errors OBJECT IDENTIFIER ::= { dot3 7 }
-- couldn't initialize MAC chip for test -- couldn't initialize MAC chip for test
dot3ErrorInitError OBJECT IDENTIFIER ::= { dot3Errors 1 } dot3ErrorInitError OBJECT IDENTIFIER ::= { dot3Errors 1 }
-- expected data not received (or not -- expected data not received (or not
-- received correctly) in loopback test -- received correctly) in loopback test
skipping to change at page 24, line 29 skipping to change at page 24, line 29
dot3ChipSetSeeq OBJECT IDENTIFIER ::= { dot3ChipSets 3 } dot3ChipSetSeeq OBJECT IDENTIFIER ::= { dot3ChipSets 3 }
dot3ChipSetSeeq8003 OBJECT IDENTIFIER ::= { dot3ChipSetSeeq 1 } dot3ChipSetSeeq8003 OBJECT IDENTIFIER ::= { dot3ChipSetSeeq 1 }
dot3ChipSetNational OBJECT IDENTIFIER ::= { dot3ChipSets 4 } dot3ChipSetNational OBJECT IDENTIFIER ::= { dot3ChipSets 4 }
dot3ChipSetNational8390 OBJECT IDENTIFIER ::= dot3ChipSetNational8390 OBJECT IDENTIFIER ::=
{ dot3ChipSetNational 1 } { dot3ChipSetNational 1 }
dot3ChipSetNationalSonic OBJECT IDENTIFIER ::= dot3ChipSetNationalSonic OBJECT IDENTIFIER ::=
{ dot3ChipSetNational 2 } { dot3ChipSetNational 2 }
dot3ChipSetFujitsu OBJECT IDENTIFIER ::= { dot3ChipSets 5 }
dot3ChipSetFujitsu86950 OBJECT IDENTIFIER ::=
{ dot3ChipSetFujitsu 1 }
-- For those chipsets not represented above, OBJECT IDENTIFIER -- For those chipsets not represented above, OBJECT IDENTIFIER
-- assignment is required in other documentation, e.g., assignment -- assignment is required in other documentation, e.g., assignment
-- within that part of the registration tree delegated to -- within that part of the registration tree delegated to
-- individual enterprises (see [4]). -- individual enterprises (see [3]).
END END
7. Acknowledgements 7. Acknowledgements
This document was produced by the Transmission MIB Working This document was produced by the Transmission MIB Working
Group. Group.
This document is based on a document written by Frank This document is based on a document written by Frank
Kastenholz of Interlan entitled IEEE 802.3 Layer Management Kastenholz of Interlan entitled IEEE 802.3 Layer Management
Draft M compatible MIB for TCP/IP Networks [10]. This Draft M compatible MIB for TCP/IP Networks [10]. This
skipping to change at page 26, line 18 skipping to change at page 26, line 18
Internet Network Management Standards. Internet Working Internet Network Management Standards. Internet Working
Group Request for Comments 1052. Network Information Group Request for Comments 1052. Network Information
Center, SRI International, Menlo Park, California, Center, SRI International, Menlo Park, California,
(April, 1988). (April, 1988).
[2] V. Cerf, Report of the Second Ad Hoc Network Management [2] V. Cerf, Report of the Second Ad Hoc Network Management
Review Group, Internet Working Group Request for Comments Review Group, Internet Working Group Request for Comments
1109. Network Information Center, SRI International, 1109. Network Information Center, SRI International,
Menlo Park, California, (August, 1989). Menlo Park, California, (August, 1989).
[3] M.T. Rose (editor), Management Information Base for [3] M.T. Rose and K. McCloghrie, Structure and Identification
Network Management of TCP/IP-based internets, Internet
Working Group Request for Comments 1158. Network
Information Center, SRI International, Menlo Park,
California, (May, 1990).
[4] M.T. Rose and K. McCloghrie, Structure and Identification
of Management Information for TCP/IP-based internets, of Management Information for TCP/IP-based internets,
Internet Working Group Request for Comments 1155. Internet Working Group Request for Comments 1155.
Network Information Center, SRI International, Menlo Network Information Center, SRI International, Menlo
Park, California, (May, 1990). Park, California, (May, 1990).
[5] K. McCloghrie and M.T. Rose, Management Information Base [4] K. McCloghrie and M.T. Rose, Management Information Base
for Network Management of TCP/IP-based internets, for Network Management of TCP/IP-based internets,
Internet Working Group Request for Comments 1156. Internet Working Group Request for Comments 1156.
Network Information Center, SRI International, Menlo Network Information Center, SRI International, Menlo
Park, California, (May, 1990). Park, California, (May, 1990).
[6] J.D. Case, M.S. Fedor, M.L. Schoffstall, and J.R. Davin, [5] J.D. Case, M.S. Fedor, M.L. Schoffstall, and J.R. Davin,
Simple Network Management Protocol, Internet Working Simple Network Management Protocol, Internet Working
Group Request for Comments 1157. Network Information Group Request for Comments 1157. Network Information
Center, SRI International, Menlo Park, California, (May, Center, SRI International, Menlo Park, California, (May,
1990). 1990).
[6] K. McCloghrie and M.T. Rose (editors), Management
Information Base for Network Management of TCP/IP-based
internets: MIB-II, Internet Working Group Request for
Comments 1213. Network Information Center, SRI
International, Menlo Park, California, (March, 1991).
[7] Information processing systems - Open Systems [7] Information processing systems - Open Systems
Interconnection - Specification of Abstract Syntax Interconnection - Specification of Abstract Syntax
Notation One (ASN.1), International Organization for Notation One (ASN.1), International Organization for
Standardization. International Standard 8824, (December, Standardization. International Standard 8824, (December,
1987). 1987).
[8] Information processing systems - Open Systems [8] Information processing systems - Open Systems
Interconnection - Specification of Basic Encoding Rules Interconnection - Specification of Basic Encoding Rules
for Abstract Notation One (ASN.1), International for Abstract Notation One (ASN.1), International
Organization for Standardization. International Standard Organization for Standardization. International Standard
8825, (December, 1987). 8825, (December, 1987).
[9] IEEE, IEEE 802.3 Layer Management, (November, 1988). [9] IEEE, IEEE 802.3 Layer Management, (November, 1988).
[10] F. Kastenholz, IEEE 802.3 Layer Management Draft M [10] F. Kastenholz, IEEE 802.3 Layer Management Draft M
compatible MIB for TCP/IP Networks, electronic mail compatible MIB for TCP/IP Networks, electronic mail
message to mib-wg@nnsc.nsf.net, (June 9, 1989). message to mib-wg@nnsc.nsf.net, (June 9, 1989).
[11] K. McCloghrie, Extensions to the Generic-Interface MIB, [11] K. McCloghrie, Extensions to the Generic-Interface MIB,
RFC draft. SNMP Working Group (in preparation). RFC draft, SNMP Working Group (in preparation).
[12] IEEE. Carrier Sense Multiple Access with Collision [12] IEEE. Carrier Sense Multiple Access with Collision
Detection (CSMA/CD) Access Method and Physical Layer Detection (CSMA/CD) Access Method and Physical Layer
Specifications. ANSI/IEEE Std 802.3-1985. Specifications. ANSI/IEEE Std 802.3-1985.
[13] M.T. Rose, K. McCloghrie (editors), Towards Concise MIB [13] M.T. Rose, K. McCloghrie (editors), Concise MIB
Definitions, Internet Working Group Request for Comments Definitions, Internet Working Group Request for Comments
(in preparation), Network Information Center, SRI 1212, Network Information Center, SRI International,
International, Menlo Park, California, (December, 1990). Menlo Park, California, (March, 1991).
Table of Contents Table of Contents
1 Status of this Memo ................................... 1 1 Status of this Memo ................................... 1
2 Abstract .............................................. 1 2 Abstract .............................................. 1
3 Historical Perspective ................................ 2 3 Historical Perspective ................................ 2
4 Objects ............................................... 4 4 Objects ............................................... 4
4.1 Format of Definitions ............................... 4 4.1 Format of Definitions ............................... 4
5 Overview .............................................. 5 5 Overview .............................................. 5
6 Definitions ........................................... 6 6 Definitions ........................................... 6
 End of changes. 14 change blocks. 
19 lines changed or deleted 23 lines changed or added

This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/