INTERNET-DRAFT Editors of this version:Hubmib and AToMMIB Working Groups Mike Ayers INTERNET DRAFT BMC Software, Inc. John Flick Hewlett-Packard Company C. M. Heard Consultant Kam Lam Lucent Technologies Kerry McDonald CSU San BernardinoJohn Flick Hewlwett-Packard Company K.C.K. C. Norseth Enterasys Networks29 JuneKaj Tesink Telcordia Technologies November 20, 2001DefinitionDefinitions of Managed Objects for the Ethernet WAN Interface Sublayer<draft-ietf-hubmib-wis-mib-00.txt><draft-ietf-hubmib-wis-mib-01.txt> Status of this Memo This document is an Internet-Draft and is in full conformance with all provisions of Section 10 of RFC2026. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF), its areas, and its working groups. Note that other groups may also distribute working documents as Internet-Drafts. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." The list of current Internet-Drafts can be accessed at http://www.ietf.org/ietf/1id-abstracts.txt The list of Internet-Draft Shadow Directories can be accessed at http://www.ietf.org/shadow.html Copyright Notice Copyright (C) The Internet Society (2001). All Rights Reserved. 1. Abstract This document defines a portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP based internets. In particular, it defines objects for managing the Ethernet Wide Area Network (WAN) Interface Sublayer (WIS)for Ethernet systems which support it.[P802.3ae]. The MIB module defined in this memo is implemented in conjunction with the Ethernet-like Interface MIB [ETHERIF], the 802.3 Medium Attachment Unit MIB [MAU-MIB], the Interfaces Group MIB [RFC2863], and the Inverted Stack Tableof Contents 1. Introduction ................................................ 3MIB [RFC2864]. It also extends the SONET MIB [SONETng] and is implemented in conjunction with that MIB module. The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in [RFC2119]. 2.Overview .................................................... 4 3. Definitions ................................................. 4 4. Notice on Intellectual Property ............................. 20 5. Acknowledgments ............................................. 21 6. Security .................................................... 21 7. References .................................................. 22 8. Editor's Address ............................................ 23 9. Full Copyright Statement .................................... 23 1. IntroductionThe SNMP Management Frameworkat the time of this writingThe 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 inthis document. -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 Frameworkat the time of this writingcan be found in RFC 2570 [RFC2570]. Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. Objects in the MIB are defined using the mechanisms defined in the SMI. This memo specifies a MIB module that is compliant to the SMIv2. A MIB conforming to the SMIv1 can be produced through the appropriate translations. The resulting translated MIB must be semantically equivalent, except where objects or events are omitted because no 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.2. Overview TBD - Include sections and/or references on measurement methods.3.Definitions ETHER-WIS DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, Integer32, mib-2 FROM SNMPv2-SMI ifIndex FROM IF-MIB MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF; etherWisMIB MODULE-IDENTITY LAST-UPDATED "200107270000Z" ORGANIZATION "IETF Hubmib Working Group" CONTACT-INFO "Mike Ayers BMC Software Tel: +1 408-546-0947 email: mayers@bmc.com" DESCRIPTION "TheOverview The objects defined in this memo are used in conjunction with objects defined in the Interfaces Group MIBmodule[RFC2863], the SONET MIB [SONETng], and the MAU MIB [MAU-MIB] todescribe Ethernetmanage the WAN Interface Sublayer (WIS) defined in [P802.3ae]. The WISobjects" ::= { mib-2 XX } --contains functions to perform OC-192c/VC-4-64c framing and scrambling. It resides between the PCS and PMA sublayers within a 10GBASE-W 10 Gb/s WAN-compatible PHY and may beassignedused in conjunction with any of the PCS, PMA, and PMD sublayers that are defined in [P802.3ae] for 10GBASE-W PHYs. Three types of 10GBASE-W PHYs are defined, distinguished byIANA --the type of optics employed: 10GBASE-SW, 10GBASE-LW, and 10GBASE-EW. Themain sectionsobjects defined in this memo may be used to manage an Ethernet interface employing any type of 10GBASE-W PHY. They do not apply to any other kind of interface. In particular, they do not apply to so-called Ethernet Line Terminating Equipment (ELTE) residing within a SONET network element that uses themodule etherWisDevice OBJECT IDENTIFIER ::= { etherWisMIB 1 } etherWisSection OBJECT IDENTIFIER ::= { etherWisMIB 2 } etherWisLine OBJECT IDENTIFIER ::= { etherWisMIB 3 } etherWisPath OBJECT IDENTIFIER ::= { etherWisMIB 4 } etherWisConformance OBJECT IDENTIFIER ::= { etherWisMIB 5 } --10GBASE-W PMA/PMD sublayers but otherwise acts as SONET Line Terminating Equipment (LTE). TheDevice group -- Theseobjectsapply to functions which may be implemented inpresented here --devices which support more than one physical connection.along with those incorporated by reference from the Interfaces Group MIB, the SONET MIB, and the MAU MIB --Therefore, changesare intended tothese objects may affect instances other -- thanprovide exact representations of thechanged instance. etherWisDeviceTable OBJECT-TYPE SYNTAX SEQUENCE OF EtherWisDeviceEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The table for Ethernet WIS devices" ::= { etherWisDevice 1 } etherWisDeviceEntry OBJECT-TYPE SYNTAX EtherWisDeviceEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entrymandatory attributes in theEthernet WIS device table" INDEX { ifIndex } ::= { etherWisDeviceTable 1} EtherWisDeviceEntry ::= SEQUENCE { etherWisDeviceReset INTEGER, etherWisDeviceLoopback INTEGER, etherWisDeviceSpeedSelection INTEGER, etherWisDevicePowerDown INTEGER, etherWisDevicePresent INTEGER, etherWisDeviceModesAllowed INTEGER, etherWisDeviceModeSelect INTEGER, etherWisDeviceJitterTestMode INTEGER } etherWisDeviceReset OBJECT-TYPE SYNTAX INTEGER { running(0), reset(1) } MAX-ACCESS read-write STATUS current DESCRIPTION "This variable can be used to resetoWIS managed object class (i.e., theWIS. The interface may be unavailable whilemembers of thereset occurspWISBasic package) defined in Clause 30 anddata may be lost." ::= { etherWisDeviceEntry 1 } etherWisDeviceLoopback OBJECT-TYPE SYNTAX INTEGER { noLoopback(0), loopBack(1) } MAX-ACCESS read-write STATUS current DESCRIPTION "Setting this variableAnnex 30A of [P802.3ae]. They are also intended toloopback will cause data sent intoprovide approximate representations of theinterfaceoptional attributes (i.e., the members of the pWISOptional package). Some objects with no analogues in oWIS are defined to support WIS testing features required by Clause 50 of [P802.3ae]. 3.1. Relationship to the SONET MIB Since the Ethernet WAN Interface Sublayer was designed to bereturned onSONET- compatible, information similar to that provided by most of thesame interface." ::= { etherWisDeviceEntry 2 } etherWisDeviceSpeedSelection OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-write STATUS current DESCRIPTION "This variablemembers of the oWIS managed object class iscurrently being changed byavailable from objects defined in theIEEE." ::= { etherWisDeviceEntry 3 } etherWisDevicePowerDown OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-write STATUS current DESCRIPTION "This variableSONET MIB [SONETng]. Thus, the MIB module defined in this memo iscurrently being changed bya sparse augmentation of theIEEE." ::= { etherWisDeviceEntry 4 } etherWisDevicePresent OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STATUS current DESCRIPTION "This variableSONET MIB -- in other words, every table defined here iscurrently being changedan extension of some table in the SONET MIB. An agent implementing the objects defined in this memo MUST implement the objects required by theIEEE." ::= { etherWisDeviceEntry 5 } etherWisDeviceModesAllowed OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-only STATUS current DESCRIPTION "This is a bit pattern indicating which modessonetCompliance2 conformance statement in the SONET MIB, and as further detailed in the conformance statement in the MIB module defined in thisdevice will permit etherWisDeviceModeSelect tomemo. It should beset to. The bit positions, with 0 beingnoted that some of theLSB, indicate: 0 - 10GBASE-W 1 - 10GBASE-R" ::= { etherWisDeviceEntry 6 } etherWisDeviceModeSelect OBJECT-TYPE SYNTAX INTEGER MAX-ACCESS read-write STATUS current DESCRIPTION "This variable indicatesobjects incorporated by reference from thecurrent operating state ofSONET MIB -- specifically, thedevice. The values usethreshold objects and interval counter objects -- provide only approximate representations of thesame bit patterncorresponding oWIS attributes, asetherWisDeviceModesAllowed. Attemptsdetailed in Section 3.6. An alternative approach would have been toset this variabledefine new objects toa value which would cause conflicting mode settings will resultexactly match the oWIS definitions. That approach was rejected because the SONET MIB objects are already used inan inconsistentValue error." ::= { etherWisDeviceEntry 7 } etherWisDeviceJitterTestMode OBJECT-TYPE SYNTAX INTEGER { disable(0), enable(1) } MAX-ACCESS read-write STATUS current DESCRIPTION "This variable controls jitter test mode." ::= { etherWisDeviceEntry 8 } etherWisSectionCurrentTable OBJECT-TYPE SYNTAX SEQUENCE OF EtherWisSectionCurrentEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The table fordeployed systems to manage thecurrent stateSONET sublayers of ATM over SONET and PPP over SONET interfaces, and it was deemed undesirable to use a different scheme to manage the SONET sublayers of 10 Gb/s WAN-compatible Ethernet interfaces. Note that the approach adopted by this memo requires no hardware support beyond that mandated by [P802.3ae] subclause 50.3.10. 3.2. Relationship to the Ethernet-like Interfaces MIB An interface which includes the Ethernet WISsections." ::= { etherWisSection 1 } etherWisSectionCurrentEntry OBJECT-TYPE SYNTAX EtherWisSectionCurrentEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entryis, by definition, an Ethernet-like interface, and an agent implementing the objects defined in this memo MUST implement theetherWisSectionCurrentTable." INDEX { ifIndex } ::= { etherWisSectionCurrentTable 1 } EtherWisSectionCurrentEntry ::= SEQUENCE { etherWisSectionCurrentJ0Transmitted INTEGER, etherWisSectionCurrentJ0Expected INTEGER, etherWisSectionCurrentJ0Received INTEGER, etherWisSectionCurrentStatus Integer32, etherWisSectionCurrentESs Integer32, etherWisSectionCurrentSESs Integer32, etherWisSectionCurrentSEFSs Integer32, etherWisSectionCurrentCVs Integer32 } etherWisSectionCurrentJ0Transmitted OBJECT-TYPE SYNTAX INTEGER ( 0..255 ) MAX-ACCESS read-write STATUS current DESCRIPTION "This isobjects required by thesection trace J0 byte which isdot3Compliance2 compliance statement in the EtherLike-MIB. 3.3. Relationship tobe transmitted." ::= { etherWisSectionCurrentEntry 1 } etherWisSectionCurrentJ0Expected OBJECT-TYPE SYNTAX INTEGER ( 0..255 ) MAX-ACCESS read-write STATUS current DESCRIPTION "This isthesection trace J0 byte which802.3 MAU MIB Support for the mauModIfCompl2 compliance statement of the MAU-MIB [MAU-MIB] is REQUIRED for all Ethernet-like interfaces. The MAU-MIB isexpectedneeded in order tobe received." ::= { etherWisSectionCurrentEntry 2 } etherWisSectionCurrentJ0Received OBJECT-TYPE SYNTAX INTEGER ( 0..255 ) MAX-ACCESS read-only STATUS current DESCRIPTION "Thisallow applications to control and/or determine the media type in use. That is important for devices than can support both thesection trace J0 byte which was actually received." ::= { etherWisSectionCurrentEntry 3 } etherWisSectionCurrentStatus OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "This variable indicates10GBASE-R 10 Gb/s LAN format (which does not include thecurrent status ofWIS) and thesection with a bit map which can indicate several defects at once.10GBASE-W 10 Gb/s WAN format (which does include the WIS). TheetherWisSectionNoDefect shouldMAU-MIB also provides the means to put a device in standby mode or to reset it; the latter may beset if and only if no other flagused to re-initialize the WIS. 3.4. Use of the ifTable This section specifies how the ifTable, as defined in [RFC2863], isset.used for the Ethernet WIS application. 3.4.1. Layering Model Ethernet interfaces that employ the WIS are layered as defined in [P802.3ae]. Thebit positions are: 1 etherWisSectionNoError 2 etherWisSectionLocalFault 4 etherWisSectionLinkDown 8 etherWisSectionLOS 16 etherWisSectionLOF" ::= { etherWisSectionCurrentEntry 4 } etherWisSectionCurrentESs OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "The countcorresponding use ofErrored Secondsthe ifTable [RFC2863] is shown in thecurrent measuring interval." ::= { etherWisSectionCurrentEntry 5 } etherWisSectionCurrentSESs OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "The countfigure below. _____________________________ _ | LLC Layer | | +_____________________________+ | | MAC Layer | | +-----------------------------+ > 1 ifEntry | Reconciliation Sublayer | | ifType: ethernetCsmacd(6) +-----------------------------+ | | Physical Coding Sublayer | | +-----------------------------+ + | Path Layer | > 1 ifEntry +-----------------------------+ + ifType: sonetPath(50) | Line Layer | | +-----------------------------+ | | Section Layer | > 1 ifEntry +-----------------------------+ | ifType: sonet(39) | Physical Medium Layer | | ----------------------------- - Figure 1 - Use of ifTable for an Ethernet WIS port The exact configuration and multiplexing ofSeverely Errored Secondsthe layers is maintained in thecurrent measuring interval." ::= { etherWisSectionCurrentEntry 6 } etherWisSectionCurrentSEFSs OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "The count of Severely Errored Framing SecondsifStackTable [RFC2863] and in thecurrent measuring interval." ::= { etherWisSectionCurrentEntry 7 } etherWisSectionCurrentCVs OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "The countifInvStackTable [RFC2864]. 3.4.2. Use of ifTable for LLC Layer/MAC Layer/Reconciliation Sublayer/Physical CodingViolationsSublayer The ifTable MUST be used as specified in [ETHERIF] and [MAU-MIB] for thecurrent measuring interval." ::= { etherWisSectionCurrentEntry 8 } etherWisSectionIntervalTable OBJECT-TYPE SYNTAX SEQUENCE OF EtherWisSectionIntervalEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The tableLLC Layer/MAC Layer/Reconciliation Sublayer/Physical Coding Sublayer. 3.4.3. Use of ifTable for SONET/SDH Path Layer The ifTable MUST be used as specified in [SONETng] forstoragethe SONET/SDH Path Layer. The value ofEthernet WIS section historical data." ::= { etherWisSection 2 } etherWisSectionIntervalEntry OBJECT-TYPE SYNTAX EtherWisSectionIntervalEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entryifHighSpeed is set to 9585. ifSpeed reports a value of 4294967295. 3.4.4. Use of ifTable for SONET/SDH Medium/Section/Line Layer The ifTable MUST be used as specified in [SONETng] for theetherWisSectionIntervalTable." INDEX { ifIndex, etherWisSectionIntervalNumber } ::= { etherWisSectionIntervalTable 1 } EtherWisSectionIntervalEntry ::= SEQUENCE { etherWisSectionIntervalNumber Integer32, etherWisSectionIntervalESs Integer32, etherWisSectionIntervalSESs Integer32, etherWisSectionIntervalSEFSs Integer32, etherWisSectionIntervalCVs Integer32 } etherWisSectionIntervalNumber OBJECT-TYPE SYNTAX Integer32 ( 1..96 ) MAX-ACCESS not-accessible STATUS current DESCRIPTION "A number identifying which 15 minute intervalSONET/SDH Medium/Section/Line Layer. The value of ifHighSpeed isrefereneced byset to 9953. ifSpeed reports a value of 4294967295. 3.5. SONET/SDH Terminology The SONET/SDH terminology used in [P802.3ae] is mostly thedatasame as in [SONETng], but there are a few differences. In those cases thetable.definitions in [P802.3ae] take precedence. Thevalue 1 representsspecific differences are as follows. Unequipped This defect is not defined by [P802.3ae]. An implementation that supports it SHOULD report it by setting themost recent completed interval." ::= { etherWisSectionIntervalEntry 1 } etherWisSectionIntervalESs OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "The count of Errored SecondssonetPathUnequipped bit inthis measuring interval." ::= { etherWisSectionIntervalEntry 2 } etherWisSectionIntervalSESs OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "The countthe appropriate instance ofSeverely Errored SecondssonetPathCurrentStatus. Signal Label Mismatch This defect is called Payload Label Mismatch (PLM) inthis measuring interval." ::= { etherWisSectionIntervalEntry 3 } etherWisSectionIntervalSEFSs OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "The count[P802.3ae]. It is reported by setting both the sonetPathSignalLabelMismatch bit in the appropriate instance ofSeverely Errored Framing SecondssonetPathCurrentStatus (defined in [SONETng]) and themeasuring interval." ::= { etherWisSectionIntervalEntry 4 } etherWisSectionIntervalCVs OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "The countetherWisPathPLM bit in the corresponding instance of etherWisPathCurrentStatus (defined below). Loss of Codegroup Delineation [P802.3ae] defines Loss of Codegroup Delineation (LCD) as occurring when the Physical CodingViolationsSublayer is unable to locate 64B/66B code group boundaries. There is no analogous defect defined in [SONETng]. It is reported by setting themeasuring interval." ::= { etherWisSectionIntervalEntry 5 } etherWisLineCurrentTable OBJECT-TYPE SYNTAX SEQUENCE OF EtherWisLineCurrentEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The table foretherWisPathLCD bit in thecurrent stateappropriate instance ofEthernet WIS lines." ::= { etherWisLine 1 } etherWisLineCurrentEntry OBJECT-TYPE SYNTAX EtherWisLineCurrentEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry intheetherWisLineCurrentTable." INDEX { ifIndex } ::= { etherWisLineCurrentTable 1 } EtherWisLineCurrentEntry ::= SEQUENCE { etherWisLineCurrentStatus Integer32, etherWisLineCurrentESs Integer32, etherWisLineCurrentSESs Integer32, etherWisLineCurrentCVs Integer32, etherWisLineCurrentUASs Integer32 } etherWisLineCurrentStatus OBJECT-TYPE SYNTAX Integer32 ( 1..6 ) MAX-ACCESS read-only STATUS current DESCRIPTION "This variable indicatesobject etherWisPathCurrentStatus defined below. STS-Path Remote Defect Indication [P802.3ae] mandates thecurrent statususe of ERDI-P (Enhanced Remote Defect Indication - Path) defined in [T1.231] to signal remote server defects (triggered by path AIS or path LOP) and remote payload defects (triggered by Payload Label Mismatch or Loss of Codegroup Delineation). [SONETng] defines theline with a bit mapone-bit RDI-P (Remote Defect Indication - Path), whichcan indicate several defects at once. The etherWisLineNoDefect should besignals remote server detects (i.e., path AIS and path LOP) only. An implementation of the WIS MUST setif and only if no other flag is set. Thethe sonetPathSTSRDI bitpositions are: 1 etherWisLineNoDefect 2 etherWisLineRDI 4 etherWisLineAIS" ::= { etherWisLineCurrentEntry 1 } etherWisLineCurrentESs OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "The count of Errored Secondsin thecurrent measuring interval." ::= { etherWisLineCurrentEntry 2 } etherWisLineCurrentSESs OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "The countappropriate instance ofSeverely Errored SecondssonetPathCurrentStatus when it receives an ERDI-P server defect indication from the remote end. Both ERDI-P payload defects and ERDI-P server defects are reported in thecurrent measuring interval." ::= { etherWisLineCurrentEntry 3 } etherWisLineCurrentCVs OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "The count ofobject etherWisFarEndPathCurrentStatus defined below. Path Coding ViolationsinIn [P802.3ae] thecurrent measuring interval." ::= { etherWisLineCurrentEntry 4 } etherWisLineCurrentUASs OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "Thepath layer CV count is based on block errors and not BIP-8 errors, i.e., it is incremented only once for each B3 byte that indicates incorrect parity, regardless ofUnavailable Seconds inthecurrent measuring interval." ::= { etherWisLineCurrentEntry 5 } etherWisLineIntervalTable OBJECT-TYPE SYNTAX SEQUENCE OF EtherWisLineIntervalEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The tablenumber 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 thehistorical datapath layer error count. 3.6. Mapping ofEthernet WIS lines." ::= { etherWisLine 2 } etherWisLineIntervalEntry OBJECT-TYPE SYNTAX EtherWisLineIntervalEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in the etherWisLineIntervalTable." INDEX { ifIndex, etherWisLineIntervalNumber } ::= { etherWisLineIntervalTable 1 } EtherWisLineIntervalEntry ::= SEQUENCE { etherWisLineIntervalNumber Integer32, etherWisLineIntervalESs Integer32, etherWisLineIntervalSESs Integer32, etherWisLineIntervalCVs Integer32, etherWisLineIntervalUASs Integer32 } etherWisLineIntervalNumber OBJECT-TYPE SYNTAX Integer32 ( 1..96 ) MAX-ACCESS not-accessible STATUS current DESCRIPTION "A number identifying which 15 minute interval is refereneced byIEEE 802.3 Managed Objects This section contains thedatamapping between oWIS managed objects defined inthe table. The value 1 represents the most recent completed interval." ::= { etherWisLineIntervalEntry 1 } etherWisLineIntervalESs OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "The count of Errored Seconds[P802.3ae] and managed objects defined inthe measuring interval." ::= { etherWisLineIntervalEntry 2 } etherWisLineIntervalSESs OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "The count of Severely Errored Secondsthis document and in associated MIB modules, i.e., themeasuring interval." ::= { etherWisLineIntervalEntry 3 } etherWisLineIntervalCVs OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "The count of Coding Violations inIF-MIB [RFC2863], themeasuring interval." ::= { etherWisLineIntervalEntry 4 } etherWisLineIntervalUASs OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "The count of Unavailable Seconds inSONET-MIB [SONETng], and themeasuring interval." ::= { etherWisLineIntervalEntry 5 } etherWisPathCurrentTable OBJECT-TYPE SYNTAX SEQUENCE OF EtherWisPathCurrentEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The table forMAU-MIB [MAU-MIB]. IEEE 802.3 Managed Object Corresponding SNMP Object oWIS - pWISBasic package aWISID IF-MIB - ifIndex aSectionStatus SONET-MIB - sonetSectionCurrentStatus aLineStatus SONET-MIB - sonetLineCurrentStatus aPathStatus etherWisPathCurrentStatus aFarEndPathStatus etherWisFarEndPathCurrentStatus oWIS - pWISOptional package aSectionSESThreshold SONET-MIB - sonetSESthresholdSet aSectionSESs SONET-MIB - sonetSectionCurrentSESs + sonetSectionIntervalSESs aSectionESs SONET-MIB - sonetSectionCurrentESs + sonetSectionIntervalESs aSectionSEFSs SONET-MIB - sonetSectionCurrentSEFSs + sonetSectionIntervalSEFSs aSectionCVs SONET-MIB - sonetSectionCurrentCVs + sonetSectionIntervalCVs aJ0ValueTX etherWisSectionCurrentJ0Transmitted aJ0ValueRX etherWisSectionCurrentJ0Received aLineSESThreshold SONET-MIB - sonetSESthresholdSet aLineSESs SONET-MIB - sonetLineCurrentSESs + sonetLineIntervalSESs aLineESs SONET-MIB - sonetLineCurrentESs + sonetLineIntervalESs aLineCVs SONET-MIB - sonetLineCurrentCVs + sonetLineIntervalCVs aFarEndLineSESs SONET-MIB - sonetFarEndLineCurrentSESs + sonetFarEndLineIntervalSESs aFarEndLineESs SONET-MIB - sonetFarEndLineCurrentESs + sonetFarEndLineIntervalESs aFarEndLineCVs SONET-MIB - sonetFarEndLineCurrentCVs + sonetFarEndLineIntervalCVs aPathSESThreshold SONET-MIB - sonetSESthresholdSet aPathSESs SONET-MIB - sonetPathCurrentSESs + sonetPathIntervalSESs aPathESs SONET-MIB - sonetPathCurrentESs + sonetPathIntervalESs aPathCVs SONET-MIB - sonetPathCurrentCVs + sonetPathIntervalCVs aJ1ValueTX etherWisPathCurrentJ1Transmitted aJ1ValueRX etherWisPathCurrentJ1Received aFarEndPathSESs SONET-MIB - sonetFarEndPathCurrentSESs + sonetFarEndPathIntervalSESs aFarEndPathESs SONET-MIB - sonetFarEndPathCurrentESs + sonetFarEndPathIntervalESs aFarEndPathCVs SONET-MIB - sonetFarEndPathCurrentCVs + sonetFarEndPathIntervalCVs Please note that thecurrent statedefinitions ofEthernet WIS paths." ::= { etherWisPath 1 } etherWisPathCurrentEntry OBJECT-TYPE SYNTAX EtherWisPathCurrentEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry intheetherWisPathCurrentTable." INDEX { ifIndex } ::= { etherWisPathCurrentTable 1 } EtherWisPathCurrentEntry ::= SEQUENCE { etherWisPathCurrentStatus Integer32, etherWisPathCurrentESs Integer32, etherWisPathCurrentSESs Integer32, etherWisPathCurrentCVs Integer32, etherWisPathCurrentUASs Integer32 } etherWisPathCurrentStatus OBJECT-TYPE SYNTAX Integer32 ( 1..6 ) MAX-ACCESS read-only STATUS current DESCRIPTION "This variable indicatesthreshold objects and counter objects imported from thecurrent statusSONET-MIB do not exactly match the definitions of theline with a bit map which can indicate several defects at once.corresponding IEEE 802.3 objects. TheetherWisPathNoDefect flag should be set if and only if no other flagspecific differences are as follows: IEEE 802.3 Managed Object How Corresponding SNMP Object Differs oWIS - pWISOptional package aSectionSESThreshold This object isset. The bit positions are: 1 etherWisPathNoDefect 2 etherWisPathLCD 4 etherWisPathPLM 8 etherWisPathAIS 16 etherWisPathLOP" ::= { etherWisPathCurrentEntry 1 } etherWisPathCurrentESs OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "The count of Errored Seconds in the current measuring interval." ::= { etherWisPathCurrentEntry 2 } etherWisPathCurrentSESs OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "The count of Severely Errored Secondsdefined in [P802.3ae] as an integer with one instance per interface. sonetSESthresholdSet is an enumerated value that has one instance per network element; it controls thecurrent measuring interval." ::= { etherWisPathCurrentEntry 3 } etherWisPathCurrentCVs OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "The count of Coding Violationsthresholds for all layers simultaneously and allows only certain discrete values to be selected. aSectionSESs This object is defined inthe current measuring interval." ::= { etherWisPathCurrentEntry 4 } etherWisPathCurrentUASs OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "The count of Unavailable Seconds[P802.3ae] as a generalized nonresetable counter. The objects sonetSectionCurrentSESs and sonetSectionIntervalSESs are 15-minute interval counters. aSectionESs This object is defined as a generalized nonresetable counter inthe current measuring interval." ::= { etherWisPathCurrentEntry 5 } etherWisPathIntervalTable OBJECT-TYPE SYNTAX SEQUENCE OF EtherWisPathIntervalEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The table for the historical data of Ethernet WIS lines." ::= { etherWisPath 2 } etherWisPathIntervalEntry OBJECT-TYPE SYNTAX EtherWisPathIntervalEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry[P802.3ae]. The objects sonetSectionCurrentESs and sonetSectionIntervalESs are 15-minute interval counters. aSectionSEFSs This object is defined as a generalized nonresetable counter inthe etherWisPathIntervalTable." INDEX { ifIndex, etherWisPathIntervalNumber } ::= { etherWisPathIntervalTable 1 } EtherWisPathIntervalEntry ::= SEQUENCE { etherWisPathIntervalNumber Integer32, etherWisPathIntervalESs Integer32, etherWisPathIntervalSESs Integer32, etherWisPathIntervalCVs Integer32, etherWisPathIntervalUASs Integer32 } etherWisPathIntervalNumber OBJECT-TYPE SYNTAX Integer32 ( 1..96 ) MAX-ACCESS not-accessible STATUS current DESCRIPTION "A number identifying which 15 minute[P802.3ae]. The objects sonetSectionCurrentSEFSs and sonetSectionIntervalSEFSs are 15-minute interval counters. aSectionCVs This object isrefereneced by the datadefined as a generalized nonresetable counter inthe table.[P802.3ae], and it is not subject to inhibiting. The objects sonetSectionCurrentCVs and sonetSectionIntervalCVs are 15-minute interval counters, and they are inhibited (not incremented) during one-second intervals that qualify as severely errored seconds. aLineSESThreshold This object is defined in [P802.3ae] as an integer with one instance per interface. sonetSESthresholdSet is an enumerated value1 representsthat has one instance per network element; it controls themost recent completed interval." ::= { etherWisPathIntervalEntry 1 } etherWisPathIntervalESs OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS current DESCRIPTION "The countthresholds for all layers simultaneously and allows only certain discrete values to be selected. aLineSESs This object is defined as a generalized nonresetable counter in [P802.3ae], and it is not subject to inhibiting. The objects sonetLineCurrentSESs and sonetLineIntervalSESs are 15-minute interval counters, and they are inhibited (not incremented) during one-second intervals that qualify as unavailable seconds. aLineESs This object is defined as a generalized nonresetable counter in [P802.3ae], and it is not subject to inhibiting. The objects sonetLineCurrentESs and sonetLineIntervalESs are 15-minute interval counters, and they are inhibited (not incremented) during one-second intervals that qualify as unavailable seconds. aLineCVs This object is defined as a generalized nonresetable counter in [P802.3ae], and it is not subject to inhibiting. The objects sonetLineCurrentCVs and sonetLineIntervalCVs are 15-minute interval counters, and they are inhibited (not incremented) during one-second intervals that qualify either as severely errored seconds or as unavailable seconds. aFarEndLineSESs This object is defined as a generalized nonresetable counter in [P802.3ae], and it is not subject to inhibiting. The objects sonetFarEndLineCurrentSESs and sonetFarEndLineIntervalSESs are 15-minute interval counters, and they are inhibited (not incremented) during one-second intervals that qualify as unavailable seconds. aFarEndLineESs This object is defined as a generalized nonresetable counter in [P802.3ae], and it is not subject to inhibiting. The objects sonetFarEndLineCurrentESs and sonetFarEndLineIntervalESs are 15-minute interval counters, and they are inhibited (not incremented) during one-second intervals that qualify as unavailable seconds. aFarEndLineCVs This object is defined as a generalized nonresetable counter in [P802.3ae], and it is not subject to inhibiting. The objects sonetFarEndLineCurrentCVs and sonetFarEndLineIntervalCVs are 15-minute interval counters, and they are inhibited (not incremented) during one-second intervals that qualify either as severely errored seconds or as unavailable seconds. aPathSESThreshold This object is defined in [P802.3ae] as an integer with one instance per interface. sonetSESthresholdSet is an enumerated value that has one instance per network element; it controls the thresholds for all layers simultaneously and allows only certain discrete values to be selected. aPathSESs This object is defined as a generalized nonresetable counter in [P802.3ae], and it is not subject to inhibiting. The objects sonetPathCurrentSESs and sonetPathIntervalSESs are 15-minute interval counters, and they are inhibited (not incremented) during one-second intervals that qualify as unavailable seconds. In addition, [P802.3ae] includes PLM-P and LCD-P defects in the criteria for declaring path layer severely errored seconds, while [SONETng] does not. aPathESs This object is defined as a generalized nonresetable counter in [P802.3ae], and it is not subject to inhibiting. The objects sonetPathCurrentESs and sonetPathIntervalESs are 15-minute interval counters, and they are inhibited (not incremented) during one-second intervals that qualify as unavailable seconds. In addition, [P802.3ae] includes PLM-P and LCD-P defects in the criteria for declaring path layer errored seconds, while [SONETng] does not. aPathCVs This object is defined as a generalized nonresetable counter in [P802.3ae], and it is not subject to inhibiting. The objects sonetPathCurrentCVs and sonetPathIntervalCVs are 15-minute interval counters, and they are inhibited (not incremented) during one-second intervals that qualify either as severely errored seconds or as unavailable seconds. aFarEndPathSESs This object is defined as a generalized nonresetable counter in [P802.3ae], and it is not subject to inhibiting. The objects sonetFarEndPathCurrentSESs and sonetFarEndPathIntervalSESs are 15-minute interval counters, and they are inhibited (not incremented) during one-second intervals that qualify as unavailable seconds. In addition, [P802.3ae] includes far-end PLM-P and LCD-P defects in the criteria for declaring far-end path layer severely errored seconds, while [SONETng] does not. aFarEndPathESs This object is defined as a generalized nonresetable counter in [P802.3ae], and it is not subject to inhibiting. The objects sonetFarEndPathCurrentESs and sonetFarEndPathIntervalESs are 15-minute interval counters, and they are inhibited (not incremented) during one-second intervals that qualify as unavailable seconds. In addition, [P802.3ae] includes far-end PLM-P and LCD-P defects in the criteria for declaring far-end path layer errored seconds, while [SONETng] does not. aFarEndPathCVs This object is defined as a generalized nonresetable counter in [P802.3ae], and it is not subject to inhibiting. The objects sonetFarEndPathCurrentCVs and sonetFarEndPathIntervalCVs are 15-minute interval counters, and they are inhibited (not incremented) during one-second intervals that qualify either as severely errored seconds or as unavailable seconds. Please note that despite the differences in semantics between the threshold objects and counter objects imported from the SONET-MIB and the corresponding IEEE 802.3 objects, the hardware support mandated by [P802.3ae] subclause 50.3.10 suffices for both. See Appendix A for details. 3.7. Mapping of SNMP Objects to WIS Station Management Registers 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- specific hardware support. [P802.3ae] subclause 50.3.10 specifies WIS management interface requirements, including a required subset of the WIS MDIO (Management Data Input/Output) registers defined in [P802.3ae] subclause 45.2.2. The table below provides a cross- reference between those managed objects and the WIS MDIO registers 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 not implemented, then the capabilities of the required register subset must be provided by other means. 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 SONET-MIB - sonetMediumType none required SONET-MIB - sonetMediumTimeElapsed none required SONET-MIB - sonetMediumValidIntervals none required SONET-MIB - sonetMediumLineCoding none required SONET-MIB - sonetMediumLineType none required SONET-MIB - sonetMediumCircuitIdentifier none required SONET-MIB - sonetMediumInvalidIntervals none required SONET-MIB - sonetMediumLoopbackConfig none required SONET-MIB - sonetSESthresholdSet none required ETHER-WIS - etherWisSectionCurrentJ0Transmitted 10G WIS J0 Tx ETHER-WIS - etherWisSectionCurrentJ0Received 10G WIS J0 Rx SONET-MIB - sonetSectionCurrentStatus 10G WIS Status 3 SONET-MIB - sonetSectionCurrentESs \ SONET-MIB - sonetSectionCurrentSESs \ SONET-MIB - sonetSectionCurrentSEFSs | 10G WIS Status 3 SONET-MIB - sonetSectionCurrentCVs | + SONET-MIB - sonetSectionIntervalESs | 10G WIS Section SONET-MIB - sonetSectionIntervalSESs | BIP Error Count SONET-MIB - sonetSectionIntervalSEFSs / SONET-MIB - sonetSectionIntervalCVs / SONET-MIB - sonetSectionIntervalValidData none required SONET-MIB - sonetLineCurrentStatus 10G WIS Status 3 SONET-MIB - sonetLineCurrentESs \ SONET-MIB - sonetLineCurrentSESs \ SONET-MIB - sonetLineCurrentCVs | 10G WIS Status 3 SONET-MIB - sonetLineCurrentUASs | + SONET-MIB - sonetLineIntervalESs | 10G WIS Line SONET-MIB - sonetLineIntervalSESs | BIP Errors SONET-MIB - sonetLineIntervalCVs / SONET-MIB - sonetLineIntervalUASs / SONET-MIB - sonetLineIntervalValidData none required SONET-MIB - sonetFarEndLineCurrentESs \ SONET-MIB - sonetFarEndLineCurrentSESs \ SONET-MIB - sonetFarEndLineCurrentCVs | 10G WIS Status 3 SONET-MIB - sonetFarEndLineCurrentUASs | + SONET-MIB - sonetFarEndLineIntervalESs | 10G WIS Far End SONET-MIB - sonetFarEndLineIntervalSESs | Line BIP Errors SONET-MIB - sonetFarEndLineIntervalCVs / SONET-MIB - sonetFarEndLineIntervalUASs / SONET-MIB - sonetFarEndLineIntervalValidData 10G WIS Status 3 ETHER-WIS - etherWisPathCurrentStatus 10G WIS Status 3 ETHER-WIS - etherWisPathCurrentJ1Transmitted 10G WIS J1 Tx ETHER-WIS - etherWisPathCurrentJ1Received 10G WIS J1 Rx SONET-MIB - sonetPathCurrentWidth none required SONET-MIB - sonetPathCurrentStatus 10G WIS Status 3 SONET-MIB - sonetPathCurrentESs \ SONET-MIB - sonetPathCurrentSESs \ SONET-MIB - sonetPathCurrentCVs | 10G WIS Status 3 SONET-MIB - sonetPathCurrentUASs | + SONET-MIB - sonetPathIntervalESs | 10G WIS SONET-MIB - sonetPathIntervalSESs | Path Block SONET-MIB - sonetPathIntervalCVs / Error Count SONET-MIB - sonetPathIntervalUASs / SONET-MIB - sonetPathIntervalValidData none required ETHER-WIS - etherWisFarEndPathCurrentStatus 10G WIS Status 3 SONET-MIB - sonetFarEndPathCurrentESs \ SONET-MIB - sonetFarEndPathCurrentSESs \ SONET-MIB - sonetFarEndPathCurrentCVs | 10G WIS Status 3 SONET-MIB - sonetFarEndPathCurrentUASs | + SONET-MIB - sonetFarEndPathIntervalESs | 10G WIS Far End SONET-MIB - sonetFarEndPathIntervalSESs | Path Block SONET-MIB - sonetFarEndPathIntervalCVs / Error Count SONET-MIB - sonetFarEndPathIntervalUASs / SONET-MIB - sonetFarEndPathIntervalValidData 10G WIS Status 3 MAU-MIB - ifMauIfIndex none required MAU-MIB - ifMauIndex none required MAU-MIB - ifMauType 10G WIS Control 2 MAU-MIB - ifMauStatus WIS Control 1 MAU-MIB - ifMauMediaAvailable \ WIS Status 1 + MAU-MIB - ifMauMediaAvailableStateExits / 10G WIS Status 3 MAU-MIB - ifMauJabberState none required MAU-MIB - ifMauJabberingStateEnters none required MAU-MIB - ifMauFalseCarriers none required MAU-MIB - ifMauDefaultType 10G WIS Control 2 MAU-MIB - ifMauAutoNegSupported none required MAU-MIB - ifMauTypeListBits 10G WIS Status 2 3.8. Structure of the MIB Module Four tables are defined in this MIB module. 3.8.1. etherWisDeviceTable The purpose of this table is to define managed objects to control the WIS test pattern mode. These objects are required to support mandatory WIS test features required by Clause 50 of [P802.3ae]. The etherWisDeviceTable is a sparse augmentation of the sonetMediumTable of the SONET MIB -- in other words, for each entry in the etherWisDeviceTable there SHALL be an entry in the sonetMediumTable and the same ifIndex value SHALL be used for both entries. 3.8.2. etherWisSectionCurrentTable The purpose of this table is to define managed objects for the transmitted and received section trace messages (J0 byte). The etherWisSectionCurrentTable is a sparse augmentation of the sonetSectionCurrentTable of the SONET MIB -- in other words, for each entry in the etherWisSectionCurrentTable there SHALL be an entry in the sonetSectionCurrentTable and the same ifIndex value SHALL be used for both entries. 3.8.3. etherWisPathCurrentTable The purpose of this table is to define managed objects for the current WIS path layer status and for the transmitted and received path trace messages (J1 byte). The path layer status object is provided because the WIS supports some near-end path status conditions that are not reported in sonetPathCurrentStatus. The etherWisPathCurrentTable is a sparse augmentation of the sonetPathCurrentTable of the SONET MIB -- in other words, for each entry in the etherWisPathCurrentTable there SHALL be an entry in the sonetPathCurrentTable and the same ifIndex value SHALL be used for both entries. 3.8.4. etherWisFarEndPathCurrentTable 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 because the WIS supports some far-end path status conditions that are not reported in sonetPathCurrentStatus. The etherWisFarEndPathCurrentTable is a sparse augmentation of the sonetFarEndPathCurrentTable of the SONET MIB -- in other words, for each entry in the etherWisFarEndPathCurrentTable there SHALL be an entry in the sonetFarEndPathCurrentTable and the same ifIndex value SHALL be used for both entries. 4. Object Definitions ETHER-WIS DEFINITIONS ::= BEGIN IMPORTS MODULE-IDENTITY, OBJECT-TYPE, transmission FROM SNMPv2-SMI ifIndex FROM IF-MIB MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF sonetMediumStuff2, sonetSectionStuff2, sonetLineStuff2, sonetFarEndLineStuff2, sonetPathStuff2, sonetFarEndPathStuff2, sonetMediumType, sonetMediumLineCoding, sonetMediumLineType, sonetMediumCircuitIdentifier, sonetMediumLoopbackConfig, sonetSESthresholdSet, sonetPathCurrentWidth FROM SONET-MIB; etherWisMIB MODULE-IDENTITY LAST-UPDATED "200111202123Z" -- November 20, 2001 ORGANIZATION "IETF Hubmib and AToMMIB Working Groups" CONTACT-INFO "Hubmib WG: http://www.ietf.org/html.charters/hubmib-charter.html AToMMIB WG: http://www.ietf.org/html.charters/atommib-charter.html Editor: C. M. Heard Postal: 600 Rainbow Dr. #141 Mountain View, CA 94041-2542 USA Tel: +1 650-964-8391 E-mail: heard@pobox.com" DESCRIPTION "The objects in this MIB module are used in conjunction with objects in the SONET-MIB and the MAU-MIB to manage the Ethernet WAN Interface Sublayer (WIS). The following reference is used throughout this MIB module: [IEEE 802.3 Std] refers to: IEEE Std 802.3, 2000 Edition: 'IEEE Standard for Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Specific requirements - Part 3: Carrier sense multiple access with collision detection (CSMA/CD) access method and physical layer specifications', as amended by IEEE Draft P802.3ae/D3.3: 'Supplement to Carrier Sense Multiple Access with Collision Detection (CSMA/CD) Access Method & Physical Layer Specifications - 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 Sublayer (WIS), type 10GBASE-W', Clause 30, '10Mb/s, 100Mb/s, 1000Mb/s, and 10Gb/s MAC Control, and Link Aggregation Management', and Clause 45, 'Management Data Input/Output (MDIO) Interface'." REVISION "200111202123Z" -- November 20, 2001 DESCRIPTION "Initial version." ::= { transmission XXX } -- to be assigned by IANA -- The main sections of the module etherWisObjects OBJECT IDENTIFIER ::= { etherWisMIB 1 } etherWisObjectsPath OBJECT IDENTIFIER ::= { etherWisMIB 2 } etherWisConformance OBJECT IDENTIFIER ::= { etherWisMIB 3 } -- groups in the Ethernet WIS MIB module etherWisDevice OBJECT IDENTIFIER ::= { etherWisObjects 1 } etherWisSection OBJECT IDENTIFIER ::= { etherWisObjects 2 } etherWisPath OBJECT IDENTIFIER ::= { etherWisObjectsPath 1 } etherWisFarEndPath OBJECT IDENTIFIER ::= { etherWisObjectsPath 2 } -- The Device group -- These objects provide WIS extensions to -- the SONET-MIB Medium Group. etherWisDeviceTable OBJECT-TYPE SYNTAX SEQUENCE OF EtherWisDeviceEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The table for Ethernet WIS devices" ::= { etherWisDevice 1 } etherWisDeviceEntry OBJECT-TYPE SYNTAX EtherWisDeviceEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in the Ethernet WIS device table. For each instance of this object there shall be a corresponding instance of sonetMediumEntry." INDEX { ifIndex } ::= { etherWisDeviceTable 1 } EtherWisDeviceEntry ::= SEQUENCE { etherWisDeviceTestPatternType INTEGER, etherWisDeviceRxTestPatternMode INTEGER, etherWisDeviceTxTestPatternMode INTEGER } etherWisDeviceTestPatternType OBJECT-TYPE SYNTAX INTEGER { mixedFrequency(0), squareWave(1) } MAX-ACCESS read-write STATUS current DESCRIPTION "This variable controls the type of test pattern. The value mixedFrequency(0) selects the framed mixed frequency test pattern specified in [IEEE 802.3 Std.] subclause 50.3.8.2. The value squareWave(1) selects the unframed square wave test pattern specified in [IEEE 802.3 Std.] subclause 50.3.8.1." REFERENCE "[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 45.2.2.6.1, Test pattern (2.7.3)." ::= { etherWisDeviceEntry 1 } etherWisDeviceRxTestPatternMode OBJECT-TYPE SYNTAX INTEGER { disabled(0), enabled(1) } MAX-ACCESS read-write STATUS current DESCRIPTION "This variable controls the receive test pattern mode. The value disabled(0) sets the WIS receive path into normal mode. The value enabled(1) sets the WIS receive path into test pattern mode. An attempt to set this object to enabled(1) when the corresponding instance of ifAdminState has the value up(1) SHALL be rejected with the error inconsistentValue. An attempt to set the corresponding instance of ifAdminStatus to the value up(1) when an instance of this object has the value enabled(1) SHALL be rejected with the error inconsistentValue." REFERENCE "[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 45.2.2.6.2, Receive test pattern mode (2.7.2)." ::= { etherWisDeviceEntry 2 } etherWisDeviceTxTestPatternMode OBJECT-TYPE SYNTAX INTEGER { disabled(0), enabled(1) } MAX-ACCESS read-write STATUS current DESCRIPTION "This variable controls the transmit test pattern mode. The value disabled(0) set the WIS transmit path into normal mode. The value enabled(1) sets the WIS transmit path into test pattern mode. An attempt to set this object to enabled(1) when the corresponding instance of ifAdminState has the value up(1) SHALL be rejected with the error inconsistentValue. An attempt to set the corresponding instance of ifAdminStatus to the value up(1) when an instance of this object has the value enabled(1) SHALL be rejected with the error inconsistentValue." REFERENCE "[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 45.2.2.6.3, Transmit test pattern mode (2.7.1)." ::= { etherWisDeviceEntry 3 } -- The Section group -- These objects provide WIS extensions to -- the SONET-MIB Section Group. etherWisSectionCurrentTable OBJECT-TYPE SYNTAX SEQUENCE OF EtherWisSectionCurrentEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The table for the current state of Ethernet WIS sections." ::= { etherWisSection 1 } etherWisSectionCurrentEntry OBJECT-TYPE SYNTAX EtherWisSectionCurrentEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in the etherWisSectionCurrentTable. For each instance of this object there shall be a corresponding instance of sonetSectionCurrentEntry." INDEX { ifIndex } ::= { etherWisSectionCurrentTable 1 } EtherWisSectionCurrentEntry ::= SEQUENCE { etherWisSectionCurrentJ0Transmitted INTEGER, etherWisSectionCurrentJ0Received INTEGER } etherWisSectionCurrentJ0Transmitted OBJECT-TYPE SYNTAX INTEGER ( 0..255 ) MAX-ACCESS read-write STATUS current DESCRIPTION "This is the single-octet section trace message that is to be transmitted in the J0 byte. The value SHOULD be set to '01'h when the section trace function is not used, and the implementation SHOULD use that value as a default if no other value has been set." REFERENCE "[IEEE 802.3 Std.], 30.8.1.1.8, aJ0ValueTX." ::= { etherWisSectionCurrentEntry 1 } etherWisSectionCurrentJ0Received OBJECT-TYPE SYNTAX INTEGER ( 0..255 ) MAX-ACCESS read-only STATUS current DESCRIPTION "This is the single-octet section trace message that was most recently received in the J0 byte." REFERENCE "[IEEE 802.3 Std.], 30.8.1.1.9, aJ0ValueRX." ::= { etherWisSectionCurrentEntry 2 } -- The Path group -- These objects provide WIS extensions to -- the SONET-MIB Path Group. etherWisPathCurrentTable OBJECT-TYPE SYNTAX SEQUENCE OF EtherWisPathCurrentEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The table for the current state of Ethernet WIS paths." ::= { etherWisPath 1 } etherWisPathCurrentEntry OBJECT-TYPE SYNTAX EtherWisPathCurrentEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in the etherWisPathCurrentTable. For each instance of this object there shall be a corresponding instance of sonetPathCurrentEntry." INDEX { ifIndex } ::= { etherWisPathCurrentTable 1 } EtherWisPathCurrentEntry ::= SEQUENCE { etherWisPathCurrentStatus BITS, etherWisPathCurrentJ1Transmitted OCTET STRING, etherWisPathCurrentJ1Received OCTET STRING } etherWisPathCurrentStatus OBJECT-TYPE SYNTAX BITS { etherWisPathLOP(0), etherWisPathAIS(1), etherWisPathPLM(2), etherWisPathLCD(3) } MAX-ACCESS read-write STATUS current DESCRIPTION "This variable indicates the current status of the path payload with a bit map that can indicate multiple defects at once. The bit positions are assigned as follows: etherWisPathLOP(0) This bit is set to indicate that an LOP-P (Loss of Pointer - Path) defect is being experienced. Note: when this bit is set, sonetPathSTSLOP MUST be set in the corresponding instance of sonetPathCurrentStatus. etherWisPathAIS(1) This bit is set to indicate that an AIS-P (Alarm Indication Signal - Path) defect is being experienced. Note: when this bit is set, sonetPathSTSAIS MUST be set in the corresponding instance of sonetPathCurrentStatus. etherWisPathPLM(1) This bit is set to indicate that a PLM-P (Payload Label Mismatch - Path) defect is being experienced. Note: when this bit is set, sonetPathSignalLabelMismatch MUST be set in the corresponding instance of sonetPathCurrentStatus. etherWisPathLCD(3) This bit is set to indicate that an LCD-P (Loss of Codegroup Delination - Path) defect is being experienced. Since this defect is detected by the PCS and not by the path layer itself, there is no corresponding bit in sonetPathCurrentStatus." REFERENCE "[IEEE 802.3 Std.], 30.8.1.1.18, aPathStatus." ::= { etherWisPathCurrentEntry 1 } etherWisPathCurrentJ1Transmitted OBJECT-TYPE SYNTAX OCTET STRING (SIZE (16)) MAX-ACCESS read-write STATUS current DESCRIPTION "This is the 16-octet path message that is to be transmitted in the J1 byte. The value SHOULD be fifteen octets of '00'h followed by '89'h (or some cyclic shift thereof) when the path trace function is not used, and the implementation SHOULD use that value (or a cyclic shift thereof) as a default if no other value has been set." REFERENCE "[IEEE 802.3 Std.], 30.8.1.1.23, aJ1ValueTX." ::= { etherWisPathCurrentEntry 2 } etherWisPathCurrentJ1Received OBJECT-TYPE SYNTAX OCTET STRING (SIZE (16)) MAX-ACCESS read-only STATUS current DESCRIPTION "This is the 16-octet path trace message that was most recently received in the J1 byte." REFERENCE "[IEEE 802.3 Std.], 30.8.1.1.24, aJ1ValueRX." ::= { etherWisPathCurrentEntry 3 } -- The Far End Path group -- These objects provide WIS extensions to -- the SONET-MIB Far End Path Group. etherWisFarEndPathCurrentTable OBJECT-TYPE SYNTAX SEQUENCE OF EtherWisFarEndPathCurrentEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "The table for the current far-end state of Ethernet WIS paths." ::= { etherWisFarEndPath 1 } etherWisFarEndPathCurrentEntry OBJECT-TYPE SYNTAX EtherWisFarEndPathCurrentEntry MAX-ACCESS not-accessible STATUS current DESCRIPTION "An entry in the etherWisFarEndPathCurrentTable. For each instance of this object there shall be a corresponding instance of sonetFarEndPathCurrentEntry." INDEX { ifIndex } ::= { etherWisFarEndPathCurrentTable 1 } EtherWisFarEndPathCurrentEntry ::= SEQUENCE { etherWisFarEndPathCurrentStatus BITS } etherWisFarEndPathCurrentStatus OBJECT-TYPE SYNTAX BITS { etherWisFarEndPayloadDefect(0), etherWisFarEndServerDefect(1) } MAX-ACCESS read-write STATUS current DESCRIPTION "This variable indicates the current status at the far end ofErrored Secondsthe path using a bit map that can indicate multiple defects at once. The bit positions are assigned as follows: etherWisFarEndPayloadDefect(0) A far end payload defect (i.e., far end PLM-P or LCD-P) is currently being signalled in G1 bits 5-7. etherWisFarEndServerDefect(1) A far end server defect (i.e., far end LOP-P or AIS-P) is currently being signalled in G1 bits 5-7. Note: when this bit is set, sonetPathSTSRDI MUST be set in themeasuring interval."corresponding instance of sonetPathCurrentStatus." REFERENCE "[IEEE 802.3 Std.], 30.8.1.1.25, aFarEndPathStatus." ::= { etherWisFarEndPathCurrentEntry 1 } -- -- Conformance Statements -- etherWisGroups OBJECT IDENTIFIER ::= { etherWisConformance 1 } etherWisCompliances OBJECT IDENTIFIER ::= {etherWisPathIntervalEntryetherWisConformance 2 }etherWisPathIntervalSESs OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only-- Object Groups etherWisDeviceGroup OBJECT-GROUP OBJECTS { etherWisDeviceTestPatternType, etherWisDeviceRxTestPatternMode, etherWisDeviceTxTestPatternMode } STATUS current DESCRIPTION"The count"A collection ofSeverely Errored Seconds in the measuring interval."objects that control test features required of all WIS devices." ::= {etherWisPathIntervalEntry 3etherWisGroups 1 } etherWisSectionGroup OBJECT-GROUP OBJECTS { etherWisSectionCurrentJ0Transmitted, etherWisSectionCurrentJ0Received }etherWisPathIntervalCVs OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-onlySTATUS current DESCRIPTION"The count"A collection ofCoding Violations in the measuring interval."objects that provide required information about a WIS section." ::= {etherWisPathIntervalEntry 4etherWisGroups 2 } etherWisPathGroup OBJECT-GROUP OBJECTS { etherWisPathCurrentStatus, etherWisPathCurrentJ1Transmitted, etherWisPathCurrentJ1Received }etherWisPathIntervalUASs OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-onlySTATUS current DESCRIPTION"The count"A collection ofUnavailable Seconds in the measuring interval."objects that provide required information about a WIS path." ::= {etherWisPathIntervalEntry 5 } -- -- Conformance Statements --etherWisGroupsOBJECT IDENTIFIER ::=3 } etherWisFarEndPathGroup OBJECT-GROUP OBJECTS {etherWisConformance 1etherWisFarEndPathCurrentStatus }etherWisCompliances OBJECT IDENTIFIERSTATUS current DESCRIPTION "A collection of objects that provide required information about the far end of a WIS path." ::= {etherWisConformance 2etherWisGroups 4 } -- Compliance Statements etherWisCurrentCompliance MODULE-COMPLIANCE STATUS current DESCRIPTION "The compliance statement forimplementations which do not support historical data."this module." MODULE -- this module MANDATORY-GROUPS { etherWisDeviceGroup,etherWisSectionCurrentGroup, etherWisLineCurrentGroup, etherWisPathCurrentGroupetherWisSectionGroup, etherWisPathGroup, etherWisFarEndPathGroup }::=MODULE SONET-MIB MANDATORY-GROUPS {etherWisCompliances 1sonetMediumStuff2, sonetSectionStuff2, sonetLineStuff2, sonetFarEndLineStuff2, sonetPathStuff2, sonetFarEndPathStuff2 }etherWisIntervalCompliance MODULE-COMPLIANCE STATUS currentOBJECT sonetMediumType SYNTAX INTEGER { sonet(1) } MIN-ACCESS read-only DESCRIPTION"The compliance statement"Write access is not required, nor is support forimplementations whichany value other than sonet(1)." OBJECT sonetMediumLineCoding SYNTAX INTEGER { sonetMediumNRZ(4) } MIN-ACCESS read-only DESCRIPTION "Write access is not required, nor is supporthistorical data." MODULE -- this module MANDATORY-GROUPSfor any value other than sonetMediumNRZ(4)." OBJECT sonetMediumLineType MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT sonetMediumCircuitIdentifier MIN-ACCESS read-only DESCRIPTION "Write access is not required." OBJECT sonetMediumLoopbackConfig SYNTAX BITS {etherWisDeviceGroup, etherWisSectionCurrentGroup, etherWisSectionIntervalGroup, etherWisLineCurrentGroup, etherWisLineIntervalGroup, etherWisPathCurrentGroup, etherWisPathIntervalGroupsonetNoLoop(0), sonetFacilityLoop(1) } MIN-ACCESS read-only DESCRIPTION "Write access is not required, nor is support for values other than sonetNoLoop(0) and sonetFacilityLoop(1)." OBJECT sonetSESthresholdSet MIN-ACCESS read-only DESCRIPTION "Write access is not required, and only one of the enumerated values need be supported." OBJECT sonetPathCurrentWidth SYNTAX INTEGER { sts192cSTM64(6) } MIN-ACCESS read-only DESCRIPTION "Write access is not required, nor is support for any value other than sts192cSTM64(6)." ::= { etherWisCompliances2 } etherWisDeviceGroup OBJECT-GROUP OBJECTS { etherWisDeviceReset, etherWisDeviceLoopback, etherWisDeviceSpeedSelection, etherWisDevicePowerDown, etherWisDevicePresent, etherWisDeviceModesAllowed, etherWisDeviceModeSelect, etherWisDeviceJitterTestMode1 }STATUS current DESCRIPTION "A collectionEND 5. Acknowledgments 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 Ethernet Task Force. 6. Security Considerations There are a number of management objectswhich provide information aboutdefined in this MIB that have a MAX-ACCESS clause of read-write and/or read-create. Such objects may be considered sensitive or vulnerable in some network environments. The support for SET operations in a non-secure environment without proper protection can have a negative effect on network operations. SNMPv1 by itself is not a secure environment. Even if thestatenetwork itself is secure (for example by using IPSec), even then, there is no control as to who on the secure network is allowed to access and GET/SET (read/change/create/delete) the objects in this MIB. It is recommended that the implementers consider the security features as provided by the SNMPv3 framework. Specifically, the use of theWIS device." ::= { etherWisGroups 1 } etherWisSectionCurrentGroup OBJECT-GROUP OBJECTS { etherWisSectionCurrentJ0Transmitted, etherWisSectionCurrentJ0Expected, etherWisSectionCurrentJ0Received, etherWisSectionCurrentStatus, etherWisSectionCurrentESs, etherWisSectionCurrentSESs, etherWisSectionCurrentSEFSs, etherWisSectionCurrentCVs } STATUS current DESCRIPTION "A collectionUser-based Security Model RFC 2574 [RFC2574] and the View- based Access Control Model RFC 2575 [RFC2575] is recommended. It is then a customer/user responsibility to ensure that the SNMP entity giving access to an instance of this MIB, 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 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for Describing SNMP Management Frameworks", RFC 2571, April 1999. [RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification ofobjects which provide information aboutManagement Information for TCP/IP-based Internets", STD 16, RFC 1155, May 1990. [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 16, RFC 1212, March 1991. [RFC1215] M. Rose, "A Convention for Defining Traps for use with thecurrent stateSNMP", RFC 1215, March 1991. [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., and S. Waldbusser, "Structure ofthe WIS section." ::= { etherWisGroupsManagement Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., and S. Waldbusser, "Textual Conventions for SMIv2", STD 58, RFC 2579, April 1999. [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., and S. Waldbusser, "Conformance Statements for SMIv2", STD 58, RFC 2580, April 1999. [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. [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport Mappings for Version 2} etherWisSectionIntervalGroup OBJECT-GROUP OBJECTS { etherWisSectionIntervalNumber, etherWisSectionIntervalESs, etherWisSectionIntervalSESs, etherWisSectionIntervalSEFSs, etherWisSectionIntervalCVs } STATUS current DESCRIPTION "A collectionofobjects which provide historical data abouttheWIS section." ::= { etherWisGroups 3 } etherWisLineCurrentGroup OBJECT-GROUP OBJECTS { etherWisLineCurrentStatus, etherWisLineCurrentESs, etherWisLineCurrentSESs, etherWisLineCurrentCVs, etherWisLineCurrentUASs } STATUS current DESCRIPTION "A collection of objects which provide information aboutSimple Network Management Protocol (SNMPv2)", RFC 1906, January 1996. [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message Processing and Dispatching for thecurrent stateSimple Network Management Protocol (SNMP)", RFC 2572, April 1999. [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for version 3 of theWIS line." ::= { etherWisGroups 4 } etherWisLineIntervalGroup OBJECT-GROUP OBJECTS { etherWisLineIntervalNumber, etherWisLineIntervalESs, etherWisLineIntervalSESs, etherWisLineIntervalCVs, etherWisLineIntervalUASs } STATUS current DESCRIPTION "A collectionSimple Network Management Protocol (SNMPv3)", RFC 2574, April 1999. [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol Operations for Version 2 ofobjects which provide historical data abouttheWIS line." ::= { etherWisGroups 5 } etherWisPathCurrentGroup OBJECT-GROUP OBJECTS { etherWisPathCurrentStatus, etherWisPathCurrentESs, etherWisPathCurrentSESs, etherWisPathCurrentCVs, etherWisPathCurrentUASs } STATUS current DESCRIPTION "A collectionSimple 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. [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, "Introduction to Version 3 ofobjects which provide information aboutthecurrent stateInternet-standard Network Management Framework", RFC 2570, April 1999. [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate Requirements Levels", BCP 14, RFC 2119, March 1997. [RFC2863] McCloghrie, K., and F. Kastenholz, "The Interfaces Group MIB", RFC 2863, June 2000. [RFC2864] McCloghrie, K., and G. Hanson, "The Inverted Stack Table Extension to the Interfaces Group MIB", RFC 2864, June 2000. [SONETng] Tesink, K., "Definitions of Managed Objects for theWIS path." ::= { etherWisGroups 6 } etherWisPathIntervalGroup OBJECT-GROUP OBJECTS { etherWisPathIntervalNumber, etherWisPathIntervalESs, etherWisPathIntervalSESs, etherWisPathIntervalCVs, etherWisPathIntervalUASs } STATUS current DESCRIPTION "A collectionSONET/SDH Interface Type", rfc2558 update (forthcoming), work in progress. [T1.231] American National Standard for Telecommunications - Digital Hierarchy - Layer 1 In-Service Digital Transmission Performance Monitoring, ANSI T1.231-1997, September 1997. [ETHERIF] Flick, J., "Definitions ofobjects which provide historical data aboutManaged Objects for theWIS path." ::= { etherWisGroups 7 } END 4. Notice onEthernet-like Interface Types", <draft-ietf-hubmib-etherif- mib-v3-00.txt>, work in progress. [MAU-MIB] Flick, J., "Definitions of Managed Objects for IEEE 802.3 Medium Attachment Units (MAUs)", <draft-ietf-hubmib-mau- mib-v3-00.txt>, work in progress. [P802.3ae] Law, D., Editor, Draft Supplement to IEEE Std. 802.3, IEEE Draft P802.3ae/D3.3, October 23, 2001, work in progress. 8. Authors' Addresses Mike Ayers BMC Software, Inc. 2141 North First Street San Jose, CA 95131 USA Phone: +1 408 546 0947 Fax: +1 408 965 0359 Email: mayers@bmc.com John Flick Hewlett-Packard Company 8000 Foothills Blvd. M/S 5557 Roseville, CA 95747-5557 Phone: +1 916 785 4018 Fax: +1 916 785 1199 Email: johnf@rose.hp.com C. M. Heard 600 Rainbow Dr. #141 Mountain View, CA 94041-2542 USA Phone: +1 650 964 8391 EMail: heard@pobox.com Kam Lam Lucent Technologies 101 Crawfords Corner Road, Room 4C-616A Holmdel, NJ 07733 Phone: +1 732 949 8338 EMail: hklam@lucent.com Kerry McDonald Institute for Applied Supercomputing California State University San Bernardino Email: kerry_mcd@hotmail.com kmcdonal@csci.csusb.edu K. C. Norseth Enterasys Networks 2691 South Decker Lake Lane Salt Lake City, Utah 84119 Phone: +1 801 887 9823 Email: knorseth@enterasys.com Kaj Tesink Telcordia Technologies 331 Newman Springs Road P.O. Box 7020 Red Bank, NJ 07701-7020 USA Phone: +1 732 758 5254 EMail: kaj@research.telcordia.com 9. Intellectual Property The IETF takes no position regarding the validity or scope of any intellectual property or other rights that might be claimed to pertain to the implementation or use of the technology described in this document or the extent to which any license under such rights might or might not be available; neither does it represent that it has made any effort to identify any such rights. Information on the IETF's procedures with respect to rights in standards-track and standards-related documentation can be found in BCP-11. Copies of claims of rights made available for publication and any assurances of licenses to be made available, or the result of an attempt made to obtain a general license or permission for the use of such proprietary rights byimplementors or users of this specification can be obtained from the IETF Secretariat. The IETF invites any interested party to bring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to practice this standard. Please address the information to the IETF Executive Director. 5. Acknowledgments This document is the product of the IETF Hubmib Working Group. 6. Security There are a number of management objects defined in this MIB that have a MAX-ACCESS clause of read-write and/or read-create. Such objects may be considered sensitive or vulnerable in some network environments. The support for SET operations in a non-secure environment without proper protection can have a negative effect on network operations. SNMPv1 by itself is not a secure environment. Even if the network itself is secure (for example by using IPSec), even then, there is no control as to who on the secure network is allowed to access and GET/SET (read/change/create/delete) the objects in this MIB. It is recommended that the implementers consider the security features as provided by the SNMPv3 framework. Specifically, the use of the User-based Security Model RFC 2574 [RFC2574] and the View- based Access Control Model RFC 2575 [RFC2575] is recommended. It is then a customer/user responsibilityimplementors or users of this specification can be obtained from the IETF Secretariat. The IETF invites any interested party toensurebring to its attention any copyrights, patents or patent applications, or other proprietary rights which may cover technology that may be required to practice this standard. Please address theSNMP entity giving accessinformation toan instancethe IETF Executive Director. Appendix A: Collection of Performance Data Using WIS MDIO Registers The purpose of thisMIB,appendix isproperly configured to give accessto illustrate how theobjects only to those principals (users) that have legitimate rights to indeed GET or SET (change/create/delete) them. 7. References [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, An Architecture for Describing SNMP Management Frameworks, RFC 2571, April 1999. [RFC1155] Rose, M., and K. McCloghrie, Structure and Identification of Management Information for TCP/IP-based Internets, STD 16, RFC 1155, May 1990. [RFC1212] Rose, M., and K. McCloghrie, Concise MIB Definitions, STD 16, RFC 1212, March 1991. [RFC1215] M. Rose, A Convention for Defining Traps for use withWIS MDIO registers specified in [P802.3ae] subclause 45.2.2 (and more specifically theSNMP, RFC 1215, March 1991. [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., and S. Waldbusser, Structure of Management Information Version 2 (SMIv2), STD 58, RFC 2578, April 1999. [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., and S. Waldbusser, Textual Conventions for SMIv2, STD 58, RFC 2579, April 1999. [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., Rose, M., and S. Waldbusser, Conformance Statements for SMIv2, STD 58, RFC 2580, April 1999. [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, Introductionsubset required by [P802.3ae] subclause 50.3.10) can be used toCommunity-based SNMPv2, RFC 1901, January 1996. [RFC1906] Case, J., McCloghrie, K., Rose, M.,collect performance data either according to the conventions adopted by this document or according to the conventions specified in [P802.3ae] Clause 30. For an agent implementing the SNMP managed objects required by this document the first step in collecting WIS performance data would be to poll the 10G WIS Status 3 register andS. Waldbusser, Transport Mappings for Version 2 oftheSimple Network Management Protocol (SNMPv2), RFC 1906, January 1996. [RFC2572] Case, J., Harrington D., Presuhn R.,various error count 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, andB. Wijnen, Message Processing10G WIS Far End Path Block Error Count) once per second. The 10G WIS Status 3 register bits are all latched until read andDispatching forso would indicate whether a given defect occurred any time during theSimple Network Management Protocol (SNMP), RFC 2572, April 1999. [RFC2574] Blumenthal, U.,previous second. The error count registers roll over modulo 2^16 or 2^32, andB. Wijnen, User-based Security Model (USM)so to find the number of errors within the previous second the agent would need to subtract (modulo 2^16 or 2^32) the current reading from the reading taken one second ago. Armed with that information, the agent could determine forversion 3any layer whether the one second interval was an errored second, a severely errored second (that requires comparison with a threshold unless a defect is present), or a severely errored frame second. Determining whether a given second is or is not part of unavailable time requires additional logic; theSimple Network Management Protocol (SNMPv3), RFC 2574, April 1999. [RFC1905] Case, J., McCloghrie, K., Rose, M.,most straightforward andS. Waldbusser, Protocol Operations for Version 2accurate method is the delay-line approach outlined in Appendix A of [SONETng]. With that information available theSimple Network Management Protocol (SNMPv2), RFC 1905, January 1996. [RFC2573] Levi, D., Meyer, P.,agent would be able to determine by how much each current count should be incremented (including effects of inhibiting). 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 approach is used then a time-of-day timestamp would accompany the one-second statistics. At the end of each interval the current registers would be pushed onto the history stack andB. Stewart, SNMPv3 Applications, RFC 2573, April 1999. [RFC2575] Wijnen, B., Presuhn, R.,then would be cleared. The xyxIntervalValidData flags would be set to False(2) if the number of samples was not between 890 andK. McCloghrie, View-based Access Control Model (VACM)910 or, in the case of far-end counts, if a near-end defect occurred during the just- completed interval (see [T1.231] Section 9.1.2.2 for details). An agent implementing theSimple Network Management Protocol (SNMP), RFC 2575, April 1999. [RFC2570] Case, J., Mundy, R., Partain, D.,[P802.3ae] Clause 30 oWIS objects could start in much the same way, i.e., by polling the 10G WIS Status 3 register andB. Stewart, Introductionthe various error count registers toVersion 3 offind theInternet-standard Network Management Framework, RFC 2570, April 1999. 8. Editor's Address Mike Ayers BMC Software, Inc. 2141 North First Street San Jose, CA 95131 USA Phone: +1 408 546 0947 Fax: +1 408 965 0359 Email: mayers@bmc.com Kerry McDonald Institutedefects and error counts forApplied Supercomputing California State University San Bernardino Email: kerry_mcd@hotmail.com kmcdonal@csci.csusb.edu K.C. Norseth Enterasys Networks 2691 South Decker Lake Lane Salt Lake City, Utah 84119 Phone: +1 801 887 9823 Email: knorseth@enterasys.com John Flick Hewlett-Packard Company 8000 Foothills Blvd. M/S 5557 Roseville, CA 95747-5557 Phone: +1 916 785 4018 Fax: +1 916 785 1199 Email: johnf@rose.hp.com 9.the previous second, and it could determine the number of errors and whether the second was an errored second, a severely errored second, or a severely errored frame second in the same manner as above. The rest of the process would be simply to increment the generalized non-resetable counters without consideration of any inhibiting rules. Full Copyright Statement Copyright (C) The Internet Society (2001). All Rights Reserved. This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this paragraph are included on all such copies and derivative works. However, this document itself may not be modified in any way, such as by removing the copyright notice or references to the Internet Society or other Internet organizations, except as needed for the purpose of developing Internet standards in which case the procedures for copyrights defined in the Internet Standards process must be followed, or as required to translate it into languages other than English. The limited permissions granted above are perpetual and will not be revoked by the Internet Society or its successors or assigns. This document and the information contained herein is provided on an "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Table of Contents 1 Abstract ..................................................... 2 2 The SNMP Management Framework ................................ 2 3 Overview ..................................................... 3 3.1 Relationship to the SONET MIB .............................. 4 3.2 Relationship to the Ethernet-like Interfaces MIB ........... 4 3.3 Relationship to the 802.3 MAU MIB .......................... 4 3.4 Use of the ifTable ......................................... 4 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 ........................................................... 5 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 ................................. 14 3.8.4 etherWisFarEndPathCurrentTable ........................... 15 4 Object Definitions ........................................... 16 5 Acknowledgments .............................................. 28 6 Security Considerations ...................................... 28 7 References ................................................... 29 8 Authors' Addresses ........................................... 31 9 Intellectual Property ........................................ 32 Appendix A: Collection of Performance Data Using WIS MDIO Registers ................................................. 33 Full Copyright Statement ...................................... 34