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