idnits 2.17.1 draft-ietf-hubmib-efm-epon-mib-06.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 on line 15. -- Found old boilerplate from RFC 3978, Section 5.5, updated by RFC 4748 on line 4290. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 4301. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 4308. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 4314. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The abstract seems to contain references ([RFC2580], [RFC2119], [RFC2578], [RFC2579], [RFC3410]), which it shouldn't. Please replace those with straight textual mentions of the documents in question. == There are 11 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 IETF Trust Copyright Line does not match the current year == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (November 13, 2006) is 6372 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) -- Possible downref: Non-RFC (?) normative reference: ref. 'ITU-T G.975' -- Possible downref: Non-RFC (?) normative reference: ref. 'ITU-T G.983' ** Obsolete normative reference: RFC 3636 (Obsoleted by RFC 4836) == Outdated reference: A later version (-05) exists of draft-ietf-hubmib-rfc3636bis-03 == Outdated reference: A later version (-06) exists of draft-ietf-hubmib-efm-mib-04 Summary: 3 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 PMC-SIERRA 4 Intended status: Standards Track November 13, 2006 5 Expires: May 17, 2007 7 Managed Objects of Ethernet Passive Optical Networks (EPON) 8 draft-ietf-hubmib-efm-epon-mib-06.txt 10 Status of this Memo 12 By submitting this Internet-Draft, each author represents that any 13 applicable patent or other IPR claims of which he or she is aware 14 have been or will be disclosed, and any of which he or she becomes 15 aware will be disclosed, in accordance with Section 6 of BCP 79. 17 Internet-Drafts are working documents of the Internet Engineering 18 Task Force (IETF), its areas, and its working groups. Note that 19 other groups may also distribute working documents as Internet- 20 Drafts. 22 Internet-Drafts are draft documents valid for a maximum of six months 23 and may be updated, replaced, or obsoleted by other documents at any 24 time. It is inappropriate to use Internet-Drafts as reference 25 material or to cite them other than as "work in progress." 27 The list of current Internet-Drafts can be accessed at 28 http://www.ietf.org/ietf/1id-abstracts.txt. 30 The list of Internet-Draft Shadow Directories can be accessed at 31 http://www.ietf.org/shadow.html. 33 This Internet-Draft will expire on May 17, 2007. 35 Copyright Notice 37 Copyright (C) The IETF Trust (2006). 39 Abstract 41 This document defines a portion of the Management Information Base 42 (MIB) for use with network management protocols in TCP/IP based 43 Internets. In particular, it defines objects for managing interfaces 44 that conform to the Ethernet Passive Optical Networks (EPON) standard 45 as defined in the IEEE Std 802.3ah-2004, which are extended 46 capabilities to the Ethernet like interfaces. 48 The Internet-Standard Management Framework 50 For a detailed overview of the documents that describe the current 51 Internet-Standard Management Framework, please refer to section 7 of 52 RFC 3410 [RFC3410]. Managed objects are accessed via a virtual 53 information store, termed the Management Information Base or MIB. 54 MIB objects are generally accessed through the Simple Network 55 Management Protocol (SNMP). Objects in the MIB are defined using the 56 mechanisms defined in the Structure of Management Information (SMI). 57 This memo specifies a MIB module that is compliant to the SMIv2, 58 which is described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 59 [RFC2579] and STD 58, RFC 2580 [RFC2580]. 61 Terminology 63 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 64 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 65 document are to be interpreted as described in [RFC2119]. 67 Table of Contents 69 1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . 5 70 1.1. Terminology and abbreviations . . . . . . . . . . . . . . 5 71 1.2. EPON architecture highlights . . . . . . . . . . . . . . 6 72 1.2.1. Introduction . . . . . . . . . . . . . . . . . . . . 6 73 1.2.2. Principles of operation . . . . . . . . . . . . . . . 8 74 1.2.3. The physical media . . . . . . . . . . . . . . . . . 9 75 1.2.4. PMD specifications . . . . . . . . . . . . . . . . . 10 76 1.2.5. Point to point emulation . . . . . . . . . . . . . . 10 77 1.2.6. Principles of the MPCP . . . . . . . . . . . . . . . 12 78 1.2.7. Forward Error correction (FEC) . . . . . . . . . . . 15 79 1.3. Management architecture . . . . . . . . . . . . . . . . . 15 80 2. MIB structure . . . . . . . . . . . . . . . . . . . . . . . . 20 81 3. Relation to other MIB Modules . . . . . . . . . . . . . . . . 26 82 3.1. Relation to the Interfaces MIB and Ethernet-like 83 Interfaces MIB . . . . . . . . . . . . . . . . . . . . . 26 84 3.2. Relation to the IEEE 802.3 MAU MIBs . . . . . . . . . . . 33 85 3.3. Relation to the EFM OAM MIB . . . . . . . . . . . . . . . 33 86 3.4. Relation to the bridge MIB . . . . . . . . . . . . . . . 34 87 4. Mapping of IEEE 802.3ah Managed Objects . . . . . . . . . . . 35 88 5. Definitions - The DOT3 EPON MIB module . . . . . . . . . . . 39 89 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 93 90 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 94 91 8. Security Considerations . . . . . . . . . . . . . . . . . . . 95 92 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 98 93 9.1. Normative References . . . . . . . . . . . . . . . . . . 98 94 9.2. Informative References . . . . . . . . . . . . . . . . . 99 95 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 100 96 Intellectual Property and Copyright Statements . . . . . . . . . 101 98 1. Overview 100 This document defines a portion of the Management Information Base 101 (MIB) for use with network management protocols in TCP/IP based 102 Internets. In particular, it defines objects for managing interfaces 103 that conform to the Ethernet Passive Optical Networks (EPON) standard 104 as defined in [802.3ah], which are extended capabilities to the 105 Ethernet like interfaces. The document contains a list of management 106 objects based on the attributes defined in the relevant parts of 107 [802.3ah] Annex 30A, referring to EPON. 109 1.1. Terminology and abbreviations 111 ACK - Acknowledge 113 BER - Bit Error Rate 115 BW - Bandwidth 117 CO - Central Office 119 CPE - Customer Premises Equipment 121 CRC - Cyclic Redundancy Check 123 FCS - Frame Check Sequence 125 FEC - Forward Error Correction 127 EFM - Ethernet First Mile 129 EPON - Ethernet Passive Optical Network 131 GMII - Gigabit Media Independent Interface 133 LAN - Local Area Network 135 LLID - Logical Link Identifier 137 MAC - Media Access Control 139 Mbps - Mega-bit per second 141 MDI - Medium Dependent Interface 143 MDIO - Management Data Input/Output 145 MPCP - Multi-Point Control Protocol 146 MP2PE - Multi-Point to Point Emulation 148 OAM - Operation Administration Maintenance 150 OLT - Optical Line Terminal (Server unit of the EPON) 152 OMP - Optical Multi-Point 154 ONU - Optical Network Unit (Client unit of the EPON) 156 P2PE - Point to Point Emulation 158 P2MP - Point to Multi-Point 160 PCS - Physical Coding Sublayer 162 PHY - Physical Layer 164 PMD - Physical Medium Dependent 166 PMA - Physical Medium Attachment 168 PON - Passive Optical Network 170 RTT - Round Trip Time 172 RS - Reconciliation Sublayer 174 SLA - Service Level Agreement 176 SLD - Start of LLID Delimiter 178 TDM - Time Division Multiplexing 180 TQ - Time Quanta 182 1.2. EPON architecture highlights 184 1.2.1. Introduction 186 The EPON standard, as defined in [802.3ah], is defining the physical 187 media (Layer 1) and media access (layer 2) of the EPON interface. 188 The EPON is a variant of the Gigabit Ethernet protocol for the 189 Optical Access. The Optical Access topology is based on passive 190 optical splitting topology. The link of a Passive Optical Network 191 (PON) is based on a single, shared optical fiber with passive optical 192 splitters dividing the single fiber into separate subscribers. 194 The Optical Line Terminal (OLT) is the server unit of the network, 195 located at the Central Office (CO). 197 The Optical Network Unit (ONU) is the client unit of the network, 198 located at the Customer Premises Equipment (CPE). 200 The following diagram describes the PON topology: 202 Device with 203 one or more P2MP 204 interfaces such as OLT 205 for EPON An EPON IP host 206 ------- OLT ONU "modem" -------- 207 Other IEEE | | interface | interface ------ Other IEEE| | 208 interface | |-------\----------------| | interface | | 209 ===========| | \ | |===========| | 210 | | \ ------ -------- 211 | | \ ------ -------- 212 . . \------------| | | | 213 | |------\ | |===========| | 214 | | \ ------ -------- 215 ------- \ etc 217 The IEEE layering architecture of an EPON interface is defined in the 218 diagram of figure 56.2 [802.3ah]. The following clauses in the 219 [802.3ah] define the corresponding layers of an EPON interface: 221 Clause 30 - management 223 Clause 60 - PMD for EPON media (Burst PMD) 225 Clause 64 - MPCP (Multipoint control protocol) - defines the 226 multipoint architecture, and control protocol for the media access of 227 EPON. 229 Clause 65 - 231 a) Virtual links definition for the EPON 233 b) FEC 235 c) PMA for the EPON. 237 1.2.2. Principles of operation 239 The specification of the EPON interface is based on the specification 240 of the gigabit Ethernet interface as described in [802.3] clause 35 241 and 36. The Ethernet MAC is working in gigabit rate. The media 242 interface to the MAC is through the GMII interface as described in 243 clause 35 and the PCS layer is based on the gigabit Ethernet PCS as 244 described in clause 36. The special EPON layers are added to the 245 Ethernet layering in the following places: 247 The MPCP is placed in the MAC control layer, providing the EPON 248 control protocol. The Emulation layer, located at the RS 249 (Reconciliation Sublayer), creates virtual private path to each ONU. 250 The FEC layer is located between the PCS and PMA layers, enhancing 251 reach and split performance of the optical link. 253 The following diagram describes the layering model of an EPON 254 interface: 256 +==========================================+ 257 | Higher layers | 258 +==========================================+ 259 | 802.1D Bridge | 260 +==========================================+ 261 | MAC client| ... |MAC client| 262 +==========================================+ 263 | MAC Control - (MPCP) | *NEW* 264 +==========================================+ 265 | MAC | ... | MAC | 266 +==========================================+ 267 | P2P Emulation (P2PE) | *NEW* 268 +==========================================+ 269 | | 270 | GMII | 271 | | 272 +==========================================+ 273 | PCS | 274 +==========================================+ 275 | FEC | *NEW* 276 +==========================================+ 277 | PMA | *Enhanced parameters 278 +==========================================+ for EPON* 279 | PMD | *Enhanced parameters 280 +==========================================+ for EPON* 281 | | 282 | MDI | 283 | | 284 /===================/ 285 / Media / 286 /===================/ 288 1.2.3. The physical media 290 The physical link is a fiber optical link. The OLT and ONUs are 291 connected through passive optical splitters. Downlink denotes the 292 transmission from the OLT to the ONUs. Uplink denotes the 293 transmission from the ONUs to the OLT. Uplink and downlink are 294 multiplexed using separated wavelengths on the same fiber. The 295 downlink is a broadcast medium where the OLT transmits the data to 296 all ONUs. The uplink is a shared transmission medium for all of the 297 ONUs. The uplink access is based on time division multiplexing (TDM) 298 and the management of the TDM media access is defined by the Multi- 299 Point control protocol (MPCP). The MPCP is a control protocol based 300 on an inband packet messaging. The OLT sends control messages (GATE 301 messages) allowing ONUs to transmit, defining when the transmission 302 occurs and what is its duration. These messages define the 303 transmission order and the amount of BW for each ONU. A scheduling 304 algorithm at the OLT, which is not defined in the [802.3ah], is 305 responsible of allocating the BW and controlling the delay of each 306 ONU according to its SLA. 308 1.2.4. PMD specifications 310 The same optical wavelength plan as the [ITU-T G.983] is selected. 311 The transceivers are derivatives of existing Ethernet optical 312 transceivers, with dual wavelength on a single fiber and extended 313 burst capabilities for the uplink. The uplink burst capability is 314 the burst transmission functionality for the ONUs and burst reception 315 functionality for the OLT. The [802.3ah] selected very relaxed burst 316 parameters to reduce the device cost of EPON products. 318 1.2.5. Point to point emulation 320 The downstream is a broadcast link meaning the OLT transmission is 321 shared for all ONUs. The sharing of the transmission of the OLT has 322 some negative privacy aspects, and should be limited to broadcast 323 traffic in nature only. The traffic dedicated to each ONU should not 324 be shared. The solution provided by the [802.3ah] is to partition 325 the EPON link, in a virtual manner, between the ONUs. Each ONU has a 326 dedicated virtual link to the OLT. The [802.3ah] also defines an 327 additional link for broadcast transmission. The medium becomes an 328 aggregation of point-to-point tunnels. The OLT can not preserve its 329 EPON interface as a single interface connected to N devices 330 (following the properties of the physical interface). The EPON 331 interface of the OLT is partitioned into separate virtual interfaces, 332 an interface for each virtual link. Hence the OLT behaves like a 333 device with N virtual ports (and an additional port for the broadcast 334 transmission). The additional single-copy-broadcast channel (tagged 335 as all ones LLID) is added to allow the broadcast transmission within 336 a single copy to all ONUs, preserving the inherent advantage of BW 337 efficiency of the PON shared media. The ONUs filter the downlink 338 traffic which is not intended for their reception, according to the 339 virtual link marking. An LLID tag is attached at the preamble of the 340 Ethernet packet denoting the virtual link. The LLID marks the 341 destination port in the downstream and source port in the upstream. 343 The virtual links concept is also used to avoid a violation of the 344 [802.1d] bridging rules for peer to peer traffic in the PON. Peer to 345 peer traffic is traffic between ONUs in the same PON. The OLT can 346 not preserve the EPON interface as a single interface connected to N 347 devices and allow traffic between these devices without violating the 348 bridging rules. The source address and destination address of the 349 peer to peer traffic are behind the same port and therefore the 350 traffic should be discarded. The separation of the ONUs into virtual 351 links solves this issue. The OLT has N virtual ports for the single 352 physical EPON port. A bridge sees a single MAC Client for every link 353 pair. 355 The private paths concept solves the networking problems and it 356 provides subscriber isolation. 358 As the tunneling is only a virtual tunneling, there is a single 359 physical interface and a single physical layer for the device so that 360 some attributes are shared. For example, the interface has a single 361 local MAC address. 363 The virtual tunneling for an OLT with 3 ONUs, is illustrated in the 364 following diagram. 366 Trunk Line 367 | 368 | 369 | 370 \|/ 371 +===============================================+ 372 | 802.1D Bridge | 373 +===============================================+ 374 | MAC client1| ... |MAC client3| 375 +===============================================+ 376 | MP2PE | 377 +===============================================+ 378 | PHY | 379 ================================================= 380 | | | 381 | | | 382 \|/ \|/ \|/ 383 +============+ +============+ +============+ 384 | PHY | | PHY | | PHY | 385 +============+ +============+ +============+ 386 | MP2PE | | MP2PE | | MP2PE | 387 +============+ +============+ +============+ 388 | MAC client | | MAC client | | MAC client | 389 +============+ +============+ +============+ 390 | PHY | | PHY | | PHY | 391 +============+ +============+ +============+ 392 /|\ /|\ /|\ 393 | | | 394 | | | 395 | | | 396 Subscriber1 Subscriber2 Subscriber3 398 1.2.6. Principles of the MPCP 400 The EPON standard defines a media access control of an optical Access 401 network. The Access network has some substantial differences from 402 the legacy LAN which the Ethernet was designed for. The differences 403 mainly lie in the provisioning of the network. An Access network is 404 an administrated environment, with an operator providing the service 405 and subscribers consuming it. The operator is controlling the 406 network and managing its traffic. For instance BW is controlled and 407 subscribers are billed for services. The MPCP protocol divides the 408 Ethernet interfaces into two unequal types of network units. The 409 first interface is an OLT interface, which is a server unit, 410 controlling the network. The second interface is an ONU interface, 411 which is a client unit, participating in the network. 413 The OLT, which is the server unit, manages the network. The MPCP 414 controls the TDM transmission of the uplink. The MPCP is implemented 415 at the MAC control layer and the MPCP messages are MAC control 416 messages using the 0x8808 Ethertype. These messages are not 417 forwarded out of the MAC. 419 A concept of time must exist in the protocol in order to schedule the 420 uplink transmission. A timestamp which is set by the OLT and 421 synchronized between the network units is passed through the MPCP 422 messages. The timestamp is also used to measure the RTT of each ONU. 423 RTT is compensated by the OLT, in the generation of the grants for 424 the uplink transmission. The difference of incoming timestamp to 425 local time allows the OLT to calculate the RTT. RTT compensation is 426 needed as the RTT in an Access network can have a significant value. 427 The standard allows the network to reach a 20km distance which is 428 equivalent to a 200usec RTT (25Kbytes of data). 430 The TDM control is done using the GATE messages. These messages 431 define, for each ONU, the time for transmission and the length of 432 transmission. The RTT is reduced from the transmission time in the 433 GATE message to shift the transmission time of the ONU in the 434 opposite direction. 436 A scheduling algorithm at the OLT, which is not defined in the 437 [802.3ah], is responsible for dividing the BW and controlling the 438 transmission delay of each ONU according to its SLA. The MPCP 439 defines a closed loop operation, in order for this algorithm to be 440 efficient. The MPCP allows the ONUs to report on the amount of BW 441 they require for transmission using a special REPORT message. This 442 allows allocating BW to an ONU only when requested, relying on the 443 statistical burst property of the traffic, allowing different peak BW 444 for different ONUs at different times, hence allowing 445 oversubscription of the BW. The REPORT message reports the amount of 446 data waiting in the ONU queues. 448 In addition to that the MPCP defines a protocol of auto-discovery and 449 registration of ONUs. 451 The registration process is defined in the diagram below: 453 OLT ONU 454 | | 455 | Discovery Gate message \| 456 |--------------------------------------------| 457 | /| 458 | | 459 |/ Register Request message | 460 |--------------------------------------------| 461 |\ | 462 | | 463 | Register message | 464 | (assigning LLID) \| 465 |--------------------------------------------| 466 | /| 467 | | 468 | Gate message \| 469 |--------------------------------------------| 470 | /| 471 | | 472 |/ Register ACK message | 473 |--------------------------------------------| 474 |\ | 475 | | 476 | | 478 A new ONU requests to register (sends a REG_REQUEST message) in a 479 special discovery grant, allocated for that by the OLT. During that 480 time more than one ONU might try to register. A collision in 481 transmission might occur as the RTT of the new ONUs is not yet known. 482 A random backoff mechanism of the transmission is used to schedule 483 the following registration requests to avoid these collisions. When 484 the OLT receives REG_REQUEST message of an ONU and approves this ONU 485 then it sends a REGISTER message to this ONU defining its LLID. From 486 that point the ONU transmission is scheduled by its LLID, knowing the 487 RTT, and no collision can occur. The ONU replies with a REGISTER_ACK 488 message and the registration process of the MPCP ends. Higher layer 489 protocols may yet be needed to authenticate the ONU and allow it to 490 participate in the network. 492 1.2.7. Forward Error correction (FEC) 494 The FEC is defined to enhance the link budget of the PON. As each 495 splitter attenuates the optical signal, the number of the splits and 496 the distance are limited by the link budget. Hence an FEC which 497 improves the link budget, has a benefit. The FEC code used is the 498 RS(239,255,8), similar to the FEC code in [ITU-T G.975], improving 499 the BER from 1E-4 to 1E-12. 501 The FEC parity encapsulation is based on the framing of the Ethernet 502 packet. The Ethernet packets are spaced by MAC rate adaptation, and 503 the parity bytes are inserted after the packet, in the provided 504 space. 506 As the start and end of packet codewords define also the FEC 507 boundaries, and they are outside the FEC protection, they are 508 replaced by a series of symbols to reduce their vulnerability to 509 errors. 511 The following diagram presents an FEC protected frame: 513 +-------------------------------------------------------------------+ 514 | | | | | | | | 515 | S_FEC | Preamble/SFD | Frame | FCS | T_FEC | Parity | T_FEC | 516 | | | | | | | | 517 +-------------------------------------------------------------------+ 519 The FEC is added in a separate layer between the PCS and PMA layers 520 of the [802.3]. 522 The FEC layer introduces a fixed delay in receive path and transmit 523 path. 525 The FEC layer is optional. 527 1.3. Management architecture 529 Each one of the EPON layers is accompanied with a management 530 interface, which is controlled through clause 30 of the [802.3ah]. 531 As the [802.3ah] spec may be used for different applications and some 532 of the clauses may be used separately, the IEEE management clause 533 allocates for each one of them a separate package. The MIB document 534 follows this partition. 536 The following diagram presents the relation of the MIB groups to the 537 [802.3ah] layers: 539 +===========================+ 540 | Higher layers | 541 +===========================+ 542 | 802.1D Bridge | 543 +===========================+ 544 |MAC client| ... |MAC client| 545 +===========================+ \ +=============================+ 546 | MAC Control - (MPCP) |----- |MpcpObjects| ... |MpcpObjects| 547 +===========================+ / +=============================+ 548 | MAC | ... | MAC | 549 +===========================+ \ +=============================+ 550 | P2P Emulation (P2PE) |----- |OmpEmulat | |OmpEmulat | 551 +===========================+ / |ionObjects | ... |ionObjects | 552 | | +=============================+ 553 | GMII | 554 | | 555 +===========================+ 556 | PCS | 557 +===========================+ \ +=============================+ 558 | FEC |----- |FecObjects | ... |FecObjects | 559 +===========================+ / +=============================+ 560 | PMA | 561 +===========================+ 562 | PMD | 563 +===========================+ 564 | | 565 | MDI | 566 | | 567 /===============/ 568 / Media / 569 /===============/ 571 The association is strait forward for the ONU interface. There is 572 one logical and one physical interface and a single copy exists for 573 each layer, that can be remotely queried by the OLT. 575 At the OLT there is a single physical interface and N virtual 576 interfaces for the virtual links of the ONUs (and another virtual 577 interface for the broadcast virtual link). As can be seen from the 578 layering diagram above, the MAC layer is virtually duplicated. 580 Therefore in this document it was selected that the management of a 581 virtual interface is like a physical interface and an interface index 582 is allocated for each one of the virtual links and an additional 583 interface index is allocated for the OLT. 585 To illustrate the interface modeling, consider two devices. The 586 first device has two physical interfaces, is typically located at a 587 consumer's site, and called an "ONU modem". 589 An "ONU modem" is shown in the figure below: 591 -------- 592 ONU interface | ONU | 10megabit interface 593 --------------| modem |-------------------- 594 --------- 596 This device would have 3 entries in the IF table, and one IF stack 597 entry, for example: 599 ifIndex=1 - interface for 10megabit interface 601 ifIndex=2 - interface for the optical interface 603 ifIndex=200 - interface for the ONU interface 605 And then in IF stack table: 607 ifStackHigherLayer=200, ifStackLowerLayer=2 - map between the 608 physical and the ONU 610 The second device has three physical interfaces, is typically located 611 at the provider's site, and may be called a "headend". 613 A "headend" is shown in the figure below: 615 --------- 616 1st OLT interface | Head | gigE interface 617 ------------------| end |-------------------- 618 | | 619 ------------------| | 620 2nd OLT interface | | 621 --------- 623 This device would have 5 entries (when no attached ONUs) in the IF 624 table, for example: 626 ifIndex=1 - interface for gigE interface 628 ifIndex=2 - interface for 1st optical interface 630 ifIndex=3 - interface for 2nd optical interface 632 ifIndex=265535 - interface for the 1st OLT broadcast interface 634 ifIndex=365535 - interface for the 2nd OLT broadcast interface 636 And then in IF stack table: 638 ifStackHigherLayer=265535, ifStackLowerLayer=2 - map between the 1st 639 physical and its broadcast interface 641 ifStackHigherLayer=365535, ifStackLowerLayer=3 - map between the 2nd 642 physical and its broadcast interface 644 If two ONUs connected to the first OLT interface, then for example, 645 the following entries would be added to the IF table: 647 ifIndex=200001 - interface for the 1st ONU of 1st OLT 649 ifIndex=200002 - interface for the 2nd ONU of 1st OLT 651 And in the IF stack table: 653 ifStackHigherLayer=200001, ifStackLowerLayer=2 - map between the 1st 654 physical and 1st ONU 656 ifStackHigherLayer=200002, ifStackLowerLayer=2 - map between the 1st 657 physical and 2nd ONU 659 For each physical interface, there would be an entry (ifIndex) in the 660 tables of the interface MIB module [RFC2863], MAU MIB module 661 [RFC3636] and Etherlike MIB module [RFC3635]. Additionally, there 662 would be entries (ifIndexes) for the virtual interfaces of the OLT 663 interface. The justification for the additional allocation of 664 indexes is that the virtual interfaces are quite well distinguished 665 as they connect different physical ONUs, from the OLT side. For 666 instance there is a meaning for separate bad frames counter or bad 667 octets counter for each virtual link, as the ONUs can be differently 668 distanced. This is quite similar to a case of separate physical 669 interfaces. 671 The same partition concept exists for the MIB module of this 672 document. Each row in the tables is indexed according to the ifIndex 673 and specifically there is a row for each virtual link. There are 674 some control objects which are shared and are the same for the 675 virtual interfaces (and they should have the same value for each 676 ifIndex) but most of the objects have different values for N+1 677 logical interfaces at the OLT. This is done for each MIB group. It 678 is a bit different from the [802.3ah] layering diagram which presents 679 the P2MP layer as a single layer while duplicating the MAC and MAC 680 client layers (Please see the diagram above). However from 681 management perspective it is more convenient and neat to partition 682 the management of the layers for the virtual links, as the atomic 683 managed entity is the virtual link. It is also convenient to use the 684 interface index of the virtual link for that purpose, as it is 685 already used to index the rows of the virtual links at the Interface, 686 MAU and etherLike interfaces MIBs. 688 2. MIB structure 690 This document defines the DOT3 EPON MIB module. The DOT3 EPON MIB 691 module defines the objects used for management of the [802.3ah] Point 692 to Multipoint (P2MP) interfaces. These MIB objects are included in 693 four groups. 695 i) The Multi-Point Control Protocol (MPCP) MIB objects - MIB objects 696 related to [802.3ah] clause 64 Multi Point Control Protocol 697 attributes. The following tables are presented in this group: 699 The dot3MpcpControlTable defines the objects used for the 700 configuration and status indication, which are per logical link, of 701 MPCP compliant interfaces. 703 The dot3MpcpStatTable defines the statistics objects, which are per 704 logical link, of MPCP compliant interfaces. 706 The operational mode of an OLT/ONU for the tables is defined by the 707 dot3MpcpMode object in the dot3MpcpControlTable. 709 ii) The OMPEmulation MIB objects - MIB objects related to [802.3ah] 710 clause 65 point to point emulation attributes. The following tables 711 are presented in this group: 713 The dot3OmpEmulationTable defines the objects used for the 714 configuration and status indication, which are per logical link, of 715 OMPEmulation compliant interfaces. 717 The dot3OmpEmulationStatTable defines the statistics objects which 718 are per logical link, of OMPEmulation compliant interfaces. 720 The operational mode of an OLT/ONU for the tables is defined by the 721 dot3OmpEmulationType object in the dot3OmpEmulationTable. 723 iii) The FEC MIB objects - MIB objects related to [802.3ah] clause 60 724 and clause 65 EPON FEC attributes. The following table is presented 725 in this group: 727 The dot3EponFecTable defines the objects used for the configuration 728 and status indication, which are per logical link, of FEC EPON 729 compliant interfaces. 731 iv) The EPON extended package MIB objects - MIB objects used for 732 configuration and status indication with extended capabilities of the 733 EPON interfaces. The following tables are presented in this group: 735 The dot3ExtPkgControlTable defines the objects which are per logical 736 link, used for the configuration and status indication of EPON 737 compliant interfaces. 739 The dot3ExtPkgQueueTable defines the objects which are per logical 740 link, and per queue, used for the configuration and status indication 741 of the ONU queues reported in the MPCP REPORT message, of EPON 742 compliant interfaces. 744 The dot3ExtPkgQueueSetsTable defines the objects which are per 745 logical link, per queue, and per queue_set, used for the 746 configuration and status indication of the ONU queue_sets reported in 747 the MPCP REPORT message, of EPON compliant interfaces. 749 The dot3ExtPkgOptIfTable defines the objects which are per logical 750 link, used for the control and status indication of the optical 751 interface of EPON compliant interfaces. 753 As described in the architecture section, each row in the tables is 754 indexed according to the ifIndex, and specifically there is a row for 755 each virtual link. There are a few control objects which are shared 756 and have the same value for the virtual interfaces (and they should 757 have the same value for each ifIndex) but most of the objects have 758 different values for N+1 logical interfaces at the OLT. This is done 759 for each MIB group. It is a bit different from the [802.3ah] 760 layering diagram which presents the P2MP layer as a single layer 761 while duplicating the MAC and MAC client layers. However from 762 management perspective it is more convenient and neat to partition 763 the management of the layers for the virtual links, as the atomic 764 managed entity is the virtual link. It is also convenient to use the 765 interface index of the virtual link for that purpose, as it is 766 already used to index the rows of the virtual links at the Interface, 767 MAU and etherLike interfaces MIBs. 769 For example provided below the values of the MPCP control table of an 770 OLT with 3 registered ONUs: 772 The table below presents the MPCP control table of ONU1 in working 773 mode. A single row exists in the table. 775 +---------------------------+-----------------+ 776 | MPCP control MIB object | Value | 777 +---------------------------+-----------------+ 778 | ifIndex | 100 | 779 | | | 780 | dot3MpcpOperStatus | true | 781 | | | 782 | dot3MpcpAdminState | true | 783 | | | 784 | dot3MpcpMode | onu | 785 | | | 786 | dot3MpcpSyncTime | 25 | 787 | | | 788 | dot3MpcpLinkID | 1 | 789 | | | 790 | dot3MpcpRemoteMACAddress | OLT_MAC_Address | 791 | | | 792 | dot3MpcpRegistrationState | registered | 793 | | | 794 | dot3MpcpTransmitElapsed | 10 | 795 | | | 796 | dot3MpcpReceiveElapsed | 10 | 797 | | | 798 | dot3MpcpRoundTripTime | 100 | 799 +---------------------------+-----------------+ 801 Table 1 803 OLT_MAC_Address is the MAC address of the OLT EPON interface. 805 The creation of the rows of the ONU interface is done at 806 initialization. 808 For example, provided below are the values for the MPCP control table 809 of the ONU, after initialization, before registration. 811 The table below presents the MPCP control table of ONU1 after 812 initialization. A single row exists in the table. 814 +---------------------------+-------------------+ 815 | MPCP control MIB object | Value | 816 +---------------------------+-------------------+ 817 | ifIndex | 100 | 818 | | | 819 | dot3MpcpOperStatus | true | 820 | | | 821 | dot3MpcpAdminState | true | 822 | | | 823 | dot3MpcpMode | onu | 824 | | | 825 | dot3MpcpSyncTime | 0 | 826 | | | 827 | dot3MpcpLinkID | 0 | 828 | | | 829 | dot3MpcpRemoteMACAddress | 00:00:00:00:00:00 | 830 | | | 831 | dot3MpcpRegistrationState | unregistered | 832 | | | 833 | dot3MpcpTransmitElapsed | 0 | 834 | | | 835 | dot3MpcpReceiveElapsed | 0 | 836 | | | 837 | dot3MpcpRoundTripTime | 0 | 838 +---------------------------+-------------------+ 840 Table 2 842 The table below presents the MPCP control table of the OLT in working 843 mode. Four rows exist in the table associated with the virtual 844 links. 846 +----------------+-----------+------------+------------+------------+ 847 | MPCP control | Value | Value | Value | Value | 848 | MIB object | | | | | 849 +----------------+-----------+------------+------------+------------+ 850 | ifIndex | 100001 | 100002 | 100003 | 165535 | 851 | | | | | | 852 | dot3MpcpOperSt | true | true | true | true | 853 | atus | | | | | 854 | | | | | | 855 | dot3MpcpAdminS | true | true | true | true | 856 | tate | | | | | 857 | | | | | | 858 | dot3MpcpMode | olt | olt | olt | olt | 859 | | | | | | 860 | dot3MpcpSyncTi | 25 | 25 | 25 | 25 | 861 | me | | | | | 862 | | | | | | 863 | dot3MpcpLinkID | 1 | 2 | 3 | 65535 | 864 | | | | | | 865 | dot3MpcpRemote | ONU1_MAC_ | ONU2_MAC_A | ONU3_MAC_A | BRCT_MAC_A | 866 | MACAddress | Address | ddress | ddress | ddress | 867 | | | | | | 868 | dot3MpcpRegist | registere | registered | registered | registered | 869 | rationState | d | | | | 870 | | | | | | 871 | dot3MpcpTransm | 10 | 10 | 10 | 10 | 872 | itElapsed | | | | | 873 | | | | | | 874 | dot3MpcpReceiv | 10 | 10 | 10 | 10 | 875 | eElapsed | | | | | 876 | | | | | | 877 | dot3MpcpRoundT | 100 | 60 | 20 | 0 | 878 | ripTime | | | | | 879 +----------------+-----------+------------+------------+------------+ 881 Table 3 883 ONU1_MAC_Address is the MAC address of ONU1 EPON interface. 885 ONU2_MAC_Address is the MAC address of ONU2 EPON interface. 887 ONU3_MAC_Address is the MAC address of ONU3 EPON interface. 889 BRCT_MAC_Address is the MAC address of the broadcast EPON interface, 890 which is the OLT MAC address. 892 The creation of the rows of the OLT interface and the broadcast 893 virtual interface is done at initialization. 895 The creation of rows of the virtual interfaces at the OLT is done 896 when the link is established (ONU registers) and the deletion is done 897 when the link is deleted (ONU deregisters). 899 For example, provided below are the values of the MPCP control table 900 of the OLT after initialization, before the ONUs register. 902 The table below presents the MPCP control table of the OLT after 903 initialization. A single row exists in this table associated with 904 the virtual broadcast link. 906 +---------------------------+------------------+ 907 | MPCP control MIB object | Value | 908 +---------------------------+------------------+ 909 | ifIndex | 165535 | 910 | | | 911 | dot3MpcpOperStatus | true | 912 | | | 913 | dot3MpcpAdminState | true | 914 | | | 915 | dot3MpcpMode | olt | 916 | | | 917 | dot3MpcpSyncTime | 25 | 918 | | | 919 | dot3MpcpLinkID | 65535 | 920 | | | 921 | dot3MpcpRemoteMACAddress | BRCT_MAC_Address | 922 | | | 923 | dot3MpcpRegistrationState | registered | 924 | | | 925 | dot3MpcpTransmitElapsed | 10 | 926 | | | 927 | dot3MpcpReceiveElapsed | 100000 | 928 | | | 929 | dot3MpcpRoundTripTime | 0 | 930 +---------------------------+------------------+ 932 Table 4 934 BRCT_MAC_Address is the MAC address of the broadcast EPON interface, 935 which is the OLT MAC address. 937 3. Relation to other MIB Modules 939 3.1. Relation to the Interfaces MIB and Ethernet-like Interfaces MIB 941 EPON interface is a kind of Ether-like interface. This MIB module 942 extends the objects of the Interface MIB and the Ether-like 943 interfaces MIB for an EPON type interface. 945 Implementing this module therefore MUST require implementation of the 946 Interfaces MIB module [RFC2863] and the Ethernet-like Interfaces MIB 947 module [RFC3635]. 949 Thus, each managed EPON interface would have a corresponding entry in 950 the mandatory tables of the Ether-like MIB module found in [RFC3635], 951 and likewise in the tables of the Interface MIB module found in 952 [RFC2863]. Also each managed virtual EPON interface would have a 953 corresponding entry in the mandatory tables of the Ether-like MIB 954 module found in [RFC3635], and likewise in the tables of the 955 Interface MIB module found in [RFC2863] with a dedicated ifIndex for 956 this interface. 958 In this document there is no replication of the objects from these 959 MIBs, so for instance the document is defining 960 dot3MpcpRemoteMACAddress only while assuming the local MAC address 961 object is already defined in [RFC3635]. 963 The interface MIB module [RFC2863] defines the interface index 964 (ifIndex). Interface Index, as specified in [RFC2863] is used in 965 this MIB Module as an index to the EPON MIB tables. The ifIndex is 966 used to denote the physical interface and the virtual link interfaces 967 at the OLT. The OLT interface and the virtual link interfaces are 968 stacked using the ifStack table defined in [RFC2863], and the 969 ifInvStack defined in [RFC2864]. The OLT interface is the lower 970 layer of all other interfaces associated with the virtual links. 972 This document defines the specific EPON objects of an ONU interface 973 and an OLT interface. Information in the tables is per LLID. The 974 rows in the EPON MIB tables, referring to the LLIDs are denoted with 975 the corresponding ifIndexes of the virtual link interfaces. 977 Please note that each virtual interface does not have a different 978 physical MAC address at the OLT as the physical interface is the 979 same. It is specified in the [802.3ah] section 64.1.2. The 980 corresponding object of the Ether-like interface MIB is duplicated 981 for all the virtual interfaces. 983 For example the values of the Interface MIB objects are presented in 984 the following tables, for an OLT with 3 registered ONUs: 986 The table below presents the objects of the Interface MIB of an ONU 987 in working mode. 989 +----------------------+--------------------------------+ 990 | Interface MIB object | Value | 991 +----------------------+--------------------------------+ 992 | ifIndex | 1 | 993 | | | 994 | ifDescr | "interface description" | 995 | | | 996 | ifType | ethernetCsmacd (6) 1000base-Px | 997 | | | 998 | ifMtu | MTU size (1522) | 999 | | | 1000 | ifSpeed | 1000000000 | 1001 | | | 1002 | ifPhysAddress | ONU_MAC_Address | 1003 | | | 1004 | ifAdminStatus | up | 1005 | | | 1006 | ifOperStatus | Up | 1007 | | | 1008 | ifLastChange | ONUup_time | 1009 | | | 1010 | ifInOctets | ONU_octets_number | 1011 | | | 1012 | ifInUcastPkts | ONU_unicast_frame_number | 1013 | | | 1014 | ifInNUcastPkts | ONU_non_unicast_frame_number | 1015 | | | 1016 | ifInDiscards | ONU_discard_frame_number | 1017 | | | 1018 | ifInErrors | ONU_error_frame_number | 1019 | | | 1020 | ifInUnknownProtos | ONU_unknown_frame_number | 1021 | | | 1022 | ifOutOctets | ONU_octets_number | 1023 | | | 1024 | ifOutUcastPkts | ONU_unicast_frame_number | 1025 | | | 1026 | ifOutNUcastPkts | ONU_non_unicast_frame_number | 1027 | | | 1028 | ifOutDiscards | ONU_discard_frame_number | 1029 | | | 1030 | ifOutErrors | ONU_error_frame_number | 1031 | | | 1032 | ifOutQLen | ONU_queue_frame_number | 1033 +----------------------+--------------------------------+ 1035 Table 5 1037 ONU_MAC_Address is the MAC address of the ONU EPON interface. 1039 The table below presents the objects of the Interface MIB of the ONU 1040 interface. 1042 +----------------------+--------------------------------+ 1043 | Interface MIB object | Value | 1044 +----------------------+--------------------------------+ 1045 | ifIndex | 100 | 1046 | | | 1047 | ifDescr | "interface description" | 1048 | | | 1049 | ifType | ethernetCsmacd (6) 1000base-Px | 1050 | | | 1051 | ifMtu | MTU size (1522) | 1052 | | | 1053 | ifSpeed | 1000000000 | 1054 | | | 1055 | ifPhysAddress | ONU_MAC_Address | 1056 | | | 1057 | ifAdminStatus | up | 1058 | | | 1059 | ifOperStatus | Up | 1060 | | | 1061 | ifLastChange | up_time | 1062 | | | 1063 | ifInOctets | ONU1_octets_number | 1064 | | | 1065 | ifInUcastPkts | ONU1_unicast_frame_number | 1066 | | | 1067 | ifInNUcastPkts | ONU1_non_unicast_frame_number | 1068 | | | 1069 | ifInDiscards | ONU1_discard_frame_number | 1070 | | | 1071 | ifInErrors | ONU1_error_frame_number | 1072 | | | 1073 | ifInUnknownProtos | ONU1_unknown_frame_number | 1074 | | | 1075 | ifOutOctets | ONU1_octets_number | 1076 | | | 1077 | ifOutUcastPkts | ONU1_unicast_frame_number | 1078 | | | 1079 | ifOutNUcastPkts | ONU1_non_unicast_frame_number | 1080 | ifOutDiscards | ONU1_discard_frame_number | 1081 | | | 1082 | ifOutErrors | ONU1_error_frame_number | 1083 | | | 1084 | ifOutQLen | ONU1_queue_frame_number | 1085 +----------------------+--------------------------------+ 1087 Table 6 1089 ONU_MAC_Address is the MAC address of the ONU EPON interface. 1091 The following values will be set in the ifStack and ifInvStack tables 1092 related to this example. 1094 ifStackTable: 1096 ifStackHigherLayer=100, ifStackLowerLayer=1 - map between the 1097 physical interface and the ONU 1099 ifInvStackTable: 1101 ifStackLowerLayer=1, ifStackHigherLayer=100,- map between the ONU and 1102 the physical interface 1104 The table below presents the Interface MIB objects of an OLT 1105 interface. 1107 +----------------------+--------------------------------+ 1108 | Interface MIB object | Value | 1109 +----------------------+--------------------------------+ 1110 | ifIndex | 2 | 1111 | | | 1112 | ifDescr | "interface description" | 1113 | | | 1114 | ifType | ethernetCsmacd (6) 1000base-Px | 1115 | | | 1116 | ifMtu | MTU size (1522) | 1117 | | | 1118 | ifSpeed | 1000000000 | 1119 | | | 1120 | ifPhysAddress | OLT_MAC_Address | 1121 | | | 1122 | ifAdminStatus | up | 1123 | | | 1124 | ifOperStatus | Up | 1125 | | | 1126 | ifLastChange | OLTup_time | 1127 | | | 1128 | ifInOctets | OLT_octets_number | 1129 | | | 1130 | ifInUcastPkts | OLT_unicast_frame_number | 1131 | | | 1132 | ifInNUcastPkts | OLT_non_unicast_frame_number | 1133 | | | 1134 | ifInDiscards | OLT_discard_frame_number | 1135 | | | 1136 | ifInErrors | OLT_error_frame_number | 1137 | | | 1138 | ifInUnknownProtos | OLT_unknown_frame_number | 1139 | | | 1140 | ifOutOctets | OLT_octets_number | 1141 | | | 1142 | ifOutUcastPkts | OLT_unicast_frame_number | 1143 | | | 1144 | ifOutNUcastPkts | OLT_non_unicast_frame_number | 1145 | | | 1146 | ifOutDiscards | OLT_discard_frame_number | 1147 | | | 1148 | ifOutErrors | OLT_error_frame_number | 1149 | | | 1150 | ifOutQLen | OLT_queue_frame_number | 1151 +----------------------+--------------------------------+ 1153 Table 7 1155 OLT_MAC_Address is the MAC address of the OLT EPON interface. 1157 The table below presents the Interface MIB objects of an OLT 1158 interface, associated with the virtual link interfaces. 1160 +----------+-------------+-------------+-------------+--------------+ 1161 | Interfac | Value | Value | Value | Value | 1162 | eMIB | | | | | 1163 | object | | | | | 1164 +----------+-------------+-------------+-------------+--------------+ 1165 | ifIndex | 200001 | 200002 | 200003 | 265535 | 1166 | | | | | | 1167 | ifDescr | "interface | "interface | "interface | "interface | 1168 | | description | description | description | description" | 1169 | | " | " | " | | 1170 | | | | | | 1171 | ifType | ethernetCsm | ethernetCsm | ethernetCsm | ethernetCsma | 1172 | | acd (6) | acd (6) | acd (6) | cd (6) | 1173 | | | | | | 1174 | ifMtu | MTUsize(152 | MTUsize(152 | MTUsize(152 | MTUsize(1522 | 1175 | | 2) | 2) | 2) | ) | 1176 | ifSpeed | 1000000000 | 1000000000 | 1000000000 | 1000000000 | 1177 | | | | | | 1178 | ifPhysAd | OLT_MAC_Add | OLT_MAC_Add | OLT_MAC_Add | OLT_MAC_Addr | 1179 | dress | ress | ress | ress | ess | 1180 | | | | | | 1181 | ifAdminS | up | up | up | up | 1182 | tatus | | | | | 1183 | | | | | | 1184 | ifOperSt | Up | Up | Up | Up | 1185 | atus | | | | | 1186 | | | | | | 1187 | ifLastCh | ONU1_up_tim | ONU2_up_tim | ONU3_up_tim | up_time | 1188 | ange | e | e | e | | 1189 | | | | | | 1190 | ifInOcte | ONU1_octets | ONU2_octets | ONU3_octets | BRCT_octets_ | 1191 | ts | _number | _number | _number | number | 1192 | | | | | | 1193 | ifInUcas | ONU1_unic_f | ONU2_unic_f | ONU3_unic_f | BRCT_unic_fr | 1194 | tPkts | rame_num | rame_num | rame_num | ame_num | 1195 | | | | | | 1196 | ifInNUca | ONU1_non_un | ONU2_non_un | ONU3_non_un | BRCT_non_uni | 1197 | stPkts | ic_frame_nu | ic_frame_nu | ic_frame_nu | c_frame_num | 1198 | | m | m | m | | 1199 | | | | | | 1200 | ifInDisc | ONU1_disc_f | ONU2_disc_f | ONU3_disc_f | BRCT_disc_fr | 1201 | ards | rame_num | rame_num | rame_num | ame_numr | 1202 | | | | | | 1203 | ifInErro | ONU1_err_fr | ONU2_err_fr | ONU3_err_fr | BRCT_err_fra | 1204 | rs | ame_num | ame_num | ame_num | me_num | 1205 | | | | | | 1206 | ifInUnkn | ONU1_unknw_ | ONU2_unknw_ | ONU3_unknw_ | BRCT_unknw_f | 1207 | ownProto | frame_num | frame_num | frame_num | rame_num | 1208 | s | | | | | 1209 | | | | | | 1210 | ifOutOct | ONU1_octets | ONU2_octets | ONU3_octets | BRCT_octets_ | 1211 | ets | _number | _number | _number | number | 1212 | | | | | | 1213 | ifOutUca | ONU1_unic_f | ONU2_unic_f | ONU3_unic_f | BRCT_unic_fr | 1214 | stPkts | rame_num | rame_num | rame_num | ame_num | 1215 | | | | | | 1216 | ifOutNUc | ONU1_non_un | ONU2_non_un | ONU3_non_un | BRCT_non_uni | 1217 | astPkts | ic_frame_nu | ic_frame_nu | ic_frame_nu | c_frame_num | 1218 | | m | m | m | | 1219 | | | | | | 1220 | ifOutDis | ONU1_disc_f | ONU2_disc_f | ONU3_disc_f | BRCT_disc_fr | 1221 | cards | rame_num | rame_num | rame_num | ame_num | 1222 | | | | | | 1223 | ifOutErr | ONU1_err_fr | ONU2_err_fr | ONU3_err_fr | BRCT_err_fra | 1224 | ors | ame_num | ame_num | ame_num | me_num | 1225 | | | | | | 1226 | ifOutQLe | ONU1_queue_ | ONU2_queue_ | ONU3_queue_ | BRCt_queue_f | 1227 | n | frame_num | frame_num | frame_num | rame_num | 1228 +----------+-------------+-------------+-------------+--------------+ 1230 Table 8 1232 OLT_MAC_Address is the MAC address of the OLT EPON interface. 1234 The following values will be set in the ifStack and ifInvStack tables 1235 related to this example: 1237 ifStackTable: 1239 ifStackHigherLayer=265535, ifStackLowerLayer=2 - map between the OLT 1240 physical interface and its broadcast virtual interface 1242 ifStackHigherLayer=200001, ifStackLowerLayer=2 - map between the OLT 1243 physical interface and its virtual interface of the 1st ONU 1245 ifStackHigherLayer=200002, ifStackLowerLayer=2 - map between the OLT 1246 physical interface and its virtual interface of the 2nd ONU 1248 ifStackHigherLayer=200003, ifStackLowerLayer=2 - map between the OLT 1249 physical interface and its virtual interface of the 3rd ONU 1251 ifInvStackTable: 1253 ifStackLowerLayer=2, ifStackHigherLayer=265535, - map between the 1254 broadcast interface of the OLT and the OLT physical interface 1256 ifStackLowerLayer=2, ifStackHigherLayer=200001 - map between the OLT 1257 virtual interface of the 1st ONU and the OLT physical interface 1259 ifStackLowerLayer=2, ifStackHigherLayer=200002 - map between the OLT 1260 virtual interface of the 2nd ONU and the OLT physical interface 1262 ifStackLowerLayer=2, ifStackHigherLayer=200003 - map between the OLT 1263 virtual interface of the 3rd ONU and the OLT physical interface 1265 The rows for the ONU interface, for the OLT interface and for the OLT 1266 broadcast interface are created in initialization. 1268 The creation of a row for a virtual link is done when the virtual 1269 link is established (ONU registers) and deletion is done when the 1270 virtual link is deleted (ONU deregisters). 1272 The EPON MIB module also extends the Interface MIB module with a set 1273 of counters, which are specific for the EPON interface. The EPON MIB 1274 module implements the same handling of the counters when the 1275 operation of the interface starts or stops. The interface MIB 1276 document describes the possible behavior of counters when an 1277 interface is re-initialized using the ifCounterDiscontinuityTime 1278 indicator, indicating the discontinuity of the counters. Please see 1279 [RFC2863] section 3.1.5 p.11 for more information. The counters of 1280 the EPON MIB should be handled in a similar manner. 1282 3.2. Relation to the IEEE 802.3 MAU MIBs 1284 The MAU types of the EPON Interface are defined in the amended MAU 1285 MIB document. This document assumes the implementation of the MAU 1286 MIB for this purpose and does not repeat the EPON MAU types. 1287 Therefore implementing this module MUST require implementation of the 1288 MAU-MIB module [RFC3636bis-03]. 1290 The handling of the ifMAU tables for the EPON case is similar to the 1291 handling described in the former section for the Interface and Ether- 1292 like interface MIBs. A single row exists for the ONU in the 1293 ifMauTable. A row for each virtual link (N+1 rows) exists at the 1294 OLT, with a separate value of ifMauIfIndex for each virtual link. 1296 As specified above the rows for the ONU interface, for the OLT 1297 interface and for the OLT broadcast interface are created in 1298 initialization. 1300 The creation of a row for a virtual link is done when the virtual 1301 link is established (ONU registers) and deletion is done when the 1302 virtual link is deleted (ONU deregisters). 1304 3.3. Relation to the EFM OAM MIB 1306 The EPON interfaces are aimed to the optical access networks and most 1307 probably will be accompanied with the implementation of the OAM 1308 section of the [802.3ah]. Therefore the EFM OAM MIB module 1309 [I-D.ietf-hubmib-efm-mib] MAY be implemented, when this MIB module is 1310 implemented, defining managed objects for the OAM layer that are 1311 complementary to the EFM EPON MIB module. As the OAM is defined for 1312 a point to point link it is implemented in this case, using the 1313 virtual links which are defined for the P2MP network, so that an 1314 instance is held for each Logical link (LLID) of the EPON. The 1315 corresponding ifIndex of the virtual link is used as the ifIndex of 1316 the tables of the OAM MIB module, for this purpose. 1318 3.4. Relation to the bridge MIB 1320 It is very probable that an EPON OLT will implement a bridging 1321 functionality above the EPON interface layer, bridging between the 1322 EPON users and the network. Bridge functionality is specified at 1323 [802.1d]. In this scenario the virtual ports of the EPON are 1324 corresponding to the virtual bridge ports. There is a direct mapping 1325 between the bridge ports and the LLIDs, which are virtual EPON 1326 channels. 1328 Therefore the bridge MIB modules [RFC4188], [RFC1525] MAY be 1329 implemented when the EFM EPON MIB module is implemented for an EPON 1330 OLT, defining managed objects for the bridge layer. 1332 The values of dot1dBasePortIfIndex would correspond to the ifIndex of 1333 the virtual port (1 for LLID1, 2 for LLID2,...) 1335 The broadcast virtual EPON interface of the OLT has no direct mapping 1336 to a virtual bridge port as it is not port specific but used for 1337 broadcast traffic. 1339 4. Mapping of IEEE 802.3ah Managed Objects 1341 This section contains the mapping between the managed objects defined 1342 in this document and the attributes defined in [802.3ah] Clause 30. 1343 The tables are divided to the relevant groups. 1345 oMPCP managed object class (30.3.5) 1347 +----------------------------+-------------------------+------------+ 1348 | dot3EPON MIB module object | IEEE802.3ah attribute | Reference | 1349 +----------------------------+-------------------------+------------+ 1350 | ifIndex | aMPCPID | 30.3.5.1.1 | 1351 | | | | 1352 | dot3MpcpOperStatus | aMPCPAdminState | 30.3.5.1.2 | 1353 | | | | 1354 | dot3MpcpMode | aMPCPMode | 30.3.5.1.3 | 1355 | | | | 1356 | dot3MpcpLinkID | aMPCPLinkID | 30.3.5.1.4 | 1357 | | | | 1358 | dot3MpcpRemoteMACAddress | aMPCPRemoteMACAddress | 30.3.5.1.5 | 1359 | | | | 1360 | dot3MpcpRegistrationState | aMPCPRegistrationState | 30.3.5.1.6 | 1361 | | | | 1362 | dot3MpcpMACCtrlFramesTrans | aMPCPMACCtrlFramesTrans | 30.3.5.1.7 | 1363 | mitted | mitted | | 1364 | | | | 1365 | dot3MpcpMACCtrlFramesRecei | aMPCPMACCtrlFramesRecei | 30.3.5.1.8 | 1366 | ved | ved | | 1367 | | | | 1368 | dot3MpcpTxGate | aMPCPTxGate | 30.3.5.1.9 | 1369 | | | | 1370 | dot3MpcpTxRegAck | aMPCPTxRegAck | 30.3.5.1.1 | 1371 | | | 0 | 1372 | | | | 1373 | dot3MpcpTxRegister | aMPCPTxRegister | 30.3.5.1.1 | 1374 | | | 1 | 1375 | | | | 1376 | dot3MpcpTxRegRequest | aMPCPTxRegRequest | 30.3.5.1.1 | 1377 | | | 2 | 1378 | | | | 1379 | dot3MpcpTxReport | aMPCPTxReport | 30.3.5.1.1 | 1380 | | | 3 | 1381 | | | | 1382 | dot3MpcpRxGate | aMPCPRxGate | 30.3.5.1.1 | 1383 | | | 4 | 1384 | | | | 1385 | dot3MpcpRxRegAck | aMPCPRxRegAck | 30.3.5.1.1 | 1386 | | | 5 | 1387 | dot3MpcpRxRegister | aMPCPRxRegister | 30.3.5.1.1 | 1388 | | | 6 | 1389 | | | | 1390 | dot3MpcpRxRegRequest | aMPCPRxRegRequest | 30.3.5.1.1 | 1391 | | | 7 | 1392 | | | | 1393 | dot3MpcpRxReport | aMPCPRxReport | 30.3.5.1.1 | 1394 | | | 8 | 1395 | | | | 1396 | dot3MpcpTransmitElapsed | aMPCPTransmitElapsed | 30.3.5.1.1 | 1397 | | | 9 | 1398 | | | | 1399 | dot3MpcpReceiveElapsed | aMPCPReceiveElapsed | 30.3.5.1.2 | 1400 | | | 0 | 1401 | | | | 1402 | dot3MpcpRoundTripTime | aMPCPRoundTripTime | 30.3.5.1.2 | 1403 | | | 1 | 1404 | | | | 1405 | dot3MpcpDiscoveryWindowsSe | aMPCPDiscoveryWindowsSe | 30.3.5.1.2 | 1406 | nt | nt | 2 | 1407 | | | | 1408 | dot3MpcpDiscoveryTimeout | aMPCPDiscoveryTimeout | 30.3.5.1.2 | 1409 | | | 3 | 1410 | | | | 1411 | dot3MpcpMaximumPendingGran | aMPCPMaximumPendingGran | 30.3.5.1.2 | 1412 | ts | ts | 4 | 1413 | | | | 1414 | dot3MpcpAdminState | aMPCPAdminControl | 30.3.5.2.1 | 1415 | | | | 1416 | dot3MpcpSyncTime | SyncTime | 64.3.3.2 | 1417 +----------------------------+-------------------------+------------+ 1419 Table 9 1421 oOMPEmulation managed object class (30.3.7) 1423 +-------------------------------------+-----------------+-----------+ 1424 | dot3EPON MIB module object | IEEE802.3ah | Reference | 1425 | | attribute | | 1426 +-------------------------------------+-----------------+-----------+ 1427 | ifIndex | aOMPEmulationID | 30.3.7.1. | 1428 | | | 1 | 1429 | | | | 1430 | dot3OmpEmulationType | aOMPEmulationTy | 30.3.7.1. | 1431 | | pe | 2 | 1432 | | | | 1433 | dot3OmpEmulationSLDErrors | aSLDErrors | 30.3.7.1. | 1434 | | | 3 | 1435 | | | | 1436 | dot3OmpEmulationCRC8Errors | aCRC8Errors | 30.3.7.1. | 1437 | | | 4 | 1438 | | | | 1439 | dot3OmpEmulationGoodLLID | aGoodLLID | 30.3.7.1. | 1440 | | | 5 | 1441 | | | | 1442 | dot3OmpEmulationOnuPonCastLLID | aONUPONcastLLID | 30.3.7.1. | 1443 | | | 6 | 1444 | | | | 1445 | dot3OmpEmulationOltPonCastLLID | aOLTPONcastLLID | 30.3.7.1. | 1446 | | | 7 | 1447 | | | | 1448 | dot3OmpEmulationBadLLID | aBadLLID | 30.3.7.1. | 1449 | | | 8 | 1450 | | | | 1451 | dot3OmpEmulationBroadcastBitNotOnuL | | | 1452 | Lid | | | 1453 | | | | 1454 | dot3OmpEmulationOnuLLIDNotBroadcast | | | 1455 | | | | 1456 | dot3OmpEmulationBroadcastBitPlusOnu | | | 1457 | Llid | | | 1458 | | | | 1459 | dot3OmpEmulationNotBroadcastBitNotO | | | 1460 | nuLlid | | | 1461 +-------------------------------------+-----------------+-----------+ 1463 Table 10 1465 oMAU managed object class (30.5.1) 1467 +--------------------------------+---------------------+------------+ 1468 | dot3EPON MIB module object | IEEE802.3ah | Reference | 1469 | | attribute | | 1470 +--------------------------------+---------------------+------------+ 1471 | dot3EponFecPCSCodingViolation | aPCSCodingViolation | 30.5.1.1.1 | 1472 | | | 2 | 1473 | | | | 1474 | dot3EponFecAbility | aFECAbility | 30.5.1.1.1 | 1475 | | | 3 | 1476 | | | | 1477 | dot3EponFecMode | aFECmode | 30.5.1.1.1 | 1478 | | | 4 | 1479 | | | | 1480 | dot3EponFecCorrectedBlocks | aFECCorrectedBlocks | 30.5.1.1.1 | 1481 | | | 5 | 1482 | | | | 1483 | dot3EponFecUncorrectableBlocks | aFECUncorrectableBl | 30.5.1.1.1 | 1484 | | ocks | 6 | 1485 | | | | 1486 | dot3EponFecBufferHeadCodingVio | | | 1487 | lation | | | 1488 +--------------------------------+---------------------+------------+ 1490 Table 11 1492 5. Definitions - The DOT3 EPON MIB module 1494 DOT3-EPON-MIB DEFINITIONS ::= BEGIN 1496 IMPORTS 1497 MODULE-IDENTITY, mib-2, OBJECT-TYPE, Counter32, 1498 Integer32, Unsigned32, Counter64 1499 FROM SNMPv2-SMI 1500 TruthValue, MacAddress 1501 FROM SNMPv2-TC 1502 ifIndex 1503 FROM IF-MIB 1504 MODULE-COMPLIANCE, OBJECT-GROUP 1505 FROM SNMPv2-CONF 1506 ; 1508 dot3EponMIB MODULE-IDENTITY 1509 LAST-UPDATED "200611070000Z" -- November 7, 2006 1510 ORGANIZATION "IETF Ethernet Interfaces and Hub MIB Working 1511 Group" 1512 CONTACT-INFO 1513 "WG charter: 1514 http://www.ietf.org/html.charters/hubmib-charter.html 1515 Mailing Lists: 1516 General Discussion: hubmib@ietf.org 1517 To Subscribe: hubmib-request@ietf.org 1518 In Body: subscribe your_email_address 1519 Chair: Bert Wijnen 1520 Postal: Lucent Technologies 1521 Schagen 33 1522 3461 GL Linschoten 1523 Netherlands 1524 Tel: +31-348-407-775 1525 E-mail: bwijnen@lucent.com 1527 Editor: Lior Khermosh 1528 Postal: PMC-SIERRA 1529 Kohav Hertzelia bldg, 1530 94 Hasadnaot St. 1531 Hertzliya Pituach 46120, 1532 ISRAEL 1533 P.O.Box 2089 Hertzliya Pituach 46120 Israel 1534 Tel: +972-9-9628000 Ext: 302 1535 E-mail: lior_khermosh@pmc-sierra.com" 1536 DESCRIPTION 1537 "The objects in this MIB module are used to manage the 1538 Ethernet in the First Mile(EFM) Ethernet Passive Optical 1539 Network(EPON) Interfaces as defined in IEEE P802.3ah 1540 clause 60,64,65. 1541 The following reference is used throughout this MIB module: 1542 [802.3ah] refers to: 1543 Information technology - Telecommunications and 1544 information exchange between systems - Local and 1545 metropolitan area networks - Specific requirements - 1546 Part 3: Carrier sense multiple access with collision 1547 detection (CSMA/CD) access method and physical layer 1548 specifications - Media Access Control Parameters, 1549 Physical Layers and Management Parameters for subscriber 1550 access networks. IEEE Std 802.3ah-2004, October 2004. 1552 Of particular interest are Clause 64(Multi-Point Control 1553 Protocol - MPCP), Clause 65(Point to Multipoint 1554 Reconciliation Sublayer - P2MP RS), Clause 60 (Ethernet 1555 Passive Optical Network Physical Medium Dependent - EPON 1556 PMDs), Clause 30, 'Management', and Clause 45, 'Management 1557 Data Input/Output (MDIO) Interface'. 1559 Copyright (C) The IETF Trust (2006). This version 1560 of this MIB module is part of XXXX see the RFC itself for 1561 full legal notices. 1563 Key abbreviations: 1564 BER - Bit Error Rate 1565 BW - bandwidth 1566 CRC - Cyclic Redundancy Check 1567 EFM - Ethernet First Mile 1568 EPON - Ethernet Passive Optical Network 1569 FEC - Forward Error Correction 1570 LLID - Logical Link Identifier 1571 MAC - Media Access Control 1572 Mbps - Mega-bit per second 1573 MDIO - Management Data Input/Output 1574 MPCP - Multi-Point Control Protocol 1575 OLT - Optical Line Terminal (Server unit of the EPON) 1576 OMP - Optical Multi-Point 1577 ONU - Optical Network Unit (Client unit of the EPON) 1578 P2MP - Point to Multi-Point 1579 PHY - Physical Layer 1580 PMD - Physical Medium Dependent 1581 PON - Passive Optical Network 1582 RTT - Round Trip Time 1583 SLD - Start of LLID Delimiter 1584 TQ - Time Quanta 1586 " 1588 -- Editor's Note: Replace XXXX with the actual RFC number 1589 -- assigned by RFC Editor and remove this note 1591 REVISION "200611070000Z" -- November 7, 2006 1592 DESCRIPTION "Initial version, published as RFC XXXX." 1594 ::= { mib-2 XXX } 1596 -- Editor's Note (to be removed prior to publication): the 1597 -- IANA is requested to assign a value for "XXX" under the 1598 -- 'mib-2' subtree and to record the assignment in the SMI 1599 -- Numbers registry. When the assignment has been made, the 1600 -- RFC Editor is asked to replace "XXX" (here and in the MIB 1601 -- module) with the assigned value and to remove this note. 1603 dot3EponObjects OBJECT IDENTIFIER ::= { dot3EponMIB 1} 1605 dot3EponConformance OBJECT IDENTIFIER ::= { dot3EponMIB 2} 1607 -- MPCP MIB modules definitions ([802.3ah] clause 30.3.5) 1609 dot3EponMpcpObjects 1610 OBJECT IDENTIFIER ::= { dot3EponObjects 1 } 1612 dot3MpcpControlTable OBJECT-TYPE 1613 SYNTAX SEQUENCE OF Dot3MpcpControlEntry 1614 MAX-ACCESS not-accessible 1615 STATUS current 1616 DESCRIPTION 1617 "A Table of dot3 Multi-Point Control Protocol (MPCP) 1618 MIB objects. The entries in the table are control and 1619 status objects of the MPCP. 1620 Each object has a row for every virtual link denoted by 1621 the corresponding ifIndex. 1622 The LLID field, as defined in the [802.3ah] is a 2bytes 1623 register (15bits field and a broadcast bit) limiting the 1624 number of virtual links to 32768. Typically the number 1625 of expected virtual links in a PON is like the number of 1626 ONUs, which is 32-64, plus an additional entry for 1627 broadcast LLID (with a value of 0xffff)." 1628 ::= { dot3EponMpcpObjects 1 } 1630 dot3MpcpControlEntry OBJECT-TYPE 1631 SYNTAX Dot3MpcpControlEntry 1632 MAX-ACCESS not-accessible 1633 STATUS current 1634 DESCRIPTION 1635 "An entry in the dot3 MPCP Control table. 1636 Rows exist for an OLT interface and an ONU interface. 1637 A Row in the table is denoted by the ifIndex of the link 1638 and it is created when the ifIndex is created. 1639 The rows in the table for an ONU interface are created 1640 at system initialization. 1641 The row in the table corresponding to the OLT ifIndex 1642 and the row corresponding to the broadcast virtual link 1643 are created at system initialization. 1644 A row in the table corresponding to the ifIndex of a 1645 virtual links is created when a virtual link is 1646 established (ONU registers) and deleted when the virtual 1647 link is deleted (ONU deregisters)." 1648 INDEX { ifIndex } 1649 ::= { dot3MpcpControlTable 1} 1651 Dot3MpcpControlEntry ::= 1652 SEQUENCE { 1653 dot3MpcpOperStatus TruthValue, 1654 dot3MpcpAdminState TruthValue, 1655 dot3MpcpMode INTEGER, 1656 dot3MpcpSyncTime Unsigned32, 1657 dot3MpcpLinkID Unsigned32, 1658 dot3MpcpRemoteMACAddress MacAddress, 1659 dot3MpcpRegistrationState INTEGER, 1660 dot3MpcpTransmitElapsed Unsigned32, 1661 dot3MpcpReceiveElapsed Unsigned32, 1662 dot3MpcpRoundTripTime Unsigned32, 1663 dot3MpcpMaximumPendingGrants Unsigned32 1664 } 1666 dot3MpcpOperStatus OBJECT-TYPE 1667 SYNTAX TruthValue 1668 MAX-ACCESS read-only 1669 STATUS current 1670 DESCRIPTION 1671 "This object reflects the operational state of the 1672 Multi-Point MAC Control sublayer, as defined in 1673 [802.3ah] clause 64. When the value is true(1) the 1674 interface will act as if Multi-Point control protocol 1675 is enabled. When the value is false(2) the interface 1676 will act as if the Multi-Point control protocol is 1677 disabled. The operational state can be changed using the 1678 dot3MpcpAdminState object. 1680 This object is applicable for an OLT, with the same 1681 value for all virtual interfaces, and for an ONU." 1682 REFERENCE "[802.3ah], 30.3.5.1.2." 1683 ::= { dot3MpcpControlEntry 1 } 1685 dot3MpcpAdminState OBJECT-TYPE 1686 SYNTAX TruthValue 1687 MAX-ACCESS read-write 1688 STATUS current 1689 DESCRIPTION 1690 "This object is used to define the admin state of the 1691 Multi-Point MAC Control sublayer, as defined in 1692 [802.3ah] clause 64, and to reflect its state. 1693 When selecting the value as true(1) the Multi-Point 1694 control protocol of the interface is enabled. 1695 When selecting the value as false(2) the Multi-Point 1696 Control protocol of the interface is disabled. 1697 This object reflects the administrative state of the 1698 Multi-Point control protocol of the interface. 1699 The write operation is not restricted in this document 1700 and can be done at any time. Changing 1701 dot3MpcpAdminState state can lead to disabling the 1702 Multi-point control protocol on the respective interface 1703 leading to the interruption of service of the users 1704 connected to the respective EPON interface. 1705 This object is applicable for an OLT, with the same 1706 value for all virtual interfaces, and for an ONU." 1707 REFERENCE "[802.3ah], 30.3.5.2.1." 1708 DEFVAL { false } 1709 ::= { dot3MpcpControlEntry 2 } 1711 dot3MpcpMode OBJECT-TYPE 1712 SYNTAX INTEGER { 1713 olt(1), 1714 onu(2) 1715 } 1716 MAX-ACCESS read-only 1717 STATUS current 1718 DESCRIPTION 1719 "This object is used to identify the operational 1720 state of the Multi-Point MAC Control sublayer, as 1721 defined in [802.3ah] clause 64. Reading olt(1) for an 1722 OLT (server) mode and onu(2) for an ONU (client) mode. 1723 This object is used to identify the operational mode 1724 for the MPCP tables. 1725 This object is applicable for an OLT, with the same 1726 value for all virtual interfaces, and for an ONU." 1728 REFERENCE "[802.3ah], 30.3.5.1.3." 1729 DEFVAL { olt } 1730 ::= { dot3MpcpControlEntry 3 } 1732 dot3MpcpSyncTime OBJECT-TYPE 1733 SYNTAX Unsigned32 1734 UNITS "TQ (16nsec)" 1735 MAX-ACCESS read-only 1736 STATUS current 1737 DESCRIPTION 1738 "An object that reports the 'sync lock time' of the 1739 OLT receiver in increments of Time Quanta (TQ)-16ns 1740 as defined in [802.3ah] 60,64,65. The value returned 1741 shall be (sync lock time ns)/16. If this value exceeds 1742 (2^32-1) the value (2^32-1) shall be returned. 1743 This object is applicable for an OLT, with the same 1744 value for all virtual interfaces, and for an ONU." 1745 REFERENCE "[802.3ah], 64.3.3.2." 1746 ::= { dot3MpcpControlEntry 4 } 1748 dot3MpcpLinkID OBJECT-TYPE 1749 SYNTAX Unsigned32 1750 MAX-ACCESS read-only 1751 STATUS current 1752 DESCRIPTION 1753 "An object that identifies the Logical Link 1754 identifier (LLID) associated with the MAC of the virtual 1755 link, as specified in [802.3ah] clause 65.1.3.2.2. 1756 This object is applicable for an OLT and an ONU. At the 1757 OLT it has a distinct value for each virtual interface. 1758 The ONU and the corresponding virtual MAC of the OLT, 1759 for the same virtual link, have the same value. 1760 Value is assigned when the ONU registers. 1761 Value is freed when the ONU deregisters." 1762 REFERENCE "[802.3ah], 30.3.5.1.4." 1763 ::= { dot3MpcpControlEntry 5 } 1765 dot3MpcpRemoteMACAddress OBJECT-TYPE 1766 SYNTAX MacAddress 1767 MAX-ACCESS read-only 1768 STATUS current 1769 DESCRIPTION 1770 "An object that identifies the source_address 1771 parameter of the last MPCPDUs passed to the MAC Control. 1772 This value is updated on reception of a valid frame with 1773 (1) a destination Field equal to the reserved multicast 1774 address for MAC Control specified in [802.3] Annex 1775 31A, (2) lengthOrType field value equal to the reserved 1776 Type for MAC Control as specified in [802.3] Annex 1777 31A. (3) an MPCP subtype value equal to the subtype 1778 reserved for MPCP as specified in [802.3ah] Annex 31A. 1779 This object is applicable for an OLT and an ONU. At the 1780 OLT it has a distinct value for each virtual interface. 1781 The value reflects the MAC address of the remote entity 1782 and therefore the OLT holds a value for each LLID which 1783 is the MAC address of the ONU and the ONU has a single 1784 value which is the OLT MAC address." 1785 REFERENCE "[802.3ah], 30.3.5.1.5." 1786 ::= { dot3MpcpControlEntry 6 } 1788 dot3MpcpRegistrationState OBJECT-TYPE 1789 SYNTAX INTEGER { 1790 unregistered(1), 1791 registering(2), 1792 registered(3) 1793 } 1794 MAX-ACCESS read-only 1795 STATUS current 1796 DESCRIPTION 1797 "An object that identifies the registration state 1798 of the Multi-Point MAC Control sublayer as defined in 1799 [802.3ah] clause 64. When this object has the 1800 enumeration unregistered(1) the interface is 1801 unregistered and may be used for registering a link 1802 partner. When this object has the enumeration 1803 registering(2) the interface is in the process of 1804 registering a link-partner. When this object has the 1805 enumeration registered(3) the interface has an 1806 established link-partner. 1807 This object is applicable for an OLT and an ONU. At the 1808 OLT it has a distinct value for each virtual interface." 1809 REFERENCE "[802.3ah], 30.3.5.1.6." 1810 ::= { dot3MpcpControlEntry 7 } 1812 dot3MpcpTransmitElapsed OBJECT-TYPE 1813 SYNTAX Unsigned32 1814 UNITS "TQ (16nsec)" 1815 MAX-ACCESS read-only 1816 STATUS current 1817 DESCRIPTION 1818 "An object that reports the interval from last 1819 MPCP frame transmission in increments of Time Quanta 1820 (TQ)-16ns. The value returned shall be (interval from 1821 last MPCP frame transmission in ns)/16. If this value 1822 exceeds (2^32-1) the value (2^32-1) shall be returned. 1824 This object is applicable for an OLT and an ONU. At the 1825 OLT it has a distinct value for each virtual interface." 1826 REFERENCE "[802.3ah], 30.3.5.1.19." 1827 ::= { dot3MpcpControlEntry 8 } 1829 dot3MpcpReceiveElapsed OBJECT-TYPE 1830 SYNTAX Unsigned32 1831 UNITS "TQ (16nsec)" 1832 MAX-ACCESS read-only 1833 STATUS current 1834 DESCRIPTION 1835 "An object that reports the interval from last MPCP frame 1836 reception in increments of Time Quanta (TQ)-16ns. The 1837 value returned shall be (interval from last MPCP frame 1838 reception in ns)/16. If this value exceeds (2^32-1) the 1839 value (2^32-1) shall be returned. 1840 This object is applicable for an OLT and an ONU. At the 1841 OLT it has a distinct value for each virtual interface." 1842 REFERENCE "[802.3ah], 30.3.5.1.20." 1843 ::= { dot3MpcpControlEntry 9 } 1845 dot3MpcpRoundTripTime OBJECT-TYPE 1846 SYNTAX Unsigned32 (0..'ffff'h) 1847 UNITS "TQ (16nsec)" 1848 MAX-ACCESS read-only 1849 STATUS current 1850 DESCRIPTION 1851 "An object that reports the MPCP round trip time in 1852 increments of Time Quanta (TQ)-16ns. The value returned 1853 shall be (round trip time in ns)/16. If this value 1854 exceeds (2^16-1) the value (2^16-1) shall be returned. 1855 This object is applicable for an OLT and an ONU. At the 1856 OLT it has a distinct value for each virtual interface." 1857 REFERENCE "[802.3ah], 30.3.5.1.21." 1858 ::= { dot3MpcpControlEntry 10 } 1860 dot3MpcpMaximumPendingGrants OBJECT-TYPE 1861 SYNTAX Unsigned32 (0..255) 1862 MAX-ACCESS read-only 1863 STATUS current 1864 DESCRIPTION 1865 "An object that reports the maximum number of grants 1866 which an ONU can store for handling. The maximum number 1867 of grants which an ONU can store for handling has a 1868 range of 0 to 255. 1869 This object is applicable for an OLT and an ONU. At the 1870 OLT it has a distinct value for each virtual interface. 1871 At the OLT the value should be zero." 1873 REFERENCE "[802.3ah], 30.3.5.1.24." 1874 ::= { dot3MpcpControlEntry 11 } 1876 dot3MpcpStatTable OBJECT-TYPE 1877 SYNTAX SEQUENCE OF Dot3MpcpStatEntry 1878 MAX-ACCESS not-accessible 1879 STATUS current 1880 DESCRIPTION 1881 "This table defines the list of statistics counters of 1882 an interface implementing the [802.3ah] clause 64 MPCP. 1883 Each object has a row for every virtual link denoted by 1884 the corresponding ifIndex. 1885 The LLID field, as defined in the [802.3ah] is a 2bytes 1886 register (15bits field and a broadcast bit) limiting the 1887 number of virtual links to 32768. Typically the number 1888 of expected virtual links in a PON is like the number of 1889 ONUs, which is 32-64, plus an additional entry for 1890 broadcast LLID (with a value of 0xffff)." 1891 ::= { dot3EponMpcpObjects 2 } 1893 dot3MpcpStatEntry OBJECT-TYPE 1894 SYNTAX Dot3MpcpStatEntry 1895 MAX-ACCESS not-accessible 1896 STATUS current 1897 DESCRIPTION 1898 "An entry in the table of statistics counters of the 1899 [802.3ah] clause 64 MPCP interface. 1900 Rows exist for an OLT interface and an ONU interface. 1901 A Row in the table is denoted by the ifIndex of the link 1902 and it is created when the ifIndex is created. 1903 The rows in the table for an ONU interface are created 1904 at system initialization. 1905 The row in the table corresponding to the OLT ifIndex 1906 and the row corresponding to the broadcast virtual link 1907 are created at system initialization. 1908 A row in the table corresponding to the ifIndex of a 1909 virtual links is created when a virtual link is 1910 established (ONU registers) and deleted when the virtual 1911 link is deleted (ONU deregisters)." 1912 INDEX { ifIndex} 1913 ::= { dot3MpcpStatTable 1 } 1915 Dot3MpcpStatEntry ::= 1916 SEQUENCE { 1917 dot3MpcpMACCtrlFramesTransmitted Counter64, 1918 dot3MpcpMACCtrlFramesReceived Counter64, 1919 dot3MpcpDiscoveryWindowsSent Counter32, 1920 dot3MpcpDiscoveryTimeout Counter32, 1921 dot3MpcpTxRegRequest Counter64, 1922 dot3MpcpRxRegRequest Counter64, 1923 dot3MpcpTxRegAck Counter64, 1924 dot3MpcpRxRegAck Counter64, 1925 dot3MpcpTxReport Counter64, 1926 dot3MpcpRxReport Counter64, 1927 dot3MpcpTxGate Counter64, 1928 dot3MpcpRxGate Counter64, 1929 dot3MpcpTxRegister Counter64, 1930 dot3MpcpRxRegister Counter64 1931 } 1933 dot3MpcpMACCtrlFramesTransmitted OBJECT-TYPE 1934 SYNTAX Counter64 1935 UNITS "frames" 1936 MAX-ACCESS read-only 1937 STATUS current 1938 DESCRIPTION 1939 "A count of MPCP frames passed to the MAC sublayer for 1940 transmission. This counter is incremented when a 1941 MA_CONTROL.request service primitive is generated within 1942 the MAC control sublayer with an opcode indicating an 1943 MPCP frame. 1944 This object is applicable for an OLT and an ONU. At the 1945 OLT it has a distinct value for each virtual interface. 1946 Discontinuities of this counter can occur at 1947 re-initialization of the management system, and at other 1948 times as indicated by the value of the 1949 ifCounterDiscontinuityTime object of the Interface MIB 1950 module." 1951 REFERENCE "[802.3ah], 30.3.5.1.7." 1952 ::= { dot3MpcpStatEntry 1 } 1954 dot3MpcpMACCtrlFramesReceived OBJECT-TYPE 1955 SYNTAX Counter64 1956 UNITS "frames" 1957 MAX-ACCESS read-only 1958 STATUS current 1959 DESCRIPTION 1960 "A count of MPCP frames passed by the MAC sublayer to the 1961 MAC Control sublayer. This counter is incremented when a 1962 ReceiveFrame function call returns a valid frame with: 1963 (1) a lengthOrType field value equal to the reserved 1964 Type for 802.3_MAC_Control as specified in 31.4.1.3, and 1965 (2) an opcode indicating an MPCP frame. 1966 This object is applicable for an OLT and an ONU. At the 1967 OLT it has a distinct value for each virtual interface. 1969 Discontinuities of this counter can occur at 1970 re-initialization of the management system, and at other 1971 times as indicated by the value of the 1972 ifCounterDiscontinuityTime object of the Interface MIB 1973 module." 1974 REFERENCE "[802.3ah], 30.3.5.1.8." 1975 ::= { dot3MpcpStatEntry 2} 1977 dot3MpcpDiscoveryWindowsSent OBJECT-TYPE 1978 SYNTAX Counter32 1979 MAX-ACCESS read-only 1980 STATUS current 1981 DESCRIPTION 1982 "A count of discovery windows generated. The counter is 1983 incremented by one for each generated discovery window. 1984 This object is applicable for an OLT and an ONU. At the 1985 OLT it has a distinct value for each virtual interface. 1986 At the ONU the value should be zero. 1987 Discontinuities of this counter can occur at 1988 re-initialization of the management system, and at other 1989 times as indicated by the value of the 1990 ifCounterDiscontinuityTime object of the Interface MIB 1991 module." 1992 REFERENCE "[802.3ah], 30.3.5.1.22." 1993 ::= { dot3MpcpStatEntry 3} 1995 dot3MpcpDiscoveryTimeout OBJECT-TYPE 1996 SYNTAX Counter32 1997 MAX-ACCESS read-only 1998 STATUS current 1999 DESCRIPTION 2000 "A count of the number of times a discovery timeout 2001 occurs. Increment the counter by one for each discovery 2002 processing state-machine reset resulting from timeout 2003 waiting for message arrival. 2004 This object is applicable for an OLT and an ONU. At the 2005 OLT it has a distinct value for each virtual interface. 2006 Discontinuities of this counter can occur at 2007 re-initialization of the management system, and at other 2008 times as indicated by the value of the 2009 ifCounterDiscontinuityTime object of the Interface MIB 2010 module." 2011 REFERENCE "[802.3ah], 30.3.5.1.23." 2012 ::= { dot3MpcpStatEntry 4} 2014 dot3MpcpTxRegRequest OBJECT-TYPE 2015 SYNTAX Counter64 2016 UNITS "frames" 2017 MAX-ACCESS read-only 2018 STATUS current 2019 DESCRIPTION 2020 "A count of the number of times a REGISTER_REQ MPCP 2021 frame transmission occurs. Increment the counter by one 2022 for each REGISTER_REQ MPCP frame transmitted as defined 2023 in [802.3ah] clause 64. 2024 This object is applicable for an OLT and an ONU. At the 2025 OLT it has a distinct value for each virtual interface. 2026 At the OLT the value should be zero. 2027 Discontinuities of this counter can occur at 2028 re-initialization of the management system, and at other 2029 times as indicated by the value of the 2030 ifCounterDiscontinuityTime object of the Interface MIB 2031 module." 2032 REFERENCE "[802.3ah], 30.3.5.1.12." 2033 ::= { dot3MpcpStatEntry 5} 2035 dot3MpcpRxRegRequest OBJECT-TYPE 2036 SYNTAX Counter64 2037 UNITS "frames" 2038 MAX-ACCESS read-only 2039 STATUS current 2040 DESCRIPTION 2041 "A count of the number of times a REGISTER_REQ MPCP 2042 frame reception occurs. 2043 Increment the counter by one for each REGISTER_REQ MPCP 2044 frame received as defined in [802.3ah] clause 64. 2045 This object is applicable for an OLT and an ONU. At the 2046 OLT it has a distinct value for each virtual interface. 2047 At the ONU the value should be zero. 2048 Discontinuities of this counter can occur at 2049 re-initialization of the management system, and at other 2050 times as indicated by the value of the 2051 ifCounterDiscontinuityTime object of the Interface MIB 2052 module." 2053 REFERENCE "[802.3ah], 30.3.5.1.17." 2054 ::= { dot3MpcpStatEntry 6} 2056 dot3MpcpTxRegAck OBJECT-TYPE 2057 SYNTAX Counter64 2058 UNITS "frames" 2059 MAX-ACCESS read-only 2060 STATUS current 2061 DESCRIPTION 2062 "A count of the number of times a REGISTER_ACK MPCP 2063 frame transmission occurs. Increment the counter by one 2064 for each REGISTER_ACK MPCP frame transmitted as defined 2065 in [802.3ah] clause 64. 2066 This object is applicable for an OLT and an ONU. At the 2067 OLT it has a distinct value for each virtual interface. 2068 At the OLT the value should be zero. 2069 Discontinuities of this counter can occur at 2070 re-initialization of the management system, and at other 2071 times as indicated by the value of the 2072 ifCounterDiscontinuityTime object of the Interface MIB 2073 module." 2074 REFERENCE "[802.3ah], 30.3.5.1.10." 2075 ::= { dot3MpcpStatEntry 7} 2077 dot3MpcpRxRegAck OBJECT-TYPE 2078 SYNTAX Counter64 2079 UNITS "frames" 2080 MAX-ACCESS read-only 2081 STATUS current 2082 DESCRIPTION 2083 "A count of the number of times a REGISTER_ACK MPCP 2084 frame reception occurs. 2085 Increment the counter by one for each REGISTER_ACK MPCP 2086 frame received, as defined in [802.3ah] clause 64. 2087 This object is applicable for an OLT and an ONU. At the 2088 OLT it has a distinct value for each virtual interface. 2089 At the ONU the value should be zero. 2090 Discontinuities of this counter can occur at 2091 re-initialization of the management system, and at other 2092 times as indicated by the value of the 2093 ifCounterDiscontinuityTime object of the Interface MIB 2094 module." 2095 REFERENCE "[802.3ah], 30.3.5.1.15." 2096 ::= { dot3MpcpStatEntry 8} 2098 dot3MpcpTxReport OBJECT-TYPE 2099 SYNTAX Counter64 2100 UNITS "frames" 2101 MAX-ACCESS read-only 2102 STATUS current 2103 DESCRIPTION 2104 "A count of the number of times a REPORT MPCP frame 2105 transmission occurs. Increment the counter by one for 2106 each REPORT MPCP frame transmitted as defined in 2107 [802.3ah] clause 64. 2108 This object is applicable for an OLT and an ONU. At the 2109 OLT it has a distinct value for each virtual interface. 2110 At the OLT the value should be zero. 2111 Discontinuities of this counter can occur at 2112 re-initialization of the management system, and at other 2113 times as indicated by the value of the 2114 ifCounterDiscontinuityTime object of the Interface MIB 2115 module." 2116 REFERENCE "[802.3ah], 30.3.5.1.13." 2117 ::= { dot3MpcpStatEntry 9} 2119 dot3MpcpRxReport OBJECT-TYPE 2120 SYNTAX Counter64 2121 UNITS "frames" 2122 MAX-ACCESS read-only 2123 STATUS current 2124 DESCRIPTION 2125 "A count of the number of times a REPORT MPCP frame 2126 reception occurs. 2127 Increment the counter by one for each REPORT MPCP frame 2128 received, as defined in [802.3ah] clause 64. 2129 This object is applicable for an OLT and an ONU. At the 2130 OLT it has a distinct value for each virtual interface. 2131 At the ONU the value should be zero. 2132 Discontinuities of this counter can occur at 2133 re-initialization of the management system, and at other 2134 times as indicated by the value of the 2135 ifCounterDiscontinuityTime object of the Interface MIB 2136 module." 2137 REFERENCE "[802.3ah], 30.3.5.1.18." 2138 ::= { dot3MpcpStatEntry 10} 2140 dot3MpcpTxGate OBJECT-TYPE 2141 SYNTAX Counter64 2142 UNITS "frames" 2143 MAX-ACCESS read-only 2144 STATUS current 2145 DESCRIPTION 2146 "A count of the number of times a GATE MPCP frame 2147 transmission occurs. 2148 Increment the counter by one for each GATE MPCP frame 2149 transmitted, as defined in [802.3ah] clause 64. 2150 This object is applicable for an OLT and an ONU. At the 2151 OLT it has a distinct value for each virtual interface. 2152 At the ONU the value should be zero. 2153 Discontinuities of this counter can occur at 2154 re-initialization of the management system, and at other 2155 times as indicated by the value of the 2156 ifCounterDiscontinuityTime object of the Interface MIB 2157 module." 2158 REFERENCE "[802.3ah], 30.3.5.1.9." 2159 ::= { dot3MpcpStatEntry 11} 2161 dot3MpcpRxGate OBJECT-TYPE 2162 SYNTAX Counter64 2163 UNITS "frames" 2164 MAX-ACCESS read-only 2165 STATUS current 2166 DESCRIPTION 2167 "A count of the number of times a GATE MPCP frame 2168 reception occurs. 2169 Increment the counter by one for each GATE MPCP frame 2170 received, as defined in [802.3ah] clause 64. 2171 This object is applicable for an OLT and an ONU. At the 2172 OLT it has a distinct value for each virtual interface. 2173 At the OLT the value should be zero. 2174 Discontinuities of this counter can occur at 2175 re-initialization of the management system, and at other 2176 times as indicated by the value of the 2177 ifCounterDiscontinuityTime object of the Interface MIB 2178 module." 2179 REFERENCE "[802.3ah], 30.3.5.1.14." 2180 ::= { dot3MpcpStatEntry 12} 2182 dot3MpcpTxRegister OBJECT-TYPE 2183 SYNTAX Counter64 2184 UNITS "frames" 2185 MAX-ACCESS read-only 2186 STATUS current 2187 DESCRIPTION 2188 "A count of the number of times a REGISTER MPCP frame 2189 transmission occurs. 2190 Increment the counter by one for each REGISTER MPCP 2191 frame transmitted, as defined in [802.3ah] clause 64. 2192 This object is applicable for an OLT and an ONU. At the 2193 OLT it has a distinct value for each virtual interface. 2194 At the ONU the value should be zero. 2195 Discontinuities of this counter can occur at 2196 re-initialization of the management system, and at other 2197 times as indicated by the value of the 2198 ifCounterDiscontinuityTime object of the Interface MIB 2199 module." 2200 REFERENCE "[802.3ah], 30.3.5.1.11." 2201 ::= { dot3MpcpStatEntry 13} 2203 dot3MpcpRxRegister OBJECT-TYPE 2204 SYNTAX Counter64 2205 UNITS "frames" 2206 MAX-ACCESS read-only 2207 STATUS current 2208 DESCRIPTION 2209 "A count of the number of times a REGISTER MPCP frame 2210 reception occurs. 2211 Increment the counter by one for each REGISTER MPCP 2212 frame received, as defined in [802.3ah] clause 64. 2213 This object is applicable for an OLT and an ONU. At the 2214 OLT it has a distinct value for each virtual interface. 2215 At the OLT the value should be zero. 2216 Discontinuities of this counter can occur at 2217 re-initialization of the management system, and at other 2218 times as indicated by the value of the 2219 ifCounterDiscontinuityTime object of the Interface MIB 2220 module." 2221 REFERENCE "[802.3ah], 30.3.5.1.16." 2222 ::= { dot3MpcpStatEntry 14} 2224 -- Optical Multi Point Emulation (OMPEmulation) 2225 -- managed object definitions 2227 dot3OmpEmulationObjects OBJECT IDENTIFIER ::={dot3EponObjects 2} 2229 dot3OmpEmulationTable OBJECT-TYPE 2230 SYNTAX SEQUENCE OF Dot3OmpEmulationEntry 2231 MAX-ACCESS not-accessible 2232 STATUS current 2233 DESCRIPTION 2234 "A table of dot3 OmpEmulation MIB objects. The table 2235 contain objects for the management of the OMPEmulation 2236 sublayer. 2237 Each object has a row for every virtual link denoted by 2238 the corresponding ifIndex. 2239 The LLID field, as defined in the [802.3ah] is a 2bytes 2240 register (15bits field and a broadcast bit) limiting the 2241 number of virtual links to 32768. Typically the number 2242 of expected virtual links in a PON is like the number of 2243 ONUs, which is 32-64, plus an additional entry for 2244 broadcast LLID (with a value of 0xffff)." 2245 ::= { dot3OmpEmulationObjects 1 } 2247 dot3OmpEmulationEntry OBJECT-TYPE 2248 SYNTAX Dot3OmpEmulationEntry 2249 MAX-ACCESS not-accessible 2250 STATUS current 2251 DESCRIPTION 2252 "An entry in the dot3 OmpEmulation table. 2253 Rows exist for an OLT interface and an ONU interface. 2254 A Row in the table is denoted by the ifIndex of the link 2255 and it is created when the ifIndex is created. 2256 The rows in the table for an ONU interface are created 2257 at system initialization. 2258 The row in the table corresponding to the OLT ifIndex 2259 and the row corresponding to the broadcast virtual link 2260 are created at system initialization. 2261 A row in the table corresponding to the ifIndex of a 2262 virtual links is created when a virtual link is 2263 established (ONU registers) and deleted when the virtual 2264 link is deleted (ONU deregisters)." 2265 INDEX { ifIndex } 2266 ::= { dot3OmpEmulationTable 1 } 2268 Dot3OmpEmulationEntry ::= 2269 SEQUENCE { 2270 dot3OmpEmulationType INTEGER 2271 } 2273 dot3OmpEmulationType OBJECT-TYPE 2274 SYNTAX INTEGER { 2275 unknown(1), 2276 olt(2), 2277 onu(3) 2278 } 2279 MAX-ACCESS read-only 2280 STATUS current 2281 DESCRIPTION 2282 "An object that indicates the mode of operation 2283 of the Reconciliation Sublayer for Point to Point 2284 Emulation (see [802.3ah] clause 65.1). unknown(1) value 2285 is assigned in initialization, true state or type not 2286 yet known. olt(2) value is assigned when the sublayer is 2287 operating in OLT mode. onu(3) value is assigned when the 2288 sublayer is operating in ONU mode. 2289 This object is applicable for an OLT, with the same 2290 value for all virtual interfaces, and for an ONU." 2291 REFERENCE "[802.3ah], 30.3.7.1.2." 2292 ::= { dot3OmpEmulationEntry 1} 2294 dot3OmpEmulationStatTable OBJECT-TYPE 2295 SYNTAX SEQUENCE OF Dot3OmpEmulationStatEntry 2296 MAX-ACCESS not-accessible 2297 STATUS current 2298 DESCRIPTION 2299 "This table defines the list of statistics counters of 2301 [802.3ah] clause 65 OMPEmulation sublayer. 2302 Each object has a row for every virtual link denoted by 2303 the corresponding ifIndex. 2304 The LLID field, as defined in the [802.3ah] is a 2bytes 2305 register (15bits field and a broadcast bit) limiting the 2306 number of virtual links to 32768. Typically the number 2307 of expected virtual links in a PON is like the number of 2308 ONUs, which is 32-64, plus an additional entry for 2309 broadcast LLID (with a value of 0xffff)." 2310 ::= { dot3OmpEmulationObjects 2} 2312 dot3OmpEmulationStatEntry OBJECT-TYPE 2313 SYNTAX Dot3OmpEmulationStatEntry 2314 MAX-ACCESS not-accessible 2315 STATUS current 2316 DESCRIPTION 2317 "An entry in the table of statistics counters of 2318 [802.3ah] clause 65 OMPEmulation sublayer. 2319 Rows exist for an OLT interface and an ONU interface. 2320 A Row in the table is denoted by the ifIndex of the link 2321 and it is created when the ifIndex is created. 2322 The rows in the table for an ONU interface are created 2323 at system initialization. 2324 The row in the table corresponding to the OLT ifIndex 2325 and the row corresponding to the broadcast virtual link 2326 are created at system initialization. 2327 A row in the table corresponding to the ifIndex of a 2328 virtual links is created when a virtual link is 2329 established (ONU registers) and deleted when the virtual 2330 link is deleted (ONU deregisters)." 2331 INDEX { ifIndex} 2332 ::= { dot3OmpEmulationStatTable 1 } 2334 Dot3OmpEmulationStatEntry::= 2335 SEQUENCE { 2336 dot3OmpEmulationSLDErrors Counter64, 2337 dot3OmpEmulationCRC8Errors Counter64, 2338 dot3OmpEmulationBadLLID Counter64, 2339 dot3OmpEmulationGoodLLID Counter64, 2340 dot3OmpEmulationOnuPonCastLLID Counter64, 2341 dot3OmpEmulationOltPonCastLLID Counter64, 2342 dot3OmpEmulationBroadcastBitNotOnuLlid Counter64, 2343 dot3OmpEmulationOnuLLIDNotBroadcast Counter64, 2344 dot3OmpEmulationBroadcastBitPlusOnuLlid Counter64, 2345 dot3OmpEmulationNotBroadcastBitNotOnuLlid Counter64 2346 } 2348 dot3OmpEmulationSLDErrors OBJECT-TYPE 2349 SYNTAX Counter64 2350 UNITS "frames" 2351 MAX-ACCESS read-only 2352 STATUS current 2353 DESCRIPTION 2354 "A count of frames received that do not contain a valid 2355 SLD field as defined in [802.3ah] clause 65.1.3.3.1. 2356 This object is applicable for an OLT and an ONU. At the 2357 OLT it has a distinct value for each virtual interface. 2358 Discontinuities of this counter can occur at 2359 re-initialization of the management system, and at other 2360 times as indicated by the value of the 2361 ifCounterDiscontinuityTime object of the Interface MIB 2362 module." 2363 REFERENCE "[802.3ah], 30.3.7.1.3." 2364 ::= { dot3OmpEmulationStatEntry 1} 2366 dot3OmpEmulationCRC8Errors OBJECT-TYPE 2367 SYNTAX Counter64 2368 UNITS "frames" 2369 MAX-ACCESS read-only 2370 STATUS current 2371 DESCRIPTION 2372 "A count of frames received that contain a valid SLD 2373 field, as defined in [802.3ah] clause 65.1.3.3.1, but do 2374 not pass the CRC-8 check as defined in [802.3ah] clause 2375 65.1.3.3.3. 2376 This object is applicable for an OLT and an ONU. At the 2377 OLT it has a distinct value for each virtual interface. 2378 Discontinuities of this counter can occur at 2379 re-initialization of the management system, and at other 2380 times as indicated by the value of the 2381 ifCounterDiscontinuityTime object of the Interface MIB 2382 module." 2383 REFERENCE "[802.3ah], 30.3.7.1.4." 2384 ::= { dot3OmpEmulationStatEntry 2} 2386 dot3OmpEmulationBadLLID OBJECT-TYPE 2387 SYNTAX Counter64 2388 UNITS "frames" 2389 MAX-ACCESS read-only 2390 STATUS current 2391 DESCRIPTION 2392 "A count of frames received that contain a valid SLD 2393 field, as defined in [802.3ah] clause 65.1.3.3.1, and 2394 pass the CRC-8 check, as defined in [802.3ah] clause 2395 65.1.3.3.3, but are discarded due to the LLID check as 2396 defined in [802.3ah] clause 65.1.3.3.2. 2397 This object is applicable for an OLT and an ONU. At the 2398 OLT it has a distinct value for each virtual interface. 2399 Discontinuities of this counter can occur at 2400 re-initialization of the management system, and at other 2401 times as indicated by the value of the 2402 ifCounterDiscontinuityTime object of the Interface MIB 2403 module." 2404 REFERENCE "[802.3ah], 30.3.7.1.8." 2405 ::= { dot3OmpEmulationStatEntry 3} 2407 dot3OmpEmulationGoodLLID OBJECT-TYPE 2408 SYNTAX Counter64 2409 UNITS "frames" 2410 MAX-ACCESS read-only 2411 STATUS current 2412 DESCRIPTION 2413 "A count of frames received that contain a valid SLD 2414 field, as defined in [802.3ah] clause 65.1.3.3.1, and 2415 pass the CRC-8 check, as defined in [802.3ah] clause 2416 65.1.3.3.3. 2417 This object is applicable for an OLT and an ONU. At the 2418 OLT it has a distinct value for each virtual interface. 2419 Discontinuities of this counter can occur at 2420 re-initialization of the management system, and at other 2421 times as indicated by the value of the 2422 ifCounterDiscontinuityTime object of the Interface MIB 2423 module." 2424 REFERENCE "[802.3ah], 30.3.7.1.5." 2425 ::= { dot3OmpEmulationStatEntry 4} 2427 dot3OmpEmulationOnuPonCastLLID OBJECT-TYPE 2428 SYNTAX Counter64 2429 UNITS "frames" 2430 MAX-ACCESS read-only 2431 STATUS current 2432 DESCRIPTION 2433 "A count of frames received that contain a valid SLD 2434 field, as defined in [802.3ah] 65.1.3.3.1, 2435 pass the CRC-8 check, as defined in [802.3ah] 2436 65.1.3.3.3, and the meet the rules of acceptance for an 2437 ONU, defined in [802.3ah] 65.1.3.3.2. 2438 This object is applicable for an OLT and an ONU. At the 2439 OLT it has a distinct value for each virtual interface. 2440 At the OLT the value should be zero. 2441 Discontinuities of this counter can occur at 2442 re-initialization of the management system, and at other 2443 times as indicated by the value of the 2444 ifCounterDiscontinuityTime object of the Interface MIB 2445 module." 2446 REFERENCE "[802.3ah], 30.3.7.1.6." 2447 ::= { dot3OmpEmulationStatEntry 5} 2449 dot3OmpEmulationOltPonCastLLID OBJECT-TYPE 2450 SYNTAX Counter64 2451 UNITS "frames" 2452 MAX-ACCESS read-only 2453 STATUS current 2454 DESCRIPTION 2455 "A count of frames received that contain a valid SLD 2456 field, as defined in [802.3ah] 65.1.3.3.1, 2457 pass the CRC-8 check, as defined in [802.3ah] 2458 65.1.3.3.3, and the meet the rules of acceptance for an 2459 OLT, defined in [802.3ah] 65.1.3.3.2. 2460 This object is applicable for an OLT and an ONU. At the 2461 OLT it has a distinct value for each virtual interface. 2462 At the ONU the value should be zero. 2463 Discontinuities of this counter can occur at 2464 re-initialization of the management system, and at other 2465 times as indicated by the value of the 2466 ifCounterDiscontinuityTime object of the Interface MIB 2467 module." 2468 REFERENCE "[802.3ah], 30.3.7.1.7." 2469 ::= { dot3OmpEmulationStatEntry 6} 2471 dot3OmpEmulationBroadcastBitNotOnuLlid OBJECT-TYPE 2472 SYNTAX Counter64 2473 UNITS "frames" 2474 MAX-ACCESS read-only 2475 STATUS current 2476 DESCRIPTION 2477 "A count of frames received that contain a valid SLD 2478 field, as defined in [802.3ah] clause 2479 65.1.3.3.1, and pass the CRC-8 check, as defined in 2480 [802.3ah] clause 65.1.3.3.3, and contain the broadcast 2481 bit in the LLID and not the ONU's LLID (frame accepted) 2482 as defined in [802.3ah] clause 65. 2483 This object is applicable for an OLT and an ONU. At the 2484 OLT it has a distinct value for each virtual interface. 2485 At the OLT the value should be zero. 2486 Discontinuities of this counter can occur at 2487 re-initialization of the management system, and at other 2488 times as indicated by the value of the 2489 ifCounterDiscontinuityTime object of the Interface MIB 2490 module." 2492 ::= { dot3OmpEmulationStatEntry 7} 2494 dot3OmpEmulationOnuLLIDNotBroadcast OBJECT-TYPE 2495 SYNTAX Counter64 2496 UNITS "frames" 2497 MAX-ACCESS read-only 2498 STATUS current 2499 DESCRIPTION 2500 "A count of frames received that contain a valid SLD 2501 field, as defined in [802.3ah] clause 2502 65.1.3.3.1, and pass the CRC-8 check, as defined in 2503 [802.3ah] clause 65.1.3.3.3, and contain the ONU's LLID 2504 as defined in [802.3ah] clause 65. 2505 This object is applicable for an OLT and an ONU. At the 2506 OLT it has a distinct value for each virtual interface. 2507 At the OLT the value should be zero. 2508 Discontinuities of this counter can occur at 2509 re-initialization of the management system, and at other 2510 times as indicated by the value of the 2511 ifCounterDiscontinuityTime object of the Interface MIB 2512 module." 2513 ::= { dot3OmpEmulationStatEntry 8} 2515 dot3OmpEmulationBroadcastBitPlusOnuLlid OBJECT-TYPE 2516 SYNTAX Counter64 2517 UNITS "frames" 2518 MAX-ACCESS read-only 2519 STATUS current 2520 DESCRIPTION 2521 "A count of frames received that contain a valid SLD 2522 field, as defined in [802.3ah] clause 2523 65.1.3.3.1, and pass the CRC-8 check, as defined in 2524 [802.3ah] clause 65.1.3.3.3, and contain the broadcast 2525 bit in the LLID and match the ONU's LLID (frame 2526 reflected) as defined in [802.3ah] clause 65. 2527 This object is applicable for an OLT and an ONU. At the 2528 OLT it has a distinct value for each virtual interface. 2529 At the OLT the value should be zero. 2530 Discontinuities of this counter can occur at 2531 re-initialization of the management system, and at other 2532 times as indicated by the value of the 2533 ifCounterDiscontinuityTime object of the Interface MIB 2534 module." 2535 ::= { dot3OmpEmulationStatEntry 9} 2537 dot3OmpEmulationNotBroadcastBitNotOnuLlid OBJECT-TYPE 2538 SYNTAX Counter64 2539 UNITS "frames" 2540 MAX-ACCESS read-only 2541 STATUS current 2542 DESCRIPTION 2543 "A count of frames received that contain a valid SLD 2544 field, as defined in [802.3ah] clause 2545 65.1.3.3.1, and pass the CRC-8 check, as defined in 2546 [802.3ah] clause 65.1.3.3.3, and do not contain 2547 the ONU's LLID as defined in [802.3ah] clause 65. 2548 This object is applicable for an OLT and an ONU. At the 2549 OLT it has a distinct value for each virtual interface. 2550 At the OLT the value should be zero. 2551 Discontinuities of this counter can occur at 2552 re-initialization of the management system, and at other 2553 times as indicated by the value of the 2554 ifCounterDiscontinuityTime object of the Interface MIB 2555 module." 2556 ::= { dot3OmpEmulationStatEntry 10} 2558 -- FEC managed object definitions (30.5.1) 2560 dot3EponFecObjects OBJECT IDENTIFIER ::={dot3EponObjects 3} 2562 dot3EponFecTable OBJECT-TYPE 2563 SYNTAX SEQUENCE OF Dot3EponFecEntry 2564 MAX-ACCESS not-accessible 2565 STATUS current 2566 DESCRIPTION 2567 "A table of dot3 EPON FEC management objects. 2568 The entries in the table are control and status objects 2569 and statistic counters for the FEC layer. 2570 Each object has a row for every virtual link denoted by 2571 the corresponding ifIndex. 2572 The LLID field, as defined in the [802.3ah] is a 2bytes 2573 register (15bits field and a broadcast bit) limiting the 2574 number of virtual links to 32768. Typically the number 2575 of expected virtual links in a PON is like the number of 2576 ONUs, which is 32-64, plus an additional entry for 2577 broadcast LLID (with a value of 0xffff)." 2578 ::= { dot3EponFecObjects 1 } 2580 dot3EponFecEntry OBJECT-TYPE 2581 SYNTAX Dot3EponFecEntry 2582 MAX-ACCESS not-accessible 2583 STATUS current 2584 DESCRIPTION 2585 "An entry in the dot3 EPON FEC table. 2586 Rows exist for an OLT interface and an ONU interface. 2587 A Row in the table is denoted by the ifIndex of the link 2588 and it is created when the ifIndex is created. 2589 The rows in the table for an ONU interface are created 2590 at system initialization. 2591 The row in the table corresponding to the OLT ifIndex 2592 and the row corresponding to the broadcast virtual link 2593 are created at system initialization. 2594 A row in the table corresponding to the ifIndex of a 2595 virtual links is created when a virtual link is 2596 established (ONU registers) and deleted when the virtual 2597 link is deleted (ONU deregisters)." 2598 INDEX { ifIndex} 2599 ::= { dot3EponFecTable 1 } 2601 Dot3EponFecEntry ::= 2602 SEQUENCE { 2603 dot3EponFecPCSCodingViolation Counter64, 2604 dot3EponFecAbility INTEGER, 2605 dot3EponFecMode INTEGER, 2606 dot3EponFecCorrectedBlocks Counter64, 2607 dot3EponFecUncorrectableBlocks Counter64, 2608 dot3EponFecBufferHeadCodingViolation Counter64 2609 } 2611 dot3EponFecPCSCodingViolation OBJECT-TYPE 2612 SYNTAX Counter64 2613 UNITS "octets" 2614 MAX-ACCESS read-only 2615 STATUS current 2616 DESCRIPTION 2617 "For 100 Mbps operation it is a count of the number of 2618 times an invalid code-group is received, other than the 2619 /H/ code-group. For 1000 Mbps operation it is a count 2620 of the number of times an invalid codegroup is received, 2621 other than the /V/ code-group. /H/ denotes a special 2622 4b5b codeword of [802.3] 100 Mbps PCS layer (clause 24), 2623 and /V/ denotes a special 8b10b codeword of the [802.3] 2624 1000 Mbps PCS layer (clause 36). 2625 This object is applicable for an OLT and an ONU. At the 2626 OLT it has a distinct value for each virtual interface. 2627 Discontinuities of this counter can occur at 2628 re-initialization of the management system, and at other 2629 times as indicated by the value of the 2630 ifCounterDiscontinuityTime object of the Interface MIB 2631 module." 2633 REFERENCE "[802.3ah], 30.5.1.1.12." 2634 ::= { dot3EponFecEntry 1} 2636 dot3EponFecAbility OBJECT-TYPE 2637 SYNTAX INTEGER { 2638 unknown (1), 2639 unsupported (2), 2640 supported (3) 2641 } 2642 MAX-ACCESS read-only 2643 STATUS current 2644 DESCRIPTION 2645 "An object that indicates the support of operation of the 2646 optional FEC sublayer of the 1000BASE-PX PHY, specified 2647 in [802.3ah] clause 65.2. 2648 unknown(1) value is assigned in initialization, for non 2649 FEC support state or type not yet known. unsupported(2) 2650 value is assigned when sublayer is not supported. 2651 supported(3) value is assigned when sublayer is 2652 supported. 2653 This object is applicable for an OLT, with the same 2654 value for all virtual interfaces, and for an ONU. 2655 the FEC counters will have a zero value, when the 2656 interface is not supporting FEC. 2657 The counters: 2658 dot3EponFecPCSCodingViolation - not affected by FEC 2659 ability. 2660 dot3EponFecCorrectedBlocks - has a zero value when 2661 dot3EponFecAbility is unknown (1) and unsupported (2). 2662 dot3EponFecUncorrectableBlocks - has a zero value when 2663 dot3EponFecAbility is unknown (1) and unsupported (2). 2664 dot3EponFecBufferHeadCodingViolation - has a zero value 2665 when dot3EponFecAbility is unknown (1) and 2666 unsupported (2). " 2667 REFERENCE "[802.3ah], 30.5.1.1.13." 2668 ::= { dot3EponFecEntry 2} 2670 dot3EponFecMode OBJECT-TYPE 2671 SYNTAX INTEGER { 2672 unknown (1), 2673 disabled (2), 2674 enabled (3) 2675 } 2676 MAX-ACCESS read-write 2677 STATUS current 2678 DESCRIPTION 2679 "An object that defines the mode of operation of the 2680 optional FEC sublayer of the 1000BASE-PX PHY, specified 2681 in [802.3ah] clause 65.2, and reflects its state. 2682 A GET operation returns the current mode of operation 2683 of the PHY. A SET operation changes the mode of 2684 operation of the PHY to the indicated value. 2685 unknown(1) value is assigned in initialization, for non 2686 FEC support state or type not yet known. 2687 disabled(2) value is assigned when the FEC sublayer is 2688 operating in disabled mode. 2689 enabled(3) value is assigned when the FEC sublayer is 2690 operating in FEC mode. 2691 The write operation is not restricted in this document 2692 and can be done at any time. Changing dot3EponFecMode 2693 state can lead to disabling the Forward error correction 2694 on the respective interface which can lead to a 2695 degradation of the optical link and therefore may lead 2696 to an interruption of service of the users connected to 2697 the respective EPON interface. 2698 This object is applicable for an OLT and an ONU. At the 2699 OLT it has a distinct value for each virtual interface. 2700 The counting of 2701 the FEC counters will stop when the FEC of the interface 2702 is disabled. 2703 The counters: 2704 dot3EponFecPCSCodingViolation - not affected by FEC 2705 mode. 2706 dot3EponFecCorrectedBlocks - stops counting when 2707 Rx_FEC is not enabled. (unknown (1) and disabled (2)). 2708 dot3EponFecUncorrectableBlocks - stops counting when 2709 Rx_FEC is not enabled (unknown (1) and disabled (2)). 2710 dot3EponFecBufferHeadCodingViolation - stops counting 2711 when Rx_FEC is not enabled (unknown (1) and 2712 disabled (2)). 2713 The object: 2714 dot3EponFecAbility - indicates the FEC ability and it 2715 is not affected by the dot3EponFecMode object." 2716 REFERENCE "[802.3ah], 30.5.1.1.14." 2717 DEFVAL { unknown } 2718 ::= { dot3EponFecEntry 3} 2720 dot3EponFecCorrectedBlocks OBJECT-TYPE 2721 SYNTAX Counter64 2722 MAX-ACCESS read-only 2723 STATUS current 2724 DESCRIPTION 2725 "For 10PASS-TS, 2BASE-TL and 1000BASE-PX PHYs it is a 2726 count of corrected FEC blocks. This counter will not 2727 increment for other PHY Types. Increment the counter by 2728 one for each received block that is corrected by the FEC 2729 function in the PHY. 2730 This object is applicable for an OLT and an ONU. At the 2731 OLT it has a distinct value for each virtual interface. 2732 Discontinuities of this counter can occur at 2733 re-initialization of the management system, and at other 2734 times as indicated by the value of the 2735 ifCounterDiscontinuityTime object of the Interface MIB 2736 module." 2737 REFERENCE "[802.3ah], 30.5.1.1.15." 2738 ::= { dot3EponFecEntry 4} 2740 dot3EponFecUncorrectableBlocks OBJECT-TYPE 2741 SYNTAX Counter64 2742 MAX-ACCESS read-only 2743 STATUS current 2744 DESCRIPTION 2745 "For 10PASS-TS, 2BASE-TL and 1000BASE-PX PHYs it is a 2746 count of uncorrectable FEC blocks. This counter will not 2747 increment for other PHY Types. Increment the counter by 2748 one for each FEC block that is determined to be 2749 uncorrectable by the FEC function in the PHY. 2750 This object is applicable for an OLT and an ONU. At the 2751 OLT it has a distinct value for each virtual interface. 2752 Discontinuities of this counter can occur at 2753 re-initialization of the management system, and at other 2754 times as indicated by the value of the 2755 ifCounterDiscontinuityTime object of the Interface MIB 2756 module." 2757 REFERENCE "[802.3ah], 30.5.1.1.16." 2758 ::= { dot3EponFecEntry 5} 2760 dot3EponFecBufferHeadCodingViolation OBJECT-TYPE 2761 SYNTAX Counter64 2762 UNITS "octets" 2763 MAX-ACCESS read-only 2764 STATUS current 2765 DESCRIPTION 2766 "For 1000 Mbps operation it is a count of the number of 2767 invalid code-group received directly from the link. The 2768 value has a meaning only in 1000 Mbps mode and it is 2769 zero otherwise. 2770 This object is applicable for an OLT and an ONU. At the 2771 OLT it has a distinct value for each virtual interface. 2772 Discontinuities of this counter can occur at 2773 re-initialization of the management system, and at other 2774 times as indicated by the value of the 2775 ifCounterDiscontinuityTime object of the Interface MIB 2776 module." 2778 ::= { dot3EponFecEntry 6} 2780 -- ExtendedPackage managed object definitions 2782 dot3ExtPkgObjects OBJECT IDENTIFIER ::={dot3EponObjects 4} 2784 dot3ExtPkgControlObjects OBJECT IDENTIFIER ::= { dot3ExtPkgObjects 1} 2786 dot3ExtPkgControlTable OBJECT-TYPE 2787 SYNTAX SEQUENCE OF Dot3ExtPkgControlEntry 2788 MAX-ACCESS not-accessible 2789 STATUS current 2790 DESCRIPTION 2791 "A table of Extended package Control management 2792 objects. Entries in the table are control and status 2793 indication objects of an EPON interface which are 2794 gathered in an extended package as an addition to the 2795 objects based on the [802.3ah] clause 30 attributes. 2796 Each object has a row for every virtual link denoted by 2797 the corresponding ifIndex. 2798 The LLID field, as defined in the [802.3ah] is a 2bytes 2799 register (15bits field and a broadcast bit) limiting the 2800 number of virtual links to 32768. Typically the number 2801 of expected virtual links in a PON is like the number of 2802 ONUs, which is 32-64, plus an additional entry for 2803 broadcast LLID (with a value of 0xffff)." 2804 ::= { dot3ExtPkgControlObjects 1 } 2806 dot3ExtPkgControlEntry OBJECT-TYPE 2807 SYNTAX Dot3ExtPkgControlEntry 2808 MAX-ACCESS not-accessible 2809 STATUS current 2810 DESCRIPTION 2811 "An entry in the Extended package Control table. 2812 Rows exist for an OLT interface and an ONU interface. 2813 A Row in the table is denoted by the ifIndex of the link 2814 and it is created when the ifIndex is created. 2815 The rows in the table for an ONU interface are created 2816 at system initialization. 2817 The row in the table corresponding to the OLT ifIndex 2818 and the row corresponding to the broadcast virtual link 2819 are created at system initialization. 2820 A row in the table corresponding to the ifIndex of a 2821 virtual links is created when a virtual link is 2822 established (ONU registers) and deleted when the virtual 2823 link is deleted (ONU deregisters)." 2824 INDEX { ifIndex} 2825 ::= { dot3ExtPkgControlTable 1 } 2827 Dot3ExtPkgControlEntry ::= 2828 SEQUENCE { 2829 dot3ExtPkgObjectReset INTEGER, 2830 dot3ExtPkgObjectPowerDown TruthValue, 2831 dot3ExtPkgObjectNumberOfLLIDs Unsigned32, 2832 dot3ExtPkgObjectFecEnabled INTEGER, 2833 dot3ExtPkgObjectReportMaximumNumQueues Unsigned32, 2834 dot3ExtPkgObjectRegisterAction INTEGER 2835 } 2837 dot3ExtPkgObjectReset OBJECT-TYPE 2838 SYNTAX INTEGER { 2839 running(1), 2840 reset(2) 2841 } 2842 MAX-ACCESS read-write 2843 STATUS current 2844 DESCRIPTION 2845 "This object is used to reset the EPON interface. The 2846 interface may be unavailable while the reset occurs and 2847 data may be lost. 2848 Setting this object to running(1) will cause the 2849 interface to enter into running mode. Setting this 2850 object to reset(2) will cause the interface to go into 2851 reset mode. When getting running(1) the interface is in 2852 running mode. When getting reset(2) the interface is in 2853 reset mode. 2854 The write operation is not restricted in this document 2855 and can be done at any time. Changing 2856 dot3ExtPkgObjectReset state can lead to a reset of the 2857 respective interface leading to an interruption of 2858 service of the users connected to the respective EPON 2859 interface. 2860 This object is applicable for an OLT and an ONU. At the 2861 OLT it has a distinct value for each virtual interface. 2862 A reset for a specific virtual interface resets only 2863 this virtual interface and not the physical interface. 2864 Thus, a virtual link which is mal-functioning can be 2865 reset without affecting the operation of other virtual 2866 interfaces. 2867 The reset can cause Discontinuities in the values of the 2868 counters of the interface, similar to re-initialization 2869 of the management system. Discontinuity should be 2870 indicated by the ifCounterDiscontinuityTime object of 2871 the Interface MIB module." 2872 DEFVAL { running } 2873 ::= { dot3ExtPkgControlEntry 1 } 2875 dot3ExtPkgObjectPowerDown OBJECT-TYPE 2876 SYNTAX TruthValue 2877 MAX-ACCESS read-write 2878 STATUS current 2879 DESCRIPTION 2880 "This object is used to power down the EPON interface. 2881 The interface may be unavailable while the power down 2882 occurs and data may be lost. 2883 Setting this object to true(1) will cause the interface 2884 to enter into power down mode. Setting this object to 2885 false(2) will cause the interface to go out of power 2886 down mode. When getting true(1) the interface is in 2887 power down mode. When getting false(2) the interface is 2888 not in power down mode. 2889 The write operation is not restricted in this document 2890 and can be done at any time. Changing 2891 dot3ExtPkgObjectPowerDown state can lead to a power down 2892 of the respective interface leading to an interruption 2893 of service of the users connected to the respective EPON 2894 interface. 2895 This object is applicable for an OLT and an ONU. At the 2896 OLT it has a distinct value for each virtual interface. 2897 A power down/up of a specific virtual interface affects 2898 only the virtual interface and not the physical 2899 interface. Hence a virtual link which needs a certain 2900 handling can be powered down and then powered up without 2901 disrupting the operation of other virtual interfaces. 2902 The object is relevant when the admin state of the 2903 interface is active as set by the dot3MpcpAdminState." 2904 DEFVAL { false } 2905 ::= { dot3ExtPkgControlEntry 2 } 2907 dot3ExtPkgObjectNumberOfLLIDs OBJECT-TYPE 2908 SYNTAX Unsigned32 2909 MAX-ACCESS read-only 2910 STATUS current 2911 DESCRIPTION 2912 "A read only object which indicates the number of 2913 registered LLIDs. Initialization value is 0. 2914 This object is applicable for an OLT, with the same 2915 value for all virtual interfaces, and for an ONU. 2916 The LLID field, as defined in the [802.3ah] is a 2bytes 2917 register (15bits field and a broadcast bit) limiting the 2918 number of virtual links to 32768. Typically the number 2919 of expected virtual links in a PON is like the number of 2920 ONUs, which is 32-64, plus an additional entry for 2921 broadcast LLID (with a value of 0xffff). At the ONU the 2922 number of LLIDs for an interface is one." 2923 ::= { dot3ExtPkgControlEntry 3 } 2925 dot3ExtPkgObjectFecEnabled OBJECT-TYPE 2926 SYNTAX INTEGER { 2927 noFecEnabled (1), 2928 fecTxEnabled (2), 2929 fecRxEnabled (3), 2930 fecTxRxEnabled (4) 2931 } 2932 MAX-ACCESS read-write 2933 STATUS current 2934 DESCRIPTION 2935 "An object defining the FEC mode of operation of the 2936 interface, and indicating its state. The modes defined in 2937 this object are extensions to the FEC modes defined in 2938 the dot3EponFecMode object. 2939 When noFECEnabled (1) the interface does not enable FEC 2940 mode. 2941 When fecTxEnabled (2) the interface enables the FEC 2942 transmit mode. 2943 When fecRxEnabled (3) the interface enables the FEC 2944 receive mode. 2945 When fecTxRxEnabled (4) the interface enables the FEC 2946 transmit and receive mode. 2947 This object is applicable for an OLT and an ONU. At the 2948 OLT it has a distinct value for each virtual interface. 2949 The FEC counters are referring to the receive path. The 2950 FEC counters will stop when the FEC receive mode of the 2951 interface is disabled, as defined by fecRxEnabled (3) 2952 and fecTxRxEnabled (4) values. 2953 The counters: 2954 dot3EponFecPCSCodingViolation - not affected by FEC 2955 mode. 2956 dot3EponFecCorrectedBlocks - stops counting when 2957 Rx_FEC is not enabled. (noFecEnabled (1) and 2958 fecTxEnabled (2)). 2959 dot3EponFecUncorrectableBlocks - stops counting when 2960 Rx_FEC is not enabled (noFecEnabled (1) and 2961 fecTxEnabled (2)). 2962 dot3EponFecBufferHeadCodingViolation - stops counting 2963 when Rx_FEC is not enabled (noFecEnabled (1) and 2964 fecTxEnabled (2)). 2965 The objects: 2966 dot3EponFecAbility - indicates the FEC ability and is 2967 not affected by the FEC mode. 2968 dot3EponFecMode - indicates the FEC mode for combined RX 2969 and TX. 2970 The write operation is not restricted in this document 2971 and can be done at any time. Changing 2972 dot3ExtPkgObjectFecEnabled state can lead to disabling 2973 the Forward error correction on the respective interface 2974 which can lead to a degradation of the optical link and 2975 therefore may lead to an interruption of service of the 2976 users connected to the respective EPON interface." 2977 DEFVAL { noFecEnabled } 2978 ::= { dot3ExtPkgControlEntry 4 } 2980 dot3ExtPkgObjectReportMaximumNumQueues OBJECT-TYPE 2981 SYNTAX Unsigned32 (0..7) 2982 MAX-ACCESS read-only 2983 STATUS current 2984 DESCRIPTION 2985 "An object, that defines the maximal number of queues in 2986 the REPORT message, as defined in [802.3ah] 64. For 2987 further information please see the description of the 2988 queue table. 2989 This object is applicable for an OLT and an ONU. At the 2990 OLT it has a distinct value for each virtual interface." 2991 DEFVAL { 0 } 2992 ::= { dot3ExtPkgControlEntry 5 } 2994 dot3ExtPkgObjectRegisterAction OBJECT-TYPE 2995 SYNTAX INTEGER { 2996 none (1), 2997 register (2), 2998 deregister (3), 2999 reregister (4) 3000 } 3001 MAX-ACCESS read-write 3002 STATUS current 3003 DESCRIPTION 3004 "An object configuring the registration state of an 3005 interface, and indicating its registration state. 3006 Write operation changes the registration state to its new 3007 value. 3008 Read operation returns the value of the state. 3009 The registration state is reflected in this object and in 3010 the dot3MpcpRegistrationState object. 3011 none(1) indicates an unknown state, 3012 register(2) indicates a registered LLID, 3013 deregister(3) indicates a deregistered LLID, 3014 reregister(4) indicates an LLID which is reregistering. 3015 The following list describes the operation of the 3016 interface, as specified in the [802.3ah], when a write 3017 operation is setting a value. 3018 none (1) - not doing any action. 3019 register (2) - registering an LLID which request to 3020 register (The LLID is in registering mode. 3021 dot3MpcpRegistrationState - registering (2) ). 3022 deregister (3) - deregisters an LLID which is registered 3023 (dot3MpcpRegistrationState - registered (3) ). 3024 reregister (4) - reregister an LLID which is registered 3025 (dot3MpcpRegistrationState - registered (3) ). 3026 The behavior of an ONU and OLT interfaces, at each one 3027 of the detailed operation at each state is described in 3028 the registration state machine of figure 64-22, 3029 [802.3ah]. 3030 This object is applicable for an OLT and an ONU. At the 3031 OLT it has a distinct value for each virtual interface. 3032 The write operation is not restricted in this document 3033 and can be done at any time. Changing 3034 dot3ExtPkgObjectRegisterAction state can lead to a change 3035 in the registration state of the respective interface 3036 leading to a deregistration and an interruption of 3037 service of the users connected to the respective EPON 3038 interface." 3039 DEFVAL { none } 3040 ::= { dot3ExtPkgControlEntry 6 } 3042 dot3ExtPkgQueueTable OBJECT-TYPE 3043 SYNTAX SEQUENCE OF Dot3ExtPkgQueueEntry 3044 MAX-ACCESS not-accessible 3045 STATUS current 3046 DESCRIPTION 3047 "A table of the extended package objects for queue 3048 management. The [802.3ah] MPCP defines a report message 3049 of the occupancy of the transmit queues for the feedback 3050 BW request from the ONUs. These queues serve the uplink 3051 transmission of the ONU and data is gathered there until 3052 the ONU is granted for transmission. 3053 The management table of the queues is added here mainly 3054 to control the reporting and to gather some statistics 3055 of their operation. This table is not duplicating 3056 existing management objects of bridging queues, 3057 specified in [802.1d], since the existence of a 3058 dedicated transmit queuing mechanism is implied in the 3059 [802.3ah] and the ONU may be a device which is not a 3060 bridge, with embedded bridging queues. 3061 The format of the REPORT message, as specified 3062 in [802.3], is presented below: 3063 +-----------------------------------+ 3064 | Destination Address | 3065 +-----------------------------------+ 3066 | Source Address | 3067 +-----------------------------------+ 3068 | Length/Type | 3069 +-----------------------------------+ 3070 | OpCode | 3071 +-----------------------------------+ 3072 | TimeStamp | 3073 +-----------------------------------+ 3074 | Number of queue Sets | 3075 +-----------------------------------+ /|\ 3076 | Report bitmap | | 3077 +-----------------------------------+ | 3078 | Queue 0 report | | 3079 +-----------------------------------+ | repeated for 3080 | Queue 1 report | | every 3081 +-----------------------------------+ | queue_set 3082 | Queue 2 report | | 3083 +-----------------------------------+ | 3084 | Queue 3 report | | 3085 +-----------------------------------+ | 3086 | Queue 4 report | | 3087 +-----------------------------------+ | 3088 | Queue 5 report | | 3089 +-----------------------------------+ | 3090 | Queue 6 report | | 3091 +-----------------------------------+ | 3092 | Queue 7 report | | 3093 +-----------------------------------+ \|/ 3094 | Pad/reserved | 3095 +-----------------------------------+ 3096 | FCS | 3097 +-----------------------------------+ 3099 The 'Queue report' field reports the occupancy of each 3100 uplink transmission queue. 3101 The number of queue sets defines the number of the 3102 reported sets, as would be explained in the description 3103 of the dot3ExtPkgQueueSetsTable table. For each set the 3104 report bitmap defines which queue is present in the 3105 report, meaning that although the MPCP REPORT message 3106 can report of up to 8 queues in a REPORT message, the 3107 actual number is flexible. The Queue table has a 3108 variable size which is limited by the 3109 dot3ExtPkgObjectReportMaximumNumQueues object as an 3110 ONU can have fewer queues to report. 3111 The entries in the table are control and status 3112 indication objects for managing the queues of an EPON 3113 interface which are gathered in an extended package as 3114 an addition to the objects which are based on the 3115 [802.3ah] attributes. 3116 Each object has a row for every virtual link and for 3117 every queue in the report. 3118 The LLID field, as defined in the [802.3ah] is a 2bytes 3119 register (15bits field and a broadcast bit) limiting the 3120 number of virtual links to 32768. Typically the number 3121 of expected virtual links in a PON is like the number of 3122 ONUs, which is 32-64, plus an additional entry for 3123 broadcast LLID (with a value of 0xffff). 3124 The number of queues is between 0 and 7 and limited by 3125 dot3ExtPkgObjectReportMaximumNumQueues." 3126 ::= { dot3ExtPkgControlObjects 2 } 3128 dot3ExtPkgQueueEntry OBJECT-TYPE 3129 SYNTAX Dot3ExtPkgQueueEntry 3130 MAX-ACCESS not-accessible 3131 STATUS current 3132 DESCRIPTION 3133 "An entry in the Extended package Queue table. At the 3134 OLT, the rows exist for each ifIndex and dot3QueueIndex. 3135 At the ONU, rows exist for the single ifIndex for each 3136 dot3QueueIndex. 3137 Rows in the table are created when the ifIndex of the 3138 link is created. A set of rows per queue are added for 3139 each ifIndex, denoted by the dot3QueueIndex. 3140 A set of rows per queue in the table, for an ONU 3141 interface are created at system initialization. 3142 A set of rows per queue in the table, corresponding to 3143 the OLT ifIndex and a set of rows per queue, 3144 corresponding to the broadcast virtual link, are 3145 created at system initialization. 3146 A set of rows per queue in the table, corresponding to 3147 the ifIndex of a virtual link are created when the 3148 virtual link is established (ONU registers) and deleted 3149 when the virtual link is deleted (ONU deregisters)." 3150 INDEX { ifIndex, dot3QueueIndex } 3151 ::= { dot3ExtPkgQueueTable 1 } 3153 Dot3ExtPkgQueueEntry ::= 3154 SEQUENCE { 3155 dot3QueueIndex Unsigned32, 3156 dot3ExtPkgObjectReportNumThreshold Unsigned32, 3157 dot3ExtPkgObjectReportMaximumNumThreshold Unsigned32, 3158 dot3ExtPkgStatTxFramesQueue Counter64, 3159 dot3ExtPkgStatRxFramesQueue Counter64, 3160 dot3ExtPkgStatDroppedFramesQueue Counter64 3161 } 3163 dot3QueueIndex OBJECT-TYPE 3164 SYNTAX Unsigned32 (0..7) 3165 MAX-ACCESS not-accessible 3166 STATUS current 3167 DESCRIPTION 3168 "An object that identifies an index for the queue table 3169 reflecting the queue index of the queues which are 3170 reported in the MPCP REPORT message, as defined in 3171 [802.3ah] clause 64. 3172 The number of queues is between 0 and 7 and limited by 3173 dot3ExtPkgObjectReportMaximumNumQueues." 3174 ::= { dot3ExtPkgQueueEntry 1 } 3176 dot3ExtPkgObjectReportNumThreshold OBJECT-TYPE 3177 SYNTAX Unsigned32 (0..7) 3178 MAX-ACCESS read-write 3179 STATUS current 3180 DESCRIPTION 3181 "An object that defines the number of thresholds for each 3182 queue in the REPORT message, as defined in [802.3ah] 3183 clause 64. 3184 Each queue_set reporting will provide information on the 3185 queue occupancy of frames below the matching Threshold. 3186 Read operation reflects the number of thresholds. 3187 Write operation sets the number of thresholds for each 3188 queue. 3189 The write operation is not restricted in this document 3190 and can be done at any time. Value can not exceed the 3191 maximal value defined by the 3192 dot3ExtPkgObjectReportMaximumNumThreshold object. 3193 Changing dot3ExtPkgObjectReportNumThreshold can lead to 3194 a change in the reporting of the ONU interface and 3195 therefore to a change in the bandwidth allocation of the 3196 respective interface. This change may lead a degradation 3197 or an interruption of service of the users connected to 3198 the respective EPON interface. 3199 This object is applicable for an OLT and an ONU. At the 3200 OLT it has a distinct value for each virtual interface 3201 and for each queue. At the ONU it has a distinct value 3202 for each queue." 3203 DEFVAL { 0 } 3204 ::= { dot3ExtPkgQueueEntry 2 } 3206 dot3ExtPkgObjectReportMaximumNumThreshold OBJECT-TYPE 3207 SYNTAX Unsigned32 (0..7) 3208 MAX-ACCESS read-only 3209 STATUS current 3210 DESCRIPTION 3211 "An object, that defines the maximal number of thresholds 3212 for each queue in the REPORT message, as defined in 3213 [802.3ah] clause 64. Each queue_set reporting will 3214 provide information on the queue occupancy of frames 3215 below the matching Threshold. 3216 This object is applicable for an OLT and an ONU. At the 3217 OLT it has a distinct value for each virtual interface 3218 and for each queue. At the ONU it has a distinct value 3219 for each queue." 3220 DEFVAL { 0 } 3221 ::= { dot3ExtPkgQueueEntry 3 } 3223 dot3ExtPkgStatTxFramesQueue OBJECT-TYPE 3224 SYNTAX Counter64 3225 UNITS "frames" 3226 MAX-ACCESS read-only 3227 STATUS current 3228 DESCRIPTION 3229 "A count of the number of times a frame transmission 3230 occurs from the corresponding 'Queue'. 3231 Increment the counter by one for each frame transmitted 3232 which is an output of the 'Queue'. 3233 The 'Queue' marking matches the REPORT MPCP message 3234 Queue field, as defined in [802.3ah] clause 64. 3235 This object is applicable for an OLT and an ONU. At the 3236 OLT it has a distinct value for each virtual interface 3237 and for each queue. At the ONU it has a distinct value 3238 for each queue. 3239 At the OLT the value should be zero. 3240 Discontinuities of this counter can occur at 3241 re-initialization of the management system, and at other 3242 times as indicated by the value of the 3243 ifCounterDiscontinuityTime object of the Interface MIB 3244 module." 3245 ::= { dot3ExtPkgQueueEntry 4} 3247 dot3ExtPkgStatRxFramesQueue OBJECT-TYPE 3248 SYNTAX Counter64 3249 UNITS "frames" 3250 MAX-ACCESS read-only 3251 STATUS current 3252 DESCRIPTION 3253 "A count of the number of times a frame reception 3254 occurs from the corresponding 'Queue'. 3255 Increment the counter by one for each frame received 3256 which is an input to the corresponding 'Queue'. 3257 The 'Queue' marking matches the REPORT MPCP message 3258 Queue field, as defined in [802.3ah] clause 64. 3259 This object is applicable for an OLT and an ONU. At the 3260 OLT it has a distinct value for each virtual interface 3261 and for each queue. At the ONU it has a distinct value 3262 for each queue. 3263 Discontinuities of this counter can occur at 3264 re-initialization of the management system, and at other 3265 times as indicated by the value of the 3266 ifCounterDiscontinuityTime object of the Interface MIB 3267 module." 3268 ::= { dot3ExtPkgQueueEntry 5} 3270 dot3ExtPkgStatDroppedFramesQueue OBJECT-TYPE 3271 SYNTAX Counter64 3272 UNITS "frames" 3273 MAX-ACCESS read-only 3274 STATUS current 3275 DESCRIPTION 3276 "A count of the number of times a frame drop 3277 occurs from the corresponding 'Queue'. 3278 Increment the counter by one for each frame dropped 3279 from the corresponding 'Queue'. 3280 The 'Queue' marking matches the REPORT MPCP message 3281 Queue field, as defined in [802.3ah] clause 64. 3282 This object is applicable for an OLT and an ONU. At the 3283 OLT it has a distinct value for each virtual interface 3284 and for each queue. At the ONU it has a distinct value 3285 for each queue. 3286 At the OLT the value should be zero. 3287 Discontinuities of this counter can occur at 3288 re-initialization of the management system, and at other 3289 times as indicated by the value of the 3290 ifCounterDiscontinuityTime object of the Interface MIB 3291 module." 3292 ::= { dot3ExtPkgQueueEntry 6} 3294 dot3ExtPkgQueueSetsTable OBJECT-TYPE 3295 SYNTAX SEQUENCE OF Dot3ExtPkgQueueSetsEntry 3296 MAX-ACCESS not-accessible 3297 STATUS current 3298 DESCRIPTION 3299 "A table of Extended package objects used for the 3300 management of the queue_sets. Entries are control and 3301 status indication objects of an EPON interface which 3302 are gathered in an extended package as an addition to 3303 the objects based on the [802.3ah] attributes. The 3304 objects in this table are specific for the queue_sets 3305 which are reported in the MPCP REPORT message as defined 3306 in [802.3ah] clause 64. 3307 The [802.3ah] MPCP defines a report message of the 3308 occupancy of the transmit queues for the feedback BW 3309 request from the ONUs. These queues serve the uplink 3310 transmission of the ONU and data is gathered there until 3311 the ONU is granted for transmission. 3312 The management table of the queues_sets is added here 3313 mainly to control the reporting and to gather some 3314 statistics of their operation. This table is not 3315 duplicating existing management objects of bridging 3316 queues, specified in [802.1d], since the existence of a 3317 dedicated transmit queuing mechanism is implied in the 3318 [802.3ah] and the ONU may be a device which is not a 3319 bridge, with embedded bridging queues. 3320 The format of the REPORT message, as specified 3321 in [802.3], is presented below: 3322 +-----------------------------------+ 3323 | Destination Address | 3324 +-----------------------------------+ 3325 | Source Address | 3326 +-----------------------------------+ 3327 | Length/Type | 3328 +-----------------------------------+ 3329 | OpCode | 3330 +-----------------------------------+ 3331 | TimeStamp | 3332 +-----------------------------------+ 3333 | Number of queue Sets | 3334 +-----------------------------------+ /|\ 3335 | Report bitmap | | 3336 +-----------------------------------+ | 3337 | Queue 0 report | | 3338 +-----------------------------------+ | repeated for 3339 | Queue 1 report | | every 3340 +-----------------------------------+ | queue_set 3341 | Queue 2 report | | 3342 +-----------------------------------+ | 3343 | Queue 3 report | | 3344 +-----------------------------------+ | 3345 | Queue 4 report | | 3346 +-----------------------------------+ | 3347 | Queue 5 report | | 3348 +-----------------------------------+ | 3349 | Queue 6 report | | 3350 +-----------------------------------+ | 3351 | Queue 7 report | | 3352 +-----------------------------------+ \|/ 3353 | Pad/reserved | 3354 +-----------------------------------+ 3355 | FCS | 3356 +-----------------------------------+ 3358 As can be seen from the message format, the ONU 3359 interface 3360 reports of the status of up to 8 queues and it can 3361 report in a single MPCP REPORT message of a few sets 3362 of queues. 3363 The number of queue_sets defines the number of the 3364 reported sets, and it can reach up to a value of 8. It 3365 means that a ONU can hold a variable number of sets 3366 between 0 to 7. 3367 The dot3ExtPkgQueueSetsTable table has a variable 3368 queue_set size which is limited by the 3369 dot3ExtPkgObjectReportMaximumNumThreshold object as an 3370 ONU can have fewer queue_sets to report. 3371 The 'Queue report' field reports the occupancy of each 3372 uplink transmission queue. The queue_sets can be used to 3373 report the occupancy of the queues in a few levels as to 3374 allow granting, in an accurate manner, of only part of 3375 the data available in the queues. A Threshold is 3376 defined for each queue_set to define the level of the 3377 queue which is counted for the report of the occupancy. 3378 The threshold is reflected in the queue_set table by the 3379 dot3ExtPkgObjectReportThreshold object. 3380 For each queue set, the report bitmap defines which 3381 queues are present in the report, meaning that 3382 although the MPCP REPORT message can report of up to 8 3383 queues in a REPORT message, the actual number is 3384 flexible. 3385 The dot3ExtPkgQueueSetsTable table has a variable queue 3386 size which is limited by the 3387 dot3ExtPkgObjectReportMaximumNumQueues object as an ONU 3388 can have fewer queues to report. 3389 Each object has a row for every virtual link, for each 3390 queue in the report and for each queue_set in the queue. 3391 The LLID field, as defined in the [802.3ah] is a 2bytes 3392 register (15bits field and a broadcast bit) limiting the 3393 number of virtual links to 32768. Typically the number 3394 of expected virtual links in a PON is like the number of 3395 ONUs, which is 32-64, plus an additional entry for 3396 broadcast LLID (with a value of 0xffff). 3397 The number of queues is between 0 and 7 and limited by 3398 dot3ExtPkgObjectReportMaximumNumQueues. 3399 The number of queues_sets is between 0 and 7 and limited 3400 by dot3ExtPkgObjectReportMaximumNumThreshold." 3402 ::= { dot3ExtPkgControlObjects 3 } 3404 dot3ExtPkgQueueSetsEntry OBJECT-TYPE 3405 SYNTAX Dot3ExtPkgQueueSetsEntry 3406 MAX-ACCESS not-accessible 3407 STATUS current 3408 DESCRIPTION 3409 "An entry in the Extended package queue_set table. At 3410 the OLT, the rows exist for each ifIndex, 3411 dot3QueueSetQueueIndex and dot3QueueSetIndex. At the 3412 ONU, rows exist for the single ifIndex, for each 3413 dot3QueueSetQueueIndex and dot3QueueSetIndex. 3414 Rows in the table are created when the ifIndex of the 3415 link is created. A set of rows per queue and per 3416 queue_set are added for each ifIndex, denoted by 3417 dot3QueueSetIndex and dot3QueueSetQueueIndex. 3418 A set of rows per queue and per queue_set in the table, 3419 for an ONU interface are created at system 3420 initialization. 3421 A set of rows per queue and per queue_Set in the table, 3422 corresponding to the OLT ifIndex and a set of rows per 3423 queue and per queue_set, corresponding to the broadcast 3424 virtual link, are created at system initialization. 3425 A set of rows per queue and per queue_set in the table, 3426 corresponding to the ifIndex of a virtual link are 3427 created when the virtual link is established (ONU 3428 registers) and deleted when the virtual link is deleted 3429 (ONU deregisters)." 3430 INDEX { ifIndex, 3431 dot3QueueSetQueueIndex,dot3QueueSetIndex} 3432 ::= { dot3ExtPkgQueueSetsTable 1 } 3434 Dot3ExtPkgQueueSetsEntry ::= 3435 SEQUENCE { 3436 dot3QueueSetQueueIndex Unsigned32, 3437 dot3QueueSetIndex Unsigned32, 3438 dot3ExtPkgObjectReportThreshold Unsigned32 3439 } 3441 dot3QueueSetQueueIndex OBJECT-TYPE 3442 SYNTAX Unsigned32 (0..7) 3443 MAX-ACCESS not-accessible 3444 STATUS current 3445 DESCRIPTION 3446 "An object that identifies the queue index for the 3447 dot3ExtPkgQueueSetsTable table. The queues are reported 3448 in the MPCP REPORT message as defined in [802.3ah] 3449 clause 64. 3450 The number of queues is between 0 and 7 and limited by 3451 dot3ExtPkgObjectReportMaximumNumQueues. 3452 Value corresponds to the dot3QueueIndex of the queue 3453 table." 3454 ::= { dot3ExtPkgQueueSetsEntry 1 } 3456 dot3QueueSetIndex OBJECT-TYPE 3457 SYNTAX Unsigned32 (0..7) 3458 MAX-ACCESS not-accessible 3459 STATUS current 3460 DESCRIPTION 3461 "An object that identifies the queue_set index for the 3462 dot3ExtPkgQueueSetsTable table. The queues are reported 3463 in the MPCP REPORT message as defined in [802.3ah] 3464 clause 64. 3465 The number of queues_sets is between 0 and 7. and 3466 limited by dot3ExtPkgObjectReportMaximumNumThreshold." 3467 ::= { dot3ExtPkgQueueSetsEntry 2 } 3469 dot3ExtPkgObjectReportThreshold OBJECT-TYPE 3470 SYNTAX Unsigned32 3471 UNITS "TQ (16nsec)" 3472 MAX-ACCESS read-write 3473 STATUS current 3474 DESCRIPTION 3475 "An object that defines the value of threshold report for 3476 each queue_set in the REPORT message, as defined in 3477 [802.3ah] clause 64. The number of sets for each queue 3478 is dot3ExtPkgObjectReportNumThreshold. 3479 In the REPORT message, each queue_set reporting will 3480 provide information on the occupancy of the queues for 3481 frames below the matching Threshold. 3482 The value returned shall be in Time quanta (TQ) which 3483 is 16nsec or 2 octets increments. 3484 Read operation provides the threshold value. Write 3485 operation sets the value of the threshold. 3486 The write operation is not restricted in this document 3487 and can be done at any time. Changing 3488 dot3ExtPkgObjectReportThreshold can lead to a change in 3489 the reporting of the ONU interface and therefore to a 3490 change in the bandwidth allocation of the respective 3491 interface. This change may lead a degradation or an 3492 interruption of service of the users connected to the 3493 respective EPON interface. 3494 This object is applicable for an OLT and an ONU. At the 3495 OLT it has a distinct value for each virtual interface, 3496 for each queue and for each queue_set. At the ONU it has 3497 a distinct value for each queue and for each queue_set." 3498 DEFVAL { 0 } 3499 ::= { dot3ExtPkgQueueSetsEntry 3 } 3501 --Optical Interface status tables 3503 dot3ExtPkgOptIfTable OBJECT-TYPE 3504 SYNTAX SEQUENCE OF Dot3ExtPkgOptIfEntry 3505 MAX-ACCESS not-accessible 3506 STATUS current 3507 DESCRIPTION 3508 "This table defines the control and status indication 3509 objects for the optical interface of the EPON interface. 3510 Each object has a row for every virtual link denoted by 3511 the corresponding ifIndex. 3512 The LLID field, as defined in the [802.3ah] is a 2bytes 3513 register (15bits field and a broadcast bit) limiting the 3514 number of virtual links to 32768. Typically the number 3515 of expected virtual links in a PON is like the number of 3516 ONUs, which is 32-64, plus an additional entry for 3517 broadcast LLID (with a value of 0xffff). 3518 Although the optical interface is a physical interface, 3519 there is a row in the table for each virtual interface. 3520 The reason for having a separate row for each virtual 3521 link is that the OLT has a separate link for each one of 3522 the ONUs. For instance, ONUs could be in different 3523 distances with different link budgets and different 3524 receive powers, therefore having different power alarms. 3525 It is quite similar to a case of different physical 3526 interfaces." 3527 ::= { dot3ExtPkgControlObjects 5} 3529 dot3ExtPkgOptIfEntry OBJECT-TYPE 3530 SYNTAX Dot3ExtPkgOptIfEntry 3531 MAX-ACCESS not-accessible 3532 STATUS current 3533 DESCRIPTION 3534 "An entry in the optical interface table of the EPON 3535 interface. 3536 Rows exist for an OLT interface and an ONU interface. 3537 A Row in the table is denoted by the ifIndex of the link 3538 and it is created when the ifIndex is created. 3539 The rows in the table for an ONU interface are created 3540 at system initialization. 3541 The row in the table corresponding to the OLT ifIndex 3542 and the row corresponding to the broadcast virtual link 3543 are created at system initialization. 3544 A row in the table corresponding to the ifIndex of a 3545 virtual links is created when a virtual link is 3546 established (ONU registers) and deleted when the virtual 3547 link is deleted (ONU deregisters)." 3548 INDEX { ifIndex } 3549 ::= { dot3ExtPkgOptIfTable 1 } 3551 Dot3ExtPkgOptIfEntry ::= 3552 SEQUENCE { 3553 dot3ExtPkgOptIfSuspectedFlag TruthValue, 3554 dot3ExtPkgOptIfInputPower Integer32, 3555 dot3ExtPkgOptIfLowInputPower Integer32, 3556 dot3ExtPkgOptIfHighInputPower Integer32, 3557 dot3ExtPkgOptIfLowerInputPowerThreshold Integer32, 3558 dot3ExtPkgOptIfUpperInputPowerThreshold Integer32, 3559 dot3ExtPkgOptIfOutputPower Integer32, 3560 dot3ExtPkgOptIfLowOutputPower Integer32, 3561 dot3ExtPkgOptIfHighOutputPower Integer32, 3562 dot3ExtPkgOptIfLowerOutputPowerThreshold Integer32, 3563 dot3ExtPkgOptIfUpperOutputPowerThreshold Integer32, 3564 dot3ExtPkgOptIfSignalDetect TruthValue, 3565 dot3ExtPkgOptIfTransmitAlarm TruthValue, 3566 dot3ExtPkgOptIfTransmitEnable TruthValue 3567 } 3569 dot3ExtPkgOptIfSuspectedFlag OBJECT-TYPE 3570 SYNTAX TruthValue 3571 MAX-ACCESS read-only 3572 STATUS current 3573 DESCRIPTION 3574 "This object is a reliability indication. 3575 If true, the data in this entry may be unreliable. 3576 This object is applicable for an OLT and an ONU. At the 3577 OLT it has a distinct value for each virtual interface." 3579 ::= { dot3ExtPkgOptIfEntry 1 } 3581 dot3ExtPkgOptIfInputPower OBJECT-TYPE 3582 SYNTAX Integer32 3583 UNITS "0.1 dbm" 3584 MAX-ACCESS read-only 3585 STATUS current 3586 DESCRIPTION 3587 "The optical power monitored at the input. 3588 This object is applicable for an OLT and an ONU. At the 3589 OLT it has a distinct value for each virtual interface." 3590 ::= { dot3ExtPkgOptIfEntry 2 } 3592 dot3ExtPkgOptIfLowInputPower OBJECT-TYPE 3593 SYNTAX Integer32 3594 UNITS "0.1 dbm" 3595 MAX-ACCESS read-only 3596 STATUS current 3597 DESCRIPTION 3598 "The lowest optical power monitored at the input during the 3599 current 15-minute interval. 3600 This object is applicable for an OLT and an ONU. At the 3601 OLT it has a distinct value for each virtual interface." 3602 ::= { dot3ExtPkgOptIfEntry 3 } 3604 dot3ExtPkgOptIfHighInputPower OBJECT-TYPE 3605 SYNTAX Integer32 3606 UNITS "0.1 dbm" 3607 MAX-ACCESS read-only 3608 STATUS current 3609 DESCRIPTION 3610 "The highest optical power monitored at the input during the 3611 current 15-minute interval. 3612 This object is applicable for an OLT and an ONU. At the 3613 OLT it has a distinct value for each virtual interface." 3614 ::= { dot3ExtPkgOptIfEntry 4 } 3616 dot3ExtPkgOptIfLowerInputPowerThreshold OBJECT-TYPE 3617 SYNTAX Integer32 3618 UNITS "0.1 dbm" 3619 MAX-ACCESS read-write 3620 STATUS current 3621 DESCRIPTION 3622 "The lower limit threshold on input power. If 3623 dot3ExtPkgOptIfInputPower drops to this value or below, 3624 a Threshold Crossing Alert (TCA) should be sent. 3625 Reading will present the threshold value. Writing will 3626 set the value of the threshold. 3628 The write operation is not restricted in this document 3629 and can be done at any time. Changing 3630 dot3ExtPkgOptIfLowerInputPowerThreshold can lead to a Threshold 3631 Crossing Alert (TCA) being sent for the respective interface. 3632 This alert may be leading to an interruption of service of the 3633 users connected to the respective EPON interface, depending on 3634 the system action on such an alert. 3635 This object is applicable for an OLT and an ONU. At the 3636 OLT it has a distinct value for each virtual interface." 3637 ::= { dot3ExtPkgOptIfEntry 5 } 3639 dot3ExtPkgOptIfUpperInputPowerThreshold OBJECT-TYPE 3640 SYNTAX Integer32 3641 UNITS "0.1 dbm" 3642 MAX-ACCESS read-write 3643 STATUS current 3644 DESCRIPTION 3645 "The upper limit threshold on input power. If 3646 dot3ExtPkgOptIfInputPower reaches or exceeds this value, 3647 a Threshold Crossing Alert (TCA) should be sent. 3648 Reading will present the threshold value. Writing will 3649 set the value of the threshold. 3650 The write operation is not restricted in this document 3651 and can be done at any time. Changing 3652 dot3ExtPkgOptIfUpperInputPowerThreshold can lead to a Threshold 3653 Crossing Alert (TCA) being sent for the respective interface. 3654 This alert may be leading to an interruption of service of the 3655 users connected to the respective EPON interface, depending on 3656 the system action on such an alert. 3657 This object is applicable for an OLT and an ONU. At the 3658 OLT it has a distinct value for each virtual interface." 3659 ::= { dot3ExtPkgOptIfEntry 6 } 3661 dot3ExtPkgOptIfOutputPower OBJECT-TYPE 3662 SYNTAX Integer32 3663 UNITS "0.1 dbm" 3664 MAX-ACCESS read-only 3665 STATUS current 3666 DESCRIPTION 3667 "The optical power monitored at the output. 3668 This object is applicable for an OLT and an ONU. At the 3669 OLT it has a distinct value for each virtual interface." 3670 ::= { dot3ExtPkgOptIfEntry 7 } 3672 dot3ExtPkgOptIfLowOutputPower OBJECT-TYPE 3673 SYNTAX Integer32 3674 UNITS "0.1 dbm" 3675 MAX-ACCESS read-only 3676 STATUS current 3677 DESCRIPTION 3678 "The lowest optical power monitored at the output during the 3679 current 15-minute interval. 3680 This object is applicable for an OLT and an ONU. At the 3681 OLT it has a distinct value for each virtual interface." 3682 ::= { dot3ExtPkgOptIfEntry 8 } 3684 dot3ExtPkgOptIfHighOutputPower OBJECT-TYPE 3685 SYNTAX Integer32 3686 UNITS "0.1 dbm" 3687 MAX-ACCESS read-only 3688 STATUS current 3689 DESCRIPTION 3690 "The highest optical power monitored at the output during the 3691 current 15-minute interval. 3692 This object is applicable for an OLT and an ONU. At the 3693 OLT it has a distinct value for each virtual interface." 3694 ::= { dot3ExtPkgOptIfEntry 9 } 3696 dot3ExtPkgOptIfLowerOutputPowerThreshold OBJECT-TYPE 3697 SYNTAX Integer32 3698 UNITS "0.1 dbm" 3699 MAX-ACCESS read-write 3700 STATUS current 3701 DESCRIPTION 3702 "The lower limit threshold on output power. If 3703 dot3ExtPkgOptIfOutputPower drops to this value or below, 3704 a Threshold Crossing Alert (TCA) should be sent. 3705 Reading will present the threshold value. Writing will 3706 set the value of the threshold. 3707 The write operation is not restricted in this document 3708 and can be done at any time. Changing 3709 dot3ExtPkgOptIfLowerOutputPowerThreshold can lead to a Threshold 3710 Crossing Alert (TCA) being sent for the respective interface. 3711 This alert may be leading to an interruption of service of the 3712 users connected to the respective EPON interface, depending on 3713 the system action on such an alert. 3714 This object is applicable for an OLT and an ONU. At the 3715 OLT it has a distinct value for each virtual interface." 3716 ::= { dot3ExtPkgOptIfEntry 10 } 3718 dot3ExtPkgOptIfUpperOutputPowerThreshold OBJECT-TYPE 3719 SYNTAX Integer32 3720 UNITS "0.1 dbm" 3721 MAX-ACCESS read-write 3722 STATUS current 3723 DESCRIPTION 3724 "The upper limit threshold on output power. If 3725 dot3ExtPkgOptIfOutputPower reaches or exceeds this value, 3726 a Threshold Crossing Alert (TCA) should be sent. 3727 Reading will present the threshold value. Writing will 3728 set the value of the threshold. 3729 The write operation is not restricted in this document 3730 and can be done at any time. Changing 3731 dot3ExtPkgOptIfUpperOutputPowerThreshold can lead to a Threshold 3732 Crossing Alert (TCA) being sent for the respective interface. 3733 This alert may be leading to an interruption of service of the 3734 users connected to the respective EPON interface, depending on 3735 the system action on such an alert. 3736 This object is applicable for an OLT and an ONU. At the 3737 OLT it has a distinct value for each virtual interface." 3738 ::= { dot3ExtPkgOptIfEntry 11 } 3740 dot3ExtPkgOptIfSignalDetect OBJECT-TYPE 3741 SYNTAX TruthValue 3742 MAX-ACCESS read-only 3743 STATUS current 3744 DESCRIPTION 3745 "When getting true(1) there is a valid optical signal at 3746 the receive, that is above the optical power level for 3747 signal detection. When getting false(2) the optical 3748 signal at the receive is below the optical power level 3749 for signal detection. 3750 This object is applicable for an OLT and an ONU. At the 3751 OLT it has a distinct value for each virtual interface." 3752 DEFVAL { false } 3753 ::= { dot3ExtPkgOptIfEntry 12 } 3755 dot3ExtPkgOptIfTransmitAlarm OBJECT-TYPE 3756 SYNTAX TruthValue 3757 MAX-ACCESS read-only 3758 STATUS current 3759 DESCRIPTION 3760 "When getting true(1) there is a non-valid optical signal 3761 at the transmit of the interface, either a higher level 3762 or lower level than expected. When getting false(2) the 3763 optical signal at the transmit is valid and in the 3764 required range. 3765 This object is applicable for an OLT and an ONU. At the 3766 OLT it has a distinct value for each virtual interface." 3767 DEFVAL { false } 3768 ::= { dot3ExtPkgOptIfEntry 13 } 3770 dot3ExtPkgOptIfTransmitEnable OBJECT-TYPE 3771 SYNTAX TruthValue 3772 MAX-ACCESS read-write 3773 STATUS current 3774 DESCRIPTION 3775 "Setting this object to true(1) will cause the optical 3776 interface to start transmission (according to the 3777 control protocol specified for the logical interface). 3778 Setting this object to false(2) will cause the 3779 interface to stop the optical transmission. 3780 When getting true(1) the optical interface is in 3781 transmitting mode (obeying to the logical control 3782 protocol). 3783 When getting false(2) the optical interface is not in 3784 transmitting mode. 3785 The write operation is not restricted in this document 3786 and can be done at any time. Changing 3787 dot3ExtPkgOptIfTransmitEnable state can lead to a halt 3788 in the optical transmission of the respective interface 3789 leading to an interruption of service of the users 3790 connected to the respective EPON interface. 3791 The object is relevant when the admin state of the 3792 interface is active as set by the dot3MpcpAdminState. 3793 This object is applicable for an OLT and an ONU. At the 3794 OLT it has a distinct value for each virtual interface." 3795 DEFVAL { false } 3796 ::= { dot3ExtPkgOptIfEntry 14 } 3798 -- Conformance Statements 3800 -- Conformance Groups 3802 dot3EponGroups OBJECT IDENTIFIER ::= { dot3EponConformance 1 } 3804 dot3MpcpGroupBase OBJECT-GROUP 3805 OBJECTS { 3806 dot3MpcpOperStatus, 3807 dot3MpcpAdminState, 3808 dot3MpcpMode, 3809 dot3MpcpSyncTime, 3810 dot3MpcpLinkID, 3811 dot3MpcpRemoteMACAddress, 3812 dot3MpcpRegistrationState, 3813 dot3MpcpMaximumPendingGrants, 3814 dot3MpcpTransmitElapsed, 3815 dot3MpcpReceiveElapsed, 3816 dot3MpcpRoundTripTime 3818 } 3819 STATUS current 3820 DESCRIPTION 3821 "A collection of objects of dot3 Mpcp Control entity state 3822 definition. Objects are per LLID." 3823 ::= { dot3EponGroups 1 } 3825 dot3MpcpGroupStat OBJECT-GROUP 3826 OBJECTS { 3827 dot3MpcpMACCtrlFramesTransmitted, 3828 dot3MpcpMACCtrlFramesReceived, 3829 dot3MpcpDiscoveryWindowsSent, 3830 dot3MpcpDiscoveryTimeout , 3831 dot3MpcpTxRegRequest, 3832 dot3MpcpRxRegRequest, 3833 dot3MpcpTxRegAck, 3834 dot3MpcpRxRegAck, 3835 dot3MpcpTxReport, 3836 dot3MpcpRxReport, 3837 dot3MpcpTxGate, 3838 dot3MpcpRxGate, 3839 dot3MpcpTxRegister, 3840 dot3MpcpRxRegister 3841 } 3842 STATUS current 3843 DESCRIPTION 3844 "A collection of objects of dot3 Mpcp Statistics. 3845 Objects are per LLID." 3846 ::= { dot3EponGroups 2 } 3848 dot3OmpeGroupID OBJECT-GROUP 3849 OBJECTS { 3850 dot3OmpEmulationType 3852 } 3853 STATUS current 3854 DESCRIPTION 3855 "A collection of objects of dot3 OMP emulation entity 3856 state definition. Objects are per LLID." 3857 ::= { dot3EponGroups 3 } 3859 dot3OmpeGroupStat OBJECT-GROUP 3860 OBJECTS { 3861 dot3OmpEmulationSLDErrors, 3862 dot3OmpEmulationCRC8Errors, 3863 dot3OmpEmulationBadLLID, 3864 dot3OmpEmulationGoodLLID, 3865 dot3OmpEmulationOnuPonCastLLID, 3866 dot3OmpEmulationOltPonCastLLID, 3867 dot3OmpEmulationBroadcastBitNotOnuLlid, 3868 dot3OmpEmulationOnuLLIDNotBroadcast, 3869 dot3OmpEmulationBroadcastBitPlusOnuLlid, 3870 dot3OmpEmulationNotBroadcastBitNotOnuLlid 3871 } 3872 STATUS current 3873 DESCRIPTION 3874 "A collection of objects of dot3 OMP emulation 3875 Statistics. Objects are per LLID." 3876 ::= { dot3EponGroups 4 } 3878 dot3EponFecGroupAll OBJECT-GROUP 3879 OBJECTS { 3880 dot3EponFecPCSCodingViolation, 3881 dot3EponFecAbility, 3882 dot3EponFecMode, 3883 dot3EponFecCorrectedBlocks, 3884 dot3EponFecUncorrectableBlocks, 3885 dot3EponFecBufferHeadCodingViolation 3886 } 3887 STATUS current 3888 DESCRIPTION 3889 "A collection of objects of dot3 FEC group control and 3890 statistics. Objects are per LLID." 3891 ::= { dot3EponGroups 5 } 3893 dot3ExtPkgGroupControl OBJECT-GROUP 3894 OBJECTS { 3895 dot3ExtPkgObjectReset, 3896 dot3ExtPkgObjectPowerDown, 3897 dot3ExtPkgObjectNumberOfLLIDs, 3898 dot3ExtPkgObjectFecEnabled, 3899 dot3ExtPkgObjectReportMaximumNumQueues, 3900 dot3ExtPkgObjectRegisterAction 3901 } 3902 STATUS current 3903 DESCRIPTION 3904 "A collection of objects of dot3ExtPkg control 3905 definition. Objects are per LLID." 3906 ::= { dot3EponGroups 6 } 3908 dot3ExtPkgGroupQueue OBJECT-GROUP 3909 OBJECTS { 3910 dot3ExtPkgObjectReportNumThreshold, 3911 dot3ExtPkgObjectReportMaximumNumThreshold, 3912 dot3ExtPkgStatTxFramesQueue, 3913 dot3ExtPkgStatRxFramesQueue, 3914 dot3ExtPkgStatDroppedFramesQueue 3915 } 3916 STATUS current 3917 DESCRIPTION 3918 "A collection of objects of dot3ExtPkg Queue 3919 control. Objects are per LLID, per queue." 3920 ::= { dot3EponGroups 7 } 3922 dot3ExtPkgGroupQueueSets OBJECT-GROUP 3923 OBJECTS { 3924 dot3ExtPkgObjectReportThreshold 3925 } 3926 STATUS current 3927 DESCRIPTION 3928 "A collection of objects of dot3ExtPkg queue_set 3929 control. Objects are per LLID, per queue, per 3930 queue_set." 3931 ::= { dot3EponGroups 8 } 3933 dot3ExtPkgGroupOptIf OBJECT-GROUP 3934 OBJECTS { 3935 dot3ExtPkgOptIfSuspectedFlag, 3936 dot3ExtPkgOptIfInputPower, 3937 dot3ExtPkgOptIfLowInputPower, 3938 dot3ExtPkgOptIfHighInputPower, 3939 dot3ExtPkgOptIfLowerInputPowerThreshold, 3940 dot3ExtPkgOptIfUpperInputPowerThreshold, 3941 dot3ExtPkgOptIfOutputPower, 3942 dot3ExtPkgOptIfLowOutputPower, 3943 dot3ExtPkgOptIfHighOutputPower, 3944 dot3ExtPkgOptIfLowerOutputPowerThreshold, 3945 dot3ExtPkgOptIfUpperOutputPowerThreshold, 3946 dot3ExtPkgOptIfSignalDetect, 3947 dot3ExtPkgOptIfTransmitAlarm, 3948 dot3ExtPkgOptIfTransmitEnable 3949 } 3950 STATUS current 3951 DESCRIPTION 3952 "A collection of objects of control and status indication 3953 of the optical interface. 3954 Objects are per LLID." 3956 ::= { dot3EponGroups 9 } 3958 -- Compliance 3960 dot3EponCompliances 3961 OBJECT IDENTIFIER ::= { dot3EponConformance 2 } 3963 dot3MPCPCompliance MODULE-COMPLIANCE 3964 STATUS current 3965 DESCRIPTION "The compliance statement for Multi-Point 3966 control protocol interfaces." 3968 MODULE -- this module 3969 MANDATORY-GROUPS { dot3MpcpGroupBase} 3971 GROUP dot3MpcpGroupStat 3972 DESCRIPTION "This group is mandatory for all MPCP supporting 3973 interfaces for statistics collection." 3974 ::= { dot3EponCompliances 1} 3976 dot3OmpeCompliance MODULE-COMPLIANCE 3977 STATUS current 3978 DESCRIPTION "The compliance statement for OMPEmulation 3979 interfaces." 3981 MODULE -- this module 3982 MANDATORY-GROUPS { dot3OmpeGroupID} 3984 GROUP dot3OmpeGroupStat 3985 DESCRIPTION "This group is mandatory for all OMPemulation 3986 supporting interfaces for statistics collection." 3988 ::= { dot3EponCompliances 2} 3990 dot3EponFecCompliance MODULE-COMPLIANCE 3991 STATUS current 3992 DESCRIPTION "The compliance statement for FEC EPON interfaces. 3993 This group is mandatory for all FEC supporting 3994 interfaces for control and statistics collection." 3996 MODULE -- this module 3997 MANDATORY-GROUPS { dot3EponFecGroupAll } 3999 ::= { dot3EponCompliances 3} 4001 dot3ExtPkgCompliance MODULE-COMPLIANCE 4002 STATUS current 4003 DESCRIPTION "The compliance statement for EPON Interfaces 4004 using the extended package." 4005 MODULE -- this module 4006 MANDATORY-GROUPS { dot3ExtPkgGroupControl } 4008 GROUP dot3ExtPkgGroupQueue 4009 DESCRIPTION " This group is mandatory for all EPON interfaces 4010 supporting REPORT queue management of the extended 4011 package." 4013 GROUP dot3ExtPkgGroupQueueSets 4014 DESCRIPTION " This group is mandatory for all EPON interfaces 4015 supporting REPORT queue_sets management of the 4016 extended package." 4018 GROUP dot3ExtPkgGroupOptIf 4019 DESCRIPTION "This group is mandatory for all EPON interfaces 4020 supporting optical interfaces management, 4021 of the extended package." 4023 ::= { dot3EponCompliances 4} 4025 END 4027 6. IANA Considerations 4029 The DOT3-EPON-MIB module requires the allocation of a single object 4030 identifier for its MODULE-IDENTITY under the MIB-2 tree. 4032 The MIB module in this document uses the following IANA-assigned 4033 OBJECT IDENTIFIER values recorded in the SMI Numbers registry: 4035 Descriptor OBJECT IDENTIFIER value 4036 ---------- ----------------------- 4038 dot3EponMIB { mib-2 XXX } 4040 Editor's Note (to be removed prior to publication): the IANA is 4041 requested to assign a value for "XXX" under the 'mib-2' subtree and 4042 to record the assignment in the SMI Numbers registry. When the 4043 assignment has been made, the RFC Editor is asked to replace "XXX" 4044 (here and in the MIB module) with the assigned value and to remove 4045 this note. 4047 7. Acknowledgements 4049 This document is the result of the efforts of the HUBMIB Working 4050 Group. Some special thanks to Dan Romascanu who was WG chair during 4051 most of the development of this document, and who did carefully 4052 review and comment on the initial draft documents. Also some special 4053 thanks to Bert Wijnen who is the current WG chair for his review and 4054 comment on the final stages of this document. 4056 Also special thanks are due to David Perkins for his detailed and 4057 helpful MIB Doctor review of this document. 4059 Also some special thanks to some of IEEE802.3ah Working Group people 4060 for their contribution and additional reviews of the document. 4062 8. Security Considerations 4064 There are number of managed objects defined in this MIB module that 4065 have a MAX-ACCESS clause of read-write or read-create. Writing to 4066 these objects can have potentially disruptive effects on network 4067 operation: Including: 4069 Changing dot3MpcpAdminState state can lead to disabling the Multi- 4070 point control protocol on the respective interface leading to the 4071 interruption of service of the users connected to the respective EPON 4072 interface. 4074 Changing dot3EponFecMode state can lead to disabling the Forward 4075 error correction on the respective interface which can lead to a 4076 degradation of the optical link and therefore may lead to an 4077 interruption of service of the users connected to the respective EPON 4078 interface. 4080 Changing dot3ExtPkgObjectReset state can lead to a reset of the 4081 respective interface leading to an interruption of service of the 4082 users connected to the respective EPON interface. 4084 Changing dot3ExtPkgObjectPowerDown state can lead to a power down of 4085 the respective interface leading to an interruption of service of the 4086 users connected to the respective EPON interface. 4088 Changing dot3ExtPkgObjectFecEnabled state can lead to disabling the 4089 Forward error correction on the respective interface which can lead 4090 to a degradation of the optical link and therefore may lead to an 4091 interruption of service of the users connected to the respective EPON 4092 interface. 4094 Changing dot3ExtPkgObjectRegisterAction state can lead to a change in 4095 the registration state of the respective interface leading to a 4096 deregistration and an interruption of service of the users connected 4097 to the respective EPON interface. 4099 Changing dot3ExtPkgObjectReportNumThreshold can lead to a change in 4100 the reporting of the ONU interface and therefore to a change in the 4101 bandwidth allocation of the respective interface. This change may 4102 lead a degradation or an interruption of service of the users 4103 connected to the respective EPON interface. 4105 Changing dot3ExtPkgObjectReportThreshold can lead to a change in the 4106 reporting of the ONU interface and therefore to a change in the 4107 bandwidth allocation of the respective interface. This change may 4108 lead a degradation or an interruption of service of the users 4109 connected to the respective EPON interface. 4111 Changing dot3ExtPkgOptIfLowerInputPowerThreshold can lead to a 4112 Threshold Crossing Alert (TCA) being sent for the respective 4113 interface. This alert may be leading to an interruption of service 4114 of the users connected to the respective EPON interface, depending on 4115 the system action on such an alert. 4117 Changing dot3ExtPkgOptIfUpperInputPowerThreshold can lead to a 4118 Threshold Crossing Alert (TCA) being sent for the respective 4119 interface. This alert may be leading to an interruption of service 4120 of the users connected to the respective EPON interface, depending on 4121 the system action on such an alert. 4123 Changing dot3ExtPkgOptIfLowerOutputPowerThreshold can lead to a 4124 Threshold Crossing Alert (TCA) being sent for the respective 4125 interface. This alert may be leading to an interruption of service 4126 of the users connected to the respective EPON interface, depending on 4127 the system action on such an alert. 4129 Changing dot3ExtPkgOptIfUpperOutputPowerThreshold can lead to a 4130 Threshold Crossing Alert (TCA) being sent for the respective 4131 interface. This alert may be leading to an interruption of service 4132 of the users connected to the respective EPON interface, depending on 4133 the system action on such an alert. 4135 Changing dot3ExtPkgOptIfTransmitEnable state can lead to a halt in 4136 the optical transmission of the respective interface leading to an 4137 interruption of service of the users connected to the respective EPON 4138 interface. 4140 The user of this MIB module must therefore be aware that support for 4141 SET operations in a non-secure environment without proper protection 4142 can have a negative effect on network operations. 4144 The readable objects in this MIB module (i.e., those with MAX-ACCESS 4145 other than not-accessible) may be considered sensitive in some 4146 environments since, collectively, they provide information about the 4147 performance of network interfaces and can reveal some aspects of 4148 their configuration. In such environments it is important to control 4149 even GET and NOTIFY access to these objects and possibly even to 4150 encrypt their values when sending them over the network via SNMP. 4152 SNMP versions prior to SNMPv3 did not include adequate security. 4153 Even if the network itself is secure (for example by using IPSec), 4154 even then, there is no control as to who on the secure network is 4155 allowed to access and GET/SET (read/change/create/delete) the objects 4156 in this MIB module. 4158 It is RECOMMENDED that implementers consider the security features as 4159 provided by the SNMPv3 framework (see [RFC3410], section 8), 4160 including full support for the SNMPv3 cryptographic mechanisms (for 4161 authentication and privacy). 4163 Further, deployment of SNMP versions prior to SNMPv3 is NOT 4164 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 4165 enable cryptographic security. It is then a customer/operator 4166 responsibility to ensure that the SNMP entity giving access to an 4167 instance of this MIB module is properly configured to give access to 4168 the objects only to those principals (users) that have legitimate 4169 rights to indeed GET or SET (change/create/delete) them. 4171 9. References 4173 9.1. Normative References 4175 [802.1d] IEEE, "Institute of Electrical and Electronic Engineers, 4176 802.1D-2004, IEEE Standard for Local and metropolitan area 4177 networks Media Access Control (MAC) Bridges.", June 2004. 4179 [802.3] IEEE, "Institute of Electrical and Electronic Engineers, 4180 IEEE Std 802.3-2002, "IEEE Standard for Carrier Sense 4181 Multiple Access with Collision Detection (CSMA/CD) Access 4182 Method and Physical Layer Specifications.", December 2002. 4184 [802.3ah] IEEE, "Institute of Electrical and Electronic Engineers, 4185 IEEE Std 802.3ah-2004. Information technology - 4186 Telecommunications and information exchange between 4187 systems - Local and metropolitan area networks - Specific 4188 requirements - Part 3: Carrier sense multiple access with 4189 collision detection (CSMA/CD) access method and physical 4190 layer specifications - Media Access Control Parameters, 4191 Physical Layers and Management Parameters for subscriber 4192 access networks.", IEEE Std 802.3ah-2004, October 2004. 4194 [ITU-T G.975] 4195 ITU, "ITU-T, SERIES G: TRANSMISSION SYSTEMS AND MEDIA, 4196 DIGITAL SYSTEMS AND NETWORKS Digital sections and digital 4197 line system - Optical fibre submarine cable systems 4198 Forward error correction for submarine systems, ITU-T 4199 Recommendation G.975", October 2000. 4201 [ITU-T G.983] 4202 ITU, "ITU-T, SERIES G: TRANSMISSION SYSTEMS AND MEDIA, 4203 DIGITAL SYSTEMS AND NETWORKS, Digital transmission systems 4204 - Digital sections and digital line system - Optical line 4205 systems for local and access networks Broadband optical 4206 access systems based on Passive Optical Networks (PON), 4207 ITU-T Recommendation G.983.1", October 1998. 4209 [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. 4210 Schoenwaelder, Ed., "Structure of Management Information 4211 Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. 4213 [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. 4214 Schoenwaelder, Ed., "Textual Conventions for SMIv2", 4215 STD 58, RFC 2579, April 1999. 4217 [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, 4218 "Conformance Statements for SMIv2", STD 58, RFC 2580, 4219 April 1999. 4221 [RFC2863] McCloghrie, K. and F. Kastenholz, "The Interfaces Group 4222 MIB", RFC 2863, June 2000. 4224 [RFC2864] McCloghrie, K. and G. Hanson, "The Inverted Stack Table 4225 Extension to the Interfaces Group MIB", RFC 2864, 4226 June 2000. 4228 [RFC3635] Flick, J., "Definitions of Managed Objects for the 4229 Ethernet-like Interface Types", RFC 3635, September 2003. 4231 [RFC3636] Flick, J., "Definitions of Managed Objects for IEEE 802.3 4232 Medium Attachment Units (MAUs)", RFC 3636, September 2003. 4234 [RFC3636bis-03] 4235 Beili, E., "Definitions of Managed Objects for IEEE 802.3 4236 Medium Attachment Units (MAUs) 4237 draft-ietf-hubmib-rfc3636bis-03.txt", 4238 draft-ietf-hubmib-rfc3636bis-03.txt (work in progress), 4239 June 2006. 4241 9.2. Informative References 4243 [I-D.ietf-hubmib-efm-mib] 4244 Squire, M., "Definitions and Managed Objects for OAM 4245 Functions on Ethernet Like Interfaces", 4246 draft-ietf-hubmib-efm-mib-04 (work in progress), 4247 March 2006. 4249 [RFC1525] Decker, E., McCloghrie, K., Langille, P., and A. 4250 Rijsinghani, "Definitions of Managed Objects for Source 4251 Routing Bridges", RFC 1525, September 1993. 4253 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 4254 Requirement Levels", BCP 14, RFC 2119, March 1997. 4256 [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, 4257 "Introduction and Applicability Statements for Internet- 4258 Standard Management Framework", RFC 3410, December 2002. 4260 [RFC4188] Norseth, K. and E. Bell, "Definitions of Managed Objects 4261 for Bridges", RFC 4188, September 2005. 4263 Author's Address 4265 Lior Khermosh 4266 PMC-SIERRA 4267 Kohav Hertzelia bldg, 4268 4 Hasadnaot St., 4269 Hertzliya Pituach, 46120 4270 ISRAEL 4272 Phone: +972-9-9628000 Ext: 302 4273 Fax: +972-9-9628001 4274 Email: lior_khermosh@pmc-sierra.com 4276 Full Copyright Statement 4278 Copyright (C) The IETF Trust (2006). 4280 This document is subject to the rights, licenses and restrictions 4281 contained in BCP 78, and except as set forth therein, the authors 4282 retain all their rights. 4284 This document and the information contained herein are provided on an 4285 "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS 4286 OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY, THE IETF TRUST AND 4287 THE INTERNET ENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS 4288 OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF 4289 THE INFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED 4290 WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 4292 Intellectual Property 4294 The IETF takes no position regarding the validity or scope of any 4295 Intellectual Property Rights or other rights that might be claimed to 4296 pertain to the implementation or use of the technology described in 4297 this document or the extent to which any license under such rights 4298 might or might not be available; nor does it represent that it has 4299 made any independent effort to identify any such rights. Information 4300 on the procedures with respect to rights in RFC documents can be 4301 found in BCP 78 and BCP 79. 4303 Copies of IPR disclosures made to the IETF Secretariat and any 4304 assurances of licenses to be made available, or the result of an 4305 attempt made to obtain a general license or permission for the use of 4306 such proprietary rights by implementers or users of this 4307 specification can be obtained from the IETF on-line IPR repository at 4308 http://www.ietf.org/ipr. 4310 The IETF invites any interested party to bring to its attention any 4311 copyrights, patents or patent applications, or other proprietary 4312 rights that may cover technology that may be required to implement 4313 this standard. Please address the information to the IETF at 4314 ietf-ipr@ietf.org. 4316 Acknowledgment 4318 Funding for the RFC Editor function is provided by the IETF 4319 Administrative Support Activity (IASA).