idnits 2.17.1 draft-ietf-hubmib-wis-mib-02.txt: ** The Abstract section seems to be numbered Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document is more than 15 pages and seems to lack a Table of Contents. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** The abstract seems to contain references ([ETHERIF], [MAU-MIB], [RFC2119], [RFC2863], [SONETng], [RFC2864]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. == There are 3 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 1681 has weird spacing: '... Use of ...' == Line 1685 has weird spacing: '... Use of ifTab...' == Line 1689 has weird spacing: '...Objects to W...' -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (February 18, 2002) is 8103 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 2571 (Obsoleted by RFC 3411) ** Downref: Normative reference to an Informational RFC: RFC 1215 ** Downref: Normative reference to an Historic RFC: RFC 1157 ** Downref: Normative reference to an Historic RFC: RFC 1901 ** Obsolete normative reference: RFC 1906 (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2572 (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2574 (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 1905 (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2573 (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2575 (Obsoleted by RFC 3415) ** Obsolete normative reference: RFC 2570 (Obsoleted by RFC 3410) ** Obsolete normative reference: RFC 2558 (ref. 'SONETng') (Obsoleted by RFC 3592) -- Possible downref: Non-RFC (?) normative reference: ref. 'ETHERIF' -- Possible downref: Non-RFC (?) normative reference: ref. 'MAU-MIB' Summary: 19 errors (**), 0 flaws (~~), 6 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Ethernet Interfaces and Hub MIB Working Group Mike Ayers 3 INTERNET DRAFT BMC Software, Inc. 4 John Flick 5 Hewlett-Packard Company 6 C. M. Heard 7 Consultant 8 Kam Lam 9 Lucent Technologies 10 Kerry McDonald 11 CSU San Bernardino 12 K. C. Norseth 13 Enterasys Networks 14 Kaj Tesink 15 Telcordia Technologies 16 February 18, 2002 18 Definitions of Managed Objects 19 for the Ethernet WAN Interface Sublayer 20 22 Status of this Memo 24 This document is an Internet-Draft and is in full conformance with 25 all provisions of Section 10 of RFC2026. Internet-Drafts are working 26 documents of the Internet Engineering Task Force (IETF), its areas, 27 and its working groups. Note that other groups may also distribute 28 working documents as Internet-Drafts. 30 Internet-Drafts are draft documents valid for a maximum of six months 31 and may be updated, replaced, or obsoleted by other documents at any 32 time. It is inappropriate to use Internet-Drafts as reference 33 material or to cite them other than as "work in progress." 35 The list of current Internet-Drafts can be accessed at 36 http://www.ietf.org/ietf/1id-abstracts.txt 38 The list of Internet-Draft Shadow Directories can be accessed at 39 http://www.ietf.org/shadow.html 41 Copyright Notice 43 Copyright (C) The Internet Society (2002). All Rights Reserved. 45 1. Abstract 47 This document defines a portion of the Management Information Base 48 (MIB) for use with network management protocols in TCP/IP based 49 internets. In particular, it defines objects for managing the 50 Ethernet Wide Area Network (WAN) Interface Sublayer (WIS) [P802.3ae]. 52 The MIB module defined in this memo is implemented in conjunction 53 with the Ethernet-like Interface MIB [ETHERIF], the 802.3 Medium 54 Attachment Unit MIB [MAU-MIB], the Interfaces Group MIB [RFC2863], 55 and the Inverted Stack Table MIB [RFC2864]. It also extends the 56 SONET MIB [SONETng] and is implemented in conjunction with that MIB 57 module. 59 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 60 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 61 document are to be interpreted as described in [RFC2119]. 63 2. The SNMP Management Framework 65 The SNMP Management Framework presently consists of five major 66 components: 68 o An overall architecture, described in RFC 2571 [RFC2571]. 70 o Mechanisms for describing and naming objects and events for the 71 purpose of management. The first version of this Structure of 72 Management Information (SMI) is called SMIv1 and described in 73 STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 74 1215 [RFC1215]. The second version, called SMIv2, is described 75 in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and 76 STD 58, RFC 2580 [RFC2580]. 78 o Message protocols for transferring management information. The 79 first version of the SNMP message protocol is called SNMPv1 and 80 described in STD 15, RFC 1157 [RFC1157]. A second version of 81 the SNMP message protocol, which is not an Internet standards 82 track protocol, is called SNMPv2c and described in RFC 1901 83 [RFC1901] and RFC 1906 [RFC1906]. The third version of the 84 message protocol is called SNMPv3 and described in RFC 1906 85 [RFC1906], RFC 2572 [RFC2572] and RFC 2574 [RFC2574]. 87 o Protocol operations for accessing management information. The 88 first set of protocol operations and associated PDU formats is 89 described in STD 15, RFC 1157 [RFC1157]. A second set of 90 protocol operations and associated PDU formats is described in 91 RFC 1905 [RFC1905]. 93 o A set of fundamental applications described in RFC 2573 94 [RFC2573] and the view-based access control mechanism described 95 in RFC 2575 [RFC2575]. 97 A more detailed introduction to the current SNMP Management Framework 98 can be found in RFC 2570 [RFC2570]. 100 Managed objects are accessed via a virtual information store, termed 101 the Management Information Base or MIB. Objects in the MIB are 102 defined using the mechanisms defined in the SMI. 104 This memo specifies a MIB module that is compliant to the SMIv2. A 105 MIB conforming to the SMIv1 can be produced through the appropriate 106 translations. The resulting translated MIB must be semantically 107 equivalent, except where objects or events are omitted because no 108 translation is possible (use of Counter64). Some machine readable 109 information in SMIv2 will be converted into textual descriptions in 110 SMIv1 during the translation process. However, this loss of machine 111 readable information is not considered to change the semantics of the 112 MIB. 114 3. Overview 116 The objects defined in this memo are used in conjunction with objects 117 defined in the Interfaces Group MIB [RFC2863], the SONET MIB 118 [SONETng], and the MAU MIB [MAU-MIB] to manage the WAN Interface 119 Sublayer (WIS) defined in [P802.3ae]. The WIS contains functions to 120 perform OC-192c/VC-4-64c framing and scrambling. It resides between 121 the PCS and PMA sublayers within a 10GBASE-W 10 Gb/s WAN-compatible 122 PHY and may be used in conjunction with any of the PCS, PMA, and PMD 123 sublayers that are defined in [P802.3ae] for 10GBASE-W PHYs. Three 124 types of 10GBASE-W PHYs are defined, distinguished by the type of 125 optics employed: 10GBASE-SW, 10GBASE-LW, and 10GBASE-EW. The 126 objects defined in this memo may be used to manage an Ethernet 127 interface employing any type of 10GBASE-W PHY. They do not apply to 128 any other kind of interface. In particular, they do not apply to 129 so-called Ethernet Line Terminating Equipment (ELTE) residing within 130 a SONET network element that uses the 10GBASE-W PMA/PMD sublayers but 131 otherwise acts as SONET Line Terminating Equipment (LTE). 133 The objects presented here -- along with those incorporated by 134 reference from the Interfaces Group MIB, the SONET MIB, and the MAU 135 MIB -- are intended to provide exact representations of the mandatory 136 attributes in the oWIS managed object class (i.e., the members of the 137 pWISBasic package) defined in Clause 30 and Annex 30A of [P802.3ae]. 138 They are also intended to provide approximate representations of the 139 optional attributes (i.e., the members of the pWISOptional package). 140 Some objects with no analogues in oWIS are defined to support WIS 141 testing features required by Clause 50 of [P802.3ae]. 143 3.1. Relationship to the SONET MIB 145 Since the Ethernet WAN Interface Sublayer was designed to be SONET- 146 compatible, information similar to that provided by most of the 147 members of the oWIS managed object class is available from objects 148 defined in the SONET MIB [SONETng]. Thus, the MIB module defined in 149 this memo is a sparse augmentation of the SONET MIB -- in other 150 words, every table defined here is an extension of some table in the 151 SONET MIB -- and its compliance statement REQUIRES that an agent 152 implementing the objects defined in this memo also implement the 153 relevant SONET MIB objects. That includes all objects required by 154 sonetCompliance2 as well as some that it leaves optional. 156 It should be noted that some of the objects incorporated by reference 157 from the SONET MIB -- specifically, the threshold objects and 158 interval counter objects -- provide only approximate representations 159 of the corresponding oWIS attributes, as detailed in Section 3.6. An 160 alternative approach would have been to define new objects to exactly 161 match the oWIS definitions. That approach was rejected because the 162 SONET MIB objects are already used in deployed systems to manage the 163 SONET sublayers of ATM over SONET and PPP over SONET interfaces, and 164 it was deemed undesirable to use a different scheme to manage the 165 SONET sublayers of 10 Gb/s WAN-compatible Ethernet interfaces. Note 166 that the approach adopted by this memo requires no hardware support 167 beyond that mandated by [P802.3ae] subclause 50.3.10. 169 3.2. Relationship to the Ethernet-like Interfaces MIB 171 An interface which includes the Ethernet WIS is, by definition, an 172 Ethernet-like interface, and an agent implementing the objects 173 defined in this memo MUST implement the objects required by the 174 dot3Compliance2 compliance statement in the EtherLike-MIB. 176 3.3. Relationship to the 802.3 MAU MIB 178 Support for the mauModIfCompl2 compliance statement of the MAU-MIB 179 [MAU-MIB] is REQUIRED for all Ethernet-like interfaces. The MAU-MIB 180 is needed in order to allow applications to control and/or determine 181 the media type in use. That is important for devices than can 182 support both the 10GBASE-R 10 Gb/s LAN format (which does not include 183 the WIS) and the 10GBASE-W 10 Gb/s WAN format (which does include the 184 WIS). The MAU-MIB also provides the means to put a device in standby 185 mode or to reset it; the latter may be used to re-initialize the 186 WIS. 188 3.4. Use of the ifTable 190 This section specifies how the ifTable, as defined in [RFC2863], is 191 used for the Ethernet WIS application. 193 3.4.1. Layering Model 195 Ethernet interfaces that employ the WIS are layered as defined in 196 [P802.3ae]. The corresponding use of the ifTable [RFC2863] is shown 197 in the figure below. 199 _____________________________ _ 200 | LLC Layer | | 201 +-----------------------------+ | 202 | MAC Layer | | 203 +-----------------------------+ > 1 ifEntry 204 | Reconciliation Sublayer | | ifType: ethernetCsmacd(6) 205 +-----------------------------+ | 206 | Physical Coding Sublayer | | 207 +-----------------------------+ + 208 | Path Layer | > 1 ifEntry 209 +-----------------------------+ + ifType: sonetPath(50) 210 | Line Layer | | 211 +-----------------------------+ | 212 | Section Layer | > 1 ifEntry 213 +-----------------------------+ | ifType: sonet(39) 214 | Physical Medium Layer | | 215 ----------------------------- - 217 Figure 1 - Use of ifTable for an Ethernet WIS port 219 The exact configuration and multiplexing of the layers is maintained 220 in the ifStackTable [RFC2863] and in the ifInvStackTable [RFC2864]. 222 3.4.2. Use of ifTable for LLC Layer/MAC Layer/Reconciliation 223 Sublayer/Physical Coding Sublayer 225 The ifTable MUST be used as specified in [ETHERIF] and [MAU-MIB] for 226 the LLC Layer/MAC Layer/Reconciliation Sublayer/Physical Coding 227 Sublayer. 229 3.4.3. Use of ifTable for SONET/SDH Path Layer 231 The ifTable MUST be used as specified in [SONETng] for the SONET/SDH 232 Path Layer. The value of ifHighSpeed is set to 9585. ifSpeed 233 reports a value of 4294967295. 235 3.4.4. Use of ifTable for SONET/SDH Medium/Section/Line Layer 237 The ifTable MUST be used as specified in [SONETng] for the SONET/SDH 238 Medium/Section/Line Layer. The value of ifHighSpeed is set to 9953. 239 ifSpeed reports a value of 4294967295. 241 3.5. SONET/SDH Terminology 243 The SONET/SDH terminology used in [P802.3ae] is mostly the same as in 244 [SONETng], but there are a few differences. In those cases the 245 definitions in [P802.3ae] take precedence. The specific differences 246 are as follows. 248 Unequipped 249 This defect is not defined by [P802.3ae]. An implementation that 250 supports it SHOULD report it by setting the sonetPathUnequipped 251 bit in the appropriate instance of sonetPathCurrentStatus. 253 Signal Label Mismatch 254 This defect is called Payload Label Mismatch (PLM) in [P802.3ae]. 255 It is reported by setting both the sonetPathSignalLabelMismatch 256 bit in the appropriate instance of sonetPathCurrentStatus 257 (defined in [SONETng]) and the etherWisPathPLM bit in the 258 corresponding instance of etherWisPathCurrentStatus (defined 259 below). 261 Loss of Codegroup Delineation 262 [P802.3ae] defines Loss of Codegroup Delineation (LCD) as 263 occurring when the Physical Coding Sublayer is unable to locate 264 64B/66B code group boundaries. There is no analogous defect 265 defined in [SONETng]. It is reported by setting the 266 etherWisPathLCD bit in the appropriate instance of the object 267 etherWisPathCurrentStatus defined below. 269 STS-Path Remote Defect Indication 270 [P802.3ae] mandates the use of ERDI-P (Enhanced Remote Defect 271 Indication - Path) defined in [T1.231] to signal remote server 272 defects (triggered by path AIS or path LOP) and remote payload 273 defects (triggered by Payload Label Mismatch or Loss of Codegroup 274 Delineation). [SONETng] defines the one-bit RDI-P (Remote Defect 275 Indication - Path), which signals remote server detects (i.e., 276 path AIS and path LOP) only. An implementation of the MIB module 277 defined in this memo MUST set the sonetPathSTSRDI bit in the 278 appropriate instance of sonetPathCurrentStatus when it receives 279 an ERDI-P server defect indication from the remote end. Both 280 ERDI-P payload defects and ERDI-P server defects are reported in 281 the object etherWisFarEndPathCurrentStatus defined below. 283 Path Coding Violations 284 In [P802.3ae] the path layer CV count is based on block errors 285 and not BIP-8 errors, i.e., it is incremented only once for each 286 B3 byte that indicates incorrect parity, regardless of the number 287 of bits in error. Note that Section 8.4.5.1 of [T1.231] allows 288 either path BIP-8 errors or path block errors to be used for the 289 path layer error count. 291 3.6. Mapping of IEEE 802.3 Managed Objects 293 This section contains the mapping between oWIS managed objects 294 defined in [P802.3ae] and managed objects defined in this document 295 and in associated MIB modules, i.e., the IF-MIB [RFC2863], the 296 SONET-MIB [SONETng], and the MAU-MIB [MAU-MIB]. 298 IEEE 802.3 Managed Object Corresponding SNMP Object 300 oWIS - pWISBasic package 301 aWISID IF-MIB - ifIndex 302 aSectionStatus SONET-MIB - sonetSectionCurrentStatus 303 aLineStatus SONET-MIB - sonetLineCurrentStatus 304 aPathStatus etherWisPathCurrentStatus 305 aFarEndPathStatus etherWisFarEndPathCurrentStatus 307 oWIS - pWISOptional package 308 aSectionSESThreshold SONET-MIB - sonetSESthresholdSet 309 aSectionSESs SONET-MIB - sonetSectionCurrentSESs + 310 sonetSectionIntervalSESs 311 aSectionESs SONET-MIB - sonetSectionCurrentESs + 312 sonetSectionIntervalESs 313 aSectionSEFSs SONET-MIB - sonetSectionCurrentSEFSs + 314 sonetSectionIntervalSEFSs 315 aSectionCVs SONET-MIB - sonetSectionCurrentCVs + 316 sonetSectionIntervalCVs 317 aJ0ValueTX etherWisSectionCurrentJ0Transmitted 318 aJ0ValueRX etherWisSectionCurrentJ0Received 319 aLineSESThreshold SONET-MIB - sonetSESthresholdSet 320 aLineSESs SONET-MIB - sonetLineCurrentSESs + 321 sonetLineIntervalSESs 322 aLineESs SONET-MIB - sonetLineCurrentESs + 323 sonetLineIntervalESs 324 aLineCVs SONET-MIB - sonetLineCurrentCVs + 325 sonetLineIntervalCVs 326 aFarEndLineSESs SONET-MIB - sonetFarEndLineCurrentSESs + 327 sonetFarEndLineIntervalSESs 328 aFarEndLineESs SONET-MIB - sonetFarEndLineCurrentESs + 329 sonetFarEndLineIntervalESs 330 aFarEndLineCVs SONET-MIB - sonetFarEndLineCurrentCVs + 331 sonetFarEndLineIntervalCVs 332 aPathSESThreshold SONET-MIB - sonetSESthresholdSet 333 aPathSESs SONET-MIB - sonetPathCurrentSESs + 334 sonetPathIntervalSESs 335 aPathESs SONET-MIB - sonetPathCurrentESs + 336 sonetPathIntervalESs 337 aPathCVs SONET-MIB - sonetPathCurrentCVs + 338 sonetPathIntervalCVs 339 aJ1ValueTX etherWisPathCurrentJ1Transmitted 340 aJ1ValueRX etherWisPathCurrentJ1Received 341 aFarEndPathSESs SONET-MIB - sonetFarEndPathCurrentSESs + 342 sonetFarEndPathIntervalSESs 343 aFarEndPathESs SONET-MIB - sonetFarEndPathCurrentESs + 344 sonetFarEndPathIntervalESs 345 aFarEndPathCVs SONET-MIB - sonetFarEndPathCurrentCVs + 346 sonetFarEndPathIntervalCVs 348 It should be noted that the threshold and counter objects imported 349 from the SONET-MIB are not completely equivalent to the corresponding 350 IEEE 802.3 objects. The specific differences are as follows: 352 IEEE 802.3 Managed Object How Corresponding SNMP Object Differs 354 oWIS - pWISOptional package 355 aSectionSESThreshold This object is defined in [P802.3ae] 356 as an integer with one instance per 357 interface. sonetSESthresholdSet 358 is an enumerated value that has one 359 instance per network element; it 360 controls the thresholds for all layers 361 simultaneously and allows only certain 362 discrete values to be selected. 363 aSectionSESs This object is defined in [P802.3ae] as 364 a generalized nonresetable counter. 365 The objects sonetSectionCurrentSESs and 366 sonetSectionIntervalSESs are 15-minute 367 interval counters. 368 aSectionESs This object is defined as a generalized 369 nonresetable counter in [P802.3ae]. 370 The objects sonetSectionCurrentESs and 371 sonetSectionIntervalESs are 15-minute 372 interval counters. 373 aSectionSEFSs This object is defined as a generalized 374 nonresetable counter in [P802.3ae]. 375 The objects sonetSectionCurrentSEFSs and 376 sonetSectionIntervalSEFSs are 15-minute 377 interval counters. 378 aSectionCVs This object is defined as a generalized 379 nonresetable counter in [P802.3ae], and 380 it is not subject to inhibiting. The 381 objects sonetSectionCurrentCVs and 382 sonetSectionIntervalCVs are 15-minute 383 interval counters, and they are 384 inhibited (not incremented) during 385 one-second intervals that qualify as 386 severely errored seconds. 387 aLineSESThreshold This object is defined in [P802.3ae] 388 as an integer with one instance per 389 interface. sonetSESthresholdSet 390 is an enumerated value that has one 391 instance per network element; it 392 controls the thresholds for all layers 393 simultaneously and allows only certain 394 discrete values to be selected. 395 aLineSESs This object is defined as a generalized 396 nonresetable counter in [P802.3ae], and 397 it is not subject to inhibiting. The 398 objects sonetLineCurrentSESs and 399 sonetLineIntervalSESs are 15-minute 400 interval counters, and they are 401 inhibited (not incremented) during 402 one-second intervals that qualify as 403 unavailable seconds. 404 aLineESs This object is defined as a generalized 405 nonresetable counter in [P802.3ae], and 406 it is not subject to inhibiting. The 407 objects sonetLineCurrentESs and 408 sonetLineIntervalESs are 15-minute 409 interval counters, and they are 410 inhibited (not incremented) during 411 one-second intervals that qualify as 412 unavailable seconds. 413 aLineCVs This object is defined as a generalized 414 nonresetable counter in [P802.3ae], and 415 it is not subject to inhibiting. The 416 objects sonetLineCurrentCVs and 417 sonetLineIntervalCVs are 15-minute 418 interval counters, and they are 419 inhibited (not incremented) during 420 one-second intervals that qualify 421 either as severely errored seconds 422 or as unavailable seconds. 423 aFarEndLineSESs This object is defined as a generalized 424 nonresetable counter in [P802.3ae], and 425 it is not subject to inhibiting. The 426 objects sonetFarEndLineCurrentSESs and 427 sonetFarEndLineIntervalSESs are 428 15-minute interval counters, and they 429 are inhibited (not incremented) during 430 one-second intervals that qualify as 431 unavailable seconds. 432 aFarEndLineESs This object is defined as a generalized 433 nonresetable counter in [P802.3ae], and 434 it is not subject to inhibiting. The 435 objects sonetFarEndLineCurrentESs and 436 sonetFarEndLineIntervalESs are 15-minute 437 interval counters, and they are 438 inhibited (not incremented) during 439 one-second intervals that qualify as 440 unavailable seconds. 441 aFarEndLineCVs This object is defined as a generalized 442 nonresetable counter in [P802.3ae], and 443 it is not subject to inhibiting. The 444 objects sonetFarEndLineCurrentCVs and 445 sonetFarEndLineIntervalCVs are 15-minute 446 interval counters, and they are 447 inhibited (not incremented) during 448 one-second intervals that qualify 449 either as severely errored seconds 450 or as unavailable seconds. 451 aPathSESThreshold This object is defined in [P802.3ae] 452 as an integer with one instance per 453 interface. sonetSESthresholdSet 454 is an enumerated value that has one 455 instance per network element; it 456 controls the thresholds for all layers 457 simultaneously and allows only certain 458 discrete values to be selected. 459 aPathSESs This object is defined as a generalized 460 nonresetable counter in [P802.3ae], and 461 it is not subject to inhibiting. The 462 objects sonetPathCurrentSESs and 463 sonetPathIntervalSESs are 15-minute 464 interval counters, and they are 465 inhibited (not incremented) during 466 one-second intervals that qualify as 467 unavailable seconds. In addition, 468 [P802.3ae] includes PLM-P and LCD-P 469 defects in the criteria for declaring 470 path layer severely errored seconds, 471 while [SONETng] does not. 472 aPathESs This object is defined as a generalized 473 nonresetable counter in [P802.3ae], and 474 it is not subject to inhibiting. The 475 objects sonetPathCurrentESs and 476 sonetPathIntervalESs are 15-minute 477 interval counters, and they are 478 inhibited (not incremented) during 479 one-second intervals that qualify as 480 unavailable seconds. In addition, 481 [P802.3ae] includes PLM-P and LCD-P 482 defects in the criteria for declaring 483 path layer errored seconds, while 484 [SONETng] does not. 485 aPathCVs This object is defined as a generalized 486 nonresetable counter in [P802.3ae], and 487 it is not subject to inhibiting. The 488 objects sonetPathCurrentCVs and 489 sonetPathIntervalCVs are 15-minute 490 interval counters, and they are 491 inhibited (not incremented) during 492 one-second intervals that qualify 493 either as severely errored seconds 494 or as unavailable seconds. 495 aFarEndPathSESs This object is defined as a generalized 496 nonresetable counter in [P802.3ae], and 497 it is not subject to inhibiting. The 498 objects sonetFarEndPathCurrentSESs and 499 sonetFarEndPathIntervalSESs are 500 15-minute interval counters, and they 501 are inhibited (not incremented) during 502 one-second intervals that qualify as 503 unavailable seconds. In addition, 504 [P802.3ae] includes far-end PLM-P and 505 LCD-P defects in the criteria for 506 declaring far-end path layer severely 507 errored seconds, while [SONETng] does 508 not. 509 aFarEndPathESs This object is defined as a generalized 510 nonresetable counter in [P802.3ae], and 511 it is not subject to inhibiting. The 512 objects sonetFarEndPathCurrentESs and 513 sonetFarEndPathIntervalESs are 15-minute 514 interval counters, and they are 515 inhibited (not incremented) during 516 one-second intervals that qualify as 517 unavailable seconds. In addition, 518 [P802.3ae] includes far-end PLM-P and 519 LCD-P defects in the criteria for 520 declaring far-end path layer errored 521 seconds, while [SONETng] does not. 522 aFarEndPathCVs This object is defined as a generalized 523 nonresetable counter in [P802.3ae], and 524 it is not subject to inhibiting. The 525 objects sonetFarEndPathCurrentCVs and 526 sonetFarEndPathIntervalCVs are 15-minute 527 interval counters, and they are 528 inhibited (not incremented) during 529 one-second intervals that qualify 530 either as severely errored seconds 531 or as unavailable seconds. 533 Please note that despite the differences in semantics between the 534 threshold objects and counter objects imported from the SONET-MIB and 535 the corresponding IEEE 802.3 objects, the hardware support mandated 536 by [P802.3ae] subclause 50.3.10 suffices for both. See Appendix A 537 for details. 539 3.7. Mapping of SNMP Objects to WIS Station Management Registers 541 Some of the objects defined in this memo or incorporated by reference 542 from the SONET-MIB [SONETng] or the MAU-MIB [MAU-MIB] require WIS- 543 specific hardware support. [P802.3ae] subclause 50.3.10 specifies 544 WIS management interface requirements, including a required subset of 545 the WIS MDIO (Management Data Input/Output) registers defined in 546 [P802.3ae] subclause 45.2.2. The table below provides a cross- 547 reference between those managed objects and the WIS MDIO registers 548 from the subset in [P802.3ae] subclause 50.3.10 required to support 549 them. Note that the MDIO interface is optional; however, if it is 550 not implemented, then the capabilities of the required register 551 subset must be provided by other means. 553 SNMP Object WIS MDIO Register(s) 555 ETHER-WIS - etherWisDeviceTxTestPatternMode 10G WIS Control 2 556 ETHER-WIS - etherWisDeviceRxTestPatternMode 10G WIS Control 2 557 ETHER-WIS - etherWisDeviceRxTestPatternErrors 10G WIS Test Pattern 558 Error Counter 560 SONET-MIB - sonetMediumType none required 561 SONET-MIB - sonetMediumTimeElapsed none required 562 SONET-MIB - sonetMediumValidIntervals none required 563 SONET-MIB - sonetMediumLineCoding none required 564 SONET-MIB - sonetMediumLineType none required 565 SONET-MIB - sonetMediumCircuitIdentifier none required 566 SONET-MIB - sonetMediumInvalidIntervals none required 567 SONET-MIB - sonetMediumLoopbackConfig none required 568 SONET-MIB - sonetSESthresholdSet none required 570 ETHER-WIS - etherWisSectionCurrentJ0Transmitted 10G WIS J0 Tx 571 ETHER-WIS - etherWisSectionCurrentJ0Received 10G WIS J0 Rx 573 SONET-MIB - sonetSectionCurrentStatus 10G WIS Status 3 574 SONET-MIB - sonetSectionCurrentESs \ 575 SONET-MIB - sonetSectionCurrentSESs \ 576 SONET-MIB - sonetSectionCurrentSEFSs | 10G WIS Status 3 577 SONET-MIB - sonetSectionCurrentCVs | + 578 SONET-MIB - sonetSectionIntervalESs | 10G WIS Section 579 SONET-MIB - sonetSectionIntervalSESs | BIP Error Count 580 SONET-MIB - sonetSectionIntervalSEFSs / 581 SONET-MIB - sonetSectionIntervalCVs / 582 SONET-MIB - sonetSectionIntervalValidData none required 583 SONET-MIB - sonetLineCurrentStatus 10G WIS Status 3 584 SONET-MIB - sonetLineCurrentESs \ 585 SONET-MIB - sonetLineCurrentSESs \ 586 SONET-MIB - sonetLineCurrentCVs | 10G WIS Status 3 587 SONET-MIB - sonetLineCurrentUASs | + 588 SONET-MIB - sonetLineIntervalESs | 10G WIS Line 589 SONET-MIB - sonetLineIntervalSESs | BIP Errors 590 SONET-MIB - sonetLineIntervalCVs / 591 SONET-MIB - sonetLineIntervalUASs / 592 SONET-MIB - sonetLineIntervalValidData none required 594 SONET-MIB - sonetFarEndLineCurrentESs \ 595 SONET-MIB - sonetFarEndLineCurrentSESs \ 596 SONET-MIB - sonetFarEndLineCurrentCVs | 10G WIS Status 3 597 SONET-MIB - sonetFarEndLineCurrentUASs | + 598 SONET-MIB - sonetFarEndLineIntervalESs | 10G WIS Far End 599 SONET-MIB - sonetFarEndLineIntervalSESs | Line BIP Errors 600 SONET-MIB - sonetFarEndLineIntervalCVs / 601 SONET-MIB - sonetFarEndLineIntervalUASs / 602 SONET-MIB - sonetFarEndLineIntervalValidData 10G WIS Status 3 604 ETHER-WIS - etherWisPathCurrentStatus 10G WIS Status 3 605 ETHER-WIS - etherWisPathCurrentJ1Transmitted 10G WIS J1 Tx 606 ETHER-WIS - etherWisPathCurrentJ1Received 10G WIS J1 Rx 608 SONET-MIB - sonetPathCurrentWidth none required 609 SONET-MIB - sonetPathCurrentStatus 10G WIS Status 3 610 SONET-MIB - sonetPathCurrentESs \ 611 SONET-MIB - sonetPathCurrentSESs \ 612 SONET-MIB - sonetPathCurrentCVs | 10G WIS Status 3 613 SONET-MIB - sonetPathCurrentUASs | + 614 SONET-MIB - sonetPathIntervalESs | 10G WIS 615 SONET-MIB - sonetPathIntervalSESs | Path Block 616 SONET-MIB - sonetPathIntervalCVs / Error Count 617 SONET-MIB - sonetPathIntervalUASs / 618 SONET-MIB - sonetPathIntervalValidData none required 620 ETHER-WIS - etherWisFarEndPathCurrentStatus 10G WIS Status 3 622 SONET-MIB - sonetFarEndPathCurrentESs \ 623 SONET-MIB - sonetFarEndPathCurrentSESs \ 624 SONET-MIB - sonetFarEndPathCurrentCVs | 10G WIS Status 3 625 SONET-MIB - sonetFarEndPathCurrentUASs | + 626 SONET-MIB - sonetFarEndPathIntervalESs | 10G WIS Far End 627 SONET-MIB - sonetFarEndPathIntervalSESs | Path Block 628 SONET-MIB - sonetFarEndPathIntervalCVs / Error Count 629 SONET-MIB - sonetFarEndPathIntervalUASs / 630 SONET-MIB - sonetFarEndPathIntervalValidData 10G WIS Status 3 631 MAU-MIB - ifMauIfIndex none required 632 MAU-MIB - ifMauIndex none required 633 MAU-MIB - ifMauType 10G WIS Control 2 634 MAU-MIB - ifMauStatus WIS Control 1 635 MAU-MIB - ifMauMediaAvailable \ WIS Status 1 + 636 MAU-MIB - ifMauMediaAvailableStateExits / 10G WIS Status 3 637 MAU-MIB - ifMauJabberState none required 638 MAU-MIB - ifMauJabberingStateEnters none required 639 MAU-MIB - ifMauFalseCarriers none required 640 MAU-MIB - ifMauDefaultType 10G WIS Control 2 641 MAU-MIB - ifMauAutoNegSupported none required 642 MAU-MIB - ifMauTypeListBits 10G WIS Status 2 644 3.8. Structure of the MIB Module 646 Four tables are defined in this MIB module. 648 3.8.1. etherWisDeviceTable 650 The purpose of this table is to define managed objects to control the 651 WIS test pattern mode. These objects are required to support 652 mandatory and optional WIS test features specified in [P802.3ae] 653 subclause 50.3.8. 655 The etherWisDeviceTable is a sparse augmentation of the 656 sonetMediumTable of the SONET MIB -- in other words, for each entry 657 in the etherWisDeviceTable there MUST be an entry in the 658 sonetMediumTable and the same ifIndex value SHALL be used for both 659 entries. 661 3.8.2. etherWisSectionCurrentTable 663 The purpose of this table is to define managed objects for the 664 transmitted and received section trace messages (J0 byte). 666 The etherWisSectionCurrentTable is a sparse augmentation of the 667 sonetSectionCurrentTable of the SONET MIB -- in other words, for each 668 entry in the etherWisSectionCurrentTable there MUST be an entry in 669 the sonetSectionCurrentTable and the same ifIndex value SHALL be used 670 for both entries. 672 3.8.3. etherWisPathCurrentTable 674 The purpose of this table is to define managed objects for the 675 current WIS path layer status and for the transmitted and received 676 path trace messages (J1 byte). The path layer status object is 677 provided because the WIS supports some near-end path status 678 conditions that are not reported in sonetPathCurrentStatus. 680 The etherWisPathCurrentTable is a sparse augmentation of the 681 sonetPathCurrentTable of the SONET MIB -- in other words, for each 682 entry in the etherWisPathCurrentTable there MUST be an entry in the 683 sonetPathCurrentTable and the same ifIndex value SHALL be used for 684 both entries. 686 3.8.4. etherWisFarEndPathCurrentTable 688 The purpose of this table is to define a managed object for the 689 current status of the far end of the path. This object is provided 690 because the WIS supports some far-end path status conditions that are 691 not reported in sonetPathCurrentStatus. 693 The etherWisFarEndPathCurrentTable is a sparse augmentation of the 694 sonetFarEndPathCurrentTable of the SONET MIB -- in other words, for 695 each entry in the etherWisFarEndPathCurrentTable there MUST be an 696 entry in the sonetFarEndPathCurrentTable and the same ifIndex value 697 SHALL be used for both entries. 699 4. Object Definitions 701 ETHER-WIS DEFINITIONS ::= BEGIN 703 IMPORTS 704 MODULE-IDENTITY, OBJECT-TYPE, 705 transmission 706 FROM SNMPv2-SMI 707 ifIndex 708 FROM IF-MIB 709 MODULE-COMPLIANCE, OBJECT-GROUP 710 FROM SNMPv2-CONF 711 sonetMediumStuff2, sonetSectionStuff2, 712 sonetLineStuff2, sonetFarEndLineStuff2, 713 sonetPathStuff2, sonetFarEndPathStuff2, 714 sonetMediumType, sonetMediumLineCoding, 715 sonetMediumLineType, sonetMediumCircuitIdentifier, 716 sonetMediumLoopbackConfig, sonetSESthresholdSet, 717 sonetPathCurrentWidth 718 FROM SONET-MIB; 720 etherWisMIB MODULE-IDENTITY 721 LAST-UPDATED "200202180140Z" -- February 18, 2002 722 ORGANIZATION "IETF Ethernet Interfaces and Hub MIB 723 Working Group" 724 CONTACT-INFO 725 "WG charter: 726 http://www.ietf.org/html.charters/hubmib-charter.html 728 Chair: Dan Romascanu 729 Postal: Avaya Inc. 730 Atidim Technology Park, Bldg. 3 731 Tel Aviv 61131 732 Israel 733 Tel: +972 3 645 8414 734 E-mail: dromasca@avaya.com 736 Editor: C. M. Heard 737 Postal: 600 Rainbow Dr. #141 738 Mountain View, CA 94041-2542 739 USA 740 Tel: +1 650-964-8391 741 E-mail: heard@pobox.com" 743 DESCRIPTION 744 "The objects in this MIB module are used in conjunction 745 with objects in the SONET-MIB and the MAU-MIB to manage 746 the Ethernet WAN Interface Sublayer (WIS). 748 The following reference is used throughout this MIB module: 750 [IEEE 802.3 Std] refers to: 751 IEEE Std 802.3, 2000 Edition: 'IEEE Standard for 752 Information technology - Telecommunications and 753 information exchange between systems - Local and 754 metropolitan area networks - Specific requirements - 755 Part 3: Carrier sense multiple access with collision 756 detection (CSMA/CD) access method and physical layer 757 specifications', as amended by IEEE Draft P802.3ae/D4.01: 758 'Supplement to Carrier Sense Multiple Access with 759 Collision Detection (CSMA/CD) Access Method & Physical 760 Layer Specifications - Media Access Control (MAC) 761 Parameters, Physical Layer, and Management Parameters 762 for 10 Gb/s Operation', February 4, 2002. 764 Of particular interest are Clause 50, 'WAN Interface 765 Sublayer (WIS), type 10GBASE-W', Clause 30, '10Mb/s, 766 100Mb/s, 1000Mb/s, and 10Gb/s MAC Control, and Link 767 Aggregation Management', and Clause 45, 'Management 768 Data Input/Output (MDIO) Interface'." 770 REVISION "200202180140Z" -- February 18, 2002 771 DESCRIPTION "Initial version, published as RFC yyyy." 772 -- RFC Ed.: replace yyyy with actual RFC number & remove this notice 774 ::= { transmission XXX } 775 -- RFC Ed.: replace XXX with IANA-assigned number & remove this notice 777 -- The main sections of the module 779 etherWisObjects OBJECT IDENTIFIER ::= { etherWisMIB 1 } 781 etherWisObjectsPath OBJECT IDENTIFIER ::= { etherWisMIB 2 } 783 etherWisConformance OBJECT IDENTIFIER ::= { etherWisMIB 3 } 785 -- groups in the Ethernet WIS MIB module 787 etherWisDevice OBJECT IDENTIFIER ::= { etherWisObjects 1 } 789 etherWisSection OBJECT IDENTIFIER ::= { etherWisObjects 2 } 791 etherWisPath OBJECT IDENTIFIER ::= { etherWisObjectsPath 1 } 793 etherWisFarEndPath OBJECT IDENTIFIER ::= { etherWisObjectsPath 2 } 794 -- The Device group 796 -- These objects provide WIS extensions to 797 -- the SONET-MIB Medium Group. 799 etherWisDeviceTable OBJECT-TYPE 800 SYNTAX SEQUENCE OF EtherWisDeviceEntry 801 MAX-ACCESS not-accessible 802 STATUS current 803 DESCRIPTION 804 "The table for Ethernet WIS devices" 805 ::= { etherWisDevice 1 } 807 etherWisDeviceEntry OBJECT-TYPE 808 SYNTAX EtherWisDeviceEntry 809 MAX-ACCESS not-accessible 810 STATUS current 811 DESCRIPTION 812 "An entry in the Ethernet WIS device table. For each 813 instance of this object there MUST be a corresponding 814 instance of sonetMediumEntry." 815 INDEX { ifIndex } 816 ::= { etherWisDeviceTable 1 } 818 EtherWisDeviceEntry ::= 819 SEQUENCE { 820 etherWisDeviceTxTestPatternMode INTEGER, 821 etherWisDeviceRxTestPatternMode INTEGER, 822 etherWisDeviceRxTestPatternErrors Gauge32 823 } 825 etherWisDeviceTxTestPatternMode OBJECT-TYPE 826 SYNTAX INTEGER { 827 none(0), 828 squareWave(1), 829 prbs31(2), 830 mixedFrequency(3) 831 } 832 MAX-ACCESS read-write 833 STATUS current 834 DESCRIPTION 835 "This variable controls the transmit test pattern mode. 836 The value none(0) puts the the WIS transmit path into 837 the normal operating mode. The value squareWave(1) puts 838 the WIS transmit path into the square wave test pattern 839 mode described in [IEEE 802.3 Std.] subclause 50.3.8.1. 840 The value prbs31(2) puts the WIS transmit path into the 841 PRBS31 test pattern mode described in [IEEE 802.3 Std.] 842 subclause 50.3.8.2. The value mixedFrequency(3) puts the 843 WIS transmit path into the mixed frequency test pattern 844 mode described in [IEEE 802.3 Std.] subclause 50.3.8.3. 845 Any attempt to set this object to a value other than 846 none(0) when the corresponding instance of ifAdminState 847 has the value up(1) MUST be rejected with the error 848 inconsistentValue, and any attempt to set the corresponding 849 instance of ifAdminStatus to the value up(1) when an 850 instance of this object has a value other than none(0) 851 MUST be rejected with the error inconsistentValue." 852 REFERENCE 853 "[IEEE 802.3 Std.], 50.3.8, WIS test pattern generator and 854 checker, 45.2.2.6, 10G WIS Control 2 register (2.7), and 855 45.2.2.7.2, PRBS31 pattern testing ability (2.8.1)." 856 ::= { etherWisDeviceEntry 1 } 858 etherWisDeviceRxTestPatternMode OBJECT-TYPE 859 SYNTAX INTEGER { 860 none(0), 861 prbs31(2), 862 mixedFrequency(3) 863 } 864 MAX-ACCESS read-write 865 STATUS current 866 DESCRIPTION 867 "This variable controls the receive test pattern mode. 868 The value none(0) puts the the WIS receive path into the 869 normal operating mode. The value prbs31(2) puts the WIS 870 receive path into the PRBS31 test pattern mode described 871 in [IEEE 802.3 Std.] subclause 50.3.8.2. The value 872 mixedFrequency(3) puts the WIS receive path into the mixed 873 frequency test pattern mode described in [IEEE 802.3 Std.] 874 subclause 50.3.8.3. Any attempt to set this object to a 875 value other than none(0) when the corresponding instance 876 of ifAdminState has the value up(1) MUST be rejected with 877 the error inconsistentValue, and any attempt to set the 878 corresponding instance of ifAdminStatus to the value up(1) 879 when an instance of this object has a value other than 880 none(0) MUST be rejected with the error inconsistentValue." 881 REFERENCE 882 "[IEEE 802.3 Std.], 50.3.8, WIS test pattern generator and 883 checker, 45.2.2.6, 10G WIS Control 2 register (2.7), and 884 45.2.2.7.2, PRBS31 pattern testing ability (2.8.1)." 885 ::= { etherWisDeviceEntry 2 } 887 etherWisDeviceRxTestPatternErrors OBJECT-TYPE 888 SYNTAX Gauge32 ( 0..65535 ) 889 MAX-ACCESS read-write 890 STATUS current 891 DESCRIPTION 892 "This object counts the number of errors detected when the 893 WIS receive path is operating in the PRBS31 test pattern 894 mode. It is reset to zero when the WIS receive path 895 initially enters that mode, and it increments each time 896 the PRBS pattern checker detects an error as described in 897 [IEEE 802.3 Std.] subclause 50.3.8.2 unless its value is 898 65535, in which case it remains unchanged. This object is 899 writeable so that it may be reset upon explicit request 900 of a command generator application while the WIS receive 901 path continues to operate in PRBS31 test pattern mode." 902 REFERENCE 903 "[IEEE 802.3 Std.], 50.3.8, WIS test pattern generator and 904 checker, 45.2.2.7.2, PRBS31 pattern testing ability 905 (2.8.1), and 45.2.2.8 10G WIS test pattern error counter 906 register (2.9)." 907 ::= { etherWisDeviceEntry 3 } 909 -- The Section group 911 -- These objects provide WIS extensions to 912 -- the SONET-MIB Section Group. 914 etherWisSectionCurrentTable OBJECT-TYPE 915 SYNTAX SEQUENCE OF EtherWisSectionCurrentEntry 916 MAX-ACCESS not-accessible 917 STATUS current 918 DESCRIPTION 919 "The table for the current state of Ethernet WIS sections." 920 ::= { etherWisSection 1 } 922 etherWisSectionCurrentEntry OBJECT-TYPE 923 SYNTAX EtherWisSectionCurrentEntry 924 MAX-ACCESS not-accessible 925 STATUS current 926 DESCRIPTION 927 "An entry in the etherWisSectionCurrentTable. For each 928 instance of this object there MUST be a corresponding 929 instance of sonetSectionCurrentEntry." 930 INDEX { ifIndex } 931 ::= { etherWisSectionCurrentTable 1 } 933 EtherWisSectionCurrentEntry ::= 934 SEQUENCE { 935 etherWisSectionCurrentJ0Transmitted OCTET STRING, 936 etherWisSectionCurrentJ0Received OCTET STRING 937 } 939 etherWisSectionCurrentJ0Transmitted OBJECT-TYPE 940 SYNTAX OCTET STRING (SIZE (16)) 941 MAX-ACCESS read-write 942 STATUS current 943 DESCRIPTION 944 "This is the 16-octet section trace message that is 945 to be transmitted in the J0 byte. The value SHOULD 946 be fifteen octets of '00'h followed by '89'h 947 (or some cyclic shift thereof) when the section 948 trace function is not used, and the implementation 949 SHOULD use that value (or a cyclic shift thereof) 950 as a default if no other value has been set." 951 REFERENCE 952 "[IEEE 802.3 Std.], 30.8.1.1.8, aJ0ValueTX." 953 ::= { etherWisSectionCurrentEntry 1 } 955 etherWisSectionCurrentJ0Received OBJECT-TYPE 956 SYNTAX OCTET STRING (SIZE (16)) 957 MAX-ACCESS read-only 958 STATUS current 959 DESCRIPTION 960 "This is the 16-octet section trace message that 961 was most recently received in the J0 byte." 962 REFERENCE 963 "[IEEE 802.3 Std.], 30.8.1.1.9, aJ0ValueRX." 964 ::= { etherWisSectionCurrentEntry 2 } 966 -- The Path group 968 -- These objects provide WIS extensions to 969 -- the SONET-MIB Path Group. 971 etherWisPathCurrentTable OBJECT-TYPE 972 SYNTAX SEQUENCE OF EtherWisPathCurrentEntry 973 MAX-ACCESS not-accessible 974 STATUS current 975 DESCRIPTION 976 "The table for the current state of Ethernet WIS paths." 977 ::= { etherWisPath 1 } 979 etherWisPathCurrentEntry OBJECT-TYPE 980 SYNTAX EtherWisPathCurrentEntry 981 MAX-ACCESS not-accessible 982 STATUS current 983 DESCRIPTION 984 "An entry in the etherWisPathCurrentTable. For each 985 instance of this object there MUST be a corresponding 986 instance of sonetPathCurrentEntry." 987 INDEX { ifIndex } 988 ::= { etherWisPathCurrentTable 1 } 990 EtherWisPathCurrentEntry ::= 991 SEQUENCE { 992 etherWisPathCurrentStatus BITS, 993 etherWisPathCurrentJ1Transmitted OCTET STRING, 994 etherWisPathCurrentJ1Received OCTET STRING 995 } 997 etherWisPathCurrentStatus OBJECT-TYPE 998 SYNTAX BITS { 999 etherWisPathLOP(0), 1000 etherWisPathAIS(1), 1001 etherWisPathPLM(2), 1002 etherWisPathLCD(3) 1003 } 1004 MAX-ACCESS read-write 1005 STATUS current 1006 DESCRIPTION 1007 "This variable indicates the current status of the 1008 path payload with a bit map that can indicate multiple 1009 defects at once. The bit positions are assigned as 1010 follows: 1012 etherWisPathLOP(0) 1013 This bit is set to indicate that an 1014 LOP-P (Loss of Pointer - Path) defect 1015 is being experienced. Note: when this 1016 bit is set, sonetPathSTSLOP MUST be set 1017 in the corresponding instance of 1018 sonetPathCurrentStatus. 1020 etherWisPathAIS(1) 1021 This bit is set to indicate that an 1022 AIS-P (Alarm Indication Signal - Path) 1023 defect is being experienced. Note: when 1024 this bit is set, sonetPathSTSAIS MUST be 1025 set in the corresponding instance of 1026 sonetPathCurrentStatus. 1028 etherWisPathPLM(1) 1029 This bit is set to indicate that a 1030 PLM-P (Payload Label Mismatch - Path) 1031 defect is being experienced. Note: when 1032 this bit is set, sonetPathSignalLabelMismatch 1033 MUST be set in the corresponding instance of 1034 sonetPathCurrentStatus. 1036 etherWisPathLCD(3) 1037 This bit is set to indicate that an 1038 LCD-P (Loss of Codegroup Delination - Path) 1039 defect is being experienced. Since this 1040 defect is detected by the PCS and not by 1041 the path layer itself, there is no 1042 corresponding bit in sonetPathCurrentStatus." 1043 REFERENCE 1044 "[IEEE 802.3 Std.], 30.8.1.1.18, aPathStatus." 1045 ::= { etherWisPathCurrentEntry 1 } 1047 etherWisPathCurrentJ1Transmitted OBJECT-TYPE 1048 SYNTAX OCTET STRING (SIZE (16)) 1049 MAX-ACCESS read-write 1050 STATUS current 1051 DESCRIPTION 1052 "This is the 16-octet path trace message that is to 1053 be transmitted in the J1 byte. The value SHOULD 1054 be fifteen octets of '00'h followed by '89'h 1055 (or some cyclic shift thereof) when the path 1056 trace function is not used, and the implementation 1057 SHOULD use that value (or a cyclic shift thereof) 1058 as a default if no other value has been set." 1059 REFERENCE 1060 "[IEEE 802.3 Std.], 30.8.1.1.23, aJ1ValueTX." 1061 ::= { etherWisPathCurrentEntry 2 } 1063 etherWisPathCurrentJ1Received OBJECT-TYPE 1064 SYNTAX OCTET STRING (SIZE (16)) 1065 MAX-ACCESS read-only 1066 STATUS current 1067 DESCRIPTION 1068 "This is the 16-octet path trace message that 1069 was most recently received in the J1 byte." 1070 REFERENCE 1071 "[IEEE 802.3 Std.], 30.8.1.1.24, aJ1ValueRX." 1072 ::= { etherWisPathCurrentEntry 3 } 1074 -- The Far End Path group 1076 -- These objects provide WIS extensions to 1077 -- the SONET-MIB Far End Path Group. 1079 etherWisFarEndPathCurrentTable OBJECT-TYPE 1080 SYNTAX SEQUENCE OF EtherWisFarEndPathCurrentEntry 1081 MAX-ACCESS not-accessible 1082 STATUS current 1083 DESCRIPTION 1084 "The table for the current far-end state of Ethernet WIS 1085 paths." 1086 ::= { etherWisFarEndPath 1 } 1088 etherWisFarEndPathCurrentEntry OBJECT-TYPE 1089 SYNTAX EtherWisFarEndPathCurrentEntry 1090 MAX-ACCESS not-accessible 1091 STATUS current 1092 DESCRIPTION 1093 "An entry in the etherWisFarEndPathCurrentTable. For each 1094 instance of this object there MUST be a corresponding 1095 instance of sonetFarEndPathCurrentEntry." 1096 INDEX { ifIndex } 1097 ::= { etherWisFarEndPathCurrentTable 1 } 1099 EtherWisFarEndPathCurrentEntry ::= 1100 SEQUENCE { 1101 etherWisFarEndPathCurrentStatus BITS 1102 } 1104 etherWisFarEndPathCurrentStatus OBJECT-TYPE 1105 SYNTAX BITS { 1106 etherWisFarEndPayloadDefect(0), 1107 etherWisFarEndServerDefect(1) 1108 } 1109 MAX-ACCESS read-write 1110 STATUS current 1111 DESCRIPTION 1112 "This variable indicates the current status at the 1113 far end of the path using a bit map that can indicate 1114 multiple defects at once. The bit positions are 1115 assigned as follows: 1117 etherWisFarEndPayloadDefect(0) 1118 A far end payload defect (i.e., far end 1119 PLM-P or LCD-P) is currently being signalled 1120 in G1 bits 5-7. 1122 etherWisFarEndServerDefect(1) 1123 A far end server defect (i.e., far end 1124 LOP-P or AIS-P) is currently being signalled 1125 in G1 bits 5-7. Note: when this bit is set, 1126 sonetPathSTSRDI MUST be set in the corresponding 1127 instance of sonetPathCurrentStatus." 1128 REFERENCE 1129 "[IEEE 802.3 Std.], 30.8.1.1.25, aFarEndPathStatus." 1130 ::= { etherWisFarEndPathCurrentEntry 1 } 1132 -- 1133 -- Conformance Statements 1134 -- 1136 etherWisGroups OBJECT IDENTIFIER ::= { etherWisConformance 1 } 1138 etherWisCompliances OBJECT IDENTIFIER ::= { etherWisConformance 2 } 1140 -- Object Groups 1142 etherWisDeviceGroupBasic OBJECT-GROUP 1143 OBJECTS { 1144 etherWisDeviceTxTestPatternMode, 1145 etherWisDeviceRxTestPatternMode 1146 } 1147 STATUS current 1148 DESCRIPTION 1149 "A collection of objects that support test 1150 features required of all WIS devices." 1151 ::= { etherWisGroups 1 } 1153 etherWisDeviceGroupExtra OBJECT-GROUP 1154 OBJECTS { 1155 etherWisDeviceRxTestPatternErrors 1156 } 1157 STATUS current 1158 DESCRIPTION 1159 "A collection of objects that support 1160 optional WIS device test features." 1161 ::= { etherWisGroups 2 } 1163 etherWisSectionGroup OBJECT-GROUP 1164 OBJECTS { 1165 etherWisSectionCurrentJ0Transmitted, 1166 etherWisSectionCurrentJ0Received 1167 } 1168 STATUS current 1169 DESCRIPTION 1170 "A collection of objects that provide 1171 required information about a WIS section." 1172 ::= { etherWisGroups 3 } 1174 etherWisPathGroup OBJECT-GROUP 1175 OBJECTS { 1176 etherWisPathCurrentStatus, 1177 etherWisPathCurrentJ1Transmitted, 1178 etherWisPathCurrentJ1Received 1179 } 1180 STATUS current 1181 DESCRIPTION 1182 "A collection of objects that provide 1183 required information about a WIS path." 1184 ::= { etherWisGroups 4 } 1186 etherWisFarEndPathGroup OBJECT-GROUP 1187 OBJECTS { 1188 etherWisFarEndPathCurrentStatus 1189 } 1190 STATUS current 1191 DESCRIPTION 1192 "A collection of objects that provide required 1193 information about the far end of a WIS path." 1194 ::= { etherWisGroups 5 } 1196 -- Compliance Statements 1198 etherWisCompliance MODULE-COMPLIANCE 1199 STATUS current 1200 DESCRIPTION 1201 "The compliance statement for this module." 1203 MODULE -- this module 1204 MANDATORY-GROUPS { 1205 etherWisDeviceGroupBasic, 1206 etherWisSectionGroup, 1207 etherWisPathGroup, 1208 etherWisFarEndPathGroup 1209 } 1211 OBJECT etherWisDeviceTxTestPatternMode 1212 SYNTAX INTEGER { 1213 none(0), 1214 squareWave(1), 1215 mixedFrequency(3) 1216 } 1217 DESCRIPTION 1218 "Support for values other than none(0), 1219 squareWave(1), and mixedFrequency(3) 1220 is not required." 1222 OBJECT etherWisDeviceRxTestPatternMode 1223 SYNTAX INTEGER { 1224 none(0), 1225 mixedFrequency(3) 1226 } 1227 DESCRIPTION 1228 "Support for values other than none(0) 1229 and mixedFrequency(3) is not required." 1231 GROUP etherWisDeviceGroupExtra 1232 DESCRIPTION 1233 "Implementation of this group, along with support for 1234 the value prbs31(2) for etherWisDeviceTxTestPatternMode 1235 and etherWisDeviceRxTestPatternMode, is necessary if the 1236 optional PRBS31 test pattern mode is to be supported." 1238 MODULE SONET-MIB 1239 MANDATORY-GROUPS { 1240 sonetMediumStuff2, 1241 sonetSectionStuff2, 1242 sonetLineStuff2, 1243 sonetFarEndLineStuff2, 1244 sonetPathStuff2, 1245 sonetFarEndPathStuff2 1246 } 1248 OBJECT sonetMediumType 1249 SYNTAX INTEGER { 1250 sonet(1) 1251 } 1252 MIN-ACCESS read-only 1253 DESCRIPTION 1254 "Write access is not required, nor is support 1255 for any value other than sonet(1)." 1257 OBJECT sonetMediumLineCoding 1258 SYNTAX INTEGER { 1259 sonetMediumNRZ(4) 1260 } 1261 MIN-ACCESS read-only 1262 DESCRIPTION 1263 "Write access is not required, nor is support 1264 for any value other than sonetMediumNRZ(4)." 1266 OBJECT sonetMediumLineType 1267 MIN-ACCESS read-only 1268 DESCRIPTION 1269 "Write access is not required." 1271 OBJECT sonetMediumCircuitIdentifier 1272 MIN-ACCESS read-only 1273 DESCRIPTION 1274 "Write access is not required." 1276 OBJECT sonetMediumLoopbackConfig 1277 SYNTAX BITS { 1278 sonetNoLoop(0), 1279 sonetFacilityLoop(1) 1280 } 1281 MIN-ACCESS read-only 1282 DESCRIPTION 1283 "Write access is not required, nor is support for values 1284 other than sonetNoLoop(0) and sonetFacilityLoop(1)." 1286 OBJECT sonetSESthresholdSet 1287 MIN-ACCESS read-only 1288 DESCRIPTION 1289 "Write access is not required, and only one 1290 of the enumerated values need be supported." 1292 OBJECT sonetPathCurrentWidth 1293 SYNTAX INTEGER { 1294 sts192cSTM64(6) 1295 } 1296 MIN-ACCESS read-only 1297 DESCRIPTION 1298 "Write access is not required, nor is support 1299 for any value other than sts192cSTM64(6)." 1301 ::= { etherWisCompliances 1 } 1303 END 1305 5. Acknowledgments 1307 This document is a product of the IETF Hubmib and AToMMIB Working 1308 Groups. It builds upon the work of the IEEE P802.3ae 10 Gigabit 1309 Ethernet Task Force. 1311 6. Security Considerations 1313 There are a number of management objects defined in this MIB that 1314 have a MAX-ACCESS clause of read-write and/or read-create. Such 1315 objects may be considered sensitive or vulnerable in some network 1316 environments. The support for SET operations in a non-secure 1317 environment without proper protection can have a negative effect on 1318 network operations. 1320 SNMPv1 by itself is not a secure environment. Even if the network 1321 itself is secure (for example by using IPSec), even then, there is no 1322 control as to who on the secure network is allowed to access and 1323 GET/SET (read/change/create/delete) the objects in this MIB. 1325 It is recommended that the implementers consider the security 1326 features as provided by the SNMPv3 framework. Specifically, the use 1327 of the User-based Security Model RFC 2574 [RFC2574] and the View- 1328 based Access Control Model RFC 2575 [RFC2575] is recommended. 1330 It is then a customer/user responsibility to ensure that the SNMP 1331 entity giving access to an instance of this MIB, is properly 1332 configured to give access to the objects only to those principals 1333 (users) that have legitimate rights to indeed GET or SET 1334 (change/create/delete) them. 1336 7. References 1338 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture 1339 for Describing SNMP Management Frameworks", RFC 2571, April 1340 1999. 1342 [RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification 1343 of Management Information for TCP/IP-based Internets", STD 1344 16, RFC 1155, May 1990. 1346 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 1347 16, RFC 1212, March 1991. 1349 [RFC1215] M. Rose, "A Convention for Defining Traps for use with the 1350 SNMP", RFC 1215, March 1991. 1352 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1353 Rose, M., and S. Waldbusser, "Structure of Management 1354 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1355 1999. 1357 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1358 Rose, M., and S. Waldbusser, "Textual Conventions for 1359 SMIv2", STD 58, RFC 2579, April 1999. 1361 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1362 Rose, M., and S. Waldbusser, "Conformance Statements for 1363 SMIv2", STD 58, RFC 2580, April 1999. 1365 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple 1366 Network Management Protocol", STD 15, RFC 1157, May 1990. 1368 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1369 "Introduction to Community-based SNMPv2", RFC 1901, January 1370 1996. 1372 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1373 "Transport Mappings for Version 2 of the Simple Network 1374 Management Protocol (SNMPv2)", RFC 1906, January 1996. 1376 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 1377 Processing and Dispatching for the Simple Network Management 1378 Protocol (SNMP)", RFC 2572, April 1999. 1380 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model 1381 (USM) for version 3 of the Simple Network Management 1382 Protocol (SNMPv3)", RFC 2574, April 1999. 1384 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1385 "Protocol Operations for Version 2 of the Simple Network 1386 Management Protocol (SNMPv2)", RFC 1905, January 1996. 1388 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", 1389 RFC 2573, April 1999. 1391 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 1392 Access Control Model (VACM) for the Simple Network 1393 Management Protocol (SNMP)", RFC 2575, April 1999. 1395 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 1396 "Introduction to Version 3 of the Internet-standard Network 1397 Management Framework", RFC 2570, April 1999. 1399 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1400 Requirements Levels", BCP 14, RFC 2119, March 1997. 1402 [RFC2863] McCloghrie, K., and F. Kastenholz, "The Interfaces Group 1403 MIB", RFC 2863, June 2000. 1405 [RFC2864] McCloghrie, K., and G. Hanson, "The Inverted Stack Table 1406 Extension to the Interfaces Group MIB", RFC 2864, June 2000. 1408 [SONETng] Tesink, K., "Definitions of Managed Objects for the 1409 SONET/SDH Interface Type", , work in progress. 1412 [T1.231] American National Standard for Telecommunications - Digital 1413 Hierarchy - Layer 1 In-Service Digital Transmission 1414 Performance Monitoring, ANSI T1.231-1997, September 1997. 1416 [ETHERIF] Flick, J., "Definitions of Managed Objects for the 1417 Ethernet-like Interface Types", , work in progress. 1420 [MAU-MIB] Flick, J., "Definitions of Managed Objects for IEEE 802.3 1421 Medium Attachment Units (MAUs)", , work in progress. 1424 [P802.3ae] Law, D., Editor, Draft Supplement to IEEE Std. 802.3, IEEE 1425 Draft P802.3ae/D4.01, February 4, 2002, work in progress. 1427 8. Authors' Addresses 1429 Mike Ayers 1430 BMC Software, Inc. 1431 2141 North First Street 1432 San Jose, CA 95131 1433 USA 1435 Phone: +1 408 546 0947 1436 Fax: +1 408 965 0359 1437 Email: mayers@bmc.com 1439 John Flick 1440 Hewlett-Packard Company 1441 8000 Foothills Blvd. M/S 5557 1442 Roseville, CA 95747-5557 1444 Phone: +1 916 785 4018 1445 Fax: +1 916 785 1199 1446 Email: johnf@rose.hp.com 1448 C. M. Heard 1449 600 Rainbow Dr. #141 1450 Mountain View, CA 94041-2542 1451 USA 1453 Phone: +1 650 964 8391 1454 EMail: heard@pobox.com 1456 Kam Lam 1457 Lucent Technologies 1458 101 Crawfords Corner Road, Room 4C-616A 1459 Holmdel, NJ 07733 1461 Phone: +1 732 949 8338 1462 EMail: hklam@lucent.com 1464 Kerry McDonald 1465 Institute for Applied Supercomputing 1466 California State University San Bernardino 1468 Email: kerry_mcd@hotmail.com 1469 kmcdonal@csci.csusb.edu 1471 K. C. Norseth 1472 Enterasys Networks 1473 2691 South Decker Lake Lane 1474 Salt Lake City, Utah 84119 1476 Phone: +1 801 887 9823 1477 Email: knorseth@enterasys.com 1479 Kaj Tesink 1480 Telcordia Technologies 1481 331 Newman Springs Road 1482 P.O. Box 7020 1483 Red Bank, NJ 07701-7020 1484 USA 1486 Phone: +1 732 758 5254 1487 EMail: kaj@research.telcordia.com 1489 9. Intellectual Property 1491 The IETF takes no position regarding the validity or scope of any 1492 intellectual property or other rights that might be claimed to 1493 pertain to the implementation or use of the technology described in 1494 this document or the extent to which any license under such rights 1495 might or might not be available; neither does it represent that it 1496 has made any effort to identify any such rights. Information on the 1497 IETF's procedures with respect to rights in standards-track and 1498 standards-related documentation can be found in BCP-11. Copies of 1499 claims of rights made available for publication and any assurances of 1500 licenses to be made available, or the result of an attempt made to 1501 obtain a general license or permission for the use of such 1502 proprietary rights by implementors or users of this specification can 1503 be obtained from the IETF Secretariat. 1505 The IETF invites any interested party to bring to its attention any 1506 copyrights, patents or patent applications, or other proprietary 1507 rights which may cover technology that may be required to practice 1508 this standard. Please address the information to the IETF Executive 1509 Director. 1511 Appendix A: Collection of Performance Data Using WIS MDIO Registers 1513 The purpose of this appendix is to illustrate how the WIS MDIO 1514 registers specified in [P802.3ae] subclause 45.2.2 (and more 1515 specifically the subset required by [P802.3ae] subclause 50.3.10) can 1516 be used to collect performance data either according to the 1517 conventions adopted by this document or according to the conventions 1518 specified in [P802.3ae] Clause 30. 1520 For an agent implementing the SNMP managed objects required by this 1521 document the first step in collecting WIS performance data would be 1522 to poll the 10G WIS Status 3 register and the various error count 1523 registers (10G WIS Section BIP Error Count, 10G WIS Line BIP Errors, 1524 10G WIS Far End Line BIP Errors, 10G WIS Path Block Error Count, and 1525 10G WIS Far End Path Block Error Count) once per second. The 10G WIS 1526 Status 3 register bits are all latched until read and so would 1527 indicate whether a given defect occurred any time during the previous 1528 second. The error count registers roll over modulo 2^16 or 2^32, and 1529 so to find the number of errors within the previous second the agent 1530 would need to subtract (modulo 2^16 or 2^32) the current reading from 1531 the reading taken one second ago. Armed with that information, the 1532 agent could determine for any layer whether the one second interval 1533 was an errored second, a severely errored second (that requires 1534 comparison with a threshold unless a defect is present), or a 1535 severely errored frame second. Determining whether a given second is 1536 or is not part of unavailable time requires additional logic; the 1537 most straightforward and accurate method is the delay-line approach 1538 outlined in Appendix A of [SONETng]. With that information available 1539 the agent would be able to determine by how much each current count 1540 should be incremented (including effects of inhibiting). 1541 Implementations that conform to [T1.231] would end each 15-minute 1542 interval on time-of-day clock 1/4 hour boundaries; if the delay-line 1543 approach is used then a time-of-day timestamp would accompany the 1544 one-second statistics. At the end of each interval the current 1545 registers would be pushed onto the history stack and then would be 1546 cleared. The xyxIntervalValidData flags would be set to False(2) if 1547 the number of samples was not between 890 and 910 or, in the case of 1548 far-end counts, if a near-end defect occurred during the just- 1549 completed interval (see [T1.231] Section 9.1.2.2 for details). 1551 An agent implementing the [P802.3ae] Clause 30 oWIS objects could 1552 start in much the same way, i.e., by polling the 10G WIS Status 3 1553 register and the various error count registers to find the defects 1554 and error counts for the previous second, and it could determine the 1555 number of errors and whether the second was an errored second, a 1556 severely errored second, or a severely errored frame second in the 1557 same manner as above. The rest of the process would be simply to 1558 increment the generalized non-resetable counters without 1559 consideration of any inhibiting rules. 1561 Full Copyright Statement 1563 Copyright (C) The Internet Society (2002). All Rights Reserved. 1565 This document and translations of it may be copied and furnished to 1566 others, and derivative works that comment on or otherwise explain it 1567 or assist in its implementation may be prepared, copied, published 1568 and distributed, in whole or in part, without restriction of any 1569 kind, provided that the above copyright notice and this paragraph are 1570 included on all such copies and derivative works. However, this 1571 document itself may not be modified in any way, such as by removing 1572 the copyright notice or references to the Internet Society or other 1573 Internet organizations, except as needed for the purpose of 1574 developing Internet standards in which case the procedures for 1575 copyrights defined in the Internet Standards process must be 1576 followed, or as required to translate it into languages other than 1577 English. 1579 The limited permissions granted above are perpetual and will not be 1580 revoked by the Internet Society or its successors or assigns. 1582 This document and the information contained herein is provided on an 1583 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 1584 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 1585 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 1586 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 1587 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1589 Revision History 1591 NOTE TO RFC Editor: this section is to be removed prior to 1592 publication as an RFC. 1594 The following changes were made to 1595 to produce : 1597 1.) Section 3.1 was updated as agreed in "WIS MIB compliance 1598 statement issue" e-mail thread, specifically to explain that the 1599 ETHER-WIS compliance statement requires all objects that required 1600 by sonetCompliance2 as well as some that it leaves optional. 1602 2.) In Section 3.5 the paragraph dealing with STS-Path Remote 1603 Defect Indication was updated to indicate that an implementation 1604 of the WIS MIB (not necessarily an arbitrary implementation of the 1605 WIS) has to set the SONET-MIB's RDI status bit when a remote 1606 server defect is detected. 1608 3.) In Section 3.6 the text introducing the table of semantic 1609 differences between IEEE GDMO and SNMP objects was wordsmithed. 1611 4.) In Section 3.7 the mapping between objects in the 1612 etherWisDeviceTable and the station management registers was 1613 updated to reflect the updated MDIO register definitions in 1614 P802.3ae/D4.01 and the corresponding updates to the MIB objects. 1616 5.) In Section 3.8.1 the text was updated to state that the 1617 purpose of the etherWisDeviceTable is to support mandatory and 1618 optional WIS test features. 1620 6.) In Sections 3.8.1, 3.8.2, 3.8.3, and 3.8.4 certain instances 1621 of "SHALL" were changed to "MUST" to improve readability. 1623 7.) The LAST-UPDATED, ORGANIZATION, REVISION, and DESCRIPTION 1624 clauses of the MODULE-IDENTITY invocation were updated. 1626 8.) The lower-case "shall" in the DESCRIPTION clause of each table 1627 entry was changed to an uppercase "MUST", per RFC 2119, because it 1628 describes a requirement of the specification in the draft. 1630 9.) The etherWisDeviceTestPatternType objects was removed, and the 1631 objects etherWisDeviceTxTestPatternMode and 1632 etherWisDeviceRxTestPatternMode were changed from simple 1633 "enable/disable" flags to enumerations that reflect the specific 1634 text pattern mode in which the transmitter or receiver is 1635 operating. A new optional object called 1636 etherWisDeviceRxTestPatternErrors was added to make visible the 1637 error count MDIO register contents when the receiver is operating 1638 in the (optional) PRBS31 test pattern mode added in D4.01. 1640 10.) The SYNTAX of etherWisSectionCurrentJ0Transmitted and 1641 etherWisSectionCurrentJ0Received was changed from INTEGER (0..255) 1642 to OCTET STRING (SIZE (16)) to reflect the change from 1-byte to 1643 16-byte section trace messages in D4.01, and the DESCRIPTION 1644 clauses were rewritten along the lines for those of the 1645 corresponding path trace objects. 1647 11.) In the DESCRIPTION of etherWisPathCurrentJ0Transmitted "path 1648 message" was changes to "path trace message". 1650 12.) etherWisDeviceGroup was split into a mandatory group 1651 etherWisDeviceGroupBasic and an optional group 1652 etherWisDeviceGroupExtra. 1654 13.) The compliance name was changed from 1655 etherWisCurrentCompliance to etherWisCompliance. 1657 14.) OBJECT clauses were added to specify required values for 1658 etherWisDeviceTxTestPatternMode and 1659 etherWisDeviceRxTestPatternMode. 1661 15.) A GROUP clause was added to state that 1662 etherWisDeviceGroupExtra needs to be implemented in order to 1663 support the PRBS31 test pattern mode. The DESCRIPTION clause 1664 points out that the prbs31 enumeration is needed for 1665 etherWisDeviceTxTestPatternMode/etherWisDeviceRxTestPatternMode. 1667 16). References [SONETng] and [P802.3ae] references were updated 1668 to draft-ietf-atommib-rfc2558bis-00.txt and P802.3ae/D4.01, 1669 respectively. 1671 Table of Contents 1673 1 Abstract .................................................. 2 1674 2 The SNMP Management Framework ............................. 2 1675 3 Overview .................................................. 3 1676 3.1 Relationship to the SONET MIB ........................... 4 1677 3.2 Relationship to the Ethernet-like Interfaces MIB ........ 4 1678 3.3 Relationship to the 802.3 MAU MIB ....................... 4 1679 3.4 Use of the ifTable ...................................... 4 1680 3.4.1 Layering Model ........................................ 5 1681 3.4.2 Use of ifTable for LLC Layer/MAC 1682 Layer/Reconciliation Sublayer/Physical Coding 1683 Sublayer ............................................... 5 1684 3.4.3 Use of ifTable for SONET/SDH Path Layer ............... 5 1685 3.4.4 Use of ifTable for SONET/SDH Medium/Section/Line 1686 Layer .................................................. 5 1687 3.5 SONET/SDH Terminology ................................... 6 1688 3.6 Mapping of IEEE 802.3 Managed Objects ................... 7 1689 3.7 Mapping of SNMP Objects to WIS Station Management 1690 Registers .............................................. 12 1691 3.8 Structure of the MIB Module ............................. 14 1692 3.8.1 etherWisDeviceTable ................................... 14 1693 3.8.2 etherWisSectionCurrentTable ........................... 14 1694 3.8.3 etherWisPathCurrentTable .............................. 14 1695 3.8.4 etherWisFarEndPathCurrentTable ........................ 15 1696 4 Object Definitions ........................................ 16 1697 5 Acknowledgments ........................................... 30 1698 6 Security Considerations ................................... 30 1699 7 References ................................................ 31 1700 8 Authors' Addresses ........................................ 33 1701 9 Intellectual Property ..................................... 34 1702 Appendix A: Collection of Performance Data Using WIS 1703 MDIO Registers ......................................... 35 1704 Full Copyright Statement ................................... 36