idnits 2.17.1 draft-squire-hubmib-efm-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 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document is more than 15 pages and seems to lack a Table of Contents. == There is 1 instance of lines with non-ascii characters in the document. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 14 longer pages, the longest (page 2) being 61 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 16 pages 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. Miscellaneous warnings: ---------------------------------------------------------------------------- == The document doesn't use any RFC 2119 keywords, yet has text resembling RFC 2119 boilerplate text. -- 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 (Apr 2004) is 7315 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Missing reference section? '1' on line 16 looks like a reference -- Missing reference section? 'RFC3410' on line 61 looks like a reference -- Missing reference section? 'RFC2578' on line 69 looks like a reference -- Missing reference section? 'RFC2579' on line 69 looks like a reference -- Missing reference section? 'RFC2580' on line 70 looks like a reference Summary: 5 errors (**), 0 flaws (~~), 5 warnings (==), 7 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Network Working Group 2 Internet Draft 3 Document: draft-squire-hubmib-efm-mib-00.txt 5 Matt Squire 6 Hatteras Networks 8 October 2003 Expires Apr 2004 10 Ethernet in the First Mile (EFM) Common MIB 12 Status of this Memo 14 This document is an Internet-Draft and is in full conformance with 15 all provisions of Section 10 of RFC2026 [1]. 17 Internet-Drafts are working documents of the Internet Engineering 18 Task Force (IETF), its areas, and its working groups. Note that 19 other groups may also distribute working documents as Internet- 20 Drafts. 22 Internet-Drafts are draft documents valid for a maximum of six 23 months and may be updated, replaced, or obsoleted by other documents 24 at any time. It is inappropriate to use Internet- Drafts as 25 reference material or to cite them other than as "work in progress." 27 The list of current Internet-Drafts can be accessed at 28 http://www.ietf.org/ietf/1id-abstracts.txt. 30 The list of Internet-Draft Shadow Directories can be accessed at 31 http://www.ietf.org/shadow.html. 33 Abstract 35 This memo defines a portion of the Management Information Base (MIB) 36 for use with network management protocols in the Internet community. 37 This document proposes an extension to the Ethernet-like Interfaces 38 MIB for the capability to manage Ethernet-in-the-First-Mile (EFM) 39 devices. 41 1 Introduction 43 New capabilities have been added to Ethernet like interfaces within 44 the PIEEE802.3ah project for Ethernet in the First Mile (EFM). This 45 memo defines a portion of the Management Information Base (MIB) for 46 use with network management protocols in the Internet community to 47 manage the new capabilities of EFM Ethernet interfaces. 49 1.1 Specification of Requirements 51 draft-squire-hubmib-efm-mib-00.txt October 2003 53 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL 54 NOT","SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in 55 this document are to be interpreted as described in RFC 2119. 57 2 The Internet-Standard Management Framework 59 For a detailed overview of the documents that describe the current 60 Internet-Standard Management Framework, please refer to section 7 of 61 RFC 3410 [RFC3410]. 63 Managed objects are accessed via a virtual information store, termed 64 the Management Information Base or MIB. MIB objects are generally 65 accessed through the Simple Network Management Protocol (SNMP). 66 Objects in the MIB are defined using the mechanisms defined in the 67 Structure of Management Information (SMI). This memo specifies a 68 MIB module that is compliant to the SMIv2, which is described in STD 69 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 70 2580 [RFC2580]. 72 3 Overview 74 Ethernet networks have evolved over time from an enterprise backbone 75 to a variety of other applications. The IEEE P802.3ah task force 76 has defined extensions to the Ethernet standard for Ethernet 77 deployments in the access space. 79 The Ethernet-in-the-First-Mile (EFM) task force has focused its 80 efforts into four categories: optics, copper, Ethernet passive 81 optical networks (Ethernet PON, or EPON), and operations, 82 administration, and maintenance (OAM). 84 Generally, one can categorize the changes developed by IEEE P802.3ah 85 as extending Ethernet with new physical layers (e.g. new optical 86 physical layers, new copper physical layers, EPON), or as adding new 87 common functionality applicable to many Ethernet physical layers 88 (e.g. OAM). 90 This memo focuses on the management extensions to the MIB for 91 Ethernet-like interfaces to address the new common Ethernet 92 functionality developed in IEEE P802.3ah. Other documents will 93 focus on detailed MIB extensions for new physical layers where 94 applicable. 96 4 MIB Structure 98 The common EFM MIB objects of this memo focus on the OAM 99 capabilities introduced in IEEE P802.3ah. The MIB objects are 100 partitioned into four (4) different MIB groups. 102 The dot3OamTable group manages the primary OAM objects of the 103 Ethernet interface. This group controls the state and status of OAM 104 as well as the mode in which it operates. 106 draft-squire-hubmib-efm-mib-00.txt October 2003 108 The dot3OamStats table maintains statistics on the number and type 109 of Ethernet OAM frames being transmitted and received on the 110 Ethernet interface. 112 The dot3OamPeer table maintains the current information on the 113 status and configuration of the peer OAM entity on the Ethernet 114 interface. Managed information includes the capabilities and 115 function available on the peer OAM entity. 117 The dot3OamEvent table defines the management objects for the event 118 notification capability available in IEEE P802.3ah OAM. With IEEE 119 P802.3ah OAM, one device may send notifications to its peer devices 120 whenever an important event happens on the local device. 122 5 Definitions 124 EFM-COMMON-MIB DEFINITIONS ::= BEGIN 125 IMPORTS 126 MODULE-IDENTITY, mib-2, OBJECT-TYPE, Counter32, 127 Integer32, Unsigned32 128 FROM SNMPv2-SMI 129 RowStatus, TruthValue, MacAddress 130 FROM SNMPv2-TC 131 ifIndex 132 FROM IF-MIB 133 MODULE-COMPLIANCE, OBJECT-GROUP 134 FROM SNMPv2-CONF; 136 efmCommonMIB MODULE-IDENTITY 137 LAST-UPDATED "200310130000Z" -- October 13, 2003 138 ORGANIZATION "IETF Ethernet Interfaces and Hub MIB 139 Working Group" 140 CONTACT-INFO 141 " 142 WG Charter: 143 http://www.ietf.org/html.charters/hubmib-charter.html 144 Mailing lists: 145 General Discussion: hubmib@ietf.org 146 To Subscribe: hubmib-requests@ietf.org 147 In Body: subscribe your_email_address 148 Chair: Dan Romascanu 149 Avaya 150 Tel: +972-3-645-8414 151 Email: dromasca@avaya.com 152 Editor: Matt Squire 153 Hatteras Networks 154 Tel: +1-919-991-5460 155 Fax: +1-919-991-0743 156 E-mail: msquire@hatterasnetworks.com 157 " 159 draft-squire-hubmib-efm-mib-00.txt October 2003 161 DESCRIPTION 162 "The MIB module for managing the new common Ethernet 163 features introduced by the Ethernet in the First 164 Mile task force (IEEE P802.3ah). The functionality 165 presented here is based on IEEE P802.3ah/D2.1, 166 released in October 2003. 168 In particular, this MIB focused on the changes to 169 Clause 30 of the draft that are not specific to any 170 physical layer. 172 The following reference is used throughout this MIB 173 module: 175 [802.3ah] refers to: 176 IEEE P802.3ah/D2.1 178 Copyright (c) The Internet Society (2003). This 179 version of this MIB module is part of RFC XXXX; 180 See the RFC itself for full legal notices. " 182 REVISION "200310130000Z" -- October 13, 2003 183 DESCRIPTION "Initial version, published as RFC XXXX." 185 ::= { mib-2 XXX } 186 -- EditorsNote: Its unclear where in the existing MIB hierarchy 187 -- we wish to hang these new capabilities. For now, putting this 188 -- as separate from dot3, though I question if that�s the right 189 -- thing to do. If this is common Ethernet function, it should 190 -- probably go into the dot3 MIB. 191 -- 193 dot3OamMIB OBJECT IDENTIFIER ::= { efmCommonMIB 1} 195 -- 196 -- Ethernet OAM Control group 197 -- 199 dot3OamTable OBJECT-TYPE 200 SYNTAX SEQUENCE OF Dot3OamEntry 201 MAX-ACCESS not-accessible 202 STATUS current 203 DESCRIPTION "Primary controls and status for the OAM 204 capabilities of an Ethernet like interface. 205 There will be one row in this table for each 206 Ethernet like interface in the system that 207 Supports the Ethernet OAM functions defined 208 IEEE 802.3ah." 209 ::= { dot3OamMIB 1 } 211 dot3OamEntry OBJECT-TYPE 213 draft-squire-hubmib-efm-mib-00.txt October 2003 215 SYNTAX Dot3OamEntry 216 MAX-ACCESS not-accessible 217 STATUS current 218 DESCRIPTION "An entry in the table, containing 219 information on the Ethernet OAM function for 220 a single Ethernet-like interface." 221 INDEX { ifIndex } 222 ::= { dot3OamTable 1 } 224 Dot3OamEntry ::= 225 SEQUENCE { 226 dot3OamRowStatus RowStatus, 227 dot3OamAdminState INTEGER, 228 dot3OamMode INTEGER, 229 dot3OamOperStatus INTEGER, 230 dot3OamUnidirectionalSupport TruthValue, 231 dot3OamLoopbackSupport TruthValue, 232 dot3OamEventSupport TruthValue, 233 dot3OamVariableSupport TruthValue, 234 dot3OamMaxOamPduSize Unsigned32, 235 dot3OamConfigRevision Unsigned32, 236 dot3OamMultiplexorState INTEGER, 237 dot3OamParserState INTEGER 238 -- dot3OamErrSymPeriodWindowConfig Unsigned32, 239 -- dot3OamErrSymPeriodThresholdConfig Unsigned32, 240 -- dot3OamErrFrameWindowConfig Unsigned32, 241 -- dot3OamErrFrameThresholdConfig Unsigned32, 242 -- dot3OamErrFramePeriodWindowConfig Unsigned32, 243 -- dot3OamErrFramePeriodThresholdConfig Unsigned32, 244 -- dot3OamErrFrameSecsSummaryWindowConfig Unsigned32, 245 -- dot3OamErrFrameSecsSummaryThresholdConfig Unsigned32 246 } 248 dot3OamRowStatus OBJECT-TYPE 249 SYNTAX RowStatus 250 MAX-ACCESS read-create 251 STATUS current 252 DESCRIPTION "Implementation and activation of OAM is 253 optional, therefore creation of the row is 254 non-automatic. 255 " 256 REFERENCE "[802.3ah], 57.1.2 point d.1" 257 ::= { dot3OamEntry 1} 259 dot3OamAdminState OBJECT-TYPE 260 SYNTAX INTEGER { 261 disabled(1), 262 enabled(2) 263 } 264 MAX-ACCESS read-write 265 STATUS current 266 DESCRIPTION "This object is used to configure the default 267 administrative OAM mode for this interface. 269 draft-squire-hubmib-efm-mib-00.txt October 2003 271 This object represents the administratively 272 configured OAM state for this interface." 273 REFERENCE "[802.3ah], 30.11.1.1.2" 274 ::= { dot3OamEntry 2 } 276 dot3OamMode OBJECT-TYPE 277 SYNTAX INTEGER { 278 active(1), 279 passive(2) 280 } 281 MAX-ACCESS read-write 282 STATUS current 283 DESCRIPTION "This object configures the mode of OAM 284 operation for this Ethernet like interface. 285 OAM on Ethernet interfaces may be in 286 active(1) mode or passive(2) mode. These two 287 modes differ in that active mode provides 288 additional capabilities to initiate 289 monitoring activities with the remote OAM 290 peer entity, while passive mode generally 291 waits for the peer to initiate OAM actions 292 with it." 293 REFERENCE "[802.3ah], 30.11.1.1.3" 294 ::= { dot3OamEntry 3 } 296 dot3OamOperStatus OBJECT-TYPE 297 SYNTAX INTEGER { 298 passiveWait(1), 299 activeSendLocal(2), 300 sendLocalAndRemote1(3), 301 sendLocalAndRemote2(4), 302 oamPeeringLocallyRejected(5), 303 oamPeeringRemotelyRejected(6), 304 operational(7) 305 } 306 MAX-ACCESS read-only 307 STATUS current 308 DESCRIPTION "At initialization and failure conditions, 309 OAM entities on the same Ethernet link begin 310 a 311 discovery phase to determine what OAM 312 capabilities maybe used on that link. The 313 progress of the initialization is controlled 314 by the OAM layer. These progress is 315 reflected by the attributes ..... 316 NEED TO ADD THINGS TO CLAUSE 30 317 " 318 REFERENCE "[802.3ah], REFERENCE TBD" 319 ::= { dot3OamEntry 4 } 320 -- EditorsNote: Need to expose above in C30, not there 321 -- 323 dot3OamUnidirectionalSupport OBJECT-TYPE 325 draft-squire-hubmib-efm-mib-00.txt October 2003 327 SYNTAX TruthValue 328 MAX-ACCESS read-write 329 STATUS current 330 DESCRIPTION "Whether the OAM entity supports 331 unidirectional operation." 332 REFERENCE "[802.3ah], REFERENCE TBD" 333 ::= { dot3OamEntry 5 } 334 -- EditorsNote: Likely not configurable depending 335 -- on the media type 337 dot3OamLoopbackSupport OBJECT-TYPE 338 SYNTAX TruthValue 339 MAX-ACCESS read-write 340 STATUS current 341 DESCRIPTION "Whether the OAM entity adheres to loopback 342 command." 343 REFERENCE "[802.3ah], REFERENCE TBD" 344 ::= { dot3OamEntry 6 } 346 dot3OamEventSupport OBJECT-TYPE 347 SYNTAX TruthValue 348 MAX-ACCESS read-write 349 STATUS current 350 DESCRIPTION "Whether the OAM entity sends and interprets 351 link events." 352 REFERENCE "[802.3ah], REFERENCE TBD" 353 ::= { dot3OamEntry 7 } 355 dot3OamVariableSupport OBJECT-TYPE 356 SYNTAX TruthValue 357 MAX-ACCESS read-write 358 STATUS current 359 DESCRIPTION "Whether the OAM entity responds to variable 360 requests." 361 REFERENCE "[802.3ah], REFERENCE TBD" 362 ::= { dot3OamEntry 8 } 364 dot3OamMaxOamPduSize OBJECT-TYPE 365 SYNTAX Unsigned32 366 MAX-ACCESS read-write 367 STATUS current 368 DESCRIPTION "The largest OAMPDU that the OAM entity 369 supports." 370 REFERENCE "[802.3ah], REFERENCE TBD" 371 ::= { dot3OamEntry 9 } 373 dot3OamConfigRevision OBJECT-TYPE 374 SYNTAX Unsigned32 375 MAX-ACCESS read-only 376 STATUS current 377 DESCRIPTION "The configuration revision of the OAM entity 378 as reflected in the latest OAMPDU sent by the 379 OAM entity. 381 draft-squire-hubmib-efm-mib-00.txt October 2003 383 " 384 REFERENCE "[802.3ah], REFERENCE TBD" 385 ::= { dot3OamEntry 10 } 387 dot3OamMultiplexorState OBJECT-TYPE 388 SYNTAX INTEGER { 389 forward(1), 390 discard(2) 391 } 392 MAX-ACCESS read-only 393 STATUS current 394 DESCRIPTION "The state of the multiplexor function for 395 the OAM entity. 396 " 397 REFERENCE "[802.3ah], REFERENCE TBD" 398 ::= { dot3OamEntry 11 } 400 dot3OamParserState OBJECT-TYPE 401 SYNTAX INTEGER { 402 forward(1), 403 loopback(2), 404 discard(3) 405 } 406 MAX-ACCESS read-only 407 STATUS current 408 DESCRIPTION "The state of the multiplexor function for 409 the OAM entity. 410 " 411 REFERENCE "[802.3ah], REFERENCE TBD" 412 ::= { dot3OamEntry 12 } 414 -- 415 -- Ethernet OAM Statistics group 416 -- 418 dot3OamStatsTable OBJECT-TYPE 419 SYNTAX SEQUENCE OF Dot3OamStatsEntry 420 MAX-ACCESS not-accessible 421 STATUS current 422 DESCRIPTION "Statistics for the OAM function on a 423 particular Ethernet like interface." 424 ::= { dot3OamMIB 2 } 426 dot3OamStatsEntry OBJECT-TYPE 427 SYNTAX Dot3OamStatsEntry 428 MAX-ACCESS not-accessible 429 STATUS current 430 DESCRIPTION "An entry in the table, containing statistics 431 information on the Ethernet OAM function for 432 a single Ethernet-like interface." 433 INDEX { ifIndex } 434 ::= { dot3OamStatsTable 1 } 436 draft-squire-hubmib-efm-mib-00.txt October 2003 438 Dot3OamStatsEntry ::= 439 SEQUENCE { 440 dot3OamPduTx Counter32, 441 dot3OamPduRx Counter32, 442 dot3OamInformationTx Counter32, 443 dot3OamInformationRx Counter32, 444 dot3OamEventNotificationTx Counter32, 445 dot3OamUniqueEventNotificationRx Counter32, 446 dot3OamDuplicateEventNotificationRx Counter32, 447 dot3OamLoopbackControlTx Counter32, 448 dot3OamLoopbackControlRx Counter32, 449 dot3OamVariableRequestTx Counter32, 450 dot3OamVariableRequestRx Counter32, 451 dot3OamVariableResponseTx Counter32, 452 dot3OamVariableResponseRx Counter32, 453 dot3OamOrgSpecificTx Counter32, 454 dot3OamOrgSpecificRx Counter32, 455 dot3OamUnsupportedCodesRx Counter32 456 } 458 dot3OamPduTx OBJECT-TYPE 459 SYNTAX Counter32 460 MAX-ACCESS read-only 461 STATUS current 462 DESCRIPTION "A count of the number of Ethernet OAM frames 463 transmitted on this interface." 464 REFERENCE "[802.3ah], 30.11.1.1.14." 465 ::= { dot3OamStatsEntry 1 } 467 dot3OamPduRx OBJECT-TYPE 468 SYNTAX Counter32 469 MAX-ACCESS read-only 470 STATUS current 471 DESCRIPTION "A count of the number of Ethernet OAM frames 472 received on this interface." 473 REFERENCE "[802.3ah], 30.11.1.1.15." 474 ::= { dot3OamStatsEntry 2 } 476 dot3OamInformationTx OBJECT-TYPE 477 SYNTAX Counter32 478 MAX-ACCESS read-only 479 STATUS current 480 DESCRIPTION "A count of the number of Information OAMPDUs 481 transmitted on this interface." 482 REFERENCE "[802.3ah], 30.11.1.1.17." 483 ::= { dot3OamStatsEntry 3 } 485 dot3OamInformationRx OBJECT-TYPE 486 SYNTAX Counter32 487 MAX-ACCESS read-only 488 STATUS current 489 DESCRIPTION "A count of the number of Information OAMPDUs 491 draft-squire-hubmib-efm-mib-00.txt October 2003 493 received on this interface." 494 REFERENCE "[802.3ah], 30.11.1.1.18." 495 ::= { dot3OamStatsEntry 4 } 497 dot3OamEventNotificationTx OBJECT-TYPE 498 SYNTAX Counter32 499 MAX-ACCESS read-only 500 STATUS current 501 DESCRIPTION "A count of the number of Event OAMPDUs 502 transmitted on this interface." 503 REFERENCE "[802.3ah], 30.11.1.1.19." 504 ::= { dot3OamStatsEntry 5 } 506 dot3OamUniqueEventNotificationRx OBJECT-TYPE 507 SYNTAX Counter32 508 MAX-ACCESS read-only 509 STATUS current 510 DESCRIPTION "A count of the number of unique Event 511 OAMPDUs received on this interface." 512 REFERENCE "[802.3ah], 30.11.1.1.20." 513 ::= { dot3OamStatsEntry 6 } 515 dot3OamDuplicateEventNotificationRx OBJECT-TYPE 516 SYNTAX Counter32 517 MAX-ACCESS read-only 518 STATUS current 519 DESCRIPTION "A count of the number of duplicate Event 520 OAMPDUs received on this interface." 521 REFERENCE "[802.3ah], 30.11.1.1.21." 522 ::= { dot3OamStatsEntry 7 } 524 dot3OamLoopbackControlTx OBJECT-TYPE 525 SYNTAX Counter32 526 MAX-ACCESS read-only 527 STATUS current 528 DESCRIPTION "A count of the number of Loopback OAMPDUs 529 transmitted on this interface." 530 REFERENCE "[802.3ah], 30.11.1.1.22." 531 ::= { dot3OamStatsEntry 8 } 533 dot3OamLoopbackControlRx OBJECT-TYPE 534 SYNTAX Counter32 535 MAX-ACCESS read-only 536 STATUS current 537 DESCRIPTION "A count of the number of Loopback OAMPDUs 538 received on this interface." 539 REFERENCE "[802.3ah], 30.11.1.1.23." 540 ::= { dot3OamStatsEntry 9 } 542 dot3OamVariableRequestTx OBJECT-TYPE 543 SYNTAX Counter32 544 MAX-ACCESS read-only 545 STATUS current 547 draft-squire-hubmib-efm-mib-00.txt October 2003 549 DESCRIPTION "A count of the number of Variable Request 550 OAMPDUs transmitted on this interface." 551 REFERENCE "[802.3ah], 30.11.1.1.24." 552 ::= { dot3OamStatsEntry 10 } 554 dot3OamVariableRequestRx OBJECT-TYPE 555 SYNTAX Counter32 556 MAX-ACCESS read-only 557 STATUS current 558 DESCRIPTION "A count of the number of Variable Request 559 OAMPDUs received on this interface." 560 REFERENCE "[802.3ah], 30.11.1.1.25." 561 ::= { dot3OamStatsEntry 11 } 563 dot3OamVariableResponseTx OBJECT-TYPE 564 SYNTAX Counter32 565 MAX-ACCESS read-only 566 STATUS current 567 DESCRIPTION "A count of the number of Variable Response 568 OAMPDUs transmitted on this interface." 569 REFERENCE "[802.3ah], 30.11.1.1.26." 570 ::= { dot3OamStatsEntry 12 } 572 dot3OamVariableResponseRx OBJECT-TYPE 573 SYNTAX Counter32 574 MAX-ACCESS read-only 575 STATUS current 576 DESCRIPTION "A count of the number of Variable Response 577 OAMPDUs received on this interface." 578 REFERENCE "[802.3ah], 30.11.1.1.27." 579 ::= { dot3OamStatsEntry 13 } 581 dot3OamOrgSpecificTx OBJECT-TYPE 582 SYNTAX Counter32 583 MAX-ACCESS read-only 584 STATUS current 585 DESCRIPTION "A count of the number of Organizational 586 Specific OAMPDUs transmitted on this 587 interface." 588 REFERENCE "[802.3ah], 30.11.1.1.28." 589 ::= { dot3OamStatsEntry 14 } 591 dot3OamOrgSpecificRx OBJECT-TYPE 592 SYNTAX Counter32 593 MAX-ACCESS read-only 594 STATUS current 595 DESCRIPTION "A count of the number of Organizational 596 Specific OAMPDUs received on this interface." 597 REFERENCE "[802.3ah], 30.11.1.1.29." 598 ::= { dot3OamStatsEntry 15 } 600 dot3OamUnsupportedCodesRx OBJECT-TYPE 601 SYNTAX Counter32 603 draft-squire-hubmib-efm-mib-00.txt October 2003 605 MAX-ACCESS read-only 606 STATUS current 607 DESCRIPTION "A count of the number of OAMPDUs with an 608 unrecognized type received on this 609 interface." 610 REFERENCE "[802.3ah], 30.11.1.1.16." 611 ::= { dot3OamStatsEntry 16 } 613 -- 614 -- Ethernet OAM Peer group 615 -- 617 dot3OamPeerTable OBJECT-TYPE 618 SYNTAX SEQUENCE OF Dot3OamPeerEntry 619 MAX-ACCESS not-accessible 620 STATUS current 621 DESCRIPTION "Information about the OAM peer for a 622 particular Ethernet like interface." 623 ::= { dot3OamMIB 3 } 625 dot3OamPeerEntry OBJECT-TYPE 626 SYNTAX Dot3OamPeerEntry 627 MAX-ACCESS not-accessible 628 STATUS current 629 DESCRIPTION "An entry in the table, containing statistics 630 information on the Ethernet OAM function for 631 a single Ethernet-like interface." 632 INDEX { ifIndex } 633 ::= { dot3OamPeerTable 1 } 635 -- 636 -- EditorsNote - Is this defined anywhere else? 637 Oui ::= 638 OCTET STRING(SIZE(3)) 640 Dot3OamPeerEntry ::= 641 SEQUENCE { 642 dot3OamPeerRowStatus RowStatus, 643 dot3OamPeerMacAddress MacAddress, 644 dot3OamPeerVendorOui Oui, 645 dot3OamPeerVendorInfo Unsigned32, 646 dot3OamPeerMode INTEGER, 647 dot3OamPeerUnidirectionalSupport TruthValue, 648 dot3OamPeerLoopbackSupport TruthValue, 649 dot3OamPeerEventSupport TruthValue, 650 dot3OamPeerVariableSupport TruthValue, 651 dot3OamPeerMaxOamPduSize Integer32, 652 dot3OamPeerConfigRevision Integer32, 653 dot3OamPeerMultiplexorState INTEGER, 654 dot3OamPeerParserState INTEGER 655 } 657 dot3OamPeerRowStatus OBJECT-TYPE 659 draft-squire-hubmib-efm-mib-00.txt October 2003 661 SYNTAX RowStatus 662 MAX-ACCESS read-create 663 STATUS current 664 DESCRIPTION "The peer row is only created when the 665 dot3OamOperStatus of this particular Ethernet 666 interface is not passiveWait or 667 activeSendLocal." 668 REFERENCE "N/A" 669 ::= { dot3OamPeerEntry 1} 671 dot3OamPeerMacAddress OBJECT-TYPE 672 SYNTAX MacAddress 673 MAX-ACCESS read-only 674 STATUS current 675 DESCRIPTION "The MAC address of the remote OAM peer 676 entity." 677 REFERENCE "[802.3ah], 30.11.1.1.4." 678 ::= { dot3OamPeerEntry 2 } 680 dot3OamPeerVendorOui OBJECT-TYPE 681 SYNTAX Oui 682 MAX-ACCESS read-only 683 STATUS current 684 DESCRIPTION "The OUI of the OAM peer as reflected in the 685 latest information OAMPDU." 686 REFERENCE "[802.3ah], 30.11.1.1.11." 687 ::= { dot3OamPeerEntry 3 } 689 dot3OamPeerVendorInfo OBJECT-TYPE 690 SYNTAX Unsigned32 691 MAX-ACCESS read-only 692 STATUS current 693 DESCRIPTION "The Vendor Info of the OAM peer as reflected 694 in the latest information OAMPDU." 695 REFERENCE "[802.3ah], 30.11.1.1.12, 30.11.1.1.13" 696 ::= { dot3OamPeerEntry 4 } 698 dot3OamPeerMode OBJECT-TYPE 699 SYNTAX INTEGER { 700 active(1), 701 passive(2) 702 } 703 MAX-ACCESS read-only 704 STATUS current 705 DESCRIPTION "The mode of the OAM peer as reflected in the 706 latest OAMPDU. 707 " 708 REFERENCE "[802.3ah], 30.11.1.1.5." 709 ::= { dot3OamPeerEntry 5 } 711 dot3OamPeerUnidirectionalSupport OBJECT-TYPE 712 SYNTAX TruthValue 713 MAX-ACCESS read-only 715 draft-squire-hubmib-efm-mib-00.txt October 2003 717 STATUS current 718 DESCRIPTION "Whether the OAM peer supports unidirectional 719 operation as reflected in the latest OAMPDU. 720 " 721 REFERENCE "[802.3ah], 30.11.1.1.5." 722 ::= { dot3OamPeerEntry 6 } 724 dot3OamPeerLoopbackSupport OBJECT-TYPE 725 SYNTAX TruthValue 726 MAX-ACCESS read-only 727 STATUS current 728 DESCRIPTION "Whether the OAM peer supports loopback 729 operation as reflected in the latest OAMPDU. 730 " 731 REFERENCE "[802.3ah], 30.11.1.1.5." 732 ::= { dot3OamPeerEntry 7 } 734 dot3OamPeerEventSupport OBJECT-TYPE 735 SYNTAX TruthValue 736 MAX-ACCESS read-only 737 STATUS current 738 DESCRIPTION "Whether the OAM peer supports event 739 notification operation as reflected in the 740 latest OAMPDU. 741 " 742 REFERENCE "[802.3ah], 30.11.1.1.5." 743 ::= { dot3OamPeerEntry 8 } 745 dot3OamPeerVariableSupport OBJECT-TYPE 746 SYNTAX TruthValue 747 MAX-ACCESS read-only 748 STATUS current 749 DESCRIPTION "Whether the OAM peer supports variable 750 request operation as reflected in the latest 751 OAMPDU. 752 " 753 REFERENCE "[802.3ah], 30.11.1.1.5." 754 ::= { dot3OamPeerEntry 9 } 756 dot3OamPeerMaxOamPduSize OBJECT-TYPE 757 SYNTAX Integer32 758 MAX-ACCESS read-only 759 STATUS current 760 DESCRIPTION "The maximum size of OAMPDU supported by the 761 peer as reflected in the latest OAMPDU. 762 Ethernet OAM on this interface must not 763 use OAMPDUs that exceed this size. 764 " 765 REFERENCE "[802.3ah], 30.11.1.1.6." 766 ::= { dot3OamPeerEntry 10 } 768 dot3OamPeerConfigRevision OBJECT-TYPE 769 SYNTAX Integer32 771 draft-squire-hubmib-efm-mib-00.txt October 2003 773 MAX-ACCESS read-only 774 STATUS current 775 DESCRIPTION "The configuration revision of the OAM peer 776 as reflected in the latest OAMPDU. This 777 attribute is changed by the peer whenever it 778 has a local configuration change for Ethernet 779 OAM this interface. 780 " 781 REFERENCE "[802.3ah], 30.11.1.1.9." 782 ::= { dot3OamPeerEntry 11 } 784 dot3OamPeerMultiplexorState OBJECT-TYPE 785 SYNTAX INTEGER { 786 forward(1), 787 discard(2) 788 } 789 MAX-ACCESS read-only 790 STATUS current 791 DESCRIPTION "The state of the multiplexor function in the 792 OAM peer as reflected in the latest OAMPDU. 793 This value is changed based on loopback 794 actions by either the local or remote device. 795 The normal value for this attribute is 796 forward. When the performing loopback 797 operations, the value goes to discard. 798 " 799 REFERENCE "[802.3ah], 30.11.1.1.10." 800 ::= { dot3OamPeerEntry 12 } 802 dot3OamPeerParserState OBJECT-TYPE 803 SYNTAX INTEGER { 804 forward(1), 805 loopback(2), 806 discard(3) 807 } 808 MAX-ACCESS read-only 809 STATUS current 810 DESCRIPTION "The state of the parser function in the 811 OAM peer as reflected in the latest OAMPDU. 812 This value is changed based on loopback 813 actions by either the local or remote 814 device. The normal value for this attribute 815 is forward. 816 When the performing loopback operations, the 817 value goes to discard (when traffic is 818 looped back at the peer) or loopback (when 819 traffic is looped back locally). 820 " 821 REFERENCE "[802.3ah], 30.11.1.1.10." 822 ::= { dot3OamPeerEntry 13 } 824 -- 825 -- Ethernet OAM Event group 827 draft-squire-hubmib-efm-mib-00.txt October 2003 829 -- 830 -- Needs to be filled in TBD TBD !! 832 -- 833 -- Ethernet OAM Compliance group 834 -- 835 -- Needs to be filled in TBD TBD !! 837 END 839 6 Security Considerations 841 7 References 843 8 Acknowledgments 845 9 Author's Addresses 847 Matt Squire 848 Hatteras Networks 849 639 Davis Drive 850 Suite 200 851 Research Triangle Park, NC 27709 852 Email: msquire@hatterasnetworks.com