draft-ietf-hubmib-mau-mib-00.txt | draft-ietf-hubmib-mau-mib-01.txt | |||
---|---|---|---|---|
Definitions of Managed Objects | Definitions of Managed Objects | |||
for IEEE 802.3 Medium Attachment Units (MAUs) | for IEEE 802.3 Medium Attachment Units (MAUs) | |||
<draft-ietf-hubmib-mau-mib-00.txt> | 14 February 1996 | |||
27 November 1995 | <draft-ietf-hubmib-mau-mib-01.txt> | |||
Dan Romascanu | Dan Romascanu | |||
LANNET Data Communications, Ltd. | Madge Networks (Israel) Ltd. | |||
dan@lannet.com | dan@lannet.com | |||
Kathryn de Graaf | Kathryn de Graaf | |||
3Com Corporation | 3Com Corporation | |||
kdegraaf@chipcom.com | kdegraaf@isd.3com.com | |||
Status of this Memo | Status of this Memo | |||
This document is an Internet-Draft. Internet-Drafts are | This document is an Internet-Draft. Internet-Drafts are | |||
working documents of the Internet Engineering Task Force | working documents of the Internet Engineering Task Force | |||
(IETF), its areas, and its working groups. Note that other | (IETF), its areas, and its working groups. Note that other | |||
groups may also distribute working documents as Internet- | groups may also distribute working documents as Internet- | |||
Drafts. | Drafts. | |||
Internet-Drafts are draft documents valid for a maximum of six | Internet-Drafts are draft documents valid for a maximum of six | |||
skipping to change at page 2, line 10 | skipping to change at page 2, line 10 | |||
To learn the current status of any Internet-Draft, please | To learn the current status of any Internet-Draft, please | |||
check the "1id-abstracts.txt" listing contained in the | check the "1id-abstracts.txt" listing contained in the | |||
Internet-Drafts Shadow Directories on ds.internic.net (US East | Internet-Drafts Shadow Directories on ds.internic.net (US East | |||
Coast), nic.nordu.net (Europe), ftp.isi.edu (US West Coast), | Coast), nic.nordu.net (Europe), ftp.isi.edu (US West Coast), | |||
or munnari.oz.au (Pacific Rim). | or munnari.oz.au (Pacific Rim). | |||
Abstract | Abstract | |||
This memo defines an experimental portion of the Management | This memo defines an experimental portion of the Management | |||
Information Base (MIB) for use with network management | Information Base (MIB) for use with network management | |||
protocols in the Internets community. In particular, it | protocols in the Internet community. In particular, it | |||
defines objects for managing 10 and 100 Mb/second Medium | defines objects for managing 10 and 100 Mb/second Medium | |||
Attachment Units (MAUs) based on IEEE Std 802.3 Section 30, | Attachment Units (MAUs) based on IEEE Std 802.3 Section 30, | |||
"10 & 100 Mb/s Management," October 26, 1995. | "10 & 100 Mb/s Management," October 26, 1995. | |||
This memo does not specify a standard for the Internet | This memo does not specify a standard for the Internet | |||
community. | community. | |||
1. The SNMPv2 Network Management Framework | 1. The SNMPv2 Network Management Framework | |||
The SNMPv2 Network Management Framework consists of four major | The SNMPv2 Network Management Framework consists of several | |||
components. They are: | major components. They include: | |||
o RFC 1442 which defines the SMI, the mechanisms used for | o RFC 1902 which defines the SMI, the mechanisms used for | |||
describing and naming objects for the purpose of | describing and naming objects for the purpose of | |||
management. | management. | |||
o STD 17, RFC 1213 defines MIB-II, the core set of managed | o STD 17, RFC 1213 defines MIB-II, the core set of managed | |||
objects for the Internet suite of protocols. | objects for the Internet suite of protocols. | |||
o RFC 1445 which defines the administrative and other | o RFC 1905 which defines the protocol used for network | |||
architectural aspects of the framework. | ||||
o RFC 1448 which defines the protocol used for network | ||||
access to managed objects. | access to managed objects. | |||
The Framework permits new objects to be defined for the | The Framework permits new objects to be defined for the | |||
purpose of experimentation and evaluation. | purpose of experimentation and evaluation. | |||
1.1. Object Definitions | 1.1. Object Definitions | |||
Managed objects are accessed via a virtual information store, | Managed objects are accessed via a virtual information store, | |||
termed the Management Information Base or MIB. Objects in the | termed the Management Information Base or MIB. Objects in the | |||
MIB are defined using the subset of Abstract Syntax Notation | MIB are defined using the subset of Abstract Syntax Notation | |||
skipping to change at page 4, line 11 | skipping to change at page 4, line 11 | |||
instance serves to uniquely identify a specific instantiation | instance serves to uniquely identify a specific instantiation | |||
of the object. For human convenience, we often use a textual | of the object. For human convenience, we often use a textual | |||
string, termed the descriptor, to refer to the object type. | string, termed the descriptor, to refer to the object type. | |||
2. Overview | 2. Overview | |||
Instances of these object types represent attributes of an | Instances of these object types represent attributes of an | |||
IEEE 802.3 MAU. Several types of MAUs are defined in the IEEE | IEEE 802.3 MAU. Several types of MAUs are defined in the IEEE | |||
802.3 CSMA/CD standard [1] and [2]. These MAUs may be | 802.3 CSMA/CD standard [1] and [2]. These MAUs may be | |||
connected to IEEE 802.3 repeaters or to 802.3 (Ethernet-like) | connected to IEEE 802.3 repeaters or to 802.3 (Ethernet-like) | |||
interfaces. | interfaces. For convenience this document refers to these | |||
devices as "repeater MAUs" and "interface MAUs." | ||||
The definitions presented here are based on Section 30.5, | The definitions presented here are based on Section 30.5, | |||
"Layer Management for 10 & 100 Mb/s Medium Attachment Units | "Layer Management for 10 & 100 Mb/s Medium Attachment Units | |||
(MAUs)", and Annex 30A, "GDMO Specifications for 802.3 managed | (MAUs)", and Annex 30A, "GDMO Specifications for 802.3 managed | |||
objects" of IEEE Std 802.3u-1995. That specification includes | objects" of IEEE Std 802.3u-1995. That specification includes | |||
definitions for both 10Mb/s and 100Mb/s devices, and is | definitions for both 10Mb/s and 100Mb/s devices, and is | |||
essentially a superset of the 10Mb/s definitions given by IEEE | essentially a superset of the 10Mb/s definitions given by IEEE | |||
802.3 Section 20. This specification is intended to serve the | 802.3 Section 20. This specification is intended to serve the | |||
same purpose: to provide for management of both 10Mb/s and | same purpose: to provide for management of both 10Mb/s and | |||
100Mb/s MAUs. | 100Mb/s MAUs. | |||
MAUs are components that are often located inside a larger | 2.1. Relationship to Other MIBs | |||
system, and are not always externally visible to a network | ||||
administrator. The external connection of a MAU is generally | It is assumed that an agent implementing this MIB will also | |||
a jack to which a network cable can be attached. The internal | implement (at least) the 'system' group defined in MIB-II. | |||
connection of a MAU can be, as explained above, a repeater | The following sections identify other MIBs that such an agent | |||
port or an interface. In some systems, this internal | should implement. | |||
connectivity may be configurable. Additionally, the | ||||
introduction of auto-negotiation functionality in the IEEE | 2.1.1. Relationship to the 'interfaces' group | |||
802.3 specification allows for a connection which can, to a | ||||
certain degree, configure or reconfigure itself during | The sections of this document that define interface MAU- | |||
operation. This MIB includes objects for jack configuration | related objects specify an extension to the 'interfaces' group | |||
and status that are intended to allow the network management | of MIB-II. An agent implementing these interface-MAU related | |||
software to model and report the connectivity between the | objects must also implement the 'interfaces' group of MIB-II. | |||
external jacks, the MAUs, and the other components (repeater | The value of the ifMauIfIndex object is the same as the value | |||
ports or interfaces) within such a system, including both | of 'ifIndex' used to instantiate the interface to which the | |||
administrative configuration and auto- negotiation. This | given MAU is connected. | |||
model assumes a one-to-one relationship between jacks and | ||||
MAUs. | It is expected that an agent implementing the interface-MAU | |||
related objects in this MIB will also implement the Ethernet- | ||||
like Interfaces MIB, RFC 1650. | ||||
(Note that repeater ports are not represented as interfaces in | ||||
the sense of MIB-II's 'interfaces' group.) | ||||
2.1.2. Relationship to the 802.3 Repeater MIB | ||||
The section of this document that defines repeater MAU-related | ||||
objects specifies an extension to the 802.3 Repeater MIB | ||||
defined in [4]. An agent implementing these repeater-MAU | ||||
related objects must also implement the 802.3 Repeater MIB. | ||||
The values of 'rpMauGroupIndex' and 'rpMauPortIndex' used to | ||||
instantiate a repeater MAU variable shall be the same as the | ||||
values of 'rptrPortGroupIndex' and 'rptrPortIndex' used to | ||||
instantiate the port to which the given MAU is connected. | ||||
2.2. Management of Internal MAUs | ||||
In some situations, a MAU can be "internal" -- i.e., its | ||||
functionality is implemented entirely within a device. For | ||||
example, a managed repeater may contain an internal repeater- | ||||
MAU and/or an internal interface-MAU through which management | ||||
communications originating on one of the repeater's external | ||||
ports pass in order to reach the management agent associated | ||||
with the repeater. Such internal MAUs may or may not be | ||||
managed. If they are managed, objects describing their | ||||
attributes should appear in the appropriate MIB group -- | ||||
dot3RpMauBasicGroup for internal repeater-MAUs and | ||||
dot3IfMauBasicGroup for internal interface-MAUs. | ||||
3. Definitions | 3. Definitions | |||
MAU-MIB DEFINITIONS ::= BEGIN | MAU-MIB DEFINITIONS ::= BEGIN | |||
IMPORTS | IMPORTS | |||
experimental, Counter32, Integer32, Gauge32, Counter64, | experimental, | |||
Counter32, Integer32, | ||||
OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE | OBJECT-TYPE, MODULE-IDENTITY, NOTIFICATION-TYPE | |||
FROM SNMPv2-SMI | FROM SNMPv2-SMI | |||
TimeStamp, DisplayString, MacAddress, TEXTUAL-CONVENTION, | OBJECT-GROUP, MODULE-COMPLIANCE | |||
RowStatus | ||||
FROM SNMPv2-TC | ||||
OBJECT-GROUP, MODULE-COMPLIANCE, NOTIFICATION-GROUP, | ||||
FROM SNMPv2-CONF | FROM SNMPv2-CONF | |||
mib-2 | mib-2 | |||
FROM RFC1213-MIB; | FROM RFC1213-MIB; | |||
mauMod MODULE-IDENTITY | mauMod MODULE-IDENTITY | |||
LAST-UPDATED "9511270000Z" | LAST-UPDATED "9602140000Z" | |||
ORGANIZATION "IETF HUB MIB Working Group" | ORGANIZATION "IETF HUB MIB Working Group" | |||
CONTACT-INFO | CONTACT-INFO | |||
"WG E-mail: hubmib@baynetworks.com | "WG E-mail: hubmib@hprnd.rose.hp.com | |||
Chair: Dan Romascanu | Chair: Dan Romascanu | |||
Postal: LANNET Data Communications, Ltd. | Postal: Madge Networks (Israel) Ltd. | |||
Atidim Technology Park, Bldg. 3 | Atidim Technology Park, Bldg. 3 | |||
Tel Aviv 61131, Israel | Tel Aviv 61131, Israel | |||
Tel: 972-3-6458414, 6458458 | Tel: 972-3-6458414, 6458458 | |||
Fax: 972-3-6487146 | Fax: 972-3-6487146 | |||
E-mail: dan@lannet.com | E-mail: dan@lannet.com | |||
Editor: Kathryn de Graaf | Editor: Kathryn de Graaf | |||
Postal: 3Com Corporation | Postal: 3Com Corporation | |||
118 Turnpike Rd. | 118 Turnpike Rd. | |||
Southborough, MA 01772 | Southborough, MA 01772 | |||
USA | USA | |||
Tel: (508)229-1627 | Tel: (508)229-1627 | |||
Fax: (508)490-5882 | Fax: (508)490-5882 | |||
E-mail: kdegraaf@chipcom.com" | E-mail: kdegraaf@isd.3com.com" | |||
DESCRIPTION | DESCRIPTION | |||
"Management information for 802.3 MAUs. | "Management information for 802.3 MAUs. | |||
The following references are used throughout this | The following references are used throughout this | |||
MIB module: | MIB module: | |||
[IEEE 802.3 Std] | [IEEE 802.3 Std] | |||
refers to IEEE 802.3/ISO 8802-3 Information | refers to IEEE 802.3/ISO 8802-3 Information | |||
processing systems - Local area networks - | processing systems - Local area networks - | |||
Part 3: Carrier sense multiple access with | Part 3: Carrier sense multiple access with | |||
skipping to change at page 6, line 22 | skipping to change at page 7, line 19 | |||
IEEE Std 802.3, clauses 22 through 29. | IEEE Std 802.3, clauses 22 through 29. | |||
[IEEE 802.3 Mgt] | [IEEE 802.3 Mgt] | |||
refers to IEEE 802.3u-1995, - 10 Mb/s & | refers to IEEE 802.3u-1995, - 10 Mb/s & | |||
100 Mb/s Management, Section 30 - | 100 Mb/s Management, Section 30 - | |||
Supplement to IEEE Std 802.3." | Supplement to IEEE Std 802.3." | |||
::= { snmpDot3MauMgt 6 } | ::= { snmpDot3MauMgt 6 } | |||
snmpDot3MauMgt OBJECT IDENTIFIER ::= { experimental x } | snmpDot3MauMgt OBJECT IDENTIFIER ::= { experimental x } | |||
-- the following subtrees are deprecated | ||||
dot3RpMauBasicGroup OBJECT IDENTIFIER ::= { snmpDot3MauMgt 1 } | dot3RpMauBasicGroup OBJECT IDENTIFIER ::= { snmpDot3MauMgt 1 } | |||
dot3IfMauBasicGroup OBJECT IDENTIFIER ::= { snmpDot3MauMgt 2 } | dot3IfMauBasicGroup OBJECT IDENTIFIER ::= { snmpDot3MauMgt 2 } | |||
dot3BroadMauBasicGroup OBJECT IDENTIFIER ::= { snmpDot3MauMgt 3 } | dot3BroadMauBasicGroup OBJECT IDENTIFIER ::= { snmpDot3MauMgt 3 } | |||
dot3MauBasicGroup OBJECT IDENTIFIER ::= { snmpDot3MauMgt 7 } | dot3IfMauAutoNegGroup OBJECT IDENTIFIER ::= { snmpDot3MauMgt 5 } | |||
-- object identifiers for MAU types | -- object identifiers for MAU types | |||
-- (see rpMauType and ifMauType for usage) | -- (see rpMauType and ifMauType for usage) | |||
dot3MauType | dot3MauType | |||
OBJECT IDENTIFIER ::= { snmpDot3MauMgt 4 } | OBJECT IDENTIFIER ::= { snmpDot3MauMgt 4 } | |||
dot3MauTypeAUI -- no internal MAU, view from AUI | dot3MauTypeAUI -- no internal MAU, view from AUI | |||
OBJECT IDENTIFIER ::= { dot3MauType 1 } | OBJECT IDENTIFIER ::= { dot3MauType 1 } | |||
dot3MauType10Base5 -- thick coax MAU (per 802.3 section 8) | dot3MauType10Base5 -- thick coax MAU (per 802.3 section 8) | |||
OBJECT IDENTIFIER ::= { dot3MauType 2 } | OBJECT IDENTIFIER ::= { dot3MauType 2 } | |||
skipping to change at page 7, line 23 | skipping to change at page 8, line 20 | |||
-- new for 100 MB/s: | -- new for 100 MB/s: | |||
dot3MauType100BaseT4 -- 4 pair categ. 3 UTP (per 802.3 section 23) | dot3MauType100BaseT4 -- 4 pair categ. 3 UTP (per 802.3 section 23) | |||
OBJECT IDENTIFIER ::= { dot3MauType 10 } | OBJECT IDENTIFIER ::= { dot3MauType 10 } | |||
dot3MauType100BaseTX -- 2 pair categ. 5 UTP (per 802.3 section 25) | dot3MauType100BaseTX -- 2 pair categ. 5 UTP (per 802.3 section 25) | |||
OBJECT IDENTIFIER ::= { dot3MauType 11 } | OBJECT IDENTIFIER ::= { dot3MauType 11 } | |||
dot3MauType100BaseFX -- X fiber over PMT (per 802.3 section 26) | dot3MauType100BaseFX -- X fiber over PMT (per 802.3 section 26) | |||
OBJECT IDENTIFIER ::= { dot3MauType 12 } | OBJECT IDENTIFIER ::= { dot3MauType 12 } | |||
-- | -- | |||
-- The Basic MAU Table | -- The Basic Repeater MAU Table | |||
-- | -- | |||
mauTable OBJECT-TYPE | rpMauTable OBJECT-TYPE | |||
SYNTAX SEQUENCE OF MauEntry | SYNTAX SEQUENCE OF RpMauEntry | |||
MAX-ACCESS not-accessible | MAX-ACCESS not-accessible | |||
STATUS mandatory | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"Table of descriptive and status information about | "Table of descriptive and status information about | |||
the managed MAU(s) in this system." | the MAU(s) attached to the ports of a repeater." | |||
::= { mauBasicGroup 1 } | ::= { dot3RpMauBasicGroup 1 } | |||
mauEntry OBJECT-TYPE | rpMauEntry OBJECT-TYPE | |||
SYNTAX MauEntry | SYNTAX RpMauEntry | |||
MAX-ACCESS not-accessible | MAX-ACCESS not-accessible | |||
STATUS mandatory | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"An entry in the table, containing information | "An entry in the table, containing information | |||
about a single MAU." | about a single MAU." | |||
INDEX { mauGroupIndex, mauIndex } | INDEX { rpMauGroupIndex, rpMauPortIndex, rpMauIndex } | |||
::= { mauTable 1 } | ::= { rpMauTable 1 } | |||
MauEntry ::= | RpMauEntry ::= | |||
SEQUENCE { | SEQUENCE { | |||
mauGroupIndex | rpMauGroupIndex | |||
Integer32, | Integer32, | |||
mauIndex | rpMauPortIndex | |||
Integer32, | Integer32, | |||
mauType | rpMauIndex | |||
OBJECT IDENTIFIER, | ||||
mauTypeList | ||||
Integer32, | Integer32, | |||
mauStatus | rpMauType | |||
OBJECT IDENTIFIER, | ||||
rpMauStatus | ||||
INTEGER, | INTEGER, | |||
mauMediaAvail | rpMauMediaAvail | |||
INTEGER, | INTEGER, | |||
mauMediaAvailStateExits | rpMauMediaAvailStateExits | |||
Counter32, | Counter32, | |||
mauJabberState | rpMauJabberState | |||
INTEGER, | INTEGER, | |||
mauJabberingStateEnters | rpMauJabberingStateEnters | |||
Counter32, | Counter32, | |||
mauFalseCarriers | rpMauFalseCarriers | |||
Counter32 | Counter32 | |||
} | } | |||
mauGroupIndex OBJECT-TYPE | rpMauGroupIndex OBJECT-TYPE | |||
SYNTAX Integer32 (1..2147483647) | SYNTAX Integer32 (1..2147483647) | |||
MAX-ACCESS read-only | MAX-ACCESS read-only | |||
STATUS mandatory | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"This variable uniquely identifies the group | "This variable uniquely identifies the group | |||
containing the MAU described by this entry. | containing the port to which the MAU described by | |||
this entry is connected. | ||||
Note: In practice, a group will generally be a | Note: In practice, a group will generally be a | |||
field-replaceable unit (i.e., module, card, or | field-replaceable unit (i.e., module, card, or | |||
board) that can fit in the physical system | board) that can fit in the physical system | |||
enclosure, and the group number will correspond to | enclosure, and the group number will correspond to | |||
a number marked on the physical enclosure. | a number marked on the physical enclosure. | |||
For MAUs attached to repeaters, the group denoted | The group denoted by a particular value of this | |||
by a particular value of this object is the same | object is the same as the group denoted by the | |||
as the group denoted by the same value of | same value of rptrGroupIndex." | |||
rptrGroupIndex." | ::= { rpMauEntry 1 } | |||
::= { mauEntry 1 } | ||||
mauIndex OBJECT-TYPE | rpMauPortIndex OBJECT-TYPE | |||
SYNTAX Integer32 (1..2147483647) | SYNTAX Integer32 (1..2147483647) | |||
MAX-ACCESS read-only | MAX-ACCESS read-only | |||
STATUS mandatory | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"This variable uniquely identifies the MAU within | "This variable uniquely identifies the repeater | |||
group mauGroupIndex that is described by this | port within group rpMauGroupIndex to which the MAU | |||
entry." | described by this entry is connected." | |||
REFERENCE | ||||
"" | ||||
::= { rpMauEntry 2 } | ||||
rpMauIndex OBJECT-TYPE | ||||
SYNTAX Integer32 (1..2147483647) | ||||
MAX-ACCESS read-only | ||||
STATUS current | ||||
DESCRIPTION | ||||
"This variable uniquely identifies the MAU | ||||
connected to port rpMauPortIndex within group | ||||
rpMauGroupIndex that is described by this entry." | ||||
REFERENCE | REFERENCE | |||
"[IEEE 802.3 Mgt], 30.5.1.1.1, aMAUID." | "[IEEE 802.3 Mgt], 30.5.1.1.1, aMAUID." | |||
::= { mauEntry 2 } | ::= { rpMauEntry 3 } | |||
mauType OBJECT-TYPE | rpMauType OBJECT-TYPE | |||
SYNTAX OBJECT IDENTIFIER | SYNTAX OBJECT IDENTIFIER | |||
MAX-ACCESS read-only | MAX-ACCESS read-only | |||
STATUS mandatory | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"This object identifies the 10 or 100 Mb/s | "This object identifies the 10 or 100 Mb/s | |||
baseband MAU type. An initial set of MAU types | baseband MAU type. An initial set of MAU types | |||
are defined above. The assignment of OBJECT | are defined above. The assignment of OBJECT | |||
IDENTIFIERs to new types of MAUs is managed by the | IDENTIFIERs to new types of MAUs is managed by the | |||
IANA. If the MAU type is unknown, the object | IANA. If the MAU type is unknown, the object | |||
identifier | identifier | |||
unknownMauType OBJECT IDENTIFIER ::= { 0 0 } | unknownMauType OBJECT IDENTIFIER ::= { 0 0 } | |||
is returned. Note that unknownMauType is a | is returned. Note that unknownMauType is a | |||
syntactically valid object identifier, and any | syntactically valid object identifier, and any | |||
conformant implementation of ASN.1 and the BER | conformant implementation of ASN.1 and the BER | |||
must be able to generate and recognize this | must be able to generate and recognize this | |||
value." | value." | |||
REFERENCE | REFERENCE | |||
"[IEEE 802.3 Mgt], 30.5.1.1.2, aMAUType." | "[IEEE 802.3 Mgt], 30.5.1.1.2, aMAUType." | |||
::= { mauEntry 3 } | ::= { rpMauEntry 4 } | |||
mauTypeList OBJECT-TYPE | ||||
SYNTAX Integer32 | ||||
MAX-ACCESS read-only | ||||
STATUS mandatory | ||||
DESCRIPTION | ||||
"A value that uniquely identifies the set of | ||||
possible IEEE 802.3 types that the MAU could be. | ||||
The value is a sum which initially takes the value | ||||
zero. Then, for each type capability of this MAU, | ||||
2 raised to the power noted below is added to the | ||||
sum. For example, a MAU which has the capability | ||||
to be only 10BASE-T would have a value of 512 | ||||
(2**9). In contrast, a MAU which supports both | ||||
10Base-T and 100BASE-TX would have a value of 1536 | ||||
((2**9) + (2**10)). | ||||
The powers of 2 assigned to the capabilities are | ||||
these: | ||||
Power Capability | ||||
1 AUI | ||||
2 10BASE-5 | ||||
3 FOIRL | ||||
4 10BASE-2 | ||||
5 10BASE-T | ||||
6 10BASE-FP | ||||
7 10BASE-FB | ||||
8 10BASE-FL | ||||
9 10BROAD36 | ||||
10 100BASE-T4 | ||||
11 100BASE-TX | ||||
12 100BASE-FX | ||||
If auto-negotiation is present on the jack to | ||||
which this MAU is attached, this attribute will | ||||
map to the jackAutoNegCapability." | ||||
::= { mauEntry 4 } | ||||
mauStatus OBJECT-TYPE | rpMauStatus OBJECT-TYPE | |||
SYNTAX INTEGER { | SYNTAX INTEGER { | |||
other(1), | other(1), | |||
unknown(2), | unknown(2), | |||
operational(3), | operational(3), | |||
standby(4), | standby(4), | |||
shutdown(5), | shutdown(5), | |||
reset(6) | reset(6) | |||
} | } | |||
MAX-ACCESS read-write | MAX-ACCESS read-write | |||
STATUS mandatory | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"The current state of the MAU. This object may be | "The current state of the MAU. This object may be | |||
implemented as a read-only object by those agents | implemented as a read-only object by those agents | |||
and MAUs that do not implement software control of | and MAUs that do not implement software control of | |||
the MAU state. Some agents may not support | the MAU state. Some agents may not support | |||
setting the value of this object to some of the | setting the value of this object to some of the | |||
enumerated values. | enumerated values. | |||
The value other(1) is returned if the MAU is in a | The value other(1) is returned if the MAU is in a | |||
state other than one of the states 2 through 6. | state other than one of the states 2 through 6. | |||
skipping to change at page 11, line 17 | skipping to change at page 11, line 33 | |||
being initialized. | being initialized. | |||
A MAU in the operational(3) state is fully | A MAU in the operational(3) state is fully | |||
functional, operates, and passes signals to its | functional, operates, and passes signals to its | |||
attached DTE or repeater port in accordance to its | attached DTE or repeater port in accordance to its | |||
specification. | specification. | |||
A MAU in standby(4) state forces DI and CI to idle | A MAU in standby(4) state forces DI and CI to idle | |||
and the media transmitter to idle or fault, if | and the media transmitter to idle or fault, if | |||
supported. Standby(4) mode only applies to link | supported. Standby(4) mode only applies to link | |||
type MAUs. The state of mauMediaAvail is | type MAUs. The state of rpMauMediaAvail is | |||
unaffected. | unaffected. | |||
A MAU in shutdown(5) state assumes the same | A MAU in shutdown(5) state assumes the same | |||
condition on DI, CI, and the media transmitter as | condition on DI, CI, and the media transmitter as | |||
though it were powered down or not connected. The | though it were powered down or not connected. The | |||
MAU may return other(1) value for the | MAU may return other(1) value for the | |||
mauJabberState and mauMediaAvail objects when it | rpMauJabberState and rpMauMediaAvail objects when | |||
is in this state. For an AUI, this state will | it is in this state. For an AUI, this state will | |||
remove power from the AUI. | remove power from the AUI. | |||
Setting this variable to the value reset(6) resets | Setting this variable to the value reset(6) resets | |||
the MAU in the same manner as a power-off, power- | the MAU in the same manner as a power-off, power- | |||
on cycle of at least one-half second would. The | on cycle of at least one-half second would. The | |||
agent is not required to return the value reset | agent is not required to return the value reset | |||
(6). | (6). | |||
Setting this variable to the value operational(3), | Setting this variable to the value operational(3), | |||
standby(4), or shutdown(5) causes the MAU to | standby(4), or shutdown(5) causes the MAU to | |||
assume the respective state except that setting a | assume the respective state except that setting a | |||
mixing-type MAU or an AUI to standby(4) will cause | mixing-type MAU or an AUI to standby(4) will cause | |||
the MAU to enter the shutdown state." | the MAU to enter the shutdown state." | |||
REFERENCE | REFERENCE | |||
"[IEEE 802.3 Mgt], 30.5.1.1.7, aMAUAdminState, | "[IEEE 802.3 Mgt], 30.5.1.1.7, aMAUAdminState, | |||
30.5.1.2.2, acMAUAdminControl, and 30.5.1.2.1, | 30.5.1.2.2, acMAUAdminControl, and 30.5.1.2.1, | |||
acRESETMAU." | acRESETMAU." | |||
::= { mauEntry 5 } | ::= { rpMauEntry 5 } | |||
mauMediaAvail OBJECT-TYPE | rpMauMediaAvail OBJECT-TYPE | |||
SYNTAX INTEGER { | SYNTAX INTEGER { | |||
other(1), | other(1), | |||
unknown(2), | unknown(2), | |||
available(3), | available(3), | |||
notAvailable(4), | notAvailable(4), | |||
remoteFault(5), | remoteFault(5), | |||
invalidSignal(6), | invalidSignal(6), | |||
remoteJabber(7), | remoteJabber(7), | |||
remoteLinkLoss(8), | remoteLinkLoss(8), | |||
remoteTest(9) | remoteTest(9) | |||
} | } | |||
MAX-ACCESS read-only | MAX-ACCESS read-only | |||
STATUS mandatory | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"If the MAU is a link or fiber type (FOIRL, | "If the MAU is a link or fiber type (FOIRL, | |||
10BASE-T, 10BASE-F) then this is equivalent to the | 10BASE-T, 10BASE-F) then this is equivalent to the | |||
link test fail state/low light function. For an | link test fail state/low light function. For an | |||
AUI or a coax (including broadband) MAU this | AUI or a coax (including broadband) MAU this | |||
indicates whether or not loopback is detected on | indicates whether or not loopback is detected on | |||
the DI circuit. The value of this attribute | the DI circuit. The value of this attribute | |||
persists between packets for MAU types AUI, | persists between packets for MAU types AUI, | |||
10BASE5, 10BASE2, 10BROAD36, and 10BASE-FP. | 10BASE5, 10BASE2, 10BROAD36, and 10BASE-FP. | |||
skipping to change at page 13, line 20 | skipping to change at page 13, line 36 | |||
This value applies to 10BASE-FB, 100BASE-T4 Far | This value applies to 10BASE-FB, 100BASE-T4 Far | |||
End Fault Indication and non-specified remote | End Fault Indication and non-specified remote | |||
faults from a system running Auto-Negotiation. | faults from a system running Auto-Negotiation. | |||
The values remoteJabber(7), remoteLinkLoss(8), and | The values remoteJabber(7), remoteLinkLoss(8), and | |||
remoteTest(9) should be used instead of | remoteTest(9) should be used instead of | |||
remoteFault(5) where the reason for remote fault | remoteFault(5) where the reason for remote fault | |||
is identified in the remote signaling protocol. | is identified in the remote signaling protocol. | |||
The value invalidSignal(6) indicates that an | The value invalidSignal(6) indicates that an | |||
invalid signal has been received from the other | invalid signal has been received from the other | |||
end of the link. Both remoteFault(5) and | end of the link. InvalidSignal(6) applies only to | |||
invalidSignal(6) apply only to MAUs of type | MAUs of type 10BASE-FB. | |||
10BASE-FB. | ||||
Where an IEEE Draft Std 802.3u/D4 clause 22 MII is | Where an IEEE Std 802.3u-1995 clause 22 MII is | |||
present, a logic one in the remote fault bit | present, a logic one in the remote fault bit | |||
(reference section 22.2.4.2.8 of that document) | (reference section 22.2.4.2.8 of that document) | |||
maps to the value remoteFault(5), and a logic zero | maps to the value remoteFault(5), and a logic zero | |||
in the link status bit (reference section | in the link status bit (reference section | |||
22.2.4.2.10 of that document) maps to the value | 22.2.4.2.10 of that document) maps to the value | |||
notAvailable(4). The value notAvailable(4) takes | notAvailable(4). The value notAvailable(4) takes | |||
precedence over the value remoteFault(5)." | precedence over the value remoteFault(5)." | |||
REFERENCE | REFERENCE | |||
"[IEEE 802.3 Mgt], 30.5.1.1.4, aMediaAvailable." | "[IEEE 802.3 Mgt], 30.5.1.1.4, aMediaAvailable." | |||
::= { mauEntry 6 } | ::= { rpMauEntry 6 } | |||
mauMediaAvailStateExits OBJECT-TYPE | rpMauMediaAvailStateExits OBJECT-TYPE | |||
SYNTAX Counter32 | SYNTAX Counter32 | |||
MAX-ACCESS read-only | MAX-ACCESS read-only | |||
STATUS mandatory | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"A count of the number of times that mauMediaAvail | "A count of the number of times that | |||
for this MAU instance leaves the state | rpMauMediaAvail for this MAU instance leaves the | |||
available(3)." | state available(3)." | |||
REFERENCE | REFERENCE | |||
"[IEEE 802.3 Mgt], 30.5.1.1.5, aLoseMediaCounter." | "[IEEE 802.3 Mgt], 30.5.1.1.5, aLoseMediaCounter." | |||
::= { mauEntry 7 } | ::= { rpMauEntry 7 } | |||
mauJabberState OBJECT-TYPE | rpMauJabberState OBJECT-TYPE | |||
SYNTAX INTEGER { | SYNTAX INTEGER { | |||
other(1), | other(1), | |||
unknown(2), | unknown(2), | |||
noJabber(3), | noJabber(3), | |||
jabbering(4) | jabbering(4) | |||
} | } | |||
MAX-ACCESS read-only | MAX-ACCESS read-only | |||
STATUS mandatory | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"The value other(1) is returned if the jabber | "The value other(1) is returned if the jabber | |||
state is not 2, 3, or 4. The agent must always | state is not 2, 3, or 4. The agent must always | |||
return other(1) for MAU type dot3MauTypeAUI. | return other(1) for MAU type dot3MauTypeAUI. | |||
The value unknown(2) is returned when the MAU's | The value unknown(2) is returned when the MAU's | |||
true state is unknown; for example, when it is | true state is unknown; for example, when it is | |||
being initialized. | being initialized. | |||
If the MAU is not jabbering the agent returns | If the MAU is not jabbering the agent returns | |||
noJabber(3). This is the 'normal' state. | noJabber(3). This is the 'normal' state. | |||
If the MAU is in jabber state the agent returns | If the MAU is in jabber state the agent returns | |||
the jabbering(4) value." | the jabbering(4) value." | |||
REFERENCE | REFERENCE | |||
"[IEEE 802.3 Mgt], 30.5.1.1.6, | "[IEEE 802.3 Mgt], 30.5.1.1.6, | |||
aJabber.jabberFlag." | aJabber.jabberFlag." | |||
::= { mauEntry 8 } | ::= { rpMauEntry 8 } | |||
mauJabberingStateEnters OBJECT-TYPE | rpMauJabberingStateEnters OBJECT-TYPE | |||
SYNTAX Counter32 | SYNTAX Counter32 | |||
MAX-ACCESS read-only | MAX-ACCESS read-only | |||
STATUS mandatory | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"A count of the number of times that | "A count of the number of times that | |||
mauJabberState for this MAU instance enters the | mauJabberState for this MAU instance enters the | |||
state jabbering(4). For MAUs of type | state jabbering(4). For MAUs of type | |||
dot3MauTypeAUI, dot3MauType100BaseT4, | dot3MauTypeAUI, dot3MauType100BaseT4, | |||
dot3MauType100BaseTX, and dot3MauType100BaseFX, | dot3MauType100BaseTX, and dot3MauType100BaseFX, | |||
this counter will always indicate zero." | this counter will always indicate zero." | |||
REFERENCE | REFERENCE | |||
"[IEEE 802.3 Mgt], 30.5.1.1.6, | "[IEEE 802.3 Mgt], 30.5.1.1.6, | |||
aJabber.jabberCounter." | aJabber.jabberCounter." | |||
::= { mauEntry 9 } | ::= { rpMauEntry 9 } | |||
mauFalseCarriers OBJECT-TYPE | rpMauFalseCarriers OBJECT-TYPE | |||
SYNTAX Counter32 | SYNTAX Counter32 | |||
MAX-ACCESS read-only | MAX-ACCESS read-only | |||
STATUS mandatory | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"A count of the number of false carrier events | "A count of the number of false carrier events | |||
during IDLE in 100BASE-X links. This counter does | during IDLE in 100BASE-X links. This counter does | |||
not increment at the symbol rate. It can | not increment at the symbol rate. It can | |||
increment after a valid carrier completion at a | increment after a valid carrier completion at a | |||
maximum rate of once per 100 ms until the next | maximum rate of once per 100 ms until the next | |||
carrier event. | carrier event. | |||
This counter increments only for MAUs of type | This counter increments only for MAUs of type | |||
dot3MauType100BaseT4, dot3MauType100BaseTX, and | dot3MauType100BaseT4, dot3MauType100BaseTX, and | |||
dot3MauType100BaseFX. For all other MAU types, | dot3MauType100BaseFX. For all other MAU types, | |||
this counter will always indicate zero. | this counter will always indicate zero. | |||
The approximate minimum time for rollover of this | The approximate minimum time for rollover of this | |||
counter is 7.4 hours." | counter is 7.4 hours." | |||
REFERENCE | REFERENCE | |||
"[IEEE 802.3 Mgt], 30.5.1.1.10, aFalseCarriers." | "[IEEE 802.3 Mgt], 30.5.1.1.10, aFalseCarriers." | |||
::= { mauEntry 10 } | ::= { rpMauEntry 10 } | |||
-- | ||||
-- Jack Tables | ||||
-- | ||||
-- The jack object types defined below are intended to provide | ||||
-- management information for external jacks on a system. They | ||||
-- describe the jack from the outside looking in, such that for | ||||
-- a particular connector at a particular location on the outside | ||||
-- of the box, these objects can be used to determine to which | ||||
-- internal entity it is mapped, and to which internal entity it | ||||
-- could potentially be mapped as a result of the operation of the | ||||
-- auto-negotiation function defined by the IEEE 802.3 management | ||||
-- standard. | ||||
-- | ||||
-- The IEEE 802.3 auto-negotiation function is defined such that | ||||
-- it can be expanded to work for technologies other than those | ||||
-- defined by 802.3. In addition, although the purpose of | ||||
-- auto-negotiation is to negotiate the use of a particular | ||||
-- (signalling?) technology across a particular link between | ||||
-- network components, the outcome of that technology choice | ||||
-- can have run-time implications for systems containing a mix | ||||
-- of networking features. | ||||
-- | ||||
-- For instance, a system containing both 10 and 100 | ||||
-- Mb/s repeater capability on a particular link will, | ||||
-- of necessity, require the link to potentially connect to | ||||
-- two different repeaters: one 10 Mb/s repeater and one 100 | ||||
-- Mb/s repeater (there being no such device as a 10/100 | ||||
-- repeater). Only one of these connections will be active | ||||
-- at run time, depending on the outcome of the auto-negotiation | ||||
-- on that link, and therefore the auto-negotiation itself can | ||||
-- have the effect of determining the actual connectivity of | ||||
-- the link. | ||||
-- | ||||
-- These tables are intended to apply firstly to jacks connected to | ||||
-- IEEE 802.3 repeaters, and additionally to any other management | ||||
-- domain for which they may be useful. Certain object types here | ||||
-- have been cross-referenced into the 802.3 repeater MIB (which | ||||
-- draft is currently under discussion by this working group) and | ||||
-- to the interfaces table of MIB-II. For example, there is | ||||
-- some overlap between "jackInternalConnection" and "rptrInfoId" | ||||
-- from the repeater MIB draft. Please refer to the object | ||||
-- definitions below for specific details. | ||||
-- The jackTable applies to systems which have one or | -- The rpJackTable applies to MAUs attached to repeaters | |||
-- more external jacks (connectors). | -- which have one or more external jacks (connectors). | |||
jackTable OBJECT-TYPE | rpJackTable OBJECT-TYPE | |||
SYNTAX SEQUENCE OF JackEntry | SYNTAX SEQUENCE OF RpJackEntry | |||
MAX-ACCESS not-accessible | MAX-ACCESS not-accessible | |||
STATUS mandatory | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"Configuration objects for the external jacks on | "Information about the external jacks attached to | |||
the system." | MAUs attached to the ports of a repeater." | |||
::= { jackBasicGroup 1 } | ::= { dot3RpMauBasicGroup 2 } | |||
jackEntry OBJECT-TYPE | rpJackEntry OBJECT-TYPE | |||
SYNTAX JackEntry | SYNTAX RpJackEntry | |||
MAX-ACCESS not-accessible | MAX-ACCESS not-accessible | |||
STATUS mandatory | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"An entry in the table, containing configuration | "An entry in the table, containing information | |||
information for a a particular jack." | about a particular jack." | |||
INDEX { jackGroupIndex, | INDEX { rpJackGroupIndex, | |||
jackjackIndex } | rpJackPortIndex, | |||
::= { jackTable 1 } | rpJackMauIndex, | |||
rpJackIndex } | ||||
::= { rpJackTable 1 } | ||||
JackEntry ::= | RpJackEntry ::= | |||
SEQUENCE { | SEQUENCE { | |||
jackGroupIndex | rpJackGroupIndex | |||
Integer32, | Integer32, | |||
jackIndex | rpJackPortIndex | |||
Integer32, | Integer32, | |||
jackType | rpJackMauIndex | |||
INTEGER, | Integer32, | |||
jackInternalConnection | rpJackIndex | |||
OBJECT IDENTIFIER, | Integer32, | |||
jackConnectionLastChange | rpJackType | |||
TimeStamp | INTEGER | |||
} | } | |||
jackGroupIndex OBJECT-TYPE | rpJackGroupIndex OBJECT-TYPE | |||
SYNTAX Integer32 (1..2147483647) | SYNTAX Integer32 (1..2147483647) | |||
MAX-ACCESS read-only | MAX-ACCESS read-only | |||
STATUS mandatory | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"This variable uniquely identifies the group | "This variable uniquely identifies the group | |||
within the system containing the jack described by | within containing the port attached to the MAU to | |||
this entry. | which the jack described by this entry is | |||
connected. | ||||
Note: In practice, a group will generally be a | Note: In practice, a group will generally be a | |||
field-replaceable unit (i.e., module, card, or | field-replaceable unit (i.e., module, card, or | |||
board) that can fit in the physical system | board) that can fit in the physical system | |||
enclosure, and the group number will correspond to | enclosure, and the group number will correspond to | |||
a number marked on the physical enclosure. | a number marked on the physical enclosure. | |||
For jacks attached to repeaters, the group denoted | The group denoted by a particular value of this | |||
by a particular value of this object is the same | object is the same as the group denoted by the | |||
as the group denoted by the same value of | same value of rpMauGroupIndex." | |||
rptrGroupIndex." | ::= { rpJackEntry 1 } | |||
::= { jackEntry 1 } | ||||
jackIndex OBJECT-TYPE | rpJackPortIndex OBJECT-TYPE | |||
SYNTAX Integer32 (1..2147483647) | SYNTAX Integer32 (1..2147483647) | |||
MAX-ACCESS read-only | MAX-ACCESS read-only | |||
STATUS mandatory | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"This variable uniquely identifies the jack | "This variable uniquely identifies the repeater | |||
described by this entry among within other jacks | port within group rpJackGroupIndex attached to the | |||
within the group denoted by jackGroupIndex. | MAU to which the jack described by this entry is | |||
connected." | ||||
REFERENCE | ||||
"" | ||||
::= { rpJackEntry 2 } | ||||
Note that if the jack is connected to a repeater, | rpJackMauIndex OBJECT-TYPE | |||
the value of this object is the same as the value | SYNTAX Integer32 (1..2147483647) | |||
of rptrPortIndex for the associated port in the | MAX-ACCESS read-only | |||
same group (i.e. jackIndex == rptrPortIndex, and | STATUS current | |||
jackGroupIndex == rptrPortGroupIndex). | DESCRIPTION | |||
"This variable uniquely identifies the MAU | ||||
connected to port rpJackPortIndex within group | ||||
rpJackGroupIndex to which the jack that is | ||||
described by this entry is connected." | ||||
REFERENCE | ||||
"[IEEE 802.3 Mgt], 30.5.1.1.1, aMAUID." | ||||
::= { rpJackEntry 3 } | ||||
Jacks may also be connected to other entities, | rpJackIndex OBJECT-TYPE | |||
including logical interfaces within the system, in | SYNTAX Integer32 (1..2147483647) | |||
which case the numbering of the entity may not | MAX-ACCESS read-only | |||
match the numbering of the jack. In all cases, | STATUS current | |||
the next-level entity to which this jack is | DESCRIPTION | |||
connected is specified by the | "This variable uniquely identifies the jack | |||
jackInternalConnection object for this entry." | described by this entry among within other jacks | |||
::= { jackEntry 2 } | attached to the MAU denoted by rpJackMauIndex." | |||
::= { rpJackEntry 4 } | ||||
jackType OBJECT-TYPE | rpJackType OBJECT-TYPE | |||
SYNTAX INTEGER { | SYNTAX INTEGER { | |||
other(1), | other(1), | |||
rj45(2) | rj45(2) | |||
} | } | |||
MAX-ACCESS read-only | MAX-ACCESS read-only | |||
STATUS mandatory | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"The jack connector type, as it appears on the | "The jack connector type, as it appears on the | |||
outside of the system." | outside of the system." | |||
::= { jackEntry 3 } | ::= { rpJackEntry 5 } | |||
jackInternalConnection OBJECT-TYPE | -- | |||
-- The Basic Interface MAU Table | ||||
-- | ||||
ifMauTable OBJECT-TYPE | ||||
SYNTAX SEQUENCE OF IfMauEntry | ||||
MAX-ACCESS not-accessible | ||||
STATUS current | ||||
DESCRIPTION | ||||
"Table of descriptive and status information about | ||||
MAU(s) attached to an interface." | ||||
::= { dot3IfMauBasicGroup 1 } | ||||
ifMauEntry OBJECT-TYPE | ||||
SYNTAX IfMauEntry | ||||
MAX-ACCESS not-accessible | ||||
STATUS current | ||||
DESCRIPTION | ||||
"An entry in the table, containing information | ||||
about a single MAU." | ||||
INDEX { ifMauIfIndex, ifMauIndex } | ||||
::= { ifMauTable 1 } | ||||
IfMauEntry ::= | ||||
SEQUENCE { | ||||
ifMauIfIndex | ||||
Integer32, | ||||
ifMauIndex | ||||
Integer32, | ||||
ifMauType | ||||
OBJECT IDENTIFIER, | ||||
ifMauStatus | ||||
INTEGER, | ||||
ifMauMediaAvail | ||||
INTEGER, | ||||
ifMauMediaAvailStateExits | ||||
Counter32, | ||||
ifMauJabberState | ||||
INTEGER, | ||||
ifMauJabberingStateEnters | ||||
Counter32, | ||||
ifMauFalseCarriers | ||||
Counter32, | ||||
ifMauTypeList | ||||
Integer32 | ||||
} | ||||
ifMauIfIndex OBJECT-TYPE | ||||
SYNTAX Integer32 | ||||
MAX-ACCESS read-only | ||||
STATUS current | ||||
DESCRIPTION | ||||
"This variable uniquely identifies the interface | ||||
to which the MAU described by this entry is | ||||
connected." | ||||
REFERENCE | ||||
"RFC 1213, ifIndex" | ||||
::= { ifMauEntry 1 } | ||||
ifMauIndex OBJECT-TYPE | ||||
SYNTAX Integer32 (1..2147483647) | ||||
MAX-ACCESS read-only | ||||
STATUS current | ||||
DESCRIPTION | ||||
"This variable uniquely identifies the MAU | ||||
connected to interface ifMauIfIndex that is | ||||
described by this entry." | ||||
REFERENCE | ||||
"[IEEE 802.3 Mgt], 30.5.1.1.1, aMAUID." | ||||
::= { ifMauEntry 2 } | ||||
ifMauType OBJECT-TYPE | ||||
SYNTAX OBJECT IDENTIFIER | SYNTAX OBJECT IDENTIFIER | |||
MAX-ACCESS read-only | MAX-ACCESS read-only | |||
STATUS mandatory | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"This variable identifies the instance of an | "This object identifies the 10 or 100 Mb/s | |||
internal entity to which the jack is connected. | baseband MAU type. An initial set of MAU types | |||
For a jack which can be administratively | are defined above. The assignment of OBJECT | |||
configured, or a jack on which auto-negotiation is | IDENTIFIERs to new types of MAUs is managed by the | |||
supported, the value of this object may change | IANA. If the MAU type is unknown, the object | |||
between system resets. | identifier | |||
If the jack is connected to a repeater, the value | unknownMauType OBJECT IDENTIFIER ::= { 0 0 } | |||
of this object will be rptrInfoId.r, where r | ||||
equals the value of rptrPortRptrId for the port | ||||
with which this jack is associated (see also the | ||||
above description of jackIndex). | ||||
If the jack is connected to an interface, the | is returned. Note that unknownMauType is a | |||
value of this object will be ifIndex.i, where i is | syntactically valid object identifier, and any | |||
the instance of the interface. | conformant implementation of ASN.1 and the BER | |||
must be able to generate and recognize this | ||||
value." | ||||
REFERENCE | ||||
"[IEEE 802.3 Mgt], 30.5.1.1.2, aMAUType." | ||||
::= { ifMauEntry 3 } | ||||
For other types of internal entities, the value of | ifMauStatus OBJECT-TYPE | |||
this object must be an instance identifier which | SYNTAX INTEGER { | |||
uniquely identifies the entity type and the | other(1), | |||
instance of that type within the managed system." | unknown(2), | |||
::= { jackEntry 4 } | operational(3), | |||
standby(4), | ||||
shutdown(5), | ||||
reset(6) | ||||
} | ||||
MAX-ACCESS read-write | ||||
STATUS current | ||||
DESCRIPTION | ||||
"The current state of the MAU. This object may be | ||||
implemented as a read-only object by those agents | ||||
and MAUs that do not implement software control of | ||||
the MAU state. Some agents may not support | ||||
setting the value of this object to some of the | ||||
enumerated values. | ||||
jackConnectionLastChange OBJECT-TYPE | The value other(1) is returned if the MAU is in a | |||
SYNTAX TimeStamp | state other than one of the states 2 through 6. | |||
The value unknown(2) is returned when the MAU's | ||||
true state is unknown; for example, when it is | ||||
being initialized. | ||||
A MAU in the operational(3) state is fully | ||||
functional, operates, and passes signals to its | ||||
attached DTE or repeater port in accordance to its | ||||
specification. | ||||
A MAU in standby(4) state forces DI and CI to idle | ||||
and the media transmitter to idle or fault, if | ||||
supported. Standby(4) mode only applies to link | ||||
type MAUs. The state of ifMauMediaAvail is | ||||
unaffected. | ||||
A MAU in shutdown(5) state assumes the same | ||||
condition on DI, CI, and the media transmitter as | ||||
though it were powered down or not connected. The | ||||
MAU may return other(1) value for the | ||||
ifMauJabberState and ifMauMediaAvail objects when | ||||
it is in this state. For an AUI, this state will | ||||
remove power from the AUI. | ||||
Setting this variable to the value reset(6) resets | ||||
the MAU in the same manner as a power-off, power- | ||||
on cycle of at least one-half second would. The | ||||
agent is not required to return the value reset | ||||
(6). | ||||
Setting this variable to the value operational(3), | ||||
standby(4), or shutdown(5) causes the MAU to | ||||
assume the respective state except that setting a | ||||
mixing-type MAU or an AUI to standby(4) will cause | ||||
the MAU to enter the shutdown state." | ||||
REFERENCE | ||||
"[IEEE 802.3 Mgt], 30.5.1.1.7, aMAUAdminState, | ||||
30.5.1.2.2, acMAUAdminControl, and 30.5.1.2.1, | ||||
acRESETMAU." | ||||
::= { ifMauEntry 4 } | ||||
ifMauMediaAvail OBJECT-TYPE | ||||
SYNTAX INTEGER { | ||||
other(1), | ||||
unknown(2), | ||||
available(3), | ||||
notAvailable(4), | ||||
remoteFault(5), | ||||
invalidSignal(6), | ||||
remoteJabber(7), | ||||
remoteLinkLoss(8), | ||||
remoteTest(9) | ||||
} | ||||
MAX-ACCESS read-only | MAX-ACCESS read-only | |||
STATUS mandatory | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"The value of sysUpTime when any of the following | "If the MAU is a link or fiber type (FOIRL, | |||
conditions occurred: | 10BASE-T, 10BASE-F) then this is equivalent to the | |||
1) the agent cold- or warm-started; | link test fail state/low light function. For an | |||
2) this instance of jack was created | AUI or a coax (including broadband) MAU this | |||
(such as when a device or module was | indicates whether or not loopback is detected on | |||
added to the system); | the DI circuit. The value of this attribute | |||
3) a change occurred in the value of | persists between packets for MAU types AUI, | |||
jackInternalConnection for this entry." | 10BASE5, 10BASE2, 10BROAD36, and 10BASE-FP. | |||
::= { jackEntry 5 } | ||||
-- The jackAutoNegTable applies to systems in which | The value other(1) is returned if the mediaAvail | |||
-- auto-negotiation is supported on one or more jacks. | state is not one of 2 through 6. | |||
jackAutoNegTable OBJECT-TYPE | The value unknown(2) is returned when the MAU's | |||
SYNTAX SEQUENCE OF JackAutoNegEntry | true state is unknown; for example, when it is | |||
being initialized. At power-up or following a | ||||
reset, the value of this attribute will be unknown | ||||
for AUI, coax, and 10BASE-FP MAUs. For these MAUs | ||||
loopback will be tested on each transmission | ||||
during which no collision is detected. If DI is | ||||
receiving input when DO returns to IDL after a | ||||
transmission and there has been no collision | ||||
during the transmission then loopback will be | ||||
detected. The value of this attribute will only | ||||
change during non-collided transmissions for AUI, | ||||
coax, and 10BASE-FP MAUs. | ||||
For 100BASE-T4, 100BASE-TX and 100BASE-FX the | ||||
enumerations match the states within the | ||||
respective link integrity state diagrams, fig 23- | ||||
12 and 24-15 of sections 23 and 24 of [2]. Any | ||||
MAU which implements management of Auto- | ||||
Negotiation will map remote fault indication to | ||||
remote fault. | ||||
The value available(3) indicates that the link, | ||||
light, or loopback is normal. The value | ||||
notAvailable(4) indicates link loss, low light, or | ||||
no loopback. | ||||
The value remoteFault(5) indicates that a fault | ||||
has been detected at the remote end of the link. | ||||
This value applies to 10BASE-FB, 100BASE-T4 Far | ||||
End Fault Indication and non-specified remote | ||||
faults from a system running Auto-Negotiation. | ||||
The values remoteJabber(7), remoteLinkLoss(8), and | ||||
remoteTest(9) should be used instead of | ||||
remoteFault(5) where the reason for remote fault | ||||
is identified in the remote signaling protocol. | ||||
The value invalidSignal(6) indicates that an | ||||
invalid signal has been received from the other | ||||
end of the link. InvalidSignal(6) applies only to | ||||
MAUs of type 10BASE-FB. | ||||
Where an IEEE Std 802.3u-1995 clause 22 MII is | ||||
present, a logic one in the remote fault bit | ||||
(reference section 22.2.4.2.8 of that document) | ||||
maps to the value remoteFault(5), and a logic zero | ||||
in the link status bit (reference section | ||||
22.2.4.2.10 of that document) maps to the value | ||||
notAvailable(4). The value notAvailable(4) takes | ||||
precedence over the value remoteFault(5)." | ||||
REFERENCE | ||||
"[IEEE 802.3 Mgt], 30.5.1.1.4, aMediaAvailable." | ||||
::= { ifMauEntry 5 } | ||||
ifMauMediaAvailStateExits OBJECT-TYPE | ||||
SYNTAX Counter32 | ||||
MAX-ACCESS read-only | ||||
STATUS current | ||||
DESCRIPTION | ||||
"A count of the number of times that | ||||
ifMauMediaAvail for this MAU instance leaves the | ||||
state available(3)." | ||||
REFERENCE | ||||
"[IEEE 802.3 Mgt], 30.5.1.1.5, aLoseMediaCounter." | ||||
::= { ifMauEntry 6 } | ||||
ifMauJabberState OBJECT-TYPE | ||||
SYNTAX INTEGER { | ||||
other(1), | ||||
unknown(2), | ||||
noJabber(3), | ||||
jabbering(4) | ||||
} | ||||
MAX-ACCESS read-only | ||||
STATUS current | ||||
DESCRIPTION | ||||
"The value other(1) is returned if the jabber | ||||
state is not 2, 3, or 4. The agent must always | ||||
return other(1) for MAU type dot3MauTypeAUI. | ||||
The value unknown(2) is returned when the MAU's | ||||
true state is unknown; for example, when it is | ||||
being initialized. | ||||
If the MAU is not jabbering the agent returns | ||||
noJabber(3). This is the 'normal' state. | ||||
If the MAU is in jabber state the agent returns | ||||
the jabbering(4) value." | ||||
REFERENCE | ||||
"[IEEE 802.3 Mgt], 30.5.1.1.6, | ||||
aJabber.jabberFlag." | ||||
::= { ifMauEntry 7 } | ||||
ifMauJabberingStateEnters OBJECT-TYPE | ||||
SYNTAX Counter32 | ||||
MAX-ACCESS read-only | ||||
STATUS current | ||||
DESCRIPTION | ||||
"A count of the number of times that | ||||
mauJabberState for this MAU instance enters the | ||||
state jabbering(4). For MAUs of type | ||||
dot3MauTypeAUI, dot3MauType100BaseT4, | ||||
dot3MauType100BaseTX, and dot3MauType100BaseFX, | ||||
this counter will always indicate zero." | ||||
REFERENCE | ||||
"[IEEE 802.3 Mgt], 30.5.1.1.6, | ||||
aJabber.jabberCounter." | ||||
::= { ifMauEntry 8 } | ||||
ifMauFalseCarriers OBJECT-TYPE | ||||
SYNTAX Counter32 | ||||
MAX-ACCESS read-only | ||||
STATUS current | ||||
DESCRIPTION | ||||
"A count of the number of false carrier events | ||||
during IDLE in 100BASE-X links. This counter does | ||||
not increment at the symbol rate. It can | ||||
increment after a valid carrier completion at a | ||||
maximum rate of once per 100 ms until the next | ||||
carrier event. | ||||
This counter increments only for MAUs of type | ||||
dot3MauType100BaseT4, dot3MauType100BaseTX, and | ||||
dot3MauType100BaseFX. For all other MAU types, | ||||
this counter will always indicate zero. | ||||
The approximate minimum time for rollover of this | ||||
counter is 7.4 hours." | ||||
REFERENCE | ||||
"[IEEE 802.3 Mgt], 30.5.1.1.10, aFalseCarriers." | ||||
::= { ifMauEntry 9 } | ||||
ifMauTypeList OBJECT-TYPE | ||||
SYNTAX Integer32 | ||||
MAX-ACCESS read-only | ||||
STATUS current | ||||
DESCRIPTION | ||||
"A value that uniquely identifies the set of | ||||
possible IEEE 802.3 types that the MAU could be. | ||||
The value is a sum which initially takes the value | ||||
zero. Then, for each type capability of this MAU, | ||||
2 raised to the power noted below is added to the | ||||
sum. For example, a MAU which has the capability | ||||
to be only 10BASE-T would have a value of 512 | ||||
(2**9). In contrast, a MAU which supports both | ||||
10Base-T and 100BASE-TX would have a value of 1536 | ||||
((2**9) + (2**10)). | ||||
The powers of 2 assigned to the capabilities are | ||||
these: | ||||
Power Capability | ||||
1 AUI | ||||
2 10BASE-5 | ||||
3 FOIRL | ||||
4 10BASE-2 | ||||
5 10BASE-T | ||||
6 10BASE-FP | ||||
7 10BASE-FB | ||||
8 10BASE-FL | ||||
9 10BROAD36 | ||||
10 100BASE-T4 | ||||
11 100BASE-TX | ||||
12 100BASE-FX | ||||
If auto-negotiation is present on the jack to | ||||
which this MAU is attached, this attribute will | ||||
map to the ifMauAutoNegCapability." | ||||
::= { ifMauEntry 10 } | ||||
-- The ifJackTable applies to MAUs attached to interfaces | ||||
-- which have one or more external jacks (connectors). | ||||
ifJackTable OBJECT-TYPE | ||||
SYNTAX SEQUENCE OF IfJackEntry | ||||
MAX-ACCESS not-accessible | MAX-ACCESS not-accessible | |||
STATUS mandatory | STATUS current | |||
DESCRIPTION | ||||
"Information about the external jacks attached to | ||||
MAUs attached to an interface." | ||||
::= { dot3IfMauBasicGroup 2 } | ||||
ifJackEntry OBJECT-TYPE | ||||
SYNTAX IfJackEntry | ||||
MAX-ACCESS not-accessible | ||||
STATUS current | ||||
DESCRIPTION | ||||
"An entry in the table, containing information | ||||
about a particular jack." | ||||
INDEX { ifJackIfIndex, | ||||
ifJackMauIndex, | ||||
ifJackIndex } | ||||
::= { ifJackTable 1 } | ||||
IfJackEntry ::= | ||||
SEQUENCE { | ||||
ifJackIfIndex | ||||
Integer32, | ||||
ifJackMauIndex | ||||
Integer32, | ||||
ifJackIndex | ||||
Integer32, | ||||
ifJackType | ||||
INTEGER | ||||
} | ||||
ifJackIfIndex OBJECT-TYPE | ||||
SYNTAX Integer32 | ||||
MAX-ACCESS read-only | ||||
STATUS current | ||||
DESCRIPTION | ||||
"This variable uniquely identifies the interface | ||||
attached to the MAU to which the jack described by | ||||
this entry is connected. | ||||
The interface denoted by a particular value of | ||||
this object is the same as the group denoted by | ||||
the same value of ifMauIfIndex." | ||||
::= { ifJackEntry 1 } | ||||
ifJackMauIndex OBJECT-TYPE | ||||
SYNTAX Integer32 (1..2147483647) | ||||
MAX-ACCESS read-only | ||||
STATUS current | ||||
DESCRIPTION | ||||
"This variable uniquely identifies the MAU | ||||
connected to port ifJackIfIndex to which the jack | ||||
that is described by this entry is connected." | ||||
REFERENCE | ||||
"[IEEE 802.3 Mgt], 30.5.1.1.1, aMAUID." | ||||
::= { ifJackEntry 2 } | ||||
ifJackIndex OBJECT-TYPE | ||||
SYNTAX Integer32 (1..2147483647) | ||||
MAX-ACCESS read-only | ||||
STATUS current | ||||
DESCRIPTION | ||||
"This variable uniquely identifies the jack | ||||
described by this entry among within other jacks | ||||
attached to the MAU denoted by ifJackMauIndex." | ||||
::= { ifJackEntry 3 } | ||||
ifJackType OBJECT-TYPE | ||||
SYNTAX INTEGER { | ||||
other(1), | ||||
rj45(2) | ||||
} | ||||
MAX-ACCESS read-only | ||||
STATUS current | ||||
DESCRIPTION | ||||
"The jack connector type, as it appears on the | ||||
outside of the system." | ||||
::= { ifJackEntry 4 } | ||||
-- The ifMauAutoNegTable applies to systems in which | ||||
-- auto-negotiation is supported on one or more MAUs | ||||
-- attached to interfaces. | ||||
ifMauAutoNegTable OBJECT-TYPE | ||||
SYNTAX SEQUENCE OF IfMauAutoNegEntry | ||||
MAX-ACCESS not-accessible | ||||
STATUS current | ||||
DESCRIPTION | DESCRIPTION | |||
"Configuration and status objects for the auto- | "Configuration and status objects for the auto- | |||
negotiation function of external jacks on the | negotiation function of MAUs attached to | |||
system." | interfaces." | |||
::= { jackAutoNegGroup 1 } | ::= { dot3IfMauAutoNegGroup 1 } | |||
jackAutoNegEntry OBJECT-TYPE | ifMauAutoNegEntry OBJECT-TYPE | |||
SYNTAX JackAutoNegEntry | SYNTAX IfMauAutoNegEntry | |||
MAX-ACCESS not-accessible | MAX-ACCESS not-accessible | |||
STATUS mandatory | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"An entry in the table, containing configuration | "An entry in the table, containing configuration | |||
and status information for the auto-negotiation | and status information for the auto-negotiation | |||
function of a particular jack." | function of a particular MAU." | |||
AUGMENTS { jackEntry } | AUGMENTS { ifMauEntry } | |||
::= { jackAutoNegTable 1 } | ::= { ifMauAutoNegTable 1 } | |||
JackAutoNegEntry ::= | IfMauAutoNegEntry ::= | |||
SEQUENCE { | SEQUENCE { | |||
jackAutoNegAdminStatus | ifMauAutoNegAdminStatus | |||
INTEGER, | INTEGER, | |||
jackAutoNegRemoteSignaling | ifMauAutoNegRemoteSignaling | |||
INTEGER, | INTEGER, | |||
jackAutoNegPotentialConnectSet | ifMauAutoNegConfig | |||
Integer32, | ||||
jackAutoNegConfig | ||||
INTEGER, | INTEGER, | |||
jackAutoNegCapability | ifMauAutoNegCapability | |||
Integer32, | Integer32, | |||
jackAutoNegCapAdvertised | ifMauAutoNegCapAdvertised | |||
Integer32, | Integer32, | |||
jackAutoNegCapReceived | ifMauAutoNegCapReceived | |||
Integer32, | Integer32, | |||
jackAutoNegTechnologyInUse | ifMauAutoNegTechnologyInUse | |||
INTEGER, | INTEGER, | |||
jackAutoNegRestart | ifMauAutoNegRestart | |||
INTEGER | INTEGER | |||
} | } | |||
ifMauAutoNegAdminStatus OBJECT-TYPE | ||||
jackAutoNegAdminStatus OBJECT-TYPE | ||||
SYNTAX INTEGER { | SYNTAX INTEGER { | |||
enabled(1), | enabled(1), | |||
disabled(2) | disabled(2) | |||
} | } | |||
MAX-ACCESS read-write | MAX-ACCESS read-write | |||
STATUS mandatory | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"Setting this object to enabled(1) will cause the | "Setting this object to enabled(1) will cause the | |||
interface which has the auto-negotiation signaling | interface which has the auto-negotiation signaling | |||
ability to be enabled. If disabled then the | ability to be enabled. If disabled then the | |||
interface will act as it would if it had no auto- | interface will act as it would if it had no auto- | |||
negotiation signaling. | negotiation signaling. | |||
Under these conditions, a jack connected to an | Under these conditions, an IEEE 802.3 MAU will | |||
IEEE 802.3 MAU will immediately be forced to the | immediately be forced to the states indicated by a | |||
states indicated by a write to the object | write to the object rpMauType or ifMauType. | |||
rpMauType or ifMauType. [Ed.--This doesn't allow | [Ed.--This doesn't allow for half vs. full | |||
for half vs. full duplex.]" | duplex.]" | |||
REFERENCE | REFERENCE | |||
"[IEEE 802.3 Mgt], 30.6.1.1.2, aAutoNegAdminState | "[IEEE 802.3 Mgt], 30.6.1.1.2, aAutoNegAdminState | |||
and 30.6.1.2.2, acAutoNegAdminControl." | and 30.6.1.2.2, acAutoNegAdminControl." | |||
::= { jackAutoNegEntry 1 } | ::= { ifMauAutoNegEntry 1 } | |||
jackAutoNegRemoteSignaling OBJECT-TYPE | ifMauAutoNegRemoteSignaling OBJECT-TYPE | |||
SYNTAX INTEGER { | SYNTAX INTEGER { | |||
detected(1), | detected(1), | |||
notdetected(2) | notdetected(2) | |||
} | } | |||
MAX-ACCESS read-only | MAX-ACCESS read-only | |||
STATUS mandatory | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"A value indicating whether the remote end of the | "A value indicating whether the remote end of the | |||
link is using auto-negotiation signaling. It takes | link is using auto-negotiation signaling. It takes | |||
the value detected(1) if and only if, during the | the value detected(1) if and only if, during the | |||
previous link negotiation, FLP Bursts were | previous link negotiation, FLP Bursts were | |||
received." | received." | |||
REFERENCE | REFERENCE | |||
"[IEEE 802.3 Mgt], 30.6.1.1.3, | "[IEEE 802.3 Mgt], 30.6.1.1.3, | |||
aAutoNegRemoteSignaling." | aAutoNegRemoteSignaling." | |||
::= { jackAutoNegEntry 2 } | ::= { ifMauAutoNegEntry 2 } | |||
jackAutoNegPotentialConnectSet OBJECT-TYPE | ||||
SYNTAX Integer32 | ||||
MAX-ACCESS read-only | ||||
STATUS mandatory | ||||
DESCRIPTION | ||||
"This variable identifies the set of internal | ||||
entities to which this jack can potentially | ||||
connect using as a result of auto-negotiation. | ||||
The set of potential connections can include, at | ||||
most, one entity supporting each of the | ||||
technologies for which this jack has auto- | ||||
negotiation capability. For example, if the | ||||
jackAutoNegCapability for this entry includes | ||||
10Base-T, then one and only one 10Base-T entity | ||||
may be included in the jack's potential connection | ||||
set. | ||||
The members of the set are defined in the | ||||
jackAutoNegConnectSetTable; the value of this | ||||
object is the first index | ||||
(jackAutoNegConnectSetIndex) into that table. | ||||
Each entry in that table whose first index has the | ||||
same value as this object is a member of the set | ||||
of potential connections for this jack. | ||||
Note that this object is read-only, and therefore | ||||
does not allow for administrative control of the | ||||
jack connection: the method of such control, if | ||||
available, is implementation-specific. [?? allow | ||||
read-write implementations of this ??] | ||||
(See also the definitions for the | ||||
jackAutoNegConnectSetTable.)" | ||||
::= { jackAutoNegEntry 3 } | ||||
jackAutoNegConfig OBJECT-TYPE | ifMauAutoNegConfig OBJECT-TYPE | |||
SYNTAX INTEGER { | SYNTAX INTEGER { | |||
other(1), | other(1), | |||
configuring(2), | configuring(2), | |||
complete(3), | complete(3), | |||
disabled(4), | disabled(4), | |||
parallelDetectFail(5) | parallelDetectFail(5) | |||
} | } | |||
MAX-ACCESS read-only | MAX-ACCESS read-only | |||
STATUS mandatory | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"A value indicating the current status of the | "A value indicating the current status of the | |||
auto-negotiation process. The enumeration | auto-negotiation process. The enumeration | |||
parallelDetectFail(5) maps to a failure in | parallelDetectFail(5) maps to a failure in | |||
parallel detection as defined in 28.2.3.1 of [IEEE | parallel detection as defined in 28.2.3.1 of [IEEE | |||
802.3 Std]." | 802.3 Std]." | |||
REFERENCE | REFERENCE | |||
"[IEEE 802.3 Mgt], 30.6.1.1.4, | "[IEEE 802.3 Mgt], 30.6.1.1.4, | |||
aAutoNegAutoConfig." | aAutoNegAutoConfig." | |||
::= { jackAutoNegEntry 4 } | ::= { ifMauAutoNegEntry 4 } | |||
jackAutoNegCapability OBJECT-TYPE | ifMauAutoNegCapability OBJECT-TYPE | |||
SYNTAX Integer32 | SYNTAX Integer32 | |||
MAX-ACCESS read-only | MAX-ACCESS read-only | |||
STATUS mandatory | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"A value that uniquely identifies the set of | "A value that uniquely identifies the set of | |||
capabilities of the local auto-negotiation entity. | capabilities of the local auto-negotiation entity. | |||
The value is a sum which initially takes the value | The value is a sum which initially takes the value | |||
zero. Then, for each capability of this | zero. Then, for each capability of this | |||
interface, 2 raised to the power noted below is | interface, 2 raised to the power noted below is | |||
added to the sum. For example, an interface which | added to the sum. For example, an interface which | |||
has the capability to support only 100Base-TX | has the capability to support only 100Base-TX | |||
would have a value of 512 (2**9). In contrast, an | would have a value of 512 (2**9). In contrast, an | |||
interface which supports both 100Base-TX and | interface which supports both 100Base-TX and | |||
skipping to change at page 23, line 31 | skipping to change at page 31, line 12 | |||
5 10BASE-FL | 5 10BASE-FL | |||
6 10BASE-FL Full Duplex | 6 10BASE-FL Full Duplex | |||
7 10BASE-FB | 7 10BASE-FB | |||
8 10BASE-FB Full Duplex | 8 10BASE-FB Full Duplex | |||
9 100BASE-TX | 9 100BASE-TX | |||
10 100BASE-TX Full Duplex | 10 100BASE-TX Full Duplex | |||
11 100BASE-FX | 11 100BASE-FX | |||
12 100BASE-FX Full Duplex | 12 100BASE-FX Full Duplex | |||
13 100BASE-T4 | 13 100BASE-T4 | |||
For jacks connected to IEEE 802.3 MAUs, the half- | For IEEE 802.3 MAUs, the half- and full-duplex | |||
and full-duplex value pairs each map to a single | value pairs each map to a single MAU type. For | |||
MAU type. For example, 10BASE-T and 10BASE-T Full | example, 10BASE-T and 10BASE-T Full Duplex each | |||
Duplex each use a MAU type of dot3MauType10BaseT. | use a MAU type of dot3MauType10BaseT. | |||
Note that interfaces that support this MIB may | Note that interfaces that support this MIB may | |||
have capabilities that extend beyond the scope of | have capabilities that extend beyond the scope of | |||
this MIB." | this MIB." | |||
REFERENCE | REFERENCE | |||
"[IEEE 802.3 Mgt], 30.6.1.1.5, | "[IEEE 802.3 Mgt], 30.6.1.1.5, | |||
aAutoNegLocalTechnologyAbility." | aAutoNegLocalTechnologyAbility." | |||
::= { jackAutoNegEntry 5 } | ::= { ifMauAutoNegEntry 5 } | |||
jackAutoNegCapAdvertised OBJECT-TYPE | ifMauAutoNegCapAdvertised OBJECT-TYPE | |||
SYNTAX Integer32 | SYNTAX Integer32 | |||
MAX-ACCESS read-write | MAX-ACCESS read-write | |||
STATUS mandatory | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"A value that uniquely identifies the set of | "A value that uniquely identifies the set of | |||
capabilities advertised by the local auto- | capabilities advertised by the local auto- | |||
negotiation entity. Refer to jackAutoNegCapability | negotiation entity. Refer to | |||
for a description of the possible values of this | ifMauAutoNegCapability for a description of the | |||
object. | possible values of this object. | |||
Capabilities in this object that are not available | Capabilities in this object that are not available | |||
in jackAutoNegCapability cannot be enabled." | in ifMauAutoNegCapability cannot be enabled." | |||
REFERENCE | REFERENCE | |||
"[IEEE 802.3 Mgt], 30.6.1.1.6, | "[IEEE 802.3 Mgt], 30.6.1.1.6, | |||
aAutoNegAdvertisedTechnologyAbility." | aAutoNegAdvertisedTechnologyAbility." | |||
::= { jackAutoNegEntry 6 } | ::= { ifMauAutoNegEntry 6 } | |||
jackAutoNegCapReceived OBJECT-TYPE | ifMauAutoNegCapReceived OBJECT-TYPE | |||
SYNTAX Integer32 | SYNTAX Integer32 | |||
MAX-ACCESS read-only | MAX-ACCESS read-only | |||
STATUS mandatory | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"A value that uniquely identifies the set of | "A value that uniquely identifies the set of | |||
capabilities received from the remote auto- | capabilities received from the remote auto- | |||
negotiation entity. Refer to jackAutoNegCapability | negotiation entity. Refer to | |||
for a description of the possible values of this | ifMauAutoNegCapability for a description of the | |||
object. | possible values of this object. | |||
Note that interfaces that support this MIB may be | Note that interfaces that support this MIB may be | |||
attached to remote auto-negotiation entities which | attached to remote auto-negotiation entities which | |||
have capabilities beyond the scope of this MIB." | have capabilities beyond the scope of this MIB." | |||
REFERENCE | REFERENCE | |||
"[IEEE 802.3 Mgt], 30.6.1.1.7, | "[IEEE 802.3 Mgt], 30.6.1.1.7, | |||
aAutoNegReceivedTechnologyAbility." | aAutoNegReceivedTechnologyAbility." | |||
::= { jackAutoNegEntry 7 } | ::= { ifMauAutoNegEntry 7 } | |||
jackAutoNegTechnologyInUse OBJECT-TYPE | ifMauAutoNegTechnologyInUse OBJECT-TYPE | |||
SYNTAX INTEGER { | SYNTAX INTEGER { | |||
other(1), | other(1), | |||
reserved(2), | reserved(2), | |||
10BASE-T(3), | t10BASET(3), | |||
10BASE-T-FD(4), | t10BASETFD(4), | |||
10BASE-FL(5), | t10BASEFL(5), | |||
10BASE-FL-FD(6), | t10BASEFLFD(6), | |||
10BASE-FB(7), | t10BASEFB(7), | |||
10BASE-FB-FD(8), | t10BASEFBFD(8), | |||
100BASE-TX(9), | t100BASETX(9), | |||
100BASE-TX-FD(10), | t100BASETXFD(10), | |||
100BASE-FX(11), | t100BASEFX(11), | |||
100BASE-FX-FD(12), | t100BASEFXFD(12), | |||
100BASE-T4(13) | t100BASET4(13) | |||
} | } | |||
MAX-ACCESS read-only | MAX-ACCESS read-only | |||
STATUS mandatory | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"The value of this object identifies the | "The value of this object identifies the | |||
technology currently in use on the link to which | technology currently in use on the link to which | |||
this jack is attached. This value may be a result | this MAU is attached. This value may be a result | |||
of auto- negotiation on the link. If auto- | of auto- negotiation on the link. If auto- | |||
negotiation is disabled and the jack is connected | negotiation is disabled and the MAU is an IEEE | |||
to an IEEE 802.3 MAU, this object will change to | 802.3 MAU, this object will change to reflect the | |||
reflect the result of a write to the object | result of a write to the object rpMauType or | |||
rpMauType or ifMauType." | ifMauType." | |||
::= { jackAutoNegEntry 8 } | ::= { ifMauAutoNegEntry 8 } | |||
jackAutoNegRestart OBJECT-TYPE | ifMauAutoNegRestart OBJECT-TYPE | |||
SYNTAX INTEGER { | SYNTAX INTEGER { | |||
restart(1), | restart(1), | |||
norestart(2) | norestart(2) | |||
} | } | |||
MAX-ACCESS read-write | MAX-ACCESS read-write | |||
STATUS mandatory | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"If the value of this object is set to restart(1) | "If the value of this object is set to restart(1) | |||
then this will force auto-negotiation to begin | then this will force auto-negotiation to begin | |||
link renegotiation. If auto-negotiation signaling | link renegotiation. If auto-negotiation signaling | |||
is disabled, a write to this object has no effect. | is disabled, a write to this object has no effect. | |||
Setting the value of this object to norestart(2) | Setting the value of this object to norestart(2) | |||
has no effect." | has no effect." | |||
REFERENCE | REFERENCE | |||
"[IEEE 802.3 Mgt], 30.6.1.2.1, | "[IEEE 802.3 Mgt], 30.6.1.2.1, | |||
acAutoNegRestartAutoConfig." | acAutoNegRestartAutoConfig." | |||
::= { jackAutoNegEntry 9 } | ::= { ifMauAutoNegEntry 9 } | |||
-- The jackAutoNegConnectSetTable applies to systems in which | ||||
-- auto-negotiation is supported on one or more jacks. | ||||
jackAutoNegConnectSetTable OBJECT-TYPE | broadMauBasicTable OBJECT-TYPE | |||
SYNTAX SEQUENCE OF JackAutoNegConnectSetEntry | SYNTAX SEQUENCE OF BroadMauBasicEntry | |||
MAX-ACCESS not-accessible | MAX-ACCESS not-accessible | |||
STATUS mandatory | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"A table describing sets of entities within the | "Table of descriptive and status information about | |||
system. Each jack in the system, for which auto- | the broadband MAUs connected to interfaces." | |||
negotiation is supported, is associated with one | ::= { dot3BroadMauBasicGroup 1 } | |||
of these sets. Each such jack may connect to any | ||||
ONE of the entities belonging to the set denoted | ||||
by its instance of jackAutoNegPotentialConnectSet, | ||||
the choice to be determined by the jack's auto- | ||||
negotiation function (if enabled). | ||||
Any single set may contain no more than one entity | ||||
representing a particular technology to which the | ||||
jack can auto-negotiate. For example, a set may | ||||
include one and only one 10BASE-T entity (e.g. a | ||||
repeater), and one and only one 100BASE-TX full | ||||
duplex entity (e.g. an interface). The list of | ||||
potential technologies is denoted by the | ||||
capabilities enumerated in the | ||||
jackAutoNegCapability OBJECT-TYPE description; it | ||||
follows that the maximum number of entities in any | ||||
set is the same as the number of different | ||||
capabilities listed in that description. | ||||
It is expected that in a system which supports | ||||
administrative configuration of connections, the | ||||
administrator will configure the connection set | ||||
for a jack so that all of the entity members are | ||||
part of a single network, in order that the auto- | ||||
negotiation function will not be able to | ||||
disconnect and reconnect a link between various | ||||
networks supported within the system. That is, | ||||
the jackAutoNegPotentialConnectSet is used to | ||||
determine the network connection (similarly to the | ||||
way a repeater port's repeater id can be used), | ||||
but WITHIN that set, the particular entity chosen | ||||
is determined via auto-negotiation during | ||||
operation." | ||||
::= { jackAutoNegGroup 2 } | ||||
jackAutoNegConnectSetEntry OBJECT-TYPE | broadMauBasicEntry OBJECT-TYPE | |||
SYNTAX JackAutoNegConnectSetEntry | SYNTAX BroadMauBasicEntry | |||
MAX-ACCESS not-accessible | MAX-ACCESS not-accessible | |||
STATUS mandatory | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"An entry defining one entity of a set of entities | "An entry in the table, containing information | |||
to which a system jack may potentially connect, | about a single broadband MAU." | |||
the determination to be made by the jack's auto- | INDEX { broadMauIfIndex, broadMauIndex } | |||
negotiation function." | ::= { broadMauBasicTable 1 } | |||
INDEX { jackAutoNegConnectSet, | ||||
jackAutoNegConnectEntityType } | ||||
::= { jackAutoNegConnectSetTable 1 } | ||||
JackAutoNegConnectSetEntry ::= | BroadMauBasicEntry ::= | |||
SEQUENCE { | SEQUENCE { | |||
jackAutoNegConnectSet | broadMauIfIndex | |||
Integer32, | Integer32, | |||
jackAutoNegConnectEntityType | broadMauIndex | |||
Integer32, | ||||
broadMauXmtRcvSplitType | ||||
INTEGER, | INTEGER, | |||
jackAutoNegConnectEntity | broadMauXmtCarrierFreq | |||
OBJECT IDENTIFIER | Integer32, | |||
broadMauTranslationFreq | ||||
Integer32 | ||||
} | } | |||
jackAutoNegConnectSet OBJECT-TYPE | broadMauIfIndex OBJECT-TYPE | |||
SYNTAX Integer32 | ||||
MAX-ACCESS read-only | ||||
STATUS current | ||||
DESCRIPTION | ||||
"This variable uniquely identifies the interface | ||||
to which the MAU described by this entry is | ||||
connected." | ||||
REFERENCE | ||||
"Reference RFC 1213, ifIndex." | ||||
::= { broadMauBasicEntry 1 } | ||||
broadMauIndex OBJECT-TYPE | ||||
SYNTAX Integer32 (1..2147483647) | SYNTAX Integer32 (1..2147483647) | |||
MAX-ACCESS read-only | MAX-ACCESS read-only | |||
STATUS mandatory | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"This variable uniquely identifies a set of entity | "This variable uniquely identifies the MAU | |||
instances among the other sets represented within | connected to interface broadMauIfIndex that is | |||
this table." | described by this entry." | |||
::= { jackAutoNegConnectSetEntry 1 } | REFERENCE | |||
"Reference IEEE 802.3 MAU Mgt, 20.2.3.2, aMAUID." | ||||
::= { broadMauBasicEntry 2 } | ||||
jackAutoNegConnectEntityType OBJECT-TYPE | broadMauXmtRcvSplitType OBJECT-TYPE | |||
SYNTAX INTEGER { | SYNTAX INTEGER { | |||
other(1), | other(1), | |||
reserved(2), | single(2), | |||
10BASE-T(3), | dual(3) | |||
10BASE-T-FD(4), | ||||
10BASE-FL(5), | ||||
10BASE-FL-FD(6), | ||||
10BASE-FB(7), | ||||
10BASE-FB-FD(8), | ||||
100BASE-TX(9), | ||||
100BASE-TX-FD(10), | ||||
100BASE-FX(11), | ||||
100BASE-FX-FD(12), | ||||
100BASE-T4(13) | ||||
} | } | |||
MAX-ACCESS read-only | MAX-ACCESS read-only | |||
STATUS mandatory | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"This variable identifies the type of internal | "This object indicates the type of frequency | |||
entity about which this entry contains | multiplexing/cabling system used to separate the | |||
information. Each set of potential connections | transmit and receive paths for the 10BROAD36 MAU. | |||
may contain no more than one entry of any | ||||
particular technology type." | ||||
::= { jackAutoNegConnectSetEntry 2 } | ||||
jackAutoNegConnectEntity OBJECT-TYPE | The value other(1) is returned if the split type | |||
SYNTAX OBJECT IDENTIFIER | is not either single or dual. | |||
The value single(2) indicates a single cable | ||||
system. The value dual(3) indicates a dual cable | ||||
system, offset normally zero." | ||||
REFERENCE | ||||
"Reference IEEE 802.3 MAU Mgt, 20.2.3.2, | ||||
aBbMAUXmitRcvSplitType." | ||||
::= { broadMauBasicEntry 3 } | ||||
broadMauXmtCarrierFreq OBJECT-TYPE | ||||
SYNTAX Integer32 | ||||
MAX-ACCESS read-only | MAX-ACCESS read-only | |||
STATUS mandatory | STATUS current | |||
DESCRIPTION | DESCRIPTION | |||
"This variable identifies the instance of an | "This variable indicates the transmit carrier | |||
internal entity to which a jack may potentially | frequency of the 10BROAD36 MAU in MHz/4; that is, | |||
connect. 802.3 repeater and interfaces are | in units of 250 kHz." | |||
examples of such entities. | REFERENCE | |||
"Reference IEEE 802.3 MAU Mgt, 20.2.3.2, | ||||
Note that if the jack is connected to a repeater, | aBroadbandFrequencies.xmitCarrierFrequency." | |||
the value of this object is the same as the value | ::= { broadMauBasicEntry 4 } | |||
of rptrPortIndex for the associated port in the | ||||
same group (i.e. jackIndex == rptrPortIndex, and | ||||
jackGroupIndex == rptrPortGroupIndex). | ||||
Jacks may also be connected to other types of | broadMauTranslationFreq OBJECT-TYPE | |||
entities, including logical interfaces within the | SYNTAX Integer32 | |||
system, in which case the numbering of the entity | MAX-ACCESS read-only | |||
may not match the numbering of the jack. In all | STATUS current | |||
cases, the next-level entity to which this jack is | DESCRIPTION | |||
connected is specified by the | "This variable indicates the translation offset | |||
jackInternalConnection object for this entry." | frequency of the 10BROAD36 MAU in MHz/4; that is, | |||
::= { jackAutoNegConnectSetEntry 3 } | in units of 250 kHz." | |||
REFERENCE | ||||
"Reference IEEE 802.3 MAU Mgt, 20.2.3.2, | ||||
aBroadbandFrequencies.translationFrequency." | ||||
::= { broadMauBasicEntry 5 } | ||||
-- Notifications for use by 802.3 MAUs | -- Notifications for use by 802.3 MAUs | |||
mauJabberTrap NOTIFICATION-TYPE | rpMauJabberTrap NOTIFICATION-TYPE | |||
OBJECTS { mauJabberState } | OBJECTS { rpMauJabberState } | |||
STATUS current | ||||
DESCRIPTION | DESCRIPTION | |||
"This trap is sent whenever a managed repeater MAU | "This trap is sent whenever a managed repeater MAU | |||
enters the jabber state. | enters the jabber state. | |||
The agent must throttle the generation of | The agent must throttle the generation of | |||
consecutive mauJabberTraps so that there is at | consecutive rpMauJabberTraps so that there is at | |||
least a five-second gap between them." | least a five-second gap between them." | |||
REFERENCE | REFERENCE | |||
"[IEEE 802.3 Mgt], 30.5.1.3.1, nJabber | "[IEEE 802.3 Mgt], 30.5.1.3.1, nJabber | |||
notification." | notification." | |||
::= { snmpDot3MauMgt 0 1 } | ::= { snmpDot3MauMgt 0 1 } | |||
ifMauJabberTrap NOTIFICATION-TYPE | ||||
OBJECTS { ifMauJabberState } | ||||
STATUS current | ||||
DESCRIPTION | ||||
"This trap is sent whenever a managed interface | ||||
MAU enters the jabber state. | ||||
The agent must throttle the generation of | ||||
consecutive ifMauJabberTraps so that there is at | ||||
least a five-second gap between them." | ||||
REFERENCE | ||||
"[IEEE 802.3 Mgt], 30.5.1.3.1, nJabber | ||||
notification." | ||||
::= { snmpDot3MauMgt 0 2 } | ||||
-- Conformance information | ||||
mauModConf | ||||
OBJECT IDENTIFIER ::= { mauMod 1 } | ||||
mauModCompls | ||||
OBJECT IDENTIFIER ::= { mauModConf 1 } | ||||
mauModObjGrps | ||||
OBJECT IDENTIFIER ::= { mauModConf 2 } | ||||
mauModNotGrps | ||||
OBJECT IDENTIFIER ::= { mauModConf 3 } | ||||
-- Object groups | ||||
mauRpGrpBasic OBJECT-GROUP | ||||
OBJECTS { rpMauGroupIndex, | ||||
rpMauPortIndex, | ||||
rpMauIndex, | ||||
rpMauType, | ||||
rpMauStatus, | ||||
rpMauMediaAvail, | ||||
rpMauMediaAvailStateExits, | ||||
rpMauJabberState, | ||||
rpMauJabberingStateEnters } | ||||
STATUS current | ||||
DESCRIPTION | ||||
"Basic conformance group for MAUs attached to | ||||
repeater ports. This group is also the | ||||
conformance specification for RFC 1515 | ||||
implementations." | ||||
::= { mauModObjGrps 1 } | ||||
mauRpGrpExtended OBJECT-GROUP | ||||
OBJECTS { rpMauFalseCarriers, | ||||
rpJackGroupIndex, | ||||
rpJackPortIndex, | ||||
rpJackMauIndex, | ||||
rpJackIndex, | ||||
rpJackType } | ||||
STATUS current | ||||
DESCRIPTION | ||||
"Conformance group for MAUs attached to | ||||
repeater ports with extended management | ||||
(including 100 Mb/s and jack management)." | ||||
::= { mauModObjGrps 2 } | ||||
mauIfGrpBasic OBJECT-GROUP | ||||
OBJECTS { ifMauIfIndex, | ||||
ifMauIndex, | ||||
ifMauType, | ||||
ifMauStatus, | ||||
ifMauMediaAvail, | ||||
ifMauMediaAvailStateExits, | ||||
ifMauJabberState, | ||||
ifMauJabberingStateEnters } | ||||
STATUS current | ||||
DESCRIPTION | ||||
"Basic conformance group for MAUs attached to | ||||
interfaces. This group also provides a | ||||
conformance specification for RFC 1515 | ||||
implementations." | ||||
::= { mauModObjGrps 3 } | ||||
mauIfGrpExtended OBJECT-GROUP | ||||
OBJECTS { ifMauFalseCarriers, | ||||
ifMauTypeList, | ||||
ifJackIfIndex, | ||||
ifJackMauIndex, | ||||
ifJackIndex, | ||||
ifJackType } | ||||
STATUS current | ||||
DESCRIPTION | ||||
"Conformance group for MAUs attached | ||||
to interfaces with extended management | ||||
(including 100 Mb/s and jack management)." | ||||
::= { mauModObjGrps 4 } | ||||
mauIfGrpAutoNeg OBJECT-GROUP | ||||
OBJECTS { ifMauAutoNegAdminStatus, | ||||
ifMauAutoNegRemoteSignaling, | ||||
ifMauAutoNegConfig, | ||||
ifMauAutoNegCapability, | ||||
ifMauAutoNegCapAdvertised, | ||||
ifMauAutoNegCapReceived, | ||||
ifMauAutoNegTechnologyInUse, | ||||
ifMauAutoNegRestart } | ||||
STATUS current | ||||
DESCRIPTION | ||||
"Conformance group for MAUs attached to | ||||
interfaces with managed auto-negotiation." | ||||
::= { mauModObjGrps 5 } | ||||
mauBroadBasic OBJECT-GROUP | ||||
OBJECTS { broadMauIfIndex, | ||||
broadMauIndex, | ||||
broadMauXmtRcvSplitType, | ||||
broadMauXmtCarrierFreq, | ||||
broadMauTranslationFreq } | ||||
STATUS current | ||||
DESCRIPTION | ||||
"Conformance group for broadband MAUs | ||||
attached to interfaces. This group | ||||
provides a conformance specification | ||||
for RFC 1515 implementations." | ||||
::= { mauModObjGrps 6 } | ||||
-- Notification groups | ||||
-- ?? later | ||||
-- Compliances | ||||
mauModRpCompl MODULE-COMPLIANCE | ||||
STATUS current | ||||
DESCRIPTION | ||||
"Compliance for MAUs attached to repeater ports." | ||||
MODULE -- this module | ||||
MANDATORY-GROUPS { mauRpGrpBasic } | ||||
GROUP mauRpGrpExtended | ||||
DESCRIPTION | ||||
"Implementation of this optional group is | ||||
recommended for MAUs which have 100Mb/s | ||||
capability and/or more than one attached | ||||
external jack." | ||||
::= { mauModCompls 1 } | ||||
mauModIfCompl MODULE-COMPLIANCE | ||||
STATUS current | ||||
DESCRIPTION | ||||
"Compliance for MAUs attached to interfaces." | ||||
MODULE -- this module | ||||
MANDATORY-GROUPS { mauIfGrpBasic } | ||||
GROUP mauIfGrpExtended | ||||
DESCRIPTION | ||||
"Implementation of this optional group is | ||||
recommended for MAUs which have 100Mb/s | ||||
capability and/or more than one attached | ||||
external jack." | ||||
GROUP mauIfGrpAutoNeg | ||||
DESCRIPTION | ||||
"Implementation of this optional group | ||||
is recommended for MAUs which support | ||||
managed auto-negotiation." | ||||
GROUP mauBroadBasic | ||||
DESCRIPTION | ||||
"Implementation of this group is | ||||
mandatory for broadband MAUs." | ||||
::= { mauModCompls 2 } | ||||
END | END | |||
4. References | 4. References | |||
[1] IEEE 802.3/ISO 8802-3 Information processing systems - | [1] IEEE 802.3/ISO 8802-3 Information processing systems - | |||
Local area networks - Part 3: Carrier sense multiple | Local area networks - Part 3: Carrier sense multiple | |||
access with collision detection (CSMA/CD) access method | access with collision detection (CSMA/CD) access method | |||
and physical layer specifications, 1993. | and physical layer specifications, 1993. | |||
[2] IEEE 802.3u-1995, "MAC Parameters, Physical Layer, Medium | [2] IEEE 802.3u-1995, "MAC Parameters, Physical Layer, Medium | |||
Attachment Units and Repeater for 100 Mb/s Operation, | Attachment Units and Repeater for 100 Mb/s Operation, | |||
Type 100BASE-T," Sections 21 through 29, Supplement to | Type 100BASE-T," Sections 21 through 29, Supplement to | |||
IEEE Std 802.3, October 26, 1995. | IEEE Std 802.3, October 26, 1995. | |||
[3] IEEE 802.3u-1995, "10 & 100 Mb/s Management," Section 30, | [3] IEEE 802.3u-1995, "10 & 100 Mb/s Management," Section 30, | |||
Supplement to IEEE Std 802.3, October 26, 1995. | Supplement to IEEE Std 802.3, October 26, 1995. | |||
[4] Romascanu, D., and K. de Graaf, "Definitions of Managed | [4] Romascanu, D., and K. de Graaf, "Definitions of Managed | |||
Objects for IEEE 802.3 Repeater Devices", November 1995. | Objects for IEEE 802.3 Repeater Devices", February 1996. | |||
End of changes. | ||||
This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/ |