draft-ietf-hubmib-wis-mib-04.txt   draft-ietf-hubmib-wis-mib-05.txt 
skipping to change at page 1, line 17 skipping to change at page 1, line 17
C. M. Heard C. M. Heard
Consultant Consultant
Kam Lam Kam Lam
Lucent Technologies Lucent Technologies
Kerry McDonald Kerry McDonald
CSU San Bernardino CSU San Bernardino
K. C. Norseth K. C. Norseth
Consultant Consultant
Kaj Tesink Kaj Tesink
Telcordia Technologies Telcordia Technologies
May 2, 2002 December 13, 2002
Definitions of Managed Objects Definitions of Managed Objects
for the Ethernet WAN Interface Sublayer for the Ethernet WAN Interface Sublayer
<draft-ietf-hubmib-wis-mib-04.txt> <draft-ietf-hubmib-wis-mib-05.txt>
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. Internet-Drafts are working all provisions of Section 10 of RFC2026. 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
skipping to change at page 2, line 17 skipping to change at page 2, line 17
This document defines a portion of the Management Information Base This document defines a portion of the Management Information Base
(MIB) for use with network management protocols in TCP/IP based (MIB) for use with network management protocols in TCP/IP based
internets. In particular, it defines objects for managing the internets. In particular, it defines objects for managing the
Ethernet Wide Area Network (WAN) Interface Sublayer (WIS). Ethernet Wide Area Network (WAN) Interface Sublayer (WIS).
The MIB module defined in this memo is an extension of the SONET/SDH The MIB module defined in this memo is an extension of the SONET/SDH
Interface MIB and is implemented in conjunction with it and with the Interface MIB and is implemented in conjunction with it and with the
Ethernet-like Interface MIB, the 802.3 Medium Attachment Unit MIB, Ethernet-like Interface MIB, the 802.3 Medium Attachment Unit MIB,
the Interfaces Group MIB, and the Inverted Stack Table MIB. the Interfaces Group MIB, and the Inverted Stack Table MIB.
Table of Contents
1 Conventions ............................................... 3
2 The Internet-Standard Management Framework ................ 3
3 Overview .................................................. 3
3.1 Relationship to the SONET/SDH Interface MIB ............. 4
3.2 Relationship to the Ethernet-like Interface MIB ......... 4
3.3 Relationship to the 802.3 MAU MIB ....................... 5
3.4 Use of the ifTable ...................................... 5
3.4.1 Layering Model ........................................ 5
3.4.2 Use of ifTable for LLC Layer/MAC
Layer/Reconciliation Sublayer/Physical Coding
Sublayer ............................................... 6
3.4.3 Use of ifTable for SONET/SDH Path Layer ............... 6
3.4.4 Use of ifTable for SONET/SDH Medium/Section/Line
Layer .................................................. 6
3.5 SONET/SDH Terminology ................................... 6
3.6 Mapping of IEEE 802.3 Managed Objects ................... 7
3.7 Mapping of SNMP Objects to WIS Station Management
Registers .............................................. 12
3.8 Structure of the MIB Module ............................. 14
3.8.1 etherWisDeviceTable ................................... 14
3.8.2 etherWisSectionCurrentTable ........................... 15
3.8.3 etherWisPathCurrentTable .............................. 15
3.8.4 etherWisFarEndPathCurrentTable ........................ 15
4 Object Definitions ........................................ 16
5 Acknowledgments ........................................... 30
6 Security Considerations ................................... 31
7 References ................................................ 32
7.1 Normative References .................................... 32
7.2 Informative References .................................. 33
8 Authors' Addresses ........................................ 33
9 Intellectual Property ..................................... 34
Appendix A: Collection of Performance Data Using WIS
MDIO Registers ......................................... 35
Full Copyright Statement ................................... 36
1. Conventions 1. Conventions
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
"OPTIONAL", when they appear in this document, are to be interpreted "OPTIONAL", when they appear in this document, are to be interpreted
as described in RFC 2119 [RFC2119]. as described in RFC 2119 [RFC2119].
2. The SNMP Management Framework 2. The Internet-Standard Management Framework
The SNMP Management Framework presently consists of five major
components:
o An overall architecture, described in RFC 2571 [RFC2571].
o Mechanisms for describing and naming objects and events for the
purpose of management. The first version of this Structure of
Management Information (SMI) is called SMIv1 and described in
STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC
1215 [RFC1215]. The second version, called SMIv2, is described
in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and
STD 58, RFC 2580 [RFC2580].
o Message protocols for transferring management information. The
first version of the SNMP message protocol is called SNMPv1 and
described in STD 15, RFC 1157 [RFC1157]. A second version of
the SNMP message protocol, which is not an Internet standards
track protocol, is called SNMPv2c and described in RFC 1901
[RFC1901] and RFC 1906 [RFC1906]. The third version of the
message protocol is called SNMPv3 and described in RFC 1906
[RFC1906], RFC 2572 [RFC2572] and RFC 2574 [RFC2574].
o Protocol operations for accessing management information. The
first set of protocol operations and associated PDU formats is
described in STD 15, RFC 1157 [RFC1157]. A second set of
protocol operations and associated PDU formats is described in
RFC 1905 [RFC1905].
o A set of fundamental applications described in RFC 2573
[RFC2573] and the view-based access control mechanism described
in RFC 2575 [RFC2575].
A more detailed introduction to the current SNMP Management Framework For a detailed overview of the documents that describe the current
can be found in RFC 2570 [RFC2570]. Internet-Standard Management Framework, please refer to section 7 of
RFC 2570bis [RFC2570bis].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. Objects in the MIB are the Management Information Base or MIB. MIB objects are generally
defined using the mechanisms defined in the SMI. accessed through the Simple Network Management Protocol (SNMP).
Objects in the MIB are defined using the mechanisms defined in the
This memo specifies a MIB module that is compliant to the SMIv2. A Structure of Management Information (SMI). This memo specifies a MIB
MIB conforming to the SMIv1 can be produced through the appropriate module that is compliant to the SMIv2, which is described in STD 58,
translations. The resulting translated MIB must be semantically RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580
equivalent, except where objects or events are omitted because no [RFC2580].
translation is possible (use of Counter64). Some machine readable
information in SMIv2 will be converted into textual descriptions in
SMIv1 during the translation process. However, this loss of machine
readable information is not considered to change the semantics of the
MIB.
3. Overview 3. Overview
The objects defined in this memo are used in conjunction with objects The objects defined in this memo are used in conjunction with objects
defined in the Interfaces Group MIB [RFC2863], the SONET/SDH defined in the Interfaces Group MIB [RFC2863], the SONET/SDH
Interface MIB [SONETng], and the 802.3 MAU MIB [MAU-MIB] to manage Interface MIB [SONETng], and the 802.3 MAU MIB [MAU-MIB] to manage
the WAN Interface Sublayer (WIS) defined in [P802.3ae]. The WIS the Ethernet Wide Area Network (WAN) Interface Sublayer (WIS) defined
contains functions to perform OC-192c/VC-4-64c framing and in [802.3ae]. The WIS contains functions to perform OC-192c/VC-4-64c
scrambling. It resides between the PCS and PMA sublayers within a framing and scrambling. It resides between the Physical Coding
10GBASE-W 10 Gb/s WAN-compatible PHY and may be used in conjunction Sublayer (PCS) and the Physical Medium Attachment (PMA) sublayer
with any of the PCS, PMA, and PMD sublayers that are defined in within a 10GBASE-W 10 Gb/s WAN-compatible physical layer device (PHY)
[P802.3ae] for 10GBASE-W PHYs. Three types of 10GBASE-W PHYs are and may be used in conjunction with any of the PCS, PMA, and Physical
defined, distinguished by the type of optics employed: 10GBASE-SW, Medium Dependent (PMD) sublayers defined in [802.3ae] for 10GBASE-W
10GBASE-LW, and 10GBASE-EW. The objects defined in this memo may be PHYs. Three types of 10GBASE-W PHYs are defined, distinguished by
used to manage an Ethernet interface employing any type of 10GBASE-W the type of optics employed: 10GBASE-SW, 10GBASE-LW, and 10GBASE-EW.
PHY. They do not apply to any other kind of interface. In The objects defined in this memo may be used to manage an Ethernet
particular, they do not apply to so-called Ethernet Line Terminating interface employing any type of 10GBASE-W PHY. They do not apply to
Equipment (ELTE) residing within a SONET network element that uses any other kind of interface. In particular, they do not apply to
the 10GBASE-W PMA/PMD sublayers but otherwise acts as SONET Line so-called Ethernet Line Terminating Equipment (ELTE) residing within
Terminating Equipment (LTE). a SONET network element that uses the 10GBASE-W PMA/PMD sublayers but
otherwise acts as SONET Line Terminating Equipment (LTE).
The objects presented here -- along with those incorporated by The objects presented here -- along with those incorporated by
reference from the Interfaces Group MIB, the SONET/SDH Interface MIB, reference from the Interfaces Group MIB, the SONET/SDH Interface MIB,
and the 802.3 MAU MIB -- are intended to provide exact and the 802.3 MAU MIB -- are intended to provide exact
representations of the mandatory attributes in the oWIS managed representations of the mandatory attributes in the oWIS managed
object class (i.e., the members of the pWISBasic package) defined in object class (i.e., the members of the pWISBasic package) defined in
Clause 30 and Annex 30A of [P802.3ae]. They are also intended to Clause 30 and Annex 30A of [802.3ae]. They are also intended to
provide approximate representations of the optional attributes (i.e., provide approximate representations of the optional attributes (i.e.,
the members of the pWISOptional package). Some objects with no the members of the pWISOptional package). Some objects with no
analogues in oWIS are defined to support WIS testing features analogues in oWIS are defined to support WIS testing features
required by Clause 50 of [P802.3ae]. required by Clause 50 of [802.3ae].
3.1. Relationship to the SONET/SDH Interface MIB 3.1. Relationship to the SONET/SDH Interface MIB
Since the Ethernet WAN Interface Sublayer was designed to be SONET- Since the Ethernet WAN Interface Sublayer was designed to be SONET-
compatible, information similar to that provided by most of the compatible, information similar to that provided by most of the
members of the oWIS managed object class is available from objects members of the oWIS managed object class is available from objects
defined in the SONET-MIB [SONETng]. Thus, the MIB module defined in defined in the SONET-MIB [SONETng]. Thus, the MIB module defined in
this memo is a sparse augmentation of the SONET-MIB -- in other this memo is a sparse augmentation of the SONET-MIB -- in other
words, every table defined here is an extension of some table in the words, every table defined here is an extension of some table in the
SONET-MIB -- and its compliance statement REQUIRES that an agent SONET-MIB -- and its compliance statement REQUIRES that an agent
skipping to change at page 4, line 32 skipping to change at page 4, line 34
from the SONET-MIB -- specifically, the threshold objects and from the SONET-MIB -- specifically, the threshold objects and
interval counter objects -- provide only approximate representations interval counter objects -- provide only approximate representations
of the corresponding oWIS attributes, as detailed in Section 3.6. An of the corresponding oWIS attributes, as detailed in Section 3.6. An
alternative approach would have been to define new objects to exactly alternative approach would have been to define new objects to exactly
match the oWIS definitions. That approach was rejected because the match the oWIS definitions. That approach was rejected because the
SONET-MIB objects are already used in deployed systems to manage the SONET-MIB objects are already used in deployed systems to manage the
SONET sublayers of ATM over SONET and PPP over SONET interfaces, and SONET sublayers of ATM over SONET and PPP over SONET interfaces, and
it was deemed undesirable to use a different scheme to manage the it was deemed undesirable to use a different scheme to manage the
SONET sublayers of 10 Gb/s WAN-compatible Ethernet interfaces. Note SONET sublayers of 10 Gb/s WAN-compatible Ethernet interfaces. Note
that the approach adopted by this memo requires no hardware support that the approach adopted by this memo requires no hardware support
beyond that mandated by [P802.3ae] subclause 50.3.11. beyond that mandated by [802.3ae] subclause 50.3.11.
3.2. Relationship to the Ethernet-like Interface MIB 3.2. Relationship to the Ethernet-like Interface MIB
An interface which includes the Ethernet WIS is, by definition, an An interface which includes the Ethernet WIS is, by definition, an
Ethernet-like interface, and an agent implementing the objects Ethernet-like interface, and an agent implementing the objects
defined in this memo MUST implement the objects required by the defined in this memo MUST implement the objects required by the
dot3Compliance2 compliance statement in the EtherLike-MIB. dot3Compliance2 compliance statement in the EtherLike-MIB.
3.3. Relationship to the 802.3 MAU MIB 3.3. Relationship to the 802.3 MAU MIB
skipping to change at page 5, line 13 skipping to change at page 5, line 25
WIS. WIS.
3.4. Use of the ifTable 3.4. Use of the ifTable
This section specifies how the ifTable, as defined in [RFC2863], is This section specifies how the ifTable, as defined in [RFC2863], is
used for the Ethernet WIS application. used for the Ethernet WIS application.
3.4.1. Layering Model 3.4.1. Layering Model
Ethernet interfaces that employ the WIS are layered as defined in Ethernet interfaces that employ the WIS are layered as defined in
[P802.3ae]. The corresponding use of the ifTable [RFC2863] is shown [802.3ae]. The corresponding use of the ifTable [RFC2863] is shown
in the figure below. in the figure below.
_____________________________ _ _____________________________ _
| LLC Layer | | | LLC Layer | |
+-----------------------------+ | +-----------------------------+ |
| MAC Layer | | | MAC Layer | |
+-----------------------------+ > 1 ifEntry +-----------------------------+ > 1 ifEntry
| Reconciliation Sublayer | | ifType: ethernetCsmacd(6) | Reconciliation Sublayer | | ifType: ethernetCsmacd(6)
+-----------------------------+ | +-----------------------------+ |
| Physical Coding Sublayer | | | Physical Coding Sublayer | |
skipping to change at page 6, line 13 skipping to change at page 6, line 26
reports a value of 4294967295. reports a value of 4294967295.
3.4.4. Use of ifTable for SONET/SDH Medium/Section/Line Layer 3.4.4. Use of ifTable for SONET/SDH Medium/Section/Line Layer
The ifTable MUST be used as specified in [SONETng] for the SONET/SDH The ifTable MUST be used as specified in [SONETng] for the SONET/SDH
Medium/Section/Line Layer. The value of ifHighSpeed is set to 9953. Medium/Section/Line Layer. The value of ifHighSpeed is set to 9953.
ifSpeed reports a value of 4294967295. ifSpeed reports a value of 4294967295.
3.5. SONET/SDH Terminology 3.5. SONET/SDH Terminology
The SONET/SDH terminology used in [P802.3ae] is mostly the same as in The SONET/SDH terminology used in [802.3ae] is mostly the same as in
[SONETng], but there are a few differences. In those cases the [SONETng], but there are a few differences. In those cases the
definitions in [P802.3ae] take precedence. The specific differences definitions in [802.3ae] take precedence. The specific differences
are as follows. are as follows.
Unequipped Unequipped
This defect is not defined by [P802.3ae]. An implementation that This defect is not defined by [802.3ae]. An implementation that
supports it SHOULD report it by setting the sonetPathUnequipped supports it SHOULD report it by setting the sonetPathUnequipped
bit in the appropriate instance of sonetPathCurrentStatus. bit in the appropriate instance of sonetPathCurrentStatus.
Signal Label Mismatch Signal Label Mismatch
This defect is called Payload Label Mismatch (PLM) in [P802.3ae]. This defect is called Payload Label Mismatch (PLM) in [802.3ae].
It is reported by setting both the sonetPathSignalLabelMismatch It is reported by setting both the sonetPathSignalLabelMismatch
bit in the appropriate instance of sonetPathCurrentStatus bit in the appropriate instance of sonetPathCurrentStatus
(defined in [SONETng]) and the etherWisPathPLM bit in the (defined in [SONETng]) and the etherWisPathPLM bit in the
corresponding instance of etherWisPathCurrentStatus (defined corresponding instance of etherWisPathCurrentStatus (defined
below). below).
Loss of Codegroup Delineation Loss of Codegroup Delineation
[P802.3ae] defines Loss of Codegroup Delineation (LCD) as [802.3ae] defines Loss of Codegroup Delineation (LCD) as
occurring when the Physical Coding Sublayer is unable to locate occurring when the Physical Coding Sublayer is unable to locate
64B/66B code group boundaries. There is no analogous defect 64B/66B code group boundaries. There is no analogous defect
defined in [SONETng]. It is reported by setting the defined in [SONETng]. It is reported by setting the
etherWisPathLCD bit in the appropriate instance of the object etherWisPathLCD bit in the appropriate instance of the object
etherWisPathCurrentStatus defined below. etherWisPathCurrentStatus defined below.
STS-Path Remote Defect Indication STS-Path Remote Defect Indication
[P802.3ae] mandates the use of ERDI-P (Enhanced Remote Defect [802.3ae] mandates the use of ERDI-P (Enhanced Remote Defect
Indication - Path) defined in [T1.231] to signal remote server Indication - Path) defined in [T1.231] to signal remote server
defects (triggered by path AIS or path LOP) and remote payload defects (triggered by path AIS or path LOP) and remote payload
defects (triggered by Payload Label Mismatch or Loss of Codegroup defects (triggered by Payload Label Mismatch or Loss of Codegroup
Delineation). [SONETng] defines the one-bit RDI-P (Remote Defect Delineation). [SONETng] defines the one-bit RDI-P (Remote Defect
Indication - Path), which signals remote server detects (i.e., Indication - Path), which signals remote server detects (i.e.,
path AIS and path LOP) only. An implementation of the MIB module path AIS and path LOP) only. An implementation of the MIB module
defined in this memo MUST set the sonetPathSTSRDI bit in the defined in this memo MUST set the sonetPathSTSRDI bit in the
appropriate instance of sonetPathCurrentStatus when it receives appropriate instance of sonetPathCurrentStatus when it receives
an ERDI-P server defect indication from the remote end. Both an ERDI-P server defect indication from the remote end. Both
ERDI-P payload defects and ERDI-P server defects are reported in ERDI-P payload defects and ERDI-P server defects are reported in
the object etherWisFarEndPathCurrentStatus defined below. the object etherWisFarEndPathCurrentStatus defined below.
Path Coding Violations Path Coding Violations
In [P802.3ae] the path layer CV count is based on block errors In [802.3ae] the path layer CV count is based on block errors and
and not BIP-8 errors, i.e., it is incremented only once for each not BIP-8 errors, i.e., it is incremented only once for each B3
B3 byte that indicates incorrect parity, regardless of the number byte that indicates incorrect parity, regardless of the number of
of bits in error. Note that Section 8.4.5.1 of [T1.231] allows bits in error. Note that Section 8.4.5.1 of [T1.231] allows
either path BIP-8 errors or path block errors to be used for the either path BIP-8 errors or path block errors to be used for the
path layer error count. path layer error count.
3.6. Mapping of IEEE 802.3 Managed Objects 3.6. Mapping of IEEE 802.3 Managed Objects
This section contains the mapping between oWIS managed objects This section contains the mapping between oWIS managed objects
defined in [P802.3ae] and managed objects defined in this document defined in [802.3ae] and managed objects defined in this document and
and in associated MIB modules, i.e., the IF-MIB [RFC2863], the in associated MIB modules, i.e., the IF-MIB [RFC2863], the SONET-MIB
SONET-MIB [SONETng], and the MAU-MIB [MAU-MIB]. [SONETng], and the MAU-MIB [MAU-MIB].
IEEE 802.3 Managed Object Corresponding SNMP Object IEEE 802.3 Managed Object Corresponding SNMP Object
oWIS - pWISBasic package oWIS - pWISBasic package
aWISID IF-MIB - ifIndex aWISID IF-MIB - ifIndex
aSectionStatus SONET-MIB - sonetSectionCurrentStatus aSectionStatus SONET-MIB - sonetSectionCurrentStatus
aLineStatus SONET-MIB - sonetLineCurrentStatus aLineStatus SONET-MIB - sonetLineCurrentStatus
aPathStatus etherWisPathCurrentStatus aPathStatus etherWisPathCurrentStatus
aFarEndPathStatus etherWisFarEndPathCurrentStatus aFarEndPathStatus etherWisFarEndPathCurrentStatus
skipping to change at page 8, line 27 skipping to change at page 8, line 41
sonetFarEndPathIntervalESs sonetFarEndPathIntervalESs
aFarEndPathCVs SONET-MIB - sonetFarEndPathCurrentCVs + aFarEndPathCVs SONET-MIB - sonetFarEndPathCurrentCVs +
sonetFarEndPathIntervalCVs sonetFarEndPathIntervalCVs
It should be noted that the threshold and counter objects imported It should be noted that the threshold and counter objects imported
from the SONET-MIB are not completely equivalent to the corresponding from the SONET-MIB are not completely equivalent to the corresponding
IEEE 802.3 objects. The specific differences are as follows: IEEE 802.3 objects. The specific differences are as follows:
IEEE 802.3 Managed Object How Corresponding SNMP Object Differs IEEE 802.3 Managed Object How Corresponding SNMP Object Differs
aSectionSESThreshold This object is defined in [P802.3ae] aSectionSESThreshold This object is defined in [802.3ae]
as an integer with one instance per as an integer with one instance per
interface. sonetSESthresholdSet interface. sonetSESthresholdSet
is an enumerated value that has one is an enumerated value that has one
instance per network element; it instance per network element; it
controls the thresholds for all layers controls the thresholds for all layers
simultaneously and allows only certain simultaneously and allows only certain
discrete values to be selected. discrete values to be selected.
aSectionSESs This object is defined in [P802.3ae] as aSectionSESs This object is defined in [802.3ae] as
a generalized nonresetable counter. a generalized nonresetable counter.
The objects sonetSectionCurrentSESs and The objects sonetSectionCurrentSESs and
sonetSectionIntervalSESs are 15-minute sonetSectionIntervalSESs are 15-minute
interval counters. interval counters.
aSectionESs This object is defined as a generalized aSectionESs This object is defined as a generalized
nonresetable counter in [P802.3ae]. nonresetable counter in [802.3ae].
The objects sonetSectionCurrentESs and The objects sonetSectionCurrentESs and
sonetSectionIntervalESs are 15-minute sonetSectionIntervalESs are 15-minute
interval counters. interval counters.
aSectionSEFSs This object is defined as a generalized aSectionSEFSs This object is defined as a generalized
nonresetable counter in [P802.3ae]. nonresetable counter in [802.3ae].
The objects sonetSectionCurrentSEFSs and The objects sonetSectionCurrentSEFSs and
sonetSectionIntervalSEFSs are 15-minute sonetSectionIntervalSEFSs are 15-minute
interval counters. interval counters.
aSectionCVs This object is defined as a generalized aSectionCVs This object is defined as a generalized
nonresetable counter in [P802.3ae], and nonresetable counter in [802.3ae], and
it is not subject to inhibiting. The it is not subject to inhibiting. The
objects sonetSectionCurrentCVs and objects sonetSectionCurrentCVs and
sonetSectionIntervalCVs are 15-minute sonetSectionIntervalCVs are 15-minute
interval counters, and they are interval counters, and they are
inhibited (not incremented) during inhibited (not incremented) during
one-second intervals that qualify as one-second intervals that qualify as
severely errored seconds. severely errored seconds.
aLineSESThreshold This object is defined in [P802.3ae] aLineSESThreshold This object is defined in [802.3ae]
as an integer with one instance per as an integer with one instance per
interface. sonetSESthresholdSet interface. sonetSESthresholdSet
is an enumerated value that has one is an enumerated value that has one
instance per network element; it instance per network element; it
controls the thresholds for all layers controls the thresholds for all layers
simultaneously and allows only certain simultaneously and allows only certain
discrete values to be selected. discrete values to be selected.
aLineSESs This object is defined as a generalized aLineSESs This object is defined as a generalized
nonresetable counter in [P802.3ae], and nonresetable counter in [802.3ae], and
it is not subject to inhibiting. The it is not subject to inhibiting. The
objects sonetLineCurrentSESs and objects sonetLineCurrentSESs and
sonetLineIntervalSESs are 15-minute sonetLineIntervalSESs are 15-minute
interval counters, and they are interval counters, and they are
inhibited (not incremented) during inhibited (not incremented) during
one-second intervals that qualify as one-second intervals that qualify as
unavailable seconds. unavailable seconds.
aLineESs This object is defined as a generalized aLineESs This object is defined as a generalized
nonresetable counter in [P802.3ae], and nonresetable counter in [802.3ae], and
it is not subject to inhibiting. The it is not subject to inhibiting. The
objects sonetLineCurrentESs and objects sonetLineCurrentESs and
sonetLineIntervalESs are 15-minute sonetLineIntervalESs are 15-minute
interval counters, and they are interval counters, and they are
inhibited (not incremented) during inhibited (not incremented) during
one-second intervals that qualify as one-second intervals that qualify as
unavailable seconds. unavailable seconds.
aLineCVs This object is defined as a generalized aLineCVs This object is defined as a generalized
nonresetable counter in [P802.3ae], and nonresetable counter in [802.3ae], and
it is not subject to inhibiting. The it is not subject to inhibiting. The
objects sonetLineCurrentCVs and objects sonetLineCurrentCVs and
sonetLineIntervalCVs are 15-minute sonetLineIntervalCVs are 15-minute
interval counters, and they are interval counters, and they are
inhibited (not incremented) during inhibited (not incremented) during
one-second intervals that qualify one-second intervals that qualify
either as severely errored seconds either as severely errored seconds
or as unavailable seconds. or as unavailable seconds.
aFarEndLineSESs This object is defined as a generalized aFarEndLineSESs This object is defined as a generalized
nonresetable counter in [P802.3ae], and nonresetable counter in [802.3ae], and
it is not subject to inhibiting. The it is not subject to inhibiting. The
objects sonetFarEndLineCurrentSESs and objects sonetFarEndLineCurrentSESs and
sonetFarEndLineIntervalSESs are sonetFarEndLineIntervalSESs are
15-minute interval counters, and they 15-minute interval counters, and they
are inhibited (not incremented) during are inhibited (not incremented) during
one-second intervals that qualify as one-second intervals that qualify as
unavailable seconds. unavailable seconds.
aFarEndLineESs This object is defined as a generalized aFarEndLineESs This object is defined as a generalized
nonresetable counter in [P802.3ae], and nonresetable counter in [802.3ae], and
it is not subject to inhibiting. The it is not subject to inhibiting. The
objects sonetFarEndLineCurrentESs and objects sonetFarEndLineCurrentESs and
sonetFarEndLineIntervalESs are 15-minute sonetFarEndLineIntervalESs are 15-minute
interval counters, and they are interval counters, and they are
inhibited (not incremented) during inhibited (not incremented) during
one-second intervals that qualify as one-second intervals that qualify as
unavailable seconds. unavailable seconds.
aFarEndLineCVs This object is defined as a generalized aFarEndLineCVs This object is defined as a generalized
nonresetable counter in [P802.3ae], and nonresetable counter in [802.3ae], and
it is not subject to inhibiting. The it is not subject to inhibiting. The
objects sonetFarEndLineCurrentCVs and objects sonetFarEndLineCurrentCVs and
sonetFarEndLineIntervalCVs are 15-minute sonetFarEndLineIntervalCVs are 15-minute
interval counters, and they are interval counters, and they are
inhibited (not incremented) during inhibited (not incremented) during
one-second intervals that qualify one-second intervals that qualify
either as severely errored seconds either as severely errored seconds
or as unavailable seconds. or as unavailable seconds.
aPathSESThreshold This object is defined in [P802.3ae] aPathSESThreshold This object is defined in [802.3ae]
as an integer with one instance per as an integer with one instance per
interface. sonetSESthresholdSet interface. sonetSESthresholdSet
is an enumerated value that has one is an enumerated value that has one
instance per network element; it instance per network element; it
controls the thresholds for all layers controls the thresholds for all layers
simultaneously and allows only certain simultaneously and allows only certain
discrete values to be selected. discrete values to be selected.
aPathSESs This object is defined as a generalized aPathSESs This object is defined as a generalized
nonresetable counter in [P802.3ae], and nonresetable counter in [802.3ae], and
it is not subject to inhibiting. The it is not subject to inhibiting. The
objects sonetPathCurrentSESs and objects sonetPathCurrentSESs and
sonetPathIntervalSESs are 15-minute sonetPathIntervalSESs are 15-minute
interval counters, and they are interval counters, and they are
inhibited (not incremented) during inhibited (not incremented) during
one-second intervals that qualify as one-second intervals that qualify as
unavailable seconds. In addition, unavailable seconds. In addition,
[P802.3ae] includes PLM-P and LCD-P [802.3ae] includes PLM-P and LCD-P
defects in the criteria for declaring defects in the criteria for declaring
path layer severely errored seconds, path layer severely errored seconds,
while [SONETng] does not. while [SONETng] does not.
aPathESs This object is defined as a generalized aPathESs This object is defined as a generalized
nonresetable counter in [P802.3ae], and nonresetable counter in [802.3ae], and
it is not subject to inhibiting. The it is not subject to inhibiting. The
objects sonetPathCurrentESs and objects sonetPathCurrentESs and
sonetPathIntervalESs are 15-minute sonetPathIntervalESs are 15-minute
interval counters, and they are interval counters, and they are
inhibited (not incremented) during inhibited (not incremented) during
one-second intervals that qualify as one-second intervals that qualify as
unavailable seconds. In addition, unavailable seconds. In addition,
[P802.3ae] includes PLM-P and LCD-P [802.3ae] includes PLM-P and LCD-P
defects in the criteria for declaring defects in the criteria for declaring
path layer errored seconds, while path layer errored seconds, while
[SONETng] does not. [SONETng] does not.
aPathCVs This object is defined as a generalized aPathCVs This object is defined as a generalized
nonresetable counter in [P802.3ae], and nonresetable counter in [802.3ae], and
it is not subject to inhibiting. The it is not subject to inhibiting. The
objects sonetPathCurrentCVs and objects sonetPathCurrentCVs and
sonetPathIntervalCVs are 15-minute sonetPathIntervalCVs are 15-minute
interval counters, and they are interval counters, and they are
inhibited (not incremented) during inhibited (not incremented) during
one-second intervals that qualify one-second intervals that qualify
either as severely errored seconds either as severely errored seconds
or as unavailable seconds. or as unavailable seconds.
aFarEndPathSESs This object is defined as a generalized aFarEndPathSESs This object is defined as a generalized
nonresetable counter in [P802.3ae], and nonresetable counter in [802.3ae], and
it is not subject to inhibiting. The it is not subject to inhibiting. The
objects sonetFarEndPathCurrentSESs and objects sonetFarEndPathCurrentSESs and
sonetFarEndPathIntervalSESs are sonetFarEndPathIntervalSESs are
15-minute interval counters, and they 15-minute interval counters, and they
are inhibited (not incremented) during are inhibited (not incremented) during
one-second intervals that qualify as one-second intervals that qualify as
unavailable seconds. In addition, unavailable seconds. In addition,
[P802.3ae] includes far-end PLM-P and [802.3ae] includes far-end PLM-P and
LCD-P defects in the criteria for LCD-P defects in the criteria for
declaring far-end path layer severely declaring far-end path layer severely
errored seconds, while [SONETng] does errored seconds, while [SONETng] does
not. not.
aFarEndPathESs This object is defined as a generalized aFarEndPathESs This object is defined as a generalized
nonresetable counter in [P802.3ae], and nonresetable counter in [802.3ae], and
it is not subject to inhibiting. The it is not subject to inhibiting. The
objects sonetFarEndPathCurrentESs and objects sonetFarEndPathCurrentESs and
sonetFarEndPathIntervalESs are 15-minute sonetFarEndPathIntervalESs are 15-minute
interval counters, and they are interval counters, and they are
inhibited (not incremented) during inhibited (not incremented) during
one-second intervals that qualify as one-second intervals that qualify as
unavailable seconds. In addition, unavailable seconds. In addition,
[P802.3ae] includes far-end PLM-P and [802.3ae] includes far-end PLM-P and
LCD-P defects in the criteria for LCD-P defects in the criteria for
declaring far-end path layer errored declaring far-end path layer errored
seconds, while [SONETng] does not. seconds, while [SONETng] does not.
aFarEndPathCVs This object is defined as a generalized aFarEndPathCVs This object is defined as a generalized
nonresetable counter in [P802.3ae], and nonresetable counter in [802.3ae], and
it is not subject to inhibiting. The it is not subject to inhibiting. The
objects sonetFarEndPathCurrentCVs and objects sonetFarEndPathCurrentCVs and
sonetFarEndPathIntervalCVs are 15-minute sonetFarEndPathIntervalCVs are 15-minute
interval counters, and they are interval counters, and they are
inhibited (not incremented) during inhibited (not incremented) during
one-second intervals that qualify one-second intervals that qualify
either as severely errored seconds either as severely errored seconds
or as unavailable seconds. or as unavailable seconds.
Note: despite the semantic differences between the threshold objects Note: despite the semantic differences between the threshold objects
and counter objects imported from the SONET-MIB and the corresponding and counter objects imported from the SONET-MIB and the corresponding
IEEE 802.3 objects, the hardware support mandated by [P802.3ae] IEEE 802.3 objects, the hardware support mandated by [802.3ae]
subclause 50.3.11 suffices for both. See Appendix A for details. subclause 50.3.11 suffices for both. See Appendix A for details.
3.7. Mapping of SNMP Objects to WIS Station Management Registers 3.7. Mapping of SNMP Objects to WIS Station Management Registers
Some of the objects defined in this memo or incorporated by reference Some of the objects defined in this memo or incorporated by reference
from the SONET-MIB [SONETng] or the MAU-MIB [MAU-MIB] require WIS- from the SONET-MIB [SONETng] or the MAU-MIB [MAU-MIB] require WIS-
specific hardware support. [P802.3ae] subclause 50.3.11 specifies specific hardware support. [802.3ae] subclause 50.3.11 specifies WIS
WIS management interface requirements, including a required subset of management interface requirements, including a required subset of the
the WIS MDIO (Management Data Input/Output) registers defined in WIS Management Data Input/Output (MDIO) registers defined in
[P802.3ae] subclause 45.2.2. The table below provides a cross- [802.3ae] subclause 45.2.2. The table below provides a cross-
reference between those managed objects and the WIS MDIO registers reference between those managed objects and the WIS MDIO registers
from the subset in [P802.3ae] subclause 50.3.11 required to support from the subset in [802.3ae] subclause 50.3.11 required to support
them. Note that the MDIO interface is optional; however, if it is them. Note that the MDIO interface is optional; however, if it is
not implemented, then the capabilities of the required register not implemented, then the capabilities of the required register
subset must be provided by other means. subset must be provided by other means.
SNMP Object WIS MDIO Register(s) SNMP Object WIS MDIO Register(s)
ETHER-WIS - etherWisDeviceTxTestPatternMode 10G WIS control 2 ETHER-WIS - etherWisDeviceTxTestPatternMode 10G WIS control 2
ETHER-WIS - etherWisDeviceRxTestPatternMode 10G WIS control 2 ETHER-WIS - etherWisDeviceRxTestPatternMode 10G WIS control 2
ETHER-WIS - etherWisDeviceRxTestPatternErrors 10G WIS test pattern ETHER-WIS - etherWisDeviceRxTestPatternErrors 10G WIS test pattern
error counter error counter
skipping to change at page 14, line 37 skipping to change at page 14, line 49
MAU-MIB - ifMauTypeListBits 10G WIS status 2 MAU-MIB - ifMauTypeListBits 10G WIS status 2
3.8. Structure of the MIB Module 3.8. Structure of the MIB Module
Four tables are defined in this MIB module. Four tables are defined in this MIB module.
3.8.1. etherWisDeviceTable 3.8.1. etherWisDeviceTable
The purpose of this table is to define managed objects to control the The purpose of this table is to define managed objects to control the
WIS test pattern mode. These objects are required to support WIS test pattern mode. These objects are required to support
mandatory and optional WIS test features specified in [P802.3ae] mandatory and optional WIS test features specified in [802.3ae]
subclause 50.3.8. subclause 50.3.8.
The etherWisDeviceTable is a sparse augmentation of the The etherWisDeviceTable is a sparse augmentation of the
sonetMediumTable of the SONET-MIB -- in other words, for each entry sonetMediumTable of the SONET-MIB -- in other words, for each entry
in the etherWisDeviceTable there MUST be an entry in the in the etherWisDeviceTable there MUST be an entry in the
sonetMediumTable and the same ifIndex value SHALL be used for both sonetMediumTable and the same ifIndex value MUST be used for both
entries. entries.
3.8.2. etherWisSectionCurrentTable 3.8.2. etherWisSectionCurrentTable
The purpose of this table is to define managed objects for the The purpose of this table is to define managed objects for the
transmitted and received section trace messages (J0 byte). transmitted and received section trace messages (J0 byte).
The etherWisSectionCurrentTable is a sparse augmentation of the The etherWisSectionCurrentTable is a sparse augmentation of the
sonetSectionCurrentTable of the SONET-MIB -- in other words, for each sonetSectionCurrentTable of the SONET-MIB -- in other words, for each
entry in the etherWisSectionCurrentTable there MUST be an entry in entry in the etherWisSectionCurrentTable there MUST be an entry in
the sonetSectionCurrentTable and the same ifIndex value SHALL be used the sonetSectionCurrentTable and the same ifIndex value MUST be used
for both entries. for both entries.
3.8.3. etherWisPathCurrentTable 3.8.3. etherWisPathCurrentTable
The purpose of this table is to define managed objects for the The purpose of this table is to define managed objects for the
current WIS path layer status and for the transmitted and received current WIS path layer status and for the transmitted and received
path trace messages (J1 byte). The path layer status object is path trace messages (J1 byte). The path layer status object is
provided because the WIS supports some near-end path status provided because the WIS supports some near-end path status
conditions that are not reported in sonetPathCurrentStatus. conditions that are not reported in sonetPathCurrentStatus.
The etherWisPathCurrentTable is a sparse augmentation of the The etherWisPathCurrentTable is a sparse augmentation of the
sonetPathCurrentTable of the SONET-MIB -- in other words, for each sonetPathCurrentTable of the SONET-MIB -- in other words, for each
entry in the etherWisPathCurrentTable there MUST be an entry in the entry in the etherWisPathCurrentTable there MUST be an entry in the
sonetPathCurrentTable and the same ifIndex value SHALL be used for sonetPathCurrentTable and the same ifIndex value MUST be used for
both entries. both entries.
3.8.4. etherWisFarEndPathCurrentTable 3.8.4. etherWisFarEndPathCurrentTable
The purpose of this table is to define a managed object for the The purpose of this table is to define a managed object for the
current status of the far end of the path. This object is provided current status of the far end of the path. This object is provided
because the WIS supports some far-end path status conditions that are because the WIS supports some far-end path status conditions that are
not reported in sonetPathCurrentStatus. not reported in sonetPathCurrentStatus.
The etherWisFarEndPathCurrentTable is a sparse augmentation of the The etherWisFarEndPathCurrentTable is a sparse augmentation of the
sonetFarEndPathCurrentTable of the SONET-MIB -- in other words, for sonetFarEndPathCurrentTable of the SONET-MIB -- in other words, for
each entry in the etherWisFarEndPathCurrentTable there MUST be an each entry in the etherWisFarEndPathCurrentTable there MUST be an
entry in the sonetFarEndPathCurrentTable and the same ifIndex value entry in the sonetFarEndPathCurrentTable and the same ifIndex value
SHALL be used for both entries. MUST be used for both entries.
4. Object Definitions 4. Object Definitions
ETHER-WIS DEFINITIONS ::= BEGIN ETHER-WIS DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, MODULE-IDENTITY, OBJECT-TYPE,
transmission Gauge32, transmission
FROM SNMPv2-SMI FROM SNMPv2-SMI
ifIndex ifIndex
FROM IF-MIB FROM IF-MIB
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
sonetMediumStuff2, sonetSectionStuff2, sonetMediumStuff2, sonetSectionStuff2,
sonetLineStuff2, sonetFarEndLineStuff2, sonetLineStuff2, sonetFarEndLineStuff2,
sonetPathStuff2, sonetFarEndPathStuff2, sonetPathStuff2, sonetFarEndPathStuff2,
sonetMediumType, sonetMediumLineCoding, sonetMediumType, sonetMediumLineCoding,
sonetMediumLineType, sonetMediumCircuitIdentifier, sonetMediumLineType, sonetMediumCircuitIdentifier,
sonetMediumLoopbackConfig, sonetSESthresholdSet, sonetMediumLoopbackConfig, sonetSESthresholdSet,
sonetPathCurrentWidth sonetPathCurrentWidth
FROM SONET-MIB; FROM SONET-MIB;
etherWisMIB MODULE-IDENTITY etherWisMIB MODULE-IDENTITY
LAST-UPDATED "200205022034Z" -- May 2, 2002 LAST-UPDATED "200212132358Z" -- December 13, 2002
ORGANIZATION "IETF Ethernet Interfaces and Hub MIB ORGANIZATION "IETF Ethernet Interfaces and Hub MIB
Working Group" Working Group"
CONTACT-INFO CONTACT-INFO
"WG charter: "WG charter:
http://www.ietf.org/html.charters/hubmib-charter.html http://www.ietf.org/html.charters/hubmib-charter.html
Chair: Dan Romascanu Chair: Dan Romascanu
Postal: Avaya Inc. Postal: Avaya Inc.
Atidim Technology Park, Bldg. 3 Atidim Technology Park, Bldg. 3
Tel Aviv 61131 Tel Aviv 61131
skipping to change at page 17, line 14 skipping to change at page 17, line 14
The following reference is used throughout this MIB module: The following reference is used throughout this MIB module:
[IEEE 802.3 Std] refers to: [IEEE 802.3 Std] refers to:
IEEE Std 802.3, 2000 Edition: 'IEEE Standard for IEEE Std 802.3, 2000 Edition: 'IEEE Standard for
Information technology - Telecommunications and Information technology - Telecommunications and
information exchange between systems - Local and information exchange between systems - Local and
metropolitan area networks - Specific requirements - metropolitan area networks - Specific requirements -
Part 3: Carrier sense multiple access with collision Part 3: Carrier sense multiple access with collision
detection (CSMA/CD) access method and physical layer detection (CSMA/CD) access method and physical layer
specifications', as amended by IEEE Draft P802.3ae/D5.0: specifications', as amended by IEEE Std 802.3ae-2002,
'Supplement to Carrier Sense Multiple Access with 'IEEE Standard for Carrier Sense Multiple Access with
Collision Detection (CSMA/CD) Access Method & Physical Collision Detection (CSMA/CD) Access Method and
Layer Specifications - Media Access Control (MAC) Physical Layer Specifications - Media Access Control
Parameters, Physical Layer, and Management Parameters (MAC) Parameters, Physical Layer and Management
for 10 Gb/s Operation', May 1, 2002. Parameters for 10 Gb/s Operation', 30 August 2002.
Of particular interest are Clause 50, 'WAN Interface Of particular interest are Clause 50, 'WAN Interface
Sublayer (WIS), type 10GBASE-W', Clause 30, '10Mb/s, Sublayer (WIS), type 10GBASE-W', Clause 30, '10Mb/s,
100Mb/s, 1000Mb/s, and 10Gb/s MAC Control, and Link 100Mb/s, 1000Mb/s, and 10Gb/s MAC Control, and Link
Aggregation Management', and Clause 45, 'Management Aggregation Management', and Clause 45, 'Management
Data Input/Output (MDIO) Interface'." Data Input/Output (MDIO) Interface'.
REVISION "200205022034Z" -- May 2, 2002 Copyright (C) The Internet Society (2002). This version
of this MIB module is part of RFC yyyy; see the RFC
itself for full legal notices."
-- RFC Ed.: replace yyyy with actual RFC number & remove this notice
REVISION "200212132358Z" -- December 13, 2002
DESCRIPTION "Initial version, published as RFC yyyy." DESCRIPTION "Initial version, published as RFC yyyy."
-- RFC Ed.: replace yyyy with actual RFC number & remove this notice -- RFC Ed.: replace yyyy with actual RFC number & remove this notice
::= { transmission XXX } ::= { transmission XXX }
-- RFC Ed.: replace XXX with IANA-assigned number & remove this notice -- RFC Ed.: replace XXX with IANA-assigned number & remove this notice
-- The main sections of the module -- The main sections of the module
etherWisObjects OBJECT IDENTIFIER ::= { etherWisMIB 1 } etherWisObjects OBJECT IDENTIFIER ::= { etherWisMIB 1 }
etherWisObjectsPath OBJECT IDENTIFIER ::= { etherWisMIB 2 } etherWisObjectsPath OBJECT IDENTIFIER ::= { etherWisMIB 2 }
etherWisConformance OBJECT IDENTIFIER ::= { etherWisMIB 3 } etherWisConformance OBJECT IDENTIFIER ::= { etherWisMIB 3 }
-- groups in the Ethernet WIS MIB module -- groups in the Ethernet WIS MIB module
skipping to change at page 18, line 27 skipping to change at page 19, line 4
etherWisDeviceEntry OBJECT-TYPE etherWisDeviceEntry OBJECT-TYPE
SYNTAX EtherWisDeviceEntry SYNTAX EtherWisDeviceEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the Ethernet WIS device table. For each "An entry in the Ethernet WIS device table. For each
instance of this object there MUST be a corresponding instance of this object there MUST be a corresponding
instance of sonetMediumEntry." instance of sonetMediumEntry."
INDEX { ifIndex } INDEX { ifIndex }
::= { etherWisDeviceTable 1 } ::= { etherWisDeviceTable 1 }
EtherWisDeviceEntry ::= EtherWisDeviceEntry ::=
SEQUENCE { SEQUENCE {
etherWisDeviceTxTestPatternMode INTEGER, etherWisDeviceTxTestPatternMode INTEGER,
etherWisDeviceRxTestPatternMode INTEGER, etherWisDeviceRxTestPatternMode INTEGER,
etherWisDeviceRxTestPatternErrors Gauge32 etherWisDeviceRxTestPatternErrors Gauge32
} }
etherWisDeviceTxTestPatternMode OBJECT-TYPE etherWisDeviceTxTestPatternMode OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
none(0), none(1),
squareWave(1), squareWave(2),
prbs31(2), prbs31(3),
mixedFrequency(3) mixedFrequency(4)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable controls the transmit test pattern mode. "This variable controls the transmit test pattern mode.
The value none(0) puts the the WIS transmit path into The value none(1) puts the the WIS transmit path into
the normal operating mode. The value squareWave(1) puts the normal operating mode. The value squareWave(2) puts
the WIS transmit path into the square wave test pattern the WIS transmit path into the square wave test pattern
mode described in [IEEE 802.3 Std.] subclause 50.3.8.1. mode described in [IEEE 802.3 Std.] subclause 50.3.8.1.
The value prbs31(2) puts the WIS transmit path into the The value prbs31(3) puts the WIS transmit path into the
PRBS31 test pattern mode described in [IEEE 802.3 Std.] PRBS31 test pattern mode described in [IEEE 802.3 Std.]
subclause 50.3.8.2. The value mixedFrequency(3) puts the subclause 50.3.8.2. The value mixedFrequency(4) puts the
WIS transmit path into the mixed frequency test pattern WIS transmit path into the mixed frequency test pattern
mode described in [IEEE 802.3 Std.] subclause 50.3.8.3. mode described in [IEEE 802.3 Std.] subclause 50.3.8.3.
Any attempt to set this object to a value other than Any attempt to set this object to a value other than
none(0) when the corresponding instance of ifAdminState none(1) when the corresponding instance of ifAdminStatus
has the value up(1) MUST be rejected with the error has the value up(1) MUST be rejected with the error
inconsistentValue, and any attempt to set the corresponding inconsistentValue, and any attempt to set the corresponding
instance of ifAdminStatus to the value up(1) when an instance of ifAdminStatus to the value up(1) when an
instance of this object has a value other than none(0) instance of this object has a value other than none(1)
MUST be rejected with the error inconsistentValue." MUST be rejected with the error inconsistentValue."
REFERENCE REFERENCE
"[IEEE 802.3 Std.], 50.3.8, WIS test pattern generator and "[IEEE 802.3 Std.], 50.3.8, WIS test pattern generator and
checker, 45.2.2.6, 10G WIS control 2 register (2.7), and checker, 45.2.2.6, 10G WIS control 2 register (2.7), and
45.2.2.7.2, PRBS31 pattern testing ability (2.8.1)." 45.2.2.7.2, PRBS31 pattern testing ability (2.8.1)."
::= { etherWisDeviceEntry 1 } ::= { etherWisDeviceEntry 1 }
etherWisDeviceRxTestPatternMode OBJECT-TYPE etherWisDeviceRxTestPatternMode OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
none(0), none(1),
prbs31(2), prbs31(3),
mixedFrequency(3) mixedFrequency(4)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable controls the receive test pattern mode. "This variable controls the receive test pattern mode.
The value none(0) puts the the WIS receive path into the The value none(1) puts the the WIS receive path into the
normal operating mode. The value prbs31(2) puts the WIS normal operating mode. The value prbs31(3) puts the WIS
receive path into the PRBS31 test pattern mode described receive path into the PRBS31 test pattern mode described
in [IEEE 802.3 Std.] subclause 50.3.8.2. The value in [IEEE 802.3 Std.] subclause 50.3.8.2. The value
mixedFrequency(3) puts the WIS receive path into the mixed mixedFrequency(4) puts the WIS receive path into the mixed
frequency test pattern mode described in [IEEE 802.3 Std.] frequency test pattern mode described in [IEEE 802.3 Std.]
subclause 50.3.8.3. Any attempt to set this object to a subclause 50.3.8.3. Any attempt to set this object to a
value other than none(0) when the corresponding instance value other than none(1) when the corresponding instance
of ifAdminState has the value up(1) MUST be rejected with of ifAdminStatus has the value up(1) MUST be rejected with
the error inconsistentValue, and any attempt to set the the error inconsistentValue, and any attempt to set the
corresponding instance of ifAdminStatus to the value up(1) corresponding instance of ifAdminStatus to the value up(1)
when an instance of this object has a value other than when an instance of this object has a value other than
none(0) MUST be rejected with the error inconsistentValue." none(1) MUST be rejected with the error inconsistentValue."
REFERENCE REFERENCE
"[IEEE 802.3 Std.], 50.3.8, WIS test pattern generator and "[IEEE 802.3 Std.], 50.3.8, WIS test pattern generator and
checker, 45.2.2.6, 10G WIS control 2 register (2.7), and checker, 45.2.2.6, 10G WIS control 2 register (2.7), and
45.2.2.7.2, PRBS31 pattern testing ability (2.8.1)." 45.2.2.7.2, PRBS31 pattern testing ability (2.8.1)."
::= { etherWisDeviceEntry 2 } ::= { etherWisDeviceEntry 2 }
etherWisDeviceRxTestPatternErrors OBJECT-TYPE etherWisDeviceRxTestPatternErrors OBJECT-TYPE
SYNTAX Gauge32 ( 0..65535 ) SYNTAX Gauge32 ( 0..65535 )
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This object counts the number of errors detected when the "This object counts the number of errors detected when the
WIS receive path is operating in the PRBS31 test pattern WIS receive path is operating in the PRBS31 test pattern
mode. It is reset to zero when the WIS receive path mode. It is reset to zero when the WIS receive path
initially enters that mode, and it increments each time initially enters that mode, and it increments each time
the PRBS pattern checker detects an error as described in the PRBS pattern checker detects an error as described in
skipping to change at page 21, line 39 skipping to change at page 21, line 39
SEQUENCE { SEQUENCE {
etherWisSectionCurrentJ0Transmitted OCTET STRING, etherWisSectionCurrentJ0Transmitted OCTET STRING,
etherWisSectionCurrentJ0Received OCTET STRING etherWisSectionCurrentJ0Received OCTET STRING
} }
etherWisSectionCurrentJ0Transmitted OBJECT-TYPE etherWisSectionCurrentJ0Transmitted OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (16)) SYNTAX OCTET STRING (SIZE (16))
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is the 16-octet section trace message that is "This is the 16-octet section trace message that
to be transmitted in the J0 byte. The value SHOULD is transmitted in the J0 byte. The value SHOULD
be '89'h followed by fifteen octets of '00'h be '89'h followed by fifteen octets of '00'h
(or some cyclic shift thereof) when the section (or some cyclic shift thereof) when the section
trace function is not used, and the implementation trace function is not used, and the implementation
SHOULD use that value (or a cyclic shift thereof) SHOULD use that value (or a cyclic shift thereof)
as a default if no other value has been set." as a default if no other value has been set."
REFERENCE REFERENCE
"[IEEE 802.3 Std.], 30.8.1.1.8, aJ0ValueTX." "[IEEE 802.3 Std.], 30.8.1.1.8, aJ0ValueTX."
::= { etherWisSectionCurrentEntry 1 } ::= { etherWisSectionCurrentEntry 1 }
etherWisSectionCurrentJ0Received OBJECT-TYPE etherWisSectionCurrentJ0Received OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (16)) SYNTAX OCTET STRING (SIZE (16))
skipping to change at page 24, line 21 skipping to change at page 24, line 21
corresponding bit in sonetPathCurrentStatus." corresponding bit in sonetPathCurrentStatus."
REFERENCE REFERENCE
"[IEEE 802.3 Std.], 30.8.1.1.18, aPathStatus." "[IEEE 802.3 Std.], 30.8.1.1.18, aPathStatus."
::= { etherWisPathCurrentEntry 1 } ::= { etherWisPathCurrentEntry 1 }
etherWisPathCurrentJ1Transmitted OBJECT-TYPE etherWisPathCurrentJ1Transmitted OBJECT-TYPE
SYNTAX OCTET STRING (SIZE (16)) SYNTAX OCTET STRING (SIZE (16))
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is the 16-octet path trace message that is to "This is the 16-octet path trace message that
be transmitted in the J1 byte. The value SHOULD is transmitted in the J1 byte. The value SHOULD
be '89'h followed by fifteen octets of '00'h be '89'h followed by fifteen octets of '00'h
(or some cyclic shift thereof) when the path (or some cyclic shift thereof) when the path
trace function is not used, and the implementation trace function is not used, and the implementation
SHOULD use that value (or a cyclic shift thereof) SHOULD use that value (or a cyclic shift thereof)
as a default if no other value has been set." as a default if no other value has been set."
REFERENCE REFERENCE
"[IEEE 802.3 Std.], 30.8.1.1.23, aJ1ValueTX." "[IEEE 802.3 Std.], 30.8.1.1.23, aJ1ValueTX."
::= { etherWisPathCurrentEntry 2 } ::= { etherWisPathCurrentEntry 2 }
etherWisPathCurrentJ1Received OBJECT-TYPE etherWisPathCurrentJ1Received OBJECT-TYPE
skipping to change at page 28, line 6 skipping to change at page 28, line 6
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
etherWisDeviceGroupBasic, etherWisDeviceGroupBasic,
etherWisSectionGroup, etherWisSectionGroup,
etherWisPathGroup, etherWisPathGroup,
etherWisFarEndPathGroup etherWisFarEndPathGroup
} }
OBJECT etherWisDeviceTxTestPatternMode OBJECT etherWisDeviceTxTestPatternMode
SYNTAX INTEGER { SYNTAX INTEGER {
none(0), none(1),
squareWave(1), squareWave(2),
mixedFrequency(3) mixedFrequency(4)
} }
DESCRIPTION DESCRIPTION
"Support for values other than none(0), "Support for values other than none(1),
squareWave(1), and mixedFrequency(3) squareWave(2), and mixedFrequency(4)
is not required." is not required. Furthermore, an
implementation is not required to allow
assignment of a value other than none(1)
if that assignment would result in this
object and etherWisDeviceRxTestPatternMode
having values other than none(1) that are
not the same."
OBJECT etherWisDeviceRxTestPatternMode OBJECT etherWisDeviceRxTestPatternMode
SYNTAX INTEGER { SYNTAX INTEGER {
none(0), none(1),
mixedFrequency(3) mixedFrequency(4)
} }
DESCRIPTION DESCRIPTION
"Support for values other than none(0) "Support for values other than none(1)
and mixedFrequency(3) is not required." and mixedFrequency(4) is not required.
Furthermore, an implementation is not
required to allow assignment of a value
other than none(1) if that assignment
would result in this object and
etherWisDeviceTxTestPatternMode having
values other than none(1) that are
not the same."
GROUP etherWisDeviceGroupExtra GROUP etherWisDeviceGroupExtra
DESCRIPTION DESCRIPTION
"Implementation of this group, along with support for "Implementation of this group, along with support for
the value prbs31(2) for etherWisDeviceTxTestPatternMode the value prbs31(3) for etherWisDeviceTxTestPatternMode
and etherWisDeviceRxTestPatternMode, is necessary if the and etherWisDeviceRxTestPatternMode, is necessary if the
optional PRBS31 test pattern mode is to be supported." optional PRBS31 test pattern mode is to be supported."
OBJECT etherWisDeviceRxTestPatternErrors
WRITE-SYNTAX Gauge32 ( 0 )
DESCRIPTION
"An implementation is not required to
allow values other than zero to be
written to this object."
MODULE SONET-MIB MODULE SONET-MIB
MANDATORY-GROUPS { MANDATORY-GROUPS {
sonetMediumStuff2, sonetMediumStuff2,
sonetSectionStuff2, sonetSectionStuff2,
sonetLineStuff2, sonetLineStuff2,
sonetFarEndLineStuff2, sonetFarEndLineStuff2,
sonetPathStuff2, sonetPathStuff2,
sonetFarEndPathStuff2 sonetFarEndPathStuff2
} }
skipping to change at page 30, line 13 skipping to change at page 31, line 7
END END
5. Acknowledgments 5. Acknowledgments
This document is a product of the IETF Hubmib and AToMMIB Working This document is a product of the IETF Hubmib and AToMMIB Working
Groups. It builds upon the work of the IEEE P802.3ae 10 Gigabit Groups. It builds upon the work of the IEEE P802.3ae 10 Gigabit
Ethernet Task Force. Ethernet Task Force.
6. Security Considerations 6. Security Considerations
There are five management objects defined in this MIB that have a There are five managed objects defined in this MIB module that have a
MAX-ACCESS clause of read-write: etherWisDeviceTxTestPatternMode, MAX-ACCESS clause of read-write: etherWisDeviceTxTestPatternMode,
etherWisDeviceRxTestPatternMode, etherWisDeviceRxTestPatternErrors, etherWisDeviceRxTestPatternMode, etherWisDeviceRxTestPatternErrors,
etherWisSectionCurrentJ0Transmitted, and etherWisSectionCurrentJ0Transmitted, and
etherWisPathCurrentJ1Transmitted. Setting these objects can have the etherWisPathCurrentJ1Transmitted. Writing to these objects can have
following potentially disruptive effects on network operation: the following potentially disruptive effects on network operation:
o changing the transmit or receive test pattern mode or modifying o changing the transmit or receive test pattern mode or modifying
the accumulated error count from a PRBS31 pattern test on an the accumulated error count from a PRBS31 pattern test on an
administratively disabled 10GBASE-W interface, which can administratively disabled 10GBASE-W interface, which can
interfere with an in-progress pattern test; interfere with an in-progress pattern test;
o modifying the transmitted section trace and/or path trace o modifying the transmitted section trace and/or path trace
message on an operational 10GBASE-W interface, which can cause message on an operational 10GBASE-W interface, which can cause
connectivity alarms to be raised at the remote of the link. connectivity alarms to be raised at the remote of the link.
Such objects may be considered sensitive or vulnerable in some The user of this MIB module must therefore be aware that support for
network environments. The support for SET operations in a non-secure SET operations in a non-secure environment without proper protection
environment without proper protection can have a negative effect on can have a negative effect on network operations.
network operations.
SNMPv1 by itself is not a secure environment. Even if the network All other managed objects in this MIB module have a MAX-ACCESS clause
itself is secure (for example by using IPSec), even then, there is no of read-only. The information contained in those objects may be
control as to who on the secure network is allowed to access and considered sensitive in some network environments. In such
GET/SET (read/change) the objects in this MIB. environments it is important to control even GET access to those
objects and possibly to even encrypt the values of these objects when
sending them over the network via SNMP.
It is recommended that the implementers consider the security SNMP versions prior to SNMPv3 did not include adequate security.
features as provided by the SNMPv3 framework. Specifically, the use Even if the network itself is secure (for example by using IPSec),
of the User-based Security Model RFC 2574 [RFC2574] and the View- even then, there is no control as to who on the secure network is
based Access Control Model RFC 2575 [RFC2575] is recommended. allowed to access and GET/SET (read/change/create/delete) the objects
in this MIB module.
It is then a customer/user responsibility to ensure that the SNMP It is RECOMMENDED that implementers consider the security features as
entity giving access to an instance of this MIB, is properly provided by the SNMPv3 framework (see [RFC2570bis], section 8),
configured to give access to the objects only to those principals inluding full support for the SNMPv3 cryptographic mechanisms (for
(users) that have legitimate rights to indeed GET or SET authentication and privacy).
(change/create/delete) them.
Further, deployment of SNMP versions prior to SNMPv3 is NOT
RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to
enable cryptographic security. It is a customer/operator
responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module, is properly configured to give access to
the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them.
7. References 7. References
7.1. Normative References 7.1. Normative References
[RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
for Describing SNMP Management Frameworks", RFC 2571, April Requirements Levels", BCP 14, RFC 2119, March 1997.
1999.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M., and S. Waldbusser, "Structure of Management Rose, M., and S. Waldbusser, "Structure of Management
Information Version 2 (SMIv2)", STD 58, RFC 2578, April Information Version 2 (SMIv2)", STD 58, RFC 2578, April
1999. 1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M., and S. Waldbusser, "Textual Conventions for Rose, M., and S. Waldbusser, "Textual Conventions for
SMIv2", STD 58, RFC 2579, April 1999. SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M., and S. Waldbusser, "Conformance Statements for Rose, M., and S. Waldbusser, "Conformance Statements for
SMIv2", STD 58, RFC 2580, April 1999. SMIv2", STD 58, RFC 2580, April 1999.
[RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Transport Mappings for Version 2 of the Simple Network
Management Protocol (SNMPv2)", RFC 1906, January 1996.
[RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message
Processing and Dispatching for the Simple Network Management
Protocol (SNMP)", RFC 2572, April 1999.
[RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model
(USM) for version 3 of the Simple Network Management
Protocol (SNMPv3)", RFC 2574, April 1999.
[RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Protocol Operations for Version 2 of the Simple Network
Management Protocol (SNMPv2)", RFC 1905, January 1996.
[RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications",
RFC 2573, April 1999.
[RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based
Access Control Model (VACM) for the Simple Network
Management Protocol (SNMP)", RFC 2575, April 1999.
[RFC2863] McCloghrie, K., and F. Kastenholz, "The Interfaces Group [RFC2863] McCloghrie, K., and F. Kastenholz, "The Interfaces Group
MIB", RFC 2863, June 2000. MIB", RFC 2863, June 2000.
[RFC2864] McCloghrie, K., and G. Hanson, "The Inverted Stack Table [RFC2864] McCloghrie, K., and G. Hanson, "The Inverted Stack Table
Extension to the Interfaces Group MIB", RFC 2864, June 2000. Extension to the Interfaces Group MIB", RFC 2864, June 2000.
[SONETng] Tesink, K., "Definitions of Managed Objects for the [SONETng] Tesink, K., "Definitions of Managed Objects for the
SONET/SDH Interface Type", <draft-ietf-atommib-rfc2558bis- SONET/SDH Interface Type", <draft-ietf-atommib-rfc2558bis-
00.txt>, work in progress. 00.txt>, work in progress.
skipping to change at page 32, line 24 skipping to change at page 32, line 47
Performance Monitoring, ANSI T1.231-1997, September 1997. Performance Monitoring, ANSI T1.231-1997, September 1997.
[ETHERIF] Flick, J., "Definitions of Managed Objects for the [ETHERIF] Flick, J., "Definitions of Managed Objects for the
Ethernet-like Interface Types", <draft-ietf-hubmib-etherif- Ethernet-like Interface Types", <draft-ietf-hubmib-etherif-
mib-v3-01.txt>, work in progress. mib-v3-01.txt>, work in progress.
[MAU-MIB] Flick, J., "Definitions of Managed Objects for IEEE 802.3 [MAU-MIB] Flick, J., "Definitions of Managed Objects for IEEE 802.3
Medium Attachment Units (MAUs)", <draft-ietf-hubmib-mau- Medium Attachment Units (MAUs)", <draft-ietf-hubmib-mau-
mib-v3-01.txt>, work in progress. mib-v3-01.txt>, work in progress.
[P802.3ae] Institute of Electrical and Electronic Engineers, IEEE Draft [802.3ae] Institute of Electrical and Electronic Engineers, IEEE Std
P802.3ae/D5.0, "Supplement to Carrier Sense Multiple Access 802.3ae-2002, "IEEE Standard for Carrier Sense Multiple
with Collision Detection (CSMA/CD) Access Method & Physical Access with Collision Detection (CSMA/CD) Access Method and
Layer Specifications - Media Access Control (MAC) Physical Layer Specifications - Media Access Control (MAC)
Parameters, Physical Layer, and Management Parameters for 10 Parameters, Physical Layer and Management Parameters for 10
Gb/s Operation", May 1, 2002, work in progress. Gb/s Operation", August 2002.
7.2. Informative References 7.2. Informative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2570bis]
Requirements Levels", BCP 14, RFC 2119, March 1997. Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for Internet-
[RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification Standard Management Framework", <draft-ietf-snmpv3-
of Management Information for TCP/IP-based Internets", STD rfc2570bis-03.txt>, work in progress.
16, RFC 1155, May 1990.
[RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD
16, RFC 1212, March 1991.
[RFC1215] Rose, M., "A Convention for Defining Traps for use with the
SNMP", RFC 1215, March 1991.
[RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple
Network Management Protocol", STD 15, RFC 1157, May 1990.
[RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
"Introduction to Community-based SNMPv2", RFC 1901, January
1996.
[RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction to Version 3 of the Internet-standard Network
Management Framework", RFC 2570, April 1999.
8. Authors' Addresses 8. Authors' Addresses
Mike Ayers Mike Ayers
1204 Knox Ave. 1204 Knox Ave.
San Jose, CA 95122 San Jose, CA 95122
USA USA
Phone: +1 408 857 6810 Phone: +1 408 857 6810
EMail: mike.ayers@earthling.net EMail: mike.ayers@earthling.net
skipping to change at page 35, line 8 skipping to change at page 35, line 8
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary copyrights, patents or patent applications, or other proprietary
rights which may cover technology that may be required to practice rights which may cover technology that may be required to practice
this standard. Please address the information to the IETF Executive this standard. Please address the information to the IETF Executive
Director. Director.
Appendix A: Collection of Performance Data Using WIS MDIO Registers Appendix A: Collection of Performance Data Using WIS MDIO Registers
The purpose of this appendix is to illustrate how the WIS MDIO The purpose of this appendix is to illustrate how the WIS MDIO
registers specified in [P802.3ae] subclause 45.2.2 (and more registers specified in [802.3ae] subclause 45.2.2 (and more
specifically the subset required by [P802.3ae] subclause 50.3.11) can specifically the subset required by [802.3ae] subclause 50.3.11) can
be used to collect performance data either according to the be used to collect performance data either according to the
conventions adopted by this document or according to the conventions conventions adopted by this document or according to the conventions
specified in [P802.3ae] Clause 30. specified in [802.3ae] Clause 30.
For an agent implementing the SNMP managed objects required by this For an agent implementing the SNMP managed objects required by this
document the first step in collecting WIS performance data would be document the first step in collecting WIS performance data would be
to poll the 10G WIS status 3 register and the various error count to poll the 10G WIS status 3 register and the various error count
registers (10G WIS section BIP error count, 10G WIS line BIP errors, registers (10G WIS section BIP error count, 10G WIS line BIP errors,
10G WIS far end line BIP errors, 10G WIS path block error count, and 10G WIS far end line BIP errors, 10G WIS path block error count, and
10G WIS far end path block error count) once per second. The 10G WIS 10G WIS far end path block error count) once per second. The 10G WIS
status 3 register bits are all latched until read and so would status 3 register bits are all latched until read and so would
indicate whether a given defect occurred any time during the previous indicate whether a given defect occurred any time during the previous
second. The error count registers roll over modulo 2^16 or 2^32, and second. The error count registers roll over modulo 2^16 or 2^32, and
skipping to change at page 35, line 45 skipping to change at page 35, line 45
Implementations that conform to [T1.231] would end each 15-minute Implementations that conform to [T1.231] would end each 15-minute
interval on time-of-day clock 1/4 hour boundaries; if the delay-line interval on time-of-day clock 1/4 hour boundaries; if the delay-line
approach is used then a time-of-day timestamp would accompany the approach is used then a time-of-day timestamp would accompany the
one-second statistics. At the end of each interval the current one-second statistics. At the end of each interval the current
registers would be pushed onto the history stack and then would be registers would be pushed onto the history stack and then would be
cleared. The xyxIntervalValidData flags would be set to False(2) if cleared. The xyxIntervalValidData flags would be set to False(2) if
the number of samples was not between 890 and 910 or, in the case of the number of samples was not between 890 and 910 or, in the case of
far-end counts, if a near-end defect occurred during the just- far-end counts, if a near-end defect occurred during the just-
completed interval (see [T1.231] Section 9.1.2.2 for details). completed interval (see [T1.231] Section 9.1.2.2 for details).
An agent implementing the [P802.3ae] Clause 30 oWIS objects could An agent implementing the [802.3ae] Clause 30 oWIS objects could also
also start by polling the 10G WIS status 3 register and the various start by polling the 10G WIS status 3 register and the various error
error count registers to find the defects and error counts for the count registers to find the defects and error counts for the previous
previous second, and it could determine the number of errors and second, and it could determine the number of errors and whether the
whether the second was an errored second, a severely errored second, second was an errored second, a severely errored second, or a
or a severely errored frame second in the same manner as above. The severely errored frame second in the same manner as above. The rest
rest of the process would simply be to increment the generalized of the process would simply be to increment the generalized non-
non-resetable counters without consideration of any inhibiting rules. resetable counters without consideration of any inhibiting rules.
Full Copyright Statement Full Copyright Statement
Copyright (C) The Internet Society (2002). All Rights Reserved. Copyright (C) The Internet Society (2002). All Rights Reserved.
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
skipping to change at page 41, line 5 skipping to change at page 40, line 42
1.) "tx" and "rx" were spelled out in the MDIO register names in 1.) "tx" and "rx" were spelled out in the MDIO register names in
Section 3.7 in order to match the usage in P802.3ae/D4.3 and Section 3.7 in order to match the usage in P802.3ae/D4.3 and
P802.3ae/D5.0. P802.3ae/D5.0.
2.) References [IEEE 802.3 Std] in the MIB module and [P802.3ae] 2.) References [IEEE 802.3 Std] in the MIB module and [P802.3ae]
in the text were updated to point to P802.3ae/D5.0. in the text were updated to point to P802.3ae/D5.0.
3.) Author contact information was updated. 3.) Author contact information was updated.
The following changes were made to <draft-ietf-hubmib-wis-mib-04.txt>
to produce <draft-ietf-hubmib-wis-mib-05.txt>:
1.) Gauge32 was added to the IMPORTS list. It was not being
imported from SNMPv2-SMI as required by RFC 2578.
2.) Enum values for etherWisDeviceTxTestPatternMode and
etherWisDeviceTxTestPatternMode now start at 1 instead of 0, as
recommended by RFC 2578.
3.) The OBJECT clauses for etherWisDeviceTxTestPatternMode and
etherWisDeviceRxTestPatternMode now state that an implementation
does not have to allow value assignments that the Clause 45 MDIO
registers can't support.
4.) An OBJECT clause for etherWisDeviceRxTestPatternErrors was
added to specify that the WRITE-SYNTAX is Gauge32(0).
5.) A paragraph warning that some environments may consider the
information in read-only objects to be sensitive was added to the
Security Considerations section, and the entire section was
updated to conform to the latest template posted to the
mibs@ops.ietf.org mailing list.
6.) The acronyms in Section 3 were expanded on first use.
7.) All occurrences of "ifAdminState" were changed to
"ifAdminStatus".
8.) The DESCRIPTION clauses for etherWisPathCurrentJ1Transmitted
and etherWisSectionCurrentJ0Transmitted were changed to use
"transmitted" in place of "to be transmitted".
9.) All remaining instances of "SHALL" were changed to "MUST" in
Sections 3.8.1, 3.8.2, 3.8.3, and 3.8.4 in order to improve
readability.
10.) The reference tag [P802.3ae] was replaced with [802.3ae], and
the corresponding normative reference was updated to point to IEEE
Std 802.3ae-2002, published 30 Aug 2002. The reference [IEEE
802.3 Std] in the MIB module was similarly updated.
11.) RFC 2119 was moved from the informative reference list to the
normative reference list, in accordance with current IESG and RFC
Editor policy.
12.) The MIB boilerplate in Section 2 and the SMI/SNMP-related
references were updated to conform to the latest template posted
to the mibs@ops.ietf.org mailing list.
13.) The DESCRIPTION clause of the MODULE-IDENTITY invocation was
updated to include the required copyright statement.
14.) The dates in the LAST-UPDATED and REVISION clauses of the
MODULE-IDENTITY invocation were changed to the current date.
15.) The document pagination was changed to match that expected
upon publication as an RFC.
To-Do List To-Do List
NOTE TO RFC Editor: prior to publishing this document please take NOTE TO RFC Editor: prior to publishing this document please take
care of any open items listed below and then remove this section. care of any open items listed below and then remove this section.
1.) All occurrences of "IEEE Draft P802.3ae/D5.0" must be changed 1.) Normative references [SONETng], [ETHERIF], and [MAU-MIB] must
to "IEEE Std 802.3ae" once the standard has been approved, the
approval date must replace the draft publication date, and all
occurrences of the reference tag [P802.3ae] must be changed to
[802.3ae]. Note that this draft is referenced both in Section 4,
"Object Definitions", and in Section 7.1, "Normative References".
2.) Normative references [SONETng], [ETHERIF], and [MAU-MIB] must
be updated to point to the appropriate RFCs when the respective be updated to point to the appropriate RFCs when the respective
Internet Drafts are published, and all occurrences of the Internet Drafts are published, and all occurrences of the
reference tags must be changed to [RFCnnnn] where nnnn is the reference tags must be changed to [RFCnnnn] where nnnn is the
assigned RFC number. assigned RFC number.
Table of Contents 2.) Informative reference [2570bis] should be updated to point to
the appropriate RFC when the corresponding Internet Draft is
published, and the reference tag should be changed to match.
1 Conventions ............................................... 2 3.) It must be determined whether members of WIS MIB design team
2 The SNMP Management Framework ............................. 2 other than editor C. M. Heard will continue to be listed in the
3 Overview .................................................. 3 front page as co-authors or whether they will be listed in a
3.1 Relationship to the SONET/SDH Interface MIB ............. 4 Contributors section with contact information, in a Contributors
3.2 Relationship to the Ethernet-like Interface MIB ......... 4 section without contact information, or in the Acknowledgments
3.3 Relationship to the 802.3 MAU MIB ....................... 4 section.
3.4 Use of the ifTable ...................................... 5
3.4.1 Layering Model ........................................ 5
3.4.2 Use of ifTable for LLC Layer/MAC
Layer/Reconciliation Sublayer/Physical Coding
Sublayer ............................................... 5
3.4.3 Use of ifTable for SONET/SDH Path Layer ............... 5
3.4.4 Use of ifTable for SONET/SDH Medium/Section/Line
Layer .................................................. 6
3.5 SONET/SDH Terminology ................................... 6
3.6 Mapping of IEEE 802.3 Managed Objects ................... 7
3.7 Mapping of SNMP Objects to WIS Station Management
Registers .............................................. 12
3.8 Structure of the MIB Module ............................. 14
3.8.1 etherWisDeviceTable ................................... 14
3.8.2 etherWisSectionCurrentTable ........................... 14
3.8.3 etherWisPathCurrentTable .............................. 15
3.8.4 etherWisFarEndPathCurrentTable ........................ 15
4 Object Definitions ........................................ 16
5 Acknowledgments ........................................... 30
6 Security Considerations ................................... 30
7 References ................................................ 31
7.1 Normative References .................................... 31
7.2 Informative References .................................. 32
8 Authors' Addresses ........................................ 33
9 Intellectual Property ..................................... 34
Appendix A: Collection of Performance Data Using WIS
MDIO Registers ......................................... 35
Full Copyright Statement ................................... 36
 End of changes. 

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