draft-ietf-hubmib-etherif-mib-03.txt   draft-ietf-hubmib-etherif-mib-04.txt 
Hub MIB Working Group J. Flick Hub MIB Working Group J. Flick
INTERNET DRAFT Hewlett-Packard Company INTERNET DRAFT Hewlett-Packard Company
J. Johnson J. Johnson
RedBack Networks RedBack Networks
F. Kastenholz March 1998
FTP Software, Inc.
February 1998
Definitions of Managed Objects for Definitions of Managed Objects for
the Ethernet-like Interface Types the Ethernet-like Interface Types
<draft-ietf-hubmib-etherif-mib-03.txt> <draft-ietf-hubmib-etherif-mib-04.txt>
Status of this Memo Status of this Memo
This document is an Internet-Draft. Internet-Drafts are working This document is an Internet-Draft. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas, documents of the Internet Engineering Task Force (IETF), its areas,
and its working groups. Note that other groups may also distribute and its working groups. Note that other groups may also distribute
working documents as Internet-Drafts. working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
skipping to change at page 1, line 43 skipping to change at page 1, line 41
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (1998). All Rights Reserved. Copyright (C) The Internet Society (1998). All Rights Reserved.
Abstract Abstract
This memo is an extension to the SNMP MIB. It specifies an IAB This memo is an extension to the SNMP MIB. It specifies an IAB
standards track protocol for the Internet community, and requests standards track protocol for the Internet community, and requests
discussion and suggestions for improvements. The origin of this memo discussion and suggestions for improvements. The origin of this memo
is from RFC 1650 "Definitions of Managed Objects for the Ethernet- is from RFC 1650 ''Definitions of Managed Objects for the Ethernet-
like Interface Types using SMIv2." This memo extends that like Interface Types using SMIv2.'' This memo extends that
specification by including management information useful for the specification by including management information useful for the
management of 100BaseT ethernet interfaces. management of 100BaseT ethernet interfaces.
Distribution of this memo is unlimited. Please forward comments to Distribution of this memo is unlimited. Please forward comments to
hubmib@hprnd.rose.hp.com. hubmib@hprnd.rose.hp.com.
Table of Contents
1. Introduction ................................................ 2
2. The SNMP Network Management Framework ...................... 2
2.1. Object Definitions ....................................... 3
3. Change Log ................................................. 3
4. Overview ................................................... 4
4.1. Relation to MIB-2 ........................................ 4
4.2. Relation to the Interfaces MIB ........................... 5
4.2.1. Layering Model ......................................... 5
4.2.2. Virtual Circuits ....................................... 5
4.2.3. ifTestTable ............................................ 6
4.2.4. ifRcvAddressTable ...................................... 6
4.2.5. ifPhysAddress .......................................... 6
4.2.6. ifType ................................................. 7
4.2.7. Specific Interface MIB Objects ......................... 8
4.3. Relation to the 802.3 MAU MIB ............................ 11
4.4. Mapping of IEEE 802.3 Managed Objects .................... 11
5. Definitions ................................................ 12
6. Intellectual Property ...................................... 35
7. Acknowledgements ........................................... 35
8. References ................................................. 36
9. Security Considerations .................................... 37
10. Author's Addresses ........................................ 38
11. Full Copyright Statement .................................. 38
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:
RFC1650 [11]. RFC1650 [11].
skipping to change at page 13, line 19 skipping to change at page 13, line 4
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY, MODULE-IDENTITY, OBJECT-TYPE, OBJECT-IDENTITY,
Counter32, mib-2, transmission Counter32, mib-2, transmission
FROM SNMPv2-SMI FROM SNMPv2-SMI
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
ifIndex, InterfaceIndex ifIndex, InterfaceIndex
FROM IF-MIB; FROM IF-MIB;
etherMIB MODULE-IDENTITY etherMIB MODULE-IDENTITY
LAST-UPDATED "9802172351Z" -- February 17, 1998 LAST-UPDATED "9802260008Z" -- February 26, 1998
ORGANIZATION "IETF 802.3 Hub MIB Working Group" ORGANIZATION "IETF 802.3 Hub MIB Working Group"
CONTACT-INFO CONTACT-INFO
"WG E-mail: hubmib@hprnd.rose.hp.com "WG E-mail: hubmib@hprnd.rose.hp.com
Chair: Dan Romascanu Chair: Dan Romascanu
Postal: Madge Networks Postal: LANNET Ltd.
Atidum Technology Park, Bldg. 3 Atidum Technology Park, Bldg. 3
Tel Aviv 61131 Tel Aviv 61131
Israel Israel
Tel: +972 3 645 8414 Tel: +972 3 645 8414
E-mail: dromasca@madge.com E-mail: dromasca@lannet.com
Editor: John Flick Editor: John Flick
Postal: Hewlett-Packard Company Postal: Hewlett-Packard Company
8000 Foothills Blvd. M/S 5556 8000 Foothills Blvd. M/S 5556
Roseville, CA 95747-5556 Roseville, CA 95747-5556
USA USA
Tel: +1 916 785 4018 Tel: +1 916 785 4018
Fax: +1 916 785 3583 Fax: +1 916 785 3583
E-mail: johnf@hprnd.rose.hp.com E-mail: johnf@hprnd.rose.hp.com
skipping to change at page 14, line 6 skipping to change at page 13, line 40
USA USA
Tel: +1 408 571 2699 Tel: +1 408 571 2699
Fax: +1 408 571 2698 Fax: +1 408 571 2698
E-Mail: jeff@redbacknetworks.com" E-Mail: jeff@redbacknetworks.com"
DESCRIPTION "The MIB module to describe generic objects for DESCRIPTION "The MIB module to describe generic objects for
Ethernet-like network interfaces. This MIB is an Ethernet-like network interfaces. This MIB is an
updated version of the Ethernet-like MIB in RFC updated version of the Ethernet-like MIB in RFC
1650." 1650."
REVISION "9802172351Z" REVISION "9802260008Z"
DESCRIPTION "Updated to include support for 100 Mb/sec DESCRIPTION "Updated to include support for 100 Mb/sec
interfaces." interfaces."
REVISION "9402030400Z" REVISION "9402030400Z"
DESCRIPTION "Version published as RFC 1650." DESCRIPTION "Version published as RFC 1650."
::= { mib-2 35 } ::= { mib-2 35 }
etherMIBObjects OBJECT IDENTIFIER ::= { etherMIB 1 } etherMIBObjects OBJECT IDENTIFIER ::= { etherMIB 1 }
dot3 OBJECT IDENTIFIER ::= { transmission 7 } dot3 OBJECT IDENTIFIER ::= { transmission 7 }
skipping to change at page 39, line 11 skipping to change at page 38, line 25
Email: johnf@hprnd.rose.hp.com Email: johnf@hprnd.rose.hp.com
Jeffrey Johnson Jeffrey Johnson
RedBack Networks RedBack Networks
2570 North First Street, Suite 410 2570 North First Street, Suite 410
San Jose, CA, 95131, USA San Jose, CA, 95131, USA
Phone: +1 408 571 2699 Phone: +1 408 571 2699
EMail: jeff@redbacknetworks.com EMail: jeff@redbacknetworks.com
Frank Kastenholz
FTP Software, Inc.
2 High Street
North Andover, Mass, USA 01845
Phone: +1 508 685 4000
EMail: kasten@ftp.com
11. Full Copyright Statement 11. Full Copyright Statement
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it others, and derivative works that comment on or otherwise explain it
or assist in its implementation may be prepared, copied, published or assist in its implementation may be prepared, copied, published
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph are kind, provided that the above copyright notice and this paragraph are
included on all such copies and derivative works. However, this included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other the copyright notice or references to the Internet Society or other
skipping to change at page 40, line 4 skipping to change at line 1788
The limited permissions granted above are perpetual and will not be The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns. revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Table of Contents
1. Introduction ................................................ 2
2. The SNMP Network Management Framework ...................... 2
2.1. Object Definitions ....................................... 2
3. Change Log ................................................. 2
4. Overview ................................................... 3
4.1. Relation to MIB-2 ........................................ 4
4.2. Relation to the Interfaces MIB ........................... 4
4.2.1. Layering Model ......................................... 5
4.2.2. Virtual Circuits ....................................... 5
4.2.3. ifTestTable ............................................ 5
4.2.4. ifRcvAddressTable ...................................... 5
4.2.5. ifPhysAddress .......................................... 6
4.2.6. ifType ................................................. 6
4.2.7. Specific Interface MIB Objects ......................... 7
4.3. Relation to the 802.3 MAU MIB ............................ 10
4.4. Mapping of IEEE 802.3 Managed Objects .................... 10
5. Definitions ................................................ 13
6. Intellectual Property ...................................... 36
7. Acknowledgements ........................................... 36
8. References ................................................. 37
9. Security Considerations .................................... 38
10. Author's Addresses ........................................ 38
11. Full Copyright Statement .................................. 39
 End of changes. 

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