idnits 2.17.1 draft-ietf-hubmib-wis-mib-06.txt: 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. == 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.) == 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 55 has weird spacing: '... Use of ...' == Line 59 has weird spacing: '... Use of ifTab...' == Line 63 has weird spacing: '...Objects to W...' == The document seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords -- however, there's a paragraph with a matching beginning. Boilerplate error? (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). -- 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 (January 4, 2003) is 7754 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) == Missing Reference: '2570bis' is mentioned on line 1836, but not defined == Missing Reference: 'RFCnnnn' is mentioned on line 1873, but not defined ** 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: 4 errors (**), 0 flaws (~~), 9 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 C. M. Heard, Editor 3 INTERNET DRAFT Consultant 4 January 4, 2003 6 Definitions of Managed Objects 7 for the Ethernet WAN Interface Sublayer 8 10 Status of this Memo 12 This document is an Internet-Draft and is in full conformance with 13 all provisions of Section 10 of RFC2026. Internet-Drafts are working 14 documents of the Internet Engineering Task Force (IETF), its areas, 15 and its working groups. Note that other groups may also distribute 16 working documents as Internet-Drafts. 18 Internet-Drafts are draft documents valid for a maximum of six months 19 and may be updated, replaced, or obsoleted by other documents at any 20 time. It is inappropriate to use Internet-Drafts as reference 21 material or to cite them other than as "work in progress." 23 The list of current Internet-Drafts can be accessed at 24 http://www.ietf.org/ietf/1id-abstracts.txt 26 The list of Internet-Draft Shadow Directories can be accessed at 27 http://www.ietf.org/shadow.html 29 Copyright Notice 31 Copyright (C) The Internet Society (2003). All Rights Reserved. 33 Abstract 35 This document defines a portion of the Management Information Base 36 (MIB) for use with network management protocols in TCP/IP based 37 internets. In particular, it defines objects for managing the 38 Ethernet Wide Area Network (WAN) Interface Sublayer (WIS). 40 The MIB module defined in this memo is an extension of the SONET/SDH 41 Interface MIB and is implemented in conjunction with it and with the 42 Ethernet-like Interface MIB, the 802.3 Medium Attachment Unit MIB, 43 the Interfaces Group MIB, and the Inverted Stack Table MIB. 45 Table of Contents 47 1 Conventions ............................................... 3 48 2 The Internet-Standard Management Framework ................ 3 49 3 Overview .................................................. 3 50 3.1 Relationship to the SONET/SDH Interface MIB ............. 4 51 3.2 Relationship to the Ethernet-like Interface MIB ......... 4 52 3.3 Relationship to the 802.3 MAU MIB ....................... 5 53 3.4 Use of the ifTable ...................................... 5 54 3.4.1 Layering Model ........................................ 5 55 3.4.2 Use of ifTable for LLC Layer/MAC 56 Layer/Reconciliation Sublayer/Physical Coding 57 Sublayer ............................................... 6 58 3.4.3 Use of ifTable for SONET/SDH Path Layer ............... 6 59 3.4.4 Use of ifTable for SONET/SDH Medium/Section/Line 60 Layer .................................................. 6 61 3.5 SONET/SDH Terminology ................................... 6 62 3.6 Mapping of IEEE 802.3 Managed Objects ................... 7 63 3.7 Mapping of SNMP Objects to WIS Station Management 64 Registers .............................................. 12 65 3.8 Structure of the MIB Module ............................. 14 66 3.8.1 etherWisDeviceTable ................................... 14 67 3.8.2 etherWisSectionCurrentTable ........................... 15 68 3.8.3 etherWisPathCurrentTable .............................. 15 69 3.8.4 etherWisFarEndPathCurrentTable ........................ 15 70 4 Object Definitions ........................................ 16 71 5 Intellectual Property ..................................... 30 72 6 Acknowledgments ........................................... 30 73 7 Security Considerations ................................... 31 74 8 References ................................................ 32 75 8.1 Normative References .................................... 32 76 8.2 Informative References .................................. 33 77 9 Contributors .............................................. 33 78 10 Editor's Address ......................................... 34 79 Appendix A: Collection of Performance Data Using WIS 80 MDIO Registers ......................................... 35 81 Full Copyright Statement ................................... 36 83 1. Conventions 85 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 86 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 87 "OPTIONAL", when they appear in this document, are to be interpreted 88 as described in RFC 2119 [RFC2119]. 90 2. The Internet-Standard Management Framework 92 For a detailed overview of the documents that describe the current 93 Internet-Standard Management Framework, please refer to section 7 of 94 RFC 3410 [RFC3410]. 96 Managed objects are accessed via a virtual information store, termed 97 the Management Information Base or MIB. MIB objects are generally 98 accessed through the Simple Network Management Protocol (SNMP). 99 Objects in the MIB are defined using the mechanisms defined in the 100 Structure of Management Information (SMI). This memo specifies a MIB 101 module that is compliant to the SMIv2, which is described in STD 58, 102 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 103 [RFC2580]. 105 3. Overview 107 The objects defined in this memo are used in conjunction with objects 108 defined in the Interfaces Group MIB [RFC2863], the SONET/SDH 109 Interface MIB [SONETng], and the 802.3 MAU MIB [MAU-MIB] to manage 110 the Ethernet Wide Area Network (WAN) Interface Sublayer (WIS) defined 111 in [802.3ae]. The WIS contains functions to perform OC-192c/VC-4-64c 112 framing and scrambling. It resides between the Physical Coding 113 Sublayer (PCS) and the Physical Medium Attachment (PMA) sublayer 114 within a 10GBASE-W 10 Gb/s WAN-compatible physical layer device (PHY) 115 and may be used in conjunction with any of the PCS, PMA, and Physical 116 Medium Dependent (PMD) sublayers defined in [802.3ae] for 10GBASE-W 117 PHYs. Three types of 10GBASE-W PHYs are defined, distinguished by 118 the type of optics employed: 10GBASE-SW, 10GBASE-LW, and 10GBASE-EW. 119 The objects defined in this memo may be used to manage an Ethernet 120 interface employing any type of 10GBASE-W PHY. They do not apply to 121 any other kind of interface. In particular, they do not apply to 122 so-called Ethernet Line Terminating Equipment (ELTE) residing within 123 a SONET network element that uses the 10GBASE-W PMA/PMD sublayers but 124 otherwise acts as SONET Line Terminating Equipment (LTE). 126 The objects presented here -- along with those incorporated by 127 reference from the Interfaces Group MIB, the SONET/SDH Interface MIB, 128 and the 802.3 MAU MIB -- are intended to provide exact 129 representations of the mandatory attributes in the oWIS managed 130 object class (i.e., the members of the pWISBasic package) defined in 131 Clause 30 and Annex 30A of [802.3ae]. They are also intended to 132 provide approximate representations of the optional attributes (i.e., 133 the members of the pWISOptional package). Some objects with no 134 analogues in oWIS are defined to support WIS testing features 135 required by Clause 50 of [802.3ae]. 137 3.1. Relationship to the SONET/SDH Interface MIB 139 Since the Ethernet WAN Interface Sublayer was designed to be SONET- 140 compatible, information similar to that provided by most of the 141 members of the oWIS managed object class is available from objects 142 defined in the SONET-MIB [SONETng]. Thus, the MIB module defined in 143 this memo is a sparse augmentation of the SONET-MIB -- in other 144 words, every table defined here is an extension of some table in the 145 SONET-MIB -- and its compliance statement REQUIRES that an agent 146 implementing the objects defined in this memo also implement the 147 relevant SONET-MIB objects. That includes all objects required by 148 sonetCompliance2 as well as some that it leaves optional. 150 It should be noted that some of the objects incorporated by reference 151 from the SONET-MIB -- specifically, the threshold objects and 152 interval counter objects -- provide only approximate representations 153 of the corresponding oWIS attributes, as detailed in Section 3.6. An 154 alternative approach would have been to define new objects to exactly 155 match the oWIS definitions. That approach was rejected because the 156 SONET-MIB objects are already used in deployed systems to manage the 157 SONET sublayers of ATM over SONET and PPP over SONET interfaces, and 158 it was deemed undesirable to use a different scheme to manage the 159 SONET sublayers of 10 Gb/s WAN-compatible Ethernet interfaces. Note 160 that the approach adopted by this memo requires no hardware support 161 beyond that mandated by [802.3ae] subclause 50.3.11. 163 3.2. Relationship to the Ethernet-like Interface MIB 165 An interface which includes the Ethernet WIS is, by definition, an 166 Ethernet-like interface, and an agent implementing the objects 167 defined in this memo MUST implement the objects required by the 168 dot3Compliance2 compliance statement in the EtherLike-MIB. 170 3.3. Relationship to the 802.3 MAU MIB 172 Support for the mauModIfCompl3 compliance statement of the MAU-MIB 173 [MAU-MIB] is REQUIRED for all Ethernet-like interfaces. The MAU-MIB 174 is needed in order to allow applications to control and/or determine 175 the media type in use. That is important for devices than can 176 support both the 10GBASE-R 10 Gb/s LAN format (which does not include 177 the WIS) and the 10GBASE-W 10 Gb/s WAN format (which does include the 178 WIS). The MAU-MIB also provides the means to put a device in standby 179 mode or to reset it; the latter may be used to re-initialize the 180 WIS. 182 3.4. Use of the ifTable 184 This section specifies how the ifTable, as defined in [RFC2863], is 185 used for the Ethernet WIS application. 187 3.4.1. Layering Model 189 Ethernet interfaces that employ the WIS are layered as defined in 190 [802.3ae]. The corresponding use of the ifTable [RFC2863] is shown 191 in the figure below. 193 _____________________________ _ 194 | LLC Layer | | 195 +-----------------------------+ | 196 | MAC Layer | | 197 +-----------------------------+ > 1 ifEntry 198 | Reconciliation Sublayer | | ifType: ethernetCsmacd(6) 199 +-----------------------------+ | 200 | Physical Coding Sublayer | | 201 +-----------------------------+ + 202 | Path Layer | > 1 ifEntry 203 +-----------------------------+ + ifType: sonetPath(50) 204 | Line Layer | | 205 +-----------------------------+ | 206 | Section Layer | > 1 ifEntry 207 +-----------------------------+ | ifType: sonet(39) 208 | Physical Medium Layer | | 209 ----------------------------- - 211 Figure 1 - Use of ifTable for an Ethernet WIS port 213 The exact configuration and multiplexing of the layers is maintained 214 in the ifStackTable [RFC2863] and in the ifInvStackTable [RFC2864]. 216 3.4.2. Use of ifTable for LLC Layer/MAC Layer/Reconciliation 217 Sublayer/Physical Coding Sublayer 219 The ifTable MUST be used as specified in [ETHERIF] and [MAU-MIB] for 220 the LLC Layer/MAC Layer/Reconciliation Sublayer/Physical Coding 221 Sublayer. 223 3.4.3. Use of ifTable for SONET/SDH Path Layer 225 The ifTable MUST be used as specified in [SONETng] for the SONET/SDH 226 Path Layer. The value of ifHighSpeed is set to 9585. ifSpeed 227 reports a value of 4294967295. 229 3.4.4. Use of ifTable for SONET/SDH Medium/Section/Line Layer 231 The ifTable MUST be used as specified in [SONETng] for the SONET/SDH 232 Medium/Section/Line Layer. The value of ifHighSpeed is set to 9953. 233 ifSpeed reports a value of 4294967295. 235 3.5. SONET/SDH Terminology 237 The SONET/SDH terminology used in [802.3ae] is mostly the same as in 238 [SONETng], but there are a few differences. In those cases the 239 definitions in [802.3ae] take precedence. The specific differences 240 are as follows. 242 Unequipped 243 This defect is not defined by [802.3ae]. An implementation that 244 supports it SHOULD report it by setting the sonetPathUnequipped 245 bit in the appropriate instance of sonetPathCurrentStatus. 247 Signal Label Mismatch 248 This defect is called Payload Label Mismatch (PLM) in [802.3ae]. 249 It is reported by setting both the sonetPathSignalLabelMismatch 250 bit in the appropriate instance of sonetPathCurrentStatus 251 (defined in [SONETng]) and the etherWisPathPLM bit in the 252 corresponding instance of etherWisPathCurrentStatus (defined 253 below). 255 Loss of Codegroup Delineation 256 [802.3ae] defines Loss of Codegroup Delineation (LCD) as 257 occurring when the Physical Coding Sublayer is unable to locate 258 64B/66B code group boundaries. There is no analogous defect 259 defined in [SONETng]. It is reported by setting the 260 etherWisPathLCD bit in the appropriate instance of the object 261 etherWisPathCurrentStatus defined below. 263 STS-Path Remote Defect Indication 264 [802.3ae] mandates the use of ERDI-P (Enhanced Remote Defect 265 Indication - Path) defined in [T1.231] to signal remote server 266 defects (triggered by path AIS or path LOP) and remote payload 267 defects (triggered by Payload Label Mismatch or Loss of Codegroup 268 Delineation). [SONETng] defines the one-bit RDI-P (Remote Defect 269 Indication - Path), which signals remote server detects (i.e., 270 path AIS and path LOP) only. An implementation of the MIB module 271 defined in this memo MUST set the sonetPathSTSRDI bit in the 272 appropriate instance of sonetPathCurrentStatus when it receives 273 an ERDI-P server defect indication from the remote end. Both 274 ERDI-P payload defects and ERDI-P server defects are reported in 275 the object etherWisFarEndPathCurrentStatus defined below. 277 Path Coding Violations 278 In [802.3ae] the path layer CV count is based on block errors and 279 not BIP-8 errors, i.e., it is incremented only once for each B3 280 byte that indicates incorrect parity, regardless of the number of 281 bits in error. Note that Section 8.4.5.1 of [T1.231] allows 282 either path BIP-8 errors or path block errors to be used for the 283 path layer error count. 285 3.6. Mapping of IEEE 802.3 Managed Objects 287 This section contains the mapping between oWIS managed objects 288 defined in [802.3ae] and managed objects defined in this document and 289 in associated MIB modules, i.e., the IF-MIB [RFC2863], the SONET-MIB 290 [SONETng], and the MAU-MIB [MAU-MIB]. 292 IEEE 802.3 Managed Object Corresponding SNMP Object 294 oWIS - pWISBasic package 295 aWISID IF-MIB - ifIndex 296 aSectionStatus SONET-MIB - sonetSectionCurrentStatus 297 aLineStatus SONET-MIB - sonetLineCurrentStatus 298 aPathStatus etherWisPathCurrentStatus 299 aFarEndPathStatus etherWisFarEndPathCurrentStatus 301 oWIS - pWISOptional package 302 aSectionSESThreshold SONET-MIB - sonetSESthresholdSet 303 aSectionSESs SONET-MIB - sonetSectionCurrentSESs + 304 sonetSectionIntervalSESs 305 aSectionESs SONET-MIB - sonetSectionCurrentESs + 306 sonetSectionIntervalESs 307 aSectionSEFSs SONET-MIB - sonetSectionCurrentSEFSs + 308 sonetSectionIntervalSEFSs 309 aSectionCVs SONET-MIB - sonetSectionCurrentCVs + 310 sonetSectionIntervalCVs 312 aJ0ValueTX etherWisSectionCurrentJ0Transmitted 313 aJ0ValueRX etherWisSectionCurrentJ0Received 314 aLineSESThreshold SONET-MIB - sonetSESthresholdSet 315 aLineSESs SONET-MIB - sonetLineCurrentSESs + 316 sonetLineIntervalSESs 317 aLineESs SONET-MIB - sonetLineCurrentESs + 318 sonetLineIntervalESs 319 aLineCVs SONET-MIB - sonetLineCurrentCVs + 320 sonetLineIntervalCVs 321 aFarEndLineSESs SONET-MIB - sonetFarEndLineCurrentSESs + 322 sonetFarEndLineIntervalSESs 323 aFarEndLineESs SONET-MIB - sonetFarEndLineCurrentESs + 324 sonetFarEndLineIntervalESs 325 aFarEndLineCVs SONET-MIB - sonetFarEndLineCurrentCVs + 326 sonetFarEndLineIntervalCVs 327 aPathSESThreshold SONET-MIB - sonetSESthresholdSet 328 aPathSESs SONET-MIB - sonetPathCurrentSESs + 329 sonetPathIntervalSESs 330 aPathESs SONET-MIB - sonetPathCurrentESs + 331 sonetPathIntervalESs 332 aPathCVs SONET-MIB - sonetPathCurrentCVs + 333 sonetPathIntervalCVs 334 aJ1ValueTX etherWisPathCurrentJ1Transmitted 335 aJ1ValueRX etherWisPathCurrentJ1Received 336 aFarEndPathSESs SONET-MIB - sonetFarEndPathCurrentSESs + 337 sonetFarEndPathIntervalSESs 338 aFarEndPathESs SONET-MIB - sonetFarEndPathCurrentESs + 339 sonetFarEndPathIntervalESs 340 aFarEndPathCVs SONET-MIB - sonetFarEndPathCurrentCVs + 341 sonetFarEndPathIntervalCVs 343 It should be noted that the threshold and counter objects imported 344 from the SONET-MIB are not completely equivalent to the corresponding 345 IEEE 802.3 objects. The specific differences are as follows: 347 IEEE 802.3 Managed Object How Corresponding SNMP Object Differs 349 aSectionSESThreshold This object is defined in [802.3ae] 350 as an integer with one instance per 351 interface. sonetSESthresholdSet 352 is an enumerated value that has one 353 instance per network element; it 354 controls the thresholds for all layers 355 simultaneously and allows only certain 356 discrete values to be selected. 357 aSectionSESs This object is defined in [802.3ae] as 358 a generalized nonresetable counter. 359 The objects sonetSectionCurrentSESs and 360 sonetSectionIntervalSESs are 15-minute 361 interval counters. 362 aSectionESs This object is defined as a generalized 363 nonresetable counter in [802.3ae]. 364 The objects sonetSectionCurrentESs and 365 sonetSectionIntervalESs are 15-minute 366 interval counters. 367 aSectionSEFSs This object is defined as a generalized 368 nonresetable counter in [802.3ae]. 369 The objects sonetSectionCurrentSEFSs and 370 sonetSectionIntervalSEFSs are 15-minute 371 interval counters. 372 aSectionCVs This object is defined as a generalized 373 nonresetable counter in [802.3ae], and 374 it is not subject to inhibiting. The 375 objects sonetSectionCurrentCVs and 376 sonetSectionIntervalCVs are 15-minute 377 interval counters, and they are 378 inhibited (not incremented) during 379 one-second intervals that qualify as 380 severely errored seconds. 381 aLineSESThreshold This object is defined in [802.3ae] 382 as an integer with one instance per 383 interface. sonetSESthresholdSet 384 is an enumerated value that has one 385 instance per network element; it 386 controls the thresholds for all layers 387 simultaneously and allows only certain 388 discrete values to be selected. 389 aLineSESs This object is defined as a generalized 390 nonresetable counter in [802.3ae], and 391 it is not subject to inhibiting. The 392 objects sonetLineCurrentSESs and 393 sonetLineIntervalSESs are 15-minute 394 interval counters, and they are 395 inhibited (not incremented) during 396 one-second intervals that qualify as 397 unavailable seconds. 398 aLineESs This object is defined as a generalized 399 nonresetable counter in [802.3ae], and 400 it is not subject to inhibiting. The 401 objects sonetLineCurrentESs and 402 sonetLineIntervalESs are 15-minute 403 interval counters, and they are 404 inhibited (not incremented) during 405 one-second intervals that qualify as 406 unavailable seconds. 407 aLineCVs This object is defined as a generalized 408 nonresetable counter in [802.3ae], and 409 it is not subject to inhibiting. The 410 objects sonetLineCurrentCVs and 411 sonetLineIntervalCVs are 15-minute 412 interval counters, and they are 413 inhibited (not incremented) during 414 one-second intervals that qualify 415 either as severely errored seconds 416 or as unavailable seconds. 417 aFarEndLineSESs This object is defined as a generalized 418 nonresetable counter in [802.3ae], and 419 it is not subject to inhibiting. The 420 objects sonetFarEndLineCurrentSESs and 421 sonetFarEndLineIntervalSESs are 422 15-minute interval counters, and they 423 are inhibited (not incremented) during 424 one-second intervals that qualify as 425 unavailable seconds. 426 aFarEndLineESs This object is defined as a generalized 427 nonresetable counter in [802.3ae], and 428 it is not subject to inhibiting. The 429 objects sonetFarEndLineCurrentESs and 430 sonetFarEndLineIntervalESs are 15-minute 431 interval counters, and they are 432 inhibited (not incremented) during 433 one-second intervals that qualify as 434 unavailable seconds. 435 aFarEndLineCVs This object is defined as a generalized 436 nonresetable counter in [802.3ae], and 437 it is not subject to inhibiting. The 438 objects sonetFarEndLineCurrentCVs and 439 sonetFarEndLineIntervalCVs are 15-minute 440 interval counters, and they are 441 inhibited (not incremented) during 442 one-second intervals that qualify 443 either as severely errored seconds 444 or as unavailable seconds. 445 aPathSESThreshold This object is defined in [802.3ae] 446 as an integer with one instance per 447 interface. sonetSESthresholdSet 448 is an enumerated value that has one 449 instance per network element; it 450 controls the thresholds for all layers 451 simultaneously and allows only certain 452 discrete values to be selected. 453 aPathSESs This object is defined as a generalized 454 nonresetable counter in [802.3ae], and 455 it is not subject to inhibiting. The 456 objects sonetPathCurrentSESs and 457 sonetPathIntervalSESs are 15-minute 458 interval counters, and they are 459 inhibited (not incremented) during 460 one-second intervals that qualify as 461 unavailable seconds. In addition, 462 [802.3ae] includes PLM-P and LCD-P 463 defects in the criteria for declaring 464 path layer severely errored seconds, 465 while [SONETng] does not. 466 aPathESs This object is defined as a generalized 467 nonresetable counter in [802.3ae], and 468 it is not subject to inhibiting. The 469 objects sonetPathCurrentESs and 470 sonetPathIntervalESs are 15-minute 471 interval counters, and they are 472 inhibited (not incremented) during 473 one-second intervals that qualify as 474 unavailable seconds. In addition, 475 [802.3ae] includes PLM-P and LCD-P 476 defects in the criteria for declaring 477 path layer errored seconds, while 478 [SONETng] does not. 479 aPathCVs This object is defined as a generalized 480 nonresetable counter in [802.3ae], and 481 it is not subject to inhibiting. The 482 objects sonetPathCurrentCVs and 483 sonetPathIntervalCVs are 15-minute 484 interval counters, and they are 485 inhibited (not incremented) during 486 one-second intervals that qualify 487 either as severely errored seconds 488 or as unavailable seconds. 489 aFarEndPathSESs This object is defined as a generalized 490 nonresetable counter in [802.3ae], and 491 it is not subject to inhibiting. The 492 objects sonetFarEndPathCurrentSESs and 493 sonetFarEndPathIntervalSESs are 494 15-minute interval counters, and they 495 are inhibited (not incremented) during 496 one-second intervals that qualify as 497 unavailable seconds. In addition, 498 [802.3ae] includes far-end PLM-P and 499 LCD-P defects in the criteria for 500 declaring far-end path layer severely 501 errored seconds, while [SONETng] does 502 not. 503 aFarEndPathESs This object is defined as a generalized 504 nonresetable counter in [802.3ae], and 505 it is not subject to inhibiting. The 506 objects sonetFarEndPathCurrentESs and 507 sonetFarEndPathIntervalESs are 15-minute 508 interval counters, and they are 509 inhibited (not incremented) during 510 one-second intervals that qualify as 511 unavailable seconds. In addition, 512 [802.3ae] includes far-end PLM-P and 513 LCD-P defects in the criteria for 514 declaring far-end path layer errored 515 seconds, while [SONETng] does not. 516 aFarEndPathCVs This object is defined as a generalized 517 nonresetable counter in [802.3ae], and 518 it is not subject to inhibiting. The 519 objects sonetFarEndPathCurrentCVs and 520 sonetFarEndPathIntervalCVs are 15-minute 521 interval counters, and they are 522 inhibited (not incremented) during 523 one-second intervals that qualify 524 either as severely errored seconds 525 or as unavailable seconds. 527 Note: despite the semantic differences between the threshold objects 528 and counter objects imported from the SONET-MIB and the corresponding 529 IEEE 802.3 objects, the hardware support mandated by [802.3ae] 530 subclause 50.3.11 suffices for both. See Appendix A for details. 532 3.7. Mapping of SNMP Objects to WIS Station Management Registers 534 Some of the objects defined in this memo or incorporated by reference 535 from the SONET-MIB [SONETng] or the MAU-MIB [MAU-MIB] require WIS- 536 specific hardware support. [802.3ae] subclause 50.3.11 specifies WIS 537 management interface requirements, including a required subset of the 538 WIS Management Data Input/Output (MDIO) registers defined in 539 [802.3ae] subclause 45.2.2. The table below provides a cross- 540 reference between those managed objects and the WIS MDIO registers 541 from the subset in [802.3ae] subclause 50.3.11 required to support 542 them. Note that the MDIO interface is optional; however, if it is 543 not implemented, then the capabilities of the required register 544 subset must be provided by other means. 546 SNMP Object WIS MDIO Register(s) 548 ETHER-WIS - etherWisDeviceTxTestPatternMode 10G WIS control 2 549 ETHER-WIS - etherWisDeviceRxTestPatternMode 10G WIS control 2 550 ETHER-WIS - etherWisDeviceRxTestPatternErrors 10G WIS test pattern 551 error counter 553 SONET-MIB - sonetMediumType none required 554 SONET-MIB - sonetMediumTimeElapsed none required 555 SONET-MIB - sonetMediumValidIntervals none required 556 SONET-MIB - sonetMediumLineCoding none required 557 SONET-MIB - sonetMediumLineType none required 558 SONET-MIB - sonetMediumCircuitIdentifier none required 559 SONET-MIB - sonetMediumInvalidIntervals none required 560 SONET-MIB - sonetMediumLoopbackConfig none required 561 SONET-MIB - sonetSESthresholdSet none required 563 ETHER-WIS - etherWisSectionCurrentJ0Transmitted 10G WIS J0 transmit 564 ETHER-WIS - etherWisSectionCurrentJ0Received 10G WIS J0 receive 566 SONET-MIB - sonetSectionCurrentStatus 10G WIS status 3 567 SONET-MIB - sonetSectionCurrentESs \ 568 SONET-MIB - sonetSectionCurrentSESs \ 569 SONET-MIB - sonetSectionCurrentSEFSs | 10G WIS status 3 570 SONET-MIB - sonetSectionCurrentCVs | + 571 SONET-MIB - sonetSectionIntervalESs | 10G WIS section 572 SONET-MIB - sonetSectionIntervalSESs | BIP error count 573 SONET-MIB - sonetSectionIntervalSEFSs / 574 SONET-MIB - sonetSectionIntervalCVs / 575 SONET-MIB - sonetSectionIntervalValidData none required 577 SONET-MIB - sonetLineCurrentStatus 10G WIS status 3 578 SONET-MIB - sonetLineCurrentESs \ 579 SONET-MIB - sonetLineCurrentSESs \ 580 SONET-MIB - sonetLineCurrentCVs | 10G WIS status 3 581 SONET-MIB - sonetLineCurrentUASs | + 582 SONET-MIB - sonetLineIntervalESs | 10G WIS line 583 SONET-MIB - sonetLineIntervalSESs | BIP errors 584 SONET-MIB - sonetLineIntervalCVs / 585 SONET-MIB - sonetLineIntervalUASs / 586 SONET-MIB - sonetLineIntervalValidData none required 588 SONET-MIB - sonetFarEndLineCurrentESs \ 589 SONET-MIB - sonetFarEndLineCurrentSESs \ 590 SONET-MIB - sonetFarEndLineCurrentCVs | 10G WIS status 3 591 SONET-MIB - sonetFarEndLineCurrentUASs | + 592 SONET-MIB - sonetFarEndLineIntervalESs | 10G WIS far end 593 SONET-MIB - sonetFarEndLineIntervalSESs | line BIP errors 594 SONET-MIB - sonetFarEndLineIntervalCVs / 595 SONET-MIB - sonetFarEndLineIntervalUASs / 596 SONET-MIB - sonetFarEndLineIntervalValidData 10G WIS status 3 598 ETHER-WIS - etherWisPathCurrentStatus 10G WIS status 3 599 ETHER-WIS - etherWisPathCurrentJ1Transmitted 10G WIS J1 transmit 600 ETHER-WIS - etherWisPathCurrentJ1Received 10G WIS J1 receive 601 SONET-MIB - sonetPathCurrentWidth none required 602 SONET-MIB - sonetPathCurrentStatus 10G WIS status 3 603 SONET-MIB - sonetPathCurrentESs \ 604 SONET-MIB - sonetPathCurrentSESs \ 605 SONET-MIB - sonetPathCurrentCVs | 10G WIS status 3 606 SONET-MIB - sonetPathCurrentUASs | + 607 SONET-MIB - sonetPathIntervalESs | 10G WIS 608 SONET-MIB - sonetPathIntervalSESs | path block 609 SONET-MIB - sonetPathIntervalCVs / error count 610 SONET-MIB - sonetPathIntervalUASs / 611 SONET-MIB - sonetPathIntervalValidData none required 613 ETHER-WIS - etherWisFarEndPathCurrentStatus 10G WIS status 3 615 SONET-MIB - sonetFarEndPathCurrentESs \ 616 SONET-MIB - sonetFarEndPathCurrentSESs \ 617 SONET-MIB - sonetFarEndPathCurrentCVs | 10G WIS status 3 618 SONET-MIB - sonetFarEndPathCurrentUASs | + 619 SONET-MIB - sonetFarEndPathIntervalESs | 10G WIS far end 620 SONET-MIB - sonetFarEndPathIntervalSESs | path block 621 SONET-MIB - sonetFarEndPathIntervalCVs / error count 622 SONET-MIB - sonetFarEndPathIntervalUASs / 623 SONET-MIB - sonetFarEndPathIntervalValidData 10G WIS status 3 625 MAU-MIB - ifMauIfIndex none required 626 MAU-MIB - ifMauIndex none required 627 MAU-MIB - ifMauType 10G WIS control 2 628 MAU-MIB - ifMauStatus WIS control 1 629 MAU-MIB - ifMauMediaAvailable \ WIS status 1 + 630 MAU-MIB - ifMauMediaAvailableStateExits / 10G WIS status 3 631 MAU-MIB - ifMauJabberState none required 632 MAU-MIB - ifMauJabberingStateEnters none required 633 MAU-MIB - ifMauFalseCarriers none required 634 MAU-MIB - ifMauDefaultType 10G WIS control 2 635 MAU-MIB - ifMauAutoNegSupported none required 636 MAU-MIB - ifMauTypeListBits 10G WIS status 2 638 3.8. Structure of the MIB Module 640 Four tables are defined in this MIB module. 642 3.8.1. etherWisDeviceTable 644 The purpose of this table is to define managed objects to control the 645 WIS test pattern mode. These objects are required to support 646 mandatory and optional WIS test features specified in [802.3ae] 647 subclause 50.3.8. 649 The etherWisDeviceTable is a sparse augmentation of the 650 sonetMediumTable of the SONET-MIB -- in other words, for each entry 651 in the etherWisDeviceTable there MUST be an entry in the 652 sonetMediumTable and the same ifIndex value MUST be used for both 653 entries. 655 3.8.2. etherWisSectionCurrentTable 657 The purpose of this table is to define managed objects for the 658 transmitted and received section trace messages (J0 byte). 660 The etherWisSectionCurrentTable is a sparse augmentation of the 661 sonetSectionCurrentTable of the SONET-MIB -- in other words, for each 662 entry in the etherWisSectionCurrentTable there MUST be an entry in 663 the sonetSectionCurrentTable and the same ifIndex value MUST be used 664 for both entries. 666 3.8.3. etherWisPathCurrentTable 668 The purpose of this table is to define managed objects for the 669 current WIS path layer status and for the transmitted and received 670 path trace messages (J1 byte). The path layer status object is 671 provided because the WIS supports some near-end path status 672 conditions that are not reported in sonetPathCurrentStatus. 674 The etherWisPathCurrentTable is a sparse augmentation of the 675 sonetPathCurrentTable of the SONET-MIB -- in other words, for each 676 entry in the etherWisPathCurrentTable there MUST be an entry in the 677 sonetPathCurrentTable and the same ifIndex value MUST be used for 678 both entries. 680 3.8.4. etherWisFarEndPathCurrentTable 682 The purpose of this table is to define a managed object for the 683 current status of the far end of the path. This object is provided 684 because the WIS supports some far-end path status conditions that are 685 not reported in sonetPathCurrentStatus. 687 The etherWisFarEndPathCurrentTable is a sparse augmentation of the 688 sonetFarEndPathCurrentTable of the SONET-MIB -- in other words, for 689 each entry in the etherWisFarEndPathCurrentTable there MUST be an 690 entry in the sonetFarEndPathCurrentTable and the same ifIndex value 691 MUST be used for both entries. 693 4. Object Definitions 695 ETHER-WIS DEFINITIONS ::= BEGIN 697 IMPORTS 698 MODULE-IDENTITY, OBJECT-TYPE, 699 Gauge32, transmission 700 FROM SNMPv2-SMI 701 ifIndex 702 FROM IF-MIB 703 MODULE-COMPLIANCE, OBJECT-GROUP 704 FROM SNMPv2-CONF 705 sonetMediumStuff2, sonetSectionStuff2, 706 sonetLineStuff2, sonetFarEndLineStuff2, 707 sonetPathStuff2, sonetFarEndPathStuff2, 708 sonetMediumType, sonetMediumLineCoding, 709 sonetMediumLineType, sonetMediumCircuitIdentifier, 710 sonetMediumLoopbackConfig, sonetSESthresholdSet, 711 sonetPathCurrentWidth 712 FROM SONET-MIB; 714 etherWisMIB MODULE-IDENTITY 715 LAST-UPDATED "200301042136Z" -- January 4, 2003 716 ORGANIZATION "IETF Ethernet Interfaces and Hub MIB 717 Working Group" 718 CONTACT-INFO 719 "WG charter: 720 http://www.ietf.org/html.charters/hubmib-charter.html 722 Mailing Lists: 723 General Discussion: hubmib@ietf.org 724 To Subscribe: hubmib-request@ietf.org 725 In Body: subscribe your_email_address 727 Chair: Dan Romascanu 728 Postal: Avaya Inc. 729 Atidim Technology Park, Bldg. 3 730 Tel Aviv 61131 731 Israel 732 Tel: +972 3 645 8414 733 E-mail: dromasca@avaya.com 735 Editor: C. M. Heard 736 Postal: 600 Rainbow Dr. #141 737 Mountain View, CA 94041-2542 738 USA 739 Tel: +1 650-964-8391 740 E-mail: heard@pobox.com" 742 DESCRIPTION 743 "The objects in this MIB module are used in conjunction 744 with objects in the SONET-MIB and the MAU-MIB to manage 745 the Ethernet WAN Interface Sublayer (WIS). 747 The following reference is used throughout this MIB module: 749 [IEEE 802.3 Std] refers to: 750 IEEE Std 802.3, 2000 Edition: 'IEEE Standard for 751 Information technology - Telecommunications and 752 information exchange between systems - Local and 753 metropolitan area networks - Specific requirements - 754 Part 3: Carrier sense multiple access with collision 755 detection (CSMA/CD) access method and physical layer 756 specifications', as amended by IEEE Std 802.3ae-2002, 757 'IEEE Standard for Carrier Sense Multiple Access with 758 Collision Detection (CSMA/CD) Access Method and 759 Physical Layer Specifications - Media Access Control 760 (MAC) Parameters, Physical Layer and Management 761 Parameters for 10 Gb/s Operation', 30 August 2002. 763 Of particular interest are Clause 50, 'WAN Interface 764 Sublayer (WIS), type 10GBASE-W', Clause 30, '10Mb/s, 765 100Mb/s, 1000Mb/s, and 10Gb/s MAC Control, and Link 766 Aggregation Management', and Clause 45, 'Management 767 Data Input/Output (MDIO) Interface'. 769 Copyright (C) The Internet Society (2003). This version 770 of this MIB module is part of RFC yyyy; see the RFC 771 itself for full legal notices." 772 -- RFC Ed.: replace yyyy with actual RFC number & remove this notice 774 REVISION "200301042136Z" -- January 4, 2003 775 DESCRIPTION "Initial version, published as RFC yyyy." 776 -- RFC Ed.: replace yyyy with actual RFC number & remove this notice 778 ::= { transmission XXX } 779 -- RFC Ed.: replace XXX with IANA-assigned number & remove this notice 780 -- The main sections of the module 782 etherWisObjects OBJECT IDENTIFIER ::= { etherWisMIB 1 } 784 etherWisObjectsPath OBJECT IDENTIFIER ::= { etherWisMIB 2 } 786 etherWisConformance OBJECT IDENTIFIER ::= { etherWisMIB 3 } 788 -- groups in the Ethernet WIS MIB module 790 etherWisDevice OBJECT IDENTIFIER ::= { etherWisObjects 1 } 792 etherWisSection OBJECT IDENTIFIER ::= { etherWisObjects 2 } 794 etherWisPath OBJECT IDENTIFIER ::= { etherWisObjectsPath 1 } 796 etherWisFarEndPath OBJECT IDENTIFIER ::= { etherWisObjectsPath 2 } 798 -- The Device group 800 -- These objects provide WIS extensions to 801 -- the SONET-MIB Medium Group. 803 etherWisDeviceTable OBJECT-TYPE 804 SYNTAX SEQUENCE OF EtherWisDeviceEntry 805 MAX-ACCESS not-accessible 806 STATUS current 807 DESCRIPTION 808 "The table for Ethernet WIS devices" 809 ::= { etherWisDevice 1 } 811 etherWisDeviceEntry OBJECT-TYPE 812 SYNTAX EtherWisDeviceEntry 813 MAX-ACCESS not-accessible 814 STATUS current 815 DESCRIPTION 816 "An entry in the Ethernet WIS device table. For each 817 instance of this object there MUST be a corresponding 818 instance of sonetMediumEntry." 819 INDEX { ifIndex } 820 ::= { etherWisDeviceTable 1 } 822 EtherWisDeviceEntry ::= 823 SEQUENCE { 824 etherWisDeviceTxTestPatternMode INTEGER, 825 etherWisDeviceRxTestPatternMode INTEGER, 826 etherWisDeviceRxTestPatternErrors Gauge32 827 } 829 etherWisDeviceTxTestPatternMode OBJECT-TYPE 830 SYNTAX INTEGER { 831 none(1), 832 squareWave(2), 833 prbs31(3), 834 mixedFrequency(4) 835 } 836 MAX-ACCESS read-write 837 STATUS current 838 DESCRIPTION 839 "This variable controls the transmit test pattern mode. 840 The value none(1) puts the the WIS transmit path into 841 the normal operating mode. The value squareWave(2) puts 842 the WIS transmit path into the square wave test pattern 843 mode described in [IEEE 802.3 Std.] subclause 50.3.8.1. 844 The value prbs31(3) puts the WIS transmit path into the 845 PRBS31 test pattern mode described in [IEEE 802.3 Std.] 846 subclause 50.3.8.2. The value mixedFrequency(4) puts the 847 WIS transmit path into the mixed frequency test pattern 848 mode described in [IEEE 802.3 Std.] subclause 50.3.8.3. 849 Any attempt to set this object to a value other than 850 none(1) when the corresponding instance of ifAdminStatus 851 has the value up(1) MUST be rejected with the error 852 inconsistentValue, and any attempt to set the corresponding 853 instance of ifAdminStatus to the value up(1) when an 854 instance of this object has a value other than none(1) 855 MUST be rejected with the error inconsistentValue." 856 REFERENCE 857 "[IEEE 802.3 Std.], 50.3.8, WIS test pattern generator and 858 checker, 45.2.2.6, 10G WIS control 2 register (2.7), and 859 45.2.2.7.2, PRBS31 pattern testing ability (2.8.1)." 860 ::= { etherWisDeviceEntry 1 } 862 etherWisDeviceRxTestPatternMode OBJECT-TYPE 863 SYNTAX INTEGER { 864 none(1), 865 prbs31(3), 866 mixedFrequency(4) 867 } 868 MAX-ACCESS read-write 869 STATUS current 870 DESCRIPTION 871 "This variable controls the receive test pattern mode. 872 The value none(1) puts the the WIS receive path into the 873 normal operating mode. The value prbs31(3) puts the WIS 874 receive path into the PRBS31 test pattern mode described 875 in [IEEE 802.3 Std.] subclause 50.3.8.2. The value 876 mixedFrequency(4) puts the WIS receive path into the mixed 877 frequency test pattern mode described in [IEEE 802.3 Std.] 878 subclause 50.3.8.3. Any attempt to set this object to a 879 value other than none(1) when the corresponding instance 880 of ifAdminStatus has the value up(1) MUST be rejected with 881 the error inconsistentValue, and any attempt to set the 882 corresponding instance of ifAdminStatus to the value up(1) 883 when an instance of this object has a value other than 884 none(1) MUST be rejected with the error inconsistentValue." 885 REFERENCE 886 "[IEEE 802.3 Std.], 50.3.8, WIS test pattern generator and 887 checker, 45.2.2.6, 10G WIS control 2 register (2.7), and 888 45.2.2.7.2, PRBS31 pattern testing ability (2.8.1)." 889 ::= { etherWisDeviceEntry 2 } 891 etherWisDeviceRxTestPatternErrors OBJECT-TYPE 892 SYNTAX Gauge32 ( 0..65535 ) 893 MAX-ACCESS read-write 894 STATUS current 895 DESCRIPTION 896 "This object counts the number of errors detected when the 897 WIS receive path is operating in the PRBS31 test pattern 898 mode. It is reset to zero when the WIS receive path 899 initially enters that mode, and it increments each time 900 the PRBS pattern checker detects an error as described in 901 [IEEE 802.3 Std.] subclause 50.3.8.2 unless its value is 902 65535, in which case it remains unchanged. This object is 903 writeable so that it may be reset upon explicit request 904 of a command generator application while the WIS receive 905 path continues to operate in PRBS31 test pattern mode." 906 REFERENCE 907 "[IEEE 802.3 Std.], 50.3.8, WIS test pattern generator and 908 checker, 45.2.2.7.2, PRBS31 pattern testing ability 909 (2.8.1), and 45.2.2.8, 10G WIS test pattern error counter 910 register (2.9)." 911 ::= { etherWisDeviceEntry 3 } 913 -- The Section group 915 -- These objects provide WIS extensions to 916 -- the SONET-MIB Section Group. 918 etherWisSectionCurrentTable OBJECT-TYPE 919 SYNTAX SEQUENCE OF EtherWisSectionCurrentEntry 920 MAX-ACCESS not-accessible 921 STATUS current 922 DESCRIPTION 923 "The table for the current state of Ethernet WIS sections." 924 ::= { etherWisSection 1 } 926 etherWisSectionCurrentEntry OBJECT-TYPE 927 SYNTAX EtherWisSectionCurrentEntry 928 MAX-ACCESS not-accessible 929 STATUS current 930 DESCRIPTION 931 "An entry in the etherWisSectionCurrentTable. For each 932 instance of this object there MUST be a corresponding 933 instance of sonetSectionCurrentEntry." 934 INDEX { ifIndex } 935 ::= { etherWisSectionCurrentTable 1 } 937 EtherWisSectionCurrentEntry ::= 938 SEQUENCE { 939 etherWisSectionCurrentJ0Transmitted OCTET STRING, 940 etherWisSectionCurrentJ0Received OCTET STRING 941 } 943 etherWisSectionCurrentJ0Transmitted OBJECT-TYPE 944 SYNTAX OCTET STRING (SIZE (16)) 945 MAX-ACCESS read-write 946 STATUS current 947 DESCRIPTION 948 "This is the 16-octet section trace message that 949 is transmitted in the J0 byte. The value SHOULD 950 be '89'h followed by fifteen octets of '00'h 951 (or some cyclic shift thereof) when the section 952 trace function is not used, and the implementation 953 SHOULD use that value (or a cyclic shift thereof) 954 as a default if no other value has been set." 955 REFERENCE 956 "[IEEE 802.3 Std.], 30.8.1.1.8, aJ0ValueTX." 957 ::= { etherWisSectionCurrentEntry 1 } 959 etherWisSectionCurrentJ0Received OBJECT-TYPE 960 SYNTAX OCTET STRING (SIZE (16)) 961 MAX-ACCESS read-only 962 STATUS current 963 DESCRIPTION 964 "This is the 16-octet section trace message that 965 was most recently received in the J0 byte." 966 REFERENCE 967 "[IEEE 802.3 Std.], 30.8.1.1.9, aJ0ValueRX." 968 ::= { etherWisSectionCurrentEntry 2 } 970 -- The Path group 972 -- These objects provide WIS extensions to 973 -- the SONET-MIB Path Group. 975 etherWisPathCurrentTable OBJECT-TYPE 976 SYNTAX SEQUENCE OF EtherWisPathCurrentEntry 977 MAX-ACCESS not-accessible 978 STATUS current 979 DESCRIPTION 980 "The table for the current state of Ethernet WIS paths." 981 ::= { etherWisPath 1 } 983 etherWisPathCurrentEntry OBJECT-TYPE 984 SYNTAX EtherWisPathCurrentEntry 985 MAX-ACCESS not-accessible 986 STATUS current 987 DESCRIPTION 988 "An entry in the etherWisPathCurrentTable. For each 989 instance of this object there MUST be a corresponding 990 instance of sonetPathCurrentEntry." 991 INDEX { ifIndex } 992 ::= { etherWisPathCurrentTable 1 } 994 EtherWisPathCurrentEntry ::= 995 SEQUENCE { 996 etherWisPathCurrentStatus BITS, 997 etherWisPathCurrentJ1Transmitted OCTET STRING, 998 etherWisPathCurrentJ1Received OCTET STRING 999 } 1001 etherWisPathCurrentStatus OBJECT-TYPE 1002 SYNTAX BITS { 1003 etherWisPathLOP(0), 1004 etherWisPathAIS(1), 1005 etherWisPathPLM(2), 1006 etherWisPathLCD(3) 1007 } 1008 MAX-ACCESS read-only 1009 STATUS current 1010 DESCRIPTION 1011 "This variable indicates the current status of the 1012 path payload with a bit map that can indicate multiple 1013 defects at once. The bit positions are assigned as 1014 follows: 1016 etherWisPathLOP(0) 1017 This bit is set to indicate that an 1018 LOP-P (Loss of Pointer - Path) defect 1019 is being experienced. Note: when this 1020 bit is set, sonetPathSTSLOP MUST be set 1021 in the corresponding instance of 1022 sonetPathCurrentStatus. 1024 etherWisPathAIS(1) 1025 This bit is set to indicate that an 1026 AIS-P (Alarm Indication Signal - Path) 1027 defect is being experienced. Note: when 1028 this bit is set, sonetPathSTSAIS MUST be 1029 set in the corresponding instance of 1030 sonetPathCurrentStatus. 1032 etherWisPathPLM(1) 1033 This bit is set to indicate that a 1034 PLM-P (Payload Label Mismatch - Path) 1035 defect is being experienced. Note: when 1036 this bit is set, sonetPathSignalLabelMismatch 1037 MUST be set in the corresponding instance of 1038 sonetPathCurrentStatus. 1040 etherWisPathLCD(3) 1041 This bit is set to indicate that an 1042 LCD-P (Loss of Codegroup Delination - Path) 1043 defect is being experienced. Since this 1044 defect is detected by the PCS and not by 1045 the path layer itself, there is no 1046 corresponding bit in sonetPathCurrentStatus." 1047 REFERENCE 1048 "[IEEE 802.3 Std.], 30.8.1.1.18, aPathStatus." 1049 ::= { etherWisPathCurrentEntry 1 } 1051 etherWisPathCurrentJ1Transmitted OBJECT-TYPE 1052 SYNTAX OCTET STRING (SIZE (16)) 1053 MAX-ACCESS read-write 1054 STATUS current 1055 DESCRIPTION 1056 "This is the 16-octet path trace message that 1057 is transmitted in the J1 byte. The value SHOULD 1058 be '89'h followed by fifteen octets of '00'h 1059 (or some cyclic shift thereof) when the path 1060 trace function is not used, and the implementation 1061 SHOULD use that value (or a cyclic shift thereof) 1062 as a default if no other value has been set." 1063 REFERENCE 1064 "[IEEE 802.3 Std.], 30.8.1.1.23, aJ1ValueTX." 1065 ::= { etherWisPathCurrentEntry 2 } 1067 etherWisPathCurrentJ1Received OBJECT-TYPE 1068 SYNTAX OCTET STRING (SIZE (16)) 1069 MAX-ACCESS read-only 1070 STATUS current 1071 DESCRIPTION 1072 "This is the 16-octet path trace message that 1073 was most recently received in the J1 byte." 1074 REFERENCE 1075 "[IEEE 802.3 Std.], 30.8.1.1.24, aJ1ValueRX." 1076 ::= { etherWisPathCurrentEntry 3 } 1078 -- The Far End Path group 1080 -- These objects provide WIS extensions to 1081 -- the SONET-MIB Far End Path Group. 1083 etherWisFarEndPathCurrentTable OBJECT-TYPE 1084 SYNTAX SEQUENCE OF EtherWisFarEndPathCurrentEntry 1085 MAX-ACCESS not-accessible 1086 STATUS current 1087 DESCRIPTION 1088 "The table for the current far-end state of Ethernet WIS 1089 paths." 1090 ::= { etherWisFarEndPath 1 } 1092 etherWisFarEndPathCurrentEntry OBJECT-TYPE 1093 SYNTAX EtherWisFarEndPathCurrentEntry 1094 MAX-ACCESS not-accessible 1095 STATUS current 1096 DESCRIPTION 1097 "An entry in the etherWisFarEndPathCurrentTable. For each 1098 instance of this object there MUST be a corresponding 1099 instance of sonetFarEndPathCurrentEntry." 1100 INDEX { ifIndex } 1101 ::= { etherWisFarEndPathCurrentTable 1 } 1103 EtherWisFarEndPathCurrentEntry ::= 1104 SEQUENCE { 1105 etherWisFarEndPathCurrentStatus BITS 1106 } 1108 etherWisFarEndPathCurrentStatus OBJECT-TYPE 1109 SYNTAX BITS { 1110 etherWisFarEndPayloadDefect(0), 1111 etherWisFarEndServerDefect(1) 1112 } 1113 MAX-ACCESS read-only 1114 STATUS current 1115 DESCRIPTION 1116 "This variable indicates the current status at the 1117 far end of the path using a bit map that can indicate 1118 multiple defects at once. The bit positions are 1119 assigned as follows: 1121 etherWisFarEndPayloadDefect(0) 1122 A far end payload defect (i.e., far end 1123 PLM-P or LCD-P) is currently being signalled 1124 in G1 bits 5-7. 1126 etherWisFarEndServerDefect(1) 1127 A far end server defect (i.e., far end 1128 LOP-P or AIS-P) is currently being signalled 1129 in G1 bits 5-7. Note: when this bit is set, 1130 sonetPathSTSRDI MUST be set in the corresponding 1131 instance of sonetPathCurrentStatus." 1132 REFERENCE 1133 "[IEEE 802.3 Std.], 30.8.1.1.25, aFarEndPathStatus." 1134 ::= { etherWisFarEndPathCurrentEntry 1 } 1136 -- 1137 -- Conformance Statements 1138 -- 1140 etherWisGroups OBJECT IDENTIFIER ::= { etherWisConformance 1 } 1142 etherWisCompliances OBJECT IDENTIFIER ::= { etherWisConformance 2 } 1144 -- Object Groups 1146 etherWisDeviceGroupBasic OBJECT-GROUP 1147 OBJECTS { 1148 etherWisDeviceTxTestPatternMode, 1149 etherWisDeviceRxTestPatternMode 1150 } 1151 STATUS current 1152 DESCRIPTION 1153 "A collection of objects that support test 1154 features required of all WIS devices." 1155 ::= { etherWisGroups 1 } 1157 etherWisDeviceGroupExtra OBJECT-GROUP 1158 OBJECTS { 1159 etherWisDeviceRxTestPatternErrors 1160 } 1161 STATUS current 1162 DESCRIPTION 1163 "A collection of objects that support 1164 optional WIS device test features." 1165 ::= { etherWisGroups 2 } 1167 etherWisSectionGroup OBJECT-GROUP 1168 OBJECTS { 1169 etherWisSectionCurrentJ0Transmitted, 1170 etherWisSectionCurrentJ0Received 1171 } 1172 STATUS current 1173 DESCRIPTION 1174 "A collection of objects that provide 1175 required information about a WIS section." 1176 ::= { etherWisGroups 3 } 1178 etherWisPathGroup OBJECT-GROUP 1179 OBJECTS { 1180 etherWisPathCurrentStatus, 1181 etherWisPathCurrentJ1Transmitted, 1182 etherWisPathCurrentJ1Received 1183 } 1184 STATUS current 1185 DESCRIPTION 1186 "A collection of objects that provide 1187 required information about a WIS path." 1188 ::= { etherWisGroups 4 } 1190 etherWisFarEndPathGroup OBJECT-GROUP 1191 OBJECTS { 1192 etherWisFarEndPathCurrentStatus 1193 } 1194 STATUS current 1195 DESCRIPTION 1196 "A collection of objects that provide required 1197 information about the far end of a WIS path." 1198 ::= { etherWisGroups 5 } 1200 -- Compliance Statements 1202 etherWisCompliance MODULE-COMPLIANCE 1203 STATUS current 1204 DESCRIPTION 1205 "The compliance statement for this module." 1207 MODULE -- this module 1208 MANDATORY-GROUPS { 1209 etherWisDeviceGroupBasic, 1210 etherWisSectionGroup, 1211 etherWisPathGroup, 1212 etherWisFarEndPathGroup 1213 } 1215 OBJECT etherWisDeviceTxTestPatternMode 1216 SYNTAX INTEGER { 1217 none(1), 1218 squareWave(2), 1219 mixedFrequency(4) 1220 } 1221 DESCRIPTION 1222 "Support for values other than none(1), 1223 squareWave(2), and mixedFrequency(4) 1224 is not required. Furthermore, an 1225 implementation is not required to allow 1226 assignment of a value other than none(1) 1227 if that assignment would result in this 1228 object and etherWisDeviceRxTestPatternMode 1229 having values other than none(1) that are 1230 not the same." 1232 OBJECT etherWisDeviceRxTestPatternMode 1233 SYNTAX INTEGER { 1234 none(1), 1235 mixedFrequency(4) 1236 } 1237 DESCRIPTION 1238 "Support for values other than none(1) 1239 and mixedFrequency(4) is not required. 1240 Furthermore, an implementation is not 1241 required to allow assignment of a value 1242 other than none(1) if that assignment 1243 would result in this object and 1244 etherWisDeviceTxTestPatternMode having 1245 values other than none(1) that are 1246 not the same." 1248 GROUP etherWisDeviceGroupExtra 1249 DESCRIPTION 1250 "Implementation of this group, along with support for 1251 the value prbs31(3) for etherWisDeviceTxTestPatternMode 1252 and etherWisDeviceRxTestPatternMode, is necessary if the 1253 optional PRBS31 test pattern mode is to be supported." 1255 OBJECT etherWisDeviceRxTestPatternErrors 1256 WRITE-SYNTAX Gauge32 ( 0 ) 1257 DESCRIPTION 1258 "An implementation is not required to 1259 allow values other than zero to be 1260 written to this object." 1262 MODULE SONET-MIB 1263 MANDATORY-GROUPS { 1264 sonetMediumStuff2, 1265 sonetSectionStuff2, 1266 sonetLineStuff2, 1267 sonetFarEndLineStuff2, 1268 sonetPathStuff2, 1269 sonetFarEndPathStuff2 1270 } 1272 OBJECT sonetMediumType 1273 SYNTAX INTEGER { 1274 sonet(1) 1275 } 1276 MIN-ACCESS read-only 1277 DESCRIPTION 1278 "Write access is not required, nor is support 1279 for any value other than sonet(1)." 1281 OBJECT sonetMediumLineCoding 1282 SYNTAX INTEGER { 1283 sonetMediumNRZ(4) 1284 } 1285 MIN-ACCESS read-only 1286 DESCRIPTION 1287 "Write access is not required, nor is support 1288 for any value other than sonetMediumNRZ(4)." 1290 OBJECT sonetMediumLineType 1291 MIN-ACCESS read-only 1292 DESCRIPTION 1293 "Write access is not required." 1295 OBJECT sonetMediumCircuitIdentifier 1296 MIN-ACCESS read-only 1297 DESCRIPTION 1298 "Write access is not required." 1300 OBJECT sonetMediumLoopbackConfig 1301 SYNTAX BITS { 1302 sonetNoLoop(0), 1303 sonetFacilityLoop(1) 1304 } 1305 MIN-ACCESS read-only 1306 DESCRIPTION 1307 "Write access is not required, nor is support for values 1308 other than sonetNoLoop(0) and sonetFacilityLoop(1)." 1310 OBJECT sonetSESthresholdSet 1311 MIN-ACCESS read-only 1312 DESCRIPTION 1313 "Write access is not required, and only one 1314 of the enumerated values need be supported." 1316 OBJECT sonetPathCurrentWidth 1317 SYNTAX INTEGER { 1318 sts192cSTM64(6) 1319 } 1320 MIN-ACCESS read-only 1321 DESCRIPTION 1322 "Write access is not required, nor is support 1323 for any value other than sts192cSTM64(6)." 1325 ::= { etherWisCompliances 1 } 1327 END 1329 5. Intellectual Property 1331 The IETF takes no position regarding the validity or scope of any 1332 intellectual property or other rights that might be claimed to 1333 pertain to the implementation or use of the technology described in 1334 this document or the extent to which any license under such rights 1335 might or might not be available; neither does it represent that it 1336 has made any effort to identify any such rights. Information on the 1337 IETF's procedures with respect to rights in standards-track and 1338 standards-related documentation can be found in BCP-11. Copies of 1339 claims of rights made available for publication and any assurances of 1340 licenses to be made available, or the result of an attempt made to 1341 obtain a general license or permission for the use of such 1342 proprietary rights by implementors or users of this specification can 1343 be obtained from the IETF Secretariat. 1345 The IETF invites any interested party to bring to its attention any 1346 copyrights, patents or patent applications, or other proprietary 1347 rights which may cover technology that may be required to practice 1348 this standard. Please address the information to the IETF Executive 1349 Director. 1351 6. Acknowledgments 1353 This document is a product of the IETF Hub MIB and AToM MIB Working 1354 Groups. It builds upon the work of the IEEE P802.3ae 10 Gigabit 1355 Ethernet Task Force. 1357 7. Security Considerations 1359 There are five managed objects defined in this MIB module that have a 1360 MAX-ACCESS clause of read-write: etherWisDeviceTxTestPatternMode, 1361 etherWisDeviceRxTestPatternMode, etherWisDeviceRxTestPatternErrors, 1362 etherWisSectionCurrentJ0Transmitted, and 1363 etherWisPathCurrentJ1Transmitted. Writing to these objects can have 1364 the following potentially disruptive effects on network operation: 1366 o changing the transmit or receive test pattern mode or modifying 1367 the accumulated error count from a PRBS31 pattern test on an 1368 administratively disabled 10GBASE-W interface, which can 1369 interfere with an in-progress pattern test; 1371 o modifying the transmitted section trace and/or path trace 1372 message on an operational 10GBASE-W interface, which can cause 1373 connectivity alarms to be raised at the remote of the link. 1375 The user of this MIB module must therefore be aware that support for 1376 SET operations in a non-secure environment without proper protection 1377 can have a negative effect on network operations. 1379 The readable objects in this MIB module (i.e., those with MAX-ACCESS 1380 other than not-accessible) may be considered sensitive in some 1381 environments since, collectively, they provide information about the 1382 performance of network interfaces and can reveal some aspects of 1383 their configuration. In such environments it is important to control 1384 even GET and NOTIFY access to these objects and possibly even to 1385 encrypt their values when sending them over the network via SNMP. 1387 SNMP versions prior to SNMPv3 did not include adequate security. 1388 Even if the network itself is secure (for example by using IPSec), 1389 even then, there is no control as to who on the secure network is 1390 allowed to access and GET/SET (read/change/create/delete) the objects 1391 in this MIB module. 1393 It is RECOMMENDED that implementers consider the security features as 1394 provided by the SNMPv3 framework (see [RFC3410], section 8), 1395 including full support for the SNMPv3 cryptographic mechanisms (for 1396 authentication and privacy). 1398 Further, deployment of SNMP versions prior to SNMPv3 is NOT 1399 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 1400 enable cryptographic security. It is then a customer/operator 1401 responsibility to ensure that the SNMP entity giving access to an 1402 instance of this MIB module is properly configured to give access to 1403 the objects only to those principals (users) that have legitimate 1404 rights to indeed GET or SET (change/create/delete) them. 1406 8. References 1408 8.1. Normative References 1410 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1411 Requirements Levels", BCP 14, RFC 2119, March 1997. 1413 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1414 Rose, M. and S. Waldbusser, "Structure of Management 1415 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1416 1999. 1418 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1419 Rose, M. and S. Waldbusser, "Textual Conventions for SMIv2", 1420 STD 58, RFC 2579, April 1999. 1422 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1423 Rose, M. and S. Waldbusser, "Conformance Statements for 1424 SMIv2", STD 58, RFC 2580, April 1999. 1426 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 1427 MIB", RFC 2863, June 2000. 1429 [RFC2864] McCloghrie, K. and G. Hanson, "The Inverted Stack Table 1430 Extension to the Interfaces Group MIB", RFC 2864, June 2000. 1432 [SONETng] Tesink, K., "Definitions of Managed Objects for the 1433 SONET/SDH Interface Type", , work in progress. 1436 [T1.231] American National Standard for Telecommunications - Digital 1437 Hierarchy - Layer 1 In-Service Digital Transmission 1438 Performance Monitoring, ANSI T1.231-1997, September 1997. 1440 [ETHERIF] Flick, J., "Definitions of Managed Objects for the 1441 Ethernet-like Interface Types", , work in progress. 1444 [MAU-MIB] Flick, J., "Definitions of Managed Objects for IEEE 802.3 1445 Medium Attachment Units (MAUs)", , work in progress. 1448 [802.3ae] Institute of Electrical and Electronic Engineers, IEEE Std 1449 802.3ae-2002, "IEEE Standard for Carrier Sense Multiple 1450 Access with Collision Detection (CSMA/CD) Access Method and 1451 Physical Layer Specifications - Media Access Control (MAC) 1452 Parameters, Physical Layer and Management Parameters for 10 1453 Gb/s Operation", August 2002. 1455 8.2. Informative References 1457 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 1458 "Introduction and Applicability Statements for Internet- 1459 Standard Management Framework", RFC 3410, December 2002. 1461 9. Contributors 1463 Mike Ayers 1464 1204 Knox Ave. 1465 San Jose, CA 95122 1466 USA 1468 Phone: +1 408 857 6810 1469 EMail: mike.ayers@earthling.net 1471 John Flick 1472 Hewlett-Packard Company 1473 8000 Foothills Blvd. M/S 5557 1474 Roseville, CA 95747-5557 1475 USA 1477 Phone: +1 916 785 4018 1478 Fax: +1 916 785 1199 1479 EMail: johnf@rose.hp.com 1481 Kam Lam 1482 Lucent Technologies 1483 101 Crawfords Corner Road, Room 4C-616A 1484 Holmdel, NJ 07733 1485 USA 1487 Phone: +1 732 949 8338 1488 EMail: hklam@lucent.com 1490 Kerry McDonald 1491 Institute for Applied Supercomputing 1492 California State University San Bernardino 1494 EMail: kerry_mcd@hotmail.com 1495 kmcdonal@csci.csusb.edu 1497 K. C. Norseth 1498 L-3 Communications 1499 640 N. 2200 West. 1500 Salt Lake City, Utah 84116-0850 1501 USA 1503 Phone: +1 801 594 2809 1504 EMail: kenyon.c.norseth@L-3com.com 1505 kcn@norseth.com 1507 Kaj Tesink 1508 Telcordia Technologies 1509 331 Newman Springs Road 1510 P.O. Box 7020 1511 Red Bank, NJ 07701-7020 1512 USA 1514 Phone: +1 732 758 5254 1515 EMail: kaj@research.telcordia.com 1517 10. Editor's Address 1519 C. M. Heard 1520 600 Rainbow Dr. #141 1521 Mountain View, CA 94041-2542 1522 USA 1524 Phone: +1 650 964 8391 1525 EMail: heard@pobox.com 1527 Appendix A: Collection of Performance Data Using WIS MDIO Registers 1529 The purpose of this appendix is to illustrate how the WIS MDIO 1530 registers specified in [802.3ae] subclause 45.2.2 (and more 1531 specifically the subset required by [802.3ae] subclause 50.3.11) can 1532 be used to collect performance data either according to the 1533 conventions adopted by this document or according to the conventions 1534 specified in [802.3ae] Clause 30. 1536 For an agent implementing the SNMP managed objects required by this 1537 document the first step in collecting WIS performance data would be 1538 to poll the 10G WIS status 3 register and the various error count 1539 registers (10G WIS section BIP error count, 10G WIS line BIP errors, 1540 10G WIS far end line BIP errors, 10G WIS path block error count, and 1541 10G WIS far end path block error count) once per second. The 10G WIS 1542 status 3 register bits are all latched until read and so would 1543 indicate whether a given defect occurred any time during the previous 1544 second. The error count registers roll over modulo 2^16 or 2^32, and 1545 so to find the number of errors within the previous second the agent 1546 would need to subtract (modulo 2^16 or 2^32) the current reading from 1547 the reading taken one second ago. Armed with that information, the 1548 agent could determine for any layer whether the one second interval 1549 was an errored second, a severely errored second (that requires 1550 comparison with a threshold unless a defect is present), or a 1551 severely errored frame second. Determining whether a given second is 1552 or is not part of unavailable time requires additional logic; the 1553 most straightforward and accurate method is the delay-line approach 1554 outlined in Appendix A of [SONETng]. With that information available 1555 the agent would be able to determine by how much each current count 1556 should be incremented (including effects of inhibiting). 1557 Implementations that conform to [T1.231] would end each 15-minute 1558 interval on time-of-day clock 1/4 hour boundaries; if the delay-line 1559 approach is used then a time-of-day timestamp would accompany the 1560 one-second statistics. At the end of each interval the current 1561 registers would be pushed onto the history stack and then would be 1562 cleared. The xyxIntervalValidData flags would be set to False(2) if 1563 the number of samples was not between 890 and 910 or, in the case of 1564 far-end counts, if a near-end defect occurred during the just- 1565 completed interval (see [T1.231] Section 9.1.2.2 for details). 1567 An agent implementing the [802.3ae] Clause 30 oWIS objects could also 1568 start by polling the 10G WIS status 3 register and the various error 1569 count registers to find the defects and error counts for the previous 1570 second, and it could determine the number of errors and whether the 1571 second was an errored second, a severely errored second, or a 1572 severely errored frame second in the same manner as above. The rest 1573 of the process would simply be to increment the generalized non- 1574 resetable counters without consideration of any inhibiting rules. 1576 Full Copyright Statement 1578 Copyright (C) The Internet Society (2003). All Rights Reserved. 1580 This document and translations of it may be copied and furnished to 1581 others, and derivative works that comment on or otherwise explain it 1582 or assist in its implementation may be prepared, copied, published 1583 and distributed, in whole or in part, without restriction of any 1584 kind, provided that the above copyright notice and this paragraph are 1585 included on all such copies and derivative works. However, this 1586 document itself may not be modified in any way, such as by removing 1587 the copyright notice or references to the Internet Society or other 1588 Internet organizations, except as needed for the purpose of 1589 developing Internet standards in which case the procedures for 1590 copyrights defined in the Internet Standards process must be 1591 followed, or as required to translate it into languages other than 1592 English. 1594 The limited permissions granted above are perpetual and will not be 1595 revoked by the Internet Society or its successors or assigns. 1597 This document and the information contained herein is provided on an 1598 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 1599 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 1600 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 1601 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 1602 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1604 Revision History 1606 NOTE TO RFC Editor: this section is to be removed prior to 1607 publication as an RFC. 1609 The following changes were made to 1610 to produce : 1612 1.) Section 3.1 was updated as agreed in "WIS MIB compliance 1613 statement issue" e-mail thread, specifically to explain that the 1614 ETHER-WIS compliance statement requires all objects that required 1615 by sonetCompliance2 as well as some that it leaves optional. 1617 2.) In Section 3.5 the paragraph dealing with STS-Path Remote 1618 Defect Indication was updated to indicate that an implementation 1619 of the WIS MIB (not necessarily an arbitrary implementation of the 1620 WIS) has to set the SONET-MIB's RDI status bit when a remote 1621 server defect is detected. 1623 3.) In Section 3.6 the text introducing the table of semantic 1624 differences between IEEE GDMO and SNMP objects was wordsmithed. 1626 4.) In Section 3.7 the mapping between objects in the 1627 etherWisDeviceTable and the station management registers was 1628 updated to reflect the updated MDIO register definitions in 1629 P802.3ae/D4.01 and the corresponding updates to the MIB objects. 1631 5.) In Section 3.8.1 the text was updated to state that the 1632 purpose of the etherWisDeviceTable is to support mandatory and 1633 optional WIS test features. 1635 6.) In Sections 3.8.1, 3.8.2, 3.8.3, and 3.8.4 certain instances 1636 of "SHALL" were changed to "MUST" to improve readability. 1638 7.) The LAST-UPDATED, ORGANIZATION, REVISION, and DESCRIPTION 1639 clauses of the MODULE-IDENTITY invocation were updated. 1641 8.) The lower-case "shall" in the DESCRIPTION clause of each table 1642 entry was changed to an uppercase "MUST", per RFC 2119, because it 1643 describes a requirement of the specification in the draft. 1645 9.) The etherWisDeviceTestPatternType objects was removed, and the 1646 objects etherWisDeviceTxTestPatternMode and 1647 etherWisDeviceRxTestPatternMode were changed from simple 1648 "enable/disable" flags to enumerations that reflect the specific 1649 text pattern mode in which the transmitter or receiver is 1650 operating. A new optional object called 1651 etherWisDeviceRxTestPatternErrors was added to make visible the 1652 error count MDIO register contents when the receiver is operating 1653 in the (optional) PRBS31 test pattern mode added in D4.01. 1655 10.) The SYNTAX of etherWisSectionCurrentJ0Transmitted and 1656 etherWisSectionCurrentJ0Received was changed from INTEGER (0..255) 1657 to OCTET STRING (SIZE (16)) to reflect the change from 1-byte to 1658 16-byte section trace messages in D4.01, and the DESCRIPTION 1659 clauses were rewritten along the lines for those of the 1660 corresponding path trace objects. 1662 11.) In the DESCRIPTION of etherWisPathCurrentJ0Transmitted "path 1663 message" was changes to "path trace message". 1665 12.) etherWisDeviceGroup was split into a mandatory group 1666 etherWisDeviceGroupBasic and an optional group 1667 etherWisDeviceGroupExtra. 1669 13.) The compliance name was changed from 1670 etherWisCurrentCompliance to etherWisCompliance. 1672 14.) OBJECT clauses were added to specify required values for 1673 etherWisDeviceTxTestPatternMode and 1674 etherWisDeviceRxTestPatternMode. 1676 15.) A GROUP clause was added to state that 1677 etherWisDeviceGroupExtra needs to be implemented in order to 1678 support the PRBS31 test pattern mode. The DESCRIPTION clause 1679 points out that the prbs31 enumeration is needed for 1680 etherWisDeviceTxTestPatternMode/etherWisDeviceRxTestPatternMode. 1682 16.) References [SONETng] and [P802.3ae] were updated to draft- 1683 ietf-atommib-rfc2558bis-00.txt and P802.3ae/D4.01, respectively. 1685 The following changes were made to 1686 to produce : 1688 1.) The page formatting was changed to match that used in recent 1689 RFCs. 1691 2.) Heading numbering and bracketed references were removed from 1692 the abstract, and "SONET MIB" was expanded to "SONET/SDH Interface 1693 MIB". 1695 3.) RFC 2119 terminology conventions were moved from the abstract 1696 into a separate numbered "Conventions" section and were 1697 wordsmithed to match the style of recent RFCs. 1699 4.) Each occurrence of "SONET MIB" in Section 3, "Overview", was 1700 expanded to "SONET/SDH Interface MIB". 1702 5.) Each occurrence of "MAU-MIB" in Section 3, "Overview", was 1703 expanded to "802.3 MAU MIB". 1705 6.) Each occurrence of "SONET MIB" in Sections 3.1, 3.8.1, 3.8.2, 1706 3.8.3, and 3.8.4 was changed to "SONET-MIB" (this matches the 1707 usage elsewhere, specifically Sections 3.2 and 3.3). 1709 7.) All occurrences of "[P802.3ae] subclause 50.3.10" were updated 1710 to "[P802.3ae] subclause 50.3.11" in order to match the subclause 1711 numbering in P802.3ae/D4.2 (affected sections are 3.1, 3.6, 3.7, 1712 and Appendix A). 1714 8.) "Ethernet-like Interfaces MIB" was changed to "Ethernet-like 1715 Interface MIB" in Section 3.2 in order to match the usage in the 1716 abstract. 1718 9.) "mauModIfCompl2" was updated to "mauModIfCompl3" in Section 1719 3.3 in order to match . 1721 10.) An unnecessary heading was removed the table in Section 3.6 1722 that compares the semantics of IEEE threshold and counter objects 1723 with those of the corresponding objects imported from the SONET- 1724 MIB. 1726 11.) The text at the end of Section 3.6 was wordsmithed to remove 1727 unnecessary verbiage. 1729 12.) The MDIO register name spellings in Section 3.7, Section 4, 1730 and Appendix A were updated to match those in P802.3ae/D4.2 1731 subclause 45.2.2. 1733 13.) A missing comma was added to the 1734 etherWisDeviceRxTestPatternErrors REFERENCE clause. 1736 14.) DESCRIPTION clauses of etherWisSectionCurrentJ0Transmitted 1737 and etherWisPathCurrentJ1Transmitted were updated to state that 1738 the default value should be '89'h followed by 16 octets of '00'h, 1739 rather than 16 octets of '00'h followed by '89'h (this matches the 1740 resolution in P802.3ae/D4.2 of a byte ordering inconsistency). 1742 15.) The MAX-ACCESS clauses of etherWisPathCurrentStatus and 1743 etherWisPathCurrentStatus were changed from 'read-write' to 1745 16.) In Section 6, "Security Considerations", all read-write 1746 objects have been explicitly listed and mention of read-create 1747 objects has been removed. 1749 17.) References [ETHERIF], [MAU-MIB], and [P802.3ae] were updated 1750 to , , and P802.3ae/D4.2, respectively. 1753 18.) Normative and informative references were moved into separate 1754 sub-sections. 1756 19.) A "To-Do List" section was added. 1758 The following changes were made to 1759 to produce : 1761 1.) "tx" and "rx" were spelled out in the MDIO register names in 1762 Section 3.7 in order to match the usage in P802.3ae/D4.3 and 1763 P802.3ae/D5.0. 1765 2.) References [IEEE 802.3 Std] in the MIB module and [P802.3ae] 1766 in the text were updated to point to P802.3ae/D5.0. 1768 3.) Author contact information was updated. 1770 The following changes were made to 1771 to produce : 1773 1.) Gauge32 was added to the IMPORTS list. It was not being 1774 imported from SNMPv2-SMI as required by RFC 2578. 1776 2.) Enum values for etherWisDeviceTxTestPatternMode and 1777 etherWisDeviceTxTestPatternMode now start at 1 instead of 0, as 1778 recommended by RFC 2578. 1780 3.) The OBJECT clauses for etherWisDeviceTxTestPatternMode and 1781 etherWisDeviceRxTestPatternMode now state that an implementation 1782 does not have to allow value assignments that the Clause 45 MDIO 1783 registers can't support. 1785 4.) An OBJECT clause for etherWisDeviceRxTestPatternErrors was 1786 added to specify that the WRITE-SYNTAX is Gauge32(0). 1788 5.) A paragraph warning that some environments may consider the 1789 information in read-only objects to be sensitive was added to the 1790 Security Considerations section, and the entire section was 1791 updated to conform to the latest template posted to the 1792 mibs@ops.ietf.org mailing list. 1794 6.) The acronyms in Section 3 were expanded on first use. 1796 7.) All occurrences of "ifAdminState" were changed to 1797 "ifAdminStatus". 1799 8.) The DESCRIPTION clauses for etherWisPathCurrentJ1Transmitted 1800 and etherWisSectionCurrentJ0Transmitted were changed to use 1801 "transmitted" in place of "to be transmitted". 1803 9.) All remaining instances of "SHALL" were changed to "MUST" in 1804 Sections 3.8.1, 3.8.2, 3.8.3, and 3.8.4 in order to improve 1805 readability. 1807 10.) The reference tag [P802.3ae] was replaced with [802.3ae], and 1808 the corresponding normative reference was updated to point to IEEE 1809 Std 802.3ae-2002, published 30 Aug 2002. The reference [IEEE 1810 802.3 Std] in the MIB module was similarly updated. 1812 11.) RFC 2119 was moved from the informative reference list to the 1813 normative reference list, in accordance with current IESG and RFC 1814 Editor policy. 1816 12.) The MIB boilerplate in Section 2 and the SMI/SNMP-related 1817 references were updated to conform to the latest template posted 1818 to the mibs@ops.ietf.org mailing list. 1820 13.) The DESCRIPTION clause of the MODULE-IDENTITY invocation was 1821 updated to include the required copyright statement. 1823 14.) The dates in the LAST-UPDATED and REVISION clauses of the 1824 MODULE-IDENTITY invocation were changed to the current date. 1826 15.) The document pagination was changed to match that expected 1827 upon publication as an RFC. 1829 The following changes were made to 1830 to produce : 1832 1.) Names of WIS MIB design team members other than the editor 1833 were removed from author list on front page. They now appear in 1834 the Contributors section with (updated) contact information. 1836 2.) Reference tag [2570bis] was replaced with [RFC3410], and the 1837 corresponding informative reference was updated to point to RFC 1838 3410. 1840 3.) Working group mailing list information was added to the 1841 CONTACT-INFO clause of the MODULE-IDENTITY invocation. 1843 4.) The dates in the LAST-UPDATED and REVISION clauses of the 1844 MODULE-IDENTITY invocation were changed to the current date. 1846 5.) The Intellectual Property section was relocated. 1848 6.) The working group names in the Acknowlegments section were 1849 corrected. 1851 7.) The part of the Security Considerations section dealing with 1852 read-only objects was wordsmithed, and some typos in the last part 1853 were fixed. 1855 8.) References [SONETng], [ETHERIF], and [MAU-MIB] were updated to 1856 point to , , and , respectively. 1860 9.) All references to multi-author RFCs were updated to conform to 1861 the style used in recently published RFCs. 1863 10.) The "To-Do List" was replaced with a "NOTES TO RFC Editor" 1864 section. 1866 ************************************************************ 1867 * NOTES TO RFC Editor (to be removed prior to publication) * 1868 * * 1869 * 1.) The normative references [SONETng], [ETHERIF], and * 1870 * [MAU-MIB] must be updated to point to the appropriate * 1871 * RFCs when the respective Internet Drafts are published, * 1872 * and all occurrences of the reference tags must be * 1873 * changed to [RFCnnnn] where nnnn is the assigned RFC * 1874 * number. * 1875 * * 1876 * 2.) Please replace all occurrences of "yyyy" in the * 1877 * DESCRIPTION clause of the MODULE-IDENTITY invocation * 1878 * in Section 4 with the RFC number assigned to this * 1879 * specification and remove the accompanying notes. * 1880 * * 1881 * 3.) Please replace "XXX" in the MODULE-IDENTITY value * 1882 * with an IANA-assigned value under the 'transmission' * 1883 * subtree and remove the accompanying note. * 1884 * * 1885 * 4.) Please remove the "Revision History" section. * 1886 * * 1887 ************************************************************