idnits 2.17.1 draft-ietf-hubmib-wis-mib-01.txt: ** The Abstract section seems to be numbered Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. ** The document is more than 15 pages and seems to lack a Table of Contents. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** The abstract seems to contain references ([ETHERIF], [MAU-MIB], [RFC2119], [RFC2863], [SONETng], [RFC2864]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. == There are 3 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 1550 has weird spacing: '...Mapping of S...' -- 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 (November 20, 2001) is 8187 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) ** Obsolete normative reference: RFC 2571 (Obsoleted by RFC 3411) ** Downref: Normative reference to an Informational RFC: RFC 1215 ** Downref: Normative reference to an Historic RFC: RFC 1157 ** Downref: Normative reference to an Historic RFC: RFC 1901 ** Obsolete normative reference: RFC 1906 (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2572 (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2574 (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 1905 (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2573 (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2575 (Obsoleted by RFC 3415) ** Obsolete normative reference: RFC 2570 (Obsoleted by RFC 3410) ** Obsolete normative reference: RFC 2558 (ref. 'SONETng') (Obsoleted by RFC 3592) -- Possible downref: Non-RFC (?) normative reference: ref. 'ETHERIF' -- Possible downref: Non-RFC (?) normative reference: ref. 'MAU-MIB' Summary: 19 errors (**), 0 flaws (~~), 4 warnings (==), 4 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 Hubmib and AToMMIB Working Groups Mike Ayers 3 INTERNET DRAFT BMC Software, Inc. 4 John Flick 5 Hewlett-Packard Company 6 C. M. Heard 7 Consultant 8 Kam Lam 9 Lucent Technologies 10 Kerry McDonald 11 CSU San Bernardino 12 K. C. Norseth 13 Enterasys Networks 14 Kaj Tesink 15 Telcordia Technologies 16 November 20, 2001 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 (2001). All Rights Reserved. 45 1. Abstract 47 This document defines a portion of the Management Information Base 48 (MIB) for use with network management protocols in TCP/IP based 49 internets. In particular, it defines objects for managing the 50 Ethernet Wide Area Network (WAN) Interface Sublayer (WIS) [P802.3ae]. 52 The MIB module defined in this memo is implemented in conjunction 53 with the Ethernet-like Interface MIB [ETHERIF], the 802.3 Medium 54 Attachment Unit MIB [MAU-MIB], the Interfaces Group MIB [RFC2863], 55 and the Inverted Stack Table MIB [RFC2864]. It also extends the 56 SONET MIB [SONETng] and is implemented in conjunction with that MIB 57 module. 59 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 60 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 61 document are to be interpreted as described in [RFC2119]. 63 2. The SNMP Management Framework 65 The SNMP Management Framework presently consists of five major 66 components: 68 o An overall architecture, described in RFC 2571 [RFC2571]. 70 o Mechanisms for describing and naming objects and events for the 71 purpose of management. The first version of this Structure of 72 Management Information (SMI) is called SMIv1 and described in 73 STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 74 1215 [RFC1215]. The second version, called SMIv2, is described 75 in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and 76 STD 58, RFC 2580 [RFC2580]. 78 o Message protocols for transferring management information. The 79 first version of the SNMP message protocol is called SNMPv1 and 80 described in STD 15, RFC 1157 [RFC1157]. A second version of 81 the SNMP message protocol, which is not an Internet standards 82 track protocol, is called SNMPv2c and described in RFC 1901 83 [RFC1901] and RFC 1906 [RFC1906]. The third version of the 84 message protocol is called SNMPv3 and described in RFC 1906 85 [RFC1906], RFC 2572 [RFC2572] and RFC 2574 [RFC2574]. 87 o Protocol operations for accessing management information. The 88 first set of protocol operations and associated PDU formats is 89 described in STD 15, RFC 1157 [RFC1157]. A second set of 90 protocol operations and associated PDU formats is described in 91 RFC 1905 [RFC1905]. 93 o A set of fundamental applications described in RFC 2573 94 [RFC2573] and the view-based access control mechanism described 95 in RFC 2575 [RFC2575]. 97 A more detailed introduction to the current SNMP Management Framework 98 can be found in RFC 2570 [RFC2570]. 100 Managed objects are accessed via a virtual information store, termed 101 the Management Information Base or MIB. Objects in the MIB are 102 defined using the mechanisms defined in the SMI. 104 This memo specifies a MIB module that is compliant to the SMIv2. A 105 MIB conforming to the SMIv1 can be produced through the appropriate 106 translations. The resulting translated MIB must be semantically 107 equivalent, except where objects or events are omitted because no 108 translation is possible (use of Counter64). Some machine readable 109 information in SMIv2 will be converted into textual descriptions in 110 SMIv1 during the translation process. However, this loss of machine 111 readable information is not considered to change the semantics of the 112 MIB. 114 3. Overview 116 The objects defined in this memo are used in conjunction with objects 117 defined in the Interfaces Group MIB [RFC2863], the SONET MIB 118 [SONETng], and the MAU MIB [MAU-MIB] to manage the WAN Interface 119 Sublayer (WIS) defined in [P802.3ae]. The WIS contains functions to 120 perform OC-192c/VC-4-64c framing and scrambling. It resides between 121 the PCS and PMA sublayers within a 10GBASE-W 10 Gb/s WAN-compatible 122 PHY and may be used in conjunction with any of the PCS, PMA, and PMD 123 sublayers that are defined in [P802.3ae] for 10GBASE-W PHYs. Three 124 types of 10GBASE-W PHYs are defined, distinguished by the type of 125 optics employed: 10GBASE-SW, 10GBASE-LW, and 10GBASE-EW. The 126 objects defined in this memo may be used to manage an Ethernet 127 interface employing any type of 10GBASE-W PHY. They do not apply to 128 any other kind of interface. In particular, they do not apply to 129 so-called Ethernet Line Terminating Equipment (ELTE) residing within 130 a SONET network element that uses the 10GBASE-W PMA/PMD sublayers but 131 otherwise acts as SONET Line Terminating Equipment (LTE). 133 The objects presented here -- along with those incorporated by 134 reference from the Interfaces Group MIB, the SONET MIB, and the MAU 135 MIB -- are intended to provide exact representations of the mandatory 136 attributes in the oWIS managed object class (i.e., the members of the 137 pWISBasic package) defined in Clause 30 and Annex 30A of [P802.3ae]. 138 They are also intended to provide approximate representations of the 139 optional attributes (i.e., the members of the pWISOptional package). 140 Some objects with no analogues in oWIS are defined to support WIS 141 testing features required by Clause 50 of [P802.3ae]. 143 3.1. Relationship to the SONET MIB 145 Since the Ethernet WAN Interface Sublayer was designed to be SONET- 146 compatible, information similar to that provided by most of the 147 members of the oWIS managed object class is available from objects 148 defined in the SONET MIB [SONETng]. Thus, the MIB module defined in 149 this memo is a sparse augmentation of the SONET MIB -- in other 150 words, every table defined here is an extension of some table in the 151 SONET MIB. An agent implementing the objects defined in this memo 152 MUST implement the objects required by the sonetCompliance2 153 conformance statement in the SONET MIB, and as further detailed in 154 the conformance statement in the MIB module defined in this memo. 156 It should be noted that some of the objects incorporated by reference 157 from the SONET MIB -- specifically, the threshold objects and 158 interval counter objects -- provide only approximate representations 159 of the corresponding oWIS attributes, as detailed in Section 3.6. An 160 alternative approach would have been to define new objects to exactly 161 match the oWIS definitions. That approach was rejected because the 162 SONET MIB objects are already used in deployed systems to manage the 163 SONET sublayers of ATM over SONET and PPP over SONET interfaces, and 164 it was deemed undesirable to use a different scheme to manage the 165 SONET sublayers of 10 Gb/s WAN-compatible Ethernet interfaces. Note 166 that the approach adopted by this memo requires no hardware support 167 beyond that mandated by [P802.3ae] subclause 50.3.10. 169 3.2. Relationship to the Ethernet-like Interfaces MIB 171 An interface which includes the Ethernet WIS is, by definition, an 172 Ethernet-like interface, and an agent implementing the objects 173 defined in this memo MUST implement the objects required by the 174 dot3Compliance2 compliance statement in the EtherLike-MIB. 176 3.3. Relationship to the 802.3 MAU MIB 178 Support for the mauModIfCompl2 compliance statement of the MAU-MIB 179 [MAU-MIB] is REQUIRED for all Ethernet-like interfaces. The MAU-MIB 180 is needed in order to allow applications to control and/or determine 181 the media type in use. That is important for devices than can 182 support both the 10GBASE-R 10 Gb/s LAN format (which does not include 183 the WIS) and the 10GBASE-W 10 Gb/s WAN format (which does include the 184 WIS). The MAU-MIB also provides the means to put a device in standby 185 mode or to reset it; the latter may be used to re-initialize the 186 WIS. 188 3.4. Use of the ifTable 190 This section specifies how the ifTable, as defined in [RFC2863], is 191 used for the Ethernet WIS application. 193 3.4.1. Layering Model 195 Ethernet interfaces that employ the WIS are layered as defined in 196 [P802.3ae]. The corresponding use of the ifTable [RFC2863] is shown 197 in the figure below. 199 _____________________________ _ 200 | LLC Layer | | 201 +_____________________________+ | 202 | MAC Layer | | 203 +-----------------------------+ > 1 ifEntry 204 | Reconciliation Sublayer | | ifType: ethernetCsmacd(6) 205 +-----------------------------+ | 206 | Physical Coding Sublayer | | 207 +-----------------------------+ + 208 | Path Layer | > 1 ifEntry 209 +-----------------------------+ + ifType: sonetPath(50) 210 | Line Layer | | 211 +-----------------------------+ | 212 | Section Layer | > 1 ifEntry 213 +-----------------------------+ | ifType: sonet(39) 214 | Physical Medium Layer | | 215 ----------------------------- - 217 Figure 1 - Use of ifTable for an Ethernet WIS port 219 The exact configuration and multiplexing of the layers is maintained 220 in the ifStackTable [RFC2863] and in the ifInvStackTable [RFC2864]. 222 3.4.2. Use of ifTable for LLC Layer/MAC Layer/Reconciliation 223 Sublayer/Physical Coding Sublayer 225 The ifTable MUST be used as specified in [ETHERIF] and [MAU-MIB] for 226 the LLC Layer/MAC Layer/Reconciliation Sublayer/Physical Coding 227 Sublayer. 229 3.4.3. Use of ifTable for SONET/SDH Path Layer 231 The ifTable MUST be used as specified in [SONETng] for the SONET/SDH 232 Path Layer. The value of ifHighSpeed is set to 9585. ifSpeed 233 reports a value of 4294967295. 235 3.4.4. Use of ifTable for SONET/SDH Medium/Section/Line Layer 237 The ifTable MUST be used as specified in [SONETng] for the SONET/SDH 238 Medium/Section/Line Layer. The value of ifHighSpeed is set to 9953. 239 ifSpeed reports a value of 4294967295. 241 3.5. SONET/SDH Terminology 243 The SONET/SDH terminology used in [P802.3ae] is mostly the same as in 244 [SONETng], but there are a few differences. In those cases the 245 definitions in [P802.3ae] take precedence. The specific differences 246 are as follows. 248 Unequipped 249 This defect is not defined by [P802.3ae]. An implementation that 250 supports it SHOULD report it by setting the sonetPathUnequipped 251 bit in the appropriate instance of sonetPathCurrentStatus. 253 Signal Label Mismatch 254 This defect is called Payload Label Mismatch (PLM) in [P802.3ae]. 255 It is reported by setting both the sonetPathSignalLabelMismatch 256 bit in the appropriate instance of sonetPathCurrentStatus 257 (defined in [SONETng]) and the etherWisPathPLM bit in the 258 corresponding instance of etherWisPathCurrentStatus (defined 259 below). 261 Loss of Codegroup Delineation 262 [P802.3ae] defines Loss of Codegroup Delineation (LCD) as 263 occurring when the Physical Coding Sublayer is unable to locate 264 64B/66B code group boundaries. There is no analogous defect 265 defined in [SONETng]. It is reported by setting the 266 etherWisPathLCD bit in the appropriate instance of the object 267 etherWisPathCurrentStatus defined below. 269 STS-Path Remote Defect Indication 270 [P802.3ae] mandates the use of ERDI-P (Enhanced Remote Defect 271 Indication - Path) defined in [T1.231] to signal remote server 272 defects (triggered by path AIS or path LOP) and remote payload 273 defects (triggered by Payload Label Mismatch or Loss of Codegroup 274 Delineation). [SONETng] defines the one-bit RDI-P (Remote Defect 275 Indication - Path), which signals remote server detects (i.e., 276 path AIS and path LOP) only. An implementation of the WIS MUST 277 set the sonetPathSTSRDI bit in the appropriate instance of 278 sonetPathCurrentStatus when it receives an ERDI-P server defect 279 indication from the remote end. Both ERDI-P payload defects and 280 ERDI-P server defects are reported in the object 281 etherWisFarEndPathCurrentStatus defined below. 283 Path Coding Violations 284 In [P802.3ae] the path layer CV count is based on block errors 285 and not BIP-8 errors, i.e., it is incremented only once for each 286 B3 byte that indicates incorrect parity, regardless of the number 287 of bits in error. Note that Section 8.4.5.1 of [T1.231] allows 288 either path BIP-8 errors or path block errors to be used for the 289 path layer error count. 291 3.6. Mapping of IEEE 802.3 Managed Objects 293 This section contains the mapping between oWIS managed objects 294 defined in [P802.3ae] and managed objects defined in this document 295 and in associated MIB modules, i.e., the IF-MIB [RFC2863], the 296 SONET-MIB [SONETng], and the MAU-MIB [MAU-MIB]. 298 IEEE 802.3 Managed Object Corresponding SNMP Object 300 oWIS - pWISBasic package 301 aWISID IF-MIB - ifIndex 302 aSectionStatus SONET-MIB - sonetSectionCurrentStatus 303 aLineStatus SONET-MIB - sonetLineCurrentStatus 304 aPathStatus etherWisPathCurrentStatus 305 aFarEndPathStatus etherWisFarEndPathCurrentStatus 307 oWIS - pWISOptional package 308 aSectionSESThreshold SONET-MIB - sonetSESthresholdSet 309 aSectionSESs SONET-MIB - sonetSectionCurrentSESs + 310 sonetSectionIntervalSESs 311 aSectionESs SONET-MIB - sonetSectionCurrentESs + 312 sonetSectionIntervalESs 313 aSectionSEFSs SONET-MIB - sonetSectionCurrentSEFSs + 314 sonetSectionIntervalSEFSs 315 aSectionCVs SONET-MIB - sonetSectionCurrentCVs + 316 sonetSectionIntervalCVs 317 aJ0ValueTX etherWisSectionCurrentJ0Transmitted 318 aJ0ValueRX etherWisSectionCurrentJ0Received 319 aLineSESThreshold SONET-MIB - sonetSESthresholdSet 320 aLineSESs SONET-MIB - sonetLineCurrentSESs + 321 sonetLineIntervalSESs 322 aLineESs SONET-MIB - sonetLineCurrentESs + 323 sonetLineIntervalESs 324 aLineCVs SONET-MIB - sonetLineCurrentCVs + 325 sonetLineIntervalCVs 326 aFarEndLineSESs SONET-MIB - sonetFarEndLineCurrentSESs + 327 sonetFarEndLineIntervalSESs 328 aFarEndLineESs SONET-MIB - sonetFarEndLineCurrentESs + 329 sonetFarEndLineIntervalESs 330 aFarEndLineCVs SONET-MIB - sonetFarEndLineCurrentCVs + 331 sonetFarEndLineIntervalCVs 332 aPathSESThreshold SONET-MIB - sonetSESthresholdSet 333 aPathSESs SONET-MIB - sonetPathCurrentSESs + 334 sonetPathIntervalSESs 335 aPathESs SONET-MIB - sonetPathCurrentESs + 336 sonetPathIntervalESs 337 aPathCVs SONET-MIB - sonetPathCurrentCVs + 338 sonetPathIntervalCVs 339 aJ1ValueTX etherWisPathCurrentJ1Transmitted 340 aJ1ValueRX etherWisPathCurrentJ1Received 341 aFarEndPathSESs SONET-MIB - sonetFarEndPathCurrentSESs + 342 sonetFarEndPathIntervalSESs 343 aFarEndPathESs SONET-MIB - sonetFarEndPathCurrentESs + 344 sonetFarEndPathIntervalESs 345 aFarEndPathCVs SONET-MIB - sonetFarEndPathCurrentCVs + 346 sonetFarEndPathIntervalCVs 348 Please note that the definitions of the threshold objects and counter 349 objects imported from the SONET-MIB do not exactly match the 350 definitions of the corresponding IEEE 802.3 objects. The specific 351 differences are as follows: 353 IEEE 802.3 Managed Object How Corresponding SNMP Object Differs 355 oWIS - pWISOptional package 356 aSectionSESThreshold This object is defined in [P802.3ae] 357 as an integer with one instance per 358 interface. sonetSESthresholdSet 359 is an enumerated value that has one 360 instance per network element; it 361 controls the thresholds for all layers 362 simultaneously and allows only certain 363 discrete values to be selected. 364 aSectionSESs This object is defined in [P802.3ae] as 365 a generalized nonresetable counter. 366 The objects sonetSectionCurrentSESs and 367 sonetSectionIntervalSESs are 15-minute 368 interval counters. 369 aSectionESs This object is defined as a generalized 370 nonresetable counter in [P802.3ae]. 371 The objects sonetSectionCurrentESs and 372 sonetSectionIntervalESs are 15-minute 373 interval counters. 374 aSectionSEFSs This object is defined as a generalized 375 nonresetable counter in [P802.3ae]. 376 The objects sonetSectionCurrentSEFSs and 377 sonetSectionIntervalSEFSs are 15-minute 378 interval counters. 379 aSectionCVs This object is defined as a generalized 380 nonresetable counter in [P802.3ae], and 381 it is not subject to inhibiting. The 382 objects sonetSectionCurrentCVs and 383 sonetSectionIntervalCVs are 15-minute 384 interval counters, and they are 385 inhibited (not incremented) during 386 one-second intervals that qualify as 387 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. 488 aPathCVs This object is defined as a generalized 489 nonresetable counter in [P802.3ae], and 490 it is not subject to inhibiting. The 491 objects sonetPathCurrentCVs and 492 sonetPathIntervalCVs are 15-minute 493 interval counters, and they are 494 inhibited (not incremented) during 495 one-second intervals that qualify 496 either as severely errored seconds 497 or as unavailable seconds. 498 aFarEndPathSESs This object is defined as a generalized 499 nonresetable counter in [P802.3ae], and 500 it is not subject to inhibiting. The 501 objects sonetFarEndPathCurrentSESs and 502 sonetFarEndPathIntervalSESs are 503 15-minute interval counters, and they 504 are inhibited (not incremented) during 505 one-second intervals that qualify as 506 unavailable seconds. In addition, 507 [P802.3ae] includes far-end PLM-P and 508 LCD-P defects in the criteria for 509 declaring far-end path layer severely 510 errored seconds, while [SONETng] does 511 not. 512 aFarEndPathESs This object is defined as a generalized 513 nonresetable counter in [P802.3ae], and 514 it is not subject to inhibiting. The 515 objects sonetFarEndPathCurrentESs and 516 sonetFarEndPathIntervalESs are 15-minute 517 interval counters, and they are 518 inhibited (not incremented) during 519 one-second intervals that qualify as 520 unavailable seconds. In addition, 521 [P802.3ae] includes far-end PLM-P and 522 LCD-P defects in the criteria for 523 declaring far-end path layer errored 524 seconds, while [SONETng] does not. 525 aFarEndPathCVs This object is defined as a generalized 526 nonresetable counter in [P802.3ae], and 527 it is not subject to inhibiting. The 528 objects sonetFarEndPathCurrentCVs and 529 sonetFarEndPathIntervalCVs are 15-minute 530 interval counters, and they are 531 inhibited (not incremented) during 532 one-second intervals that qualify 533 either as severely errored seconds 534 or as unavailable seconds. 536 Please note that despite the differences in semantics between the 537 threshold objects and counter objects imported from the SONET-MIB and 538 the corresponding IEEE 802.3 objects, the hardware support mandated 539 by [P802.3ae] subclause 50.3.10 suffices for both. See Appendix A 540 for details. 542 3.7. Mapping of SNMP Objects to WIS Station Management Registers 544 Some of the objects defined in this memo or incorporated by reference 545 from the SONET-MIB [SONETng] or the MAU-MIB [MAU-MIB] require WIS- 546 specific hardware support. [P802.3ae] subclause 50.3.10 specifies 547 WIS management interface requirements, including a required subset of 548 the WIS MDIO (Management Data Input/Output) registers defined in 549 [P802.3ae] subclause 45.2.2. The table below provides a cross- 550 reference between those managed objects and the WIS MDIO registers 551 from the subset in [P802.3ae] subclause 50.3.10 required to support 552 them. Note that the MDIO interface is optional; however, if it is 553 not implemented, then the capabilities of the required register 554 subset must be provided by other means. 556 SNMP Object WIS MDIO Register(s) 558 ETHER-WIS - etherWisDeviceTestPatternType 10G WIS Control 2 559 ETHER-WIS - etherWisDeviceRxTestPatternMode 10G WIS Control 2 560 ETHER-WIS - etherWisDeviceTxTestPatternMode 10G WIS Control 2 562 SONET-MIB - sonetMediumType none required 563 SONET-MIB - sonetMediumTimeElapsed none required 564 SONET-MIB - sonetMediumValidIntervals none required 565 SONET-MIB - sonetMediumLineCoding none required 566 SONET-MIB - sonetMediumLineType none required 567 SONET-MIB - sonetMediumCircuitIdentifier none required 568 SONET-MIB - sonetMediumInvalidIntervals none required 569 SONET-MIB - sonetMediumLoopbackConfig none required 570 SONET-MIB - sonetSESthresholdSet none required 572 ETHER-WIS - etherWisSectionCurrentJ0Transmitted 10G WIS J0 Tx 573 ETHER-WIS - etherWisSectionCurrentJ0Received 10G WIS J0 Rx 575 SONET-MIB - sonetSectionCurrentStatus 10G WIS Status 3 576 SONET-MIB - sonetSectionCurrentESs \ 577 SONET-MIB - sonetSectionCurrentSESs \ 578 SONET-MIB - sonetSectionCurrentSEFSs | 10G WIS Status 3 579 SONET-MIB - sonetSectionCurrentCVs | + 580 SONET-MIB - sonetSectionIntervalESs | 10G WIS Section 581 SONET-MIB - sonetSectionIntervalSESs | BIP Error Count 582 SONET-MIB - sonetSectionIntervalSEFSs / 583 SONET-MIB - sonetSectionIntervalCVs / 584 SONET-MIB - sonetSectionIntervalValidData none required 585 SONET-MIB - sonetLineCurrentStatus 10G WIS Status 3 586 SONET-MIB - sonetLineCurrentESs \ 587 SONET-MIB - sonetLineCurrentSESs \ 588 SONET-MIB - sonetLineCurrentCVs | 10G WIS Status 3 589 SONET-MIB - sonetLineCurrentUASs | + 590 SONET-MIB - sonetLineIntervalESs | 10G WIS Line 591 SONET-MIB - sonetLineIntervalSESs | BIP Errors 592 SONET-MIB - sonetLineIntervalCVs / 593 SONET-MIB - sonetLineIntervalUASs / 594 SONET-MIB - sonetLineIntervalValidData none required 596 SONET-MIB - sonetFarEndLineCurrentESs \ 597 SONET-MIB - sonetFarEndLineCurrentSESs \ 598 SONET-MIB - sonetFarEndLineCurrentCVs | 10G WIS Status 3 599 SONET-MIB - sonetFarEndLineCurrentUASs | + 600 SONET-MIB - sonetFarEndLineIntervalESs | 10G WIS Far End 601 SONET-MIB - sonetFarEndLineIntervalSESs | Line BIP Errors 602 SONET-MIB - sonetFarEndLineIntervalCVs / 603 SONET-MIB - sonetFarEndLineIntervalUASs / 604 SONET-MIB - sonetFarEndLineIntervalValidData 10G WIS Status 3 606 ETHER-WIS - etherWisPathCurrentStatus 10G WIS Status 3 607 ETHER-WIS - etherWisPathCurrentJ1Transmitted 10G WIS J1 Tx 608 ETHER-WIS - etherWisPathCurrentJ1Received 10G WIS J1 Rx 610 SONET-MIB - sonetPathCurrentWidth none required 611 SONET-MIB - sonetPathCurrentStatus 10G WIS Status 3 612 SONET-MIB - sonetPathCurrentESs \ 613 SONET-MIB - sonetPathCurrentSESs \ 614 SONET-MIB - sonetPathCurrentCVs | 10G WIS Status 3 615 SONET-MIB - sonetPathCurrentUASs | + 616 SONET-MIB - sonetPathIntervalESs | 10G WIS 617 SONET-MIB - sonetPathIntervalSESs | Path Block 618 SONET-MIB - sonetPathIntervalCVs / Error Count 619 SONET-MIB - sonetPathIntervalUASs / 620 SONET-MIB - sonetPathIntervalValidData none required 622 ETHER-WIS - etherWisFarEndPathCurrentStatus 10G WIS Status 3 624 SONET-MIB - sonetFarEndPathCurrentESs \ 625 SONET-MIB - sonetFarEndPathCurrentSESs \ 626 SONET-MIB - sonetFarEndPathCurrentCVs | 10G WIS Status 3 627 SONET-MIB - sonetFarEndPathCurrentUASs | + 628 SONET-MIB - sonetFarEndPathIntervalESs | 10G WIS Far End 629 SONET-MIB - sonetFarEndPathIntervalSESs | Path Block 630 SONET-MIB - sonetFarEndPathIntervalCVs / Error Count 631 SONET-MIB - sonetFarEndPathIntervalUASs / 632 SONET-MIB - sonetFarEndPathIntervalValidData 10G WIS Status 3 633 MAU-MIB - ifMauIfIndex none required 634 MAU-MIB - ifMauIndex none required 635 MAU-MIB - ifMauType 10G WIS Control 2 636 MAU-MIB - ifMauStatus WIS Control 1 637 MAU-MIB - ifMauMediaAvailable \ WIS Status 1 + 638 MAU-MIB - ifMauMediaAvailableStateExits / 10G WIS Status 3 639 MAU-MIB - ifMauJabberState none required 640 MAU-MIB - ifMauJabberingStateEnters none required 641 MAU-MIB - ifMauFalseCarriers none required 642 MAU-MIB - ifMauDefaultType 10G WIS Control 2 643 MAU-MIB - ifMauAutoNegSupported none required 644 MAU-MIB - ifMauTypeListBits 10G WIS Status 2 646 3.8. Structure of the MIB Module 648 Four tables are defined in this MIB module. 650 3.8.1. etherWisDeviceTable 652 The purpose of this table is to define managed objects to control the 653 WIS test pattern mode. These objects are required to support 654 mandatory WIS test features required by Clause 50 of [P802.3ae]. 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 SHALL 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 SHALL 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 SHALL 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 SHALL 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 "200111202123Z" -- November 20, 2001 723 ORGANIZATION "IETF Hubmib and AToMMIB Working Groups" 724 CONTACT-INFO 725 "Hubmib WG: 726 http://www.ietf.org/html.charters/hubmib-charter.html 728 AToMMIB WG: 729 http://www.ietf.org/html.charters/atommib-charter.html 731 Editor: C. M. Heard 732 Postal: 600 Rainbow Dr. #141 733 Mountain View, CA 94041-2542 734 USA 735 Tel: +1 650-964-8391 736 E-mail: heard@pobox.com" 738 DESCRIPTION 739 "The objects in this MIB module are used in conjunction 740 with objects in the SONET-MIB and the MAU-MIB to manage 741 the Ethernet WAN Interface Sublayer (WIS). 743 The following reference is used throughout this MIB module: 745 [IEEE 802.3 Std] refers to: 746 IEEE Std 802.3, 2000 Edition: 'IEEE Standard 747 for Information technology - 748 Telecommunications and information exchange 749 between systems - Local and metropolitan 750 area networks - Specific requirements - 751 Part 3: Carrier sense multiple access with 752 collision detection (CSMA/CD) access method 753 and physical layer specifications', as 754 amended by IEEE Draft P802.3ae/D3.3: 755 'Supplement to Carrier Sense Multiple Access 756 with Collision Detection (CSMA/CD) Access 757 Method & Physical Layer Specifications - 758 Media Access Control (MAC) Parameters, 759 Physical Layer, and Management Parameters 760 for 10 Gb/s Operation', October 23, 2001. 762 Of particular interest are Clause 50, 'WAN Interface 763 Sublayer (WIS), type 10GBASE-W', Clause 30, '10Mb/s, 764 100Mb/s, 1000Mb/s, and 10Gb/s MAC Control, and Link 765 Aggregation Management', and Clause 45, 'Management 766 Data Input/Output (MDIO) Interface'." 768 REVISION "200111202123Z" -- November 20, 2001 769 DESCRIPTION "Initial version." 771 ::= { transmission XXX } -- to be assigned by IANA 773 -- The main sections of the module 775 etherWisObjects OBJECT IDENTIFIER ::= { etherWisMIB 1 } 777 etherWisObjectsPath OBJECT IDENTIFIER ::= { etherWisMIB 2 } 779 etherWisConformance OBJECT IDENTIFIER ::= { etherWisMIB 3 } 781 -- groups in the Ethernet WIS MIB module 783 etherWisDevice OBJECT IDENTIFIER ::= { etherWisObjects 1 } 785 etherWisSection OBJECT IDENTIFIER ::= { etherWisObjects 2 } 787 etherWisPath OBJECT IDENTIFIER ::= { etherWisObjectsPath 1 } 789 etherWisFarEndPath OBJECT IDENTIFIER ::= { etherWisObjectsPath 2 } 790 -- The Device group 792 -- These objects provide WIS extensions to 793 -- the SONET-MIB Medium Group. 795 etherWisDeviceTable OBJECT-TYPE 796 SYNTAX SEQUENCE OF EtherWisDeviceEntry 797 MAX-ACCESS not-accessible 798 STATUS current 799 DESCRIPTION 800 "The table for Ethernet WIS devices" 801 ::= { etherWisDevice 1 } 803 etherWisDeviceEntry OBJECT-TYPE 804 SYNTAX EtherWisDeviceEntry 805 MAX-ACCESS not-accessible 806 STATUS current 807 DESCRIPTION 808 "An entry in the Ethernet WIS device table. For each 809 instance of this object there shall be a corresponding 810 instance of sonetMediumEntry." 811 INDEX { ifIndex } 812 ::= { etherWisDeviceTable 1 } 814 EtherWisDeviceEntry ::= 815 SEQUENCE { 816 etherWisDeviceTestPatternType INTEGER, 817 etherWisDeviceRxTestPatternMode INTEGER, 818 etherWisDeviceTxTestPatternMode INTEGER 819 } 821 etherWisDeviceTestPatternType OBJECT-TYPE 822 SYNTAX INTEGER { 823 mixedFrequency(0), 824 squareWave(1) 825 } 826 MAX-ACCESS read-write 827 STATUS current 828 DESCRIPTION 829 "This variable controls the type of test pattern. The value 830 mixedFrequency(0) selects the framed mixed frequency test 831 pattern specified in [IEEE 802.3 Std.] subclause 50.3.8.2. 832 The value squareWave(1) selects the unframed square wave test 833 pattern specified in [IEEE 802.3 Std.] subclause 50.3.8.1." 834 REFERENCE 835 "[IEEE 802.3 Std.], 50.3.8, WIS test pattern generator and 836 checker, 45.2.2.6, 10G WIS Control 2 register (2.7), and 837 45.2.2.6.1, Test pattern (2.7.3)." 838 ::= { etherWisDeviceEntry 1 } 840 etherWisDeviceRxTestPatternMode OBJECT-TYPE 841 SYNTAX INTEGER { 842 disabled(0), 843 enabled(1) 844 } 845 MAX-ACCESS read-write 846 STATUS current 847 DESCRIPTION 848 "This variable controls the receive test pattern mode. 849 The value disabled(0) sets the WIS receive path into 850 normal mode. The value enabled(1) sets the WIS receive 851 path into test pattern mode. An attempt to set this 852 object to enabled(1) when the corresponding instance 853 of ifAdminState has the value up(1) SHALL be rejected 854 with the error inconsistentValue. An attempt to set the 855 corresponding instance of ifAdminStatus to the value 856 up(1) when an instance of this object has the value 857 enabled(1) SHALL be rejected with the error 858 inconsistentValue." 859 REFERENCE 860 "[IEEE 802.3 Std.], 50.3.8, WIS test pattern generator and 861 checker, 45.2.2.6, 10G WIS Control 2 register (2.7), and 862 45.2.2.6.2, Receive test pattern mode (2.7.2)." 863 ::= { etherWisDeviceEntry 2 } 865 etherWisDeviceTxTestPatternMode OBJECT-TYPE 866 SYNTAX INTEGER { 867 disabled(0), 868 enabled(1) 869 } 870 MAX-ACCESS read-write 871 STATUS current 872 DESCRIPTION 873 "This variable controls the transmit test pattern mode. 874 The value disabled(0) set the WIS transmit path into 875 normal mode. The value enabled(1) sets the WIS transmit 876 path into test pattern mode. An attempt to set this 877 object to enabled(1) when the corresponding instance 878 of ifAdminState has the value up(1) SHALL be rejected 879 with the error inconsistentValue. An attempt to set the 880 corresponding instance of ifAdminStatus to the value 881 up(1) when an instance of this object has the value 882 enabled(1) SHALL be rejected with the error 883 inconsistentValue." 884 REFERENCE 885 "[IEEE 802.3 Std.], 50.3.8, WIS test pattern generator and 886 checker, 45.2.2.6, 10G WIS Control 2 register (2.7), and 887 45.2.2.6.3, Transmit test pattern mode (2.7.1)." 888 ::= { etherWisDeviceEntry 3 } 890 -- The Section group 892 -- These objects provide WIS extensions to 893 -- the SONET-MIB Section Group. 895 etherWisSectionCurrentTable OBJECT-TYPE 896 SYNTAX SEQUENCE OF EtherWisSectionCurrentEntry 897 MAX-ACCESS not-accessible 898 STATUS current 899 DESCRIPTION 900 "The table for the current state of Ethernet WIS sections." 901 ::= { etherWisSection 1 } 903 etherWisSectionCurrentEntry OBJECT-TYPE 904 SYNTAX EtherWisSectionCurrentEntry 905 MAX-ACCESS not-accessible 906 STATUS current 907 DESCRIPTION 908 "An entry in the etherWisSectionCurrentTable. For each 909 instance of this object there shall be a corresponding 910 instance of sonetSectionCurrentEntry." 911 INDEX { ifIndex } 912 ::= { etherWisSectionCurrentTable 1 } 914 EtherWisSectionCurrentEntry ::= 915 SEQUENCE { 916 etherWisSectionCurrentJ0Transmitted INTEGER, 917 etherWisSectionCurrentJ0Received INTEGER 918 } 920 etherWisSectionCurrentJ0Transmitted OBJECT-TYPE 921 SYNTAX INTEGER ( 0..255 ) 922 MAX-ACCESS read-write 923 STATUS current 924 DESCRIPTION 925 "This is the single-octet section trace message 926 that is to be transmitted in the J0 byte. The 927 value SHOULD be set to '01'h when the section 928 trace function is not used, and the implementation 929 SHOULD use that value as a default if no other 930 value has been set." 931 REFERENCE 932 "[IEEE 802.3 Std.], 30.8.1.1.8, aJ0ValueTX." 933 ::= { etherWisSectionCurrentEntry 1 } 935 etherWisSectionCurrentJ0Received OBJECT-TYPE 936 SYNTAX INTEGER ( 0..255 ) 937 MAX-ACCESS read-only 938 STATUS current 939 DESCRIPTION 940 "This is the single-octet section trace message 941 that was most recently received in the J0 byte." 942 REFERENCE 943 "[IEEE 802.3 Std.], 30.8.1.1.9, aJ0ValueRX." 944 ::= { etherWisSectionCurrentEntry 2 } 946 -- The Path group 948 -- These objects provide WIS extensions to 949 -- the SONET-MIB Path Group. 951 etherWisPathCurrentTable OBJECT-TYPE 952 SYNTAX SEQUENCE OF EtherWisPathCurrentEntry 953 MAX-ACCESS not-accessible 954 STATUS current 955 DESCRIPTION 956 "The table for the current state of Ethernet WIS paths." 957 ::= { etherWisPath 1 } 959 etherWisPathCurrentEntry OBJECT-TYPE 960 SYNTAX EtherWisPathCurrentEntry 961 MAX-ACCESS not-accessible 962 STATUS current 963 DESCRIPTION 964 "An entry in the etherWisPathCurrentTable. For each 965 instance of this object there shall be a corresponding 966 instance of sonetPathCurrentEntry." 967 INDEX { ifIndex } 968 ::= { etherWisPathCurrentTable 1 } 970 EtherWisPathCurrentEntry ::= 971 SEQUENCE { 972 etherWisPathCurrentStatus BITS, 973 etherWisPathCurrentJ1Transmitted OCTET STRING, 974 etherWisPathCurrentJ1Received OCTET STRING 975 } 977 etherWisPathCurrentStatus OBJECT-TYPE 978 SYNTAX BITS { 979 etherWisPathLOP(0), 980 etherWisPathAIS(1), 981 etherWisPathPLM(2), 982 etherWisPathLCD(3) 983 } 984 MAX-ACCESS read-write 985 STATUS current 986 DESCRIPTION 987 "This variable indicates the current status of the 988 path payload with a bit map that can indicate multiple 989 defects at once. The bit positions are assigned as 990 follows: 992 etherWisPathLOP(0) 993 This bit is set to indicate that an 994 LOP-P (Loss of Pointer - Path) defect 995 is being experienced. Note: when this 996 bit is set, sonetPathSTSLOP MUST be set 997 in the corresponding instance of 998 sonetPathCurrentStatus. 1000 etherWisPathAIS(1) 1001 This bit is set to indicate that an 1002 AIS-P (Alarm Indication Signal - Path) 1003 defect is being experienced. Note: when 1004 this bit is set, sonetPathSTSAIS MUST be 1005 set in the corresponding instance of 1006 sonetPathCurrentStatus. 1008 etherWisPathPLM(1) 1009 This bit is set to indicate that a 1010 PLM-P (Payload Label Mismatch - Path) 1011 defect is being experienced. Note: when 1012 this bit is set, sonetPathSignalLabelMismatch 1013 MUST be set in the corresponding instance of 1014 sonetPathCurrentStatus. 1016 etherWisPathLCD(3) 1017 This bit is set to indicate that an 1018 LCD-P (Loss of Codegroup Delination - Path) 1019 defect is being experienced. Since this 1020 defect is detected by the PCS and not by 1021 the path layer itself, there is no 1022 corresponding bit in sonetPathCurrentStatus." 1023 REFERENCE 1024 "[IEEE 802.3 Std.], 30.8.1.1.18, aPathStatus." 1025 ::= { etherWisPathCurrentEntry 1 } 1027 etherWisPathCurrentJ1Transmitted OBJECT-TYPE 1028 SYNTAX OCTET STRING (SIZE (16)) 1029 MAX-ACCESS read-write 1030 STATUS current 1031 DESCRIPTION 1032 "This is the 16-octet path message that is to 1033 be transmitted in the J1 byte. The value SHOULD 1034 be fifteen octets of '00'h followed by '89'h 1035 (or some cyclic shift thereof) when the path 1036 trace function is not used, and the implementation 1037 SHOULD use that value (or a cyclic shift thereof) 1038 as a default if no other value has been set." 1039 REFERENCE 1040 "[IEEE 802.3 Std.], 30.8.1.1.23, aJ1ValueTX." 1041 ::= { etherWisPathCurrentEntry 2 } 1043 etherWisPathCurrentJ1Received OBJECT-TYPE 1044 SYNTAX OCTET STRING (SIZE (16)) 1045 MAX-ACCESS read-only 1046 STATUS current 1047 DESCRIPTION 1048 "This is the 16-octet path trace message that 1049 was most recently received in the J1 byte." 1050 REFERENCE 1051 "[IEEE 802.3 Std.], 30.8.1.1.24, aJ1ValueRX." 1052 ::= { etherWisPathCurrentEntry 3 } 1054 -- The Far End Path group 1056 -- These objects provide WIS extensions to 1057 -- the SONET-MIB Far End Path Group. 1059 etherWisFarEndPathCurrentTable OBJECT-TYPE 1060 SYNTAX SEQUENCE OF EtherWisFarEndPathCurrentEntry 1061 MAX-ACCESS not-accessible 1062 STATUS current 1063 DESCRIPTION 1064 "The table for the current far-end state of Ethernet WIS 1065 paths." 1066 ::= { etherWisFarEndPath 1 } 1068 etherWisFarEndPathCurrentEntry OBJECT-TYPE 1069 SYNTAX EtherWisFarEndPathCurrentEntry 1070 MAX-ACCESS not-accessible 1071 STATUS current 1072 DESCRIPTION 1073 "An entry in the etherWisFarEndPathCurrentTable. For each 1074 instance of this object there shall be a corresponding 1075 instance of sonetFarEndPathCurrentEntry." 1076 INDEX { ifIndex } 1077 ::= { etherWisFarEndPathCurrentTable 1 } 1079 EtherWisFarEndPathCurrentEntry ::= 1080 SEQUENCE { 1081 etherWisFarEndPathCurrentStatus BITS 1082 } 1084 etherWisFarEndPathCurrentStatus OBJECT-TYPE 1085 SYNTAX BITS { 1086 etherWisFarEndPayloadDefect(0), 1087 etherWisFarEndServerDefect(1) 1088 } 1089 MAX-ACCESS read-write 1090 STATUS current 1091 DESCRIPTION 1092 "This variable indicates the current status at the 1093 far end of the path using a bit map that can indicate 1094 multiple defects at once. The bit positions are 1095 assigned as follows: 1097 etherWisFarEndPayloadDefect(0) 1098 A far end payload defect (i.e., far end 1099 PLM-P or LCD-P) is currently being signalled 1100 in G1 bits 5-7. 1102 etherWisFarEndServerDefect(1) 1103 A far end server defect (i.e., far end 1104 LOP-P or AIS-P) is currently being signalled 1105 in G1 bits 5-7. Note: when this bit is set, 1106 sonetPathSTSRDI MUST be set in the corresponding 1107 instance of sonetPathCurrentStatus." 1108 REFERENCE 1109 "[IEEE 802.3 Std.], 30.8.1.1.25, aFarEndPathStatus." 1110 ::= { etherWisFarEndPathCurrentEntry 1 } 1112 -- 1113 -- Conformance Statements 1114 -- 1116 etherWisGroups OBJECT IDENTIFIER ::= { etherWisConformance 1 } 1118 etherWisCompliances OBJECT IDENTIFIER ::= { etherWisConformance 2 } 1120 -- Object Groups 1122 etherWisDeviceGroup OBJECT-GROUP 1123 OBJECTS { 1124 etherWisDeviceTestPatternType, 1125 etherWisDeviceRxTestPatternMode, 1126 etherWisDeviceTxTestPatternMode 1127 } 1128 STATUS current 1129 DESCRIPTION 1130 "A collection of objects that control test 1131 features required of all WIS devices." 1132 ::= { etherWisGroups 1 } 1134 etherWisSectionGroup OBJECT-GROUP 1135 OBJECTS { 1136 etherWisSectionCurrentJ0Transmitted, 1137 etherWisSectionCurrentJ0Received 1138 } 1139 STATUS current 1140 DESCRIPTION 1141 "A collection of objects that provide 1142 required information about a WIS section." 1143 ::= { etherWisGroups 2 } 1145 etherWisPathGroup OBJECT-GROUP 1146 OBJECTS { 1147 etherWisPathCurrentStatus, 1148 etherWisPathCurrentJ1Transmitted, 1149 etherWisPathCurrentJ1Received 1150 } 1151 STATUS current 1152 DESCRIPTION 1153 "A collection of objects that provide 1154 required information about a WIS path." 1155 ::= { etherWisGroups 3 } 1157 etherWisFarEndPathGroup OBJECT-GROUP 1158 OBJECTS { 1159 etherWisFarEndPathCurrentStatus 1160 } 1161 STATUS current 1162 DESCRIPTION 1163 "A collection of objects that provide required 1164 information about the far end of a WIS path." 1165 ::= { etherWisGroups 4 } 1167 -- Compliance Statements 1169 etherWisCurrentCompliance MODULE-COMPLIANCE 1170 STATUS current 1171 DESCRIPTION 1172 "The compliance statement for this module." 1174 MODULE -- this module 1175 MANDATORY-GROUPS { 1176 etherWisDeviceGroup, 1177 etherWisSectionGroup, 1178 etherWisPathGroup, 1179 etherWisFarEndPathGroup 1180 } 1182 MODULE SONET-MIB 1183 MANDATORY-GROUPS { 1184 sonetMediumStuff2, 1185 sonetSectionStuff2, 1186 sonetLineStuff2, 1187 sonetFarEndLineStuff2, 1188 sonetPathStuff2, 1189 sonetFarEndPathStuff2 1190 } 1192 OBJECT sonetMediumType 1193 SYNTAX INTEGER { 1194 sonet(1) 1195 } 1196 MIN-ACCESS read-only 1197 DESCRIPTION 1198 "Write access is not required, nor is support 1199 for any value other than sonet(1)." 1201 OBJECT sonetMediumLineCoding 1202 SYNTAX INTEGER { 1203 sonetMediumNRZ(4) 1204 } 1205 MIN-ACCESS read-only 1206 DESCRIPTION 1207 "Write access is not required, nor is support 1208 for any value other than sonetMediumNRZ(4)." 1210 OBJECT sonetMediumLineType 1211 MIN-ACCESS read-only 1212 DESCRIPTION 1213 "Write access is not required." 1215 OBJECT sonetMediumCircuitIdentifier 1216 MIN-ACCESS read-only 1217 DESCRIPTION 1218 "Write access is not required." 1220 OBJECT sonetMediumLoopbackConfig 1221 SYNTAX BITS { 1222 sonetNoLoop(0), 1223 sonetFacilityLoop(1) 1224 } 1225 MIN-ACCESS read-only 1226 DESCRIPTION 1227 "Write access is not required, nor is support for values 1228 other than sonetNoLoop(0) and sonetFacilityLoop(1)." 1230 OBJECT sonetSESthresholdSet 1231 MIN-ACCESS read-only 1232 DESCRIPTION 1233 "Write access is not required, and only one 1234 of the enumerated values need be supported." 1236 OBJECT sonetPathCurrentWidth 1237 SYNTAX INTEGER { 1238 sts192cSTM64(6) 1239 } 1240 MIN-ACCESS read-only 1241 DESCRIPTION 1242 "Write access is not required, nor is support 1243 for any value other than sts192cSTM64(6)." 1245 ::= { etherWisCompliances 1 } 1247 END 1249 5. Acknowledgments 1251 This document is a product of the IETF Hubmib and AToMMIB Working 1252 Groups. It builds upon the work of the IEEE P802.3ae 10 Gigabit 1253 Ethernet Task Force. 1255 6. Security Considerations 1257 There are a number of management objects defined in this MIB that 1258 have a MAX-ACCESS clause of read-write and/or read-create. Such 1259 objects may be considered sensitive or vulnerable in some network 1260 environments. The support for SET operations in a non-secure 1261 environment without proper protection can have a negative effect on 1262 network operations. 1264 SNMPv1 by itself is not a secure environment. Even if the network 1265 itself is secure (for example by using IPSec), even then, there is no 1266 control as to who on the secure network is allowed to access and 1267 GET/SET (read/change/create/delete) the objects in this MIB. 1269 It is recommended that the implementers consider the security 1270 features as provided by the SNMPv3 framework. Specifically, the use 1271 of the User-based Security Model RFC 2574 [RFC2574] and the View- 1272 based Access Control Model RFC 2575 [RFC2575] is recommended. 1274 It is then a customer/user responsibility to ensure that the SNMP 1275 entity giving access to an instance of this MIB, is properly 1276 configured to give access to the objects only to those principals 1277 (users) that have legitimate rights to indeed GET or SET 1278 (change/create/delete) them. 1280 7. References 1282 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture 1283 for Describing SNMP Management Frameworks", RFC 2571, April 1284 1999. 1286 [RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification 1287 of Management Information for TCP/IP-based Internets", STD 1288 16, RFC 1155, May 1990. 1290 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD 1291 16, RFC 1212, March 1991. 1293 [RFC1215] M. Rose, "A Convention for Defining Traps for use with the 1294 SNMP", RFC 1215, March 1991. 1296 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1297 Rose, M., and S. Waldbusser, "Structure of Management 1298 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1299 1999. 1301 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1302 Rose, M., and S. Waldbusser, "Textual Conventions for 1303 SMIv2", STD 58, RFC 2579, April 1999. 1305 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 1306 Rose, M., and S. Waldbusser, "Conformance Statements for 1307 SMIv2", STD 58, RFC 2580, April 1999. 1309 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple 1310 Network Management Protocol", STD 15, RFC 1157, May 1990. 1312 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1313 "Introduction to Community-based SNMPv2", RFC 1901, January 1314 1996. 1316 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1317 "Transport Mappings for Version 2 of the Simple Network 1318 Management Protocol (SNMPv2)", RFC 1906, January 1996. 1320 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message 1321 Processing and Dispatching for the Simple Network Management 1322 Protocol (SNMP)", RFC 2572, April 1999. 1324 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model 1325 (USM) for version 3 of the Simple Network Management 1326 Protocol (SNMPv3)", RFC 2574, April 1999. 1328 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1329 "Protocol Operations for Version 2 of the Simple Network 1330 Management Protocol (SNMPv2)", RFC 1905, January 1996. 1332 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", 1333 RFC 2573, April 1999. 1335 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 1336 Access Control Model (VACM) for the Simple Network 1337 Management Protocol (SNMP)", RFC 2575, April 1999. 1339 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 1340 "Introduction to Version 3 of the Internet-standard Network 1341 Management Framework", RFC 2570, April 1999. 1343 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1344 Requirements Levels", BCP 14, RFC 2119, March 1997. 1346 [RFC2863] McCloghrie, K., and F. Kastenholz, "The Interfaces Group 1347 MIB", RFC 2863, June 2000. 1349 [RFC2864] McCloghrie, K., and G. Hanson, "The Inverted Stack Table 1350 Extension to the Interfaces Group MIB", RFC 2864, June 2000. 1352 [SONETng] Tesink, K., "Definitions of Managed Objects for the 1353 SONET/SDH Interface Type", rfc2558 update (forthcoming), 1354 work in progress. 1356 [T1.231] American National Standard for Telecommunications - Digital 1357 Hierarchy - Layer 1 In-Service Digital Transmission 1358 Performance Monitoring, ANSI T1.231-1997, September 1997. 1360 [ETHERIF] Flick, J., "Definitions of Managed Objects for the 1361 Ethernet-like Interface Types", , work in progress. 1364 [MAU-MIB] Flick, J., "Definitions of Managed Objects for IEEE 802.3 1365 Medium Attachment Units (MAUs)", , work in progress. 1368 [P802.3ae] Law, D., Editor, Draft Supplement to IEEE Std. 802.3, IEEE 1369 Draft P802.3ae/D3.3, October 23, 2001, work in progress. 1371 8. Authors' Addresses 1373 Mike Ayers 1374 BMC Software, Inc. 1375 2141 North First Street 1376 San Jose, CA 95131 1377 USA 1379 Phone: +1 408 546 0947 1380 Fax: +1 408 965 0359 1381 Email: mayers@bmc.com 1383 John Flick 1384 Hewlett-Packard Company 1385 8000 Foothills Blvd. M/S 5557 1386 Roseville, CA 95747-5557 1388 Phone: +1 916 785 4018 1389 Fax: +1 916 785 1199 1390 Email: johnf@rose.hp.com 1392 C. M. Heard 1393 600 Rainbow Dr. #141 1394 Mountain View, CA 94041-2542 1395 USA 1397 Phone: +1 650 964 8391 1398 EMail: heard@pobox.com 1400 Kam Lam 1401 Lucent Technologies 1402 101 Crawfords Corner Road, Room 4C-616A 1403 Holmdel, NJ 07733 1405 Phone: +1 732 949 8338 1406 EMail: hklam@lucent.com 1408 Kerry McDonald 1409 Institute for Applied Supercomputing 1410 California State University San Bernardino 1412 Email: kerry_mcd@hotmail.com 1413 kmcdonal@csci.csusb.edu 1415 K. C. Norseth 1416 Enterasys Networks 1417 2691 South Decker Lake Lane 1418 Salt Lake City, Utah 84119 1420 Phone: +1 801 887 9823 1421 Email: knorseth@enterasys.com 1423 Kaj Tesink 1424 Telcordia Technologies 1425 331 Newman Springs Road 1426 P.O. Box 7020 1427 Red Bank, NJ 07701-7020 1428 USA 1430 Phone: +1 732 758 5254 1431 EMail: kaj@research.telcordia.com 1433 9. Intellectual Property 1435 The IETF takes no position regarding the validity or scope of any 1436 intellectual property or other rights that might be claimed to 1437 pertain to the implementation or use of the technology described in 1438 this document or the extent to which any license under such rights 1439 might or might not be available; neither does it represent that it 1440 has made any effort to identify any such rights. Information on the 1441 IETF's procedures with respect to rights in standards-track and 1442 standards-related documentation can be found in BCP-11. Copies of 1443 claims of rights made available for publication and any assurances of 1444 licenses to be made available, or the result of an attempt made to 1445 obtain a general license or permission for the use of such 1446 proprietary rights by implementors or users of this specification can 1447 be obtained from the IETF Secretariat. 1449 The IETF invites any interested party to bring to its attention any 1450 copyrights, patents or patent applications, or other proprietary 1451 rights which may cover technology that may be required to practice 1452 this standard. Please address the information to the IETF Executive 1453 Director. 1455 Appendix A: Collection of Performance Data Using WIS MDIO Registers 1457 The purpose of this appendix is to illustrate how the WIS MDIO 1458 registers specified in [P802.3ae] subclause 45.2.2 (and more 1459 specifically the subset required by [P802.3ae] subclause 50.3.10) can 1460 be used to collect performance data either according to the 1461 conventions adopted by this document or according to the conventions 1462 specified in [P802.3ae] Clause 30. 1464 For an agent implementing the SNMP managed objects required by this 1465 document the first step in collecting WIS performance data would be 1466 to poll the 10G WIS Status 3 register and the various error count 1467 registers (10G WIS Section BIP Error Count, 10G WIS Line BIP Errors, 1468 10G WIS Far End Line BIP Errors, 10G WIS Path Block Error Count, and 1469 10G WIS Far End Path Block Error Count) once per second. The 10G WIS 1470 Status 3 register bits are all latched until read and so would 1471 indicate whether a given defect occurred any time during the previous 1472 second. The error count registers roll over modulo 2^16 or 2^32, and 1473 so to find the number of errors within the previous second the agent 1474 would need to subtract (modulo 2^16 or 2^32) the current reading from 1475 the reading taken one second ago. Armed with that information, the 1476 agent could determine for any layer whether the one second interval 1477 was an errored second, a severely errored second (that requires 1478 comparison with a threshold unless a defect is present), or a 1479 severely errored frame second. Determining whether a given second is 1480 or is not part of unavailable time requires additional logic; the 1481 most straightforward and accurate method is the delay-line approach 1482 outlined in Appendix A of [SONETng]. With that information available 1483 the agent would be able to determine by how much each current count 1484 should be incremented (including effects of inhibiting). 1485 Implementations that conform to [T1.231] would end each 15-minute 1486 interval on time-of-day clock 1/4 hour boundaries; if the delay-line 1487 approach is used then a time-of-day timestamp would accompany the 1488 one-second statistics. At the end of each interval the current 1489 registers would be pushed onto the history stack and then would be 1490 cleared. The xyxIntervalValidData flags would be set to False(2) if 1491 the number of samples was not between 890 and 910 or, in the case of 1492 far-end counts, if a near-end defect occurred during the just- 1493 completed interval (see [T1.231] Section 9.1.2.2 for details). 1495 An agent implementing the [P802.3ae] Clause 30 oWIS objects could 1496 start in much the same way, i.e., by polling the 10G WIS Status 3 1497 register and the various error count registers to find the defects 1498 and error counts for the previous second, and it could determine the 1499 number of errors and whether the second was an errored second, a 1500 severely errored second, or a severely errored frame second in the 1501 same manner as above. The rest of the process would be simply to 1502 increment the generalized non-resetable counters without 1503 consideration of any inhibiting rules. 1505 Full Copyright Statement 1507 Copyright (C) The Internet Society (2001). All Rights Reserved. 1509 This document and translations of it may be copied and furnished to 1510 others, and derivative works that comment on or otherwise explain it 1511 or assist in its implementation may be prepared, copied, published 1512 and distributed, in whole or in part, without restriction of any 1513 kind, provided that the above copyright notice and this paragraph are 1514 included on all such copies and derivative works. However, this 1515 document itself may not be modified in any way, such as by removing 1516 the copyright notice or references to the Internet Society or other 1517 Internet organizations, except as needed for the purpose of 1518 developing Internet standards in which case the procedures for 1519 copyrights defined in the Internet Standards process must be 1520 followed, or as required to translate it into languages other than 1521 English. 1523 The limited permissions granted above are perpetual and will not be 1524 revoked by the Internet Society or its successors or assigns. 1526 This document and the information contained herein is provided on an 1527 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 1528 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 1529 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 1530 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 1531 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1533 Table of Contents 1535 1 Abstract ..................................................... 2 1536 2 The SNMP Management Framework ................................ 2 1537 3 Overview ..................................................... 3 1538 3.1 Relationship to the SONET MIB .............................. 4 1539 3.2 Relationship to the Ethernet-like Interfaces MIB ........... 4 1540 3.3 Relationship to the 802.3 MAU MIB .......................... 4 1541 3.4 Use of the ifTable ......................................... 4 1542 3.4.1 Layering Model ........................................... 5 1543 3.4.2 Use of ifTable for LLC Layer/MAC Layer/Reconciliation 1544 Sublayer/Physical Coding Sublayer ......................... 5 1545 3.4.3 Use of ifTable for SONET/SDH Path Layer .................. 5 1546 3.4.4 Use of ifTable for SONET/SDH Medium/Section/Line Layer 1547 ........................................................... 5 1548 3.5 SONET/SDH Terminology ...................................... 6 1549 3.6 Mapping of IEEE 802.3 Managed Objects ...................... 7 1550 3.7 Mapping of SNMP Objects to WIS Station Management 1551 Registers ................................................. 12 1552 3.8 Structure of the MIB Module ................................ 14 1553 3.8.1 etherWisDeviceTable ...................................... 14 1554 3.8.2 etherWisSectionCurrentTable .............................. 14 1555 3.8.3 etherWisPathCurrentTable ................................. 14 1556 3.8.4 etherWisFarEndPathCurrentTable ........................... 15 1557 4 Object Definitions ........................................... 16 1558 5 Acknowledgments .............................................. 28 1559 6 Security Considerations ...................................... 28 1560 7 References ................................................... 29 1561 8 Authors' Addresses ........................................... 31 1562 9 Intellectual Property ........................................ 32 1563 Appendix A: Collection of Performance Data Using WIS MDIO 1564 Registers ................................................. 33 1565 Full Copyright Statement ...................................... 34