idnits 2.17.1 draft-ietf-hubmib-efm-epon-mib-03.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1.a on line 16. -- Found old boilerplate from RFC 3978, Section 5.5 on line 2663. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 2635. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 2642. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 2648. ** The document seems to lack an RFC 3978 Section 5.1 IPR Disclosure Acknowledgement. ** This document has an original RFC 3978 Section 5.4 Copyright Line, instead of the newer IETF Trust Copyright according to RFC 4748. ** This document has an original RFC 3978 Section 5.5 Disclaimer, instead of the newer disclaimer which includes the IETF Trust according to RFC 4748. ** The document uses RFC 3667 boilerplate or RFC 3978-like boilerplate instead of verbatim RFC 3978 boilerplate. After 6 May 2005, submission of drafts without verbatim RFC 3978 boilerplate is not accepted. The following non-3978 patterns matched text found in the document. That text should be removed or replaced: This document is an Internet-Draft and is subject to all provisions of Section 3 of RFC 3667. By submitting this Internet-Draft, each author represents that any applicable patent or other IPR claims of which he or she is aware have been or will be disclosed, and any of which he or she becomes aware will be disclosed, in accordance with Section 6 of BCP 79. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- == There are 7 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 == The document seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (March 11, 2005) is 6983 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: 'RFC2864' is defined on line 2601, but no explicit reference was found in the text -- Unexpected draft version: The latest known version of draft-squire-hubmib-efm-mib is -00, but you're referring to -02. -- Possible downref: Normative reference to a draft: ref. 'I-D.ietf-hubmib-efm-mib' ** Obsolete normative reference: RFC 1493 (Obsoleted by RFC 4188) ** Downref: Normative reference to an Historic RFC: RFC 1525 ** Obsolete normative reference: RFC 2669 (Obsoleted by RFC 4639) ** Obsolete normative reference: RFC 2737 (Obsoleted by RFC 4133) ** Obsolete normative reference: RFC 3636 (Obsoleted by RFC 4836) Summary: 10 errors (**), 0 flaws (~~), 5 warnings (==), 9 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 EPON MIB WG L. Khermosh 3 Internet-Draft Passave Technologies 4 Expires: September 12, 2005 March 11, 2005 6 Managed Objects of EPON 7 draft-ietf-hubmib-efm-epon-mib-03.txt 9 Status of this Memo 11 This document is an Internet-Draft and is subject to all provisions 12 of Section 3 of RFC 3667. By submitting this Internet-Draft, each 13 author represents that any applicable patent or other IPR claims of 14 which he or she is aware have been or will be disclosed, and any of 15 which he or she become aware will be disclosed, in accordance with 16 RFC 3668. 18 Internet-Drafts are working documents of the Internet Engineering 19 Task Force (IETF), its areas, and its working groups. Note that 20 other groups may also distribute working documents as 21 Internet-Drafts. 23 Internet-Drafts are draft documents valid for a maximum of six months 24 and may be updated, replaced, or obsoleted by other documents at any 25 time. It is inappropriate to use Internet-Drafts as reference 26 material or to cite them other than as "work in progress." 28 The list of current Internet-Drafts can be accessed at 29 http://www.ietf.org/ietf/1id-abstracts.txt. 31 The list of Internet-Draft Shadow Directories can be accessed at 32 http://www.ietf.org/shadow.html. 34 This Internet-Draft will expire on September 12, 2005. 36 Copyright Notice 38 Copyright (C) The Internet Society (2005). 40 Abstract 42 This document defines a portion of the Management Information Base 43 (MIB) for use with network management protocols in TCP/IP based 44 Internets. In particular, it defines objects for managing devices 45 and interfaces that conform to the Ethernet Passive Optical Networks 46 (EPON) standards as defined in IEEE 802.3-2004. The document 47 contains a list of management entities based on the registers defined 48 in the Institute of Electrical and Electronic Engineers, IEEE 49 802.3-2004 Annex 30A and mainly partitioned accordingly. 51 Table of Contents 53 1. Terminology . . . . . . . . . . . . . . . . . . . . . . . . 3 54 2. The Internet-Standard Management Framework . . . . . . . . . 4 55 3. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 5 56 4. Relationship of the EFM EPON MIB and EPON device MIB to 57 other MIBs . . . . . . . . . . . . . . . . . . . . . . . . . 6 58 4.1 Relationship of the EFM EPON MIB to the Interfaces MIB . . 6 59 4.2 Relationship of the EFM EPON MIB to the Ethernet-like 60 Interfaces MIB . . . . . . . . . . . . . . . . . . . . . . 6 61 4.3 Relationship of the EFM EPON MIB to the MAU MIB EFM 62 EPON interfaces . . . . . . . . . . . . . . . . . . . . . 6 63 4.4 Relationship of the EFM EPON MIB to the EFM OAM MIB . . . 6 64 4.5 Relationship of the EPON Device MIB to EFM EPON MIB . . . 6 65 4.6 Relationship of the EPON Device MIB to Optical 66 interface MIB . . . . . . . . . . . . . . . . . . . . . . 6 67 4.7 Relationship of the EPON Device MIB to bridge MIB . . . . 6 68 4.8 Relationship of the EPON Device MIB to the Entity MIB . . 7 69 4.9 Relationship of the EPON Device MIB to the Entity 70 Sensor MIB . . . . . . . . . . . . . . . . . . . . . . . . 7 71 5. IANA Considerations . . . . . . . . . . . . . . . . . . . . 8 72 6. MIB structure . . . . . . . . . . . . . . . . . . . . . . . 9 73 7. Relationship table of the dot3EFM MIB module objects to 74 the IEEE802.3 objects . . . . . . . . . . . . . . . . . . . 10 75 8. Definitions - The EFM EPON MIB module . . . . . . . . . . . 14 76 9. Definitions - The EPON Device MIB . . . . . . . . . . . . . 39 77 10. Security Considerations . . . . . . . . . . . . . . . . . . 59 78 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 61 79 11.1 Normative References . . . . . . . . . . . . . . . . . . 61 80 11.2 Informative References . . . . . . . . . . . . . . . . . 62 81 Author's Address . . . . . . . . . . . . . . . . . . . . . . 62 82 Intellectual Property and Copyright Statements . . . . . . . 63 84 1. Terminology 86 Key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 87 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 88 document are to be interpreted as described in [RFC2119]. 90 2. The Internet-Standard Management Framework 92 For a detailed overview of the documents that describe the current 93 Internet-Standard Management Framework, please refer to section 7 of 94 RFC 3410 [RFC3410]. Managed objects are accessed via a virtual 95 information store, termed the Management Information Base or MIB. 96 MIB objects are generally accessed through the Simple Network 97 Management Protocol (SNMP). Objects in the MIB are defined using the 98 mechanisms defined in the Structure of Management Information (SMI). 99 This memo specifies a MIB module that is compliant to the SMIv2, 100 which is described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 101 [RFC2579] and STD 58, RFC 2580 [RFC2580]. 103 3. Overview 105 This document defines a portion of the Management Information Base 106 (MIB) for use with network management protocols in TCP/IP based 107 Internets. In particular, it defines objects for managing devices 108 and interfaces that conform to the Ethernet Passive Optical Networks 109 (EPON) standards as defined in [802.3]. The document contains a list 110 of management entities based on the registers defined in [802.3] 111 Annex 30A for EPON and partitioned accordingly. The document also 112 contains a device group section defining the MIB modules for EPON 113 from a device perspective, that are connected directly to the IEEE 114 802.3 EPON specifications. 116 4. Relationship of the EFM EPON MIB and EPON device MIB to other MIBs 118 4.1 Relationship of the EFM EPON MIB to the Interfaces MIB 120 Implementing this module MUST require implementation of Interfaces 121 MIB module [RFC2863]. The MIB modules defined in this document are 122 an extension of the MIB modules in this document. 124 4.2 Relationship of the EFM EPON MIB to the Ethernet-like Interfaces 125 MIB 127 Implementing this module MUST require implementation of Ethernet-like 128 Interfaces MIB module [RFC3635]. The MIB modules defined in this 129 document are an extension of the Ethernet-like Interfaces MIB 130 modules. For instance, the document is defining 131 dot3MpcpRemoteMACAddress only while assuming the local MAC address 132 attribute is already defined in [RFC3635]. 134 4.3 Relationship of the EFM EPON MIB to the MAU MIB EFM EPON interfaces 136 Implementing this module MUST require implementation of MAU-MIB 137 module [RFC3636]. The MIB modules defined in this document are an 138 extension of the MAU-MIB modules. 140 4.4 Relationship of the EFM EPON MIB to the EFM OAM MIB 142 EFM EPON interfaces MUST require implementation of EFM OAM MIB module 143 [I-D.ietf-hubmib-efm-mib]. This document defines OAM MIB module 144 attributes and managed objects that are complementary to the EFM EPON 145 MIB module. 147 4.5 Relationship of the EPON Device MIB to EFM EPON MIB 149 EPON devices MUST require implementation of the EFM EPON MIB module 150 which are specified in this document. The opposite is not required 151 as it possible to implement the EFM interfaces by itself. 153 4.6 Relationship of the EPON Device MIB to Optical interface MIB 155 EPON devices MAY implement the Optical interface MIB module 156 [RFC3591]. The optical interface MIB module document defines optical 157 interface attributes and managed objects that are assumed to be used 158 by an EPON device. 160 4.7 Relationship of the EPON Device MIB to bridge MIB 162 EPON OLT devices MAY implement the bridge MIB modules [RFC1493], 163 [RFC1525], Where the LLIDs of the PON are referred as the bridge 164 ports. There is a direct mapping between the bridge ports and the 165 LLIDs, which are virtual bridge ports. Attributes in the bridge MIB 166 module should be used accordingly. This document defines managed 167 objects for a bridge that are assumed to be used by an EPON OLT 168 device which bridges the data between the LLIDs of the PON. 170 4.8 Relationship of the EPON Device MIB to the Entity MIB 172 EPON OLT devices MAY implement the Entity MIB modules [RFC2737], 173 Where attributes like physical device ID and physical status, 174 Hardware status are used from that MIB module 176 4.9 Relationship of the EPON Device MIB to the Entity Sensor MIB 178 EPON OLT devices MAY implement the Entity Sensor MIB modules 179 [RFC3433], where various attributes of sensors entities of the EPON 180 device can be used from that MIB module 182 5. IANA Considerations 184 The EFM EPON MIB module requires the allocation of a single object 185 identifier for its MODULE-IDENTITY under the MIB-2 tree. The EPON 186 Device MIB module requires the allocation of a single object 187 identifier for its MODULE-IDENTITY under the MIB-2 tree. 189 6. MIB structure 191 This document includes two MIB modules, the first is the EFM EPON MIB 192 module and the second is the EPON device MIB module. The EFM EPON 193 MIB module defines the objects used for configuration and description 194 of the [802.3] Point to Multipoint (P2MP) section. These MIB module 195 objects are included in three MIB module groups. 197 The Multi-Point Control Protocol (MPCP) MIB module definition - MIB 198 module related to [802.3] clause 64 Multi Point Control Protocol 199 attributes. In this MIB module group: The dot3MpcpTable defines the 200 objects used for the configuration and description of the status of 201 MPCP ([802.3] Multi-Point Control Protocol) compliant interfaces. 202 The dot3MpcpStatTable defines the statistics group for MPCP compliant 203 interfaces. 205 The OMPEmulation MIB module definitions - MIB module related to 206 [802.3] clause 65 point to point emulation attributes. In this MIB 207 module group: The dot3OmpEmulationTable defines the objects used for 208 the configuration and description of the status of OMPEmulation 209 compliant interfaces. The dot3OmpEmulationStatTable defines the 210 statistics group for OMPEmulation compliant interfaces. 212 The MAU MIB module definition including MAU type definitions and EPON 213 MAU managed object related to [802.3] clause 60 and clause 65. The 214 dot3EponMauTable defines the objects used for the configuration and 215 description of the status of MAU EPON compliant interfaces. 217 The EPON Device MIB module defines the objects used for configuration 218 and description of management objects for EPON compliant Devices. 219 The eponDeviceControlTable defines the objects used for the 220 configuration and description of the EPON compliant devices. The 221 eponDeviceRemoteMACAddressLLIDTable defines the objects used for 222 configuration and description of the MacAddress to LLID table used 223 for the bridge emulation of the EPON devices. The 224 eponDeviceStatTable defines the objects used for the statistics group 225 of the EPON devices. 227 7. Relationship table of the dot3EFM MIB module objects to the 228 IEEE802.3 objects 230 oMPCP managed object class (30.3.5) 232 +----------------------+----------------------+---------------------+ 233 | dot3EFM MIB module | IEEE802.3 object | Reference | 234 | object | | | 235 +----------------------+----------------------+---------------------+ 236 | dot3MpcpID | aMPCPID | 30.3.5.1.1 | 237 | | | | 238 | dot3MpcpOperStatus | aMPCPAdminState | 30.3.5.1.2 | 239 | | | | 240 | dot3MpcpMode | aMPCPMode | 30.3.5.1.3 | 241 | | | | 242 | dot3MpcpLinkID | aMPCPLinkID | 30.3.5.1.4 | 243 | | | | 244 | dot3MpcpRemoteMACAdd | aMPCPRemoteMACAddres | 30.3.5.1.5 | 245 | ress | s | | 246 | | | | 247 | dot3MpcpRegistration | aMPCPRegistrationSta | 30.3.5.1.6 | 248 | State | te | | 249 | | | | 250 | dot3MpcpMACCtrlFrame | aMPCPMACCtrlFramesTr | 30.3.5.1.7 | 251 | sTransmitted | ansmitted | | 252 | | | | 253 | dot3MpcpMACCtrlFrame | aMPCPMACCtrlFramesRe | 30.3.5.1.8 | 254 | sReceived | ceived | | 255 | | | | 256 | dot3MpcpTxGate | aMPCPTxGate | 30.3.5.1.9 | 257 | | | | 258 | dot3MpcpTxRegAck | aMPCPTxRegAck | 30.3.5.1.10 | 259 | | | | 260 | dot3MpcpTxRegister | aMPCPTxRegister | 30.3.5.1.11 | 261 | | | | 262 | dot3MpcpTxRegRequest | aMPCPTxRegRequest | 30.3.5.1.12 | 263 | | | | 264 | dot3MpcpTxReport | aMPCPTxReport | 30.3.5.1.13 | 265 | | | | 266 | dot3MpcpRxGate | aMPCPRxGate | 30.3.5.1.14 | 267 | | | | 268 | dot3MpcpRxRegAck | aMPCPRxRegAck | 30.3.5.1.15 | 269 | | | | 270 | dot3MpcpRxRegister | aMPCPRxRegister | 30.3.5.1.16 | 271 | | | | 272 | dot3MpcpRxRegRequest | aMPCPRxRegRequest | 30.3.5.1.17 | 273 | | | | 274 | dot3MpcpRxReport | aMPCPRxReport | 30.3.5.1.18 | 275 | | | | 276 | dot3MpcpTransmitElap | aMPCPTransmitElapsed | 30.3.5.1.19 | 277 | sed | | | 278 | | | | 279 | dot3MpcpReceiveElaps | aMPCPReceiveElapsed | 30.3.5.1.20 | 280 | ed | | | 281 | | | | 282 | dot3MpcpRoundTripTim | aMPCPRoundTripTime | 30.3.5.1.21 | 283 | e | | | 284 | | | | 285 | dot3MpcpDiscoveryWin | aMPCPDiscoveryWindow | 30.3.5.1.22 | 286 | dowsSent | sSent | | 287 | | | | 288 | dot3MpcpDiscoveryTim | aMPCPDiscoveryTimeou | 30.3.5.1.23 | 289 | eout | t | | 290 | | | | 291 | dot3MpcpMaximumPendi | aMPCPMaximumPendingG | 30.3.5.1.24 | 292 | ngGrants | rants | | 293 | | | | 294 | dot3MpcpAdminState | aMPCPAdminControl | 30.3.5.2.1 | 295 | | | | 296 | dot3MpcpOnTime | laserOnTime | 64.3.5.1 | 297 | | | | 298 | dot3MpcpOffTime | laserOffTime | 64.3.5.1 | 299 | | | | 300 | dot3MpcpSyncTime | SyncTime | 64.3.3.2 | 301 +----------------------+----------------------+---------------------+ 303 Table 1 305 oOMPEmulation managed object class (30.3.7) 307 +----------------------+----------------------+---------------------+ 308 | dot3EFM MIB module | IEEE802.3 object | Reference | 309 | object | | | 310 +----------------------+----------------------+---------------------+ 311 | dot3OmpEmulationID | aOMPEmulationID | 30.3.7.1.1 | 312 | | | | 313 | dot3OmpEmulationType | aOMPEmulationType | 30.3.7.1.2 | 314 | | | | 315 | dot3OmpEmulationSLDE | aSLDErrors | 30.3.7.1.3 | 316 | rrors | | | 317 | | | | 318 | dot3OmpEmulationCRC8 | aCRC8Errors | 30.3.7.1.4 | 319 | Errors | | | 320 | | | | 321 | dot3OmpEmulationGood | aGoodLLID | 30.3.7.1.5 | 322 | LLID | | | 323 | | | | 324 | dot3OmpEmulationOnuP | aONUPONcastLLID | 30.3.7.1.6 | 325 | onCastLLID | | | 326 | | | | 327 | dot3OmpEmulationOltP | aOLTPONcastLLID | 30.3.7.1.7 | 328 | onCastLLID | | | 329 | | | | 330 | dot3OmpEmulationBadL | aBadLLID | 30.3.7.1.8 | 331 | LID | | | 332 | | | | 333 | dot3OmpEmulationBroa | | | 334 | dcastBitNotOnuLLid | | | 335 | | | | 336 | dot3OmpEmulationOnuL | | | 337 | LIDNotBroadcast | | | 338 | | | | 339 | dot3OmpEmulationBroa | | | 340 | dcastBitPlusOnuLlid | | | 341 | | | | 342 | dot3OmpEmulationNotB | | | 343 | roadcastBitNotOnuLli | | | 344 | d | | | 345 +----------------------+----------------------+---------------------+ 347 Table 2 349 oMAU managed object class (30.5.1) 351 +----------------------+----------------------+---------------------+ 352 | dot3EFM MIB module | IEEE802.3 object | Reference | 353 | object | | | 354 +----------------------+----------------------+---------------------+ 355 | dot3EponMauPCSCoding | aPCSCodingViolation | 30.5.1.1.12 | 356 | Violation | | | 357 | | | | 358 | dot3EponMauFecAbilit | aFECAbility | 30.5.1.1.13 | 359 | y | | | 360 | | | | 361 | dot3EponMauFecMode | aFECmode | 30.5.1.1.14 | 362 | | | | 363 | dot3EponMauFECCorrec | aFECCorrectedBlocks | 30.5.1.1.15 | 364 | tedBlocks | | | 365 | | | | 366 | dot3EponMauFECUncorr | aFECUncorrectableBlo | 30.5.1.1.16 | 367 | ectableBlocks | cks | | 368 | | | | 369 | dot3EponMauBufferHea | | | 370 | dCodingViolation | | | 371 +----------------------+----------------------+---------------------+ 373 Table 3 375 8. Definitions - The EFM EPON MIB module 377 (See section 30.2.5 in [802.3] for details) 379 DOT3-EFM-EPON-MIB DEFINITIONS ::= BEGIN 381 IMPORTS 382 MODULE-IDENTITY, mib-2, OBJECT-TYPE, Counter32, 383 Integer32 384 FROM SNMPv2-SMI 385 TruthValue, MacAddress 386 FROM SNMPv2-TC 387 ifIndex 388 FROM IF-MIB 389 MODULE-COMPLIANCE, OBJECT-GROUP 390 FROM SNMPv2-CONF 391 ; 393 dot3EfmeponMIB MODULE-IDENTITY 394 LAST-UPDATED "200503100000Z" -- March 10, 2005 395 ORGANIZATION "IETF Ethernet Interfaces and Hub MIB Working 396 Group" 397 CONTACT-INFO 398 "WG charter: 399 http://www.ietf.org/html.charters/hubmib-charter.html 400 Mailing Lists: 401 General Discussion: hubmib@ietf.org 402 To Subscribe: hubmib-request@ietf.org 403 In Body: subscribe your_email_address 404 Chair: Dan Romascanu 405 Postal: Avaya 406 Atidim Technology Park, Bldg. 3 407 Tel Aviv 61131 408 Israel 409 Tel: +972-3-645-8414 410 E-mail: dromasca@avaya.com 412 Editor: Lior Khermosh 413 Postal: Passave Technologies Inc. 414 Kohav Hertzelia bldg, 415 4 Hasadnaot St. 416 Hertzliya Pituach 46120, 417 ISRAEL 418 P.O.Box 2089 Hertzliya Pituach 46120 Israel 419 Tel: +972-9-9628000 Ext: 302 420 E-mail: lior.khermosh@passave.com" 421 DESCRIPTION 422 "The objects in this MIB module are used to manage the 423 Ethernet in the First Mile (EFM) Multi Point Control 424 Protocol (MPCP) Interfaces as defined in IEEE P802.3 425 clause 64,65. 426 The following reference is used throughout this MIB module: 427 [802.3] refers to: 428 IEEE Draft P802.3: 'Information technology - 429 Telecommunications and information exchange between 430 systems - Local and metropolitan area networks - 431 Specific requirements - 432 Part 3: Carrier sense multiple access with collision 433 detection (CSMA/CD) access method and physical layer 434 specifications - Media Access Control Parameters, 435 Physical Layers and Management Parameters for 436 subscriber access networks', 8 December 2004. 438 Of particular interest are Clause 64(MPCP) 65(P2MP RS) and 439 60 (PON PMDs). Clause 30, 'Management', and Clause 45, 440 'Management Data Input/Output (MDIO) Interface'. 442 Copyright (C) The Internet Society (2005). This version 443 of this MIB module is part of XXXX see the RFC itself for 444 full legal notices." 446 -- Editor's Note: Replace XXXX with the actual RFC number 447 -- assigned by RFC Editor and remove this note 449 REVISION "200503100000Z" -- March 10, 2005 450 DESCRIPTION "Initial version, published as RFC XXXX." 452 ::= { mib-2 XXX } 454 -- Editor's Note: Replace XXX with a real OID once it is 455 -- assigned by IANA and remove this note. 457 -- Editor-s note: MPCP MIB modules definitions ([802.3] 458 --- clause 30.3.5) 459 -- Editor-s note: Description in attributes with References should be 460 -- minimized in later versions 462 dot3MpcpMIB OBJECT IDENTIFIER ::= { dot3EfmeponMIB 1} 464 dot3MpcpObjects OBJECT IDENTIFIER ::= { dot3MpcpMIB 1} 466 dot3MpcpConformance OBJECT IDENTIFIER ::= { dot3MpcpMIB 2} 467 dot3MpcpTable OBJECT-TYPE 468 SYNTAX SEQUENCE OF Dot3MpcpEntry 469 MAX-ACCESS not-accessible 470 STATUS current 471 DESCRIPTION 472 "Table for dot3 Multi-Point Control Protocol (MPCP) 473 MIB modules." 474 ::= { dot3MpcpObjects 1 } 476 dot3MpcpEntry OBJECT-TYPE 477 SYNTAX Dot3MpcpEntry 478 MAX-ACCESS not-accessible 479 STATUS current 480 DESCRIPTION 481 "An entry in the dot3 MPCP MIB modules table." 482 INDEX { ifIndex } 483 ::= { dot3MpcpTable 1 } 485 Dot3MpcpEntry ::= 486 SEQUENCE { 487 dot3MpcpID Integer32, 488 dot3MpcpOperStatus TruthValue, 489 dot3MpcpMode INTEGER, 490 dot3MpcpLinkID Integer32, 491 dot3MpcpRemoteMACAddress MacAddress, 492 dot3MpcpRegistrationState INTEGER, 493 dot3MpcpTransmitElapsed Integer32, 494 dot3MpcpReceiveElapsed Integer32, 495 dot3MpcpRoundTripTime Integer32, 496 dot3MpcpMaximumPendingGrants Integer32, 497 dot3MpcpAdminState TruthValue, 498 dot3MpcpOnTime Integer32, 499 dot3MpcpOffTime Integer32, 500 dot3MpcpSyncTime Integer32 501 } 503 dot3MpcpID OBJECT-TYPE 504 SYNTAX Integer32 505 MAX-ACCESS read-only 506 STATUS current 507 DESCRIPTION 508 "This variable is assigned so as to uniquely identify the 509 Multi-Point MAC Control (MPCP) entity, as defined in 510 [802.3] clause 64, among the subordinate managed 511 objects of the containing object. 512 This attribute is relevant for an OLT and an ONU." 513 REFERENCE "[802.3], 30.3.5.1.1." 514 ::= { dot3MpcpEntry 1 } 516 dot3MpcpOperStatus OBJECT-TYPE 517 SYNTAX TruthValue 518 MAX-ACCESS read-only 519 STATUS current 520 DESCRIPTION 521 "This variable can be used to define the operational 522 state of the Multi-Point MAC Control sublayer as 523 defined in [802.3] clause 64. Selecting admin for an 524 interface with Multi-Point MAC Control sublayer. When 525 the attribute is True the the interface will act as if 526 Multi-point control protocol is enabled. When the 527 attribute is False the interface will act as if it does 528 not have the Multi-point control protocol. The 529 operational state can be changed using the 530 dot3MpcpAdminState attribute. 531 This attribute is relevant for an OLT and an ONU." 532 REFERENCE "[802.3], 30.3.5.1.2." 533 ::= { dot3MpcpEntry 2 } 535 dot3MpcpMode OBJECT-TYPE 536 SYNTAX INTEGER { 537 olt(1), 538 onu(2) 539 } 540 MAX-ACCESS read-only 541 STATUS current 542 DESCRIPTION 543 "This variable can be used to identify the operational 544 state of the Multi-Point MAC Control sublayer as 545 defined in [802.3] clause 64. Reading olt(1) for an 546 OLT (server) mode and onu(2) for an ONU (client) mode. 547 This attribute is relevant for an OLT and an ONU." 548 REFERENCE "[802.3], 30.3.5.1.3." 549 DEFVAL { 1 } 550 ::= { dot3MpcpEntry 3 } 552 dot3MpcpLinkID OBJECT-TYPE 553 SYNTAX Integer32 554 MAX-ACCESS read-only 555 STATUS current 556 DESCRIPTION 557 "A read-only value that identifies the Logical Link 558 identity (LLID) associated with the MAC port as 559 specified in [802.3] clause 65.1.3.2.2. 560 This attribute is relevant for an OLT and an ONU." 561 REFERENCE "[802.3], 30.3.5.1.4." 562 ::= { dot3MpcpEntry 4 } 564 dot3MpcpRemoteMACAddress OBJECT-TYPE 565 SYNTAX MacAddress 566 MAX-ACCESS read-only 567 STATUS current 568 DESCRIPTION 569 "A read-only value that identifies the source_address 570 parameter of the last MPCPDUs passed to the MAC Control. 571 This value is updated on reception of a valid frame with 572 (1) a destination Field equal to the reserved multicast 573 address for MAC Control specified in [802.3] Annex 574 31A, (2) lengthOrType field value equal to the reserved 575 Type for MAC Control as specified in [802.3] Annex 576 31A. (3) an MPCP subtype value equal to the subtype 577 reserved for MPCP as specified in [802.3] Annex 31A. 578 This attribute is relevant for an OLT and an ONU." 579 REFERENCE "[802.3], 30.3.5.1.5." 580 ::= { dot3MpcpEntry 5 } 582 dot3MpcpRegistrationState OBJECT-TYPE 583 SYNTAX INTEGER { 584 unregistered(1), 585 registering(2), 586 registered(3) 587 } 588 MAX-ACCESS read-only 589 STATUS current 590 DESCRIPTION 591 "A read-only value that identifies the operational state 592 of the Multi-Point MAC Control sublayer as defined in 593 [802.3] clause 64. When this attribute has the 594 enumeration unregistered(1) the interface may be used 595 for registering a link partner. When this attribute has 596 the enumeration registering(2) the interface is in the 597 process of registering a link-partner. When this 598 attribute has the enumeration registered(3) the 599 interface has an established link-partner. 600 This attribute is relevant for an OLT and an ONU. For 601 the OLT it provides an indication per LLID." 602 REFERENCE "[802.3], 30.3.5.1.6." 603 ::= { dot3MpcpEntry 6 } 605 dot3MpcpTransmitElapsed OBJECT-TYPE 606 SYNTAX Integer32 607 UNITS "TQ (16nsec)" 608 MAX-ACCESS read-only 609 STATUS current 610 DESCRIPTION 611 "A read-only value that reports the interval from last 612 MPCP frame transmission in increments of Time Quanta 613 (TQ) 16ns. The value returned shall be (interval from 614 last MPCP frame transmission in ns)/16. If this value 615 exceeds (2^32-1) the value (2^32-1) shall be returned. 616 This attribute is relevant for an OLT and an ONU." 617 REFERENCE "[802.3], 30.3.5.1.19." 618 ::= { dot3MpcpEntry 7 } 620 dot3MpcpReceiveElapsed OBJECT-TYPE 621 SYNTAX Integer32 622 UNITS "TQ (16nsec)" 623 MAX-ACCESS read-only 624 STATUS current 625 DESCRIPTION 626 "A read-only value that reports the interval from last 627 MPCP frame reception in increments of Time Quanta (TQ) 628 16ns. The value returned shall be (interval from last 629 MPCP last MPCP frame reception in ns)/16. If this value 630 exceeds (2^32-1) the value (2^32-1) shall be returned. 631 This attribute is relevant for an OLT and an ONU." 632 REFERENCE "[802.3], 30.3.5.1.20." 633 ::= { dot3MpcpEntry 8 } 635 dot3MpcpRoundTripTime OBJECT-TYPE 636 SYNTAX Integer32 637 UNITS "TQ (16nsec)" 638 MAX-ACCESS read-only 639 STATUS current 640 DESCRIPTION 641 "A read-only value that reports the MPCP round trip time 642 in increments of Time Quanta (TQ) 16ns. The value 643 returned shall be (round trip time in ns)/16. If this 644 value exceeds (2^16-1) the value (2^16-1) shall be 645 returned. This attribute is relevant for an OLT only. 646 For the OLT there is a value per LLID" 647 REFERENCE "[802.3], 30.3.5.1.21." 648 ::= { dot3MpcpEntry 9 } 650 dot3MpcpMaximumPendingGrants OBJECT-TYPE 651 SYNTAX Integer32 (0..255) 652 MAX-ACCESS read-only 653 STATUS current 654 DESCRIPTION 655 "A read-only value that indicates the maximum number of 656 grants an ONU can store. The maximum number of grants an 657 ONU can store has a range of 0 to 255. 658 This attribute is relevant for an OLT and an ONU. For 659 the OLT there is a value per LLID" 661 REFERENCE "[802.3], 30.3.5.1.24." 662 ::= { dot3MpcpEntry 10 } 664 dot3MpcpAdminState OBJECT-TYPE 665 SYNTAX TruthValue 666 MAX-ACCESS read-write 667 STATUS current 668 DESCRIPTION 669 "This variable can be used to define the operational 670 state of the Multi-Point MAC Control sublayer as defined 671 in [802.3] clause 64. Selecting admin for an interface 672 with Multi-Point MAC Control sublayer. When selecting 673 the value as True the interface Multi-Point control 674 protocol is enabled. When selecting the value as False 675 the interface acts as if the Multi-point Control 676 protocol does not exist. Reading reflects the state of 677 the attribute and the operation of the Multi-point 678 control protocol mode of the interface. 679 Writing can be done all the time. 680 This attribute is relevant for an OLT and an ONU." 681 REFERENCE "[802.3], 30.3.5.2.1." 682 DEFVAL { false } 683 ::= { dot3MpcpEntry 11 } 685 dot3MpcpOnTime OBJECT-TYPE 686 SYNTAX Integer32 687 UNITS "TQ (16nsec)" 688 MAX-ACCESS read-only 689 STATUS current 690 DESCRIPTION 691 "A read-only value that reports the -on time- for a grant 692 burst in increments of Time Quanta (TQ) 16ns as defined 693 in [802.3] 60,64. The value returned shall be (on time 694 ns)/16. If this value exceeds (2^32-1) the value 695 (2^32-1) shall be returned. Value is 32 TQs. 696 This attribute is relevant for an OLT and an ONU." 697 REFERENCE "[802.3], 64.3.5.1." 698 ::= { dot3MpcpEntry 12 } 700 dot3MpcpOffTime OBJECT-TYPE 701 SYNTAX Integer32 702 UNITS "TQ (16nsec)" 703 MAX-ACCESS read-only 704 STATUS current 705 DESCRIPTION 706 "A read-only value that reports the -off time- for a 707 grant burst in increments of Time Quanta (TQ) 16ns as 708 defined in [802.3] 60,64. The value returned shall be 709 (off time ns)/16. If this value exceeds (2^32-1) the 710 value (2^32-1) shall be returned. Value is 32 TQs. 711 This attribute is relevant for an OLT and an ONU." 712 REFERENCE "[802.3], 64.3.5.1." 713 ::= { dot3MpcpEntry 13 } 715 dot3MpcpSyncTime OBJECT-TYPE 716 SYNTAX Integer32 717 UNITS "TQ (16nsec)" 718 MAX-ACCESS read-only 719 STATUS current 720 DESCRIPTION 721 "A read-only value that reports the -sync lock time- for 722 an OLT receiver in increments of Time Quanta (TQ) 16ns 723 as defined in [802.3] 60,64,65. The value returned 724 shall be (sync lock time ns)/16. If this value exceeds 725 (2^32-1) the value (2^32-1) shall be returned. 726 This attribute is relevant for an OLT and an ONU." 727 REFERENCE "[802.3], 64.3.3.2." 728 ::= { dot3MpcpEntry 14 } 730 dot3MpcpStatTable OBJECT-TYPE 731 SYNTAX SEQUENCE OF Dot3MpcpStatEntry 732 MAX-ACCESS not-accessible 733 STATUS current 734 DESCRIPTION 735 "This table defines the list of statistics counters of 736 [802.3] clause 64 MPCP interface." 737 ::= { dot3MpcpObjects 2 } 739 dot3MpcpStatEntry OBJECT-TYPE 740 SYNTAX Dot3MpcpStatEntry 741 MAX-ACCESS not-accessible 742 STATUS current 743 DESCRIPTION 744 "Table entries for table of statistics counters of 745 [802.3] clause 64 MPCP interface." 746 INDEX { ifIndex } 747 ::= { dot3MpcpStatTable 1 } 749 Dot3MpcpStatEntry ::= 750 SEQUENCE { 751 dot3MpcpMACCtrlFramesTransmitted Counter32, 752 dot3MpcpMACCtrlFramesReceived Counter32, 753 dot3MpcpDiscoveryWindowsSent Counter32, 754 dot3MpcpDiscoveryTimeout Counter32, 755 dot3MpcpTxRegRequest Counter32, 756 dot3MpcpRxRegRequest Counter32, 757 dot3MpcpTxRegAck Counter32, 758 dot3MpcpRxRegAck Counter32, 759 dot3MpcpTxReport Counter32, 760 dot3MpcpRxReport Counter32, 761 dot3MpcpTxGate Counter32, 762 dot3MpcpRxGate Counter32, 763 dot3MpcpTxRegister Counter32, 764 dot3MpcpRxRegister Counter32 765 } 767 dot3MpcpMACCtrlFramesTransmitted OBJECT-TYPE 768 SYNTAX Counter32 769 UNITS "frames" 770 MAX-ACCESS read-only 771 STATUS current 772 DESCRIPTION 773 "A count of MPCP frames passed to the MAC sublayer for 774 transmission. This counter is incremented when a 775 MA_CONTROL.request service primitive is generated within 776 the MAC control sublayer with an opcode indicating a 777 MPCP frame. 778 This attribute is relevant for an OLT and an ONU." 779 REFERENCE "[802.3], 30.3.5.1.7." 780 ::= { dot3MpcpStatEntry 1 } 782 dot3MpcpMACCtrlFramesReceived OBJECT-TYPE 783 SYNTAX Counter32 784 UNITS "frames" 785 MAX-ACCESS read-only 786 STATUS current 787 DESCRIPTION 788 "A count of MPCP frames passed by the MAC sublayer to the 789 MAC Control sublayer. This counter is incremented when a 790 ReceiveFrame function call returns a valid frame with: 791 (1) a lengthOrType field value equal to the reserved 792 Type for 802.3_MAC_Control as specified in 31.4.1.3, and 793 (2) an opcode indicating a MPCP frame. 794 This attribute is relevant for an OLT and an ONU." 795 REFERENCE "[802.3], 30.3.5.1.8." 796 ::= { dot3MpcpStatEntry 2} 798 dot3MpcpDiscoveryWindowsSent OBJECT-TYPE 799 SYNTAX Counter32 800 MAX-ACCESS read-only 801 STATUS current 802 DESCRIPTION 803 "A count of discovery windows generated. The counter is 804 incremented by one for each generated discovery window. 805 This attribute is relevant for an OLT and an ONU. At the 806 ONU value should be zero." 807 REFERENCE "[802.3], 30.3.5.1.22." 808 ::= { dot3MpcpStatEntry 3} 810 dot3MpcpDiscoveryTimeout OBJECT-TYPE 811 SYNTAX Counter32 812 MAX-ACCESS read-only 813 STATUS current 814 DESCRIPTION 815 "A count of the number of times a discovery timeout 816 occurs. Increment the counter by one for each discovery 817 processing state-machine reset resulting from timeout 818 waiting for message arrival. 819 This attribute is relevant for an OLT and an ONU." 820 REFERENCE "[802.3], 30.3.5.1.23." 821 ::= { dot3MpcpStatEntry 4} 823 dot3MpcpTxRegRequest OBJECT-TYPE 824 SYNTAX Counter32 825 UNITS "frames" 826 MAX-ACCESS read-only 827 STATUS current 828 DESCRIPTION 829 "A count of the number of times a REGISTER_REQ MPCP 830 frames transmission occurs. Increment the counter by one 831 for each REGISTER_REQ MPCP frame transmitted as defined 832 in [802.3] clause 64. This counter is mandatory for an 833 ONU. This attribute is relevant for an OLT and an ONU. 834 At the OLT value should be zero." 835 REFERENCE "[802.3], 30.3.5.1.12." 836 ::= { dot3MpcpStatEntry 5} 838 dot3MpcpRxRegRequest OBJECT-TYPE 839 SYNTAX Counter32 840 UNITS "frames" 841 MAX-ACCESS read-only 842 STATUS current 843 DESCRIPTION 844 "A count of the number of times a REGISTER_REQ MPCP 845 frames reception occurs. A single counter at the ONU and 846 a set of counters, one for each LLID, at the OLT. 847 Increment the counter by one for each REGISTER_REQ MPCP 848 frame received for each LLID as defined in [802.3] 849 clause 64. This counter is mandatory for an ONU and for 850 an OLT. At the ONU value should be zero." 851 REFERENCE "[802.3], 30.3.5.1.17." 852 ::= { dot3MpcpStatEntry 6} 854 dot3MpcpTxRegAck OBJECT-TYPE 855 SYNTAX Counter32 856 UNITS "frames" 857 MAX-ACCESS read-only 858 STATUS current 859 DESCRIPTION 860 "A count of the number of times a REGISTER_ACK MPCP 861 frames transmission occurs. Increment the counter by one 862 for each REGISTER_ACK MPCP frame transmitted as defined 863 in [802.3] clause 64. This counter is mandatory for an 864 ONU. This attribute is relevant for an OLT and an ONU. 865 At the OLT the value should be zero." 866 REFERENCE "[802.3], 30.3.5.1.10." 867 ::= { dot3MpcpStatEntry 7} 869 dot3MpcpRxRegAck OBJECT-TYPE 870 SYNTAX Counter32 871 UNITS "frames" 872 MAX-ACCESS read-only 873 STATUS current 874 DESCRIPTION 875 "A count of the number of times a REGISTER_ACK MPCP 876 frames reception occurs. A single counter at the ONU and 877 a set of counters, one for each LLID, at the OLT. 878 Increment the counter by one for each REGISTER_ACK MPCP 879 frame received for each LLID, as defined in [802.3] 880 clause 64. This counter is mandatory for an ONU and for 881 an OLT. At the ONU the value should be zero." 882 REFERENCE "[802.3], 30.3.5.1.15." 883 ::= { dot3MpcpStatEntry 8} 885 dot3MpcpTxReport OBJECT-TYPE 886 SYNTAX Counter32 887 UNITS "frames" 888 MAX-ACCESS read-only 889 STATUS current 890 DESCRIPTION 891 "A count of the number of times a REPORT MPCP frames 892 transmission occurs. Increment the counter by one for 893 each REPORT MPCP frame transmitted as defined in 894 [802.3] clause 64. This counter is mandatory for an 895 ONU. This attribute is relevant for an OLT and an ONU. 896 At the OLT value should be zero." 898 REFERENCE "[802.3], 30.3.5.1.13." 899 ::= { dot3MpcpStatEntry 9} 901 dot3MpcpRxReport OBJECT-TYPE 902 SYNTAX Counter32 903 UNITS "frames" 904 MAX-ACCESS read-only 905 STATUS current 906 DESCRIPTION 907 "A count of the number of times a REPORT MPCP frames 908 reception occurs. A single counter at the ONU and a set 909 of counters, one for each LLID, at the OLT. Increment 910 the counter by one for each REPORT MPCP frame received 911 for each LLID, as defined in [802.3] clause 64. 912 This counter is mandatory for an ONU and for an OLT. 913 At the ONU value should be zero." 914 REFERENCE "[802.3], 30.3.5.1.18." 915 ::= { dot3MpcpStatEntry 10} 917 dot3MpcpTxGate OBJECT-TYPE 918 SYNTAX Counter32 919 UNITS "frames" 920 MAX-ACCESS read-only 921 STATUS current 922 DESCRIPTION 923 "A count of the number of times a GATE MPCP frames 924 transmission occurs. A set of counters, one for each 925 LLID, at the OLT. Increment the counter by one for each 926 GATE MPCP frame transmitted, for each LLID, as defined 927 in [802.3] clause 64. This counter is mandatory for an 928 OLT. This attribute is relevant for an OLT and an ONU. 929 At the ONU the value should be zero." 930 REFERENCE "[802.3], 30.3.5.1.9." 931 ::= { dot3MpcpStatEntry 11} 933 dot3MpcpRxGate OBJECT-TYPE 934 SYNTAX Counter32 935 UNITS "frames" 936 MAX-ACCESS read-only 937 STATUS current 938 DESCRIPTION 939 "A count of the number of times a GATE MPCP frames 940 reception occurs. A single counter at the ONU and a set 941 of counters, one for each LLID ,at the OLT. Increment 942 the counter by one for each GATE MPCP frame received, 943 for each LLID, as defined in [802.3] clause 64. This 944 counter is mandatory for an ONU and for an OLT. At the 945 OLT the value should be zero." 947 REFERENCE "[802.3], 30.3.5.1.14." 948 ::= { dot3MpcpStatEntry 12} 950 dot3MpcpTxRegister OBJECT-TYPE 951 SYNTAX Counter32 952 UNITS "frames" 953 MAX-ACCESS read-only 954 STATUS current 955 DESCRIPTION 956 "A count of the number of times a REGISTER MPCP frames 957 transmission occurs. A set of counters, one for each 958 LLID, at the OLT. Increment the counter by one for each 959 REGISTER MPCP frame transmitted, for each LLID, as 960 defined in [802.3] clause 64. This counter is 961 mandatory for an OLT. This attribute is relevant for an 962 OLT and an ONU. At the ONU the value should be zero." 963 REFERENCE "[802.3], 30.3.5.1.11." 964 ::= { dot3MpcpStatEntry 13} 966 dot3MpcpRxRegister OBJECT-TYPE 967 SYNTAX Counter32 968 UNITS "frames" 969 MAX-ACCESS read-only 970 STATUS current 971 DESCRIPTION 972 "A count of the number of times a REGISTER MPCP frames 973 reception occurs. A single counter at the ONU and a set 974 of counters, one for each LLID, at the OLT. Increment 975 the counter by one for each REGISTER MPCP frame 976 received, for each LLID, as defined in [802.3] clause 977 64. This counter is mandatory for an ONU and for an OLT. 978 at the OLT the value should be zero." 979 REFERENCE "[802.3], 30.3.5.1.16." 980 ::= { dot3MpcpStatEntry 14} 982 -- Conformance Statements 984 -- Conformance Groups 986 dot3MpcpGroups OBJECT IDENTIFIER ::= { dot3MpcpConformance 1 } 988 dot3MpcpGroupBase OBJECT-GROUP 989 OBJECTS { 990 dot3MpcpID, 991 dot3MpcpOperStatus, 992 dot3MpcpMode, 993 dot3MpcpLinkID, 994 dot3MpcpRemoteMACAddress, 995 dot3MpcpRegistrationState, 996 dot3MpcpMaximumPendingGrants, 997 dot3MpcpAdminState 998 } 999 STATUS current 1000 DESCRIPTION 1001 "A collection of objects of dot3 Mpcp Basic entity state 1002 definition." 1003 ::= { dot3MpcpGroups 1 } 1005 dot3MpcpGroupParam OBJECT-GROUP 1006 OBJECTS { 1007 dot3MpcpTransmitElapsed, 1008 dot3MpcpReceiveElapsed, 1009 dot3MpcpRoundTripTime, 1010 dot3MpcpOnTime, 1011 dot3MpcpOffTime, 1012 dot3MpcpSyncTime 1013 } 1014 STATUS current 1015 DESCRIPTION 1016 "A collection of objects of dot3 Mpcp for P2MP 1017 parameters." 1018 ::= { dot3MpcpGroups 2 } 1020 dot3MpcpGroupStat OBJECT-GROUP 1021 OBJECTS { 1022 dot3MpcpMACCtrlFramesTransmitted, 1023 dot3MpcpMACCtrlFramesReceived, 1024 dot3MpcpDiscoveryWindowsSent, 1025 dot3MpcpDiscoveryTimeout , 1026 dot3MpcpTxRegRequest, 1027 dot3MpcpRxRegRequest, 1028 dot3MpcpTxRegAck, 1029 dot3MpcpRxRegAck, 1030 dot3MpcpTxReport, 1031 dot3MpcpRxReport, 1032 dot3MpcpTxGate, 1033 dot3MpcpRxGate, 1034 dot3MpcpTxRegister, 1035 dot3MpcpRxRegister 1036 } 1037 STATUS current 1038 DESCRIPTION 1039 "A collection of objects of dot3 Mpcp Statistics" 1041 ::= { dot3MpcpGroups 3 } 1043 -- Compliance 1045 dot3MpcpCompliances OBJECT IDENTIFIER ::= { dot3MpcpConformance 2 } 1047 dot3MPCPCompliance MODULE-COMPLIANCE 1048 STATUS current 1049 DESCRIPTION "The compliance statement for Multi-point 1050 control protocol interfaces." 1052 MODULE -- this module 1053 MANDATORY-GROUPS { dot3MpcpGroupBase} 1055 GROUP dot3MpcpGroupParam 1056 DESCRIPTION "This group is mandatory for all MPCP supporting 1057 interfaces for configuration of the Multipoint 1058 Parameters." 1059 GROUP dot3MpcpGroupStat 1060 DESCRIPTION "This group is mandatory for all MPCP supporting 1061 interfaces for Statistics collection." 1062 ::= { dot3MpcpCompliances 1} 1064 -- Editor-s note: OMPEmulation managed object definitions 1066 dot3OmpEmulationMIB OBJECT IDENTIFIER ::= { dot3EfmeponMIB 2} 1068 dot3OmpEmulationObjects OBJECT IDENTIFIER ::={dot3OmpEmulationMIB 1} 1070 dot3OmpeConformance OBJECT IDENTIFIER ::= { dot3OmpEmulationMIB 2 } 1072 dot3OmpEmulationTable OBJECT-TYPE 1073 SYNTAX SEQUENCE OF Dot3OmpEmulationEntry 1074 MAX-ACCESS not-accessible 1075 STATUS current 1076 DESCRIPTION 1077 "Table for dot3 OmpEmulation MIB modules." 1078 ::= { dot3OmpEmulationObjects 1 } 1080 dot3OmpEmulationEntry OBJECT-TYPE 1081 SYNTAX Dot3OmpEmulationEntry 1082 MAX-ACCESS not-accessible 1083 STATUS current 1084 DESCRIPTION 1085 "An entry in the dot3 OmpEmulation MIB modules table." 1086 INDEX { ifIndex } 1087 ::= { dot3OmpEmulationTable 1 } 1089 Dot3OmpEmulationEntry ::= 1090 SEQUENCE { 1091 dot3OmpEmulationID Integer32, 1092 dot3OmpEmulationType INTEGER 1093 } 1095 dot3OmpEmulationID OBJECT-TYPE 1096 SYNTAX Integer32 1097 MAX-ACCESS read-only 1098 STATUS current 1099 DESCRIPTION 1100 "The value of dot3OmpEmulationID is assigned so as to 1101 uniquely identify a OMPEmulation entity among the 1102 subordinate managed objects of the containing object. 1103 The value is mandated for an ONU." 1104 REFERENCE "[802.3], 30.3.7.1.1." 1105 ::= { dot3OmpEmulationEntry 1} 1107 dot3OmpEmulationType OBJECT-TYPE 1108 SYNTAX INTEGER { 1109 unknown(1), 1110 olt(2), 1111 onu(3) 1112 } 1113 MAX-ACCESS read-only 1114 STATUS current 1115 DESCRIPTION 1116 "A read-only value that indicates that mode of operation 1117 of the Reconciliation Sublayer for Point to Point 1118 Emulation (see [802.3] clause 65.1). unknown(1) value 1119 is assigned in initializing, true state or type not yet 1120 known. olt(2) value is assigned when Sublayer operating 1121 in OLT mode. onu(3) value is assigned when Sublayer 1122 operating in ONU mode." 1123 REFERENCE "[802.3], 30.3.7.1.2." 1124 ::= { dot3OmpEmulationEntry 2} 1126 dot3OmpEmulationStatTable OBJECT-TYPE 1127 SYNTAX SEQUENCE OF Dot3OmpEmulationStatEntry 1128 MAX-ACCESS not-accessible 1129 STATUS current 1130 DESCRIPTION 1131 "This table defines the list of statistics counters of 1132 [802.3] clause 65 OMP interface." 1133 ::= { dot3OmpEmulationObjects 2} 1135 dot3OmpEmulationStatEntry OBJECT-TYPE 1136 SYNTAX Dot3OmpEmulationStatEntry 1137 MAX-ACCESS not-accessible 1138 STATUS current 1139 DESCRIPTION 1140 "Table entries for Table of statistics counters of 1141 [802.3] clause 65 OMP interface." 1142 INDEX { ifIndex } 1143 ::= { dot3OmpEmulationStatTable 1 } 1145 Dot3OmpEmulationStatEntry::= 1146 SEQUENCE { 1147 dot3OmpEmulationSLDErrors Counter32, 1148 dot3OmpEmulationCRC8Errors Counter32, 1149 dot3OmpEmulationBadLLID Counter32, 1150 dot3OmpEmulationGoodLLID Counter32, 1151 dot3OmpEmulationOnuPonCastLLID Counter32, 1152 dot3OmpEmulationOltPonCastLLID Counter32, 1153 dot3OmpEmulationBroadcastBitNotOnuLlid Counter32, 1154 dot3OmpEmulationOnuLLIDNotBroadcast Counter32, 1155 dot3OmpEmulationBroadcastBitPlusOnuLlid Counter32, 1156 dot3OmpEmulationNotBroadcastBitNotOnuLlid Counter32 1157 } 1159 dot3OmpEmulationSLDErrors OBJECT-TYPE 1160 SYNTAX Counter32 1161 UNITS "frames" 1162 MAX-ACCESS read-only 1163 STATUS current 1164 DESCRIPTION 1165 "A count of frames received that do not contain a valid 1166 SLD field as defined in [802.3] clause 65.1.3.3.1. 1167 This attribute is mandatory for an OLT and for an ONU." 1168 REFERENCE "[802.3], 30.3.7.1.3." 1169 ::= { dot3OmpEmulationStatEntry 1} 1171 dot3OmpEmulationCRC8Errors OBJECT-TYPE 1172 SYNTAX Counter32 1173 UNITS "frames" 1174 MAX-ACCESS read-only 1175 STATUS current 1176 DESCRIPTION 1177 "A count of frames received that contain a valid SLD 1178 field, as defined in [802.3] clause 65.1.3.3.1, but do 1179 not pass the CRC-8 check as defined in [802.3] clause 1180 65.1.3.3.3. This attribute is mandatory for an OLT and 1181 for an ONU." 1182 REFERENCE "[802.3], 30.3.7.1.4." 1183 ::= { dot3OmpEmulationStatEntry 2} 1185 dot3OmpEmulationBadLLID OBJECT-TYPE 1186 SYNTAX Counter32 1187 UNITS "frames" 1188 MAX-ACCESS read-only 1189 STATUS current 1190 DESCRIPTION 1191 "A count of frames received that contain a valid SLD 1192 field, as defined in [802.3] clause 65.1.3.3.1, and 1193 pass the CRC-8 check, as defined in [802.3] clause 1194 65.1.3.3.3, but are discarded due to the LLID check as 1195 defined in [802.3] clause 65.1.3.3.2. 1196 This attribute is relevant for an OLT and an ONU." 1197 REFERENCE "[802.3], 30.3.7.1.8." 1198 ::= { dot3OmpEmulationStatEntry 3} 1200 dot3OmpEmulationGoodLLID OBJECT-TYPE 1201 SYNTAX Counter32 1202 UNITS "frames" 1203 MAX-ACCESS read-only 1204 STATUS current 1205 DESCRIPTION 1206 "A count of frames received that contain a valid SLD 1207 field, as defined in [802.3] clause 65.1.3.3.1, and 1208 pass the CRC-8 check, as defined in [802.3] clause 1209 65.1.3.3.3. 1210 This attribute is relevant for an OLT and an ONU." 1211 REFERENCE "[802.3], 30.3.7.1.5." 1212 ::= { dot3OmpEmulationStatEntry 4} 1214 dot3OmpEmulationOnuPonCastLLID OBJECT-TYPE 1215 SYNTAX Counter32 1216 UNITS "frames" 1217 MAX-ACCESS read-only 1218 STATUS current 1219 DESCRIPTION 1220 "A count of frames received that contain a valid SLD 1221 field in an ONU, as defined in [802.3] 65.1.3.3.1, 1222 passes the CRC-8 check, as defined in [802.3] 1223 65.1.3.3.3, and the frame meets the rule for acceptance 1224 defined in [802.3] 65.1.3.3.2." 1226 REFERENCE "[802.3], 30.3.7.1.6." 1227 ::= { dot3OmpEmulationStatEntry 5} 1229 dot3OmpEmulationOltPonCastLLID OBJECT-TYPE 1230 SYNTAX Counter32 1231 UNITS "frames" 1232 MAX-ACCESS read-only 1233 STATUS current 1234 DESCRIPTION 1235 "A count of frames received that contain a valid SLD 1236 field in an OLT, as defined in [802.3] 65.1.3.3.1, 1237 passes the CRC-8 check, as defined in [802.3] 1238 65.1.3.3.3, and the frame meets the rule for acceptance 1239 defined in [802.3] 65.1.3.3.2." 1240 REFERENCE "[802.3], 30.3.7.1.7." 1241 ::= { dot3OmpEmulationStatEntry 6} 1243 dot3OmpEmulationBroadcastBitNotOnuLlid OBJECT-TYPE 1244 SYNTAX Counter32 1245 UNITS "frames" 1246 MAX-ACCESS read-only 1247 STATUS current 1248 DESCRIPTION 1249 "A count of frames received that contain a valid SLD 1250 field in a OLT, as defined in [802.3] clause 1251 65.1.3.3.1, and pass the CRC-8 check, as defined in 1252 [802.3] clause 65.1.3.3.3, and contain broadcast bit 1253 in LLID and not the ONU's LLID (frame accepted) as 1254 defined in [802.3] clause 65 . 1255 This attribute is mandatory for an OLT and for an ONU." 1256 ::= { dot3OmpEmulationStatEntry 7} 1258 dot3OmpEmulationOnuLLIDNotBroadcast OBJECT-TYPE 1259 SYNTAX Counter32 1260 UNITS "frames" 1261 MAX-ACCESS read-only 1262 STATUS current 1263 DESCRIPTION 1264 "A count of frames received that contain a valid SLD 1265 field in a OLT, as defined in [802.3] clause 1266 65.1.3.3.1, and pass the CRC-8 check, as defined in 1267 [802.3] clause 65.1.3.3.3, and contain the ONU's LLID 1268 as defined in [802.3] clause 65. This attribute is 1269 mandatory for an ONU and mandatory for an OLT (a 1270 counter per LLID)." 1271 ::= { dot3OmpEmulationStatEntry 8} 1273 dot3OmpEmulationBroadcastBitPlusOnuLlid OBJECT-TYPE 1274 SYNTAX Counter32 1275 UNITS "frames" 1276 MAX-ACCESS read-only 1277 STATUS current 1278 DESCRIPTION 1279 "A count of frames received that contain a valid SLD 1280 field in a OLT, as defined in [802.3] clause 1281 65.1.3.3.1, and pass the CRC-8 check, as defined in 1282 [802.3] clause 65.1.3.3.3, and contain the broadcast 1283 bit in LLID and the ONU's LLID (frame reflected) as 1284 defined in [802.3] clause 65. This attribute is 1285 mandatory for an ONU and mandatory for an OLT (a 1286 counter per LLID)." 1287 ::= { dot3OmpEmulationStatEntry 9} 1289 dot3OmpEmulationNotBroadcastBitNotOnuLlid OBJECT-TYPE 1290 SYNTAX Counter32 1291 UNITS "frames" 1292 MAX-ACCESS read-only 1293 STATUS current 1294 DESCRIPTION 1295 "A count of frames received that contain a valid SLD 1296 field in a OLT, as defined in [802.3] clause 1297 65.1.3.3.1, and pass the CRC-8 check, as defined in 1298 [802.3] clause 65.1.3.3.3, and and does not contain 1299 the ONU's LLID as defined in [802.3] clause 65. 1300 This attribute is mandatory for an ONU" 1301 ::= { dot3OmpEmulationStatEntry 10} 1303 -- Conformance Statements 1305 -- Conformance Groups 1307 dot3OmpeGroups OBJECT IDENTIFIER ::={ dot3OmpeConformance 1} 1309 dot3OmpeGroupID OBJECT-GROUP 1310 OBJECTS { 1311 dot3OmpEmulationID, 1312 dot3OmpEmulationType 1314 } 1315 STATUS current 1316 DESCRIPTION 1317 "A collection of objects of dot3 OMP emulation ID entity 1318 state definition." 1320 ::= { dot3OmpeGroups 1 } 1322 dot3OmpeGroupStat OBJECT-GROUP 1323 OBJECTS { 1324 dot3OmpEmulationSLDErrors, 1325 dot3OmpEmulationCRC8Errors, 1326 dot3OmpEmulationBadLLID, 1327 dot3OmpEmulationGoodLLID, 1328 dot3OmpEmulationOnuPonCastLLID, 1329 dot3OmpEmulationOltPonCastLLID, 1330 dot3OmpEmulationBroadcastBitNotOnuLlid, 1331 dot3OmpEmulationOnuLLIDNotBroadcast, 1332 dot3OmpEmulationBroadcastBitPlusOnuLlid, 1333 dot3OmpEmulationNotBroadcastBitNotOnuLlid 1334 } 1335 STATUS current 1336 DESCRIPTION 1337 "A collection of objects of dot3 OMP emulation 1338 Statistics" 1339 ::= { dot3OmpeGroups 2 } 1341 -- Compliance 1343 dot3OmpeCompliances OBJECT IDENTIFIER ::= { dot3OmpeConformance 2 } 1345 dot3OmpeCompliance MODULE-COMPLIANCE 1346 STATUS current 1347 DESCRIPTION "The compliance statement for OMPEmulation 1348 interfaces." 1350 MODULE -- this module 1351 MANDATORY-GROUPS { dot3OmpeGroupID} 1353 GROUP dot3OmpeGroupStat 1354 DESCRIPTION "This group is mandatory for all OMPemulation 1355 supporting interfaces for Statistics collection." 1357 ::= { dot3OmpeCompliances 1} 1359 -- Editor-s note: MAU managed object definitions (30.5.1) 1361 dot3EponMauMIB OBJECT IDENTIFIER ::= { dot3EfmeponMIB 3} 1362 dot3EponMauObjects OBJECT IDENTIFIER ::= { dot3EponMauMIB 1} 1364 dot3EponMauConformance OBJECT IDENTIFIER ::= { dot3EponMauMIB 2 } 1366 dot3EponMauTable OBJECT-TYPE 1367 SYNTAX SEQUENCE OF Dot3EponMauEntry 1368 MAX-ACCESS not-accessible 1369 STATUS current 1370 DESCRIPTION 1371 "Table for dot3 MAU EPON MIB modules." 1372 ::= { dot3EponMauObjects 1 } 1374 dot3EponMauEntry OBJECT-TYPE 1375 SYNTAX Dot3EponMauEntry 1376 MAX-ACCESS not-accessible 1377 STATUS current 1378 DESCRIPTION 1379 "An entry in the dot3 MAU EPON MIB modules table." 1380 INDEX { ifIndex } 1381 ::= { dot3EponMauTable 1 } 1383 Dot3EponMauEntry ::= 1384 SEQUENCE { 1385 dot3EponMauPCSCodingViolation Counter32, 1386 dot3EponMauFecAbility INTEGER, 1387 dot3EponMauFecMode INTEGER, 1388 dot3EponMauFECCorrectedBlocks Counter32, 1389 dot3EponMauFECUncorrectableBlocks Counter32, 1390 dot3EponMauBufferHeadCodingViolation Counter32 1391 } 1393 dot3EponMauPCSCodingViolation OBJECT-TYPE 1394 SYNTAX Counter32 1395 UNITS "octets" 1396 MAX-ACCESS read-only 1397 STATUS current 1398 DESCRIPTION 1399 "For 100 Mb/ s operation it is a count of the number of 1400 times an invalid code-group is received, other than the 1401 /H/ code-group. For 1000 Mb/ s operation it is a count 1402 of the number of times an invalid codegroup is received, 1403 other than the /V/ code-group." 1404 REFERENCE "[802.3], 30.5.1.1.12." 1405 ::= { dot3EponMauEntry 1} 1407 dot3EponMauFecAbility OBJECT-TYPE 1408 SYNTAX INTEGER { 1409 unknown (1), 1410 nonsupported (2), 1411 supported (3) 1412 } 1413 MAX-ACCESS read-only 1414 STATUS current 1415 DESCRIPTION 1416 "A read-only value that indicates the support of 1417 operation of the 1000BASE-PX PHY optional FEC Sublayer 1418 for Forward error correction see [802.3] clause 65.2). 1419 unknown(1) value is assigned in initializing, for non 1420 FEC support state or type not yet known. nonsupported(2) 1421 value is assigned when Sublayer is not support. 1422 supported(3) value is assigned when Sublayer is 1423 supported." 1424 REFERENCE "[802.3], 30.5.1.1.13." 1425 ::= { dot3EponMauEntry 2} 1427 dot3EponMauFecMode OBJECT-TYPE 1428 SYNTAX INTEGER { 1429 unknown (1), 1430 disabled (2), 1431 enabled (3) 1432 } 1433 MAX-ACCESS read-write 1434 STATUS current 1435 DESCRIPTION 1436 "A read-write value that indicates the mode of operation 1437 of the 1000BASE-PX PHY optional FEC Sublayer for Forward 1438 error correction see [802.3] clause 65.2). 1439 A GET operation returns the current mode of operation 1440 the PHY. A SET operation changes the mode of operation 1441 of the PHY to the indicated value. unknown(1) value is 1442 assigned in initializing, for non FEC support state or 1443 type not yet known. disabled(2) value is assigned when 1444 Sublayer operating in disabled mode. enabled(3) value is 1445 assigned when Sublayer operating in FEC mode. writing 1446 can be done all the time." 1447 REFERENCE "[802.3], 30.5.1.1.14." 1448 DEFVAL { 1 } 1449 ::= { dot3EponMauEntry 3} 1451 dot3EponMauFECCorrectedBlocks OBJECT-TYPE 1452 SYNTAX Counter32 1453 MAX-ACCESS read-only 1454 STATUS current 1455 DESCRIPTION 1456 "For 10PASS-TS, 2BASE-TL and 1000BASE-PX PHYs, a count 1457 of corrected FEC blocks. This counter will not increment 1458 for other PHY Types. Increment the counter by one for 1459 each received block that is corrected by the FEC 1460 function in the PHY." 1461 REFERENCE "[802.3], 30.5.1.1.15." 1462 ::= { dot3EponMauEntry 4} 1464 dot3EponMauFECUncorrectableBlocks OBJECT-TYPE 1465 SYNTAX Counter32 1466 MAX-ACCESS read-only 1467 STATUS current 1468 DESCRIPTION 1469 "For 10PASS-TS, 2BASE-TL and 1000BASE-PX PHYs, a count of 1470 uncorrectable FEC blocks. This counter will not 1471 increment for other PHY Types. Increment the counter by 1472 one for each FEC block that is determined to be 1473 uncorrectable by the FEC function in the PHY." 1474 REFERENCE "[802.3], 30.5.1.1.16." 1475 ::= { dot3EponMauEntry 5} 1477 dot3EponMauBufferHeadCodingViolation OBJECT-TYPE 1478 SYNTAX Counter32 1479 UNITS "octets" 1480 MAX-ACCESS read-only 1481 STATUS current 1482 DESCRIPTION 1483 "For 1000 Mbps operation it is a counts of the number of 1484 invalid code-group received directly from the link." 1485 ::= { dot3EponMauEntry 6} 1487 -- Conformance Statements 1489 -- Conformance Groups 1491 dot3EponMauGroups OBJECT IDENTIFIER ::={ dot3EponMauConformance 1} 1493 dot3EponMauGroupAll OBJECT-GROUP 1494 OBJECTS { 1495 dot3EponMauPCSCodingViolation 1496 } 1497 STATUS current 1498 DESCRIPTION 1499 "A collection of objects of dot3 MAU definition." 1500 ::= { dot3EponMauGroups 1 } 1502 dot3EponMauGroupFEC OBJECT-GROUP 1503 OBJECTS { 1504 dot3EponMauFecAbility, 1505 dot3EponMauFecMode, 1506 dot3EponMauFECCorrectedBlocks, 1507 dot3EponMauFECUncorrectableBlocks, 1508 dot3EponMauBufferHeadCodingViolation 1509 } 1510 STATUS current 1511 DESCRIPTION 1512 "A collection of objects of FEC group definition." 1513 ::= { dot3EponMauGroups 2 } 1515 -- Compliance 1517 dot3EponMauCompliances OBJECT IDENTIFIER::={dot3EponMauConformance 2} 1519 dot3EponMauCompliance MODULE-COMPLIANCE 1520 STATUS current 1521 DESCRIPTION "The compliance statement for MAU EPON interfaces." 1523 MODULE -- this module 1524 MANDATORY-GROUPS { dot3EponMauGroupAll } 1526 GROUP dot3EponMauGroupFEC 1527 DESCRIPTION "This group is mandatory for all EPON MAU devices 1528 Supporting FEC functionality as for Definitions and 1529 BER Statistics collection." 1531 ::= { dot3EponMauCompliances 1} 1533 END 1535 9. Definitions - The EPON Device MIB 1537 EPON-DEVICE-MIB DEFINITIONS ::= BEGIN 1539 IMPORTS 1540 MODULE-IDENTITY, mib-2, OBJECT-TYPE, Counter32, 1541 Unsigned32, Integer32, zeroDotZero 1542 FROM SNMPv2-SMI 1543 TruthValue, RowStatus, MacAddress 1544 FROM SNMPv2-TC 1545 ifIndex 1546 FROM IF-MIB 1547 MODULE-COMPLIANCE, OBJECT-GROUP 1548 FROM SNMPv2-CONF 1549 SnmpAdminString 1550 FROM SNMP-FRAMEWORK-MIB 1551 ; 1553 eponDeviceMIB MODULE-IDENTITY 1554 LAST-UPDATED "200503100000Z" -- March 10, 2005 1555 ORGANIZATION "IETF Ethernet Interfaces and Hub MIB Working 1556 Group" 1557 CONTACT-INFO 1558 "WG charter: 1559 http://www.ietf.org/html.charters/hubmib-charter.html 1560 Mailing Lists: 1561 General Discussion: hubmib@ietf.org 1562 To Subscribe: hubmib-request@ietf.org 1563 In Body: subscribe your_email_address 1564 Chair: Dan Romascanu 1565 Postal: Avaya 1566 Atidim Technology Park, Bldg. 3 1567 Tel Aviv 61131 1568 Israel 1569 Tel: +972-3-645-8414 1570 E-mail: dromasca@avaya.com 1572 Editor: Lior Khermosh 1573 Postal: Passave Technologies Inc. 1574 Kohav Hertzelia bldg, 1575 4 Hasadnaot St. 1576 Hertzliya Pituach 46120, 1577 ISRAEL 1579 P.O.Box 2089 Hertzliya Pituach 46120 Israel 1580 Tel: +972-9-9628000 Ext: 302 1581 E-mail: lior.khermosh@passave.com" 1582 DESCRIPTION 1583 "The objects in this MIB module are used to manage 1584 Ethernet Passive Optical Network (EPON) devices which 1585 are based on the Ethernet in the First Mile (EFM) PON 1586 as defined in IEEE P802.3 clause 64,65. 1588 The following reference is used throughout this MIB 1589 module: 1590 [802.3] refers to: 1591 IEEE Draft P802.3: 'Information technology - 1592 Telecommunications and information exchange between 1593 systems - Local and metropolitan area networks - 1594 Specific requirements - 1595 Part 3: Carrier sense multiple access with collision 1596 detection (CSMA/CD) access method and physical layer 1597 specifications - Media Access Control Parameters, 1598 Physical Layers and Management Parameters for 1599 subscriber access networks', 8 December 2004. 1600 Of particular interest are Clause 64(MPCP) 65(P2mP RS) 1601 and 60 (PON PMDs). Clause 30, 'Management', and Clause 1602 45,'Management Data Input/Output (MDIO) Interface'. 1604 Copyright (C) The Internet Society (2005). This version 1605 of this MIB module is part of XXXX see the RFC itself 1606 for full legal notices." 1608 -- Editor's Note: Replace XXXX with the actual RFC number 1609 -- assigned by RFC Editor and remove this note 1611 REVISION "200503100000Z" -- March 10, 2005 1612 DESCRIPTION "Initial version, published as RFC XXXX." 1614 ::= { mib-2 XXX } 1616 -- Editor's Note: Replace XXX with a real OID once it is 1617 -- assigned by IANA and remove this note. 1619 eponDeviceObjectMIB OBJECT IDENTIFIER ::= { eponDeviceMIB 1} 1621 eponDeviceObjects OBJECT IDENTIFIER ::= { eponDeviceObjectMIB 1} 1623 eponDeviceConformance OBJECT IDENTIFIER ::= { eponDeviceObjectMIB 2} 1625 eponDeviceControlObjects OBJECT IDENTIFIER ::= { eponDeviceObjects 1} 1626 eponDeviceStatObjects OBJECT IDENTIFIER ::= { eponDeviceObjects 2} 1628 eponDeviceEventObjects OBJECT IDENTIFIER ::= { eponDeviceObjects 3} 1630 eponDeviceControlTable OBJECT-TYPE 1631 SYNTAX SEQUENCE OF EponDeviceControlEntry 1632 MAX-ACCESS not-accessible 1633 STATUS current 1634 DESCRIPTION 1635 "Table for EPON device MIB modules." 1636 ::= { eponDeviceControlObjects 1 } 1638 eponDeviceControlEntry OBJECT-TYPE 1639 SYNTAX EponDeviceControlEntry 1640 MAX-ACCESS not-accessible 1641 STATUS current 1642 DESCRIPTION 1643 "An entry in the EPON device Control table." 1644 INDEX { ifIndex } 1645 ::= { eponDeviceControlTable 1 } 1647 EponDeviceControlEntry ::= 1648 SEQUENCE { 1649 eponDeviceObjectReset INTEGER, 1650 eponDeviceObjectModes INTEGER, 1651 eponDeviceObjectFecEnabled INTEGER, 1652 eponDeviceObjectDeviceReadyMode INTEGER, 1653 eponDeviceObjectPowerDown TruthValue, 1654 eponDeviceObjectNumberOfLLIDs Integer32, 1655 eponDeviceObjectReportNumThreshold Integer32, 1656 eponDeviceObjectReportThreshold Integer32, 1657 eponDeviceObjectReportMaximumNumThreshold Integer32, 1658 eponDeviceObjectReportMaximumNumQueues Integer32, 1659 eponDeviceRemoteMACAddressLLIDControl INTEGER 1660 } 1662 eponDeviceObjectReset OBJECT-TYPE 1663 SYNTAX INTEGER { 1664 running(1), 1665 reset(2) 1666 } 1667 MAX-ACCESS read-write 1668 STATUS current 1669 DESCRIPTION 1670 "This variable is used to reset the EPON device. The 1671 interface may be unavailable while the reset occurs and 1672 data may be lost. During reading operation it returns 1673 the state of the EPON device. running(1) indicates and 1674 operates normal operation, reset(2) indicates and 1675 operates reset mode. Writing can be done all the time." 1676 DEFVAL { 1 } 1677 ::= { eponDeviceControlEntry 1 } 1679 eponDeviceObjectModes OBJECT-TYPE 1680 SYNTAX INTEGER { 1681 olt(1), 1682 onu(2) 1683 } 1684 MAX-ACCESS read-only 1685 STATUS current 1686 DESCRIPTION 1687 "This variable defines the mode of the EPON device. When 1688 an olt(1) it is an Optical Line Terminal device (server) 1689 and when an onu(2) and Optical Network Unit device 1690 (client)" 1691 ::= { eponDeviceControlEntry 2 } 1693 eponDeviceObjectFecEnabled OBJECT-TYPE 1694 SYNTAX INTEGER { 1695 noFecEnabled (1), 1696 fecTxEnabled (2), 1697 fecRxEnabled (3), 1698 fecTxRxEnabled (4) 1699 } 1700 MAX-ACCESS read-write 1701 STATUS current 1702 DESCRIPTION 1703 "This variable defines and provides information whether the 1704 EPON device uses FEC as defined in the [802.3] clause 1705 65.2 for EPON. When noFECEnabled(1) the device does not 1706 support FEC mode. When fecTxEnabled(2) the device supports 1707 the FEC transmission mode. When fecRxEnabled(3) the device 1708 supports the FEC Receive mode. When fecTxRxEnabled(4) the 1709 device supports the FEC transmission and receive mode. 1710 Writing can be done all the time. 1711 This attribute is relevant for an OLT and an ONU." 1712 DEFVAL { 1 } 1713 ::= { eponDeviceControlEntry 3 } 1715 eponDeviceObjectDeviceReadyMode OBJECT-TYPE 1716 SYNTAX INTEGER { 1717 notReady (1), 1718 inProcess (2), 1719 ready (3) 1720 } 1721 MAX-ACCESS read-write 1722 STATUS current 1723 DESCRIPTION 1724 "This variable defines the mode of an EPON device and 1725 provides information on the mode in initialization - 1726 ready for registration as defined by the [802.3] 1727 clause 64. 1728 When notReady(1) the device is not ready for operation. 1729 When inProcess(2) the device is in initialization 1730 process. 1731 When ready(3) the device is ready for registration. 1732 Writing can be done all the time. 1733 This attribute is relevant for an OLT and an ONU." 1734 DEFVAL { 1 } 1735 ::= { eponDeviceControlEntry 4 } 1737 eponDeviceObjectPowerDown OBJECT-TYPE 1738 SYNTAX TruthValue 1739 MAX-ACCESS read-write 1740 STATUS current 1741 DESCRIPTION 1742 "Setting this variable to True(1) will cause Device to be 1743 entered into Power down mode. Setting this variable to 1744 False(0) will cause the device to go out of power down 1745 mode. When getting True(1) the device is in power down. 1746 when getting False(0) the device is not in power down. 1747 Writing can be done all the time. 1748 This attribute is relevant for an OLT and an ONU." 1749 DEFVAL { false } 1750 ::= { eponDeviceControlEntry 5 } 1752 eponDeviceObjectNumberOfLLIDs OBJECT-TYPE 1753 SYNTAX Integer32 1754 MAX-ACCESS read-only 1755 STATUS current 1756 DESCRIPTION 1757 "A read only variable which defines the number of 1758 registered LLIDs (as defined by the [802.3] clause 65) 1759 in a EPON network for an OLT and an ONU. Initialization 1760 value is 0. 1761 This attribute is relevant for an OLT and an ONU." 1762 ::= { eponDeviceControlEntry 6 } 1764 eponDeviceObjectReportNumThreshold OBJECT-TYPE 1765 SYNTAX Integer32 1766 MAX-ACCESS read-write 1767 STATUS current 1768 DESCRIPTION 1769 "A set of 8 integers, for each LLID, that defines the 1770 number of thresholds for each Queue in the REPORT 1771 message, as defined in [802.3] 64. Each Queue set 1772 reporting will provide information on the queue 1773 occupancy of frames below the matching Threshold. 1774 Writing can be done all the time. 1775 This attribute is relevant for an OLT and an ONU." 1776 DEFVAL { 0 } 1777 ::= { eponDeviceControlEntry 7 } 1779 eponDeviceObjectReportThreshold OBJECT-TYPE 1780 SYNTAX Integer32 1781 UNITS "TQ (16nsec)" 1782 MAX-ACCESS read-write 1783 STATUS current 1784 DESCRIPTION 1785 "A multiple set of 8 integers, for each LLID, that 1786 defines the thresholds reporting for each Queue in the 1787 REPORT message, as defined in [802.3] 64. The number 1788 of sets is eponDeviceObjectReportNumThreshold. Each 1789 Queue set reporting will provide information on the 1790 queue occupancy of frames below the matching Threshold. 1791 The value returned shall be in Time quanta (TQ) which 1792 is 16nsec or 2 octets increments. 1793 Writing can be done all the time. 1794 This attribute is relevant for an OLT and an ONU." 1795 DEFVAL { 0 } 1796 ::= { eponDeviceControlEntry 8 } 1798 eponDeviceObjectReportMaximumNumThreshold OBJECT-TYPE 1799 SYNTAX Integer32 1800 MAX-ACCESS read-only 1801 STATUS current 1802 DESCRIPTION 1803 "A set of 8 integers, for each LLID, that defines the 1804 maximal number of thresholds for each Queue in the 1805 REPORT message, as defined in [802.3] 64. Each Queue 1806 set reporting will provide information on the queue 1807 occupancy of frames below the matching Threshold. 1808 This attribute is relevant for an ONU and an OLT." 1809 DEFVAL { 0 } 1810 ::= { eponDeviceControlEntry 9 } 1812 eponDeviceObjectReportMaximumNumQueues OBJECT-TYPE 1813 SYNTAX Integer32 1814 MAX-ACCESS read-only 1815 STATUS current 1816 DESCRIPTION 1817 "A set of 8 integers, for each LLID, that defines the 1818 maximal number of queues in the REPORT message, as 1819 defined in [802.3] 64. 1820 This attribute is relevant for an ONU and an OLT." 1821 DEFVAL { 0 } 1822 ::= { eponDeviceControlEntry 10 } 1824 eponDeviceRemoteMACAddressLLIDControl OBJECT-TYPE 1825 SYNTAX INTEGER { 1826 none(1), 1827 resetLog(2), 1828 useDefaultReporting(3) 1829 } 1830 MAX-ACCESS read-write 1831 STATUS current 1832 DESCRIPTION 1833 "Indicates and controls the resetting of the LLID MAC 1834 address log. Setting this object to none(1) has no 1835 action resetLog(2) empties the LLID MAC address log. All 1836 data is deleted. Setting it to useDefaultReporting(3) 1837 returns all entries priorities to their factory-default 1838 reporting. Reading this object always returns 1839 useDefaultReporting(3)." 1840 DEFVAL { 3 } 1841 ::= { eponDeviceControlEntry 11 } 1843 eponDeviceRemoteMACAddressLLIDTable OBJECT-TYPE 1844 SYNTAX SEQUENCE OF EponDeviceRemoteMACAddressLLIDEntry 1845 MAX-ACCESS not-accessible 1846 STATUS current 1847 DESCRIPTION 1848 "A read-only table of objects that identifies the source 1849 MacAddress and LLIDs parameter of the remote devices in 1850 the network. 1851 This MacAddress value, as defined in [802.3], 1852 30.3.5.1.5, is updated on reception of a valid frame 1853 with: 1854 (1) a unicast destination Field or a destination Field 1855 equal to the reserved multicast address for MAC Control 1856 specified in [802.3] Annex 31A. 1857 (2) lengthOrType field value equal to the reserved 1858 Type for MAC Control as specified in [802.3] Annex 1859 31A. 1861 (3)an MPCP subtype value equal to the subtype reserved 1862 for MPCP as specified in [802.3] Annex 31A, 1863 and an LLID as allocated by the OLT. 1864 This table is denoted as 'Remote MAC address - LLID' 1865 (RMadL) table. 1866 The table is relevant only for an OLT device." 1867 ::= { eponDeviceControlObjects 2 } 1869 eponDeviceRemoteMACAddressLLIDEntry OBJECT-TYPE 1870 SYNTAX EponDeviceRemoteMACAddressLLIDEntry 1871 MAX-ACCESS not-accessible 1872 STATUS current 1873 DESCRIPTION 1874 "A group of entries. Applications create and delete 1875 entries using eponDeviceRMadlEntryStatus. 1876 When adding objects to an LLID they are added in the 1877 persistent order of their index in this table." 1878 INDEX {ifIndex } 1879 ::= { eponDeviceRemoteMACAddressLLIDTable 1 } 1881 EponDeviceRemoteMACAddressLLIDEntry ::= 1882 SEQUENCE { 1883 eponDeviceRemoteMACAddressLLIDName SnmpAdminString, 1884 eponDeviceRMadlLLID Unsigned32, 1885 eponDeviceRMadlLogID OBJECT IDENTIFIER, 1886 eponDeviceRMadlRemoteAddress MacAddress, 1887 eponDeviceRMadlType INTEGER, 1888 eponDeviceRMadlAction INTEGER, 1889 eponDeviceRMadlEntryStatus RowStatus 1890 } 1892 eponDeviceRemoteMACAddressLLIDName OBJECT-TYPE 1893 SYNTAX SnmpAdminString (SIZE (1..32)) 1894 MAX-ACCESS not-accessible 1895 STATUS current 1896 DESCRIPTION 1897 "A locally-unique, administratively assigned name for a 1898 group of entries." 1899 ::= { eponDeviceRemoteMACAddressLLIDEntry 1 } 1901 eponDeviceRMadlLLID OBJECT-TYPE 1902 SYNTAX Unsigned32 (1..4294967295) 1903 MAX-ACCESS read-write 1904 STATUS current 1905 DESCRIPTION 1906 "An arbitrary integer for the purpose of identifying the 1907 LLID. Writing can be done all the time." 1909 DEFVAL { 1 } 1910 ::= { eponDeviceRemoteMACAddressLLIDEntry 2 } 1912 eponDeviceRMadlLogID OBJECT-TYPE 1913 SYNTAX OBJECT IDENTIFIER 1914 MAX-ACCESS read-create 1915 STATUS current 1916 DESCRIPTION 1917 "The object identifier of a MIB module object to add to 1918 an entry, indicating the entry ID in the table. Writing 1919 can be done all the time." 1920 DEFVAL { zeroDotZero } 1921 ::= { eponDeviceRemoteMACAddressLLIDEntry 3 } 1923 eponDeviceRMadlRemoteAddress OBJECT-TYPE 1924 SYNTAX MacAddress 1925 MAX-ACCESS read-create 1926 STATUS current 1927 DESCRIPTION 1928 "The remote MAC address of the LLID. 1929 Writing can be done all the time." 1930 ::= { eponDeviceRemoteMACAddressLLIDEntry 4 } 1932 eponDeviceRMadlType OBJECT-TYPE 1933 SYNTAX INTEGER { 1934 notRegister (1), 1935 registered (2) 1936 } 1937 MAX-ACCESS read-write 1938 STATUS current 1939 DESCRIPTION 1940 "A list of types for entries - LLIDs. Indicates and 1941 defines the state of registration. notRegister(1) marks 1942 a non registered LID, registered(2) marks a registered 1943 LLID. Writing can be done all the time." 1944 DEFVAL { 1 } 1945 ::= { eponDeviceRemoteMACAddressLLIDEntry 5 } 1947 eponDeviceRMadlAction OBJECT-TYPE 1948 SYNTAX INTEGER { 1949 none (1), 1950 register (2), 1951 deregister (3), 1952 reregister (4) 1953 } 1954 MAX-ACCESS read-write 1955 STATUS current 1956 DESCRIPTION 1957 "A list of actions for an entry - LLID. Indicates and 1958 defines the state of registration for the remote device. 1959 none(1) marks no action, register(2) marks to register 1960 an LLID, deregister(3) marks to deregister an LLID, 1961 reregister(4) marks reregistered LLID. 1962 Writing can be done all the time." 1963 DEFVAL { 1 } 1964 ::= { eponDeviceRemoteMACAddressLLIDEntry 6 } 1966 eponDeviceRMadlEntryStatus OBJECT-TYPE 1967 SYNTAX RowStatus 1968 MAX-ACCESS read-create 1969 STATUS current 1970 DESCRIPTION 1971 "The control that allows creation and deletion of 1972 entries. Once made active an entry MAY not be modified 1973 except to delete it." 1974 ::= { eponDeviceRemoteMACAddressLLIDEntry 7 } 1976 --Statistics tables 1978 eponDeviceStatTable OBJECT-TYPE 1979 SYNTAX SEQUENCE OF EponDeviceStatEntry 1980 MAX-ACCESS not-accessible 1981 STATUS current 1982 DESCRIPTION 1983 "This table defines the list of statistics counters of 1984 EPON devices. The attributes are relevant for an OLT and 1985 an ONU." 1986 ::= { eponDeviceStatObjects 1} 1988 eponDeviceStatEntry OBJECT-TYPE 1989 SYNTAX EponDeviceStatEntry 1990 MAX-ACCESS not-accessible 1991 STATUS current 1992 DESCRIPTION 1993 "Table entries for Table of statistics counters of EPON 1994 devices." 1995 INDEX { ifIndex } 1996 ::= { eponDeviceStatTable 1 } 1998 EponDeviceStatEntry::= 1999 SEQUENCE { 2000 eponDeviceStatTxFramesQueue0 Counter32, 2001 eponDeviceStatTxFramesQueue1 Counter32, 2002 eponDeviceStatTxFramesQueue2 Counter32, 2003 eponDeviceStatTxFramesQueue3 Counter32, 2004 eponDeviceStatTxFramesQueue4 Counter32, 2005 eponDeviceStatTxFramesQueue5 Counter32, 2006 eponDeviceStatTxFramesQueue6 Counter32, 2007 eponDeviceStatTxFramesQueue7 Counter32, 2008 eponDeviceStatRxFramesQueue0 Counter32, 2009 eponDeviceStatRxFramesQueue1 Counter32, 2010 eponDeviceStatRxFramesQueue2 Counter32, 2011 eponDeviceStatRxFramesQueue3 Counter32, 2012 eponDeviceStatRxFramesQueue4 Counter32, 2013 eponDeviceStatRxFramesQueue5 Counter32, 2014 eponDeviceStatRxFramesQueue6 Counter32, 2015 eponDeviceStatRxFramesQueue7 Counter32, 2016 eponDeviceStatDroppedFramesQueue0 Counter32, 2017 eponDeviceStatDroppedFramesQueue1 Counter32, 2018 eponDeviceStatDroppedFramesQueue2 Counter32, 2019 eponDeviceStatDroppedFramesQueue3 Counter32, 2020 eponDeviceStatDroppedFramesQueue4 Counter32, 2021 eponDeviceStatDroppedFramesQueue5 Counter32, 2022 eponDeviceStatDroppedFramesQueue6 Counter32, 2023 eponDeviceStatDroppedFramesQueue7 Counter32 2024 } 2026 eponDeviceStatTxFramesQueue0 OBJECT-TYPE 2027 SYNTAX Counter32 2028 UNITS "frames" 2029 MAX-ACCESS read-only 2030 STATUS current 2031 DESCRIPTION 2032 "A count of the number of times a -Queue-0- frames 2033 transmission occurs. Increment the counter by one for 2034 each frame transmitted which is an output of -Queue-0-. 2035 The -Queue-0- marking matched the REPORT MPCP message 2036 Queue-0 field, as defined in [802.3] clause 64. This 2037 counter is mandatory for an ONU." 2038 ::= { eponDeviceStatEntry 1} 2040 eponDeviceStatTxFramesQueue1 OBJECT-TYPE 2041 SYNTAX Counter32 2042 UNITS "frames" 2043 MAX-ACCESS read-only 2044 STATUS current 2045 DESCRIPTION 2046 "A count of the number of times a -Queue-1- frames 2047 transmission occurs. Increment the counter by one for 2048 each frame transmitted which is an output of -Queue-1-. 2049 The -Queue-1- marking matched the REPORT MPCP message 2050 Queue-1 field, as defined in [802.3] clause 64. This 2051 counter is mandatory for an ONU." 2052 ::= { eponDeviceStatEntry 2} 2054 eponDeviceStatTxFramesQueue2 OBJECT-TYPE 2055 SYNTAX Counter32 2056 UNITS "frames" 2057 MAX-ACCESS read-only 2058 STATUS current 2059 DESCRIPTION 2060 "A count of the number of times a -Queue-2- frames 2061 transmission occurs. Increment the counter by one for 2062 each frame transmitted which is an output of -Queue-2-. 2063 The -Queue-2- marking matched the REPORT MPCP message 2064 Queue-2 field, as defined in [802.3] clause 64. This 2065 counter is mandatory for an ONU." 2066 ::= { eponDeviceStatEntry 3} 2068 eponDeviceStatTxFramesQueue3 OBJECT-TYPE 2069 SYNTAX Counter32 2070 UNITS "frames" 2071 MAX-ACCESS read-only 2072 STATUS current 2073 DESCRIPTION 2074 "A count of the number of times a -Queue-3- frames 2075 transmission occurs. Increment the counter by one for 2076 each frame transmitted which is an output of -Queue-3-. 2077 The -Queue-3- marking matched the REPORT MPCP message 2078 Queue-3 field, as defined in [802.3] clause 64. 2079 This counter is mandatory for an ONU." 2080 ::= { eponDeviceStatEntry 4} 2082 eponDeviceStatTxFramesQueue4 OBJECT-TYPE 2083 SYNTAX Counter32 2084 UNITS "frames" 2085 MAX-ACCESS read-only 2086 STATUS current 2087 DESCRIPTION 2088 "A count of the number of times a -Queue-4- frames 2089 transmission occurs. Increment the counter by one for 2090 each frame transmitted which is an output of -Queue-4-. 2091 The -Queue-4- marking matched the REPORT MPCP message 2092 Queue-4 field, as defined in [802.3] clause 64. 2093 This counter is mandatory for an ONU." 2094 ::= { eponDeviceStatEntry 5} 2096 eponDeviceStatTxFramesQueue5 OBJECT-TYPE 2097 SYNTAX Counter32 2098 UNITS "frames" 2099 MAX-ACCESS read-only 2100 STATUS current 2101 DESCRIPTION 2102 "A count of the number of times a -Queue-5- frames 2103 transmission occurs. Increment the counter by one for 2104 each frame transmitted which is an output of -Queue-5-. 2105 The -Queue-5- marking matched the REPORT MPCP message 2106 Queue-5 field, as defined in [802.3] clause 64. 2107 This counter is mandatory for an ONU." 2108 ::= { eponDeviceStatEntry 6} 2110 eponDeviceStatTxFramesQueue6 OBJECT-TYPE 2111 SYNTAX Counter32 2112 UNITS "frames" 2113 MAX-ACCESS read-only 2114 STATUS current 2115 DESCRIPTION 2116 "A count of the number of times a -Queue-6- frames 2117 transmission occurs. Increment the counter by one for 2118 each frame transmitted which is an output of -Queue-6-. 2119 The -Queue-6- marking matched the REPORT MPCP message 2120 Queue-6 field, as defined in [802.3] clause 64. 2121 This counter is mandatory for an ONU." 2122 ::= { eponDeviceStatEntry 7} 2124 eponDeviceStatTxFramesQueue7 OBJECT-TYPE 2125 SYNTAX Counter32 2126 UNITS "frames" 2127 MAX-ACCESS read-only 2128 STATUS current 2129 DESCRIPTION 2130 "A count of the number of times a -Queue-7- frames 2131 transmission occurs. Increment the counter by one for 2132 each frame transmitted which is an output of -Queue-7-. 2133 The -Queue-7- marking matched the REPORT MPCP message 2134 Queue-7 field, as defined in [802.3] clause 64. 2135 This counter is mandatory for an ONU." 2136 ::= { eponDeviceStatEntry 8} 2138 eponDeviceStatRxFramesQueue0 OBJECT-TYPE 2139 SYNTAX Counter32 2140 UNITS "frames" 2141 MAX-ACCESS read-only 2142 STATUS current 2143 DESCRIPTION 2144 "A count of the number of times a -Queue-0- frames 2145 reception occurs. Increment the counter by one for each 2146 frame received, which is an output of -Queue-0-. The 2147 -Queue-0- marking matched the REPORT MPCP message 2148 Queue-0 field, as defined in [802.3] clause 64. 2149 This counter is mandatory for an ONU." 2150 ::= { eponDeviceStatEntry 9} 2152 eponDeviceStatRxFramesQueue1 OBJECT-TYPE 2153 SYNTAX Counter32 2154 UNITS "frames" 2155 MAX-ACCESS read-only 2156 STATUS current 2157 DESCRIPTION 2158 "A count of the number of times a -Queue-1- frames 2159 reception occurs. Increment the counter by one for each 2160 frame received, which is an output of -Queue-1-. The 2161 -Queue-1- marking matched the REPORT MPCP message 2162 Queue-1 field, as defined in [802.3] clause 64. 2163 This counter is mandatory for an ONU." 2164 ::= { eponDeviceStatEntry 10} 2166 eponDeviceStatRxFramesQueue2 OBJECT-TYPE 2167 SYNTAX Counter32 2168 UNITS "frames" 2169 MAX-ACCESS read-only 2170 STATUS current 2171 DESCRIPTION 2172 "A count of the number of times a -Queue-2- frames 2173 reception occurs. Increment the counter by one for each 2174 frame received, which is an output of -Queue-2-. The 2175 -Queue-2- marking matched the REPORT MPCP message 2176 Queue-2 field, as defined in [802.3] clause 64. 2177 This counter is mandatory for an ONU." 2178 ::= { eponDeviceStatEntry 11} 2180 eponDeviceStatRxFramesQueue3 OBJECT-TYPE 2181 SYNTAX Counter32 2182 UNITS "frames" 2183 MAX-ACCESS read-only 2184 STATUS current 2185 DESCRIPTION 2186 "A count of the number of times a -Queue-3- frames 2187 reception occurs. Increment the counter by one for each 2188 frame received, which is an output of -Queue-3-. The 2189 -Queue-3- marking matched the REPORT MPCP message 2190 Queue-3 field, as defined in [802.3] clause 64. 2191 This counter is mandatory for an ONU." 2193 ::= { eponDeviceStatEntry 12} 2195 eponDeviceStatRxFramesQueue4 OBJECT-TYPE 2196 SYNTAX Counter32 2197 UNITS "frames" 2198 MAX-ACCESS read-only 2199 STATUS current 2200 DESCRIPTION 2201 "A count of the number of times a -Queue-4- frames 2202 reception occurs. Increment the counter by one for each 2203 frame received, which is an output of -Queue-4-. The 2204 -Queue-4- marking matched the REPORT MPCP message 2205 Queue-4 field, as defined in [802.3] clause 64. 2206 This counter is mandatory for an ONU." 2207 ::= { eponDeviceStatEntry 13} 2209 eponDeviceStatRxFramesQueue5 OBJECT-TYPE 2210 SYNTAX Counter32 2211 UNITS "frames" 2212 MAX-ACCESS read-only 2213 STATUS current 2214 DESCRIPTION 2215 "A count of the number of times a -Queue-5- frames 2216 reception occurs. Increment the counter by one for each 2217 frame received, which is an output of -Queue-5-. The 2218 -Queue-5- marking matched the REPORT MPCP message 2219 Queue-5 field, as defined in [802.3] clause 64. 2220 This counter is mandatory for an ONU." 2221 ::= { eponDeviceStatEntry 14} 2223 eponDeviceStatRxFramesQueue6 OBJECT-TYPE 2224 SYNTAX Counter32 2225 UNITS "frames" 2226 MAX-ACCESS read-only 2227 STATUS current 2228 DESCRIPTION 2229 "A count of the number of times a -Queue-6- frames 2230 reception occurs. Increment the counter by one for each 2231 frame received, which is an output of -Queue-6-. The 2232 -Queue-6- marking matched the REPORT MPCP message 2233 Queue-6 field, as defined in [802.3] clause 64. 2234 This counter is mandatory for an ONU." 2235 ::= { eponDeviceStatEntry 15} 2237 eponDeviceStatRxFramesQueue7 OBJECT-TYPE 2238 SYNTAX Counter32 2239 UNITS "frames" 2240 MAX-ACCESS read-only 2241 STATUS current 2242 DESCRIPTION 2243 "A count of the number of times a -Queue-7- frames 2244 reception occurs. Increment the counter by one for each 2245 frame received, which is an output of -Queue-7-. The 2246 -Queue-7- marking matched the REPORT MPCP message 2247 Queue-7 field, as defined in [802.3] clause 64. 2248 This counter is mandatory for an ONU." 2249 ::= { eponDeviceStatEntry 16} 2251 eponDeviceStatDroppedFramesQueue0 OBJECT-TYPE 2252 SYNTAX Counter32 2253 UNITS "frames" 2254 MAX-ACCESS read-only 2255 STATUS current 2256 DESCRIPTION 2257 "A count of the number of times a -Queue-0- frames drops 2258 occurs. Increment the counter by one for each frame 2259 dropped from -Queue-0-. The -Queue-0- marking matched 2260 the REPORT MPCP message Queue-0 field, as defined in 2261 [802.3] clause 64. 2262 This counter is mandatory for an ONU." 2263 ::= { eponDeviceStatEntry 17} 2265 eponDeviceStatDroppedFramesQueue1 OBJECT-TYPE 2266 SYNTAX Counter32 2267 UNITS "frames" 2268 MAX-ACCESS read-only 2269 STATUS current 2270 DESCRIPTION 2271 "A count of the number of times a -Queue-1- frames drops 2272 occurs. Increment the counter by one for each frame 2273 dropped from -Queue-1-. The -Queue-1- marking matched 2274 the REPORT MPCP message Queue-1 field, as defined in 2275 [802.3] clause 64. 2276 This counter is mandatory for an ONU." 2277 ::= { eponDeviceStatEntry 18} 2279 eponDeviceStatDroppedFramesQueue2 OBJECT-TYPE 2280 SYNTAX Counter32 2281 UNITS "frames" 2282 MAX-ACCESS read-only 2283 STATUS current 2284 DESCRIPTION 2285 "A count of the number of times a -Queue-2- frames drops 2286 occurs. Increment the counter by one for each frame 2287 dropped from -Queue-2-. The -Queue-2- marking matched 2288 the REPORT MPCP message Queue-2 field, as defined in 2290 [802.3] clause 64. 2291 This counter is mandatory for an ONU." 2292 ::= { eponDeviceStatEntry 19} 2294 eponDeviceStatDroppedFramesQueue3 OBJECT-TYPE 2295 SYNTAX Counter32 2296 UNITS "frames" 2297 MAX-ACCESS read-only 2298 STATUS current 2299 DESCRIPTION 2300 "A count of the number of times a -Queue-3- frames drops 2301 occurs. Increment the counter by one for each frame 2302 dropped from -Queue-3-. The -Queue-3- marking matched 2303 the REPORT MPCP message Queue-3 field, as defined in 2304 [802.3] clause 64. 2305 This counter is mandatory for an ONU." 2306 ::= { eponDeviceStatEntry 20} 2308 eponDeviceStatDroppedFramesQueue4 OBJECT-TYPE 2309 SYNTAX Counter32 2310 UNITS "frames" 2311 MAX-ACCESS read-only 2312 STATUS current 2313 DESCRIPTION 2314 "A count of the number of times a -Queue-4- frames drops 2315 occurs. Increment the counter by one for each frame 2316 dropped from -Queue-4-. The -Queue-4- marking matched 2317 the REPORT MPCP message Queue-4 field, as defined in 2318 [802.3] clause 64. 2319 This counter is mandatory for an ONU." 2320 ::= { eponDeviceStatEntry 21} 2322 eponDeviceStatDroppedFramesQueue5 OBJECT-TYPE 2323 SYNTAX Counter32 2324 UNITS "frames" 2325 MAX-ACCESS read-only 2326 STATUS current 2327 DESCRIPTION 2328 "A count of the number of times a -Queue-5- frames drops 2329 occurs. Increment the counter by one for each frame 2330 dropped from -Queue-5-. The -Queue-5- marking matched 2331 the REPORT MPCP message Queue-5 field, as defined in 2332 [802.3] clause 64. 2333 This counter is mandatory for an ONU." 2334 ::= { eponDeviceStatEntry 22} 2336 eponDeviceStatDroppedFramesQueue6 OBJECT-TYPE 2337 SYNTAX Counter32 2338 UNITS "frames" 2339 MAX-ACCESS read-only 2340 STATUS current 2341 DESCRIPTION 2342 "A count of the number of times a -Queue-6- frames drops 2343 occurs. Increment the counter by one for each frame 2344 dropped from -Queue-6-. The -Queue-6- marking matched 2345 the REPORT MPCP message Queue-6 field, as defined in 2346 [802.3] clause 64. 2347 This counter is mandatory for an ONU." 2348 ::= { eponDeviceStatEntry 23} 2350 eponDeviceStatDroppedFramesQueue7 OBJECT-TYPE 2351 SYNTAX Counter32 2352 UNITS "frames" 2353 MAX-ACCESS read-only 2354 STATUS current 2355 DESCRIPTION 2356 "A count of the number of times a -Queue-7- frames drops 2357 occurs. Increment the counter by one for each frame 2358 dropped from -Queue-7-. The -Queue-7- marking matched 2359 the REPORT MPCP message Queue-7 field, as defined in 2360 [802.3] clause 64. 2361 This counter is mandatory for an ONU." 2362 ::= { eponDeviceStatEntry 24} 2364 --Editor's Note use reference to event MIB modules [RFC2981] and 2365 --docsis MIB modules [RFC2669] 2367 -- Conformance Statements 2369 -- Conformance Groups 2371 eponDeviceGroups OBJECT IDENTIFIER ::={ eponDeviceConformance 1} 2373 eponDeviceGroupControl OBJECT-GROUP 2374 OBJECTS { 2375 eponDeviceObjectReset, 2376 eponDeviceObjectModes, 2377 eponDeviceObjectFecEnabled, 2378 eponDeviceObjectDeviceReadyMode, 2379 eponDeviceObjectPowerDown, 2380 eponDeviceObjectNumberOfLLIDs, 2381 eponDeviceObjectReportNumThreshold, 2382 eponDeviceObjectReportThreshold, 2383 eponDeviceObjectReportMaximumNumThreshold, 2384 eponDeviceObjectReportMaximumNumQueues, 2385 eponDeviceRemoteMACAddressLLIDControl 2386 } 2387 STATUS current 2388 DESCRIPTION 2389 "A collection of objects of eponDevice control 2390 definition." 2391 ::= { eponDeviceGroups 1 } 2393 eponDeviceGroupRMadLTable OBJECT-GROUP 2394 OBJECTS { 2395 eponDeviceRMadlLLID, 2396 eponDeviceRMadlLogID, 2397 eponDeviceRMadlRemoteAddress, 2398 eponDeviceRMadlType, 2399 eponDeviceRMadlAction, 2400 eponDeviceRMadlEntryStatus 2401 } 2402 STATUS current 2403 DESCRIPTION 2404 "A collection of objects of eponDevice remote Mac address 2405 to LLID table." 2406 ::= { eponDeviceGroups 2 } 2408 eponDeviceGroupStat OBJECT-GROUP 2409 OBJECTS { 2410 eponDeviceStatTxFramesQueue0, 2411 eponDeviceStatTxFramesQueue1, 2412 eponDeviceStatTxFramesQueue2, 2413 eponDeviceStatTxFramesQueue3, 2414 eponDeviceStatTxFramesQueue4, 2415 eponDeviceStatTxFramesQueue5, 2416 eponDeviceStatTxFramesQueue6, 2417 eponDeviceStatTxFramesQueue7, 2418 eponDeviceStatRxFramesQueue0, 2419 eponDeviceStatRxFramesQueue1, 2420 eponDeviceStatRxFramesQueue2, 2421 eponDeviceStatRxFramesQueue3, 2422 eponDeviceStatRxFramesQueue4, 2423 eponDeviceStatRxFramesQueue5, 2424 eponDeviceStatRxFramesQueue6, 2425 eponDeviceStatRxFramesQueue7, 2426 eponDeviceStatDroppedFramesQueue0, 2427 eponDeviceStatDroppedFramesQueue1, 2428 eponDeviceStatDroppedFramesQueue2, 2429 eponDeviceStatDroppedFramesQueue3, 2430 eponDeviceStatDroppedFramesQueue4, 2431 eponDeviceStatDroppedFramesQueue5, 2432 eponDeviceStatDroppedFramesQueue6, 2433 eponDeviceStatDroppedFramesQueue7 2434 } 2435 STATUS current 2436 DESCRIPTION 2437 "A collection of objects of EPON device Statistics" 2438 ::= { eponDeviceGroups 3 } 2440 -- Compliance 2442 eponDeviceCompliances OBJECT IDENTIFIER ::= {eponDeviceConformance 2} 2444 eponDeviceCompliance MODULE-COMPLIANCE 2445 STATUS current 2446 DESCRIPTION "The compliance statement for EPON Devices." 2447 MODULE -- this module 2448 MANDATORY-GROUPS { eponDeviceGroupControl } 2450 GROUP eponDeviceGroupRMadLTable 2451 DESCRIPTION " This group is mandatory for all 2452 OLT EPON devices supporting LLID-MAC 2453 address table." 2455 GROUP eponDeviceGroupStat 2456 DESCRIPTION "This group is mandatory for all EPON devices 2457 supporting interfaces for Statistics collection." 2459 ::= { eponDeviceCompliances 1} 2461 END 2463 10. Security Considerations 2465 There are number of managed objects defined in this MIB module that 2466 have a MAX-ACCESS clause of read-write or read-create. Writing to 2467 these objects can have a potentially disruptive effects on network 2468 operation: Including: 2470 Changing dot3MpcpAdminState state (Writing can be done all the time) 2472 Changing dot3EponMauFecMode mode (Writing can be done all the time) 2474 Changing eponDeviceObjectReset mode (Writing can be done all the 2475 time) 2477 Changing eponDeviceObjectFecEnabled mode (Writing can be done all the 2478 time) 2480 Changing eponDeviceObjectDeviceReadyMode (Writing can be done all the 2481 time) 2483 Changing eponDeviceObjectPowerDown (Writing can be done all the time) 2485 Changing eponDeviceObjectReportNumThreshold (Writing can be done all 2486 the time) 2488 Changing eponDeviceObjectReportThreshold (Writing can be done all the 2489 time) 2491 Changing eponDeviceRemoteMACAddressLLIDControl (Writing can be done 2492 all the time) 2494 Changing eponDeviceRMadlLogID (Writing can be done all the time) 2496 Changing eponDeviceRMadlLLID (Writing can be done all the time) 2498 Changing eponDeviceRMadlRemoteAddress (Writing can be done all the 2499 time) 2501 Changing eponDeviceRMadlType (Writing can be done all the time) 2503 Changing eponDeviceRMadlAction (Writing can be done all the time) 2505 Changing eponDeviceRMadlEntryStatus (Writing can be done all the 2506 time) 2508 The user of this MIB module must therefore be aware that support for 2509 SET operations in a non-secure environment without proper protection 2510 can have a negative effect on network operations. 2512 The readable objects in this MIB module (i.e., those with MAX-ACCESS 2513 other than not-accessible) may be considered sensitive in some 2514 environments since, collectively, they provide information about the 2515 performance of network interfaces and can reveal some aspects of 2516 their configuration. In such environments it is important to control 2517 even GET and NOTIFY access to these objects and possibly even to 2518 encrypt their values when sending them over the network via SNMP. 2520 SNMP versions prior to SNMPv3 did not include adequate security. 2521 Even if the network itself is secure (for example by using IPSec), 2522 even then, there is no control as to who on the secure network is 2523 allowed to access and GET/SET (read/change/create/delete) the objects 2524 in this MIB module. 2526 It is RECOMMENDED that implementers consider the security features as 2527 provided by the SNMPv3 framework (see [RFC3410], section 8), 2528 including full support for the SNMPv3 cryptographic mechanisms (for 2529 authentication and privacy). 2531 Further, deployment of SNMP versions prior to SNMPv3 is NOT 2532 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 2533 enable cryptographic security. It is then a customer/operator 2534 responsibility to ensure that the SNMP entity giving access to an 2535 instance of this MIB module is properly configured to give access to 2536 the objects only to those principals (users) that have legitimate 2537 rights to indeed GET or SET (change/create/delete) them. 2539 11. References 2541 11.1 Normative References 2543 [802.3] IEEE, "Institute of Electrical and Electronic Engineers, 2544 IEEE Std 802.3-2004, "IEEE Standard for Carrier Sense 2545 Multiple Access with Collision Detection (CSMA/CD) Access 2546 Method and Physical Layer Specifications", December 2004. 2548 [I-D.ietf-hubmib-efm-mib] 2549 Squire, M., "Ethernet in the First Mile (EFM) Common MIB", 2550 Internet-Draft draft-squire-hubmib-efm-mib-02, December 2551 2004. 2553 [RFC1493] Decker, E., Langille, P., Rijsinghani, A. and K. 2554 McCloghrie, "Definitions of Managed Objects for Bridges", 2555 RFC 1493, July 1993. 2557 [RFC1525] Decker, E., McCloghrie, K., Langille, P. and A. 2558 Rijsinghani, "Definitions of Managed Objects for Source 2559 Routing Bridges", RFC 1525, September 1993. 2561 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed. and J. 2562 Schoenwaelder, Ed., "Structure of Management Information 2563 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 2565 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed. and J. 2566 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 2567 STD 58, RFC 2579, April 1999. 2569 [RFC2580] McCloghrie, K., Perkins, D. and J. Schoenwaelder, 2570 "Conformance Statements for SMIv2", STD 58, RFC 2580, 2571 April 1999. 2573 [RFC2669] St. Johns, M., "DOCSIS Cable Device MIB Cable Device 2574 Management Information Base for DOCSIS compliant Cable 2575 Modems and Cable Modem Termination Systems", RFC 2669, 2576 August 1999. 2578 [RFC2737] McCloghrie, K. and A. Bierman, "Entity MIB (Version 2)", 2579 RFC 2737, December 1999. 2581 [RFC2981] Kavasseri, R., "Event MIB", RFC 2981, October 2000. 2583 [RFC3591] Lam, H-K., Stewart, M. and A. Huynh, "Definitions of 2584 Managed Objects for the Optical Interface Type", RFC 3591, 2585 September 2003. 2587 [RFC3635] Flick, J., "Definitions of Managed Objects for the 2588 Ethernet-like Interface Types", RFC 3635, September 2003. 2590 [RFC3636] Flick, J., "Definitions of Managed Objects for IEEE 802.3 2591 Medium Attachment Units (MAUs)", RFC 3636, September 2003. 2593 11.2 Informative References 2595 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 2596 Requirement Levels", BCP 14, RFC 2119, March 1997. 2598 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 2599 MIB", RFC 2863, June 2000. 2601 [RFC2864] McCloghrie, K. and G. Hanson, "The Inverted Stack Table 2602 Extension to the Interfaces Group MIB", RFC 2864, June 2603 2000. 2605 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 2606 "Introduction and Applicability Statements for 2607 Internet-Standard Management Framework", RFC 3410, 2608 December 2002. 2610 [RFC3433] Bierman, A., Romascanu, D. and K. Norseth, "Entity Sensor 2611 Management Information Base", RFC 3433, December 2002. 2613 Author's Address 2615 Lior Khermosh 2616 Passave Technologies 2617 Kohav Hertzelia bldg, 2618 4 Hasadnaot St., 2619 Hertzliya Pituach, 46120 2620 ISRAEL 2622 Phone: +972-9-9628000 Ext: 302 2623 Fax: +972-9-9628001 2624 Email: lior.khermosh@passave.com 2626 Intellectual Property Statement 2628 The IETF takes no position regarding the validity or scope of any 2629 Intellectual Property Rights or other rights that might be claimed to 2630 pertain to the implementation or use of the technology described in 2631 this document or the extent to which any license under such rights 2632 might or might not be available; nor does it represent that it has 2633 made any independent effort to identify any such rights. Information 2634 on the procedures with respect to rights in RFC documents can be 2635 found in BCP 78 and BCP 79. 2637 Copies of IPR disclosures made to the IETF Secretariat and any 2638 assurances of licenses to be made available, or the result of an 2639 attempt made to obtain a general license or permission for the use of 2640 such proprietary rights by implementers or users of this 2641 specification can be obtained from the IETF on-line IPR repository at 2642 http://www.ietf.org/ipr. 2644 The IETF invites any interested party to bring to its attention any 2645 copyrights, patents or patent applications, or other proprietary 2646 rights that may cover technology that may be required to implement 2647 this standard. Please address the information to the IETF at 2648 ietf-ipr@ietf.org. 2650 The IETF has been notified of intellectual property rights claimed in 2651 regard to some or all of the specification contained in this 2652 document. For more information consult the online list of claimed 2653 rights. 2655 Disclaimer of Validity 2657 This document and the information contained herein are provided on an 2658 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 2659 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNET 2660 ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED, 2661 INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE 2662 INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 2663 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 2665 Copyright Statement 2667 Copyright (C) The Internet Society (2005). This document is subject 2668 to the rights, licenses and restrictions contained in BCP 78, and 2669 except as set forth therein, the authors retain all their rights. 2671 Acknowledgment 2673 Funding for the RFC Editor function is currently provided by the 2674 Internet Society.