Browse Prior Art Database

Definitions of Managed Objects for the Ethernet-like Interface Types (RFC2665)

IP.com Disclosure Number: IPCOM000003255D
Original Publication Date: 1999-Aug-01
Included in the Prior Art Database: 2000-Sep-13

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

J. Flick: AUTHOR [+2]

Abstract

This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. This memo obsoletes RFC 2358, "Definitions of Managed Objects for the Ethernet-like Interface Types". This memo extends that specification by including management information useful for the management of 1000 Mb/s and full-duplex Ethernet interfaces.

This text was extracted from a ASCII Text document.
This is the abbreviated version, containing approximately 3% of the total text.

Network Working Group J. Flick

Request for Comments: 2665 Hewlett-Packard Company

Obsoletes: 2358 J. Johnson

Category: Standards Track RedBack Networks

August 1999

Definitions of Managed Objects for

the Ethernet-like Interface Types

Status of this Memo

This document specifies an Internet standards track protocol for the

Internet community, and requests discussion and suggestions for

improvements. Please refer to the current edition of the "Internet

Official Protocol Standards" (STD 1) for the standardization state

and status of this protocol. Distribution of this memo is unlimited.

Copyright Notice

Copyright (C) The Internet Society (1999). All Rights Reserved.

Abstract

This memo defines a portion of the Management Information Base (MIB)

for use with network management protocols in the Internet community.

This memo obsoletes RFC 2358, "Definitions of Managed Objects for the

Ethernet-like Interface Types". This memo extends that specification

by including management information useful for the management of 1000

Mb/s and full-duplex Ethernet interfaces.

Ethernet technology, as defined by the 802.3 Working Group of the

IEEE, continues to evolve, with scalable increases in speed, new

types of cabling and interfaces, and new features. This evolution

may require changes in the managed objects in order to reflect this

new functionality. This document, as with other documents issued by

this working group, reflects a certain stage in the evolution of

Ethernet technology. In the future, this document might be revised,

or new documents might be issued by the Ethernet Interfaces and Hub

MIB Working Group, in order to reflect the evolution of Ethernet

technology.

Table of Contents

1. Introduction ................................................ 2

2. The SNMP Management Framework .............................. 3

3. Overview ................................................... 4

3.1. Relation to MIB-2 ........................................ 4

3.2. Relation to the Interfaces MIB ........................... 5

3.2.1. Layering Model ......................................... 5

3.2.2. Virtual Circuits ....................................... 5

3.2.3. ifTestTable ............................................ 5

3.2.4. ifRcvAddressTable ...................................... 6

3.2.5. ifPhysAddress .......................................... 6

3.2.6. ifType ................................................. 6

3.2.7. Specific Interface MIB Objects ......................... 7

3.3. Relation to the 802.3 MAU MIB ............................ 11

3.4. dot3StatsEtherChipSet .................................... 11

3.5. Mapping...