draft-ietf-hubmib-wis-mib-01.txt   draft-ietf-hubmib-wis-mib-02.txt 
Hubmib and AToMMIB Working Groups Mike Ayers Ethernet Interfaces and Hub MIB Working Group Mike Ayers
INTERNET DRAFT BMC Software, Inc. INTERNET DRAFT BMC Software, Inc.
John Flick John Flick
Hewlett-Packard Company Hewlett-Packard Company
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
Enterasys Networks Enterasys Networks
Kaj Tesink Kaj Tesink
Telcordia Technologies Telcordia Technologies
November 20, 2001 February 18, 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-01.txt> <draft-ietf-hubmib-wis-mib-02.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 1, line 44 skipping to change at page 1, line 44
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html http://www.ietf.org/shadow.html
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2001). All Rights Reserved. Copyright (C) The Internet Society (2002). All Rights Reserved.
1. Abstract 1. Abstract
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) [P802.3ae]. Ethernet Wide Area Network (WAN) Interface Sublayer (WIS) [P802.3ae].
The MIB module defined in this memo is implemented in conjunction The MIB module defined in this memo is implemented in conjunction
with the Ethernet-like Interface MIB [ETHERIF], the 802.3 Medium with the Ethernet-like Interface MIB [ETHERIF], the 802.3 Medium
skipping to change at page 4, line 13 skipping to change at page 4, line 13
testing features required by Clause 50 of [P802.3ae]. testing features required by Clause 50 of [P802.3ae].
3.1. Relationship to the SONET MIB 3.1. Relationship to the SONET 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. An agent implementing the objects defined in this memo SONET MIB -- and its compliance statement REQUIRES that an agent
MUST implement the objects required by the sonetCompliance2 implementing the objects defined in this memo also implement the
conformance statement in the SONET MIB, and as further detailed in relevant SONET MIB objects. That includes all objects required by
the conformance statement in the MIB module defined in this memo. sonetCompliance2 as well as some that it leaves optional.
It should be noted that some of the objects incorporated by reference It should be noted that some of the objects incorporated by reference
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
skipping to change at page 5, line 13 skipping to change at page 5, line 13
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 [P802.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 | |
+-----------------------------+ + +-----------------------------+ +
| Path Layer | > 1 ifEntry | Path Layer | > 1 ifEntry
+-----------------------------+ + ifType: sonetPath(50) +-----------------------------+ + ifType: sonetPath(50)
| Line Layer | | | Line Layer | |
+-----------------------------+ | +-----------------------------+ |
skipping to change at page 6, line 40 skipping to change at page 6, line 40
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 [P802.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 WIS MUST path AIS and path LOP) only. An implementation of the MIB module
set the sonetPathSTSRDI bit in the appropriate instance of defined in this memo MUST set the sonetPathSTSRDI bit in the
sonetPathCurrentStatus when it receives an ERDI-P server defect appropriate instance of sonetPathCurrentStatus when it receives
indication from the remote end. Both ERDI-P payload defects and an ERDI-P server defect indication from the remote end. Both
ERDI-P server defects are reported in the object ERDI-P payload defects and ERDI-P server defects are reported in
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 [P802.3ae] the path layer CV count is based on block errors
and not BIP-8 errors, i.e., it is incremented only once for each and not BIP-8 errors, i.e., it is incremented only once for each
B3 byte that indicates incorrect parity, regardless of the number B3 byte that indicates incorrect parity, regardless of the number
of bits in error. Note that Section 8.4.5.1 of [T1.231] allows of 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
skipping to change at page 8, line 12 skipping to change at page 8, line 12
sonetPathIntervalCVs sonetPathIntervalCVs
aJ1ValueTX etherWisPathCurrentJ1Transmitted aJ1ValueTX etherWisPathCurrentJ1Transmitted
aJ1ValueRX etherWisPathCurrentJ1Received aJ1ValueRX etherWisPathCurrentJ1Received
aFarEndPathSESs SONET-MIB - sonetFarEndPathCurrentSESs + aFarEndPathSESs SONET-MIB - sonetFarEndPathCurrentSESs +
sonetFarEndPathIntervalSESs sonetFarEndPathIntervalSESs
aFarEndPathESs SONET-MIB - sonetFarEndPathCurrentESs + aFarEndPathESs SONET-MIB - sonetFarEndPathCurrentESs +
sonetFarEndPathIntervalESs sonetFarEndPathIntervalESs
aFarEndPathCVs SONET-MIB - sonetFarEndPathCurrentCVs + aFarEndPathCVs SONET-MIB - sonetFarEndPathCurrentCVs +
sonetFarEndPathIntervalCVs sonetFarEndPathIntervalCVs
Please note that the definitions of the threshold objects and counter It should be noted that the threshold and counter objects imported
objects imported from the SONET-MIB do not exactly match the from the SONET-MIB are not completely equivalent to the corresponding
definitions of the corresponding IEEE 802.3 objects. The specific IEEE 802.3 objects. The specific differences are as follows:
differences are as follows:
IEEE 802.3 Managed Object How Corresponding SNMP Object Differs IEEE 802.3 Managed Object How Corresponding SNMP Object Differs
oWIS - pWISOptional package oWIS - pWISOptional package
aSectionSESThreshold This object is defined in [P802.3ae] aSectionSESThreshold This object is defined in [P802.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
skipping to change at page 12, line 27 skipping to change at page 12, line 23
the WIS MDIO (Management Data Input/Output) registers defined in the WIS MDIO (Management Data Input/Output) registers defined in
[P802.3ae] subclause 45.2.2. The table below provides a cross- [P802.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.10 required to support from the subset in [P802.3ae] subclause 50.3.10 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 - etherWisDeviceTestPatternType 10G WIS Control 2
ETHER-WIS - etherWisDeviceRxTestPatternMode 10G WIS Control 2
ETHER-WIS - etherWisDeviceTxTestPatternMode 10G WIS Control 2 ETHER-WIS - etherWisDeviceTxTestPatternMode 10G WIS Control 2
ETHER-WIS - etherWisDeviceRxTestPatternMode 10G WIS Control 2
ETHER-WIS - etherWisDeviceRxTestPatternErrors 10G WIS Test Pattern
Error Counter
SONET-MIB - sonetMediumType none required SONET-MIB - sonetMediumType none required
SONET-MIB - sonetMediumTimeElapsed none required SONET-MIB - sonetMediumTimeElapsed none required
SONET-MIB - sonetMediumValidIntervals none required SONET-MIB - sonetMediumValidIntervals none required
SONET-MIB - sonetMediumLineCoding none required SONET-MIB - sonetMediumLineCoding none required
SONET-MIB - sonetMediumLineType none required SONET-MIB - sonetMediumLineType none required
SONET-MIB - sonetMediumCircuitIdentifier none required SONET-MIB - sonetMediumCircuitIdentifier none required
SONET-MIB - sonetMediumInvalidIntervals none required SONET-MIB - sonetMediumInvalidIntervals none required
SONET-MIB - sonetMediumLoopbackConfig none required SONET-MIB - sonetMediumLoopbackConfig none required
SONET-MIB - sonetSESthresholdSet none required SONET-MIB - sonetSESthresholdSet none required
skipping to change at page 14, line 25 skipping to change at page 14, line 25
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 WIS test features required by Clause 50 of [P802.3ae]. mandatory and optional WIS test features specified in [P802.3ae]
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 SHALL 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 SHALL 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 SHALL 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 SHALL 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 SHALL 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 SHALL 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 SHALL 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. SHALL 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 transmission
skipping to change at page 16, line 27 skipping to change at page 16, line 27
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 "200111202123Z" -- November 20, 2001 LAST-UPDATED "200202180140Z" -- February 18, 2002
ORGANIZATION "IETF Hubmib and AToMMIB Working Groups" ORGANIZATION "IETF Ethernet Interfaces and Hub MIB
Working Group"
CONTACT-INFO CONTACT-INFO
"Hubmib WG: "WG charter:
http://www.ietf.org/html.charters/hubmib-charter.html http://www.ietf.org/html.charters/hubmib-charter.html
AToMMIB WG: Chair: Dan Romascanu
http://www.ietf.org/html.charters/atommib-charter.html Postal: Avaya Inc.
Atidim Technology Park, Bldg. 3
Tel Aviv 61131
Israel
Tel: +972 3 645 8414
E-mail: dromasca@avaya.com
Editor: C. M. Heard Editor: C. M. Heard
Postal: 600 Rainbow Dr. #141 Postal: 600 Rainbow Dr. #141
Mountain View, CA 94041-2542 Mountain View, CA 94041-2542
USA USA
Tel: +1 650-964-8391 Tel: +1 650-964-8391
E-mail: heard@pobox.com" E-mail: heard@pobox.com"
DESCRIPTION DESCRIPTION
"The objects in this MIB module are used in conjunction "The objects in this MIB module are used in conjunction
with objects in the SONET-MIB and the MAU-MIB to manage with objects in the SONET-MIB and the MAU-MIB to manage
the Ethernet WAN Interface Sublayer (WIS). the Ethernet WAN Interface Sublayer (WIS).
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 IEEE Std 802.3, 2000 Edition: 'IEEE Standard for
for Information technology - Information technology - Telecommunications and
Telecommunications and information exchange information exchange between systems - Local and
between systems - Local and metropolitan metropolitan area networks - Specific requirements -
area networks - Specific requirements - Part 3: Carrier sense multiple access with collision
Part 3: Carrier sense multiple access with detection (CSMA/CD) access method and physical layer
collision detection (CSMA/CD) access method specifications', as amended by IEEE Draft P802.3ae/D4.01:
and physical layer specifications', as 'Supplement to Carrier Sense Multiple Access with
amended by IEEE Draft P802.3ae/D3.3: Collision Detection (CSMA/CD) Access Method & Physical
'Supplement to Carrier Sense Multiple Access Layer Specifications - Media Access Control (MAC)
with Collision Detection (CSMA/CD) Access Parameters, Physical Layer, and Management Parameters
Method & Physical Layer Specifications - for 10 Gb/s Operation', February 4, 2002.
Media Access Control (MAC) Parameters,
Physical Layer, and Management Parameters
for 10 Gb/s Operation', October 23, 2001.
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 "200111202123Z" -- November 20, 2001 REVISION "200202180140Z" -- February 18, 2002
DESCRIPTION "Initial version." DESCRIPTION "Initial version, published as RFC yyyy."
-- RFC Ed.: replace yyyy with actual RFC number & remove this notice
::= { transmission XXX } -- to be assigned by IANA ::= { transmission XXX }
-- RFC Ed.: replace XXX with IANA-assigned number & remove this notice
- <span class="insert">RFC Ed.: replace XXX with IANA-assigned number &amp; remove this notice</span>
-- 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 23 skipping to change at page 18, line 23
DESCRIPTION DESCRIPTION
"The table for Ethernet WIS devices" "The table for Ethernet WIS devices"
::= { etherWisDevice 1 } ::= { etherWisDevice 1 }
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 shall 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 {
etherWisDeviceTestPatternType INTEGER, etherWisDeviceTxTestPatternMode INTEGER,
etherWisDeviceRxTestPatternMode INTEGER, etherWisDeviceRxTestPatternMode INTEGER,
etherWisDeviceTxTestPatternMode INTEGER etherWisDeviceRxTestPatternErrors Gauge32
} }
etherWisDeviceTestPatternType OBJECT-TYPE etherWisDeviceTxTestPatternMode OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
mixedFrequency(0), none(0),
squareWave(1) squareWave(1),
prbs31(2),
mixedFrequency(3)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable controls the type of test pattern. The value "This variable controls the transmit test pattern mode.
mixedFrequency(0) selects the framed mixed frequency test The value none(0) puts the the WIS transmit path into
pattern specified in [IEEE 802.3 Std.] subclause 50.3.8.2. the normal operating mode. The value squareWave(1) puts
The value squareWave(1) selects the unframed square wave test the WIS transmit path into the square wave test pattern
pattern specified 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
PRBS31 test pattern mode described in [IEEE 802.3 Std.]
subclause 50.3.8.2. The value mixedFrequency(3) puts the
WIS transmit path into the mixed frequency test pattern
mode described in [IEEE 802.3 Std.] subclause 50.3.8.3.
Any attempt to set this object to a value other than
none(0) when the corresponding instance of ifAdminState
has the value up(1) MUST be rejected with the error
inconsistentValue, and any attempt to set the corresponding
instance of ifAdminStatus to the value up(1) when an
instance of this object has a value other than none(0)
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.6.1, Test pattern (2.7.3)." 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 {
disabled(0), none(0),
enabled(1) prbs31(2),
mixedFrequency(3)
} }
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 disabled(0) sets the WIS receive path into The value none(0) puts the the WIS receive path into the
normal mode. The value enabled(1) sets the WIS receive normal operating mode. The value prbs31(2) puts the WIS
path into test pattern mode. An attempt to set this receive path into the PRBS31 test pattern mode described
object to enabled(1) when the corresponding instance in [IEEE 802.3 Std.] subclause 50.3.8.2. The value
of ifAdminState has the value up(1) SHALL be rejected mixedFrequency(3) puts the WIS receive path into the mixed
with the error inconsistentValue. An attempt to set the frequency test pattern mode described in [IEEE 802.3 Std.]
corresponding instance of ifAdminStatus to the value subclause 50.3.8.3. Any attempt to set this object to a
up(1) when an instance of this object has the value value other than none(0) when the corresponding instance
enabled(1) SHALL be rejected with the error of ifAdminState has the value up(1) MUST be rejected with
inconsistentValue." the error inconsistentValue, and any attempt to set the
corresponding instance of ifAdminStatus to the value up(1)
when an instance of this object has a value other than
none(0) 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.6.2, Receive test pattern mode (2.7.2)." 45.2.2.7.2, PRBS31 pattern testing ability (2.8.1)."
::= { etherWisDeviceEntry 2 } ::= { etherWisDeviceEntry 2 }
etherWisDeviceRxTestPatternErrors OBJECT-TYPE
etherWisDeviceTxTestPatternMode OBJECT-TYPE SYNTAX Gauge32 ( 0..65535 )
SYNTAX INTEGER {
disabled(0),
enabled(1)
}
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable controls the transmit test pattern mode. "This object counts the number of errors detected when the
The value disabled(0) set the WIS transmit path into WIS receive path is operating in the PRBS31 test pattern
normal mode. The value enabled(1) sets the WIS transmit mode. It is reset to zero when the WIS receive path
path into test pattern mode. An attempt to set this initially enters that mode, and it increments each time
object to enabled(1) when the corresponding instance the PRBS pattern checker detects an error as described in
of ifAdminState has the value up(1) SHALL be rejected [IEEE 802.3 Std.] subclause 50.3.8.2 unless its value is
with the error inconsistentValue. An attempt to set the 65535, in which case it remains unchanged. This object is
corresponding instance of ifAdminStatus to the value writeable so that it may be reset upon explicit request
up(1) when an instance of this object has the value of a command generator application while the WIS receive
enabled(1) SHALL be rejected with the error path continues to operate in PRBS31 test pattern mode."
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.7.2, PRBS31 pattern testing ability
45.2.2.6.3, Transmit test pattern mode (2.7.1)." (2.8.1), and 45.2.2.8 10G WIS test pattern error counter
register (2.9)."
::= { etherWisDeviceEntry 3 } ::= { etherWisDeviceEntry 3 }
-- The Section group -- The Section group
-- These objects provide WIS extensions to -- These objects provide WIS extensions to
-- the SONET-MIB Section Group. -- the SONET-MIB Section Group.
etherWisSectionCurrentTable OBJECT-TYPE etherWisSectionCurrentTable OBJECT-TYPE
SYNTAX SEQUENCE OF EtherWisSectionCurrentEntry SYNTAX SEQUENCE OF EtherWisSectionCurrentEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The table for the current state of Ethernet WIS sections." "The table for the current state of Ethernet WIS sections."
::= { etherWisSection 1 } ::= { etherWisSection 1 }
etherWisSectionCurrentEntry OBJECT-TYPE etherWisSectionCurrentEntry OBJECT-TYPE
SYNTAX EtherWisSectionCurrentEntry SYNTAX EtherWisSectionCurrentEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the etherWisSectionCurrentTable. For each "An entry in the etherWisSectionCurrentTable. For each
instance of this object there shall be a corresponding instance of this object there MUST be a corresponding
instance of sonetSectionCurrentEntry." instance of sonetSectionCurrentEntry."
INDEX { ifIndex } INDEX { ifIndex }
::= { etherWisSectionCurrentTable 1 } ::= { etherWisSectionCurrentTable 1 }
EtherWisSectionCurrentEntry ::= EtherWisSectionCurrentEntry ::=
SEQUENCE { SEQUENCE {
etherWisSectionCurrentJ0Transmitted INTEGER, etherWisSectionCurrentJ0Transmitted OCTET STRING,
etherWisSectionCurrentJ0Received INTEGER etherWisSectionCurrentJ0Received OCTET STRING
} }
etherWisSectionCurrentJ0Transmitted OBJECT-TYPE etherWisSectionCurrentJ0Transmitted OBJECT-TYPE
SYNTAX INTEGER ( 0..255 ) SYNTAX OCTET STRING (SIZE (16))
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is the single-octet section trace message "This is the 16-octet section trace message that is
that is to be transmitted in the J0 byte. The to be transmitted in the J0 byte. The value SHOULD
value SHOULD be set to '01'h when the section be fifteen octets of '00'h followed by '89'h
(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 as a default if no other SHOULD use that value (or a cyclic shift thereof)
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 INTEGER ( 0..255 ) SYNTAX OCTET STRING (SIZE (16))
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This is the single-octet section trace message "This is the 16-octet section trace message that
that was most recently received in the J0 byte." was most recently received in the J0 byte."
REFERENCE REFERENCE
"[IEEE 802.3 Std.], 30.8.1.1.9, aJ0ValueRX." "[IEEE 802.3 Std.], 30.8.1.1.9, aJ0ValueRX."
::= { etherWisSectionCurrentEntry 2 } ::= { etherWisSectionCurrentEntry 2 }
-- The Path group -- The Path group
-- These objects provide WIS extensions to -- These objects provide WIS extensions to
-- the SONET-MIB Path Group. -- the SONET-MIB Path Group.
etherWisPathCurrentTable OBJECT-TYPE etherWisPathCurrentTable OBJECT-TYPE
skipping to change at page 21, line 34 skipping to change at page 22, line 34
DESCRIPTION DESCRIPTION
"The table for the current state of Ethernet WIS paths." "The table for the current state of Ethernet WIS paths."
::= { etherWisPath 1 } ::= { etherWisPath 1 }
etherWisPathCurrentEntry OBJECT-TYPE etherWisPathCurrentEntry OBJECT-TYPE
SYNTAX EtherWisPathCurrentEntry SYNTAX EtherWisPathCurrentEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the etherWisPathCurrentTable. For each "An entry in the etherWisPathCurrentTable. For each
instance of this object there shall be a corresponding instance of this object there MUST be a corresponding
instance of sonetPathCurrentEntry." instance of sonetPathCurrentEntry."
INDEX { ifIndex } INDEX { ifIndex }
::= { etherWisPathCurrentTable 1 } ::= { etherWisPathCurrentTable 1 }
EtherWisPathCurrentEntry ::= EtherWisPathCurrentEntry ::=
SEQUENCE { SEQUENCE {
etherWisPathCurrentStatus BITS, etherWisPathCurrentStatus BITS,
etherWisPathCurrentJ1Transmitted OCTET STRING, etherWisPathCurrentJ1Transmitted OCTET STRING,
etherWisPathCurrentJ1Received OCTET STRING etherWisPathCurrentJ1Received OCTET STRING
} }
skipping to change at page 23, line 9 skipping to change at page 24, line 9
the path layer itself, there is no the path layer itself, there is no
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 message that is to "This is the 16-octet path trace message that is to
be transmitted in the J1 byte. The value SHOULD be transmitted in the J1 byte. The value SHOULD
be fifteen octets of '00'h followed by '89'h be fifteen octets of '00'h followed by '89'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 }
skipping to change at page 24, line 10 skipping to change at page 25, line 10
DESCRIPTION DESCRIPTION
"The table for the current far-end state of Ethernet WIS "The table for the current far-end state of Ethernet WIS
paths." paths."
::= { etherWisFarEndPath 1 } ::= { etherWisFarEndPath 1 }
etherWisFarEndPathCurrentEntry OBJECT-TYPE etherWisFarEndPathCurrentEntry OBJECT-TYPE
SYNTAX EtherWisFarEndPathCurrentEntry SYNTAX EtherWisFarEndPathCurrentEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the etherWisFarEndPathCurrentTable. For each "An entry in the etherWisFarEndPathCurrentTable. For each
instance of this object there shall be a corresponding instance of this object there MUST be a corresponding
instance of sonetFarEndPathCurrentEntry." instance of sonetFarEndPathCurrentEntry."
INDEX { ifIndex } INDEX { ifIndex }
::= { etherWisFarEndPathCurrentTable 1 } ::= { etherWisFarEndPathCurrentTable 1 }
EtherWisFarEndPathCurrentEntry ::= EtherWisFarEndPathCurrentEntry ::=
SEQUENCE { SEQUENCE {
etherWisFarEndPathCurrentStatus BITS etherWisFarEndPathCurrentStatus BITS
} }
etherWisFarEndPathCurrentStatus OBJECT-TYPE etherWisFarEndPathCurrentStatus OBJECT-TYPE
skipping to change at page 25, line 14 skipping to change at page 26, line 14
-- --
-- Conformance Statements -- Conformance Statements
-- --
etherWisGroups OBJECT IDENTIFIER ::= { etherWisConformance 1 } etherWisGroups OBJECT IDENTIFIER ::= { etherWisConformance 1 }
etherWisCompliances OBJECT IDENTIFIER ::= { etherWisConformance 2 } etherWisCompliances OBJECT IDENTIFIER ::= { etherWisConformance 2 }
-- Object Groups -- Object Groups
etherWisDeviceGroup OBJECT-GROUP etherWisDeviceGroupBasic OBJECT-GROUP
OBJECTS { OBJECTS {
etherWisDeviceTestPatternType, etherWisDeviceTxTestPatternMode,
etherWisDeviceRxTestPatternMode, etherWisDeviceRxTestPatternMode
etherWisDeviceTxTestPatternMode
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects that control test "A collection of objects that support test
features required of all WIS devices." features required of all WIS devices."
::= { etherWisGroups 1 } ::= { etherWisGroups 1 }
etherWisDeviceGroupExtra OBJECT-GROUP
OBJECTS {
etherWisDeviceRxTestPatternErrors
}
STATUS current
DESCRIPTION
"A collection of objects that support
optional WIS device test features."
::= { etherWisGroups 2 }
etherWisSectionGroup OBJECT-GROUP etherWisSectionGroup OBJECT-GROUP
OBJECTS { OBJECTS {
etherWisSectionCurrentJ0Transmitted, etherWisSectionCurrentJ0Transmitted,
etherWisSectionCurrentJ0Received etherWisSectionCurrentJ0Received
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects that provide "A collection of objects that provide
required information about a WIS section." required information about a WIS section."
::= { etherWisGroups 2 } ::= { etherWisGroups 3 }
etherWisPathGroup OBJECT-GROUP etherWisPathGroup OBJECT-GROUP
OBJECTS { OBJECTS {
etherWisPathCurrentStatus, etherWisPathCurrentStatus,
etherWisPathCurrentJ1Transmitted, etherWisPathCurrentJ1Transmitted,
etherWisPathCurrentJ1Received etherWisPathCurrentJ1Received
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects that provide "A collection of objects that provide
required information about a WIS path." required information about a WIS path."
::= { etherWisGroups 3 } ::= { etherWisGroups 4 }
etherWisFarEndPathGroup OBJECT-GROUP etherWisFarEndPathGroup OBJECT-GROUP
OBJECTS { OBJECTS {
etherWisFarEndPathCurrentStatus etherWisFarEndPathCurrentStatus
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects that provide required "A collection of objects that provide required
information about the far end of a WIS path." information about the far end of a WIS path."
::= { etherWisGroups 4 } ::= { etherWisGroups 5 }
-- Compliance Statements -- Compliance Statements
etherWisCurrentCompliance MODULE-COMPLIANCE etherWisCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for this module." "The compliance statement for this module."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
etherWisDeviceGroup, etherWisDeviceGroupBasic,
etherWisSectionGroup, etherWisSectionGroup,
etherWisPathGroup, etherWisPathGroup,
etherWisFarEndPathGroup etherWisFarEndPathGroup
} }
OBJECT etherWisDeviceTxTestPatternMode
SYNTAX INTEGER {
none(0),
squareWave(1),
mixedFrequency(3)
}
DESCRIPTION
"Support for values other than none(0),
squareWave(1), and mixedFrequency(3)
is not required."
OBJECT etherWisDeviceRxTestPatternMode
SYNTAX INTEGER {
none(0),
mixedFrequency(3)
}
DESCRIPTION
"Support for values other than none(0)
and mixedFrequency(3) is not required."
GROUP etherWisDeviceGroupExtra
DESCRIPTION
"Implementation of this group, along with support for
the value prbs31(2) for etherWisDeviceTxTestPatternMode
and etherWisDeviceRxTestPatternMode, is necessary if the
optional PRBS31 test pattern mode is to be supported."
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 30 skipping to change at page 32, line 30
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirements Levels", BCP 14, RFC 2119, March 1997. Requirements Levels", BCP 14, RFC 2119, March 1997.
[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", rfc2558 update (forthcoming), SONET/SDH Interface Type", <draft-ietf-atommib-rfc2558bis-
work in progress. 00.txt>, work in progress.
[T1.231] American National Standard for Telecommunications - Digital [T1.231] American National Standard for Telecommunications - Digital
Hierarchy - Layer 1 In-Service Digital Transmission Hierarchy - Layer 1 In-Service Digital Transmission
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-00.txt>, work in progress. mib-v3-00.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-00.txt>, work in progress. mib-v3-00.txt>, work in progress.
[P802.3ae] Law, D., Editor, Draft Supplement to IEEE Std. 802.3, IEEE [P802.3ae] Law, D., Editor, Draft Supplement to IEEE Std. 802.3, IEEE
Draft P802.3ae/D3.3, October 23, 2001, work in progress. Draft P802.3ae/D4.01, February 4, 2002, work in progress.
8. Authors' Addresses 8. Authors' Addresses
Mike Ayers Mike Ayers
BMC Software, Inc. BMC Software, Inc.
2141 North First Street 2141 North First Street
San Jose, CA 95131 San Jose, CA 95131
USA USA
Phone: +1 408 546 0947 Phone: +1 408 546 0947
skipping to change at page 34, line 7 skipping to change at page 36, line 7
register and the various error count registers to find the defects register and the various error count registers to find the defects
and error counts for the previous second, and it could determine the and error counts for the previous second, and it could determine the
number of errors and whether the second was an errored second, a number of errors and whether the second was an errored second, a
severely errored second, or a severely errored frame second in the severely errored second, or a severely errored frame second in the
same manner as above. The rest of the process would be simply to same manner as above. The rest of the process would be simply to
increment the generalized non-resetable counters without increment the generalized non-resetable counters without
consideration of any inhibiting rules. consideration of any inhibiting rules.
Full Copyright Statement Full Copyright Statement
Copyright (C) The Internet Society (2001). 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
included on all such copies and derivative works. However, this included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of Internet organizations, except as needed for the purpose of
skipping to change at page 35, line 5 skipping to change at page 37, line 5
The limited permissions granted above are perpetual and will not be The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns. revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Revision History
NOTE TO RFC Editor: this section is to be removed prior to
publication as an RFC.
The following changes were made to <draft-ietf-hubmib-wis-mib-01.txt>
to produce <draft-ietf-hubmib-wis-mib-02.txt>:
1.) Section 3.1 was updated as agreed in "WIS MIB compliance
statement issue" e-mail thread, specifically to explain that the
ETHER-WIS compliance statement requires all objects that required
by sonetCompliance2 as well as some that it leaves optional.
2.) In Section 3.5 the paragraph dealing with STS-Path Remote
Defect Indication was updated to indicate that an implementation
of the WIS MIB (not necessarily an arbitrary implementation of the
WIS) has to set the SONET-MIB's RDI status bit when a remote
server defect is detected.
3.) In Section 3.6 the text introducing the table of semantic
differences between IEEE GDMO and SNMP objects was wordsmithed.
4.) In Section 3.7 the mapping between objects in the
etherWisDeviceTable and the station management registers was
updated to reflect the updated MDIO register definitions in
P802.3ae/D4.01 and the corresponding updates to the MIB objects.
5.) In Section 3.8.1 the text was updated to state that the
purpose of the etherWisDeviceTable is to support mandatory and
optional WIS test features.
6.) In Sections 3.8.1, 3.8.2, 3.8.3, and 3.8.4 certain instances
of "SHALL" were changed to "MUST" to improve readability.
7.) The LAST-UPDATED, ORGANIZATION, REVISION, and DESCRIPTION
clauses of the MODULE-IDENTITY invocation were updated.
8.) The lower-case "shall" in the DESCRIPTION clause of each table
entry was changed to an uppercase "MUST", per RFC 2119, because it
describes a requirement of the specification in the draft.
9.) The etherWisDeviceTestPatternType objects was removed, and the
objects etherWisDeviceTxTestPatternMode and
etherWisDeviceRxTestPatternMode were changed from simple
"enable/disable" flags to enumerations that reflect the specific
text pattern mode in which the transmitter or receiver is
operating. A new optional object called
etherWisDeviceRxTestPatternErrors was added to make visible the
error count MDIO register contents when the receiver is operating
in the (optional) PRBS31 test pattern mode added in D4.01.
10.) The SYNTAX of etherWisSectionCurrentJ0Transmitted and
etherWisSectionCurrentJ0Received was changed from INTEGER (0..255)
to OCTET STRING (SIZE (16)) to reflect the change from 1-byte to
16-byte section trace messages in D4.01, and the DESCRIPTION
clauses were rewritten along the lines for those of the
corresponding path trace objects.
11.) In the DESCRIPTION of etherWisPathCurrentJ0Transmitted "path
message" was changes to "path trace message".
12.) etherWisDeviceGroup was split into a mandatory group
etherWisDeviceGroupBasic and an optional group
etherWisDeviceGroupExtra.
13.) The compliance name was changed from
etherWisCurrentCompliance to etherWisCompliance.
14.) OBJECT clauses were added to specify required values for
etherWisDeviceTxTestPatternMode and
etherWisDeviceRxTestPatternMode.
15.) A GROUP clause was added to state that
etherWisDeviceGroupExtra needs to be implemented in order to
support the PRBS31 test pattern mode. The DESCRIPTION clause
points out that the prbs31 enumeration is needed for
etherWisDeviceTxTestPatternMode/etherWisDeviceRxTestPatternMode.
16). References [SONETng] and [P802.3ae] references were updated
to draft-ietf-atommib-rfc2558bis-00.txt and P802.3ae/D4.01,
respectively.
Table of Contents Table of Contents
1 Abstract ..................................................... 2 1 Abstract .................................................. 2
2 The SNMP Management Framework ................................ 2 2 The SNMP Management Framework ............................. 2
3 Overview ..................................................... 3 3 Overview .................................................. 3
3.1 Relationship to the SONET MIB .............................. 4 3.1 Relationship to the SONET MIB ........................... 4
3.2 Relationship to the Ethernet-like Interfaces MIB ........... 4 3.2 Relationship to the Ethernet-like Interfaces MIB ........ 4
3.3 Relationship to the 802.3 MAU MIB .......................... 4 3.3 Relationship to the 802.3 MAU MIB ....................... 4
3.4 Use of the ifTable ......................................... 4 3.4 Use of the ifTable ...................................... 4
3.4.1 Layering Model ........................................... 5 3.4.1 Layering Model ........................................ 5
3.4.2 Use of ifTable for LLC Layer/MAC Layer/Reconciliation 3.4.2 Use of ifTable for LLC Layer/MAC
Sublayer/Physical Coding Sublayer ......................... 5 Layer/Reconciliation Sublayer/Physical Coding
3.4.3 Use of ifTable for SONET/SDH Path Layer .................. 5 Sublayer ............................................... 5
3.4.4 Use of ifTable for SONET/SDH Medium/Section/Line Layer 3.4.3 Use of ifTable for SONET/SDH Path Layer ............... 5
........................................................... 5 3.4.4 Use of ifTable for SONET/SDH Medium/Section/Line
3.5 SONET/SDH Terminology ...................................... 6 Layer .................................................. 5
3.6 Mapping of IEEE 802.3 Managed Objects ...................... 7 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 3.7 Mapping of SNMP Objects to WIS Station Management
Registers ................................................. 12 Registers .............................................. 12
3.8 Structure of the MIB Module ................................ 14 3.8 Structure of the MIB Module ............................. 14
3.8.1 etherWisDeviceTable ...................................... 14 3.8.1 etherWisDeviceTable ................................... 14
3.8.2 etherWisSectionCurrentTable .............................. 14 3.8.2 etherWisSectionCurrentTable ........................... 14
3.8.3 etherWisPathCurrentTable ................................. 14 3.8.3 etherWisPathCurrentTable .............................. 14
3.8.4 etherWisFarEndPathCurrentTable ........................... 15 3.8.4 etherWisFarEndPathCurrentTable ........................ 15
4 Object Definitions ........................................... 16 4 Object Definitions ........................................ 16
5 Acknowledgments .............................................. 28 5 Acknowledgments ........................................... 30
6 Security Considerations ...................................... 28 6 Security Considerations ................................... 30
7 References ................................................... 29 7 References ................................................ 31
8 Authors' Addresses ........................................... 31 8 Authors' Addresses ........................................ 33
9 Intellectual Property ........................................ 32 9 Intellectual Property ..................................... 34
Appendix A: Collection of Performance Data Using WIS MDIO Appendix A: Collection of Performance Data Using WIS
Registers ................................................. 33 MDIO Registers ......................................... 35
Full Copyright Statement ...................................... 34 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/