idnits 2.17.1 draft-ietf-hubmib-wis-mib-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about Internet-Drafts being working documents. == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** There are 2 instances of too long lines in the document, the longest one being 2 characters in excess of 72. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year -- 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 (29 June 2001) is 8337 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) == Unused Reference: 'RFC1905' is defined on line 1010, but no explicit reference was found in the text ** 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) Summary: 16 errors (**), 0 flaws (~~), 3 warnings (==), 2 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 INTERNET-DRAFT Editors of this version: 2 Mike Ayers 3 BMC Software, Inc. 4 Kerry McDonald 5 CSU San Bernardino 6 John Flick 7 Hewlwett-Packard Company 8 K.C. Norseth 9 Enterasys Networks 10 29 June 2001 12 Definition of Managed Objects for the 13 Ethernet WAN Interface Sublayer 14 16 Status of this Memo 18 This document is an Internet-Draft and is in full conformance with 19 all provisions of Section 10 of RFC2026. Internet-Drafts are working 20 documents of the Internet Engineering Task Force (IETF), its areas, 21 and its working groups. Note that other groups may also distribute 22 working documents as Internet-Drafts. 24 Internet-Drafts are draft documents valid for a maximum of six months 25 and may be updated, replaced, or obsoleted by other documents at any 26 time. It is inappropriate to use Internet-Drafts as reference 27 material or to cite them other than as "work in progress." 29 The list of current Internet-Drafts can be accessed at 30 http://www.ietf.org/ietf/1id-abstracts.txt 32 The list of Internet-Draft Shadow Directories can be accessed at 33 http://www.ietf.org/shadow.html 35 Copyright Notice 37 Copyright (C) The Internet Society (2001). All Rights Reserved. 39 Abstract 41 This document defines a portion of the Management Information Base 42 (MIB) for use with network management protocols in TCP/IP based 43 internets. In particular, it defines objects for managing the Wide 44 Area Network (WAN) Interface Sublayer (WIS) for Ethernet systems 45 which support it. 47 Table of Contents 49 1. Introduction ................................................ 3 50 2. Overview .................................................... 4 51 3. Definitions ................................................. 4 52 4. Notice on Intellectual Property ............................. 20 53 5. Acknowledgments ............................................. 21 54 6. Security .................................................... 21 55 7. References .................................................. 22 56 8. Editor's Address ............................................ 23 57 9. Full Copyright Statement .................................... 23 59 1. Introduction 61 The SNMP Management Framework at the time of this writing consists of 62 five major components: 64 - An overall architecture, described in RFC 2571 [RFC2571]. 66 - Mechanisms for describing and naming objects and events for 67 the purpose of management. The first version of this 68 Structure of Management Information (SMI) is called SMIv1 69 and described in STD 16, RFC 1155 [RFC1155], STD 16, RFC 70 1212 [RFC1212] and RFC 1215 [RFC1215]. The second version, 71 called SMIv2, is described in STD 58, RFC 2578 [RFC2578], 72 STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580]. 74 - Message protocols for transferring management information. 75 The first version of the SNMP message protocol is called 76 SNMPv1 and described in STD 15, RFC 1157 [RFC1157]. A 77 second version of the SNMP message protocol, which is not 78 an Internet standards track protocol, is called SNMPv2c and 79 described in RFC 1901 [RFC1901] and RFC 1906 [RFC1906]. 80 The third version of the message protocol is called SNMPv3 81 and described in RFC 1906 [RFC1906], RFC 2572 [RFC2572] and 82 RFC 2574 [RFC2574]. 84 - Protocol operations for accessing management information. 85 The first set of protocol operations and associated PDU 86 formats is described in STD 15, RFC 1157 [RFC1157]. A 87 second set of protocol operations and associated PDU 88 formats is described in this document. 90 - A set of fundamental applications described in RFC 2573 91 [RFC2573] and the view-based access control mechanism 92 described in RFC 2575 [RFC2575]. 94 A more detailed introduction to the SNMP Management Framework at the 95 time of this writing can be found in RFC 2570 [RFC2570]. 97 Managed objects are accessed via a virtual information store, termed 98 the Management Information Base or MIB. Objects in the MIB are 99 defined using the mechanisms defined in the SMI. 101 This memo specifies a MIB module that is compliant to the SMIv2. A 102 MIB conforming to the SMIv1 can be produced through the appropriate 103 translations. The resulting translated MIB must be semantically 104 equivalent, except where objects or events are omitted because no 105 translation is possible (use of Counter64). Some machine readable 106 information in SMIv2 will be converted into textual descriptions in 107 SMIv1 during the translation process. However, this loss of machine 108 readable information is not considered to change the semantics of the 109 MIB. 111 2. Overview 113 TBD - Include sections and/or references on measurement methods. 115 3. Definitions 117 ETHER-WIS DEFINITIONS ::= BEGIN 119 IMPORTS 120 MODULE-IDENTITY, OBJECT-TYPE, 121 Integer32, mib-2 122 FROM SNMPv2-SMI 123 ifIndex 124 FROM IF-MIB 125 MODULE-COMPLIANCE, OBJECT-GROUP 126 FROM SNMPv2-CONF; 128 etherWisMIB MODULE-IDENTITY 129 LAST-UPDATED "200107270000Z" 130 ORGANIZATION "IETF Hubmib Working Group" 131 CONTACT-INFO 132 "Mike Ayers 133 BMC Software 134 Tel: +1 408-546-0947 135 email: mayers@bmc.com" 136 DESCRIPTION 137 "The MIB module to describe Ethernet WIS objects" 139 ::= { mib-2 XX } -- to be assigned by IANA 141 -- The main sections of the module 143 etherWisDevice OBJECT IDENTIFIER ::= { etherWisMIB 1 } 145 etherWisSection OBJECT IDENTIFIER ::= { etherWisMIB 2 } 147 etherWisLine OBJECT IDENTIFIER ::= { etherWisMIB 3 } 149 etherWisPath OBJECT IDENTIFIER ::= { etherWisMIB 4 } 151 etherWisConformance OBJECT IDENTIFIER ::= { etherWisMIB 5 } 152 -- The Device group 154 -- These objects apply to functions which may be implemented in 155 -- devices which support more than one physical connection. 156 -- Therefore, changes to these objects may affect instances other 157 -- than the changed instance. 159 etherWisDeviceTable OBJECT-TYPE 160 SYNTAX SEQUENCE OF EtherWisDeviceEntry 161 MAX-ACCESS not-accessible 162 STATUS current 163 DESCRIPTION 164 "The table for Ethernet WIS devices" 165 ::= { etherWisDevice 1 } 167 etherWisDeviceEntry OBJECT-TYPE 168 SYNTAX EtherWisDeviceEntry 169 MAX-ACCESS not-accessible 170 STATUS current 171 DESCRIPTION 172 "An entry in the Ethernet WIS device table" 173 INDEX { ifIndex } 174 ::= { etherWisDeviceTable 1} 176 EtherWisDeviceEntry ::= 177 SEQUENCE { 178 etherWisDeviceReset INTEGER, 179 etherWisDeviceLoopback INTEGER, 180 etherWisDeviceSpeedSelection INTEGER, 181 etherWisDevicePowerDown INTEGER, 182 etherWisDevicePresent INTEGER, 183 etherWisDeviceModesAllowed INTEGER, 184 etherWisDeviceModeSelect INTEGER, 185 etherWisDeviceJitterTestMode INTEGER 186 } 188 etherWisDeviceReset OBJECT-TYPE 189 SYNTAX INTEGER { 190 running(0), 191 reset(1) 192 } 193 MAX-ACCESS read-write 194 STATUS current 195 DESCRIPTION 196 "This variable can be used to reset the WIS. The interface may 197 be unavailable while the reset occurs and data may be lost." 198 ::= { etherWisDeviceEntry 1 } 200 etherWisDeviceLoopback OBJECT-TYPE 201 SYNTAX INTEGER { 202 noLoopback(0), 203 loopBack(1) 204 } 205 MAX-ACCESS read-write 206 STATUS current 207 DESCRIPTION 208 "Setting this variable to loopback will cause data sent into the 209 interface to be returned on the same interface." 210 ::= { etherWisDeviceEntry 2 } 212 etherWisDeviceSpeedSelection OBJECT-TYPE 213 SYNTAX INTEGER 214 MAX-ACCESS read-write 215 STATUS current 216 DESCRIPTION 217 "This variable is currently being changed by the IEEE." 218 ::= { etherWisDeviceEntry 3 } 220 etherWisDevicePowerDown OBJECT-TYPE 221 SYNTAX INTEGER 222 MAX-ACCESS read-write 223 STATUS current 224 DESCRIPTION 225 "This variable is currently being changed by the IEEE." 226 ::= { etherWisDeviceEntry 4 } 228 etherWisDevicePresent OBJECT-TYPE 229 SYNTAX INTEGER 230 MAX-ACCESS read-only 231 STATUS current 232 DESCRIPTION 233 "This variable is currently being changed by the IEEE." 234 ::= { etherWisDeviceEntry 5 } 236 etherWisDeviceModesAllowed OBJECT-TYPE 237 SYNTAX INTEGER 238 MAX-ACCESS read-only 239 STATUS current 240 DESCRIPTION 241 "This is a bit pattern indicating which modes this device 242 will permit etherWisDeviceModeSelect to be set to. The 243 bit positions, with 0 being the LSB, indicate: 245 0 - 10GBASE-W 246 1 - 10GBASE-R" 247 ::= { etherWisDeviceEntry 6 } 249 etherWisDeviceModeSelect OBJECT-TYPE 250 SYNTAX INTEGER 251 MAX-ACCESS read-write 252 STATUS current 253 DESCRIPTION 254 "This variable indicates the current operating state of the 255 device. The values use the same bit pattern as 256 etherWisDeviceModesAllowed. Attempts to set this variable 257 to a value which would cause conflicting mode settings will 258 result in an inconsistentValue error." 259 ::= { etherWisDeviceEntry 7 } 261 etherWisDeviceJitterTestMode OBJECT-TYPE 262 SYNTAX INTEGER { 263 disable(0), 264 enable(1) 265 } 266 MAX-ACCESS read-write 267 STATUS current 268 DESCRIPTION 269 "This variable controls jitter test mode." 270 ::= { etherWisDeviceEntry 8 } 272 etherWisSectionCurrentTable OBJECT-TYPE 273 SYNTAX SEQUENCE OF EtherWisSectionCurrentEntry 274 MAX-ACCESS not-accessible 275 STATUS current 276 DESCRIPTION 277 "The table for the current state of Ethernet WIS sections." 278 ::= { etherWisSection 1 } 280 etherWisSectionCurrentEntry OBJECT-TYPE 281 SYNTAX EtherWisSectionCurrentEntry 282 MAX-ACCESS not-accessible 283 STATUS current 284 DESCRIPTION 285 "An entry in the etherWisSectionCurrentTable." 286 INDEX { ifIndex } 287 ::= { etherWisSectionCurrentTable 1 } 289 EtherWisSectionCurrentEntry ::= 290 SEQUENCE { 291 etherWisSectionCurrentJ0Transmitted INTEGER, 292 etherWisSectionCurrentJ0Expected INTEGER, 293 etherWisSectionCurrentJ0Received INTEGER, 294 etherWisSectionCurrentStatus Integer32, 295 etherWisSectionCurrentESs Integer32, 296 etherWisSectionCurrentSESs Integer32, 297 etherWisSectionCurrentSEFSs Integer32, 298 etherWisSectionCurrentCVs Integer32 299 } 301 etherWisSectionCurrentJ0Transmitted OBJECT-TYPE 302 SYNTAX INTEGER ( 0..255 ) 303 MAX-ACCESS read-write 304 STATUS current 305 DESCRIPTION 306 "This is the section trace J0 byte which is to be 307 transmitted." 308 ::= { etherWisSectionCurrentEntry 1 } 310 etherWisSectionCurrentJ0Expected OBJECT-TYPE 311 SYNTAX INTEGER ( 0..255 ) 312 MAX-ACCESS read-write 313 STATUS current 314 DESCRIPTION 315 "This is the section trace J0 byte which is 316 expected to be received." 317 ::= { etherWisSectionCurrentEntry 2 } 319 etherWisSectionCurrentJ0Received OBJECT-TYPE 320 SYNTAX INTEGER ( 0..255 ) 321 MAX-ACCESS read-only 322 STATUS current 323 DESCRIPTION 324 "This is the section trace J0 byte which was 325 actually received." 326 ::= { etherWisSectionCurrentEntry 3 } 328 etherWisSectionCurrentStatus OBJECT-TYPE 329 SYNTAX Integer32 330 MAX-ACCESS read-only 331 STATUS current 332 DESCRIPTION 333 "This variable indicates the current status of the 334 section with a bit map which can indicate several 335 defects at once. The etherWisSectionNoDefect should 336 be set if and only if no other flag is set. 338 The bit positions are: 339 1 etherWisSectionNoError 340 2 etherWisSectionLocalFault 341 4 etherWisSectionLinkDown 342 8 etherWisSectionLOS 343 16 etherWisSectionLOF" 344 ::= { etherWisSectionCurrentEntry 4 } 346 etherWisSectionCurrentESs OBJECT-TYPE 347 SYNTAX Integer32 348 MAX-ACCESS read-only 349 STATUS current 350 DESCRIPTION 351 "The count of Errored Seconds in the current 352 measuring interval." 353 ::= { etherWisSectionCurrentEntry 5 } 355 etherWisSectionCurrentSESs OBJECT-TYPE 356 SYNTAX Integer32 357 MAX-ACCESS read-only 358 STATUS current 359 DESCRIPTION 360 "The count of Severely Errored Seconds in the current 361 measuring interval." 362 ::= { etherWisSectionCurrentEntry 6 } 364 etherWisSectionCurrentSEFSs OBJECT-TYPE 365 SYNTAX Integer32 366 MAX-ACCESS read-only 367 STATUS current 368 DESCRIPTION 369 "The count of Severely Errored Framing Seconds in the 370 current measuring interval." 371 ::= { etherWisSectionCurrentEntry 7 } 373 etherWisSectionCurrentCVs OBJECT-TYPE 374 SYNTAX Integer32 375 MAX-ACCESS read-only 376 STATUS current 377 DESCRIPTION 378 "The count of Coding Violations in the current 379 measuring interval." 380 ::= { etherWisSectionCurrentEntry 8 } 382 etherWisSectionIntervalTable OBJECT-TYPE 383 SYNTAX SEQUENCE OF EtherWisSectionIntervalEntry 384 MAX-ACCESS not-accessible 385 STATUS current 386 DESCRIPTION 387 "The table for storage of Ethernet WIS section 388 historical data." 389 ::= { etherWisSection 2 } 391 etherWisSectionIntervalEntry OBJECT-TYPE 392 SYNTAX EtherWisSectionIntervalEntry 393 MAX-ACCESS not-accessible 394 STATUS current 395 DESCRIPTION 396 "An entry in the etherWisSectionIntervalTable." 397 INDEX { ifIndex, 398 etherWisSectionIntervalNumber } 399 ::= { etherWisSectionIntervalTable 1 } 401 EtherWisSectionIntervalEntry ::= 402 SEQUENCE { 403 etherWisSectionIntervalNumber Integer32, 404 etherWisSectionIntervalESs Integer32, 405 etherWisSectionIntervalSESs Integer32, 406 etherWisSectionIntervalSEFSs Integer32, 407 etherWisSectionIntervalCVs Integer32 408 } 410 etherWisSectionIntervalNumber OBJECT-TYPE 411 SYNTAX Integer32 ( 1..96 ) 412 MAX-ACCESS not-accessible 413 STATUS current 414 DESCRIPTION 415 "A number identifying which 15 minute interval is 416 refereneced by the data in the table. The value 417 1 represents the most recent completed interval." 418 ::= { etherWisSectionIntervalEntry 1 } 420 etherWisSectionIntervalESs OBJECT-TYPE 421 SYNTAX Integer32 422 MAX-ACCESS read-only 423 STATUS current 424 DESCRIPTION 425 "The count of Errored Seconds in this 426 measuring interval." 427 ::= { etherWisSectionIntervalEntry 2 } 429 etherWisSectionIntervalSESs OBJECT-TYPE 430 SYNTAX Integer32 431 MAX-ACCESS read-only 432 STATUS current 433 DESCRIPTION 434 "The count of Severely Errored Seconds in this 435 measuring interval." 436 ::= { etherWisSectionIntervalEntry 3 } 438 etherWisSectionIntervalSEFSs OBJECT-TYPE 439 SYNTAX Integer32 440 MAX-ACCESS read-only 441 STATUS current 442 DESCRIPTION 443 "The count of Severely Errored Framing Seconds in the 444 measuring interval." 445 ::= { etherWisSectionIntervalEntry 4 } 447 etherWisSectionIntervalCVs OBJECT-TYPE 448 SYNTAX Integer32 449 MAX-ACCESS read-only 450 STATUS current 451 DESCRIPTION 452 "The count of Coding Violations in the 453 measuring interval." 454 ::= { etherWisSectionIntervalEntry 5 } 456 etherWisLineCurrentTable OBJECT-TYPE 457 SYNTAX SEQUENCE OF EtherWisLineCurrentEntry 458 MAX-ACCESS not-accessible 459 STATUS current 460 DESCRIPTION 461 "The table for the current state of Ethernet WIS lines." 462 ::= { etherWisLine 1 } 464 etherWisLineCurrentEntry OBJECT-TYPE 465 SYNTAX EtherWisLineCurrentEntry 466 MAX-ACCESS not-accessible 467 STATUS current 468 DESCRIPTION 469 "An entry in the etherWisLineCurrentTable." 470 INDEX { ifIndex } 471 ::= { etherWisLineCurrentTable 1 } 473 EtherWisLineCurrentEntry ::= 474 SEQUENCE { 475 etherWisLineCurrentStatus Integer32, 476 etherWisLineCurrentESs Integer32, 477 etherWisLineCurrentSESs Integer32, 478 etherWisLineCurrentCVs Integer32, 479 etherWisLineCurrentUASs Integer32 480 } 482 etherWisLineCurrentStatus OBJECT-TYPE 483 SYNTAX Integer32 ( 1..6 ) 484 MAX-ACCESS read-only 485 STATUS current 486 DESCRIPTION 487 "This variable indicates the current status of the 488 line with a bit map which can indicate several 489 defects at once. The etherWisLineNoDefect should 490 be set if and only if no other flag is set. 492 The bit positions are: 493 1 etherWisLineNoDefect 494 2 etherWisLineRDI 495 4 etherWisLineAIS" 496 ::= { etherWisLineCurrentEntry 1 } 498 etherWisLineCurrentESs OBJECT-TYPE 499 SYNTAX Integer32 500 MAX-ACCESS read-only 501 STATUS current 502 DESCRIPTION 503 "The count of Errored Seconds in the current 504 measuring interval." 505 ::= { etherWisLineCurrentEntry 2 } 507 etherWisLineCurrentSESs OBJECT-TYPE 508 SYNTAX Integer32 509 MAX-ACCESS read-only 510 STATUS current 511 DESCRIPTION 512 "The count of Severely Errored Seconds in the current 513 measuring interval." 514 ::= { etherWisLineCurrentEntry 3 } 516 etherWisLineCurrentCVs OBJECT-TYPE 517 SYNTAX Integer32 518 MAX-ACCESS read-only 519 STATUS current 520 DESCRIPTION 521 "The count of Coding Violations in the current 522 measuring interval." 523 ::= { etherWisLineCurrentEntry 4 } 525 etherWisLineCurrentUASs OBJECT-TYPE 526 SYNTAX Integer32 527 MAX-ACCESS read-only 528 STATUS current 529 DESCRIPTION 530 "The count of Unavailable Seconds in the current 531 measuring interval." 532 ::= { etherWisLineCurrentEntry 5 } 534 etherWisLineIntervalTable OBJECT-TYPE 535 SYNTAX SEQUENCE OF EtherWisLineIntervalEntry 536 MAX-ACCESS not-accessible 537 STATUS current 538 DESCRIPTION 539 "The table for the historical data of Ethernet WIS lines." 540 ::= { etherWisLine 2 } 542 etherWisLineIntervalEntry OBJECT-TYPE 543 SYNTAX EtherWisLineIntervalEntry 544 MAX-ACCESS not-accessible 545 STATUS current 546 DESCRIPTION 547 "An entry in the etherWisLineIntervalTable." 548 INDEX { ifIndex, 549 etherWisLineIntervalNumber } 550 ::= { etherWisLineIntervalTable 1 } 552 EtherWisLineIntervalEntry ::= 553 SEQUENCE { 554 etherWisLineIntervalNumber Integer32, 555 etherWisLineIntervalESs Integer32, 556 etherWisLineIntervalSESs Integer32, 557 etherWisLineIntervalCVs Integer32, 558 etherWisLineIntervalUASs Integer32 559 } 561 etherWisLineIntervalNumber OBJECT-TYPE 562 SYNTAX Integer32 ( 1..96 ) 563 MAX-ACCESS not-accessible 564 STATUS current 565 DESCRIPTION 566 "A number identifying which 15 minute interval is 567 refereneced by the data in the table. The value 568 1 represents the most recent completed interval." 569 ::= { etherWisLineIntervalEntry 1 } 571 etherWisLineIntervalESs OBJECT-TYPE 572 SYNTAX Integer32 573 MAX-ACCESS read-only 574 STATUS current 575 DESCRIPTION 576 "The count of Errored Seconds in the 577 measuring interval." 578 ::= { etherWisLineIntervalEntry 2 } 580 etherWisLineIntervalSESs OBJECT-TYPE 581 SYNTAX Integer32 582 MAX-ACCESS read-only 583 STATUS current 584 DESCRIPTION 585 "The count of Severely Errored Seconds in the 586 measuring interval." 587 ::= { etherWisLineIntervalEntry 3 } 589 etherWisLineIntervalCVs OBJECT-TYPE 590 SYNTAX Integer32 591 MAX-ACCESS read-only 592 STATUS current 593 DESCRIPTION 594 "The count of Coding Violations in the 595 measuring interval." 596 ::= { etherWisLineIntervalEntry 4 } 598 etherWisLineIntervalUASs OBJECT-TYPE 599 SYNTAX Integer32 600 MAX-ACCESS read-only 601 STATUS current 602 DESCRIPTION 603 "The count of Unavailable Seconds in the 604 measuring interval." 605 ::= { etherWisLineIntervalEntry 5 } 607 etherWisPathCurrentTable OBJECT-TYPE 608 SYNTAX SEQUENCE OF EtherWisPathCurrentEntry 609 MAX-ACCESS not-accessible 610 STATUS current 611 DESCRIPTION 612 "The table for the current state of Ethernet WIS paths." 613 ::= { etherWisPath 1 } 615 etherWisPathCurrentEntry OBJECT-TYPE 616 SYNTAX EtherWisPathCurrentEntry 617 MAX-ACCESS not-accessible 618 STATUS current 619 DESCRIPTION 620 "An entry in the etherWisPathCurrentTable." 621 INDEX { ifIndex } 622 ::= { etherWisPathCurrentTable 1 } 624 EtherWisPathCurrentEntry ::= 625 SEQUENCE { 626 etherWisPathCurrentStatus Integer32, 627 etherWisPathCurrentESs Integer32, 628 etherWisPathCurrentSESs Integer32, 629 etherWisPathCurrentCVs Integer32, 630 etherWisPathCurrentUASs Integer32 631 } 633 etherWisPathCurrentStatus OBJECT-TYPE 634 SYNTAX Integer32 ( 1..6 ) 635 MAX-ACCESS read-only 636 STATUS current 637 DESCRIPTION 638 "This variable indicates the current status of the 639 line with a bit map which can indicate several 640 defects at once. The etherWisPathNoDefect flag should 641 be set if and only if no other flag is set. 643 The bit positions are: 644 1 etherWisPathNoDefect 645 2 etherWisPathLCD 646 4 etherWisPathPLM 647 8 etherWisPathAIS 648 16 etherWisPathLOP" 649 ::= { etherWisPathCurrentEntry 1 } 651 etherWisPathCurrentESs OBJECT-TYPE 652 SYNTAX Integer32 653 MAX-ACCESS read-only 654 STATUS current 655 DESCRIPTION 656 "The count of Errored Seconds in the current 657 measuring interval." 658 ::= { etherWisPathCurrentEntry 2 } 660 etherWisPathCurrentSESs OBJECT-TYPE 661 SYNTAX Integer32 662 MAX-ACCESS read-only 663 STATUS current 664 DESCRIPTION 665 "The count of Severely Errored Seconds in the current 666 measuring interval." 667 ::= { etherWisPathCurrentEntry 3 } 669 etherWisPathCurrentCVs OBJECT-TYPE 670 SYNTAX Integer32 671 MAX-ACCESS read-only 672 STATUS current 673 DESCRIPTION 674 "The count of Coding Violations in the current 675 measuring interval." 676 ::= { etherWisPathCurrentEntry 4 } 678 etherWisPathCurrentUASs OBJECT-TYPE 679 SYNTAX Integer32 680 MAX-ACCESS read-only 681 STATUS current 682 DESCRIPTION 683 "The count of Unavailable Seconds in the current 684 measuring interval." 685 ::= { etherWisPathCurrentEntry 5 } 687 etherWisPathIntervalTable OBJECT-TYPE 688 SYNTAX SEQUENCE OF EtherWisPathIntervalEntry 689 MAX-ACCESS not-accessible 690 STATUS current 691 DESCRIPTION 692 "The table for the historical data of Ethernet WIS lines." 693 ::= { etherWisPath 2 } 695 etherWisPathIntervalEntry OBJECT-TYPE 696 SYNTAX EtherWisPathIntervalEntry 697 MAX-ACCESS not-accessible 698 STATUS current 699 DESCRIPTION 700 "An entry in the etherWisPathIntervalTable." 701 INDEX { ifIndex, 702 etherWisPathIntervalNumber } 703 ::= { etherWisPathIntervalTable 1 } 705 EtherWisPathIntervalEntry ::= 706 SEQUENCE { 707 etherWisPathIntervalNumber Integer32, 708 etherWisPathIntervalESs Integer32, 709 etherWisPathIntervalSESs Integer32, 710 etherWisPathIntervalCVs Integer32, 711 etherWisPathIntervalUASs Integer32 712 } 714 etherWisPathIntervalNumber OBJECT-TYPE 715 SYNTAX Integer32 ( 1..96 ) 716 MAX-ACCESS not-accessible 717 STATUS current 718 DESCRIPTION 719 "A number identifying which 15 minute interval is 720 refereneced by the data in the table. The value 721 1 represents the most recent completed interval." 722 ::= { etherWisPathIntervalEntry 1 } 724 etherWisPathIntervalESs OBJECT-TYPE 725 SYNTAX Integer32 726 MAX-ACCESS read-only 727 STATUS current 728 DESCRIPTION 729 "The count of Errored Seconds in the 730 measuring interval." 731 ::= { etherWisPathIntervalEntry 2 } 733 etherWisPathIntervalSESs OBJECT-TYPE 734 SYNTAX Integer32 735 MAX-ACCESS read-only 736 STATUS current 737 DESCRIPTION 738 "The count of Severely Errored Seconds in the 739 measuring interval." 740 ::= { etherWisPathIntervalEntry 3 } 742 etherWisPathIntervalCVs OBJECT-TYPE 743 SYNTAX Integer32 744 MAX-ACCESS read-only 745 STATUS current 746 DESCRIPTION 747 "The count of Coding Violations in the 748 measuring interval." 749 ::= { etherWisPathIntervalEntry 4 } 751 etherWisPathIntervalUASs OBJECT-TYPE 752 SYNTAX Integer32 753 MAX-ACCESS read-only 754 STATUS current 755 DESCRIPTION 756 "The count of Unavailable Seconds in the 757 measuring interval." 758 ::= { etherWisPathIntervalEntry 5 } 760 -- 761 -- Conformance Statements 762 -- 764 etherWisGroups OBJECT IDENTIFIER ::= { etherWisConformance 1 } 766 etherWisCompliances OBJECT IDENTIFIER ::= { etherWisConformance 2 } 768 -- Compliance Statements 770 etherWisCurrentCompliance MODULE-COMPLIANCE 771 STATUS current 772 DESCRIPTION 773 "The compliance statement for implementations which do not 774 support historical data." 776 MODULE -- this module 777 MANDATORY-GROUPS { 778 etherWisDeviceGroup, 779 etherWisSectionCurrentGroup, 780 etherWisLineCurrentGroup, 781 etherWisPathCurrentGroup 782 } 784 ::= { etherWisCompliances 1 } 786 etherWisIntervalCompliance MODULE-COMPLIANCE 787 STATUS current 788 DESCRIPTION 789 "The compliance statement for implementations which support 790 historical data." 792 MODULE -- this module 793 MANDATORY-GROUPS { 794 etherWisDeviceGroup, 795 etherWisSectionCurrentGroup, 796 etherWisSectionIntervalGroup, 797 etherWisLineCurrentGroup, 798 etherWisLineIntervalGroup, 799 etherWisPathCurrentGroup, 800 etherWisPathIntervalGroup 801 } 803 ::= { etherWisCompliances 2 } 805 etherWisDeviceGroup OBJECT-GROUP 806 OBJECTS { 807 etherWisDeviceReset, 808 etherWisDeviceLoopback, 809 etherWisDeviceSpeedSelection, 810 etherWisDevicePowerDown, 811 etherWisDevicePresent, 812 etherWisDeviceModesAllowed, 813 etherWisDeviceModeSelect, 814 etherWisDeviceJitterTestMode 815 } 816 STATUS current 817 DESCRIPTION 818 "A collection of objects which provide information about the 819 state of the WIS device." 820 ::= { etherWisGroups 1 } 822 etherWisSectionCurrentGroup OBJECT-GROUP 823 OBJECTS { 824 etherWisSectionCurrentJ0Transmitted, 825 etherWisSectionCurrentJ0Expected, 826 etherWisSectionCurrentJ0Received, 827 etherWisSectionCurrentStatus, 828 etherWisSectionCurrentESs, 829 etherWisSectionCurrentSESs, 830 etherWisSectionCurrentSEFSs, 831 etherWisSectionCurrentCVs 832 } 833 STATUS current 834 DESCRIPTION 835 "A collection of objects which provide information about the 836 current state of the WIS section." 837 ::= { etherWisGroups 2 } 839 etherWisSectionIntervalGroup OBJECT-GROUP 840 OBJECTS { 841 etherWisSectionIntervalNumber, 842 etherWisSectionIntervalESs, 843 etherWisSectionIntervalSESs, 844 etherWisSectionIntervalSEFSs, 845 etherWisSectionIntervalCVs 846 } 847 STATUS current 848 DESCRIPTION 849 "A collection of objects which provide historical data 850 about the WIS section." 851 ::= { etherWisGroups 3 } 853 etherWisLineCurrentGroup OBJECT-GROUP 854 OBJECTS { 855 etherWisLineCurrentStatus, 856 etherWisLineCurrentESs, 857 etherWisLineCurrentSESs, 858 etherWisLineCurrentCVs, 859 etherWisLineCurrentUASs 860 } 861 STATUS current 862 DESCRIPTION 863 "A collection of objects which provide information about the 864 current state of the WIS line." 865 ::= { etherWisGroups 4 } 867 etherWisLineIntervalGroup OBJECT-GROUP 868 OBJECTS { 869 etherWisLineIntervalNumber, 870 etherWisLineIntervalESs, 871 etherWisLineIntervalSESs, 872 etherWisLineIntervalCVs, 873 etherWisLineIntervalUASs 874 } 875 STATUS current 876 DESCRIPTION 877 "A collection of objects which provide historical data 878 about the WIS line." 879 ::= { etherWisGroups 5 } 881 etherWisPathCurrentGroup OBJECT-GROUP 882 OBJECTS { 883 etherWisPathCurrentStatus, 884 etherWisPathCurrentESs, 885 etherWisPathCurrentSESs, 886 etherWisPathCurrentCVs, 887 etherWisPathCurrentUASs 888 } 889 STATUS current 890 DESCRIPTION 891 "A collection of objects which provide information about the 892 current state of the WIS path." 893 ::= { etherWisGroups 6 } 895 etherWisPathIntervalGroup OBJECT-GROUP 896 OBJECTS { 897 etherWisPathIntervalNumber, 898 etherWisPathIntervalESs, 899 etherWisPathIntervalSESs, 900 etherWisPathIntervalCVs, 901 etherWisPathIntervalUASs 902 } 903 STATUS current 904 DESCRIPTION 905 "A collection of objects which provide historical data 906 about the WIS path." 907 ::= { etherWisGroups 7 } 909 END 911 4. Notice on Intellectual Property 913 The IETF takes no position regarding the validity or scope of any 914 intellectual property or other rights that might be claimed to 915 pertain to the implementation or use of the technology described in 916 this document or the extent to which any license under such rights 917 might or might not be available; neither does it represent that it 918 has made any effort to identify any such rights. Information on the 919 IETF's procedures with respect to rights in standards-track and 920 standards-related documentation can be found in BCP-11. Copies of 921 claims of rights made available for publication and any assurances of 922 licenses to be made available, or the result of an attempt made to 923 obtain a general license or permission for the use of such 924 proprietary rights by implementors or users of this specification can 925 be obtained from the IETF Secretariat. 927 The IETF invites any interested party to bring to its attention any 928 copyrights, patents or patent applications, or other proprietary 929 rights which may cover technology that may be required to practice 930 this standard. Please address the information to the IETF Executive 931 Director. 933 5. Acknowledgments 935 This document is the product of the IETF Hubmib Working Group. 937 6. Security 939 There are a number of management objects defined in this MIB that have a 940 MAX-ACCESS clause of read-write and/or read-create. Such objects may 941 be considered sensitive or vulnerable in some network environments. 942 The support for SET operations in a non-secure environment without 943 proper protection can have a negative effect on network operations. 945 SNMPv1 by itself is not a secure environment. Even if the network 946 itself is secure (for example by using IPSec), even then, there is no 947 control as to who on the secure network is allowed to access and 948 GET/SET (read/change/create/delete) the objects in this MIB. 950 It is recommended that the implementers consider the security 951 features as provided by the SNMPv3 framework. Specifically, the use 952 of the User-based Security Model RFC 2574 [RFC2574] and the View- 953 based Access Control Model RFC 2575 [RFC2575] is recommended. 955 It is then a customer/user responsibility to ensure that the SNMP 956 entity giving access to an instance of this MIB, is properly 957 configured to give access to the objects only to those principals 958 (users) that have legitimate rights to indeed GET or SET 959 (change/create/delete) them. 961 7. References 963 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, An 964 Architecture for Describing SNMP Management Frameworks, 965 RFC 2571, April 1999. 967 [RFC1155] Rose, M., and K. McCloghrie, Structure and Identification 968 of Management Information for TCP/IP-based Internets, STD 969 16, RFC 1155, May 1990. 971 [RFC1212] Rose, M., and K. McCloghrie, Concise MIB Definitions, STD 972 16, RFC 1212, March 1991. 974 [RFC1215] M. Rose, A Convention for Defining Traps for use with the 975 SNMP, RFC 1215, March 1991. 977 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 978 Rose, M., and S. Waldbusser, Structure of Management 979 Information Version 2 (SMIv2), STD 58, RFC 2578, April 980 1999. 982 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 983 Rose, M., and S. Waldbusser, Textual Conventions for 984 SMIv2, STD 58, RFC 2579, April 1999. 986 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 987 Rose, M., and S. Waldbusser, Conformance Statements for 988 SMIv2, STD 58, RFC 2580, April 1999. 990 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, 991 Simple Network Management Protocol, STD 15, RFC 1157, May 992 1990. 994 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 995 Introduction to Community-based SNMPv2, RFC 1901, January 996 1996. 998 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 999 Transport Mappings for Version 2 of the Simple Network 1000 Management Protocol (SNMPv2), RFC 1906, January 1996. 1002 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, 1003 Message Processing and Dispatching for the Simple Network 1004 Management Protocol (SNMP), RFC 2572, April 1999. 1006 [RFC2574] Blumenthal, U., and B. Wijnen, User-based Security Model 1007 (USM) for version 3 of the Simple Network Management 1008 Protocol (SNMPv3), RFC 2574, April 1999. 1010 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 1011 Protocol Operations for Version 2 of the Simple Network 1012 Management Protocol (SNMPv2), RFC 1905, January 1996. 1014 [RFC2573] Levi, D., Meyer, P., and B. Stewart, SNMPv3 Applications, 1015 RFC 2573, April 1999. 1017 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, View-based 1018 Access Control Model (VACM) for the Simple Network 1019 Management Protocol (SNMP), RFC 2575, April 1999. 1021 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 1022 Introduction to Version 3 of the Internet-standard 1023 Network Management Framework, RFC 2570, April 1999. 1025 8. Editor's Address 1027 Mike Ayers 1028 BMC Software, Inc. 1029 2141 North First Street 1030 San Jose, CA 95131 1031 USA 1033 Phone: +1 408 546 0947 1034 Fax: +1 408 965 0359 1035 Email: mayers@bmc.com 1037 Kerry McDonald 1038 Institute for Applied Supercomputing 1039 California State University San Bernardino 1041 Email: kerry_mcd@hotmail.com 1042 kmcdonal@csci.csusb.edu 1044 K.C. Norseth 1045 Enterasys Networks 1046 2691 South Decker Lake Lane 1047 Salt Lake City, Utah 84119 1049 Phone: +1 801 887 9823 1050 Email: knorseth@enterasys.com 1052 John Flick 1053 Hewlett-Packard Company 1054 8000 Foothills Blvd. M/S 5557 1055 Roseville, CA 95747-5557 1057 Phone: +1 916 785 4018 1058 Fax: +1 916 785 1199 1059 Email: johnf@rose.hp.com 1061 9. Full Copyright Statement 1063 Copyright (C) The Internet Society (2001). All Rights Reserved. 1065 This document and translations of it may be copied and furnished to 1066 others, and derivative works that comment on or otherwise explain it 1067 or assist in its implementation may be prepared, copied, published 1068 and distributed, in whole or in part, without restriction of any 1069 kind, provided that the above copyright notice and this paragraph are 1070 included on all such copies and derivative works. However, this 1071 document itself may not be modified in any way, such as by removing 1072 the copyright notice or references to the Internet Society or other 1073 Internet organizations, except as needed for the purpose of 1074 developing Internet standards in which case the procedures for 1075 copyrights defined in the Internet Standards process must be 1076 followed, or as required to translate it into languages other than 1077 English. 1079 The limited permissions granted above are perpetual and will not be 1080 revoked by the Internet Society or its successors or assigns. 1082 This document and the information contained herein is provided on an 1083 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 1084 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 1085 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 1086 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 1087 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.