draft-ietf-hubmib-efm-epon-mib-04.txt   draft-ietf-hubmib-efm-epon-mib-05.txt 
EPON MIB WG L. Khermosh EPON MIB WG L. Khermosh
Internet-Draft Passave Technologies Internet-Draft PMC-SIERRA
Expires: August 14, 2006 February 10, 2006 Expires: January 24, 2007 July 23, 2006
Managed Objects of EPON Managed Objects of EPON
draft-ietf-hubmib-efm-epon-mib-04.txt draft-ietf-hubmib-efm-epon-mib-05.txt
Status of this Memo Status of this Memo
By submitting this Internet-Draft, each author represents that any By submitting this Internet-Draft, each author represents that any
applicable patent or other IPR claims of which he or she is aware applicable patent or other IPR claims of which he or she is aware
have been or will be disclosed, and any of which he or she becomes have been or will be disclosed, and any of which he or she becomes
aware will be disclosed, in accordance with Section 6 of BCP 79. aware will be disclosed, in accordance with Section 6 of BCP 79.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
skipping to change at page 1, line 33 skipping to change at page 1, line 33
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt. http://www.ietf.org/ietf/1id-abstracts.txt.
The list of Internet-Draft Shadow Directories can be accessed at The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html. http://www.ietf.org/shadow.html.
This Internet-Draft will expire on August 14, 2006. This Internet-Draft will expire on January 24, 2007.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (2006). Copyright (C) The Internet Society (2006).
Abstract Abstract
This document defines a portion of the Management Information Base This document defines a portion of the Management Information Base
(MIB) for use with network management protocols in TCP/IP based (MIB) for use with network management protocols in TCP/IP based
Internets. In particular, it defines objects for managing for Internets. In particular, it defines objects for managing interfaces
generic point to multi-point (P2MP) networks, and in specifically that conform to the Ethernet Passive Optical Networks (EPON) standard
Ethernet Passive Optical Networks (EPON) interfaces, defined in IEEE as defined in [802.3ah], which are extended capabilities to the
Std 802.3ah-2004, which amends IEEE Std 802.3-2002. Ethernet like interfaces.
The Internet-Standard Management Framework The Internet-Standard Management Framework
For a detailed overview of the documents that describe the current For a detailed overview of the documents that describe the current
Internet-Standard Management Framework, please refer to section 7 of Internet-Standard Management Framework, please refer to section 7 of
RFC 3410 [RFC3410]. Managed objects are accessed via a virtual RFC 3410 [RFC3410]. Managed objects are accessed via a virtual
information store, termed the Management Information Base or MIB. information store, termed the Management Information Base or MIB.
MIB objects are generally accessed through the Simple Network MIB objects are generally accessed through the Simple Network
Management Protocol (SNMP). Objects in the MIB are defined using the Management Protocol (SNMP). Objects in the MIB are defined using the
mechanisms defined in the Structure of Management Information (SMI). mechanisms defined in the Structure of Management Information (SMI).
This memo specifies a MIB module that is compliant to the SMIv2, This memo specifies a MIB module that is compliant to the SMIv2,
which is described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 which is described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579
[RFC2579] and STD 58, RFC 2580 [RFC2580]. [RFC2579] and STD 58, RFC 2580 [RFC2580].
Terminology Terminology
Key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in [RFC2119]. document are to be interpreted as described in [RFC2119].
Table of Contents Table of Contents
1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.1. Terminology and abbreviations . . . . . . . . . . . . . . 4 1.1. Terminology and abbreviations . . . . . . . . . . . . . . 4
1.2. EPON architecture highlights . . . . . . . . . . . . . . . 5 1.2. EPON architecture highlights . . . . . . . . . . . . . . . 5
1.2.1. Introduction . . . . . . . . . . . . . . . . . . . . . 5 1.2.1. Introduction . . . . . . . . . . . . . . . . . . . . . 5
1.2.2. Principles of operation . . . . . . . . . . . . . . . 6 1.2.2. Principles of operation . . . . . . . . . . . . . . . 7
1.2.3. The physical media . . . . . . . . . . . . . . . . . . 7 1.2.3. The physical media . . . . . . . . . . . . . . . . . . 8
1.2.4. PMD specifications . . . . . . . . . . . . . . . . . . 8 1.2.4. PMD specifications . . . . . . . . . . . . . . . . . . 9
1.2.5. Point to point emulation . . . . . . . . . . . . . . . 8 1.2.5. Point to point emulation . . . . . . . . . . . . . . . 9
1.2.6. MPCP principles . . . . . . . . . . . . . . . . . . . 9 1.2.6. Principles of the MPCP . . . . . . . . . . . . . . . . 11
1.2.7. Forward Error correction (FEC) . . . . . . . . . . . . 11 1.2.7. Forward Error correction (FEC) . . . . . . . . . . . . 14
1.3. Management architecture . . . . . . . . . . . . . . . . . 12 1.3. Management architecture . . . . . . . . . . . . . . . . . 14
2. MIB structure . . . . . . . . . . . . . . . . . . . . . . . . 18 2. MIB structure . . . . . . . . . . . . . . . . . . . . . . . . 19
3. Relation to other MIB Modules . . . . . . . . . . . . . . . . 19 3. Relation to other MIB Modules . . . . . . . . . . . . . . . . 25
3.1. Relation to the Interfaces MIB and Ethernet-like 3.1. Relation to the Interfaces MIB and Ethernet-like
Interfaces MIB . . . . . . . . . . . . . . . . . . . . . . 19 Interfaces MIB . . . . . . . . . . . . . . . . . . . . . . 25
3.2. Relation to the IEEE 802.3 MAU MIBs . . . . . . . . . . . 23 3.2. Relation to the IEEE 802.3 MAU MIBs . . . . . . . . . . . 32
3.3. Relation to the EFM OAM MIB . . . . . . . . . . . . . . . 24 3.3. Relation to the EFM OAM MIB . . . . . . . . . . . . . . . 32
3.4. Relation to the bridge MIB . . . . . . . . . . . . . . . . 24 3.4. Relation to the bridge MIB . . . . . . . . . . . . . . . . 33
4. Relation table of the dot3EPON MIB module objects to the 4. Mapping of IEEE 802.3ah Managed Objects . . . . . . . . . . . 34
IEEE802.3ah attributes . . . . . . . . . . . . . . . . . . . . 25 5. Definitions - The DOT3 EPON MIB module . . . . . . . . . . . . 38
5. Definitions - The DOT3 EPON MIB module . . . . . . . . . . . . 29 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 89
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 70 7. Security Considerations . . . . . . . . . . . . . . . . . . . 90
7. Security Considerations . . . . . . . . . . . . . . . . . . . 71 8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 92
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 73 8.1. Normative References . . . . . . . . . . . . . . . . . . . 92
8.1. Normative References . . . . . . . . . . . . . . . . . . . 73 8.2. Informative References . . . . . . . . . . . . . . . . . . 93
8.2. Informative References . . . . . . . . . . . . . . . . . . 73 Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 94
Author's Address . . . . . . . . . . . . . . . . . . . . . . . . . 75 Intellectual Property and Copyright Statements . . . . . . . . . . 95
Intellectual Property and Copyright Statements . . . . . . . . . . 76
1. Overview 1. Overview
This document defines a portion of the Management Information Base This document defines a portion of the Management Information Base
(MIB) for use with network management protocols in TCP/IP based (MIB) for use with network management protocols in TCP/IP based
Internets. In particular, it defines objects for managing interfaces Internets. In particular, it defines objects for managing interfaces
that conform to the Ethernet Passive Optical Networks (EPON) standard that conform to the Ethernet Passive Optical Networks (EPON) standard
as defined in [802.3ah], which are extended capabilities to the as defined in [802.3ah], which are extended capabilities to the
Ethernet like interfaces. The document contains a list of management Ethernet like interfaces. The document contains a list of management
entities based on the attributes defined in [802.3ah] Annex 30A for objects based on the attributes defined in the relevant parts of
the EPON section. [802.3ah] Annex 30A, referring to EPON.
1.1. Terminology and abbreviations 1.1. Terminology and abbreviations
ACK - Acknowledge
BER - Bit Error Rate BER - Bit Error Rate
BW - Bandwidth BW - Bandwidth
CO - Central Office CO - Central Office
CPE - Central Premises Equipment CPE - Customer Premises Equipment
CRC - Cyclic Redundancy Check
FCS - Frame Check Sequence FCS - Frame Check Sequence
FEC - Forward Error Correction
EFM - Ethernet First Mile EFM - Ethernet First Mile
EPON - Ethernet Passive Optical Network EPON - Ethernet Passive Optical Network
LLID - Logical Link IDentifier GMII - Gigabit Media Independent Interface
LAN - Local Area Network
LLID - Logical Link Identifier
MAC - Media Access Control MAC - Media Access Control
Mbps - Mega-bit per second
MDI - Medium Dependent Interface
MDIO - Management Data Input/Output
MPCP - Multi-Point Control Protocol MPCP - Multi-Point Control Protocol
MP2PE - Multi-Point to Point Emulation
OAM - Operation Administration Maintenance OAM - Operation Administration Maintenance
OLT - Optical Line Terminal (Server unit of the EPON) OLT - Optical Line Terminal (Server unit of the EPON)
OMP - Optical Multi-Point
ONU - Optical Network Unit (Client unit of the EPON) ONU - Optical Network Unit (Client unit of the EPON)
P2PE - Point to Point Emulation
P2MP - Point to Multi-Point
PCS - Physical Coding Sublayer
PHY - Physical Layer PHY - Physical Layer
PMD - Physical Medium Dependant PMD - Physical Medium Dependent
PMA - Physical Medium Attachment
PON - Passive Optical Network
RTT - Round Trip Time RTT - Round Trip Time
RS - Reconciliation Sublayer
SLA - Service Level Agreement SLA - Service Level Agreement
SLD - Start of LLID Delimiter
TDM - Time Division Multiplexing TDM - Time Division Multiplexing
TQ - Time Quanta
1.2. EPON architecture highlights 1.2. EPON architecture highlights
1.2.1. Introduction 1.2.1. Introduction
The EPON standard, as defined in [802.3ah], is defining the Layer 1 The EPON standard, as defined in [802.3ah], is defining the physical
(Physical media) and layer 2 (media access) interfaces for the media (Layer 1) and media access (layer 2) of the EPON interface.
Ethernet passive optical networks. The EPON is a Gigabit Ethernet The EPON is a variant of the Gigabit Ethernet protocol for the
protocol for the Optical Access based on passive optical splitting Optical Access. The Optical Access topology is based on passive
(PON) topology. A Passive Optical Network (PON) is a single, shared optical splitting topology. The link of a Passive Optical Network
optical fiber that uses optical passive splitters to divide the (PON) is based on a single, shared optical fiber with passive optical
single fiber into separate subscribers. splitters dividing the single fiber into separate subscribers.
Server unit - Optical Line Terminal (OLT). The equipment at the CO.
Client Unit - Optical Network Unit (ONU). The equipment at the CPE. The Optical Line Terminal (OLT) is the server unit of the network,
located at the Central Office (CO).
Standard is IEEE802.3ah. The Optical Network Unit (ONU) is the client unit of the network,
located at the Customer Premises Equipment (CPE).
The following diagram describes the PON topology: The following diagram describes the PON topology:
Device with Device with
one or more P2MP one or more P2MP
interfaces such as OLT interfaces such as OLT
for EPON An EPON IP host for EPON An EPON IP host
------- OLT ONU "modem" -------- ------- OLT ONU "modem" --------
Other IEEE | | interface | interface ------ Other IEEE| | Other IEEE | | interface | interface ------ Other IEEE| |
interface | |-------\----------------| | interface | | interface | |-------\----------------| | interface | |
===========| | \ | |===========| | ===========| | \ | |===========| |
| | \ ------ -------- | | \ ------ --------
| | \ ------ -------- | | \ ------ --------
. . \------------| | | | . . \------------| | | |
| |------\ | |===========| | | |------\ | |===========| |
| | \ ------ -------- | | \ ------ --------
------- \ etc ------- \ etc
The architecture positioning is defined in the [802.3ah] Figure 56.2 The IEEE layering architecture of an EPON interface is defined in the
diagram. The [802.3ah] defines the following clauses for the network diagram of figure 56.2 [802.3ah]. The following clauses in the
operation. [802.3ah] define the corresponding layers of an EPON interface:
Clause 30 - management Clause 30 - management
Clause 60 - PMD for the EPON media (Burst PMD) Clause 60 - PMD for EPON media (Burst PMD)
Clause 64 - MPCP (Multipoint control protocol) - defines the media
access for the operation of the multipoint architecture of the EPON. Clause 64 - MPCP (Multipoint control protocol) - defines the
multipoint architecture, and control protocol for the media access of
EPON.
Clause 65 - Clause 65 -
a) Virtual links for the EPON a) Virtual links definition for the EPON
b) FEC b) FEC
c) PMA for the EPON. c) PMA for the EPON.
1.2.2. Principles of operation 1.2.2. Principles of operation
The EPON protocol is based on the gigabit Ethernet protocol of the The specification of the EPON interface is based on the specification
IEEE as described in [802.3ah] clause 35 and 36. The interface to of the gigabit Ethernet interface as described in [802.3] clause 35
the MAC is through the GMII I/F as described in clause 35 and the PCS and 36. The Ethernet MAC is working in gigabit rate. The media
layer is based on the gigabit Ethernet clause 36. The MPCP is placed interface to the MAC is through the GMII interface as described in
in the MAC control layer. The Emulation layer, located at the RS clause 35 and the PCS layer is based on the gigabit Ethernet PCS as
(Reconciliation Sublayer), creates virtual private path to each ONU described in clause 36. The special EPON layers are added to the
and the FEC enhances reach and split performance. Ethernet layering in the following places:
The following diagram describes the layering: The MPCP is placed in the MAC control layer, providing the EPON
control protocol. The Emulation layer, located at the RS
(Reconciliation Sublayer), creates virtual private path to each ONU.
The FEC layer is located between the PCS and PMA layers, enhancing
reach and split performance of the optical link.
The following diagram describes the layering model of an EPON
interface:
+==========================================+ +==========================================+
| Higher layers | | Higher layers |
+==========================================+ +==========================================+
| 802.1D Bridge | | 802.1D Bridge |
+==========================================+ +==========================================+
| MAC client| ... |MAC client| | MAC client| ... |MAC client|
+==========================================+ +==========================================+
| MAC Control - (MPCP) | *NEW* | MAC Control - (MPCP) | *NEW*
+==========================================+ +==========================================+
skipping to change at page 7, line 28 skipping to change at page 8, line 29
| P2P Emulation (P2PE) | *NEW* | P2P Emulation (P2PE) | *NEW*
+==========================================+ +==========================================+
| | | |
| GMII | | GMII |
| | | |
+==========================================+ +==========================================+
| PCS | | PCS |
+==========================================+ +==========================================+
| FEC | *NEW* | FEC | *NEW*
+==========================================+ +==========================================+
| PMA | | PMA | *Enhanced parameters
+==========================================+ +==========================================+ for EPON*
| PMD | | PMD | *Enhanced parameters
+==========================================+ +==========================================+ for EPON*
| | | |
| MDI | | MDI |
| | | |
/===================/ /===================/
/ Media / / Media /
/===================/ /===================/
1.2.3. The physical media 1.2.3. The physical media
Uplink and downlink are multiplexed using separated wavelengths on The physical link is a fiber optical link. The OLT and ONUs are
the same fiber. The Downlink is a broadcast media where the OLT connected through passive optical splitters. Downlink denotes the
transmits the data to all ONUs. The uplink is a shared transmission transmission from the OLT to the ONUs. Uplink denotes the
media for all of the ONUs. The uplink multiplexing access is based transmission from the ONUs to the OLT. Uplink and downlink are
on time division (TDM) and the management of the TDM access is multiplexed using separated wavelengths on the same fiber. The
defined in the Multi-Point control protocol (MPCP). The upstream downlink is a broadcast medium where the OLT transmits the data to
collisions are avoided through the transmission coordination done by all ONUs. The uplink is a shared transmission medium for all of the
the MPCP protocol. The transmission is of one ONU at a time. The ONUs. The uplink access is based on time division multiplexing (TDM)
OLT send control messages (GATE messages) allowing ONUs to transmit, and the management of the TDM media access is defined by the Multi-
defining when the transmission occurs and what is its duration. Point control protocol (MPCP). The MPCP is a control protocol based
These messages define the transmission order and the amount of BW for on an inband packet messaging. The OLT sends control messages (GATE
each ONU. A scheduling algorithm at the OLT, which is not defined, messages) allowing ONUs to transmit, defining when the transmission
in the [802.3ah] is responsible to divide the BW and control the occurs and what is its duration. These messages define the
delay of each ONU according to its SLA. transmission order and the amount of BW for each ONU. A scheduling
algorithm at the OLT, which is not defined in the [802.3ah], is
responsible of allocating the BW and controlling the delay of each
ONU according to its SLA.
1.2.4. PMD specifications 1.2.4. PMD specifications
The same wavelength optical plan as ITU-T G.983 is selected. The The same optical wavelength plan as the [ITU-T G.983] is selected.
transceivers are derivations from existing Ethernet optics The transceivers are derivatives of existing Ethernet optical
transceivers. What is added is the burst functionality for the transceivers, with dual wavelength on a single fiber and extended
uplink - burst transmission at the ONU and burst reception at the burst capabilities for the uplink. The uplink burst capability is
OLT. The [802.3ah] selected very relaxed burst parameters. the burst transmission functionality for the ONUs and burst reception
functionality for the OLT. The [802.3ah] selected very relaxed burst
parameters to reduce the device cost of EPON products.
1.2.5. Point to point emulation 1.2.5. Point to point emulation
An emulated point-to-point link is created for each ONU. The The downstream is a broadcast link meaning the OLT transmission is
downstream transmission is an aggregation of point-to-point tunnels shared for all ONUs. The sharing of the transmission of the OLT has
and single-copy-broadcast channel (tagged as all ones LLID). The some negative privacy aspects, and should be limited to broadcast
ONUa filter traffic not intended for their reception according to the traffic in nature only. The traffic dedicated to each ONU should not
virtual link marking. An LLID tag is attached at the preamble to be shared. The solution provided by the [802.3ah] is to partition
denote the virtual link - destination at the downstream and source at the EPON link, in a virtual manner, between the ONUs. Each ONU has a
the upstream. dedicated virtual link to the OLT. The [802.3ah] also defines an
additional link for broadcast transmission. The medium becomes an
aggregation of point-to-point tunnels. The OLT can not preserve its
EPON interface as a single interface connected to N devices
(following the properties of the physical interface). The EPON
interface of the OLT is partitioned into separate virtual interfaces,
an interface for each virtual link. Hence the OLT behaves like a
device with N virtual ports (and an additional port for the broadcast
transmission). The additional single-copy-broadcast channel (tagged
as all ones LLID) is added to allow the broadcast transmission within
a single copy to all ONUs, preserving the inherent advantage of BW
efficiency of the PON shared media. The ONUs filter the downlink
traffic which is not intended for their reception, according to the
virtual link marking. An LLID tag is attached at the preamble of the
Ethernet packet denoting the virtual link. The LLID marks the
destination port in the downstream and source port in the upstream.
The virtual links concept is also used to avoid violations of The virtual links concept is also used to avoid a violation of the
bridging rules for peer to peer traffic in the PON. A bridge sees a [802.1d] bridging rules for peer to peer traffic in the PON. Peer to
single MAC Client for every link pair. The private paths concept peer traffic is traffic between ONUs in the same PON. The OLT can
means no networking problems exist and it provides subscriber not preserve the EPON interface as a single interface connected to N
isolation. As the tunneling is only virtual there is a single devices and allow traffic between these devices without violating the
physical interface and a single physical layer for the device bridging rules. The source address and destination address of the
including attributes like local MAC address. The following diagram peer to peer traffic are behind the same port and therefore the
describes the virtual tunneling for the EPON. traffic should be discarded. The separation of the ONUs into virtual
links solves this issue. The OLT has N virtual ports for the single
physical EPON port. A bridge sees a single MAC Client for every link
pair.
The private paths concept solves the networking problems and it
provides subscriber isolation.
As the tunneling is only a virtual tunneling, there is a single
physical interface and a single physical layer for the device so that
some attributes are shared. For example, the interface has a single
local MAC address.
The virtual tunneling for an OLT with 3 ONUs, is illustrated in the
following diagram.
Trunk Line Trunk Line
| |
| |
| |
\|/ \|/
+===============================================+ +===============================================+
| 802.1D Bridge | | 802.1D Bridge |
+===============================================+ +===============================================+
| MAC client1| ... |MAC client3| | MAC client1| ... |MAC client3|
skipping to change at page 9, line 37 skipping to change at page 11, line 37
| MAC client | | MAC client | | MAC client | | MAC client | | MAC client | | MAC client |
+============+ +============+ +============+ +============+ +============+ +============+
| PHY | | PHY | | PHY | | PHY | | PHY | | PHY |
+============+ +============+ +============+ +============+ +============+ +============+
/|\ /|\ /|\ /|\ /|\ /|\
| | | | | |
| | | | | |
| | | | | |
Subscriber1 Subscriber2 Subscriber3 Subscriber1 Subscriber2 Subscriber3
1.2.6. MPCP principles 1.2.6. Principles of the MPCP
The EPON standard defines a media access control of an optical Access
network. The Access network has some substantial differences from
the legacy LAN which the Ethernet was designed for. The differences
mainly lie in the provisioning of the network. An Access network is
an administrated environment, with an operator providing the service
and subscribers consuming it. The operator is controlling the
network and managing its traffic. For instance BW is controlled and
subscribers are billed for services. The MPCP protocol divides the
Ethernet interfaces into two unequal types of network units. The
first interface is an OLT interface, which is a server unit,
controlling the network. The second interface is an ONU interface,
which is a client unit, participating in the network.
The OLT, which is the server unit, manages the network. The MPCP The OLT, which is the server unit, manages the network. The MPCP
controls the TDM transmission of the uplink. The MPCP is implemented controls the TDM transmission of the uplink. The MPCP is implemented
at the MAC control layer and the MPCP messages are MAC control at the MAC control layer and the MPCP messages are MAC control
messages using the 8808 Ethertype. These messages are not forwarded messages using the 0x8808 Ethertype. These messages are not
from the MAC. A concept of time must exist in the protocol in order forwarded out of the MAC.
to schedule the uplink transmission. The synchronized timestamp in
the network is managed through the MPCP messages. The timestamp is A concept of time must exist in the protocol in order to schedule the
also used to measure the RTT of each ONU and compensate it for uplink transmission. A timestamp which is set by the OLT and
transmission. The difference of incoming timestamp to local time synchronized between the network units is passed through the MPCP
allows OLT to calculate the RTT. The TDM control is done using the messages. The timestamp is also used to measure the RTT of each ONU.
gate messages. These messages define for each ONU the time for RTT is compensated by the OLT, in the generation of the grants for
transmission and the length of transmission. The RTT is reduced from the uplink transmission. The difference of incoming timestamp to
the transmission time at the gate message to shift the ONU local time allows the OLT to calculate the RTT. RTT compensation is
transmission time in the opposite direction. needed as the RTT in an Access network can have a significant value.
The standard allows the network to reach a 20km distance which is
equivalent to a 200usec RTT (25Kbytes of data).
The TDM control is done using the GATE messages. These messages
define, for each ONU, the time for transmission and the length of
transmission. The RTT is reduced from the transmission time in the
GATE message to shift the transmission time of the ONU in the
opposite direction.
A scheduling algorithm at the OLT, which is not defined in the A scheduling algorithm at the OLT, which is not defined in the
[802.3ah], is responsible to divide the BW and control the [802.3ah], is responsible for dividing the BW and controlling the
transmission delay of each ONU according to its SLA. In order for transmission delay of each ONU according to its SLA. The MPCP
this algorithm to be efficient a closed loop operation is enabled defines a closed loop operation, in order for this algorithm to be
meaning. The closed loop is achieved by that the ONU reports on the efficient. The MPCP allows the ONUs to report on the amount of BW
amount of BW it require for transmission. This allows to allocate they require for transmission using a special REPORT message. This
different peak BW for each ONU at different times using the allows allocating BW to an ONU only when requested, relying on the
statistical properties of the traffic hence allowing oversubscription statistical burst property of the traffic, allowing different peak BW
of the BW. The messages are for the BW report are denoted as REPORT for different ONUs at different times, hence allowing
messages which report the amount of data in the ONU queues. In oversubscription of the BW. The REPORT message reports the amount of
addition to that the MPCP defines a protocol of auto-discovery and data waiting in the ONU queues.
In addition to that the MPCP defines a protocol of auto-discovery and
registration of ONUs. registration of ONUs.
The registration process is defined in the diagram below: The registration process is defined in the diagram below:
OLT ONU OLT ONU
| | | |
| Discovery Gate \| | Discovery Gate message \|
|--------------------------------------------| |--------------------------------------------|
| /| | /|
| | | |
|/ Register Request | |/ Register Request message |
|--------------------------------------------| |--------------------------------------------|
|\ | |\ |
| | | |
| Register | | Register message |
| (assigning LLID) \| | (assigning LLID) \|
|--------------------------------------------| |--------------------------------------------|
| /| | /|
| | | |
| Gate \| | Gate message \|
|--------------------------------------------| |--------------------------------------------|
| /| | /|
| | | |
|/ Register ACK | |/ Register ACK message |
|--------------------------------------------| |--------------------------------------------|
|\ | |\ |
| | | |
| | | |
A new ONU requests to register (sends a REG_REQUEST message) in a A new ONU requests to register (sends a REG_REQUEST message) in a
special discovery grant allocated for that by the OLT. During that special discovery grant, allocated for that by the OLT. During that
time more than one ONU might try to register and as the RTT of the time more than one ONU might try to register. A collision in
new ONUs is not known yet a collision in transmission might occur. A transmission might occur as the RTT of the new ONUs is not yet known.
random backoff mechanism of transmission is used to schedule the next A random backoff mechanism of the transmission is used to schedule
registration requests to avoid these collisions. When the OLT the following registration requests to avoid these collisions. When
receives REG_REQUEST message of an ONU and approves this ONU then it the OLT receives REG_REQUEST message of an ONU and approves this ONU
sends a REGISTER message to this ONU defining its LLID. From this then it sends a REGISTER message to this ONU defining its LLID. From
time the ONU transmission is scheduled by its LLID, knowing the RTT, that point the ONU transmission is scheduled by its LLID, knowing the
and no collision can occur. The ONU replies with a REGISTER_ACK RTT, and no collision can occur. The ONU replies with a REGISTER_ACK
message and the registration process of the MPCP ends. Higher layer message and the registration process of the MPCP ends. Higher layer
protocols may yet be needed to authenticate the ONU and allow it to protocols may yet be needed to authenticate the ONU and allow it to
participate in the network. participate in the network.
1.2.7. Forward Error correction (FEC) 1.2.7. Forward Error correction (FEC)
The FEC is defined to enhance the link budget of the PON. As each The FEC is defined to enhance the link budget of the PON. As each
splitter attenuates the optical signal, the number of the splits and splitter attenuates the optical signal, the number of the splits and
the distance are limited by the link budget and hence an FEC which the distance are limited by the link budget. Hence an FEC which
improves the link budget is very useful. The FEC code used is the improves the link budget, has a benefit. The FEC code used is the
RS(239,255,8), similar to G.975 improving the BER from 1E-4 to 1E-12. RS(239,255,8), similar to the FEC code in [ITU-T G.975], improving
the BER from 1E-4 to 1E-12.
The FEC parity encapsulation is based on the Ethernet frames. The The FEC parity encapsulation is based on the framing of the Ethernet
Ethernet frames are spaced by rate adaptation, and the parity bytes packet. The Ethernet packets are spaced by MAC rate adaptation, and
are inserted in the provided space. the parity bytes are inserted after the packet, in the provided
space.
As the start and end of frame signals are outside of the FEC As the start and end of packet codewords define also the FEC
protection, they are replaced by a series of symbols to enhance their boundaries, and they are outside the FEC protection, they are
vulnerability to errors. replaced by a series of symbols to reduce their vulnerability to
errors.
The following diagram presents an FEC protected frame: The following diagram presents an FEC protected frame:
+-------------------------------------------------------------------+ +-------------------------------------------------------------------+
| | | | | | | | | | | | | | | |
| S_FEC | Preamble/SFD | Frame | FCS | T_FEC | Parity | T_FEC | | S_FEC | Preamble/SFD | Frame | FCS | T_FEC | Parity | T_FEC |
| | | | | | | | | | | | | | | |
+-------------------------------------------------------------------+ +-------------------------------------------------------------------+
The FEC layer introduces a fixed delay in the receive and transmit The FEC is added in a separate layer between the PCS and PMA layers
of the [802.3].
The FEC layer introduces a fixed delay in receive path and transmit
path. path.
The FEC layer is optional. The FEC layer is optional.
1.3. Management architecture 1.3. Management architecture
Each one of the EPON layers is accompanied by a management I/F, which Each one of the EPON layers is accompanied with a management
is controlled through clause 30 of the spec. The MIB document interface, which is controlled through clause 30 of the [802.3ah].
allocates for each one of them a separate package, as the [802.3ah] As the [802.3ah] spec may be used for different applications and some
spec may be used for different applications and may use some of the of the clauses may be used separately, the IEEE management clause
clauses separately. allocates for each one of them a separate package. The MIB document
follows this partition.
The following diagram presents the packages relation to IEEE layering The following diagram presents the relation of the MIB groups to the
diagram: [802.3ah] layers:
+===========================+ +===========================+
| Higher layers | | Higher layers |
+===========================+ +===========================+
| 802.1D Bridge | | 802.1D Bridge |
+===========================+ +===========================+
|MAC client| ... |MAC client| |MAC client| ... |MAC client|
+===========================+ \ +=============================+ +===========================+ \ +=============================+
| MAC Control - (MPCP) |----- |MpcpObjects| ... |MpcpObjects| | MAC Control - (MPCP) |----- |MpcpObjects| ... |MpcpObjects|
+===========================+ / +=============================+ +===========================+ / +=============================+
skipping to change at page 13, line 4 skipping to change at page 15, line 39
| PMA | | PMA |
+===========================+ +===========================+
| PMD | | PMD |
+===========================+ +===========================+
| | | |
| MDI | | MDI |
| | | |
/===============/ /===============/
/ Media / / Media /
/===============/ /===============/
As for the ONU the situation is simple. There is one logical and
physical interface and a single copy exists for each layer which can
be remotely queried by the OLT.
At the OLT there is a single physical interface and N virtual logical The association is strait forward for the ONU interface. There is
one logical and one physical interface and a single copy exists for
each layer, that can be remotely queried by the OLT.
At the OLT there is a single physical interface and N virtual
interfaces for the virtual links of the ONUs ( and another virtual interfaces for the virtual links of the ONUs ( and another virtual
interface for the broadcast virtual link). As can be seen from the interface for the broadcast virtual link). As can be seen from the
layering diagram above, the MAC is virtually duplicated and therefore layering diagram above, the MAC layer is virtually duplicated.
the selection for the management for this scenario is to allocate an
interface index for each one of the virtual link and an additional Therefore in this document it was selected that the management of a
interface index for the OLT. Therefore the Interface, MAU and virtual interface is like a physical interface and an interface index
etherLike interfaces MIBs have a row (ifIndex) for each virtual link is allocated for each one of the virtual links and an additional
at the OLT. The justification for this partition is that the interface index is allocated for the OLT.
interfaces are quite well separated as they present physical
different ONUs which are viewed from the OLT point of view, and for To illustrate the interface modeling, consider two devices. The
instance there is a meaning for a separate bad frames, or bad octets first device has two physical interfaces, is typically located at a
counters for each virtual link as the ONUs can be distanced consumer's site, and called an "ONU modem".
differently, which is quite similar to a separate physical interface.
An "ONU modem" is shown in the figure below:
--------
ONU interface | ONU | 10megabit interface
--------------| modem |--------------------
---------
This device would have 3 entries in the IF table, and one IF stack
entry, for example:
ifIndex=1 - interface for 10megabit interface
ifIndex=2 - interface for the optical interface
ifIndex=200 - interface for the ONU interface
And then in IF stack table:
ifStackHigherLayer=200, ifStackLowerLayer=2 - map between the
physical and the ONU
The second device has three physical interfaces, is typically located
at the provider's site, and may be called a "headend".
A "headend" is shown in the figure below:
---------
1st OLT interface | Head | gigE interface
------------------| end |--------------------
| |
------------------| |
2nd OLT interface | |
---------
This device would have 5 entries (when no attached ONUs) in the IF
table, for example:
ifIndex=1 - interface for gigE interface
ifIndex=2 - interface for 1st optical interface
ifIndex=3 - interface for 2nd optical interface
ifIndex=265535 - interface for the 1st OLT broadcast interface
ifIndex=365535 - interface for the 2nd OLT broadcast interface
And then in IF stack table:
ifStackHigherLayer=265535, ifStackLowerLayer=2 - map between the 1st
physical and its broadcast interface
ifStackHigherLayer=365535, ifStackLowerLayer=3 - map between the 2nd
physical and its broadcast interface
If two ONUs connected to the first OLT interface, then for example,
the following entries would be added to the IF table:
ifIndex=200001 - interface for the 1st ONU of 1st OLT
ifIndex=200002 - interface for the 2nd ONU of 1st OLT
And in the IF stack table:
ifStackHigherLayer=200001, ifStackLowerLayer=2 - map between the 1st
physical and 1st ONU
ifStackHigherLayer=200002, ifStackLowerLayer=2 - map between the 1st
physical and 2nd ONU
For each physical interface, there would be an entry (ifIndex) in the
tables of the interface MIB module [RFC2863], MAU MIB module
[RFC3636] and Etherlike MIB module [RFC3635]. Additionally, there
would be entries (ifIndexes) for the virtual interfaces of the OLT
interface. The justification for the additional allocation of
indexes is that the virtual interfaces are quite well distinguished
as they connect different physical ONUs, from the OLT side. For
instance there is a meaning for separate bad frames counter or bad
octets counter for each virtual link, as the ONUs can be differently
distanced. This is quite similar to a case of separate physical
interfaces.
The same partition concept exists for the MIB module of this The same partition concept exists for the MIB module of this
document. Each row in the tables is selected according to the document. Each row in the tables is indexed according to the ifIndex
ifIndex and specifically there is a row for each virtual link. There and specifically there is a row for each virtual link. There are
are a few control objects which are defined for the entire layer (and some control objects which are shared and are the same for the
they should have the same value for each ifIndex) but most of the virtual interfaces (and they should have the same value for each
objects are partitioned into N+1 logical interfaces at the OLT for ifIndex) but most of the objects have different values for N+1
each layer. It is a bit different than the IEEE layering diagram logical interfaces at the OLT. This is done for each MIB group. It
which present the P2MP layer as a single layer while duplicating the is a bit different from the [802.3ah] layering diagram which presents
MAC and MAC client layers (Please see the diagram above). However the P2MP layer as a single layer while duplicating the MAC and MAC
from management perspective it is more convenient and neat to client layers (Please see the diagram above). However from
partition the management of the entities for the virtual links as the management perspective it is more convenient and neat to partition
managed atomic entity is the virtual link, and use the interface the management of the layers for the virtual links, as the atomic
index for that purpose as it is already used for the rows of the managed entity is the virtual link. It is also convenient to use the
virtual links at the Interface, MAU and etherLike interfaces MIBs. interface index of the virtual link for that purpose, as it is
already used to index the rows of the virtual links at the Interface,
MAU and etherLike interfaces MIBs.
As an example provided below are the values for the MPCP control 2. MIB structure
table for an OLT with 3 ONUs registered:
At ONU1 in working mode, one row: This document defines the DOT3 EPON MIB module. The DOT3 EPON MIB
module defines the objects used for management of the [802.3ah] Point
to Multipoint (P2MP) interfaces. These MIB objects are included in
four groups.
i) The Multi-Point Control Protocol (MPCP) MIB objects - MIB objects
related to [802.3ah] clause 64 Multi Point Control Protocol
attributes. The following tables are presented in this group:
The dot3MpcpControlTable defines the objects used for the
configuration and status indication, which are per logical link, of
MPCP compliant interfaces.
The dot3MpcpStatTable defines the statistics objects, which are per
logical link, of MPCP compliant interfaces.
The operational mode of an OLT/ONU for the tables is defined by the
dot3MpcpMode object in the dot3MpcpControlTable.
ii) The OMPEmulation MIB objects - MIB objects related to [802.3ah]
clause 65 point to point emulation attributes. The following tables
are presented in this group:
The dot3OmpEmulationTable defines the objects used for the
configuration and status indication, which are per logical link, of
OMPEmulation compliant interfaces.
The dot3OmpEmulationStatTable defines the statistics objects which
are per logical link, of OMPEmulation compliant interfaces.
The operational mode of an OLT/ONU for the tables is defined by the
dot3OmpEmulationType object in the dot3OmpEmulationTable.
iii) The FEC MIB objects - MIB objects related to [802.3ah] clause 60
and clause 65 EPON FEC attributes. The following table is presented
in this group:
The dot3EponFecTable defines the objects used for the configuration
and status indication, which are per logical link, of FEC EPON
compliant interfaces.
iv) The EPON extended package MIB objects - MIB objects used for
configuration and status indication with extended capabilities of the
EPON interfaces. The following tables are presented in this group:
The dot3ExtPkgControlTable defines the objects which are per logical
link, used for the configuration and status indication of EPON
compliant interfaces.
The dot3ExtPkgQueueTable defines the objects which are per logical
link, and per queue, used for the configuration and status indication
of the ONU queues reported in the MPCP REPORT message, of EPON
compliant interfaces.
The dot3ExtPkgQueueSetsTable defines the objects which are per
logical link, per queue, and per queue_set, used for the
configuration and status indication of the ONU queue_sets reported in
the MPCP REPORT message, of EPON compliant interfaces.
The dot3ExtPkgOptIfTable defines the objects which are per logical
link, used for the control and status indication of the optical
interface of EPON compliant interfaces.
As described in the architecture section, each row in the tables is
indexed according to the ifIndex, and specifically there is a row for
each virtual link. There are a few control objects which are shared
and have the same value for the virtual interfaces (and they should
have the same value for each ifIndex) but most of the objects have
different values for N+1 logical interfaces at the OLT. This is done
for each MIB group. It is a bit different from the [802.3ah]
layering diagram which presents the P2MP layer as a single layer
while duplicating the MAC and MAC client layers. However from
management perspective it is more convenient and neat to partition
the management of the layers for the virtual links, as the atomic
managed entity is the virtual link. It is also convenient to use the
interface index of the virtual link for that purpose, as it is
already used to index the rows of the virtual links at the Interface,
MAU and etherLike interfaces MIBs.
For example provided below the values of the MPCP control table of an
OLT with 3 registered ONUs:
The table below presents the MPCP control table of ONU1 in working
mode. A single row exists in the table.
+---------------------------+-----------------+ +---------------------------+-----------------+
| MPCP control MIB object | Value | | MPCP control MIB object | Value |
+---------------------------+-----------------+ +---------------------------+-----------------+
| ifIndex | 1 | | ifIndex | 100 |
| | | | | |
| dot3MpcpOperStatus | true | | dot3MpcpOperStatus | true |
| | | | | |
| dot3MpcpAdminState | true | | dot3MpcpAdminState | true |
| | | | | |
| dot3MpcpMode | onu | | dot3MpcpMode | onu |
| | | | | |
| dot3MpcpSyncTime | 25 | | dot3MpcpSyncTime | 25 |
| | | | | |
| dot3MpcpLinkID | 1 | | dot3MpcpLinkID | 1 |
skipping to change at page 15, line 4 skipping to change at page 21, line 35
| dot3MpcpRegistrationState | registered | | dot3MpcpRegistrationState | registered |
| | | | | |
| dot3MpcpTransmitElapsed | 10 | | dot3MpcpTransmitElapsed | 10 |
| | | | | |
| dot3MpcpReceiveElapsed | 10 | | dot3MpcpReceiveElapsed | 10 |
| | | | | |
| dot3MpcpRoundTripTime | 100 | | dot3MpcpRoundTripTime | 100 |
+---------------------------+-----------------+ +---------------------------+-----------------+
Table 1 Table 1
at the OLT in working mode the MPCP cotrol objects associated with
the virtual links, 4 rows OLT_MAC_Address is the MAC address of the OLT EPON interface.
The creation of the rows of the ONU interface is done at
initialization.
For example, provided below are the values for the MPCP control table
of the ONU, after initialization, before registration.
The table below presents the MPCP control table of ONU1 after
initialization. A single row exists in the table.
+---------------------------+-------------------+
| MPCP control MIB object | Value |
+---------------------------+-------------------+
| ifIndex | 100 |
| | |
| dot3MpcpOperStatus | true |
| | |
| dot3MpcpAdminState | true |
| | |
| dot3MpcpMode | onu |
| | |
| dot3MpcpSyncTime | 0 |
| | |
| dot3MpcpLinkID | 0 |
| | |
| dot3MpcpRemoteMACAddress | 00:00:00:00:00:00 |
| | |
| dot3MpcpRegistrationState | unregistered |
| | |
| dot3MpcpTransmitElapsed | 0 |
| | |
| dot3MpcpReceiveElapsed | 0 |
| | |
| dot3MpcpRoundTripTime | 0 |
+---------------------------+-------------------+
Table 2
The table below presents the MPCP control table of the OLT in working
mode. Four rows exist in the table associated with the virtual
links.
+----------------+-----------+------------+------------+------------+ +----------------+-----------+------------+------------+------------+
| MPCP control | Value | Value | Value | Value | | MPCP control | Value | Value | Value | Value |
| MIB object | | | | | | MIB object | | | | |
+----------------+-----------+------------+------------+------------+ +----------------+-----------+------------+------------+------------+
| ifIndex | 1 | 2 | 3 | 65535 | | ifIndex | 100001 | 100002 | 100003 | 165535 |
| | | | | | | | | | | |
| dot3MpcpOperSt | true | true | true | true | | dot3MpcpOperSt | true | true | true | true |
| atus | | | | | | atus | | | | |
| | | | | | | | | | | |
| dot3MpcpAdminS | true | true | true | true | | dot3MpcpAdminS | true | true | true | true |
| tate | | | | | | tate | | | | |
| | | | | | | | | | | |
| dot3MpcpMode | olt | olt | olt | olt | | dot3MpcpMode | olt | olt | olt | olt |
| | | | | | | | | | | |
| dot3MpcpSyncTi | 25 | 25 | 25 | 25 | | dot3MpcpSyncTi | 25 | 25 | 25 | 25 |
skipping to change at page 15, line 42 skipping to change at page 23, line 43
| dot3MpcpTransm | 10 | 10 | 10 | 10 | | dot3MpcpTransm | 10 | 10 | 10 | 10 |
| itElapsed | | | | | | itElapsed | | | | |
| | | | | | | | | | | |
| dot3MpcpReceiv | 10 | 10 | 10 | 10 | | dot3MpcpReceiv | 10 | 10 | 10 | 10 |
| eElapsed | | | | | | eElapsed | | | | |
| | | | | | | | | | | |
| dot3MpcpRoundT | 100 | 60 | 20 | 0 | | dot3MpcpRoundT | 100 | 60 | 20 | 0 |
| ripTime | | | | | | ripTime | | | | |
+----------------+-----------+------------+------------+------------+ +----------------+-----------+------------+------------+------------+
Table 2 Table 3
The creation of the rows at the ONU and at the OLT, for the OLT ONU1_MAC_Address is the MAC address of ONU1 EPON interface.
interface and the broadcast virtual interface is done at
initialization. The creation and deletion of rows at the OLT for the
virtual link interfaces is done when the link is established (ONU
registers) and when the link is deleted (ONU deregisters).
As an example, provided below are the values for the MPCP control ONU2_MAC_Address is the MAC address of ONU2 EPON interface.
table after initialization:
At ONU1 in working mode, one row: ONU3_MAC_Address is the MAC address of ONU3 EPON interface.
+---------------------------+--------------+ BRCT_MAC_Address is the MAC address of the broadcast EPON interface,
| MPCP control MIB object | Value | which is the OLT MAC address.
+---------------------------+--------------+
| ifIndex | 1 |
| | |
| dot3MpcpOperStatus | true |
| | |
| dot3MpcpAdminState | true |
| | |
| dot3MpcpMode | onu |
| | |
| dot3MpcpSyncTime | 0 |
| | |
| dot3MpcpLinkID | 0 |
| | |
| dot3MpcpRemoteMACAddress | 00 |
| | |
| dot3MpcpRegistrationState | unregistered |
| | |
| dot3MpcpTransmitElapsed | 0 |
| | |
| dot3MpcpReceiveElapsed | 0 |
| | |
| dot3MpcpRoundTripTime | 0 |
+---------------------------+--------------+
Table 3 The creation of the rows of the OLT interface and the broadcast
at the OLT in working mode the MPCP cotrol objects associated with virtual interface is done at initialization.
the virtual links, one row:
The creation of rows of the virtual interfaces at the OLT is done
when the link is established (ONU registers) and the deletion is done
when the link is deleted (ONU deregisters).
For example, provided below are the values of the MPCP control table
of the OLT after initialization, before the ONUs register.
The table below presents the MPCP control table of the OLT after
initialization. A single row exists in this table associated with
the virtual broadcast link.
+---------------------------+------------------+ +---------------------------+------------------+
| MPCP control MIB object | Value | | MPCP control MIB object | Value |
+---------------------------+------------------+ +---------------------------+------------------+
| ifIndex | 65535 | | ifIndex | 165535 |
| | | | | |
| dot3MpcpOperStatus | true | | dot3MpcpOperStatus | true |
| | | | | |
| dot3MpcpAdminState | true | | dot3MpcpAdminState | true |
| | | | | |
| dot3MpcpMode | olt | | dot3MpcpMode | olt |
| | | | | |
| dot3MpcpSyncTime | 25 | | dot3MpcpSyncTime | 25 |
| | | | | |
| dot3MpcpLinkID | 65535 | | dot3MpcpLinkID | 65535 |
skipping to change at page 17, line 35 skipping to change at page 24, line 48
| | | | | |
| dot3MpcpTransmitElapsed | 10 | | dot3MpcpTransmitElapsed | 10 |
| | | | | |
| dot3MpcpReceiveElapsed | 100000 | | dot3MpcpReceiveElapsed | 100000 |
| | | | | |
| dot3MpcpRoundTripTime | 0 | | dot3MpcpRoundTripTime | 0 |
+---------------------------+------------------+ +---------------------------+------------------+
Table 4 Table 4
The example above shows the MPCP control objects when 3 ONUs are BRCT_MAC_Address is the MAC address of the broadcast EPON interface,
registered. Creation of rows for the Interface, MAU and etherLike which is the OLT MAC address.
interfaces MIBs is quite similar. Please see the example in section
3.
2. MIB structure
This document defines the DOT3 EPON MIB module. The DOT3 EPON MIB 3. Relation to other MIB Modules
module defines the objects used for configuration and description of
the [802.3ah] Point to Multipoint (P2MP) section. These MIB module
objects are included in four MIB module groups.
The Multi-Point Control Protocol (MPCP) MIB objects - MIB objects 3.1. Relation to the Interfaces MIB and Ethernet-like Interfaces MIB
related to [802.3ah] clause 64 Multi Point Control Protocol
attributes. In this MIB module group: The dot3MpcpControlTable
defines the objects used for the configuration and status indication,
which are per logical link, of MPCP layer ([802.3ah] Multi-Point
Control Protocol) compliant interfaces. The dot3MpcpStatTable
defines the statistics objects, which are per logical link, for MPCP
compliant interfaces.
The OMPEmulation MIB objects - MIB module related to [802.3ah] clause EPON interface is a kind of Ether-like interface. This MIB module
65 point to point emulation attributes. In this MIB module group: extends the objects of the Interface MIB and the Ether-like
The dot3OmpEmulationTable defines the objects used for the interfaces MIB for an EPON type interface.
configurations and status indications which are per logical link, of
OMPEmulation compliant interfaces. The dot3OmpEmulationStatTable
defines the statistics objects, which are per logical link, for
OMPEmulation compliant interfaces.
The FEC MIB module objects - managed object related to [802.3ah] Implementing this module therefore MUST require implementation of the
clause 60 and clause 65 EPON FEC attributes. The dot3EponFecTable Interfaces MIB module [RFC2863] and the Ethernet-like Interfaces MIB
defines the objects used for the configurations and status module [RFC3635].
indications, which are per logical link, of FEC EPON compliant
interfaces.
The EPON extended package MIB objects defining the objects used for Thus, each managed EPON interface would have a corresponding entry in
configuration and description of management objects for extended the mandatory tables of the Ether-like MIB module found in [RFC3635],
capabilities of the EPON interfaces. The dot3ExtPkgControlTable and likewise in the tables of the Interface MIB module found in
defines the extended package objects, which are per logical link, [RFC2863]. Also each managed virtual EPON interface would have a
used for the configuration and status indication of the EPON corresponding entry in the mandatory tables of the Ether-like MIB
interfaces. The dot3ExtPkgQueueTable defines the extended package module found in [RFC3635], and likewise in the tables of the
objects, which are per logical link, and per REPORT queue used for Interface MIB module found in [RFC2863] with a dedicated ifIndex for
the configuration and status indication of the ONU queues reported at this interface.
the MPCP REPORT message of the EPON interfaces. The
dot3ExtPkgQueueSetsTable defines the extended package objects, which
are per logical link per REPORT queue, and per queue_set used for the
configuration and status indication of the ONU queue_sets reported at
the MPCP REPORT message of the EPON interfaces. The
dot3ExtPkgOptIfTable defines the extended package objects, which are
per logical link, used for the control and status indication of the
optical interfaces of the EPON interfaces.
3. Relation to other MIB Modules In this document there is no replication of the objects from these
MIBs, so for instance the document is defining
dot3MpcpRemoteMACAddress only while assuming the local MAC address
object is already defined in [RFC3635].
3.1. Relation to the Interfaces MIB and Ethernet-like Interfaces MIB The interface MIB module [RFC2863] defines the interface index
(ifIndex). Interface Index, as specified in [RFC2863] is used in
this MIB Module as an index to the EPON MIB tables. The ifIndex is
used to denote the physical interface and the virtual link interfaces
at the OLT. The OLT interface and the virtual link interfaces are
stacked using the ifStack table defined in [RFC2863], and the
ifInvStack defined in [RFC2864]. The OLT interface is the lower
layer of all other interfaces associated with the virtual links.
EPON interfaces are a type of Ether-like interface. This module This document defines the specific EPON objects of an ONU interface
extends the objects of the Ehter-like interfaces management for the and an OLT interface. Information in the tables is per LLID. The
EPON type interfaces. Thus, each managed EPON interface would have a rows in the EPON MIB tables, referring to the LLIDs are denoted with
corresponding entry in the mandatory tables of the Ether-like MIB the corresponding ifIndexes of the virtual link interfaces.
module found in [RFC3635], and likewise in the tables from the
Interface MIB module found in [RFC2863]. Also each managed virtual
EPON interface defined by the virtual link at the OLT would have a
corresponding entry in the mandatory tables of the Ether-like MIB
module found in [RFC3635], and likewise in the tables from the
Interface MIB module found in [RFC2863] with a dedicated ifIndex.
There is no replication of the objects from these RFCs, so for Please note that each virtual interface does not have a different
instance the document is defining dot3MpcpRemoteMACAddress only while physical MAC address at the OLT as the physical interface is the
assuming the local MAC address attribute is already defined in same. It is specified in the [802.3ah] section 64.1.2. The
[RFC3635] corresponding object of the Ether-like interface MIB is duplicated
for all the virtual interfaces.
Interface Indexes as specified in [RFC2863] are used in these MIB For example the values of the Interface MIB objects are presented in
Modules. The descriptions of the ifIndexes denote which ifIndex is the following tables, for an OLT with 3 registered ONUs:
being used. The use of ifIndex is for actual existing connections
and for the virtual links at the OLT. The OLT interface and the
virtual link interfaces are stacked using the ifStack table specified
at [RFC2863] and the ifInvStack defined in [RFC2864]. At the OLT the
OLT interface and the virtual links associated with it are stacked as
the OLT interface is the higher layer of all other interfaces related
to the virtual links.
In this MIB module the interface referred to is the OLT interface and The table below presents the objects of the Interface MIB of an ONU
the sub-layers defined in the [802.3ah] for the OLT are also divided in working mode.
into virtual links. Therefore the ifIndexs used in the MIB document
for the OLT are the ifIndex of the OLT and the ifIndexes of the
virtual links. Information for each LLID in the tables is indexed by
the interface index for each table. This index is corresponding to
the virtual link interfaces ifIndexs.
Only the MAC address at the OLT is not duplicated as the physical +----------------------+--------------------------------+
interface is the same. It is specified in the [802.3ah] section | Interface MIB object | Value |
64.1.2. At the tables this entry is duplicated for the virtual +----------------------+--------------------------------+
interfaces. | ifIndex | 1 |
| | |
| ifDescr | "interface description" |
| | |
| ifType | ethernetCsmacd (6) 1000base-Px |
| | |
| ifMtu | MTU size (1522) |
| | |
| ifSpeed | 1000000000 |
| | |
| ifPhysAddress | ONU_MAC_Address |
| | |
| ifAdminStatus | up |
| | |
| ifOperStatus | Up |
| | |
| ifLastChange | ONUup_time |
| | |
| ifInOctets | ONU_octets_number |
| | |
| ifInUcastPkts | ONU_unicast_frame_number |
| | |
| ifInNUcastPkts | ONU_non_unicast_frame_number |
| | |
| ifInDiscards | ONU_discard_frame_number |
| | |
| ifInErrors | ONU_error_frame_number |
| | |
| ifInUnknownProtos | ONU_unknown_frame_number |
| | |
| ifOutOctets | ONU_octets_number |
| | |
| ifOutUcastPkts | ONU_unicast_frame_number |
| | |
| ifOutNUcastPkts | ONU_non_unicast_frame_number |
| | |
| ifOutDiscards | ONU_discard_frame_number |
| | |
| ifOutErrors | ONU_error_frame_number |
| | |
| ifOutQLen | ONU_queue_frame_number |
+----------------------+--------------------------------+
Implementing this module therefore MUST require implementation of Table 5
Interfaces MIB module [RFC2863] and Ethernet-like Interfaces MIB
module [RFC3635].
As an example here are the values for the Interface MIB for an OLT ONU_MAC_Address is the MAC address of the ONU EPON interface.
with 3 ONUs registered:
At the ONU in working mode: The table below presents the objects of the Interface MIB of the ONU
interface.
+----------------------+-----------------------------------+ +----------------------+--------------------------------+
| Interface MIB object | Value | | Interface MIB object | Value |
+----------------------+-----------------------------------+ +----------------------+--------------------------------+
| ifIndex | 1 | | ifIndex | 100 |
| | | | | |
| ifDescr | "I/F description" | | ifDescr | "interface description" |
| | | | | |
| ifType | gigabitEthernet (117) 1000base-Px | | ifType | ethernetCsmacd (6) 1000base-Px |
| | | | | |
| ifMtu | MTU size (1522) | | ifMtu | MTU size (1522) |
| | | | | |
| ifSpeed | 1000000000 | | ifSpeed | 1000000000 |
| | | | | |
| ifPhysAddress | ONU_MAC_Address | | ifPhysAddress | ONU_MAC_Address |
| | | | | |
| ifAdminStatus | up | | ifAdminStatus | up |
| | | | | |
| ifOperStatus | Up | | ifOperStatus | Up |
skipping to change at page 20, line 46 skipping to change at page 28, line 4
| | | | | |
| ifInErrors | ONU1_error_frame_number | | ifInErrors | ONU1_error_frame_number |
| | | | | |
| ifInUnknownProtos | ONU1_unknown_frame_number | | ifInUnknownProtos | ONU1_unknown_frame_number |
| | | | | |
| ifOutOctets | ONU1_octets_number | | ifOutOctets | ONU1_octets_number |
| | | | | |
| ifOutUcastPkts | ONU1_unicast_frame_number | | ifOutUcastPkts | ONU1_unicast_frame_number |
| | | | | |
| ifOutNUcastPkts | ONU1_non_unicast_frame_number | | ifOutNUcastPkts | ONU1_non_unicast_frame_number |
| | |
| ifOutDiscards | ONU1_discard_frame_number | | ifOutDiscards | ONU1_discard_frame_number |
| | | | | |
| ifOutErrors | ONU1_error_frame_number | | ifOutErrors | ONU1_error_frame_number |
| | | | | |
| ifOutQLen | ONU1_queue_frame_number | | ifOutQLen | ONU1_queue_frame_number |
+----------------------+-----------------------------------+ +----------------------+--------------------------------+
Table 5 Table 6
at the OLT in working mode the interfaces associated with the virtual ONU_MAC_Address is the MAC address of the ONU EPON interface.
links:
The following values will be set in the ifStack and ifInvStack tables
related to this example.
ifStackTable:
ifStackHigherLayer=100, ifStackLowerLayer=1 - map between the
physical interface and the ONU
ifInvStackTable:
ifStackLowerLayer=1, ifStackHigherLayer=100,- map between the ONU and
the physical interface
The table below presents the Interface MIB objects of an OLT
interface.
+----------------------+--------------------------------+
| Interface MIB object | Value |
+----------------------+--------------------------------+
| ifIndex | 2 |
| | |
| ifDescr | "interface description" |
| | |
| ifType | ethernetCsmacd (6) 1000base-Px |
| | |
| ifMtu | MTU size (1522) |
| | |
| ifSpeed | 1000000000 |
| | |
| ifPhysAddress | OLT_MAC_Address |
| | |
| ifAdminStatus | up |
| | |
| ifOperStatus | Up |
| | |
| ifLastChange | OLTup_time |
| | |
| ifInOctets | OLT_octets_number |
| | |
| ifInUcastPkts | OLT_unicast_frame_number |
| | |
| ifInNUcastPkts | OLT_non_unicast_frame_number |
| | |
| ifInDiscards | OLT_discard_frame_number |
| | |
| ifInErrors | OLT_error_frame_number |
| | |
| ifInUnknownProtos | OLT_unknown_frame_number |
| | |
| ifOutOctets | OLT_octets_number |
| | |
| ifOutUcastPkts | OLT_unicast_frame_number |
| | |
| ifOutNUcastPkts | OLT_non_unicast_frame_number |
| | |
| ifOutDiscards | OLT_discard_frame_number |
| | |
| ifOutErrors | OLT_error_frame_number |
| | |
| ifOutQLen | OLT_queue_frame_number |
+----------------------+--------------------------------+
Table 7
OLT_MAC_Address is the MAC address of the OLT EPON interface.
The table below presents the Interface MIB objects of an OLT
interface, associated with the virtual link interfaces.
+----------+-------------+-------------+-------------+--------------+ +----------+-------------+-------------+-------------+--------------+
| Interfac | Value | Value | Value | Value | | Interfac | Value | Value | Value | Value |
| eMIB | | | | | | eMIB | | | | |
| object | | | | | | object | | | | |
+----------+-------------+-------------+-------------+--------------+ +----------+-------------+-------------+-------------+--------------+
| ifIndex | 1 | 2 | 3 | 65535 | | ifIndex | 200001 | 200002 | 200003 | 265535 |
| | | | | | | | | | | |
| ifDescr | "I/Fdescrip | "I/Fdescrip | "I/Fdescrip | "I/Fdescript | | ifDescr | "interface | "interface | "interface | "interface |
| | tion" | tion" | tion" | ion" | | | description | description | description | description" |
| | " | " | " | |
| | | | | | | | | | | |
| ifType | gigabitEthe | gigabitEthe | gigabitEthe | gigabitEther | | ifType | ethernetCsm | ethernetCsm | ethernetCsm | ethernetCsma |
| | rnet(117) | rnet(117) | rnet(117) | net(117) | | | acd (6) | acd (6) | acd (6) | cd (6) |
| | | | | | | | | | | |
| ifMtu | MTUsize(152 | MTUsize(152 | MTUsize(152 | MTUsize(1522 | | ifMtu | MTUsize(152 | MTUsize(152 | MTUsize(152 | MTUsize(1522 |
| | 2) | 2) | 2) | ) | | | 2) | 2) | 2) | ) |
| | | | | |
| ifSpeed | 1000000000 | 1000000000 | 1000000000 | 1000000000 | | ifSpeed | 1000000000 | 1000000000 | 1000000000 | 1000000000 |
| | | | | | | | | | | |
| ifPhysAd | OLT_MAC_Add | OLT_MAC_Add | OLT_MAC_Add | OLT_MAC_Addr | | ifPhysAd | OLT_MAC_Add | OLT_MAC_Add | OLT_MAC_Add | OLT_MAC_Addr |
| dress | ress | ress | ress | ess | | dress | ress | ress | ress | ess |
| | | | | | | | | | | |
| ifAdminS | up | up | up | up | | ifAdminS | up | up | up | up |
| tatus | | | | | | tatus | | | | |
| | | | | | | | | | | |
| ifOperSt | Up | Up | Up | Up | | ifOperSt | Up | Up | Up | Up |
| atus | | | | | | atus | | | | |
skipping to change at page 22, line 34 skipping to change at page 31, line 11
| ifOutDis | ONU1_disc_f | ONU2_disc_f | ONU3_disc_f | BRCT_disc_fr | | ifOutDis | ONU1_disc_f | ONU2_disc_f | ONU3_disc_f | BRCT_disc_fr |
| cards | rame_num | rame_num | rame_num | ame_num | | cards | rame_num | rame_num | rame_num | ame_num |
| | | | | | | | | | | |
| ifOutErr | ONU1_err_fr | ONU2_err_fr | ONU3_err_fr | BRCT_err_fra | | ifOutErr | ONU1_err_fr | ONU2_err_fr | ONU3_err_fr | BRCT_err_fra |
| ors | ame_num | ame_num | ame_num | me_num | | ors | ame_num | ame_num | ame_num | me_num |
| | | | | | | | | | | |
| ifOutQLe | ONU1_queue_ | ONU2_queue_ | ONU3_queue_ | BRCt_queue_f | | ifOutQLe | ONU1_queue_ | ONU2_queue_ | ONU3_queue_ | BRCt_queue_f |
| n | frame_num | frame_num | frame_num | rame_num | | n | frame_num | frame_num | frame_num | rame_num |
+----------+-------------+-------------+-------------+--------------+ +----------+-------------+-------------+-------------+--------------+
Table 6 Table 8
And the OLT interface: OLT_MAC_Address is the MAC address of the OLT EPON interface.
+----------------------+-----------------------------------+ The following values will be set in the ifStack and ifInvStack tables
| Interface MIB object | Value | related to this example:
+----------------------+-----------------------------------+
| ifIndex | 100000 |
| | |
| ifDescr | "I/F description" |
| | |
| ifType | gigabitEthernet (117) 1000base-Px |
| | |
| ifMtu | MTU size (1522) |
| | |
| ifSpeed | 1000000000 |
| | |
| ifPhysAddress | OLT_MAC_Address |
| ifAdminStatus | up |
| | |
| ifOperStatus | Up |
| | |
| ifLastChange | OLTup_time |
| | |
| ifInOctets | OLT_octets_number |
| | |
| ifInUcastPkts | OLT_unicast_frame_number |
| | |
| ifInNUcastPkts | OLT_non_unicast_frame_number |
| | |
| ifInDiscards | OLT_discard_frame_number |
| | |
| ifInErrors | OLT_error_frame_number |
| | |
| ifInUnknownProtos | OLT_unknown_frame_number |
| | |
| ifOutOctets | OLT_octets_number |
| | |
| ifOutUcastPkts | OLT_unicast_frame_number |
| | |
| ifOutNUcastPkts | OLT_non_unicast_frame_number |
| | |
| ifOutDiscards | OLT_discard_frame_number |
| | |
| ifOutErrors | OLT_error_frame_number |
| | |
| ifOutQLen | OLT_queue_frame_number |
+----------------------+-----------------------------------+
Table 7 ifStackTable:
As specified above the creation of the rows at the ONU and at the ifStackHigherLayer=265535, ifStackLowerLayer=2 - map between the OLT
OLT, for the OLT interface and for the broadcast virtual index, is physical interface and its broadcast virtual interface
done at initialization. The creation and deletion of rows for the
virtual links is done when the virtual link is established (ONU ifStackHigherLayer=200001, ifStackLowerLayer=2 - map between the OLT
registers) and when the virtual link is deleted (ONU deregisters). physical interface and its virtual interface of the 1st ONU
ifStackHigherLayer=200002, ifStackLowerLayer=2 - map between the OLT
physical interface and its virtual interface of the 2nd ONU
ifStackHigherLayer=200003, ifStackLowerLayer=2 - map between the OLT
physical interface and its virtual interface of the 3rd ONU
ifInvStackTable:
ifStackLowerLayer=2, ifStackHigherLayer=265535, - map between the
broadcast interface of the OLT and the OLT physical interface
ifStackLowerLayer=2, ifStackHigherLayer=200001 - map between the OLT
virtual interface of the 1st ONU and the OLT physical interface
ifStackLowerLayer=2, ifStackHigherLayer=200002 - map between the OLT
virtual interface of the 2nd ONU and the OLT physical interface
ifStackLowerLayer=2, ifStackHigherLayer=200003 - map between the OLT
virtual interface of the 3rd ONU and the OLT physical interface
The rows for the ONU interface, for the OLT interface and for the OLT
broadcast interface are created in initialization.
The creation of a row for a virtual link is done when the virtual
link is established (ONU registers) and deletion is done when the
virtual link is deleted (ONU deregisters).
The EPON MIB module also extends the Interface MIB module with a set
of counters, which are specific for the EPON interface. The EPON MIB
module implements the same handling of the counters when the
operation of the interface starts or stops. The interface MIB
document describes the possible behavior of counters when an
interface is re-initialized using the ifCounterDiscontinuityTime
indicator, indicating the discontinuity of the counters. Please see
[RFC2863] section 3.1.5 p.11 for more information. The counters of
the EPON MIB should be handled in a similar manner.
3.2. Relation to the IEEE 802.3 MAU MIBs 3.2. Relation to the IEEE 802.3 MAU MIBs
In the amended MAU MIB document the MAU types of the EPON Interfaces The MAU types of the EPON Interface are defined in the amended MAU
is defined. This document assumes the implementation of the MAU MIB MIB document. This document assumes the implementation of the MAU
for this purpose and does not repeat the EPON MAU types. Therefore MIB for this purpose and does not repeat the EPON MAU types.
implementing this module MUST require implementation of MAU-MIB Therefore implementing this module MUST require implementation of the
module [RFC3636]. For the ONU there is a single row for the MAU-MIB module [RFC3636bis-03].
ifMauTable. At the OLT there is a row for each virtual link (N+1),
ifMauIfIndex has a value for each virtual link.
As specified above the creation of the rows at the ONU and at the OLT The handling of the ifMAU tables for the EPON case is similar to the
for the OLT interface and for the broadcast virtual index, is done at handling described in the former section for the Interface and Ether-
initialization. The creation and deletion of rows for the virtual like interface MIBs. A single row exists for the ONU in the
links is done when the virtual link is established (ONU registers) ifMauTable. A row for each virtual link (N+1 rows) exists at the
and when the virtual link is deleted (ONU deregisters). OLT, with a separate value of ifMauIfIndex for each virtual link.
As specified above the rows for the ONU interface, for the OLT
interface and for the OLT broadcast interface are created in
initialization.
The creation of a row for a virtual link is done when the virtual
link is established (ONU registers) and deletion is done when the
virtual link is deleted (ONU deregisters).
3.3. Relation to the EFM OAM MIB 3.3. Relation to the EFM OAM MIB
The EPON interfaces are aimed to the access optical networks and most The EPON interfaces are aimed to the optical access networks and most
probably will be followed by implementation of the OAM section of the probably will be accompanied with the implementation of the OAM
[802.3ah]. Therefore The EFM OAM MIB module [I-D.ietf-hubmib-efm- section of the [802.3ah]. Therefore the EFM OAM MIB module
mib] MAY be implemented defining attributes and managed objects that [I-D.ietf-hubmib-efm-mib] MAY be implemented, when this MIB module is
are complementary to the EFM EPON MIB module. As the OAM is defined implemented, defining managed objects for the OAM layer that are
for a point to point link it is implemented using the virtual links complementary to the EFM EPON MIB module. As the OAM is defined for
which are defined for the P2MP network, so that an instance is held a point to point link it is implemented in this case, using the
for each Logical link (LLID) of the EPON. The respective ifIndex of virtual links which are defined for the P2MP network, so that an
the virtual link is used as the ifIndex of the OAM MIB for this instance is held for each Logical link (LLID) of the EPON. The
purpose. corresponding ifIndex of the virtual link is used as the ifIndex of
the tables of the OAM MIB module, for this purpose.
3.4. Relation to the bridge MIB 3.4. Relation to the bridge MIB
It is very probable that an EPON OLT will implement a bridging It is very probable that an EPON OLT will implement a bridging
functionality above the EPON interface layer, bridging between the functionality above the EPON interface layer, bridging between the
EPON users and the network. In this scenario the virtual ports of EPON users and the network. Bridge functionality is specified at
the EPON are corresponding to the virtual bridge ports. There is a [802.1d]. In this scenario the virtual ports of the EPON are
direct mapping between the bridge ports and the LLIDs, which are corresponding to the virtual bridge ports. There is a direct mapping
virtual EPON channels. between the bridge ports and the LLIDs, which are virtual EPON
channels.
If the OLT supports bridging then the virtual physical interfaces are Therefore the bridge MIB modules [RFC4188], [RFC1525] MAY be
the bridge virtual ports. The values for dot1dBasePortIfIndex would implemented when the EFM EPON MIB module is implemented for an EPON
be the number of the ifIndex for the virtual port (1 for LLID1, 2 for OLT, defining managed objects for the bridge layer.
LLID2,...)
The bridge MIB modules [RFC4188], [RFC1525] MAY be implemented in The values of dot1dBasePortIfIndex would correspond to the ifIndex of
this case where the objects of the bridge MIB module are used the virtual port (1 for LLID1, 2 for LLID2,...)
accordingly.
4. Relation table of the dot3EPON MIB module objects to the The broadcast virtual EPON interface of the OLT has no direct mapping
IEEE802.3ah attributes to a virtual bridge port as it is not port specific but used for
broadcast traffic.
4. Mapping of IEEE 802.3ah Managed Objects
This section contains the mapping between the managed objects defined
in this document and the attributes defined in [802.3ah] Clause 30.
The tables are divided to the relevant groups.
oMPCP managed object class (30.3.5) oMPCP managed object class (30.3.5)
+----------------------------+-------------------------+------------+ +----------------------------+-------------------------+------------+
| dot3EPON MIB module object | IEEE802.3ah attribute | Reference | | dot3EPON MIB module object | IEEE802.3ah attribute | Reference |
+----------------------------+-------------------------+------------+ +----------------------------+-------------------------+------------+
| ifIndex | aMPCPID | 30.3.5.1.1 | | ifIndex | aMPCPID | 30.3.5.1.1 |
| | | | | | | |
| dot3MpcpOperStatus | aMPCPAdminState | 30.3.5.1.2 | | dot3MpcpOperStatus | aMPCPAdminState | 30.3.5.1.2 |
| | | | | | | |
skipping to change at page 25, line 50 skipping to change at page 35, line 4
| | | 2 | | | | 2 |
| | | | | | | |
| dot3MpcpTxReport | aMPCPTxReport | 30.3.5.1.1 | | dot3MpcpTxReport | aMPCPTxReport | 30.3.5.1.1 |
| | | 3 | | | | 3 |
| | | | | | | |
| dot3MpcpRxGate | aMPCPRxGate | 30.3.5.1.1 | | dot3MpcpRxGate | aMPCPRxGate | 30.3.5.1.1 |
| | | 4 | | | | 4 |
| | | | | | | |
| dot3MpcpRxRegAck | aMPCPRxRegAck | 30.3.5.1.1 | | dot3MpcpRxRegAck | aMPCPRxRegAck | 30.3.5.1.1 |
| | | 5 | | | | 5 |
| | | |
| dot3MpcpRxRegister | aMPCPRxRegister | 30.3.5.1.1 | | dot3MpcpRxRegister | aMPCPRxRegister | 30.3.5.1.1 |
| | | 6 | | | | 6 |
| | | |
| dot3MpcpRxRegRequest | aMPCPRxRegRequest | 30.3.5.1.1 | | dot3MpcpRxRegRequest | aMPCPRxRegRequest | 30.3.5.1.1 |
| | | 7 | | | | 7 |
| | | | | | | |
| dot3MpcpRxReport | aMPCPRxReport | 30.3.5.1.1 | | dot3MpcpRxReport | aMPCPRxReport | 30.3.5.1.1 |
| | | 8 | | | | 8 |
| | | | | | | |
| dot3MpcpTransmitElapsed | aMPCPTransmitElapsed | 30.3.5.1.1 | | dot3MpcpTransmitElapsed | aMPCPTransmitElapsed | 30.3.5.1.1 |
| | | 9 | | | | 9 |
| | | | | | | |
| dot3MpcpReceiveElapsed | aMPCPReceiveElapsed | 30.3.5.1.2 | | dot3MpcpReceiveElapsed | aMPCPReceiveElapsed | 30.3.5.1.2 |
skipping to change at page 26, line 33 skipping to change at page 35, line 36
| | | 3 | | | | 3 |
| | | | | | | |
| dot3MpcpMaximumPendingGran | aMPCPMaximumPendingGran | 30.3.5.1.2 | | dot3MpcpMaximumPendingGran | aMPCPMaximumPendingGran | 30.3.5.1.2 |
| ts | ts | 4 | | ts | ts | 4 |
| | | | | | | |
| dot3MpcpAdminState | aMPCPAdminControl | 30.3.5.2.1 | | dot3MpcpAdminState | aMPCPAdminControl | 30.3.5.2.1 |
| | | | | | | |
| dot3MpcpSyncTime | SyncTime | 64.3.3.2 | | dot3MpcpSyncTime | SyncTime | 64.3.3.2 |
+----------------------------+-------------------------+------------+ +----------------------------+-------------------------+------------+
Table 8 Table 9
oOMPEmulation managed object class (30.3.7) oOMPEmulation managed object class (30.3.7)
+-------------------------------------+-----------------+-----------+ +-------------------------------------+-----------------+-----------+
| dot3EPON MIB module object | IEEE802.3ah | Reference | | dot3EPON MIB module object | IEEE802.3ah | Reference |
| | attribute | | | | attribute | |
+-------------------------------------+-----------------+-----------+ +-------------------------------------+-----------------+-----------+
| ifIndex | aOMPEmulationID | 30.3.7.1. | | ifIndex | aOMPEmulationID | 30.3.7.1. |
| | | 1 | | | | 1 |
| | | | | | | |
| dot3OmpEmulationType | aOMPEmulationTy | 30.3.7.1. | | dot3OmpEmulationType | aOMPEmulationTy | 30.3.7.1. |
skipping to change at page 27, line 46 skipping to change at page 36, line 46
| | | | | | | |
| dot3OmpEmulationOnuLLIDNotBroadcast | | | | dot3OmpEmulationOnuLLIDNotBroadcast | | |
| | | | | | | |
| dot3OmpEmulationBroadcastBitPlusOnu | | | | dot3OmpEmulationBroadcastBitPlusOnu | | |
| Llid | | | | Llid | | |
| | | | | | | |
| dot3OmpEmulationNotBroadcastBitNotO | | | | dot3OmpEmulationNotBroadcastBitNotO | | |
| nuLlid | | | | nuLlid | | |
+-------------------------------------+-----------------+-----------+ +-------------------------------------+-----------------+-----------+
Table 9 Table 10
oMAU managed object class (30.5.1) oMAU managed object class (30.5.1)
+--------------------------------+---------------------+------------+ +--------------------------------+---------------------+------------+
| dot3EPON MIB module object | IEEE802.3ah | Reference | | dot3EPON MIB module object | IEEE802.3ah | Reference |
| | attribute | | | | attribute | |
+--------------------------------+---------------------+------------+ +--------------------------------+---------------------+------------+
| dot3EponFecPCSCodingViolation | aPCSCodingViolation | 30.5.1.1.1 | | dot3EponFecPCSCodingViolation | aPCSCodingViolation | 30.5.1.1.1 |
| | | 2 | | | | 2 |
| | | | | | | |
| dot3EponFecAbility | aFECAbility | 30.5.1.1.1 | | dot3EponFecAbility | aFECAbility | 30.5.1.1.1 |
skipping to change at page 28, line 29 skipping to change at page 37, line 29
| dot3EponFecCorrectedBlocks | aFECCorrectedBlocks | 30.5.1.1.1 | | dot3EponFecCorrectedBlocks | aFECCorrectedBlocks | 30.5.1.1.1 |
| | | 5 | | | | 5 |
| | | | | | | |
| dot3EponFecUncorrectableBlocks | aFECUncorrectableBl | 30.5.1.1.1 | | dot3EponFecUncorrectableBlocks | aFECUncorrectableBl | 30.5.1.1.1 |
| | ocks | 6 | | | ocks | 6 |
| | | | | | | |
| dot3EponFecBufferHeadCodingVio | | | | dot3EponFecBufferHeadCodingVio | | |
| lation | | | | lation | | |
+--------------------------------+---------------------+------------+ +--------------------------------+---------------------+------------+
Table 10 Table 11
5. Definitions - The DOT3 EPON MIB module 5. Definitions - The DOT3 EPON MIB module
DOT3-EPON-MIB DEFINITIONS ::= BEGIN DOT3-EPON-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, mib-2, OBJECT-TYPE, Counter32, MODULE-IDENTITY, mib-2, OBJECT-TYPE, Counter32,
Integer32, Unsigned32, Counter64 Integer32, Unsigned32, Counter64
FROM SNMPv2-SMI FROM SNMPv2-SMI
TruthValue, MacAddress TruthValue, MacAddress
FROM SNMPv2-TC FROM SNMPv2-TC
ifIndex ifIndex
FROM IF-MIB FROM IF-MIB
MODULE-COMPLIANCE, OBJECT-GROUP MODULE-COMPLIANCE, OBJECT-GROUP
FROM SNMPv2-CONF FROM SNMPv2-CONF
; ;
dot3EponMIB MODULE-IDENTITY dot3EponMIB MODULE-IDENTITY
LAST-UPDATED "200602080000Z" -- February 8, 2006 LAST-UPDATED "200607210000Z" -- July 21, 2006
ORGANIZATION "IETF Ethernet Interfaces and Hub MIB Working ORGANIZATION "IETF Ethernet Interfaces and Hub MIB Working
Group" Group"
CONTACT-INFO CONTACT-INFO
"WG charter: "WG charter:
http://www.ietf.org/html.charters/hubmib-charter.html http://www.ietf.org/html.charters/hubmib-charter.html
Mailing Lists: Mailing Lists:
General Discussion: hubmib@ietf.org General Discussion: hubmib@ietf.org
To Subscribe: hubmib-request@ietf.org To Subscribe: hubmib-request@ietf.org
In Body: subscribe your_email_address In Body: subscribe your_email_address
Chair: Dan Romascanu Chair: Dan Romascanu
Postal: Avaya Postal: Avaya
Atidim Technology Park, Bldg. 3 Atidim Technology Park, Bldg. 3
Tel Aviv 61131 Tel Aviv 61131
Israel Israel
Tel: +972-3-645-8414 Tel: +972-3-645-8414
E-mail: dromasca@avaya.com E-mail: dromasca@avaya.com
Editor: Lior Khermosh Editor: Lior Khermosh
Postal: Passave Technologies Inc. Postal: PMC-SIERRA
Kohav Hertzelia bldg, Kohav Hertzelia bldg,
94 Hasadnaot St. 94 Hasadnaot St.
Hertzliya Pituach 46120, Hertzliya Pituach 46120,
ISRAEL ISRAEL
P.O.Box 2089 Hertzliya Pituach 46120 Israel P.O.Box 2089 Hertzliya Pituach 46120 Israel
Tel: +972-9-9628000 Ext: 302 Tel: +972-9-9628000 Ext: 302
E-mail: lior.khermosh@passave.com" E-mail: lior_khermosh@pmc-sierra.com"
DESCRIPTION DESCRIPTION
"The objects in this MIB module are used to manage the "The objects in this MIB module are used to manage the
Ethernet in the First Mile(EFM) Ethernet Passive Optical Ethernet in the First Mile(EFM) Ethernet Passive Optical
Network(EPON) Interfaces as defined in IEEE P802.3ah Network(EPON) Interfaces as defined in IEEE P802.3ah
clause 60,64,65. clause 60,64,65.
The following reference is used throughout this MIB module: The following reference is used throughout this MIB module:
[802.3ah] refers to: [802.3ah] refers to:
Information technology - Telecommunications and Information technology - Telecommunications and
information exchange between systems - Local and information exchange between systems - Local and
metropolitan area networks - Specific requirements - metropolitan area networks - Specific requirements -
Part 3: Carrier sense multiple access with collision Part 3: Carrier sense multiple access with collision
detection (CSMA/CD) access method and physical layer detection (CSMA/CD) access method and physical layer
specifications - Media Access Control Parameters, specifications - Media Access Control Parameters,
Physical Layers and Management Parameters for subscriber Physical Layers and Management Parameters for subscriber
access networks. IEEE Std 802.3ah-2004, October 2004. access networks. IEEE Std 802.3ah-2004, October 2004.
Of particular interest are Clause 64(Multi-Point Control Of particular interest are Clause 64(Multi-Point Control
Protocol - MPCP), Clause 65(Point to Multipoint Protocol - MPCP), Clause 65(Point to Multipoint
Reconciliation Sublayer - P2MP RS), Clause 60 (Ethernet Reconciliation Sublayer - P2MP RS), Clause 60 (Ethernet
Passive Optical Network Physical Medium Dependant - EPON Passive Optical Network Physical Medium Dependent - EPON
PMDs), Clause 30, 'Management', and Clause 45, 'Management PMDs), Clause 30, 'Management', and Clause 45, 'Management
Data Input/Output (MDIO) Interface'. Data Input/Output (MDIO) Interface'.
Copyright (C) The Internet Society (2005). This version Copyright (C) The Internet Society (2006). This version
of this MIB module is part of XXXX see the RFC itself for of this MIB module is part of XXXX see the RFC itself for
full legal notices. full legal notices.
Key abbreviations: Key abbreviations:
BER - Bit Error Rate BER - Bit Error Rate
BW - bandwidth
CRC - Cyclic Redundancy Check
EFM - Ethernet First Mile EFM - Ethernet First Mile
EPON - Ethernet Passive Optical Network EPON - Ethernet Passive Optical Network
LLID - Logical Link IDentifier FEC - Forward Error Correction
LLID - Logical Link Identifier
MAC - Media Access Control MAC - Media Access Control
Mbps - Mega-bit per second
MDIO - Management Data Input/Output
MPCP - Multi-Point Control Protocol MPCP - Multi-Point Control Protocol
OLT - Optical Line Terminal (Server unit of the EPON) OLT - Optical Line Terminal (Server unit of the EPON)
OMP - Optical Multi-Point
ONU - Optical Network Unit (Client unit of the EPON) ONU - Optical Network Unit (Client unit of the EPON)
P2MP - Point to Multi-Point
PHY - Physical Layer PHY - Physical Layer
PMD - Physical Medium Dependant PMD - Physical Medium Dependent
PON - Passive Optical Network
RTT - Round Trip Time RTT - Round Trip Time
SLD - Start of LLID Delimiter
TQ - Time Quanta
" "
-- Editor's Note: Replace XXXX with the actual RFC number -- Editor's Note: Replace XXXX with the actual RFC number
-- assigned by RFC Editor and remove this note -- assigned by RFC Editor and remove this note
REVISION "200602080000Z" -- February 8, 2006 REVISION "200607210000Z" -- July 21, 2006
DESCRIPTION "Initial version, published as RFC XXXX." DESCRIPTION "Initial version, published as RFC XXXX."
::= { mib-2 XXX } ::= { mib-2 XXX }
-- Editor's Note (to be removed prior to publication): the -- Editor's Note (to be removed prior to publication): the
-- IANA is requested to assign a value for "XXX" under the -- IANA is requested to assign a value for "XXX" under the
-- 'mib-2' subtree and to record the assignment in the SMI -- 'mib-2' subtree and to record the assignment in the SMI
-- Numbers registry. When the assignment has been made, the -- Numbers registry. When the assignment has been made, the
-- RFC Editor is asked to replace "XXX" (here and in the MIB -- RFC Editor is asked to replace "XXX" (here and in the MIB
-- module) with the assigned value and to remove this note. -- module) with the assigned value and to remove this note.
dot3EponObjects OBJECT IDENTIFIER ::= { dot3EponMIB 1} dot3EponObjects OBJECT IDENTIFIER ::= { dot3EponMIB 1}
dot3EponConformance OBJECT IDENTIFIER ::= { dot3EponMIB 2} dot3EponConformance OBJECT IDENTIFIER ::= { dot3EponMIB 2}
skipping to change at page 31, line 25 skipping to change at page 40, line 35
-- MPCP MIB modules definitions ([802.3ah] clause 30.3.5) -- MPCP MIB modules definitions ([802.3ah] clause 30.3.5)
dot3EponMpcpObjects dot3EponMpcpObjects
OBJECT IDENTIFIER ::= { dot3EponObjects 1 } OBJECT IDENTIFIER ::= { dot3EponObjects 1 }
dot3MpcpControlTable OBJECT-TYPE dot3MpcpControlTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot3MpcpControlEntry SYNTAX SEQUENCE OF Dot3MpcpControlEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Table for dot3 Multi-Point Control Protocol (MPCP) "Table of dot3 Multi-Point Control Protocol (MPCP)
MIB management objects. The entries in the table are MIB objects. The entries in the table are control and
control and status entities of the MPCP. Each object has status objects of the MPCP.
a row for every virtual link according to the proper Each object has a row for every virtual link denoted by
ifIndex. Typically the number of expected virtual link the corresponding ifIndex.
in a PON is like the number of ONUs 32-64 plus an Typically the number of expected virtual links in a PON
additional entry for broadcast LLID (which is marked by is like the number of ONUs, which is 32-64, plus an
0xffff). In the [802.3ah] the LLID is a 2bytes register additional entry for broadcast LLID (with a value of
and the number of LLIDs is limited by that." 0xffff).
In the [802.3ah] the LLID is a 2bytes register and the
number of LLIDs is limited by that."
::= { dot3EponMpcpObjects 1 } ::= { dot3EponMpcpObjects 1 }
dot3MpcpControlEntry OBJECT-TYPE dot3MpcpControlEntry OBJECT-TYPE
SYNTAX Dot3MpcpControlEntry SYNTAX Dot3MpcpControlEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the dot3 MPCP Control table. "An entry in the dot3 MPCP Control table.
Rows in the table are created when ifIndexs are created. Rows exist for an OLT interface and an ONU interface.
Rows in the table are denoted by the ifIndexes and they
are created when the ifIndexes are created.
For the ONU rows are created at system initialization. For the ONU rows are created at system initialization.
For the OLT the rows of the OLT ifIndex and the row of For the OLT the row of the OLT ifIndex and the row of
the ifIndex referring to the broadcast virtual link are the ifIndex referring to the broadcast virtual link are
created at system initialization. For the ifIndexs created at system initialization. For the ifIndexes
referring to the virtual links at the OLT, a row is referring to the virtual links at the OLT, a row is
created when a virtual link is established (ONU created when a virtual link is established (ONU
registers) and deleted when the virtual link is deleted registers) and deleted when the virtual link is deleted
(ONU deregisters). Rows exist for an OLT interface and (ONU deregisters)."
an ONU interface."
INDEX { ifIndex } INDEX { ifIndex }
::= { dot3MpcpControlTable 1} ::= { dot3MpcpControlTable 1}
Dot3MpcpControlEntry ::= Dot3MpcpControlEntry ::=
SEQUENCE { SEQUENCE {
dot3MpcpOperStatus TruthValue, dot3MpcpOperStatus TruthValue,
dot3MpcpAdminState TruthValue, dot3MpcpAdminState TruthValue,
dot3MpcpMode INTEGER, dot3MpcpMode INTEGER,
dot3MpcpSyncTime Unsigned32, dot3MpcpSyncTime Unsigned32,
dot3MpcpLinkID Unsigned32, dot3MpcpLinkID Unsigned32,
skipping to change at page 32, line 30 skipping to change at page 41, line 43
dot3MpcpReceiveElapsed Unsigned32, dot3MpcpReceiveElapsed Unsigned32,
dot3MpcpRoundTripTime Unsigned32, dot3MpcpRoundTripTime Unsigned32,
dot3MpcpMaximumPendingGrants Unsigned32 dot3MpcpMaximumPendingGrants Unsigned32
} }
dot3MpcpOperStatus OBJECT-TYPE dot3MpcpOperStatus OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable reflects the operational state of the "This object reflects the operational state of the
Multi-Point MAC Control sublayer as defined in [802.3ah] Multi-Point MAC Control sublayer as defined in [802.3ah]
clause 64. When the value is true(1) the interface will clause 64. When the value is true(1) the interface will
act as if Multi-point control protocol is enabled. act as if Multi-Point control protocol is enabled.
When the value is false(2) the interface will act as if When the value is false(2) the interface will act as if
it does not have the Multi-point control protocol. The it does not have the Multi-Point control protocol. The
operational state can be changed using the operational state can be changed using the
dot3MpcpAdminState object. dot3MpcpAdminState object.
This object is relevant for an OLT, same for all This object is applicable for an OLT, with the same
virtual links, and for an ONU." value for all virtual interfaces, and for an ONU."
REFERENCE "[802.3ah], 30.3.5.1.2." REFERENCE "[802.3ah], 30.3.5.1.2."
::= { dot3MpcpControlEntry 1 } ::= { dot3MpcpControlEntry 1 }
dot3MpcpAdminState OBJECT-TYPE dot3MpcpAdminState OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable can be used to define the admin state of "This object is used to define the admin state of
the Multi-Point MAC Control sublayer as defined in the Multi-Point MAC Control sublayer as defined in
[802.3ah] clause 64. When selecting the value as true(1) [802.3ah] clause 64. When selecting the value as true(1)
the interface Multi-Point control protocol is enabled. the Multi-Point control protocol of the interface is
enabled.
When selecting the value as false(2) the interface acts When selecting the value as false(2) the interface acts
as if the Multi-point Control protocol does not exist. as if the Multi-Point Control protocol does not exist.
Reading reflects the state of the object and the Reading reflects the state of the object which is the
operation of the Multi-point control protocol mode of mode of operation of the Multi-Point control protocol of
the interface. the interface.
Writing can be done at any time. Writing can be done at any time.
This object is relevant for an OLT, same for all This object is applicable for an OLT, with the same
virtual links, and for an ONU." value for all virtual interfaces, and for an ONU."
REFERENCE "[802.3ah], 30.3.5.2.1." REFERENCE "[802.3ah], 30.3.5.2.1."
DEFVAL { false } DEFVAL { false }
::= { dot3MpcpControlEntry 2 } ::= { dot3MpcpControlEntry 2 }
dot3MpcpMode OBJECT-TYPE dot3MpcpMode OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
olt(1), olt(1),
onu(2) onu(2)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable can be used to identify the operational "This object is used to identify the operational
state of the Multi-Point MAC Control sublayer as state of the Multi-Point MAC Control sublayer as
defined in [802.3ah] clause 64. Reading olt(1) for an defined in [802.3ah] clause 64. Reading olt(1) for an
OLT (server) mode and onu(2) for an ONU (client) mode. OLT (server) mode and onu(2) for an ONU (client) mode.
This object is relevant for an OLT, same for all This object is used to identify the operational mode
virtual links, and for an ONU." for the MPCP tables.
This object is applicable for an OLT, with the same
value for all virtual interfaces, and for an ONU."
REFERENCE "[802.3ah], 30.3.5.1.3." REFERENCE "[802.3ah], 30.3.5.1.3."
DEFVAL { 1 } DEFVAL { 1 }
::= { dot3MpcpControlEntry 3 } ::= { dot3MpcpControlEntry 3 }
dot3MpcpSyncTime OBJECT-TYPE dot3MpcpSyncTime OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "TQ (16nsec)" UNITS "TQ (16nsec)"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A value that reports the 'sync lock time' for "An object that reports the 'sync lock time' of the
an OLT receiver in increments of Time Quanta (TQ) 16ns OLT receiver in increments of Time Quanta (TQ)-16ns
as defined in [802.3ah] 60,64,65. The value returned as defined in [802.3ah] 60,64,65. The value returned
shall be (sync lock time ns)/16. If this value exceeds shall be (sync lock time ns)/16. If this value exceeds
(2^32-1) the value (2^32-1) shall be returned. (2^32-1) the value (2^32-1) shall be returned.
This object is relevant for an OLT, same for all This object is applicable for an OLT, with the same
virtual links, and for an ONU." value for all virtual interfaces, and for an ONU."
REFERENCE "[802.3ah], 64.3.3.2." REFERENCE "[802.3ah], 64.3.3.2."
::= { dot3MpcpControlEntry 4 } ::= { dot3MpcpControlEntry 4 }
dot3MpcpLinkID OBJECT-TYPE dot3MpcpLinkID OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A value that identifies the Logical Link "An object that identifies the Logical Link
identity (LLID) associated with the MAC port as identifier (LLID) associated with the MAC of the virtual
specified in [802.3ah] clause 65.1.3.2.2. link, as specified in [802.3ah] clause 65.1.3.2.2.
This object is relevant for an OLT and an ONU. For This object is applicable for an OLT and an ONU. At the
the same virtual link the value is the same at the ONU OLT it has a value for each virtual interface.
and OLT. Value is assigned when an ONU is registered. For the same virtual link, the ONU and the corresponding
Value is freed when an ONU deregister." virtual MAC of the OLT have the same value.
Value is assigned when the ONU registers.
Value is freed when the ONU deregisters."
REFERENCE "[802.3ah], 30.3.5.1.4." REFERENCE "[802.3ah], 30.3.5.1.4."
::= { dot3MpcpControlEntry 5 } ::= { dot3MpcpControlEntry 5 }
dot3MpcpRemoteMACAddress OBJECT-TYPE dot3MpcpRemoteMACAddress OBJECT-TYPE
SYNTAX MacAddress SYNTAX MacAddress
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A value that identifies the source_address "An object that identifies the source_address
parameter of the last MPCPDUs passed to the MAC Control. parameter of the last MPCPDUs passed to the MAC Control.
This value is updated on reception of a valid frame with This value is updated on reception of a valid frame with
(1) a destination Field equal to the reserved multicast (1) a destination Field equal to the reserved multicast
address for MAC Control specified in [802.3] Annex address for MAC Control specified in [802.3] Annex
31A, (2) lengthOrType field value equal to the reserved 31A, (2) lengthOrType field value equal to the reserved
Type for MAC Control as specified in [802.3] Annex Type for MAC Control as specified in [802.3] Annex
31A. (3) an MPCP subtype value equal to the subtype 31A. (3) an MPCP subtype value equal to the subtype
reserved for MPCP as specified in [802.3ah] Annex 31A. reserved for MPCP as specified in [802.3ah] Annex 31A.
This object is relevant for an OLT and an ONU. This object is applicable for an OLT and an ONU. At the
The value reflects the MAC address of the remote entry OLT it has a value for each virtual interface.
and therefore the OLT hold a value for each LLID and the The value reflects the MAC address of the remote entity
ONU has a single value which is the OLT MAC address. " and therefore the OLT holds a value for each LLID which
is the MAC address of the ONU and the ONU has a single
value which is the OLT MAC address."
REFERENCE "[802.3ah], 30.3.5.1.5." REFERENCE "[802.3ah], 30.3.5.1.5."
::= { dot3MpcpControlEntry 6 } ::= { dot3MpcpControlEntry 6 }
dot3MpcpRegistrationState OBJECT-TYPE dot3MpcpRegistrationState OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
unregistered(1), unregistered(1),
registering(2), registering(2),
registered(3) registered(3)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A value that identifies the operational state "An object that identifies the registration state
of the Multi-Point MAC Control sublayer as defined in of the Multi-Point MAC Control sublayer as defined in
[802.3ah] clause 64. When this object has the [802.3ah] clause 64. When this object has the
enumeration unregistered(1) the interface may be used enumeration unregistered(1) the interface is
for registering a link partner. When this object has unregistered and may be used for registering a link
the enumeration registering(2) the interface is in the partner. When this object has the enumeration
process of registering a link-partner. When this registering(2) the interface is in the process of
object has the enumeration registered(3) the registering a link-partner. When this object has the
interface has an established link-partner. enumeration registered(3) the interface has an
This object is relevant for an OLT and an ONU. For established link-partner.
the OLT it provides an indication per LLID." This object is applicable for an OLT and an ONU. At the
OLT it has a value for each virtual interface."
REFERENCE "[802.3ah], 30.3.5.1.6." REFERENCE "[802.3ah], 30.3.5.1.6."
::= { dot3MpcpControlEntry 7 } ::= { dot3MpcpControlEntry 7 }
dot3MpcpTransmitElapsed OBJECT-TYPE dot3MpcpTransmitElapsed OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "TQ (16nsec)" UNITS "TQ (16nsec)"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A value that reports the interval from last "An object that reports the interval from last
MPCP frame transmission in increments of Time Quanta MPCP frame transmission in increments of Time Quanta
(TQ) 16ns. The value returned shall be (interval from (TQ)-16ns. The value returned shall be (interval from
last MPCP frame transmission in ns)/16. If this value last MPCP frame transmission in ns)/16. If this value
exceeds (2^32-1) the value (2^32-1) shall be returned. exceeds (2^32-1) the value (2^32-1) shall be returned.
This object is relevant for an OLT and an ONU. For This object is applicable for an OLT and an ONU. At the
the OLT it provides an indication per LLID." OLT it has a value for each virtual interface."
REFERENCE "[802.3ah], 30.3.5.1.19." REFERENCE "[802.3ah], 30.3.5.1.19."
::= { dot3MpcpControlEntry 8 } ::= { dot3MpcpControlEntry 8 }
dot3MpcpReceiveElapsed OBJECT-TYPE dot3MpcpReceiveElapsed OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "TQ (16nsec)" UNITS "TQ (16nsec)"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A value that reports the interval from last "An object that reports the interval from last MPCP frame
MPCP frame reception in increments of Time Quanta (TQ) reception in increments of Time Quanta (TQ)-16ns. The
16ns. The value returned shall be (interval from last value returned shall be (interval from last MPCP frame
MPCP last MPCP frame reception in ns)/16. If this value reception in ns)/16. If this value exceeds (2^32-1) the
exceeds (2^32-1) the value (2^32-1) shall be returned. value (2^32-1) shall be returned.
This object is relevant for an OLT and an ONU. For This object is applicable for an OLT and an ONU. At the
the OLT it provides an indication per LLID." OLT it has a value for each virtual interface."
REFERENCE "[802.3ah], 30.3.5.1.20." REFERENCE "[802.3ah], 30.3.5.1.20."
::= { dot3MpcpControlEntry 9 } ::= { dot3MpcpControlEntry 9 }
dot3MpcpRoundTripTime OBJECT-TYPE dot3MpcpRoundTripTime OBJECT-TYPE
SYNTAX Unsigned32 (0..'ffff'h) SYNTAX Unsigned32 (0..'ffff'h)
UNITS "TQ (16nsec)" UNITS "TQ (16nsec)"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A value that reports the MPCP round trip time "An object that reports the MPCP round trip time in
in increments of Time Quanta (TQ) 16ns. The value increments of Time Quanta (TQ)-16ns. The value returned
returned shall be (round trip time in ns)/16. If this shall be (round trip time in ns)/16. If this value
value exceeds (2^16-1) the value (2^16-1) shall be exceeds (2^16-1) the value (2^16-1) shall be returned.
returned. This object is relevant for an OLT only. This object is applicable for an OLT and an ONU. At the
For the OLT there is a value per LLID" OLT it has a value for each virtual interface."
REFERENCE "[802.3ah], 30.3.5.1.21." REFERENCE "[802.3ah], 30.3.5.1.21."
::= { dot3MpcpControlEntry 10 } ::= { dot3MpcpControlEntry 10 }
dot3MpcpMaximumPendingGrants OBJECT-TYPE dot3MpcpMaximumPendingGrants OBJECT-TYPE
SYNTAX Unsigned32 (0..255) SYNTAX Unsigned32 (0..255)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A value that indicates the maximum number of "An object that reports the maximum number of grants an
grants an ONU can store. The maximum number of grants an ONU can store for handling. The maximum number of grants
ONU can store has a range of 0 to 255. an ONU can store for handling has a range of 0 to 255.
This object is relevant for an OLT and an ONU. For This object is applicable for an OLT and an ONU. At the
the OLT there is a value per LLID" OLT it has a value for each virtual interface.
At the OLT the value should be zero."
REFERENCE "[802.3ah], 30.3.5.1.24." REFERENCE "[802.3ah], 30.3.5.1.24."
::= { dot3MpcpControlEntry 11 } ::= { dot3MpcpControlEntry 11 }
dot3MpcpStatTable OBJECT-TYPE dot3MpcpStatTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot3MpcpStatEntry SYNTAX SEQUENCE OF Dot3MpcpStatEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table defines the list of statistics counters for "This table defines the list of statistics counters of
[802.3ah] clause 64 MPCP interface. Each object has an interface implementing the [802.3ah] clause 64 MPCP.
a row for every virtual link according to the proper Each object has a row for every virtual link denoted by
ifIndex. Typically the number of expected virtual link the corresponding ifIndex.
in a PON is like the number of ONUs 32-64 plus an Typically the number of expected virtual links in a PON
additional entry for broadcast LLID (which is marked by is like the number of ONUs, which is 32-64, plus an
0xffff). In the [802.3ah] the LLID is a 2bytes register additional entry for broadcast LLID (with a value of
and the number of LLIDs is limited by that." 0xffff).
In the [802.3ah] the LLID is a 2bytes register and the
number of LLIDs is limited by that."
::= { dot3EponMpcpObjects 2 } ::= { dot3EponMpcpObjects 2 }
dot3MpcpStatEntry OBJECT-TYPE dot3MpcpStatEntry OBJECT-TYPE
SYNTAX Dot3MpcpStatEntry SYNTAX Dot3MpcpStatEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Table entries for the table of statistics counters of "Table entries for the table of statistics counters of
[802.3ah] clause 64 MPCP interface. the [802.3ah] clause 64 MPCP interface.
Rows in the table are created when ifIndexs are created. Rows exist for an OLT interface and an ONU interface.
Rows in the table are denoted by the ifIndexes and they
are created when the ifIndexes are created.
For the ONU rows are created at system initialization. For the ONU rows are created at system initialization.
For the OLT the row of the OLT ifIndex and the row of
For the OLT the rows of the OLT ifIndex and the row of
the ifIndex referring to the broadcast virtual link are the ifIndex referring to the broadcast virtual link are
created at system initialization. For the ifIndexs created at system initialization. For the ifIndexes
referring to the virtual links at the OLT, a row is referring to the virtual links at the OLT, a row is
created when a virtual link is established (ONU created when a virtual link is established (ONU
registers) and deleted when the virtual link is deleted registers) and deleted when the virtual link is deleted
(ONU deregisters). Rows exist for an OLT interface and (ONU deregisters)."
an ONU interface."
INDEX { ifIndex} INDEX { ifIndex}
::= { dot3MpcpStatTable 1 } ::= { dot3MpcpStatTable 1 }
Dot3MpcpStatEntry ::= Dot3MpcpStatEntry ::=
SEQUENCE { SEQUENCE {
dot3MpcpMACCtrlFramesTransmitted Counter64, dot3MpcpMACCtrlFramesTransmitted Counter64,
dot3MpcpMACCtrlFramesReceived Counter64, dot3MpcpMACCtrlFramesReceived Counter64,
dot3MpcpDiscoveryWindowsSent Counter32, dot3MpcpDiscoveryWindowsSent Counter32,
dot3MpcpDiscoveryTimeout Counter32, dot3MpcpDiscoveryTimeout Counter32,
skipping to change at page 37, line 44 skipping to change at page 47, line 20
dot3MpcpMACCtrlFramesTransmitted OBJECT-TYPE dot3MpcpMACCtrlFramesTransmitted OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
UNITS "frames" UNITS "frames"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of MPCP frames passed to the MAC sublayer for "A count of MPCP frames passed to the MAC sublayer for
transmission. This counter is incremented when a transmission. This counter is incremented when a
MA_CONTROL.request service primitive is generated within MA_CONTROL.request service primitive is generated within
the MAC control sublayer with an opcode indicating a the MAC control sublayer with an opcode indicating an
MPCP frame. MPCP frame.
This counter is relevant for an OLT and an ONU. For This object is applicable for an OLT and an ONU. At the
the OLT there is a value per LLID." OLT it has a value for each virtual interface.
Discontinuities of this counter can occur at
re-initialization of the management system, and at other
times as indicated by the value of the
ifCounterDiscontinuityTime."
REFERENCE "[802.3ah], 30.3.5.1.7." REFERENCE "[802.3ah], 30.3.5.1.7."
::= { dot3MpcpStatEntry 1 } ::= { dot3MpcpStatEntry 1 }
dot3MpcpMACCtrlFramesReceived OBJECT-TYPE dot3MpcpMACCtrlFramesReceived OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
UNITS "frames" UNITS "frames"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of MPCP frames passed by the MAC sublayer to the "A count of MPCP frames passed by the MAC sublayer to the
MAC Control sublayer. This counter is incremented when a MAC Control sublayer. This counter is incremented when a
ReceiveFrame function call returns a valid frame with: ReceiveFrame function call returns a valid frame with:
(1) a lengthOrType field value equal to the reserved (1) a lengthOrType field value equal to the reserved
Type for 802.3_MAC_Control as specified in 31.4.1.3, and Type for 802.3_MAC_Control as specified in 31.4.1.3, and
(2) an opcode indicating a MPCP frame. (2) an opcode indicating an MPCP frame.
This counter is relevant for an OLT and an ONU. For This object is applicable for an OLT and an ONU. At the
the OLT there is a value per LLID." OLT it has a value for each virtual interface.
Discontinuities of this counter can occur at
re-initialization of the management system, and at other
times as indicated by the value of the
ifCounterDiscontinuityTime."
REFERENCE "[802.3ah], 30.3.5.1.8." REFERENCE "[802.3ah], 30.3.5.1.8."
::= { dot3MpcpStatEntry 2} ::= { dot3MpcpStatEntry 2}
dot3MpcpDiscoveryWindowsSent OBJECT-TYPE dot3MpcpDiscoveryWindowsSent OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of discovery windows generated. The counter is "A count of discovery windows generated. The counter is
incremented by one for each generated discovery window. incremented by one for each generated discovery window.
This counter is relevant for an OLT and an ONU. For This object is applicable for an OLT and an ONU. At the
the OLT there is a value per LLID. At the ONU value OLT it has a value for each virtual interface.
should be zero." At the ONU the value should be zero.
Discontinuities of this counter can occur at
re-initialization of the management system, and at other
times as indicated by the value of the
ifCounterDiscontinuityTime."
REFERENCE "[802.3ah], 30.3.5.1.22." REFERENCE "[802.3ah], 30.3.5.1.22."
::= { dot3MpcpStatEntry 3} ::= { dot3MpcpStatEntry 3}
dot3MpcpDiscoveryTimeout OBJECT-TYPE dot3MpcpDiscoveryTimeout OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of the number of times a discovery timeout "A count of the number of times a discovery timeout
occurs. Increment the counter by one for each discovery occurs. Increment the counter by one for each discovery
processing state-machine reset resulting from timeout processing state-machine reset resulting from timeout
waiting for message arrival. waiting for message arrival.
This counter is relevant for an OLT and an ONU. For This object is applicable for an OLT and an ONU. At the
the OLT there is a value per LLID." OLT it has a value for each virtual interface.
Discontinuities of this counter can occur at
re-initialization of the management system, and at other
times as indicated by the value of the
ifCounterDiscontinuityTime."
REFERENCE "[802.3ah], 30.3.5.1.23." REFERENCE "[802.3ah], 30.3.5.1.23."
::= { dot3MpcpStatEntry 4} ::= { dot3MpcpStatEntry 4}
dot3MpcpTxRegRequest OBJECT-TYPE dot3MpcpTxRegRequest OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
UNITS "frames" UNITS "frames"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of the number of times a REGISTER_REQ MPCP "A count of the number of times a REGISTER_REQ MPCP
frames transmission occurs. Increment the counter by one frame transmission occurs. Increment the counter by one
for each REGISTER_REQ MPCP frame transmitted as defined for each REGISTER_REQ MPCP frame transmitted as defined
in [802.3ah] clause 64. This counter is mandatory for an in [802.3ah] clause 64.
ONU. This counter is relevant for an OLT and an ONU. This object is applicable for an OLT and an ONU. At the
For the OLT there is a value per LLID. At the OLT value OLT it has a value for each virtual interface.
should be zero."
At the OLT the value should be zero.
Discontinuities of this counter can occur at
re-initialization of the management system, and at other
times as indicated by the value of the
ifCounterDiscontinuityTime."
REFERENCE "[802.3ah], 30.3.5.1.12." REFERENCE "[802.3ah], 30.3.5.1.12."
::= { dot3MpcpStatEntry 5} ::= { dot3MpcpStatEntry 5}
dot3MpcpRxRegRequest OBJECT-TYPE dot3MpcpRxRegRequest OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
UNITS "frames" UNITS "frames"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of the number of times a REGISTER_REQ MPCP "A count of the number of times a REGISTER_REQ MPCP
frames reception occurs. A single counter at the ONU and frame reception occurs.
a set of counters, one for each LLID, at the OLT.
Increment the counter by one for each REGISTER_REQ MPCP Increment the counter by one for each REGISTER_REQ MPCP
frame received for each LLID as defined in [802.3ah] frame received as defined in [802.3ah] clause 64.
clause 64. This counter is mandatory for an ONU and for This object is applicable for an OLT and an ONU. At the
an OLT. For the OLT there is a value per LLID. OLT it has a value for each virtual interface.
At the ONU value should be zero." At the ONU the value should be zero.
Discontinuities of this counter can occur at
re-initialization of the management system, and at other
times as indicated by the value of the
ifCounterDiscontinuityTime."
REFERENCE "[802.3ah], 30.3.5.1.17." REFERENCE "[802.3ah], 30.3.5.1.17."
::= { dot3MpcpStatEntry 6} ::= { dot3MpcpStatEntry 6}
dot3MpcpTxRegAck OBJECT-TYPE dot3MpcpTxRegAck OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
UNITS "frames" UNITS "frames"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of the number of times a REGISTER_ACK MPCP "A count of the number of times a REGISTER_ACK MPCP
frames transmission occurs. Increment the counter by one frame transmission occurs. Increment the counter by one
for each REGISTER_ACK MPCP frame transmitted as defined for each REGISTER_ACK MPCP frame transmitted as defined
in [802.3ah] clause 64. This counter is mandatory for an in [802.3ah] clause 64.
ONU. This object is relevant for an OLT and an ONU. This object is applicable for an OLT and an ONU. At the
For the OLT there is a value per LLID. At the OLT the OLT it has a value for each virtual interface.
value should be zero." At the OLT the value should be zero.
Discontinuities of this counter can occur at
re-initialization of the management system, and at other
times as indicated by the value of the
ifCounterDiscontinuityTime."
REFERENCE "[802.3ah], 30.3.5.1.10." REFERENCE "[802.3ah], 30.3.5.1.10."
::= { dot3MpcpStatEntry 7} ::= { dot3MpcpStatEntry 7}
dot3MpcpRxRegAck OBJECT-TYPE dot3MpcpRxRegAck OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
UNITS "frames" UNITS "frames"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of the number of times a REGISTER_ACK MPCP "A count of the number of times a REGISTER_ACK MPCP
frames reception occurs. A single counter at the ONU and frame reception occurs.
a set of counters, one for each LLID, at the OLT.
Increment the counter by one for each REGISTER_ACK MPCP Increment the counter by one for each REGISTER_ACK MPCP
frame received for each LLID, as defined in [802.3ah] frame received, as defined in [802.3ah] clause 64.
clause 64. This counter is mandatory for an ONU and for This object is applicable for an OLT and an ONU. At the
an OLT. For the OLT there is a value per LLID. OLT it has a value for each virtual interface.
At the ONU the value should be zero." At the ONU the value should be zero.
Discontinuities of this counter can occur at
re-initialization of the management system, and at other
times as indicated by the value of the
ifCounterDiscontinuityTime."
REFERENCE "[802.3ah], 30.3.5.1.15." REFERENCE "[802.3ah], 30.3.5.1.15."
::= { dot3MpcpStatEntry 8} ::= { dot3MpcpStatEntry 8}
dot3MpcpTxReport OBJECT-TYPE dot3MpcpTxReport OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
UNITS "frames" UNITS "frames"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of the number of times a REPORT MPCP frames "A count of the number of times a REPORT MPCP frame
transmission occurs. Increment the counter by one for transmission occurs. Increment the counter by one for
each REPORT MPCP frame transmitted as defined in each REPORT MPCP frame transmitted as defined in
[802.3ah] clause 64. This counter is mandatory for an [802.3ah] clause 64.
ONU. This counter is relevant for an OLT and an ONU. This object is applicable for an OLT and an ONU. At the
For the OLT there is a value per LLID. OLT it has a value for each virtual interface.
At the OLT value should be zero." At the OLT the value should be zero.
Discontinuities of this counter can occur at
re-initialization of the management system, and at other
times as indicated by the value of the
ifCounterDiscontinuityTime."
REFERENCE "[802.3ah], 30.3.5.1.13." REFERENCE "[802.3ah], 30.3.5.1.13."
::= { dot3MpcpStatEntry 9} ::= { dot3MpcpStatEntry 9}
dot3MpcpRxReport OBJECT-TYPE dot3MpcpRxReport OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
UNITS "frames" UNITS "frames"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of the number of times a REPORT MPCP frames "A count of the number of times a REPORT MPCP frame
reception occurs. A single counter at the ONU and a set reception occurs.
of counters, one for each LLID, at the OLT. Increment
the counter by one for each REPORT MPCP frame received Increment the counter by one for each REPORT MPCP frame
for each LLID, as defined in [802.3ah] clause 64. received, as defined in [802.3ah] clause 64.
This counter is mandatory for an ONU and for an OLT. This object is applicable for an OLT and an ONU. At the
For the OLT there is a value per LLID. OLT it has a value for each virtual interface.
At the ONU value should be zero." At the ONU the value should be zero.
Discontinuities of this counter can occur at
re-initialization of the management system, and at other
times as indicated by the value of the
ifCounterDiscontinuityTime."
REFERENCE "[802.3ah], 30.3.5.1.18." REFERENCE "[802.3ah], 30.3.5.1.18."
::= { dot3MpcpStatEntry 10} ::= { dot3MpcpStatEntry 10}
dot3MpcpTxGate OBJECT-TYPE dot3MpcpTxGate OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
UNITS "frames" UNITS "frames"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of the number of times a GATE MPCP frames "A count of the number of times a GATE MPCP frame
transmission occurs. A set of counters, one for each transmission occurs.
LLID, at the OLT. Increment the counter by one for each Increment the counter by one for each GATE MPCP frame
GATE MPCP frame transmitted, for each LLID, as defined transmitted, as defined in [802.3ah] clause 64.
in [802.3ah] clause 64. This counter is mandatory for an This object is applicable for an OLT and an ONU. At the
OLT. This counter is relevant for an OLT and an ONU. OLT it has a value for each virtual interface.
For the OLT there is a value per LLID. At the ONU the value should be zero.
At the ONU the value should be zero." Discontinuities of this counter can occur at
re-initialization of the management system, and at other
times as indicated by the value of the
ifCounterDiscontinuityTime."
REFERENCE "[802.3ah], 30.3.5.1.9." REFERENCE "[802.3ah], 30.3.5.1.9."
::= { dot3MpcpStatEntry 11} ::= { dot3MpcpStatEntry 11}
dot3MpcpRxGate OBJECT-TYPE dot3MpcpRxGate OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
UNITS "frames" UNITS "frames"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of the number of times a GATE MPCP frames "A count of the number of times a GATE MPCP frame
reception occurs. A single counter at the ONU and a set reception occurs.
of counters, one for each LLID ,at the OLT. Increment Increment the counter by one for each GATE MPCP frame
the counter by one for each GATE MPCP frame received, received, as defined in [802.3ah] clause 64.
for each LLID, as defined in [802.3ah] clause 64. This This object is applicable for an OLT and an ONU. At the
counter is mandatory for an ONU and for an OLT. For the OLT it has a value for each virtual interface.
OLT there is a value per LLID. At the OLT the value At the OLT the value should be zero.
should be zero." Discontinuities of this counter can occur at
re-initialization of the management system, and at other
times as indicated by the value of the
ifCounterDiscontinuityTime."
REFERENCE "[802.3ah], 30.3.5.1.14." REFERENCE "[802.3ah], 30.3.5.1.14."
::= { dot3MpcpStatEntry 12} ::= { dot3MpcpStatEntry 12}
dot3MpcpTxRegister OBJECT-TYPE dot3MpcpTxRegister OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
UNITS "frames" UNITS "frames"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of the number of times a REGISTER MPCP frames "A count of the number of times a REGISTER MPCP frame
transmission occurs. A set of counters, one for each transmission occurs.
LLID, at the OLT. Increment the counter by one for each Increment the counter by one for each REGISTER MPCP
REGISTER MPCP frame transmitted, for each LLID, as frame transmitted, as defined in [802.3ah] clause 64.
defined in [802.3ah] clause 64. This counter is This object is applicable for an OLT and an ONU. At the
mandatory for an OLT. This counter is relevant for an OLT it has a value for each virtual interface.
OLT and an ONU. For the OLT there is a value per LLID. At the ONU the value should be zero.
At the ONU the value should be zero." Discontinuities of this counter can occur at
re-initialization of the management system, and at other
times as indicated by the value of the
ifCounterDiscontinuityTime."
REFERENCE "[802.3ah], 30.3.5.1.11." REFERENCE "[802.3ah], 30.3.5.1.11."
::= { dot3MpcpStatEntry 13} ::= { dot3MpcpStatEntry 13}
dot3MpcpRxRegister OBJECT-TYPE dot3MpcpRxRegister OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
UNITS "frames" UNITS "frames"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of the number of times a REGISTER MPCP frames "A count of the number of times a REGISTER MPCP frame
reception occurs. A single counter at the ONU and a set reception occurs.
of counters, one for each LLID, at the OLT. Increment Increment the counter by one for each REGISTER MPCP
the counter by one for each REGISTER MPCP frame frame received, as defined in [802.3ah] clause 64.
received, for each LLID, as defined in [802.3ah] clause This object is applicable for an OLT and an ONU. At the
64. This counter is mandatory for an ONU and for an OLT. OLT it has a value for each virtual interface.
For the OLT there is a value per LLID. At the OLT the value should be zero.
at the OLT the value should be zero." Discontinuities of this counter can occur at
re-initialization of the management system, and at other
times as indicated by the value of the
ifCounterDiscontinuityTime."
REFERENCE "[802.3ah], 30.3.5.1.16." REFERENCE "[802.3ah], 30.3.5.1.16."
::= { dot3MpcpStatEntry 14} ::= { dot3MpcpStatEntry 14}
-- OMPEmulation managed object definitions -- Optical Multi Point Emulation (OMPEmulation)
-- managed object definitions
dot3OmpEmulationObjects OBJECT IDENTIFIER ::={dot3EponObjects 2} dot3OmpEmulationObjects OBJECT IDENTIFIER ::={dot3EponObjects 2}
dot3OmpEmulationTable OBJECT-TYPE dot3OmpEmulationTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot3OmpEmulationEntry SYNTAX SEQUENCE OF Dot3OmpEmulationEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Table for dot3 OmpEmulation MIB objects. The table "Table of dot3 OmpEmulation MIB objects. The table
defines the parameter settings of the OMP Emulation defines the management settings of the OMPEmulation
layer. Each object has a row for every virtual link sublayer.
according to the proper ifIndex. Typically the number Each object has a row for every virtual link denoted by
of expected virtual link in a PON is like the number of the corresponding ifIndex.
ONUs 32-64 plus an additional entry for broadcast LLID Typically the number of expected virtual links in a PON
(which is marked by 0xffff). In the [802.3ah] the LLID is like the number of ONUs, which is 32-64, plus an
is a 2bytes register and the number of LLIDs limited by additional entry for broadcast LLID (with a value of
that." 0xffff).
In the [802.3ah] the LLID is a 2bytes register and the
number of LLIDs is limited by that."
::= { dot3OmpEmulationObjects 1 } ::= { dot3OmpEmulationObjects 1 }
dot3OmpEmulationEntry OBJECT-TYPE dot3OmpEmulationEntry OBJECT-TYPE
SYNTAX Dot3OmpEmulationEntry SYNTAX Dot3OmpEmulationEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the dot3 OmpEmulation table. "An entry in the dot3 OmpEmulation table.
Rows exist for an OLT interface and an ONU interface.
Rows in the table are created when ifIndexs are created. Rows in the table are denoted by the ifIndexes and they
are created when the ifIndexes are created.
For the ONU rows are created at system initialization. For the ONU rows are created at system initialization.
For the OLT the rows of the OLT ifIndex and the row of For the OLT the row of the OLT ifIndex and the row of
the ifIndex referring to the broadcast virtual link are the ifIndex referring to the broadcast virtual link are
created at system initialization. For the ifIndexs created at system initialization. For the ifIndexes
referring to the virtual links at the OLT, a row is referring to the virtual links at the OLT, a row is
created when a virtual link is established (ONU created when a virtual link is established (ONU
registers) and deleted when the virtual link is deleted registers) and deleted when the virtual link is deleted
(ONU deregisters). Rows exist for an OLT interface and (ONU deregisters)."
an ONU interface."
INDEX { ifIndex } INDEX { ifIndex }
::= { dot3OmpEmulationTable 1 } ::= { dot3OmpEmulationTable 1 }
Dot3OmpEmulationEntry ::= Dot3OmpEmulationEntry ::=
SEQUENCE { SEQUENCE {
dot3OmpEmulationType INTEGER dot3OmpEmulationType INTEGER
} }
dot3OmpEmulationType OBJECT-TYPE dot3OmpEmulationType OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
unknown(1), unknown(1),
olt(2), olt(2),
onu(3) onu(3)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A value that indicates that mode of operation "An object that indicates the mode of operation
of the Reconciliation Sublayer for Point to Point of the Reconciliation Sublayer for Point to Point
Emulation (see [802.3ah] clause 65.1). unknown(1) value Emulation (see [802.3ah] clause 65.1). unknown(1) value
is assigned in initializing, true state or type not yet is assigned in initialization, true state or type not
known. olt(2) value is assigned when Sublayer operating yet known. olt(2) value is assigned when the sublayer is
in OLT mode. onu(3) value is assigned when Sublayer operating in OLT mode. onu(3) value is assigned when the
operating in ONU mode. sublayer is operating in ONU mode.
This object is relevant for an OLT, same for all This object is applicable for an OLT, with the same
virtual links, and for an ONU." value for all virtual interfaces, and for an ONU."
REFERENCE "[802.3ah], 30.3.7.1.2." REFERENCE "[802.3ah], 30.3.7.1.2."
::= { dot3OmpEmulationEntry 1} ::= { dot3OmpEmulationEntry 1}
dot3OmpEmulationStatTable OBJECT-TYPE dot3OmpEmulationStatTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot3OmpEmulationStatEntry SYNTAX SEQUENCE OF Dot3OmpEmulationStatEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table defines the list of statistics counters for "This table defines the list of statistics counters of
[802.3ah] clause 65 OMP interface. [802.3ah] clause 65 OMPEmulation sublayer.
Each object has a row for every virtual link Each object has a row for every virtual link denoted by
according to the proper ifIndex. Typically the number the corresponding ifIndex.
of expected virtual link in a PON is like the number of Typically the number of expected virtual links in a PON
ONUs 32-64 plus an additional entry for broadcast LLID is like the number of ONUs, which is 32-64, plus an
(which is marked by 0xffff). In the [802.3ah] the LLID additional entry for broadcast LLID (with a value of
is a 2bytes register and the number of LLIDs limited by 0xffff).
that." In the [802.3ah] the LLID is a 2bytes register and the
number of LLIDs is limited by that."
::= { dot3OmpEmulationObjects 2} ::= { dot3OmpEmulationObjects 2}
dot3OmpEmulationStatEntry OBJECT-TYPE dot3OmpEmulationStatEntry OBJECT-TYPE
SYNTAX Dot3OmpEmulationStatEntry SYNTAX Dot3OmpEmulationStatEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Table entries for the table of statistics counters of "Table entries for the table of statistics counters of
[802.3ah] clause 65 OMP interface. [802.3ah] clause 65 OMPEmulation sublayer.
Rows in the table are created when ifIndexs are created. Rows exist for an OLT interface and an ONU interface.
Rows in the table are denoted by the ifIndexes and they
are created when the ifIndexes are created.
For the ONU rows are created at system initialization. For the ONU rows are created at system initialization.
For the OLT the rows of the OLT ifIndex and the row of For the OLT the row of the OLT ifIndex and the row of
the ifIndex referring to the broadcast virtual link are the ifIndex referring to the broadcast virtual link are
created at system initialization. For the ifIndexs created at system initialization. For the ifIndexes
referring to the virtual links at the OLT, a row is referring to the virtual links at the OLT, a row is
created when a virtual link is established (ONU created when a virtual link is established (ONU
registers) and deleted when the virtual link is deleted registers) and deleted when the virtual link is deleted
(ONU deregisters). Rows exist for an OLT interface and (ONU deregisters)."
an ONU interface."
INDEX { ifIndex} INDEX { ifIndex}
::= { dot3OmpEmulationStatTable 1 } ::= { dot3OmpEmulationStatTable 1 }
Dot3OmpEmulationStatEntry::= Dot3OmpEmulationStatEntry::=
SEQUENCE { SEQUENCE {
dot3OmpEmulationSLDErrors Counter64, dot3OmpEmulationSLDErrors Counter64,
dot3OmpEmulationCRC8Errors Counter64, dot3OmpEmulationCRC8Errors Counter64,
dot3OmpEmulationBadLLID Counter64, dot3OmpEmulationBadLLID Counter64,
dot3OmpEmulationGoodLLID Counter64, dot3OmpEmulationGoodLLID Counter64,
dot3OmpEmulationOnuPonCastLLID Counter64, dot3OmpEmulationOnuPonCastLLID Counter64,
skipping to change at page 45, line 5 skipping to change at page 55, line 38
} }
dot3OmpEmulationSLDErrors OBJECT-TYPE dot3OmpEmulationSLDErrors OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
UNITS "frames" UNITS "frames"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of frames received that do not contain a valid "A count of frames received that do not contain a valid
SLD field as defined in [802.3ah] clause 65.1.3.3.1. SLD field as defined in [802.3ah] clause 65.1.3.3.1.
This counter is relevant for an OLT and an ONU. For the This object is applicable for an OLT and an ONU. At the
OLT there is a value per LLID." OLT it has a value for each virtual interface.
Discontinuities of this counter can occur at
re-initialization of the management system, and at other
times as indicated by the value of the
ifCounterDiscontinuityTime."
REFERENCE "[802.3ah], 30.3.7.1.3." REFERENCE "[802.3ah], 30.3.7.1.3."
::= { dot3OmpEmulationStatEntry 1} ::= { dot3OmpEmulationStatEntry 1}
dot3OmpEmulationCRC8Errors OBJECT-TYPE dot3OmpEmulationCRC8Errors OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
UNITS "frames" UNITS "frames"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of frames received that contain a valid SLD "A count of frames received that contain a valid SLD
field, as defined in [802.3ah] clause 65.1.3.3.1, but do field, as defined in [802.3ah] clause 65.1.3.3.1, but do
not pass the CRC-8 check as defined in [802.3ah] clause not pass the CRC-8 check as defined in [802.3ah] clause
65.1.3.3.3. 65.1.3.3.3.
This counter is relevant for an OLT and an ONU. For the This object is applicable for an OLT and an ONU. At the
OLT there is a value per LLID." OLT it has a value for each virtual interface.
Discontinuities of this counter can occur at
re-initialization of the management system, and at other
times as indicated by the value of the
ifCounterDiscontinuityTime."
REFERENCE "[802.3ah], 30.3.7.1.4." REFERENCE "[802.3ah], 30.3.7.1.4."
::= { dot3OmpEmulationStatEntry 2} ::= { dot3OmpEmulationStatEntry 2}
dot3OmpEmulationBadLLID OBJECT-TYPE dot3OmpEmulationBadLLID OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
UNITS "frames" UNITS "frames"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of frames received that contain a valid SLD "A count of frames received that contain a valid SLD
field, as defined in [802.3ah] clause 65.1.3.3.1, and field, as defined in [802.3ah] clause 65.1.3.3.1, and
pass the CRC-8 check, as defined in [802.3ah] clause pass the CRC-8 check, as defined in [802.3ah] clause
65.1.3.3.3, but are discarded due to the LLID check as 65.1.3.3.3, but are discarded due to the LLID check as
defined in [802.3ah] clause 65.1.3.3.2. defined in [802.3ah] clause 65.1.3.3.2.
This counter is relevant for an OLT and an ONU. For the This object is applicable for an OLT and an ONU. At the
OLT there is a value per LLID." OLT it has a value for each virtual interface.
Discontinuities of this counter can occur at
re-initialization of the management system, and at other
times as indicated by the value of the
ifCounterDiscontinuityTime."
REFERENCE "[802.3ah], 30.3.7.1.8." REFERENCE "[802.3ah], 30.3.7.1.8."
::= { dot3OmpEmulationStatEntry 3} ::= { dot3OmpEmulationStatEntry 3}
dot3OmpEmulationGoodLLID OBJECT-TYPE dot3OmpEmulationGoodLLID OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
UNITS "frames" UNITS "frames"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of frames received that contain a valid SLD "A count of frames received that contain a valid SLD
field, as defined in [802.3ah] clause 65.1.3.3.1, and field, as defined in [802.3ah] clause 65.1.3.3.1, and
pass the CRC-8 check, as defined in [802.3ah] clause pass the CRC-8 check, as defined in [802.3ah] clause
65.1.3.3.3. 65.1.3.3.3.
This object is applicable for an OLT and an ONU. At the
This counter is relevant for an OLT and an ONU. For the OLT it has a value for each virtual interface.
OLT there is a value per LLID." Discontinuities of this counter can occur at
re-initialization of the management system, and at other
times as indicated by the value of the
ifCounterDiscontinuityTime."
REFERENCE "[802.3ah], 30.3.7.1.5." REFERENCE "[802.3ah], 30.3.7.1.5."
::= { dot3OmpEmulationStatEntry 4} ::= { dot3OmpEmulationStatEntry 4}
dot3OmpEmulationOnuPonCastLLID OBJECT-TYPE dot3OmpEmulationOnuPonCastLLID OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
UNITS "frames" UNITS "frames"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of frames received that contain a valid SLD "A count of frames received that contain a valid SLD
field in an ONU, as defined in [802.3ah] 65.1.3.3.1, field, as defined in [802.3ah] 65.1.3.3.1,
passes the CRC-8 check, as defined in [802.3ah] pass the CRC-8 check, as defined in [802.3ah]
65.1.3.3.3, and the frame meets the rule for acceptance 65.1.3.3.3, and the meet the rules for acceptance
defined in [802.3ah] 65.1.3.3.2. defined in [802.3ah] 65.1.3.3.2, for an ONU.
This counter is relevant for an OLT and an ONU. For the This object is applicable for an OLT and an ONU. At the
OLT there is a value per LLID. OLT it has a value for each virtual interface.
The value is zero for an OLT." At the OLT the value should be zero.
Discontinuities of this counter can occur at
re-initialization of the management system, and at other
times as indicated by the value of the
ifCounterDiscontinuityTime."
REFERENCE "[802.3ah], 30.3.7.1.6." REFERENCE "[802.3ah], 30.3.7.1.6."
::= { dot3OmpEmulationStatEntry 5} ::= { dot3OmpEmulationStatEntry 5}
dot3OmpEmulationOltPonCastLLID OBJECT-TYPE dot3OmpEmulationOltPonCastLLID OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
UNITS "frames" UNITS "frames"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of frames received that contain a valid SLD "A count of frames received that contain a valid SLD
field in an OLT, as defined in [802.3ah] 65.1.3.3.1, field, as defined in [802.3ah] 65.1.3.3.1,
passes the CRC-8 check, as defined in [802.3ah] pass the CRC-8 check, as defined in [802.3ah]
65.1.3.3.3, and the frame meets the rule for acceptance 65.1.3.3.3, and the meet the rules for acceptance
defined in [802.3ah] 65.1.3.3.2. defined in [802.3ah] 65.1.3.3.2, for an OLT.
This counter is relevant for an OLT and an ONU. For the This object is applicable for an OLT and an ONU. At the
OLT there is a value per LLID. OLT it has a value for each virtual interface.
The value is zero for an ONU." At the ONU the value should be zero.
Discontinuities of this counter can occur at
re-initialization of the management system, and at other
times as indicated by the value of the
ifCounterDiscontinuityTime."
REFERENCE "[802.3ah], 30.3.7.1.7." REFERENCE "[802.3ah], 30.3.7.1.7."
::= { dot3OmpEmulationStatEntry 6} ::= { dot3OmpEmulationStatEntry 6}
dot3OmpEmulationBroadcastBitNotOnuLlid OBJECT-TYPE dot3OmpEmulationBroadcastBitNotOnuLlid OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
UNITS "frames" UNITS "frames"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of frames received that contain a valid SLD "A count of frames received that contain a valid SLD
field in a OLT, as defined in [802.3ah] clause field, as defined in [802.3ah] clause
65.1.3.3.1, and pass the CRC-8 check, as defined in 65.1.3.3.1, and pass the CRC-8 check, as defined in
[802.3ah] clause 65.1.3.3.3, and contain broadcast bit [802.3ah] clause 65.1.3.3.3, and contain the broadcast
in LLID and not the ONU's LLID (frame accepted) as bit in the LLID and not the ONU's LLID (frame accepted)
defined in [802.3ah] clause 65. as defined in [802.3ah] clause 65.
This counter is relevant for an OLT and an ONU. For the This object is applicable for an OLT and an ONU. At the
OLT there is a value per LLID." OLT it has a value for each virtual interface.
At the OLT the value should be zero.
Discontinuities of this counter can occur at
re-initialization of the management system, and at other
times as indicated by the value of the
ifCounterDiscontinuityTime."
::= { dot3OmpEmulationStatEntry 7} ::= { dot3OmpEmulationStatEntry 7}
dot3OmpEmulationOnuLLIDNotBroadcast OBJECT-TYPE dot3OmpEmulationOnuLLIDNotBroadcast OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
UNITS "frames" UNITS "frames"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of frames received that contain a valid SLD "A count of frames received that contain a valid SLD
field in a OLT, as defined in [802.3ah] clause field, as defined in [802.3ah] clause
65.1.3.3.1, and pass the CRC-8 check, as defined in 65.1.3.3.1, and pass the CRC-8 check, as defined in
[802.3ah] clause 65.1.3.3.3, and contain the ONU's LLID [802.3ah] clause 65.1.3.3.3, and contain the ONU's LLID
as defined in [802.3ah] clause 65. This object is as defined in [802.3ah] clause 65.
This counter is relevant for an OLT and an ONU. For the This object is applicable for an OLT and an ONU. At the
OLT there is a value per LLID." OLT it has a value for each virtual interface.
At the OLT the value should be zero.
Discontinuities of this counter can occur at
re-initialization of the management system, and at other
times as indicated by the value of the
ifCounterDiscontinuityTime."
::= { dot3OmpEmulationStatEntry 8} ::= { dot3OmpEmulationStatEntry 8}
dot3OmpEmulationBroadcastBitPlusOnuLlid OBJECT-TYPE dot3OmpEmulationBroadcastBitPlusOnuLlid OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
UNITS "frames" UNITS "frames"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of frames received that contain a valid SLD "A count of frames received that contain a valid SLD
field in a OLT, as defined in [802.3ah] clause field, as defined in [802.3ah] clause
65.1.3.3.1, and pass the CRC-8 check, as defined in 65.1.3.3.1, and pass the CRC-8 check, as defined in
[802.3ah] clause 65.1.3.3.3, and contain the broadcast [802.3ah] clause 65.1.3.3.3, and contain the broadcast
bit in LLID and the ONU's LLID (frame reflected) as bit in the LLID and match the ONU's LLID (frame
defined in [802.3ah] clause 65. reflected) as defined in [802.3ah] clause 65.
This counter is relevant for an OLT and an ONU. For the This object is applicable for an OLT and an ONU. At the
OLT there is a value per LLID." OLT it has a value for each virtual interface.
At the OLT the value should be zero.
Discontinuities of this counter can occur at
re-initialization of the management system, and at other
times as indicated by the value of the
ifCounterDiscontinuityTime."
::= { dot3OmpEmulationStatEntry 9} ::= { dot3OmpEmulationStatEntry 9}
dot3OmpEmulationNotBroadcastBitNotOnuLlid OBJECT-TYPE dot3OmpEmulationNotBroadcastBitNotOnuLlid OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
UNITS "frames" UNITS "frames"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of frames received that contain a valid SLD "A count of frames received that contain a valid SLD
field in a OLT, as defined in [802.3ah] clause field, as defined in [802.3ah] clause
65.1.3.3.1, and pass the CRC-8 check, as defined in 65.1.3.3.1, and pass the CRC-8 check, as defined in
[802.3ah] clause 65.1.3.3.3, and does not contain [802.3ah] clause 65.1.3.3.3, and does not contain
the ONU's LLID as defined in [802.3ah] clause 65. the ONU's LLID as defined in [802.3ah] clause 65.
This object is mandatory for an ONU" This object is applicable for an OLT and an ONU. At the
OLT it has a value for each virtual interface.
At the OLT the value should be zero.
Discontinuities of this counter can occur at
re-initialization of the management system, and at other
times as indicated by the value of the
ifCounterDiscontinuityTime."
::= { dot3OmpEmulationStatEntry 10} ::= { dot3OmpEmulationStatEntry 10}
-- FEC managed object definitions (30.5.1) -- FEC managed object definitions (30.5.1)
dot3EponFecObjects OBJECT IDENTIFIER ::={dot3EponObjects 3} dot3EponFecObjects OBJECT IDENTIFIER ::={dot3EponObjects 3}
dot3EponFecTable OBJECT-TYPE dot3EponFecTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot3EponFecEntry SYNTAX SEQUENCE OF Dot3EponFecEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Table for dot3 EPON FEC management objects. "Table of dot3 EPON FEC management objects.
The entries in the table are control and status entities
The entries in the table are control and status objects
and statistic counters for the FEC layer. and statistic counters for the FEC layer.
Each object has a row for every virtual link Each object has a row for every virtual link denoted by
according to the proper ifIndex. Typically the number the corresponding ifIndex.
of expected virtual link in a PON is like the number of Typically the number of expected virtual links in a PON
ONUs 32-64 plus an additional entry for broadcast LLID is like the number of ONUs, which is 32-64, plus an
(which is marked by 0xffff). In the [802.3ah] the LLID additional entry for broadcast LLID (with a value of
is a 2bytes register and the number of LLIDs limited by 0xffff).
that." In the [802.3ah] the LLID is a 2bytes register and the
number of LLIDs is limited by that."
::= { dot3EponFecObjects 1 } ::= { dot3EponFecObjects 1 }
dot3EponFecEntry OBJECT-TYPE dot3EponFecEntry OBJECT-TYPE
SYNTAX Dot3EponFecEntry SYNTAX Dot3EponFecEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the dot3 EPON FEC table. The Rows in the "An entry in the dot3 EPON FEC table.
table are created when ifIndexs are created. Rows exist for an OLT interface and an ONU interface.
Rows in the table are denoted by the ifIndexes and they
are created when the ifIndexes are created.
For the ONU rows are created at system initialization. For the ONU rows are created at system initialization.
For the OLT the rows of the OLT ifIndex and the row of For the OLT the row of the OLT ifIndex and the row of
the ifIndex referring to the broadcast virtual link are the ifIndex referring to the broadcast virtual link are
created at system initialization. For the ifIndexs created at system initialization. For the ifIndexes
referring to the virtual links at the OLT, a row is referring to the virtual links at the OLT, a row is
created when a virtual link is established (ONU created when a virtual link is established (ONU
registers) and deleted when the virtual link is deleted registers) and deleted when the virtual link is deleted
(ONU deregisters). Rows exist for an OLT interface and (ONU deregisters)."
an ONU interface."
INDEX { ifIndex} INDEX { ifIndex}
::= { dot3EponFecTable 1 } ::= { dot3EponFecTable 1 }
Dot3EponFecEntry ::= Dot3EponFecEntry ::=
SEQUENCE { SEQUENCE {
dot3EponFecPCSCodingViolation Counter64, dot3EponFecPCSCodingViolation Counter64,
dot3EponFecAbility INTEGER, dot3EponFecAbility INTEGER,
dot3EponFecMode INTEGER, dot3EponFecMode INTEGER,
dot3EponFecCorrectedBlocks Counter64, dot3EponFecCorrectedBlocks Counter64,
dot3EponFecUncorrectableBlocks Counter64, dot3EponFecUncorrectableBlocks Counter64,
dot3EponFecBufferHeadCodingViolation Counter64 dot3EponFecBufferHeadCodingViolation Counter64
} }
skipping to change at page 49, line 20 skipping to change at page 61, line 4
dot3EponFecUncorrectableBlocks Counter64, dot3EponFecUncorrectableBlocks Counter64,
dot3EponFecBufferHeadCodingViolation Counter64 dot3EponFecBufferHeadCodingViolation Counter64
} }
dot3EponFecPCSCodingViolation OBJECT-TYPE dot3EponFecPCSCodingViolation OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
UNITS "octets" UNITS "octets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"For 100 Mb/ s operation it is a count of the number of "For 100 Mbps operation it is a count of the number of
times an invalid code-group is received, other than the times an invalid code-group is received, other than the
/H/ code-group. For 1000 Mb/ s operation it is a count /H/ code-group. For 1000 Mbps operation it is a count
of the number of times an invalid codegroup is received, of the number of times an invalid codegroup is received,
other than the /V/ code-group. /H/ and /V/ denote other than the /V/ code-group. /H/ denotes a special
special 8b10b codewords of the [802.3] PCS layer (clause 4b5b codeword of [802.3] 100 Mbps PCS layer (clause 24),
36)." and /V/ denotes a special 8b10b codeword of the [802.3]
1000 Mbps PCS layer (clause 36).
This object is applicable for an OLT and an ONU. At the
OLT it has a value for each virtual interface.
Discontinuities of this counter can occur at
re-initialization of the management system, and at other
times as indicated by the value of the
ifCounterDiscontinuityTime."
REFERENCE "[802.3ah], 30.5.1.1.12." REFERENCE "[802.3ah], 30.5.1.1.12."
::= { dot3EponFecEntry 1} ::= { dot3EponFecEntry 1}
dot3EponFecAbility OBJECT-TYPE dot3EponFecAbility OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
unknown (1), unknown (1),
unsupported (2), unsupported (2),
supported (3) supported (3)
} }
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A value that indicates the support of "An object that indicates the support of operation of the
operation of the 1000BASE-PX PHY optional FEC Sublayer optional FEC sublayer of the 1000BASE-PX PHY, specified
for Forward error correction see [802.3ah] clause in [802.3ah] clause 65.2.
65.2). unknown(1) value is assigned in initialization, for non
unknown(1) value is assigned in initializing, for non
FEC support state or type not yet known. unsupported(2) FEC support state or type not yet known. unsupported(2)
value is assigned when Sublayer is not support. value is assigned when sublayer is not supported.
supported(3) value is assigned when Sublayer is supported(3) value is assigned when sublayer is
supported." supported.
This object is applicable for an OLT, with the same
value for all virtual interfaces, and for an ONU.
When the interface is not supporting FEC the FEC
counters will have a zero value.
The counters:
dot3EponFecPCSCodingViolation - not affected by FEC
ability.
dot3EponFecCorrectedBlocks - has a zero value when
dot3EponFecAbility is unknown (1) and unsupported (2).
dot3EponFecUncorrectableBlocks - has a zero value when
dot3EponFecAbility is unknown (1) and unsupported (2).
dot3EponFecBufferHeadCodingViolation - has a zero value
when dot3EponFecAbility is unknown (1) and
unsupported (2). "
REFERENCE "[802.3ah], 30.5.1.1.13." REFERENCE "[802.3ah], 30.5.1.1.13."
::= { dot3EponFecEntry 2} ::= { dot3EponFecEntry 2}
dot3EponFecMode OBJECT-TYPE dot3EponFecMode OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
unknown (1), unknown (1),
disabled (2), disabled (2),
enabled (3) enabled (3)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A read-write value that indicates the mode of operation "An object that defines and indicates the mode of
of the 1000BASE-PX PHY optional FEC Sublayer for Forward operation of the optional FEC sublayer of the
error correction see [802.3ah] clause 65.2). 1000BASE-PX PHY, specified in [802.3ah] clause 65.2.
A GET operation returns the current mode of operation A GET operation returns the current mode of operation
the PHY. A SET operation changes the mode of operation of the PHY. A SET operation changes the mode of
of the PHY to the indicated value. unknown(1) value is operation of the PHY to the indicated value.
assigned in initializing, for non FEC support state or unknown(1) value is assigned in initialization, for non
type not yet known. disabled(2) value is assigned when FEC support state or type not yet known.
Sublayer operating in disabled mode. enabled(3) value is disabled(2) value is assigned when the FEC sublayer is
assigned when Sublayer operating in FEC mode. writing operating in disabled mode.
can be done at any time." enabled(3) value is assigned when the FEC sublayer is
operating in FEC mode.
writing can be done at any time.
This object is applicable for an OLT and an ONU. At the
OLT it has a value for each virtual interface.
When the interface is not enabling FEC the counting of
the FEC counters will stop. Generally the FEC counters
are referring to the receive path and affected by
fecRxEnabled and fecTxRxEnabled.
The counters:
dot3EponFecPCSCodingViolation - not affected by FEC
mode.
dot3EponFecCorrectedBlocks - stops counting when
Rx_FEC is not enabled. (unknown (1) and disabled (2)).
dot3EponFecUncorrectableBlocks - stops counting when
Rx_FEC is not enabled (unknown (1) and disabled (2)).
dot3EponFecBufferHeadCodingViolation - stops counting
when Rx_FEC is not enabled (unknown (1) and
disabled (2)).
The object:
dot3EponFecAbility - indicates the FEC ability and is
not affected by the FEC mode."
REFERENCE "[802.3ah], 30.5.1.1.14." REFERENCE "[802.3ah], 30.5.1.1.14."
DEFVAL { 1 } DEFVAL { 1 }
::= { dot3EponFecEntry 3} ::= { dot3EponFecEntry 3}
dot3EponFecCorrectedBlocks OBJECT-TYPE dot3EponFecCorrectedBlocks OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"For 10PASS-TS, 2BASE-TL and 1000BASE-PX PHYs, a count "For 10PASS-TS, 2BASE-TL and 1000BASE-PX PHYs it is a
of corrected FEC blocks. This counter will not increment count of corrected FEC blocks. This counter will not
for other PHY Types. Increment the counter by one for increment for other PHY Types. Increment the counter by
each received block that is corrected by the FEC one for each received block that is corrected by the FEC
function in the PHY." function in the PHY.
This object is applicable for an OLT and an ONU. At the
OLT it has a value for each virtual interface.
Discontinuities of this counter can occur at
re-initialization of the management system, and at other
times as indicated by the value of the
ifCounterDiscontinuityTime."
REFERENCE "[802.3ah], 30.5.1.1.15." REFERENCE "[802.3ah], 30.5.1.1.15."
::= { dot3EponFecEntry 4} ::= { dot3EponFecEntry 4}
dot3EponFecUncorrectableBlocks OBJECT-TYPE dot3EponFecUncorrectableBlocks OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"For 10PASS-TS, 2BASE-TL and 1000BASE-PX PHYs, a count of "For 10PASS-TS, 2BASE-TL and 1000BASE-PX PHYs it is a
uncorrectable FEC blocks. This counter will not count of uncorrectable FEC blocks. This counter will not
increment for other PHY Types. Increment the counter by increment for other PHY Types. Increment the counter by
one for each FEC block that is determined to be one for each FEC block that is determined to be
uncorrectable by the FEC function in the PHY." uncorrectable by the FEC function in the PHY.
This object is applicable for an OLT and an ONU. At the
OLT it has a value for each virtual interface.
Discontinuities of this counter can occur at
re-initialization of the management system, and at other
times as indicated by the value of the
ifCounterDiscontinuityTime."
REFERENCE "[802.3ah], 30.5.1.1.16." REFERENCE "[802.3ah], 30.5.1.1.16."
::= { dot3EponFecEntry 5} ::= { dot3EponFecEntry 5}
dot3EponFecBufferHeadCodingViolation OBJECT-TYPE dot3EponFecBufferHeadCodingViolation OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
UNITS "octets" UNITS "octets"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"For 1000 Mbps operation it is a counts of the number of "For 1000 Mbps operation it is a count of the number of
invalid code-group received directly from the link." invalid code-group received directly from the link. The
value has a meaning only in 1000 Mbps mode and it is
zero otherwise.
This object is applicable for an OLT and an ONU. At the
OLT it has a value for each virtual interface.
Discontinuities of this counter can occur at
re-initialization of the management system, and at other
times as indicated by the value of the
ifCounterDiscontinuityTime."
::= { dot3EponFecEntry 6} ::= { dot3EponFecEntry 6}
-- ExtendedPackage managed object definitions -- ExtendedPackage managed object definitions
dot3ExtPkgObjects OBJECT IDENTIFIER ::={dot3EponObjects 4} dot3ExtPkgObjects OBJECT IDENTIFIER ::={dot3EponObjects 4}
dot3ExtPkgControlObjects OBJECT IDENTIFIER ::= { dot3ExtPkgObjects 1} dot3ExtPkgControlObjects OBJECT IDENTIFIER ::= { dot3ExtPkgObjects 1}
dot3ExtPkgControlTable OBJECT-TYPE dot3ExtPkgControlTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot3ExtPkgControlEntry SYNTAX SEQUENCE OF Dot3ExtPkgControlEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table for Extended package Control management "A table of Extended package Control management
objects. Entries are control and status indication objects. Entries in the table are control and status
objects for an EPON interface which are gathered in an indication objects of an EPON interface which are
extended package as an addition for the [802.3ah] gathered in an extended package as an addition to the
attributes. objects based on the [802.3ah] clause 30 attributes.
Each object has a row for every virtual link Each object has a row for every virtual link denoted by
according to the proper ifIndex. Typically the number the corresponding ifIndex.
of expected virtual link in a PON is like the number of Typically the number of expected virtual links in a PON
ONUs 32-64 plus an additional entry for broadcast LLID is like the number of ONUs, which is 32-64, plus an
(which is marked by 0xffff). In the [802.3ah] the LLID additional entry for broadcast LLID (with a value of
is a 2bytes register and the number of LLIDs limited by 0xffff).
that." In the [802.3ah] the LLID is a 2bytes register and the
number of LLIDs is limited by that."
::= { dot3ExtPkgControlObjects 1 } ::= { dot3ExtPkgControlObjects 1 }
dot3ExtPkgControlEntry OBJECT-TYPE dot3ExtPkgControlEntry OBJECT-TYPE
SYNTAX Dot3ExtPkgControlEntry SYNTAX Dot3ExtPkgControlEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the Extended package Control table. "An entry in the Extended package Control table.
Rows in the table are created when ifIndexs are created. Rows exist for an OLT interface and an ONU interface.
Rows in the table are denoted by the ifIndexes and they
are created when the ifIndexes are created.
For the ONU rows are created at system initialization. For the ONU rows are created at system initialization.
For the OLT the rows of the OLT ifIndex and the row of
For the OLT the row of the OLT ifIndex and the row of
the ifIndex referring to the broadcast virtual link are the ifIndex referring to the broadcast virtual link are
created at system initialization. For the ifIndexs created at system initialization. For the ifIndexes
referring to the virtual links at the OLT, a row is referring to the virtual links at the OLT, a row is
created when a virtual link is established (ONU created when a virtual link is established (ONU
registers) and deleted when the virtual link is deleted registers) and deleted when the virtual link is deleted
(ONU deregisters). Rows exist for an OLT interface and (ONU deregisters)."
an ONU interface."
INDEX { ifIndex} INDEX { ifIndex}
::= { dot3ExtPkgControlTable 1 } ::= { dot3ExtPkgControlTable 1 }
Dot3ExtPkgControlEntry ::= Dot3ExtPkgControlEntry ::=
SEQUENCE { SEQUENCE {
dot3ExtPkgObjectReset INTEGER, dot3ExtPkgObjectReset INTEGER,
dot3ExtPkgObjectPowerDown TruthValue, dot3ExtPkgObjectPowerDown TruthValue,
dot3ExtPkgObjectNumberOfLLIDs Unsigned32, dot3ExtPkgObjectNumberOfLLIDs Unsigned32,
dot3ExtPkgObjectFecEnabled INTEGER, dot3ExtPkgObjectFecEnabled INTEGER,
dot3ExtPkgObjectReportMaximumNumQueues Unsigned32, dot3ExtPkgObjectReportMaximumNumQueues Unsigned32,
skipping to change at page 52, line 32 skipping to change at page 65, line 33
} }
dot3ExtPkgObjectReset OBJECT-TYPE dot3ExtPkgObjectReset OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
running(1), running(1),
reset(2) reset(2)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable is used to reset the EPON interface. The "This object is used to reset the EPON interface. The
interface may be unavailable while the reset occurs and interface may be unavailable while the reset occurs and
data may be lost. During reading operation it returns data may be lost.
the state of the EPON interface. running(1) indicates Setting this object to running(1) will cause the
and operates normal operation, reset(2) indicates and interface to enter into running mode. Setting this
operates reset mode. Writing can be done at any time. object to reset(2) will cause the interface to go into
This object is relevant for an OLT, same for all reset mode. When getting running(1) the interface is in
virtual links, and for an ONU." running mode. When getting reset(2) the interface is in
reset mode.
Writing can be done at any time.
This object is applicable for an OLT and an ONU. At the
OLT it has a value for each virtual interface.
A reset for a virtual interface resets only the virtual
interface and not the physical interface. Thus, a
virtual link which is mal-functioning can be reset
without affecting the operation of other virtual
interfaces.
The reset can cause Discontinuities in the values of the
counters of the interface, similar to re-initialization
of the management system. Discontinuity should be
indicated by the ifCounterDiscontinuityTime object. "
DEFVAL { 1 } DEFVAL { 1 }
::= { dot3ExtPkgControlEntry 1 } ::= { dot3ExtPkgControlEntry 1 }
dot3ExtPkgObjectPowerDown OBJECT-TYPE dot3ExtPkgObjectPowerDown OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Setting this variable to true(1) will cause the "This object is used to power down the EPON interface.
interface to be entered into Power down mode. Setting The interface may be unavailable while the power down
this variable to false(2) will cause the interface to go occurs and data may be lost.
out of power down mode. When getting true(1) the Setting this object to true(1) will cause the interface
interface is in power down. When getting false(2) the to enter into power down mode. Setting this object to
interface is not in power down. false(2) will cause the interface to go out of power
down mode. When getting true(1) the interface is in
power down mode. When getting false(2) the interface is
not in power down mode.
Writing can be done at any time. Writing can be done at any time.
The variable is relevant when the admin state of the This object is applicable for an OLT and an ONU. At the
device is active as set by the dot3MpcpAdminState. OLT it has a value for each virtual interface.
This object is relevant for an OLT, same for all A power down/up of a virtual interface affects only the
virtual links, and for an ONU." virtual interface and not the physical interface. Hence
a virtual link which needs a certain handling can be
powered down and then powered up without disrupting the
operation of other virtual interfaces.
The object is relevant when the admin state of the
device is active as set by the dot3MpcpAdminState."
DEFVAL { false } DEFVAL { false }
::= { dot3ExtPkgControlEntry 2 } ::= { dot3ExtPkgControlEntry 2 }
dot3ExtPkgObjectNumberOfLLIDs OBJECT-TYPE dot3ExtPkgObjectNumberOfLLIDs OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A read only variable which defines the number of "A read only object which indicates the number of
registered LLIDs (as defined by the [802.3ah] clause 65) registered LLIDs. Initialization value is 0.
in a EPON network for an OLT and an ONU. Initialization This object is applicable for an OLT, with the same
value is 0. value for all virtual interfaces, and for an ONU.
This object is relevant for an OLT and an ONU. Typically the number of expected virtual links in a PON
Typically the number of expected virtual link in a PON is like the number of ONUs, which is 32-64, plus an
is like the number of ONUs 32-64 plus an additional additional entry for broadcast LLID (with a value of
entry for broadcast LLID (which is marked by 0xffff). In 0xffff).
the [802.3ah] the LLID is a 2bytes register and the In the [802.3ah] the LLID is a 2bytes register and the
number of LLIDs is limited by that. At the ONU the number of LLIDs is limited by that. At the ONU the
number of LLIDs for an interface is one. number of LLIDs for an interface is one."
This object is relevant for an OLT, same for all
virtual links, and for an ONU."
::= { dot3ExtPkgControlEntry 3 } ::= { dot3ExtPkgControlEntry 3 }
dot3ExtPkgObjectFecEnabled OBJECT-TYPE dot3ExtPkgObjectFecEnabled OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
noFecEnabled (1), noFecEnabled (1),
fecTxEnabled (2), fecTxEnabled (2),
fecRxEnabled (3), fecRxEnabled (3),
fecTxRxEnabled (4) fecTxRxEnabled (4)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This variable defines and provides information whether the "This object defines a list of actions for the
EPON interface uses FEC as defined in the [802.3ah] clause FEC state of an interface, and indicates the FEC state of
65.2 for EPON. When noFECEnabled(1) the interface does not the interface.
support FEC mode. When fecTxEnabled(2) the interface When noFECEnabled(1) the interface does not enable FEC
supports the FEC transmission mode. When fecRxEnabled(3) mode.
the interface supports the FEC Receive mode. When When fecTxEnabled(2) the interface enables the FEC
fecTxRxEnabled(4) the interface supports the FEC transmit mode.
transmission and receive mode. When fecRxEnabled(3) the interface enables the FEC
Writing can be done at any time. receive mode.
This object is relevant for an OLT and an ONU. For the When fecTxRxEnabled(4) the interface enables the FEC
OLT there is a value per LLID." transmit and receive mode.
This object is applicable for an OLT and an ONU. At the
OLT it has a value for each virtual interface.
When the interface is not enabling FEC the counting of
the FEC counters will stop. Generally the FEC counters are
referring to the receive path and affected by fecRxEnabled
and fecTxRxEnabled.
The counters:
dot3EponFecPCSCodingViolation - not affected by FEC mode.
dot3EponFecCorrectedBlocks - stops counting when
Rx_FEC is not enabled. (noFecEnabled (1) and
fecTxEnabled (2)).
dot3EponFecUncorrectableBlocks - stops counting when
Rx_FEC is not enabled (noFecEnabled (1) and
fecTxEnabled (2)).
dot3EponFecBufferHeadCodingViolation - stops counting
when Rx_FEC is not enabled (noFecEnabled (1) and
fecTxEnabled (2)).
The objects:
dot3EponFecAbility - indicates the FEC ability and is not
affected by the FEC mode.
dot3EponFecMode - indicates the FEC mode for combined RX
and TX.
Writing can be done at any time."
DEFVAL { 1 } DEFVAL { 1 }
::= { dot3ExtPkgControlEntry 4 } ::= { dot3ExtPkgControlEntry 4 }
dot3ExtPkgObjectReportMaximumNumQueues OBJECT-TYPE dot3ExtPkgObjectReportMaximumNumQueues OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32 (0..7)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An integer for each LLID, that defines the "An object, that defines the maximal number of queues in
maximal number of queues in the REPORT message, as the REPORT message, as defined in [802.3ah] 64. For
defined in [802.3ah] 64. further information please see the description of the
This object is relevant for an OLT and an ONU. For the queue table.
OLT there is a value per LLID." This object is applicable for an OLT and an ONU. At the
OLT it has a value for each virtual interface."
DEFVAL { 0 } DEFVAL { 0 }
::= { dot3ExtPkgControlEntry 5 } ::= { dot3ExtPkgControlEntry 5 }
dot3ExtPkgObjectRegisterAction OBJECT-TYPE dot3ExtPkgObjectRegisterAction OBJECT-TYPE
SYNTAX INTEGER { SYNTAX INTEGER {
none (1), none (1),
register (2), register (2),
deregister (3), deregister (3),
reregister (4) reregister (4)
} }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A list of actions for an entry - LLID. Indicates and "An object which defines a list of actions for the
defines the state of registration for the remote registration state of an interface, and indicates the
interface. registration state of the interface.
none(1) marks no action, register(2) marks to register When writing the state is changed to the new value.
an LLID, deregister(3) marks to deregister an LLID, When reading the state value is returned.
reregister(4) marks reregistered LLID. none(1) indicates an unknown state,
This object is relevant for an OLT and an ONU. For the register(2) indicates a registered LLID,
OLT there is a value per LLID." deregister(3) indicates a deregistered LLID,
reregister(4) indicates an LLID which is reregistering.
When writing the object changes the LLID state as
specified in [802.3ah] clause 64. The actions that can
be done for an LLID as described in the [802.3] are
none (1) - not doing any action.
register (2) - registering an LLID which request to
register (in registering mode
(dot3MpcpRegistrationState - registering (2)).
deregister (3) - deregisters an LLID which is registered
(dot3MpcpRegistrationState - registered (3) ).
reregister (4) - reregister an LLID which is registered
(dot3MpcpRegistrationState - registered (3) ).
The behavior of an ONU and OLT interfaces, at each one
of the states is described in the registration state
machine in figure 64-22 of [802.3ah].
The indication of the registration state is reflected in
this object and in the dot3MpcpRegistrationState object.
This object is applicable for an OLT and an ONU. At the
OLT it has a value for each virtual interface."
DEFVAL { 1 } DEFVAL { 1 }
::= { dot3ExtPkgControlEntry 6 } ::= { dot3ExtPkgControlEntry 6 }
dot3ExtPkgQueueTable OBJECT-TYPE dot3ExtPkgQueueTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot3ExtPkgQueueEntry SYNTAX SEQUENCE OF Dot3ExtPkgQueueEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table for extended package Queue management objects. "A table of the extended package objects for queue
The [802.3ah] MPCP uses for the feedback BW request from management. The [802.3ah] MPCP defines a report of the
the ONUs a report of some queues occupancy. These queues occupancy of the transmit queues for the feedback BW
serve the ONU transmission and data is gathered there request from the ONUs. These queues serve the uplink
until the ONU is granted for transmission. Since the transmission of the ONU and data is gathered there until
existence of such queuing mechanism is implied in the the ONU is granted for transmission.
[802.3ah] spec and an ONU may not be a switch device, The management table of the queues is added here mainly
a management section is added here for the queues, to gather some statistics of their operation. This table
mainly to gather some statistics of their operation. is not duplicating existing management objects of
Entries are control and status indication bridging queues, specified in [802.1d], since the ONU
objects for an EPON interface which are gathered in an may not be a bridge device, with embedded bridging
extended package as an addition for the [802.3ah] queues and the existence of the transmit queuing
attributes. The objects in this table are specific for mechanism is implied in the [802.3ah] spec.
the queues which are reported in the MPCP REPORT message The format of the REPORT message, as specified
as defined in [802.3ah] clause 64. in [802.3], is presented below:
+-----------------------------------+
| Destination Address |
+-----------------------------------+
| Source Address |
+-----------------------------------+
| Length/Type |
+-----------------------------------+
| OpCode |
+-----------------------------------+
| TimeStamp |
+-----------------------------------+
| Number of queue Sets |
+-----------------------------------+ /|\
| Report bitmap | |
+-----------------------------------+ |
| Queue 0 report | |
+-----------------------------------+ | repeated for
| Queue 1 report | | every
+-----------------------------------+ | queue_set
| Queue 2 report | |
+-----------------------------------+ |
| Queue 3 report | |
+-----------------------------------+ |
| Queue 4 report | |
+-----------------------------------+ |
| Queue 5 report | |
+-----------------------------------+ |
| Queue 6 report | |
+-----------------------------------+ |
| Queue 7 report | |
+-----------------------------------+ \|/
| Pad/reserved |
+-----------------------------------+
| FCS |
+-----------------------------------+
The 'Queue report' field reports the occupancy of each
uplink transmission queue.
The number of queue sets defines the number of the
reported sets, as would be explained in the description
of the dot3ExtPkgQueueSetsTable table. For each set the
report bitmap defines which queue is present in the
report, meaning that although the MPCP REPORT message
can report of up to 8 queues in a REPORT message, the
actual number is flexible. The Queue table has a
variable size which is limited by the
dot3ExtPkgObjectReportMaximumNumQueues object as an
ONU can have fewer queues to report.
The entries in the table are control and status
indication objects for managing the queues of an EPON
interface which are gathered in an extended package as
an addition to the objects which are based on the
[802.3ah] attributes.
Each object has a row for every virtual link and for Each object has a row for every virtual link and for
every queue in the report. Typically the number of every queue in the report.
expected virtual link in a PON is like the number of Typically the number of expected virtual links in a PON
ONUs 32-64 plus an additional entry for broadcast LLID is like the number of ONUs, which is 32-64, plus an
(which is marked by 0xffff). In the [802.3ah] the LLID additional entry for broadcast LLID (with a value of
is a 2bytes register and the number of LLIDs limited by 0xffff).
that. In the [802.3ah] the LLID is a 2bytes register and the
number of LLIDs is limited by that.
The number of queues is between 0 and 7 and limited by The number of queues is between 0 and 7 and limited by
dot3ExtPkgObjectReportMaximumNumQueues." dot3ExtPkgObjectReportMaximumNumQueues."
::= { dot3ExtPkgControlObjects 2 } ::= { dot3ExtPkgControlObjects 2 }
dot3ExtPkgQueueEntry OBJECT-TYPE dot3ExtPkgQueueEntry OBJECT-TYPE
SYNTAX Dot3ExtPkgQueueEntry SYNTAX Dot3ExtPkgQueueEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the Extended package Queue table. The rows "An entry in the Extended package Queue table. At the
are added for each ifIndex and dot3QueueIndex at the OLT, the rows exist for each ifIndex and dot3QueueIndex.
OLT. At the ONU the rows are added for each At the ONU, rows exist for the single ifIndex for each
dot3QueueIndex and a single row of ifIndex. dot3QueueIndex.
Rows in the table are created when ifIndexs are created. Rows in the table are created when the ifIndexes are
created. A set of rows per queue is added for each
ifIndex, denoted with the dot3QueueIndex.
For the ONU rows are created at system initialization. For the ONU rows are created at system initialization.
For the OLT the rows of the OLT ifIndex and the row of For the OLT the rows of the OLT ifIndex and the rows of
the ifIndex referring to the broadcast virtual link are the ifIndex referring to the broadcast virtual link are
created at system initialization. For the ifIndexs created at system initialization. For the ifIndexes
referring to the virtual links at the OLT, a row is referring to the virtual links at the OLT, a set of rows
created when a virtual link is established (ONU per queue are created when a virtual link is established
registers) and deleted when the virtual link is deleted (ONU registers) and deleted when the virtual link is
(ONU deregisters). Rows exist for an OLT interface and deleted (ONU deregisters)."
an ONU interface."
INDEX { ifIndex, dot3QueueIndex } INDEX { ifIndex, dot3QueueIndex }
::= { dot3ExtPkgQueueTable 1 } ::= { dot3ExtPkgQueueTable 1 }
Dot3ExtPkgQueueEntry ::= Dot3ExtPkgQueueEntry ::=
SEQUENCE { SEQUENCE {
dot3QueueIndex Unsigned32, dot3QueueIndex Unsigned32,
dot3ExtPkgObjectReportNumThreshold Unsigned32, dot3ExtPkgObjectReportNumThreshold Unsigned32,
dot3ExtPkgObjectReportMaximumNumThreshold Unsigned32, dot3ExtPkgObjectReportMaximumNumThreshold Unsigned32,
dot3ExtPkgStatTxFramesQueue Counter64, dot3ExtPkgStatTxFramesQueue Counter64,
dot3ExtPkgStatRxFramesQueue Counter64, dot3ExtPkgStatRxFramesQueue Counter64,
dot3ExtPkgStatDroppedFramesQueue Counter64 dot3ExtPkgStatDroppedFramesQueue Counter64
} }
dot3QueueIndex OBJECT-TYPE dot3QueueIndex OBJECT-TYPE
SYNTAX Unsigned32 (0..7) SYNTAX Unsigned32 (0..7)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A value that identifies the queue index for the queue "An object that identifies an index for the queue table
table. The queues are reported in the MPCP REPORT reflecting the queue index of the queues which are
message as defined in [802.3ah] clause 64. reported in the MPCP REPORT message, as defined in
[802.3ah] clause 64.
The number of queues is between 0 and 7 and limited by The number of queues is between 0 and 7 and limited by
dot3ExtPkgObjectReportMaximumNumQueues." dot3ExtPkgObjectReportMaximumNumQueues."
::= { dot3ExtPkgQueueEntry 1 } ::= { dot3ExtPkgQueueEntry 1 }
dot3ExtPkgObjectReportNumThreshold OBJECT-TYPE dot3ExtPkgObjectReportNumThreshold OBJECT-TYPE
SYNTAX Unsigned32 (0..7) SYNTAX Unsigned32 (0..7)
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An integers for each LLID, that defines the "An object that defines the number of thresholds for each
number of thresholds for each Queue in the REPORT queue in the REPORT message, as defined in [802.3ah] 64.
message, as defined in [802.3ah] 64. Each Queue set Each queue_set reporting will provide information on the
reporting will provide information on the queue queue occupancy of frames below the matching Threshold.
occupancy of frames below the matching Threshold. When reading, the value reflects the number of
Writing can be done at any time. thresholds.
This object is relevant for an OLT and an ONU. For the When writing, the number of thresholds for each queue is
OLT there is a value per LLID." set.
Writing can be done at any time. Value can not exceed
the maximal value defined by the
dot3ExtPkgObjectReportMaximumNumThreshold object.
This object is applicable for an OLT and an ONU. At the
OLT it has a value for each virtual interface and for
each queue. At the ONU it has a value for each queue."
DEFVAL { 0 } DEFVAL { 0 }
::= { dot3ExtPkgQueueEntry 2 } ::= { dot3ExtPkgQueueEntry 2 }
dot3ExtPkgObjectReportMaximumNumThreshold OBJECT-TYPE dot3ExtPkgObjectReportMaximumNumThreshold OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32 (0..7)
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An integer for each LLID, that defines the "An object, that defines the maximal number of thresholds
maximal number of thresholds for each Queue in the for each queue in the REPORT message, as defined in
REPORT message, as defined in [802.3ah] 64. Each Queue [802.3ah] 64. Each queue_set reporting will provide
set reporting will provide information on the queue information on the queue occupancy of frames below the
occupancy of frames below the matching Threshold. matching Threshold.
This object is relevant for an OLT and an ONU. For the This object is applicable for an OLT and an ONU. At the
OLT there is a value per LLID." OLT it has a value for each virtual interface and for
each queue. At the ONU it has a value for each queue."
DEFVAL { 0 } DEFVAL { 0 }
::= { dot3ExtPkgQueueEntry 3 } ::= { dot3ExtPkgQueueEntry 3 }
dot3ExtPkgStatTxFramesQueue OBJECT-TYPE dot3ExtPkgStatTxFramesQueue OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
UNITS "frames" UNITS "frames"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of the number of times a relevant 'Queue' frames "A count of the number of times a frame transmission
transmission occurs. Increment the counter by one for occurs from the corresponding 'Queue'.
each frame transmitted which is an output of the Increment the counter by one for each frame transmitted
'Queue'. which is an output of the 'Queue'.
The 'Queue' marking matched the REPORT MPCP message The 'Queue' marking matches the REPORT MPCP message
Queue field, as defined in [802.3ah] clause 64. This Queue field, as defined in [802.3ah] clause 64.
counter is mandatory for an ONU only." This object is applicable for an OLT and an ONU. At the
OLT it has a value for each virtual interface and for
each queue. At the ONU it has a value for each queue.
At the OLT the value should be zero.
Discontinuities of this counter can occur at
re-initialization of the management system, and at other
times as indicated by the value of the
ifCounterDiscontinuityTime."
::= { dot3ExtPkgQueueEntry 4} ::= { dot3ExtPkgQueueEntry 4}
dot3ExtPkgStatRxFramesQueue OBJECT-TYPE dot3ExtPkgStatRxFramesQueue OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
UNITS "frames" UNITS "frames"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of the number of times a relevant 'Queue' frames "A count of the number of times a frame reception
reception occurs. Increment the counter by one for each occurs from the corresponding 'Queue'.
frame received, which is an output of 'Queue'. The Increment the counter by one for each frame received
'Queue' marking matched the REPORT MPCP message which is an output of the corresponding 'Queue'.
The 'Queue' marking matches the REPORT MPCP message
Queue field, as defined in [802.3ah] clause 64. Queue field, as defined in [802.3ah] clause 64.
This counter is mandatory for an ONU only." This object is applicable for an OLT and an ONU. At the
OLT it has a value for each virtual interface and for
each queue. At the ONU it has a value for each queue.
Discontinuities of this counter can occur at
re-initialization of the management system, and at other
times as indicated by the value of the
ifCounterDiscontinuityTime."
::= { dot3ExtPkgQueueEntry 5} ::= { dot3ExtPkgQueueEntry 5}
dot3ExtPkgStatDroppedFramesQueue OBJECT-TYPE dot3ExtPkgStatDroppedFramesQueue OBJECT-TYPE
SYNTAX Counter64 SYNTAX Counter64
UNITS "frames" UNITS "frames"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A count of the number of times a relevant 'Queue' frames "A count of the number of times a frame drop
drops occurs. Increment the counter by one for each occurs from the corresponding 'Queue'.
frame dropped from 'Queue'. The 'Queue' marking matched Increment the counter by one for each frame dropped
the REPORT MPCP message Queue field, as defined in from the corresponding 'Queue'.
[802.3ah] clause 64. The 'Queue' marking matches the REPORT MPCP message
This counter is mandatory for an ONU only." Queue field, as defined in [802.3ah] clause 64.
This object is applicable for an OLT and an ONU. At the
OLT it has a value for each virtual interface and for
each queue. At the ONU it has a value for each queue.
At the OLT the value should be zero.
Discontinuities of this counter can occur at
re-initialization of the management system, and at other
times as indicated by the value of the
ifCounterDiscontinuityTime."
::= { dot3ExtPkgQueueEntry 6} ::= { dot3ExtPkgQueueEntry 6}
dot3ExtPkgQueueSetsTable OBJECT-TYPE dot3ExtPkgQueueSetsTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot3ExtPkgQueueSetsEntry SYNTAX SEQUENCE OF Dot3ExtPkgQueueSetsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table for Extended package Queue_Sets management "A table of Extended package objects used for the
objects. Entries are control and status indication management of the queue_sets. Entries are control and
objects for an EPON interface which are gathered in an status indication objects of an EPON interface which
extended package as an addition for the [802.3ah] are gathered in an extended package as an addition to
attributes. The objects in this table are specific for the objects based on the [802.3ah] attributes. The
the queue-sets which are reported in the MPCP REPORT objects in this table are specific for the queue_sets
message as defined in [802.3ah] clause 64. which are reported in the MPCP REPORT message as defined
Each object has a row for every virtual link and for in [802.3ah] clause 64.
each queue in the report and for each queue_set in the The [802.3ah] MPCP defines a report of the occupancy of
queue. Typically the number of expected virtual link in the transmit queues for the feedback BW request from the
a PON is like the number of ONUs 32-64 plus an ONUs. These queues serve the uplink transmission of the
additional entry for broadcast LLID (which is marked by ONU and data is gathered there until the ONU is granted
0xffff). In the [802.3ah] the LLID is a 2bytes register for transmission.
and the number of LLIDs is limited by that. The management table of the queues is added here mainly
to gather some statistics of their operation. This table
is not duplicating existing management object of
bridging queues, specified in [802.1d], since the ONU
may not be a bridge device, with embedded bridging
queues and the existence of the transmit queuing
mechanism is implied in the [802.3ah] spec.
The format of the REPORT message, as specified
in [802.3], is presented below:
+-----------------------------------+
| Destination Address |
+-----------------------------------+
| Source Address |
+-----------------------------------+
| Length/Type |
+-----------------------------------+
| OpCode |
+-----------------------------------+
| TimeStamp |
+-----------------------------------+
| Number of queue Sets |
+-----------------------------------+ /|\
| Report bitmap | |
+-----------------------------------+ |
| Queue 0 report | |
+-----------------------------------+ | repeated for
| Queue 1 report | | every
+-----------------------------------+ | queue_set
| Queue 2 report | |
+-----------------------------------+ |
| Queue 3 report | |
+-----------------------------------+ |
| Queue 4 report | |
+-----------------------------------+ |
| Queue 5 report | |
+-----------------------------------+ |
| Queue 6 report | |
+-----------------------------------+ |
| Queue 7 report | |
+-----------------------------------+ \|/
| Pad/reserved |
+-----------------------------------+
| FCS |
+-----------------------------------+
As can be seen from the message format, the ONU device
reports of the status of up to 8 queues and it can
report in a single MPCP REPORT message of a few sets
of queues.
The number of queue_sets defines the number of the
reported sets, and it can reach up to a value of 8. It
means that a device can hold a variable number of sets
between 0 to 7.
The dot3ExtPkgQueueSetsTable table has a variable
queue_set size which is limited by the
dot3ExtPkgObjectReportMaximumNumThreshold object as an
ONU can have fewer queue_sets to report.
The 'Queue report' field reports the occupancy of each
uplink transmission queue. The queue_sets can be used to
report the occupancy of the queues in a few levels as to
allow granting, in an accurate manner, of only part of
the data available in the queues. A Threshold is
defined for each queue_set to define the level of the
queue which is counted for the report of the occupancy.
The threshold is reflected in the queue_set table by the
dot3ExtPkgObjectReportThreshold object.
For each queue set, the report bitmap defines which
queues are present in the report, meaning that
although the MPCP REPORT message can report of up to 8
queues in a REPORT message, the actual number is
flexible.
The dot3ExtPkgQueueSetsTable table has a variable queue
size which is limited by the
dot3ExtPkgObjectReportMaximumNumQueues object as an ONU
can have fewer queues to report.
Each object has a row for every virtual link, for each
queue in the report and for each queue_set in the queue.
Typically the number of expected virtual links in a PON
is like the number of ONUs, which is 32-64, plus an
additional entry for broadcast LLID (with a value of
0xffff).
In the [802.3ah] the LLID is a 2bytes register and the
number of LLIDs is limited by that.
The number of queues is between 0 and 7 and limited by The number of queues is between 0 and 7 and limited by
dot3ExtPkgObjectReportMaximumNumQueues. dot3ExtPkgObjectReportMaximumNumQueues.
The number of queues_sets is between 0 and 7 and limited The number of queues_sets is between 0 and 7 and limited
by dot3ExtPkgObjectReportMaximumNumThreshold." by dot3ExtPkgObjectReportMaximumNumThreshold."
::= { dot3ExtPkgControlObjects 3 } ::= { dot3ExtPkgControlObjects 3 }
dot3ExtPkgQueueSetsEntry OBJECT-TYPE dot3ExtPkgQueueSetsEntry OBJECT-TYPE
SYNTAX Dot3ExtPkgQueueSetsEntry SYNTAX Dot3ExtPkgQueueSetsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An entry in the Extended package Queue sets table. The "An entry in the Extended package queue_set table. At
rows are added for each ifIndex, dot3QueueSetQueueIndex the OLT, the rows exist for each ifIndex,
and dot3QueueSetIndex at the OLT. dot3QueueSetQueueIndex and dot3QueueSetIndex. At the
At the ONU the rows are added for each ONU, rows exist for the single ifIndex, for each
dot3QueueSetQueueIndex, dot3QueueSetIndex and a single dot3QueueSetQueueIndex and dot3QueueSetIndex.
row for the ifIndex. Rows in the table are created when the ifIndexes are
Rows in the table are created when ifIndexs are created. created. A set of rows per queue and per queue_set is
added for each ifIndex, denoted with the
dot3QueueSetIndex and dot3QueueSetQueueIndex.
For the ONU rows are created at system initialization. For the ONU rows are created at system initialization.
For the OLT the rows of the OLT ifIndex and the rows of
For the OLT the rows of the OLT ifIndex and the row of
the ifIndex referring to the broadcast virtual link are the ifIndex referring to the broadcast virtual link are
created at system initialization. For the ifIndexs created at system initialization. For the ifIndexes
referring to the virtual links at the OLT, a row is referring to the virtual links at the OLT, a set of rows
created when a virtual link is established (ONU per queue and queue_set are created when a virtual link
registers) and deleted when the virtual link is deleted is established (ONU registers) and deleted when the
(ONU deregisters). Rows exist for an OLT interface and virtual link is deleted (ONU deregisters)."
an ONU interface."
INDEX { ifIndex, INDEX { ifIndex,
dot3QueueSetQueueIndex,dot3QueueSetIndex} dot3QueueSetQueueIndex,dot3QueueSetIndex}
::= { dot3ExtPkgQueueSetsTable 1 } ::= { dot3ExtPkgQueueSetsTable 1 }
Dot3ExtPkgQueueSetsEntry ::= Dot3ExtPkgQueueSetsEntry ::=
SEQUENCE { SEQUENCE {
dot3QueueSetQueueIndex Unsigned32, dot3QueueSetQueueIndex Unsigned32,
dot3QueueSetIndex Unsigned32, dot3QueueSetIndex Unsigned32,
dot3ExtPkgObjectReportThreshold Unsigned32 dot3ExtPkgObjectReportThreshold Unsigned32
} }
dot3QueueSetQueueIndex OBJECT-TYPE dot3QueueSetQueueIndex OBJECT-TYPE
SYNTAX Unsigned32 (0..7) SYNTAX Unsigned32 (0..7)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A value that identifies the queue index for the queue "An object that identifies the queue index for the
set table. The queues are reported in the MPCP REPORT dot3ExtPkgQueueSetsTable table. The queues are reported
message as defined in [802.3ah] clause 64. in the MPCP REPORT message as defined in [802.3ah]
clause 64.
The number of queues is between 0 and 7 and limited by The number of queues is between 0 and 7 and limited by
dot3ExtPkgObjectReportMaximumNumQueues. dot3ExtPkgObjectReportMaximumNumQueues.
Value corresponds to the dot3QueueIndex of the queue Value corresponds to the dot3QueueIndex of the queue
table." table."
::= { dot3ExtPkgQueueSetsEntry 1 } ::= { dot3ExtPkgQueueSetsEntry 1 }
dot3QueueSetIndex OBJECT-TYPE dot3QueueSetIndex OBJECT-TYPE
SYNTAX Unsigned32 (0..7) SYNTAX Unsigned32 (0..7)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A value that identifies the queue_set index for the "An object that identifies the queue_set index for the
queue_sets table. The queues are reported in the MPCP dot3ExtPkgQueueSetsTable table. The queues are reported
REPORT message as defined in [802.3ah] clause 64. in the MPCP REPORT message as defined in [802.3ah]
The number of queues_sets is between 0 and 7." clause 64.
The number of queues_sets is between 0 and 7. and
limited by dot3ExtPkgObjectReportMaximumNumThreshold."
::= { dot3ExtPkgQueueSetsEntry 2 } ::= { dot3ExtPkgQueueSetsEntry 2 }
dot3ExtPkgObjectReportThreshold OBJECT-TYPE dot3ExtPkgObjectReportThreshold OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "TQ (16nsec)" UNITS "TQ (16nsec)"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An integer that defines the threshold reporting for each "An object that defines the value of threshold report for
Queue_set in the REPORT message, as defined in [802.3ah] each queue_set in the REPORT message, as defined in
64. The number of sets is [802.3ah] clause 64. The number of sets for each queue
dot3ExtPkgObjectReportNumThreshold. Each Queue set is dot3ExtPkgObjectReportNumThreshold.
reporting will provide information on the queue
occupancy of frames below the matching Threshold. In the REPORT message, each queue_set reporting will
provide information on the occupancy of the queues for
frames below the matching Threshold.
The value returned shall be in Time quanta (TQ) which The value returned shall be in Time quanta (TQ) which
is 16nsec or 2 octets increments. is 16nsec or 2 octets increments.
Reading will present the threshold value. Writing will
set the value of the threshold.
Writing can be done at any time. Writing can be done at any time.
This object is relevant for an OLT and an ONU. For the This object is applicable for an OLT and an ONU. At the
OLT there is a value per LLID." OLT it has a value for each virtual interface, for each
queue and for each queue_set. At the ONU it has a value
for each queue and for each queue_set."
DEFVAL { 0 } DEFVAL { 0 }
::= { dot3ExtPkgQueueSetsEntry 3 } ::= { dot3ExtPkgQueueSetsEntry 3 }
--Optical Interface status tables --Optical Interface status tables
dot3ExtPkgOptIfTable OBJECT-TYPE dot3ExtPkgOptIfTable OBJECT-TYPE
SYNTAX SEQUENCE OF Dot3ExtPkgOptIfEntry SYNTAX SEQUENCE OF Dot3ExtPkgOptIfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"This table defines the list of status control and status "This table defines the control and status indication
indication for the optical interface of an EPON objects for the optical interface of the EPON interface.
interface. Each object has a row for every virtual link denoted by
Each object has a row for every virtual link the corresponding ifIndex.
according to the proper ifIndex. Typically the number Typically the number of expected virtual links in a PON
of expected virtual link in a PON is like the number of is like the number of ONUs, which is 32-64, plus an
ONUs 32-64 plus an additional entry for broadcast LLID additional entry for broadcast LLID (with a value of
(which is marked by 0xffff). In the [802.3ah] the LLID 0xffff).
is a 2bytes register and the number of LLIDs limited by In the [802.3ah] the LLID is a 2bytes register and the
that." number of LLIDs is limited by that.
Although the optical interface is a physical interface,
there is a row in the table for each virtual interface.
The reason for having a separate row for each virtual
link is that the OLT has a separate link for each one of
the ONUs. For instance, they could be in different
distances with different link budgets and different
receive powers, therefore having different power alarms.
It is quite similar to a case of different physical
interfaces."
::= { dot3ExtPkgControlObjects 5} ::= { dot3ExtPkgControlObjects 5}
dot3ExtPkgOptIfEntry OBJECT-TYPE dot3ExtPkgOptIfEntry OBJECT-TYPE
SYNTAX Dot3ExtPkgOptIfEntry SYNTAX Dot3ExtPkgOptIfEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Table entries for the Table of optical interfaces "An entry in the optical interface table of the EPON
control and status indication of EPON interfaces. interface.
Rows in the table are created when ifIndexs are created. Rows exist for an OLT interface and an ONU interface.
Rows in the table are denoted by the ifIndexes and they
are created when the ifIndexes are created.
For the ONU rows are created at system initialization. For the ONU rows are created at system initialization.
For the OLT the rows of the OLT ifIndex and the row of For the OLT the row of the OLT ifIndex and the row of
the ifIndex referring to the broadcast virtual link are the ifIndex referring to the broadcast virtual link are
created at system initialization. For the ifIndexs created at system initialization. For the ifIndexes
referring to the virtual links at the OLT, a row is referring to the virtual links at the OLT, a row is
created when a virtual link is established (ONU created when a virtual link is established (ONU
registers) and deleted when the virtual link is deleted registers) and deleted when the virtual link is deleted
(ONU deregisters). Rows exist for an OLT interface and (ONU deregisters)."
an ONU interface."
INDEX { ifIndex } INDEX { ifIndex }
::= { dot3ExtPkgOptIfTable 1 } ::= { dot3ExtPkgOptIfTable 1 }
Dot3ExtPkgOptIfEntry ::= Dot3ExtPkgOptIfEntry ::=
SEQUENCE { SEQUENCE {
dot3ExtPkgOptIfSuspectedFlag TruthValue, dot3ExtPkgOptIfSuspectedFlag TruthValue,
dot3ExtPkgOptIfInputPower Integer32, dot3ExtPkgOptIfInputPower Integer32,
dot3ExtPkgOptIfLowInputPower Integer32, dot3ExtPkgOptIfLowInputPower Integer32,
dot3ExtPkgOptIfHighInputPower Integer32, dot3ExtPkgOptIfHighInputPower Integer32,
dot3ExtPkgOptIfLowerInputPowerThreshold Integer32, dot3ExtPkgOptIfLowerInputPowerThreshold Integer32,
skipping to change at page 61, line 37 skipping to change at page 79, line 45
dot3ExtPkgOptIfSignalDetect TruthValue, dot3ExtPkgOptIfSignalDetect TruthValue,
dot3ExtPkgOptIfTransmitAlarm TruthValue, dot3ExtPkgOptIfTransmitAlarm TruthValue,
dot3ExtPkgOptIfTransmitEnable TruthValue dot3ExtPkgOptIfTransmitEnable TruthValue
} }
dot3ExtPkgOptIfSuspectedFlag OBJECT-TYPE dot3ExtPkgOptIfSuspectedFlag OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"If true, the data in this entry may be unreliable." "If true, the data in this entry may be unreliable.
This object is applicable for an OLT and an ONU. At the
OLT it has a value for each virtual interface."
::= { dot3ExtPkgOptIfEntry 1 } ::= { dot3ExtPkgOptIfEntry 1 }
dot3ExtPkgOptIfInputPower OBJECT-TYPE dot3ExtPkgOptIfInputPower OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS "0.1 dbm" UNITS "0.1 dbm"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The optical power monitored at the input." "The optical power monitored at the input.
This object is applicable for an OLT and an ONU. At the
OLT it has a value for each virtual interface."
::= { dot3ExtPkgOptIfEntry 2 } ::= { dot3ExtPkgOptIfEntry 2 }
dot3ExtPkgOptIfLowInputPower OBJECT-TYPE dot3ExtPkgOptIfLowInputPower OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS "0.1 dbm" UNITS "0.1 dbm"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The lowest optical power monitored at the input during the "The lowest optical power monitored at the input during the
current 15-minute interval." current 15-minute interval.
This object is applicable for an OLT and an ONU. At the
OLT it has a value for each virtual interface."
::= { dot3ExtPkgOptIfEntry 3 } ::= { dot3ExtPkgOptIfEntry 3 }
dot3ExtPkgOptIfHighInputPower OBJECT-TYPE dot3ExtPkgOptIfHighInputPower OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS "0.1 dbm" UNITS "0.1 dbm"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The highest optical power monitored at the input during the "The highest optical power monitored at the input during the
current 15-minute interval." current 15-minute interval.
This object is applicable for an OLT and an ONU. At the
OLT it has a value for each virtual interface."
::= { dot3ExtPkgOptIfEntry 4 } ::= { dot3ExtPkgOptIfEntry 4 }
dot3ExtPkgOptIfLowerInputPowerThreshold OBJECT-TYPE dot3ExtPkgOptIfLowerInputPowerThreshold OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS "0.1 dbm" UNITS "0.1 dbm"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The lower limit threshold on input power. If "The lower limit threshold on input power. If
dot3ExtPkgOptIfInputPower drops to this value or below, dot3ExtPkgOptIfInputPower drops to this value or below,
a Threshold Crossing Alert (TCA) should be sent." a Threshold Crossing Alert (TCA) should be sent.
Reading will present the threshold value. Writing will
set the value of the threshold.
Writing can be done at any time.
This object is applicable for an OLT and an ONU. At the
OLT it has a value for each virtual interface."
::= { dot3ExtPkgOptIfEntry 5 } ::= { dot3ExtPkgOptIfEntry 5 }
dot3ExtPkgOptIfUpperInputPowerThreshold OBJECT-TYPE dot3ExtPkgOptIfUpperInputPowerThreshold OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS "0.1 dbm" UNITS "0.1 dbm"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The upper limit threshold on input power. If "The upper limit threshold on input power. If
dot3ExtPkgOptIfInputPower reaches or exceeds this value, dot3ExtPkgOptIfInputPower reaches or exceeds this value,
a Threshold Crossing Alert (TCA) should be sent." a Threshold Crossing Alert (TCA) should be sent.
Reading will present the threshold value. Writing will
set the value of the threshold.
Writing can be done at any time.
This object is applicable for an OLT and an ONU. At the
OLT it has a value for each virtual interface."
::= { dot3ExtPkgOptIfEntry 6 } ::= { dot3ExtPkgOptIfEntry 6 }
dot3ExtPkgOptIfOutputPower OBJECT-TYPE dot3ExtPkgOptIfOutputPower OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS "0.1 dbm" UNITS "0.1 dbm"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The optical power monitored at the output." "The optical power monitored at the output.
This object is applicable for an OLT and an ONU. At the
OLT it has a value for each virtual interface."
::= { dot3ExtPkgOptIfEntry 7 } ::= { dot3ExtPkgOptIfEntry 7 }
dot3ExtPkgOptIfLowOutputPower OBJECT-TYPE dot3ExtPkgOptIfLowOutputPower OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS "0.1 dbm" UNITS "0.1 dbm"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The lowest optical power monitored at the output during the "The lowest optical power monitored at the output during the
current 15-minute interval." current 15-minute interval.
This object is applicable for an OLT and an ONU. At the
OLT it has a value for each virtual interface."
::= { dot3ExtPkgOptIfEntry 8 } ::= { dot3ExtPkgOptIfEntry 8 }
dot3ExtPkgOptIfHighOutputPower OBJECT-TYPE dot3ExtPkgOptIfHighOutputPower OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS "0.1 dbm" UNITS "0.1 dbm"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The highest optical power monitored at the output during the "The highest optical power monitored at the output during the
current 15-minute interval." current 15-minute interval.
This object is applicable for an OLT and an ONU. At the
OLT it has a value for each virtual interface."
::= { dot3ExtPkgOptIfEntry 9 } ::= { dot3ExtPkgOptIfEntry 9 }
dot3ExtPkgOptIfLowerOutputPowerThreshold OBJECT-TYPE dot3ExtPkgOptIfLowerOutputPowerThreshold OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS "0.1 dbm" UNITS "0.1 dbm"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The lower limit threshold on output power. If "The lower limit threshold on output power. If
dot3ExtPkgOptIfOutputPower drops to this value or below, dot3ExtPkgOptIfOutputPower drops to this value or below,
a Threshold Crossing Alert (TCA) should be sent." a Threshold Crossing Alert (TCA) should be sent.
Reading will present the threshold value. Writing will
set the value of the threshold.
Writing can be done at any time.
This object is applicable for an OLT and an ONU. At the
OLT it has a value for each virtual interface."
::= { dot3ExtPkgOptIfEntry 10 } ::= { dot3ExtPkgOptIfEntry 10 }
dot3ExtPkgOptIfUpperOutputPowerThreshold OBJECT-TYPE dot3ExtPkgOptIfUpperOutputPowerThreshold OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
UNITS "0.1 dbm" UNITS "0.1 dbm"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The upper limit threshold on output power. If "The upper limit threshold on output power. If
dot3ExtPkgOptIfOutputPower reaches or exceeds this value, dot3ExtPkgOptIfOutputPower reaches or exceeds this value,
a Threshold Crossing Alert (TCA) should be sent." a Threshold Crossing Alert (TCA) should be sent.
Reading will present the threshold value. Writing will
set the value of the threshold.
Writing can be done at any time.
This object is applicable for an OLT and an ONU. At the
OLT it has a value for each virtual interface."
::= { dot3ExtPkgOptIfEntry 11 } ::= { dot3ExtPkgOptIfEntry 11 }
dot3ExtPkgOptIfSignalDetect OBJECT-TYPE dot3ExtPkgOptIfSignalDetect OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"When getting true(1) there is a valid optical signal at "When getting true(1) there is a valid optical signal at
the receive which is above the optical power level for the receive, that is above the optical power level for
signal detection. When getting false(2) the optical signal detection. When getting false(2) the optical
signal at the receive is below the optical power level signal at the receive is below the optical power level
for signal detection. for signal detection.
This object is relevant for an OLT and an ONU." This object is applicable for an OLT and an ONU. At the
OLT it has a value for each virtual interface."
DEFVAL { false } DEFVAL { false }
::= { dot3ExtPkgOptIfEntry 12 } ::= { dot3ExtPkgOptIfEntry 12 }
dot3ExtPkgOptIfTransmitAlarm OBJECT-TYPE dot3ExtPkgOptIfTransmitAlarm OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"When getting true(1) there is a non-valid optical signal "When getting true(1) there is a non-valid optical signal
at the transmit of the interface, either a higher level at the transmit of the interface, either a higher level
or lower level than expected. When getting false(2) the or lower level than expected. When getting false(2) the
optical signal at the transmit is valid and in the optical signal at the transmit is valid and in the
required range. required range.
This object is relevant for an OLT and an ONU." This object is applicable for an OLT and an ONU. At the
OLT it has a value for each virtual interface."
DEFVAL { false } DEFVAL { false }
::= { dot3ExtPkgOptIfEntry 13 } ::= { dot3ExtPkgOptIfEntry 13 }
dot3ExtPkgOptIfTransmitEnable OBJECT-TYPE dot3ExtPkgOptIfTransmitEnable OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Setting this variable to true(1) will cause the optical "Setting this object to true(1) will cause the optical
interface to start transmission (according to the interface to start transmission (according to the
control protocol specified for the logical interface). control protocol specified for the logical interface).
Setting this variable to false(2) will cause the Setting this object to false(2) will cause the
interface to stop the optical transmission. interface to stop the optical transmission.
When getting true(1) the optical interface is in When getting true(1) the optical interface is in
transmit mode (obeying to the logical control protocol). transmitting mode (obeying to the logical control
protocol).
When getting false(2) the optical interface is not in When getting false(2) the optical interface is not in
transmit mode. transmitting mode.
Writing can be done at any time. Writing can be done at any time.
The variable is relevant when the admin state of the The object is relevant when the admin state of the
device is active as set by the dot3MpcpAdminState. device is active as set by the dot3MpcpAdminState.
This object is relevant for an OLT and an ONU." This object is applicable for an OLT and an ONU. At the
OLT it has a value for each virtual interface."
DEFVAL { false } DEFVAL { false }
::= { dot3ExtPkgOptIfEntry 14 } ::= { dot3ExtPkgOptIfEntry 14 }
-- Conformance Statements -- Conformance Statements
-- Conformance Groups -- Conformance Groups
dot3EponGroups OBJECT IDENTIFIER ::= { dot3EponConformance 1 } dot3EponGroups OBJECT IDENTIFIER ::= { dot3EponConformance 1 }
dot3MpcpGroupBase OBJECT-GROUP dot3MpcpGroupBase OBJECT-GROUP
OBJECTS { OBJECTS {
skipping to change at page 66, line 9 skipping to change at page 85, line 9
Objects are per LLID." Objects are per LLID."
::= { dot3EponGroups 2 } ::= { dot3EponGroups 2 }
dot3OmpeGroupID OBJECT-GROUP dot3OmpeGroupID OBJECT-GROUP
OBJECTS { OBJECTS {
dot3OmpEmulationType dot3OmpEmulationType
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects of dot3 OMP emulation ID entity "A collection of objects of dot3 OMP emulation entity
state definition. Objects are per LLID." state definition. Objects are per LLID."
::= { dot3EponGroups 3 } ::= { dot3EponGroups 3 }
dot3OmpeGroupStat OBJECT-GROUP dot3OmpeGroupStat OBJECT-GROUP
OBJECTS { OBJECTS {
dot3OmpEmulationSLDErrors, dot3OmpEmulationSLDErrors,
dot3OmpEmulationCRC8Errors, dot3OmpEmulationCRC8Errors,
dot3OmpEmulationBadLLID, dot3OmpEmulationBadLLID,
dot3OmpEmulationGoodLLID, dot3OmpEmulationGoodLLID,
dot3OmpEmulationOnuPonCastLLID, dot3OmpEmulationOnuPonCastLLID,
skipping to change at page 66, line 43 skipping to change at page 85, line 43
OBJECTS { OBJECTS {
dot3EponFecPCSCodingViolation, dot3EponFecPCSCodingViolation,
dot3EponFecAbility, dot3EponFecAbility,
dot3EponFecMode, dot3EponFecMode,
dot3EponFecCorrectedBlocks, dot3EponFecCorrectedBlocks,
dot3EponFecUncorrectableBlocks, dot3EponFecUncorrectableBlocks,
dot3EponFecBufferHeadCodingViolation dot3EponFecBufferHeadCodingViolation
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects of FEC group definition. "A collection of objects of dot3 FEC group control and
Objects are per LLID." statistics. Objects are per LLID."
::= { dot3EponGroups 5 } ::= { dot3EponGroups 5 }
dot3ExtPkgGroupControl OBJECT-GROUP dot3ExtPkgGroupControl OBJECT-GROUP
OBJECTS { OBJECTS {
dot3ExtPkgObjectReset, dot3ExtPkgObjectReset,
dot3ExtPkgObjectPowerDown, dot3ExtPkgObjectPowerDown,
dot3ExtPkgObjectNumberOfLLIDs, dot3ExtPkgObjectNumberOfLLIDs,
dot3ExtPkgObjectFecEnabled, dot3ExtPkgObjectFecEnabled,
dot3ExtPkgObjectReportMaximumNumQueues, dot3ExtPkgObjectReportMaximumNumQueues,
dot3ExtPkgObjectRegisterAction dot3ExtPkgObjectRegisterAction
skipping to change at page 67, line 29 skipping to change at page 86, line 29
OBJECTS { OBJECTS {
dot3ExtPkgObjectReportNumThreshold, dot3ExtPkgObjectReportNumThreshold,
dot3ExtPkgObjectReportMaximumNumThreshold, dot3ExtPkgObjectReportMaximumNumThreshold,
dot3ExtPkgStatTxFramesQueue, dot3ExtPkgStatTxFramesQueue,
dot3ExtPkgStatRxFramesQueue, dot3ExtPkgStatRxFramesQueue,
dot3ExtPkgStatDroppedFramesQueue dot3ExtPkgStatDroppedFramesQueue
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects of dot3ExtPkg Queue "A collection of objects of dot3ExtPkg Queue
definition. Objects are per LLID, per queue." control. Objects are per LLID, per queue."
::= { dot3EponGroups 7 } ::= { dot3EponGroups 7 }
dot3ExtPkgGroupQueueSets OBJECT-GROUP dot3ExtPkgGroupQueueSets OBJECT-GROUP
OBJECTS { OBJECTS {
dot3ExtPkgObjectReportThreshold dot3ExtPkgObjectReportThreshold
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects of dot3ExtPkg Queue_sets "A collection of objects of dot3ExtPkg queue_set
definition. Objects are per LLID, per queue, per control. Objects are per LLID, per queue, per
queue_set." queue_set."
::= { dot3EponGroups 8 } ::= { dot3EponGroups 8 }
dot3ExtPkgGroupOptIf OBJECT-GROUP dot3ExtPkgGroupOptIf OBJECT-GROUP
OBJECTS { OBJECTS {
dot3ExtPkgOptIfSuspectedFlag, dot3ExtPkgOptIfSuspectedFlag,
dot3ExtPkgOptIfInputPower, dot3ExtPkgOptIfInputPower,
dot3ExtPkgOptIfLowInputPower, dot3ExtPkgOptIfLowInputPower,
dot3ExtPkgOptIfHighInputPower, dot3ExtPkgOptIfHighInputPower,
dot3ExtPkgOptIfLowerInputPowerThreshold, dot3ExtPkgOptIfLowerInputPowerThreshold,
skipping to change at page 68, line 16 skipping to change at page 87, line 16
dot3ExtPkgOptIfLowOutputPower, dot3ExtPkgOptIfLowOutputPower,
dot3ExtPkgOptIfHighOutputPower, dot3ExtPkgOptIfHighOutputPower,
dot3ExtPkgOptIfLowerOutputPowerThreshold, dot3ExtPkgOptIfLowerOutputPowerThreshold,
dot3ExtPkgOptIfUpperOutputPowerThreshold, dot3ExtPkgOptIfUpperOutputPowerThreshold,
dot3ExtPkgOptIfSignalDetect, dot3ExtPkgOptIfSignalDetect,
dot3ExtPkgOptIfTransmitAlarm, dot3ExtPkgOptIfTransmitAlarm,
dot3ExtPkgOptIfTransmitEnable dot3ExtPkgOptIfTransmitEnable
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A collection of objects of Optical interface control and "A collection of objects of control and status indication
status indication for the EPON Interfaces. of the optical interface for the EPON Interfaces.
Objects are per LLID." Objects are per LLID."
::= { dot3EponGroups 9 } ::= { dot3EponGroups 9 }
-- Compliance -- Compliance
dot3EponCompliances dot3EponCompliances
OBJECT IDENTIFIER ::= { dot3EponConformance 2 } OBJECT IDENTIFIER ::= { dot3EponConformance 2 }
dot3MPCPCompliance MODULE-COMPLIANCE dot3MPCPCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION "The compliance statement for Multi-point DESCRIPTION "The compliance statement for Multi-Point
control protocol interfaces." control protocol interfaces."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { dot3MpcpGroupBase} MANDATORY-GROUPS { dot3MpcpGroupBase}
GROUP dot3MpcpGroupStat GROUP dot3MpcpGroupStat
DESCRIPTION "This group is mandatory for all MPCP supporting DESCRIPTION "This group is mandatory for all MPCP supporting
interfaces for Statistics collection." interfaces for statistics collection."
::= { dot3EponCompliances 1} ::= { dot3EponCompliances 1}
dot3OmpeCompliance MODULE-COMPLIANCE dot3OmpeCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION "The compliance statement for OMPEmulation DESCRIPTION "The compliance statement for OMPEmulation
interfaces." interfaces."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { dot3OmpeGroupID} MANDATORY-GROUPS { dot3OmpeGroupID}
GROUP dot3OmpeGroupStat GROUP dot3OmpeGroupStat
DESCRIPTION "This group is mandatory for all OMPemulation DESCRIPTION "This group is mandatory for all OMPemulation
supporting interfaces for Statistics collection." supporting interfaces for statistics collection."
::= { dot3EponCompliances 2} ::= { dot3EponCompliances 2}
dot3EponFecCompliance MODULE-COMPLIANCE dot3EponFecCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION "The compliance statement for Fec EPON interfaces. DESCRIPTION "The compliance statement for FEC EPON interfaces.
This group is mandatory for all EPON interfaces This group is mandatory for all EPON interfaces
Supporting FEC functionality as for Definitions and supporting FEC functionality of control and
BER Statistics collection." statistics collection."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { dot3EponFecGroupAll } MANDATORY-GROUPS { dot3EponFecGroupAll }
::= { dot3EponCompliances 3} ::= { dot3EponCompliances 3}
dot3ExtPkgCompliance MODULE-COMPLIANCE dot3ExtPkgCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION "The compliance statement for EPON Interfaces DESCRIPTION "The compliance statement for EPON Interfaces
using the extended package." using the extended package."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { dot3ExtPkgGroupControl } MANDATORY-GROUPS { dot3ExtPkgGroupControl }
GROUP dot3ExtPkgGroupQueue GROUP dot3ExtPkgGroupQueue
DESCRIPTION " This group is mandatory for all OLT EPON interfaces DESCRIPTION " This group is mandatory for all EPON interfaces
supporting Report Queue management of the extended supporting REPORT queue management of the extended
package." package."
GROUP dot3ExtPkgGroupQueueSets GROUP dot3ExtPkgGroupQueueSets
DESCRIPTION " This group is mandatory for all OLT EPON interfaces DESCRIPTION " This group is mandatory for all EPON interfaces
supporting Report Queue_sets management of the supporting REPORT queue_sets management of the
extended package." extended package."
GROUP dot3ExtPkgGroupOptIf GROUP dot3ExtPkgGroupOptIf
DESCRIPTION "This group is mandatory for all EPON interfaces DESCRIPTION "This group is mandatory for all EPON interfaces
supporting optical interfaces control and indication supporting optical interfaces management,
of the extended package." of the extended package."
::= { dot3EponCompliances 4} ::= { dot3EponCompliances 4}
END END
6. IANA Considerations 6. IANA Considerations
The DOT3 EPON MIB module requires the allocation of a single object The DOT3 EPON MIB module requires the allocation of a single object
identifier for its MODULE-IDENTITY under the MIB-2 tree. identifier for its MODULE-IDENTITY under the MIB-2 tree.
skipping to change at page 73, line 9 skipping to change at page 92, line 9
enable cryptographic security. It is then a customer/operator enable cryptographic security. It is then a customer/operator
responsibility to ensure that the SNMP entity giving access to an responsibility to ensure that the SNMP entity giving access to an
instance of this MIB module is properly configured to give access to instance of this MIB module is properly configured to give access to
the objects only to those principals (users) that have legitimate the objects only to those principals (users) that have legitimate
rights to indeed GET or SET (change/create/delete) them. rights to indeed GET or SET (change/create/delete) them.
8. References 8. References
8.1. Normative References 8.1. Normative References
[802.1d] IEEE, "Institute of Electrical and Electronic Engineers,
802.1D-2004, IEEE Standard for Local and metropolitan area
networks Media Access Control (MAC) Bridges.", June 2004.
[802.3] IEEE, "Institute of Electrical and Electronic Engineers, [802.3] IEEE, "Institute of Electrical and Electronic Engineers,
IEEE Std 802.3-2002, "IEEE Standard for Carrier Sense IEEE Std 802.3-2002, "IEEE Standard for Carrier Sense
Multiple Access with Collision Detection (CSMA/CD) Access Multiple Access with Collision Detection (CSMA/CD) Access
Method and Physical Layer Specifications", December 2002. Method and Physical Layer Specifications.", December 2002.
[802.3ah] IEEE, "Institute of Electrical and Electronic Engineers, [802.3ah] IEEE, "Institute of Electrical and Electronic Engineers,
IEEE Std 802.3ah-2004. Information technology - IEEE Std 802.3ah-2004. Information technology -
Telecommunications and information exchange between Telecommunications and information exchange between
systems - Local and metropolitan area networks - Specific systems - Local and metropolitan area networks - Specific
requirements - Part 3: Carrier sense multiple access with requirements - Part 3: Carrier sense multiple access with
collision detection (CSMA/CD) access method and physical collision detection (CSMA/CD) access method and physical
layer specifications - Media Access Control Parameters, layer specifications - Media Access Control Parameters,
Physical Layers and Management Parameters for subscriber Physical Layers and Management Parameters for subscriber
access networks", IEEE Std 802.3ah-2004, October 2004. access networks.", IEEE Std 802.3ah-2004, October 2004.
[ITU-T G.975]
ITU, "ITU-T, SERIES G: TRANSMISSION SYSTEMS AND MEDIA,
DIGITAL SYSTEMS AND NETWORKS Digital sections and digital
line system - Optical fibre submarine cable systems
Forward error correction for submarine systems, ITU-T
Recommendation G.975", October 2000.
[ITU-T G.983]
ITU, "ITU-T, SERIES G: TRANSMISSION SYSTEMS AND MEDIA,
DIGITAL SYSTEMS AND NETWORKS, Digital transmission systems
- Digital sections and digital line system - Optical line
systems for local and access networks Broadband optical
access systems based on Passive Optical Networks (PON),
ITU-T Recommendation G.983.1", October 1998.
[RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2578] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Structure of Management Information Schoenwaelder, Ed., "Structure of Management Information
Version 2 (SMIv2)", STD 58, RFC 2578, April 1999. Version 2 (SMIv2)", STD 58, RFC 2578, April 1999.
[RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J. [RFC2579] McCloghrie, K., Ed., Perkins, D., Ed., and J.
Schoenwaelder, Ed., "Textual Conventions for SMIv2", Schoenwaelder, Ed., "Textual Conventions for SMIv2",
STD 58, RFC 2579, April 1999. STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder, [RFC2580] McCloghrie, K., Perkins, D., and J. Schoenwaelder,
skipping to change at page 73, line 49 skipping to change at page 93, line 19
[RFC2864] McCloghrie, K. and G. Hanson, "The Inverted Stack Table [RFC2864] McCloghrie, K. and G. Hanson, "The Inverted Stack Table
Extension to the Interfaces Group MIB", RFC 2864, Extension to the Interfaces Group MIB", RFC 2864,
June 2000. June 2000.
[RFC3635] Flick, J., "Definitions of Managed Objects for the [RFC3635] Flick, J., "Definitions of Managed Objects for the
Ethernet-like Interface Types", RFC 3635, September 2003. Ethernet-like Interface Types", RFC 3635, September 2003.
[RFC3636] Flick, J., "Definitions of Managed Objects for IEEE 802.3 [RFC3636] Flick, J., "Definitions of Managed Objects for IEEE 802.3
Medium Attachment Units (MAUs)", RFC 3636, September 2003. Medium Attachment Units (MAUs)", RFC 3636, September 2003.
[RFC3636bis-03]
Beili, E., "Definitions of Managed Objects for IEEE 802.3
Medium Attachment Units (MAUs)
draft-ietf-hubmib-rfc3636bis-03.txt",
draft-ietf-hubmib-rfc3636bis-03.txt (work in progress),
June 2006.
8.2. Informative References 8.2. Informative References
[I-D.ietf-hubmib-efm-mib] [I-D.ietf-hubmib-efm-mib]
Squire, M., "Ethernet in the First Mile (EFM) Common MIB", Squire, M., "Definitions and Managed Objects for OAM
draft-squire-hubmib-efm-mib-02 (work in progress), Functions on Ethernet Like Interfaces",
December 2004. draft-ietf-hubmib-efm-mib-04 (work in progress),
March 2006.
[RFC1525] Decker, E., McCloghrie, K., Langille, P., and A. [RFC1525] Decker, E., McCloghrie, K., Langille, P., and A.
Rijsinghani, "Definitions of Managed Objects for Source Rijsinghani, "Definitions of Managed Objects for Source
Routing Bridges", RFC 1525, September 1993. Routing Bridges", RFC 1525, September 1993.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, March 1997. Requirement Levels", BCP 14, RFC 2119, March 1997.
[RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart, [RFC3410] Case, J., Mundy, R., Partain, D., and B. Stewart,
"Introduction and Applicability Statements for Internet- "Introduction and Applicability Statements for Internet-
Standard Management Framework", RFC 3410, December 2002. Standard Management Framework", RFC 3410, December 2002.
[RFC4188] Norseth, K. and E. Bell, "Definitions of Managed Objects [RFC4188] Norseth, K. and E. Bell, "Definitions of Managed Objects
for Bridges", RFC 4188, September 2005. for Bridges", RFC 4188, September 2005.
Author's Address Author's Address
Lior Khermosh Lior Khermosh
Passave Technologies PMC-SIERRA
Kohav Hertzelia bldg, Kohav Hertzelia bldg,
4 Hasadnaot St., 4 Hasadnaot St.,
Hertzliya Pituach, 46120 Hertzliya Pituach, 46120
ISRAEL ISRAEL
Phone: +972-9-9628000 Ext: 302 Phone: +972-9-9628000 Ext: 302
Fax: +972-9-9628001 Fax: +972-9-9628001
Email: lior.khermosh@passave.com Email: lior_khermosh@pmc-sierra.com
Intellectual Property Statement Intellectual Property Statement
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
Intellectual Property Rights or other rights that might be claimed to Intellectual Property Rights or other rights that might be claimed to
pertain to the implementation or use of the technology described in pertain to the implementation or use of the technology described in
this document or the extent to which any license under such rights this document or the extent to which any license under such rights
might or might not be available; nor does it represent that it has might or might not be available; nor does it represent that it has
made any independent effort to identify any such rights. Information made any independent effort to identify any such rights. Information
on the procedures with respect to rights in RFC documents can be on the procedures with respect to rights in RFC documents can be
 End of changes. 315 change blocks. 
982 lines changed or deleted 1861 lines changed or added

This html diff was produced by rfcdiff 1.32. The latest version is available from http://www.levkowetz.com/ietf/tools/rfcdiff/