idnits 2.17.1 draft-ietf-hubmib-wis-mib-03.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. ** 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.) == 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 1794 has weird spacing: '... Use of ...' == Line 1798 has weird spacing: '... Use of ifTab...' == Line 1802 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 (April 14, 2002) is 8047 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: 'RFCnnnn' is mentioned on line 1781, but not defined ** Obsolete normative reference: RFC 2571 (Obsoleted by RFC 3411) ** 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 2558 (ref. 'SONETng') (Obsoleted by RFC 3592) -- Possible downref: Non-RFC (?) normative reference: ref. 'ETHERIF' -- Possible downref: Non-RFC (?) normative reference: ref. 'MAU-MIB' -- Obsolete informational reference (is this intentional?): RFC 2570 (Obsoleted by RFC 3410) Summary: 12 errors (**), 0 flaws (~~), 8 warnings (==), 5 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 Consultant 14 Kaj Tesink 15 Telcordia Technologies 16 April 14, 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 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). 52 The MIB module defined in this memo is an extension of the SONET/SDH 53 Interface MIB and is implemented in conjunction with it and with the 54 Ethernet-like Interface MIB, the 802.3 Medium Attachment Unit MIB, 55 the Interfaces Group MIB, and the Inverted Stack Table MIB. 57 1. Conventions 59 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 60 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 61 "OPTIONAL", when they appear in this document, are to be interpreted 62 as described in RFC 2119 [RFC2119]. 64 2. The SNMP Management Framework 66 The SNMP Management Framework presently consists of five major 67 components: 69 o An overall architecture, described in RFC 2571 [RFC2571]. 71 o Mechanisms for describing and naming objects and events for the 72 purpose of management. The first version of this Structure of 73 Management Information (SMI) is called SMIv1 and described in 74 STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 75 1215 [RFC1215]. The second version, called SMIv2, is described 76 in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and 77 STD 58, RFC 2580 [RFC2580]. 79 o Message protocols for transferring management information. The 80 first version of the SNMP message protocol is called SNMPv1 and 81 described in STD 15, RFC 1157 [RFC1157]. A second version of 82 the SNMP message protocol, which is not an Internet standards 83 track protocol, is called SNMPv2c and described in RFC 1901 84 [RFC1901] and RFC 1906 [RFC1906]. The third version of the 85 message protocol is called SNMPv3 and described in RFC 1906 86 [RFC1906], RFC 2572 [RFC2572] and RFC 2574 [RFC2574]. 88 o Protocol operations for accessing management information. The 89 first set of protocol operations and associated PDU formats is 90 described in STD 15, RFC 1157 [RFC1157]. A second set of 91 protocol operations and associated PDU formats is described in 92 RFC 1905 [RFC1905]. 94 o A set of fundamental applications described in RFC 2573 95 [RFC2573] and the view-based access control mechanism described 96 in RFC 2575 [RFC2575]. 98 A more detailed introduction to the current SNMP Management Framework 99 can be found in RFC 2570 [RFC2570]. 101 Managed objects are accessed via a virtual information store, termed 102 the Management Information Base or MIB. Objects in the MIB are 103 defined using the mechanisms defined in the SMI. 105 This memo specifies a MIB module that is compliant to the SMIv2. A 106 MIB conforming to the SMIv1 can be produced through the appropriate 107 translations. The resulting translated MIB must be semantically 108 equivalent, except where objects or events are omitted because no 109 translation is possible (use of Counter64). Some machine readable 110 information in SMIv2 will be converted into textual descriptions in 111 SMIv1 during the translation process. However, this loss of machine 112 readable information is not considered to change the semantics of the 113 MIB. 115 3. Overview 117 The objects defined in this memo are used in conjunction with objects 118 defined in the Interfaces Group MIB [RFC2863], the SONET/SDH 119 Interface MIB [SONETng], and the 802.3 MAU MIB [MAU-MIB] to manage 120 the WAN Interface Sublayer (WIS) defined in [P802.3ae]. The WIS 121 contains functions to perform OC-192c/VC-4-64c framing and 122 scrambling. It resides between the PCS and PMA sublayers within a 123 10GBASE-W 10 Gb/s WAN-compatible PHY and may be used in conjunction 124 with any of the PCS, PMA, and PMD sublayers that are defined in 125 [P802.3ae] for 10GBASE-W PHYs. Three types of 10GBASE-W PHYs are 126 defined, distinguished by the type of optics employed: 10GBASE-SW, 127 10GBASE-LW, and 10GBASE-EW. The objects defined in this memo may be 128 used to manage an Ethernet interface employing any type of 10GBASE-W 129 PHY. They do not apply to any other kind of interface. In 130 particular, they do not apply to so-called Ethernet Line Terminating 131 Equipment (ELTE) residing within a SONET network element that uses 132 the 10GBASE-W PMA/PMD sublayers but otherwise acts as SONET Line 133 Terminating Equipment (LTE). 135 The objects presented here -- along with those incorporated by 136 reference from the Interfaces Group MIB, the SONET/SDH Interface MIB, 137 and the 802.3 MAU MIB -- are intended to provide exact 138 representations of the mandatory attributes in the oWIS managed 139 object class (i.e., the members of the pWISBasic package) defined in 140 Clause 30 and Annex 30A of [P802.3ae]. They are also intended to 141 provide approximate representations of the optional attributes (i.e., 142 the members of the pWISOptional package). Some objects with no 143 analogues in oWIS are defined to support WIS testing features 144 required by Clause 50 of [P802.3ae]. 146 3.1. Relationship to the SONET/SDH Interface MIB 148 Since the Ethernet WAN Interface Sublayer was designed to be SONET- 149 compatible, information similar to that provided by most of the 150 members of the oWIS managed object class is available from objects 151 defined in the SONET-MIB [SONETng]. Thus, the MIB module defined in 152 this memo is a sparse augmentation of the SONET-MIB -- in other 153 words, every table defined here is an extension of some table in the 154 SONET-MIB -- and its compliance statement REQUIRES that an agent 155 implementing the objects defined in this memo also implement the 156 relevant SONET-MIB objects. That includes all objects required by 157 sonetCompliance2 as well as some that it leaves optional. 159 It should be noted that some of the objects incorporated by reference 160 from the SONET-MIB -- specifically, the threshold objects and 161 interval counter objects -- provide only approximate representations 162 of the corresponding oWIS attributes, as detailed in Section 3.6. An 163 alternative approach would have been to define new objects to exactly 164 match the oWIS definitions. That approach was rejected because the 165 SONET-MIB objects are already used in deployed systems to manage the 166 SONET sublayers of ATM over SONET and PPP over SONET interfaces, and 167 it was deemed undesirable to use a different scheme to manage the 168 SONET sublayers of 10 Gb/s WAN-compatible Ethernet interfaces. Note 169 that the approach adopted by this memo requires no hardware support 170 beyond that mandated by [P802.3ae] subclause 50.3.11. 172 3.2. Relationship to the Ethernet-like Interface MIB 174 An interface which includes the Ethernet WIS is, by definition, an 175 Ethernet-like interface, and an agent implementing the objects 176 defined in this memo MUST implement the objects required by the 177 dot3Compliance2 compliance statement in the EtherLike-MIB. 179 3.3. Relationship to the 802.3 MAU MIB 181 Support for the mauModIfCompl3 compliance statement of the MAU-MIB 182 [MAU-MIB] is REQUIRED for all Ethernet-like interfaces. The MAU-MIB 183 is needed in order to allow applications to control and/or determine 184 the media type in use. That is important for devices than can 185 support both the 10GBASE-R 10 Gb/s LAN format (which does not include 186 the WIS) and the 10GBASE-W 10 Gb/s WAN format (which does include the 187 WIS). The MAU-MIB also provides the means to put a device in standby 188 mode or to reset it; the latter may be used to re-initialize the 189 WIS. 191 3.4. Use of the ifTable 193 This section specifies how the ifTable, as defined in [RFC2863], is 194 used for the Ethernet WIS application. 196 3.4.1. Layering Model 198 Ethernet interfaces that employ the WIS are layered as defined in 199 [P802.3ae]. The corresponding use of the ifTable [RFC2863] is shown 200 in the figure below. 202 _____________________________ _ 203 | LLC Layer | | 204 +-----------------------------+ | 205 | MAC Layer | | 206 +-----------------------------+ > 1 ifEntry 207 | Reconciliation Sublayer | | ifType: ethernetCsmacd(6) 208 +-----------------------------+ | 209 | Physical Coding Sublayer | | 210 +-----------------------------+ + 211 | Path Layer | > 1 ifEntry 212 +-----------------------------+ + ifType: sonetPath(50) 213 | Line Layer | | 214 +-----------------------------+ | 215 | Section Layer | > 1 ifEntry 216 +-----------------------------+ | ifType: sonet(39) 217 | Physical Medium Layer | | 218 ----------------------------- - 220 Figure 1 - Use of ifTable for an Ethernet WIS port 222 The exact configuration and multiplexing of the layers is maintained 223 in the ifStackTable [RFC2863] and in the ifInvStackTable [RFC2864]. 225 3.4.2. Use of ifTable for LLC Layer/MAC Layer/Reconciliation 226 Sublayer/Physical Coding Sublayer 228 The ifTable MUST be used as specified in [ETHERIF] and [MAU-MIB] for 229 the LLC Layer/MAC Layer/Reconciliation Sublayer/Physical Coding 230 Sublayer. 232 3.4.3. Use of ifTable for SONET/SDH Path Layer 234 The ifTable MUST be used as specified in [SONETng] for the SONET/SDH 235 Path Layer. The value of ifHighSpeed is set to 9585. ifSpeed 236 reports a value of 4294967295. 238 3.4.4. Use of ifTable for SONET/SDH Medium/Section/Line Layer 240 The ifTable MUST be used as specified in [SONETng] for the SONET/SDH 241 Medium/Section/Line Layer. The value of ifHighSpeed is set to 9953. 242 ifSpeed reports a value of 4294967295. 244 3.5. SONET/SDH Terminology 246 The SONET/SDH terminology used in [P802.3ae] is mostly the same as in 247 [SONETng], but there are a few differences. In those cases the 248 definitions in [P802.3ae] take precedence. The specific differences 249 are as follows. 251 Unequipped 252 This defect is not defined by [P802.3ae]. An implementation that 253 supports it SHOULD report it by setting the sonetPathUnequipped 254 bit in the appropriate instance of sonetPathCurrentStatus. 256 Signal Label Mismatch 257 This defect is called Payload Label Mismatch (PLM) in [P802.3ae]. 258 It is reported by setting both the sonetPathSignalLabelMismatch 259 bit in the appropriate instance of sonetPathCurrentStatus 260 (defined in [SONETng]) and the etherWisPathPLM bit in the 261 corresponding instance of etherWisPathCurrentStatus (defined 262 below). 264 Loss of Codegroup Delineation 265 [P802.3ae] defines Loss of Codegroup Delineation (LCD) as 266 occurring when the Physical Coding Sublayer is unable to locate 267 64B/66B code group boundaries. There is no analogous defect 268 defined in [SONETng]. It is reported by setting the 269 etherWisPathLCD bit in the appropriate instance of the object 270 etherWisPathCurrentStatus defined below. 272 STS-Path Remote Defect Indication 273 [P802.3ae] mandates the use of ERDI-P (Enhanced Remote Defect 274 Indication - Path) defined in [T1.231] to signal remote server 275 defects (triggered by path AIS or path LOP) and remote payload 276 defects (triggered by Payload Label Mismatch or Loss of Codegroup 277 Delineation). [SONETng] defines the one-bit RDI-P (Remote Defect 278 Indication - Path), which signals remote server detects (i.e., 279 path AIS and path LOP) only. An implementation of the MIB module 280 defined in this memo MUST set the sonetPathSTSRDI bit in the 281 appropriate instance of sonetPathCurrentStatus when it receives 282 an ERDI-P server defect indication from the remote end. Both 283 ERDI-P payload defects and ERDI-P server defects are reported in 284 the object etherWisFarEndPathCurrentStatus defined below. 286 Path Coding Violations 287 In [P802.3ae] the path layer CV count is based on block errors 288 and not BIP-8 errors, i.e., it is incremented only once for each 289 B3 byte that indicates incorrect parity, regardless of the number 290 of bits in error. Note that Section 8.4.5.1 of [T1.231] allows 291 either path BIP-8 errors or path block errors to be used for the 292 path layer error count. 294 3.6. Mapping of IEEE 802.3 Managed Objects 296 This section contains the mapping between oWIS managed objects 297 defined in [P802.3ae] and managed objects defined in this document 298 and in associated MIB modules, i.e., the IF-MIB [RFC2863], the 299 SONET-MIB [SONETng], and the MAU-MIB [MAU-MIB]. 301 IEEE 802.3 Managed Object Corresponding SNMP Object 303 oWIS - pWISBasic package 304 aWISID IF-MIB - ifIndex 305 aSectionStatus SONET-MIB - sonetSectionCurrentStatus 306 aLineStatus SONET-MIB - sonetLineCurrentStatus 307 aPathStatus etherWisPathCurrentStatus 308 aFarEndPathStatus etherWisFarEndPathCurrentStatus 310 oWIS - pWISOptional package 311 aSectionSESThreshold SONET-MIB - sonetSESthresholdSet 312 aSectionSESs SONET-MIB - sonetSectionCurrentSESs + 313 sonetSectionIntervalSESs 314 aSectionESs SONET-MIB - sonetSectionCurrentESs + 315 sonetSectionIntervalESs 316 aSectionSEFSs SONET-MIB - sonetSectionCurrentSEFSs + 317 sonetSectionIntervalSEFSs 318 aSectionCVs SONET-MIB - sonetSectionCurrentCVs + 319 sonetSectionIntervalCVs 320 aJ0ValueTX etherWisSectionCurrentJ0Transmitted 321 aJ0ValueRX etherWisSectionCurrentJ0Received 322 aLineSESThreshold SONET-MIB - sonetSESthresholdSet 323 aLineSESs SONET-MIB - sonetLineCurrentSESs + 324 sonetLineIntervalSESs 325 aLineESs SONET-MIB - sonetLineCurrentESs + 326 sonetLineIntervalESs 327 aLineCVs SONET-MIB - sonetLineCurrentCVs + 328 sonetLineIntervalCVs 329 aFarEndLineSESs SONET-MIB - sonetFarEndLineCurrentSESs + 330 sonetFarEndLineIntervalSESs 331 aFarEndLineESs SONET-MIB - sonetFarEndLineCurrentESs + 332 sonetFarEndLineIntervalESs 333 aFarEndLineCVs SONET-MIB - sonetFarEndLineCurrentCVs + 334 sonetFarEndLineIntervalCVs 335 aPathSESThreshold SONET-MIB - sonetSESthresholdSet 336 aPathSESs SONET-MIB - sonetPathCurrentSESs + 337 sonetPathIntervalSESs 338 aPathESs SONET-MIB - sonetPathCurrentESs + 339 sonetPathIntervalESs 340 aPathCVs SONET-MIB - sonetPathCurrentCVs + 341 sonetPathIntervalCVs 342 aJ1ValueTX etherWisPathCurrentJ1Transmitted 343 aJ1ValueRX etherWisPathCurrentJ1Received 344 aFarEndPathSESs SONET-MIB - sonetFarEndPathCurrentSESs + 345 sonetFarEndPathIntervalSESs 346 aFarEndPathESs SONET-MIB - sonetFarEndPathCurrentESs + 347 sonetFarEndPathIntervalESs 348 aFarEndPathCVs SONET-MIB - sonetFarEndPathCurrentCVs + 349 sonetFarEndPathIntervalCVs 351 It should be noted that the threshold and counter objects imported 352 from the SONET-MIB are not completely equivalent to the corresponding 353 IEEE 802.3 objects. The specific differences are as follows: 355 IEEE 802.3 Managed Object How Corresponding SNMP Object Differs 357 aSectionSESThreshold This object is defined in [P802.3ae] 358 as an integer with one instance per 359 interface. sonetSESthresholdSet 360 is an enumerated value that has one 361 instance per network element; it 362 controls the thresholds for all layers 363 simultaneously and allows only certain 364 discrete values to be selected. 365 aSectionSESs This object is defined in [P802.3ae] as 366 a generalized nonresetable counter. 367 The objects sonetSectionCurrentSESs and 368 sonetSectionIntervalSESs are 15-minute 369 interval counters. 370 aSectionESs This object is defined as a generalized 371 nonresetable counter in [P802.3ae]. 372 The objects sonetSectionCurrentESs and 373 sonetSectionIntervalESs are 15-minute 374 interval counters. 375 aSectionSEFSs This object is defined as a generalized 376 nonresetable counter in [P802.3ae]. 377 The objects sonetSectionCurrentSEFSs and 378 sonetSectionIntervalSEFSs are 15-minute 379 interval counters. 380 aSectionCVs This object is defined as a generalized 381 nonresetable counter in [P802.3ae], and 382 it is not subject to inhibiting. The 383 objects sonetSectionCurrentCVs and 384 sonetSectionIntervalCVs are 15-minute 385 interval counters, and they are 386 inhibited (not incremented) during 387 one-second intervals that qualify as 388 severely errored seconds. 389 aLineSESThreshold This object is defined in [P802.3ae] 390 as an integer with one instance per 391 interface. sonetSESthresholdSet 392 is an enumerated value that has one 393 instance per network element; it 394 controls the thresholds for all layers 395 simultaneously and allows only certain 396 discrete values to be selected. 397 aLineSESs This object is defined as a generalized 398 nonresetable counter in [P802.3ae], and 399 it is not subject to inhibiting. The 400 objects sonetLineCurrentSESs and 401 sonetLineIntervalSESs are 15-minute 402 interval counters, and they are 403 inhibited (not incremented) during 404 one-second intervals that qualify as 405 unavailable seconds. 406 aLineESs This object is defined as a generalized 407 nonresetable counter in [P802.3ae], and 408 it is not subject to inhibiting. The 409 objects sonetLineCurrentESs and 410 sonetLineIntervalESs are 15-minute 411 interval counters, and they are 412 inhibited (not incremented) during 413 one-second intervals that qualify as 414 unavailable seconds. 415 aLineCVs This object is defined as a generalized 416 nonresetable counter in [P802.3ae], and 417 it is not subject to inhibiting. The 418 objects sonetLineCurrentCVs and 419 sonetLineIntervalCVs are 15-minute 420 interval counters, and they are 421 inhibited (not incremented) during 422 one-second intervals that qualify 423 either as severely errored seconds 424 or as unavailable seconds. 425 aFarEndLineSESs This object is defined as a generalized 426 nonresetable counter in [P802.3ae], and 427 it is not subject to inhibiting. The 428 objects sonetFarEndLineCurrentSESs and 429 sonetFarEndLineIntervalSESs are 430 15-minute interval counters, and they 431 are inhibited (not incremented) during 432 one-second intervals that qualify as 433 unavailable seconds. 434 aFarEndLineESs This object is defined as a generalized 435 nonresetable counter in [P802.3ae], and 436 it is not subject to inhibiting. The 437 objects sonetFarEndLineCurrentESs and 438 sonetFarEndLineIntervalESs are 15-minute 439 interval counters, and they are 440 inhibited (not incremented) during 441 one-second intervals that qualify as 442 unavailable seconds. 443 aFarEndLineCVs This object is defined as a generalized 444 nonresetable counter in [P802.3ae], and 445 it is not subject to inhibiting. The 446 objects sonetFarEndLineCurrentCVs and 447 sonetFarEndLineIntervalCVs are 15-minute 448 interval counters, and they are 449 inhibited (not incremented) during 450 one-second intervals that qualify 451 either as severely errored seconds 452 or as unavailable seconds. 453 aPathSESThreshold This object is defined in [P802.3ae] 454 as an integer with one instance per 455 interface. sonetSESthresholdSet 456 is an enumerated value that has one 457 instance per network element; it 458 controls the thresholds for all layers 459 simultaneously and allows only certain 460 discrete values to be selected. 461 aPathSESs This object is defined as a generalized 462 nonresetable counter in [P802.3ae], and 463 it is not subject to inhibiting. The 464 objects sonetPathCurrentSESs and 465 sonetPathIntervalSESs are 15-minute 466 interval counters, and they are 467 inhibited (not incremented) during 468 one-second intervals that qualify as 469 unavailable seconds. In addition, 470 [P802.3ae] includes PLM-P and LCD-P 471 defects in the criteria for declaring 472 path layer severely errored seconds, 473 while [SONETng] does not. 474 aPathESs This object is defined as a generalized 475 nonresetable counter in [P802.3ae], and 476 it is not subject to inhibiting. The 477 objects sonetPathCurrentESs and 478 sonetPathIntervalESs are 15-minute 479 interval counters, and they are 480 inhibited (not incremented) during 481 one-second intervals that qualify as 482 unavailable seconds. In addition, 483 [P802.3ae] includes PLM-P and LCD-P 484 defects in the criteria for declaring 485 path layer errored seconds, while 486 [SONETng] does not. 487 aPathCVs This object is defined as a generalized 488 nonresetable counter in [P802.3ae], and 489 it is not subject to inhibiting. The 490 objects sonetPathCurrentCVs and 491 sonetPathIntervalCVs are 15-minute 492 interval counters, and they are 493 inhibited (not incremented) during 494 one-second intervals that qualify 495 either as severely errored seconds 496 or as unavailable seconds. 497 aFarEndPathSESs This object is defined as a generalized 498 nonresetable counter in [P802.3ae], and 499 it is not subject to inhibiting. The 500 objects sonetFarEndPathCurrentSESs and 501 sonetFarEndPathIntervalSESs are 502 15-minute interval counters, and they 503 are inhibited (not incremented) during 504 one-second intervals that qualify as 505 unavailable seconds. In addition, 506 [P802.3ae] includes far-end PLM-P and 507 LCD-P defects in the criteria for 508 declaring far-end path layer severely 509 errored seconds, while [SONETng] does 510 not. 511 aFarEndPathESs This object is defined as a generalized 512 nonresetable counter in [P802.3ae], and 513 it is not subject to inhibiting. The 514 objects sonetFarEndPathCurrentESs and 515 sonetFarEndPathIntervalESs are 15-minute 516 interval counters, and they are 517 inhibited (not incremented) during 518 one-second intervals that qualify as 519 unavailable seconds. In addition, 520 [P802.3ae] includes far-end PLM-P and 521 LCD-P defects in the criteria for 522 declaring far-end path layer errored 523 seconds, while [SONETng] does not. 524 aFarEndPathCVs This object is defined as a generalized 525 nonresetable counter in [P802.3ae], and 526 it is not subject to inhibiting. The 527 objects sonetFarEndPathCurrentCVs and 528 sonetFarEndPathIntervalCVs are 15-minute 529 interval counters, and they are 530 inhibited (not incremented) during 531 one-second intervals that qualify 532 either as severely errored seconds 533 or as unavailable seconds. 535 Note: despite the semantic differences between the threshold objects 536 and counter objects imported from the SONET-MIB and the corresponding 537 IEEE 802.3 objects, the hardware support mandated by [P802.3ae] 538 subclause 50.3.11 suffices for both. See Appendix A for details. 540 3.7. Mapping of SNMP Objects to WIS Station Management Registers 542 Some of the objects defined in this memo or incorporated by reference 543 from the SONET-MIB [SONETng] or the MAU-MIB [MAU-MIB] require WIS- 544 specific hardware support. [P802.3ae] subclause 50.3.11 specifies 545 WIS management interface requirements, including a required subset of 546 the WIS MDIO (Management Data Input/Output) registers defined in 547 [P802.3ae] subclause 45.2.2. The table below provides a cross- 548 reference between those managed objects and the WIS MDIO registers 549 from the subset in [P802.3ae] subclause 50.3.11 required to support 550 them. Note that the MDIO interface is optional; however, if it is 551 not implemented, then the capabilities of the required register 552 subset must be provided by other means. 554 SNMP Object WIS MDIO Register(s) 556 ETHER-WIS - etherWisDeviceTxTestPatternMode 10G WIS control 2 557 ETHER-WIS - etherWisDeviceRxTestPatternMode 10G WIS control 2 558 ETHER-WIS - etherWisDeviceRxTestPatternErrors 10G WIS test pattern 559 error counter 561 SONET-MIB - sonetMediumType none required 562 SONET-MIB - sonetMediumTimeElapsed none required 563 SONET-MIB - sonetMediumValidIntervals none required 564 SONET-MIB - sonetMediumLineCoding none required 565 SONET-MIB - sonetMediumLineType none required 566 SONET-MIB - sonetMediumCircuitIdentifier none required 567 SONET-MIB - sonetMediumInvalidIntervals none required 568 SONET-MIB - sonetMediumLoopbackConfig none required 569 SONET-MIB - sonetSESthresholdSet none required 571 ETHER-WIS - etherWisSectionCurrentJ0Transmitted 10G WIS J0 tx 572 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 584 SONET-MIB - sonetLineCurrentStatus 10G WIS status 3 585 SONET-MIB - sonetLineCurrentESs \ 586 SONET-MIB - sonetLineCurrentSESs \ 587 SONET-MIB - sonetLineCurrentCVs | 10G WIS status 3 588 SONET-MIB - sonetLineCurrentUASs | + 589 SONET-MIB - sonetLineIntervalESs | 10G WIS line 590 SONET-MIB - sonetLineIntervalSESs | BIP errors 591 SONET-MIB - sonetLineIntervalCVs / 592 SONET-MIB - sonetLineIntervalUASs / 593 SONET-MIB - sonetLineIntervalValidData none required 595 SONET-MIB - sonetFarEndLineCurrentESs \ 596 SONET-MIB - sonetFarEndLineCurrentSESs \ 597 SONET-MIB - sonetFarEndLineCurrentCVs | 10G WIS status 3 598 SONET-MIB - sonetFarEndLineCurrentUASs | + 599 SONET-MIB - sonetFarEndLineIntervalESs | 10G WIS far end 600 SONET-MIB - sonetFarEndLineIntervalSESs | line BIP errors 601 SONET-MIB - sonetFarEndLineIntervalCVs / 602 SONET-MIB - sonetFarEndLineIntervalUASs / 603 SONET-MIB - sonetFarEndLineIntervalValidData 10G WIS status 3 605 ETHER-WIS - etherWisPathCurrentStatus 10G WIS status 3 606 ETHER-WIS - etherWisPathCurrentJ1Transmitted 10G WIS J1 tx 607 ETHER-WIS - etherWisPathCurrentJ1Received 10G WIS J1 rx 609 SONET-MIB - sonetPathCurrentWidth none required 610 SONET-MIB - sonetPathCurrentStatus 10G WIS status 3 611 SONET-MIB - sonetPathCurrentESs \ 612 SONET-MIB - sonetPathCurrentSESs \ 613 SONET-MIB - sonetPathCurrentCVs | 10G WIS status 3 614 SONET-MIB - sonetPathCurrentUASs | + 615 SONET-MIB - sonetPathIntervalESs | 10G WIS 616 SONET-MIB - sonetPathIntervalSESs | path block 617 SONET-MIB - sonetPathIntervalCVs / error count 618 SONET-MIB - sonetPathIntervalUASs / 619 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 632 MAU-MIB - ifMauIfIndex none required 633 MAU-MIB - ifMauIndex none required 634 MAU-MIB - ifMauType 10G WIS control 2 635 MAU-MIB - ifMauStatus WIS control 1 636 MAU-MIB - ifMauMediaAvailable \ WIS status 1 + 637 MAU-MIB - ifMauMediaAvailableStateExits / 10G WIS status 3 638 MAU-MIB - ifMauJabberState none required 639 MAU-MIB - ifMauJabberingStateEnters none required 640 MAU-MIB - ifMauFalseCarriers none required 641 MAU-MIB - ifMauDefaultType 10G WIS control 2 642 MAU-MIB - ifMauAutoNegSupported none required 643 MAU-MIB - ifMauTypeListBits 10G WIS status 2 645 3.8. Structure of the MIB Module 647 Four tables are defined in this MIB module. 649 3.8.1. etherWisDeviceTable 651 The purpose of this table is to define managed objects to control the 652 WIS test pattern mode. These objects are required to support 653 mandatory and optional WIS test features specified in [P802.3ae] 654 subclause 50.3.8. 656 The etherWisDeviceTable is a sparse augmentation of the 657 sonetMediumTable of the SONET-MIB -- in other words, for each entry 658 in the etherWisDeviceTable there MUST be an entry in the 659 sonetMediumTable and the same ifIndex value SHALL be used for both 660 entries. 662 3.8.2. etherWisSectionCurrentTable 664 The purpose of this table is to define managed objects for the 665 transmitted and received section trace messages (J0 byte). 667 The etherWisSectionCurrentTable is a sparse augmentation of the 668 sonetSectionCurrentTable of the SONET-MIB -- in other words, for each 669 entry in the etherWisSectionCurrentTable there MUST be an entry in 670 the sonetSectionCurrentTable and the same ifIndex value SHALL be used 671 for both entries. 673 3.8.3. etherWisPathCurrentTable 675 The purpose of this table is to define managed objects for the 676 current WIS path layer status and for the transmitted and received 677 path trace messages (J1 byte). The path layer status object is 678 provided because the WIS supports some near-end path status 679 conditions that are not reported in sonetPathCurrentStatus. 681 The etherWisPathCurrentTable is a sparse augmentation of the 682 sonetPathCurrentTable of the SONET-MIB -- in other words, for each 683 entry in the etherWisPathCurrentTable there MUST be an entry in the 684 sonetPathCurrentTable and the same ifIndex value SHALL be used for 685 both entries. 687 3.8.4. etherWisFarEndPathCurrentTable 689 The purpose of this table is to define a managed object for the 690 current status of the far end of the path. This object is provided 691 because the WIS supports some far-end path status conditions that are 692 not reported in sonetPathCurrentStatus. 694 The etherWisFarEndPathCurrentTable is a sparse augmentation of the 695 sonetFarEndPathCurrentTable of the SONET-MIB -- in other words, for 696 each entry in the etherWisFarEndPathCurrentTable there MUST be an 697 entry in the sonetFarEndPathCurrentTable and the same ifIndex value 698 SHALL be used for both entries. 700 4. Object Definitions 702 ETHER-WIS DEFINITIONS ::= BEGIN 704 IMPORTS 705 MODULE-IDENTITY, OBJECT-TYPE, 706 transmission 707 FROM SNMPv2-SMI 708 ifIndex 709 FROM IF-MIB 710 MODULE-COMPLIANCE, OBJECT-GROUP 711 FROM SNMPv2-CONF 712 sonetMediumStuff2, sonetSectionStuff2, 713 sonetLineStuff2, sonetFarEndLineStuff2, 714 sonetPathStuff2, sonetFarEndPathStuff2, 715 sonetMediumType, sonetMediumLineCoding, 716 sonetMediumLineType, sonetMediumCircuitIdentifier, 717 sonetMediumLoopbackConfig, sonetSESthresholdSet, 718 sonetPathCurrentWidth 719 FROM SONET-MIB; 721 etherWisMIB MODULE-IDENTITY 722 LAST-UPDATED "200204141830Z" -- April 14, 2002 723 ORGANIZATION "IETF Ethernet Interfaces and Hub MIB 724 Working Group" 725 CONTACT-INFO 726 "WG charter: 727 http://www.ietf.org/html.charters/hubmib-charter.html 729 Chair: Dan Romascanu 730 Postal: Avaya Inc. 731 Atidim Technology Park, Bldg. 3 732 Tel Aviv 61131 733 Israel 734 Tel: +972 3 645 8414 735 E-mail: dromasca@avaya.com 737 Editor: C. M. Heard 738 Postal: 600 Rainbow Dr. #141 739 Mountain View, CA 94041-2542 740 USA 741 Tel: +1 650-964-8391 742 E-mail: heard@pobox.com" 744 DESCRIPTION 745 "The objects in this MIB module are used in conjunction 746 with objects in the SONET-MIB and the MAU-MIB to manage 747 the Ethernet WAN Interface Sublayer (WIS). 749 The following reference is used throughout this MIB module: 751 [IEEE 802.3 Std] refers to: 752 IEEE Std 802.3, 2000 Edition: 'IEEE Standard for 753 Information technology - Telecommunications and 754 information exchange between systems - Local and 755 metropolitan area networks - Specific requirements - 756 Part 3: Carrier sense multiple access with collision 757 detection (CSMA/CD) access method and physical layer 758 specifications', as amended by IEEE Draft P802.3ae/D4.2: 759 'Supplement to Carrier Sense Multiple Access with 760 Collision Detection (CSMA/CD) Access Method & Physical 761 Layer Specifications - Media Access Control (MAC) 762 Parameters, Physical Layer, and Management Parameters 763 for 10 Gb/s Operation', March 21, 2002. 765 Of particular interest are Clause 50, 'WAN Interface 766 Sublayer (WIS), type 10GBASE-W', Clause 30, '10Mb/s, 767 100Mb/s, 1000Mb/s, and 10Gb/s MAC Control, and Link 768 Aggregation Management', and Clause 45, 'Management 769 Data Input/Output (MDIO) Interface'." 771 REVISION "200204141830Z" -- April 14, 2002 772 DESCRIPTION "Initial version, published as RFC yyyy." 773 -- RFC Ed.: replace yyyy with actual RFC number & remove this notice 775 ::= { transmission XXX } 776 -- RFC Ed.: replace XXX with IANA-assigned number & remove this notice 778 -- The main sections of the module 780 etherWisObjects OBJECT IDENTIFIER ::= { etherWisMIB 1 } 782 etherWisObjectsPath OBJECT IDENTIFIER ::= { etherWisMIB 2 } 784 etherWisConformance OBJECT IDENTIFIER ::= { etherWisMIB 3 } 786 -- groups in the Ethernet WIS MIB module 788 etherWisDevice OBJECT IDENTIFIER ::= { etherWisObjects 1 } 790 etherWisSection OBJECT IDENTIFIER ::= { etherWisObjects 2 } 792 etherWisPath OBJECT IDENTIFIER ::= { etherWisObjectsPath 1 } 794 etherWisFarEndPath OBJECT IDENTIFIER ::= { etherWisObjectsPath 2 } 795 -- The Device group 797 -- These objects provide WIS extensions to 798 -- the SONET-MIB Medium Group. 800 etherWisDeviceTable OBJECT-TYPE 801 SYNTAX SEQUENCE OF EtherWisDeviceEntry 802 MAX-ACCESS not-accessible 803 STATUS current 804 DESCRIPTION 805 "The table for Ethernet WIS devices" 806 ::= { etherWisDevice 1 } 808 etherWisDeviceEntry OBJECT-TYPE 809 SYNTAX EtherWisDeviceEntry 810 MAX-ACCESS not-accessible 811 STATUS current 812 DESCRIPTION 813 "An entry in the Ethernet WIS device table. For each 814 instance of this object there MUST be a corresponding 815 instance of sonetMediumEntry." 816 INDEX { ifIndex } 817 ::= { etherWisDeviceTable 1 } 819 EtherWisDeviceEntry ::= 820 SEQUENCE { 821 etherWisDeviceTxTestPatternMode INTEGER, 822 etherWisDeviceRxTestPatternMode INTEGER, 823 etherWisDeviceRxTestPatternErrors Gauge32 824 } 826 etherWisDeviceTxTestPatternMode OBJECT-TYPE 827 SYNTAX INTEGER { 828 none(0), 829 squareWave(1), 830 prbs31(2), 831 mixedFrequency(3) 832 } 833 MAX-ACCESS read-write 834 STATUS current 835 DESCRIPTION 836 "This variable controls the transmit test pattern mode. 837 The value none(0) puts the the WIS transmit path into 838 the normal operating mode. The value squareWave(1) puts 839 the WIS transmit path into the square wave test pattern 840 mode described in [IEEE 802.3 Std.] subclause 50.3.8.1. 841 The value prbs31(2) puts the WIS transmit path into the 842 PRBS31 test pattern mode described in [IEEE 802.3 Std.] 843 subclause 50.3.8.2. The value mixedFrequency(3) puts the 844 WIS transmit path into the mixed frequency test pattern 845 mode described in [IEEE 802.3 Std.] subclause 50.3.8.3. 846 Any attempt to set this object to a value other than 847 none(0) when the corresponding instance of ifAdminState 848 has the value up(1) MUST be rejected with the error 849 inconsistentValue, and any attempt to set the corresponding 850 instance of ifAdminStatus to the value up(1) when an 851 instance of this object has a value other than none(0) 852 MUST be rejected with the error inconsistentValue." 853 REFERENCE 854 "[IEEE 802.3 Std.], 50.3.8, WIS test pattern generator and 855 checker, 45.2.2.6, 10G WIS control 2 register (2.7), and 856 45.2.2.7.2, PRBS31 pattern testing ability (2.8.1)." 857 ::= { etherWisDeviceEntry 1 } 859 etherWisDeviceRxTestPatternMode OBJECT-TYPE 860 SYNTAX INTEGER { 861 none(0), 862 prbs31(2), 863 mixedFrequency(3) 864 } 865 MAX-ACCESS read-write 866 STATUS current 867 DESCRIPTION 868 "This variable controls the receive test pattern mode. 869 The value none(0) puts the the WIS receive path into the 870 normal operating mode. The value prbs31(2) puts the WIS 871 receive path into the PRBS31 test pattern mode described 872 in [IEEE 802.3 Std.] subclause 50.3.8.2. The value 873 mixedFrequency(3) puts the WIS receive path into the mixed 874 frequency test pattern mode described in [IEEE 802.3 Std.] 875 subclause 50.3.8.3. Any attempt to set this object to a 876 value other than none(0) when the corresponding instance 877 of ifAdminState has the value up(1) MUST be rejected with 878 the error inconsistentValue, and any attempt to set the 879 corresponding instance of ifAdminStatus to the value up(1) 880 when an instance of this object has a value other than 881 none(0) MUST be rejected with the error inconsistentValue." 882 REFERENCE 883 "[IEEE 802.3 Std.], 50.3.8, WIS test pattern generator and 884 checker, 45.2.2.6, 10G WIS control 2 register (2.7), and 885 45.2.2.7.2, PRBS31 pattern testing ability (2.8.1)." 886 ::= { etherWisDeviceEntry 2 } 888 etherWisDeviceRxTestPatternErrors OBJECT-TYPE 889 SYNTAX Gauge32 ( 0..65535 ) 890 MAX-ACCESS read-write 891 STATUS current 892 DESCRIPTION 893 "This object counts the number of errors detected when the 894 WIS receive path is operating in the PRBS31 test pattern 895 mode. It is reset to zero when the WIS receive path 896 initially enters that mode, and it increments each time 897 the PRBS pattern checker detects an error as described in 898 [IEEE 802.3 Std.] subclause 50.3.8.2 unless its value is 899 65535, in which case it remains unchanged. This object is 900 writeable so that it may be reset upon explicit request 901 of a command generator application while the WIS receive 902 path continues to operate in PRBS31 test pattern mode." 903 REFERENCE 904 "[IEEE 802.3 Std.], 50.3.8, WIS test pattern generator and 905 checker, 45.2.2.7.2, PRBS31 pattern testing ability 906 (2.8.1), and 45.2.2.8, 10G WIS test pattern error counter 907 register (2.9)." 908 ::= { etherWisDeviceEntry 3 } 910 -- The Section group 912 -- These objects provide WIS extensions to 913 -- the SONET-MIB Section Group. 915 etherWisSectionCurrentTable OBJECT-TYPE 916 SYNTAX SEQUENCE OF EtherWisSectionCurrentEntry 917 MAX-ACCESS not-accessible 918 STATUS current 919 DESCRIPTION 920 "The table for the current state of Ethernet WIS sections." 921 ::= { etherWisSection 1 } 923 etherWisSectionCurrentEntry OBJECT-TYPE 924 SYNTAX EtherWisSectionCurrentEntry 925 MAX-ACCESS not-accessible 926 STATUS current 927 DESCRIPTION 928 "An entry in the etherWisSectionCurrentTable. For each 929 instance of this object there MUST be a corresponding 930 instance of sonetSectionCurrentEntry." 931 INDEX { ifIndex } 932 ::= { etherWisSectionCurrentTable 1 } 934 EtherWisSectionCurrentEntry ::= 935 SEQUENCE { 936 etherWisSectionCurrentJ0Transmitted OCTET STRING, 937 etherWisSectionCurrentJ0Received OCTET STRING 938 } 940 etherWisSectionCurrentJ0Transmitted OBJECT-TYPE 941 SYNTAX OCTET STRING (SIZE (16)) 942 MAX-ACCESS read-write 943 STATUS current 944 DESCRIPTION 945 "This is the 16-octet section trace message that is 946 to be transmitted in the J0 byte. The value SHOULD 947 be '89'h followed by fifteen octets of '00'h 948 (or some cyclic shift thereof) when the section 949 trace function is not used, and the implementation 950 SHOULD use that value (or a cyclic shift thereof) 951 as a default if no other value has been set." 952 REFERENCE 953 "[IEEE 802.3 Std.], 30.8.1.1.8, aJ0ValueTX." 954 ::= { etherWisSectionCurrentEntry 1 } 956 etherWisSectionCurrentJ0Received OBJECT-TYPE 957 SYNTAX OCTET STRING (SIZE (16)) 958 MAX-ACCESS read-only 959 STATUS current 960 DESCRIPTION 961 "This is the 16-octet section trace message that 962 was most recently received in the J0 byte." 963 REFERENCE 964 "[IEEE 802.3 Std.], 30.8.1.1.9, aJ0ValueRX." 965 ::= { etherWisSectionCurrentEntry 2 } 967 -- The Path group 969 -- These objects provide WIS extensions to 970 -- the SONET-MIB Path Group. 972 etherWisPathCurrentTable OBJECT-TYPE 973 SYNTAX SEQUENCE OF EtherWisPathCurrentEntry 974 MAX-ACCESS not-accessible 975 STATUS current 976 DESCRIPTION 977 "The table for the current state of Ethernet WIS paths." 978 ::= { etherWisPath 1 } 980 etherWisPathCurrentEntry OBJECT-TYPE 981 SYNTAX EtherWisPathCurrentEntry 982 MAX-ACCESS not-accessible 983 STATUS current 984 DESCRIPTION 985 "An entry in the etherWisPathCurrentTable. For each 986 instance of this object there MUST be a corresponding 987 instance of sonetPathCurrentEntry." 988 INDEX { ifIndex } 989 ::= { etherWisPathCurrentTable 1 } 991 EtherWisPathCurrentEntry ::= 992 SEQUENCE { 993 etherWisPathCurrentStatus BITS, 994 etherWisPathCurrentJ1Transmitted OCTET STRING, 995 etherWisPathCurrentJ1Received OCTET STRING 996 } 998 etherWisPathCurrentStatus OBJECT-TYPE 999 SYNTAX BITS { 1000 etherWisPathLOP(0), 1001 etherWisPathAIS(1), 1002 etherWisPathPLM(2), 1003 etherWisPathLCD(3) 1004 } 1005 MAX-ACCESS read-only 1006 STATUS current 1007 DESCRIPTION 1008 "This variable indicates the current status of the 1009 path payload with a bit map that can indicate multiple 1010 defects at once. The bit positions are assigned as 1011 follows: 1013 etherWisPathLOP(0) 1014 This bit is set to indicate that an 1015 LOP-P (Loss of Pointer - Path) defect 1016 is being experienced. Note: when this 1017 bit is set, sonetPathSTSLOP MUST be set 1018 in the corresponding instance of 1019 sonetPathCurrentStatus. 1021 etherWisPathAIS(1) 1022 This bit is set to indicate that an 1023 AIS-P (Alarm Indication Signal - Path) 1024 defect is being experienced. Note: when 1025 this bit is set, sonetPathSTSAIS MUST be 1026 set in the corresponding instance of 1027 sonetPathCurrentStatus. 1029 etherWisPathPLM(1) 1030 This bit is set to indicate that a 1031 PLM-P (Payload Label Mismatch - Path) 1032 defect is being experienced. Note: when 1033 this bit is set, sonetPathSignalLabelMismatch 1034 MUST be set in the corresponding instance of 1035 sonetPathCurrentStatus. 1037 etherWisPathLCD(3) 1038 This bit is set to indicate that an 1039 LCD-P (Loss of Codegroup Delination - Path) 1040 defect is being experienced. Since this 1041 defect is detected by the PCS and not by 1042 the path layer itself, there is no 1043 corresponding bit in sonetPathCurrentStatus." 1044 REFERENCE 1045 "[IEEE 802.3 Std.], 30.8.1.1.18, aPathStatus." 1046 ::= { etherWisPathCurrentEntry 1 } 1048 etherWisPathCurrentJ1Transmitted OBJECT-TYPE 1049 SYNTAX OCTET STRING (SIZE (16)) 1050 MAX-ACCESS read-write 1051 STATUS current 1052 DESCRIPTION 1053 "This is the 16-octet path trace message that is to 1054 be transmitted in the J1 byte. The value SHOULD 1055 be '89'h followed by fifteen octets of '00'h 1056 (or some cyclic shift thereof) when the path 1057 trace function is not used, and the implementation 1058 SHOULD use that value (or a cyclic shift thereof) 1059 as a default if no other value has been set." 1060 REFERENCE 1061 "[IEEE 802.3 Std.], 30.8.1.1.23, aJ1ValueTX." 1062 ::= { etherWisPathCurrentEntry 2 } 1064 etherWisPathCurrentJ1Received OBJECT-TYPE 1065 SYNTAX OCTET STRING (SIZE (16)) 1066 MAX-ACCESS read-only 1067 STATUS current 1068 DESCRIPTION 1069 "This is the 16-octet path trace message that 1070 was most recently received in the J1 byte." 1071 REFERENCE 1072 "[IEEE 802.3 Std.], 30.8.1.1.24, aJ1ValueRX." 1073 ::= { etherWisPathCurrentEntry 3 } 1075 -- The Far End Path group 1077 -- These objects provide WIS extensions to 1078 -- the SONET-MIB Far End Path Group. 1080 etherWisFarEndPathCurrentTable OBJECT-TYPE 1081 SYNTAX SEQUENCE OF EtherWisFarEndPathCurrentEntry 1082 MAX-ACCESS not-accessible 1083 STATUS current 1084 DESCRIPTION 1085 "The table for the current far-end state of Ethernet WIS 1086 paths." 1087 ::= { etherWisFarEndPath 1 } 1089 etherWisFarEndPathCurrentEntry OBJECT-TYPE 1090 SYNTAX EtherWisFarEndPathCurrentEntry 1091 MAX-ACCESS not-accessible 1092 STATUS current 1093 DESCRIPTION 1094 "An entry in the etherWisFarEndPathCurrentTable. For each 1095 instance of this object there MUST be a corresponding 1096 instance of sonetFarEndPathCurrentEntry." 1097 INDEX { ifIndex } 1098 ::= { etherWisFarEndPathCurrentTable 1 } 1100 EtherWisFarEndPathCurrentEntry ::= 1101 SEQUENCE { 1102 etherWisFarEndPathCurrentStatus BITS 1103 } 1105 etherWisFarEndPathCurrentStatus OBJECT-TYPE 1106 SYNTAX BITS { 1107 etherWisFarEndPayloadDefect(0), 1108 etherWisFarEndServerDefect(1) 1109 } 1110 MAX-ACCESS read-only 1111 STATUS current 1112 DESCRIPTION 1113 "This variable indicates the current status at the 1114 far end of the path using a bit map that can indicate 1115 multiple defects at once. The bit positions are 1116 assigned as follows: 1118 etherWisFarEndPayloadDefect(0) 1119 A far end payload defect (i.e., far end 1120 PLM-P or LCD-P) is currently being signalled 1121 in G1 bits 5-7. 1123 etherWisFarEndServerDefect(1) 1124 A far end server defect (i.e., far end 1125 LOP-P or AIS-P) is currently being signalled 1126 in G1 bits 5-7. Note: when this bit is set, 1127 sonetPathSTSRDI MUST be set in the corresponding 1128 instance of sonetPathCurrentStatus." 1129 REFERENCE 1130 "[IEEE 802.3 Std.], 30.8.1.1.25, aFarEndPathStatus." 1131 ::= { etherWisFarEndPathCurrentEntry 1 } 1133 -- 1134 -- Conformance Statements 1135 -- 1137 etherWisGroups OBJECT IDENTIFIER ::= { etherWisConformance 1 } 1139 etherWisCompliances OBJECT IDENTIFIER ::= { etherWisConformance 2 } 1141 -- Object Groups 1143 etherWisDeviceGroupBasic OBJECT-GROUP 1144 OBJECTS { 1145 etherWisDeviceTxTestPatternMode, 1146 etherWisDeviceRxTestPatternMode 1147 } 1148 STATUS current 1149 DESCRIPTION 1150 "A collection of objects that support test 1151 features required of all WIS devices." 1152 ::= { etherWisGroups 1 } 1154 etherWisDeviceGroupExtra OBJECT-GROUP 1155 OBJECTS { 1156 etherWisDeviceRxTestPatternErrors 1157 } 1158 STATUS current 1159 DESCRIPTION 1160 "A collection of objects that support 1161 optional WIS device test features." 1162 ::= { etherWisGroups 2 } 1164 etherWisSectionGroup OBJECT-GROUP 1165 OBJECTS { 1166 etherWisSectionCurrentJ0Transmitted, 1167 etherWisSectionCurrentJ0Received 1168 } 1169 STATUS current 1170 DESCRIPTION 1171 "A collection of objects that provide 1172 required information about a WIS section." 1173 ::= { etherWisGroups 3 } 1175 etherWisPathGroup OBJECT-GROUP 1176 OBJECTS { 1177 etherWisPathCurrentStatus, 1178 etherWisPathCurrentJ1Transmitted, 1179 etherWisPathCurrentJ1Received 1180 } 1181 STATUS current 1182 DESCRIPTION 1183 "A collection of objects that provide 1184 required information about a WIS path." 1185 ::= { etherWisGroups 4 } 1187 etherWisFarEndPathGroup OBJECT-GROUP 1188 OBJECTS { 1189 etherWisFarEndPathCurrentStatus 1190 } 1191 STATUS current 1192 DESCRIPTION 1193 "A collection of objects that provide required 1194 information about the far end of a WIS path." 1195 ::= { etherWisGroups 5 } 1197 -- Compliance Statements 1199 etherWisCompliance MODULE-COMPLIANCE 1200 STATUS current 1201 DESCRIPTION 1202 "The compliance statement for this module." 1204 MODULE -- this module 1205 MANDATORY-GROUPS { 1206 etherWisDeviceGroupBasic, 1207 etherWisSectionGroup, 1208 etherWisPathGroup, 1209 etherWisFarEndPathGroup 1210 } 1212 OBJECT etherWisDeviceTxTestPatternMode 1213 SYNTAX INTEGER { 1214 none(0), 1215 squareWave(1), 1216 mixedFrequency(3) 1217 } 1218 DESCRIPTION 1219 "Support for values other than none(0), 1220 squareWave(1), and mixedFrequency(3) 1221 is not required." 1223 OBJECT etherWisDeviceRxTestPatternMode 1224 SYNTAX INTEGER { 1225 none(0), 1226 mixedFrequency(3) 1227 } 1228 DESCRIPTION 1229 "Support for values other than none(0) 1230 and mixedFrequency(3) is not required." 1232 GROUP etherWisDeviceGroupExtra 1233 DESCRIPTION 1234 "Implementation of this group, along with support for 1235 the value prbs31(2) for etherWisDeviceTxTestPatternMode 1236 and etherWisDeviceRxTestPatternMode, is necessary if the 1237 optional PRBS31 test pattern mode is to be supported." 1239 MODULE SONET-MIB 1240 MANDATORY-GROUPS { 1241 sonetMediumStuff2, 1242 sonetSectionStuff2, 1243 sonetLineStuff2, 1244 sonetFarEndLineStuff2, 1245 sonetPathStuff2, 1246 sonetFarEndPathStuff2 1247 } 1249 OBJECT sonetMediumType 1250 SYNTAX INTEGER { 1251 sonet(1) 1252 } 1253 MIN-ACCESS read-only 1254 DESCRIPTION 1255 "Write access is not required, nor is support 1256 for any value other than sonet(1)." 1258 OBJECT sonetMediumLineCoding 1259 SYNTAX INTEGER { 1260 sonetMediumNRZ(4) 1261 } 1262 MIN-ACCESS read-only 1263 DESCRIPTION 1264 "Write access is not required, nor is support 1265 for any value other than sonetMediumNRZ(4)." 1267 OBJECT sonetMediumLineType 1268 MIN-ACCESS read-only 1269 DESCRIPTION 1270 "Write access is not required." 1272 OBJECT sonetMediumCircuitIdentifier 1273 MIN-ACCESS read-only 1274 DESCRIPTION 1275 "Write access is not required." 1277 OBJECT sonetMediumLoopbackConfig 1278 SYNTAX BITS { 1279 sonetNoLoop(0), 1280 sonetFacilityLoop(1) 1281 } 1282 MIN-ACCESS read-only 1283 DESCRIPTION 1284 "Write access is not required, nor is support for values 1285 other than sonetNoLoop(0) and sonetFacilityLoop(1)." 1287 OBJECT sonetSESthresholdSet 1288 MIN-ACCESS read-only 1289 DESCRIPTION 1290 "Write access is not required, and only one 1291 of the enumerated values need be supported." 1293 OBJECT sonetPathCurrentWidth 1294 SYNTAX INTEGER { 1295 sts192cSTM64(6) 1296 } 1297 MIN-ACCESS read-only 1298 DESCRIPTION 1299 "Write access is not required, nor is support 1300 for any value other than sts192cSTM64(6)." 1302 ::= { etherWisCompliances 1 } 1304 END 1306 5. Acknowledgments 1308 This document is a product of the IETF Hubmib and AToMMIB Working 1309 Groups. It builds upon the work of the IEEE P802.3ae 10 Gigabit 1310 Ethernet Task Force. 1312 6. Security Considerations 1314 There are five management objects defined in this MIB that have a 1315 MAX-ACCESS clause of read-write: etherWisDeviceTxTestPatternMode, 1316 etherWisDeviceRxTestPatternMode, etherWisDeviceRxTestPatternErrors, 1317 etherWisSectionCurrentJ0Transmitted, and 1318 etherWisPathCurrentJ1Transmitted. Setting these objects can have the 1319 following potentially disruptive effects on network operation: 1321 o changing the transmit or receive test pattern mode or modifying 1322 the accumulated error count from a PRBS31 pattern test on an 1323 administratively disabled 10GBASE-W interface, which can 1324 interfere with an in-progress pattern test; 1326 o modifying the transmitted section trace and/or path trace 1327 message on an operational 10GBASE-W interface, which can cause 1328 connectivity alarms to be raised at the remote of the link. 1330 Such objects may be considered sensitive or vulnerable in some 1331 network environments. The support for SET operations in a non-secure 1332 environment without proper protection can have a negative effect on 1333 network operations. 1335 SNMPv1 by itself is not a secure environment. Even if the network 1336 itself is secure (for example by using IPSec), even then, there is no 1337 control as to who on the secure network is allowed to access and 1338 GET/SET (read/change) the objects in this MIB. 1340 It is recommended that the implementers consider the security 1341 features as provided by the SNMPv3 framework. Specifically, the use 1342 of the User-based Security Model RFC 2574 [RFC2574] and the View- 1343 based Access Control Model RFC 2575 [RFC2575] is recommended. 1345 It is then a customer/user responsibility to ensure that the SNMP 1346 entity giving access to an instance of this MIB, is properly 1347 configured to give access to the objects only to those principals 1348 (users) that have legitimate rights to indeed GET or SET 1349 (change/create/delete) them. 1351 7. References 1353 7.1. Normative References 1355 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture 1356 for Describing SNMP Management Frameworks", RFC 2571, April 1357 1999. 1359 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1360 Rose, M., and S. Waldbusser, "Structure of Management 1361 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1362 1999. 1364 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1365 Rose, M., and S. Waldbusser, "Textual Conventions for 1366 SMIv2", STD 58, RFC 2579, April 1999. 1368 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1369 Rose, M., and S. Waldbusser, "Conformance Statements for 1370 SMIv2", STD 58, RFC 2580, April 1999. 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 [RFC2863] McCloghrie, K., and F. Kastenholz, "The Interfaces Group 1396 MIB", RFC 2863, June 2000. 1398 [RFC2864] McCloghrie, K., and G. Hanson, "The Inverted Stack Table 1399 Extension to the Interfaces Group MIB", RFC 2864, June 2000. 1401 [SONETng] Tesink, K., "Definitions of Managed Objects for the 1402 SONET/SDH Interface Type", , work in progress. 1405 [T1.231] American National Standard for Telecommunications - Digital 1406 Hierarchy - Layer 1 In-Service Digital Transmission 1407 Performance Monitoring, ANSI T1.231-1997, September 1997. 1409 [ETHERIF] Flick, J., "Definitions of Managed Objects for the 1410 Ethernet-like Interface Types", , work in progress. 1413 [MAU-MIB] Flick, J., "Definitions of Managed Objects for IEEE 802.3 1414 Medium Attachment Units (MAUs)", , work in progress. 1417 [P802.3ae] Institute of Electrical and Electronic Engineers, IEEE Draft 1418 P802.3ae/D4.2, "Supplement to Carrier Sense Multiple Access 1419 with Collision Detection (CSMA/CD) Access Method & Physical 1420 Layer Specifications - Media Access Control (MAC) 1421 Parameters, Physical Layer, and Management Parameters for 10 1422 Gb/s Operation", March 21, 2002, work in progress. 1424 7.2. Informative References 1426 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1427 Requirements Levels", BCP 14, RFC 2119, March 1997. 1429 [RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification 1430 of Management Information for TCP/IP-based Internets", STD 1431 16, RFC 1155, May 1990. 1433 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 1434 16, RFC 1212, March 1991. 1436 [RFC1215] Rose, M., "A Convention for Defining Traps for use with the 1437 SNMP", RFC 1215, March 1991. 1439 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple 1440 Network Management Protocol", STD 15, RFC 1157, May 1990. 1442 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1443 "Introduction to Community-based SNMPv2", RFC 1901, January 1444 1996. 1446 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 1447 "Introduction to Version 3 of the Internet-standard Network 1448 Management Framework", RFC 2570, April 1999. 1450 8. Authors' Addresses 1452 Mike Ayers 1453 BMC Software, Inc. 1454 2141 North First Street 1455 San Jose, CA 95131 1456 USA 1458 Phone: +1 408 546 0947 1459 Fax: +1 408 965 0359 1460 Email: mayers@bmc.com 1462 John Flick 1463 Hewlett-Packard Company 1464 8000 Foothills Blvd. M/S 5557 1465 Roseville, CA 95747-5557 1466 USA 1468 Phone: +1 916 785 4018 1469 Fax: +1 916 785 1199 1470 Email: johnf@rose.hp.com 1472 C. M. Heard 1473 600 Rainbow Dr. #141 1474 Mountain View, CA 94041-2542 1475 USA 1477 Phone: +1 650 964 8391 1478 EMail: heard@pobox.com 1480 Kam Lam 1481 Lucent Technologies 1482 101 Crawfords Corner Road, Room 4C-616A 1483 Holmdel, NJ 07733 1484 USA 1486 Phone: +1 732 949 8338 1487 EMail: hklam@lucent.com 1488 Kerry McDonald 1489 Institute for Applied Supercomputing 1490 California State University San Bernardino 1492 Email: kerry_mcd@hotmail.com 1493 kmcdonal@csci.csusb.edu 1495 K. C. Norseth 1496 934 S. Palos Verdes Dr. 1497 Kaysville, Utah 84037 1498 USA 1500 Phone: +1 801 546 3316 1501 Email: kcn@norseth.com 1503 Kaj Tesink 1504 Telcordia Technologies 1505 331 Newman Springs Road 1506 P.O. Box 7020 1507 Red Bank, NJ 07701-7020 1508 USA 1510 Phone: +1 732 758 5254 1511 EMail: kaj@research.telcordia.com 1513 9. Intellectual Property 1515 The IETF takes no position regarding the validity or scope of any 1516 intellectual property or other rights that might be claimed to 1517 pertain to the implementation or use of the technology described in 1518 this document or the extent to which any license under such rights 1519 might or might not be available; neither does it represent that it 1520 has made any effort to identify any such rights. Information on the 1521 IETF's procedures with respect to rights in standards-track and 1522 standards-related documentation can be found in BCP-11. Copies of 1523 claims of rights made available for publication and any assurances of 1524 licenses to be made available, or the result of an attempt made to 1525 obtain a general license or permission for the use of such 1526 proprietary rights by implementors or users of this specification can 1527 be obtained from the IETF Secretariat. 1529 The IETF invites any interested party to bring to its attention any 1530 copyrights, patents or patent applications, or other proprietary 1531 rights which may cover technology that may be required to practice 1532 this standard. Please address the information to the IETF Executive 1533 Director. 1535 Appendix A: Collection of Performance Data Using WIS MDIO Registers 1537 The purpose of this appendix is to illustrate how the WIS MDIO 1538 registers specified in [P802.3ae] subclause 45.2.2 (and more 1539 specifically the subset required by [P802.3ae] subclause 50.3.11) can 1540 be used to collect performance data either according to the 1541 conventions adopted by this document or according to the conventions 1542 specified in [P802.3ae] Clause 30. 1544 For an agent implementing the SNMP managed objects required by this 1545 document the first step in collecting WIS performance data would be 1546 to poll the 10G WIS status 3 register and the various error count 1547 registers (10G WIS section BIP error count, 10G WIS line BIP errors, 1548 10G WIS far end line BIP errors, 10G WIS path block error count, and 1549 10G WIS far end path block error count) once per second. The 10G WIS 1550 status 3 register bits are all latched until read and so would 1551 indicate whether a given defect occurred any time during the previous 1552 second. The error count registers roll over modulo 2^16 or 2^32, and 1553 so to find the number of errors within the previous second the agent 1554 would need to subtract (modulo 2^16 or 2^32) the current reading from 1555 the reading taken one second ago. Armed with that information, the 1556 agent could determine for any layer whether the one second interval 1557 was an errored second, a severely errored second (that requires 1558 comparison with a threshold unless a defect is present), or a 1559 severely errored frame second. Determining whether a given second is 1560 or is not part of unavailable time requires additional logic; the 1561 most straightforward and accurate method is the delay-line approach 1562 outlined in Appendix A of [SONETng]. With that information available 1563 the agent would be able to determine by how much each current count 1564 should be incremented (including effects of inhibiting). 1565 Implementations that conform to [T1.231] would end each 15-minute 1566 interval on time-of-day clock 1/4 hour boundaries; if the delay-line 1567 approach is used then a time-of-day timestamp would accompany the 1568 one-second statistics. At the end of each interval the current 1569 registers would be pushed onto the history stack and then would be 1570 cleared. The xyxIntervalValidData flags would be set to False(2) if 1571 the number of samples was not between 890 and 910 or, in the case of 1572 far-end counts, if a near-end defect occurred during the just- 1573 completed interval (see [T1.231] Section 9.1.2.2 for details). 1575 An agent implementing the [P802.3ae] Clause 30 oWIS objects could 1576 also start by polling the 10G WIS status 3 register and the various 1577 error count registers to find the defects and error counts for the 1578 previous second, and it could determine the number of errors and 1579 whether the second was an errored second, a severely errored second, 1580 or a severely errored frame second in the same manner as above. The 1581 rest of the process would simply be to increment the generalized 1582 non-resetable counters without consideration of any inhibiting rules. 1584 Full Copyright Statement 1586 Copyright (C) The Internet Society (2002). All Rights Reserved. 1588 This document and translations of it may be copied and furnished to 1589 others, and derivative works that comment on or otherwise explain it 1590 or assist in its implementation may be prepared, copied, published 1591 and distributed, in whole or in part, without restriction of any 1592 kind, provided that the above copyright notice and this paragraph are 1593 included on all such copies and derivative works. However, this 1594 document itself may not be modified in any way, such as by removing 1595 the copyright notice or references to the Internet Society or other 1596 Internet organizations, except as needed for the purpose of 1597 developing Internet standards in which case the procedures for 1598 copyrights defined in the Internet Standards process must be 1599 followed, or as required to translate it into languages other than 1600 English. 1602 The limited permissions granted above are perpetual and will not be 1603 revoked by the Internet Society or its successors or assigns. 1605 This document and the information contained herein is provided on an 1606 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 1607 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 1608 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 1609 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 1610 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1612 Revision History 1614 NOTE TO RFC Editor: this section is to be removed prior to 1615 publication as an RFC. 1617 The following changes were made to 1618 to produce : 1620 1.) Section 3.1 was updated as agreed in "WIS MIB compliance 1621 statement issue" e-mail thread, specifically to explain that the 1622 ETHER-WIS compliance statement requires all objects that required 1623 by sonetCompliance2 as well as some that it leaves optional. 1625 2.) In Section 3.5 the paragraph dealing with STS-Path Remote 1626 Defect Indication was updated to indicate that an implementation 1627 of the WIS MIB (not necessarily an arbitrary implementation of the 1628 WIS) has to set the SONET-MIB's RDI status bit when a remote 1629 server defect is detected. 1631 3.) In Section 3.6 the text introducing the table of semantic 1632 differences between IEEE GDMO and SNMP objects was wordsmithed. 1634 4.) In Section 3.7 the mapping between objects in the 1635 etherWisDeviceTable and the station management registers was 1636 updated to reflect the updated MDIO register definitions in 1637 P802.3ae/D4.01 and the corresponding updates to the MIB objects. 1639 5.) In Section 3.8.1 the text was updated to state that the 1640 purpose of the etherWisDeviceTable is to support mandatory and 1641 optional WIS test features. 1643 6.) In Sections 3.8.1, 3.8.2, 3.8.3, and 3.8.4 certain instances 1644 of "SHALL" were changed to "MUST" to improve readability. 1646 7.) The LAST-UPDATED, ORGANIZATION, REVISION, and DESCRIPTION 1647 clauses of the MODULE-IDENTITY invocation were updated. 1649 8.) The lower-case "shall" in the DESCRIPTION clause of each table 1650 entry was changed to an uppercase "MUST", per RFC 2119, because it 1651 describes a requirement of the specification in the draft. 1653 9.) The etherWisDeviceTestPatternType objects was removed, and the 1654 objects etherWisDeviceTxTestPatternMode and 1655 etherWisDeviceRxTestPatternMode were changed from simple 1656 "enable/disable" flags to enumerations that reflect the specific 1657 text pattern mode in which the transmitter or receiver is 1658 operating. A new optional object called 1659 etherWisDeviceRxTestPatternErrors was added to make visible the 1660 error count MDIO register contents when the receiver is operating 1661 in the (optional) PRBS31 test pattern mode added in D4.01. 1663 10.) The SYNTAX of etherWisSectionCurrentJ0Transmitted and 1664 etherWisSectionCurrentJ0Received was changed from INTEGER (0..255) 1665 to OCTET STRING (SIZE (16)) to reflect the change from 1-byte to 1666 16-byte section trace messages in D4.01, and the DESCRIPTION 1667 clauses were rewritten along the lines for those of the 1668 corresponding path trace objects. 1670 11.) In the DESCRIPTION of etherWisPathCurrentJ0Transmitted "path 1671 message" was changes to "path trace message". 1673 12.) etherWisDeviceGroup was split into a mandatory group 1674 etherWisDeviceGroupBasic and an optional group 1675 etherWisDeviceGroupExtra. 1677 13.) The compliance name was changed from 1678 etherWisCurrentCompliance to etherWisCompliance. 1680 14.) OBJECT clauses were added to specify required values for 1681 etherWisDeviceTxTestPatternMode and 1682 etherWisDeviceRxTestPatternMode. 1684 15.) A GROUP clause was added to state that 1685 etherWisDeviceGroupExtra needs to be implemented in order to 1686 support the PRBS31 test pattern mode. The DESCRIPTION clause 1687 points out that the prbs31 enumeration is needed for 1688 etherWisDeviceTxTestPatternMode/etherWisDeviceRxTestPatternMode. 1690 16.) References [SONETng] and [P802.3ae] were updated to draft- 1691 ietf-atommib-rfc2558bis-00.txt and P802.3ae/D4.01, respectively. 1693 The following changes were made to 1694 to produce : 1696 1.) The page formatting was changed to match that used in recent 1697 RFCs. 1699 2.) Heading numbering and bracketed references were removed from 1700 the abstract, and "SONET MIB" was expanded to "SONET/SDH Interface 1701 MIB". 1703 3.) RFC 2119 terminology conventions were moved from the abstract 1704 into a separate numbered "Conventions" section and were 1705 wordsmithed to match the style of recent RFCs. 1707 4.) Each occurrence of "SONET MIB" in Section 3, "Overview", was 1708 expanded to "SONET/SDH Interface MIB". 1710 5.) Each occurrence of "MAU-MIB" in Section 3, "Overview", was 1711 expanded to "802.3 MAU MIB". 1713 6.) Each occurrence of "SONET MIB" in Sections 3.1, 3.8.1, 3.8.2, 1714 3.8.3, and 3.8.4 was changed to "SONET-MIB" (this matches the 1715 usage elsewhere, specifically Sections 3.2 and 3.3). 1717 7.) All occurrences of "[P802.3ae] subclause 50.3.10" were updated 1718 to "[P802.3ae] subclause 50.3.11" in order to match the subclause 1719 numbering in P802.3ae/D4.2 (affected sections are 3.1, 3.6, 3.7, 1720 and Appendix A). 1722 8.) "Ethernet-like Interfaces MIB" was changed to "Ethernet-like 1723 Interface MIB" in Section 3.2 in order to match the usage in the 1724 abstract. 1726 9.) "mauModIfCompl2" was updated to "mauModIfCompl3" in Section 1727 3.3 in order to match . 1729 10.) An unnecessary heading was removed the table in Section 3.6 1730 that compares the semantics of IEEE threshold and counter objects 1731 with those of the corresponding objects imported from the SONET- 1732 MIB. 1734 11.) The text at the end of Section 3.6 was wordsmithed to remove 1735 unnecessary verbiage. 1737 12.) The MDIO register name spellings in Section 3.7, Section 4, 1738 and Appendix A were updated to match those in P802.3ae/D4.2 1739 subclause 45.2.2. 1741 13.) A missing comma was added to the 1742 etherWisDeviceRxTestPatternErrors REFERENCE clause. 1744 14.) DESCRIPTION clauses of etherWisSectionCurrentJ0Transmitted 1745 and etherWisPathCurrentJ1Transmitted were updates to state that 1746 the default value should be '89'h followed by 16 octets of '00'h, 1747 rather than 16 octets of '00'h followed by '89'h (this matches the 1748 resolution in P802.3ae/D4.2 of a byte ordering inconsistency). 1750 15.) The MAX-ACCESS clauses of etherWisPathCurrentStatus and 1751 etherWisPathCurrentStatus were changed from 'read-write' to 1753 16.) In Section 6, "Security Considerations", all read-write 1754 objects have been explicitly listed and mention of read-create 1755 objects has been removed. 1757 17.) References [ETHERIF], [MAU-MIB], and [P802.3ae] were updated 1758 to , , and P802.3ae/D4.2, respectively. 1761 18.) Normative and informative references were moved into separate 1762 sub-sections. 1764 19.) A "To-Do List" section was added. 1766 To-Do List 1768 NOTE TO RFC Editor: prior to publishing this document please take 1769 care of any open items listed below and then remove this section. 1771 1.) All occurrences of "IEEE Draft P802.3ae/D4.2" must be changed 1772 to "IEEE Std 802.3ae" once the standard has been approved, the 1773 approval date must replace the draft publication date, and all 1774 occurrences of the reference tag [P802.3ae] must be changed to 1775 [802.3ae]. Note that this draft is referenced both in Section 4, 1776 "Object Definitions", and in Section 7.1, "Normative References". 1778 2.) Normative references [SONETng], [ETHERIF], and [MAU-MIB] must 1779 be updated to point to the appropriate RFCs when the respective 1780 Internet Drafts are published, and all occurrences of the 1781 reference tags must be changed to [RFCnnnn] where nnnn is the 1782 assigned RFC number. 1784 Table of Contents 1786 1 Conventions ............................................... 2 1787 2 The SNMP Management Framework ............................. 2 1788 3 Overview .................................................. 3 1789 3.1 Relationship to the SONET/SDH Interface MIB ............. 4 1790 3.2 Relationship to the Ethernet-like Interface MIB ......... 4 1791 3.3 Relationship to the 802.3 MAU MIB ....................... 4 1792 3.4 Use of the ifTable ...................................... 5 1793 3.4.1 Layering Model ........................................ 5 1794 3.4.2 Use of ifTable for LLC Layer/MAC 1795 Layer/Reconciliation Sublayer/Physical Coding 1796 Sublayer ............................................... 5 1797 3.4.3 Use of ifTable for SONET/SDH Path Layer ............... 5 1798 3.4.4 Use of ifTable for SONET/SDH Medium/Section/Line 1799 Layer .................................................. 6 1800 3.5 SONET/SDH Terminology ................................... 6 1801 3.6 Mapping of IEEE 802.3 Managed Objects ................... 7 1802 3.7 Mapping of SNMP Objects to WIS Station Management 1803 Registers .............................................. 12 1804 3.8 Structure of the MIB Module ............................. 14 1805 3.8.1 etherWisDeviceTable ................................... 14 1806 3.8.2 etherWisSectionCurrentTable ........................... 14 1807 3.8.3 etherWisPathCurrentTable .............................. 15 1808 3.8.4 etherWisFarEndPathCurrentTable ........................ 15 1809 4 Object Definitions ........................................ 16 1810 5 Acknowledgments ........................................... 30 1811 6 Security Considerations ................................... 30 1812 7 References ................................................ 31 1813 7.1 Normative References .................................... 31 1814 7.2 Informative References .................................. 32 1815 8 Authors' Addresses ........................................ 33 1816 9 Intellectual Property ..................................... 34 1817 Appendix A: Collection of Performance Data Using WIS 1818 MDIO Registers ......................................... 35 1819 Full Copyright Statement ................................... 36